On Thu, Aug 1, 2019 at 9:32 AM Alessandro Vesely <[email protected]> wrote:
> Let me narrate a use case. Courier-MTA can be configured to reject on SPF > -all > early in the SMTP dialogue, except if whitelisted. It writes SPF as well > as > dnswl results in the header, but does not interpret the policy.ip. > Downstream > filters can interpret the field based on the dns.zone. I use that feature > to > pass messages tagged "Heuristic" by the antivirus filter if policy.ip has a > positive trustworthiness. > I think this is a bit unusual, but RFC8601 doesn't preclude it. Seems to me you're effectively throwing away the result, "pass" or "fail", if downstream agents actually know more about the applied algorithm than the border MTA adding it. > Yes, the last paragraph is guidance about querying ANY. It could go to an > appendix or be stroked, if we want to go through another revision. > > The first paragraph is about how dnswl's may work. Rfc5782 just says > "DNSWLs > MAY have a TXT record that describes the reason for the entry." I agree > it is > slightly out of scope for registering the parameters. OTOH, I'd like to > know > more dnswl's in order to inform better on TXT record usage. > As long as the text is focused on the registration and not providing opinion about RFC5782, it's fine. I'm not so sure where the current text lands. -MSK
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
