Gnus development mailing list
 help / color / mirror / Atom feed
From: gallego@cri.ensmp.fr (Emilio Jesús Gallego Arias)
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: duplicates with offlineimap+dovecot
Date: Wed, 10 Feb 2016 02:17:01 +0100	[thread overview]
Message-ID: <87si11nz3m.fsf@cri.ensmp.fr> (raw)
In-Reply-To: <87wpqd5u46.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 10 Feb 2016 10:42:01 +1100")

Hi Lars,

Lars Ingebrigtsen <larsi@gnus.org> writes:

> gallego@cri.ensmp.fr (Emilio Jesús Gallego Arias) writes:
>
>> 09:00:13 [host] 5455 LIST "" "*"
>> 09:00:14 [host] 5456 SELECT "INBOX"
>> 09:00:14 [host] 5457 UID FETCH 1:* FLAGS
>> 09:00:14 [host] 5458 UID FETCH 10775:10795 (UID BODY.PEEK[HEADER])
>> 09:00:14 [host] 5459 UID MOVE 10779 "folder1"
>> 09:00:14 [host] 5460 UID MOVE 10780 "folder2"
>> 09:00:14 [host] 5461 UID MOVE 10791 "folder3"
>> 09:00:14 [host] 5462 UID MOVE 10775:10777,10781:10790,10792:10794 "folder5"
>> 09:00:14 [host] 5463 UID MOVE 10795 "folder4"
>
> So that's the splitting.  It's all MOVE, so those articles should no
> longer be in INBOX...

Indeed, that's weird, maybe the server is returning some kind of weird status?

Isn't there a way to debug even more/IMAP return status? I've tried to
gather the contents of the *nnimap host *nntpd** buffer but without success.

Thanks a lot for the help,
Emilio

p.d: I couldn't get dovecot to log in verbose mode either, investigating
this.




  reply	other threads:[~2016-02-10  1:17 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 [this message]
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
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=87si11nz3m.fsf@cri.ensmp.fr \
    --to=gallego@cri.ensmp.fr \
    --cc=ding@gnus.org \
    --cc=larsi@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).