Why Gmail shows 'via' next to your sender name, and how to make it go away

Gmail shows via when the domain in your From address and the domain that signed the message are not the same. "Acme via sendgrid.net" is Gmail saying, as plainly as it can, that Acme did not sign this — somebody else did on Acme's behalf. Fixing it takes one DKIM key on your own domain, which is the thing most shared-provider setups never publish.

Key takeaways

• via appears when DKIM alignment fails: the signing domain (the d= in the DKIM signature) is not your From domain.
• It is not a spam penalty. It is a trust signal shown to the reader, and readers do read it.
• The fix is DKIM on your own domain. Custom MAIL FROM fixes the SPF half, which DMARC also wants.
• You can check any message in Gmail: open it, choose Show original, and read the DKIM and SPF lines.

What exactly triggers it?

Every message carries two identities that Gmail compares:

• the From header — the address the reader sees;
• the DKIM signing domain — the d= value in the DKIM-Signature header, which is whoever holds the private key that signed the message.

When those two domains match (or the signing domain is the organizational domain of the From), Gmail shows just the sender. When they differ, it shows via followed by the signing domain. A provider that signs everything with its own key — sendgrid.net, mailgun.org, amazonses.com — produces via for every customer that has not published a key of their own.

SPF has a similar comparison with the Return-Path domain, but Gmail's via is driven by DKIM. SPF alignment matters for DMARC, which is the next section.

Does 'via' hurt deliverability?

Not directly. It is displayed, not scored. What it hurts is the reader's confidence — a receipt from "Acme via someone-else.net" looks like something between a forward and a phish — and confidence is what opens, clicks and the absence of spam reports are made of. Spam reports do feed reputation, so via costs deliverability at one remove.

There is a second cost that is direct: a message without aligned DKIM cannot pass DMARC. If your domain publishes DMARC at p=quarantine or p=reject, unaligned mail is not merely labeled; it is quarantined or refused. Many senders discover their via problem on the day they tighten DMARC.

How do I remove it?

Publish a DKIM key for your own domain and sign with it. Concretely, with any provider that supports it:

1. Ask the provider for a DKIM record for your domain. It is a TXT record at selector._domainkey.yourdomain.com containing a public key. The provider keeps the private half and signs your messages with it.
2. Publish the record at your DNS host. Keys are long and arrive split across several TXT strings; that is normal.
3. Wait for the provider to verify it, then send a test to a Gmail address and open Show original. The DKIM line should read PASS with domain yourdomain.com.

On PigeonAtlas this is the domain verification step: adding a domain generates a 2048-bit key pair for it, the page shows the record to publish, and every message from that domain is signed with that key. The domain page ticks the record green when it resolves, and until it does you cannot send from the domain at all — which is the reason nothing from PigeonAtlas ever shows via.

What about custom MAIL FROM?

DKIM alignment removes via. DMARC wants alignment on SPF as well, which means the domain in the Return-Path — where bounces go — should also be yours. Providers call this a custom MAIL FROM or bounce domain: a subdomain such as bounce.mail.yourdomain.com with an MX record pointing back at the provider and an SPF record authorizing it. PigeonAtlas asks for both records at the same time as DKIM, so a verified domain is aligned on both.

How do I check my own mail?

In Gmail, open a message you sent, choose Show original from the menu. The summary at the top has three lines:

• SPF: PASS with IP … and the domain it checked;
• DKIM: PASS with domain … — this domain is what via compares;
• DMARC: PASS or FAIL, with the policy that applied.

If the DKIM domain is not yours, you have found the cause. If there is no DKIM line at all, the message was not signed — worse than via, and the same fix.

Frequently asked questions

Gmail shows 'via' only for some recipients. Why? Only Gmail and a few other providers display it; Outlook and Apple Mail do not. The condition is the same for everyone; the label is a Gmail interface choice.

I published DKIM and still see 'via'. Either the record has not propagated, the selector in the record does not match the selector the provider signs with, or the provider is still signing with its own key because your domain is not marked verified on their side. Show original tells you which domain signed.

Will a subdomain like mail.yourdomain.com still show 'via'? No. Gmail treats a signing domain that is the organizational domain or a subdomain of the From domain as aligned in relaxed mode, which is the default.

Does 'via' appear on forwarded messages? Forwarding rewrites the path and often breaks SPF, but DKIM survives an unmodified forward, so a properly signed message usually does not gain via when forwarded.