The short version
- Email forwarding re-sends a message that reached one address on to another address. It happens in one of three places: you press Forward, your mailbox follows a rule, or a mail server forwards everything sent to an address.
- Every email carries two sets of addresses: the envelope that servers use for delivery, and the From and To headers you see. Forwarding changes the envelope, which is why it can break SPF checks.
- Good forwarders fix this by rewriting the envelope sender (SRS), leaving DKIM signatures intact, and adding ARC. Without those, forwarded mail is far more likely to land in spam.
How does email forwarding work? When a message reaches an address that forwards, a mail server accepts it and immediately sends it on to a second address, so it lands in an inbox the sender never wrote to. That sounds simple, but behind it sit DNS lookups, two separate sets of addresses on every email, and authentication checks that forwarding can easily break.
This guide follows a forwarded message hop by hop. You’ll see the three kinds of email forwarding, what changes on the way, why forwarded mail sometimes ends up in spam, and how to set up forwarding in Gmail and Outlook without losing messages. No mail-server experience needed: each technical term is explained when it first comes up.
What Is Email Forwarding?
Email forwarding is sending a message you received on to another email address. The new recipient gets a copy of the original message, usually with its subject, body and attachments, even though the original sender only wrote to you.
People use the word for three quite different things, and that’s the source of most confusion:
- Pressing Forward on one message. You open an email, click Forward, add a recipient and send. This is a brand-new email from you that quotes the original.
- Automatic forwarding from your mailbox. You tell Gmail or Outlook to send a copy of every new message, or of messages that match a rule, to another address.
- Forwarding at the address level. An address has no mailbox of its own. Its mail server simply passes everything it receives to a real inbox. This is how forwarding addresses, catch-all domains and email aliases work.
The first is something you do by hand. The other two run automatically on a mail server, and they’re what people usually mean when they ask how forwarding works. They’re also where the interesting problems with spam filters and authentication appear.
How Does Email Forwarding Work? The Short Answer
In one sentence: a server receives a message for one address, then sends a new copy of it to a different address, acting as a sender itself. Forwarding is always two deliveries, never one. The original sender’s server delivers to the forwarding server, and the forwarding server delivers to the final inbox.
That second delivery is the part that matters. To the receiving inbox, the forwarding server is the one knocking on the door, not the person who wrote the message. So the final inbox has to decide whether to trust a message that claims to come from one company but arrives from another company’s server. How the forwarder handles that question decides whether the message lands in the inbox, in spam, or nowhere at all.
If you only need the basics, that’s the whole idea. The rest of this guide explains each piece: what changes between the two deliveries, which checks can fail, and what a well-run forwarder does to keep its mail trusted.
The Three Kinds of Email Forwarding
Each kind of forwarding behaves differently, from who appears as the sender to whether replies go back to the original sender. The table sums up the differences.
| Kind | Who triggers it | Shown as sender | Replies go to | Typical use |
|---|---|---|---|---|
| Manual forward (Forward button) | You, one message at a time | You | You | Sharing a receipt or thread with a colleague |
| Mailbox auto-forwarding | A setting or rule in your mailbox | Usually the original sender | The original sender | Moving from an old account, collecting mail in one place |
| Address-level forwarding | The mail server for the address | Original sender, or the alias address | The original sender, or a reply address that hides yours | Forwarding addresses, custom domains, email aliases |
1. Manual forwarding
When you press Forward, your email app creates a new message. It puts “Fwd:” in front of the subject, quotes the original under a short header block (From, Date, Subject, To), and keeps the attachments. You are the sender, so the message is checked as your mail, and any reply comes back to you. Nothing about the original sender’s authentication matters any more.
That’s why manual forwarding almost never causes delivery problems. It’s also why the original sender can’t tell you forwarded their message unless the new recipient tells them.
2. Mailbox auto-forwarding
Here your mailbox provider sends a copy of incoming messages to another address without you doing anything. The forwarded copy normally keeps the original From address, so the final inbox sees a message from, say, your bank, delivered by Gmail’s or Outlook’s servers. That mismatch is exactly the situation spam filters are built to question.
3. Address-level forwarding
With address-level forwarding, the address itself is just a routing rule on a mail server: “anything that arrives for this address, send to that inbox”. There’s no mailbox to log into. Forwarding services, domain hosts and alias services work this way, and the same pattern lets you forward one alias to several inboxes or catch every address on a domain with a catch-all address.
Two Addresses on Every Email: the Envelope and the Headers
To understand forwarding, you need one idea that most people never hear about: every email has two sets of sender and recipient addresses.
- The envelope. When two mail servers talk, the sending server announces a sender (the MAIL FROM command, also called the return path or bounce address) and a recipient (RCPT TO). Servers use these to route the message and to return bounces. The SMTP standard, RFC 5321, defines this conversation.
- The headers. Inside the message are the From, To and Subject lines your email app shows you. These are part of the message content, much like the letterhead and greeting inside a paper letter.
The two usually match, but they don’t have to. A newsletter can show “From: The Shop” while its envelope sender is a bounce address at the shop’s email provider. Blind copies work the same way: a Bcc recipient is in the envelope but not in the To or Cc headers.
Forwarding depends on this split. A forwarder changes the envelope recipient (from your forwarding address to your real inbox) and often leaves the visible headers alone. Whether it also changes the envelope sender is the single biggest factor in whether forwarded mail gets delivered, as the next sections show.
How Does Email Forwarding Work, Step by Step?
Let’s follow one message. Alice at shop.example writes to you@forward.example, an address that forwards to your Gmail inbox. Here’s what happens, hop by hop.

