I made my server listen on two ports now, but what about people that don't have control over their mail servers? On Tue, 2007-04-03 at 22:40 -0500, Brian D. Ropers-Huilman 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. > ________________________________________________________________________ Jon Schewe | http://mtu.net/~jpschewe Help Jen and I fight cancer by donating to the Leukemia & Lymphomia Society Here's our website: http://www.active.com/donate/tntmn/tntmnJSchewe If you see an attachment named signature.asc, this is my digital signature. See http://www.gnupg.org for more information. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20070404/e50106cd/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20070404/e50106cd/attachment.pgp