‘Mail forwarding is dead’

An envelope stuck halfway in a letterbox

In the fight against spam, many measures have been taken and new systems devised in recent years. One of those systems is the Sender Policy Framework, or SPF. A handy system, but one that gets in the way of one of the oldest functions of email: automatic forwarding.

SPF verifies the origin of incoming email: does an email really come from the server that is allowed to send for the sender’s domain? If not, the email is regarded as ‘spam’. These days this check is an important weapon in the fight against unwanted email. That’s why more and more companies have set up SPF records for their domain.

Your server is not in the SPF records

And that is exactly where a problem lies. Especially at companies that use an outdated or closed mail environment, where you can’t get to your email from another location. For example, when an employee works from home. To still be able to read the email, a rule is often created that forwards mail automatically (mail forwarding): all mail sent to the employee’s email address must be forwarded, unopened, to a personal email address, such as a Gmail one.

So what’s the problem? Say you receive an email from Facebook that has been checked by Onlinespamfilter, found to be fine and delivered to your mail server. The rule set up on your mail server says that this email must be sent straight on to the personal address. And that is what this mail server does. In short, it then pretends to be a Facebook mail server. But this server is of course not included in Facebook’s SPF records; you have no permission whatsoever to send mail on their behalf. Gmail sees that too, and can’t tell that the email took a detour. That’s why Google will inevitably reject the email. It makes no difference whether you hand the email to Google directly or through Onlinespamfilter’s sending service.

This can have quite some consequences: mail no longer arrives (because Gmail doesn’t trust it), and if this happens too often, the sending server may be seen as untrustworthy and put on a blacklist.

How do I prevent this?

This is something users have to solve themselves. One solution is to automatically give a forwarded email a new sender address. This ‘Sender Rewriting Scheme’ is explained on Wikipedia. Because this has to be set up differently for every server, Onlinespamfilter unfortunately has no general manual for it.

SPF records are a good way to make a start against spammers abusing your domain. But it does mean that one of the oldest – and still widely used – functions of email is disappearing.