It appears that Barry Leiba said:
>I think it should be handled as HFDU, and John should open an issue
>for it on the bis doc. The working group needs to decide what the
>right ABNF should be.
I added an issue with suggested BNF.
Looking at a sample of reports, I see that almost nobody follows
I think it should be handled as HFDU, and John should open an issue
for it on the bis doc. The working group needs to decide what the
right ABNF should be.
Barry
On Fri, Sep 30, 2022 at 8:51 AM Independent Submissions Editor (Eliot
Lear) wrote:
>
> Hi,
>
> Can I get a bit more clarity on what s
Hi,
Can I get a bit more clarity on what should happen with this one.
Eliot
On 21.08.22 17:06, John Levine wrote:
I happen to have a folder with 300,000 reports and took a look. Reporters can
be pretty
random about what they do.
Comcast and Yahoo put angle brackets around the report ID but
I happen to have a folder with 300,000 reports and took a look. Reporters can
be pretty
random about what they do.
Comcast and Yahoo put angle brackets around the report ID but Google and
Microsoft don't and
nobody else does as far as I can see, so I would change the last line of the
ABNF to:
Dear Authors and DMARC group,
In my continuing review of errata posted against RFC 7489, my view is
that the following erratum should be verified, and I intend to do so in
the next month unless given good cause not to do so. My logic is that
running code in the wild should trump whatever is i
