搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Can not synchronize Inbox from Office 365, other folder is fine

  • 4 个回答
  • 1 人有此问题
  • 3 次查看
  • 最后回复者为 tommydyr1

more options

Hi, I'm a novice to use thunderbird mail client to take place of Outlook 2013. To sign in office 365 account is absolutely straightforward. However, when Thunderbird commence to synchronize with Office 365, there is a pop-up to say "The current operation on Inbox did not succeed. The mail server for account Leo.Zhang@XXXX.com reponded:INBOX doesn't exist".

This situation is not new to me. I use another mail client "Netease mail master"(popular in China mainland) also meet the same issue.

I'm sure the inbox is existing as it work properly at Outlook 2013. How can I make it work for me?

Thanks and best regards,

Leo Zhang

Hi, I'm a novice to use thunderbird mail client to take place of Outlook 2013. To sign in office 365 account is absolutely straightforward. However, when Thunderbird commence to synchronize with Office 365, there is a pop-up to say "The current operation on Inbox did not succeed. The mail server for account Leo.Zhang@XXXX.com reponded:INBOX doesn't exist". This situation is not new to me. I use another mail client "Netease mail master"(popular in China mainland) also meet the same issue. I'm sure the inbox is existing as it work properly at Outlook 2013. How can I make it work for me? Thanks and best regards, Leo Zhang

被采纳的解决方案

There are a couple of issues here.

1. outlook does not use IMAP to talk to exchange which is what the mail server in O365 is. so what Outlook does and what any other mail client does can not be compared. Just as what I write probably would no make any sense literally translated into another language.

2. Microsoft has a somewhat quirky implementation of IMAP.

3. You XX'ed out the domain, so I must assume it is not a generic hotmail or outlook one. In this instance it is possible that the administrator has not enabled IMAP at all for the domain.

4. Do you use the exchange addon OWL https://addons.thunderbird.net/en-US/thunderbird/addon/owl-for-exchange/?src=ss This enable contacting o365 accounts without IMAP.

If I am getting it wrong here. It is possible that he issue may be localization of folder names. Is you Thunderbird version for the same language as the native server? Perhaps an English or a Chinese language version might not present the problem

定位到答案原位置 👍 1

所有回复 (4)

more options

选择的解决方案

There are a couple of issues here.

1. outlook does not use IMAP to talk to exchange which is what the mail server in O365 is. so what Outlook does and what any other mail client does can not be compared. Just as what I write probably would no make any sense literally translated into another language.

2. Microsoft has a somewhat quirky implementation of IMAP.

3. You XX'ed out the domain, so I must assume it is not a generic hotmail or outlook one. In this instance it is possible that the administrator has not enabled IMAP at all for the domain.

4. Do you use the exchange addon OWL https://addons.thunderbird.net/en-US/thunderbird/addon/owl-for-exchange/?src=ss This enable contacting o365 accounts without IMAP.

If I am getting it wrong here. It is possible that he issue may be localization of folder names. Is you Thunderbird version for the same language as the native server? Perhaps an English or a Chinese language version might not present the problem

more options

Dear Matt,

Thank you. I use OWL as workaround though it's not free~

I also checked my email inbox, actually as your assumed, it is in Chinese.

This may caused the sync issue.

Thanks again.

Leo

more options

The owl addon page has a support address, I suggest you use it. They are keep to fix issues especially bugs, and this sounds like a bug

more options

I have an office 365 account setup in Thunderbird as well; what's interesting, Thunderbird can receive office 365 email but Thunderbird cannot send email using Office365 smtp settings; Because I used Thunderbird for multiple email accounts, I simply changed the outgoing server to another smtp account for outgoing mail and bypassed the proprietary bs that is Microsoft