Author Topic: Inbox Has Decompression Bomb. What to do?  (Read 2862 times)

0 Members and 1 Guest are viewing this topic.

Nattechy

  • Guest
Inbox Has Decompression Bomb. What to do?
« on: April 02, 2010, 07:01:02 PM »
Hello all! I recently formatted my hard drive. I backed up my data, emails, etc. (I use Thunderbird) and installed the latest version of Avast! on my fresh WinXP install.

For kicks I decided it would be a good idea to have avast run a virus  scan on all my backed up data just in case. It turned up a "decompression bomb" in my email programs inbox. The thing is the inbox is one whole file (or looks to be anyway), inbox.msf. I am afraid to open it.

How can I delete the offending email without deleting my entire inbox (I have hundreds of emails that I need to keep)? The file avast has found is called "partno_0#2958668151". I've ran a search in Thunderbird for an email with this header, subject and have found nothing. Any help would be greatly appreciated. Thank you!

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 88445
  • No support PMs thanks
Re: Inbox Has Decompression Bomb. What to do?
« Reply #1 on: April 02, 2010, 07:24:35 PM »
Do nothing.
- Decompression Bomb, a file that is highly compressed, which could be very large when decompressed. This used to be a tactic long ago to swamp the system, also see http://forum.avast.com/index.php?topic=15389.msg131213#msg131213.
 
The name really is the most dangerous thing about this and I wish they would change it or simply not report it, a real PITA.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 23.10.6086 (build 23.10.8563.800) UI 1.0.784/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Hermite15

  • Guest
Re: Inbox Has Decompression Bomb. What to do?
« Reply #2 on: April 02, 2010, 07:51:46 PM »
Quote
Inbox Has Decompression Bomb. What to do?
>>> run  ;D
OK seriously it would be about time that Avast calls that something else ::) This would avoid this same question to be asked again and again ;)
what about "lethal file/archive" ???  :D