can't configure new exchange account

Bug #20227 reported by Joe Barnett
24
Affects Status Importance Assigned to Milestone
evolution-exchange (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs

Bug Description

the "configuration" field only contains the user name, so I can't specify the
proper server/domain/etc.

Revision history for this message
timo (timo-carl) wrote :

Same here (current breezy), whereas ximian-connector-setup tool works properly.
But a connection being setup with that tool is not accessible in evolution.

Revision history for this message
Joe Barnett (thejoe) wrote :

still seeing this on 2.4.0

Revision history for this message
Joe Barnett (thejoe) wrote :

--from ubuntu-devel-list:

I was just able to set one up yesterday. If you run the
ximian-connector-setup-2.4 and setup the server properties then all you
need to enter in the config box in Evolution itself is your username.
That worked fine for me yesterday.

--
Daniel

-----------------------------

hmm.... didn't entirely work for me:

when I first set it up, it kept saying I had the wrong password, even though I
was providing the correct one. I went in and edited gconf keys to add
";owa_url=https://server/exchange" to the transport url and the source url, and
was able to connect.

will add this information to the bugzilla report.
-Joe

Revision history for this message
Matt Zimmerman (mdz) wrote :

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

Revision history for this message
senectus (senectus) wrote :

The "ximian-connector-setup-2.4" setup method worked for me.
Using Breezy as of the 12th of Sept.

Revision history for this message
timo (timo-carl) wrote :

Configuration is still not possible in Evolution itself; workaround with
ximian-connectorp-setup and/or gconf required.
Please change the target to breezy in order to get more attention on this one.

Thanks!

Revision history for this message
joerg.battermann (jb-justbe) wrote :

unfortunately, since the ximian-conncetor-xyz-way asks for a global catalog server (which is a
must here), and which I don't have, I cannot setup evolution using the workaround either :|

I'd really like to have this fixed for breezy because not being able to specify an exchange
server renders the evolution-exchange package useless for the enduser :\

Revision history for this message
Joe Barnett (thejoe) wrote :

still seeing this even with evolution-plugins installed (thought that might have
fixed it, but no such luck).

Revision history for this message
James D (freelsjd-comcast) wrote :

confirmation of bug here. Also files similar bug report on evolution-exchange. Please correct evolution-exchange in Breezy. If not, I will have to resort
to Debian/Sarge (reading e-mail here is a MUST).

Revision history for this message
Drew Wilkinson (dwilkinson) wrote :

I worked around the same problem as in comment #7 by ssh -L
3268:DOMAINCONTROLLER:3268 linuxserver.mynetwork.com so that I could
authenticate to my global contact server. The GC server is my domain controller,
I've just not got access to it remotely. So I just put localhost for my GC
server, and use ssh to bounce through a linux server that can talk to the domain
controller. That worked fine and tcpdump shows that the connector setup
application works and hits both servers. Evolution doesn't even try to hit
either the domain server, or the OWA server. I managed to get the gconf hack to
work. The order of the arguments seems important, I put the owa_url argument
after the auth= argument in both transport and source. This is a very difficult
setup, but it's clearly possible to do.

Revision history for this message
Penzo (peep) wrote :

i managed fix my problem with evolution-exchange by just editing
apps/evolution/mail/accounts gconf key and adding exchange server name to end of
my account name in <transport url> and <source url>.
"exchange://'account name'@'server name'/"
and after that everything worked;)

Revision history for this message
John Leach (johnleach) wrote :

Still experiencing this bug on latest Breezy updates

ii evolution 2.4.0-0ubuntu3
ii evolution-data-server 1.4.0-0ubuntu2
ii evolution-exchange 2.4.0-0ubuntu1
ii evolution-plugins 2.4.0-0ubuntu3

I first experienced this problem when moving to 2.4

Revision history for this message
Jeff Bailey (jbailey) wrote :

Fixed in 2.4.1-0ubuntu2

Revision history for this message
Erik (echakr) wrote :

It's back?!

evolution 2.11.6.1

Ubuntu 7.10 PPC

Revision history for this message
witt (ubuntu-bugs-tillwitt) wrote :

I can confirm this - it is back in 7.10 ubuntu. having the same problem which I did not have with feisty fawn.

Revision history for this message
Chaotarch (jens-chaos-co) wrote :

Also in 2.21.5 at Ubuntu 8.04 :(

To post a comment you must log in.
This report contains Public information  
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.