Sunday afternoon, one of our database programmers was debugging some automessaging code on our websites and inserted a piece of code that, unbeknownst to him, resulted in an infinite loop continually sending messages to an info mailbox. By the time I noticed it this morning, almost half a million messages had been sent. This kinda clogged the system!
We stemmed the flow and I was left with an incoming queue containing 474,323 messages, 439,985 of them resulting from the infinite loop. In the Admin GUI, I scanned the entire incoming queue (it took 4 hours). I selected the appropriate sender address, right-clicked and selected Delete. I was asked if I really wanted to delete 439,985 messages, to which I responded "You betcha!" And now the Admin GUI and I are just sitting there looking at each other.
Is the deletion likely to complete? If so, how long is it likely to take? How will I know when it has completed? Should I click the Refresh button on the Incoming queue tab periodically, or will that result in another 4-hour scan job?
Should I have gone about this another way? (Not that I'm planning a repeat performance.)
On the flip side, I must say that it's very impressive that Zimbra appears to have withstood the onslaught, albeit suffering chronic indigestion of the incoming queue. All the services are running, but the hamsters working the treadmills must be getting pretty tired by now ... :-)