On 4/3/07, Brian D. Ropers-Huilman <brian at ropers-huilman.net> wrote: > On 4/3/07, Jon Schewe <jpschewe at mtu.net> wrote: > > Has anyone else run across this? As of today I'm no longer able to send > > mail through my mailserver (mtu.net) port 25 as comcast is blocking all > > outgoing connections on port 25 for "my protection". > > This is a fairly common practice to prevent you from using mail > servers that are not their own. One easy solution is to setup your MTA > to listen on another port (I've used 2525) or to send via SSL/TLS as > they never think to block 465. Well, he said outgoing. The "proper" way to do this is to configure your MTA to relay your mail to your comcast SMTP server, and everything will work just great. You can still use SSL/TLS, but that only fixes stuff for incoming. And IIRC, Comcast shouldn't block 25/tcp into your server, so it should not interfere with receiving (or sending from outside your LAN). -jth