Description of problem: After updating to 7.1.8-1 I can't move messages to zarafa imap folders, this errors apear in the gateway log Tue Mar 4 11:07:44 2014: [ 8027] Unable to parse sub multipart 1 of mail body Tue Mar 4 11:07:44 2014: [ 8027] Unable to parse mail body Tue Mar 4 11:09:23 2014: [ 8027] Unable to parse sub multipart 1 of mail body Tue Mar 4 11:09:23 2014: [ 8027] Unable to parse mail body Version-Release number of selected component (if applicable): 7.1.8-1 How reproducible: Move a multipart email to zarafas imap folders using thunderbird Actual results: The email is not moved Expected results: The email is moved Additional info:
Juan, thank you for your report. Fortunately this issue is known already and also fixed by the re-release of 7.1.8 by upstream. This updated package is at the moment only available via the testing repository.
zarafa-7.1.8-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/FEDORA-2014-2959/zarafa-7.1.8-3.fc20
zarafa-7.1.8-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/FEDORA-2014-2904/zarafa-7.1.8-3.fc19
zarafa-7.1.8-3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0633/zarafa-7.1.8-3.el6
zarafa-7.1.8-3.el5, php53-mapi-7.1.8-3.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0635/zarafa-7.1.8-3.el5,php53-mapi-7.1.8-3.el5
zarafa-7.1.8-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-7.1.8-3.el5, php53-mapi-7.1.8-3.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-7.1.8-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-7.1.8-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.