From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: duplicates with offlineimap+dovecot
Date: Tue, 23 Feb 2016 17:05:42 -0500 [thread overview]
Message-ID: <87h9gzw095.fsf@uwo.ca> (raw)
In-Reply-To: <8737sjw936.fsf@cri.ensmp.fr>
On Feb 23, 2016, gallego@cri.ensmp.fr (Emilio Jesús Gallego Arias) wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> gallego@cri.ensmp.fr (Emilio Jesús Gallego Arias) writes:
>>
>>> Update: this has been fixed upstream:
>>>
>>> http://www.dovecot.org/list/dovecot/2016-February/103205.html
>>
>> Perhaps we should add a quirk to nnimap to disable MOVE for the Dovecot
>> versions affected? What versions are those?
>
> I dunno when the bug was introduced, but it didn't hurt too many people
> it seems.
>
> Maybe adding an entry to the FAQ/QUIRKS file instructing to remove
> "MOVE" from nnimap-capabilities may be better than polluting the code.
I have only skimmed this thread, but isn't it *streaming* moves that
are the problem? If so, maybe it would be better to have Gnus do an
expunge (or whatever is needed) between moves? Or does Gnus need to
adjust it's internal article numbering between moves?
I'm also curious about which versions of dovecot are affected. I'm
using 1:2.2.9-1ubuntu2.1 from Ubuntu 14.04, and I occasionally see a
problem that might be related, but I'm not sure.
Dan
next prev parent reply other threads:[~2016-02-23 22:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 17:31 Julien Cubizolles
2016-02-01 22:34 ` Malcolm Purvis
2016-02-02 8:49 ` Julien Cubizolles
2016-02-09 11:05 ` Emilio Jesús Gallego Arias
2016-02-09 23:42 ` Lars Ingebrigtsen
2016-02-10 1:17 ` Emilio Jesús Gallego Arias
2016-02-10 2:56 ` Lars Ingebrigtsen
2016-02-10 22:18 ` Emilio Jesús Gallego Arias
2016-02-10 23:56 ` Emilio Jesús Gallego Arias
2016-02-13 6:52 ` Lars Ingebrigtsen
2016-02-13 14:03 ` Emilio Jesús Gallego Arias
2016-02-14 2:34 ` Lars Ingebrigtsen
2016-02-14 4:05 ` Emilio Jesús Gallego Arias
2016-02-14 4:36 ` Lars Ingebrigtsen
2016-02-14 4:56 ` Emilio Jesús Gallego Arias
2016-02-14 5:23 ` Lars Ingebrigtsen
2016-02-14 12:19 ` Emilio Jesús Gallego Arias
2016-02-15 7:54 ` Lars Ingebrigtsen
2016-02-20 7:52 ` Steinar Bang
2016-02-20 8:21 ` Lars Ingebrigtsen
2016-02-20 14:47 ` Steinar Bang
2016-02-22 23:12 ` Emilio Jesús Gallego Arias
2016-02-23 0:58 ` Lars Ingebrigtsen
2016-02-23 18:54 ` Emilio Jesús Gallego Arias
2016-02-23 22:05 ` Dan Christensen [this message]
2016-02-24 1:10 ` Lars Ingebrigtsen
2016-02-24 1:11 ` Lars Ingebrigtsen
2016-02-24 17:59 ` Emilio Jesús Gallego Arias
2016-02-01 22:40 ` Dave Abrahams
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=87h9gzw095.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).