Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Thunderbird can't subscribe to Outlook's sub-folders

  • 2 wótegronje
  • 1 ma toś ten problem
  • 6 naglědow
  • Slědne wótegrono wót whebs

more options

Using outlook.office365 set up with IMAP. I am able to subscribe to the folders that exist in my inbox, but I do not see any of those folders' sub-folders in the subscribe dialogue.

Show only subscribed folders & Server supports sub-folders are both selected. Showing all folders (not just subscribed) hasn't resolved the issue.

Using outlook.office365 set up with IMAP. I am able to subscribe to the folders that exist in my inbox, but I do not see any of those folders' sub-folders in the subscribe dialogue. Show only subscribed folders & Server supports sub-folders are both selected. Showing all folders (not just subscribed) hasn't resolved the issue.

Wšykne wótegrona (2)

more options

I think there were bugs affecting subscriptions to folders with either long names or strange characters, but suspect this bug may apply if you have subfolders nested higher than 2 levels, i.e. sub-subfolder.

I would suggest creating one new subfolder on the server using webmail, move the affected messages there, and see if you can subscribe to that new folder. If things work after syncing, you can choose to remove the old subfolder and recreate it, or leave it out if the folder structure contains more than 2 levels. If you feel comfortable doing so, you could experiment to see to what folder level or for which characters/names the issue still occurs.

more options

Thank you for your effort, but I solved the problem by switching to eM Client.