On Feb 27, 2014, at 10:43 AM, Dustin <[email protected]> wrote:
> Perhaps one example of being wary of p=reject: Absolutely. > Matt's message, as evaluated by Gmail, failed alignment, and was consequently > marked as spam. Thanks to DMARC reports, the sender is quite aware. Of course I'd prefer that this list didn't invalidate my DKIM signatures. I'd also prefer that Google's SPF recognized that this list server is SPF permitted for @tnpi.net. But that's outside my ability to influence. $ spfquery --mfrom [email protected] --ip-address=`dig medusa.blackops.org +short` pass Received-SPF: pass (tnpi.net: Sender is authorized to use '[email protected]' in 'mfrom' identity (mechanism 'include:lists._spf.tnpi.net' matched)) receiver=rmbp.local; identity=mailfrom; envelope-from="[email protected]"; client-ip=208.69.40.157 Until we have a solution that lets DMARC mail securely transit email lists, our two legged DMARC table will wobble. Matt _______________________________________________ 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)
