Troubleshooting
WordPress Email Forwarding Not Working: Causes and How to Fix It

Short answer
Email forwarding on a WordPress domain usually fails because the MX records point to a different mail service than the one holding your forwarders, or because Gmail and Outlook reject forwarded mail that fails SPF or DMARC. WordPress itself does not forward email, so fix it in DNS or your host's email settings.
Key takeaways
- WordPress does not forward email; your host, registrar or DNS provider does.
- Check that MX records point to the service where your forwarders live.
- Forwarded mail can fail SPF and DMARC, so use a forwarder that supports SRS.
- Set cPanel Email Routing to Remote when your mail is hosted elsewhere.
- Test with an outside address and read bounce messages for the exact reason.
Why is WordPress email forwarding not working?
Email forwarding usually fails because the domain's MX records point to the wrong server, the receiving inbox rejects forwarded mail for failing SPF or DMARC, or the forwarder was set up in the wrong place.
The first thing to know is that WordPress does not forward email. Forwarding is handled by your host, your domain registrar, or a service such as Cloudflare Email Routing. WordPress only sends emails, such as form notifications and password resets.
So when someone says WordPress email forwarding is broken, the problem is almost always in DNS or the mail server, not in a WordPress setting. That is good news, because the fixes are usually quick once you find the right place.
| Symptom | Most likely cause | Where to fix |
|---|---|---|
| No forwarded mail at all | MX records point elsewhere | DNS settings |
| Forwards stopped after a move | MX or DNS changed during migration | DNS and host panel |
| Only some emails arrive | Spam filter or DMARC rejection at Gmail or Outlook | SPF, DKIM, DMARC, SRS |
| Website form emails missing | Local delivery on the web server | Email routing setting |
| Bounce messages | Wrong destination or forwarding loop | Forwarder settings |
Where is email forwarding actually set up?
Forwarding is set up wherever your domain's mail is received, which is the service your MX records point to, such as cPanel, your registrar, Cloudflare, Google Workspace or Microsoft 365.
Find out where your mail goes before changing anything. Look up your domain's MX records with a DNS lookup tool or your DNS provider's dashboard.
- MX points to your web host: set up forwarders in the host's panel, such as cPanel Forwarders.
- MX points to your registrar: use the registrar's email forwarding page.
- MX points to Cloudflare: use Cloudflare Email Routing.
- MX points to Google or Microsoft: use routing or forwarding rules inside that service.
A forwarder created at your host does nothing if your MX records point to Cloudflare or your registrar. This mismatch is the single most common reason forwarding seems to do nothing.
Our guide to WordPress DNS settings explains MX records and the other records your domain needs.
How do you check your MX records?
Open your DNS provider's dashboard or a DNS lookup tool, look up the MX records for your domain, and confirm they point to the service where your forwarders live.
If the records point somewhere unexpected, someone changed them, often during a hosting move or when nameservers switched to Cloudflare.
Fix the records to match your forwarding provider's instructions. Each provider gives the exact MX hostnames and priorities to use.
DNS changes can take time to spread. Our guide on how long DNS propagation takes explains what to expect.
Did forwarding break after moving hosts or DNS?
Yes, migrations are a top cause, because moving nameservers or hosting often replaces MX records or leaves forwarders behind on the old server.
When you move a site, the new host may create default MX records pointing to its own mail server. Your old forwarders, which lived at the previous host, no longer receive anything.
After any migration, recreate forwarders at the new host or point MX records back to your chosen mail service. Then send a test email from an outside address.
Switching nameservers to Cloudflare has the same effect. Cloudflare copies most records during setup, but always check that the MX records came across correctly.
Why does Gmail or Outlook reject forwarded email?
Forwarded mail can fail SPF and DMARC checks because the forwarding server is not authorized to send for the original sender's domain, so big inbox providers may reject or spam it.
Here is what happens. Someone at example.com emails you.
Your server forwards it to Gmail. Gmail sees mail claiming to be from example.com arriving from your server, which example.com never authorized.
Google's email sender guidelines explain the authentication checks Gmail applies. Strict DMARC policies on the sender's domain make rejection more likely.
The fix is SRS, the Sender Rewriting Scheme. It rewrites the envelope sender so SPF checks pass on your domain. Many hosts and Cloudflare Email Routing apply SRS automatically, but some older mail setups do not.
If your host does not support SRS, consider using a mailbox instead of a forwarder, or a forwarding service that does.
Are your own domain's SPF, DKIM and DMARC records correct?
Missing or wrong SPF, DKIM and DMARC records on your domain make forwarded and website emails look suspicious, so they land in spam or get rejected.
Your SPF record should include every service that sends mail for your domain, including your host, your forwarding service and any SMTP provider your WordPress site uses.
Only one SPF record is allowed per domain. Two separate SPF records break SPF completely, which is a common mistake after adding a new service.
DMARC.org has a clear overview of how SPF, DKIM and DMARC work together. Our step-by-step guide on setting up SPF, DKIM and DMARC for WordPress email shows how to add each record.
Why do website form emails not reach a forwarded address?
When the website and the email domain share a server, WordPress emails may be delivered locally on that server and never reach the real inbox if your mail actually lives elsewhere.
This catches many cPanel users. Your site sends a form notification to info@yourdomain. The server thinks it handles mail for that domain, so it delivers the message to a local mailbox nobody reads.
In cPanel, open Email Routing and set it to Remote Mail Exchanger when your mail is hosted with Google, Microsoft or another provider. The cPanel email routing docs explain each option.
Also check the From address on your forms. Forms that send from the visitor's address fail DMARC. Send from an address on your own domain and put the visitor's email in Reply-To.
If form emails are missing entirely, our guide on fixing a contact form not sending email covers the other common causes.
Should WordPress use SMTP instead of PHP mail?
Yes, sending WordPress emails through an authenticated SMTP service improves delivery a lot, because PHP mail from shared servers often fails authentication checks.
By default, WordPress uses the server's mail function. Messages from shared servers often lack proper DKIM signing, so inbox providers treat them with suspicion, and forwarders pass that suspicion along.
An SMTP plugin connects WordPress to a proper mail service, such as your email provider or a transactional service. Messages then carry valid authentication.
Our guide on how to set up SMTP in WordPress walks through the setup.
How do you test email forwarding properly?
Send test emails from an outside account, such as a personal Gmail or Outlook address, to the forwarded address, then check the destination inbox, spam folder and any bounce messages.
Do not test by sending from the destination address to itself. Gmail, for example, hides messages that loop back to the account that sent them, so a working forwarder can look broken.
Read bounce messages closely. They usually state the reason, such as an SPF failure, a blocked sender or an unknown recipient.
Many host panels also keep a delivery report or mail log. In cPanel, Track Delivery shows whether a message was forwarded, rejected or queued.
What else can stop forwarding?
Forwarding loops, full or disabled destination inboxes, spam filters at your host, and typos in the forwarder address can all stop mail silently.
- Loops: forwarding A to B and B back to A creates a loop that mail servers stop.
- Full mailbox: a destination inbox over quota bounces new mail.
- Host spam filter: some hosts drop suspected spam before forwarding it.
- Catch-all conflicts: a catch-all rule may grab mail before your forwarder runs.
- Typos: a single wrong letter in the destination address sends mail nowhere.
If you are setting up domain email for the first time, our guide on setting up email with WordPress hosting covers mailboxes and forwarders from scratch.
Still stuck? Contact your host or forwarding provider with the time of a test email. They can read their mail logs and see exactly what happened to it.
Frequently asked questions
Does WordPress have an email forwarding setting?
No. WordPress only sends emails such as notifications and password resets. Forwarding happens at the mail server for your domain, which may be your host, your registrar, Cloudflare Email Routing or a service like Google Workspace.
Why did my email forwarding stop after changing hosts?
Moving hosts or nameservers often changes your MX records, so mail now goes to a server without your forwarders. Recreate the forwarders at the new provider or set the MX records back to your chosen mail service.
Why are forwarded emails going to spam in Gmail?
Forwarded messages can fail SPF or DMARC because your server is not authorized to send for the original sender's domain. Use a forwarder that supports the Sender Rewriting Scheme and make sure your own domain's authentication records are correct.
Why don't my contact form emails reach my forwarded address?
If the website and email domain share a server, the form email may be delivered to a local mailbox instead of your real inbox. In cPanel, set Email Routing to Remote Mail Exchanger, and send form emails from an address on your own domain.
Is a forwarder or a mailbox better for a business domain?
A mailbox is more reliable because messages are stored and checked on one service without extra hops. Forwarders are fine for low volumes, but strict DMARC policies and spam filters can cause some forwarded mail to go missing.
Sources
- Email Routing cPanel Documentation
- Email sender guidelines Google Gmail Help
- DMARC Overview DMARC.org
- Cloudflare Email Routing Cloudflare Docs
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


