Microsoft KB Archive/262354

= Misleading NDR When Sending to Remote Domain That Does Not Allow Relay =

Article ID: 262354

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-



This article was previously published under Q262354



SYMPTOMS
When you send messages to a remote domain that does not allow relay, you may receive an non-delivery report (NDR) similar to the following:

The following recipient(s) could not be reached:

User@Remotedomain.com on 1/6/00 7:58 PM

The originator does not have permission to submit message

dns;Wsilver.com failed 5.7.1 smtp;550

5.7.1 Unable to relay for User@Remotedomain.com



CAUSE
The actual reason for the NDR is that the remote domain has prohibited the sending domain from relaying. The NDR can be misleading because it implies that it is a permissions problem with the sender. The Delivery Status Notification (DSN) error code is defined in Request for Comments (RFC) 1893 as &quot;Delivery not authorized, message refused.&quot; For additional information about status codes forDelivery Status Notification (DSN) messages, click the article number below to view the article in the Microsoft Knowledge Base:

256321 XCON: Enhanced Status Codes for Delivery - RFC 1893



STATUS
This behavior is by design.

Additional query words: xmrp exch2kp2w XCON

Keywords: kbnofix kbprb KB262354

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.