Our website is in Dutch; support is available in English.

Why does my email end up in spam?

The four causes in order, how to test your content, and why there is no button that fixes this.

Updated 4 minute read

Contents of this article
  1. There is no button that fixes this
  2. The four causes in order
  3. When it goes wrong with one recipient
  4. What we can't do here
  5. Further reading

Receiving mail servers weigh several signals against each other before they accept a message. This page explains which signals those are, in what order to check them, and what you can reasonably expect.

There is no button that fixes this

Let's start there, because it is the heart of the matter. Whether your message lands in the inbox or in the spam folder is decided neither by us nor by you, but by the receiving side. Google, Microsoft and the rest make that call per message, based on signals they don't publish, and they change how they weigh them regularly.

What you can do is get the signals you control in order. That is no guarantee, but in practice the difference between a domain where everything is right and one where it isn't is large. Work through the four causes below in this order.

The four causes in order

  1. Missing or incorrect SPF, DKIM and DMARC

    This is the most common cause and the only one entirely in your own hands. If a recipient can't establish that you are allowed to send mail on behalf of your domain, that is a reason to distrust your message. Watch out especially for the classics: two SPF records side by side, a newsletter service or accounting package that isn't in your SPF, or a DKIM key that was never published. How to set this up is explained in Setting up SPF, DKIM and DMARC.

  2. The reputation of the sending IP address and domain

    Recipients keep track of how mail from an IP address and from a domain has behaved in the past. If you send from an address that spam has come from before, that counts against you. A brand-new domain also starts out neutral to slightly negative: reputation has to be built up, and that takes weeks of normal traffic, not hours. Suddenly sending far more mail than usual is a signal in itself as well.

    A common mistake here: sending mail from your own office connection, or from a server at a provider that doesn't keep its IP space clean. Our own ranges are in AS211588, registered to Innovation Harbor B.V., and can be checked in the RIPE database.

  3. The content of the message

    Filters also look at the message itself. What usually goes wrong: a message that consists entirely of one image, an HTML version without a plain-text version, links pointing to a different domain than the sender's, shortened links, lots of capitals and exclamation marks, or an attachment in a format more often used for malware than for paperwork.

    You can measure this part. Send your message to the address mail-tester.com gives you, then look at the result. You get a list of what stands out about your records, your sending server and your content. Treat the outcome as a checklist, not as a score you have to max out: losing one point for a missing unsubscribe link in an ordinary business email is not a problem.

  4. Complaints from recipients

    If recipients mark your mail as spam, that weighs heavily and carries over to other recipients. It mainly happens with mail people didn't ask for: a list of addresses you once bought or collected, a newsletter without a clear unsubscribe link, or a mailing list that hasn't been cleaned up in years. Recipients that no longer exist also produce error messages, and a high number of those is a negative signal in itself. If you send newsletters, do so through a service that handles unsubscribes and undeliverable addresses automatically, not from your ordinary mailbox.

When it goes wrong with one recipient

If your mail lands in spam with one contact and arrives normally everywhere else, the problem is almost always on their side: a filter set by their IT administrator, a rule in their mailbox, or an earlier click on "spam". Ask the recipient to mark the message as "not spam" and add your address to their trusted senders. That solves it faster than searching further on your end.

If it goes wrong with many recipients at once and your records are correct, send us a message with the full headers of a rejected message. From those we can work out exactly what the receiving server ran into.

What we can't do here

We can review your records, check your sending server and read through the headers of a rejected message with you. We can't force another party to put your mail in the inbox, and we can't promise anyone it will always go well after these steps. We can submit a removal request to a blocklist, but whether it is granted, and how quickly, is up to that list.

Further reading

Was this article helpful?

Still stuck?

Send us a message. We will help you, usually within one working day.