Hi list members,
We see many aggregate reports where is a subdomain
which does not publish a DMARC record. The DMARC record is on the organisation
domain.
The specification (RFC 7489 appendix C) says this should be the domain at which
the DMARC record was found, not the RFC5322 From domain:
Hi there,
Yahoo (OAuth) is sending DMARC reports with a space after the “end” timestamp:
1538524800
1538611199
This breaks strict parsers which expect an integer, following the schema In RFC
7489:
It has been like
Hi,
Is anyone from Trustwave on this list?
Their SEG software don’t know how to spell "Content-Type”. It’s spelled without
dash:
=c5c709ca-bc35-4c5e-aca0-da12cbc9280f
ContentType: application/gzip;
name=“receiver.co.uk!sender.com!1523433708!1523522202!4344.xml.gz"
Content-Transfer-E
Is anyone from Trustwave SEG on this list? They should check the spelling of
Content-Type in their DMARC reports:
=6777a7f7-be29-40d4-ba25-6d03af8ce8d1
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
This is a DMARC report generated by Trustwave SEG.
-
Hi Franck,
You explained this before, but also then I didn’t quite understand.
First you say there is the SPF check on HELO and on MAILFROM. That I know and
understand.
Then you say DMARC only uses the RFC5321.Mailfrom, but which includes falls
back on RFC5321.Helo.
But isn’t that the same in
Do you mean that in the XML you see 6 elements in one
element? Or do you mean you see 6 different domains in the your reports?
Maarten Oelering
Postmastery
> On 4 apr. 2016, at 09:05, Nick via dmarc-discuss
> wrote:
>
> I received a DMARC report with multiple SPF results. I wonder how this
If you can share the full email header of a test mail as it is received,
that would help. For example from a Gmail account. Based on that it's easy
to check SPF/DKIM validation, alignment, etc. You can also use a service
like emailaudit.com to check all DMARC prerequisites.
Maarten
Postmastery
On