Charles Lindsey suggested: >> It really needs to back up and define how a sender publishes its >> policy, how a recipient can look up a policy if it wants to do so, >> then stop. That's all they need to interoperate. > > But that is going too far. It covers my #1, but not my #2, which > includes important stuff such as the 'strict' and 'deny' features. > > And I am still happy to see BCP material which then, essentially, > describes ways in which verifiers are "expected" > to apply the "advice".
A fine idea -- except, how do we list Best Current Practices when there are no current practices yet? -- J.D. Falk Receiver Products Return Path _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
