Re: [PATCH] Use IMAP MOVE extension if available

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Nikolaus Rath <Nikolaus@rath.org> writes:

> Hello,
>
> The attached revision fixes a small error when parsing the response to
> the UID MOVE command. Previously, it would fail to find the COPYUID
> response and fall back to using the message id to determine the UID of
> the copied message.

I'm running these patches locally, and (I think) seeing more hangs than
I used to. This only happens on first startup of Gnus. I set
toggle-debug-on-quit to t, and quit on the next hang -- see the
traceback below.

This is connecting to a dovecot server running on localhost. The first
thing this tells me is that the MOVE capability (which dovecot provides)
isn't getting noticed by Gnus -- as you noted in your previous exchange
with Lars (was there no resolution to that?). That does need to get
fixed, otherwise Gnus is missing a lot of added functionality.

The other thing is this hang. I'm not immediately inclined to blame Gnus
for this, but the fact is that this a local connection and there
shouldn't be anything stalling it. If anyone has any bright ideas...

  nnimap-wait-for-response(85)
  nnimap-get-response(85)
  nnimap-command("UID STORE %s +FLAGS.SILENT (\\Deleted)" "")
  nnimap-delete-article(nil t)
  nnimap-split-incoming-mail()
  nnimap-request-scan(nil "PR")
  gnus-request-scan(nil (nnimap "PR" (nnimap-address "localhost")
  (nnimap-user "user") (nnimap-authenticator login) (stuff omitted) (nnimap-stream network) (nnimap-inbox "INBOX")))
  gnus-get-unread-articles(4 nil)
  gnus-setup-news(nil 4 nil)
  ...bytecode omitted...
  gnus-1(4 nil nil)
  gnus(4)