Bug 1928026 Comment 6 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Maybe there is a good explanation for why your server rejects the AUTH PLAIN command. But, regardless, I now have a fix that, after AUTH PLAIN fail, correctly moves on and tries AUTH LOGIN (if supported) and then USER/PASS login as last resort. So this should fix the problem you are seeing.
Right now I'm running a "try" build of the current daily version with my fix applied here: https://treeherder.mozilla.org/jobs?repo=try-comm-central&revision=f581f48c3ebb23d719e1d0327962b68efdb9775d
When this finishes you should be able to click on on the green "B" next to your desired computer platform and then down below click on "Artifacts and Debugging" tab and you should find the installation file to download:
- Linux or linux64 is target.tar.bz2 (just unzip and run thunderbird executable inside)
- Windows or windows64 is target.installer.exe
- Mac/OS is target.dmg

If you could verify that this fixes the problem by running the appropriate "try" build it would be most helpful.

I still need to submit a formal patch for approval to incorporate the fix into daily, then beta and finally the ESR release.
Maybe there is a good explanation for why your server rejects the AUTH PLAIN command. But, regardless, I now have a fix that, after AUTH PLAIN fail, correctly moves on and tries AUTH LOGIN (if supported) and then USER/PASS login as last resort. So this should fix the problem you are seeing.
Right now I'm making a "try" build of the current daily version with my fix applied here: https://treeherder.mozilla.org/jobs?repo=try-comm-central&revision=f581f48c3ebb23d719e1d0327962b68efdb9775d
When this finishes you should be able to click on on the green "B" next to your desired computer platform and then down below click on "Artifacts and Debugging" tab and you should find the installation file to download:
- Linux or linux64 is target.tar.bz2 (just unzip and run thunderbird executable inside)
- Windows or windows64 is target.installer.exe
- Mac/OS is target.dmg

If you could verify that this fixes the problem by running the appropriate "try" build it would be most helpful.

I still need to submit a formal patch for approval to incorporate the fix into daily, then beta and finally the ESR release.

Back to Bug 1928026 Comment 6