The product could be compile-time such as this idea submitted by DFS of Roaring Penguin:

$ perl Makefile.PL
[...]

The following RBLs have certain usage restrictions.  Would you like to
enable them?  If unsure, say Y.  (Y/N): [Y]
[... a list of RBLs, preferably with links to their policy pages ...]

so that at installation time, SA users are at least aware of the issues.

For package maintainers, you'd want a noninteractive way to build SpamAssassin
and then a post-install configuration script that asks the RBL question.
(This is easily done on Debian; not so easy with RPM-based systems that
don't allow interaction during installation.)


- or -


Something like Martin Gregorie's idea:

...it won't work for the package installs that I and, at a guess, a
lot of small installations use. I run the Fedora distro, and so the
version of SA I'm running is that installed and periodically updated by
yum.

I like the idea of the tool though, particularly if it can link to
descriptions of each RBL and, hopefully, to the masscheck results for
it. From my POV a post-install tool, and especially one that can be
re-run periodically, would be a lot more useful.


This may cross-over to the idea to disable queries as discussed in bug 6724 as split into bug 6728 and a way to list the rules that should be disabled for a DNSBL.