<div>
<div class="content wysiwyg-content">
I have a script that sends out periodic emails using anonymous (IP-based) relay via an Exchange 2010 SMTP server. The script works fine if i run it from any machine on the LAN (i have a Receive Connector that allows relay from LAN IPs). However if I try to run the script on the actual Exchange Server machine (that is also on the same LAN) it fails with the following error:<br />
The message could not be sent to the SMTP server. The transport error code was 0x800ccc67. The server response was 421 4.3.2 Service not available<br />
any clues?
</div>
</div>


I have a script that sends out periodic emails using anonymous (IP-based) relay via an Exchange 2010 SMTP server. The script works fine if i run it from any machine on the LAN (i have a Receive Connector that allows relay from LAN IPs). However if I try to run the script on the actual Exchange Server machine (that is also on the same LAN) it fails with the following error:
The message could not be sent to the SMTP server. The transport error code was 0x800ccc67. The server response was 421 4.3.2 Service not available
any clues?

Problem with Exchange 2010 Anonymous Relay from the server itself

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.

Exchange

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.