Message Rerouted And Delayed By Store Driver Exchange 2007

Posted on by

One of the common things that OWA users notice about Exchange 2013 is that outgoing messages sometimes appear to get “stuck” in the Drafts folder. Not only do messages seem to linger in Drafts, no trace of the outbound messages ever shows up in the Outbox. Or so it seems, but really it’s an urban myth. Exchange 2013 boasts a new architecture. The hub transport server role is no more and its processing has been subsumed into the mailbox server role.

In turn, as the TechNet description of the makes clear, the Mailbox Transport service and the Transport service work together to process messages sent by clients. Exchange 2013 Mail Flow (source: TechNet) But how does the Drafts folder come into the picture? Well, OWA clients automatically capture copies of messages as they are being composed and store them in the Drafts folder. When the user issues a sent command, the Mailbox submit agent (running within the Store driver) takes over and processes the outbound message by giving it to either the Transport service running on the same mailbox server or to the Transport server running on another mailbox server. The connection is made via SMTP. Messages stay in the Drafts folder until they are successfully sent by being processed by the transport service.

Thoughtsofanidlemind's Blog. With Exchange 2007 if you installed HT on the MBX server then the MBX server. Exchange 2013: Stuck messages in.

Message Rerouted And Delayed By Store Driver Exchange 2007Exchange

At this point, items are moved into the Sent Items folder. OWA 2013 behaves in the same way as OWA 2010 – nothing has changed in the way that messages are held in the Drafts folder until dispatch. What might account for user descriptions of items being “stuck” is when a problem occurs somewhere in the transport pipeline that prevents outbound messages being processed. For instance, items will remain in the Drafts folder if the Store cannot pass them to the transport system. If the transport service is not running on any available server or the mailbox transport service is not running on the mailbox server that hosts the active database for the user’s mailbox, items will stay in the Drafts folder until the services come online and Exchange is able to process outbound items.