DKIM: DomainKeys identified mail
In a last effort to save e-mail from being obsoleted, some guys at Yahoo thought of the DomainKeys system to prevent message spoofing. SMTP servers that are DomainKeys-aware can check the contents of the message to find out whether it was really sent by the person mentioned in the From: mail header.
To be honest, I’m more of a fan of SPF. It’s an incredibly simple protocol and I really can’t think of any reason it shouldn’t be used by any mail server. (Interestingly, the Yahoo mail servers don’t use it, probably to boost acceptance of DomainKeys.)
Let’s explain SPF first, since it so much easier. In a nutshell: SPF uses DNS records to identify which IPs are allowed to send mail for a domain. So a server receiving mail for email@example.com would fetch the SPF record from example.com and check whether the IP of the connected SMTP client is actually allowed to send mail originating from the example.com domain.
That’s it, it’s that easy. Since I’m hosting my own mail server, my domain’s SPF record just mentions my mail server’s IP (actually, it doesn’t mention the IP directly, but refers to its DNS A record.) A server receiving an e-mail that was allegedly sent by me will just have to check whether the SMTP client is in fact my own mail server and if it isn’t, reject the mail.
DomainKeys is a little more advanced. Instead of checking the IP, it will check all contents of the message. It’s like the mail server is signing the message on your behalf. Using DKIM, each outgoing message will be signed using the server’s private key, and DKIM signatures present in the incoming message will be checked against the originating server’s public key. That public key, by they way, is distributed using a DNS record, similar to the way SPF records are distributed.
Here are the steps I did to get DKIM working on my server. First, create an RSA key pair:
Now you’ll have to add the public key to your domain(s) DNS entry. Do this by adding a TXT record for selector._domainkeys.yourdomain.com, where selector can be anything, but make sure to mention the same selector in the config file.
Next, install dkim-filter and edit the /etc/dkim-filter.conf Domain, KeyFile and Selector settings. Domain= comma separated list of domains for which to sign the mail; KeyFile= path to above keyfile; Selector= domain name prefix.
Add the following to /etc/postfix/main.conf:
and restart postfix.
To test whether it’s working as it should, send yourself a mail and inspect the headers. Or, you could for example send a mail to a gmail account and gmail will show that the mail is “signed-by” your server.