On Sat 13/Aug/2022 18:09:54 +0200 John R Levine wrote:
I'd rather it be more general, to show where all of the plausible parts go.
Message/rfc822 is not more general, is just different. If I implemented
failure reporting, I'd choose text/rfc822-headers (and heavy redaction) to
reduce PII leakage as much as possible.
The point of the example is to show people what the message format is, so I
would include all the stuff that would plausibly appear in a failure report.
Oh well, I added the body, and a paragraph below to mention that one could have
added just the header.
Any other note?
Shall I post it?
By the way, it looks like you edited this into the XML rather than the
markdown source. It would be nice to have the markdown available for future
edits.
I agree. However, the md file in the repository is strange as it contains
stuff which should be generated.
It does, it looks like someone did a quick cut and paste to make the markdown.
But it's not that long, you're the editor, how about fixing the md so it's
useful for editing?
It must have been me. I recalled; I searched again for something to generate
the md and again found only https://codebeautify.org/html-to-markdown. That
way the (bottom) part of the md looks similar to the txt, but it's not usable
for editing.
I'll fix it next time...
Best
Ale
--
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
