From: Lars Ingebrigtsen <larsi@gnus.org>
To: gallego@cri.ensmp.fr (Emilio Jesús Gallego Arias)
Cc: ding@gnus.org
Subject: Re: duplicates with offlineimap+dovecot
Date: Sun, 14 Feb 2016 16:23:14 +1100 [thread overview]
Message-ID: <874mdb3lx9.fsf@gnus.org> (raw)
In-Reply-To: <87povzlwjz.fsf@cri.ensmp.fr> ("Emilio =?iso-8859-1?Q?Jes=FAs?= Gallego Arias"'s message of "Sun, 14 Feb 2016 05:56:16 +0100")
gallego@cri.ensmp.fr (Emilio Jes?FFFAs Gallego Arias) writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> gallego@cri.ensmp.fr (Emilio Jes?FFFAs Gallego Arias) writes:
>>
>>>> The server may send EXPUNGE (or VANISHED) responses before the tagged
>>>> response, so the client cannot safely send more commands with message
>>>> sequence number arguments while the server is processing MOVE or UID
>>>> MOVE.
>>>
>>> Doesn't that mean that gnus should not stream the two MOVES?
>>
>> I interpret that to mean that the client shouldn't send other non-MOVE
>> commands that depend on those MOVEs having been done (when streaming).
>
> But isn't a MOVE "a command with message sequence number arguments" ?
That's a possible interpretation, but then the MOVE RFC should just have
said "MOVEs can't be streamed". I can't see that it does that. And the
VANISH stuff comes from the QRESYNC support, which is a separate
feature. If MOVE fails, it should have said so, and it doesn't:
21:02:59 [domain] 9019 UID MOVE 4062,4066,4068 "unrelated2"
21:02:59 [domain] 9020 UID MOVE 4063:4064,4067,4069:4072 "folder1"
[...]
9019 OK Move completed.
9020 OK [HIGHESTMODSEQ 5193] Move completed.
Both commands completed with OK.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-14 5:23 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 [this message]
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
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=874mdb3lx9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=gallego@cri.ensmp.fr \
/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).