What is an email redirect?

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

An email redirect is when a mail server automatically sends an incoming message to a different address without changing who the original sender appears to be. The "From" line stays the same, the message just ends up somewhere else.

This is different from forwarding. When you forward an email, you're the sender of the new message (it shows "Forwarded by you"). With a redirect, the original sender's address stays intact, which sounds convenient but creates authentication headaches.

Here's what happens: the original sender authenticated their message with SPF, DKIM, and DMARC for delivery to address A. The message arrives at address A's server, which then redirects it to address B. But address B's server sees a message claiming to come from the original sender, arriving from address A's server. The authentication doesn't match up anymore. DMARC fails.

You'll see this break most often with mailing lists and university email systems. A message gets sent to listserv@university.edu, the list redistributes it to 500 members, and suddenly half the copies land in spam because DMARC alignment failed. The receiving servers think someone's spoofing the original sender. This DMARC-breaking problem was so common that a new standard called ARC (Authenticated Received Chain) was created to fix it. ARC acts like a chain of custody receipt. Each server that handles the message adds its own signature saying "yes, this was authenticated when it arrived here, and here's proof." The final receiving server can check the ARC chain and see that the message was legitimate at the start, even if the redirect broke the original authentication.

Most major mailbox providers (Gmail, Yahoo, Outlook) now support ARC, but not all mail servers have implemented it yet. If you run a mailing list or an email forwarding service, enabling ARC on your mail server helps keep legitimate redirected mail out of spam. If you're a sender whose messages are getting redistributed through mailing lists, there's not much you can do except hope the list operator has ARC configured.

If you're troubleshooting why messages sent through a mailing list are landing in spam, check your DMARC reports for alignment failures. If you see failures coming from known mailing list servers, that's the redirect problem. The fix is on the list operator's side, not yours.

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

Paste your setup details above and let's figure out if redirects are breaking your authentication

I read this on the Email Almanac about email redirects: "An email redirect is when a mail server automatically sends an incoming message to a different address without changing who the original sender appears to be. This creates authentication headaches because the original sender authenticated for delivery to address A, but the message ends up at address B through a different server. DMARC fails." Help me understand how this applies to MY specific situation: --- Business context: - Email platform/ESP: [e.g. Mailchimp, university email system, mailing list software] - Are you running a mailing list or forwarding service?: yes/no, which software? - Are your messages being redistributed through lists?: yes/no, which lists? - What problem are you seeing?: [messages landing in spam after redirect, DMARC failures in reports, legitimate forwards getting blocked] --- Based on your answers, I'll provide: 1. Whether this redirect/ARC issue is causing your problem 2. How to check your DMARC reports for redirect-related failures 3. If you run a list: how to enable ARC on your mail server 4. If you're a sender: what you can (and can't) control when your messages get redistributed

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