From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Seamonkey automatic email download after switch to Oauth2
Date: Thu, 2 Jun 2022 20:45:11 -0500 [thread overview]
Message-ID: <33106514-ceee-9041-88de-aed91f414a10@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
Howdy,
Early this morning Seamonkey could no longer fetch emails. It wouldn't
accept the username and password. I did some searching and it seems
that Google is disabling plain text username and password. Honestly,
sounds like a good idea really. During my searches, most recommended
OAuth2 so I switched to it. I'd never heard of it before but dove in
head first. Turns out, easy enough. When I hit Get Msgs after changing
the settings, it asked for the password and it started downloading
emails. My first thought, yeppie!!
After a while, I noticed it wasn't downloading new emails
automatically. I have it set to check for new messages every 10 minutes
or so. I had to hit the Get Msgs button each time. I'd prefer it to do
it automatically. I tried restarting Seamonkey and even changing the
settings for doing it automatically, in case a config file needed
updating after the switch, still doesn't do it automatically. I'm
attaching a screenshot of the settings.
Does using OAuth2 disable automatically fetching messages or am I
missing some other setting? It worked fine until I switched to OAuth2
so I don't know what else it could be. Is there something better than
OAuth2 that gmail supports? I just picked the first option I found.
Thoughts??
Dale
:-) :-)
[-- Attachment #2: 2022-06-02-19-21-43-0001-scale.JPG --]
[-- Type: image/jpeg, Size: 191808 bytes --]
next reply other threads:[~2022-06-03 1:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 1:45 Dale [this message]
2022-06-03 8:53 ` [gentoo-user] Seamonkey automatic email download after switch to Oauth2 Michael
2022-06-03 9:31 ` Dale
2022-06-03 10:39 ` spareproject776
2022-06-03 10:07 ` spareproject776
2022-06-03 9:54 ` Michael
2022-06-03 11:15 ` spareproject776
2022-06-03 10:50 ` Michael
2022-06-03 11:57 ` Peter Humphrey
2022-06-03 14:57 ` Matt Connell (Gmail)
2022-07-23 18:58 ` Dale
2022-07-23 19:21 ` Wol
2022-07-23 20:50 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33106514-ceee-9041-88de-aed91f414a10@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox