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 720339 - Can't use IMAP with a MS Exchange 2010 Server: Error fetching folders: list: expecting '(' or NEWLINE
Can't use IMAP with a MS Exchange 2010 Server: Error fetching folders: list: ...
Status: RESOLVED DUPLICATE of bug 722275
Product: evolution
Classification: Applications
Component: general
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-12-12 17:31 UTC by Bernhard
Modified: 2014-02-11 14:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bernhard 2013-12-12 17:31:51 UTC
Since I upgraded to 3.10, I get the following error trying to setup a new IMAP account:
Error fetching folders: list: expecting '(' or NEWLINE
Comment 1 Bernhard 2013-12-23 11:26:01 UTC
This is the first attempt of me filing a bug report. Maybe I should be a little more specific.

evolution version: 3.10.3
distribution: arch linux

problem description:
When switching to arch, i also switched from an older version of evolution (possibly still 2.x) to 3.10. My problem is to connect to a MS Exchange 2010 e-Mail Server via imap: I cannot set-up my account, since there is apparently something wrong with (the parsing of) the folder list:
"Error fetching folders: list: expecting '(' or NEWLINE"
This is a problem specific to newer versions of evolution; everything works well with thunderbird and older version of evolution.

If you need any more information, I am happy to provide it.
Comment 2 Milan Crha 2014-02-11 14:15:07 UTC
Thanks for a bug report. Evolution-data-server 3.10.4 contains a fix from
bug #722275, which makes it work again. Please update to it once your distribution provides it for you. The 3.10.4 has been released only yesterday.

*** This bug has been marked as a duplicate of bug 722275 ***