GNOME Bugzilla – Bug 221088
Want the ability to connect to multiple exchange accounts
Last modified: 2013-07-23 14:32:27 UTC
Any way to request the ability to have 2 exchange servers setup?
This is already planned for 1.2. The only reason it's not allowed in 1.0 is that we have no way to declare which account is the "default" for things like Summary, Pilot syncing, etc.
*** http://bugzilla.ximian.com/show_bug.cgi?id=23804 has been marked as a duplicate of this bug. ***
I agree this would make things easier, but Outlook 2000 doesn't allow configuration of more than 1 Exchange Server email account (surprise!).
Christine, Right... Outlook doesn't support this feature and so it would be an addition that only we have. (Although through Outlook Web Access it's fairly easy to access more than one account just by logging out, it isn't quite the same thing. Outlook also doesn't (IIRC) support using IMAP or POP AND Exchange at the same time. This comes up as a feature request from customers though.
Outlook XP lets you configure as many accounts as you want, of any type. Outlook 2000 lets you add other users' mailboxes to the folder tree if you have permission to view them.
This is not currently possible because you can't make soup use one username/password for some requests and a different username/ password for other requests. (Or rather, you can't control which one it will end up using for any given request.)
The soup problems are fixed now. All that needs to be done is to remove the restriction in exchange-config-listener.c, and then fix any parts of the code that implicitly assume there is only a single account. (eg, the migration code.)
Reassiging these to the maintainer 'surfy'.
I am also one of the persons that would like to see this functionallity. Is there any work on this going on?
Is any work still being done on this? Multiple Exchange server is one thing, but also the ability to add more than one account to view (on the same server), would be awesome. In Outlook you can add additional mail accounts to view, if you have permission for you. In Entourage they're called "delegates" but it works the same way. For Outlook Web Access, you don't need to log out and back in, you just need to specify the path. eg: - Log into your OWA. - Now you can view your inbox. - Without logging out, modify the URL to "https://[servername]/exchange/[username]" and if your logged in account has access, boom, you're in. Seems to me everything on the Exchange side should be fairly easy. Rock on folks, you do good work!
just requesting some update on this. Judging by Dan's post (4 years ago) this seems fairly straightforward. This is essential for anyone trying to migrate his company's workstations to open source since, at the moment, this is the only real obstacle for people with more than one Exchange account to adopt this solution and there are no alternatives. If this turns out to be too complicated, I'd suggest enabling multiple separate configuration files depending on multiple profiles (again, like Outlook does), then we could work around the problem and make it tolerable in the workplace with just a few extra steps from the user.
I too would really appreciate an update (and a solution!) - I only recently tried using Evolution for OWA and was bowled over by how well it worked. Well done, guys! So far, being unable to connect to both my Exchange accounts at the two companies I work for is the only flaw I've found.
Is there anyone working on a solution for this right now?
*** Bug 409688 has been marked as a duplicate of this bug. ***
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported. Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.