SB and Exchange

[bodycare]

I have search the web high and low for an answer please can someone help. Here is the situation nothing has changed on our exchange server we currently have mailboxes set-up for 3 remote users and then we forward all mail out to their own accounts e,g freeserve, hotmail

We have a program that generates a mail and sends it to a mail list that these 3 users are on it gets to their internal account but fails when trying to forward to their external mail account nothing has changed in the programme that generates the mail or on their external accounts but a Undeliverable message comes back with the following error

The message contains a content type that is not supported
<server.domain.com #5.6.1 smtp;554 5.6.1 Body type not supported by Remote Host>

This has worked many times before I just can't figure out why it has just stopped or how to fix it. I have treid send to other external accounts and it works, also if I send other mail to their external; account they receive it fine

 

[hrswift]

By default, the IIS SMTP service advertises 8BITMIME and allows MIME messages to be relayed. However, Microsoft Exchange Server versions 4.0, 5.0, and 5.5 are not able to handle 8-bit MIME messages.

To stop the Microsoft Windows 2000 / 2003 SMTP service from advertising 8BITMIME, please refer to the following Microsoft Knowledge base article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q262168

 

[N0ktar]

What program do you use and why are you not using Custom Recipient object to accomplish this task in Exchange server?
You could Create a Custom Recipient (Ctrl+R) in the Recipients folder and assign it an external email address (e,g freeserve, hotmail).
You would than open mailbox properties of a client who needs mail forward, go to Delivery Options and define your Custom Recipient as an Alternate Recipient and check to deliver email to both.

 

[bodycare]

Thats the way I am doing it, the program that sends the mails out is just an epos system it has worked fine for years then all of a sudden we get these messages nothing has change i.e the set-up of any part of the machine

 

[gpa3]

Microsoft just released a patch for Exchange 2000. I suspect one of the servers in your route is an Exchange server. Regardless, this is an 8bitmime issue and here is the correct way to fix it in Exchange 2000 if that is where your problem is. You have to fix it in active directory because active directory over-rides per server settings. We just had this problem on our incoming Exchange servers and this fixed it.

http://support.microsoft.com/kb/257569/