On Thu, 8 Apr 2004, Mark Crispin wrote:

> > Is there a good place in imapd we can hack "Junk" into the default keywords
> > available for all newly created (in our case, mbx format) mailboxes?
> 
> Yes, just write a dummy message, select the mailbox, and store the flags.

That's ok if you're writing a new proprietary client, but not for users 
creating mailboxes the normal way.

I meant new, empty mailboxes, i.e., this list, which seems to be specified
by rfc3501 section 2.3.2.

  Pre-authenticated user rcgraves moe.unet.brandeis.edu IMAP4rev1 2003.339 
  at Thu, 8 Apr 2004 13:32:24 -0400 (EDT)
. create foobar2
. OK CREATE completed
. select foobar2
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1081445606] UID validity status
* OK [UIDNEXT 1] Predicted next UID
* FLAGS (\Answered \Flagged \Deleted \Draft \Seen)
* OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags
. OK [READ-WRITE] SELECT completed

Yuck. Looks like those are hardcoded and do not appear in the mbx file at 
all. Only newly defined ones do. Any hope?

I do see that

. store 999999 +FLAGS (Junk)

Succeeds in creating the "Junk" flag even if no message 999999 exists. But
that seems ugly, and how would I automate it upon mailbox creation?

Incidentally, the error message you get when trying to DELETE a currently
selected mailbox is a little misleading. It's not "another" process, it's
the current process. This annoys users when they try to delete an empty
mailbox from a GUI client. In some cases it can take some serious
gymnastics to shift-click and delete a mailbox without SELECTing it. I
always assumed this was a silliness about the GUI client, but it's the
server. So should client authors "have known" that they need to unselect a
mailbox otherwise in use? What about servers (including uw imapd until
recently) that don't implement UNSELECT?

. delete foobar2
. NO DELETE failed: Mailbox foobar2 is in use by another process
. unselect
. OK UNSELECT completed
. delete foobar2
. OK DELETE completed
-- 
Rich Graves <[EMAIL PROTECTED]>
UNet Systems Administrator

Reply via email to