At 01:53 PM 10/31/2003 -0500, you wrote:
Glenn Parsons wrote:If this is an unrelated question, please let me know:If this is the case, why does SpamAssassin not work on the RaQ AT ALL, until you start using procmail to call spamc (sorry!) to handle incoming mail?/etc/procmailrc: DROPPRIVS=yes # :0fw * < 256000 | spamc I ask because, I'd like to understand all of this a lot better.Well, SpamAssassin will work when called from MailScanner. (You need to make sure you have it switched on and you're looking for the correct mail headers to recognize spam. IIRC, set "Spam Checks = yes" and "Use SpamAssassin = yes" in /etc/MailScanner/MailScanner.conf, and set your e-mail client to look for X-%org-name%-MailScanner-SpamScore where %org-name% is whatever you've set for your local organization in the same file.)Regards, Richard.
Ah, I see. It is possible you are relating your experience with MailScanner 4.x and I am relating mine with MailScanner 3.22, which was made fantastically popular by Bassi's PKG. I now run 4.24, but only have a week's experience under my belt with it. I could not get SpamAssassin to work under MailScanner 3.22 without plugging in through procmail. I didn't think to remove the /etc/procmailrc to see if it would work without it after the upgrade.
Most (not all) Cobalt users will stay at 3.22 because of the difficulties of the upgrade.
Thanks,Glenn