Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: 4266 is the 666 of the IMAP world (retrieval issues and odd behaviours)
Date: Tue, 03 Apr 2012 20:10:15 +0200	[thread overview]
Message-ID: <87iphg660o.fsf@dod.no> (raw)
In-Reply-To: <87ehs4ah5y.fsf@dancingfrog.co.uk>

When you initially connected to the exchange server, did you `M-g' on
all of the nnimap groups?  It's probably not necessary when you start
initial subscription (my subscriptions were old when I transitioned to
the new nnimap backend) but it is something to try.

AFAIK `M-g' does a fully sync of what's available in that particular
nnimap group, and put that information in the .newsrc.eld, so that it
can do quick QRESYNC requests later.




  reply	other threads:[~2012-04-03 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 16:55 Matt Ford
2012-04-03 18:10 ` Steinar Bang [this message]
2012-04-03 19:38   ` Matt Ford
2012-04-04 14:17 ` Matt Ford
2012-04-10 18:55   ` Lars Magne Ingebrigtsen
2012-04-06 12:05 ` Matt Ford

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=87iphg660o.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).