For this reason, you should probably disable automatic moving of spam around by your email client. This is important, because the way I am setting this up, anything that is sent to the Junk folder is deleted every 4 hours. procmailrc, I tell procmail to move mail marked as spam by Spamassassin to my $Maildir/.Trash/. This works nicely for me, keeping spamassassin smart and preventing me from missing important emails. # actions until you're sure it's working right. It's a good idea to let procmail log all its # Set our default mailbox, which is where mail that doesn't have You can also set the HOME variable, which # Set our default shell, which may not be necessary, as it #.procmailrc - by jorge - Updated by glenn 6/8/05 Since procmail will be delivering to the Maildirs instead of Postfix, you need to double check this setup ~]$ cat. For the sake of definition, procmail becomes our MDA (Mail Delivery Agent). This will actually take the mail from Postfix, filter it through spamassassin, then deliver it to the Maildirs. Once you have installed Spamassassin and procmail, we want to setup a. Refer to this IBM Developerworks article () to get more detail on Spamassassin. If you do set it up system wide (), the users can always customize their own rules. You can setup procmail and Spamassassin to be systemwide, but I prefer to do it by user - for the sake of flexibility. Procmail allows us to feed our incoming mail through different programs, then place them in different mailboxes based on the outout of those programs. We'll use the combination of procmail () and Spamassassin () to filter spam from our incoming mail. Using Spamassassin and procmail to filter spamġ.1.1 One spamassassin autolearning setupġ.1.3 Performance issues with training the bayesian filter

Thunderbird spamassassin