At the end of May, 2022, GMail discontinued use of standard authentication methods for POP3, IMAP, and SMTP connections. The available OAuth2 authentication mechanism in the latest SeaMonkey and Thunderbird for the OS/2 platform is unable to properly complete the authentication procedure with GMail, and will leave the application in a hung state.
There are several methods to work around this, but perhaps the easiest is simply to generate what Google calls an app password, which is, quite simply, a 16-digit passcode which gives a non-Google application or device permission to access your Google Account.
To generate the app password, follow the directions available here. Remember, that in order to do this, you must have 2-Step-Verification enabled for your account.
Once you have generated the app password, copy it to your clipboard. Open SeaMonkey Mail or Thunderbird, and access the server settings for your GMail account. Ensure that the authentication method is set for Normal password (Google will not accept encrypted passwords for this). Make the same change for the GMail SMTP server. Note that in both cases, SSL/TLS should be selected for the connection security, and specifically not STARTTLS. Close the settings dialog and attempt to access the account. You should be prompted for a new password. Paste the app password into the prompt.
To configure a second system to access the same account, simply paste (or type) the same app password. This technique should work for other mail clients, as well.
For questions, there is an informative discussion in the OS/2 World forum on this very topic.
Just as bare metal systems may benefit from updated drivers for their existing (or newly added) hardware, the emulation of hardware in virtual machines may change or may be better leveraged by OS/2-based guests (OS/2 Warp, eCS, or ArcaOS) by utilizing the latest drivers available from Arca Noae.
We have seen instances where virtual machines are configured with a sort of “set it and forget it” mindset on the part of the user, believing that hypervisor updates will not impact configured virtual machines. Unfortunately, this is not always the case. Various hypervisors (VirtualBox, etc.) may indeed alter the emulated PC BIOS and emulated firmware for other components (networking, USB, etc.).
If your virtual machines are running ArcaOS, keeping your ArcaOS Support & Maintenance subscriptions in force and applying the latest available updates will not only keep your drivers up to date, but the ArcaOS kernel, as well. In addition, other components of ArcaOS which affect usability may also be updated through subscription downloads (ArcaOS Desktop, bundled applications, etc.).
If your virtual machines are still running OS/2 Warp 4 or eComStation, keeping your OS/2 & eCS Drivers & Software subscriptions in force will allow you to keep your drivers current, as well as any other included content. (Note that kernel updates are not included in the OS/2 & eCS Drivers & Software subscription, as the ArcaOS kernel itself is not licensed for use with any distribution other than ArcaOS. If you have a need for the advanced features provided by the ArcaOS kernel, the best upgrade path is to purchase a license for ArcaOS.)
In conclusion, simply consider that virtual machines are, from the point of view of the operating system, just computers, after all, just like their bare metal counterparts.