Ronald I. Nutter wrote:
If you are putting the blacklist_from lines in the 90_blacklist.cf fine in /usr/share/spamassassin it may be over written when you upgrade. I'm not sure how postfix/amavisd uses the results from spamd, but your local.cf (and .pre's for 3.0.x and up) should be in /etc/mail/spamassassin.I have spam coming through that I havent been able to block with the blacklist command. Tried putting it in a 90_blacklist.cf file. thought it was working but things are still coming through. I am using a setup with postfix/amavisd that calls the daemonized version of SA. Should the blacklist command be put in a local.cf file instead of where I have been trying it ? Next question is where should the local.cf file reside - in /usr/share/spamassassin ?Thanks, Ron
I have several lines of blacklist_from in separate file in my /etc/mail/spamassassin path called 'localbl.cf' where I have a line for each blacklist entry. It would be good to show the list some headers where the blacklist_from is not hitting. Also, be sure you restart spamd each time you add/change a setting from any file.
HTH -- Thanks, JamesDR
smime.p7s
Description: S/MIME Cryptographic Signature
