Gnus development mailing list
 help / color / mirror / Atom feed
From: gallego@cri.ensmp.fr (Emilio Jesús Gallego Arias)
To: ding@gnus.org
Subject: Re: duplicates with offlineimap+dovecot
Date: Sun, 14 Feb 2016 13:19:10 +0100	[thread overview]
Message-ID: <87h9hbiiwx.fsf@cri.ensmp.fr> (raw)
In-Reply-To: <874mdb3lx9.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

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

The RFC states that MOVE is exactly equivalent to COPY + STORE +
EXPUNGE, and defer streaming to ambiguity rules.

IMO it is not very clear what should this mean, I've asked on dovecot
and imap mailing lists.

After a quick look to Dovecot's source code, I think I got a small
intuition on what is going on.

Dovecot will only check the success of the move to issue the "OK Move
completed" response. There is no check for expunge failing.

[see cmd-copy.c: + mail-storage.c:mailbox_move()]

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

Yeah this means that the copy part of the move didn't fail, but not all
messages (form the second copy) where expunged from the INBOX.

Thanks for the help,
E.




  reply	other threads:[~2016-02-14 12:19 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 [this message]
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=87h9hbiiwx.fsf@cri.ensmp.fr \
    --to=gallego@cri.ensmp.fr \
    --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).