On Tue, 24 Oct 2006, Michael Schaap wrote:
imapd 2006c can still delete a currently-selected mbx mailbox, though - but
that's not "intentionally", I assume. :-)
It's not supposed to do so, and it doesn't on my system:
. create #driver.mbx/foo
. OK CREATE completed
. select foo
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1161645269] 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
. delete foo
. NO Can not DELETE the selected mailbox
If you use something like ~/foo to work around the test in imapd, locking
should still prevent it:
. delete ~/foo
. NO Mailbox ~/foo is in use by another process
So the only way you should be able to delete a currently-selected mbx
mailbox is if the file is accessed via NFS. But use of NFS for mbx format
files isn't supported and will quickly lead to corrupted files.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
