I have considered what if Gmail follows suit and plan to ask Google about just that question. They made me a top contributor a few months ago so hopefully I can get an answer. However, in general my interactions with Google on mail flow and RFCs has always been good and make sense. Plus they have paying customers so I think a change would need to be communicated far better than Yahoo's somewhat out of the blue change.
Beyond that, my guess is that this may ultimately be a stopgap measure to buy time for mailing lists to change. I know the recent mailman Release Candidate added dmarc policy settings just because of this issue. In fact, I am still not sure this is a bad thing. It was the lack of notice that really took a lot of people by surprise. Perhaps no one predicted how bad this would affect lists? Regards, KAM "David F. Skoll" <[email protected]> wrote: >On Thu, 24 Apr 2014 15:30:49 -0400 >"Kevin A. McGrail" <[email protected]> wrote: > >> We apologize for the inconvenience but the cause of the issue rests >> squarely and solely on your email provider. We recommend you >> consider a free Google account available at http://www.gmail.com/. > >I like the logic but wonder what recommendations we can make if (when?) >gmail.com goes to "p=reject"? :( > >I think I'll implement something like this on our server---thanks for >the code sample. _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
