Comcast looking for competent SysAdmins?

[Collins Richey]

On Fri, 05 Sep 2003 21:12:17 -0600
Andrew Mathews <andrew_mathews at linux-works.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> <rant>
> As of today's count, Comcast now has 1783 ip addresses that I've
> automatically blocked for being a spam source in the last week. These
> people have got to qualify for the #1 $LUSER and having a totally
> fscked up system. I have NO sympathy for anyone whose email is blocked
> because they use these arseholes for an isp. No, I WON'T accept 800+
> spam messages a day to receive a couple from legitimate people.
> </rant>
> 

Not being an email ISP myself, I would love to hear more (exact details)
about how this works.  How do Comcast ip's become a source of spam?  How
would a Comcast sysadmin go about rectifying the situation?

I've been an ATT/COMCAST subscriber for about 5 years now, and they
certainly provide a reliable broadband offering.  Until about 6 months
ago, I never heard about these complaints.  I've never noticed anything
other than very occasional spam on any of the mail groups that I
subscribe to, but one group that I subscribed to as ATT now blocks any
traffic from me on COMCAST.

COMCAST may be an arsehole ISP, but it would be nice to know what that
really means instead of just slinging names.  I find it rough that I
would need to pay for an additional ISP just to play email, since
COMCAST provides what I consider to be an excellent service.


-- 
Collins Richey - Denver Area
if you fill your heart with regrets of yesterday and the 
worries of tomorrow, you have no today to be thankful for.