Article ID: 329636 - View products that this article applies to.
This article was previously published under Q329636
When users send e-mail to external, remote, or Internet domains, they may receive the following notification from the Postmaster or Administrator of the local Exchange server:
Delivery Status NotificationThe user may also receive the following message indicating the time expiration of delivery attempts for the message:
This is an automatically generated Delivery Status Notification.
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE
Delivery to the following recipients has been delayed
Your message did not reach some or all of the intended recipients.
Subject: Sender's subject
Sent: Date and time that the message was sent
The following recipient(s) could not be reached:
email@example.com on date and time
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
This behavior may occur if the outbound security of the Simple Mail Transfer Protocol (SMTP) virtual server or the outbound security of one or more SMTP Connectors are set incorrectly.
To verify whether this is the cause:
To view the description of the queues in retry status:
This resolution addresses two types of delivery methods.
Using DNS for DeliveryBy default, Anonymous access is the default setting for sending SMTP mail by using DNS to all Internet domains. To resolve this behavior:
Forwarding Mail Through a Smart HostUse an SMTP connector for this type of delivery, and set access control to the requirements of the smart host. For more information about when to use an SMTP Connector, see the "References" section.
(http://support.microsoft.com/kb/294736/EN-US/ )XCON: When to Create SMTP Connectors in Exchange 2000
(http://support.microsoft.com/kb/314961/EN-US/ )HOW TO: Install and Configure SMTP Connectors in Exchange 2000 Server
(http://support.microsoft.com/kb/284204/EN-US/ )XCON: Delivery Status Notifications in Exchange 2000 Server
Article ID: 329636 - Last Review: October 30, 2006 - Revision: 2.2
Contact us for more help