Bug 5774 - __ANY_OUTLOOK_MUA and X-Mailer: Microsoft Office Outlook
Summary: __ANY_OUTLOOK_MUA and X-Mailer: Microsoft Office Outlook
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: 3.2.4
Hardware: Other other
: P5 normal
Target Milestone: 3.2.6
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-08 07:36 UTC by James Wilkinson
Modified: 2011-05-31 22:27 UTC (History)
2 users (show)


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 James Wilkinson 2008-01-08 07:36:30 UTC 
Hi there.

The definition of __ANY_OUTLOOK_MUA is
header __ANY_OUTLOOK_MUA X-Mailer =~ /^Microsoft Outlook\b/

But I've been seeing a lot of ham and spam with
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-Mailer: Microsoft Office Outlook 12.0
(and other numbers).

Should the rule be updated so it matches both formats?

Thanks,

James.
Comment 1 Jason Haar 2008-01-27 22:42:36 UTC 
I'll add in my 5cents here too. I just found the same thing.

How about redefining as:

header __ANY_OUTLOOK_MUA  X-Mailer =~ /^Microsoft (Office|) Outlook\b/
Comment 2 Karsten Bräckelmann 2008-02-16 17:56:35 UTC 
Jason, there's a space too much in your rule, preventing all previously detected
'Microsoft Outlook' matches. ;)  The rule below will work.

  header __ANY_OUTLOOK_MUA  X-Mailer =~ /^Microsoft (Office )?Outlook\b/

Oh, and yes, I have seen this in my spam, too. About 25% as of some Jan corpus
checks. This seems to be a bug.
Comment 3 Justin Mason 2008-02-21 06:51:07 UTC 
fixed:

: jm 154...; svn commit -m "bug 5774: __ANY_OUTLOOK_MUA needs to match new
format for Outlook X-Mailer strings; 'Microsoft Office Outlook'" rules/20_ratware.cf
Sending        rules/20_ratware.cf
Transmitting file data .
Committed revision 629810.
Comment 4 Matus UHLAR - fantomas 2009-08-07 02:43:53 UTC 
could this be pushed to SA updates?
Comment 5 Justin Mason 2009-08-07 03:02:47 UTC 
reaiming for possible update, if anyone has the tuits
Comment 6 Darxus 2011-05-31 22:20:11 UTC 
Close.

Fix committed to trunk before 3.3 was branched from trunk.

Last updated 1.8 years ago.
Comment 7 Warren Togami 2011-05-31 22:27:06 UTC 
Fixed prior to 3.3