What's going on?

I've encountered some anti-spammers who would do half-
assed investigations, declare an ISP guilty, then
spread the word on private mailing lists shared
by all sorts of hackers, who are apparently looking
for an excuse to have fun and feel good about it.

Despite our policy of not allowing spams from our
network, we were labeled spammer friendly not too
long ago and a minor break-in happened the same
night. Just speculating, too.

Sanjay.

Tell me about it. In the course of today's activities, I
learned that one of our users with a small commercial web site
on one of our servers spammed the net from an account on
another ISP. The spam contained a pointer to his URL on
our server.

Some of the mail seems to be holding us partially culpable
for the spam. I'm happy to report that the other ISP is taking
action against the spam complaint, but I don't know of any
interpretation of Netiquette that condemns commercial WWW sites.
I don't know that I'd favor an abuse policy that encompasses
WWW sites, even if they are listed elsewhere in spam mailings,
but if there's a reasonable policy out there that contemplates
this type of situation, I'd love to know how it reads.

Sanjay Dani writes:

==>> Despite our policy of not allowing spams from our
==>> network, we were labeled spammer friendly not too
==>> long ago and a minor break-in happened the same
==>> night. Just speculating, too.

You might have been labelled spammer friendly.

However, AGIS openly proclaims themselves as a good place for spammers to
buy circuits.

Maybe networks should begin considering filtering routes with _4200_ ?

I will say that I believe AGIS is doing a severe injustice to their 'good'
customers who are getting caught up in Phil's antics. There are regexps
for procmail published daily which will happily send mail down /dev/null
if it comes from anywhere within AGIS's CIDR blocks.

Talking to their NOC does nothing because they've been told to not say a
word about their spam policies; it's an offense which warrants
termination.

Anyway, this is getting to the point where it should be mopped into the
regular drivel of inet-access...

/cah