From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: INBOX is not uidvalid
Date: Fri, 17 Aug 2001 20:00:19 +0200 [thread overview]
Message-ID: <iluwv42d0ss.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <200108171742.f7HHg8u04526@bothner.com> (Per Bothner's message of "Fri, 17 Aug 2001 10:42:08 -0700")
Per Bothner <per@bothner.com> writes:
> I tried setting up an imap server, and things seemed to work.
> But now when I select INBOX (in the Group buffer), I get this very
> utterly diagnostic:
>
> nnimap: Group INBOX is not uidvalid. Continue?
>
> This is Gnus 5.8.5 under xemacs 21.4.4 under Red Hat 7.1.
The error message is disabled in Oort Gnus, patch below.
However, if you use the cache or agent in a group that your IMAP
server decides to re-number (and thus changing UIDVALIDITY), you might
have problems. Problems such as seeing information for one article in
the summary buffer and a completely different message in the article
buffer. But this seem to be rare. Tell us if you experience this, or
any other problem, with the patch.
Index: nnimap.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/nnimap.el,v
retrieving revision 6.7
retrieving revision 6.8
diff -u -r6.7 -r6.8
--- nnimap.el 2001/07/04 17:41:56 6.7
+++ nnimap.el 2001/07/06 17:56:46 6.8
@@ -397,6 +397,8 @@
(if (or (nnimap-verify-uidvalidity
group (or server nnimap-current-server))
(zerop (imap-mailbox-get 'exists group))
+ t ;; for OGnus to see if ignoring uidvalidity
+ ;; changes has any bad effects.
(yes-or-no-p
(format
"nnimap: Group %s is not uidvalid. Continue? " group)))
next prev parent reply other threads:[~2001-08-17 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 17:42 Per Bothner
2001-08-17 18:00 ` Simon Josefsson [this message]
2001-08-17 20:48 ` Per Bothner
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=iluwv42d0ss.fsf@barbar.josefsson.org \
--to=jas@extundo.com \
--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).