> spamassassin (http://spamassassin.org/) works well for me and it is > set up for use w/ procmail. you add a recipe to run spamassassin. > spamassassin tags it and then you can do whatever you want with the > spam with another recipe.
Yeah, spamassassin is very cool, but unfortunately it's not 100% perfect. So if i let probable spam get filtered as if it weren't, it'll get dropped off in the archive folders and i'll have to delete it manually. If i drop probable spam into its own folder without archiving it, and then i find stuff in there that's not spam, i have to manually copy it to the archive folders. I think what i'll do is filter probable spam as if it were just regular mail and write a script that i can call on each piece of spam. The script will count the number of bytes in the message (call it N) and then look through the archives for all messages whose filesize is N. (I use maildir) Then, for each of those matching messages, i'll strcmp it to the original message, and if there's a perfect match, delete the file.
msg28918/pgp00000.pgp
Description: PGP signature
