
The short answer: when your address forwards messages to another (for example, to Gmail), the destination server sees the message arriving from your server, which is not on the list of who may send for the original sender. SPF fails, and the message falls into spam or is refused. There are three ways round it.
Why it happens
| Step | What goes on |
| 1. Someone writes to you | The sender (a bank, say) writes to your address on your domain. |
| 2. Your server forwards | It hands the message to Gmail with the original sender’s address, but from your server. |
| 3. Gmail checks SPF | It asks the sender’s domain whether your server is authorised. It is not. It fails. |
| 4. The result | Spam, quarantine or refusal, especially if the sender has a strict policy (DMARC). |
| What survives | The DKIM signature, when there is one and it is not altered, passes the check even when forwarded. |
What to do, in order of preference
|
|
|
|
|
| Adding the forwarding server to the sender’s SPF does not work: that is not in your hands (it is the other party’s domain) and should not be. Those who can act are you, by changing how you receive, or the forwarder, by rewriting the sender. |
| Forwarders, aliases and catch-all are easily confused: Catch-all, forwarders and aliases. If the message came back with a code, see Bounce message 550. |
|
An important message does not arrive when forwarded? Open a ticket with that message’s full header (no passwords). Open a support ticket |
RECOMMENDED PRODUCT Professional e-mail on your domain Mailboxes in your company name, no adverts, with spam filtering. from $5.36/mo (3-year plan, with coupon) See plans |
- 0 Users Found This Useful











