Worm.Mimail.J aka PayPal.com worm crashes Thunderbird junk mail controls and thus Thunderbird

RESOLVED EXPIRED

Status

--
critical
RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: rasche, Assigned: mscott)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031225 Firebird/0.7
Build Identifier:  Mozilla Thunderbird 0.4 (20031221) - no more info in the about - why? - I'm running under (X11; U; Debian GNU/Linux i686 2.6.1 unstable; en-US)

Hi ALL,

I encounter regularly crashes of Mozilla-Thunderbird under Debian GNU/Linux Sid
if with Worm.Mimail.J infected mail comes in. As I see it this happens when the
Junk Mail Control is beginning to take care of this messages. It mark them and
Thunderbird goes by.

After a restart Thunderbird tries mostly again to download the message and the
some thing happens. Cause my Mail ISP has a time limit for connecting, after
some tries Thunderbird can not anymore try to download the infected message.
Than I may be able to delete the infected message mostly with marking it within
a bunch of others. If I do it with marking it junk, Thunderbird mostly crashed
again and again, sometime he comes also over it so.

One important thing:
My mail ISP freemail.web.de tells me in his Web front end that a virus was
deleted from the message. This can mean they cause the Thunderbird crash with
there virus removal tool?

One important thing:

Entfernter Virus: Worm.Mimail.J Viruswarnung an Absender  E-Mail löschen 
"PayPal.com"<Do_Not_Reply@paypal.com>  	IMPORTANT fmvvzroc 1K Mi. 07.01.04 

As my mail ISP calls the worm 'WORM_MIMAIL.J [Trend]' it looks as they use Trend
following Symantec's list here:
http://securityresponse.symantec.com/avcenter/venc/data/w32.mimail.j@mm.html
Also Known As: 	W32/Mimail.j@MM [McAfee], WORM_MIMAIL.J [Trend], Win32.Mimail.J
[Computer Associates], W32/Mimail-J [Sophos], I-Worm.Mimail.j [Kaspersky]
Variants: 	W32.Mimail.I@mm

My mail ISP web.de is probably Germany's biggest one, so as Thunderbird has a
nice market share here it may occur to others too.

Thank you in advance! Jan


	



Reproducible: Always

Steps to Reproduce:
1.
2.
3.



Expected Results:  
I can live with this crashes - but this may not looking good for Thunderbird on
not as geeky guys. :-)

Comment 1

14 years ago
If this still happens recent builds, would it be possible for you to download
the message that crashes Thunderbird and post it an attachment?
If it does not happen anymore then please close this bug.

Comment 2

14 years ago
Jan Rasche: If you could reproduce this crash, please provide TalkBack incident ID?
Keywords: crash
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.