We've seen a dramatic increase in rejects from Microsoft with 'Message lacks SPF/DKIM/DMARC' even on domains with correct SPF + DKIM. Anyone else seeing this? Have they changed their policy on requiring DMARC records?
@beasts What I need to know is how to fix their broken reputation system that shunts my one or two messages a month to spam for no valid reason. They treat bulk senders better.
@beasts They used to silently reject some mails before, maybe they just changed that you get properly notified now and your config is indeed incorrect.
@wildrikku config is fine. We've confirmed valid DKIM and SPF on the affected mail. It appears that Microsoft have made an unannounced change to their policy and now require a DMARC record.
@beasts Ah, I see. I set up DMARC together with DKIM and SPF when I stumbled upon the DKIM requirement a while back, so I missed that DMARC wasn't required before but is now. Good you figured it out.
@beasts I've seen it once, so far, and put it aside as an anecdote. Will keep an eye out on it.
@dentangle @CenturyAvocado @srtcd424 I thought it was 5000/day. I assume it has correct SPF? Do sender + from domain match?
@chloeraccoon @tiggy yes, but only for bulk senders (> 5000/day). It looks like they have just changed their policy.
@beasts Yes I got some rejects overnight from a virtual server in your estate that has it's own email server.
@beasts I think @CenturyAvocado saw something like that yesterday with email from MS to Hotmail (weirdly)? Sounds like they may have screwed something up.
@CenturyAvocado @srtcd424 @beasts I thought that was the case already if you want reliable delivery.
@CenturyAvocado @srtcd424 Thank you! We've now had confirmation from one customer that adding a p=none policy appears to fix it. I wonder if this change was intentional, as I can't seen any announcement of it.
@beasts Wouldn't waste my piss on these vibe coding clowns. Knew the writing was on the wall after they broke cut and paste in Excel. FFS.