Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

How to restrict the outflow of large messages using an SMTP Connector


Author: Mark Arnold MVP

View products that this article applies to.

Summary

Knowledge base article detailing how to configure a Routing Group and SMTP connector to control outbound SMTP traffic on a scheduled basis.

↑ Back to the top


Symptoms

Where�users�have a bulk mailing to be sent that may�have a large attachment going with that message you may not wish that message to be transmitted immediately. Sending�a low priority�message such as this�during working hours may swamp your Internet connection and reduce the performance�of Internet browsing for the user population. You may wish to defer the sending of these messages until a more appropriate time.

↑ Back to the top


Resolution

You can create a Routing Group (where one does not already exist) and then create an SMTP connector. Open Exchange System Manager and expand the Administrative Group. If you do not see either the Administrative Groups object or a folder called "Routing Groups" then select Action and then Properties. You will then be able to see whether your organisation is in Mixed or Native Mode and be able to select whether or not to view Administrative Groups and Routing Groups.

Highlight�the Routing Groups folder and right click, selecting New Routing Group. There are no options here beyond what to call it and the option to enter some notes. The Routing Group will be created, as will two folders underneath called Connectors and Members.

Highlight and right click on the Connectors folder and select "New" and then�"SMTP Connector". A window with a large number of tabs will be presented. Only the necessary fields�are documented here.

On the General tab decide whether to send messages out via a smart host or not. This setting overrides any setting that has been entered on the SMTP Virtual Server. Select the local bridgehead. Where there are multiple servers in an organisation you may wish to select one server to hold the queue of messages until the scheduled time.

On the Address Space tab the default will be for messages to all domains. If you�send large, low priority messages to a small number of domains then you may wish to narrow down this connector to a list of domains that you specify.

The final important section is the Delivery Options tab. This is where the sending schedule is set. Generally the "Connection time" is not changed but the checkbox for "Use different delivery times for oversize messages" must now be ticked. This will make the oversize message size box visible. Remember that this setting is in Kilobytes rather than Megabytes. The last task is to select the Connection Time.�The default is to "Use custom schedule". The Customise button is now selected and a time frame for sending messages larger than the pre-defined size is now made. Select the schedule and apply the changes.

Other tabs exist but for the purposes of this article are not relevant.

Messages larger than the pre determined size will now be queued on the bridgehead server until the appropriate time has been reached.



↑ Back to the top


More information

This article is for the restriction of messages from entitled users but you may wish to deny certain users access to Internet mail. http://www.msexchange.org/tutorials/MF025.html�explains this process.

↑ Back to the top


Community solutions content disclaimer

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.

↑ Back to the top


Keywords: KB555260, kbhowto, kbpubtypecca, kbpubmvp

↑ Back to the top

Article Info
Article ID : 555260
Revision : 1
Created on : 8/1/2005
Published on : 8/1/2005
Exists online : False
Views : 252