I just checked with programmers again about this point.
They indicated that port 25 should work because it starts unencrypted but
then start-tls invokes up the encryption. If you use 465 it starts with
encrypting the channel right away (hence less chance for problems).
The documentation should be updated and changed within the hour.
Scott G. Thomas
Division Mgr, Computing Services
408A Computer Center
Michigan State University
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of Chris Wolf
Sent: Friday, December 19, 2003 11:34 AM
To: [log in to unmask]
Subject: Re: [MSUNAG] My mail.msu.edu SSL SMTP Port Weirdness
At 10:42 AM 12/19/2003, Doug Nelson wrote:
>Port 25 is correct for non-SSL, and 465 for SSL.
But the "client documentation" pages found at
say that, for example, with Outlook Express for Windows, you should choose
SSL, but use port 25 (not 465). I use this setting at home and it works
Similarly, I've discovered that Eudora for Windows does not actually require
the SSL settings indicated in the client documentation page. The Eudora
documentation there says to set your SSL settings to "Required, Alternate
Port", but for us it also works fine when set to "If Available, STARTTLS".
Can anyone explain what's going on here? Is there some other circumstance
that we haven't run into where SSL with port 25 in Outlook Express or the
"If Available, STARTTLS" setting in Eudora would fail to work?
Chris Wolf Computer Service Manager
Agricultural Economics [log in to unmask]
Michigan State University 517 353-5017