On Wed, 2007-04-04 at 13:10 -0500, Brian D. Ropers-Huilman wrote: > On 4/4/07, John T. Hoffoss <john.t.hoffoss at gmail.com> wrote: > > On 4/3/07, Brian D. Ropers-Huilman <brian at ropers-huilman.net> wrote: > > > 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). > > Yes, there is some confusion here. I was assuming he has some mail > agent trying to send a message (whether a client or an MTA). As has > been hashed out here, most ISPs only allow :25 traffic to pass to > their own servers. For many people this is just fine, but some people > want their mail to come from their own MTAs. With :25 "blocked," the > only other solution is to point to another port. For example, my > Alpine client can quite happily send mail directly through my MSI > servers via :465. Yes, one reason for needing to send mail through another outside server are mailman lists that check the from and if it doesn't match up, reject the message. Sending all of my mail through smtp.comcast.net would cause this problem. Allowing my mailserver to accept mail messages on another port has allowed me to get around this problem. Is it just the case that now everyone that uses mailing lists sends mail through the ISP's servers (and thus uses that address for subscription) or uses some type of web based email? This assumes that the population that would like to use an alternate email address and doesn't run their own mailserver is somewhat large. > If, however, the situation is that he's running his own mail server at > home, then, yes, things are quite different. He's explained that he's > an MX for mtu.net and I do not see any clear solution to him running > an SMTP on a box in his home. This is the second problem. There hasn't been enough traffic to draw attention to myself, probably because I was using mtu.net as my smart host. Now that I switched it to help on some other issues comcast has noticed and I need to rethink where to host the secondary MX. My ability to send email apparently has been collateral damage. ________________________________________________________________________ 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 -------------- 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/7fda99cb/attachment.pgp