Hi all, Here’s a quick description of my customer’s network… Outside the network: eMail webhost that uses web squirrel mail. Inside the network: Microsoft Small Business Server 2008 sp1 with Exchange 2007 (V8.1 build 240.6) The Exchange server has connectors that gets eMail from the outside webhost. Outlook 2003 clients Various Smart Phones to access Exchange eMail On Aug 20^th, my customer started receiving eMails from two different domains, let’s say @client1.com and @client2.com, in the old MIME Text format, about 90% of the time, from any user from either client domain to any user in my customer’s eMail domain. It does not matter if the message is short, long, attachment, or no attachment. Any other client eMail domain is fine (so far)… If we bypass the Exchange Server, and directly access the webhost with squirrel mail, everything is fine. If we access the Exchange Server from Outlook or any Smart Phone, about 90% of the messages are in the old MIME text format from @client1.com and @client2.com. The eMail Antivirus scanning happens on the workstation with Outlook client. We’ve turned it off, but still have the problem. Client’s Outlook is set for HTML format at both ends, my customer, and their client. I’ve rebooted the file server and ran OS updates several times after Aug 20^th, but the problem still persists. The eMail has been working fine for quite some time, before this issue started on Aug 20^th. There has been no manual changes to Windows Server, or Exchange Server prior to Aug 20^th. I can’t find anything in the event logs from Aug 15^th – Aug 20^th that’s noteworthy to mention. There were no OS updates ran for those days Example of eMail: (User and Server names have been changed) Return-path: < USER1@CLIENT1.COM > Envelope-to: USER@MY-CUSTOMER.COM Delivery-date: Thu, 26 Aug 2010 14:42:36 -0500 Received: from mail by D.E.COM with spam-scanned (Exim 4.69) (envelope-from < USER1@CLIENT1.COM >) id 1OoiLM-0000df-6a for USER@MY-CUSTOMER.COM; Thu, 26 Aug 2010 14:42:36 -0500 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on A.B.com X-Spam-Level: X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,EXTRA_MPART_TYPE, HTML_MESSAGE autolearn=no version=3.2.5 Received: from A.B.COM ([1.1.1.1] helo=C.D.com) by F.G.COM with esmtps (SSLv3:DES-CBC3-SHA:168) (Exim 4.69) (envelope-from < USER1@CLIENT1.COM >) id 1OoiLL-0000dc-RG for USER@MY-CUSTOMER.COM; Thu, 26 Aug 2010 14:42:36 -0500 X-Note-AR-ScanTimeLocal: 8/26/2010 2:42:32 PM X-Policy: GLOBAL – CLIENT1.COM X-Primary: USER1@CLIENT1.COM X-Note: This Email was scanned by AppRiver SecureTide … … What I -think- is happening is something is in the eMail from those two clients that Exchange can't process so that the eMail recipient sees the message not in HTML, but in MIME...??? Any assistance would be greatly appreciated!

