Solved

Undeliverable message when sending email

Posted on 2011-09-19
4
2,260 Views
Last Modified: 2012-05-12
Hi Experts,

I'm getting the following NDR back, I need some help with identifying where the problem lie?
The person I'm trying to send to put as "recipient.email@somewhere.com" to hide to original email address and my email (the sender) and put as "my.email@somewhere.com"
I suspect the issue is at the recipients end, but would need to understand how you can see see that based on the NDR log below
__________________________________________________________________________

Delivery has failed to these recipients or groups:

recipient.email@somewhere.com
A problem occurred during the delivery of this message. Please try to resend the message later. If the problem continues, contact your helpdesk.

Diagnostic information for administrators:

Generating server: np0nteml04.hiq.net.nz

recipient.email@somewhere.com
#< #5.4.6 smtp;554 5.4.6 mail loop detected> #SMTP#

Original message headers:

Original message headers:

 

Received: from mx1.securemx.biz ([203.84.134.2]) by np0nteml04.hiq.net.nz with

Microsoft SMTPSVC(6.0.3790.4675);       Mon, 19 Sep 2011 17:30:25 +1200

Received: from np0nteml04.hiq.net.nz ([202.14.107.9]) by omr.securemx.biz      with

ESMTP id 4E76D352-B3F00FC1@mta1103.omr;      Mon, 19 Sep 2011 05:29:54 +0000

Received: from mx1.securemx.biz ([203.84.134.2]) by np0nteml04.hiq.net.nz with

Microsoft SMTPSVC(6.0.3790.4675);       Mon, 19 Sep 2011 17:19:19 +1200

Received: from np0nteml04.hiq.net.nz ([202.14.107.9]) by omr.securemx.biz      with

ESMTP id 4E76D0B8-C68B1A2C@mta1103.omr;      Mon, 19 Sep 2011 05:18:48 +0000

Received: from mx1.securemx.biz ([203.84.134.2]) by np0nteml04.hiq.net.nz with

Microsoft SMTPSVC(6.0.3790.4675);       Mon, 19 Sep 2011 17:08:21 +1200

Received: from np0nteml04.hiq.net.nz ([202.14.107.9]) by omr.securemx.biz      with

ESMTP id 4E76CE26-49CC2733@mta1102.omr;      Mon, 19 Sep 2011 05:07:50 +0000

Received: from mx1.securemx.biz ([203.84.134.2]) by np0nteml04.hiq.net.nz with

Microsoft SMTPSVC(6.0.3790.4675);       Mon, 19 Sep 2011 16:57:21 +1200

Received: from np0nteml04.hiq.net.nz ([202.14.107.9]) by omr.securemx.biz      with

ESMTP id 4E76CB91-EADF0A31@mta1101.omr;      Mon, 19 Sep 2011 04:56:50 +0000

Received: from mx1.securemx.biz ([203.84.134.2]) by np0nteml04.hiq.net.nz with

Microsoft SMTPSVC(6.0.3790.4675);       Mon, 19 Sep 2011 16:46:20 +1200

Received: from np0nteml04.hiq.net.nz ([202.14.107.9]) by omr.securemx.biz      with

ESMTP id 4E76C8FD-4B032C0E@mta1103.omr;      Mon, 19 Sep 2011 04:45:49 +0000

Received: from mx1.securemx.biz ([203.84.134.2]) by np0nteml04.hiq.net.nz with

Microsoft SMTPSVC(6.0.3790.4675);       Mon, 19 Sep 2011 16:35:26 +1200

Received: from np0nteml04.hiq.net.nz ([202.14.107.9]) by omr.securemx.biz      with

ESMTP id 4E76C66F-D26809A1@mta1101.omr;      Mon, 19 Sep 2011 04:34:55 +0000

Received: from mx1.securemx.biz ([203.84.134.2]) by np0nteml04.hiq.net.nz with

Microsoft SMTPSVC(6.0.3790.4675);       Mon, 19 Sep 2011 16:24:54 +1200

