Re: nnimap against Cyrus imapd just stopped working

[Steinar Bang <sb@dod.no>]

>>>>> Simon Josefsson <jas@extundo.com>:

> Steinar Bang <sb@dod.no> writes:
>> | 2 <- nnimap-find-minmax-uid: (15980 1 15990)
>> | 2 -> nnimap-find-minmax-uid: group="INBOX.archive.info-cyrus" examine=examine
>> | 2 <- nnimap-find-minmax-uid: nil
>> | 2 -> nnimap-find-minmax-uid: group="Trash\\\\a?.er1" examine=examine
>> | 2 <- nnimap-find-minmax-uid: nil
>> | 2 -> nnimap-find-minmax-uid: group="archive.cyrus-sasl" examine=examine
>> | 2 <- nnimap-find-minmax-uid: nil
>> | 2 -> nnimap-find-minmax-uid: group="b¥?" examine=examine
>> | 2 <- nnimap-find-minmax-uid: nil

> Those group names looks weird.  Do they really have such folders?

I haven't subscribed to any that I know about.

> They don't match archive.* either, I'm not sure why they are shown
> at all.  Perhaps there is some kind of data corruption somewhere?
> .newsrc.eld?

Sounds like a likely candidate, yes.  Perhaps caused by a gnus-slave
file merge?  That would probably be a bug, but:
 1. it may not be there in the latest CVS
 2. I have no idea to go about reproducing it, because I have been
    using gnus-slave for ages without seeing any strange effects

> Try C-k all nnimap group and resubscribe to them.

I'll try that when I get home.  I wish there was a simple way to keep
the group parameters when I do this.