Hi there,
Yahoo (OAuth) is sending DMARC reports with a space after the “end” timestamp:
<date_range>
<begin>1538524800</begin>
<end>1538611199 </end>
</date_range>
This breaks strict parsers which expect an integer, following the schema In RFC
7489:
<xs:complexType name="DateRangeType">
<xs:all>
<xs:element name="begin" type="xs:integer"/>
<xs:element name="end" type="xs:integer"/>
</xs:all>
</xs:complexType>
It has been like this for years, and probably many have found a workaround or
use relaxed parsers. But I think it should be fixed.
Anyone from OAuth in this group who can push for a fix?
Thanks,
Maarten Oelering
Postmastery
_______________________________________________
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)
