I’d suggest either not repeating the email address twice, or wrapping the first instance in quotes?
Aloha, Michael. -- Michael J Wise Microsoft Corporation| Spam Analysis "Your Spam Specimen Has Been Processed." Got the Junk Mail Reporting Tool<http://www.microsoft.com/en-us/download/details.aspx?id=18275> ? From: mailop <mailop-boun...@mailop.org> On Behalf Of Rob Heilman via mailop Sent: Monday, April 30, 2018 2:28 PM To: Mailop List <mailop@mailop.org> Subject: Re: [mailop] Microsoft Contact We appear to be having issues with the way Microsoft’s systems are parsing headers. In particular headers using display-name strings containing the @ symbol. For example: From: sen...@domain.net<mailto:sen...@domain.net> <sen...@domain.net<mailto:sen...@domain.net>> To: recipie...@gmail.com<mailto:recipie...@gmail.com> <recipie...@gmail.com<mailto:recipie...@gmail.com>>, recipie...@hotmail.com<mailto:recipie...@hotmail.com> <recipie...@hotmail.com<mailto:recipie...@hotmail.com>>, recipie...@yahoo.com<mailto:recipie...@yahoo.com> <recipie...@yahoo.com<mailto:recipie...@yahoo.com>> I tested against these three domains to validate the findings against multiple large providers. We are having issues with many domains hosted by Microsoft ranging from SMBs to universities along with hotmail.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fhotmail.com&data=02%7C01%7Cmichael.wise%40microsoft.com%7C5a4d30820a594c08099d08d5aee2a0ef%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636607210753547618&sdata=dVwVhZWfbQlDtdTgmnrmQcfoaahAnsH%2BkzwT7Ufixj8%3D&reserved=0>, outlook.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Foutlook.com&data=02%7C01%7Cmichael.wise%40microsoft.com%7C5a4d30820a594c08099d08d5aee2a0ef%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636607210753547618&sdata=XUrt3CTcgJ2ussExcUZWxhhslcDlE1h0nPgMhK5iJ8E%3D&reserved=0>, etc. Google parses the headers and encapsulates the display-name in dquotes like this: From: "sen...@domain.net<mailto:sen...@domain.net>" <sen...@domain.net<mailto:sen...@domain.net>> To: "recipie...@gmail.com<mailto:recipie...@gmail.com>" <recipie...@gmail.com<mailto:recipie...@gmail.com>>, "recipie...@hotmail.com<mailto:recipie...@hotmail.com>" <recipie...@hotmail.com<mailto:recipie...@hotmail.com>>, "recipie...@yahoo.com<mailto:recipie...@yahoo.com>" <recipie...@yahoo.com<mailto:recipie...@yahoo.com>> Yahoo does not appear to be modifying the headers at all. Microsoft however appears to be doing something strange. With the from header in this format the message is accepted by Microsoft’s servers but never gets delivered. With a different display-name in the From: header I can see that the To: header is being parsed to look like this: To: “recipient1@" <gmail.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgmail.com&data=02%7C01%7Cmichael.wise%40microsoft.com%7C5a4d30820a594c08099d08d5aee2a0ef%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636607210753557627&sdata=o1KpyUzCwX2CgPKjfVdN2Bsgcd53abn%2FHN%2Fd5obQ7v8%3D&reserved=0> recipie...@gmail.com<mailto:recipie...@gmail.com>>, "recipient2@“ <hotmail.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fhotmail.com&data=02%7C01%7Cmichael.wise%40microsoft.com%7C5a4d30820a594c08099d08d5aee2a0ef%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636607210753557627&sdata=SMUs44IckV7XYCVo%2FvQ%2BhZWKluDgAny0X4mhdMbyVhQ%3D&reserved=0> recipie...@hotmail.com<mailto:recipie...@hotmail.com>>, "recipient3@“ <yahoo.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fyahoo.com&data=02%7C01%7Cmichael.wise%40microsoft.com%7C5a4d30820a594c08099d08d5aee2a0ef%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636607210753567635&sdata=Nh%2B0LfKybKgdCddaOpf4TmFXLtzt5gN2bEJYySIgOh8%3D&reserved=0> recipie...@yahoo.com<mailto:recipie...@yahoo.com>> This causes the Microsoft webmail client to not be able to reply to the message as that the angle-addr strings have been malformed. My understanding is that these headers are using RFC5322 compliant name-addr formatting. I have also validated that against a couple of the online “test your mail” systems that check RFC compliance, SPF, DMARC, DKIM, SSL, etc. The messages that never get delivered is the bigger issue, but the ability for users to reply is also of concern. Is there something that I am missing about the formatting of these headers that is in violation of the RFCs? If not, can someone from Microsoft comment either on or off-list regarding these observed behaviors? Thanks, Rob Heilman rheilman at echolabs.net<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fecholabs.net&data=02%7C01%7Cmichael.wise%40microsoft.com%7C5a4d30820a594c08099d08d5aee2a0ef%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636607210753577644&sdata=RekkqeAFvOpg9YDLGtibn%2FIR%2B5ntex1w8vuYmOB0jRs%3D&reserved=0> On Apr 28, 2018, at 3:52 PM, Rob Heilman via mailop <mailop@mailop.org<mailto:mailop@mailop.org>> wrote: I need to work with someone at Microsoft off list. Can Michael or anyone else available shoot me a message? Thanks, Rob Heilman rheilman at echolabs.net<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fecholabs.net&data=02%7C01%7Cmichael.wise%40microsoft.com%7C5a4d30820a594c08099d08d5aee2a0ef%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636607210753577644&sdata=RekkqeAFvOpg9YDLGtibn%2FIR%2B5ntex1w8vuYmOB0jRs%3D&reserved=0> _______________________________________________ mailop mailing list mailop@mailop.org<mailto:mailop@mailop.org> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
