User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0.1) Gecko/20100101 Firefox/8.0.1 Build ID: 20111120135848 Steps to reproduce: Interacting with IMAP server. Running TB 9.0.1 on Mac OS X 10.6.8. Create new sub-folder X which contains folders only. Actual results: X does not appear in the hierarchy of folders. Run subscribe for that email account. Refresh. X does appear in folders list. Also, X is created as a directory on IMAP server. Expected results: X should appear in the hierarchy of folders.

(In reply to Arthur Goldberg from comment #0) See bug 234010. I tried it on an IMAP server and it doesn't create the subfolder: User Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 Application Build ID: 20111222141531

Thanks Hashem. What do you mean when you say "it doesn't create the subfolder"? Does the new subfolder appear in subscribe's list of folders, is it created as a directory on the IMAP server, does it appear in the folders list? Thanks (In reply to Hashem Masoud from comment #1) > (In reply to Arthur Goldberg from comment #0) > See bug 234010. I tried it on an IMAP server and it doesn't create the > subfolder: > User Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 > Thunderbird/9.0.1 > Application Build ID: 20111222141531

The IMAP server is running dovecot Version 2.0.13

(In reply to Arthur Goldberg from comment #2) > Thanks Hashem. > What do you mean when you say "it doesn't create the subfolder"? I meant not being able to create the subfolder. Basically I have the same issue as the one you are facing. Check the bug I mentioned above, maybe it is similar to this issue.

Hi Hashem This is not <a href="show_bug.cgi?id=234010">bug 234010</a>, because that bug says "Unable to create subfolders in IMAP accounts. ... No error generated, but folder never appears, not created on Server." My behavior is that the sub-folder IS created on the server. That's why I asked: "Does the new subfolder appear in subscribe's list of folders, and is it created as a directory on the IMAP server?" Answers to those questions would be helpful.

Can we get an imap log as described at https://wiki.mozilla.org/MailNews:Logging#Other_Protocol_Logging_options_within_MailNews ?

(In reply to Ludovic Hirlimann [:Usul] from comment #6) > Can we get an imap log as described at > https://wiki.mozilla.org/MailNews: > Logging#Other_Protocol_Logging_options_within_MailNews ? Hi Ludovic Thanks. I have an IMAP log. I did export NSPR_LOG_MODULES=imap:4. However, I'm reluctant to post it, as it contains somewhat sensitive info, such as folder names, etc. Can I filter down the data and/or just email it to you? Thanks Arthur

Arthur, you can send the log to me - you're using IMAP subscription, right, so in advanced server settings for the imap account in thunderbird, it says "Show only subscribed folders"?

(In reply to Arthur Goldberg from comment #7) > I'm reluctant to post it, as it contains somewhat sensitive info, such as folder names, etc. See bug 710507 for similar phenomenon to yours in Yahoo! IMAP when "Show only subscribed folders"=Off(cause is "no subfolder is retured to LIST .../%/% from Yahoo! IMAP"). Relevant and required log is for (a) command/response of NAMESPACE, (b) untagged response(* folder_name attributes) of LIST and LSUB command for relevant mail folders(paret folder of the X and the X folder), and (c) LIST/LSUB command and OK response for (b). Remove any other logs from log file, and if folder name in relevant LIST/LSUB command/response is confidential data, replace it with keeping consistency of folder names, please. LIST confidential-folder-name => LIST replaced-folder-name * confidential-folder-name ... => * replaced-folder-name ... OK > The IMAP server is running dovecot Version 2.0.13 As Dovecot, cause is probably "no required attribute in LSUB and/or LIST response" or "wrong attribute string in LIST/LSUB response". To avoid problem due to above, there is option of "Server supports folder that contains sub-folders and messages"=Off in Server Setings/Advanced. Does "double click of parent folder of the X" show expand button of the parent folder? As subfolders of the folder is shown in subscription list, Tb perhaps requests "LIST .../parent-folder/%" when double-click'ed. If subfolders are retruned to the LIST command, Tb tries to show them at folder pane, then expand button is shown at folder pane. This worked well for Yahoo! IMAP, because Yahoo! IMAP normally returns subfolders if "LIST .../parent-folder/%", although no subfolders is returned when "LIST .../parent-folder/%/%".

(In reply to David :Bienvenu from comment #8) > Arthur, you can send the log to me - you're using IMAP subscription, right, > so in advanced server settings for the imap account in thunderbird, it says > "Show only subscribed folders"? Yes.

(In reply to WADA from comment #9) > (In reply to Arthur Goldberg from comment #7) > > I'm reluctant to post it, as it contains somewhat sensitive info, such as folder names, etc. > > See bug 710507 for similar phenomenon to yours in Yahoo! IMAP when "Show > only subscribed folders"=Off(cause is "no subfolder is retured to LIST > .../%/% from Yahoo! IMAP"). Note that "Show only subscribed folders" is checked. Does that mean =On or =Off? > Relevant and required log is for (a) command/response of NAMESPACE, (b) > untagged response(* folder_name attributes) of LIST and LSUB command for > relevant mail folders(paret folder of the X and the X folder), and (c) > LIST/LSUB command and OK response for (b). > Remove any other logs from log file, and if folder name in relevant > LIST/LSUB command/response is confidential data, replace it with keeping > consistency of folder names, please. > LIST confidential-folder-name => LIST replaced-folder-name > * confidential-folder-name ... => * replaced-folder-name ... > OK I'm a little unclear what you want, so I'll email it to you and ask that you clean it before any posting. Preferably, just post relevant snippets. > > > The IMAP server is running dovecot Version 2.0.13 > > As Dovecot, cause is probably "no required attribute in LSUB and/or LIST > response" or "wrong attribute string in LIST/LSUB response". > To avoid problem due to above, there is option of "Server supports folder > that contains sub-folders and messages"=Off in Server Setings/Advanced. Yes, "Server supports folder that contains sub-folders and messages" is not checked, which I presume means =Off. This gives me an idea, however. I tried checking that option. And VOILA! Now I am able to create a Folder that appears in the Folder tree. Now, in the past I needed to leave this option unchecked for this IMAP server, but I think the server software has changed in the interim. Now we can debate whether this is a bug. I would argue that Tb, not the user, should determine whether "Server supports folder that contains sub-folders and messages", and therefore it should NOT be an option. Is this possible? Does IMAP contain a SERVER_TYPE message? I couldn't find one. Thanks Arthur

(In reply to Arthur Goldberg from comment #11) > Note that "Show only subscribed folders" is checked. > Does that mean =On or =Off? I meant "Checed" by =On, and "Unchecked" by =Off.

Arthur, does the folder appear if you restart? Does the log you sent me have an example of the bug, where you tried to create a folder? I don't see any attempt to create a folder in the log, other than the Trash folder. And how do you create the folder that only has subfolders? By creating "X/Y"?

There are two possible states of "Server supports folders that contain sub-folders and messages". I'll call these complex folders. Behavior differs between the two states. Checked aka On: TB behaves as expected. Newly created folders appear in the folder tree, deleted folders are removed from the tree. Unchecked aka Off: TB behaves as in the bug report above. Newly created folders never appear, either after creation or after restart and/or reboot. In a narrow sense one can argue that I've been using TB incorrectly, since my options should have said the server supports complex folders. But (as I said to the DA) I didn't know. I believe this is the sequence of events that got me to this situation. Long ago my mail provider ran an IMAP server that did not supports complex folders, and I recall things not working when I checked the box. So I did not check the box. And things worked OK. Years passed. People were born and died. Glaciers receded. :-) My mail provider changed their IMAP server to one that does support complex folders. But I didn't know that. My computers changed, but when I set up IMAP I still did not check the box. And I didn't create new folders so TB worked OK, although it was incorrectly configured. Then I tried to create a folder and ran into the bug we're investigating. This leads me to the following conclusion. I feel very strongly that even under an 'advanced' option, users should not be responsible for, or even have an opportunity to, indicate whether the server supports complex folders. First, it is difficult for them to know the right choice, and second, the right choice may change without them knowing. Arthur PS. David, you're right the log doesn't have folder creation operations. Sorry about that. I can make a log with those, but not right now. (In reply to David :Bienvenu from comment #13) > Arthur, does the folder appear if you restart? Does the log you sent me have > an example of the bug, where you tried to create a folder? I don't see any > attempt to create a folder in the log, other than the Trash folder. And how > do you create the folder that only has subfolders? By creating "X/Y"?

(In reply to Arthur Goldberg from comment #14) Continuing ... Suppose the Complex folder option is removed. How would we implement that? Here I'm guessing, as I'm not familiar with the code. But I see to main options: identify the IMAP server type and lookup its complex folder support in a table, or detect whether the server supports complex folders experimentally. 1) identify the IMAP server type and lookup its complex folder support in a table: there are are relatively small number of IMAP servers in wide use (and most of them support complex folders, I read), so it would be easy to maintain a mapping from server type to complex folder support. the code could assume that an unknown server did not support complex folders, and perhaps report the detection of such a server to the development team. but, unfortunately, as far as I can tell, the IMAP protocol doesn't support this. according to 3501 the CAPABILITY command doesn't indicate complex folder support, although it could. 2) a reliable, general-purpose means to determine whether a server provides complex folder support would be to try it. create some test folders and see. then delete them. this could be added to a login activity. naturally, it would need to be very careful to not conflict with real data. I think these are worth investigating. A

(In reply to Arthur Goldberg from comment #14) > PS. David, you're right the log doesn't have folder creation operations. > Sorry about that. I can make a log with those, but not right now. please do so we can move the bug along

Resolved per whiteboard