Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was closed and archived. Please ask a new question if you need help.

How to create .mab and associated missing files

  • 2 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 1 view
  • Last reply by Matt

I had to format my hard drive to delete CryptoLocker. I had saved my Thunderbird email files from the directory tree and successfully re-integrated them into a newly downloaded copy of Thunderbird. I either didn't save the address book files or they were deleted as corrupted. I get a message about not being able to load .mab and I think that all of those files/folders to do with Address Book are probably missing. How do I make new ones to capture the addresses now when using Thunderbird?

I had to format my hard drive to delete CryptoLocker. I had saved my Thunderbird email files from the directory tree and successfully re-integrated them into a newly downloaded copy of Thunderbird. I either didn't save the address book files or they were deleted as corrupted. I get a message about not being able to load .mab and I think that all of those files/folders to do with Address Book are probably missing. How do I make new ones to capture the addresses now when using Thunderbird?

All Replies (2)

I have gone through my directory tree, deleted history.mab and re-opened TBird to find that it re-created itself just fine and a test email resulted in the Address Book showing the test email recipient's address. I have concerns about other files bearing the date of the corruption event. If I delete them, will they re-create themselves? In particular logins.json search.json.mozlz4 (is that a file at all, or is that possibly one created by the corruption event that I can just delete?) session_error_20161217104742672.json (again - is that a legitimate file? 17th is the date I installed TBird; perhaps the other numerals were put in there on 6.12.16 when the corruption occurred). Thanks