No, the sender won't get a notification when you forward their email, and most email services won't even tell them it happened. The exception matters more than people expect: if someone wants proof, forwarded headers, embedded tracking pixels, or a Gmail delegation misstep can expose the forward after the fact. The answer isn't "never" β€” it's "not automatically, but sometimes traceably."

Forwarding Doesn't Trigger a Read Receipt the Way Replying Does

Email forwarding is a client-side action. Your mail app takes the message body and headers, wraps them in a new envelope, and sends that as a fresh email. Nothing in the original sender's inbox changes. There's no delivery notification, no read alert, and no server-side record tying the forward back to them unless the forwarded copy lands somewhere they can see.

Read receipts only work when the recipient's email client honors a request embedded in the original message β€” and forwarding strips or resets that behavior. If you forward a message that asked for a read receipt, the new recipient's client may prompt them, but that prompt goes to you, not to the original sender. The original sender's receipt request dies with the original thread.

Compare this to replying. A reply stays in the thread, so the original sender sees it in their inbox naturally. A forward creates a new thread. From the sender's side, the email they sent just sits there unanswered. Some clients (Outlook on Exchange, for one) can show "forwarded" status in the reading pane, but that displays to the recipient of a forward, not the original sender. It's a common inversion of expectations.

The one auto-notification worth knowing: Gmail's "Forwarding" setting under Settings β†’ Forwarding and POP/IMAP sends a confirmation email to the account owner when forwarding is set up β€” not to people whose mail is forwarded. If you've set a filter to auto-forward someone else's messages, they won't be told. The account holder will.

Why the New Recipient Sees a Fwd: Tag but the Original Sender Doesn't

When you hit Forward in Gmail, Outlook, or Apple Mail, the app prefixes the subject with "Fwd:" and pastes the original body under a quote bar. That visible marker reaches the person you forwarded to. The original sender gets nothing. It's a one-way disclosure: the recipient knows you're passing along someone else's words; the author stays in the dark.

That Fwd: prefix is also the cheapest way a recipient can spot that a message wasn't written for them. If a colleague gets "Fwd: Budget questions from Dana," they know Dana didn't send it to them directly. Dana, meanwhile, has no idea. This asymmetry is why forwarding feels private from the sender's side and obviously not private from the recipient's side.

