Whenever I start up messenger, I get ASSERTION: hierarchy separator unknown: 'delimiterToUse != kOnlineHierarchySeparatorUnknown', file c:\mozsrc\mozilla\mailnews\imap\src\nsImapUrl.cpp, line 725 The debugger shows that it is working on the name "foo". My folders are as follows: >0.009>* LSUB (\NoInferiors) "/" INBOX * LSUB (\HasNoChildren) "/" Drafts * LSUB (\HasNoChildren) "/" Old * LSUB (\HasNoChildren) "/" Sent * LSUB (\HasNoChildren) "/" Trash * LSUB (\HasNoChildren) "/" foo/bar * LSUB (\HasNoChildren) "/" r&AOk-pertoires * LSUB (\HasNoChildren) "/" wallace&-gromit 5 OK Completed <0.064<6 lsub "" "Shared Folders/User/*" I notice that "foo" isn't displayed in grey as it is in 4.71, but that's probably a separate bug. >0.001>6 OK Completed
I can't remember if it was Jeff or David that was poking at this stuff recently..
Assignee: mscott → jefft
We both were, but I think it was still working when I stopped poking at it :-)
Fix checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
QA Contact: lchiang → huang
John, I am trying to verify this bug. Please provide the answers of the following questions: 1) Was this bug logged for UW IMAP server? 2) From thes two lines: LSUB (\HasNoChildren) "/" foo/bar "foo" isn't displayed in grey.. So, is "foo" folder-only folder and "bar" message-only folder?
I was using a Netscape server to test this. I telented to the IMAP port and did a "tag create foo/bar" to create that test folder, then I subscribed to it. "foo" is folder-only and "bar" is currently message-only. "bar" may contain subfolders in the future.
And foo should have the \NoSelect flag if I am correct. The display for grey will be fixed when I check in fixes for 28916, 28301, & 27396.
My questions are: 1) Isn't NMS IMAP only provide dual-use-folders? Are you sure this bug is logged for NMS server? 2) Why I didn't see "foo" grey out from 4.7 NMS? 3) If "bar" is message-only folder, why it will contain subfolder in the future?
But, if I create a/b folder from NMS, "a" will gey out, and "b" will be the subfoler of "a", there was bug#29926 logged, but even that, why "a" turn to grey on 4.7? Also, how can I get into non-dual-use-folder from NMS 4.7?
Bar currently only contains messages. It may contain messages in the future. Foo currently cannot contain messages. If someone does a "CREATE foo", then it may start containing messages. I am sure this is against a Netscape 4.15p1 server.
Thanks John. OK. I see......there was problem on 4.7 NMS client side. (But nobody logged that bug on 4.7 before...) I think that I will keep an eye on 5.0..... And, Jeff, I only see \HasNoChildren for foo folder. Marking as verified for this bug since there is no "hierarchy separator unknown" error anymore by following John's procedures.
Status: RESOLVED → VERIFIED
And I was using on 03-07-09-M15 WinNT commercial build.
Jeff, you are right! foo should have the \NoSelect flag but it just didn't be reported for NMS server before.....
I am not sure that is a bug on 4.7 client. 4.7 client only grey out if the mailbox has \NoSelect flag set. I am not sure that creating "foo/bar" without creating "foo" first will set the "foo" with \NoSelect flag for Netscape 4.15 server.
Whiteboard: verified → This will be fixed along fixing bug 26547
Yes. It seems that Jeff bring up the good point... John, can you answer the question?
There is no requirement in the protocol that the server issue a response for the "foo" hierarchy level. The presense and nonselectability of that level of hierarchy can be inferred from the "foo/bar" response.
You need to log in before you can comment on or make changes to this bug.