Bug 1048644 - "Error fetching folders: list: expecting '(' or NEWLINE": IMAP LIST results > 16kb
Summary: "Error fetching folders: list: expecting '(' or NEWLINE": IMAP LIST results >...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-06 02:02 UTC by Axel Thimm
Modified: 2014-01-15 16:12 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-15 16:12:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 722275 0 None None None Never

Description Axel Thimm 2014-01-06 02:02:01 UTC
Description of problem:
After upgrading from F19 to F20 evolution fails to connect to an account with many mailboxes. The error is

Error fetching folders: list: expecting '(' or NEWLINE

Version-Release number of selected component (if applicable):
evolution-3.10.3-1.fc20.x86_64

How reproducible:
Always on a many mailbox account

Steps to Reproduce:
1.Start evolution - Account in question is show w/o any folders
2.Go to subscription menu - the above error occurs
3.

Actual results:
The account is shown w/o folders and mailboxes. Upon trying top list them in the subscription menu the mentioned error is displayed

Expected results:
Normal list behaviour of folders and mailboxes in them

Additional info:
The same imap server/account setup worked for all previous Fedora releases, e.g. evolution up to version evolution-3.8.5-2.fc19. It still works for manual entry of IMAP commands as well as other clients like mutt.

I turned off SSL and debugged the TCP stream. evolution sends the following commands:

R00854 LOGIN XXXXX XXXXX
R00855 NAMESPACE
R00856 ENABLE CONDSTORE QRESYNC
R00857 LIST "" "*" RETURN (SUBSCRIBED)

The last command's result is broken into several TCP/IP packages, evolution breaks the stream after receiving the first one and errors out on parsing the last unfinished line. The other mail clients or manual IMAP commands aggregate the results and wait for the IMAP end sequence of the LIST command.

This is a regression wrt 3.8.x as this worked nicely up to the upgrade to F20/evolution 3.10.x.

Tagged as high severity as anyone with a larger number of mailboxes in his account will not be able to use evolution.

Comment 1 John Horne 2014-01-11 22:08:45 UTC
I too am now seeing this problem, having just updated my work PC to Fedora 20. The PC runs 'dovecot' for IMAP services. I used F17 previously, and that worked fine (using Dovecot/IMAP/Evolution).

However, whilst the error does occur if I use the 'Folder->Subscriptions' command, I can see my mailboxes and the subfolders and the messages in them. The error message does popup every so often (at the top of the message list pane), but I am unsure when exactly it occurs. If I click 'Refresh' on a folder, the message doesn't appear; if I click 'Send/Receive' for my mail, the message doesn't appear. Sorry to muddy the waters a bit!

I am using (if it helps): dovecot-2.2.9-1.fc20.x86_64

Comment 2 John Horne 2014-01-11 22:25:18 UTC
A little more info...

In my case I have configured Evolution to check for IMAP mail every 5 minutes. I get the above error message appearing when that 5 minute check occurs. The message appears, and then I see at the bottom of the Evolution window the message "Checking for new mail at 'Work'" (Work being the mailbox on my work PC).

Comment 3 John Horne 2014-01-13 14:14:27 UTC
This is actually a show-stopper for me now. I am at work and cannot see any mail at all  (just the 'Work' folder, but no messages) - obviously not good at all!

If I cannot find a workaround very soon, then I may well have to see about downgrading to F19 or use another mail client.

Comment 4 Milan Crha 2014-01-15 16:12:52 UTC
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions. This way the upstream IMAP developer will notice the issue more easily.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=722275


Note You need to log in before you can comment on or make changes to this bug.