<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 01/30/2012 12:06 PM, Greg Colburn wrote:
<blockquote cite="mid:CB4C43C6.11676%25greg.colburn@returnpath.net"
type="cite"><br>
<div>Also, we provide an authentication reflector that will check
dkim, spf, dmarc and associated information. Email to
<a class="moz-txt-link-abbreviated" href="mailto:checkmyauth@auth.returnpath.net">checkmyauth@auth.returnpath.net</a> and you will receive an email
report 10-15 minutes later with full details.</div>
</blockquote>
<br>
Thanks for getting this out there so quickly! However the DMARC
summary doesn't actually indicate what would have been done with the
message. Viz:<br>
<br>
<pre wrap="">DMARC Results
=============
Domain = _dmarc.crash.com
DNS Record(s) =
_dmarc.crash.com TXT p=quarantine; sp=reject; ri=43200; rua=<a class="moz-txt-link-freetext" href="mailto:sysadm@crash.com">mailto:sysadm@crash.com</a>; ruf=<a class="moz-txt-link-freetext" href="mailto:sysadm@crash.com">mailto:sysadm@crash.com</a>; v=DMARC1
</pre>
<br>
It does indicate earlier in the report whether or not SPF and DKIM
are aligned, and whether or not SPF and DKIM passed, so I'm sure
this is just an minor oversight.<br>
<br>
This report is a great thing to have, especially when somebody's
doing this for the first time or trying to troubleshoot a problem.
But I would also recommend generating some traffic to a GMail
address so you can see what the report looks like the following day.<br>
<br>
Thanks again Greg!<br>
--<i>S</i>.<br>
</body>
</html>