Last time I checked, your ISP has to allow port 25 outbound to arbitrary locations (i.e., outside the ISP's network), in order to run an SMTP server (on the Internet at large).
Cox blocks port 25 beyond the ISP's network.
You might be able to set up an SMTP server somewhere else (where port 25 out is allowed), and then send it messages from home (encrypted, most likely) using another port.
Without port 25, though, those messages are going nowhere fast!
I think they should re-cut the cable, and cut the other ones going to India, too.
That way, I won't have to try to understand some Indian call-center person reading straight out of a book - and them not understanding I have more IT knowledge than the average sheep the book was written for.:p
Slashdot Mirror
Umm, no...
Last time I checked, your ISP has to allow port 25 outbound to arbitrary locations (i.e., outside the ISP's network), in order to run an SMTP server (on the Internet at large).
Cox blocks port 25 beyond the ISP's network.
You might be able to set up an SMTP server somewhere else (where port 25 out is allowed), and then send it messages from home (encrypted, most likely) using another port.
Without port 25, though, those messages are going nowhere fast!
Not able to secure port 25? Donkey balls.
I'm sure that an authentication scheme can be implemented just as well on an SMTP server using port 25, as any other port.
If anything, the fact that keyword filtering is going on, just makes me push people harder to adopt encryption.
I think they should re-cut the cable, and cut the other ones going to India, too.
:p
That way, I won't have to try to understand some Indian call-center person reading straight out of a book - and them not understanding I have more IT knowledge than the average sheep the book was written for.