In a mailbox's message list, before the subject, the user sees the sender name. It is the element that decides whether a message gets opened, ignored or reported as spam. At the same time, the address behind that name is what DMARC and domain reputation rely on. Choosing the sender identity well is both a communication decision and a technical one, and changing it lightly has consequences on both fronts.
The parts of the From header
The From header has two components:
From: Digital Workshop <news@news.example.com>
- the display name, «Digital Workshop», which is what most clients show;
- the address,
news@news.example.com, whose domain is the one DMARC checks.
The display name is not authenticated: anyone can write any name. That is why filters are suspicious of messages where the name imitates a well-known brand while the address belongs to a different domain, a typical phishing technique. A name consistent with the address's domain is a signal of trustworthiness.
Choosing the display name
The name should make it immediately clear who is writing. The most common choices are:
| Format | Example | When it works |
|---|---|---|
| brand only | «Digital Workshop» | newsletters and official communications |
| person and brand | «Laura at Digital Workshop» | editorial content, more personal relationships |
| brand and service | «Digital Workshop Invoices» | specific transactional flows |
| person only | «Laura Bianchi» | only if the audience already knows that person |
The mistake to avoid is changing it often. Users learn to recognise a name; filters attach a history to that identity. A different name for every campaign makes both more wary.
The From address
The address must belong to a domain you control, authenticated with aligned SPF and DKIM. Some practical pointers:
- no free mailbox provider addresses as the sender of bulk mail: their domains publish strict DMARC policies, and messages sent from external platforms get rejected;
- one subdomain per flow, if you need to separate reputation: for example one for newsletters and one for account notifications;
- the local part of the address, before the @, matters less, but it should make sense:
news@,orders@,support@; - stability: the same address over time for the same kind of message.
The trouble with «no-reply»
Many sends use addresses like noreply@ or do-not-reply@. It is a widespread choice and a wrong one, for several reasons:
- it tells the user the conversation is one-way;
- people reply anyway, and their questions, unsubscribe requests and error reports get lost;
- a user who can't get heard is more likely to end up using the spam button;
- replies are a positive engagement signal: preventing them means giving that up.
If replies can't be handled by a person, it is better to route them to a mailbox that sorts them automatically: unsubscribe requests get processed, everything else is forwarded to support.
Reply-To: when and how to use it
The Reply-To header states which address replies should go to, if different from From. It is useful in specific cases:
- when From is a sending-only address but replies need to reach support;
- in editorial communications signed by a person, so replies reach them directly;
- in website contact forms, where the message leaves from your domain but the reply goes to the person who wrote in.
The last case is important and often done wrong. A contact form must never put the visitor's address in From: your server would be sending mail on behalf of someone else's domain, and DMARC would get it rejected. From stays an address on your domain, and the visitor's address goes in Reply-To.
Reply-To should stay on the same domain or on clearly related domains. A Reply-To pointing to an unrelated domain, with no connection to From, is a frequent feature of scams and is noticed by filters.
Changing identity without damage
Sometimes a change is unavoidable: a new brand, a merger, a new domain. In those cases it pays to:
- announce the change in advance in messages sent with the current identity;
- keep, for a while, a display name that recalls the old one;
- treat the new domain as one to warm up, with increasing volumes;
- verify authentication and alignment before the first send.
In short
- The display name decides the open; the address's domain is what DMARC checks.
- Name and address should remain consistent and stable over time.
- No-reply addresses lose useful replies and increase complaints.
- Reply-To routes replies, and in contact forms it carries the visitor's address.
- A change of identity should be announced and treated as a new warm-up.
