We're using spamassassin 3.1.7 on a slack-10 box, invoked via cron.
I'm having problems getting a domain whitelisted. Previously, adding
domains to be whitelisted simply meant adding a whitelist_from *...@domain.com
to my /opt/MailScanner/etc/spam.assassin.prefs.conf file.
Now, however, my
/var/log/maillog output:
May 13 10:53:46 cerberus MailScanner[3309]: Message n4DFrTip004779 from
63.93.193.30 (a...@easymatch.com) to saintjoe.edu http://saintjoe.edu/ is
spam, SpamAssassin (not cached, score=68.739, required 4, AWL -33.17,
BAYES_50 0.00, FORGED_RCVD_HELO 0.14, HTML_30_40
Well maybe you should figure out what is going on with these two: RE_PASSWORD
100.00, RE_PASSWORDV 100.00
since your choice of -100 (it is not a magic pass value, just another factor
in the arithmetic) for your manual whitelist only counteracts one of them ...
or run your manual whitelist score
On Wed, 2009-05-13 at 11:16 -0500, Michael Lyon wrote:
We're using spamassassin 3.1.7 on a slack-10 box, invoked via cron.
I suggest upgrading. That's quite ancient...
I'm having problems getting a domain whitelisted. Previously, adding
domains to be whitelisted simply meant adding a
Please always keep threads on-list by replying to list. I am not the
only one, who can help you.
On Wed, 2009-05-13 at 11:57 -0500, Michael Lyon wrote:
But...how do I remove an autowhitelist entry for just one user? I
have a rule that was duplicated and causing me problems (It was to
prevent
