Re: [dmarc-discuss] dmarc-discuss Digest, Vol 72, Issue 2

2018-04-18 Thread Roland Turner via dmarc-discuss
As they're purely internal to a single organisation (the receiving domain, which happens to have outsourced to Mimecast and Microsoft), there's no reason to record the failures but, yes, Authentication-Results: headers might reasonably be expected to contain this information. ARC headers also

Re: [dmarc-discuss] dmarc-discuss Digest, Vol 72, Issue 2

2018-04-18 Thread Roland Turner via dmarc-discuss
On 19/04/18 00:48, Ivan Kovachev via dmarc-discuss wrote: I found this on Microsoft's website: "If you have configured your domain's MX records where EOP is not the first entry, DMARC failures will not be enforced for your domain. If you're an Office 365 customer, and your domain's primary MX

Re: [dmarc-discuss] dmarc-discuss Digest, Vol 72, Issue 2

2018-04-18 Thread Al Iverson via dmarc-discuss
So in this scenario, how is O365 denoting the DMARC failures? Is it alerting, or is it something visible only when viewing the message headers? On Wed, Apr 18, 2018 at 12:48 PM, Ivan Kovachev via dmarc-discuss wrote: > Hello Roland, > > thank you for the reply. > > I

Re: [dmarc-discuss] dmarc-discuss Digest, Vol 72, Issue 2

2018-04-18 Thread Ivan Kovachev via dmarc-discuss
Hello Roland, thank you for the reply. I found this on Microsoft's website: "If you have configured your domain's MX records where EOP is not the first entry, DMARC failures will not be enforced for your domain. If you're an Office 365 customer, and your domain's primary MX record does not