Quantcast
Channel: Exchange Server 2013 - Mail Flow and Secure Messaging forum
Viewing all articles
Browse latest Browse all 3660

Exchange 2013 convert MIME Multipart/Mixed Messages to text/plain

$
0
0

Hi Exchange Team,

We are in Transition from Ex2010 SP3 RU6 to Ex2013 CU5 by One of our Customer. The Customer have a ERP System that sends Multipart/Mixed Messages. After we testing the SMTP Transition (change the SMTP Server in the ERP System from Ex2010 to Ex2013) we noted that the Messages are Convertet to Text/plain. We are Sniffing the Network Communication between the ERP System and the Ex2013 Servers, it seems ok.  We Start Pipline Tracing on the Ex2013 Server and find out that the Message are Convertet from SmtpReceive0006.eml to  SmtpReceive0007.eml with the Source of „X-MessageSnapshot-Source: OnEndOfData,Inbound Trust Agent“.

Is there a protocol change in the MIME Communication for the Ex2013 Server? What can we do that the Message are not Convertet to „Text/plain“?

Kind Regards

Steven

#Netmon communication

MIME-Version: 1.0

Content-Transfer-Encoding: 8bit

Content-Type: multipart/mixed; boundary="7D81B75CCC90D2974F7A1CBD"

Date: 20.08.2014 14:43:20

From: medfolio@domain.com

To: ext.spare@domain.com

Subject: =?iso-8859-15?Q?Mail-Test =C4=D6=DC=E4=F6=FC?=

Reply-To: medfolio@domain.com

--7D81B75CCC90D2974F7A1CBD

Content-Type: text/html; charset="iso-8859-15"

(Text/Plain oder Text/HTML)

--7D81B75CCC90D2974F7A1CBD--

#Pipline Tracing

X-CreatedBy: MessageSnapshot-Begin injected headers

X-MessageSnapshot-UTC-Time: 2014-08-20T14:43:20.991Z

X-MessageSnapshot-Protocol-Id: 08D18A0283150E09;2014-08-20T14:43:20.757Z;2

X-MessageSnapshot-Source: OnEndOfData

X-Sender: medfolio@domain.com

X-Receiver: tobias.joerger@domain.com

X-EndOfInjectedXHeaders: MessageSnapshot-End injected headers

Received: from Exchange2013-SRV01 (172.18.16.121) by

Exchange2013-SRV02 (172.18.16.122) with Microsoft SMTP Server (TLS) id

15.0.913.22; Wed, 20 Aug 2014 14:43:20 +0200

Received: from mail.ex2013.intra (172.18.16.251) by Exchange2013-SRV01

(172.18.16.123) with Microsoft SMTP Server id 15.0.913.22 via Frontend

Transport; Wed, 20 Aug 2014 14:43:20 +0200

MIME-Version: 1.0

Content-Transfer-Encoding: 8bit

Content-Type: text/plain

Date: Wed, 20 Aug 2014 14:43:20 +0000

From: <medfolio@domain.com>

To: <tobias.joerger@domain.com>

Subject: =?iso-8859-15?Q?Mutation?=

Reply-To: <medfolio@domain.com>

Message-ID: <5d883ac8-0dea-4736-9f90-49985494f9a2@Exchange2013-SRV01>

Return-Path: medfolio@domain.com

X-MS-Exchange-Organization-OriginalArrivalTime: 20 Aug 2014 14:43:20.0341

(UTC)

X-MS-Exchange-Forest-ArrivalHubServer: Exchange2013-SRV01

X-MS-Exchange-Organization-OriginalClientIPAddress: 172.18.16.251

X-MS-Exchange-Organization-OriginalServerIPAddress: 172.18.16.123

X-MS-Exchange-Organization-Cross-Premises-Headers-Processed: Exchange2013-SRV01

X-MS-Exchange-Organization-MessageLatencyInProgress: LSRV=Exchange2013-SRV01:TOTAL=0;2014-08-20T14:43:20.034Z

X-MS-Exchange-Organization-AuthSource: Exchange2013-SRV01

X-MS-Exchange-Organization-AuthAs: Anonymous

X-MS-Exchange-Organization-PRD: domain.com

X-MS-Exchange-Organization-SenderIdResult: None

Received-SPF: None (Exchange2013-SRV02: medfolio@domain.com does not

designate permitted sender hosts)

X-MS-Exchange-Organization-Network-Message-Id:

d51d83ab-a49a-4e2f-5476-08d18a69d83b

(Text/HTML)

-------7D81B75CCC90D2974F7A1CBD--


Viewing all articles
Browse latest Browse all 3660

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>