Hi, we have an exchange 2003 and one database .edb file grow very very fast. We check public/rules and mailbox/rules looking for a loop but we haven´t events. We have 4 database and just one of them has the issue. The database has more than 30gb but the mailboxes on it do not has more than 1gb. We run defragmentation process on it and the recover space is not enough. thanks for ideas.

Certainly sounds like a mail loop. Look under the mailbox store object at the list of mailboxes in that store and see if one of the is growing faster than the rest. If so, stick a prohibit send and receive quota on it and stop and restart the Information Store service. That should kill it.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "Johan M. R." wrote in message news:54a8588d-c290-4d3b-b7fb-db934cb03261... Hi, we have an exchange 2003 and one database .edb file grow very very fast. We check public/rules and mailbox/rules looking for a loop but we havent events. We have 4 database and just one of them has the issue. The database has more than 30gb but the mailboxes on it do not has more than 1gb. We run defragmentation process on it and the recover space is not enough. thanks for ideas. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Ed, the database was defragmented but it is still big. You think that it stopped the loop... and the database need an other defragmentation ?? Thanks.

At this point I'd move whatever mailboxes to another database, delete the database, create a clean one, then move the mailboxes back.Assuming the mailboxes really are just 1GB of data. It would be much faster that way and no outage.

Hi,For this issue, we need to diagnose it based on the below steps:Looping Messages: Check through the Message Tracking logCheck Public Folder Replication.Check File Level Antivirus ScanningDo you implement "Move Mailbox operation"?Whether any email stuck in the queue?If not the above cause, please try to use Isinteg to check whether any logical corruption in the database file.isinteg -s server1 -fix -test alltestshttp://support.microsoft.com/kb/182081ThanksAllen

Hi, Allen we found that antivirus exceptions was not configured. When defragmentation process was done and although the database size is more big from normal the growing was stopped. We are moving the mailboxes to a new database to be sure that database structure is ok. thanks a lot for your help. Johan Montano R.