SMTP: Default Value of Outbound Connections Too High

 Last reviewed: February 3, 1998
Article ID: Q160826
The information in this article applies to:
  • Microsoft Commercial Internet System, version 1.0

SYMPTOMS

The current default setting for the maximum number of outbound connections is 500. This value has been known to cause TCP/IP on the sending server to stop responding if the receiving server cannot handle the large number of incoming connections. Reducing the default setting will aid in preventing this problem from occurring in production environments, but will not completely eliminate it.

WORKAROUND

To work around this problem, reduce the maximum number of outbound connections to 100.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Commercial Internet System (MCIS) version 1.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

No site, not even a site with more than a million messages per day, should require more than 100 concurrent outbound connections. Even if a site does need more than 100 connections, you can make this configuration on the SMTP Service tab of the Internet Service Manager (ISM).

Additional query words: 1.00 SMTP
Keywords : kbbug1.00 kbenv
Version : 1.00
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.