<div>
Do you know why this change was implemented?
</div>


Do you know why this change was implemented?

<div>
Not really sure why. But heres why I think it was.<br />
<br />
Since the link speeds and the bandwidth has grown so large, there really no need to schedule delivery. Messages can be transferred in real time.<br />
<br />
Its just what I think.. You can ask the Exchange design team at <a href="http://msexchangeteam.com/" rel="ugc">http://msexchangeteam.com/</a>
</div>


Not really sure why. But heres why I think it was.

Since the link speeds and the bandwidth has grown so large, there really no need to schedule delivery. Messages can be transferred in real time.

Its just what I think.. You can ask the Exchange design team at http://msexchangeteam.com/ [http://msexchangeteam.com/]

<div>
<div class="content wysiwyg-content">
We are in the process of upgrading Exchange from 2003 to 2007. &nbsp;In Exchange 2003 you could set when the Routing Group connect was available. &nbsp;You can modify the setting under Routing Groups | Connectors | Properties | Delivery Options tab Specify when message are sent through this connector. &nbsp;We used this to delay mass mails to after business hours. &nbsp;I wanted to see how you set this up in Exchange 2007.
</div>
</div>


We are in the process of upgrading Exchange from 2003 to 2007.  In Exchange 2003 you could set when the Routing Group connect was available.  You can modify the setting under Routing Groups | Connectors | Properties | Delivery Options tab Specify when message are sent through this connector.  We used this to delay mass mails to after business hours.  I wanted to see how you set this up in Exchange 2007.

Delay messages in send connector

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.