Hello All, I've search for that problem on the internet an on this forum without much success. We run Exchange 2003 in native mode. We have 2 backend servers ( clustered, Active/Active/Passive ). We have 2 front-end servers ( webmail, POP3, etc ) and 2 bridgehead servers ( for incoming and outcoming internet mail ). For now, everyting is working fine except for one thing: on one ofour bridgehead server, the database priv1.stm is 57 Go ( huge ! ). On the other bridgehead server, the size of priv1.stm is 700 Mo. according to event id 1221, on the problematic bridgehead server, there's only 9 Mo of free space for priv1.stm. I ran the eseutil with the /G switch to verify that the 57 Go database has no inconsistencies. No errors were found. I have 2 questions: 1. Does anybody has an idea as to why this database is so huge ? It is only a bridgehead server and it has no user mailbox. The 3 generic mailboxes ( SMTP, System Attendant and SystemMailbox ) on that server only total 361 Kb in size according to Exchange System manager; 2. How can I correct the problem ? Can I dismount the store, rename the priv1.stm file, and remount the store so that a new database will be created ? If so, would the mails that are queued on that server be lost during this operation ? Thanks in advance to all of you for your answers.

the stm file holds all mail submitted by non-mapi clients, so you'd have to look and see who isn't connecting with outlook. Look for event 1221 in the application log. there could be white space to be reclaimed during a defrag. question 2- an offline defrag will reduce the size if it really shouldn't be that big (based on event 1221) Exchange Storage Architecture http://technet.microsoft.com/en-us/library/bb124808(EXCHG.65).aspx How to defragment with the Eseutil utility (Eseutil.exe) http://support.microsoft.com/kb/192185

sorry i didnt see you already noticed the 1221 event. try the defrag and check back