Hi The other night, the transaction logs on one of our Exch 2007 servers was growing rapidly. We managed to find the cause was a client that must have had a virus or something but was causing a lot of work for Exchange, which in turn generated logs for this work. We managed to close the connection by disabling the client's port on the local Cisco switch. We're looking at ways we could have done this better. Is there another way we can disable a client's connection to Exchange? I was thinking one of the following 1. Disable MAPI on the offending mailbox 2. Use TCPView to close the connection (IP > right click > Close Connection) Does anyone know any other method?

It sounds like you experiences a mail loop. Do you allow automatic forwards and/or replies to the Internet? That can allow them to happen. Mail loops are why I recommend setting a high Prohibit Send and Receive quota on all mailboxes, while setting the Prohibit Send quota to the actual enforcement quota limit. The Prohibit Send and Receive quota will eventually stop mail loops--it'll stop all mail for that matter--until the user can fix whatever he did and delete the multiple copies of the looping message. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi Chuck, Any updates? And if you consider virus is found, you should disconnect the client from the LAN immediately. Try to delete the virus. End user maybe connect to Exchange using OWA, POP3 as well... Maybe you can find the more information about the issue using Message Tracking or ExMon. Microsoft Exchange Server User Monitor http://www.microsoft.com/downloads/en/details.aspx?FamilyId=9A49C22E-E0C7-4B7C-ACEF-729D48AF7BC9&displaylang=enPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

An excellent write-up by Mike Lagase - Troubleshooting Exchange 2007 Store Log/Database growth issues . - Thanks, Jinesh.