On Friday, June 6, 2014 10:16 PM, J. Gomez <[email protected]> wrote:
>> === >> FROM header: [email protected] >> MAIL-FROM envelope: [email protected] >> DKIM domain: yahoo.com >> === >> >> results: >> 1. mail legitimate; validated by sending ESP using: >> 2. valid DKIM @yahoo.com, >> 3. servers validated by SPF at yahoo.com, >> 4. goodone.tk SPF records r of no importance here, >> 5. DMARC is unable to authenticate this email: no 3rd party support. > I think DMARC would be able to authenticate that email as long as > GOODONE.TK included in his SPF record the SPF record of YAHOO.COM. well, u think wrongly. i suggest rereading both of SPF, DKIM and DMARC drafts. > If the particular SPF record of YAHOO.COM does not lend itself > to be SPF-included with third parties (as it uses the "redirect" > mechanism), that is not a SPF problem nor a DMARC problem, > instead it is a YAHOO.COM problem and an implicit declaration > from YAHOO.COM that your use case does not fit with them > (but if you don't have your own MTA, then again your use case > could indeed fit with YAHOO.COM). omg. u rly don't know much about SPF... >> i hope others understand my example. > I hope so too, so that I can be enlightened about why am I wrong. good luck getting help on this mailing list, lol. maybe some DMARC's 3rd party support supporters can replace me here, cause i lost all my interest in participating in this black hole called DMARC mailing list, for now. sorry for that. -- Vlatko Salaj aka goodone http://goodone.tk _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
