Why in the *WORLD* would you think that INBOX placement is based on such a small set of factors...?
The one guaranteed way to get traffic delivered to the INBOX is for the recipient to SafeSender the domains. Past that … don’t spam, don’t look like a spammer. If it’s Hotmail related, make sure you’re on the SNDS and JMRP… and if you are still having issues, open a ticket. If it’s Office365 related, get your customers to open a ticket. And most importantly, if it’s a case of traffic going to Junk … don’t ask me to try and fix it, as the above are the only way this scales for millions of tenants, and billions of pieces of email each day. Sorry for the delay, but only getting back to this today… it’s been a week. 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> ? -----Original Message----- From: mailop <mailop-boun...@mailop.org> On Behalf Of David Jones via mailop Sent: Sunday, April 14, 2019 2:20 PM To: mailop@mailop.org Subject: Re: [mailop] Our customers e-mail constantly going to outlook.com junkmail (any Microsoft people around?) On 4/14/19 12:04 PM, Sébastien Riccio wrote: > Hello mailop, > > We're a "small" internet service provider in Switzerland and are running mail > services for our customers. > > Since a long time, customers are complaining that the mail they send are > always getting to junk folder at outlook.com (no issues with gmail for > example). > > We give a lot of time to keep our mail servers reputation as good as possible > and I think we're quite doing a good job at it. > > - We're not in any blacklist > - Our senderscore is at the moment 98% > - Talos intelligence mail reputation is good. > - Our customer domains have spf records, dkim, dmarc configured and checked > with no errors. > - On the Microsoft SNDS we have no apparent issue and the complaint > rate is always <0.1% > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fi.im > gur.com%2FrBJXlV6.png&data=02%7C01%7Cmichael.wise%40microsoft.com% > 7C6c952cae2b3b48a5f5ec08d6c120097d%7C72f988bf86f141af91ab2d7cd011db47% > 7C1%7C0%7C636908740685064391&sdata=1XI96ZNp%2Figdk54utDi6JLrR%2F96 > v%2BluReB3X852g3E8%3D&reserved=0 > I have seen this same problem for the past 20+ years of doing enterprise email support back to Exchange and continuing with Office 365 and outlooks.com. The Junk Email folder logic inside Outlook/Forefront Online Protection/Exchange Online Protection (whatever Microsoft is calling this week) is very inconsistent in it's classification/sorting. From what I can tell, it doesn't seem to be based on any industry standards that you mentioned like SPF, DKIM, DMARC, RBLs, SenderScore reputation, Cloudmark scoring, etc. or even the sending domain or body content. When people ask me this question, I recommend they turn off the Junk Email feature. I know this doesn't help from the sending perspective since it's impractical to get all recipients to disable this feature in Outlook.com or Office 365. Somehow our mail relay IPs have been able to deliver to Office 365 and Outlook.com/Hotmail.com reiably and consistently. Here's what I have done over the years: - Sign up for as many feedback loops as possible (Yahoo, AOL, Comcast, etc.). - Make sure FCrDNS is setup perfectly for your outbound mail server IPs with a one-to-one A record and PTR record matching the EHLO. Example: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmultirbl.valli.org%2Flookup%2F96.4.1.10.html&data=02%7C01%7Cmichael.wise%40microsoft.com%7C6c952cae2b3b48a5f5ec08d6c120097d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636908740685064391&sdata=sIDGd9NHQEJV5LS%2FTeZhj2CjDWEm%2FvPAf6pju%2Fd7bYQ%3D&reserved=0 - Make sure your outbound mail relays have their own SPF record for bounce messages. Example: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdmarcian.com%2Fspf-survey%2F%3Fdomain%3Dsmtp2n.ena.net&data=02%7C01%7Cmichael.wise%40microsoft.com%7C6c952cae2b3b48a5f5ec08d6c120097d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636908740685074385&sdata=ZTeaLGB1z1LoH62%2BpoIFjm5DCOgPNfe5uhVqSPwn%2FI8%3D&reserved=0 - Filter outbound mail with some deep header inspection to catch bad senders before they damage your mail server's reputation - Enable compromised account detection to discard spam from single senders quickly based on unusual activity - Try rate limiting your outbound mail to outlook.com. Maybe MS considers us smaller senders as suspicious after X messages per day per IP. -- David Jones _______________________________________________ mailop mailing list mailop@mailop.org<mailto:mailop@mailop.org> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchilli.nosignal.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fmailop&data=02%7C01%7Cmichael.wise%40microsoft.com%7C6c952cae2b3b48a5f5ec08d6c120097d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636908740685074385&sdata=nX%2Bnxn4VjTz7ElNSQEGwmvp%2FdAlii5PPDfcQl1fGYYU%3D&reserved=0
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
