Dear John,
"PS: I presume you all know that we've been working on workarounds."
Please John, explain your results or understanding in the IETF list,
that all members in the list know, for what you work and what problems
exist for you.
many thanks and greetings, willi
On 01/03/2017 18:00, John Levine wrote:
In article <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@xxxxxxxxxxx> you write:
This is a good idea. Taking it a step further, perhaps a warning could be included when
subscribing to an IETF list from an email provider who is known to use DMARC.
You can tell who publishes DMARC policies, but without experimentation
you can't tell who follows them on inbound mail.
Of the large public mail providers, only AOL and Yahoo currently
publish DMARC policies, but Gmail certainly looks at DMARC, albeit as
part of the special sauce so a Gmail user might get mail with DMARC
problems or might not. I'm reasonably sure that Hotmail and Comcast
also look at DMARC on incoming mail. DMARC is surprisingly useful for
blocking phishes, which is a big issue for consumer mail providers, so
the providers that use it are not going to stop.
R's,
John
PS: I presume you all know that we've been working on workarounds.