We have a new install of Exchange 2007 with clients using OWA only (except for some IT staff using full outlook). When sending to our Groupwise users attachments arrive with the file name tnef.001, tnef.002 etc. Theseattahcments can be viewed correctly in the groupWise client, and when saved as filename.xls, filename.doc etc Word or excel can open the attachments correctly. This does require our 500+ Groupwise users to know what the filename and extension should be. Is there any way to force an Exchange 2007 server (with all roles in single box) to not send TNEF attachents that groupwise can read. Some articles suggest sending plain text or html from Outlook, but A) we dont use outlook, B) it doesn't work where I have tried it, and C) I cannot find an option to do this at the server. Questions around the Novell arena suggest this is quite common and the patch leel of groupwise does not seem to matter Any help would be greatly appreciated.

I am assuming that you are using SMTP to send to Groupwise. Open up the Exchange Management Console and go in to the Organization Config -> Hub Transport. Click on the Remote Domains tab. Create a new Remote Domain for the SMTP domain name of your Groupwise system. Then, on the properties of that domain, set the Exchange Rich Text Formatting option to "Never Use" See if that resolves this problem.

Our internal users use The Bat for getting email by POP3. They always receive the enclosure that contains file Winmail.dat. Can I turn off TNEF for Exchange 2007 for some internal users?

Bingo!!! Thanks for that Jim. I edited the Default remote domain to "never use Rich Text" and tested successfully. Attachments received with the correct filenames and extensions.

Thanks, also worked for me!