Received: from np0nteml04.hiq.net.nz ([202.14.107.9]) by omr.securemx.biz      with

ESMTP id 4E76C3F7-BEF13BC7@mta1101.omr;      Mon, 19 Sep 2011 04:24:23 +0000

Received: from mx1.securemx.biz ([203.84.134.2]) by np0nteml04.hiq.net.nz with

Microsoft SMTPSVC(6.0.3790.4675);       Mon, 19 Sep 2011 16:24:52 +1200

Received: from np0nteml04.hiq.net.nz ([202.14.107.9]) by omr.securemx.biz      with

ESMTP id 4E76C3F5-2FD838A0@mta1102.omr;      Mon, 19 Sep 2011 04:24:21 +0000

Received: from mx1.securemx.biz ([203.84.134.2]) by np0nteml04.hiq.net.nz with

Microsoft SMTPSVC(6.0.3790.4675);       Mon, 19 Sep 2011 16:24:49 +1200

Received: from company.co.nz ([202.55.96.5]) by mx1.securemx.biz with ESMTP

      (using TLSv1 with cipher AES256-SHA (256/256 bits))      id

4E76C3F1-99380976@mta1101; Mon, 19 Sep 2011 04:24:18 +0000

Received: from wpdfg.company.co.nz ([172.16.1.20])      by FortiMail.company.co.nz

  with ESMTP id p8J4OEAZ016808-p8J4OEAb016808      (version=TLSv1 cipher=RC4-MD5

bits=128 verify=NO)      for <recipient.email@somewhere.com>; Mon, 19 Sep 2011

16:24:14 +1200

Received: from iuuytrewq02.hdsnz.int (172.16.1.42) by qwertyyu2.hdsnz.int

(172.16.1.20) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 19 Sep 2011

16:24:13 +1200

Content-Type: multipart/related;

      boundary="----=_NextPart_000_8428B_01CC76E8.929AF1E0"

Content-Transfer-Encoding: 7bit

Received: from RVIWPDMBX02.hdsnz.int ([::1]) by iuuytrewq02.hdsnz.int ([::1])  with mapi id 14.01.0289.001; Mon, 19 Sep 2011 16:24:13 +1200

From: Joe Blogg <my.email@somewhere.com>

Content-Class: urn:content-classes:message

Importance: normal

Priority: normal

X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4862

To: <recipient.email@somewhere.com>

Subject: TEST MESSAGE

Thread-Topic: TEST MESSAGE

thread-index: Acx2hBxU1As5H65HQP+INqaGnAvgiA==

Date: Mon, 19 Sep 2011 04:25:07 +0000

Message-ID: <5B6FECF8C889F7428D4369807C5CFCBD2E264F@RVIWPDMBX02.hdsnz.int>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

x-originating-ip: [172.16.1.23]

MIME-Version: 1.0

X-OriginalArrivalTime: 19 Sep 2011 04:24:49.0619 (UTC)  FILETIME=[11F8F230:01CC7684]

Return-Path: my.email@somewhere.com

[Edited by SouthMod]
0
Comment
Question by:craigleenz
  • 2
  • 2
4 Comments
 
LVL 18

Accepted Solution

by:
Netflo earned 500 total points
Comment Utility
Hi,

The answer lies with your recipients mail server, the hint is: #5.4.6 smtp;554 5.4.6 mail loop detected.

They appear to have forwarding to another location which in turn is configured to route back to their mailbox, either with a client side or server side rule.

Best to get in touch with their IT team and mention "error 5.4.6 mail loop detected"

Hope that helps.
0
 

Author Comment

by:craigleenz
Comment Utility
thanks Netflo, exactly what I was after,
0
 

Author Closing Comment

by:craigleenz
Comment Utility
thanks Netflo, exactly what I was after,
0
 
LVL 18

Expert Comment

by:Netflo
Comment Utility
Your most welcome :)
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

Utilizing an array to gracefully append to a list of EmailAddresses
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now