An email message carries several addresses that look similar and do different jobs. The From header names the author and is what the recipient sees. The envelope sender, also called the return-path, tells servers where to send bounces. The Reply-To header tells the recipient's mail client where to send a reply, if that should differ from the From address. Used well, Reply-To lets a no-reply sending address coexist with a monitored inbox, lets a contact form pass the visitor's address back to your staff and lets a platform send on behalf of a customer. Used badly, it sends replies to the wrong place, triggers spoofing suspicion or loses customer messages. This guide explains what the header does, how clients handle it, when to set it, how it interacts with authentication and spam filtering and how to set it in common code.
The three addresses compared
| Address | Set by | Who uses it | Affects |
|---|---|---|---|
| From | Message author or sending system | Recipient sees it; DMARC checks its domain | Identity, trust, DMARC alignment |
| Reply-To | Message author or sending system | Mail client when the user replies | Where replies go |
| Sender | Sending system when it differs from From | Some clients display "on behalf of" | Identity display in some clients |
| Return-Path (MAIL FROM) | Sending server | Receiving server for bounces and SPF | Bounce routing, SPF alignment |
See Return-Path vs From for the envelope address and DMARC alignment for what must match. Reply-To plays no part in DMARC: the policy looks only at the From domain.
When to use Reply-To
- Contact forms. The form on your website should send from an address at your own domain (so that SPF, DKIM and DMARC pass) and set Reply-To to the visitor's email address, so that your staff can answer by pressing Reply. Never set From to the visitor's address: your server is not allowed to send for their domain and the message will fail authentication or be rejected. See WordPress contact form email.
- Notifications from an application. The message comes from
[email protected], but replies should reach[email protected]. Set Reply-To to the support address, or better, make the support address monitored and use it as From. See no-reply addresses. - Platforms that send for customers. A help desk or CRM sends in the name of an agent. From shows the agent's name on the platform's authenticated domain, Reply-To holds the agent's own address.
- Campaigns with a monitored reply inbox. Marketing mail sent via an email platform often uses a dedicated address for replies.
- Role-based routing. An invoice from the finance system can route replies to the accounts team.
How clients treat it
When a user clicks Reply, the client fills the "To" field with the Reply-To address if there is one, otherwise with From. "Reply all" adds the other recipients as well. Most clients do not show the Reply-To address before the reply is opened, so the user may not know where the reply will go. Some clients, in particular on mobile devices, display only the name. This has two consequences. First, a Reply-To that differs from From in a surprising way, for example a free webmail address on a message from a bank-like sender, is a classic phishing pattern and recipients (and filters) have learned to be suspicious. Second, a typo in the Reply-To means lost replies without any bounce reaching you, because the message to the wrong address is a new message from the customer.
Authentication and spam filters
Because Reply-To is not authenticated, anyone can write anything in it. Spam filters therefore treat it as a signal, not as proof. Patterns that raise suspicion include a Reply-To domain that differs from the From domain and looks unrelated, a Reply-To at a free webmail provider on a message that claims to be from a company, a Reply-To that points at a domain recently registered or on a blocklist, and a Reply-To containing multiple addresses on a bulk message. Business use of a different address is common and usually harmless: a Reply-To on the same organisational domain, or on a clearly related brand domain, will not hurt. If your Reply-To domain is different, make sure it is a real domain with working MX records, SPF and DMARC of its own; the guide on MX records helps. Check your own domains with the checker.
Setting Reply-To in code
# Python
msg['Reply-To'] = 'Support <[email protected]>'
// PHPMailer
$mail->addReplyTo('[email protected]', 'Support');
// Nodemailer
await transport.sendMail({ from: '[email protected]', replyTo: '[email protected]', to: '[email protected]', subject: 'Hello', text: 'Hi' });
# Raw header
Reply-To: Support <[email protected]>For a contact form, use the visitor's address but validate it first, strip line breaks (header injection is a known attack) and use a library that encodes headers safely. Setting Reply-To: $_POST["email"] without validation allows an attacker to inject extra headers or to turn your form into a spam relay. See the email validator and PHPMailer guide.
Multiple addresses and names
The header can hold a list of addresses separated by commas, and the reply goes to all of them. This is useful for a team inbox but unusual, and some clients handle it poorly. Prefer a single monitored address, or a group address managed on your side. Include a display name; it helps the user recognise where the reply is going. If the name contains non-ASCII characters, encode it as described in email encoding.
Common mistakes
| Mistake | Result | Fix |
|---|---|---|
| Contact form sets From to the visitor | Authentication fails; message rejected or in spam | From = your domain; Reply-To = visitor |
| Reply-To points at an unmonitored address | Customer replies are lost | Monitor it, or use a real support address |
| Reply-To on a lookalike or free domain | Filter suspicion; phishing impression | Use your own domain |
| No-reply From and no Reply-To | Customers cannot answer | Add Reply-To or use a monitored From |
| Typo in Reply-To | Silent loss | Validate and test |
| Unvalidated user input | Header injection | Validate, strip newlines, use a library |
| Assuming Reply-To affects bounces | Bounces still go to the return-path | Set a custom return-path, see return-path setup |
Reply-To and mailing lists, forwarding and auto-replies
Mailing list software often rewrites or adds Reply-To so that replies go to the list or to the poster. If you subscribe a company address to a list, remember that the list's settings decide where replies go, not your original header. Auto-responders, such as out-of-office messages, should reply to the envelope sender or the Reply-To according to the rules in the standard; badly written auto-responders reply to the wrong address and create loops. See auto-replies and mail loops. When mail is forwarded, the Reply-To normally survives unchanged, so a customer who answers a forwarded message still reaches the address you intended.
Testing
Send a message to test accounts at different providers, press Reply and look at the address that appears. Test with plain Reply and Reply All. Check the raw source of the received message to see that only one Reply-To header is present. If you use a platform, make sure that its setting for the reply address is applied to every stream, including automated mail and transactional mail, not only to campaigns. If the replies are processed by software, for instance a ticket system, test the full loop: send, reply, and see that the ticket updates. See inbound email processing.
Reply-To is a simple tool for a simple purpose: send replies where they will be handled. Keep From authenticated and trustworthy, use Reply-To for the routing, validate any address that comes from outside and test the full conversation.
Send from your own authenticated domain Authenticated From, custom return-path and flexible reply routing on our relay and API.
References and further reading
Frequently asked questions
What is the Reply-To header?
It tells the recipient's mail client where to send a reply, overriding the From address for replies.
Does Reply-To affect DMARC?
No. DMARC checks the domain in the From header only.
Should a contact form set From to the visitor?
No. Use your own domain in From so that authentication passes, and put the visitor's address in Reply-To.
Can a different Reply-To hurt deliverability?
A Reply-To on an unrelated or free-mail domain can raise suspicion. Use your own or a closely related domain.
Does Reply-To change where bounces go?
No. Bounces go to the envelope sender, the return-path.