Thunderbird tries enabling UTF8=ACCEPT even when not available
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
People
(Reporter: mail, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3650.1 Iron Safari/537.36
Steps to reproduce:
In Thunderbird 102.10.0 portable, the client always attempts to enable UTF8=ACCEPT, even when this capability is not advertised by the IMAP server.
Possible regression introduced by 1571672.
Actual results:
<= * CAPABILITY IMAP4rev1 AUTH=PLAIN UNSELECT CHILDREN IDLE NAMESPACE QUOTA QUOTA=RES-STORAGE ID SASL-IR ACL SORT URLAUTH ESEARCH ESORT SEARCHRES UIDPLUS APPENDLIMIT MOVE WITHIN ENABLE CONDSTORE QRESYNC
=> 53 ENABLE UTF8=ACCEPT
<= 53 BAD [CLIENTBUG] Bad capability
Expected results:
Thunderbird should not try to enable capabilities that are not available on the IMAP server.
|
||
Updated•2 years ago
|
|
||
Comment 1•2 years ago
•
|
||
Reporter,
Is this causing any other problems with TB?
Also, curious as to which imap server type you see this on?
The bug is actually a server bug and not a client bug. As long as ENABLE capability is present this command sequence is legal to try to enable unsupported capability FOO:
c: 53 ENABLE FOO
s: 53 OK
If FOO is something actually supported in capabilites, the server should respond like this:
c: 53 ENABLE FOO
s: * ENABLED FOO
s: 53 OK
So the untagged "ENABLED FOO" response tell us that the server supports FOO. Lack of this untagged response indicates that FOO is not supported.
Anyhow, this issue has been fixed in bug 1673158 but it is not yet in 102. That fix does as you suggest and doesn't try to enable UTF8 unless it is actually listed in the capabilities.
Description
•