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 603917 - Evolution can't handle a mail message it receives, fails to retrieve further mail. (no output stream?)
Evolution can't handle a mail message it receives, fails to retrieve further ...
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-12-06 19:02 UTC by Tim Blokdijk
Modified: 2018-12-11 16:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Logfile generated with "CAMEL_DEBUG=all evolution >& evo.log" (61.79 KB, text/x-log)
2009-12-06 19:02 UTC, Tim Blokdijk 		Details

Description Tim Blokdijk 2009-12-06 19:02:07 UTC 
Created attachment 149207 [details]
Logfile generated with "CAMEL_DEBUG=all evolution >& evo.log"

Hello people,

I have a e-mail message on my server that makes Evolution error out. I tried to triage the bug on launchpad, the Ubuntu bugtracker.

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/485979

Attached is a logfile, I replaced some specific things in the log with the string '[*removed from log by bug submitter*]'.
In the log the problem is mentioned at line 1697 as:
CamelException.set(0x9576524, 201, 'Geen uitvoerstroom')

I was asked to send the bug information upstream.
Comment 1 Akhil Laddha 2009-12-07 04:44:54 UTC 
should be a duplicate of bug 573240
Comment 2 Tim Blokdijk 2009-12-07 21:24:39 UTC 
I don't know, this (my) bug is reliably triggered by retrieving a specific e-mail from a server. Bug 573240 is sometimes triggered by deleting random e-mail.
Comment 3 Tim Blokdijk 2009-12-28 19:49:19 UTC 
Same person sends me a mail and again evolution can't handle it. So I guess evolution can't parse something.
Comment 4 Roland Lezuo 2010-07-29 11:35:13 UTC 
I've had an similar issue. I figured out a filter rule tried to move somthing to an IMAP account long gone. Removing that filter resolved the issue.

Failing filters shoudl definitely produce a better error message.
Comment 5 Tim Blokdijk 2010-07-29 20:24:36 UTC 
I had multiple IMAP accounts configured and filters that were moving mail. It's quite possible that a filter was moving mail to a non-existing IMAP account as I had removed an IMAP account around that time.

A failing filter (presuming this is indeed the problem) should also not break further e-mail retrieval.
Comment 6 Milan Crha 2018-12-11 16:18:21 UTC 
Thanks for a bug report. I'm closing this as obsolete, but feel free to reopen or comment in case you can reproduce with the current 3.30.x stable series. Having a test message would help, together with filter options, but I believe all the code changed made meanwhile make Evolution work better.