This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[anti-abuse-wg] 2011-06 Review Phase Extension
- Previous message (by thread): [anti-abuse-wg] 2011-06 Review Phase Extension
- Next message (by thread): [anti-abuse-wg] 2011-06 Review Phase Extension
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Frank Gadegast
ripe-anti-spam-wg at powerweb.de
Tue Jul 31 14:16:24 CEST 2012
Jørgen Hovland wrote: > > > At 10:42 31/07/2012 (UTC), Tobias Knecht wrote: > > > > > So I'm really interested in hearing more reasons for your objection here > > no matter if you are talking about the "abuse-c:" or the > > "abuse-mailbox:" attribute. > > > Just to make things clear about real consequences of mandatory abuse-c: > > 1. > None of our customers have an abuse department or abuse contact (and > often tech person). We will therefore bulk update the abuse-c with the > value from the admin-c handle. Well, its your decision, if you like to reveal personal data via the abuse-c. In fact, you shouldnt do this. You could either: - set the abuse contact email address to abuse at customerdomain.de automatically and inform your customers, that this email address has to be read from now on - inform and educate your customers to tell you another address - you could set it to something like abuse-inetnum-x-x-x-x at hovland.cx and forward incoming mail to your (and now hidden) customers email address and if your customer does not like to have incoming mails mixed with his other mails, well, he could tell you another address - or set it to your own abuse address and handle incoming reports for your customer > 2. > The e-mail field in the role object (abuse-c requires a role object) is > mandatory. We actually have customers that do not have an email address > or haven't provided one (probably also dont want to provide one). In > these cases, I guess the e-mail field will be populated with a bogus > email address in the form "there.is.no at email.address" and perhaps insert > remarks: with company URL instead etc. What is absolutly ok. The proposol is not forcing resource owners to have a working abuse department, its simply forcing all objects to have a single place where to store abuse addresses. But: the proposal is a nice starting point to educate resource owners, so it would be really nice, if you make your customers aware of abuse problems and how your customer should deal with them. Kind regards, Frank -- -- Mit freundlichen Gruessen, -- MOTD: "have you enabled SSL on a website or mailbox today ?" -- PHADE Software - PowerWeb http://www.powerweb.de Inh. Dipl.-Inform. Frank Gadegast mailto:frank at powerweb.de Schinkelstrasse 17 fon: +49 33200 52920 14558 Nuthetal OT Rehbruecke, Germany fax: +49 33200 52921 ======================================================================
- Previous message (by thread): [anti-abuse-wg] 2011-06 Review Phase Extension
- Next message (by thread): [anti-abuse-wg] 2011-06 Review Phase Extension
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]