Guide · AT-R09REV. 2026-A
Why do my e-mails end up in spam? SPF, DKIM and DMARC explained

By Felix GötzManaging director · qualified IT officer (Informatikkaufmann, IHK)Last updated:
The call usually goes like this: “The customer says he never received our quote. But it is in our Sent folder.”
And yes, it was sent. It just was not delivered. At least not to where anyone looks.
That is a lot more expensive than it sounds. An invoice in spam does not get paid. A quote in spam does not get accepted. And you usually never find out, because nobody rings to tell you they have not heard from you.
What happens at the other end
When your mail reaches the recipient, their server asks three questions before it delivers it to the inbox:
Was this server allowed to send on your behalf at all?
Was the mail altered on the way?
And what should I do if the answer to one of these is no?
Each of these questions has a record that you store in your DNS. That is where the settings for your domain live, usually at your hosting provider. If the records are missing, the receiving server has to guess. And when in doubt, it guesses against you.
SPF: who may send on your behalf?
SPF is a list. It states which servers may send mail for your domain. If a mail comes from a server that is not on the list, that is a warning sign.
One detail that becomes important later: what gets checked is not the sender address the recipient sees in their mailbox, but the technical return address on the envelope of the mail. The two can differ. That is exactly what DMARC is for.
Sounds simple, and it is. There are still two traps.
First: there may only be one SPF record per domain. We regularly find two or three, because a new one was simply added with every new service. The result is not twice as good, but broken. Everything has to go into one record.
Second: think of everything that sends on your behalf. Not just the mail server. Also the newsletter tool, the accounting software that sends invoices, the contact form on the website. If one of them is forgotten, it is exactly that mailing that lands in spam.
DKIM: the seal on the envelope
DKIM puts a digital signature on every outgoing mail. The recipient checks this signature against a key that you have published in your DNS.
If it matches, they know two things: the mail really comes from your company, and nobody has tampered with it on the way.
Your mail provider usually handles the setup. With Microsoft 365 it is a few clicks plus two DNS records, with Google Workspace a single one is enough. The tiresome part is the same again: every service that sends on your behalf needs its own key.
DMARC: the instruction for what should happen in case of doubt
SPF and DKIM only establish whether something is wrong. What should happen then is what DMARC says.
You store one of three instructions:
- none means: do nothing, just report
- quarantine means: off to the spam folder
- reject means: do not accept it at all
But DMARC checks a second thing as well, and that is where most setups fail: the domain that passed SPF or DKIM must match the domain the recipient sees as the sender. A typical case is the newsletter tool. It sends cleanly from a technical point of view via its own domain, SPF shows PASS, and DMARC still fails because your company address is shown as the sender. This can be solved by having the service sign the mails with a DKIM key of your domain, or send them from a sender address on your domain.
And this is the point where most people stop. DMARC is set to “none” because that is harmless, and then it stays there. For ever. You then have a record, but no protection at all. Anyone can still send mails using your address.
DMARC also brings reports. You regularly receive a summary of who is sending on your behalf. Services turn up that nobody has used for ages. And occasionally senders that never had anything to do with you.
How to check whether it works
You need no tool and no service provider for this. Send yourself a mail from your company address to a Gmail account. In Gmail, open the message, click the three dots and choose “Show original”.
At the top there are three lines: SPF, DKIM, DMARC. Each is followed by PASS or FAIL.
PASS on all three is the goal. Anything else is something to fix.
The test takes two minutes and tells you more than any guesswork. Repeat it after every change, and do it separately for each way mail leaves your company. The server can be fine while the newsletter tool fails.
What is in your DNS is shown by the e-mail check: enter the domain, and it lists SPF, DKIM and DMARC with an explanation of what is missing. It does not replace the test mail, because only that shows how a particular sending route actually arrives. What is in the header of the test mail once it has arrived is translated by the e-mail header analysis.
Where it usually goes wrong in practice
Two or three SPF records at the same time. Happens more often than you would think.
The newsletter service or the ERP system is in none of the records, because both were added two years after the mail was set up.
DMARC has been on “none” for three years and nobody reads the reports.
The SPF record has too many references. A maximum of ten lookups is allowed, and every included service counts. Beyond that the record becomes invalid altogether, without an error message appearing anywhere.
And the classic: everything was set up, but nobody ever checked whether it actually takes effect.
What this does not solve
Honestly: even with PASS on all three, mails can land in spam. The technology is the prerequisite, not the guarantee. If your subject line sounds like advertising, if you suddenly send two thousand mails at once or if your domain has only existed since last week, the best DNS record helps little.
But without the records you have lost from the start. And since 2024 Google and Yahoo, and by now Microsoft too, require all three for larger sending volumes anyway.
The order
- List all systems that send mail on your behalf. Really all of them.
- Create a single SPF record that covers them all. Remove any existing duplicates.
- Activate DKIM with your mail provider and set it up for every other sending service.
- Set DMARC to “none” first and evaluate the reports for a few weeks.
- When nothing important fails any more, step up to “quarantine”. Later to “reject”.
- Gmail test. After every change.
Point 4 is the one you should not skip. If you go straight to “reject”, you may well block your own invoice e-mails.
There is another reason for caution with point 5. As soon as a mail is forwarded, through an alias, a distribution list or a mailing list, SPF breaks by design: the forwarding server is not on your list. What can still save the mail then is an intact DKIM signature, because that survives forwarding. You should therefore only go to “reject” once DKIM is truly in place on all sending routes.
If you would rather not work through the list yourself: we take on exactly this kind of setup as part of IT support for businesses.