To add one more observation, we seem to find now that Eudora 6.01 will send with either port 25 or 465. This was not true six months ago; at that time our tests with port 25 failed. At 12:24 PM 8/18/2004, Wendy Tate wrote: >Last week I didn't make any changes on my end, but I suddenly couldn't send >mail anymore until I changed my port to 465. > >I noticed the timing of my problem correlated with the mail team's posted >tape library problem. I assumed they had needed to restart the mail system, >and that my having to change ports happened as a result of that restart. > >This is just an alternative theory, because I know I have been sending mail >both on and off campus continuously, and I've got records of outgoing >off-campus mail I sent successfully just a couple of days before I >unexpectedly had to switch to port 465. > >Beats me, though... > > > >Wendy Tate >Network Coordinator >Department of Economics >W. 147 Owen Hall >Michigan State University >East Lansing, MI 48825-1109 >517-355-1816 >[log in to unmask] > > >-----Original Message----- >From: MSU Network Administrators Group [mailto:[log in to unmask]] On >Behalf Of Richard Wiggins >Sent: Wednesday, August 18, 2004 12:01 PM >To: [log in to unmask] >Subject: Re: [MSUNAG] mail.msu.edu SMTP port > >I have recent experience that corroborates what Ed surmises. On a new >computer running Windows XP Pro, I installed Office 2003 and attempted >to send mail via Outlook. It failed consistently when sending via >mail.msu.edu. I had it configured to use port 465 directly. I did an >Office Update, and Outlook sends via mail.msu.edu just fine now. > >/rich > >On Wed, 18 Aug 2004 11:32:06 -0400, Ed Symanzik <[log in to unmask]> wrote: >> mail.msu.edu listens on both ports. Port 465 is SSL encrypted only. Port >25 >> uses TLS to switch to encryption. I have found no consistent behavior >from >> clients explaining when they need one or the other. Your own >configuration, for >> example, uses port 25 then, with no apparent reason, needs port 465. >(this is >> with Eudora?) >> >> A wild guess for you is that for 4 weeks you were sending mail to users >@msu.edu >> which does not require authentication and encryption. At week 4 you sent >to a >> non-msu.edu address and relay was denied. >> >> Another wild guess is that there is some auto-patch from MS that causes >things >> to work differently. >> >> -- >> Ed Symanzik >> MSU Mail Team >> [log in to unmask] >> --Chris ============================================== Chris Wolf Computer Service Manager Agricultural Economics [log in to unmask] Michigan State University 517 353-5017