Evolution can't handle a mail message it receives, fails to retrieve further mail. (no output stream?)

[Tim Blokdijk]

Binary package hint: evolution

Evolution 2.28.1-0ubuntu2
Ubuntu 9.10

I have a e-mail message on my mailserver that when retrieved makes evolution spit out a localized but very unclear error.
The error massage is attached to this bug, English translation would be something like:

Error during message retrieval.
No output stream

Anyway, Evolution fails to retrieve the e-mail and any other e-mail on this account. (it's a pop3 account) Another imap account keeps functioning.
Moving this specific e-mail to trash (on the server via webmail) works as a workaround, Evolution can retrieve other mail for the account. Moving the mail back from trash to the inbox again makes Evolution error out.

Starting Evolution from the command line won't generate errors that are clearly linked to the failed retrieval of this e-mail.
I removed Evolution via Synaptic (keeping configuration) and reinstalled, problem remains the same.

What can I do to help triage this bug? Is there a detailed error log for Evolution? There is a basic error log available mentioning the errors but it has no further details.

[Pedro Villavicencio (pedro)]

Yes, could you run evolution as: CAMEL_DEBUG=all evolution >& evo.log and attach that resulting log file to the report? Thanks in advance.

[Tim Blokdijk (tim-blokdijk)]

Alright, I have a more detailed log. Only problem now is that some parts of the log contain more personal information. Maybe I can do a clean evolution setup. Or clean out some details in the log.

[Tim Blokdijk (tim-blokdijk)]

Ok, I decided to clean up the log, replaced e-mail addresses, names and a mail folder name with the string '[*removed from log by bug submitter*]'.

The string "Geen uitvoerstroom" is mentioned once in the log at line 1697 as:
CamelException.set(0x9576524, 201, 'Geen uitvoerstroom')

What I did to generate this log:
ran "CAMEL_DEBUG=all evolution >& evo.log" in a terminal.
Evolution starts and retrieves the e-mail message.
Evolution fails and shows a exclamation mark in the status bar.
I close evolution and it closes cleanly.
E-mail message remains on the server. (and any other mail for that account)
Edited the log found in ~/evo.log to remove some details. The e-mail account that retrieves the e-mail message is not edited out (it's <email address hidden>).

The logfile contains the e-mail message it fails to retrieve, so maybe it's a (spam) filter or parsing problem?

I have four e-mail accounts configured two of those are active <email address hidden> (pop3) and a gmail account (imap). The other two are disabled via the preference menu within evolution. The disabled accounts are for a local network imap server.
I believe that I upgraded Ubuntu from 8.04 through to 9.10 but it could have been from 7.10, anyway one of the upgrades updated the evolution database to sqlite. I don't know if that's relevant but it can't hurt to mention it.

[Tim Blokdijk (tim-blokdijk)]

I have been reading the evolution-data-server-2.28.1 source code. (although I'm not a C programmer)
In the evolution-data-server-2.28.1/camel/providers/imap/camel-imap-command.c file I can find the string "No output stream" in connection with a CAMEL_EXCEPTION_STORE_INVALID. Something wrong with storing the mail.. that would make some sense. But I can't find a similar exception in the code for pop3. Which is strange as the e-mail account involved is using the pop3 protocol not imap.

[Tim Blokdijk (tim-blokdijk)]

Well, I gave it a try but I lack the knowledge to triage this further. Anybody here that can help out?

[Pedro Villavicencio (pedro)]

This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at https://wiki.ubuntu.com/Bugs/Upstream/GNOME . Thanks in advance!

[Tim Blokdijk (tim-blokdijk)]

Alright, I added a bug upstream. See https://bugzilla.gnome.org/show_bug.cgi?id=603917
I used the "Also affects project" function to link this bug to the upstream bug.

[Jörg Frings-Fürst (jff-de)]

bug from 2009. Version not more supported.
change status to invalid.