Search  Rules  Login
TheBat English » The Bat! - Configuring the E-mail Client
Pages: 1
RSS
questions, access to e-mails
 
#1
0  
1) Is there any way to convert TheBat e-mail folders to Outlook without losing any file or format?

2) I cannot read in TheBat v.3 some of my e-mails which had been archived in TheBat v. 2. What is the solution?

3)Is there any way to get rid of compressing-decompressing since I turn on/off my computer serveral times a day?

4) While searching for e-mails I am receiving several error messages becasue some e-mails are not readable by TheBat v.3.  How can I get rid of these error messages?
 
 
 
#2
0  
well, I don#t have any hints on 1) as I don't use Outlook - guees it depends on if that can handle UNIX mbox format... or whatever you might export from TB - no clue on 2)... BUT ;)

3 - there is (though I would not recommend this when you're getting a sustantial amount of mails! the data base needs some care... however): first ensure that account/properties/options "compress all folders on exit" is UNset - then (if still compression runs) review the "on exit" settings of every folder on which compression is acting (foder/properties/general "on exit")

btw: you can schedule folder maintenance, too (via SmartBat scheduler)! I'd suggest to at least do that once a week when you turn it off on shutdown

4 - well, could be a thousand reasons, from corrupted single files up to hard disc problems (they DO happen!)... first step would be to use the folder maintenance center for "check integrity/repair" on alle folders... then see, what happens... btw: errors are more likely if you do not compress the mail data base for a long time (at least so it was in the past)

hope this helps
 
 
 
#3
0  
1) The only way to export from TB to Outlook is to export your TB mail to .eml, import those .eml files in Outlook Express and Outlook can import from OE.

2) Can have a wide variety of reasons, all coming down to the fact that the messagebase has been corrupted. From TB 1.45 on all versions used the same message base format, so messages should only be unreadable when something went awry.
The other cause could be a corrupt index file, you can easily check for that. Close TB, go to your problem folder(s) and rename the messages.tbi files to messages.tbi.old. Start TB and go to those folders and check whether the problem persists. If so than go to my next piece of prose, if not than you know what was the problem.

I don't know how many problem messages you've got, are they all in the same folder or do you encounter them in many folders?
Running maintenance as discussed by nlkes should offer an opputunity to get rid of them. When you think they might be important messages you can create a copy of the messages.tbb files of the problem folder(s) and search those copies for the problem messages with a plain text editor, salvage your messages by saving them as *.msg (plain text) and you can import them again in TB.
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
 
 
 
Pages: 1