On Thursday, June 05, 2014 11:10 PM [GMT+1=CET], Vlatko Salaj wrote: > 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.
Yes, and why is that a problem for the use case you stated? When you said "i have trust in ymail to send email on behalf of my domain", were you meaning that you wanted ymail using your domain in the MAIL-FROM envelope (1), or in the Header-From field (2)? If (1), that would be something unreasonable to expect from ymail, and please explain why would you need it. If (2), please explain whether ymail allows it or not, and if not please explain why would that be a DMARC limitation instead of a ymail limitation. You should describe your indented use case with more detail, I'm afraid I'm not following your reasoning here. > so, ur suggestion just shows how DMARC ppl don't > understand wide scale of broad email usage scenarios. It's a way to put it. Another way would be: your use case is obscure and you shed no light on it. > currently, DMARC rigidity excludes my usage scenario, and > that's wrong. Please, explain with more detail how is your usage scenario excluded by DMARC. I fail to see how, as described by you up to now, is your usage sceneario impeded by DMARC instead of by ymail/whatever, given that DMARC leverages SPF and SPF has the concept of includes available to you. Regards, J.Gomez _______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
