See http://www.pmail.com/newsflash.htm

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Sounds good, so perhaps for Pop3 it could be a solution. But I think even with IMAP you are working again on the google servers and not local anymore. :( But regardless of this, I think for google the creation of an app passwords will be a good mid term solution. At the moment I found no announcement from google that it will not work anymore after they will force next month 2FA and the deactivated of option "use of less secure apps". And "app password" is mentioned explicit as fix for the 30th May changes, see here: https://support.google.com/accounts/answer/6010255?hl=en#zippy=%2Cif-less-secure-app-access-is-on-for-your-account%2Cif-less-secure-app-access-is-off-for-your-account

[quote="pid:53872, uid:29380"]But I think even with IMAP you are working again on the google servers and not local anymore. smile[/quote] The point is whether a _third party_ can access the authenticated user's data which isn't the case with IMAP either unless running a client-server network with the (like your employer's) server being the "man in the middle", so using Mercury this way would most likely be a different thing. As long as only you (via you local Pegasus Mail client) and the mail hoster are accessing your data there is no third party involved (as far as I understand it).

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C