Microsoft KB Archive Search

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.

  1. Home
  2. Message Delivery in Exchange Server fails with an Event ID 3017 & a NDR with a status code of 5.4.5

Message Delivery in Exchange Server fails with an Event ID 3017 & a NDR with a status code of 5.4.5

Author: Mohammed Athif Khaleel MVP

View products that this article applies to.

Summary

Event ID 3017: A non-delivery report with a status code of 5.4.5 was generated for recipient rfc822; user@domain.com.Causes: A looping condition was detected. (The server is configured to route mail back to itself).

↑ Back to the top

Symptoms

Event Type:�Error
Event Source:�MSExchangeTransport
Event Category:�NDR
Event ID:�3017
User:��N/A
�
Description:
A non-delivery report with a status code of 5.3.5 was generated for recipient rfc822;User@domain.com (Message-ID <DAAEA583454F0145AE3D3CD522D9293703E8E40C@AFG-NET-EXC.riyadh.afg.com>).��

Causes: A looping condition was detected. (The server is configured to route mail back to itself). If you have multiple SMTP Virtual Servers configured on your Exchange server, make sure they are defined by a unique incoming port and that the outgoing SMTP port configuration is valid to avoid looping between local virtual servers.�
��
Solution: Check the configuration of the virtual server�s connectors for loops and ensure each virtual server is defined by a unique incoming port.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: cf 02 04 c0�������������� �..����

↑ Back to the top

Cause

This is due to�a loop-back situation where the server is configured to loop back on itself and�a non-delivery report with a status code of 5.3.5 was generated for recipient.

↑ Back to the top

Resolution

Check the configuration of the SMTP Virtual Server;
�
- Using Exchange System Manager navigate to the following location;
- Default SMTP Virtual Server Properties
- Delivery Tab - Advanced
- Advanced Delivery - Configure
- Make sure you do not have any Internal and External DNS configured. This may cause�a loop-back situation.

Note: External DNS IP's should be configured only on Front End SMTP Virtual Server.
Check the configuration of the Exchange SMTP Connector;
�
- Using Exchange System Manager navigate to the following location;
- Administrative Group - Servers
- Connectors
- SMTP Internet Connector - Properties
- Address space - Make sure the SMTP Address space is Asterisk, "*"
�
Since, SMTP Connector is used to send emails to any domain on Internet, it should always be "*"
�

↑ Back to the top

More information

For a list of Non Delivery Report Status Codes, check;
Delivery status notifications in Exchange Server and in Small Business Server;
http://support.microsoft.com/kb/284204

↑ Back to the top

Properties

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

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: KB555418, kbhowto, kbpubtypecca, kbpubmvp

↑ Back to the top

Article Info
Article ID : 555418
Revision : 1
Created on : 8/17/2005
Published on : 8/17/2005
Exists online : False
Views : 265