Unable to subscribe to Office 365 IMAP folders from MUA since 2022-11-01

Anonymous
2022-11-02T07:33:01+00:00

I'm using Thunderbird to access my Office 365 mail account and it has been working fine (a couple of month ago I also switched to OAuth2 due to deprecation of basic IMAP authentication). However, since 2022-11-01, Thunderbird is unable to subscribe to IMAP folders. Last time I know it was working was last Friday 2022-10-28. Thunderbird is able to list to available folders (e.g. when opening the "Subscribe" dialog from the mail account settings), but cannot subscribe to them. I enabled IMAP logging in Thunderbird, and it shows that the server answer the subscribe request with "BAD SUBSCRIBE".

It is not a password/authentication issue, as Thunderbird can still see the content of "Inbox" and "Deleted Items". And if I disable the option "Show only subscribed folders", it can access everything in my Office 265 account.

Edit: here's the relevant logs from Thunderbird (note: I've replaced the actual folder name with "xxxx"):

[Parent ...: IMAP]: I/IMAP ...:outlook.office365.com:A:SendData: 76 subscribe "INBOX/xxxx"

[Parent ...: IMAP]: I/IMAP ...:outlook.office365.com:A:CreateNewLineFromSocket: 76 BAD SUBSCRIBE failed.
Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

106 answers

Sort by: Oldest
  1. Anonymous
    2022-12-03T02:58:08+00:00

    I simply cannot believe it. One month since the initial bug report and no fix yet; shouldn't this be a high priority issue?

    The bug hit me just yesterday. Our university had the grandiose idea to switch their email server from a local one to the Microsoft 365 cloud.

    Looking at the number of people that are using Linux, or macOS-based operating systems, I'd image that thousands of users are affected by this broken implementation on our campus alone. And we even paid for that mess with taxpayer's money.

    You would assume that these things are being tested before they are being deployed on a large scale?! Well done Microsoft, well done...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-12-03T12:22:12+00:00

    I simply cannot believe it. One month since the initial bug report and no fix yet; shouldn't this be a high priority issue?

    The bug hit me just yesterday. Our university had the grandiose idea to switch their email server from a local one to the Microsoft 365 cloud.

    Looking at the number of people that are using Linux, or macOS-based operating systems, I'd image that thousands of users are affected by this broken implementation on our campus alone. And we even paid for that mess with taxpayer's money.

    You would assume that these things are being tested before they are being deployed on a large scale?! Well done Microsoft, well done...

    I chased it up on the 30th and no update - and I did point out that they had been sat on a service affecting fault for a whole month.

    My previous advice still stands. Each individual O365 system administrator with affected users needs to be raising their own service request in Admin Centre - and perhaps cross referring to the one I have already posted up if they are certain they are seeing the exact same fault. It only takes a few seconds to do this from the O365 Admin Centre menu (see below) so there is no excuse not to, if people want to see this fixed.

    Imagining that thousands* of users are affected is not the same as Microsoft having it evidenced to them in the form of incident reports.

    *You may well be right, but remember that this is far less likely to affect corporates who will tend to own and be in complete control of end users devices, and will generally be on Outlook over MAPI - so this will simply not be on Microsoft's radar as a priority unless those of us who are affected put it there.

    My O365 tenant is non-profit related where I have no control whatsoever over the email client apps my users choose to use, and educational establishments will tend to be in a similar position with their students.

    Image

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-12-03T12:54:05+00:00

    Dear Michael,

     

    Good day!

    Thank you for posting to Microsoft Community. We are happy to help you.

     

    Based on your description, I understand that you have a concern with "Unable to subscribe to Office 365 IMAP folders from MUA" At this very moment, I am looking into whether there could be a possible solution to this issue. I will get back to you as soon as I get any additional information about your query.

     

    Your patience and cooperation are much appreciated.

     

    Sincerely,

    Ashraf | Microsoft Community Moderator

    Any progress from your side Ashraf?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-12-04T19:49:30+00:00

    For those that missed it....

    DISABLE the Thunderbird option: "SHOW ONLY SUBSCRIBED FOLDERS"

    Located at: 'Tools' > 'Account Settings' > 'Server Settings' > 'Advanced' > "show only subscribed folders"

    Uncheck that and then get messages and all folders will show up.

    Having all folders shown is better than missing the important ones.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2022-12-04T20:53:05+00:00

    For those that missed it....

    DISABLE the Thunderbird option: "SHOW ONLY SUBSCRIBED FOLDERS"

    Located at: 'Tools' > 'Account Settings' > 'Server Settings' > 'Advanced' > "show only subscribed folders"

    Uncheck that and then get messages and all folders will show up.

    Having all folders shown is better than missing the important ones.

    This provides at best an ugly hack to the problem that the last update (?) of Microsoft's MAPI (or OAuth2) implementation created in the first place.

    However, this hack of changing the synchronization/subscription settings appears to work only for the Thunderbird mail client.

    Be aware that a plethora of MUAs besides Thunderbird are affected. According to the other replies it has become apparent that such a solution does not exist for every email client out there.

    And switching to Outlook is simply not a solution when affected users are on macOS/iOS or GNU/Linux - based operating systems.

    The IMAP protocol - a de facto standard - should be adhered to, also by *Microsoft'*s implementation thereof.

    Edit: It appears that the guys on the Vivaldi mail client development team have located the issue.

    To my understanding Microsoft O365's IMAP implementation has dropped support for 'LSUB' without documenting this.

    See their discussion: https://forum.vivaldi.net/topic/80723/lsub-failed-with-office-365-imap-server/9

    Was this answer helpful?

    0 comments No comments