On Fri, 3 Sep 2010 19:22:33 +0000, Another Rob Hawkins wrote: >On Aug 20^th, my customer started receiving eMails from two different domains, let?s say @client1.com and @client2.com, in the old MIME Text format, about 90% of the time, from any user from either client domain to any user in my customer?s eMail domain. It does not matter if the message is short, long, attachment, or no attachment. Any other client eMail domain is fine (so far)? What does "old MIME Text format" mean? >Example of eMail: (User and Server names have been changed) >Return-path: < USER1@CLIENT1.COM > >Envelope-to: USER@MY-CUSTOMER.COM >Delivery-date: Thu, 26 Aug 2010 14:42:36 -0500 >Received: from mail by D.E.COM with spam-scanned (Exim 4.69) > (envelope-from < USER1@CLIENT1.COM >) > id 1OoiLM-0000df-6a > for USER@MY-CUSTOMER.COM; Thu, 26 Aug 2010 14:42:36 -0500 >X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on > A.B.com >X-Spam-Level: >X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,EXTRA_MPART_TYPE, > HTML_MESSAGE autolearn=no version=3.2.5 >Received: from A.B.COM ([1.1.1.1] helo=C.D.com) > by F.G.COM with esmtps (SSLv3:DES-CBC3-SHA:168) > (Exim 4.69) > (envelope-from < USER1@CLIENT1.COM >) > id 1OoiLL-0000dc-RG > for USER@MY-CUSTOMER.COM; Thu, 26 Aug 2010 14:42:36 -0500 >X-Note-AR-ScanTimeLocal: 8/26/2010 2:42:32 PM >X-Policy: GLOBAL ? CLIENT1.COM >X-Primary: USER1@CLIENT1.COM >X-Note: This Email was scanned by AppRiver SecureTide If the message was SENT using MIME (which it probably was), and the headers above represent what was received, then something's removed important information from the message headers. Where the "MIME-Version: 1.0"? Where's the header 'Content-Type: someformat/somethingelse; boundary="blahblahblah"'? >What I -think- is happening is something is in the eMail from those two clients that Exchange can't process so that the eMail recipient sees the message not in HTML, but in MIME...??? Any assistance would be greatly appreciated! I don't understand the "in MIME" part. Do you mean the message, as viewed with an e-mail clinet, shows the MIME headers and the message in base64 encoded format? Without the missing message headers the e-mail isn't being processed as it should be, it's simply being treated as if the message body contains only text and not MIME body parts. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks for your reply Rich, The eMail that my customer receives from their client contains the header info, and the message body in html, and an attachment in what we used to call back in the mid 90's as MIME format. Back in the 90's when file attachments were sent in eMail, they were sent in this MIME format and had to be reassembled by the recipient. Sorry for not being clear and the confusion. I didn't include the whole eMail before due to length. Please keep in mind that all other eMails are received fine except from two of my customer's clients. The message as viewed with Outlook 2003, and with a smart phone eMail client shows the headers, the body message in html, and the file attachment in base64 encoded format. The following is an eMail that my customer received from their client is exactly as you see, except with names and IP's changed: Err, ok... so I pasted the whole eMail >>here<<... But after I clicked on the Submit button, a window poped up with a yellow triangle and with a '!' in the middle. In the window was the headder info, html body message and the base64 encoded attachment, and no other error message. Is there a way I can show you the message? Any assistance is greatly appreciated! Thanks - Rob

