> Well, user rules are always allowed when 'spamassassin' is run so a --lint
> message would have to say "if you plan on using spamd your user rules
won't be
> used".
>
> On the other hand, spamd when called with -Dconfig, will tell you it's not
> parsing each of your user rules.
>
> So... do we really want to nag people using 'spamassassin' about their
user rules?
IMO, assuming SA has read local.cf or the equivalent (which I assume to be
the case even when run as "spamassassin --lint"), SA should remember if
allow_user_rules exists in that file, even if it overrides the value for
current processing.
If sa then discovers
if (lint && !had_allow_user_rules && user_rule_file_exists) warn "This
ain't gonna work..";
Or something along those lines.
