THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Filter mails in Outlook Express
If SpamAssassin only adds some mail headers (like X-Spam-Flag) to tag spam and you don't want the subject to be mangled, Outlook Express cannot filter spam to a separate folder. A [http://article.gmane.org/gmane.mail.spam.spamassassin.general/52651 nice idea] from a person called Matt was to change the mail's priority to low, because this is something that OE can use for filtering. This can be done using [http://www.procmail.org/ procmail], as scripted by DanKohn or using [http://www.courier-mta.org/maildrop/ maildrop] as scripted by Kai Bolay.
This procmail version has been updated to first remove low priority headers from messages before filtering:
# Remove low priority headers by piping through formail. # If end-users filter on low priority headers, this will avoid # false positives. This is a procmail "or" rule requiring any # of the three headers to trigger. :0fw: formail1.lock * ^X-Priority: 5|\ ^Priority: Non-Urgent|\ ^Importance: low | formail -I "X-Priority" -I "Priority" -I "Importance" :0fw: spamassassin.lock * < 256000 | spamassassin # Pipe likely spam through formail adding # the three headers that represent low priority :0fw: formail2.lock * ^X-Spam-Flag: YES | formail -I "X-Priority: 5" -I "Priority: Non-Urgent" -I "Importance: low"
The same with maildrop:
if ($SIZE < 256000)
{
exception {
xfilter "spamassassin"
}
}
if (/^X-Spam-Flag: YES$/)
{
# add the three headers that represent low priority
exception {
xfilter '/web/servers/qmail/bin/reformail -I "X-Priority: 5" \
-I "Priority: Non-Urgent"
-I "Importance: low"'
}
}
else
{
if (/^X-Priority: 5$/ || \
/^Priority: Non-Urgent$/ || \
/^Importance: low$/)
{
# Remove low priority headers by piping through reformail.
# If end-users filter on low priority headers, this will avoid
# false positives.
exception {
xfilter '/web/servers/qmail/bin/reformail -I "X-Priority:" \
-I "Priority:" \
-I "Importance:"'
}
}