What role does the transport provider play when the message store supports submits directly? Our message store provider reads and writes information directly to an online database server. As such, calling IMessage::SubmitMessage() triggers the backend to do the send of the message without involving the transport provider. Similarly, when new mail arrives it is automatically delivered into the user's mailbox on the backend, triggering a table update in Outlook. The transport provider isn't really involved in "downloading" new mail like it would be in a POP or IMAP account. Yet a message service must have a transport provider defined to even be considered an "email account" by Outlook. I imagine that the Exchange providers operate in a similar manner. Could you elaborate on the interaction between the exchange message store and transport provider? I've also noticed that exchange includes two transport providers in it's message service: both a normal and a remote transport provider. How does the remote transport provider interact with the message store?
Thanks,
Dan
Microsoft
