Here's what I saw reported on it:
Authentication-Results: mx.google.com;
dkim=pass [email protected] header.s=ietf1 header.b=bJFPnWzx;
dkim=pass [email protected] header.s=ietf1 header.b=BcDgnOt9;
dkim=neutral (body hash did not verify) [email protected]
header.s=20161025 header.b=TUo2B94r;
spf=pass (google.com: domain of [email protected] designates
2001:1900:3001:11::2c as permitted sender) smtp.mailfrom=
[email protected]
From: Barry Leiba <[email protected]>
Date: Tue, 10 Apr 2018 11:41:59 -0400
Errors-To: [email protected]
Sender: dmarc <[email protected]>
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass [email protected] header.s=ietf1 header.b=bJFPnWzx;
dkim=pass [email protected] header.s=ietf1 header.b=BcDgnOt9;
dkim=neutral (body hash did not verify) [email protected]
header.s=20161025 header.b=TUo2B94r;
spf=pass (google.com: domain of [email protected] designates
2001:1900:3001:11::2c as permitted sender) smtp.mailfrom=
[email protected]
--Kurt
On Tue, Apr 10, 2018 at 8:41 AM, Barry Leiba <[email protected]>
wrote:
> I understand we now have the DMARC workaround test up in this list.
> That means that "from" addresses should get rewritten if they identify
> domains with DMARC p=reject. Let's check that out.
>
> This message is from my usual computer.org address, and shouldn't get
> rewritten. It should say
> sender: [email protected]
> from: [email protected]
>
> Barry
>
> _______________________________________________
> dmarc mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dmarc
>
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
