On Wed, Sep 6, 2023 at 8:20 AM Charles Meigh via mailop <mailop@mailop.org> wrote:
> I think you are seeing MS composite (or implicit) authentication at work. > You mention that you see Junk placement on O365, and if that is if, and > only if you send to O365-hosted mailboxes than I think that is the root > cause. ( > https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/email-authentication-about?view=o365-worldwide). > If you get Junk placement at other ISPs then it is something else. > > > > Your SPF is passing, and you appear to have DKIM signed on the d= > mail1.wpengine.com; domain. MS does not see wpengine.com align with > hinckleyhomeinternet.com domain and it “fails” MS’s composite > authentication. > > > > If you send an email message to an O365 address look for the string > compauth in the headers then you’ll see something like “compauth=fail > reason=601” or similar. The easiest fix is almost certainly to get DKIM > aligning on the hinckleyhomeinternet.com domain. > > > ^^^^^ YES ^^^ THIS ^^^. If you aren't DKIM signing for the domain found in your visible/friendly from Office365 WILL put you in the junk folder. They have decided this is how mail should be, regardless of any other Best practices or RFCs. Their mailbox, their rules. Tara Natanson > > *From: *mailop <mailop-boun...@mailop.org> on behalf of Mike Hammett via > mailop <mailop@mailop.org> > *Date: *Tuesday, September 5, 2023 at 18:03 > *To: *mailop <mailop@mailop.org> > *Subject: *[mailop] WPEngine, Mail Channels, 365, MX Toolbox, Mail Genius > > We have a website on WP Engine. WP Engine sends its email through Mail > Channels. It's ending up in our Junk Mail box on 365. > > > > I test via MX Toolbox's Mail Deliverability Report. It fails for "Domain > not found in SPF", yet manually, everything I look up appears good. The IP > it sends from is included in the SPF record MXToolbox says. > > > > I test via MailGenius, and it says the SPF is good. > > > > > > I'm clearly getting an undesired result by it hitting our Junk Mail > folder. MXToolbox says it's bad, but then has conflicting info elsewhere. > Someone else says it's fine. I'm not sure on how to proceed. It's not for > sending campaigns, just transactional email (sending to us website contact > forms, etc.). The domain is newish, but it's been around a few months. > > > > > > https://mxtoolbox.com/deliverability/6e6dc435-d515-4fc9-afab-776a215a5095 > > > https://app.mailgenius.com/spam-test/5783b6?_gl=1*9cwct7*_ga*OTE0Njc2NTgzLjE2OTM5NDg0NTc.*_ga_2BJPW3X1ZW*MTY5Mzk0ODQ1Ny4xLjAuMTY5Mzk0ODQ2Mi41NS4wLjA > . > > > > > > I think I could set up DKIM, but that seems like it's not part of the > low-hanging fruit problem. > > > > > > ----- > Mike Hammett > Intelligent Computing Solutions <http://www.ics-il.com/> > <https://www.facebook.com/ICSIL> > <https://plus.google.com/+IntelligentComputingSolutionsDeKalb> > <https://www.linkedin.com/company/intelligent-computing-solutions> > <https://twitter.com/ICSIL> > Midwest Internet Exchange <http://www.midwest-ix.com/> > <https://www.facebook.com/mdwestix> > <https://www.linkedin.com/company/midwest-internet-exchange> > <https://twitter.com/mdwestix> > The Brothers WISP <http://www.thebrotherswisp.com/> > <https://www.facebook.com/thebrotherswisp> > <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
