Exchange Server 2007 - truncated e-mails
Hello,I have Exchange Server 2007 Standard Edition SP1, Update Rollup 2.The problem is that we keep receiving truncated emails (on Microsoft Office Outlook 2003 and Outlook Web Access), the body begins normally, text is shown and then I get something like the following lines for example:------_=extPart_001_01C8D5C7.24EA1386Content-Type: text/html; charset=s-ascii"Content-Transfer-Encoding: quoted-printable<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html xmlns: o="urn: schemas-microsoft-com: office: office" xmlns: st1="urn: schemas-microsoft-com: office: smarttags"><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><title>Message</title><meta content="MSHTML 6.00.2900.3020" name="GENERATOR"></head><body><div> </div><div></div><div class="OutlookMessageHeader" lang="en-us" dir="ltr" align="left"><font face="Tahoma" size="2">-----Original Message-----<br><b>From:</b> John <br><b>Sent:</b> 18 June 2008 18:08<br><b>To:</b>Michael<br><b>Subject:</b> FW: message<br><br></font></div>or just that Next Part Reference------_=extPart_002_01C8D525.3E7DB44D-- For the first example, Internet Headers look like this:Content-Class: urn:content-classes:messageMIME-Version: 1.0Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8D5C7.24EA1386"X-MimeOLE: Produced By Microsoft Exchange V6.5Subject: FW: messageDate: Tue, 24 Jun 2008 09:54:24 +0300Message-ID: <31970A14F40017429C7F102CC309B98007B436F8@hq-exch2k3.intranet.domain.ro>X-MS-Has-Attach:X-MS-TNEF-Correlator:I have also checked the Internet Headers for some other truncated e-mails and most of them look like this:Received: from dc.domain.com ([192.168.200.100]) by dc.domain.com([192.168.200.100]) with mapi; Mon, 23 Jun 2008 14:38:35 +0300Content-Type: application/ms-tnef; name="winmail.dat"Content-Transfer-Encoding: binaryFrom: John <john@domain.com>To: Michael <michael@domain.com>Date: Mon, 23 Jun 2008 14:38:34 +0300Subject: FW: Thread-Index: AcjSl6OQt2qIR5KkREGdnFQxFDcSjwAAAZEAAAb0+kAAkUxoAAALOjmAMessage-ID: <28CE590F222B38469FCB7AE16BFC3A2809E381B3BF@dc.rem.local>Accept-Language: en-USContent-Language: en-USX-MS-Has-Attach: yesX-MS-Exchange-Organization-SCL: -1X-MS-TNEF-Correlator: <28CE590F222B38469FCB7AE16BFC3A2809E381B3BF@dc.domain.com>MIME-Version: 1.0Based on this, I have found on microsoft.com only one tnef-related issuehttp://support.microsoft.com/kb/944153/I tried those settings, but it didn't work.I have also seen on some forums that Microsoft fixed this issue by making a change to the IIS metabase, but no further details on how they did it exactly. If anybody knows, please reply.Any other ideas?Thank you!
June 24th, 2008 11:42am
I have read on microsoft.com the following:Messages that are composed by MIME clients as a multipart/mixed MIME message without a "name" parameter for the "content-type" or an optional "filename" parameter for the "content-disposition" header may not be rendered correctly when received by Exchange.I have some of my headers looking like this:MIME-Version: 1.0Content-Type: multipart/mixed; boundary="----=_NextPart_000_0014_01C8D6C0.30DDDB50"X-Mailer: Microsoft Office Outlook 12.0or MIME-Version: 1.0Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01C8D6AF.74CE1886"X-MS-Has-Attach: yesX-MS-TNEF-Correlator:Thread-Topic: for sale Content-Class: urn:content-classes:messageThread-Index: AcjWr3PnEmJHOWAOQNCpuHnvsQrxOA==X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0Could this be the problem and, if so, what is the solution?Thank you!
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2008 12:58pm
Hi,
Firstly, please help to clarify below questions so that we can troubleshoot it more effectively.
1) When did the issue begin? ( As I remembered that this issue once be fixed in the Roll up 1 update for SP1, see KB941851.) Whether it may reoccur again after installing roll up 2?
2) This issue also may cause by some third party Eventsink (such as third party disclaimer tool or anti-spam agents). If you have related third party disclaimer services, Would you like to stop them temporary to narrow down the cause?
3) Does these messages coming from internet or just in internal? If they are coming from internet, Whether it only occur at certain special email domain?
According to my experience, to troubleshoot the issue, we need verify whether the original message has been corrupted already at the sender domain or it corrupted during transporting in yours Exchange organization. Based on it, I suggest you enable Pipeline tracing log with EMS on the transport server.
Code SnippetSet-transportserver servername" PipelineTracingEnabled:$True PipelineTracingSenderAddress senders@address.com
Note: Set the sender address to the smtp address of the users sending the message
After enabling the pipeline log, please try reproducing the issue and collect the log files to my email address
The log file should be in below path:
C:\program Files\Microsoft\Exchange Server\TransportRoles\Logs\PipelineTracing Directory
Here is the related articles
=====================
How to Enable Pipeline Tracing
Using Pipeline Tracing to Diagnose Transport Agent Problems
if you have anything unclear, please let me know.
Regards,
Jason
June 25th, 2008 3:01pm
1) When did the issue begin? ( As I remembered that this issue once be fixed in the Roll up 1 update for SP1, see KB941851.) Whether it may reoccur again after installing roll up 2?The issue was from the beginning and it continued even after installing Update Rollup 2.2) This issue also may cause by some third party Eventsink (such as third partydisclaimer tool or anti-spam agents). If you have related third partydisclaimer services, Would you like to stop them temporary to narrowdown the cause?I have one antivirus for Exchange Server 2007, but I have disabled it and it did not change the problem.I have ISA Server 2006 in my organization, I even uninstalled it yesterday, to be sure I did't have any rule (or setting) that messed up my emails, but the behaviour was the same.3) Do these messages coming from internet or just in internal? If they are coming from internet, Whether it only occur at certain special email domain?They arrive from different domains (not all of them arrive 'scrambled'), this especially happens when the message contains inline attachments, different formatting styles for the text, images, signatures, etc. It happens on direct e-mails, on replies, on forwards.I have asked one of our partners to send an email with CC to one of my personal address and there it arrives correctly, so the issue can not be at the sender.I have enabled Pipeline Tracing, I have sent you an email.Thank you for your help!
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2008 10:57am
Hi Elena,
Thank you for your reply.
I am glad that you tried the suggestions. At this time, since I have got your pipeline tracing log, you can disable the pipeline tracing. I will do my best to check the possible fault phase in the mail flow.
To turn Pipelinetracing off:
===================
Code Snippet
set-transportserver -identity <servername> -pipelinetracingenabled $false
-pipelinetracingsenderaddress "senderSMTPaddress"
Regards,
Jason
June 26th, 2008 11:56am
Hi Elena,
Thank you for providing the pipeline tracing logs.
After checking the logs, I find out that this message flow is fine at edge server, the fault occurs while delivering message from edge server to hub server. Please open the PipelineTracingHUB attachment you sent me, we can see a source agent named BD_Exchange2007_Agent in SmtpReceive0002.eml header, which should be the culprit. I couldnt find any information about the agent in our internal articles, so it may be a third party agent I think, but it still need your investigate on your side.
I also suggest you double check this agent in the in SmtpReceive0002.eml header. To check this header, you can open it with notepad.
X-CreatedBy: MessageSnapshot-Begin injected headers
X-MessageSnapshot-UTC-Time: 2008-06-26T07:27:50.406Z
X-MessageSnapshot-Protocol-Id: 08CAA3F2C495AA17;2008-06-26T07:27:49.687Z;1
X-MessageSnapshot-Source: OnEndOfData,BD_Exchange2007_Agent
X-Sender: elena.opincaru@gmail.com
X-Receiver: elena.henta@rem.local
For more information about diagnosing with Pipeline Tracing logs, I highly recommend you read below article:
http://technet.microsoft.com/en-us/library/bb125198(EXCHG.80).aspx
Meanwhile, I also have tested to send this message through our companys Exchange servers and also test in my local lab(one server: Exchange 2007 SP1 rollup 2), both results are fine, this message arrives me perfect.
Regards,
Jason
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2008 2:26pm
Hello,I gave up on that antivirus solution I had for Exchange. Initially I stopped those services, ran some tests and I noticed the problems were the same, now I have disabled the services and my emails are finally looking right.Thank you!
June 26th, 2008 3:35pm
Im glad to hear my suggestion helps. Pipeline tracing is a good for diagnosing transport issue. I hope other folks see these thread may familiar with it , do not forget to immediately turn it off after getting the logs.
Regards,
Jason
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2008 9:10am
This topic is archived. No further replies will be accepted.
Other recent topics
