[54143] in North American Network Operators' Group
RE: Spam. Again.. -- and blocking net blocks?
daemon@ATHENA.MIT.EDU (Scott Silzer)
Tue Dec 10 20:41:48 2002
In-Reply-To: <20021210234116.AAA26396@shell.webmaster.com@whenever>
Date: Tue, 10 Dec 2002 20:39:12 -0500
To: David Schwartz <davids@webmaster.com>
From: Scott Silzer <scotts@primus.ca>
Cc: "'nanog@nanog.org'" <nanog@nanog.org>
Errors-To: owner-nanog-outgoing@merit.edu
That is exactly what was done to to Futureway a third party spammed
for a site hosted by a downstream ISP and the result was there entire
network begging blacklisted by SPEWS.
At 15:41 -0800 12/10/2002, David Schwartz wrote:
>On Tue, 10 Dec 2002 15:45:29 -0500, Scott Silzer wrote:
>
>>I could understand if an ISP was allowing spam from a portion of
>>there network. But in this case the only thing that the ISP did is
>>host a website, the SPAM was sent from from a third party's network.
>>The ISP did terminate the customer but in the meantime the entire
>>NSP's network has been blacklisted, for a rouge webhosting account
>>does sound a bit harsh.
>
> A spam blocking service that worked that way would be
>useless. Anyone could
>get any site they didn't like blacklisted simply by spamvertising it. Anyone
>who uses a spam blocking list that works that way is DoSing themselves.
>
> DS
--
Scott A Silzer
