On Microsoft SBS2003 I am running Exchange 2003, we as everyone else exceeded the 16 gig limit and made the necessary registry settings modifications to over ride this limitation. At which point I have run the eseutil /d (database name) /p /t (name of edb) /s (name of stm), the edb an stm files compressed and defragged fine. The database again began to grow where both the stm and edb files were 14 and 15 gigs in size = 29 gigs, I again tried the eseutil with the same settings, and the size only went down by 1 gig in total.
Since I've run the following switches in using the eseutil to determine if I've got a bad information store:
/g - Result was no errors what so ever everything checked out great
/k - Same as above nothing wrong with the headers
/mh - The shut down was fine, state of databases were normal - no problems
/ml - log files checked out fine
The databases continue to grow and now I've run the above checks prior to running the eseutil /d command and both the stm and edb files only compress about 1 gig only in total size adding both stm and edb files together.
We're using a mixed MAPI, POP3 and IMAP clients for email conncectivity including the HTTP Web Mail options over RFC.
We've examined the sizes of the mailboxes on the exchange server as well under the Server Manager panal / Information Store / Mailboxes and calculated what it is showing in the mail boxes of our users and it totals 10 gigs total...again where is all this mail going?
Would like any suggestions or help to this problem please, Thank you!