Autodiscover Encryption element not supported during account setup
Categories
(Thunderbird :: Account Manager, enhancement, P5)
Tracking
(Not tracked)
People
(Reporter: gaspard, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36
Steps to reproduce:
As per the Autodiscover protocol (https://interoperability.blob.core.windows.net/files/MS-OXDSCLI/%5BMS-OXDSCLI%5D.pdf), the SSL element is optional and can be replaced by the Encryption element. Thunderbird does not take into account the Encryption element, and would reply there is no encryption while there is: TLS for example. (Can also be Auto, None, and SSL).
Actual results:
I wanted to add an email account with autodiscover set up in the DNS and on my server. On the autodiscover server, I replaced the SSL element by the Encryption element as it is more detailed with two more parameters : "None" and "Auto". But Thunderbird does not support the Encryption element and thinks there is no encryption for the mail server, which is untrue.
Expected results:
If Thunderbird was supporting the Encryption element, the autodiscovery process would have fully worked and the mail account would have been added with the right encryption.
Comment 1•2 years ago
|
||
- Ben, is this autoconfig territory?
- HLFH, is this a bug or a request for feature enhancement?
- What are the exact steps which you are doing inside Thunderbird and which fail?
Comment 2•2 years ago
•
|
||
(In reply to HLFH from comment #0)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36
Steps to reproduce:
HLFH (Gaspard), can you please reply to my comment 1 and describe your exact steps inside Thunderbird?
Actual results:
I wanted to add an email account with autodiscover set up in the DNS and on my server. On the autodiscover server, I replaced the SSL element by the Encryption element as it is more detailed with two more parameters : "None" and "Auto". But Thunderbird does not support the Encryption element and thinks there is no encryption for the mail server, which is untrue.
How did Thunderbird "reply there is no encryption" or otherwise how did you see that "Thunderbird does not support the Encryption element"? (You can add privacy-redacted screenshots via Attach New File
button above comment 0.)
Expected results:
If Thunderbird was supporting the Encryption element, the autodiscovery process would have fully worked and the mail account would have been added with the right encryption.
Comment 3•2 years ago
|
||
Reporter refers to Microsoft documentation:
[MS-OXDSCLI]: Autodiscover Publishing and Lookup Protocol.
Do we know if this is something we should care about for interoperability during account setup?
Comment 4•2 years ago
|
||
Let's keep a copy of the document mentioned in comment 0 FTR.
Attached: [MS-OXDSCLI] Autodiscover Publishing and Lookup Protocol.pdf
Comment 5•2 years ago
|
||
Not my area of expertise, sorry, I wouldn't know what to decide here.
Gentle ping for Andrei to see if he has any suggestion on who's most suited to make a decision.
Comment 6•2 years ago
|
||
This is not very relevant in practice, because this property is valid only for IMAP, POP3 and SMTP (per the doc), and (on-premise) Microsoft Exchange usually doesn't list these protocols in Autodiscover, even if they are enabled.
Comment 7•2 years ago
•
|
||
@Gaspard DHautefeuille, could you please list steps in Thunderbird UI, with a concrete and specific email domain, where this fails, so that there's at least one test case? As I said, these are exceedingly rare.
Updated•2 years ago
|
Comment hidden (off-topic) |
Updated•2 years ago
|
Comment 9•2 years ago
|
||
It's not clear to me if this is even worth supporting, as Ben said it seems like it would be very uncommon.
Comment 10•2 years ago
|
||
Closing as WONTFIX
Comment 11•1 month ago
|
||
Actually, added support in bug 1876992.
Description
•