On 11/27/2018 05:03 PM, Michael Peddemors wrote:
Okay, I get it.. you don't want the customer to reply to your 'Latest News' blast about your product, but if you ARE going to use 'donotreply@', at least put the proper headers to indicate that ...Auto-Submitted: auto-generated X-Auto-Response-Suppress: OOF And why do people put in a header for Reply-To: noreply@ If you don't want a reply, you don't need a reply to header..
I find the entire do-not-reply thing annoying.Arguably any outgoing email should come from an email address that hypothetically could receive email. IMHO this is independent of whether or not you actually want replies.
My preference is to send from an address and direct proper replies to something like info@ or sales@ front door type addresses and let that (likely existing) mechanism filter through them.
In my experience some end users will reply. And the failure mode they experience will reflect somewhere between neutral and badly. Receiving a bounce never goes well.
My preference and what I recommended customers do was: · Send with an SMTP envelope using VERP. · Send to an SMTP recipient with ORCPT.· Send with a From: header that accurately reflects the source / campaign / etc.
· Make sure that there is an MX for the From: (or parent) domain.
· Send with a Reply-To: header set to a front door service address.
· Make sure that there is an MX for the Reply-To: (or parent) domain.
· Include the aforementioned headers:
· Auto-Submitted: auto-generated
· X-Auto-Response-Suppress: OOF
· Precedence: Bulk (for broadcast / multicast emails)
· Make sure that you react to bounces.
· Provide an unsubscribe / opt-out option.
· Make sure that you react to unsubscribe requests.
· Send text/plain if at all possible.
· Send with matching text/plain and text/html if you must use HTML.
· Make it easy for the recipient to determine if this is specific to
them or a general broadcast.
· Consider using different (From:) email addresses for different
services / campaigns.
· (Now) DKIM sign outgoing messages.
· Adhere to your SPF records.
· Use DMARC that is satisfied by DKIM -or- SPF.
· Helps with forwarded email.
· Optionally include an "X-Abuse-Complaints-To:" (type) header.
· Otherwise be as good a netizen as possible.
I don't think any of this is hard. It's just that there are a lot of
relatively simple things to do that make the quality of email a lot higher.
And just because you don't want a reply to, and don't feel a need to 'thread', still no reason not to generate a reasonable 'Message-ID' header..
Agreed. -- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
