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 201146 - Don't display message after crash
Don't display message after crash
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal enhancement
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2001-01-16 06:53 UTC by Ali Abdin
Modified: 2008-10-29 23:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ali Abdin 2001-01-16 06:53:43 UTC
I just encountered what seems to be a nice feature in Outlook Express.

If Outlook doesn't shutdown properly when you are viewing a mail (i.e. your 
computer reboots spontaneously, outlook crashes, etc.). When you next startup 
Outlook it will not display that specific mail message that you have been 
viewing unless you click a link (the reasoning being is that mail may have 
crashed Outlook, so maybe you want to not view the message and just delete it)
Comment 1 Dan Winship 2001-01-19 15:31:41 UTC
A nice idea, but I'm not sure how easy it would be...
Comment 2 Jeffrey Stedfast 2001-07-20 21:29:34 UTC
marking as future, although I'm not even certain we should even bother
doing this...

Comment 3 gnobian_ken00bie 2005-06-07 10:47:30 UTC
With bugs such as http://bugzilla.gnome.org/show_bug.cgi?id=306751 and the
possibility of others like it, I would consider this to be of far greater
severity than you seem to suppose. As a relative newbie assisting a nontechnical
user who experienced this crashing problem - Evolution crashing repeatedly at
startup - my only solution was to first delete
~/.evolution/mail/local/Inbox.cmeta and then to change preferences to plaintext
only so that the offending e-mail could be deleted. I don't believe the e-mail
was malicious, but doesn't this qualify as a DoS vulnerability?
Comment 4 gnobian_ken00bie 2005-06-07 10:54:01 UTC
I looked it up and no, this isn't a DoS. My apologies for improper terminology.
But it is potentially very frustrating for users. As for example, a user in a
forum discussing this crashing whose only solution was to delete his Inbox.
Comment 5 bugs 2005-12-02 08:31:02 UTC
This seems to be a no-brainer.  I do not see why it would not be included.
Comment 6 Sebastien Bacher 2008-10-29 23:01:36 UTC
the bug is fixed in the current version