GNOME Bugzilla – Bug 751511
evolution can not send mail after being open a couple of minutes
Last modified: 2015-09-03 06:29:27 UTC
I can only send emails for the first couple of minutes after opening evolution. Thereafter the following error occurs: The reported error was "Could not send message: ResolveNames: MAPI error (0x61b48bd7) occurred". or The reported error was "Could not send message: ResolveNames: MAPI error (0xcae16a08) occurred". The work around is to close evolution and restart it. There is no problem with receiving emails. --------------------------------------------------- fro more details see launchpad: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1318971 Yura.
I looked more into this problem and here are some extra info, evolution is sending emails until these messages in the syslog: Jun 25 11:19:00 yku-sp3 org.gnome.evolution.dataserver.AddressBook6[2069]: (evolution-addressbook-factory:21194): libedata-book-CRITICAL **: book_backend_get_contact_list_uids_sync: assertion 'class->get_contact_list_sync != NULL' failed Jun 25 11:19:00 yku-sp3 org.gnome.evolution.dataserver.AddressBook6[2069]: message repeated 2 times: [ (evolution-addressbook-factory:21194): libedata-book-CRITICAL **: book_backend_get_contact_list_uids_sync: assertion 'class->get_contact_list_sync != NULL' failed] Jun 25 11:19:24 yku-sp3 org.freedesktop.Notifications[2069]: ** (notify-osd:21669): WARNING **: stack_close_notification_handler(): notification id == 0, likely wrong after this point I cannot send emails...
BTW, the above errors/warnings happens after I checked for new emails (via Send/Receive button) and then select any new/unread email in evolution. Maybe it is interesting to know that if I (or evolution) did not check for new emails, I can select new/unread emails and no error/warning message.
I think there is related bug for this one in fedora 18, but this release is EOL and they closed it... https://bugzilla.redhat.com/show_bug.cgi?id=903166
OK, here is my solution to this problem. I updated to evolution 3.16.0 from ppa:fta/gnome3 and it is working right now. and even more, with this version I have server push notification so it is much better user experiance! BTW I see the same errors/warnings in the system log, but I can send emails... Jun 25 16:54:12 yku-sp3 kernel: [25635.895571] mce: [Hardware Error]: Machine check events logged Jun 25 16:54:09 yku-sp3 org.gnome.evolution.dataserver.AddressBook9[2069]: message repeated 17 times: [ (evolution-addressbook-factory-subprocess:17736): libedata-book-CRITICAL **: book_backend_get_contact_list_uids_sync: assertion 'class->get_contact_list_sync != NULL' failed] Jun 25 16:55:27 yku-sp3 org.freedesktop.Notifications[2069]: ** (notify-osd:21669): WARNING **: stack_close_notification_handler(): notification id == 0, likely wrong Jun 25 16:55:41 yku-sp3 org.gnome.evolution.dataserver.AddressBook9[2069]: (evolution-addressbook-factory-subprocess:17736): libebookbackend-WARNING **: Unable to update gal : 404 Not Found Jun 25 16:55:47 yku-sp3 org.gnome.evolution.dataserver.AddressBook9[2069]: message repeated 4 times: [ (evolution-addressbook-factory-subprocess:17736): libebookbackend-WARNING **: Unable to update gal : 404 Not Found] Jun 25 16:57:26 yku-sp3 org.freedesktop.Notifications[2069]: ** (notify-osd:21669): WARNING **: stack_close_notification_handler(): notification id == 0, likely wrong Jun 25 16:57:52 yku-sp3 org.gnome.evolution.dataserver.AddressBook9[2069]: (evolution-addressbook-factory-subprocess:17736): libebookbackend-WARNING **: Unable to update gal : 404 Not Found
Thanks for a bug report. I guess the update to 3.16.x took in also newer OpenChange and eventually Samba, on which evolution-mapi depends. I do not know what server version you connect to, but if I can suggest then since Exchange 2007 an evolution-ews can be used to connect there. It's lighter for dependencies and in certain cases even quicker than evolution-mapi. With Exchange 2013 servers the MAPI protocol is disabled by default and only EWS protocol is available. As you made this running, I think I can either close this or convert it into a bug report about the critical warnings from the book_backend_get_contact_list_uids_sync().
I'm closing this in favor of 3.16, and eventually upcoming 3.18.0.