From: josecss.es@gmail.com   
      
   El 05/11/2025 a las 17:25, NFN Smith escribió:   
   > Jota.Ce wrote:   
   >   
   >>   
   >> Anyway... Last year, SeaMonkey Mail worked without problems with   
   institutional mail account (MS 365 ecosystem). Since we are jailed, SeaMonkey   
   >> can't retrieve/send mails, but i can't really know why. Maybe they are   
   blocking the port? At home, that settings work as expected.   
   >>   
   >> Outlook works, ThunderBird works if i choose Exchange account, but not if i   
   choose POP acount (didn't try on IMAP).   
   >>   
   >> What could i do? Can SeaMonkey use Exchange mail servers? Can SeaMonkey   
   "steal" a ThunderBird account copying some files/folders? Is there   
   >> anything i can test/try? Is there any logs i could see to point to some   
   clue?   
   >   
   > As noted elsewhere in this thread, Seamonkey has no problems with Microsoft   
   servers for POP and IMAP.  Beyond the basic settings for IMAP   
   > (server=outlook.office365.com, Port=993, your user ID and password and   
   Connection Security=SSL/TLS) the key difference is in setting the   
   > Authentication Method to OAuth2.   
   >   
   > When you make a first setup of a Microsoft account and you use the setup   
   wizard, after you enter all settings correctly, at the end of the   
   > process, you should see a Microsoft-branded pop-up that requests your   
   password a second time.  After you enter the password the second time,   
   > then an OAuth2 token is created and saved in your passwords store. That's   
   the way that it's supposed to work, but there are sometimes   
   > complications.   
   >   
   > I've found that sometimes, things don't work -- it seems to be that there   
   are occasions when there's some sort of corruption related to the   
   > saved OAuth2 token. If that happens, then the thing to do is to go into the   
   password manager and delete any OAuth2 tokens for that account, and   
   > a subsequent connection attempt should generate a new Microsoft pop-up.   
   >   
   > Noted elsewhere in this thread is justification for OAuth2 and "Modern   
   Authentication" that includes the eye-rolling "for your security".  In   
   > this case, it's not just Microsoft's paternalistic attitude toward users,   
   but a real security enhancement, a way of doing 2-Factor   
   > Authentication, where the "something you have" is the OAuth2 token that has   
   been saved.  If you do setups in multiple places (e.g., a second   
   > profile, another mail client, another computer, etc.) each one will need to   
   have a unique OAuth2 token, and I believe that if you copy a profile   
   > (e.g., transfer to a new computer), you have to delete any saved OAuth2   
   tokens and let them be recreated.   
   >   
   > A further item with Microsoft servers is that they have a structure that   
   allows for Shared accounts.  In that, if an account is designated as   
   > shared, then it has a list of email addresses that are allowed to interact   
   with that account. From there, it is possible to set up a connection   
   > to the shared account that shows up in Seamonkey as just another mail   
   account.  It takes a little tinkering with the setup process to correctly   
   > generate the proper OAuth2 token, but it does work, and the result is that   
   there is no sharing of passwords for the shared account. From the   
   > side of administrator, it's easy to grant or deny access to the shared   
   account for specific users, and the admins have full logging, knowing who   
   > is using the account and access details.   
   >   
   > For what it's worth, use of OAuth2 isn't limited to Microsoft. Google is   
   doing that with Gmail, and it's getting common with other providers.   
   > Some may allow for "application password" that is different from the   
   password you use for an interactive connection, but OAuth2 is becoming a   
   > standard.   
   >   
   > However, for your issue, I don't believe that OAuth2 handling is the   
   problem, nor port issues, nor a config setting that can be borrowed from   
   > Thunderbird. It's a structural issue that is beyond the current capacities   
   of Seamonkey. Besides POP and IMAP, Exchange is a different protocol   
   > that is specific to Microsoft servers, and where that's used with   
   Microsoft-specific applications that are tightly integrated with the various   
   > tools that are bundled in the Outlook client. Not just email, but calendar,   
   as well.  Thus, something like a contact management database that   
   > allows generation and storage of email and tracking of calendar activities.   
   >   
   > Unfortunately, if an account is configured as an Exchange account on the   
   server, you have to be using a client that supports Exchange   
   > connections. Obviously, Microsoft assumes use of Outlook. I know that Apple   
   Mail supports Exchange, and I believe that it's still possible with   
   > Evolution (although more difficult than it used to be). Thunderbird is   
   working on direct support, although that's something that is evolving   
   > with successive mainstream releases (and not the ESR track), and it's not   
   fully active yet -- I don't see that being truly "ready for prime   
   > time" until at least the turnover of the next ESR cycle next June.   
   >   
   > The one way that I know that it's possible to get Thunderbird to interact   
   with Exchange is through a paid extension called OWL. But until   
   > Thunderbird completes its own work for Exchange support, OWL may be the only   
   reliable option.   
   >   
   > For you, it seems that the Exchange server has been configured to allow only   
   Exchange connections, and it's entirely possible that they've   
   > disabled IMAP and POP.  If that's the case, I agree that it sucks,   
   especially if you don't have any felt need to do all the interaction with the   
   > Microsoft stack, and only want the ability to send and receive mail.   
   >   
   > But if the server is configured to not allow POP or IMAP connections, and   
   requires everything to be done with Exchange connections, then using   
   > Seamonkey is not an option now, and probably never will be.  In   
   Thunderbird, the process for adding Exchange support has been a several-year   
   > project, and I'm doubtful that the maintainers of Seamonkey have the   
   resources to replicate. And even with OWL, that won't be possible in   
   > Seamonkey unless/until Seamonkey is able to support WebExtensions, something   
   that is also not expected any time in the near future.   
   >   
   > For your particular situation, your options are probably limited to using   
   Outlook, or using Thunderbird, whether the Exchange support is mature   
   > enough in the main release version, or paying for OWL.   
   >   
   > Smith   
   >   
   Thanks for your time, writing a so descriptive answer.   
      
   Just for clarification...   
     - POP/SMTP servers for that "365" account are working at home. In my   
   workplace, if i remove Ethernet cable, and use a WiFi adapter with a   
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)