On Thursday, June 5, 2014 10:22 PM, J. Gomez <[email protected]> wrote:
>> ps. to state an example, if anybody doesn't get it. >> i have trust in ymail to send email on behalf of my domain, >> and i want a way to state that in my DMARC policy. > For that use case, you should do an SPF-include of Yahoo's SPF > inside your own SPF record. nope, that doesn't work. ESPs send email using account's original address during SMTP MAIL FROM, not user's 3rd party address. in my case that's @yahoo.com, not @goodone.tk. and that's perfectly regular and quite logical, since that's the address that is transmitting email. it would be wrong for any ESP to claim they send email for a domain they don't control. only domain-owner can do that. however, while DMARC was created exactly for something like that [domain owners specifying how they want their mail treated], it doesn't offer such choice. so, ur suggestion just shows how DMARC ppl don't understand wide scale of broad email usage scenarios. if DMARC had Sender-ID as one of underlying protocols, sure, that would work, since Sender-ID does PRA processing, which covers bunch of these scenarios, including ML, forwarding, broad 3rd party, whatever... however, for the sake of this discussion, it's obvious DMARC MUST include some 3rd party support, or it will be a failure at the end, as much as many previous policy attempts, now merely historic references. and, btw, i do have ymail in my domain's SPF. it's there for Sender-ID compatibility. not that it matters for this discussion. currently, DMARC rigidity excludes my usage scenario, and that's wrong. -- Vlatko Salaj aka goodone http://goodone.tk _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
