Thanks for the replies everyone. To clarify: 1) I am seeing the issue with seed tests.
2) I am seeing the issue with Return Path panel data. 3) I am seeing the issue when testing to personal mailboxes that I control. So it is not an issue solely limited to seed testing, it is a real issue that I can confirm is happening to our customers with their mail. Microsoft tier 1 support in India would have me believe that Microsoft's spam filters are the best in the world and everyone else is getting it wrong. Anecdotally, I've created a brand new Hotmail account, and sent an email from that account to itself, using their own webmail infrastructure, and had that email go to the spam folder. I've also spoken to people who have sent someone an email, had the recipient REPLY to that email, and that reply went to junk. It may be anecdotal, but if Microsoft can't get basic things like these right, they're not geniuses who are better at filtering spam than the rest of us. My hope is that if we could actually reach an engineer at the company and show them the cases where we believe their filtering is applying a wrong verdict, they would either agree and fix the filtering, or at least provide us information on how we need to treat their platform differently than everyone else's to avoid the issue. Here are the headers from a transactional IP (SNDS green): X-Forefront-Antispam-Report: EFV:NLI;SFV:NSPM;SFS:(98901004);DIR:INB;SFP:;SCL:1;SRVR:BY2NAM03HT072;H:mta-c-24-30.infusionmail.com;FPR:;SPF:None;LANG:; We have a good SCL and SFV verdict here. X-Microsoft-Antispam: BCL:2;PCL:0;RULEID:(5000109)(4604075)(4605076)(610169)(650170)(8291501071);SRVR:BY2NAM03HT072; BCL and PCL are fine. X-Exchange-Antispam-Report-Test: UriScan:; It was a plain text email with no URIs so nothing much to report here. X-Exchange-Antispam-Report-CFA-Test: BCL:2;PCL:0;RULEID:(444111537)(595095)(82015058);SRVR:BY2NAM03HT072;BCL:2;PCL:0;RULEID:(100000803101)(100110400095);SRVR:BY2NAM03HT072; The BCL and PCL still look good here. X-Microsoft-Antispam-Mailbox-Delivery: abwl:0;wl:0;pcwl:0;kl:0;iwl:0;dwl:0;dkl:0;rwl:0;ex:0;auth:1;dest:J;ENG:(400001000128)(400125000095)(5062000261)(5061607266)(5061608174)(4900095)(4920089)(6370004)(4950112)(4990090)(9140004);RF:JunkEmail;OFR:SpamFilterAuthJ; Here we see the same behavior that you are, Benjamin, where we can see it's filtered to the junk folder. If I click "This isn't spam" and send again, it delivers to my inbox, but as an ESP we can't expect our customers to tell their customers "Our emails to you, including our transactional emails, will go to spam, and you have to click the button to tell Microsoft it's not spam." ________________________________ From: Benjamin BILLON <bbil...@splio.com> Sent: Tuesday, December 26, 2017 11:28 PM To: David Carriger; mailop@mailop.org Subject: RE: Microsoft inbox placement issues Hi David, Can you share the headers such as X-Forefront-Antispam-Report:, X-Microsoft-Antispam:, X-Exchange-Antispam-Report-Test:, X-Exchange-Antispam-Report-CFA-Test:, X-Microsoft-Antispam-Mailbox-Delivery:, and whatever else relevant? BTW this tool https://testconnectivity.microsoft.com/ could help visualize the headers more easily In my cases of undoubtedly misplaced emails (in junk folder instead of inbox), I have some funky things such as: - BCL:8 (all indicators of complaints, including those provided by SNDS and JMRP, being at the lowest for months, I don’t explain this score) - SFV:NSPM (so the content filter said “non-spam”) - PCL:0 (nothing weird here) - SCL:1 ("Non-spam because the message was scanned and determined to be clean") - SPF, DKIM and DMARC results are "pass", MAIL FROM:, From: and d= domains are aligned - X-Microsoft-Antispam-Mailbox-Delivery: contains "RF:JunkEmail;OFR:SpamFilterAuthJ;" for the case when it's in junk folder When these emails reach inbox (because they sometimes do), the _only_ notable difference is that this last header doesn’t contain these RF: and OFR: information. There’s just no mention of it. The rest is identical, even the BCL:8. I’d be happy to gather similar cases so we could build a bigger and better argumentation (the objective being to ease Microsoft’s job in fixing this), so don’t hesitate to share on or off list. Cheers, Benjamin De : mailop [mailto:mailop-boun...@mailop.org] De la part de David Carriger Envoyé : mercredi 27 décembre 2017 05:27 À : mailop@mailop.org Objet : [mailop] Microsoft inbox placement issues Hi everyone, I'm hoping someone here might be able to help. We're a small ESP that focuses on serving the small business market. In Return Path, we're seeing great inbox placement at Gmail, Yahoo and AOL, and terrible inbox placement at Microsoft. We use SNDS and JMRP already and neither seem to help. It doesn't matter whether I do a seed test from a green IP, yellow IP, or red IP, they all run into the same filtering issues. Even my seed test emails going out of transactional-only, always green IPs run into filtering problems. I've opened several support tickets with Microsoft - SRX1407027597ID is the latest - but they seem completely unable to help. They just tell me that there's nothing wrong with the IPs, or that the filtering is due to SmartScreen, etc but provide nothing actionable that would help us fix the issue and improve our inbox placement. We already monitor things like hard bounce rates, complaint rates, spam filter analysis, spam trap hits, etc. for all of our customers and take action on bad actors in our network. So far that's been working for us everywhere else, but not at Microsoft. Any ideas of what we can do, or who to talk to, to get better inbox placement at Microsoft? Small Business Growth Expert DAVID CARRIGER Linux Systems Administrator -- david.carri...@infusionsoft.com<mailto:david.carri...@infusionsoft.com>
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
