I have been struggling with this problem all weekend and I think I have it narrowed down, but I don't know what to do about it.We have a hub and spoke configuration for email, we just upgraded the hub to E2007, so the hub site has E2003 and E2007 with most users in this head office on E2007. Users in the remote offices are on E2003. All mail is moving as expected except for mail sent to recipients on E2003 from 2007 when the E2003 recipient also has an alternate recipient configured. In those cases, the sender recieves a NDR as below (mars is the E2003 server, europa the 2007 server). Now, here's the rub. The forwarded email is, in fact delivered, the headers on that email indicate it was sent by E2007, which is configured to send directly. It looks like two attempts to send it are being made, one successful from 2007 and another which is failing for some unknown reason from 2003. I will note that anyone sending to those same recipients from 2003 DO NOT get the NDR, their messages are delivered and forwarded as normal through 2003 without the message below. What I don't understand is the message itself, since both servers support 8BITMIME, I think the message doesn't mean what it seems to mean, but I am not sure how to fix it.Generating server: mars.xxx.com paul_blonsky@yahoo.com#< #5.6.1 smtp;554 5.6.1 Body type not supported by Remote Host> #SMTP# Original message headers: Received: from europa.xxx.com ([192.168.0.92]) by mars.xxx.com withMicrosoft SMTPSVC(6.0.3790.3959); Mon, 13 Jul 2009 07:11:18 -0400Received: from europa.xxx.com ([192.168.0.92]) by europa.xxx.com([192.168.0.92]) with mapi; Mon, 13 Jul 2009 07:11:19 -0400Content-Type: application/ms-tnef; name="winmail.dat"Content-Transfer-Encoding: binaryFrom: Paul Blonsky <blonskyp@xxx.com>To: marstest <marstest@xxx.com>Date: Mon, 13 Jul 2009 07:11:17 -0400Subject: Another oneThread-Topic: Another oneThread-Index: AcoDqqTQqyqdHM49Q2CwDhVgBVPxdA==Message-ID: <0ED0424BBA9648438FCEC7297E22627B0CB3312627@europa.xxx.com>Accept-Language: en-USContent-Language: en-USX-MS-Has-Attach:X-MS-TNEF-Correlator: <0ED0424BBA9648438FCEC7297E22627B0CB3312627@europa.xxx.com>MIME-Version: 1.0Return-Path: blonskyp@xxx.comX-OriginalArrivalTime: 13 Jul 2009 11:11:18.0937 (UTC) FILETIME=[A57F0890:01CA03AA]

This should have something to do with 7bit-8bit MIME encoding...try this on e2k7:note the configuration of the send connector usingGet-SendConnector -Identity <SendConnectorIdParameter>then try:Set-SendConnector -Identity <SendConnectorIdParameter> -forceHELO $trueif it is $false.sounds messy, but this will force using the 7bit encoding.You should really look at upgrading to SP1 your E2k7: i heard somewhere thatsolves the problem.HTH.Diego Castelli

I should have said that I looked through all that 8-bit stuff when this issue first came up, but we're already on SP1 and both servers involved are Exchange (one 2003and 2007)and support 8BITMIME. This is why I don't think that error is telling the whole story.The thing is, when I send directly to the same external recipient from 2003, it works. When I send direct from 2007 directly to the external recipient, it works. It's only when I send via 2007 to a 2003 recipient with an alternate recipient set that I get that bounce from the 2003 server regarding the external alternate recipient. Regards,Paul

