I'm evaluating Exchange 2007 at the moment, looking at upgrading our 2003 server to 2007 (and windows 2008 server). We have run into a weird problem where we can send normal text only emails just fine, but when we send an email through our Exchange 2007 server with an attachment, it corrupts the attachment and removes the message body and moves it to an attachment called "ATT00001.TXT" with the body of the message in that attachment.So normal emails are fine, anything with an attachment result in an email with two attachments, the original we sent (corrupted) and the message body now in the ATT00001.TXT attachment. The email itself is blank but it does have the subject we specified. I've done some research and found (http://support.microsoft.com/default.aspx/kb/157735) that on Exchange 5.5 there was a charset issue where you had to send using us-ascii, which we are, but it still happens. We did not see this problem on our Exchange 2003 server, only on our trial Exchange 2007 box. Has anyone had any experience with this, or know if theres a configuration somewhere that is causing this? Hopefully its something simple either on how the email is being sent, or some easy configuration option that is set to do this to the email (which i'm assuming is the latter). Any help would be greatly appreciated, figure I can make the best of my trial if I don't spend a week trying to fix a simple problem if someone else already has it figured out. :)Thanks!Leonard

Hi Leonard, 1. I would like to whether the issue only occurs when sending to external recipient through Exchange 2007. Or the issue occurs on both internal and external recipient 2. Please describe your environment. Whether it is a single Exchange Server 2007 organization. 3. Which client is used to send and receive the message? OWA, Outlook Exchange Mode, Outlook POP3/SMTP, Outlook Express and so on? To troubleshoot the issue, you need to analyze the message received by the Exchange 2007 and the output of the message after leaving Exchange 2007. Pipeline Tracing is a good function to help troubleshooting the issue: Using Pipeline Tracing to Diagnose Transport Agent Problems http://technet.microsoft.com/en-us/library/bb125198.aspx How to Enable Pipeline Tracing http://technet.microsoft.com/en-us/library/bb125018.aspx Mike