rblcheck: A command-line interface to RBL-style listings | ||
---|---|---|
<<< Previous | Building | Next >>> |
If you're distributing a pre-built version of rblcheck for your users, I strongly recommend leaving everything in sites.h commented out. The ability to add sites there was only added as a convenience feature for people building a personal copy for their own use, and was never intended to be used to pre-set policy for people using pre-packaged versions.
Over the years, there has been a great deal of volatility in the RBL listing "market"; even the venerable MAPS RBL is no longer publically available without making special arrangements. Therefore, along with those pre-defined lists of RBL services is built-in obsolescence.
As a side-note, I don't make new releases just to update the sites.h file, and at some point in the future, I'll probably stop seeding it with suggestions. As the package maintainer, you're taking on the burden of keeping that up-to-date. Do you really want that hassle, or would it just be easier to point your users at a list of RBL services that is up-to-date (see the rblcheck homepage for links to several current listings)?
You're also making life a more difficult for the user; users will come to depend on that pre-built list of sites. What happens when, by necessity, you need to change that built-in list (because some listings are no longer available, or because new ones are now online)? Your users will very likely complain about the change in behavior, and rightly so. Even worse, what does the user do when they disagree with your selection of services? Recompile from source (which defeats the purpose of providing them with a pre-compiled binary in the first place)? Let them pick their own listings. You and your users will be much happier.
If you feel that you just can't release rblcheck without a built-in list, may I suggest using the global rblcheckrc which the rbl script uses? At least that way, the end user can change your pre-selections on their own, without having to build from source.
<<< Previous | Home | Next >>> |
Note to developers | Up | Using |