...

Pine bouncing, for instance, adds headers like:

 ReSent-Date: Wed, 27 Oct 2004 08:57:14 -0500 (CDT)

...

 ReSent-From: My Name <myname@company.com>

...

 ReSent-To: myname+spam@company.com

...

 ReSent-Subject: !!! How can you refuse such a sexy plus size single community!

...

 ReSent-Message-ID:

which may be stripped with an appropriate .procmailrc / sed stanza:

 :0fw: splitmsg.lck

...

 | sed -e '/^ReSent-/ d'

IMAP folders

Another option, and one that's easier for most users to use, is to set up two public IMAP folders on your IMAP server, one for MissedSpam, one for NotSpam.

Then ask your users to move messages that SpamAssassin misses into the MissedSpam folder, and move copy messages that SpamAssassin marked incorrectly as spam into the NotSpam folder.

You can then run sa-learn from a cron job over those folders to update the Bayesian databases.

Also see RemoteImapFolderSee RemoteImapFolder for more info.

How to set up site wide aliases on postfix where ham and spam can be sent for learning with Postfix

...

\[http://jousset.org/pub/sa-postfix.en.html The cookbook is available at http://joussetgtmp.org/pubdoku.php/publications:sa-postfix.-en.html\], it works fine for \[http://www.postfix.org/ postfix\]. Note: don't call your aliases spam and ham unless you want spammers to flood the ham box :)CategoryBayesbox - ideally, the aliases should not be directly accessible by inbound mail at all, there should be restrictions in place to only allow local users to send mail to those aliases.