From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Christoph Groth <christoph@grothesque.org>
Cc: info-gnus-english@gnu.org
Subject: Re: Gnus stuck in nnimap-wait-for-response with local dovecot
Date: Fri, 03 Sep 2021 13:02:42 -0700 [thread overview]
Message-ID: <87tuj1jul9.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87h7f2dkth.fsf@drac> (Christoph Groth's message of "Fri, 03 Sep 2021 12:18:02 +0200")
Christoph Groth <christoph@grothesque.org> writes:
> Hello,
>
> I’m still using a mail setup that involves Gnus with nnimap and a local
> dovecot that is run on demand. I sync mail between the local maildir
> (that is used by dovecot when it runs) and remote IMAP servers using
> isync/mbsync.
>
> I learned about this setup from Eric Abrahamsen on the ding mailing list
> in the old days. I believe that the original presentation of the idea
> was this blog post:
>
> https://web.archive.org/web/20160427162529/http://roland.entierement.nu/blog/2010/09/08/gnus-dovecot-offlineimap-search-a-howto.html
>
> On the Gnus side, the setup is based on setting nnimap-shell-program to
>
> "/usr/lib/dovecot/imap -o mail_location=maildir:$HOME/.mail/%s/ 2>>$HOME/.dovecot.err"
>
> only that this happens inside a setup involving fancy splitting. (This
> way of using dovecot seems to be somewhat obscure, or at least
> I haven’t been able to find much documentation about it.)
>
> Anyway, my setup has been working like this for many years now, but
> there’s a wart. Whenever there is new mail and I launch M-x gnus, it
> will typically freeze during startup and I have to abort with C-g and
> retry. After retrying one or two times Gnus does start and everything
> seems to work normally. The new mail is visible in Gnus.
>
> Here is the kind of the backtrace that I can typically obtain in the
> situation
>
> Debugger entered: ("Quit")
> nnimap-wait-for-response(839)
> nnimap-get-groups()
I can't really guess why this would be happening. The call to
`nnimap-request-scan' should be setting everything up properly, so far
as I know. Perhaps someone else will have some better tips for
debugging. My only other suggestion would be switching to dovecot as an
always-on system service, and then switching Gnus to using "localhost"
as the IMAP server address. It seems entirely plausible that that will
improve things.
prev parent reply other threads:[~2021-09-03 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 10:18 Christoph Groth
2021-09-03 20:02 ` Eric Abrahamsen [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=87tuj1jul9.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=christoph@grothesque.org \
--cc=info-gnus-english@gnu.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).