Can anyone shred some light on the #driver.mbx stuff? How is the client supposed to figure the below case out by itself? It seems as if it only works because c-client has this behaviour hard coded, but then it of course doesn't work for non-c-client clients.
-------------------- Start of forwarded message -------------------- From: Simon Josefsson <[EMAIL PROTECTED]> Newsgroups: gnu.emacs.gnus Subject: Re: How to create new groups with nnimap Date: Mon, 22 Apr 2002 19:12:03 +0200 Message-ID: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Nevin Kapur <[EMAIL PROTECTED]> writes: > I want to create a mailbox (say try) in mbx format on a UW IMAP > server. The way to do this is to create a group called > #driver.mbx/try. One I fiddle around with gnus-invalid-group-regexp, > I can do this. However the group shows up as nnimap:#driver.mbx/try > and then I can't access it. > > 456 CREATE "#driver.mbx/try" > 456 OK CREATE completed > 457 SELECT "#driver.mbx/try" > 457 NO SELECT failed: Can't open mailbox #driver.mbx/try: no such mailbox > 458 SELECT "#driver.mbx/try" > 458 NO SELECT failed: Can't open mailbox #driver.mbx/try: no such mailbox > > UW's documentation says that to access this mailbox should be accessed > as try, just like any other mailbox. > > I guess this is more of a feature request: on a UW server, a 'G m' > that starts with #driver.xxx/group should send then > name verbatim to the server for the CREATE command but should create a > group whose name does not have the #driver.xxx string. This is really weird, I cannot see any bearing for this kind of behaviour in the IMAP spec. As the IMAP author wrote the UW server, perhaps we can ask on the IMAP list. Is it OK to forward the above? I don't understand how a client is supposed to know that mailboxes it creates are to be accessed under a different name. -------------------- End of forwarded message --------------------
