Mon, 06 Apr 2026 06:58:52 +0000 https://bugs.horde.org/ticket/14771 Possibly malformed e-mail not handled properly The attached message stops cannot be read through the webmail interface and stops ActiveSync from synchronizing the folder it is in. After removing it from the folder, all is well again. Mon, 22 Jan 2018 11:36:34 +0000 https://bugs.horde.org/ticket/14771#t92674 Logfile excerpt while attempting to sync message Mon, 22 Jan 2018 11:37:39 +0000 https://bugs.horde.org/ticket/14771#t92675 In case relevant, IMAP server is Dovecot-2.3. Mon, 22 Jan 2018 11:39:35 +0000 https://bugs.horde.org/ticket/14771#t92676 I notice that a small percentage of messages that previously (less than a month ago) could be read just fine, now no longer do and lead to the dreaded communication failure with the server. Tue, 23 Jan 2018 13:14:59 +0000 https://bugs.horde.org/ticket/14771#t92705 FWIW, the messages can be opened and read through MozillaThunderbird just fine. Curiously enough, Horde only has problems in messages from one mailinglist. Thu, 25 Jan 2018 19:43:15 +0000 https://bugs.horde.org/ticket/14771#t92710 debug_raw log when trying to open message (fails) Fri, 26 Jan 2018 11:25:08 +0000 https://bugs.horde.org/ticket/14771#t92711 And problem found. Dovecot 2.3+ has changed something: * IMAP: When BINARY FETCH finds a broken mails, send [PARSE] error instead of [UNKNOWNCTE] And lo-and-behold, if I apply the attached patch, all seems to be well again. I doubt this is the correct way to deal with the above change however, as this will bluntly treat a PARSE error as UNKNOWNCTE and I really suck at PHP programming. You have been warned... Fri, 26 Jan 2018 16:10:33 +0000 https://bugs.horde.org/ticket/14771#t92712 Patch was missing. Fri, 26 Jan 2018 16:11:11 +0000 https://bugs.horde.org/ticket/14771#t92713 The fatal error, which is what is causing the broken sync, is caused by the error fixed here: https://github.com/horde/Imap_Client/commit/4666bf5d32372955a32f9efcc6c083812fb202d3 I've added some code that will treat the PARSE error the same as a CTE error with respect to a binary fetch in that it will try it again without the binary extension before failing. Sun, 11 Feb 2018 02:17:57 +0000 https://bugs.horde.org/ticket/14771#t92735