- The sender’s server looks up your domain. Alice’s mail server asks DNS for the MX records of forward.example. MX records name the servers that accept mail for a domain.
- It delivers to the forwarding server. Alice’s server connects to that server and sends the envelope (sender alice@shop.example, recipient you@forward.example), then the message itself.
- The forwarding server checks the message. A good forwarder runs the usual checks at this point (SPF, DKIM, DMARC, spam and virus filtering) and records the results. Rejecting obvious spam now protects its reputation later.
- It looks up the forwarding rule. The server finds that you@forward.example should go to your Gmail address and swaps the envelope recipient.
- It decides on the envelope sender. A careless forwarder keeps alice@shop.example. A careful one rewrites it to an address on its own domain, using SRS or its own bounce address.
- It may add headers. Many forwarders add a forwarding note or an ARC seal recording what the checks in step 3 found.
- It delivers to your inbox. The forwarding server looks up Gmail’s MX records and delivers the message, now acting as the sender.
- Your inbox runs its own checks. Gmail checks SPF, DKIM and DMARC again from scratch, plus its own spam signals, and then files the message in your inbox or spam folder.
Steps 5 to 8 are where forwarding succeeds or fails. The message left Alice as a trusted, authenticated email. Whether it still looks trustworthy after the second delivery depends on what the forwarder did in between.
Why Forwarding Breaks SPF, and How SRS Fixes It
SPF (Sender Policy Framework) lets a domain publish the list of servers allowed to send its mail. The receiving server takes the domain from the envelope sender, looks up that domain’s SPF record, and checks whether the connecting server is on the list.
Now look at the second delivery. If the forwarder keeps alice@shop.example as the envelope sender, Gmail checks shop.example’s SPF record and finds the forwarding server isn’t on it, because it isn’t one of the shop’s servers. SPF fails, even though nothing dishonest happened. The SPF standard, RFC 7208, discusses this limitation directly.
The fix: rewrite the envelope sender
The Sender Rewriting Scheme (SRS) solves it. The forwarder replaces the envelope sender with an address on its own domain that encodes the original one, for example SRS0=hash=time=shop.example=alice@forward.example. Gmail now checks forward.example’s SPF record, the forwarding server is listed, and SPF passes.
The encoding isn’t decoration. If the final delivery bounces, the bounce goes to the forwarder, which decodes the address and passes the bounce back to Alice. The hash and timestamp stop spammers from abusing the rewritten addresses to send their own mail. Some services use their own bounce addresses instead of classic SRS, which works the same way for SPF.
Google’s own advice matches this. Its page on forwarding email to Gmail tells forwarders to change the envelope sender to their own domain, set up SPF and DKIM, and filter spam before forwarding it.
DKIM, DMARC and ARC on Forwarded Mail
SPF is only half of email authentication. The other half travels inside the message, which is why it can survive forwarding.
DKIM survives, if nobody edits the message
DKIM (DomainKeys Identified Mail, RFC 6376) adds a cryptographic signature to the message, covering the body and key headers such as From and Subject. The receiver checks it against a public key in the sender’s DNS. Because the signature is part of the message, it still verifies after forwarding, as long as the signed parts are unchanged.
That’s the catch. Forwarders that add a footer, tag the subject line, or re-encode the message break the signature. Mailing lists are the classic example: adding “[list-name]” to the subject is enough.
DMARC decides what happens next
DMARC ties the two checks to the visible From address. A message passes DMARC if SPF or DKIM passes for a domain that matches the From domain. Our guide to what DMARC is covers the details. For forwarding, the outcomes are:
- SPF fails, DKIM intact: DMARC still passes thanks to DKIM. This is the normal case for clean forwarding.
- SPF rewritten by SRS, DKIM intact: DMARC passes thanks to DKIM. SPF passes too, for the forwarder’s domain, which helps its reputation.
- DKIM broken by edits: DMARC fails. If the sender’s domain publishes a strict policy (p=reject), the final inbox may refuse the message completely.
ARC records what the forwarder saw
ARC (Authenticated Received Chain, RFC 8617) covers the cases where a message had to change. The forwarder adds signed headers saying, in effect, “when this reached me, SPF, DKIM and DMARC passed”. A receiver that trusts the forwarder can rely on that record even if the original signature no longer verifies. ARC doesn’t force anyone to accept a message, but it gives honest forwarders a way to vouch for the mail they pass on.
Why Forwarded Emails Land in Spam
Even with the authentication right, forwarded mail faces extra suspicion. These are the usual causes:
- Forwarding spam along with everything else. If a forwarder passes on junk and you mark it as spam, the receiving provider learns that the forwarding server sends spam. Over time, its genuine mail suffers too. Google specifically warns about this.
- No SRS and no DKIM. A message with failing SPF and no valid DKIM signature fails DMARC and looks exactly like a forgery.
- Modified messages. Footers, subject tags or rewritten links break DKIM signatures.
- A new or shared forwarding server. Servers with little sending history, or shared with careless users, start with a weak reputation.
- The sender’s own reputation. Forwarding doesn’t clean up mail from a sender that inboxes already distrust.
The practical takeaway: if forwarded mail keeps landing in spam, check the full headers of one message. Look at the Authentication-Results line for spf=, dkim= and dmarc= results, and whether the envelope sender (Return-Path) was rewritten. That tells you which link in the chain broke.
How Does Email Forwarding Work in Gmail and Outlook?
Both providers do mailbox auto-forwarding: they receive the message in your account and send a copy on. The setup differs slightly.
Gmail
- On a computer, open Gmail, click the Settings gear and choose See all settings.
- Open the Forwarding and POP/IMAP tab and click Add a forwarding address.
- Enter the destination address. Gmail emails a confirmation link to that address, and forwarding only works after it’s confirmed.
- Back in Settings, choose Forward a copy of incoming mail to, pick the address, and decide whether to keep Gmail’s copy in the inbox or archive it.
- Click Save Changes.
Gmail forwards new mail only, not spam, and not messages you already have. To forward only some messages, create a filter instead. Google’s help page on automatic forwarding covers both options. Gmail also shows a reminder banner for the first week after you turn forwarding on.
Outlook
- In Outlook.com, open Settings, then Mail, then Forwarding and IMAP (in the new Outlook app, Mail then Forwarding).
- Turn on Enable forwarding and enter the destination address.
- Choose whether to keep a copy of forwarded messages, if the option is offered, and save.
Microsoft’s guide to automatic forwarding in Outlook also covers forwarding with rules. On work and school accounts, your administrator may block forwarding outside the organisation. Microsoft 365 turned automatic external forwarding off by default for new organisations in 2021, and blocked messages bounce back with error 5.7.520 Access denied, as Microsoft’s documentation explains.
Mailbox forwarding and your privacy
Mailbox forwarding keeps your original address in use. Every site that has it can still email it, sell it, or leak it in a breach. Forwarding only moves where those messages end up. If the goal is to protect the address itself, you need address-level forwarding with a separate address for each site.
How Does Email Forwarding Work With an Email Alias?
An email alias is address-level forwarding built for privacy. You give a website an alias instead of your real address, and the alias service forwards what arrives to your inbox. If the alias starts getting spam or turns up in a leak, you switch that one alias off. The forwarding service explainer, what is an email forwarding service, compares the main types of service.
Here’s how EmailAlias.io handles a forward, mapped onto the steps above:
- Receiving: mail for your aliases arrives at our servers, through our alias domain or your own custom domain on Premium, and goes through spam and authentication checks before anything is forwarded.
- Re-sending: the forward is sent from our own mail servers with a bounce address on our domain as the envelope sender, so SPF passes for our domain. We also add DKIM signatures and an ARC record of the original checks.
- What you see: the message arrives from the alias address, with the original sender shown at the top. Your real address never goes back to the sender.
- Replies: on Premium, a reply goes out through the alias, so the other side only ever sees the alias.
Our aliases are permanent forwarding addresses: they keep forwarding until you turn them off. The free plan includes 10 aliases, and Premium is $4 a month with custom domains and replies.
Troubleshooting Email Forwarding
Most forwarding problems fall into a few patterns:
- Nothing arrives. Check that the forwarding address was confirmed (Gmail requires it), that it’s spelled correctly, and that forwarding is switched on. Then look in the destination’s spam folder.
- Messages bounce with 5.7.520. A Microsoft 365 administrator has blocked external forwarding. Only the admin can allow it.
- Forwarded mail lands in spam. Check the Authentication-Results header. Failing SPF with broken DKIM points to a forwarder that edits messages or doesn’t rewrite the envelope sender.
- Mail loops or duplicates. Two addresses forwarding to each other create a loop. Servers usually stop it after a set number of hops and bounce the message.
- Old messages don’t forward. Auto-forwarding applies only to new mail. Move old mail with an import tool or IMAP instead.
- Large attachments fail. Every hop has a size limit, and the smallest one wins. Send large files as a link.
For forwarding that keeps your real address private and encrypted in transit, our guides to secure email forwarding and private email forwarding go further.
Final Thoughts
So how does email forwarding work? A server accepts a message for one address and delivers a fresh copy to another, acting as the sender for that second hop. Everything else follows from that: SPF fails unless the envelope sender is rewritten, DKIM survives only if the message is left alone, and DMARC and ARC decide whether the final inbox trusts the result.
For everyday use, pick the right kind of forwarding for the job. Use the Forward button to share a message, mailbox forwarding to gather accounts in one place, and an alias service when you want to keep your real address away from the sites you sign up to. With a forwarder that handles authentication properly, forwarded mail is as reliable as any other email.
Frequently Asked Questions
How does email forwarding work?
A mail server receives a message for one address and sends a new copy of it to a different address, acting as the sender for that second delivery. The original sender’s server delivers to the forwarding server, and the forwarding server delivers to your real inbox, which then runs its own spam and authentication checks.
What does forwarding an email do?
Pressing Forward creates a new email from you that quotes the original message and keeps its attachments, with Fwd: added to the subject. The new recipient sees you as the sender, replies come back to you, and the original sender isn’t notified.
Does the sender know if I forward their email?
No. Forwarding happens on your side, so the original sender gets no notice. They’d only find out if the person you forwarded it to replied to them or told them.
Why do forwarded emails go to spam?
Usually because authentication breaks on the second delivery. If the forwarder keeps the original envelope sender, SPF fails, and if it edits the message, the DKIM signature breaks too, so DMARC fails. Forwarding spam along with genuine mail also damages the forwarding server’s reputation.
What is SRS in email forwarding?
SRS, the Sender Rewriting Scheme, replaces the envelope sender of a forwarded message with an address on the forwarder’s own domain that encodes the original one. SPF then passes for the forwarder, and bounces can still find their way back to the original sender.
Does email forwarding break DKIM?
Not by itself. A DKIM signature travels inside the message, so it still verifies after forwarding as long as the signed body and headers are unchanged. Adding a footer, tagging the subject or re-encoding the message breaks it.
How does email forwarding work in Gmail?
In Gmail on a computer, go to Settings, See all settings, then Forwarding and POP/IMAP, and add a forwarding address. Gmail sends a confirmation link to that address. Once it’s confirmed, choose Forward a copy of incoming mail, decide what happens to Gmail’s copy, and save. Only new mail is forwarded, and spam isn’t.
Is an email alias the same as email forwarding?
An email alias is a form of address-level forwarding. Mail sent to the alias is forwarded to your real inbox, but each alias can be switched off on its own, and with a reply feature the other side never sees your real address. Ordinary mailbox forwarding still uses and exposes your original address.