On Sat, 4 Sep 2010 20:14:37 +0000, Another Rob Hawkins wrote: > > >Thanks for your reply Rich, > >The eMail that my customer receives from their client contains the header info, and the message body in html, and an attachment in what we used to call back in the mid 90's as MIME format. I'm old enough to remember. :-) >Back in the 90's when file attachments were sent in eMail, they were sent in this MIME format and had to be reassembled by the recipient. Back then there was more UUENCODE than MIME. >Sorry for not being clear and the confusion. I didn't include the whole eMail before due to length. Please keep in mind that all other eMails are received fine except from two of my customer's clients. The message as viewed with Outlook 2003, and with a smart phone eMail client shows the headers, the body message in html, and the file attachment in base64 encoded format. The following is an eMail that my customer received from their client is exactly as you see, except with names and IP's changed: If you're seeing the RFC822 message headers in the message body, that's usually the result of an empty line in the message headers where there shouldn't be one. The empty line marks the transition from the message headers to the message body. >Err, ok... so I pasted the whole eMail >>here<<... But after I clicked on the Submit button, a window poped up with a yellow triangle and with a '!' in the middle. In the window was the headder info, html body message and the base64 encoded attachment, and no other error message. Is there a way I can show you the message? > >Any assistance is greatly appreciated! Thanks - Rob Before you post the entire message, just grab the headers -- the stuff from the top of the message down to the 1st empty line. Since you say that you see the "MIME-Version: 1.0" header somewhere in the message I'm going to guess that you see it AFTER the empty line. That would mean the e-mail cliet treats is as part of the message body. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, Here's the eMail all the way down to the first line of the file attachment. Hopefully this will go through. Thanks for your help. -Rob Return-path: <User1@client1.com> Envelope-to: Customer@CustomersDomain.com Delivery-date: Thu, 26 Aug 2010 14:42:36 -0500 Received: from mail by apollo.trexservers.com with spam-scanned (Exim 4.69) (envelope-from <User1@client1.com>) id 1OoiLM-0000df-6a for Customer@CustomersDomain.com; Thu, 26 Aug 2010 14:42:36 -0500 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on apollo.trexservers.com X-Spam-Level: X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,EXTRA_MPART_TYPE, HTML_MESSAGE autolearn=no version=3.2.5 Received: from server518d.Client1.com ([1.1.1.1] helo=server518.Client1.com) by apollo.trexservers.com with esmtps (SSLv3:DES-CBC3-SHA:168) (Exim 4.69) (envelope-from <User1@client1.com>) id 1OoiLL-0000dc-RG for Customer@CustomersDomain.com; Thu, 26 Aug 2010 14:42:36 -0500 X-Note-AR-ScanTimeLocal: 8/26/2010 2:42:32 PM X-Policy: GLOBAL - Client1.com X-Primary: User1@client1.com X-Note: This Email was scanned by Client1 SecureTide X-ALLOW: @Client1.com ALLOWED X-Virus-Scan: V- X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES X-Note-Sending-IP: 1.1.1.1 X-Note-Reverse-DNS: X-Note-WHTLIST: User1@client1.com X-Note: User Rule Hits: X-Note: Global Rule Hits: G202 G203 G204 G205 G209 G210 G221 G309 X-Note: Encrypt Rule Hits: X-Note: Mail Class: ALLOWEDSENDER X-Note: Headers Injected Received: from [2.2.2.2] (HELO mail.Client1.com) by server518.Client1.com (CommuniGate Pro SMTP 5.3.7) with ESMTP id 147452247 for Customer@CustomersDomain.com; Thu, 26 Aug 2010 14:42:32 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/related; boundary="----_=_NextPart_001_01CB4556.D2EE6944"; type="multipart/alternative" Subject: RE: Test email Date: Thu, 26 Aug 2010 14:42:31 -0500 Message-ID: <CF5FF3A1A573DC49BF767677837D66E0018D1317@sckcmsg01.Client1KC.com> In-Reply-To: <48378CC92868D245993CE9C066A77E3A028FE54FC9ED@SBS02.CustomersDomain.local> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Test email Thread-Index: ActFVk1o64rt1rClQnCpfHA8+gBiyAAACTaQAAAL7+AAAAiWEA== References: <CF5FF3A1A573DC49BF767677837D66E0018D1311@sckcmsg01.Client1KC.com> <48378CC92868D245993CE9C066A77E3A028FE54FC9ED@SBS02.CustomersDomain.local> From: "User1" <User1@client1.com> To: "Customer" <Customer@CustomersDomain.com> X-Antivirus-Scanner: Seems clean. You should still use an Antivirus Scanner This is a multi-part message in MIME format. ------_=_NextPart_001_01CB4556.D2EE6944 Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01CB4556.D2EE6944" ------_=_NextPart_002_01CB4556.D2EE6944 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Good luck! =20 From: Customer [mailto:Customer@CustomersDomain.com]=20 Sent: Thursday, August 26, 2010 2:42 PM To: User1 Subject: RE: Test email =20 Thanks... Came through perfect. Unfortunately, that didn't help !!!! =20 I'll keep digging. =20 Thanks, Customer -----Original Message----- From: User1 [mailto:User1@client1.com]=20 Sent: Thursday, August 26, 2010 2:40 PM To: Customer Subject: RE: Test email I also included an attachment! =20 From: Customer [mailto:Customer@CustomersDomain.com]=20 Sent: Thursday, August 26, 2010 2:39 PM To: User1 Subject: Test email =20 Can you reply back to this email. XXX has been having troubles with the emails he is receiving from you. It looks like somewhere out in cyberspace something is messing them up. There are others in our office having the same trouble, so I'm fairly sure it's on our end. =20 Thanks, =20 Customer RA, ASAI =20 www.CustomersDomain.com <http://www.CustomersDomain.com/>=20 =20 ------_=_NextPart_002_01CB4556.D2EE6944 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:x=3D"urn:schemas-microsoft-com:office:excel" = xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" = xmlns:a=3D"urn:schemas-microsoft-com:office:access" = xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" = xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" = xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" = xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" = xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" = xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" = xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" = xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" = xmlns:html=3D"http://www.w3.org/TR/REC-html40" = xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" = xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" = xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" = xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" = xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" = xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" = xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" = xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" = xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" = xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" = xmlns:udc=3D"http://schemas.microsoft.com/data/udc" = xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" = xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"= xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" = xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" = xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" = xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" = xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" = xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" = xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" = xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" = xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" = xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" = xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig= nature" = xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006= " xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi= ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" = xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"= = xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag= es" = xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/= " = xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub= lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" = xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)"> <!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--> <title>Message</title> <style> <!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p {mso-style-priority:99; mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; font-size:12.0pt; font-family:"Times New Roman","serif";} span.EmailStyle18 {mso-style-type:personal; font-family:"Calibri","sans-serif"; color:#1F497D;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --> </style> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div class=3DWordSection1> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'>Good luck!<o:p></o:p></span></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'><o:p>&nbsp;</o:p></span></p> <div> <div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt = 0in 0in 0in'> <p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Customer = Customer [mailto:Customer@CustomersDomain.com] <br> <b>Sent:</b> Thursday, August 26, 2010 2:42 PM<br> <b>To:</b> User1<br> <b>Subject:</b> RE: Test email<o:p></o:p></span></p> </div> </div> <p class=3DMsoNormal><o:p>&nbsp;</o:p></p> <div> <p class=3DMsoNormal><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:blue'>Thanks...&nbsp; Came through perfect.&nbsp; Unfortunately, = that didn't help !!!!</span><o:p></o:p></p> </div> <div> <p class=3DMsoNormal>&nbsp;<o:p></o:p></p> </div> <div> <p class=3DMsoNormal><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:blue'>I'll keep digging.</span><o:p></o:p></p> </div> <div> <p class=3DMsoNormal>&nbsp;<o:p></o:p></p> </div> <div> <p class=3DMsoNormal><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:blue'>Thanks,</span><o:p></o:p></p> </div> <div> <p class=3DMsoNormal><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:blue'>Customer</span><o:p></o:p></p> </div> <blockquote = style=3D'margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'> <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span = style=3D'font-size:10.0pt; font-family:"Tahoma","sans-serif"'>-----Original Message-----<br> <b>From:</b> User1 [mailto:User1@client1.com] <br> <b>Sent:</b> Thursday, August 26, 2010 2:40 PM<br> <b>To:</b> Customer<br> <b>Subject:</b> RE: Test email</span><o:p></o:p></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'>I also included an attachment!<o:p></o:p></span></p> <p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"; color:#1F497D'><o:p>&nbsp;</o:p></span></p> <div> <div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt = 0in 0in 0in'> <p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Customer = Customer [mailto:Customer@CustomersDomain.com] <br> <b>Sent:</b> Thursday, August 26, 2010 2:39 PM<br> <b>To:</b> User1<br> <b>Subject:</b> Test email<o:p></o:p></span></p> </div> </div> <p class=3DMsoNormal><o:p>&nbsp;</o:p></p> <div> <p class=3DMsoNormal><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Can you reply back to this email.&nbsp; Dustin has been having troubles with = the emails he is receiving from you.&nbsp; It looks like somewhere out in cyberspace something is messing them up.&nbsp; There are others in our = office having the same trouble, so I'm fairly sure it's on our = end.</span><o:p></o:p></p> </div> <div> <p class=3DMsoNormal>&nbsp;<o:p></o:p></p> </div> <div> <p class=3DMsoNormal><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Thanks,</span= ><o:p></o:p></p> </div> <div> <p class=3DMsoNormal>&nbsp;<o:p></o:p></p> </div> <p class=3DMsoNormal><strong><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:#004785'>Customer</span></strong><span = style=3D'font-size:10.0pt; font-family:"Arial","sans-serif";color:navy'>&nbsp;</span><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:black'>RA= , ASAI</span><o:p></o:p></p> <p><img width=3D150 height=3D75 id=3D"_x0000_i1025" src=3D"cid:image001.jpg@01CB452C.E9DB44D0"><o:p></o:p></p> <p class=3DMsoNormal><strong><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"; color:#004785'>Williams Spurgeon Kuhl &amp; Freshnock Architects, = Inc</span></strong><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>.<= /span><o:p></o:p></p> <p class=3DMsoNormal><span = style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>P.816.300.410= 1&nbsp;&nbsp;&nbsp;&nbsp; F.816.300.4102<em><span = style=3D'font-family:"Arial","sans-serif"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= <a href=3D"http://www.CustomersDomain.com/">www.CustomersDomain.com</a></span></em></span>= <o:p></o:p></p> <div> <p class=3DMsoNormal>&nbsp;<o:p></o:p></p> </div> </blockquote> </div> </body> </html> ------_=_NextPart_002_01CB4556.D2EE6944-- ------_=_NextPart_001_01CB4556.D2EE6944 Content-Type: image/jpeg; name="image001.jpg" Content-Transfer-Encoding: base64 Content-ID: <image001.jpg@01CB452C.E9DB44D0> Content-Description: image001.jpg Content-Location: image001.jpg /9j/4AAQSkZJRgABAgEAlgCWAAD/4REmRXhpZgAATU0AKgAAAAgABwESAAMAAAABAAEAAAEaAAUA

