Re: [dmarc-ietf] Non-solution for DMARC disruption of normal email use while still offering its normal protection

2014-05-30 Thread John R Levine
TLDR summary: addressing "legitimate-but-unauthorizable" mail is my answer to Scott Kitterman's question: "How do we define the scope of work for this list?". Yup. Yes, I get it, I guess in my own jaded way I don't think there is any amount of money that Yahoo and AOL can spend that will fix

Re: [dmarc-ietf] Non-solution for DMARC disruption of normal email use while still offering its normal protection

2014-05-30 Thread John Sweet
There's probably no point in coding a patch unless you feel the people responsible for the codebase are likely to apply it. That's a lot of effort down a rathole, especially since some number of the intended audience feel that it's inappropriate to ask them to change anything in their software. It

Re: [dmarc-ietf] Non-solution for DMARC disruption of normal email use while still offering its normal protection

2014-05-30 Thread Tim Draegen
On May 29, 2014, at 3:05 AM, John R Levine wrote: > Really, that makes no difference. I don't want Yahoo or anyone else to pay > us to screw up our mail software to work around them -- I want them to spend > their money to fix things so we don't have to. Yes, I get it, I guess in my own jaded

Re: [dmarc-ietf] Non-solution for DMARC disruption of normal email use while still offering its normal protection

2014-05-29 Thread John R Levine
Hello John, what you're missing -- and its easy to miss -- is that Yahoo has an outstanding offer to help developers (this means $!) fix things. Really, that makes no difference. I don't want Yahoo or anyone else to pay us to screw up our mail software to work around them -- I want them to sp