SpamAssassin scanning spam repeatedly

Enverex

SpamAssassin seems to be scanning pieces of spam repeatedly, and this could be a problem, as it ends up attaching the spam notification to a spam notification saying that it's spam, and possibly also attaching that notification to a notification, etc etc.

This page shows all the code in Exims config file (top 2 paragraphs) and the script that it is run through - http://sial.org/pbot/602?hl=on&submit=Format+it%21

Any ideas why it isn't scanning it just once? As it sets "spam-scanned" but that doesn't seem to be helping.

Cheers,
Ex

Straight_Man

Trick is to have script than delete offending files, OR to move them to an email folder whihc Spam Assassin than does not scan. At a guess, the canned script is intended to work with an email client which uses the SPAM note as a key to either delete or move the messages to a folder that Spam Assassin does not scan so you can decide you either want them or delete tham yourself. Until a SpamAssassin is trained in, I tend to move to a folder, then say a month later when it is pretty well trained in I simply tell the script to erase contants of folder I established as the scan run closes. Also, I do not email spam hit notes to myself, those go back through the scan process....

John.

Enverex

SA is integrated with the MTA itself, so it needs to go back into SA to actually get delivered to the correct user, and to get the correct headers attached.
The script is for Exim, so it can't be that it was designed for another MTA. The point is, this should actually be working, and I need to find out why.

Enverex

Fixed it with the help of Byte in #Linux. Turns out I had one of my lines slightly wrong, it needed to be -

[php]
condition = "${if and { {!eq {$sender_host_address}{127.0.0.1}} {!eq {$received_protocol}{spam-scanned}}} {1}{0}}"

instead of -

condition = ${if and { {!def:h_X-Spam-Flag:} {!eq{$received_protocol}{spam-scanned}}} {1}{0}}"
[/php]

Which doesn't quite work. So all done