Hi Paul, Firstly, please check whether I understand the problem correctly: Auto-forward is configured on an Exchange 2003 user A to forward message to an external user B. When the user C in Exchange 2007 sends a message to the user A, the user C received a NDR message indicated that the message cannot be delivered to user B due to Body type not supported by Remote Host. If I am off base, please let me know. Based on current situation, I think that we have two issues currently: 1. Why the Exchange 2003 attempts auto-forward the message to user B again. 2. Why the NDR message is received. After my local test, I think after Exchange 2007 auto-forward the message to user B, the Exchange 2003 should not auto-forward the message again. If we are able to solve the first issue, I think the second issue does not exist. Therefore, I suggest we focus on the first issue. I would like to explain that in Exchange 2003, the journaling of messages and the identification of journal reports are controlled by using the X-EXCH50 binary large object (BLOB). By examining the X-EXCH50 BLOB, Exchange 2003 can determine whether a message has been journaled by a previous Exchange 2003 server and prevents later Exchange 2003 servers from journaling the message again. In Exchange 2007, the X-EXCH50 BLOB is deprecated and replaced with Simple Mail Transfer Protocol (SMTP) headers (X-MS-Exchange-Organization-Journal-Report) to which header firewall is applied. When Exchange 2007 journals a message, it adds a property to the X-EXCH50 BLOB in addition to the X-MS-Exchange-Organization-Processed-By-Journaling SMTP header so that Exchange 2003 servers that encounter the message know that the message has already been journaled. Therefore, the issue may occur if the X-EXCH50 BLOB is not transfer to Exchange 2003. I suggest you check whether the XEXCH50 command was provided by Exchange 2003 to Exchange 2007 when Exchange 2007 telnet to 2003. In addition, you should get 250 XEXCH50 Ok message if SMTP log is enabled on SMTP Virtual server on Exchange 2003. For your reference: Troubleshooting message journaling in Exchange Server 2003 and in Exchange 2000 Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;843105 Understanding Journaling in a Mixed Exchange 2003 and Exchange 2007 Environment http://technet.microsoft.com/en-us/library/aa997918.aspx Journaling Considerations in Mixed Environments http://msexchangeteam.com/archive/2009/06/01/451514.aspx Mike

Hi Paul, Firstly, please check whether I understand the problem correctly: Auto-forward is configured on an Exchange 2003 user A to forward message to an external user B. When the user C in Exchange 2007 sends a message to the user A, the user C received a NDR message indicated that the message cannot be delivered to user B due to Body type not supported by Remote Host. If I am off base, please let me know. Based on current situation, I think that we have two issues currently: 1. Why the Exchange 2003 attempts auto-forward the message to user B again. 2. Why the NDR message is received. After my local test, I think after Exchange 2007 auto-forward the message to user B, the Exchange 2003 should not auto-forward the message again. If we are able to solve the first issue, I think the second issue does not exist. Therefore, I suggest we focus on the first issue. I would like to explain that in Exchange 2003, the journaling of messages and the identification of journal reports are controlled by using the X-EXCH50 binary large object (BLOB). By examining the X-EXCH50 BLOB, Exchange 2003 can determine whether a message has been journaled by a previous Exchange 2003 server and prevents later Exchange 2003 servers from journaling the message again. In Exchange 2007, the X-EXCH50 BLOB is deprecated and replaced with Simple Mail Transfer Protocol (SMTP) headers (X-MS-Exchange-Organization-Journal-Report) to which header firewall is applied. When Exchange 2007 journals a message, it adds a property to the X-EXCH50 BLOB in addition to the X-MS-Exchange-Organization-Processed-By-Journaling SMTP header so that Exchange 2003 servers that encounter the message know that the message has already been journaled. Therefore, the issue may occur if the X-EXCH50 BLOB is not transfer to Exchange 2003. I suggest you check whether the XEXCH50 command was provided by Exchange 2003 to Exchange 2007 when Exchange 2007 telnet to 2003. In addition, you should get 250 XEXCH50 Ok message if SMTP log is enabled on SMTP Virtual server on Exchange 2003. For your reference: Troubleshooting message journaling in Exchange Server 2003 and in Exchange 2000 Server http://support.microsoft.com/default.aspx?scid=kb;EN-US;843105 Understanding Journaling in a Mixed Exchange 2003 and Exchange 2007 Environment http://technet.microsoft.com/en-us/library/aa997918.aspx Journaling Considerations in Mixed Environments http://msexchangeteam.com/archive/2009/06/01/451514.aspx Mike You are correct in your assessment of the behavior of the mail and the NDRs.When I telnet into the 2003 server and issue a EHLO, I do get a 250-XEXCH50, however the SMTP logs for an actual message being transferred from 2007 to 2003 does not contain a 250 XEXCH50 OK192.168.0.92 europa.XXX.COM - +europa.XXX.COM 245 20 -192.168.0.92 europa.XXX.COM - +GSSAPI 22 13 -192.168.0.92 europa.XXX.COM - +FROM:<blonskyp@XXX.COM> 42 55 -192.168.0.92 europa.XXX.COM - +TO:<marstest@XXX.COM> 0 27 -192.168.0.92 europa.XXX.COM - +156+2 32 13 -192.168.0.92 europa.XXX.COM - +<0ED0424BBA9648438FCEC7297E22627B0CC0586CDC@europa.XXX.COM> 98 3871 -192.168.0.92 europa.XXX.COM - europa.XXX.COM 62 4 -I do, however, see the XEXCH50 OK when the 2003 server is transferring mail to the other 2003 servers in the organization.