Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Michael Na Li <lina@u.washington.edu>
Subject: Re: Oops!  Readonly INBOX after Oort upgrade?
Date: Mon, 05 Aug 2002 15:14:22 -0700	[thread overview]
Message-ID: <m2ado1eywx.fsf@u.washington.edu> (raw)
In-Reply-To: <87ofco71bz.fsf@phiwumbda.localnet>


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


           reply	other threads:[~2002-08-05 22:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87ofco71bz.fsf@phiwumbda.localnet>]

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=m2ado1eywx.fsf@u.washington.edu \
    --to=lina@u.washington.edu \
    /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).