<div>
Why not send the email directly from the address in &quot;reply-to&quot;? Anyway you give them a way to contact you...
</div>


Why not send the email directly from the address in "reply-to"? Anyway you give them a way to contact you...

<div>
Because the real reply is a randomly generated email address. &nbsp;The belief is that if people see it, then it might cause more confusion the problem of people clicking &quot;reply all&quot;.
</div>


Because the real reply is a randomly generated email address.  The belief is that if people see it, then it might cause more confusion the problem of people clicking "reply all".

<div>
This is what I expected. &nbsp;I will ask my developers to change the From, but I don't think management will allow it. &nbsp;I will read the link you send. &nbsp;thanks
</div>


This is what I expected.  I will ask my developers to change the From, but I don't think management will allow it.  I will read the link you send.  thanks

<div>
<div class="content wysiwyg-content">
I'm sending an email from a nonexistent address. &nbsp;When the user replies, they use the reply-to field.<br />
<br />
I'm curious if I can control how a client handles a &nbsp;&quot;reply all&quot;.<br />
<br />
Google Apps uses the from and reply-to fields for a &quot;reply all&quot;.<br />
<br />
Yahoo mail uses only the reply-to for a &quot;reply all&quot;<br />
<br />
Outlook 2007 uses the reply-to and the To files for a &quot;reply all&quot;. &nbsp;<br />
<br />
Can I force clients to use only the reply-all?
</div>
</div>


I'm sending an email from a nonexistent address.  When the user replies, they use the reply-to field.

I'm curious if I can control how a client handles a  "reply all".

Google Apps uses the from and reply-to fields for a "reply all".

Yahoo mail uses only the reply-to for a "reply all"

Outlook 2007 uses the reply-to and the To files for a "reply all".  

Can I force clients to use only the reply-all?

Reply All handling

An email client, email reader or more formally mail user agent (MUA) is a computer program in the category of groupware environments used to access and manage a user's email. A web application that provides message management, composition, and reception functions may internally act as an email client; as a whole, it is commonly referred to as webmail. Likewise, email client may be referred to a piece of computer hardware or software whose primary or most visible role is to work as an email client. Email clients can also have other systems, like calendars, notes and contact managers.

Email Clients

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.

Email Servers

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.