[118729] in North American Network Operators' Group
Re: dealing with bogon spam ?
daemon@ATHENA.MIT.EDU (Suresh Ramasubramanian)
Tue Oct 27 21:48:29 2009
In-Reply-To: <Pine.LNX.4.61.0910272126030.22812@soloth.lewis.org>
Date: Wed, 28 Oct 2009 07:17:43 +0530
From: Suresh Ramasubramanian <ops.lists@gmail.com>
To: Jon Lewis <jlewis@lewis.org>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Seen it before - but mostly for malware rather than for spam. And
certainly not long enough / persistent enough for a full fledged spam
campaign (4..5 days rather than a day or two at the most when people
start noticing and dropping the bogus announcement)
On Wed, Oct 28, 2009 at 6:57 AM, Jon Lewis <jlewis@lewis.org> wrote:
> Unallocated doesn't mean non-routed. =C2=A0All a spammer needs is a
> willing/non-filtering provider doing BGP with them, and they can announce
> any space they like, send out some spam, and then pull the announcement.
> Next morning, when you see the spam and try to figure out who to send
> complaints to, you're either going to complain to the wrong people or fin=
d
> that whois is of no help.
