I can add this.

I should note that generally, while there's an "error" field available, there's 
no guidance about what should go in there. (not in 7489 either that I could 
find in a brief search)

-- 
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast
 

> -----Original Message-----
> From: dmarc <[email protected]> On Behalf Of Matthäus Wander
> Sent: Monday, October 23, 2023 2:51 PM
> To: [email protected]
> Subject: Re: [dmarc-ietf] DMARC policy discovery and invalid tag exception.
> 
> Murray S. Kucherawy wrote on 2023-10-20 21:35:
> > (2) Mapping a misspelled "reject" or "quarantine" to "none" even only
> > in the report will be confusing; the domain owner will be told there's
> > a "none" out there when there isn't.  A non-thorough domain owner
> > might conclude that the receiver is broken and not debug their
> > problem.  The guidance here ought to result in the report indicating
> > somehow that the receiver assumed "none" because what it extracted
> > from the DNS appeared to be junk.  Should the report include a mechanism
> making this explicit?
> 
> I'm a strong proponent of including human-understandable error messages in
> DMARC reports. More than once, I puzzled over whether the outgoing message
> stream or the report sender is broken.
> 
> In the above case, the already existing (but not prominently known) optional
> <error> field in the <report_metadata> section can be used to include an error
> message, e.g., "syntax error in sp tag".
> 
> Text suggestion:
> The Mail Receiver MAY utilize the optional "error" field in aggregate reports 
> to
> announce syntax errors identified in the DMARC policy record.
> 
> Regards,
> Matt
> 
> _______________________________________________
> dmarc mailing list
> [email protected]
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/dmarc__;!!C
> Ql3mcHX2A!GcbuMEjhafXK7OEhrWB70xSYAvSFVGT776G7Rd9JLN_8FJuuyBCEfJJ
> wkqzM64HD4KC46q0fl4NgesMsfXj22Jxg6gI7MWpfWutCZrad$
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc

Reply via email to