What happens when you forward an email?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

Let's say someone forwards your newsletter to a colleague. Or a customer forwards your receipt to their accountant. What actually happens under the hood, and why does it matter for deliverability?

So when When someone hits "forward", their mail client creates a brand new message. The original email gets embedded or quoted in the body, but all the technical headers that proved your email was legitimate (From, To, Message-ID, authentication signatures) are no longer active. They're just text now, sitting in the quoted content like any other paragraph.

The forwarded message uses the forwarder's own From address and their own domain's authentication. If the original email had a DKIM signature, it'll fail validation on the forwarded copy because the body content changed (the forwarder added "FYI" or "See below" or just quoted the whole thing). That's not a bug, that's how forwarding works. The new sender is responsible for the new message.

Why this matters: if you're tracking "forwarded to a friend" shares, don't expect your original authentication to pass. The forwarded email is the forwarder's email, not yours. Their reputation is what mailbox providers check, not yours. If their domain has bad authentication or a poor reputation, the forwarded email might land in spam even if your original delivered perfectly.

One practical consequence: "Forward to a Friend" features built into ESPs work differently than manual forwarding. When Mailchimp or Brevo offer a "forward this email" button, they're actually sending a new email from your domain with the original content, not letting the subscriber forward from their own inbox. That keeps your authentication intact and gives you tracking data. Manual forwarding (hitting forward in Gmail or Outlook) gives you neither.

And if you're seeing DKIM failures or SPF failures on what looks like your email, check if it's actually a forwarded copy. The symptoms look similar (failed auth, different delivery path) but the root cause is completely different. A forwarded email failing DKIM is normal. Your original email failing DKIM is a setup problem.

Want to see what's actually in the headers of a forwarded email versus the original? Grab both and run them through our Email Header Analyzer to compare side by side.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Analyze My Forwarding Setup

I read this on the Email Almanac about "What happens when you forward an email": "When someone forwards your email, it creates a brand new message under their authentication. The original DKIM signature fails because the body content changed. The forwarded email's deliverability depends on the forwarder's domain reputation, not yours. ESP 'forward to a friend' features work differently because they send a new email from your domain with tracking intact." Help me apply this to MY specific situation: 1. If I'm seeing authentication failures, how do I tell if they're from forwarded copies (normal) or my original sends (problem)? 2. Should I be using an ESP's built-in "forward to a friend" feature instead of encouraging manual forwarding? 3. If customers are forwarding receipts or transactional emails internally, could that cause deliverability issues for them? 4. What tracking data do I lose when someone manually forwards versus using a share feature? --- My details (fill in what applies): - Email platform/ESP: e.g. Mailchimp, SendGrid, Postmark, HubSpot, Gmail - Email type: [marketing newsletter, transactional receipts, internal communications] - What I'm seeing: [DKIM failures in reports, forwarded emails landing in spam, tracking gaps] - Use case: [encouraging shares, tracking virality, troubleshooting auth failures] - Experience level: beginner / intermediate / advanced

Edit the yellow boxes, then send to the AI of your choice.