From: worldoff9908@gmail.com   
      
   DICK HOFFMAN wrote:   
   > I went back to Smith's post and reread it carefully. Then I looked at   
   > the SeaMonkey server settings for my Hotmail account again and found   
   > that I had not set my email address correctly in the SMTP settings. I've   
   > fixed that and now emails seem to be going through correctly. Had to be   
   > some little thing that I overlooked. Thanks for the r   
   sponses I got   
      
   Glad to see that that helped.   
      
   I don't do anything with Hotmail, but I do a lot of support work with   
   corporate implementations of mail hosted at Microsoft. I think that for   
   the most part, the only difference between the two is the name of the   
   servers use, and otherwise, the methodology is all the same.   
      
   With any mail server, you need to have the correct params for each   
   connection, both inbound and outbound -- your ID and password, the name   
   of the server, the correct port number, and the correct designation for   
   connection security the authentication method.   
      
   I would guess that the majority of mail servers use SSL/TLS and port 993   
   for IMAP (995 for POP) and 587 and STARTTLS with SMTP, and with   
   connections encrypted, then the Authentication method is usually   
   "normal", where login credentials are protected by the encryption. Any   
   other settings are unusual, and typically used in more specialized cases.   
      
   However, with the overall push to connectivity that includes Multi   
   Factor Authentication, it's now getting to be really common that servers   
   have switched to authentication via OAuth2, where a saved OAuth2 token   
   becomes the second factor. If that token is in place, then you don't   
   have to jump through hoops of things like codes sent through SMS or   
   email, or making use of TOTP authenticator apps with a smart phone.   
      
   Although there are some providers that allow you to set up a "secondary   
   password" (one that is saved into your mail client and different from   
   the password if you're making access interactively through a web   
   connection), OAuth2 is becoming more-or-less standard. Among other   
   things, Gmail also uses OAuth2, but I think they implement it slightly   
   differently than Microsoft does.   
      
   There are times that it can take more effort than seems necessary to get   
   the token created, and with both Seamonkey and Thunderbird, I've found   
   that there are occasions that a token suddenly doesn't work. Most often,   
   the work-around is, as I suggested previously, deleting the saved token   
   and letting it re-create through a fresh login process.   
      
   Smith   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)