DKIM is no use for spam filtering

We sometimes get questions about supporting and implementing DKIM. Somewhere the idea arose that it works against spam. But that is by no means the case. That is why we always say ‘no’. This may sound illogical given the information you have heard about it. So we are happy to explain why we don’t want to sell you DKIM.
DKIM seems popular because it shows up in all kinds of online checklists from security companies. But the value of DKIM stands or falls with the right implementation. And a spam filter platform in the Cloud is a typical example of implementing this security feature in the wrong place.
Why don’t we implement DKIM?
We don’t implement DKIM. Simply because it gives zero protection against spam. It is certainly a useful technique, but not for spam filtering. DKIM can increase the security of your email communication, provided it is implemented in the right place. If you don’t do it the right way, it’s nice to be able to tick the feature off for show, but it encourages a false sense of security. To see why, we need to understand exactly what DKIM is for.
What is DKIM for?
DKIM is a technique in which you give your email a cryptographic signature, so the receiving party can see that (parts of) the email were not changed ‘along the way’. Just like a normal signature, you really have to add it before you seal the envelope and hand it to the postman. So it is best done as close to the sender as possible.
So DKIM is really a technique you apply on the sending mail server, where the email is first submitted. By the time an email reaches our spam filter service, it is actually already too late; the message may already have been altered by a malicious party along the way! As a result, the recipient of the message wrongly believes the message is safe.
The reverse is also true. If Onlinespamfilter checks a DKIM signature, that doesn’t release the recipient from still doing it themselves. What would happen, for example, if Onlinespamfilter were hacked? Or if a ‘bad actor’ were active on an intermediate server after our spam filter? The DKIM signature is best checked in the recipient’s email client. This usually requires add-on software.
DKIM is useless in fighting spam
In fighting spam, a DKIM signature is effectively useless: spammers and scammers who send with a DKIM signature always do so from a hacked account, so they know the DKIM signature is valid. And if not, they send without the signature, so there is nothing to check. Only an invalid DKIM signature means that ‘something’ in the message was changed along the way.
Onlinespamfilter can look at this on request. This check is off by default, because in practice many legitimate parties make mistakes when signing their email, which often leads to email being rejected wrongly.
SPF is useful for protection against spam
SPF, on the other hand, is a very useful protocol in the fight against spam. It is, as it were, a list of servers your emails may be sent from. Most spammers know that too. So it is practically impossible for a spammer to send an email from your domain, unless of course you let your server get hacked. Also read our blog post about SPF.
