I have a client who is having trouble recieving attachments from a single client of theres, everybody else is ok. What is happening is. Client A sends an email to Client B. Client B cant view the attachment they recieved and get loads of garbled text appears in body of email. Client A sends email to ME I then forward email to Client B and they can open attachment ok. Client A uses outlook 2007. Client B uses Exchange 2003/outlook 2007 I use exchange 2010/ Outlook 2010. Here is a copy of the header of the email message that is having problem opening attachments. Microsoft Mail Internet Headers Version 2.0 Received: from inpmx001.iondale.net ([81.134.204.215]) by adlsbs001rm5.adlhq.atlas-dies.co.uk with Microsoft SMTPSVC(6.0.3790.4675); Mon, 13 Dec 2010 09:20:35 +0000 X-MDAV-Processed: inpmx001.iondale.net, Mon, 13 Dec 2010 09:20:34 +0000 Received: from relay1.post.newnet.co.uk (relay1.post.newnet.co.uk [212.87.80.27]) by inpmx001.iondale.net (inpmx001.iondale.net) (MDaemon PRO v10.0.0) with ESMTP id md50000772755.msg for <>; Mon, 13 Dec 2010 09:20:33 +0000 Authentication-Results: inpmx001.iondale.net spf=neutral ; x-ip-ptr=pass dns.ptr=relay1.post.newnet.co.uk (ip=212.87.80.27); x-ip-helo=pass smtp.helo=relay1.post.newnet.co.uk (ip=212.87.80.27); x-ip-mail=hardfail (does not match 212.87.80.27) X-Spam-Processed: inpmx001.iondale.net, Mon, 13 Dec 2010 09:20:33 +0000 (not processed: message size (152983) exceeds spam filter configured max size of (102400)) X-MDOP-RefID: fgs=0 (_st=1 _vt=0 _iwf=0) X-MDPtrLookup-Result: pass dns.ptr=relay1.post.newnet.co.uk (ip=212.87.80.27) (inpmx001.iondale.net) X-MDHeloLookup-Result: pass smtp.helo=relay1.post.newnet.co.uk (ip=212.87.80.27) (inpmx001.iondale.net) X-MDMailLookup-Result: hardfail (does not match 212.87.80.27) (inpmx001.iondale.net) X-MDDK-Result: neutral (inpmx001.iondale.net) X-MDDKIM-Result: neutral (inpmx001.iondale.net) X-Rcpt-To: X-MDRcpt-To: X-MDRemoteIP: X-Envelope-From: Received: (qmail 3233 invoked from network); 13 Dec 2010 09:20:11 -0000 Received: from wasp1-34.adsl.newnet.co.uk (HELO mail.wasp-ltd.co.uk) ( by relay1.post.newnet.co.uk with SMTP; 13 Dec 2010 09:20:11 -0000 Received: from SRV-02.wasp-ltd.local ([fe80::b4a6:4584:530e:feae]) by SRV-02.wasp-ltd.local ([fe80::b4a6:4584:530e:feae%11]) with mapi; Mon, 13 Dec 2010 09:20:11 +0000 From: Richard Haustead To: Denis Huxtable < Subject: RE: K4528 knife tool [Scanned] Thread-Topic: K4528 knife tool [Scanned] Thread-Index: AcuYb1chW6M7GJW+TPKEWRaYcB6zagAANxVQAAALf6AAACPK8ACNYW9w Date: Mon, 13 Dec 2010 09:20:09 +0000 Message-ID: <DB7C2E0D33773543AA9DA291CB3FEAD404ECB5@SRV-02.wasp-ltd.local> References: <15a5149e-5dad-484e-a6d8-ed9e2f6c827c@SRV-02.wasp-ltd.local> <A32724A1EE8EBA43B8EB8A1F5B696ADC122A35@adlsbs001rm5.adlhq.atlas-dies.co.uk> <DB7C2E0D33773543AA9DA291CB3FEAD404EC61@SRV-02.wasp-ltd.local> <> In-Reply-To: <> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Content-Type: multipart/mixed; boundary="_006_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_" MIME-Version: 1.0 X-Return-Path: <> X-MDaemon-Deliver-To: <> Return-Path: X-OriginalArrivalTime: 13 Dec 2010 09:20:35.0729 (UTC) FILETIME=[FFD07010:01CB9AA6] --_006_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: multipart/related; boundary="_005_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_"; type="multipart/alternative" --_005_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: multipart/alternative; boundary="_000_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_" --_000_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable --_000_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

On Wed, 2 Feb 2011 16:27:17 +0000, Sdurbidge83 wrote: > > >I have a client who is having trouble recieving attachments from a single client of theres, everybody else is ok. > >What is happening is. Client A sends an email to Client B. Client B cant view the attachment they recieved and get loads of garbled text appears in body of email. Client A sends email to ME I then forward email to Client B and they can open attachment ok. I don't see any attachments in the MIME body parts. I'd guess that there's something between A and B that's incorrectly reassembling the body parts after inspecting them. Anti-spam and anti-virus are always good candidates. Does the set of "Received:" headers in the messages you receive differ from the ones the damaged messages contain? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

the only thing that is different is i dont get the last part of the headers on the emails i recieve. The detail below is only in the damged emails. I have tried a test of sending a Plan text email TO cLIENT a with attachments who then forwars on to Client B and they can recieve ok. I am just wondering wheather exchange is having trouble converting the emails from Client A but what confuses me is that they both are using outlook?????? --_006_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: multipart/related; boundary="_005_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_"; type="multipart/alternative" --_005_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: multipart/alternative; boundary="_000_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_" --_000_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable --_000_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable. I dont know if this helps but this is what they are getting at the bottom of the damged emails. This is only a small section of what appears on the email. This garbled text can be 2 - 3 pages long. image/gif; name=TT03707.gif" Content-Description: ATT03707.gif Content-Disposition: inline; filename=TT03707.gif"; size409; creation-date=on, 24 Jan 2011 08:33:15 GMT"; modification-date=on, 24 Jan 2011 08:33:15 GMT" Content-ID: Content-Transfer-Encoding: base64 R0lGODlhrgGxAeUAAP///wAAAPDw8Ojo6ODg4NDQ0MDAwNjY2Li4uMjIyKioqLCwsIiIiKCgoJiY mICAgJCQkEhISHBwcHh4eGhoaFhYWGBgYFBQUEBAQDg4ODAwMBgYGCAgICgoKEig+Giw+LjQ+LjY +ODo+ODw+AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAArgGxAUAI/wABCBxIsKDBgwgT KlzIsKHDhxAjSpxIsaLFixgzatzIsaPHjwQXCHB4YMGCBAdGglzJsqXLlzAbDjhgwGQBlQVpxtxZ 0QAEBAaAHhiAU+KBBDwF0AyakqfTp1BdKkUANAGBlwIMFI3KFcAABBsVDCTAgMGCpgRnIljggMIE BFejKk2wAMEBAASGGkgwoKvfrgcIKO1LwIACBAUE/2U4twGFCwwaULWreKKCu4sdGoh7UUGDzAYF ECiwgEEFCAoMbCa6cUCCw0NB+xVdAIGCAn1hChhQuGaDCacXJBawFeaCCQYyNhArO6GC4hEPRGhO XeBMwxMYOPDswEDuATUNJP/uKjpBULsHaTpYzl0Cg9TDqy8+QCF3RdLyBx69OIF5/v8NLfBZRK/Z ZxBKEpFlIIAMFiQABcndN2B1CCwIUQIVNKghQ7U5VABSMoHV0AH+bWgiQRBAUNEAD1AHXkUQnihj QQM8t5AACEDHUIkJOcDZjCcWUIGONzZgIVcFYBYRAhQA6aRAlyn0IUYVKiSABLIRR9RoiRUAwEi8 PSnQBUpClOFi3knEAIhizogAmwaJxFEBXiJ0VpszSrCARCd1RQCcEF0JYAABEEToQYcalCgAhQ5E 6KKGNirQoo0eKulD+B1YZkcD7GkQiRBBCqmjl5LqaKSjTnoppaoyquFPEt3/FlWSG5HFwKZ4Zmkk QQLwyJKcBEmAa67VkTXsQwkwEFMCtr3oFwEINPDArh6N+ui1ppJaqrbZMioppY8WlOpBPg602VMI WqfiQ9ZeCy6qCIXb6rzealvquB4l8EAFFHRH5Jy+slTYk0otIMFl/xILQJ+dPhuhcAoHSkADF1Tg AG4NCjBBARD0xxJfCS4AgcVAqTbydlZR5wCgTh6w3JFyGXCAsrle2WLEoUGQ8EUCeKoQBBHuBJ4D DqSYwM4yMfDjkxbkB2ubCtz8kmspNmDW0vfd2lADWGtEp0Jr4SymAAzU2eAAEiB9drQMRNCvSZup /RcEZh/0QN0aBWzdA3KL/53lmnhG67eMhiWkWmsiGqQAy4P/50DiYgvwwLGNN0eAA9DVlBFcoWFZ OYAK6P25T587jrdXNFekN1WlNyd46w5JDjnsfymwNAE2SjQlQwNMwDjtLBngAPAWKUi8U5IHbdCZ

the only thing that is different is i dont get the last part of the headers on the emails i recieve. The detail below is only in the damged emails. I have tried a test of sending a Plan text email TO cLIENT a with attachments who then forwars on to Client B and they can recieve ok. I am just wondering wheather exchange is having trouble converting the emails from Client A but what confuses me is that they both are using outlook?????? --_006_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: multipart/related; boundary="_005_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_"; type="multipart/alternative" --_005_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: multipart/alternative; boundary="_000_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_" --_000_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable --_000_DB7C2E0D33773543AA9DA291CB3FEAD404ECB5SRV02waspltdlocal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable. I dont know if this helps but this is what they are getting at the bottom of the damged emails. This is only a small section of what appears on the email. This garbled text can be 2 - 3 pages long. image/gif; name=TT03707.gif" Content-Description: ATT03707.gif Content-Disposition: inline; filename=TT03707.gif"; size409; creation-date=on, 24 Jan 2011 08:33:15 GMT"; modification-date=on, 24 Jan 2011 08:33:15 GMT" Content-ID: Content-Transfer-Encoding: base64 R0lGODlhrgGxAeUAAP///wAAAPDw8Ojo6ODg4NDQ0MDAwNjY2Li4uMjIyKioqLCwsIiIiKCgoJiY mICAgJCQkEhISHBwcHh4eGhoaFhYWGBgYFBQUEBAQDg4ODAwMBgYGCAgICgoKEig+Giw+LjQ+LjY +ODo+ODw+AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAArgGxAUAI/wABCBxIsKDBgwgT KlzIsKHDhxAjSpxIsaLFixgzatzIsaPHjwQXCHB4YMGCBAdGglzJsqXLlzAbDjhgwGQBlQVpxtxZ 0QAEBAaAHhiAU+KBBDwF0AyakqfTp1BdKkUANAGBlwIMFI3KFcAABBsVDCTAgMGCpgRnIljggMIE BFejKk2wAMEBAASGGkgwoKvfrgcIKO1LwIACBAUE/2U4twGFCwwaULWreKKCu4sdGoh7UUGDzAYF ECiwgEEFCAoMbCa6cUCCw0NB+xVdAIGCAn1hChhQuGaDCacXJBawFeaCCQYyNhArO6GC4hEPRGhO XeBMwxMYOPDswEDuATUNJP/uKjpBULsHaTpYzl0Cg9TDqy8+QCF3RdLyBx69OIF5/v8NLfBZRK/Z ZxBKEpFlIIAMFiQABcndN2B1CCwIUQIVNKghQ7U5VABSMoHV0AH+bWgiQRBAUNEAD1AHXkUQnihj QQM8t5AACEDHUIkJOcDZjCcWUIGONzZgIVcFYBYRAhQA6aRAlyn0IUYVKiSABLIRR9RoiRUAwEi8 PSnQBUpClOFi3knEAIhizogAmwaJxFEBXiJ0VpszSrCARCd1RQCcEF0JYAABEEToQYcalCgAhQ5E 6KKGNirQoo0eKulD+B1YZkcD7GkQiRBBCqmjl5LqaKSjTnoppaoyquFPEt3/FlWSG5HFwKZ4Zmkk QQLwyJKcBEmAa67VkTXsQwkwEFMCtr3oFwEINPDArh6N+ui1ppJaqrbZMioppY8WlOpBPg602VMI WqfiQ9ZeCy6qCIXb6rzealvquB4l8EAFFHRH5Jy+slTYk0otIMFl/xILQJ+dPhuhcAoHSkADF1Tg AG4NCjBBARD0xxJfCS4AgcVAqTbydlZR5wCgTh6w3JFyGXCAsrle2WLEoUGQ8EUCeKoQBBHuBJ4D DqSYwM4yMfDjkxbkB2ubCtz8kmspNmDW0vfd2lADWGtEp0Jr4SymAAzU2eAAEiB9drQMRNCvSZup /RcEZh/0QN0aBWzdA3KL/53lmnhG67eMhiWkWmsiGqQAy4P/50DiYgvwwLGNN0eAA9DVlBFcoWFZ OYAK6P25T587jrdXNFekN1WlNyd46w5JDjnsfymwNAE2SjQlQwNMwDjtLBngAPAWKUi8U5IHbdCZ

On Thu, 3 Feb 2011 09:24:33 +0000, Sdurbidge83 wrote: >the only thing that is different is i dont get the last part of the headers on the emails i recieve. The detail below is only in the damged emails. I have tried a test of sending a Plan text email TO cLIENT a with attachments who then forwars on to Client B and they can recieve ok. I am just wondering wheather exchange is having trouble converting the emails from Client A but what confuses me is that they both are using outlook?????? [ snip ] >I dont know if this helps but this is what they are getting at the bottom of the damged emails. This is only a small section of what appears on the email. This garbled text can be 2 - 3 pages long. What you have there is the attachment that's missing part of the MIME headers. What's missing is the "Content-type:". It should look like this: Content-type: image/gif; name=TT03707.gif" Content-Description: ATT03707.gif Content-Disposition: inline; filename=TT03707.gif"; size409; creation-date=on, 24 Jan 2011 08:33:15 GMT"; modification-date=on, 24 Jan 2011 08:33:15 GMT" Content-ID: Content-Transfer-Encoding: base64 >image/gif; name=TT03707.gif" Content-Description: ATT03707.gif Content-Disposition: inline; filename=TT03707.gif"; size409; creation-date=on, 24 Jan 2011 08:33:15 GMT"; modification-date=on, 24 Jan 2011 08:33:15 GMT" Content-ID: Content-Transfer-Encoding: base64 R0lGODlhrgGxAeUAAP///wAAAPDw8Ojo6ODg4NDQ0MDAwNjY2Li4uMjIyKioqLCwsIiIiKCgoJiY mICAgJCQkEhISHBwcHh4eGhoaFhYWGBgYFBQUEBAQDg4ODAwMBgYGCAgICgoKEig+Giw+LjQ+LjY +ODo+ODw+AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAArgGxAUAI/wABCBxIsKDBgwgT KlzIsKHDhxAjSpxIsaLFixgzatzIsaPHjwQXCHB4YMGCBAdGglzJsqXLlzAbDjhgwGQBlQVpxtxZ 0QAEBAaAHhiAU+KBBDwF0AyakqfTp1BdKkUANAGBlwIMFI3KFcAABBsVDCTAgMGCpgRnIljggMIE BFejKk2wAMEBAASGGkgwoKvfrgcIKO1LwIACBAUE/2U4twGFCwwaULWreKKCu4sdGoh7UUGDzAYF ECiwgEEFCAoMbCa6cUCCw0NB+xVdAIGCAn1hChhQuGaDCacXJBawFeaCCQYyNhArO6GC4hEPRGhO XeBMwxMYOPDswEDuATUNJP/uKjpBULsHaTpYzl0Cg9TDqy8+QCF3RdLyBx69OIF5/v8NLfBZRK/Z >ZxBKEpFlIIAMFiQABcndN2B1CCwIUQIVNKghQ7U5VABSMoHV0AH+bWgiQRBAUNEAD1AHXkUQnihj QQM8t5AACEDHUIkJOcDZjCcWUIGONzZgIVcFYBYRAhQA6aRAlyn0IUYVKiSABLIRR9RoiRUAwEi8 PSnQBUpClOFi3knEAIhizogAmwaJxFEBXiJ0VpszSrCARCd1RQCcEF0JYAABEEToQYcalCgAhQ5E 6KKGNirQoo0eKulD+B1YZkcD7GkQiRBBCqmjl5LqaKSjTnoppaoyquFPEt3/FlWSG5HFwKZ4Zmkk QQLwyJKcBEmAa67VkTXsQwkwEFMCtr3oFwEINPDArh6N+ui1ppJaqrbZMioppY8WlOpBPg602VMI WqfiQ9ZeCy6qCIXb6rzealvquB4l8EAFFHRH5Jy+slTYk0otIMFl/xILQJ+dPhuhcAoHSkADF1Tg AG4NCjBBARD0xxJfCS4AgcVAqTbydlZR5wCgTh6w3JFyGXCAsrle2WLEoUGQ8EUCeKoQBBHuBJ4D DqSYwM4yMfDjkxbkB2ubCtz8kmspNmDW0vfd2lADWGtEp0Jr4SymAAzU2eAAEiB9drQMRNCvSZup /RcEZh/0QN0aBWzdA3KL/53lmnhG67eMhiWkWmsiGqQAy4P/50DiYgvwwLGNN0eAA9DVlBFcoWFZ OYAK6P25T587jrdXNFekN1WlNyd46w5JDjnsfymwNAE2SjQlQwNMwDjtLBngAPAWKUi8U5IHbdCZ The way it is now, it looks like it's just part of the previous MIME body part. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP