When OE Inbox.dbx becomes too big

 
You have two choices. If you do not have any messages that you need, you can just wipe out the Inbox by creating a new one.

If you do have messages you need, do the following, but instead of deleting the Inbox.dbx, rename it to Inboxold.dbx. You will still have a new empty, and working Inbox, but will need a tool to retrieve the lost messages. 

Tools | Options | Maintenance | Store Folder will reveal the location of your Outlook Express files. Write the location down and navigate to it in Windows Explorer or, copy and paste it into Start | Run.
In WinXP, Win2K & Win2K3, the OE user files (DBX and WAB) are by default marked as hidden. To view these files in Windows Explorer, you must enable Show Hidden Files and Folders under Start | Control Panel | Folder Options Icon | View, or in Windows Explorer | Tools | Folder Options | View.
With OE closed, find the Inbox.dbx. as mentioned above, if there isn't any mail such important, you can delete them directly otherwise otherwise rename as I mentioned before.  (But Remember it is defenitely a difficult task t oretrieve those mails as OE doesn't support a. Inbox.dbx file more than 2GB. There should be some softwares available to retrieve so.) A new Inbox will be created automatically when you re-open OE.

General precautions for Outlook Express:
Do not archive mail in the Inbox or Sent Items. Create your own user defined folders and move the messages you wish to save to them. Empty Deleted Items folder daily. Although dbx files have a theoretical capacity of 2GB, I recommend about a 300MB max for less chance of corruption.

Comments

Post a Comment

Popular posts from this blog

CDbConnection failed to open the DB connection mysql 8

Image
While accessing web configured with mysql 8 and php and you see the following error: CDbConnection failed to open the DB connection: SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client OR  PHP Fatal error:  Uncaught PDOException: PDO::__construct(): The server requested authentication method unknown to the client [caching_sha2_password]  It maybe due to  PHP devs might have not implemented the MySQL's 8.0 connection protocol ( auth with caching_sha2_password ) within the newer PHP versions. If you want to use mysql >= 8 and you dont care about caching_sha2_password,  If you are running a fresh install of mysql 8, just select the second option as shown in the image. Otherwise, you need to  configure MySQL 8.0 to run in mysql_native_password mode. As it can't configured in my.cnf, change the user profile as:- ALTER USER 'mysqlUsername'@'localhost' IDENTIFIED WITH mysql_native_password BY 'mysqlUs...
Read more

Oracle 10g installation steps in CentOS 5

 Download the Oracle 10g database from the Oracle website. Graphical environment should be installed correctly in the server before installing oracle. Open a terminal command line and Untar the zip file and go to the folder 'database'. From there type the below given command as a user other than root. Better create a user named 'oracle'. ./runInstaller -ignoreSysPrereqs If you find any error as shown below, ---------- Initializing Java Virtual Machine from /tmp/OraInstall2008-08-25_11-53-58AM/jre/bin/java. Please wait... Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/OraInstall2008-08-25_11-53-58AM/jre/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory  --------- Then install libXp as shown below, yum install libXp And then give the command 'runinstaller' . The software will then open a graphical interface and will check for the system requirements. If it shows some errors in th...
Read more

/bin/sh^M: bad interpreter: No such file or directory Linux

While running a script in Linux, if you encounter an error such as : /bin/sh^M: bad interpreter: No such file or directory The error is due to incorrect format of the script. Most probably when the script is created in Windows and transferred to Linux. The script might have a dos line ending file. The clue is the ^M Inorder to resolve this error: Open the script in Linux using vim editor,  enter in vi command mode (key ESC), then type this: : set fileformat = unix   Finally save it :x! or :wq! Thats it! Try running the script again and the error would have disappeared.  
Read more