Re: Oops! Readonly INBOX after Oort upgrade?

Re: Oops! Readonly INBOX after Oort upgrade?

[Michael Na Li]

I have a similar problem that just popped up to annoy me.  In short, I can't
nnimap-expunge-on-close even though 'G x' (gnus-group-nnimap-expunge) does
work.

Here is part of *imap-log*:

256 SELECT "INBOX"^M
* 54 EXISTS^M
* 0 RECENT
* OK [UIDVALIDITY 1] UID validity status
* OK [UIDNEXT 76424] Predicted next UID
* FLAGS (gnus-dormant gnus-expire $MDNSent \Answered \Flagged \Deleted \Draft \Seen)
* OK [PERMANENTFLAGS (gnus-dormant gnus-expire $MDNSent \* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags
256 OK [READ-WRITE] SELECT completed

Everything seems to be fine up until now, and after lots of FETCH,

264 OK UID FETCH completed
265 EXAMINE "INBOX"
* 54 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1] UID validity status
* OK [UIDNEXT 76424] Predicted next UID
* FLAGS (gnus-dormant gnus-expire $MDNSent \Answered \Flagged \Deleted \Draft \Seen)
* OK [PERMANENTFLAGS ()] Permanent flags
265 OK [READ-ONLY] EXAMINE completed
266 CLOSE
* NO Expunge ignored on readonly mailbox
266 OK CLOSE completed

It ends up with READ-ONLY mailbox and no expunge is done.

Any idea?


-- 
---------------------------------------------------
Michael Na Li
Email: lina@u.washington.edu
Department of Biostatistics, Box 357232
University of Washington, Seattle, WA 98195  
---------------------------------------------------