Exchange connector support broken

Bug #23151 reported by Shawn Carver on 2005-10-04
28
Affects Status Importance Assigned to Milestone
evolution-exchange (Ubuntu)
High
Ubuntu Desktop Bugs

Bug Description

OS Version: Ubuntu Breezy
Evolution version: 2.4.1-0ubuntu3
Evolution-exchange version: 2.4.0-0ubuntu1

After setting up a new Exchange account in Evolution, I am able to see my
Personal Folders tree, but if I try to click on any of my folders to browse my
message headers, I'm presented with an error similar to this one:

Error while Opening folder exchange://
<email address hidden>/;personal/Inbox.

No such folder.

Thank you.

I can't add much to the problem, except to say: Me too!

In other words, I just want to confirm that this problem is seen by multiple
people. I tried to recreate my exchange account, and had the same problem, with
the same versions of the software.

Jeff Bailey (jbailey) wrote :

Can you try the suggestion here and see if it works, please:

http://permalink.gmane.org/gmane.comp.gnome.ximian.connector/165

I will also try some experiments later.

Tks,
Jeff Bailey

Shawn Carver (scarver) wrote :

Well, the error description in the link you gave doesn't quite match the error
that I'm getting.

The user also mentions being able to "browse mail". I'm not sure whether that
means actually seeing the headers, or just the folders.

In my case, I can see my folders but I never get a chance to see any mail
headers because I get the error message as soon as I click on a folder.

However, I will try what is suggested, although it may take some time to get to
it due to the fact that it involves rebooting the Exchange server.

I'll try as soon as possible and report back with the results.

Thanks again.

Shawn

(In reply to comment #2)
> Can you try the suggestion here and see if it works, please:
>
> http://permalink.gmane.org/gmane.comp.gnome.ximian.connector/165
>
> I will also try some experiments later.
>
> Tks,
> Jeff Bailey

(In reply to comment #2)
> Can you try the suggestion here and see if it works, please:
>
> http://permalink.gmane.org/gmane.comp.gnome.ximian.connector/165
>
> I will also try some experiments later.
>
> Tks,
> Jeff Bailey

Rached Blili (bugzilla-dread) wrote :

I am seeing this too. Just to be more clear. It seems that there is an extra
semi-colon being inserted in the directory path somehow.

Rached Blili (bugzilla-dread) wrote :

This bug is a duplicate of bug 23192

Jeff Bailey (jbailey) wrote :

*** Bug 23192 has been marked as a duplicate of this bug. ***

Btw, it has been confirmed in the forums as being resolved if the version of
evolution-exchange package is updated to the 2.4.1 version. All versions of
evolution packages were updated from 2.4.0 versions to 2.4.1 the other day when
I filed 17008 filed as duplicate of this bug.

None of the usual gmane evolution exchange ML fixes seem to resolve this. It
seems to be centered around the addition of the extra semi-colon into the path
for the folders. Btw, this is does not seem to be configurable from the xml
files in the .evolution dir. I tried that and those ended up being installing
over-written on re-start of evolution.

This does not appear to be an upstream bug if the evolution-exchange package is
updated to the 2.4.1 version.

 http://www.ubuntuforums.org/showthread.php?t=65293&page=3 post #22 illustrates
the suggested fix for this bug.

Dennis Kaarsemaker (dennis) wrote :

*** Bug 23324 has been marked as a duplicate of this bug. ***

Joe Barnett (thejoe) wrote :

creating a 2.4.1 evolution-exchange package fixes this for me, but filters on my
exchange account's Inbox don't work. should I file a separate bug for that now,
or wait until an official 2.4.1 package exists?

Shawn Carver (scarver) wrote :

The new evolution-exchange 2.4.1-0ubuntu1 package came in, and now everything
appears to work correctly for me now.

Thank you!

Shawn

Robb Kidd (ubuntu-thekidds) wrote :

I can second that the extra semi-colon problem has been resolved with the
inclusion of evolution-exchange 2.4.1.

Jeff Bailey (jbailey) wrote :

Two people (including the submitter) have confirmed that this is fixed. Closing
this bug.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.