Bug 659868 – imapx: missing closing ')' on fetch response

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 659868 - imapx: missing closing ')' on fetch response


Summary:	imapx: missing closing ')' on fetch response


Status:	RESOLVED OBSOLETE

Product:	evolution-data-server
Classification:	Platform
Component:	Mailer
Version:	3.0.x (obsolete)
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:	evolution[imapx]

Depends on:
Blocks:

Reported:	2011-09-22 19:59 UTC by tobias.eberle
Modified:	2015-08-11 14:33 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
log file (491.59 KB, text/plain) 2011-09-22 20:48 UTC, tobias.eberle	Details

Description tobias.eberle 2011-09-22 19:59:33 UTC

Hello,

I have set up imapx with a Lotus Notes IMAP Server. For certain emails I get the following message when I try to download the body:

Unable to retrieve message
missing closing ')' on fetch response

I'm not sure but I think it only happens with emails with attachments (but only with some, not all). With the old imap handler the same email can be downloaded flawlessly.

I know this is not much information, but I don't know how to provide more. Please tell me.

Thank you.

Evolution 3.0.3 on Fedora 15.

Comment 1 tobias.eberle 2011-09-22 20:48:09 UTC

Created attachment 197291 [details]
log file

CAMEL_DEBUG=imapx, log while loading a message in question

Comment 2 Milan Crha 2015-08-11 14:33:06 UTC

Thanks for a bug report and log. I do not know how much relevant is still is, after almost 4 years, both the code of the IMAPx mail provider in the evolution changed significantly, and your server could change as well.

I assume this is obsolete, but feel free to reopen, if you can retest with a more recent versions, like 3.16.4/3.16.5, though the best would be to wait for 3.18.0, which will contain changes from bug #745545, which changed the IMAPx provider internals heavily.