[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Spamassassin problems




Mike, I'm having a few problems since the upgrade too, but things are getting better. I'm not getting a "ton" of spam - Just a couple a day getting through that didn't previously with v2.64. Check out the Spamassassin Archives (search trusted networks for starters), the SpamAssassin Wiki, and then post your question(s) to the Spamassassin users mail list. I would offer to help you myself, but I barely understand my own config! ;-) John



Thanks John. I'm sort of thinking this might be a debian specific problem. Not a spamassassin problem. Otherwise the configuration I posted 'should' be working with 3.0.x and it 'was' working with 3.0.x until something else happened. Like another sarge package updated that breaks spamc/spamd or something.

One thing I have done since then is switched it to use the perl implimentation that most people use. e.g.

from;
/etc/procmailrc ---------------------------------------------------------------------------------
DROPPRIVS=yes
:0fw: spamassassin.lock
* < 256000
| spamc

to;
/etc/procmailrc ---------------------------------------------------------------------------------
DROPPRIVS=yes
:0fw: spamassassin.lock
* < 256000
| spamassassin


And now everything works correctly. (which isn't really what I wanted to do.....)

-Mike



Reply to: