Like any email server, Exchange makes heavy use of DNS, so it’s logical that if DNS is not configured properly, then messages are not going to be transported to either internal or external destinations. Unless the Exchange 2013 servers know how to route messages, the items stay where they are. Incorrect DNS binding to server NICs is one of the likely culprits. What else would stop transport being able to process outbound messages and force the Store to keep them in the Drafts folder?Ĭhecking DNS Lookup properties for a server with EAC Certainly, if a service fails or is not running for some reason, it’s likely that the administrator will notice that this is the case and fix the problem. Now, the normal state of events is that all of the Exchange services are running along quite happily on the server. ![]() 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. 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.įor instance, items will remain in the Drafts folder if the Store cannot pass them to the transport system. 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. At this point, items are moved into the Sent Items folder. ![]() Messages stay in the Drafts folder until they are successfully sent by being processed by the transport service. 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. Exchange 2013 Mail Flow (source: TechNet)īut 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.
0 Comments
Leave a Reply. |