Please provide the complete output of spamassassin --lint -D

On 8/18/2007 3:02 AM, MaraBlue wrote:
> I've used custom rules in /etc/mail/spamassassin/ since v3.1.7 with
> never a problem. Since upgrading to v3.2.3, it's as if SpamAssassin isn't
> seeing/registering the same rules that have always worked.
> I'm running SpamAssassin on CentOS 4.5, with cPanel and through a
> MailScanner package, so spamd is disabled through cPanel.
> Any time I've added a custom rule I make sure it passes lint, then reload
> MailScanner. I've never had a problem with SA not "acknowledging" the rules
> in until v3.2.3. This version isn't seeing rules that have been
> there several versions back.
> I've run --lint -D, and SA is reading (I can post the log if
> needed). The only other thing I changed a few days before this started was
> switching from using's SARE channels to I can't
> imagine that change would have caused this, though, and the rules pass lint.
> SA is just...chosing to ignore them.
> I'm completely perplexed on what to do, aside from downgrading to a
> previously known working (for me) version. Any ideas on what to check/change
> would be appreciated.