From: Steinar Bang <sb@dod.no>
Subject: nnimap against Cyrus imapd just stopped working
Date: Tue, 09 Jul 2002 22:10:22 +0200 [thread overview]
Message-ID: <87ofdg8xxt.fsf@doohan.bang.priv.no> (raw)
Platform: Intel PII, debian woody,
XEmacs 21.4 (patch 6) "Common Lisp" [Lucid] (i386-debian-linux, Mule)
Oort Gnus v0.06 (CVS checkout from Feb 1)
Cyrus imapd 1.5.19
Today nnimap against my cyrus imapd stopped working without me having
made any changes to the system. I'm wondering if the problem is in
the imapd or in Gnus. I'm running without agent support. I see the
same problems on both GNU Emacs and XEmacs.
The login works normally, but when I try to enter an nnimap group, I
get a beep, and a split display, and the following messages in the
lower buffer that's opened:
(1) (error/warning) Error in process filter: (wrong-type-argument stringp nil)
(2) (error/warning) Error in process filter: (wrong-type-argument stringp nil)
When I look at the results of `C-h l', I see the following:
Couldn't request group nnimap+doohan:INBOX: nil
nil
Opening nnimap server on doohan...done
Opening nnimap server on doohan...
The *nnimap* doohan buffer at this point, is:
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen gnus-forward \*)]
* 1014 EXISTS
* 0 RECENT
* OK [UNSEEN 1013]
* OK [UIDVALIDITY 964202290]
32 OK [READ-WRITE] Completed
* FLAGS (\Answered \Flagged \Draft \Deleted \Seen gnus-forward)
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen gnus-forward \*)]
* 1014 EXISTS
* 0 RECENT
* OK [UNSEEN 1013]
* OK [UIDVALIDITY 964202290]
33 OK [READ-WRITE] Completed
My own best guess is that something has been corrupted in the cyrus
imapd database. But I don't know what, or how to correct it. But I'm
wondering if it could be something under ~/News/ or ~/Mail/.
All hints and tips appreciated. I would like to be able to read my
mail again.
Thanx!
- Steinar
next reply other threads:[~2002-07-09 20:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 20:10 Steinar Bang [this message]
2002-07-09 20:20 ` Simon Josefsson
2002-07-09 20:34 ` Steinar Bang
2002-07-09 20:38 ` Steinar Bang
2002-07-09 20:44 ` Simon Josefsson
2002-07-09 20:55 ` Steinar Bang
2002-07-09 21:04 ` Simon Josefsson
2002-07-09 21:51 ` Steinar Bang
2002-07-10 11:02 ` Simon Josefsson
2002-07-10 11:12 ` Steinar Bang
2002-07-09 21:53 ` Steinar Bang
2002-07-10 5:58 ` Steinar Bang
2002-07-09 20:41 ` Simon Josefsson
2002-07-09 20:50 ` Steinar Bang
2002-07-09 21:02 ` Simon Josefsson
2002-07-09 21:43 ` Steinar Bang
2002-07-10 11:05 ` Simon Josefsson
2002-07-10 11:17 ` Steinar Bang
2002-07-10 11:26 ` Simon Josefsson
2002-07-10 11:43 ` Steinar Bang
2002-07-10 12:39 ` Kai Großjohann
2002-07-10 14:21 ` Reiner Steib
2002-07-11 8:18 ` Kai Großjohann
2002-07-11 18:34 ` group and topic parameters (was: nnimap against Cyrus imapd just stopped working) Reiner Steib
2002-07-12 0:49 ` Janne Rinta-Mänty
2002-07-10 22:34 ` nnimap against Cyrus imapd just stopped working Steinar Bang
2002-07-11 10:37 ` A .newsrc.eld validator? (Was: nnimap against Cyrus...) Steinar Bang
2002-07-11 16:45 ` nnimap against Cyrus imapd just stopped working Steinar Bang
2002-07-11 17:56 ` Steinar Bang
2002-07-11 18:09 ` Steinar Bang
2002-07-11 18:17 ` Steinar Bang
2002-07-11 18:51 ` Steinar Bang
2002-07-26 12:18 ` Simon Josefsson
2002-07-27 9:38 ` Steinar Bang
2002-07-11 20:01 ` Steinar Bang
2002-07-11 22:24 ` Amos Gouaux
2002-07-11 22:33 ` Amos Gouaux
2002-07-12 5:54 ` Steinar Bang
2002-07-10 8:50 ` 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=87ofdg8xxt.fsf@doohan.bang.priv.no \
--to=sb@dod.no \
/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).