> On Oct 23, 2017, at 12:27 AM, Poliman - Serwis <ser...@poliman.pl> wrote:
>
> Ok, I make a mistake, because I didn't say about for what will be use "do not
> reply". So - I work in IT company. Developers make different applications and
> these applications send mainly confirmation emails, also reminder password
> emails. These emails should only be send and receiver could not answer this
> email with success. That's all. I use ISP config with postfix.
You need to take the time to understand the distinctions between:
1. The message envelope sender
2. The RFC2822 "From:" message header
3. The RFC2822 "Reply-To:" message header
The email address used in (1) MUST be valid, and your system
must accept email back to this address. You can choose to
discard it, but for auto-generated traffic it is really best
practice, and important for ongoing deliverability to implement
a proper automated bounce processor for replies to this address.
It is should use VERP or similar to make it maximally likely
that you can identity the target recipient that elicited the
bounce.
The email address used in "2", gives the recipient some sense
of who the message is from. This can be a mailbox that
rejects all replies, but is better to use:
From: "Example Corp password reset robot (please do not reply)"
<supp...@example.com>
Reply-To: "Example Corp no reply mailbox" <nore...@example.com>
So that most replies bounce, but some folks can choose to manually
override reply-to and send mail to "supp...@example.com".
The email address in (3) can be a non-deliverable address that is always
rejected.
--
Viktor.
