From: Michael Richardson <lsuc!nrcaer!julie!mcr@xxxxxx>
I agree strongly with you: the IETF needs to do something in some direction.
That something could be to properly reject email with a DMARC policy that
does not permit forwarding. That would piss off an awful lot of IETF
participants, but it would be simple, since it requires no protocol
changes, just social changes.
=JeffH <Jeff.Hodges@xxxxxxxxxxxxxxxxx> wrote:
> Regardless of details, applying some sort of remediation to
> ietf.org/mailman is becoming more pressing IMV -- I am noticing that
> email, sent from pingidentity.com (p=quarantine; pct=100;) via IETF
> mailing lists, is not being delivered to my paypal.com inbox at
> all. Also, the same is occurring for some email from microsoft.com
> (p=quarantine; pct=30;). The same is true for email I might send via my
> @paypal.com persona.
It seems that email is operating exactly as DMARC intends :-)
> The W3C mailing list manager (MLM) is apparently configured to do
> rfc5322.from field re-writing which seems to ameliorate the DMARC-MLM
> issues (in my experience, at least), and it would be helpful if the
> IETF would take similar measures.
But, that would also render the From: field meaningless.
--
Michael Richardson <mcr+IETF@xxxxxxxxxxxx>, Sandelman Software Works
-= IPv6 IoT consulting =-
Attachment:
signature.asc
Description: PGP signature