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/[email protected]/
[anti-abuse-wg] Policy disallowing spam from RIPE blocks
- Previous message (by thread): [anti-abuse-wg] Policy disallowing spam from RIPE blocks
- Next message (by thread): [anti-abuse-wg] Policy disallowing spam from RIPE blocks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Thu Mar 10 09:21:07 CET 2011
On Thu, Mar 10, 2011 at 1:23 PM, Frank Gadegast <ripe-anti-spam-wg at powerweb.de> wrote: > > BTW: spam farms are usally not a big technical problem, because > its easy to detect ranges with spam outbreaks. More problematic > are all those unprotected PCs out there with daily changing IP. > Its not a "technical" problem in that a smtp block or a nullroute solves it for you Now picture what happens when the ISP turfs whatever spammer got a /14 from them, or the RIR revokes a /20 that is full of malware C&C .. and then, months later, its reassigned to someone else. I would invite you to go explain how easy or difficult a technical problem it is, to whichever poor SOB gets that netblock. -- Suresh Ramasubramanian (ops.lists at gmail.com)
- Previous message (by thread): [anti-abuse-wg] Policy disallowing spam from RIPE blocks
- Next message (by thread): [anti-abuse-wg] Policy disallowing spam from RIPE blocks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]