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.
2017-10-20 18:04 GMT+02:00 Bill Cole < postfixlists-070...@billmail.scconsult.com>: > On 20 Oct 2017, at 11:37 (-0400), Michael Orlitzky wrote: > > tl;dr use a real address >> > > That's the bottom line best practice for all use cases. ALL. > > If you can't think of a process to handle the asynchronous bounces and the > intentional replies by innocent fools, you should not be sending the email. > Make the SMTP envelope sender an address that works so that you know (or > automatically deal with) the inevitable cases when a target address goes > bad. Add a Reply-To header with a role address that a real human or one of > a group of humans will read at least daily, to handle the clueless human > issues. > > This isn't really hard, unless you're trying to escape responsibility for > the mail you send. That's actually very hard, because if people want it to > stop, they'll find ways to keep it out and maybe impair your general > ability to send to others. > > -- > Bill Cole > b...@scconsult.com or billc...@apache.org > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Currently Seeking Paying Work: https://linkedin.com/in/billcole > -- *Pozdrawiam / Best Regards* *Piotr Bracha*
