Antispammers and Abuse-C
Dear antispammers! Could you be so kind as updating your software to match the algorithm, developed by the incredible RIPE people. May I help you?
Again and again we get abuse mails about IP adresses of our customers. But we inserted the correct abuse-c entries into the RIPE DB.
The reason is simple: If you ask the RIPE DB for such an IP, you will get two contraticting results:
$ whois -h whois.ripe.net a.b.c.d | fgrep -i abuse % Abuse contact for 'a.b.c.x - a.b.c.y' is 'firstname.lastname@example.org' abuse-mailbox: email@example.com
Ok, we created the problem by ourself: The tech-c of many inet*num is the abuse-c of our own org object.
That might be a masochistic approach, but it really help to detect the corner cases in the programms of anti-abuse activists. Such bugs need to be fixed, simply because you have to be correct yourself if you are going to complain somewhere.
I do fill response forms and even phone those activists in order to get their software fixed. Usually I get upset after half an hour.
So let me summarize: Either you are grep the "Abuse contact ..." comment provided by RIPE or you implement the correct algorithm:
#! /bin/sh getripe="whois -h whois.ripe.net --" $getripe -rL -T inetnum,inet6num "$1" | egrep '^org:' | while read ot ov; do $getripe -r -T organisation $ov | egrep '^abuse-c:' | while read at av; do $getripe -r $av | fgrep abuse-mailbox done done | tail -1
It is really that hard?
Total 2 comments