293112 - Hangs on viewing mailbox holding message with certain header?

Status: RESOLVED EXPIRED

(Thunderbird :: General, defect)

Description

[dolphinling]

I recieved an email, automatically marked as junk. When I went to view the Junk
mailbox, Thunderbird hung at 100% cpu. I force-quit and restarted twice, and
both times it still hung. Then I went into the <profile>/Mail/<account>/Junk
file, backed it up, and deleted a header:

Original-recipient: rfc822;[e-mail]

from the email. After starting Thunderbird again, it worked fine.

After that, I tried to reproduce the problem, but even after restoring from the
backup and deleting the Junk.msf file the problem did not show up. I don't have
any way to send myself an email with arbitrary headers, or I would try that.

Other things happened on their own (the backup, Junk.old, got its own .msf and
.sbd), so I believe something in my testings may have "de-corrupted" a file
without my knowing, and that made me unable to reproduce the problem.

My system is (Gentoo) Linux, Thunderbird 1.0.2 

I've marked this security sensitive because if there is a bug that can be
exploited, it appears to be able to DoS a particular mailbox.

Comment 1

[dolphinling]

Attachment: Email that caused the problem

Here's the email that (AFAICT) caused the problem. As I said before, things
happened on their own that I didn't konw about, so this _might_ not be in
pristine form, but I haven't done anything to it.

If there's anything else I can attach or test, I'd be happy to

Comment 2

[Daniel Veditz [:dveditz]]

I can't reproduce this, opening up to get potentially more eyes on the problem.
It could well be some interaction with your particular profile state, such as
the spam training data or an index file corruption. If you can't reproduce this
anymore either I'm not hopeful we'll be able to discover the problem.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.