The 03.05.24 at 13:09, Jon Clausen wrote:
Which works *very* well indeed:
I enabled spamd through YaST yesterday, and changed the procmail line from | spamassassin -a to | spamc
-and I haven't even *received* any spam since!!! ;)
Good! :-) But you know that simply calling spamc is not enough: that only pass all mail though the filter, adding appropiate headers and such. Then, you need your email client filters, or procmail itself (probably faster) to do the job. The rule I have in .procmailrc is: :0fw | /usr/bin/spamc :0 a: * ^X-Spam-Status: Yes $HOME/Mail/in_spam Some people send it to dev/null directly, but I don't trust it so much. I have some legitimate emails marked as spam now and then...
Which means that I don't *actually* know if spamd/spamc works, because there hasn't been anything for it to catch... A highly unusual situation... may it last forever :)
Turn "full headers on" on your email viewer, and you will notice the line(s) added by SpamAssassin. Your's has: X-Spam-Status: No, hits=-29.5 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,FROM_ENDS_IN_NUMS,IN_REP_TO, QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_MUTT autolearn=ham version=2.53 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) I'll have to read the docs carefully, I saw something about sending spam that passes the filter somewhere so that it is detected next time. I wonder if that address is local or remote :-? -- Cheers, Carlos Robinson