Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Latest - MS Exchange on TB 102

  • 5 respuestas
  • 0 tienen este problema
  • 1 visita
  • Última respuesta de 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.

Todas las respuestas (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.