From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: very short tip: imap.gmail.com sync
Date: Wed, 06 Feb 2019 11:41:04 -0800 [thread overview]
Message-ID: <87y36s7lin.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87imxxh5lv.fsf@delta.birch.chromebook>
soyeomul@doraji.xyz (Byung-Hee HWANG "(황병희, 黃炳熙)") writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> soyeomul@doraji.xyz (Byung-Hee HWANG "(황병희, 黃炳熙)") writes:
>>
>>> soyeomul@doraji.xyz (Byung-Hee HWANG "(황병희, 黃炳熙)") writes:
>>>
>>>> for years i used just nnimap for imap.gmail.com. nnimap sync all
>>>> label. so it takes time for minutes with huge label such as linux-kernel
>>>> mailing archive. so i did googling.
>>>>
>>>> now i use getmail [1]. and by `G f' in group buffer, i could choose the
>>>> mbox. speed? very very very fast. it appears as nndoc in group buffer.
>>>>
>>>> [1] https://en.wikipedia.org/wiki/Getmail
>>>
>>> just added screenshot: (getmail do sync [Inbox, gmane])
>>> https://gitlab.com/soyeomul/Gnus/raw/master/ss/getmail+gnus.png
>>
>> And getmail does two-way syncing with Gmail? I mean, local changes get
>> propagated to the server?
>
> Yes, i use this python script: (with cron service)
> https://gitlab.com/soyeomul/Gnus/raw/master/getmail.py
Interesting. I didn't realize you could effectively sync a remote imap
server to so many different local options: a local imap server, a
maildir, and apparently an nndoc. Thanks for the information!
next prev parent reply other threads:[~2019-02-06 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 16:16 Byung-Hee HWANG (황병희, 黃炳熙)
2019-02-06 2:09 ` Byung-Hee HWANG (황병희, 黃炳熙)
2019-02-06 3:18 ` Eric Abrahamsen
2019-02-06 5:02 ` Byung-Hee HWANG (황병희, 黃炳熙)
2019-02-06 19:41 ` Eric Abrahamsen [this message]
2019-02-06 23:15 ` Byung-Hee HWANG (황병희, 黃炳熙)
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=87y36s7lin.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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).