crash when trying to create first exchange MAPI account

[matt_hargett]

Binary package hint: evolution

-on a fresh kubuntu/evolution install, start evolution, click Forward
-enter email address (e.g. <email address hidden>), click Forward
-select Exchange MAPI for server type, enter known good (from outlook) exchange server, then enter known good domain name, click Auth

result:
crash. console output:
matt@hargett-755:~$ evolution
** (evolution:7234): DEBUG: Loading Exchange MAPI Plugin

** (evolution:7234): DEBUG: MAPI listener is constructed with 0 listed MAPI accounts
RSS Plugin enabled (evolution 2.26, evolution-rss 0.1.2)
Create profile with matt.hargett cf-cal bcs-mail04.internal.cacheflow.com
libexchangemapi-Message: exchange-mapi-connection.c:2874: exchange_mapi_create_profile: lock(connect_lock)
Unknown parameter encountered: "max log size"
Ignoring unknown parameter "max log size"
Unknown parameter encountered: "syslog"
Ignoring unknown parameter "syslog"
Unknown parameter encountered: "passdb backend"
Ignoring unknown parameter "passdb backend"
Unknown parameter encountered: "unix password sync"
Ignoring unknown parameter "unix password sync"
Unknown parameter encountered: "passwd program"
Ignoring unknown parameter "passwd program"
Unknown parameter encountered: "pam password change"
Ignoring unknown parameter "pam password change"
Unknown parameter encountered: "map to guest"
Ignoring unknown parameter "map to guest"
Unknown parameter encountered: "usershare allow guests"
Ignoring unknown parameter "usershare allow guests"
Unknown parameter encountered: "guest ok"
Ignoring unknown parameter "guest ok"
Unknown parameter encountered: "guest ok"
Ignoring unknown parameter "guest ok"
Logging into the server... succeeded
libexchangemapi-Message: exchange-mapi-connection.c:146: exchange_mapi_connection_close: lock(connect_lock)
Segmentation fault

various log files as suggested by the Debugging Evolution wiki page are attached.

[Sebastien Bacher (seb128)]

thank you for your bug report, no ubuntu bug triager has access to an exchange server though so you should better open the bug directly to the software writters on bugzilla.gnome.org