Send mail impossible with "Use secure connection" checked

same problem. on ubuntu 11.10

When i would like send email, i have this error in the console :

libexchangemapi-CRITICAL **: exchange_mapi_connection_find: assertion `profile != NULL' failed

Thank
Sylvain

Status changed to 'Confirmed' because the bug affects multiple users.

Same error as LUI:

(evolution:1565): libexchangemapi-CRITICAL **: exchange_mapi_connection_find: assertion `profile != NULL' failed

max

Same problem.
Ubuntu 11.10
evolution 3.2.2-0ubuntu0.1
evolution-mapi 3.2.0-0ubuntu1

Thanks,
bayerb

Same problem, same configuration and software versions.

Thanks,
Steve

Same problem, and I'm running with the same versions as bayerb.

Regards,
Sam.

Same problem. I use the 64-bit version of Ubuntu if that is relevant, otherwise I have the samve versions as bayerb.

Regards
Jonas

I have ubuntu 12.04, and if i create new account i have similar problems, but if i create account in 11.10 and then upgrade to 12.04 then it working (send and recieve email via evolution-mapi plugin, even supported html format to send a email (previously it doesn't)) (i'm talking about same exchange account)
ubuntu 12.04 amd64

Strangely the problem disappeared for me. The only thing that I changed, that I can think of, was that I added another mail account connected with IMAP to my google account. After doing that also the MAPI account seems to work as expected.

Cheers
Jonas

After migrate from one exchange server to another (mail1.domain.local to mail-server.domain.local),
i have change server address in my account settings, but i get same error again ("An error occurred while sending. How do you want to proceed? The reported error was "Could not send message.")

There was not any errors in console, even with MAPI_DEBUG=1, when i send email, only evolution error message box.

To resolve that, i change record in gconf-editor path /apps/evolution/mail/accounts/accounts
I found my account xml record , and replace all old links to new one (replace mail1.domain.local with mail-server.domain.local)
After that i can send email messages again!

Removing my kerberos keys (/etc/krb5.keytab file) allowed me to send email under Ubuntu 12.04 LTS.

At my office MS and Linux are on two separate networks but it seems that evolution somehow tries to authenticate using kerberos for sending email if kerberos is setup on the system. What's wierd is that kerberos authentification is not checked in my MAPI configuration so it should not even try that?

So, for now, at every login I must move my krb5.keytab file ;)

For our server, I got it working only after I unchecked 'Use secure connection' in the MAPI settings.

I see the below in the console as well:

libexchangemapi-CRITICAL **: exchange_mapi_connection_find: assertion `profile != NULL'

Exchange 2010, Ubuntu 12.04

thnx for the info Martijn, removing 'Use secure connection' solved it for me too.

Probably it was removing of 'Use secure connection' that did the trick for me too.

Unchecking "Use secure connection" and restarting Evolution solved the problem on me.

Why do you expire the bug without any comment? Do you have a solution?

also be sure that you have exactly same time as on domain controller.
for example:
sudo /etc/init.d/ntp stop
sudo ntpdate <domain controller ip>
then restart evolution
i have difference in 7 seconds and evolution didn't work

I had the same issue until I disabled "USe secure connection".
Ubuntu 12.04
Evolution 3.2.3-0ubuntu6
Evolution-mapi 3.2.2-1

Same issue, same solution. Restart is important!

Ubuntu 12.04
Evolution 3.2.3-0ubuntu6
Evolution-mapi 3.2.2-1

This bug appears to have duplicates (988396 and 1003274). The work around for this problem solves the issue of the other two bugs.

Using gconf-editor, one can go to: /apps/evolution/mail/accounts
and from there copy the contents of the "account" key. Create a key called "transport" if it's not present, and paste the contents of the "account" key into it.

Doing this allows the "Use secure connection" option to function correctly.

Further investigatin (and experience) reveals my previous post (#21) does not permanently resolve the problems in the above mentioned bugs.