I wouldn't take the lack of answers terribly personally. There certainly are a lot of threads to track right now.
As for your specific ideas: On Mon, Apr 14, 2014 at 10:10 AM, Vlatko Salaj <[email protected]>wrote: > i already mentioned including SRS in check logic. unfortunately, no dmarc > author rly added much to the topic, and i work alone only on my own > projects, > not on collaborative things as these. > I seem to remember there was in fact discussion of your SRS advocacy. > also, my 2nd suggestion, independent from 1st, if we mark SRS as 1st, > would be: > a. dmarc alignment is a big issue. read: huge issue. > b. since alignment is an issue, make it policy optional. > c. by "make it policy optional" i mean: include an option in dmarc dns > policy, > so that domain owners could turn dmarc alignment check on/off. > One way of viewing DMARC is that it seeks to allow a domain owner to have better control of how its domain is used, so I don't know what this would accomplish. If alignment is optional, what does DMARC do policy-wise that DKIM and SPF don't already do? this could be useful for: > domains using high volume ML participation, > domains that use 3rd party services for their email infrastructure, > domains that use forwarders, > bunch of other special cases u can find on internet today and in future. > > my 3rd suggestion, which would go nicely together with 2nd, is: > 1. current dmarc spec uses OR logic while processing SPF and DKIM; why? > They have complementary failure modes. Data shows that the vast majority of mail passes at least one if not both. OR is the best logic in that scenario, is it not? 2. make this policy processing logic selectable. > 3. by "make it selectable" i mean: include an option in dmarc dns policy, > so that domain owners could turn dmarc processing logic either to OR or > AND. > That might be useful, but isn't that more restrictive, and not less restrictive? How would it help your use case, for example? -MSK
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
