I have an email in which an auto-response was sent to Google via sieve. The envelope from was therefore empty as per the RFCs.
However, Google included this email in the aggregate reports with auth_results of DKIM pass, SPF pass, and policy_evaluated of DKIM pass, and SPF *fail*. The "domain" in auth_results is the FQDN of the mail server, which is a hostname, not a domain. The evaluated SPF fail was presumably because, with an empty Return-Path, google used the FQDN of the mail server as the domain. So what is the problem here? Misconfiguration on my mail server, problem with Google's DMARC logic, or a DMARC spec ambiguity? Regards, Raman _______________________________________________ dmarc-discuss mailing list [email protected] http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