On Mon, 6 Sep 2010 08:59:45 +0000, Another Rob Hawkins wrote: > > >Hi Rich, > >Here's the eMail all the way down to the first line of the file attachment. Hopefully this will go through. > >Thanks for your help. I don't know if some of the things that are pointed out in this link are because of the medium used to get that raw message to me. http://www.apps.ietf.org/content/message-lint You might want to use FireFox (IE8 complains of a cross-site scripting problem) or some other browser to check the message. Besides lots of errors about too long lines and incorrect quoted-printable sequences (which may just be the result of copying your data from a HTML format into notepad), there was one problem that may be contributing to this -- the missing 0x0A at the end of one of the lines in the "Content-Type" header. Another may be the use of "multipart/alternative" instead of "multipart/mixed" as the content type. I'm hoping that at the end of your message there's a header "------_=_NextPart_001_01CB4556.D2EE6944--" to signal the end of that MIME body part. It wasn't in the data you posted. Since the only thing in this message that was base64-encoded was the attachment "image001.jpg", can you say what it is that you see when you open the message? Are you seing base64-encoded test, or are you seeing the "=20" stuff (quoted-printable)? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, >I don't know if some of the things that are pointed out in this link >are because of the medium used to get that raw message to me. I did copy from Outlook to Notepad, then to here from my previous post. >http://www.apps.ietf.org/content/message-lint >You might want to use FireFox (IE8 complains of a cross-site scripting >problem) or some other browser to check the message. Here's the top part of the results from the link you provided using the full eMail message directly copied from my Outlook 2007: MIME Lint v1.0 2007-06-22 is a strict syntax validator for Internet messages including MIME, RFC 822, DSN (RFC 1891) and MDN (RFC 2298) elements which has be run on the attached message. The result follows: ----------- UNKNOWN: unknown header 'Envelope-to' at line 2 UNKNOWN: unknown header 'Delivery-date' at line 3 WARNING: short-form domain 'mail' unwise in header 'Received' at lines 4-7 UNKNOWN: unknown 'with' item 'spam-scanned' in header 'Received' at lines 4-7 UNKNOWN: unknown header 'X-Spam-Checker-Version' at lines 8-9 UNKNOWN: unknown header 'X-Spam-Level' at line 10 UNKNOWN: unknown header 'X-Spam-Status' at lines 11-12 WARNING: line too long in header 'Received:' at line 13 UNKNOWN: unknown 'with' item 'esmtps' in header 'Received' at lines 13-18 UNKNOWN: unknown header 'X-Note-AR-ScanTimeLocal' at line 19 UNKNOWN: unknown header 'X-Policy' at line 20 UNKNOWN: unknown header 'X-Primary' at line 21 UNKNOWN: unknown header 'X-Note' at line 22 UNKNOWN: unknown header 'X-ALLOW' at line 23 UNKNOWN: unknown header 'X-Virus-Scan' at line 24 UNKNOWN: unknown header 'X-Note' at line 25 UNKNOWN: unknown header 'X-Country-Path' at line 26 UNKNOWN: unknown header 'X-Note-Sending-IP' at line 27 UNKNOWN: unknown header 'X-Note-Reverse-DNS' at line 28 UNKNOWN: unknown header 'X-Note-WHTLIST' at line 29 UNKNOWN: unknown header 'X-Note' at line 30 UNKNOWN: unknown header 'X-Note' at line 31 UNKNOWN: unknown header 'X-Note' at line 32 UNKNOWN: unknown header 'X-Note' at line 33 UNKNOWN: unknown header 'X-Note' at line 34 WARNING: line too long in header 'Received:' at line 37 UNKNOWN: unknown header 'X-MimeOLE' at line 38 UNKNOWN: unknown header 'Content-class' at line 39 UNKNOWN: unknown top-level content-type 'multipart/alternative' in type parameter in header 'Content-Type' at lines 41-43 ERROR: missing tokens '/A' at end of type parameter in header 'Content-Type' at lines 41-43 UNKNOWN: unknown header 'X-MS-Has-Attach' at line 48 UNKNOWN: unknown header 'X-MS-TNEF-Correlator' at line 49 UNKNOWN: unknown header 'Thread-Topic' at line 50 UNKNOWN: unknown header 'Thread-Index' at line 51 WARNING: line too long in header 'References:' at line 52 UNKNOWN: unknown header 'X-Antivirus-Scanner' at line 55 OK: found part multipart/related line 57 OK: preamble 57: OK: preamble 58: This is a multi-part message in MIME format. OK: preamble 59: OK: found part multipart/alternative line 64 OK: preamble 64: OK: preamble 65: OK: found part text/plain line 71 OK: found part text/html line 141 WARNING: decoded line 194 too long (2873 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: decoded line 271 too long (84 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: decoded line 275 too long (84 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: suppressed 2 duplicates of previous WARNING WARNING: Unnecessary quoted-printable soft line break line 286 WARNING: decoded line 302 too long (82 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: decoded line 318 too long (82 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: decoded line 332 too long (82 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: suppressed 5 duplicates of previous WARNING WARNING: Unnecessary quoted-printable soft line break line 372 WARNING: decoded line 388 too long (86 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: decoded line 395 too long (82 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: decoded line 409 too long (112 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: suppressed 1 duplicate of previous WARNING WARNING: Unnecessary quoted-printable soft line break line 421 WARNING: decoded line 425 too long (99 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: decoded line 431 too long (90 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: decoded line 433 too long (90 chars); text/plain shouldn't need folding (RFC 2046-4.1.1) WARNING: suppressed 4 duplicates of previous WARNING OK: epilogue 461: UNKNOWN: unknown header 'Content-Location' at line 468 ERROR: Content-Type 'name' parameter deprecated in favor of Content-Disposition 'filename' parameter (RFC 2046 sec 4.5.1, RFC 2183) lines 463-468 OK: found part image/jpeg line 470 OK: epilogue 941: ----------- Output lines begin with 'OK:' for informational messages, 'UNKNOWN:' for unregistered/unfamiliar extensions which may be incorrect, 'WARNING:' for poor usage which is either likely to cause problems or fails the 'generate conservative protocol' principle, and 'ERROR:' for standards violations. If your result contains only 'OK:' results, your message passed MIME Lint v1.0 2007-06-22 validation. There is no guarantee that this validator is free of bugs itself, so feel free to contact <chris.newman@sun.com> if you think you found an error in the validator or have a good idea to enhance the validator. Input message follows: ----------- ... I will mention that in my Outlook 2007, viewing the forwarded message from my customer, at the top of the eMail is says, "This message may contain extra line breaks." I can click on that line and an options pops to that says, "Remove line breaks". >I'm hoping that at the end of your message there's a header >"------_=_NextPart_001_01CB4556.D2EE6944--" to signal the end of that >MIME body part. It wasn't in the data you posted. Yes, the very last line in the eMail is: ------_=_NextPart_001_01CB4556.D2EE6944-- When I view the eMail from my client in my Outlook 2007, as a ATT00007.eml attachment is exactly what you see from my last post, less me changing names, domain names, IP addresses, and the removed long base64-encoded part as the attachment. Right after the headders, I do see a few lines that do have the =20, where the main user message is, then after that a bunch of HTML(I think), just as you see from my post on here. I affraid that I don't know much about the format codes for eMail. I hope that helps. Thanks - Rob

