Re: Fwd: BLOCK: RIPE
- Date: Mon, 23 Apr 2001 11:05:38 +0200
I wouldn't worry about it.
I think anybody who does that will undo it pretty soon all by them
selves.
(see last line of my .sig for more context :-)
Poul-Henning
In message <009FAF64.DFFEC796.9@localhost>, "Christian Panigl, ACOnet/VIX
/UniVie" writes:
> Hmmm, reasonable diligence or epidemic paranoia ?
>
> Just got this one forwarded, thought it might be worth letting you know
> ...
>
> Cheers
> CP
>
>================================
>X-Mailer: Forte Agent 1.8/32.548
>Message-ID: 6uu6ets5102thcbdrigof2l7urtmd2gmjl@localhost
>Date: Sun, 22 Apr 2001 20:48:13 -0400
>From: Daniel Norton danorton@localhost
>To: SPAM-L@localhost
>Reply-To: Daniel Norton danorton@localhost
>Sender: Spam Prevention Discussion List SPAM-L@localhost
>Organization: .
>Subject: BLOCK: RIPE
>
>RIPE's database is down for an indeterminate period of time. Since it
>might be impossible to determine an abuse contact address without the
>RIPE database, you might wish to consider blocking all RIPE traffic
>until they get things back in order. Here are the RIPE IP address
>ranges:
>
> 24.132/14
> 62/8
> 139.20/14
> 139.24/14
> 139.28/15
> 141.0/10
> 141.64/12
> 141.80/14
> 141.84/15
> 145.224/12
> 145.240/13
> 145.248/14
> 145.252/15
> 145.254/16
> 149.202/15
> 149.204/16
> 149.206/15
> 149.208/12
> 149.224/12
> 149.240/13
> 149.248/14
> 150.254/16
> 151.13/16
> 151.14/15
> 151.16/12
> 151.32/11
> 151.64/12
> 151.80/15
> 151.3/16
> 151.4/15
> 151.82/16
> 151.91/16
> 151.92/15
> 151.95/16
> 160.216/14
> 160.220/16
> 160.44/14
> 160.48/12
> 163.156/14
> 163.160/12
> 164.0/11
> 164.32/13
> 164.40/16
> 164.128/12
> 171.16/12
> 171.32/15
> 192.106.196/23
> 192.162/16
> 192.164/14
> 192.71/16
> 193/8
> 194/8
> 195/8
> 198.17.117/24
> 212/8
> 213/8
> 217/8
>
>--
>Daniel Norton
>
>----- End of forwarded message from Daniel Norton -----
>
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@localhost | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
- References:
- Fwd: BLOCK: RIPE
- From: Christian Panigl, ACOnet/VIX/UniVie" , db-wg@localhost, ripe-dbm@localhost