On Mon, Sep 20, 2021 at 2:32 PM Scott Kitterman <[email protected]> wrote:
> > That's not specified in RFC 7489, so it's an assumption that this is how > the > world works. At best it's undefined and I don't think we can engineer > interoperability based on assumptions about how current implementations > address undefined behavior. > > Also, in my experience anyway, mailing lists aren't a significant source > of > problematic spam and so I don't think doing things to solve what is mostly > already a non-problem is really needed. > > Let's not do this. > > Scott K > +1 It does more than assume how current implementations address undefined behavior. It also makes assumptions about curren behavior that is somewhat known and defined but not necessarily consistent across participating entities. It assumes for example that outbound mail only does a single hop except for going through MLMs. It assumes that there aren't multiple hops on the inbound side (Think for example cloud based or hybrid security solutions where the ultimate receiver may have limited control or no control over behavior before ultimate delivery. So as Scott succinctly puts it, " Let's not do this." Michael Hammer
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
