evolution tries to send a mail but outbox is empty

[Kai Krakow]

Binary package hint: evolution

Evolution was closed during sending the outbox. Now it's stuck telling there is one message to send but the outbox is empty. I consider this a bug as opposed to #179288 because evolutions idea about the sending queue and the outbox seems to be inconsistent and it should automatically recover from such problems.

ProblemType: Bug
Architecture: i386
Date: Wed Jun 18 16:07:22 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evolution
Package: evolution 2.22.1.1-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
Uname: Linux 2.6.24-18-generic i686

[Pedro Villavicencio (pedro)]

Thanks for your report, can you reprduce this everytime? may you tell us a few steps in order to trigger the behavior? thanks.

[Kai Krakow (hurikhan77)]

I have some new information regarding this problem:

We tracked it down to a big mail sitting in the outbox of the local folder structure. The user expected to find the mail in the outbox of the exchange folder storage. So after deleting this mail it worked.

But the bug isn't resolved because trying to delete this mail locked evolution. Evolution seemed to be busy trying to send this big email (several megabyte) and the exchange server policy probably refused to accept such a big mail. Instead of informing the user about the error reason, the send/receive dialog just sits there doing what looks like nothing. I had to try several times until some point evolution even refused to start.

Trying from the command line, evolution just displayed some empty lines (no error messages) and returned to the command line. Trying to logoff made the whole session stop responding (logoff button was clickable but didn't respond, gnome desktop bars didn't respond to other clicks either). So I ctrl+alt+backspace'd the x-session and did a relogin. Evolution still did not start. I had to run "evolution --force-shutdown". Now evolution started again but the "offending" mail was still there. The difference this time was I could successfully delete the mail.

I suppose the problem is somewhere located in the exchange connector not recovering from errors properly.

[Sebastien Bacher (seb128)]

could be an issue in the exchange code indeed, do you still have a buggy case or a way to trigger the issue to get extra informations if required?

[Pedro Villavicencio (pedro)]

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.