On Monday, 25 January 2016 04:47:41 CET, SagaXu wrote:
* 1 FETCH (UID 1325373061 INTERNALDATE "22-Dec-2015 15:57:52 +0800" ENVELOPE ("22-Dec-2015 15:57:50 +0800" "=?UTF-8?B?UmU6IFFBIENsYXJpZmljYXRpb25z?=" (("=?UTF-8?B?U2FnYVh1?=" NIL "saga.xu" "avantport.com")) NIL NIL (("=?UTF-8?B?UWl0b25nIFh1?=" NIL "QXu" "roamdata.com")) NIL NIL ((NIL NIL "ECD46103-4C38-4183-8D0F-FB47AD528DD9" "roamdata.com")) "") BODYSTRUCTURE ("text" "plain" ("charset" "US-ASCII") NIL NIL "7bit" 1548 40 NIL NIL NIL) RFC822.SIZE 3216 BODY[HEADER.FIELDS (REFERENCES LIST-POST)] {139} References: )
Hi, thanks for your bugreport. This IMAP server is broken on several fronts:
1) It's trying to send the "env-in-reply-to" field using a similar syntax as the from/cc/... fields, which is a bug. It MUST be sent as a string.
2) The format of the date doesn't follow RFC5322, but is instead using something similar to IMAP's INTERNALDATE. That's also a bug.
These two errors together very strongly suggest that the IMAP server has seen just a very limited amount of interoperability testing. As it happens, many IMAP clients are not using all aspects of the IMAP protocol (which makes them slower than needed). Trojita is different, it relies on reasonable performance of the IMAP server, and if the server sends garbage, Trojita gives up.
Now, both of these two flaws could be patched, we can have a local workaround within Trojita (see the patch at [1] for some very quick & dirty solution; the test suite needs work in particular). However, my intuition tells me that there will be many more bugs in this particular IMAP server, and that this might be an endless process. My suggestion is to raise this issue with your server vendor's support, and point them to this response which identifies the two bugs in their software package that need fixing.
With kind regards, Jan [1] https://gerrit.vesnicky.cesnet.cz/r/571 -- Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
