How can I prevent MS TNEF (Microsoft Transport Neutral Encapsulation Format) from sending erroneously to GroupWise users. Prevent the unexpected Winmail.dat and hidden attachments (in the Winmail.dat) from being sent to GroupWise users.
We know that Exchange can share a namespace easily, but previously it has been recommended to configure subdomain routing from Exchange to GroupWise to address some formatting issues when sending to GroupWise that are resolved by creating an Exchange Remote Domain and setting the Message Format for the Exchange rich-text format to Never Use.
Example: gw.domain.com (or source.domain.com) and then create a new remote domain to deal with the MS TNEF issue and therefore just disabling it for the subdomain.
Here’s an example of the instructions:
Create New Remote Domain
Create a remote domain to represent the GroupWise address space. To do this, follow these steps:
1. Start the Exchange Management Console.
2. In the navigation pane, expand the Organization Configuration container.
3. Under Organization Configuration, click Hub Transport.
4. In the details pane, click the Remote Domains tab.
5. In the Actions pane, click New Remote Domain.
6. In the New Remote Domain dialog box that appears, type a descriptive name in the Name box. For example, type Mail to GroupWise.
7. In the Domain name box, type the SMTP domain for GroupWise users. For example, type gw.domain.com.
8. Click New.
9. After you create the domain object, right-click the object, and then click Properties.
10. In the Mail to GroupWise Properties dialog box, click the General tab.
11. Under Out-of-office message types delivered to this remote domain, click Allow external out of-office messages only.
12. Click the Message Format tab.
13. Under Exchange rich-text format, click Never use, and then click OK.
Configure Remote Domain Properties
TNEF Conversion Options