You may have seen a Gmail message with a sender line like "Jane Smith via example.com", or a "mailed-by" or "signed-by" entry in the message details. This is the "via" label. It does not mean the message is dangerous, but it does mean that Gmail found a difference between the address in the From line and the domain that actually handled or signed the message. For people who send email, the label looks unprofessional and is a sign that authentication is not fully set up. This guide explains what the via label means, why Gmail shows it, how to read the details, and how to fix it so that your mail shows only your name.
What does "via" mean in an email?
When Gmail displays a sender as "name via domain", it is telling the reader that the message came through a different domain from the one in the From address. The label appears next to the sender name, and the message details show the related entries: mailed-by and signed-by.
- mailed-by is the domain in the envelope sender, also called the return path or MAIL FROM address. It is used in SPF checks and for bounces.
- signed-by is the domain that signed the message with DKIM, taken from the
d=value in the signature.
When both of these are the same as the From domain, Gmail has no reason to add the label. When one differs, Gmail may show it, because it wants the reader to know that the message did not come purely from the domain it claims to come from.
Common situations that show a via label
- A sending service signs with its own domain. You send from [email protected] through a platform that signs with its own DKIM key and uses its own bounce domain. Gmail shows "via the-platform.example".
- A mailing list or forwarder rewrites the message. A group address or a forwarding service sends on behalf of the original author.
- A shared mailbox or delegated sending. Mail sent on behalf of another address.
- A website form or plugin that sends as your domain from a server that is not set up for it, for example the default mail function of a web host. Our WordPress contact form email guide covers this common case.
- Missing or partial DKIM. If the message is unsigned, or signed by a default key of a service, the signed-by domain will not be yours.
How to see why Gmail shows it
- Open the message in Gmail.
- Click the small arrow next to the recipients to open the message details, and read mailed-by and signed-by.
- Choose the option to show the original message. Gmail shows the authentication results at the top, with PASS or FAIL for SPF, DKIM and DMARC, and the domains involved.
- Compare the domains with the one in your From address.
Reading these results takes a little practice. Our guide to tracing an email through its logs and events explains the other half of the picture from the sending side.
Alignment: the idea behind the label
DMARC uses a rule called alignment. For a message to pass DMARC, at least one of two checks must pass and align with the From domain: SPF with a return path on the same domain, or DKIM with a signing domain on the same domain. Alignment can be strict (the exact same domain) or relaxed (the same organisational domain, so that a subdomain of yours counts). The via label is Gmail's visible signal that the message is not fully aligned with the From domain on one of these paths. Fixing alignment removes the label and also helps DMARC pass, which matters as mailbox providers expect authenticated mail. See how to set up DMARC.
How to remove the via label
The solution is to make your sending domain and your signing domain match your From domain.
- Set up DKIM with your own domain. In your sending service, add your domain, then publish the DKIM records it gives you in your DNS, usually as TXT or CNAME records. After the records are verified, messages are signed with
d=yourdomain.com. The DKIM setup guide covers this. - Use a custom return path. Many services let you choose a bounce domain on your own domain, such as
bounce.yourdomain.com, set with a CNAME. This makes the mailed-by value yours and lets SPF align. - Publish SPF correctly and include every service that sends as your domain. Check that you have a single SPF record. See the SPF record guide.
- Publish a DMARC record, starting with a monitoring policy, and read the reports to find sources that do not align.
- Send from an address on a domain you control, not from a free mailbox address through a third-party service. A message sent as a Gmail address from another server cannot align.
- Retest. Send a message to a Gmail account and check that mailed-by and signed-by show your domain.
Our guide authenticate your sending domain with SPF, DKIM and DMARC puts these steps in a single order. After you change records, give DNS time to update, and use the free SPF, DKIM and DMARC checker to confirm the result.
When the label is expected
Sometimes the label is correct and cannot be removed. If a person sends a message through a mailing list, the list server legitimately sends on behalf of the author, and the label reflects that. If you use a delegate or an assistant to send as you, the same holds. For these cases the label is accurate, not a defect. Your effort belongs on mail you control, such as your newsletters, receipts and application messages.
Does the via label affect deliverability?
We cannot see how any mailbox provider weighs one signal, and none publishes a formula. What we can say is that an unaligned message is weaker evidence that it comes from you. It can make a reader hesitate, particularly with a message about money or passwords, and it often points to a setup in which DMARC fails or only passes by luck. Aligned authentication is the baseline that large mailbox providers expect from senders, and it makes later problems, such as spoofing of your brand, easier to prevent. For the wider picture, see our deliverability overview.
A quick troubleshooting table
| You see | Likely cause | Fix |
|---|---|---|
| signed-by is a service's domain | DKIM is not set up for your domain | Publish the service's DKIM records for your domain |
| mailed-by is a service's domain | Default bounce domain in use | Set a custom return path on your domain |
| No signed-by line | Message is unsigned | Turn on DKIM signing |
| DMARC fails | Neither SPF nor DKIM aligns | Fix one or both, then recheck |
| Via appears only on list mail | A list server relays the message | Expected behaviour |
Send as your own brand, with no "via" Add your domain, publish the records we give you and send with aligned SPF and DKIM.
References and further reading
Frequently asked questions
What does via mean in a Gmail message?
It means the domain that sent or signed the message differs from the domain in the From address. Gmail shows it so the reader knows the message came through another domain.
Is a message with a via label spam?
Not by itself. Mailing lists and services produce it legitimately. For your own mail, though, it shows that authentication is not aligned with your From domain.
What are mailed-by and signed-by?
Mailed-by is the envelope sender or return path domain used by SPF. Signed-by is the domain that applied the DKIM signature. Both appear in the Gmail message details.
How do I remove the via label from my emails?
Authenticate your own domain with DKIM, use a custom return path on your domain, publish a single correct SPF record, add DMARC and send from an address on your domain.
Does the via label affect deliverability?
Providers do not publish how they weigh it. It indicates weaker alignment, which can affect DMARC results and reader trust, so fixing it is a sound baseline.