|
Not to start a big argument about the issue, but just to reiterate my
stance on this...while blocking port 25 would work, it is unnecessarily
prohibitive. If my provider was to drop port 25 support, I would be
forced to move to a new provider immediately as would most around
here. I also get enough calls already from the few customers that
actually have E-mail hosting with my company when they can't send
E-mail or when E-mail isn't being received, only to find that they
aren't even using my server for SMTP. If they shut off port 25, there would still be hundreds of thousands of open proxies and other types of relays for spammers to hit, and to administrators like ourselves, this would have little impact. Most importantly though...if these guys find it difficult to relay their spam directly from such IP space, they will turn in greater numbers to relaying though the ISP's mail servers as they have already been doing, and spam relayed through legitimate mail hosts is difficult to score in comparison to a direct host, and many of the people around here are already giving legitimate mail hosts extra credit by using tests like SPF and AHBL-EXEMPT. I would personally much rather score Comcast zombies with 8 points for being DUL, 8 points for XBL, 4 points for BADHEADERS, 3 points for HELOBOGUS, 4 points for SPAMDOMAINS, 6 points for SNIFFER-PHARMACY, 3 points for GIBBERISH, 4 points for GIBBERISHSUB, etc., etc. The zombies that land in my hold file are almost always from obscure ISP's with untracked DUL space, or virus infected mail hosts. If people want to stop the problem, they should go out and arrest the dozen or so people at the root of every piece of zombie spam out there currently. There's a very limited number of criminals doing this. Matt Dave Doherty wrote: I know I don't see eye to eye with some folks here about this, but Comcast could prevent the problem entirely by blocking port 25 and putting some solid limits on outbound mail with a product like Ddeeclude Hijack...If they were really serious about fixing the problem, that is. -Dave ----- Original Message ----- From: "Dan Patnode" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 10, 2004 9:44 PM Subject: [Declude.JunkMail] Comcast Update -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ ===================================================== |
- Re[2]: [Declude.JunkMail] Filter Actions ... Roger Heath
- [Declude.JunkMail] Whitelist help Robert Grosshandler
- Re: [Declude.JunkMail] Whitelist help Matt
- RE: [Declude.JunkMail] Whitelist help Robert Grosshandler
- [Declude.JunkMail] SPF - Question Robert Grosshandler
- Re: [Declude.JunkMail] SPF - Question R. Scott Perry
- [Declude.JunkMail] Comcast Update Dan Patnode
- Re: [Declude.JunkMail] Comcast Up... Matt
- Re: [Declude.JunkMail] Comcast Up... Dave Doherty
- Re: [Declude.JunkMail] Comca... Matt
- Re: [Declude.JunkMail] C... Gerald V. Livingston II
- Re: [Declude.JunkMail] C... Matt
