Bug 364666

Summary: Expected a list enclosed in (), but got something else instead
Product: [Applications] trojita Reporter: philipp <usergate18>
Component: IMAPAssignee: Trojita default assignee <trojita-bugs>
Status: RESOLVED UPSTREAM    
Severity: normal CC: kde
Priority: NOR    
Version First Reported In: git   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=358898
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Exclude password and login from traff

Description philipp 2016-06-23 10:09:41 UTC
Created attachment 99667 [details]
Exclude password and login from traff

Version 0.7 builded for xUbuntu 16.04. installerd from repository.
Connect it to our IMAP-server and got this error:

15:49:28.847 <<< * STATUS Trash/Softline and other trash (MESSAGES 104 UNSEEN 0 RECENT 0)␍␊
15:49:28.847 <<< * STATUS Trash/Softline and other trash (MESSAGES 104 UNSEEN 0 RECENT 0)␍␊y29 OK STATUS completed.␍␊
15:49:28.847 UnexpectedHere Could not parse list: expected a list enclosed in (), but got something else instead␊* STATUS Trash/Softline and other trash (MESSAGES 104 UNSEEN 0 RECENT 0)␍␊␊                        ^ here
15:49:28.847 Imap::Mailbox::NumberOfMessagesTask attached to Trash/Softline and other trash Failed: Going offline
15:49:28.847 conn Logged out.
15:49:28.848 *** Connection killed.

Log from wireshark attached as text of the TCP-stream.
Comment 1 paalsteek 2016-06-23 11:17:40 UTC
According to RFC3501 mailbox names with special characters or spaces have to be quoted. This is done correctly by Trojitá (y29 STATUS "Trash/Softline and other trash" (MESSAGES UNSEEN RECENT)) but the server responds with the unquoted name (* STATUS Trash/Softline and other trash (MESSAGES 104 UNSEEN 0 RECENT 0)
y29 OK STATUS completed.).

Do you know what IMAP server software is running?
Comment 2 Jan Kundrát 2016-06-23 12:17:21 UTC
Yeah, the IMAP server violates RFC 3501 here. Looking at your e-mail address, it's probably yandex.ru, which means that it's a custom hand-crafted solution AFAIK. There's nothing that we can do here, you should contact their user support and report this as a bug.