It seems that qmailscanner deletes any existing X-Spam-Status and
X-Spam-Flag-headers from the scanned email, so that these are ignored in
case a spammer has put them there to fool useres of spamassassin. This is
the expected behaviour, I guess.
However I've noticed that if an already spamassassin-scanned message
(piped through spamassassin via procmail) contains, ie.:
<cut>
X-Spam-Status: No, hits=0.7 required=5.0
tests=MSG_ID_ADDED_BY_MTA_3
version=2.55
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
<cut>
and the email gets scanned again by spamassassin using qmail-scanner, then
the existing X-Spam-Status -header gets deleted incerrectly, resulting
in:
<cut>
tests=MSG_ID_ADDED_BY_MTA_3
version=2.55
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
<cut>
The lines starting with "tests=..." simply remains in the message, which
confuses my mailklient's parsing of the surrounding headers.
I use qmail-scanner 1.15. From the changelog I can't see that the newest
stable version (1.16) should alter the behavior in this particular
situation.
Have I discovered a bug in qmail-scanner or in the configuration of my
mailserver?
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Qmail-scanner-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
