[prev in list] [next in list] [prev in thread] [next in thread]
List: spamassassin-devel
Subject: [Bug 6071] New: false positives on X-Mailer: Microsoft Outlook
From: bugzilla-daemon () issues ! apache ! org
Date: 2009-02-22 17:35:13
Message-ID: bug-6071-26 () https ! issues ! apache ! org/SpamAssassin/
[Download RAW message or body]
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6071
Summary: false positives on X-Mailer: Microsoft Outlook
Product: Spamassassin
Version: 3.2.4
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: Rules
AssignedTo: dev@spamassassin.apache.org
ReportedBy: brian@interlinx.bc.ca
Similar to bug 5962 I am getting false positives from MS Outlook sent mails.
I have a message in hand that is triggering false positives based on the
ratware rules in 3.2.4.
The specific headers are:
Message-ID: <BLU0-SMTP74E123FDE12343A12DE12BD1B20@phx.gbl>
X-Mailer: Microsoft Outlook, Build 10.0.6838
Specifically, it seems that the X-Mailer header matches
__OUTLOOK_DOLLARS_MUA, and the Message-ID matches __HOTMAIL_BAYDAV_MSGID
The problem is that __OUTLOOK_DOLLARS_MUA is included in
__FORGED_OUTLOOK_DOLLARS without an exception for __HOTMAIL_BAYDAV_MSGID
so __FORGED_OUTLOOK_DOLLARS causes a hit on FORGED_MUA_OUTLOOK.
It seems to me, given this valid, non spam, non-ratware originating
message, that __FORGED_OUTLOOK_DOLLARS needs to include an "&& !
__HOTMAIL_BAYDAV_MSGID" in the exception list.
P.S. I do see that trunk is handling this combination of headers in a
fairly different manner. But that doesn't change the fact that this MUA
is causing false positives on 3.2, even with the latest (sa-
update_3.2_20081231172858 according to SVN) 3.2 udpate.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic