Philip,
Here are the effects that I see. I use this gmail account for my IETF mailing lists. I am now consistently seeing email sent from Yahoo users end up in my spam folder with the following embedded warning message:
Be careful with this message. Our systems couldn't verify that this message was really sent by yahoo.com. You might want to avoid clicking links or replying with personal information. Learn more
The sender, of course, is completely unaware of what is happening on the receiver's end, so they have no reason to want to change from Yahoo to another domain for posting.
So this is imposing pain on the receiver, since I now have to consistently check my spam folder for valid IETF email.
I see that you also use gmail, so you should start checking your spam folder as well.
Cheers,
Andy
On Tue, Apr 29, 2014 at 3:54 PM, Phillip Hallam-Baker <hallam@xxxxxxxxx> wrote:
I am finding it rather hard to follow the DMARC discussion. Some folk
have managed to convince me that they are upset but working out why
would require rather a lot of spec crunching.
My best theory so far is that DMARC is some sort of email policy
statement and that either (1) some companies are now publishing a
policy that states 'reject all mail that purports to come from this
address that does not have authentication Y' or (2) some companies are
now rejecting mail not in compliance with said policy or (3) both.
There is a simple truth about DNS names: Whoever owns them makes the
rules for their use [1]. If you don't like the rules for google.com
then choose another domain to post from.
If people want email to work with mailing lists, then don't complain
about reasonable choices people want to make. Work out a way to fix
mailing lists so that they work properly.
There is no reason we can't change the way From works. Or add new from headers.
Are we engineers or curators of the past?
[1] Thus be rather suspicious of folk who claim that we merely rent
the use on terms of their choosing.
--
Website: http://hallambaker.com/