Gnus development mailing list
 help / color / mirror / Atom feed
From: "Chris D.Halverson" <cdh@CompleteIS.com>
Subject: Re: nnimap UIDVALIDITY problem on exchange server
Date: 20 Jun 2000 08:13:57 -0500	[thread overview]
Message-ID: <wpsnu8336y.fsf@CompleteIS.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 20 Jun 2000 11:39:59 +0200"

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1218 bytes --]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Your idea of `G DEL'-ing the group was a good one.  Maybe the group
> wasn't really deleted?  I think it is important to say `s' to save the
> .newsrc.eld file, then check the file to see if Gnus really deleted
> all traces of this group from the .newsrc.eld file.  In particular, no
> article number information should remain.

I had this happen once too (not w/ Exchange, UW IMAP for some
reason). There was a thread on this list about it. Another thing to
remember is to remove ~/News/overview/nnimap.mail.INBOX.novcache. That
hosed me up for a while. Here's my step by step actions:

 1. I C-k the group

 2. Examined ~/.newsrc.eld to ensure it wasn't there

 3. Removed the overview cache file

 4. Started Gnus and did a "G m" to remake the group and everything
 worked.

 Earlier I had done a "A A" and re-subscribed to it. Evidently this is
 different than "G m" the group as the "A A" try seemed to pull out old
 values for somewhere.

Hope that helps.

cdh

-- 
Chris D. Halverson                         Complete Internet Solutions
PGP mail accepted, finger for public key   http://www.CompleteIS.com/~cdh/



  reply	other threads:[~2000-06-20 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-20  7:55 Steinar Bang
2000-06-20  9:39 ` Kai Großjohann
2000-06-20 13:13   ` Chris D.Halverson [this message]
2000-06-20 14:09     ` Steinar Bang
2000-06-20 15:18       ` Toby Speight
2000-06-20 14:23     ` Kai Großjohann

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=wpsnu8336y.fsf@CompleteIS.com \
    --to=cdh@completeis.com \
    /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).