google accounts in Seamonkey

[wim van helden]

Dear Forumites

Perhaps this has already passed this forum once, but I hope you will apologise a "newby" for asking again.

I have Seamonkey installed (under Windows 10) as my standard browser and mailclient. In the mailclient I have my primary mail account (a Dutch "xs4all.nl" domain) and several gmail accounts.

Since a couple of months I keep being bothered by a message, obviously from Semonkey, that states that the standaard port of Google (pop.gmail.com:995) tries to identify itself with incorrect information. The g-mail accounts have (for a part) been used for years now, so I cannot imagine that all of a sudden Gmail is abusing some security protocol (or whatever).

Has anyone seen this before, and hopefully solved it? (I cannot see how to attach a image file, I have the error message in jpg format available.)

Looking forward!

Wim van Helden, Holland

[LIMPET235]

Moving this to SeaMonkey Support...

[wim van helden]

I realised I should add some more details:

All my accounts are configured as "Pop mail accounts".

Every time I get the error message I am invited tot confirm a security exception which I do, but the same message keep coming.

I hope someone knows how to deal with it!

Wim van Helden

[hardys]

Please try to configure Gmail for access with "less secure apps"
https://support.mozilla.org/en-US/questions/1029976

[therube]

http://kb.mozillazine.org/Using_Gmail_w ... illa_Suite
https://support.google.com/mail/answer/ ... ic=7280141

[therube]

Is it possible that antivirus is interfering?

Maybe test in a new, clean Profile.
Set, ahead of time, to "leave messages on server" (so that when you test in this new Profile it won't affect getting [the same] messages in your regular Profile).

[wim van helden]

@Hardys: all my Gmail accounts have been configured for access with "less secure apps"
@Therube: I have already 4 Gmail accounts two of which have been started in the past months only (the earliest however is several years in service). In seems to me that something has been changed in the security settings of Seamonkey / Mozilla, which causes this problem, quite recently, but if that is the case more people should encounter problems I would guess.

STRANGE!!