Your newsletter stopped reaching the inbox
Open rates that fall off a cliff are rarely about the subject line. Since 2024 Gmail and Yahoo enforce requirements on anyone sending in bulk, and a list that delivered fine for years can start bouncing over a header that was never there.
What this usually looks like
- Open rates that dropped sharply and did not recover
- Gmail or Yahoo rejecting mail with a bulk sender error
- Landing in Promotions when you used to reach the inbox
- Some segments of the list delivering and others not
What the audit checks for this
Every audit covers the same ground. These are the parts that decide this one.
- DMARC policy and alignment — required for bulk senders, and the most common thing missing
- One-click unsubscribe (RFC 8058) and the List-Unsubscribe headers, which are now a condition of delivery rather than a courtesy
- Whether your spam complaint rate is above the threshold the big providers publish, and what is driving it
- Domain and subdomain separation between campaigns and everything else you send
- The sending platform's own configuration, not just your DNS
What this will not do
- It will not improve a list that people do not want to be on.
- It will not rewrite your content. If recipients are marking you as spam, the fix is upstream of anything I can check.
Reading a DMARC policy the way a bulk receiver reads it
Gmail and Yahoo require an aligned DMARC policy from bulk senders. Whether yours qualifies is three commands, and you can run them against this domain to see what a passing answer looks like.
$ dig +short TXT _dmarc.strictmx.com"v=DMARC1; p=reject; rua=mailto:postmaster@strictmx.com"
A policy exists and it is enforcing. p=none satisfies the letter of the bulk sender requirement and tells receivers to do nothing, which is why so many domains have one and still have a problem.
$ dig +short TXT strictmx.com | grep spf"v=spf1 mx -all"
One record, ending in -all rather than ~all. The MX mechanism means the hosts that receive mail for the domain may also send it, which is true here and is not true for most senders using a platform.
$ dig +short DS strictmx.com | head -144746 8 2 CDB41DD97555A2AE954F67EC4EFF4DAE62A639D6...
DNSSEC. Not required by the bulk sender rules, and it is what stops the answers above being forged in transit to the receiver asking.
The part this does not show is alignment, which is where most newsletters actually fail: the platform signs with its own domain, the From header carries yours, and DMARC needs one of SPF or DKIM to match the visible From. A record can be perfect and still not align, which is why the audit reads the headers of a message that was really sent rather than only the DNS.
Questions people ask about this
- Why did my newsletter open rates suddenly drop?
- A sharp drop is usually delivery, not content. Since February 2024 Gmail and Yahoo enforce requirements on bulk senders: an aligned DMARC policy, one-click unsubscribe, and a spam complaint rate below 0.3%. A list that delivered fine for years can start failing over a header that was never there.
- What are the Gmail and Yahoo bulk sender requirements?
- For anyone sending roughly 5,000 messages a day or more: SPF and DKIM both passing and aligned with the From domain, a published DMARC policy, one-click unsubscribe implemented per RFC 8058, a functioning List-Unsubscribe header, and spam complaints kept under 0.3%. Failing any of them moves you from the inbox to the spam folder, or gets the mail rejected outright.
- How do I get my newsletter out of the Promotions tab?
- Promotions is not a spam folder and not a deliverability failure — it is a categorisation. Authentication does not move you out of it. What an audit can tell you is whether you are in Promotions or actually in spam, because the fixes are entirely different and people routinely mistake one for the other.
- What is a good spam complaint rate?
- Below 0.1% is healthy. Google publishes 0.3% as the point at which delivery suffers, and by the time you reach it the damage is already in your domain's reputation. Postmaster Tools shows the number for Gmail; the audit covers how to read it and what is driving yours.
Where this comes from
Everything above is checkable against the specifications that define it. These are the documents, not a summary of them.
- Google Email sender guidelines
- Yahoo Sender best practices
- RFC 8058 Signaling One-Click Functionality for List Email Headers
- RFC 7489 Domain-based Message Authentication, Reporting, and Conformance (DMARC)
One domain, one report, by email within 48 hours of your intake. No account, no call.
Not sure it covers your setup? Ask before you buy: audit@strictmx.com