Configure Email Forwarding

The Problem

You need mail sent to one address to automatically land in another inbox — a sales@ address forwarding to your personal mailbox, or an old domain still needing to reach your current one — but basic forwarding set up the wrong way breaks SPF and can get the forwarded mail marked as spam.

About this problem

Email forwarding is simple in concept but has a well-known side effect: it naturally breaks SPF, since the forwarded message now arrives at the final destination from the forwarding server's IP rather than the original sender's, which isn't in the original sender's SPF record. Done carelessly, this means a perfectly legitimate forwarded message can get flagged or rejected at the final destination.

This gets set up for all kinds of reasons — consolidating several addresses into one inbox, keeping an old domain's mail flowing during a transition, or giving a role-based address (support@, sales@) a human inbox to land in.

What's Included

• Setting up the forwarding rule(s) you need, from whichever address(es) to whichever destination
• Checking whether the forwarding mechanism supports SRS (Sender Rewriting Scheme) to preserve SPF validity
• Adjusting SPF/DKIM considerations so forwarded mail doesn't get needlessly flagged at the destination
• Testing with real messages to confirm forwarding is instant and reliable
• A quick note on how to add or change forwarding rules yourself later

What's NOT Included

• Fixing deliverability issues at the final destination mailbox unrelated to the forwarding itself
• Two-way email aliasing where replies need to appear to come from the original address (see email alias setup instead)
• Forwarding attachments or content filtering/transformation beyond standard forwarding

How It Works

1. Confirm the exact source and destination addresses, and whether this needs to be one rule or several.
2. Check whether the mail platform/forwarding service supports SRS, which rewrites the envelope sender so SPF still validates at the final hop.
3. Set up the forwarding rule(s) at the DNS or mailbox-provider level, whichever is appropriate for the platform in use.
4. Where SRS isn't available, check whether the destination's own spam filtering is likely to flag forwarded mail and adjust where possible.
5. Send live test messages through each forwarding rule and confirm they arrive promptly and aren't filtered.
6. Document the forwarding setup so it's clear what's forwarding where if you need to change it later.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

Does email forwarding affect SPF or DKIM?

Forwarding typically breaks SPF validation at the final destination unless the forwarding service rewrites the sender using SRS; DKIM usually survives forwarding since the signature travels with the message content.

Can I forward email from one domain to a completely different domain?

Yes, forwarding works across domains and providers, though the SPF/deliverability considerations are the same regardless of whether source and destination share a domain.

Will forwarded emails look like they came from the original sender?

The original sender's name typically still shows, but some providers add a note or change technical headers to reflect the forwarding — appearance varies slightly by platform.

Can I forward an address to multiple inboxes at once?

Yes, most forwarding setups support sending a copy to several destinations simultaneously if that's what you need.

Is email forwarding the same as an email alias?

Not quite — forwarding typically just redirects incoming mail, while an alias can often also let you send mail that appears to come from the alias address, which forwarding alone doesn't provide.

Why is my forwarded mail ending up in spam at the destination?

Usually because SPF fails for the forwarded message at the final hop and the destination's spam filter weighs that heavily — using a forwarding method that supports SRS or relies more on DKIM/DMARC alignment reduces this risk.