My transactional emails land in spam. What do SPF, DKIM and DMARC need to say?
Publish one SPF record that lists your sending service, turn on DKIM signing for your own domain, and add a DMARC record starting at p=none with a reporting address. Then make sure the domain in the visible From address lines up with the SPF or DKIM domain. Misaligned domains are the most common reason.
Cite
GitShowcase Forum, "My transactional emails land in spam. What do SPF, DKIM and DMARC need to say?", https://gitshowcase.com/forum/discuss/my-transactional-emails-land-in-spam-what-do-spf-dkim-and-dmarc-need/, accessed 2026-11-18.- Maren CastilloStaffForum lead: databases, hosting, CI and production ·
What each record does
- SPF (Sender Policy Framework) is a DNS record listing which servers may send mail for a domain. Yahoo's sender guidance describes it as the list of IPs allowed to send for that domain.
- DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message. The receiver checks it against a public key in your DNS, which shows the message was not altered and ties it to the signing domain.
- DMARC (Domain-based Message Authentication, Reporting and Conformance) sits on top. Per RFC 7489, it tells receivers what to do when a message fails, and it requires alignment: the domain in the visible From address must match the domain that passed SPF or DKIM. One aligned pass is enough.
Passing SPF on some other domain does not help if the From address shows yours. That mismatch is why mail from a "properly configured" service still lands in spam.
Check first
- Open one spam copy, choose "Show original" or "View source", and read the
Authentication-Resultsheader. Note whether spf, dkim and dmarc say pass, fail or none, and which domains they name. - Look up your current records:
dig +short TXT example.com dig +short TXT _dmarc.example.com dig +short TXT selector1._domainkey.example.comReplace
example.comand the selector with your domain and the selector your email provider gave you. 3. Find out which domain your provider uses in the envelope sender (Return-Path) and in the DKIMd=value. If both are the provider's domain rather than yours, DMARC alignment fails.Step 1: SPF, one record only
Add a TXT record at your domain root. The include value comes from your email provider's setup page:
v=spf1 include:<PROVIDER_SPF_DOMAIN> ~allTwo traps, both from RFC 7208:
- A domain must publish a single SPF record. If evaluation finds more than one, the result is a permanent error, so merge them into one line rather than adding a second.
- SPF evaluation limits the number of terms that trigger DNS lookups to 10, and exceeding it also returns a permanent error. Stacking many
include:entries from marketing tools, a helpdesk and a transactional service can hit this. Remove senders you no longer use.
Step 2: DKIM on your own domain
In your email provider's dashboard, add your sending domain and copy the DNS records it gives you, usually CNAME or TXT records under a
_domainkeyname. Wait for it to show verified, then send a test and confirmdkim=passwithd=equal to your domain or a subdomain of it. Yahoo's guidance asks for a minimum 1024-bit key length; most providers generate a suitable key for you.Step 3: DMARC, start in monitoring
_dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"p=noneasks receivers to take no action on failures, so it is safe while you learn what sends as your domain.ruais where aggregate reports go. RFC 7489 defines the policies:p=valueMeaning noneNo specific action requested quarantineTreat failures as suspicious, which can mean the spam folder rejectAsk receivers to reject failing mail The policy applies to subdomains too, unless you set an
sptag. Alignment is relaxed by default (adkimdefaults tor), which lets a subdomain likemail.example.comalign withexample.com. After the reports show every legitimate sender passing with alignment, move toquarantine, thenreject.Step 4: Use a subdomain for transactional mail
Yahoo's sender guidance recommends separating mail types, so bulk or marketing sending does not share reputation with user, transactional and alert mail. A common setup is
mail.example.comornotify.example.comfor receipts and password resets, with its own SPF and DKIM, and marketing on a different subdomain.What the big mailbox providers want
As of Yahoo's sender requirements in November 2026, bulk senders must implement both SPF and DKIM, publish a DMARC policy of at least
p=nonethat passes, keep the spam complaint rate below 0.3%, and support one click unsubscribe for marketing mail (aList-Unsubscribeheader, with the POST method described in RFC 8058 highly recommended). All senders need valid forward and reverse DNS on sending IPs. Pure receipts and resets are not marketing, but a provider's definition of "bulk" is theirs, so authenticate everything the same way.If authentication passes and mail is still in spam
- Content problems: a link shortener, a mismatched link domain, or an image only message.
- A cold domain sending a sudden large volume. Ramp up gradually.
- Old or invalid addresses producing bounces, which hurt reputation. Remove hard bounces promptly.
Provider choice matters less than these records; the email API guide compares the services.
Write something first.
Give people something to work with: at least 30 words on what happened and what you tried.
That is too long. Keep it under 6,000 characters.
Write the question as the title, 15 to 140 characters, no links.
Pick a category.
Add a name (2 to 40 characters, no links).
That email address does not look right.
That was quick. Read the thread, then try again.
The form expired. Reload the page and post again.
Something went wrong with the form. Reload and try again.
Please complete the check and post again.
Limit reached for now. Try again later.
This thread is closed to new replies.
This thread no longer accepts replies.
Something went wrong with the form. Reload and try again.
Post a reply or question first (name and email), then this browser can vote, edit and accept answers.
You cannot vote on your own post.
Only the author (within 30 days) or the forum team can do that.
That email already has an account. Use your sign-in link instead.
New accounts are paused for the moment. Try again later.
That was already posted.