After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 687179 - MAPI_E_CALL_FAILED (0x80004005) When sending mails longer than a few lines
MAPI_E_CALL_FAILED (0x80004005) When sending mails longer than a few lines
Status: RESOLVED DUPLICATE of bug 682449
Product: evolution-mapi
Classification: Applications
Component: Mail
3.6.x
Other Linux
: Normal major
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2012-10-30 09:37 UTC by Arpad Bakay
Modified: 2012-10-30 13:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Loglines generated while sending a shorter email (success) and a longer one (fail), created with MAPI_DEBUG=10 (12.47 KB, text/x-log)
2012-10-30 09:37 UTC, Arpad Bakay 		Details

Description Arpad Bakay 2012-10-30 09:37:37 UTC 
Created attachment 227619 [details]
Loglines generated while sending a shorter email (success) and a longer one (fail), created with MAPI_DEBUG=10 

I have upgraded to Ubuntu 12.10, which comes with an evolution 3.6

Since the upgrade, I discovered that I can only send mails with a few lines only, all mails longer than  that (e.g. the ones with attachments) result in an error: 

WriteStream: MAPI_E_CALL_FAILED (0x80004005) 

If I cut the mail back to a few lines, the mail will send correctly.

Since then I have built the current stable Evo (3.6.1 with 3.6.0 MAPI), but the problem persists.  

I attached the MAPI_DEBUG=10 log, which demonstrates a short mail, and a long one. Unfortunately no clear sign of the error, but I am ready to do further tests upon your request. 

It appears that other people also face this bug after an upgrade:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1053510
Comment 1 Milan Crha 2012-10-30 13:12:30 UTC 
Thanks for a bug report. This had been filled already, thus I'm marking this as a duplicate of it. Note the change to fix this comes to OpenChange.

*** This bug has been marked as a duplicate of bug 682449 ***