From: "Jason Gunthorpe" <jgg@ziepe.ca>
To: Ludovic.Desroches@microchip.com
Cc: konstantin@linuxfoundation.org, users@linux.kernel.org,
tools@linux.kernel.org
Subject: Re: [kernel.org users] B4 and gmail integration features
Date: Fri, 27 Mar 2020 10:46:25 -0300 [thread overview]
Message-ID: <20200327134625.GV20941@ziepe.ca> (raw)
In-Reply-To: <93abb185-edc7-6edb-11e8-a1bd0b2b6bbe@microchip.com>
On Fri, Mar 27, 2020 at 01:34:39PM +0000, Ludovic.Desroches@microchip.com wrote:
> On 3/27/2020 2:14 PM, Jason Gunthorpe wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Fri, Mar 27, 2020 at 12:53:57PM +0000, Ludovic.Desroches@microchip.com wrote:
> >> On 3/23/2020 1:16 PM, Jason Gunthorpe wrote:
> >>> On Fri, Mar 20, 2020 at 05:45:32PM -0400, Konstantin Ryabitsev wrote:
> >>>> Hi, all:
> >>>>
> >>>> For my next B4 trick, I plan to add some basic gmail integration --
> >>>> since I know many of you do use gmail.
> >>>
> >>> FWIW, I've done some work on this here to avoid the 'OAUTH Apocalypse'
> >>> that is coming. You may find the oauth code helpful:
> >>>
> >>> https://github.com/jgunthorpe/cloud_mdir_sync
> >>
> >> Thanks a lot for this tool. We have an Exchange server with IMAP support
> >> disabled recently. It has broken my mail workflow.
> >
> > Yes, we are looking to a similar future.
> >
> > I hope in a month or so I can show how to make IMAP work again with an
> > OAUTH helper, but this tool turned out well and is nicer than mutt's
> > built in IMAP or mbsync..
> >
> >> I didn't play much yet with your tool but first tests are encouraging to
> >> be able to use notmuch and mutt again.
> >
> > Consider it 'beta' at the momement, would be interested in feedback
>
> Sure. I already have one question. I noticed that if I remove a mail
> from the server, it is also removed locally. That's good as I deal with
> my mails on two computers. I wonder how it will behave with email
> retention? I fear it removes the mails from my local maildir...
Right, the local maildir always matches the cloud mailbox, and extra
local mails are deleted to make them match.
Keeping a local archive would need some new feature - for instance to
de-dup and insert encountered messages into a public inbox.
Jason
prev parent reply other threads:[~2020-03-27 13:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 21:45 B4 and gmail integration features Konstantin Ryabitsev
2020-03-20 21:49 ` [kernel.org users] " Johannes Berg
2020-03-20 22:01 ` Konstantin Ryabitsev
2020-03-20 22:03 ` Jens Axboe
2020-03-20 22:03 ` Johannes Berg
2020-03-23 12:06 ` [tools] " Mark Brown
2020-03-23 12:16 ` [kernel.org users] " Jason Gunthorpe
2020-03-27 12:53 ` Ludovic Desroches
2020-03-27 13:14 ` Jason Gunthorpe
2020-03-27 13:34 ` Ludovic Desroches
2020-03-27 13:46 ` Jason Gunthorpe [this message]
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=20200327134625.GV20941@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Ludovic.Desroches@microchip.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.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;
as well as URLs for NNTP newsgroup(s).