On Fri, 2008-07-18 at 18:32 -0400, David Ronis wrote:
> I use evolution as my mail client. Evolution supports spamassassin and
> in the past I let evolution use spamassassin to filter incoming mail.
> Recently, I switched to spam filtering using procmail. The relevant
> section of my my .procmailrc file is:
Good move. ;)
> :0fw: spamc.lock
> * < 256000
> | spamc
>
> # Mails with a score of 15 or higher are almost certainly spam (with 0.05%
> # false positives according to rules/STATISTICS.txt). Let's put them in a
> # different mbox. (This one is optional.)
> :0:
> * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
> Inbox.Spam
>
> # All mail tagged as spam (eg. with a score higher than the set threshold)
> # is moved to "probably-spam".
> :0:
> * ^X-Spam-Status: Yes
> Likely.Spam
Rather weird folder name, huh?
> Evolution then simply reads the various mboxes.
>
> Here's my question. I tell spamassassin to (re)learn the spam tagged
> messages using evolution. However, the format of the messages now has
> the spamc report with the offending message as an attachment. Is
> spamassassin "smart" enough to recognize the differnece between the two
> parts of the message?
As Sahil already answered: Yes, SA will unwrap the original message and
strip it's own headers before learning.
Since you've just moved from client side filtering, some additional
hints:
If you don't like the message wrapped as an attachment, the option
'report_safe 0' will prevent this. All reports are in the headers in
that case, the message will not be altered otherwise. This pretty much
looks like what you are used to -- with the notable exception of
additional report headers.
Also, learning (Bayes training) now needs to be done server side. The
clients "Junk" buttons won't work.
guenther
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
