spamassassin-users October 2010 archive
Main Archive Page > Month Archives  > spamassassin-users archives
spamassassin-users: Re: Spam tagging not happening

Re: Spam tagging not happening

From: Dominic Benson <dominic_at_nospam>
Date: Mon Oct 18 2010 - 15:48:57 GMT

On 18/10/10 16:11, Jeremy Van Rooyen wrote:
> Thanks for the quick reply Dominic,
> I just checked and the SApermreject is set sensible for now. The
> latter part of your email refers to SA-Flagged messages, how do I make
> sure this is working, as I have enabled rewrite_header in
> /etc/spamassassin/ <>
If rewite_header is enabled, and you don't see the *****SPAM***** (or
alternative you specified) in the subject line, then it didn't get

Could you set SAEximDebug: 1 in /etc/exim4/sa-exim.conf, and then paste
the output of a message in /var/log/exim4/mainlog, e.g.:

2010-10-18 16:26:48 1P7rbr-0007e3-NS SA: Debug: SAEximRunCond expand
returned: 'true'
2010-10-18 16:26:48 1P7rbr-0007e3-NS SA: Debug: check succeeded, running
2010-10-18 16:26:51 1P7rbr-0007e3-NS SA: Action: permanently rejected
message: score=15.7 required=5.0 trigger=12.0 (scanned in 3/3 secs |
Message-Id: 1P7rbr-0007e3-NS). From <>
(host=NULL []) for

Then we should be able to see what is actually happening.

Also, could you check the output of "grep sa-exim
- if you use Exim in unsplit configuration, sa-exim doesn't get used by
default. exim4-daemon-heavy has an alternative way of using SpamAssassin
(exiscan_acl), which is powerful, but not so convenient.
> How do I add a message rule that subject starts with *****SPAM***** ?
> Do I add to my <>? I'm sure I did this already.
I mean you should do this in either your mail client, or e.g. a Cyrus
sieve. This is about using the data that SpamAssassin/Exim have added to
the message to classify it in your inbox, rather than a mail routing
decision. (e.g. in Thunderbird you would go Tools -> Message Filters -> New)