Closed Bug 1082458 Opened 10 years ago Closed 2 years ago

Thunderbird don't refresh the list of subfolders on a shared imap account

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: nico286, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux i686; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140918134118

Steps to reproduce:

I use a shared IMAP account with subfolders in it.
Users of that shared imap account may create subfolders.


Actual results:

When someone creates a folder or change his name, the others users of the shared mail account can't see that folder, even if they refresh.
It seems that the only way to "update" the folders list is to close and restart Thunderbird, or use "open in new window".


Expected results:

When someone creates a new folder, everyone should see it immediately. As quickly as he can see new mails
Component: Folder and Message Lists → Networking: IMAP
Product: Thunderbird → MailNews Core

(In reply to nico286 from comment #0)

...
When someone creates a new folder, everyone should see it immediately. As
quickly as he can see new mails

this would only happen with idle enabled, correct?

Flags: needinfo?(gds)

I don't think it has anything to do with imap idle. Idle only notifies there are new messages in an existing folder, not that there is a new (sub)folder. I don't know of a mechanism in imap that monitors for and notifies there is a new folder, regardless if it is shared or private.

It seems that the only way to "update" the folders list is to close and restart Thunderbird, or use "open in new window".

A somewhat undocumented way to "re-discover" the folder list is to collapse/expand the folder tree at the account root level. This usually works except for a when oauth2 is used (e.g., gmail) since it can't get a password.

Flags: needinfo?(gds)
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.