the message uses an encoding consistent with the declared MIME type; I
cannot blame the originator for using a non-utf8 encoding, since it is
correctly tagged so. The problem is that Evolution ignores the encoding
on inbound messages *but* fails to nuke any invalid utf-8 sequences.
(in that respect, #505249 share a lot of things)
Originally tagged as a security issue, since remotely-controlled SEGV
are not something to ignore in my opinion (although indeed, the
workaround suggested by Y.A. Perez does work, the wording of the
question is quite different from "should I attempt to display again the
message that caused me to crash?", which could lead to another round of
hair cutting (best avoided)). Won't discuss further the severity
downgrade, but one might wonder about the sorry state of Evolution, even
though it's supposed to be the default GNOME mail/calendar&kitchen sink
app...
-- Cyrille
