Adrian wrote:
On Thu, Dec 01, 2011 at 03:24:05PM +0100, Frank Gadegast wrote:
hi,
Hi,
You forgot about bigger ISPs that likes to report abuse automatically in standarized formats (and what most abuse departments really LIKE to receive).
True, but this is an orthogonal problem.
An unrestricted abuse contact really helps here a lot.
Like, the abuse mailbox defined in RFC 2142?
Dont forget that the abuse-mailbox is mandatory, the new abuce-c isnt (and its also hierachically). When automatic parsing is needed, your need to query several objects including IRT, remarks, abuse-mailbox (what is usally not present for networks that ARE spamming a lot) and finally personal objects to find at least one email address you could send an abuse report too. And personal objects ARE restricted, what compicates things a lot.
But to be honest: no restriction helps that your email address ends up in a spammers list, they have more
Adding arbitrary restrictions doesn't prevent that either.
power you can dream of (I even heared that they pay people to enter captcha codes).
Yes.
Ok, so lets restrict access to personal objects even more and lets have a non mandatory and public abuse-c without any restriction. And I still like the idea of an "preferred contact method" field, so we can decide what format to use automatically.
Cheers, Adrian
Kind regards, Frank -- PHADE Software - PowerWeb http://www.powerweb.de Inh. Dipl.-Inform. Frank Gadegast mailto:frank@powerweb.de Schinkelstrasse 17 fon: +49 33200 52920 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 ====================================================================== Public PGP Key available for frank@powerweb.de