I was always under the impression anyways that ISPs like Comcast did not allow any servers to be run period. Ironically I started using my own e-mail server way back when Mediaone/RoadRunner/AT&T/Comcast kept changing ownership so often I could not rely on having an e-mail address remain current for more than a year. I did get contacted at one point from I believe AT&T asking me if I was running a server, and if so to inform me I was breaking the TOS. Never responded back, and they were soon sold to Comcast or whoever after. In my opinion, if they did not keep changing the *#&@ domain name for e-mail so often, I am sure a few would not bother to run their own e-mail. I think the lesson of the story is services like Comcast are just not reliable for anything. I know Comcast is one company that reportedly will monitor bandwidth, and if yours is excessive they will contact you on this, which kind of defeats the purpose of broadband in my opinion. Especially with the cities doing their own wireless shortly. -----Original Message----- From: Jon Schewe <jpschewe at mtu.net> To: "John T. Hoffoss" <john.t.hoffoss at gmail.com> Cc: "tclug-list at mn-linux.org" <tclug-list at mn-linux.org> Date: Wed, 04 Apr 2007 12:06:39 -0500 Subject: Re: [tclug-list] Comcast blocking port25 On Wed, 2007-04-04 at 11:48 -0500, John T. Hoffoss wrote: > 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). I think that's what got me into trouble in the first place as comcast was seeing a lot of mail traffic going through their server because I'm the backup MX for mtu.net. They are blocking all traffic both to and from port 25 on my machine. ________________________________________________________________________ Jon Schewe | http://mtu.net/~jpschewe [http://mtu.net/%7Ejpschewe] Help Jen and I fight cancer by donating to the Leukemia & Lymphomia Society Here's our website: http://www.active.com/donate/tntmn/tntmnJSchewe [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 [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/3b93adee/attachment-0001.htm