On Wed, Jul 12, 2017 at 11:38 AM, Terry Zink via arc-discuss < [email protected]> wrote:
> This structure has always bugged me: > > > authentication-results: google.com; dkim=none (message not signed) > > header.d=none;google.com; dmarc=none action=none header.from= > linkedin.com; > > What's going on is that there are separate agents that do the DKIM > evaluation and the DMARC evaluation. Their output result is <recipient > domain>; <output of agent>. They are all concatenated onto the end of the > Authentication-Results header. There isn't a "clean up" afterwards (DKIM > and DMARC agents individually may fail as well which gets even more > confusing, but at least one of them gets stamped). And on an outbound > message (which is what you see here), there is no SPF check so it just > looks weird. > I don't know if you've see the other threads on the dmarc@ietf list, but the A-R header(s) and the content thereof have been a bit of an open item. If we were to recreate something other than RFC7601 to become the AAR header, do you have some suggestions for a better approach? --Kurt
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
