From: Tassilo Horn <tsdh@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: ding@gnus.org
Subject: Re: gmail+imap+smtp (oauth2)
Date: Tue, 03 May 2022 08:27:48 +0200 [thread overview]
Message-ID: <87a6bzazp6.fsf@gnu.org> (raw)
In-Reply-To: <877d73duph.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
> [[S/MIME Signed Part:Undecided]]
>>>> "ESF" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> On Monday, 2 May 2022 at 08:45, Uwe Brauer wrote:
>>> There have been some discussion, either on emacs-devel or here, how to
>>> make emacs (gnus) work with gmail under those circumstances, that is
>>> using oauth2.
>
>> Uwe,
>
>> I had the same problem with our institution which uses Exchange and
>> moved to multi-factor authentication, i.e. oauth2. I solved this
>> problem by using davmail [1]. I don't know if this will work for gmail
>> as well but you may wish to try.
>
> Thanks, when we started with gmail, I tried out dovecot, and there was
> a problem, that it started to download every message over and over
> when I tried to download new email,
I'm using isync (mbsync) to have a bidi-synchronization between several
imap mail accounts (fastmail, gmail, work) and local maildir stores.
That's the gmail specific part of my ~/.mbsyncrc:
--8<---------------cut here---------------start------------->8---
IMAPAccount gmail
Host imap.gmail.com
User USER@gmail.com
# I have my credentials in ~/.authinfo.gpg in the form:
# machine imap.gmail.com login USER@gmail.com password APP_PWD force yes
# where APP_PWD is an application specific password one can generate
# somewhere in the Gmail/Google account settings.
PassCmd +"gpg --decrypt --no-tty --for-your-eyes-only ~/.authinfo.gpg 2> /dev/null | grep imap.gmail.com | sed 's/.*password \\([^ ]\\+\\).*/\\1/'"
SSLType IMAPS
IMAPStore gmail-remote
Account gmail
MaildirStore gmail-local
Path ~/.mail/Gmail/
Inbox ~/.mail/Gmail/INBOX
SubFolders Verbatim
Channel Gmail
Far :gmail-remote:
Near :gmail-local:
Create Near
Remove Near
Expunge Both
CopyArrivalDate yes
Patterns *
Sync All
SyncState *
--8<---------------cut here---------------end--------------->8---
I'm not sure if this application specific password thingy I'm using will
work in the future, though. But luckily I've moved away from Gmail in
the past years.
> besides it fill up my hard disk with additional 13 GB and that I would
> like to avoid. But maybe this will be the only way.
Both dovecot and isync usually do full synchronizations so you have
everything locally. I consider that a good thing because then you can
index it for quick local searches. But you can configure mbsync to sync
only specific folders. For example, I think many people exclude Gmail's
"All Mails" folder.
Bye,
Tassilo
next prev parent reply other threads:[~2022-05-03 6:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 6:45 Uwe Brauer
2022-05-02 11:33 ` Eric S Fraga
2022-05-03 5:57 ` Uwe Brauer
2022-05-03 6:27 ` Tassilo Horn [this message]
2022-05-03 6:33 ` Byung-Hee HWANG
2022-05-03 7:52 ` Eric S Fraga
2022-05-03 17:37 ` Bob Newell
2022-05-04 8:53 ` Eric S Fraga
2022-05-04 14:02 ` George Clemmer
2022-05-04 15:34 ` Uwe Brauer
2022-10-24 8:20 ` Jarmo Hurri
2022-10-24 17:13 ` Bob Newell
2022-10-25 7:36 ` Jarmo Hurri
2022-10-25 8:33 ` Eric S Fraga
2022-10-25 18:26 ` Bob Newell
2022-05-03 0:57 ` Byung-Hee HWANG
2022-05-11 16:24 ` Leo Butler
2022-05-13 8:50 ` Eric S Fraga
2022-05-17 16:29 ` Uwe Brauer
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=87a6bzazp6.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
--cc=oub@mat.ucm.es \
/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;
as well as URLs for NNTP newsgroup(s).