Forwarding that reports success and forwarding that actually delivers to the inbox are two different things. A reader who runs a small design studio wrote in with a puzzle: mail sent to her GoDaddy domain address showed as forwarded in the Email & Office Dashboard, the log said delivered, and every message still turned up in her Gmail spam folder. Nothing was broken in the obvious sense. The forwarder did its job. Gmail simply did not trust what arrived. This is the most common forwarding failure I see, and it has almost nothing to do with GoDaddy’s forwarding service itself.
The setup: Workspace Email, a dead mailbox, and a Gmail destination
Her domain was registered at GoDaddy and had been on Workspace Email for years, with a single mailbox for hello@ plus two aliases. When GoDaddy retired Workspace Email, she moved her actual correspondence to Gmail and set up GoDaddy email forwarding so the old address would keep working. That is a reasonable path, and it is the one most people take after a platform migration.
The mechanics looked clean. GoDaddy no longer bundles free email forwarding with domains the way it once did, so she was working against forwarding credits tied to her account. Email Forwarding is independent of other GoDaddy email products, which means the forwarder is its own service and does not require a mailbox behind it. Users can forward mail without a GoDaddy email product at all, and that was her situation: a forwarder at the domain, a Gmail inbox at the destination, nothing in between.
For the first week it worked perfectly. Then a client replied to an old thread and the message landed in spam. Over the following days, roughly a third of forwarded mail went to spam while the rest arrived normally. The pattern was not random. Messages from senders with strict DMARC policies failed. Messages from small domains without DMARC passed.
Why “forwarded successfully” and “delivered to inbox” are separate events
The dashboard was not lying. It reported that the forwarder accepted the message and handed it to the destination server. What it cannot report is how the destination judges the message on arrival. That judgment happens entirely on Gmail’s side, using the headers the forwarder left behind.
The envelope sender rewrite that breaks SPF alignment
Here is the part that trips people up. When GoDaddy’s forwarder relays a message, it typically rewrites the envelope sender to an address on the forwarding domain. The visible From header stays intact, so the message still looks like it came from the original sender. But SPF checks the envelope sender against the sending IP. The forwarder’s IP is authorized by the forwarder’s domain, not by the original sender’s domain.
Gmail evaluates SPF against the domain in the From header for alignment purposes. The forwarder’s IP is not in the original sender’s SPF record, so alignment fails. If the original domain publishes a strict DMARC policy with p=reject or p=quarantine and no relaxed alignment, Gmail has a legitimate reason to distrust the message. The forwarder did everything right and the result still lands in spam. This is not a GoDaddy bug. It is how SPF and DMARC interact with any forwarding path, and it affects every forwarder on the market.
The tell in her case was in the Gmail message details: SPF softfail on the forwarding domain, DKIM absent because the original sender had not signed, and DMARC fail on the From domain. Three signals pointing the same direction, as the AllMail blog notes. Once you see that combination, you know the problem is authentication, not delivery.
Two fixes that actually work, and one that does not
The instinctive fix is to resend the message or ask the sender to whitelist the address. Neither scales. The sender cannot control how your forwarder relays their mail, and you cannot ask every correspondent to adjust their DNS. The workable options are narrower.
- Add the forwarding path to SPF where you control the sending domain. If the mail originates from your own domain and you forward it onward, publish an SPF record that includes the forwarder’s sending infrastructure. This resolves alignment for mail you originate, though it does nothing for mail sent to you by third parties.
- Use a destination that tolerates forwarding. Gmail is strict about DMARC alignment. Some providers and some business tiers apply more lenient scoring to forwarded mail with intact From headers. Testing a second destination is the fastest way to confirm the diagnosis.
- Move to a mailbox product with native forwarding controls. Professional Email is powered by Titan and offers external forwarding on Pro Plus, Premium and Ultra plans. A real mailbox at the domain means the message is delivered locally first, then forwarded under your own domain’s authentication rather than a relay’s.
- Avoid the whitelist reflex. Adding the sender to contacts in Gmail helps with some filters but does not override a DMARC alignment failure. It creates the illusion of a fix and hides the real cause.
She chose a combination: Professional Email on the Pro Plus plan for the primary address, with external forwarding to Gmail retained for archival, plus a corrected SPF record on her own domain for the mail she originates. Spam placement dropped to near zero within 48 hours.
What to check before you blame the forwarder
Before touching DNS, confirm the forwarder is actually the problem. Open a spam-trapped message in Gmail, choose Show original, and read the authentication results. If SPF shows softfail or fail on a domain you do not recognize as the sender’s, the relay is the cause. If SPF passes and DKIM passes, look elsewhere, because the issue is likely content filtering or a reputation problem at the destination.
Dashboard settings, credits, and the catch-all trap
The Email & Office Dashboard is the control surface for forwarding rules, and it is worth confirming the rule itself is correct before chasing authentication. Check that the forwarding destination is verified, that the rule is active, and that forwarding credits are still available on the account. Email Forwarding requires existing forwarding credits, and a rule that silently stops applying because credits ran out will look like a delivery failure when it is really a billing state.
Catch-all addresses deserve a separate warning. A catch-all that forwards every unroutable address to one Gmail inbox is a spam magnet, and the volume alone can push legitimate mail into spam through reputation damage. If you run a catch-all, forward it to a dedicated destination, not your primary inbox. The same applies to distribution groups that fan out to multiple external addresses.
If your domain also runs Microsoft 365, remember that Microsoft 365 restricts automatic external forwarding by default. A rule that works in the GoDaddy dashboard can be blocked at the Microsoft 365 tenant level, and the failure looks identical from the sender’s side. Outlook on the web will show the rule as active while the tenant policy quietly drops the outbound copy.
One more thing worth knowing: GoDaddy updates help pages frequently, and the rules around forwarding credits, plan eligibility, and which products include forwarding have changed more than once. Do not rely on a forum post from two years ago. Check the current help page for your specific product before you conclude the feature is gone.
Start by reading the authentication headers on a trapped message, because that single step separates a relay problem from a rule problem. If SPF alignment is failing, either fix SPF for mail you originate, move to a mailbox product like Professional Email that forwards under your own domain’s authentication, or point the forwarder at a destination that scores forwarded mail more tolerantly. Then verify the rule in the Email & Office Dashboard, confirm your forwarding credits, and retest with a message from a strict-DMARC sender. Forwarding that “worked” is only half the story; delivery to the inbox is the part that counts.