> 4.3.1. > The reports SHOULD use "Feedback-Type: abuse", but can use other > types as appropriate to the nature of the abuse being reported. > However, the Mailbox Provider generating the reports needs to > understand that the operator receiving the reports might not > treat different feedback types any differently. > > How about instead: "The reports SHOULD use "Feedback-Type: abuse" for its > type. Although a Mailbox Provider generating the reports can use other types > appropriate to the nature of the abuse being reported, the operator > receiving the reports might not treat different feedback types differently." > The "needs to understand" construction confused me as it didn't seem like > something actionable.
For the ARF reports we generate, we always use "Feedback-Type: abuse", but add an Abuse-Type field that describes the origin of the abuse. Currently this is one of complaint, trap, trap-pristine, or trap-recycled. Are we suggesting that these types should be used in place of abuse for Feedback-Type? Section 5.2.1 makes it clear that the specific meaning of abuse might require additional analysis. > 6.2.1 > Handling of unsolicited reports has a significant cost to the > receiver. Senders of unsolicited reports, especially those > sending large volumes of them automatically, need to be aware of > this and do all they reasonably can to avoid sending reports that > cannot be used as a basis for action by the recipient, whether > this is due to the report being sent about an incident that is > not abuse-related, the report being sent to an email address that > won't result in action, or the content or format of the report > being hard for the recipient to read or use. > > I don't get why 2119 language is being avoided in the above. Why not s/need > to be aware of this and do all they reasonably can to avoid > sending/[MUST/SHOULD] NOT send ? Are generators of unsolicited report also required to respect 6.1.1? Does this establish some type of opt-out regime? _______________________________________________ marf mailing list [email protected] https://www.ietf.org/mailman/listinfo/marf
