Scott Haneda wrote: > In the same way it would not be fair to target the owner of a building > if a kid sprayp aints profane graffitti on it... I do not think you > can go after the ISP for users who abuse their network. > > Most do their best. I spoke with Comcast and suggested port 25 > blocking or at least forced authentication to stop virus's from > zombied machines. > > Their valid point is how many users that would break email for because > they are not technically able to change settings in their email client. > > I find it extremely odd that anyone at Comcast would make that sort of claim while Bellsouth/AT&T and others who are much larger as well as most smaller ISPs are doing exactly that, at least in the U.S. If you don't authenticate you don't send mail. I was told by several people whom I trust that Comcast does this also, but since I'm not on Comcast I can't say from personal experience so I'll have to do some more research in detail. However I do know that claiming that their users are 'technically unable' to make this change is at best ludicrous, at worst an out and out lie. I would be highly suspicious of your source on that info. I understand that things do change on a regular basis, but I would be extremely surprised to find the Comcast wasn't blocking 25. Most ISPs only allow SMTP to their mail servers for exactly this reason. Even if they don't force authentication they can track the source of whatever mail comes into the server if they want to bother.
------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
