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/address-policy-wg@ripe.net/
[address-policy-wg] Re: please remove invalid abuse contacts
- Previous message (by thread): [address-policy-wg] Re: please remove invalid abuse contacts
- Next message (by thread): [address-policy-wg] Re: please remove invalid abuse contacts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
michael.dillon at bt.com
michael.dillon at bt.com
Thu Jun 4 15:02:36 CEST 2009
> > perhaps try ripe-tech at ono.es > > > The issue is I have no time to try and I would like the right > contact at the first try. > > How to ensure the whois database is accurate just after the > IP range registration ? You really need to get some education on how the Internet works. First of all, this IP range was never registered with RIPE because it is from an APNIC allocation. Secondly, this email address was probably accurate at the time of registration. In fact, it was probably accurate two days ago as well. The email address exists and is active on an email server which replied to you that the mailbox is full. This often happens when a spammer starts sending email from a new source, and a flood of complaints fill up the mailbox during the next few hours. Thirdly, it is not your responsibility to police the APNIC database or the RIPE database. Fourthly, people who understand the dynamics of SPAM attacks, also understand why mailboxes are full, and since there are already lots of complaints, they decide that there is no point in adding one more complaint. Instead, they block that IP address (or IP address range) from their email servers for a few days. Finally, this RIPE address policy working group does not have the powers to create policies which police the APNIC database, and probably not even the RIPE database, because policing is not really in scope for RIPE. If there is some technical reason why you cannot solve this issue by blocking traffic from the IP address range of the source of the SPAM, then your only logical course of action is to contact the upstream peers of the SPAM source ISP and ask those peers to block your address range from receiving packets. Generally you only want to do this if it is a DDoS. --Michael Dillon P.S. Once evening, a policeman notices a man crawling on his knees searching for something under a lamppost. "Excuse me, sir, have you lost something?" he says. The man replies, "It's my car-keys, I dropped them". The policeman gets down on his knees and helps to search. After a moment, he says to the man, "Are you sure that you dropped them here?". "Oh no, says the man, I dropped them way down the street but it is too dark there to see anything so I came here under the street lamp where it is easier to see.".
- Previous message (by thread): [address-policy-wg] Re: please remove invalid abuse contacts
- Next message (by thread): [address-policy-wg] Re: please remove invalid abuse contacts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]