Your domain address receives mail, the forwarder is set, and Gmail stays empty. If you're searching "email forwarding not working," start with the reassuring part: the forwarder itself is rarely broken. Far more often the message leaves your server and the destination rejects it, buries it in Spam, or hides it on purpose.
Quick Answer: As of September 2026, four causes explain most failed forwarders: testing from the same Gmail account you forward to, SPF failing because your server isn't authorised to send for the original sender's domain, cPanel Email Routing set to Remote so your server never sees the mail, and filters or loops dropping it. Trace the forwarder, read the delivery log, then fix whichever cause the log names.
Last verified: September 2026, against cPanel & WHM 138 (RELEASE) and 134 (LTS) documentation and Gmail's 2026 POP-fetch changes.
Our team resolves 20-30 client issues every day, and this guide is built from the forwarding cases in that queue. It's written so you can fix yours yourself, in order, without guessing. Start at Step 1 even if it feels too simple. It catches more people than you'd expect.
Why Is Email Forwarding Not Working? The Causes, Ranked
A forwarder is a relay. Your server accepts a message for [email protected], then sends a fresh copy on to the destination. Every failure happens at one of three points: the mail never reaches your server, your server drops or loops it, or the receiving server refuses it.
Our team calls this the Three-Hop Check: did it arrive, did it leave, was it accepted? Answer those three in order and you stop guessing.
These are the causes in roughly the order they turn up in real tickets:
| Rank | Cause | Tell-tale sign | Where to look | |---|---|---|---| | 1 | Testing from the destination Gmail account | Message sits in Sent, never Inbox | Send from a different account | | 2 | SPF/DMARC failure at the destination | 550-5.7.26 bounce, or mail in Spam | Delivery log, bounce text | | 3 | Email Routing or MX pointing elsewhere | Nothing in your server's log at all | cPanel Email Routing, MX lookup | | 4 | Typo or forwarder on the wrong domain | Trace shows a red error icon | cPanel Forwarders, Trace | | 5 | Spam filter or discard rule | Log shows accepted, then dropped | Email Filters, SpamAssassin | | 6 | Forwarding loop | "suspected mail loop" bounce | Delivery log | | 7 | Rate limits or a full mailbox | 421-4.7.28 deferral or quota bounce | Delivery log |
Cause 2 is the one that catches careful people. SPF, defined in RFC 7208, the Sender Policy Framework specification, checks whether the sending IP may send mail for the envelope sender's domain. When your server forwards a message from bank.com to Gmail, your IP isn't in bank.com's SPF record, so SPF fails even though nobody did anything wrong. Add a strict DMARC policy and a broken DKIM signature, and Gmail returns a 550-5.7.26 rejection.
How to Fix a Broken Email Forwarder, Step by Step
Work through these five steps in order. Each one either fixes the problem or rules out a cause, so by the end you'll know exactly where the mail is stopping.
Step 1: Why does my test email never show up in Gmail?
Because Gmail hides it. Send a test from [email protected] to [email protected], have that address forward back to [email protected], and Gmail sees a message it already holds (same Message-ID). It files the copy under Sent only. Your forwarder worked; Gmail just didn't show you.
Test from a different account instead: a colleague's address, an Outlook.com account, anything that isn't the destination. If that test arrives, you're finished. If it doesn't, carry on.
Step 2: Trace the forwarder in cPanel
A surprising share of "cPanel email forwarder not working" tickets end at a typo. Open cPanel » Email » Forwarders, find the address, and click Trace. According to cPanel's official Forwarders documentation, a red exclamation icon means messages will hit an error, while a green globe means they're leaving for another server as intended.
While you're on that screen, check three things:
- The forwarder sits on the right domain (each addon domain has its own list).
- The destination is spelled correctly, with no trailing space.
- Advanced Options isn't set to Discard.
cPanel can't edit an existing forwarder, so delete and recreate it if anything is off.
Step 3: Make sure the mail reaches your server at all
If the delivery log shows nothing for the address, the mail isn't landing on this server. Open cPanel » Email » Email Routing and confirm it reads Local Mail Exchanger (or Automatically Detect, with MX pointing here). Set to Remote, your server hands the mail off and never runs the forwarder.
Across the 4,000+ sites Hostaccent has migrated since 2016, this is the mail step people most often get wrong: the site moves, MX records change, and Email Routing keeps the old setting. Run dig MX yourdomain.com +short as well, and confirm the answer points at your hosting server rather than a previous provider.
Step 4: Stop SPF failures with SRS
This is the server-side fix behind most "email forwarding to Gmail not working" cases. The Sender Rewriting Scheme (SRS) rewrites the envelope sender of forwarded mail to your own domain, so Gmail checks SPF against a domain that actually authorises your server.
On a cPanel server where you have root:
- Open WHM » Service Configuration » Exim Configuration Manager » Basic Editor.
- Set Enable Sender Rewriting Scheme (SRS) Support to On.
- Save. WHM rebuilds the Exim configuration and restarts the service.
On shared hosting you can't flip this yourself, so ask your host whether SRS is enabled. Also make sure your own domain publishes valid SPF and DKIM records; our guide to WordPress emails going to spam walks through both.
Live mailbox and no time to experiment? Our engineers fix broken forwarders for a small one-time fee, and you see the exact quote before anyone touches your server. Hosted with Hostaccent? Then a forwarding problem is simply part of support, free. Have an engineer fix it
Step 5: Clear filters, loops and limits
Three quieter causes live here.
Filters and spam rules. Check Email Filters and Global Email Filters in cPanel for any rule that discards or redirects mail. On servers you control, Exim Configuration Manager also has an option that stops SpamAssassin-flagged mail from being forwarded to external recipients. It protects your IP's reputation, but it can quietly swallow borderline messages.
A forwarder loop error. If address A forwards to B and B forwards back to A, Exim eventually bounces the message with "Too many Received headers - suspected mail loop". Break one side of the chain.
Limits. Forwarded mail can count toward your account's hourly sending cap, and a busy address hits it fast (see our note on shared hosting resource limits). Gmail also throttles high-volume forwarders with a temporary 421-4.7.28 deferral, and a full destination mailbox bounces everything.
Still seeing the mail error?
Share the bounce message, affected domain, and sending route. We can investigate DNS, authentication, reputation, and server configuration across providers.
How to Confirm Forwarded Mail Is Arriving Again
Send one test from an outside account, then read the delivery log instead of staring at your inbox. A log entry appears within about 60 seconds and states exactly what happened to the message, while an inbox can leave you guessing for hours about whether mail was delayed, filtered or rejected.
- Shared hosting: open cPanel » Email » Track Delivery, search the address, and look for a success line to the destination.
- Root access: run
exigrep '[email protected]' /var/log/exim_mainlog. A healthy forward shows the incoming<=line, a=>delivery to the Gmail address, thenCompleted. On Plesk, the equivalent log is/var/log/maillog.
Next, open the delivered message in Gmail, choose Show original, and read the results. You want SPF and DKIM both showing PASS, and a Return-Path starting with SRS0= confirms rewriting is on. If forwarded mail not arriving is still your problem, the log line names the reason: 5.7.26 means authentication, 4.7.28 means rate, and a quota message means the destination is full.
Pro Tip: A 4xx code is a deferral, not a failure. Exim's default retry rules keep trying for up to 4 days, so a 421 from Gmail usually clears on its own. Only 5xx codes mean the message is gone for good, and those are the ones worth acting on straight away.
Keep Your Forwarders From Breaking Again
Forwarding breaks again whenever something upstream changes: a DNS move, a new filter, a sender tightening DMARC. A few habits catch those changes before your clients notice.
There's also a reason forwarding matters more this year. Through 2026, Google has been retiring Gmail's POP-based "Check mail from other accounts" feature and Gmailify, so the old workaround of letting Gmail fetch domain mail is disappearing. More people are switching to forwarders in 2026, and more forwarders are meeting strict DMARC for the first time.
The habits we'd keep:
- Publish your own DMARC record, starting at
p=none, so aggregate reports show you failures early. Cloudflare's explanation of how DMARC records work covers the syntax. - Add ARC signing where your mail server supports it. RFC 8617, the ARC specification, lets a forwarder vouch for the authentication a message had before it was forwarded.
- Re-check Email Routing and MX after every migration.
- Watch memory on a VPS. When the kernel kills SpamAssassin's spamd under memory pressure, mail backs up in the queue; our guide to a VPS running out of RAM shows how to spot it.
Pro Tip: Never let anything modify forwarded mail. SRS makes SPF pass, but that pass won't align with the visible From address, so DMARC leans entirely on the original DKIM signature. One added footer or "[SPAM]" subject tag breaks it.
According to Hostaccent's support-queue data (September 2026), Linux server issues make up about 25% of monthly tickets, and in our experience forwarding faults almost always land there: server configuration, not a broken mailbox. That's why we read logs first, the same way we approach diagnosing a slow WordPress site.
Your Next Step: Mail That Arrives Without Babysitting
Fixed it? Keep one habit: after any DNS or server change, send a test from an outside account and read the log. That 30-second check catches email forwarding not working before a customer does. On a well-managed host, SRS, routing and filter hygiene are support's job, not yours. If you'd like that, start on the Economy plan: Economy, $1.99/mo, same price at renewal, from a UK-registered host (hosting since 2016, UK-incorporated 2018) with 24/7 human support and a 30-day money-back guarantee. It's sized for one site, so if you run several domains, Standard ($4.58/mo) fits better.
Still stuck? Open a ticket with our engineers and Hostaccent will fix the forwarder for a small one-time fee, with the exact quote in front of you before work starts.
Frequently Asked Questions
Why is email forwarding not working even though the forwarder looks right?
Usually because the forwarder did its job and the destination refused or hid the result. Gmail rejects forwarded mail that fails SPF and DMARC, drops copies of messages you sent yourself, and throttles busy forwarders. Trace the forwarder in cPanel first, then read Track Delivery or the Exim log. The log line shows whether the message left your server and which code came back, which turns guessing into a quick fix.
Why do my forwarded emails land in Gmail's Spam folder?
Forwarded mail arrives from your server's IP, not the original sender's, so SPF fails or looks suspicious to Gmail. Gmail also weighs your server's reputation, which suffers when it forwards spam it received. Enable SRS, make sure your domain publishes SPF and DKIM, and create a Gmail filter for the forwarded address with "Never send it to Spam" ticked. Marking a few messages as not spam also helps.
Does SRS fix DMARC failures on forwarded mail?
Only partly. SRS makes SPF pass by rewriting the envelope sender to your domain, but DMARC needs the passing domain to match the visible From address, and after SRS it doesn't. DMARC for forwarded mail therefore depends on the original DKIM signature surviving unchanged. Keep forwarded messages unmodified, and where your server supports it, add ARC signing so Gmail can see the message passed authentication before you forwarded it.
Is forwarding or IMAP better for getting domain mail into Gmail?
IMAP is more reliable, because nothing gets re-sent and no authentication breaks along the way. You can add your domain mailbox to the Gmail mobile app over IMAP, or use any desktop mail client. Gmail's web interface is losing its POP-based "Check mail from other accounts" feature during 2026, though, so forwarding stays the simplest way to see domain mail in Gmail on a desktop browser. Enable SRS if you forward.
How long does a new forwarder take to start working?
A cPanel forwarder works as soon as you save it, usually within a minute, because Exim reads the forwarder list on each delivery. If mail still isn't forwarding, the delay is somewhere else. MX records you just changed can take as long as their TTL, often 1 to 24 hours, to update across resolvers. Check the MX answer with dig, then send a fresh test from an outside account once it points at your server.
Discussion
Have a question or tip about this topic? Share it below — your comment will appear after review.