From: Rainer M Krug <Rainer@krugs.de>
To: myglc2 <myglc2@gmail.com>
Cc: info-gnus-english@gnu.org
Subject: Re: nnir-notmuch-engine setup with gnus/offlineimap/dovecot
Date: Fri, 30 Sep 2016 09:04:24 +0200 [thread overview]
Message-ID: <m2h98xswav.fsf@krugs.de> (raw)
In-Reply-To: <86fuoi6uij.fsf@gmail.com> (myglc2@gmail.com's message of "Thu, 29 Sep 2016 21:33:56 -0400")
[-- Attachment #1.1: Type: text/plain, Size: 1731 bytes --]
myglc2 <myglc2@gmail.com> writes:
> Dave Abrahams <dave@boostpro.com> writes:
>>
>> Yes. Other things that work really well in a setup like that are:
>>
>> 1. Using dovecot's mdbox storage format, which is much more efficient
>>
>> 2. Building dovecot with clucene and stemmer support for search
>>
>> 3. Using mbsync from the isync project (scales much better than
>> offlineimap IMO,
>
> I saw this too. mbsync (AKA isync) was ~30 times faster in my tests. It
Very interesting - I might look into isync than.
> was also important to build from the git repo because, at least a month
> or two ago, the tar.gz at version 1.2.1 was missing a feature that turns
> out to be important in my gmail sync setup.
Which feature was this, if I may ask? I would also use isync for
syncing a gmail account. Could you share your config so that I can have
an idea what I am looking at in a change ti isync?
How do these two compare in regards to stability (offlineimap has
e.g. an issue wit suspend on the Mac)?
>
> Built from the git repo it shows this version info:
>
> g1@g1 ~$ mbsync --version
> isync 1.3.0
Yup - that is the one I also have now from git.
>
>> though I am about to try dropping it because doveadm sync is already
>> part of dovecot)
>
> A couple months ago I put a fair amount of effort into trying to use
> dovecot sync. I ended up concluding that mbsync is faster and easier to
> config.
Thanks,
Rainer
>
>
> _______________________________________________
> info-gnus-english mailing list
> info-gnus-english@gnu.org
> https://lists.gnu.org/mailman/listinfo/info-gnus-english
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
next prev parent reply other threads:[~2016-09-30 7:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 23:00 Arkady Grudzinsky
2016-09-23 5:21 ` Dmitry Alexandrov
2016-09-23 7:56 ` Rainer M Krug
2016-09-29 21:06 ` Dave Abrahams
2016-09-30 1:33 ` myglc2
2016-09-30 7:04 ` Rainer M Krug [this message]
2016-09-30 14:01 ` myglc2
2016-09-30 15:04 ` Rainer M Krug
2016-09-30 17:13 ` Dave Abrahams
2016-09-30 12:02 ` Dave Abrahams
2016-09-30 14:28 ` myglc2
2016-09-30 15:06 ` Rainer M Krug
2016-09-30 6:59 ` Rainer M Krug
2016-09-30 9:51 ` Alan Schmitt
2016-09-30 10:33 ` Rainer M Krug
2016-09-30 11:50 ` Dave Abrahams
2016-09-30 11:44 ` Dave Abrahams
2016-09-30 12:56 ` Rainer M Krug
2016-09-30 17:13 ` Dave Abrahams
2016-09-23 7:58 ` Rainer M Krug
2016-09-23 21:27 ` Adam Sjøgren
2016-09-26 23:51 ` Arkady Grudzinsky
2016-09-27 2:54 ` Adam Sjøgren
2016-09-27 7:27 ` Rainer M Krug
2016-09-28 22:10 ` Arkady Grudzinsky
2016-09-29 6:57 ` Rainer M Krug
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=m2h98xswav.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=info-gnus-english@gnu.org \
--cc=myglc2@gmail.com \
/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).