GNOME Bugzilla – Bug 677845
Silently fails to send message
Last modified: 2012-06-12 20:45:51 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=830320 Evolution silently fails to send email through an Exchange server. By all appearances it sends, but no recipient receives an email. Version-Release number of selected component (if applicable): $ rpm -qa | grep evolution evolution-exchange-3.4.1-1.fc17.x86_64 evolution-data-server-3.4.2-1.fc17.x86_64 evolution-NetworkManager-3.4.2-1.fc17.x86_64 evolution-3.4.2-1.fc17.x86_64 MS Exchange 2003 How reproducible: 100%, sadly. Steps to Reproduce: 1. Configure Evolution to an Exchange 2003 server 2. Compose email 3. Click send Actual results: Email appears sent successfully (email composition window closes, mail appears in Sent Items folder). If Evolution is started thusly: $ E2K_DEBUG=5 evolution The following messages appear when the email is sent: (evolution:26229): camel-exchange-provider-CRITICAL **: camel_exchange_utils_send_message: assertion `ed != NULL' failed (evolution:26229): camel-WARNING **: CamelExchangeTransport::send_to_sync() reported failure without setting its GError Expected results: The email actually gets sent. Additional info: Given the silent nature of the failure, I recommend it get considered for higher severity. Took me a week before I discovered that *none* of the emails that I sent actually were delivered. Receiving emails works fine. Confirmed there is no problem sending email from this account using a real Outlook client. No problems with this with the version of Evolution that came with F14. Another instance seen here: http://forums.fedoraforum.org/showthread.php?t=280362
Confirming, I can reproduce this too.
Created attachment 216119 [details] [review] eex patch for evolution-exchange; Silly issue, there was missing set exchange settings in the transport store, which made the comparison on the ExchangeData fail, thus those runtime warnings. I also made it claim error when this runtime error is printed on console, together with a change when only one exchange account is configured then that one is picked as a fallback (with emitted runtime warning as well).
Created commit 6977d42 in eex master (3.5.3+) Created commit 3ad3617 in eex gnome-3-4 (3.4.3+)