Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Unable to get all messages in an IMAP group
Date: Tue, 03 Feb 2015 09:05:23 +0100	[thread overview]
Message-ID: <upzcegq7fmik.fsf@dod.no> (raw)
In-Reply-To: <m3egq7a1ds.fsf@neo.luffy.cx>

>>>>> Vincent Bernat <bernat@luffy.cx>:

> It's Dovecot 2.2.13. I don't use the agent.

Hm, ok... from your symptoms, I suspected the agent, but obviously that
wasn't the problem.

And dovecot is the best-behaved IMAP server nnimap is used
against.

> I see that nnimap-debug doesn't exist anymore.

So it is.

> How to get some traces?

I don't know, unfortunately.

> Also, the content of .newsrc.eld may be inexact. I am synchronizing it
> across my hosts and I am using isync to replicate IMAP mailboxes (served
> locally by Dovecot). So, each host has its own view of the IMAP
> server. Usually, after a sync, M-g is enough to get Gnus and Dovecot
> agree again.

What happens if you move your .newsrc.eld aside and create a new
.newsrc.eld for the nnimap groups?  Does it work initially and then get
corrupted?  Does it work initially and continue to work?




  parent reply	other threads:[~2015-02-03  8:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 23:18 Vincent Bernat
2015-02-03  6:42 ` Steinar Bang
2015-02-03  7:40   ` Vincent Bernat
2015-02-03  7:44     ` Vincent Bernat
2015-02-03  8:05     ` Steinar Bang [this message]
2015-02-03  8:17       ` Tassilo Horn
2015-02-03  9:09       ` Vincent Bernat
2015-02-03 10:54         ` Steinar Bang
2015-02-03 20:52           ` Vincent Bernat
2015-02-04  6:28             ` Steinar Bang
2015-02-04 20:48               ` Vincent Bernat
2015-02-04 21:10                 ` Steinar Bang
2015-02-04 21:11                 ` Vincent Bernat
2015-02-04 21:19                   ` Vincent Bernat
2015-02-04 21:35                     ` Vincent Bernat
2015-02-05  3:10                       ` Lars Ingebrigtsen
2015-02-05  6:27                         ` Vincent Bernat
2015-02-05  3:06                   ` Lars Ingebrigtsen

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=upzcegq7fmik.fsf@dod.no \
    --to=sb@dod.no \
    --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).