| William H. Magill on Fri, 1 Nov 2002 03:20:04 -0500 |
|
On Thursday, October 31, 2002, at 06:13 PM, Jason Costomiris wrote: At my place I've got a cable modem from Comcast. My parents have Verizon DSL. When reading and sending mail from my place (using Mail.app on Mac OS X 10.2.1), everything works perfectly. However, from my parents' house, I can read fine using IMAP/SSL, but sending mail fails every time.
I gather that you are talking about some sort of PowerBook which you are taking from one location to another. That it reads and sends mail in one location, but only reads mail in another. My mail server is running RH 7.3 with Postfix 1.1.11 with TLS and SASL support built in. SMTP connections from my client to the system are done over TLS and authenticated using the SASL LOGIN method. When on the Verizon DSL and connecting to the mail server, the connection gets established, and the DATA command *seems* to be fine, but eventually times out. Of course, pointing to Verizon's smtp server doesn't help, because they only allow @verizon.net and @bellatlantic.net email addresses to use their mail relays. One assumes that you are using DHCP to obtain an IP address unique to each network, but retaining/using the same DNS name in both locations. The implication here is that when you take your @comcast.com DNS name and address over to another network, (ie Verizons) mail doesn't work completely. [The Verizon relay issue makes perfect sense in that context.] I assume that your RedHat mail server is NOT configured as a peer on the Internet, but rather one that feeds all outgoing mail back up to a Comcast mail server for distribution. [Last I checked, Comcast still prohibits you from running any kind of server on your "Comcast@home" setup. If you want to run any kind of server, you need to upgrade to "Comcast@work"... and send them more money.] Now that I'm back @ my house, everything's working normally. Anyone know of issues with Verizon's DSL network and SMTP servers that are outside of Verizon's network? If my assumptions are correct, I would look to blame Comcast, not Verizon. This is coming to you from an iMac via Bell Atlantic DSL (yes, it's that old.) However, I do use DCAnet as an ISP, so its not exactly Verizon DSL -- I have static IPs. I run a local mail server under my own registered domain. [My mail server happens to be an Alpha running Tru64.] I haven't used the iBook from the outside world now since 10.1, so I can't say for certain what Jaguar has done/does (if anything). However, way back then, I used the iBook fairly frequently from various hotel DSL-DHCP setups without problems. I would expect your configuration to work locally on Comcast since that is what it is configured for. However, I would guess that if you had a Verizon configured setup, you would encounter the same problems. I would guess that if you configured your PowerBook to use the Comcast mail server and used it on Verizon's network, that it would work. My experience with Consumer Cable modem setups (ie @home) in general has been that they are far more restrictive than ISP based DSL. "Always on" does not make you a Peer on the Internet. Commercial Cable modem setups (@work) on the other had are (or can be) a different story. Also, Comcast service has always been far more restrictive than Time Warner's RoadRunner service in Philadelphia. T.T.F.N. William H. Magill magill@mcgillsociety.org magill@acm.org magill@mac.com _________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|