Some people assume the "Fwd:" tag is the only tell. It isn't. Forwarded messages carry the original message's headers in the body if you use "Forward as attachment" (Outlook) or expand full headers (Gmail's three-dot menu β†’ Show original, then copy). Those header blocks include the sender's IP address, the original recipients, and timestamps. A curious recipient can learn a lot from what you paste.

If you want to forward without the tag, you'd have to retype the content, which defeats the purpose and loses the header trail. Editing the subject to strip "Fwd:" is cosmetic. The header block, if pasted, still names the original.

Tracking Pixels Travel With the Body You Forward, Not the Sender's Inbox

Email tracking works via a tiny invisible image (a 1Γ—1 pixel) loaded from a tracking server when the message is opened. Tools like Mailtrack, HubSpot Sales, and Yesware attach these to outbound emails and log opens against the sender's account. Here's the part that catches people: when you forward a tracked email, the tracking pixel is usually still in the HTML body β€” unless your client strips it.

That means the original sender's tracking dashboard may register a new open when your recipient loads the forwarded message. Their dashboard shows "opened" and sometimes a location or device guess, but it can't tell them who opened it or that the message was forwarded. They may see two opens from two locations and infer a second reader. That inference is the closest thing to "knowing," and it's a guess, not a notification.

Whether the pixel survives depends on your client and how you forward. Gmail's plain "Forward" sends HTML, so pixels often ride along. "Forward as attachment" (Outlook) or pasting as plain text strips them. Some corporate mail gateways β€” Microsoft 365 Defender, Google Workspace security settings β€” block third-party tracking pixels entirely, so the original tracker logs nothing from the forwarded copy. The behavior is genuinely inconsistent across setups, which is why you can't assume "tracked means notified" or "tracked means lost."

A worked example of the confusion: a salesperson sends a tracked email to a prospect, who forwards it to a procurement colleague. The tracker logs two opens β€” 9:14 a.m. from the prospect's city, 11:02 a.m. from a nearby city. The salesperson now knows the message was read twice from two places. They do not know who the second reader was, whether a forward happened, or what the second reader did after reading. The pixel delivers a number, not a story.

How a Recipient Can Prove a Forward Happened After the Fact

If you need to establish that an email was forwarded, you don't need the sender's cooperation β€” you need the headers. Every email message contains a chain of "Received:" lines recording each server that handled it. A forwarded message, if forwarded with headers intact, shows the original server path plus the new path.

Here's the verification path in plain steps:

1: Open the forwarded message in Gmail, click the three-dot menu next to the reply arrow, and choose "Show original." 2: Look for the "Received:" lines at the top β€” the newest is your server, the oldest is the original sender's outbound server. 3: Compare the "Return-Path" and "From" domains. If the original sender's domain appears in the header chain but not in your own account, the message passed through their outbound flow. 4: Check the "Reply-To" and "Date" fields against the thread you expected. 5: If the forwarder used "Forward as attachment" (Outlook: Home β†’ More β†’ Forward as Attachment), the original .eml file is a downloadable attachment with full headers, which is the strongest proof a recipient can hold.

Failure case worth flagging: if the forwarder pasted the body as plain text rather than forwarding the message, none of this survives. You get clean text with no header chain. Similarly, if a corporate gateway rewrites headers (common with some DMARC-rewriting services), the original "From" domain may be replaced by a forwarder's relay domain. In that case, the header trail points to the relay, not the original author, and you'll need to ask the forwarder directly.

For legal or HR purposes, a forwarded .eml or .msg attachment with full headers is usually accepted as evidence of the message's existence and path. A plain-text paste is not. The distinction matters and is frequently glossed over in casual advice.

The Bcc Trap: How a Sender Learns About a Forward by Accident

The most common real-world way senders find out about a forward has nothing to do with emails at all. It's email chains where someone replies-all and a forwarded recipient is still on the copy line. The forward becomes a reply. The sender sees a name they don't recognize in the To or Cc field and asks.

A close cousin: Bcc. If you Bcc someone and they hit Reply All, their address appears to everyone on the thread, including the original sender. Senders learn about Bcc'd readers this way constantly. Neither is a notification β€” it's a consequence of the recipient's own action.

There's also the auto-reply leak. If you forward a message to a colleague who has an out-of-office reply, that auto-reply goes to you, not the original sender. But if a forwarded chain later loops back β€” someone replies to the whole thread and the original sender is still copied β€” the auto-reply can surface. These accidental loops are the dominant cause of "how did they know I forwarded this?" surprises. The technology didn't tell them. Someone's reply did.

Google Workspace adds one more scenario. If an admin has set up email delegation (Settings β†’ Users β†’ Delegated access), the delegate can read the mailbox. A sender who knows the delegation exists may infer forwards are visible. The delegate sees forwarded messages, but the sender doesn't. Delegation is visible to the delegate and admin, not to senders β€” a frequently confused boundary.

Gmail, Outlook, and Apple Mail: What Each Does and Doesn't Tell Anyone

The big three email clients behave differently enough that a general "they won't know" needs a per-client check. Here's the side-by-side on what happens when you forward, using default settings on current versions as of late 2026:

Client Sender notified of forward? Tracking pixels survive forward? Headers preserved in forward? Notable exception
Gmail (web) No Usually yes (HTML forward) Yes via "Show original" Auto-forwarding setup sends confirmation to account holder only
Outlook desktop (Microsoft 365) No Often stripped by "Forward as Attachment" Yes, full .eml attachment Exchange "forwarded" status visible to the recipient, not sender
Apple Mail (macOS/iOS) No Usually yes unless "Send as plain text" Yes if headers expanded iOS share sheet may strip HTML in some paths
Gmail app (Android/iOS) No Usually yes Partial (headers via web only) Mobile app can't show original headers; use desktop
Outlook web (OWA) No Usually yes Yes via "View message details" Tenant tracking-block settings can strip pixels

The verdict row by row: nobody notifies the sender by default. The difference is in what survives the forward β€” pixels and headers β€” and that's where the traceability lives. If your recipient is sophisticated and you're forwarding a tracked email, the sender's dashboard may pick up an extra open. If you're forwarding to a corporate tenant with pixel blocking, nothing survives.

One drawback worth stating plainly: Outlook's "Forward as Attachment" is the best option for preserving evidence, but it also means the recipient gets a downloadable file they may not open β€” they might reply "can't read it" and you're back to pasting. The safest practical default is to forward normally and tell your recipient in the body why you're forwarding, which sidesteps most of the inference games.

Worked Scenario: A Colleague Forwards a Client Email and the Dashboard Lights Up

Put real numbers on the tracking-pixel uncertainty. A sales team uses HubSpot Sales to track outbound proposals. A rep sends a proposal to a client at 10:00 a.m. The client opens it at 10:07 a.m. from their office IP β€” logged as open #1. The client then forwards it to their finance director at 2:30 p.m. The finance director opens it at 3:15 p.m. from a different city.

HubSpot logs open #2 at 3:15 p.m. from the finance director's city. The rep sees two opens, two locations. Total elapsed time from send to second open: 5 hours, 15 minutes. The rep does not see a "forwarded" flag, a name, or a reason. HubSpot's own documentation frames these as "opens," not forwards, and the tool has no forward-detection feature in its standard pipeline.

What the rep can legitimately conclude: someone at the client organization is still reading the proposal, and at least two devices or locations touched it. What the rep cannot conclude: who forwarded it, whether the finance director was the second reader, or whether an assistant opened it on the client's behalf. The dashboard oversells certainty, and good sales managers teach reps to treat "two opens" as a prompt to follow up rather than proof of a forward.

Wrap the same example in a corporate tenant with Microsoft 365 Defender's safe-link and pixel-blocking settings turned on. The forwarded copy's pixel never loads. The dashboard shows one open. The rep sees nothing. The forward still happened, invisibly. This asymmetry β€” visible to the recipient, invisible to the tracker, and vice versa depending on settings β€” is the core fact of the whole topic.

Forwarding Your Own Sent Mail Is Different From Forwarding Someone Else's

When you forward a message you sent to someone new, you're the sender and forwarder at once. No mystery. But consider forwarding your sent copy to a third party so they can see what you told a client. From the client's side, nothing happened. From the third party's side, they see your words plus the headers. From your side, you have a record. This is the safest, most common legitimate use of forwarding and carries no notification risk to anyone.

Forwarding someone else's message is riskier because you're handling their words and their metadata. Three rules make it clean: don't alter the body, don't strip the header block if the recipient needs provenance, and add one sentence at the top saying who you are and why you're forwarding. That sentence does more to prevent misunderstandings than any technical trick.

There's also the reply-vs-forward confusion. Some people use "Forward" to reply to a thread β€” sending the same message back with a note. That creates duplicate messages in the original sender's inbox if they're on the thread, and it can trigger the accidental-loop scenario above. The correct action is Reply or Reply All. Forwarding is for people outside the thread.

If you're forwarding from a shared mailbox (front desk, support queue), the sender of the original message may see a new address appear if a later reply-all touches the thread. Shared-mailbox forwards don't notify the sender either, but shared mailboxes are often watched by more people, and that's a disclosure risk everyone involved should know.

Where "They Won't Know" Breaks: Relays, DMARC, and Header Rewrites

Some email setups rewrite "From" when forwarding. If your organization uses a forwarding relay β€” a group address that forwards to members, or an alias that redirects β€” the original sender's DMARC check may fail on the relayed copy, and the relay may rewrite the "From" domain to its own to pass authentication. The recipient then sees the relay's domain in the header chain.

The practical implication: if you forward through a company alias (support@ β†’ individual inboxes), the sender's original message may still be visible in the body, but the header trail points to your relay, not to the original sender. A recipient trying to trace the path finds the relay and stops. The original sender still gets no notification β€” but they also lose control over the header provenance, which matters if the message is later used as evidence.

A second break case: Bcc'd auto-forwarding rules. If someone sets an inbox rule "forward all messages with 'contract' in the subject to outside address," the original sender never sees it, but the outside recipient gets full headers. The sender has no notification and no visibility. If that outside recipient later replies to the sender, the sender learns. The leakage is always in the reply, never the forward.

The DMARC angle is worth one sentence of caution for anyone in compliance: forwarding can break authentication and cause legitimate messages to land in spam at the destination. If you routinely forward client messages internally, ask IT whether the relay passes DMARC. The answer determines whether your forwards arrive or vanish silently β€” a failure mode nobody tells the sender or the forwarder about.

When Forwarding Should Not Be Quiet: Confidentiality and the Read-Once Mindset

Some messages shouldn't be forwarded quietly, not because the sender will find out but because they ought to. A message marked confidential, a legal notice, an HR note, a client's private account detail β€” these are candidates for asking first, or forwarding with the sender copied so nothing is hidden.

The technical fact remains: no notification fires. That's exactly why forwarding should be treated as a decision, not a reflex. The confidentiality default in most organizations β€” "don't forward without permission" β€” exists precisely because the email protocol makes quiet forwarding easy. The protocol won't protect the sender; company policy has to.

A useful habit for high-stakes messages: reply to the sender saying "I'm looping in [name] by forwarding this β€” is that okay?" That turns an invisible action into a visible one. It costs ten seconds and eliminates the accidental-discovery scenario entirely. For routine work emails, that's overkill. For anything marked private, it's the difference between a boring afternoon and a difficult conversation.

For organizations handling regulated data, forwarding controls live in the security stack, not the client: Microsoft Purview's data loss prevention policies can block or flag forwards of labeled content, Google Workspace's DLP does similar, and both notify the admin, not the original sender. The admin disclosure path is the only reliable "someone will know" mechanism in the whole ecosystem β€” and it's the one most employees don't think about.

If you're forwarding in a regulated context (health, legal, finance), confirm your employer's data-handling policy before sending. This article is general information about how email forwarding works, not legal or compliance advice, and policies vary by jurisdiction and organization. For questions about your specific obligations, consult a qualified professional in your jurisdiction or your organization's compliance office. If a message involves immediate risk to a person β€” threats, self-harm, or a safety emergency β€” contact local emergency or crisis services rather than relying on email forwarding as a disclosure path.

FAQ

Does Gmail notify the sender when I forward an email?

No. Gmail sends no notification to the original sender when you forward a message, and its forwarding settings only email the account holder when auto-forwarding is configured. Gmail's own help documentation on forwarding describes recipient-side setup only. What can leak: if the forwarded message contains a tracking pixel that loads at the new recipient, the original sender's tracking dashboard may log an additional open from a new location.

What happens to a read receipt request when I forward the email?

The request doesn't travel with the forward in most clients, and even when it does, the receipt goes to the new recipient's response path, not the original sender's inbox. Outlook on Exchange can occasionally show the original receipt request in the forwarded copy, but the resulting acknowledgment goes to the forwarder. Practically, forwarding cancels the original sender's visibility into read status.

Can someone tell an email was forwarded without being told?

Yes, if headers survive. A forwarded .eml or .msg attachment contains the full "Received:" chain, the original sender's IP, timestamps, and recipient list. A recipient who opens "Show original" in Gmail or "View message details" in Outlook can trace the message path back to the original domain. A plain-text paste strips all of it, and header-rewriting relays replace the original "From" domain with the relay's.

Is it safe to forward a tracked sales email to a colleague?

Often not, if the sender uses a pixel tracker. Most HTML forwards preserve the 1Γ—1 tracking image, so the sender's dashboard may register an extra open from your colleague's location. The sender won't know it was a forward, but they may infer a second reader from two opens in different cities. Outlook's "Forward as Attachment" and corporate pixel-blocking settings both cut the tracker off β€” behavior varies by tenant, so confirm with IT.

Why did the original sender see my Bcc'd recipient's name?

Because Bcc only hides the address in the original send. If a Bcc'd recipient later uses Reply All, their address appears in the To or Cc field of the new message, visible to everyone on the thread β€” including the original sender. The same pattern shows up when a forwarded message gets pulled into a reply-all chain. The sender learns from the reply, not from the forward.

Do Microsoft 365 or Google Workspace notify the sender about forwarded mail?

Neither notifies the original sender. Both can block or flag forwards of labeled or sensitive content through their compliance tools (Purview in Microsoft 365, data loss prevention in Workspace), but those alerts go to administrators, not to the person who wrote the email. If your organization uses such policies, forwarding labeled content may generate an internal review rather than a sender notification.

Can I forward an email and keep the sender from seeing the "Fwd:" tag?

You can edit the subject to remove the "Fwd:" prefix in most clients, but that's cosmetic. The header block still records the original message if you paste or attach it, and the body quote bar remains unless you retype the content. Some clients offer "Forward as attachment," which hides the tag but produces a downloadable file. None of these affect whether the original sender is notified, because none of them trigger a notification.

What's the difference between forwarding and redirecting an email?

Forwarding wraps the message in a new envelope from you, with your "From" address and a "Fwd:" subject line. Redirecting (sometimes called "Resend" or "Bounce") keeps the original "From" and headers intact and sends it forward as if the original server did it β€” available in some clients and mail servers, not in Gmail's web interface. Redirecting preserves more provenance but can fail DMARC checks and land in spam at the destination. Neither notifies the original sender.