Hi there,

I've been quickly going through the archives to try to catch up in the discussion after reading the current document. It struck me as odd that the role objects will have a single abuse-mailbox object which should be used to receive both automatic and manual reports. I'm aware of this (related) exchange (from the archives):

From Tobias Knecht
> > Is it for high volume automated report dissemination (trap or sensor initiated
> > identification of "activity")?
>
> > For this to work it needs automated handling on the receiving side and it should
> > be clearly opt-in, so that the receiving entity can prepare for proper processing.
>
> Disagree from my experience in the anti-abuse industry. First of all
> reporting must be easy and receiving reports must be easy as well. [...]
>
> Second, if you do not want to receive reports from one party, block them
> or directly delete them. That is best practice and widely adopted and
> really not complicated to do. [...]


While this matches my experience -- and I'm sure this will also match with the experience of anybody who has had to handle a large volume anti-abuse operation -- I remember there were times where I wished there was an easier way.

The automated reports tend to vastly outnumber the manual reports, which also mix with the loads of spam that are (purposely?) pointed at the abuse contacts. This complicates the task of sifting through the mail flow to direct the complaints into their proper bins for processing. There's also the case of those that don't care about abuse originating from their resources. Those are likely to simply devnull their abuse complaint flow just as they have been doing up until now.

I believe that having an optional "auto-abuse-mailbox" object (that is mandatory to use when present) dealing only with automated reports, could help anti-abuse operators (both in the report sending and receiving sides). The automated, high volume generators can decide not to waste resources with entities that do not have the right objects setup (ie, if there's not an auto-abuse-mailbox, do not generate the report) and the entities that are not prepared to deal with automated reports, could signal that to the community by not defining an auto-abuse-mailbox.

Note that I still support the notion of a mandatory abuse-mailbox where manual complaints can be sent. At least that takes a way a lot of (guess)work out of figuring out where to send the complaint.

Best regards

-lem