On Mon, 3 Oct 2005, bobgir2004 wrote: > >> > >> Read and understood your explanation, below, and made those changes to > >> my Advanced Sending Options. > > > > That was neither Scott nor John who wrote what you quoted below, it was me. > > Please keep your attributions accurate. > > Larry - > > That was sloppy on my part. The road to hell is indeed paved with good > intentions. I always try to respond with a "thank you" to folks who help > out and this is what sometimes happens in threads that go on for awhile: > i.e., I thank the wrong party. My bad. :( > > Think in the future I'll just respond with a direct email so I don't > make that mistake again.
We all make mistakes. I shouldn't have been so sharp in my response as well. > Can you tolerate one more question? Of course. > Which is: I have shared the information on changes to the Advanced > Sending Options of Entourage with several friends who are Mac users and both > essentially responded: > > > I see what has been recommended and done. This may be fairly specific > > to > > Earthlink but certainly seems worthwhile if it accomplishes the privacy > > mission. I guess what¹s not crystal clear to me though is why this works! It's not specific to Earthlink. It will work with any mail server that accepts connections on port 587. Without getting too technical (although that's tough to avoid), in the world of TCP/IP, certain ports in a connection have well defined purposes. You've seen us refer to port 25 which is defined for SMTP. SMTP is the protocol for one mail server to talk to another mail server. In other words, when one computer connects to another, it should either find a mail server speaking SMTP on port 25 or nothing at all. Likewise, port 110 is defined for POP3, the protocol for retrieving e-mail and port 80 is for HTTP (web servers). Above, I said SMTP is for mail server to mail server. But you probably know that most e-mail clients by default send via port 25. That's because for purposes of sending, they act like a mail server rather than a client. Now I'm not totally sure of the chronology of the rest but over time, extensions to SMTP were developed to allow, among other things, authenticated sending via port 25. But unfortunately, SMTP is still largely insecure. So also developed were the standards for the submission port, 587. Submission meaning the initial injection of a mail message from a client into the SMTP world. Done properly, the submission port should always require authentication and may (must?) require encryption (which with Entourage 04, will be handled transparently for you just as it is with secure https sites in all modern web browsers). And if encrypted, then it also eliminates that whole issue of the hotel's ISP or anyone else intercepting the message. The nice thing about using port 587 is if your ISP supports it, you can use it all the time and do away with the settings dance when you travel. Since port 587 should always require authentication, there is no reason for an ISP to block it since their goal in blocking port 25 is to stop viruses that connect directly to the destination mail server which obviously needs to be unauthenticated since the sender will usually not have an account there. > Again, many thanks for your crystal clear instructions. You're welcome. -- Larry Stone [EMAIL PROTECTED] -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
