Thank you for a lot of answers. Could you tell me how would you resolve the problem? I am not much experienced in mailer daemons. Which is the best option in my case - developed application send confirmation emails on which receiver shouldn't answer.
2017-10-23 9:41 GMT+02:00 Matus UHLAR - fantomas <uh...@fantomas.sk>: > 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. >>> >> > On 23.10.17 01:51, Viktor Dukhovni wrote: > >> 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. >> > > actually, the address can be null: <> and bounces must not go to that > address. The downside is that some systems/spam filters may reject it. > > 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". >> > > I am not sure if some autoreplies won't use From: addresses even if this > case. but I am sure most OOO responders will send the mail to one of those > addreses even if the "1" address is null. > > However one canusualy add headers as "Precedence: bulk", and > "Auto-Submitted: auto-generated" to avoid these cases as much as possible. > > The email address in (3) can be a non-deliverable address that is always >> rejected. >> > > but I still would not recommend that... > > -- > Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ > Warning: I wish NOT to receive e-mail advertising to this address. > Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. > Posli tento mail 100 svojim znamim - nech vidia aky si idiot > Send this email to 100 your friends - let them see what an idiot you are > -- *Pozdrawiam / Best Regards* *Piotr Bracha*
