Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <>
To: Erik Colson <>
Subject: Re: maildir and gnus
Date: Wed, 25 May 2022 11:20:10 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Erik Colson's message of "Wed, 04 May 2022 14:31:54 +0200")

Erik Colson <> writes:

> So I finally installed the thing: mbsync / dovecot / nnimap
> Still some issues but not speed actually.

Adding my past few years experience:

1. I went from using nnimap to offlineimap->maildir folders a large
number of years ago.  It worked generally well, allowed easy offline
support (better than offline mode somewhat).  NOV files would build up
though, so I built a script to clean them.  After large quantities of
time (order 2-5 years), it did seem to get slower and slower (probably
from id number lists expanding, but that's a guess).

Anyway, with a recent desktop that no longer moves around I moved it
back to nnimap and its *much* faster than my previous offlineimap
method.  I don't mean just for the transfer though.  I tried mbsync and
got it working, but for some reason nnimap is faster in most respects.
Gnus scanning nnmaildir directories took probably 5-10 times longer than
nnimap when fetching new mail.

Also, another downside of offline/mbsync -> maildir is that it marks
everything as "not new" on the server because you are in fact pulling it
by pulling it (ok, I assume this is true for mbsync -- I didn't verify
that).  There is probably a way to hack the new flag back on the imap
side, but I never tried.  With nnimap, the new flag remains correct and
thus other clients or biff-like utilities continue to work properly.


Wes Hardaker                                     
My Pictures:

      reply	other threads:[~2022-05-25 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 12:34 Erik Colson
2022-04-08 13:13 ` Eric S Fraga
2022-05-04 12:31   ` Erik Colson
2022-05-25 18:20     ` Wes Hardaker [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).