Bug 5765 - FORGED_MUA_OUTLOOK FP on Outlook express mail from sympatico.ca customers
Summary: FORGED_MUA_OUTLOOK FP on Outlook express mail from sympatico.ca customers
Status: RESOLVED DUPLICATE of bug 5666
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-06 04:10 UTC by Sidney Markowitz
Modified: 2008-01-07 11:57 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sidney Markowitz 2008-01-06 04:10:45 UTC 
I saw an email from a sympatico.ca address that was sent with Outlook Express
that had an FP for FORGED_MUA_OUTLOOK because the msg-id was

Message-ID: <BAYC1-PASMTP042C93CD66C4A8801F919CE34C0@CEZ.ICE>

Google finds some other examples on the web. Here are just two of many:

http://www.openoffice.org/servlets/ReadMsg?list=users&msgNo=165660&raw=true
http://www.gwmicro.com/Support/GW-Info_Archives/index.php?postID=18841&showAllHeaders=1

I've added another header test in my sandbox to test, to add to the tests in
meta rule __FORGED_OE

header __OE_MSGID_4 MESSAGEID =~ /^<BAYC\d+-PASMTP\d+[A-Z0-9]{25}\@CEZ\.ICE>$/m
Comment 1 Sidney Markowitz 2008-01-06 19:11:17 UTC 
Does anyone have an opinion as to whether I should just go ahead and check into
the rules in trunk, 3.2, and 3.2 update the new header rule __OE_MSGID_4 and add
that to the definition of __FORGED_OE? The latest nightly mass-check shows it
not matching anything in the corpus, but I do have examples in the wild showing
that OE mail from sympatico.ca customers will trigger FPs that this fixes.

Yes/no?
Comment 2 Sidney Markowitz 2008-01-07 11:57:33 UTC 

*** This bug has been marked as a duplicate of 5666 ***