Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

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

  • 2 Antworten
  • 1 hat dieses Problem
  • 6 Aufrufe
  • Letzte Antwort von 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.

Alle Antworten (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.