On Mon, 6 Sep 2010 16:31:43 +0000, Another Rob Hawkins wrote: > > >Hi Rich, > >>I don't know if some of the things that are pointed out in this link >>are because of the medium used to get that raw message to me. > >I did copy from Outlook to Notepad, then to here from my previous post. It's not now YOU did it, it's how the data are presented (in HTML vs. text) in these forums. >>http://www.apps.ietf.org/content/message-lint >>You might want to use FireFox (IE8 complains of a cross-site scripting >problem) or some other browser to check the message. >Here's the top part of the results from the link you provided using the full eMail message directly copied from my Outlook 2007: Oh, I know what it looks like. And I see you had some (but not all) of the same problem. I had tons of errors with the quoted-printable format because the HTML from the forum ignores lots of whitespace. The one error in the message body that's troubling is the 2873 character line. The others, in the message's headers are the missing 0x0a and the use of multipart/alternative where, I'm pretty sure, they should be using multipart/mixed. [ snip ] >I will mention that in my Outlook 2007, viewing the forwarded message from my customer, at the top of the eMail is says, "This message may contain extra line breaks." I can click on that line and an options pops to that says, "Remove line breaks". > >>I'm hoping that at the end of your message there's a header > >>"------_=_NextPart_001_01CB4556.D2EE6944--" to signal the end of that > >>MIME body part. It wasn't in the data you posted. > >Yes, the very last line in the eMail is: ------_=_NextPart_001_01CB4556.D2EE6944-- > >When I view the eMail from my client in my Outlook 2007, as a ATT00007.eml attachment Okay . . . so the message you posted was just the attachment? I didn't see any body part with "message\rfc822" as the content type. That's what I'd expect to see if someone included a message embedded in the message body. If you save the attachment as a .eml file and open it with Outlook Express do you see the same sort of problem as you do with Outlook? >is exactly what you see from my last post, less me changing names, domain names, IP addresses, and the removed long base64-encoded part as the attachment. Right after the headders, I do see a few lines that do have the =20, where the main user message is, then after that a bunch of HTML(I think), just as you see from my post on here. I affraid that I don't know much about the format codes for eMail. I hope that helps. If I save the text in your previos message as a .eml file and view it in Outlook 2010 or Windows Live Mail clients I see the errors in the quoted-printable formatting (i.e. the "=" in the text and the missing "t"): "Thanks... Came through perfect. Unfortunately, =hat didn't help !!!!" I do NOT see any HTML in the message. So, if you only sent the attachment, let's try again by you running the message *with the attachment* through that Message Lint web page and see what happens. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP