Bug 5707

I've seen this too, and again the MUA was Microsoft Office Outlook 12.0

Seen that as well.

Message id syntax is < id-left @ id-right >

id-left and id-right may NOT have an @ sign, so the MUA is generating an invalid
msg-id. Does Microsoft run a kind of a bugzilla for reporting this bug?

We've also seen this issue with email from Outlook 2007 (aka Outlook 12). 

Given the prevalence of the Outlook 2007 client why is this unaddressed over a year and a half later?

...because it's a problem within Outlook/Exchange, not SA? Sadly, Microsoft Outlook isn't (yet) recognized by the Microsoft Connect website.

Perhaps the correct fix is to meta it:

meta  ADJ_OUTLOOK_MSGID_BUG  (MSGID_MULTIPLE_AT && __ANY_OUTLOOK_MUA && !MSGID_OUTLOOK_INVALID)
score ADJ_OUTLOOK_MSGID_BUG  -1.00

What about changing MSGID_MULTIPLE_AT to __MSGID_MULTIPLE_AT and defining MSGID_MULTIPLE_AT as __MSGID_MULTIPLE_AT && !__ANY_OUTLOOK_MUA
?

Created attachment 4507 [details]
patch to make MSGID_MULTIPLE_AT conditional on split local part and not Outlook

FWIW I agree with Matus.  Also in my experience, this Outlook bug only manifests when the local part of the sender contains a dot, so here's a patch to apply both those conditions.

Supposedly one should be able to make a "Suggestion for Microsoft" via https://www.microsoft.com/office/community/en-us/default.mspx?dg=microsoft.public.outlook.general&lang=en&cr=US , but it wasn't working for me with a new LiveID, so I posted via Google Groups instead:
http://groups.google.co.uk/group/microsoft.public.outlook.general/browse_thread/thread/487aa7845624b86/8ce0680570f47114 . 

Searching the web also incidentally turned up what may be a related Outlook bug, although not one that SA seems sensitive to:
http://office-outlook.com/outlook-forum/index.php/m/255091/

I have just had a couple of FPs due to X-Mailer = "Microsoft Office Outlook 12.0" not being recognised by __ANY_OUTLOOK_MUA.

before this can be reviewed, we need to see it checked in and ruleqa'd against the original.

moving all open 3.3.1 bugs to 3.3.2

Moving back off of Security, which got changed by accident during the mass Target Milestone move.

Moving all open bugs where target is defined and 3.4.0 or lower to 3.4.1 target

This happens here as well, with SpamAssassin version 3.3.2:

X-Mailer: Microsoft Office Outlook 12.0
Message-ID: <000601cf5403$d83f83f0$88be8bd0$@username@domain.de>

(In reply to Christian Kujau from comment #12)
> This happens here as well, with SpamAssassin version 3.3.2:
> 
> X-Mailer: Microsoft Office Outlook 12.0
> Message-ID: <000601cf5403$d83f83f0$88be8bd0$@username@domain.de>

please post the full spam report of a message where this rule caused an FP

cannot reproduce and need spample on pastebin or similar.   Pushing to 3.4.2

> please post the full spam report of a message where this rule caused an FP

I missed this request, but it was still in my spam folder:

========================================================
Content preview:  ok ok [...] 

Content analysis details:   (3.1 points, 2.5 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
                            trust
                            [212.227.17.175 listed in list.dnswl.org]
 1.0 MSGID_MULTIPLE_AT      Message-ID contains multiple '@' characters
 0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                            (foo.bar[at]freenet.de)
 0.4 MIME_HTML_MOSTLY       BODY: Multipart message mostly text/html MIME
 0.0 HTML_MESSAGE           BODY: HTML included in message
 0.8 BAYES_50               BODY: Bayes spam probability is 40 to 60%
                            [score: 0.5000]
 0.8 RDNS_NONE              Delivered to internal network by a host with no rDNS
 1.0 TVD_SPACE_RATIO        TVD_SPACE_RATIO
 0.2 HELO_MISC_IP           Looking for more Dynamic IP Relays
-1.2 AWL                    AWL: From: address is in the auto white-list
========================================================

I've since moved to SpamAssassin 3.4.0 (Debian: 3.4.0-2~bpo70+1) and cannot reproduce this any more.

My SA changelog.gz has his from March 2012 (when Debian was shipping SA 3.3.2):

========================================================
r1303397 | kmcgrail | 2012-03-21 14:10:27 +0000 (Wed, 21 Mar 2012) | 1 line

 Demoted MSGID_MULTIPLE_AT from default rules to sandbox
========================================================

So, maybe this got fixed long ago?

OK, closing as worksforme unless we can get a current sample.