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
