Re: [Evolution] long outstanding evolution bug 339028 - any updates?

[Eugene Kanter <eugene bct bz>]

12.07.2011, 14:02, "Adam Tauno Williams" <awilliam whitemice org>:
> On Tue, 2011-07-12 at 13:31 -0500, Eugene Kanter wrote:
>
> >  https://bugzilla.gnome.org/show_bug.cgi?id=339028 filed 2006-04-19
> >  13:49:28 UTC and last updated 2011-07-11 08:39:22 UTC, status NEW.
> >  Reproducible in every version including the latest one.
> >  Is there any valid reason for keeping this bug in the code for over 5
> >  years?
> >  As recently as about 3 months ago on this thread
> >  http://mail.gnome.org/archives/evolution-list/2011-March/msg00127.html
> >  the error came up again but bug was not mentioned.
> >  Thunderbird doesn't report any damaged messages in the same IMAP
> >  mailbox. It reads all emails with no problems.
>
> This is what I call a "crap shoot".

open source list does not mean dirty language.

> I've seen TB choke on messages on numerous occasions.  I haven't had
> Evolution, in my every-day usage with two busy IMAP accounts, have an
> issue displaying any message.  Same is true of Horde [which is probably
> the most reliable IMAP client on the planet].  But I've no doubt
> messages exist that will make either of them weep.

I've been using Evolution exclusively since the very first release and have more then ten active IMAP 
accounts in my preferences box.
This error occurrence is very rare but I've seen it more then several times.
Every time I must use other client to locate a suspicious message and remove it in order to continue using 
Evolution. 

> Is this an Exchange only issue?  It sort of seems like a server-side
> problem; such a message shouldn't be allowed to exist.  It would seem
> like a message without a date/from/to would have gotten kicked to the
> curb by the MTA [not that clients shouldn't deal with stupidity
> gracefully - I just think such an occurance is extremely rare].

This has nothing to do with Exchange. I've seen it happen on both imap.gmail.com and imap.yandex.ru servers.

My point is that brain dead decision to abandon mail box processing upon encountering a minor message 
formatting error is not acceptable.
The primary function of any mail client is to display all messages the best way possible and don't lock user 
out of mail box if corrupted message is encountered.

Eugene.