TheSonicGod
asked on
Exchange 2007 to Lotus Domino 'Maximum hop count exceeded. Message probably in a routing loop' errors
Hi Everyone,
We have a couple of users who when sending to one of our vendors randomly keep getting the same errors for an undeliverable message:
Delivery has failed to these recipients or distribution lists:
name@vendor.ca
An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
The following organization rejected your message: xxx.xxx.19.86.
Diagnostic information for administrators:
Generating server: vendor.ca
name@vendor.ca
xxx.xxx.19.86 #<xxx.xxx.19.86 #5.0.0 X-Notes; Error transferring to xxx.xxx.19.86; Maximum hop count exceeded. Message probably in a routing loop.> #SMTP#
Original message headers:
Received: from smta01.vendor.ca ([10.252.40.136]) by
vendor.ca (Lotus Domino Release 8.5.3FP6) with ESMTP id
2014062012385660-283430 ; Fri, 20 Jun 2014 12:38:56 -0400
Received: from BRIGHT01.vendor.ca ([xx.xxx.20.167])
by smta01.vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385652-121329 ;
Fri, 20 Jun 2014 12:38:56 -0400
Received: from scmze000.xxxx.xxx-xxx.xx.c a ( [xxx.xxx.19.84])
by BRIGHT01.vendor.ca (Symantec Messaging Gateway) with SMTP id 52.99.20810.E9364A35; Fri, 20 Jun 2014 12:38:55 -0400 (EDT)
Received: from scmze999.xxxx.xxx-xxx.xx.c a ([xxx.xxx.19.83])
by scmze000.xxxx.xxx-xxx.xx.c a with ESMTP; 20 Jun 2014 16:38:54 +0000
Received: from inbound4.vendor.ca (HELO vendor.ca) ([xxx.xxx.93.80])
by scmze000.xxxx.xxx-xxx.xx.c a with ESMTP; 20 Jun 2014 16:38:54 +0000
Received: from smta01.vendor.ca ([xx.xxx.40.136])
by vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385378-283427 ;
Fri, 20 Jun 2014 12:38:53 -0400
Received: from BRIGHT01.vendor.ca ([10.252.20.167])
by smta01.vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385374-121323 ;
Fri, 20 Jun 2014 12:38:53 -0400
Received: from scmze000.xxxx.xxx-xxx.xx.c a ( [xxx.xxx.19.84])
by BRIGHT01.vendor.ca (Symantec Messaging Gateway) with SMTP id D1.99.20810.B9364A35; Fri, 20 Jun 2014 12:38:52 -0400 (EDT)
Received: from scmze999.xxxx.xxx-xxx.xx.c a ([xxx.xxx.19.83])
by scmze000.xxxx.xxx-xxx.xx.c a with ESMTP; 20 Jun 2014 16:38:51 +0000
Received: from inbound4.vendor.ca (HELO util01.vendor.ca) ([xxx.xxx.93.80])
by scmze000.xxxx.xxx-xxx.xx.c a with ESMTP; 20 Jun 2014 16:38:51 +0000
Received: from smta01.vendor.ca ([xx.xxx.40.136])
by util01.vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385088-283423 ;
Fri, 20 Jun 2014 12:38:50 -0400
Received: from bright11.vendor.ca ([xx.xxx.20.144])
by smta01.vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385079-121314 ;
Fri, 20 Jun 2014 12:38:50 -0400
Received: from scmze000.xxxx.xxx-xxx.xx.c a (scmze000.xxxx.xxx-xxx.xx. ca [xxx.xxx.19.84])
by bright11.vendor.ca (Symantec Messaging Gateway) with SMTP id 2E.93.31377.79364A35; Fri, 20 Jun 2014 12:38:48 -0400 (EDT)
Received: from mail.ourdomain.com ([xx.xx.243.3])
by scmze000.xxxx.xxx-xxx.xx.c a with ESMTP; 20 Jun 2014 16:38:43 +0000
Received: from Exch2.internal.ourdomain.c om
([fe80::44f3:3628:92d4:c7b 3]) by Exch2.internal.ourdomain.c om
([fe80::44f3:3628:92d4:c7b 3%10]) with mapi; Fri, 20 Jun 2014 12:38:42 -0400
X-AuditID: 0afc14a7-b7f038e00000514a- 1e-53a4639 e3542
X-SBRS: 5.1
X-IronPort-Anti-Spam-Filte red: true
X-IronPort-Anti-Spam-Resul t: AoQBADZjpFNAKPMDl2dsb2JhbA DKCQ8BAQEB AR4HPA
From: First Lastname <name@ourdomain.com>
To: "'name@vendor.ca'" <name@vendor.ca>
Date: Fri, 20 Jun 2014 12:38:41 -0400
Subject: FW: Pending MRA
Thread-Topic: Pending MRA
Thread-Index: Ac9VuHn5PLpfA0+YSv63OLIYf6 qOZgAAC3Jw AMidCYABVj zkAAFc19tw AcevQYABj9 FRUATCJ7jw ACsTzwAB+t Fz0A==
Accept-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA2VUfWwTdRju73 ptr7UHR9ut ry0oO4cZxm 6rzrgR/CDG aPQPTLp/RH Ec3dlW
+zF7LVkXTZYYxZWNLGMb5bbaDS YYnWx+Baco 0BmSMdlgAQ huLhTQfUCI miBxzuFdf+ 1s5b/n
nvd9n+d5f29TSmmY01oovj7EB/ 2cl1XryNNJ Y7Ut5uxzlM +fL6mcSbyt fBI9e/GTFv QC2qLb
WMt7PTv4YNnj23Tu3r1DmroL18 31iVFfI+rv NkeRlgKmAq bPiWqMC+HM 9EAaG5gLCI 4ME5i/
C37r/VGF8X1w+NMlDcbPwNHOYR Xufwv6ozdR FOkkPIrg54 5zpFxQM+th fOxausnEPA YnFz9E
MiaZdfDF4JxSxkZmI3wweGm5Z2 /7URLj1+CX 2K10IJp5BV ITJ9MYSUFv nepPh1MyZv jpaiIT
1ASps6OZZQpg7sqSCvcXwNTOAY T7PTC1WEdg zVUwsu8q2Y oKxRwpMadN zGkTpd2UzC 4EPben
1SKipI8AtAybMFwPA1+X4dEiaN +V0mBcAu90 xzV38jaIXV vKWLHQ3XNC g+UPIjj2q6 jGBTv8
XW/U0XkT8sez0H//xhwXQ5jF9K qvDsEILjs8 fRnWar4fOO pjSfPYeYcw 4ZaxkGFnaK pJh+Ohra
0/agx+UO2e2lbqdNcJa6nKVO7j Mk/ch1i6bW r1DXnsokYi jE6unGLX0O g4rbIUR8SV RFEWwB
/SUnUSu2B2ojbk5w1wTDXl5g76 Grq3odBvMy LYSFOo/TEw gLNeGgN4mK pQiXBz8+gy ykP+Dn
WRNtrZZ06Fou0sAHA1gmiawUyZ pp++YDDgPj 4kL86zxfxw ez1ScoigW6 Rw6wKsi7+P pXPd5Q
tswW0Sk5gyW38v8YBKVNokcpve R/VpahhTrO J3hcGYk19M uyRGGWzR8/ hZ6ymOkxeY 6RO9xh
/7K7ZS3tXUg4DHfnFPKns38iE2 iNxUgjhUJh 0Eu7+TyhjH mmPo8ekZ7e SMdlH73HH/ ov3moc
ryBD5uvPS3sR0l4HmvfLe4W4UO 5eEzJbmGXz Jy2NaFCx56 /OqoUSdKjP a+t+scyqOL FhfCw2
ThTdmPCvrGi1vjG37mDD5srnb3 /75u7dDXD9 WE3x6fOIOf Qg9cPNy9RL f269WLMp1h yN3FsR
7mriIt9NaTufbpsdUr6/ifj+XS ebautqKxqe oWaJSf/W5v sJa8PDR96z GW2+6EjbQy v1HSwp
uDn7A8qgwP0Lv4FAnHwFAAA=
X-MIMETrack: Itemize by SMTP Server on SMTA01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:50 PM,
Serialize by Router on SMTA01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:50 PM,
Itemize by SMTP Server on UTIL01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:50 PM,
Serialize by Router on UTIL01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:51 PM,
Itemize by SMTP Server on SMTA01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:53 PM,
Serialize by Router on SMTA01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:53 PM,
Itemize by SMTP Server on UTIL01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:53 PM,
Serialize by Router on UTIL01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:54 PM,
Itemize by SMTP Server on SMTA01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:56 PM,
Serialize by Router on SMTA01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:56 PM,
Itemize by SMTP Server on UTIL01/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:56 PM,
Serialize by Router on SMTA00/XX-XX/XX/CA(Release 8.5.3FP6|November 21, 2013) at
2014-06-20 12:38:57 PM
Message-ID: <OFCB8C422A.A76FC341-ON852 57CFD.005B 74BF-85257 CFD.005B74 D2@vendor. ca>
Content-Type: multipart/mixed;
boundary="_007_AAF472715C9 D3848ACB27 71FB023921 D7935488F0 FExch2in_"
Content-Language: en-US
We do not filter our outbound message and I have checked our spf records and reverse dns is all setup correctly. Is there anything we need to change on our Exchange server to get these messages to get through or is it an issue on the vendor's end as it looks like the messages are bouncing around within their internal email systems.
Thanks in advance for your help,
TheSonicOne
We have a couple of users who when sending to one of our vendors randomly keep getting the same errors for an undeliverable message:
Delivery has failed to these recipients or distribution lists:
name@vendor.ca
An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
The following organization rejected your message: xxx.xxx.19.86.
Diagnostic information for administrators:
Generating server: vendor.ca
name@vendor.ca
xxx.xxx.19.86 #<xxx.xxx.19.86 #5.0.0 X-Notes; Error transferring to xxx.xxx.19.86; Maximum hop count exceeded. Message probably in a routing loop.> #SMTP#
Original message headers:
Received: from smta01.vendor.ca ([10.252.40.136]) by
vendor.ca (Lotus Domino Release 8.5.3FP6) with ESMTP id
2014062012385660-283430 ; Fri, 20 Jun 2014 12:38:56 -0400
Received: from BRIGHT01.vendor.ca ([xx.xxx.20.167])
by smta01.vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385652-121329 ;
Fri, 20 Jun 2014 12:38:56 -0400
Received: from scmze000.xxxx.xxx-xxx.xx.c
by BRIGHT01.vendor.ca (Symantec Messaging Gateway) with SMTP id 52.99.20810.E9364A35; Fri, 20 Jun 2014 12:38:55 -0400 (EDT)
Received: from scmze999.xxxx.xxx-xxx.xx.c
by scmze000.xxxx.xxx-xxx.xx.c
Received: from inbound4.vendor.ca (HELO vendor.ca) ([xxx.xxx.93.80])
by scmze000.xxxx.xxx-xxx.xx.c
Received: from smta01.vendor.ca ([xx.xxx.40.136])
by vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385378-283427 ;
Fri, 20 Jun 2014 12:38:53 -0400
Received: from BRIGHT01.vendor.ca ([10.252.20.167])
by smta01.vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385374-121323 ;
Fri, 20 Jun 2014 12:38:53 -0400
Received: from scmze000.xxxx.xxx-xxx.xx.c
by BRIGHT01.vendor.ca (Symantec Messaging Gateway) with SMTP id D1.99.20810.B9364A35; Fri, 20 Jun 2014 12:38:52 -0400 (EDT)
Received: from scmze999.xxxx.xxx-xxx.xx.c
by scmze000.xxxx.xxx-xxx.xx.c
Received: from inbound4.vendor.ca (HELO util01.vendor.ca) ([xxx.xxx.93.80])
by scmze000.xxxx.xxx-xxx.xx.c
Received: from smta01.vendor.ca ([xx.xxx.40.136])
by util01.vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385088-283423 ;
Fri, 20 Jun 2014 12:38:50 -0400
Received: from bright11.vendor.ca ([xx.xxx.20.144])
by smta01.vendor.ca (Lotus Domino Release 8.5.3FP6)
with ESMTP id 2014062012385079-121314 ;
Fri, 20 Jun 2014 12:38:50 -0400
Received: from scmze000.xxxx.xxx-xxx.xx.c
by bright11.vendor.ca (Symantec Messaging Gateway) with SMTP id 2E.93.31377.79364A35; Fri, 20 Jun 2014 12:38:48 -0400 (EDT)
Received: from mail.ourdomain.com ([xx.xx.243.3])
by scmze000.xxxx.xxx-xxx.xx.c
Received: from Exch2.internal.ourdomain.c
([fe80::44f3:3628:92d4:c7b
([fe80::44f3:3628:92d4:c7b
X-AuditID: 0afc14a7-b7f038e00000514a-
X-SBRS: 5.1
X-IronPort-Anti-Spam-Filte
X-IronPort-Anti-Spam-Resul
From: First Lastname <name@ourdomain.com>
To: "'name@vendor.ca'" <name@vendor.ca>
Date: Fri, 20 Jun 2014 12:38:41 -0400
Subject: FW: Pending MRA
Thread-Topic: Pending MRA
Thread-Index: Ac9VuHn5PLpfA0+YSv63OLIYf6
Accept-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA2VUfWwTdRju73
+zF7LVkXTZYYxZWNLGMb5bbaDS
nvd9n+d5f29TSmmY01oovj7EB/
WMt7PTv4YNnj23Tu3r1DmroL18
C37r/VGF8X1w+NMlDcbPwNHOYR
MiaZdfDF4JxSxkZmI3wweGm5Z2
1ASps6OZZQpg7sqSCvcXwNTOAY
1SKipI8AtAybMFwPA1+X4dEiaN
XW/U0XkT8sez0H//xhwXQ5jF9K
0/agx+UO2e2lbqdNcJa6nKVO7j
/SUnUSu2B2ojbk5w1wTDXl5g76
WRNtrZZ06Fou0sAHA1gmiawUyZ
tswW0Sk5gyW38v8YBKVNokcpve
/7K7ZS3tXUg4DHfnFPKns38iE2
ryBD5uvPS3sR0l4HmvfLe4W4UO
ThTdmPCvrGi1vjG37mDD5srnb3
7mriIt9NaTufbpsdUr6/ifj+XS
uDn7A8qgwP0Lv4FAnHwFAAA=
X-MIMETrack: Itemize by SMTP Server on SMTA01/XX-XX/XX/CA(Release
2014-06-20 12:38:50 PM,
Serialize by Router on SMTA01/XX-XX/XX/CA(Release
2014-06-20 12:38:50 PM,
Itemize by SMTP Server on UTIL01/XX-XX/XX/CA(Release
2014-06-20 12:38:50 PM,
Serialize by Router on UTIL01/XX-XX/XX/CA(Release
2014-06-20 12:38:51 PM,
Itemize by SMTP Server on SMTA01/XX-XX/XX/CA(Release
2014-06-20 12:38:53 PM,
Serialize by Router on SMTA01/XX-XX/XX/CA(Release
2014-06-20 12:38:53 PM,
Itemize by SMTP Server on UTIL01/XX-XX/XX/CA(Release
2014-06-20 12:38:53 PM,
Serialize by Router on UTIL01/XX-XX/XX/CA(Release
2014-06-20 12:38:54 PM,
Itemize by SMTP Server on SMTA01/XX-XX/XX/CA(Release
2014-06-20 12:38:56 PM,
Serialize by Router on SMTA01/XX-XX/XX/CA(Release
2014-06-20 12:38:56 PM,
Itemize by SMTP Server on UTIL01/XX-XX/XX/CA(Release
2014-06-20 12:38:56 PM,
Serialize by Router on SMTA00/XX-XX/XX/CA(Release
2014-06-20 12:38:57 PM
Message-ID: <OFCB8C422A.A76FC341-ON852
Content-Type: multipart/mixed;
boundary="_007_AAF472715C9
Content-Language: en-US
We do not filter our outbound message and I have checked our spf records and reverse dns is all setup correctly. Is there anything we need to change on our Exchange server to get these messages to get through or is it an issue on the vendor's end as it looks like the messages are bouncing around within their internal email systems.
Thanks in advance for your help,
TheSonicOne
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER