IMAP needs to escape folder names with '/', the canonical hierarchy separator, when dealing with folders with '/' in the name (and unescape them when generating urls). This is not a problem on Netscape IMAP servers, because '/' is the hierarchy delimiter, but it is a problem on servers with other hierarchy delimiters. The code claims to expect the '/'s to be escaped, but I can't find any code that actually does the escaping, even back to 4.5.
No, it's not a dup, unfortunately for me. bug 29926, as near as I can tell has to do with CREATING folders that end with '/'. bug 56489 has to do with handling any hierarchy separator. This bug has to do with handling folder names with our "canonical" hiearchy separator, which is '/' when the '/' is not meant to be a hierarchy separator.
OK. More clear now. Thanks for the explanation.
adding mail3 keyword
Priority: P3 → P2
This is a feature blocking bug for the Lotus Domino IMAP server NAMESPACE feature. In Notes, user's full name always includes domain name. For example, Wei-Lee Jamrog/Iris. That is how we want to display other users' namespace. Without domain name that means users can only see other users that are in the same domain which is not practical at all. Without this fix, we are seriously limit the scope of NAMESPACE.
fixed so that we can display and read those folders with slashes in the name on servers where the hieararchy delimiter is not '/' (this fix only affects servers where the hiearchy delimiter is not '/', e.g., the Cyrus servers, and the Lotus Domino server). There are still some bugs - you can't create folders with '/' in the name on these servers, and the subscribe UI is confused about these folders. I'll open separate bugs on these.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Yes. Verified the fix on our in house Cyrus server which with "." hierarchy separator. Build 12-22-09-Mtrunk. I am marking as verified for this bug now. Wei-Lee, if problem is still occurring on your Lotus Domino server, please reopen this bug then.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.