Re: nnimap against Cyrus imapd just stopped working

[Simon Josefsson <jas@extundo.com>]

Steinar Bang <sb@dod.no> writes:

> 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)

Does (setq debug-on-signal t) do anything useful?  Toggling
nnimap-debug might.  It is a Nnimap bug for sure, I haven't seen these
kind of errors for a long time.

> 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/.

The error comes from the imap protocol parser, so it is either the
server or imap.el.  I doubt any caches are involved at that stage.