Slashdot Mirror
Comcast Gets Tough on Spam
WeakGeek writes "The Washington Post is reporting that Comcast, the nation's largest broadband ISP, has started blocking port 25 to reduce Spam. Jeanne Russo said Comcast is not blocking port 25 for all its users because it does not want to remove the option for legitimate customers who process their own e-mail. So the company is monitoring traffic and picking out machines that look suspicious. By blocking port 25, they say they cut Spam by 20% last week." ZDnet has another article, with a nice statistic: Comcast generates 800 million email messages/day, but only about 100 million of those are sent through Comcast's SMTP servers.
...how about they start block ports 1080 and 2280? I often see horrific trolls invading the IRC networks and channels we inhabit, triggering mass K-lines by inviting people to juped channels, flooding, mass-noticing and trying to piss people off in general. And everytime I check these trolls' hostmasks, oh! - it's Comcast.
:-( Since SOCKS is also a generic relay protocol, it could be used for spamming too!
A lot of Comcast users seem to be running as SOCKS proxies for some reason.
God. Then freakin' prioritize.
.001% of broadband subscribers who run their own mail servers seem to think that blocking port 25 is the same as armageddon. If port 25 causes you so much damn trouble, then switch ISPs when it gets blocked. Just let me and the other average users out there reduce our spam without you having a hissy about it.
Do you prefer having your own email server?
Or do you prefer having twice as much spam?
Seriously, shut up. The
Comment of the year