> On Dec 14, 2018, at 8:11 PM, DMARC via dmarc-discuss
> <dmarc-discuss@dmarc.org> wrote:
>
> https://mxtoolbox.com/Public/Tools/EmailHeaders.aspx?huid=8cbcac83-feb4-4c7f-93ba-a1c7b6111dac
>
> Any idea why the DMARC/SPF/DKIM is reported by MXToolbox as possibly
> problematic?
>
> Background, the mailrouting is being bounced internally, before being sent to
> a GMail account. My concern, is that while technically the email is 100%
> valid for DMARC/SPF/DKIM, perhaps some receiving mail server might balk.
Google thinks it's fine:
Authentication-Results: mx.google.com;
dkim=pass header.i=@faa.gov header.s=020518 header.b=FaAg+jU7;
spf=pass (google.com: domain of jack.ctr.daus...@faa.gov designates
162.58.35.109 as permitted sender) smtp.mailfrom=jack.ctr.daus...@faa.gov;
dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=faa.gov
I'd guess mxtoolbox has just gotten confused in it's parsing somehow rather
than there being an issue with the way you're sending mail.
Cheers,
Steve
>
> Thanks !
>
> _______________________________________________
> dmarc-discuss mailing list
> dmarc-discuss@dmarc.org
> 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)
_______________________________________________
dmarc-discuss mailing list
dmarc-discuss@dmarc.org
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)