You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2004/06/29 02:20:01 UTC
[Bug 3553] New: PerMsgStatus.pm problem with subject rewrite if Spam
http://bugzilla.spamassassin.org/show_bug.cgi?id=3553
Summary: PerMsgStatus.pm problem with subject rewrite if Spam
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: All
OS/Version: FreeBSD
Status: NEW
Severity: normal
Priority: P4
Component: Libraries
AssignedTo: spamassassin-dev@incubator.apache.org
ReportedBy: mlist-mail@esosoft.com
I'm using the 3.000000-pre1 version on FreeBSD 4.7 with exim 4.30 but without
the exiscan patch.
The problem occurs if SA detects Spam, but that Spam basically only contains
received headers and no body content and no other headers. I have set the
rewrite_header configuration variable to the following value:
rewrite_header Subject *****SPAM*****
report_safe 1
(It does not happen with report_safe 0). I haven't tried it with report_safe 2.
Here is an example of one of the spam messages which I am getting:
Received: from ool-4352def6.dyn.optonline.net ([67.82.222.246])
by eagle.esosoft.net with smtp (Exim 4.30)
id 1Bf40G-000Pdy-2e
for mlist-mail@esosoft.com; Mon, 28 Jun 2004 14:49:28 -0700
Received: from 92.214.167.90 by 67.82.222.246; Mon, 28 Jun 2004 20:42:37 -0200
If you run this one through SA it does not matter if it goes through spamd or
the standard spamassassin the modified message will look like this:
>>>>>>>>>>>>>>>
Received: from localhost by zebra.esosoft.net
with SpamAssassin (version 3.0.0-pre1);
Mon, 28 Jun 2004 17:07:53 -0700
Subject: *****SPAM***** X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.0.0-pre1 (2004-06-19) on
zebra.esosoft.net
X-Spam-Status: Yes, score=9.1 required=5.0 tests=HELO_DYNAMIC_OOL,
MISSING_DATE,MISSING_HEADERS,MISSING_SUBJECT,RCVD_BY_IP,
RCVD_DOUBLE_IP_SPAM,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DSBL,
RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=disabled
version=3.0.0-pre1
<<<<<<<<<<<<
I skipped the rest of the message as it is not important.
Notice the subject header has the following value:
Subject: *****SPAM***** X-Spam-Flag: YES
The "X-Spam-Flag: YES" should be in the next line by itself which means if you
check for that header if it is spam or not the message will go through.
It has the same problem if you include a message id under the received lines
the only thing which happens is that the subject line will look now:
Subject: *****SPAM***** Message-ID: <ex...@hostname.com>
If you apply the patch which I've included the problem is fixed. I don't know
if that is the best solution I just took it from the previous SA version 2.63.
I also applied it to the From and To header re-writes, but I haven't actually
tested it if there is the same problem.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.