Geoff Soper
2014-09-04 06:51:54 UTC
Hi,
I've got an issue whereby spam messages seem to be somehow bypassing SA and getting into my inbox. I call SA via procmail as per https://wiki.apache.org/spamassassin/UsedViaProcmail
The exact procmail file that calls SA is as follows:
#
#Standard SA call to be included from .procmailrc files
#
:0 f
| formail -A"X-Procmail-SpamAssassinInclude: 23/03/2010"
#
# Pipe the mail through spamassassin (replace 'spamassassin' with 'spamc'
# if you use the spamc/spamd combination)
#
# The condition line ensures that only messages smaller than 250 kB
# (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam
# isn't bigger than a few k and working with big messages can bring
# SpamAssassin to its knees.
#
# The lock file ensures that only 1 spamassassin invocation happens
# at 1 time, to keep the load down.
#
:0fw: spamassassin.lock
* < 400000
| spamc -x
# Work around procmail bug: any output on stderr will cause the "F" in "From"
# to be dropped. This will re-add it.
:0
* ^^rom[ ]
{
LOG="*** Dropped F off From_ header! Fixing up. "
:0 fhw
| sed -e '1s/^/F/'
}
:0
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*
/dev/null
#${DIR}.Spam.Bad/
:0
* ^X-Spam-Status: Yes
${DIR}.Spam/
When I see these spam messages in my inbox, they have the X-Procmail-SpamAssassinInclude header but no evidence (i.e. headers) of SA having processed the message. According to Thunderbird, these messages are well below the size threshold specified. Can it be todo with the locking mechanism specified by the file above? If it's locked, what happens? Does it wait for SA to be available or simply skip SA? Historically I've been getting these messages occasionally but over the past week I've had bursts of dozens of messages over a few minutes all apparently bypassing SA. I'm running version 3.3.2.
Thanks in anticipation
I've got an issue whereby spam messages seem to be somehow bypassing SA and getting into my inbox. I call SA via procmail as per https://wiki.apache.org/spamassassin/UsedViaProcmail
The exact procmail file that calls SA is as follows:
#
#Standard SA call to be included from .procmailrc files
#
:0 f
| formail -A"X-Procmail-SpamAssassinInclude: 23/03/2010"
#
# Pipe the mail through spamassassin (replace 'spamassassin' with 'spamc'
# if you use the spamc/spamd combination)
#
# The condition line ensures that only messages smaller than 250 kB
# (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam
# isn't bigger than a few k and working with big messages can bring
# SpamAssassin to its knees.
#
# The lock file ensures that only 1 spamassassin invocation happens
# at 1 time, to keep the load down.
#
:0fw: spamassassin.lock
* < 400000
| spamc -x
# Work around procmail bug: any output on stderr will cause the "F" in "From"
# to be dropped. This will re-add it.
:0
* ^^rom[ ]
{
LOG="*** Dropped F off From_ header! Fixing up. "
:0 fhw
| sed -e '1s/^/F/'
}
:0
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*
/dev/null
#${DIR}.Spam.Bad/
:0
* ^X-Spam-Status: Yes
${DIR}.Spam/
When I see these spam messages in my inbox, they have the X-Procmail-SpamAssassinInclude header but no evidence (i.e. headers) of SA having processed the message. According to Thunderbird, these messages are well below the size threshold specified. Can it be todo with the locking mechanism specified by the file above? If it's locked, what happens? Does it wait for SA to be available or simply skip SA? Historically I've been getting these messages occasionally but over the past week I've had bursts of dozens of messages over a few minutes all apparently bypassing SA. I'm running version 3.3.2.
Thanks in anticipation