From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Cannot read INBOX on Exchange server any longer
Date: Tue, 06 Nov 2001 14:56:17 +0100 [thread overview]
Message-ID: <vafelncgfzy.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3d72wrqxt.fsf@linux.local> (Christoph Rohland's message of "06 Nov 2001 14:04:30 +0100")
Christoph Rohland <cr@sap.com> writes:
> I have an nnimap backend connected to an MS Exchange server. It did
> work for some time now, but somehow it screwed up my INBOX. I got
> uidvalidity errors and now if I try to access the INBOX it always
> fails with 'Can't select group'.
Does it help to do M-x gnus-group-clear-data RET on the group?
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~2001-11-06 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 13:04 Christoph Rohland
2001-11-06 13:56 ` Kai Großjohann [this message]
2001-11-06 13:50 ` Christoph Rohland
2001-11-06 14:04 ` Christoph Rohland
2001-11-06 14:59 ` Mario Peter
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=vafelncgfzy.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).