为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

Latest - MS Exchange on TB 102

  • 5 个回答
  • 0 人有此问题
  • 1 次查看
  • 最后回复者为 Matt

more options

This question has been asked previously on this forum, with the quires and various proposed solutions dating back several years, in some cases.

GoDaddy.com is - again - stating that, as of June 24, 2023, email clients such as TB will not be able to send or receive MS Exchange email messages using basic authentication. The settings need to be updated from POP/IMAP to Exchange. Our company has received this same alert from Godaddy several times in the last couple of years, each with different sunset dates. TB continues to function with our MS accounts as of the posting date of this question. Proposed solutions included changing the incoming and outgoing sever settings in TB to "OAuth 2.0" as well as downloading a 3rd party AP such as "Owl". Some report that the Apps do work, but wreck the existing TB folder structure. We have tried the OAuth 2.0 settings in the past but they always result in a "cannot connect to server" error message. Going back to ssl/tls [incoming] and starttls [outgoing] settings restores functionality. GoDaddy advises us that, as TB is a 3rd party email client, they do not have any guidance on a resolution and to just use the MS web based Exchange portal or install the Exchange AP, which management does not want to do.

We need to continue to use TB. Can anyone advise for certain how to configure the settings to work with MS Exchange email? If there is no way to do so, which app[s] are know to work from direct experience and won't break the TB folder structure? Thank you in advance for any help.

This question has been asked previously on this forum, with the quires and various proposed solutions dating back several years, in some cases. GoDaddy.com is - again - stating that, as of June 24, 2023, email clients such as TB will not be able to send or receive MS Exchange email messages using basic authentication. The settings need to be updated from POP/IMAP to Exchange. Our company has received this same alert from Godaddy several times in the last couple of years, each with different sunset dates. TB continues to function with our MS accounts as of the posting date of this question. Proposed solutions included changing the incoming and outgoing sever settings in TB to "OAuth 2.0" as well as downloading a 3rd party AP such as "Owl". Some report that the Apps do work, but wreck the existing TB folder structure. We have tried the OAuth 2.0 settings in the past but they always result in a "cannot connect to server" error message. Going back to ssl/tls [incoming] and starttls [outgoing] settings restores functionality. GoDaddy advises us that, as TB is a 3rd party email client, they do not have any guidance on a resolution and to just use the MS web based Exchange portal or install the Exchange AP, which management does not want to do. We need to continue to use TB. Can anyone advise for certain how to configure the settings to work with MS Exchange email? If there is no way to do so, which app[s] are know to work from direct experience and won't break the TB folder structure? Thank you in advance for any help.

所有回复 (5)

more options

The two addons, OWL and EXQUILLA, continue to work well with Exchange. There is a freeware product, DAVMAIL, that also works, but does not appear to have some of the same functions as the two addons.

more options

David,

Thanks for the reply. Do you have direct experience using any of the apps with TB??

more options

Yes, I used Exquilla for a few years and enjoyed the extensive access to corporate addressbook, something that Davmail lacked. I have also seen positive comments here from Owl users. I think there is a 30-day trial.

more options

OK. I've read others comments in support that 1 of the add ons - Owl? - broke the folder tree.

Anyone else care to comment?

more options

Given both the add-ons mentioned are maintained by Beonex, I really think the approach is use the one they wrote themselves (OWL) instead of one they took over maintenance on (Exquilla ) Beyond that there is nothing really to discuss, internally I am guessing they are becoming more similar all the time, but as it is closed source, there is no one but the owner/author of the add-on that knows exactly how they work or what they do.