Yes, there are several of us from Oath here. I'll have someone take a look.
On Thu, Oct 4, 2018 at 7:15 AM Maarten Oelering via dmarc-discuss <
dmarc-discuss@dmarc.org> wrote:
> 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 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)
--
PAUL ROCK
*Sr Software Dev Engineer* | AOL Mail
P: 703-265-5734 | C: 703-980-8380
AIM: paulsrock
22070 Broderick Dr.| Dulles, VA | 20166-9305
___
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)
