I've run across a strange situation on my exchange 2007 server, that I can't find any info on anywhere. I have two message with a status of "active" stuck in my submission queue. In the Queues view, the submission queue has a delivery type of "undefined". However in the messages view, the message source name is SMTP : default (mailservername). Both messages are past their expiration date, yet are still there. Most actions performed on these messages fail due to their active state. They cannot be deleted, they cannot be exported, etc. etc. Here's the output of: get-message -q submission: Code Snippet Identity FromAddress Status Queue Subject-------- ----------- ------ ----- -------xxxmail\Submission\33935 matthewk@xxxxx.com Active pstmail\Submission Order #172076xxxmail\Submission\37500 JLievanos@xxxxx.com Active pstmail\Submission PLEASE FILL OUT THE ATTACH... And piped to fl: Code Snippet Identity : xxxmail\Submission\33935Subject : Order #172076InternetMessageId : <71C3A0304D961643B28EE5F7C67012E30273317F@obiwan.xxxxx.net>FromAddress : matthewk@xxxxx.comStatus : ActiveSize : 345113BMessageSourceName : SMTP:Default xxxMAILSourceIP : xx.150.7.200SCL : 0DateReceived : 3/31/2008 5:02:19 PMExpirationTime : 4/1/2008 5:02:19 PMLastError :RetryCount : 0Queue : xxxmail\SubmissionRecipients :IsValid : TrueObjectState : UnchangedIdentity : xxxmail\Submission\37500Subject : PLEASE FILL OUT THE ATTACHED...InternetMessageId : <BC7E4457B677CC4385BD63B6EA13DD5F0E09F116@nd.corp.xxxxxx.com>FromAddress : JLievanos@xxxxxx.comStatus : ActiveSize : 548693BMessageSourceName : SMTP:Default xxxMAILSourceIP : xx.87.54.12SCL : 0DateReceived : 4/1/2008 1:47:14 PMExpirationTime : 4/2/2008 1:47:14 PMLastError :RetryCount : 0Queue : xxxmail\SubmissionRecipients :IsValid : TrueObjectState : Unchanged The other odd thing is, that groupshield has detected both messages as being corrupt. I have restarted the service thinking perhaps that's what's keeping it there somehow, but no love. How do I delete these sticky messages? I've already confirmed that they have been delivered to the intended recipients, These are actually previous failed attempts to send them. UPDATE; restarting the groupshield service gets it going again, but I have to do it like twice a day. LAME!!! Thanks, Rich Weber

Exact same problem here, but only a single message in my case. I rebooted the HT server and when it came back online, the Transport service hung... I rebooted it again, and it came back, and processed the message in the queue. Not exactly a production solution, but it worked. I would love to know how to fix this without a rebootbefore I deploy into a production environment.

As I wrote in my update above, for me, I have to restart my antivirus for exchange software to get it moving again. This didn't happen at all when I had a smarthost antivirus solution. I'm against edge transport because of the incredible amount of extra cost associated with it, when it was a one box solution before, However, I may go that direction. Currently, I simply have to watch the queue for build up all day since I don't have MOM, either.