XML in body converted to Attachment in Exchange 2010

Hi - I've just migrated a mailbox from Exchange 2003 to Exchange 2010 and emails which contain XML in the body of the message are saved as XML attachments in exchange 2010.

Is there a way to turn this off or change the default group policy?

We receive a large number of emails from difference sources so its not possible to make a change to the emails.
Iron-MikeAsked:
Who is Participating?
 
jrhelgesonCommented:
The answer is going to be in creating a proper transport rule.  You'll need to tweak the rules and settings, but this should get you started in the right direction - if not solve it outright.

Create Transport Rule as follows:
MANAGING MIME TYPE
1) Within Exchange System Manager, select | Organization Configuration | Hub Transport | Transport Rules Tab
2) Right-click and select "New Transport Rule"
3) Select the conditions “from users that are inside or outside the organization” and ‘when the message header contains specific words”.
4) Select the action '”set header with value”.
5) Create the new transport rule.

To verify if the transport rule is working, you have to enable pipeline tracking on the HUB transport server. Now you can send a new message with xml to see if the transport rule changes the Content-Type.
0
 
Arjun VyavahareTechnical ConsultantCommented:
This same is happening from Exchange 2010 OWA?

Regards,
Arjun
0
 
Iron-MikeAuthor Commented:
We don't use OWA as there is an application which monitors the email box and strips the XML contained within the body of an email and saves it to a file.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
jrhelgesonCommented:
Did you just answer your own question there?  What application are you referring to?
0
 
Iron-MikeAuthor Commented:
No I was responding to the previous post. I just need to know how to allow exchange 2010 to accept emails with XML in the body as it is currently saving stripping out the XML in the body and saving it as an attachment.
0
 
jrhelgesonCommented:
And he asked if you were to look at an email using OWA, does it show the XML as being stripped out?

We're trying to figure out if it is being stripped out by the transport, the server, or the client.
0
 
Iron-MikeAuthor Commented:
Sorry, we are looking at the email from outlook 2003 client. But it worked when the mailbox was stored on the Exchange 2003 server
0
 
jrhelgesonCommented:
Okay, so lets keep rolling here with the information...  You used to have Exchange 2003, now you have exchange 2010.  Clients are using Outlook 2003.  XML files used to come through on Exchange 2003 no problem. With exchange 2010, those xml files are being converted to an attachment to the message.

Now: What are the origins of these xml files?  When those files are sent via email, how does the message look using OWA.  Is it already converted to an attachment there?  When the message is sent, is the sent message show as an attachment or in the body of the email?
0
 
allen_richCommented:
0
 
Iron-MikeAuthor Commented:
Thanks for your posts. In response to jrhelgeson question, it appears as an attachment in web mail as well.

We have hundreds or applications sending in this format so any change at the senders end will be very difficult to make.  So the email is sent with the xml in the body, it then reaches the exchange 2010 server and the body message is blank and the XML saved as an attachment in web mail and in the outlook client we use to monitor the email.

It work perfectly in exchange 2003 so must be a security update that surely could be changed somewhere in the configuration?
0
 
jrhelgesonCommented:
Are these messages coming in from internal IP addresses, or do they come from devices across the internet?
0
 
Iron-MikeAuthor Commented:
They are coming in from devices across the internet
0
 
Iron-MikeAuthor Commented:
Many thanks, I'm fairly new to exchange 2010....how do you enable pipeline tracking and what's it for?
0
 
jrhelgesonCommented:
Here is a link that does a pretty good job outlining "Pipeline Tracing" it and its uses:
http://howexchangeworks.com/2011/06/troubleshooting-transport-using.html 

Note: I incorrectly said "Tracking" in my previous comment - the proper word is "Tracing"

Also: When you create the rule, you select the conditions “from users that are inside or outside the organization” - but the rule will show "inside the organization".  Click on the text in the rule "inside the organization" and you'll be able to choose "outside the organization" from the drop-down menu.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.