nanog mailing list archives
Re: Lazy network operators - NOT
From: Sean Donelan <sean () donelan com>
Date: Sun, 18 Apr 2004 22:39:49 -0400 (EDT)
On Sun, 18 Apr 2004, Doug White wrote:
Well, Paul did advance a methodology - blackhole them all <grin>
If Paul came up with a practical way to fix millions of compromised computers which didn't involve hiring entire second-world countries to talk grandma through the process, I think many people would be interested in talking to him. On the other hand, repeately shocking the rat regardless of what it does, just results in the rat sitting in the cage afraid to do anything.
I prefer to send a 550 IP blocked for USE - for resolution contact your service provider.
If you haven't noticed, the infected user doesn't notice this. However many other people with legitimate uses are frequently caught up in the collateral damage. That's why I keep advocating better ways to identify the specific sources of the unwanted traffic, even if they change IP addresses. That way you could positively block the infected computers from not only mail but anything else you don't want to supply (no more GOOGLE/YAHOO/CNN for you), without massive collateral damage. Then the cost-benefit equation would be closer. If you annoy a lot of people, lots of people can completely and positively ignore you. With better identification, you directly receive the benefit of keeping your computer clean. You eliminate the third-party dependency of needing to fix other's peoples mistakes in order to do your work. It also makes it easier for other people to take action, because the collateral damage is less.
The job becomes even more difficult when not everyone can agree on what is spam and what is legitimate.
Stop requiring people to agree on it. If you want to force third-parties to do stuff, you must define exactly what you want them to do or not do. On the other hand, if you have the power to make the decision yourself, you don't need to convince a third-party the activity was a violation.
Current thread:
- Re: Lazy network operators - NOT, (continued)
- Re: Lazy network operators - NOT Mike Jezierski - BOFH (Apr 18)
- Blocking Win95 hosts [WAS: Lazy network operators - NOT] Patrick W . Gilmore (Apr 18)
- Re: Blocking Win95 hosts [WAS: Lazy network operators - NOT] Matt Hess (Apr 18)
- Fingerprints (was Re: Lazy network operators - NOT) Sean Donelan (Apr 19)
- Re: Lazy network operators - NOT Petri Helenius (Apr 18)
- Re: Lazy network operators - NOT Paul Vixie (Apr 18)
- Re: Lazy network operators - NOT Jerry Eyers (Apr 18)
- Re: Lazy network operators - NOT Lou Katz (Apr 18)
- Re: Lazy network operators - NOT Rodney Joffe (Apr 18)
- Re: Lazy network operators - NOT Doug White (Apr 18)
- Re: Lazy network operators - NOT Sean Donelan (Apr 18)
- Re: Lazy network operators - NOT Doug White (Apr 18)
- Microsoft XP SP2 (was Re: Lazy network operators - NOT) Sean Donelan (Apr 18)
- Re: Microsoft XP SP2 (was Re: Lazy network operators - NOT) Brandon Shiers (Apr 18)
- Re: Microsoft XP SP2 (was Re: Lazy network operators - NOT) Petri Helenius (Apr 18)
- Re: Microsoft XP SP2 (was Re: Lazy network operators - NOT) Henry Yen (Apr 18)
- Re: Microsoft XP SP2 (was Re: Lazy network operators - NOT) Peter Galbavy (Apr 19)
- Re: Microsoft XP SP2 (was Re: Lazy network operators - NOT) Michael Painter (Apr 19)
- Re: Microsoft XP SP2 (was Re: Lazy network operators - NOT) Patrick W . Gilmore (Apr 19)
- Re: Microsoft XP SP2 (was Re: Lazy network operators - NOT) Paul Vixie (Apr 19)
- Re: Microsoft XP SP2 (was Re: Lazy network operators - NOT) John Kristoff (Apr 19)