Domain Email Forwarding Not Working (Forwarding to Gmail)
Domain email forwarding not working — mail sent to [email protected] should land in your Gmail or Outlook inbox, but some or all of it never arrives, or senders get a bounce back.
Common signs of this issue
- Domain email forwarding not working: messages sent to your business address never show up in the Gmail, Outlook, or other inbox it is supposed to forward to.
- Some forwarded mail arrives but other messages vanish — often invoices, newsletters, or mail from big companies with strict email security.
- Senders get a bounce mentioning SPF, DMARC, "unauthenticated email", or an error like 550-5.7.26 from Gmail.
- Forwarding worked for months or years and stopped without anyone touching it.
- It broke right after you moved your website, changed hosts, or switched where your domain's DNS is managed.
- Your inbox fills with spam sent to addresses that never existed, and real messages seem to go missing alongside it.
- Replies you send from Gmail show your personal address instead of your business one, or land in the recipient's spam.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Send a test from a different account — a friend's email or a second personal address — to your business address. Do not test from the Gmail account the mail forwards to; Gmail often hides messages that loop back to the same mailbox, which looks like a failure when it is not.
- Find out where your forwarding is actually set up: at your domain registrar (many offer free forwarding), at your web host (cPanel's Forwarders screen), or at a service like Cloudflare Email Routing. Write it down. Most forwarding problems start with two places each thinking they are in charge.
- Look up your domain's MX records with a free MX lookup tool (search "MX lookup"). Mail goes only where the MX records point. If forwarding is configured at your registrar but the MX points to your web host, or the other way round, the forwarding rule is never used.
- If a sender received a bounce, ask them to send you the full bounce text. Words like SPF, DMARC, "not authenticated", or "policy" point to the forwarding-and-authentication problem described below. "User unknown" or "no such mailbox" points to a typo or a missing forwarder.
- Check the Spam and All Mail folders in the destination inbox, and search for the sender's address. Forwarded mail is judged more harshly than direct mail and is often junked rather than rejected.
- Open the forwarding settings and confirm the destination address is spelled correctly and still exists. Old forwards to a former employee's or a closed personal account fail quietly.
- Check whether you have a catch-all (forward everything@yourdomain) enabled. If so, count how much of what arrives is spam. A catch-all forwarding large volumes of junk to Gmail can get the forwarding server's mail throttled or rejected — taking real mail down with it.
- If you use Gmail's older "Check mail from other accounts" (POP fetch) feature instead of true forwarding, check your Gmail settings for any notice about it. Google has been phasing that feature out, and accounts relying on it may stop collecting mail.
What this usually means
Forwarding breaks email authentication by design. When a customer's server sends mail to [email protected] and your forwarding service passes it on to Gmail, Gmail sees the message arriving from your forwarder's server — not from the customer's. The customer's SPF record does not list your forwarder, so SPF fails. If the customer's domain has a strict DMARC policy (p=reject or p=quarantine) and their DKIM signature did not survive the trip, Gmail or Outlook does exactly what that policy says: rejects or junks it. That is why forwarding tends to lose mail from banks, big retailers, and other security-conscious senders first.
Good forwarding services work around this with SRS (Sender Rewriting Scheme), which rewrites the envelope sender so SPF checks against the forwarder instead, and by leaving the original DKIM signature intact. Many free registrar forwarders and some older hosting setups do not do SRS, or do not do it reliably. The other common causes are simpler: MX records pointing somewhere other than where forwarding is configured (very common after a host move), a forward to an address that no longer exists, or a catch-all that turned the forwarder into a spam firehose and damaged its reputation with Gmail.
The honest long-term answer for a business address that matters is often to stop forwarding and use a real mailbox. A proper business email account receives mail directly, so there is no hop to break authentication, and you can send replies as your business address with correct SPF, DKIM, and DMARC. Forwarding is fine for a secondary address or a low-stakes domain, but it is a fragile foundation for the address on your invoices and your website.
What not to do
- Don't set up forwarding in two places at once (registrar and host) and hope one of them works. Pick one, point the MX records there, and remove the other.
- Don't change your MX records without writing down the old values first. If you guess wrong, all incoming mail can stop, not just the forwarded copies.
- Don't leave a catch-all forwarding to Gmail indefinitely. It invites spam, and the spam can get your forwarder rate-limited or blocked.
- Don't weaken or remove your own domain's SPF or DMARC records to try to fix forwarding. Your records affect mail you send, not mail others send to you.
- Don't reply from Gmail using your business address unless Gmail's Send mail as feature is set up to send through a proper SMTP server — otherwise replies fail authentication and land in spam.
- Don't assume a test from your own Gmail account proves anything. Test from an outside address.
When to get help
It is time to bring in help when you cannot tell where your mail is actually being delivered, when the MX records point somewhere nobody recognizes, or when mail from specific customers keeps disappearing and the bounces mention DMARC. Missing email is a quiet way to lose business: quote requests, invoices, and password resets simply never arrive, and nobody tells you. Someone experienced will read the MX and DNS records, trace where each message stops, and decide whether the right fix is a forwarding service that supports SRS, a change of MX, or moving you onto a proper mailbox — without cutting off the mail that is working today. If you are also worried about 550 bounces or business email not working more broadly, it usually makes sense to sort it all out in one pass.
Glenn, who runs WebsiteSelfHelp, untangles broken domain forwarding and gets small-business mail landing reliably again. Tell him what is going missing — a bounce message or two helps — and you will get a plain answer on the cause and what it takes to fix. No passwords are needed to start.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
Why is my domain email forwarding not working with Gmail?
Usually because forwarding makes the message fail SPF, and if the original sender has a strict DMARC policy, Gmail rejects or junks it. Other common causes are MX records pointing somewhere other than your forwarding service, or a catch-all forwarding so much spam that Gmail throttles the forwarder.
What does 550-5.7.26 unauthenticated email mean on forwarded mail?
It means Gmail checked the message against the sender's DMARC policy and it failed, so Gmail refused it. With forwarding, that failure is often caused by the forwarding hop itself, not by the original sender doing anything wrong.
What is SRS in email forwarding?
Sender Rewriting Scheme. It rewrites the hidden return address on forwarded mail so SPF is checked against the forwarding server rather than the original sender. Forwarding services that support SRS lose far less mail.
Is registrar email forwarding good enough for a business?
For a secondary or low-traffic address, often yes. For your main business address, it is fragile: you cannot send properly as that address, and forwarded mail is judged more harshly. A real mailbox is more dependable.
Why did forwarding stop after I moved my website?
Moving hosts often changes the MX records or the DNS provider. If forwarding lived at the old host or registrar and the MX now points elsewhere, the old forwarding rules are simply never used.
Can I fix email forwarding myself?
Often. Confirm where forwarding is configured, check that the MX records point there, fix the destination address, and turn off the catch-all. If mail from specific senders still fails with DMARC errors, you need a forwarder with SRS or a real mailbox.
Should I use a catch-all email address?
Generally no. A catch-all accepts mail to any made-up address at your domain, which mostly means spam. Create the specific addresses you need instead.