Gmail and Yahoo now require specific headers on all bulk mail, and RFC 8058 one-click unsubscribe is mandatory on every marketing message. If your emails go to spam despite passing SPF and DKIM, the answer is usually in the headers.
The core headers
From and Return-Path must share a domain to pass DMARC alignment — a mismatch is the most common cause of DMARC failure. Message-ID should be fresh on every send and use a domain you control.
Authentication-Results
This header is added by the receiving server and reports the outcome of SPF, DKIM and DMARC. Look for pass on all three. fail means a DNS or signing problem; none means a record is missing entirely.
List-Unsubscribe and RFC 8058
Two headers together enable Gmail and Yahoo's native one-click unsubscribe button:
List-Unsubscribe: <mailto:unsubscribe@yourdomain.com>, <https://send.yourdomain.com/unsubscribe?u=abc>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
When the user clicks Unsubscribe, Gmail sends a POST to your HTTPS URL. Your endpoint must return a 2xx status and unsubscribe the user synchronously — no login page, no redirect.
Gmail and Yahoo bulk sender requirements
Since February 2024, senders of 5,000+ messages a day to Gmail or Yahoo must: authenticate with SPF and DKIM, publish a DMARC record, keep spam complaints under 0.3%, and support one-click unsubscribe. Unsubscribes must take effect within 48 hours.
Reading headers in Gmail
Open the message, click the three-dot menu, choose "Show original". Check Authentication-Results first — if SPF, DKIM and DMARC aren't all pass, that's your deliverability problem.