There's also already RFC7960 which expands upon 5598 with specific reference to DMARC's impact.
On Sat, Nov 30, 2019 at 7:37 AM Dave Crocker <[email protected]> wrote: > On 11/30/2019 4:40 AM, Alessandro Vesely wrote: > > Let me quote this from the ietf-smtp mailing list: > > On Sat 30/Nov/2019 00:12:53 +0100 John C Klensin wrote: > > --On Friday, 29 November, 2019 11:16 -0600 Pete Resnick wrote: > [...] > > Even the "From: rewriting" issue is > a gatewaying issue, not a message format issue per se. > > That is less clear. It fits into the gray area that has existed > for years about just exactly what a mailing list exploder / > redistribution system really is. > > > This view is reasonable only if one re-defines accepted terminology and > ignores some basic technical facts. > > A user specifies a recipient address. The message is posted and then > delivered to that address. > > That simple process describes basic email handling, and has been the > accepted view for roughly 40 years. > > And it describes the /first/ leg of a message sent /through/ a mailing > list. > > For the second leg, a bot at that address /re-/posts the message. In > simple, formal email technical terms, this is an entirely new email > transaction. > > It isn't 'gatewaying' per se, since that term applies to transit between > heterogeneous systems, but it /is/ a higher-level process. > > If only we had a document that discussed all this coherently, defined > basic terminology, and had undergone IETF review and approval. If only we > had RFC 5598... > > > d/ > > -- > Dave Crocker > Brandenburg InternetWorkingbbiw.net > > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc >
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
