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: Sat, 13 Feb 2016 15:03:56 +0100	[thread overview]
Message-ID: <87twlcvh9v.fsf@cri.ensmp.fr> (raw)
In-Reply-To: <87io1wfbvp.fsf@cri.ensmp.fr>

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> Yeah so the only idea that came to my mind is if the pipelining of UID
>> MOVEs could be causing some problem...
>
> Pipelining is something that all IMAP servers should handle without too
> much problem.

After some more research and RFC there seems to be a catch with this,
when pipelining and using QRESYNC, mailboxes may get "conceptually out
of sync", so some operations may need to be reissued again.

Indeed, this problem of duplicates is more common when more moves are issued.

>>> * OK [COPYUID 1424475206 4065 96] Moved UIDs.
[...]
>>> I'm really puzzled by this log, dunno how to interpret it.
>
> I think that it says "I did everything you asked".  So if these messages
> remain in the original folder after the server says "Move completed",
> then there's something wrong with that server...

I'm not sure that is the right interpretation of the log (but my
knowlegde of IMAP is very limited), let me restructure the log to remove
useless stuff:

> *first press of g*
> 21:02:59 [domain] 9020 UID MOVE 4063:4064,4067,4069:4072 "folder1"
> * OK [COPYUID 1424475231 4063:4064,4067,4069:4072 26:32] Moved UIDs.
> * VANISHED 4062,4066,4068:4072
> * 3 RECENT
> 9020 OK [HIGHESTMODSEQ 5193] Move completed.

I interpret this as "only 4062,4066,4068:4072" got moved.

Indeed, then later:

> --- Second press of g
> 21:07:20 [domain] 9307 UID MOVE 4063:4064,4067 "folder1"
> * OK [COPYUID 1424475231 4063:4064,4067 33:35] Moved UIDs.
> * VANISHED 4063:4064,4067
> 9307 OK [HIGHESTMODSEQ 5194] Move completed.

Precisely the messages that were missing from the previous VANISHED.

If my interpretation of the RFC is correct, indeed this is a bug in
gnus, as it should parse VANISHED output to confirm the moves.

Thanks a lot for the help, best regards,
Emilio





  parent reply	other threads:[~2016-02-13 14:03 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 [this message]
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
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=87twlcvh9v.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).