On Thu, 24 Jul 2003, George Lindholm wrote:
I crated two files named 'b &- d' and 'C & D' and then did a:
"C & D" is not a valid mailbox name.
"b &- d" is a mailbox name which should display as "b & d".
As you can see, the folder name of 'b &- d' comes out as 'b & d' and of 'C & D' comes out as 'C '. This makes in difficult, if not impossible to access the folders.
Yup...
And if I read RFC3501, section 5.1.3, correctly, isn't the imap server supposed to escape the '&' properly since this is the signal to the client that the string is BASE64 encoded?
There is no requirement for the IMAP server to do any escaping. In UW imapd, the file names are the same as the mailbox names. UW imapd won't protect you if you create a file with a name that is an invalid mailbox name. The client is responsible for not doing that.
We are moving away from local filesystem access to the folders to imap access, and unfortunately, pine allows you to create folders with '&' (as well as '*' and '%") so we have a number of users out there that have created folders with these characters of the years that now can no longer access them.
George -- [EMAIL PROTECTED] ITServices, UBC Programmer/Analyst
phone: 604.822.4375 fax: 604.822.5116
