This guy from bugzilla solved the issue for Fedora users here is his respond about the bug:
Milan Crha [evolution-mapi developer] 2011-11-24 13:21:39 UTC
Nice. I couldn't reproduce it the first time I created the account, the message
was sent, but when I closed evolution and run it again, and did almost the same
steps (instead of replying I created a new message), then the message sending
failed. Looking into GConf key /apps/evolution/mail/accounts the corresponding
one for the MAPI account has its <url /> for <source /> with a 'profile'
parameter, but the <transport><url /></transport> is without that 'profile'
parameter, which makes it fail. A workaround is to add the parameter into the
XML blob into the GConf key (it can be tricky).
I'll try to workaround this in evo-mapi sources. I'm confirming the bug.
This guy from bugzilla solved the issue for Fedora users here is his respond about the bug:
Milan Crha [evolution-mapi developer] 2011-11-24 13:21:39 UTC
Nice. I couldn't reproduce it the first time I created the account, the message /mail/accounts the corresponding
was sent, but when I closed evolution and run it again, and did almost the same
steps (instead of replying I created a new message), then the message sending
failed. Looking into GConf key /apps/evolution
one for the MAPI account has its <url /> for <source /> with a 'profile'
parameter, but the <transport><url /></transport> is without that 'profile'
parameter, which makes it fail. A workaround is to add the parameter into the
XML blob into the GConf key (it can be tricky).
I'll try to workaround this in evo-mapi sources. I'm confirming the bug.
Could anyone patch it please?