On 22 Jun 2000, at 8:09, Greg Woods wrote:
> What he apparently did, and I've seen this pattern a lot which is why I
> brought this up, was do a traceroute back to what he *thinks* is the
> source, and blast a complaint to postmaster at every domain that turns
> up in the traceroute. So the answer to your question here is no, he
> did not contact the originating site first.
This is almost certainly what happened. The thing is that the "moral
outrage" of a lot of the spam-haters often exceeds their technical
prowess, and so rather than work harder [or learn more!] so that they can
really try to figure out whence the spam, they take the easier course:
they try to find EVERY host that could _possibly_ have touched the
messages [even obviously incorrect and bogus ones] and just complain to
*EVERYBODY*. They figure that among _all_ of those folk *some* sysadmin
will be the actual culprit... hassling other folk unnecessarily and
inappropriately almost certainly doesn't register high on their list of
concerns...
We get occasional spam complaints with an incredible "laundry list" of
[apparently random] hosts in the address list. In one case, we got a
spam complaint because were were the domain-contact of one of the
[forged!] host addresses in one of the header fields...
/Bernie\
--
Bernie Cosell Fantasy Farm Fibers
mailto:[EMAIL PROTECTED] Pearisburg, VA
--> Too many people, too few sheep <--
