Internet Related/Filtering/Firewall Thread, Exchange Mailboxes in Technical; The badmail folder contains messages that can't be delivered, like NDR's with a non-existant recipient (mostly spammessages). I had this ...
18th June 2009, 11:24 AM #16
The badmail folder contains messages that can't be delivered, like NDR's with a non-existant recipient (mostly spammessages). I had this folder filling up and clogging my mailserver once...
The way around this is to have your Exchange check wether or not a recipient exists when receiving mail, rather than accept the mail, check for the recipient and when te recipient does not exist, send a NDR (wich, in the case of spam, can't be delivered because the sender address was spoofed).
If there are any messages in the badmail folder, just delete them, they can't be delivered anyway...
IDG Tech News
18th June 2009, 11:27 AM #17
Where do i find that folder??
18th June 2009, 01:20 PM #18
I think it's somewhere in C:\Program Files\Exchsrvr (maybe under MDBDATA)...
I've moved mine to another drive, so i can't check anymore...
If you use search in Explorer and search for 'badmail' you should find it.
18th June 2009, 01:37 PM #19
Assuming its in the default location, look in:
c:\Program Files\Exchsrvr\Mailroot\vsi 1
18th June 2009, 06:11 PM #20
Yes should work, I think it is in the bin folder under exchsvr. Should just be sble to copy it and the datastore to a different box for defrag/compress.
Originally Posted by DSapseid
18th June 2009, 10:47 PM #21
As a rule when sizing the volumes to be used for an exchange database you need at least as much free space as that used by your database and log files.
If your exchange database used space is 40Gb then you need 80Gb of total diskspace.
The reason for this is so that your exchange maintenance can work properly by making a copy of the database during the maintenance cycle.
If you get to the point where your free space is less than your used space the database never compresses properly and it starts to grow rapidly.
Space created by deleted items never gets compressed.
Once this happens an offline defrag and compress using eseutil becomes essential.
If you want to keep your database small keep it on a volume with plenty of space and it will keep itself healthy.
Where possible I keep the logs on one volume and the databases on another.
Even better keep the databases on an expandable array.
By danrhodes in forum Windows Server 2000/2003
Last Post: 24th March 2009, 10:20 AM
By coop1984 in forum Windows
Last Post: 14th December 2007, 09:37 AM
Last Post: 21st January 2007, 04:46 PM
By paullong in forum Windows
Last Post: 29th March 2006, 07:27 AM
By pickman in forum Windows
Last Post: 10th February 2006, 09:06 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)