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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
- Previous message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
- Next message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jørgen Hovland
jorgen at hovland.cx
Thu Nov 11 09:55:20 CET 2010
On 11/10/10 17:42, Frank Gadegast wrote: > > I simply want ONE clearly defined contact instead of the messy > whois we currentyl have. But making things mandatory doesn't solve poor design. > Not at all. > We report all spam our customers receive. My ideas about this is probably a bit drastic, but I usually never report spam unless I know the ISP/system because it doesn't make any sense. We do however block it (the spam, not the ISP). It doesn't give us any benefits to report it. We get paid to filter spam. If I reported it the spam would stop. That's bad for business. > All password-checking, Why are you reporting that? We have things like that constantly 24/7. In a perfect world, your system should be designed to filter this instead. > sniffing I'm not sure if I understand what this means, but you would probably spend your time changing passwords instead of complaining that somebody stole them. Nevertheless, this would be a case for law enforcement if it's so important. > and DDoS-Attacks > Seriously. The 90s just called. They want you back. > And we currently: > - cannot find the abuse address without mistakes > - cannot be sure that our complaint reached the one beeing officially > responsible (simply because he filed the mandatory field or object) > - and cannot detect if the receiver is not interested, lazy or > spammer friendly, out of office or whatsoever > > And this is simply because there is no mandatory field ... > > I think people often mix contact information with abuse contact information. Sometimes it's the same, sometimes not. Some people don't understand the difference and some people don't care and mail everyone anyway. This is where the database design/language perhaps could be improved. Contact information is to me more important than abuse contact information because it lets me get in touch with the legal entity. Remember that a complaint is just a message saying you are unhappy with something. You can never expect anyone to reply or even do anything about it, and they have their fully right to do so.
- Previous message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
- Next message (by thread): [anti-abuse-wg] 2010-08 New Policy Proposal (Abuse contact information)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]