Hi All My users are receiving emails from a company that are coming through in HTML with the body of the email stripped. The sender and subject line are intact but the the body is blank, no clues as to why it was removed. Exchange 2007 and happens across outlook 2003; 2007 & 2010. If I view the email via OWA the body is still blank. If the mail is sent to my personal acc it shows up as expected and if I forward that mail through my exchange servers to my office mailbox the body comes through intact? Any ideas here? Thanks

Do you have any perimeter content control features in place?

On Wed, 13 Oct 2010 00:24:07 +0000, remora wrote: >My users are receiving emails from a company that are coming through in HTML with the body of the email stripped. The sender and subject line are intact but the the body is blank, no clues as to why it was removed. > >Exchange 2007 and happens across outlook 2003; 2007 & 2010. If I view the email via OWA the body is still blank. If the mail is sent to my personal acc it shows up as expected and if I forward that mail through my exchange servers to my office mailbox the body comes through intact? > >Any ideas here? You need to get a copy of the e-mail as it arrives and examine the message. Not all e-mail is created correctly. It's possible that there are mutiple HTML body parts in the message and the first one is empty. You can use pipeline tracing to get a copy of the original e-mail and the e-mail as it passes through the various stages in the Exchange transport ("message anapshot files"). http://technet.microsoft.com/en-us/library/bb125198(EXCHG.80).aspx --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, Thanks for that, have enabled pipeline tracing and got them to resend the email. Am still going through the logs but have come across this on the Edge Server X-MS-Exchange-Organization-PRD: elders.com.au X-MS-Exchange-Organization-SenderIdResult: Fail Received-SPF: Fail (EdgeSVR01.domain.com.au: domain of no-reply@elders.com.au does not designate 203.100.58.112 as permitted sender) receiver=EdgeSVR01.domain.com.au; client-ip=203.100.58.112; helo=sy1-mta-81b.au.emailfiltering.com; X-MS-Exchange-Organization-OriginalSize: 4322 I'm a bit stumped - could this be my problem?

Hi TJM01 No nothing that would block it, the email is beiing sent to multiple users across the organisation with the same results. We run Forefront for Exchange on the exchange servers. Cheers T

On Wed, 13 Oct 2010 05:04:05 +0000, remora wrote: >Thanks for that, have enabled pipeline tracing and got them to resend the email. Am still going through the logs but have come across this on the Edge Server You can, if the message isn't overly large, use "Message Lint" to see if there are any gross problems with the message. It'll pick up lots of odd things with MIME messages: http://www.apps.ietf.org/content/message-lint >X-MS-Exchange-Organization-PRD: elders.com.au >X-MS-Exchange-Organization-SenderIdResult: Fail >Received-SPF: Fail (EdgeSVR01.domain.com.au: domain of > no-reply@elders.com.au does not designate 203.100.58.112 as permitted > sender) receiver=EdgeSVR01.domain.com.au; > client-ip=203.100.58.112; helo=sy1-mta-81b.au.emailfiltering.com; >X-MS-Exchange-Organization-OriginalSize: 4322 > > > > > >I'm a bit stumped - could this be my problem? I don't think so. If the message was not delivered it might be a problem. But I don't know what you're doing with SPF failures. If you just accept them then the results are only useful in the determinstion of whether the message is spam or not. In any case, the 203.100.58.112 IP address has a PTR that looks like they're sending their mail through a 3rd-party server: sy1-mta-81b.au.emailfiltering.com If that's the case they need to add them to their SPF record. Their SPF data is: "v=spf1 ip4:203.30.41.0/24 ip4:203.27.144.90 ip4:203.161.127.131 include:mailcontrol.com include:run.com.au include:amnet.net.au -all" The other SPF records for the "include" are: mailcontrol.com text = "v=spf1 a:cluster-abdefghjkm.mailcontrol.com a:cluster-y.mailcontrol.com a:cluster-z.mailcontrol.com ip4:85.115.32.0/19 ip4:86.111.216.0/21 ip4:116.50.56.0/21 ip4:208.87.232.0/21 ~all" run.com.au text = "v=spf1 mx ptr:mail.run.com.au ip4:144.140.160.85 -all" amnet.net.au text = "v=spf1 ip4:203.161.124.48/29 ip4:203.161.126.28 ip4:203.161.126.29 ~all" --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Have you tried to open the generated .eml files via outlook? If not, please open the one that named as “Original.eml”. It’s the original copy of the incoming mail that hasn’t gone through any transport agent on the exchange serverJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Yes, Open the original email and look at the mime formatting: 1. Is the required MIME 1.0 header there? 2. Is the MIME type correct for the message? 3. Are the MIME message body parts properly spcified? I seem to remember a problem with improperly formed MIME messages coming from certain 3rd party email servers. J

Any update?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com