DegoJay
asked on
5.6.1 smtp;554 5.6.1 "Body type not supported by Remote Host" when sending from Exchage 2010
We have a mixed envirnment with Exchange 2010 and 2003. When a user sends a specific (auto-forwarded message) from an Exchange 2010 mbx server in one of our remote office to an outside address the message bounces at our 2003 bridgehead server. An internal users is also copied on this message and he gets it no problem.
If I just open the message and forward it the message goes through no problem. Below is the NDR that the sender receives.
Delivery has failed to these recipients or groups:
recipient@externaldomain.c om
The e-mail system had a problem processing this message. Exchange won't try to deliver this message again.
Diagnostic information for administrators:
Generating server: 2003bridgehead.domain.COM
recipient@externaldomain.c om
#< #5.6.1 smtp;554 5.6.1 Body type not supported by Remote Host> #SMTP#
Original message headers:
Received: from EXCHANGE2010.domain.com ([10.1.1.53]) by 2003bridgehead.domain.COM
with Microsoft SMTPSVC(6.0.3790.4675); Fri, 6 Jan 2012 01:39:27 -0500
Received: from users2010MBX.HDP.com (10.6.1.44) by EXCHANGE2010.domain.com (10.1.1.53) with Microsoft SMTP Server (TLS) id 14.1.289.8; Fri, 6 Jan 2012
01:39:27 -0500
Received: from users2010MBX.HDP.com ([fe80::940e:f6b5:c876:f2a f%13]) by users2010MBX.HDP.com ([fe80::940e:f6b5:c876:f2a f%13]) with Microsoft SMTP Server id 14.01.0355.002; Fri, 6 Jan 2012 01:39:26 -0500
Content-Transfer-Encoding: binary
From: "InternalSender" <user@domain.com>
To: "internalrecipiant" <user2@domain.com>, <recipient@externaldomain. com>
Subject: FW: [Patent] Patently-O updates
Thread-Topic: [Patent] Patently-O updates
Thread-Index: AQHMzD3vS9vJrbFqGkKBxpIunI UEZw==
References: <MAIL01hpKVUXu6okEiJ00008c 10@mail01. feedblitz. com>
In-Reply-To: <MAIL01hpKVUXu6okEiJ00008c 10@mail01. feedblitz. com>
X-MS-Has-Attach: yes
X-MS-Exchange-Inbox-Rules- Loop:
X-MS-TNEF-Correlator: 2f66cb22-7191-48b1-a049-ea 63d7a05cf2
MIME-Version: 1.0
Date: Fri, 6 Jan 2012 01:39:26 -0500
Message-ID: <450da630a52c4286b097fd934 b41ab12@DC -MBX1.HDP. com>
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Type: multipart/mixed;
boundary="----=_NextPart_0 00_9587_01 CCCC3D.EFF D2D84"
Return-Path: <user@domain.com>
X-OriginalArrivalTime: 06 Jan 2012 06:39:27.0769 (UTC) FILETIME=[EFF39090:01CCCC3 D]
If I just open the message and forward it the message goes through no problem. Below is the NDR that the sender receives.
Delivery has failed to these recipients or groups:
recipient@externaldomain.c
The e-mail system had a problem processing this message. Exchange won't try to deliver this message again.
Diagnostic information for administrators:
Generating server: 2003bridgehead.domain.COM
recipient@externaldomain.c
#< #5.6.1 smtp;554 5.6.1 Body type not supported by Remote Host> #SMTP#
Original message headers:
Received: from EXCHANGE2010.domain.com ([10.1.1.53]) by 2003bridgehead.domain.COM
with Microsoft SMTPSVC(6.0.3790.4675); Fri, 6 Jan 2012 01:39:27 -0500
Received: from users2010MBX.HDP.com (10.6.1.44) by EXCHANGE2010.domain.com (10.1.1.53) with Microsoft SMTP Server (TLS) id 14.1.289.8; Fri, 6 Jan 2012
01:39:27 -0500
Received: from users2010MBX.HDP.com ([fe80::940e:f6b5:c876:f2a
Content-Transfer-Encoding:
From: "InternalSender" <user@domain.com>
To: "internalrecipiant" <user2@domain.com>, <recipient@externaldomain.
Subject: FW: [Patent] Patently-O updates
Thread-Topic: [Patent] Patently-O updates
Thread-Index: AQHMzD3vS9vJrbFqGkKBxpIunI
References: <MAIL01hpKVUXu6okEiJ00008c
In-Reply-To: <MAIL01hpKVUXu6okEiJ00008c
X-MS-Has-Attach: yes
X-MS-Exchange-Inbox-Rules-
X-MS-TNEF-Correlator: 2f66cb22-7191-48b1-a049-ea
MIME-Version: 1.0
Date: Fri, 6 Jan 2012 01:39:26 -0500
Message-ID: <450da630a52c4286b097fd934
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Type: multipart/mixed;
boundary="----=_NextPart_0
Return-Path: <user@domain.com>
X-OriginalArrivalTime: 06 Jan 2012 06:39:27.0769 (UTC) FILETIME=[EFF39090:01CCCC3
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.