office365 imap subscribe folders list is incomplete
Hello,
I setup an IMAP account on Thunderbird 38.5.1 client on Windows 7 64-bit, to access office365.com email.
Problem is when I right click on account and select "Subscribe..." option, the displayed list is not matching the full hierarchy I defined on server side, many folders are not displaying the contained subfolders.
Using refresh option doesn't help, the option "servers supports folders that contein subfolders" is already selected.
I did already lower "maximmum number of connections to cache" to 1, and this also doesn't help.
When I do the same client configuration using Evolution client on Linux, and I define the account as "IMAP+" , I do not see the problem, I can see the complete folders hierarchy to subscribe to.
I did also a complete account delete (including data directory below imapmail) and recreate from scratch, but the issue still appears.
How to fix this behavior ?
Thanks
Regards
Giorgio
All Replies (4)
While the re-created account data are syncing, I did setup another Thunderbird install, this time on Linux (Fedora 22 x86_64) it is version 38.4 Fedora 22 x86_64 package.
And I see first time I go to subscribe folders, I see the complete hierarchy and can select all what I need.
The behavior is : going back into other setup on Windows 7, and going again into "Subscribe..." , I see now the complete hierarchy here too.
So it seems a newer install / account setup from a different client system, can trigger the folders hierarchy info presented to IMAP subscribe to be refreshed.
So you are saying there is a bug in Office 365?
Modified
It doesn't seem a bug, because at the end I can get the complete hierarchy.
However this seems the workaround, also after I modified again my folders hierarchy, and got a first time a not complete subscribed folder tree, just setting up an IMAP account from scratch on a different system, I was able to get the complete hierarchy on the original system too.
well to me that is a bug in office 365. The site fails to perform as advertised unless you jump through an arcane workaround. That is a bug.