Keep your confirmation email out of the spam folder

An envelope on a conveyor belt in a sorting centre

We’ve all been there. You fill in a form on a website and you are supposed to get a confirmation email. But it just doesn’t arrive. Then it turns out to have ended up in the spam folder. How can you, as an organisation, best prevent that?

There are various reasons why such an email is flagged as spam. In some cases it is because the email address and the associated IP address were once flagged as hacked and so ended up on a list that spam filters regard as potentially dangerous. So it is a good idea to check whether this has happened to your organisation.

Request for Comments

But there are also a number of technical reasons why a confirmation email is seen as spam. Often it has to do with how an email is structured. Since the beginning of the internet, protocols have been drawn up that serve as standards for the internet, so-called RFCs (Request for Comments). If an email does not comply with these RFCs, it is flagged as a potential danger and disappears into the spam folder.

Especially now that emails no longer contain just text, but also links and images, the email really does have to stick to the rules. Use ‘containers’ to lay out an email. These containers hold either text or code, and together they make up the email. That way the receiving mail server knows what to expect (text only, or HTML code as well). If this is not set up properly, the confirmation emails may be flagged as spam.

SPF records

Another important factor is missing or incorrect SPF records. Sender Policy Framework (SPF) records verify the origin of incoming emails: does an email really come from the server it claims to come from? If they are missing, or not set up properly, an email is also seen as spam. So make sure the SPF records are set up correctly, including for your website’s mail server. This is a lot of work, which is why spammers often don’t do it.

Email queue

A common problem is that confirmation emails are sent from an app or an email module on a website. These modules are often not connected to a mail server. As a result, such an email cannot be placed in a waiting line (queue) when the receiving server is busy, to try sending it again later. Onlinespamfilter checks for this too. If an email is not offered again after a while, it is seen as spam and stopped by us. To prevent these problems, it is therefore wise to connect a mail server to your web server and send the confirmation emails from there.

So an email can be flagged as spam for various technical reasons. We therefore recommend checking whether your confirmation email meets the points above. That way your customers don’t have to keep waiting endlessly for their confirmation.