Hi, I was wondering if you ever found the problem. I have come across it as
well. My situation:
Two exchange server 2003 boxes. Mailboxes in either server can send
attachments to the outside world just fine. Server1 users can send
attachments to Server2 mailboxes just fine, but users on Server2 cannot send
attachments to users on Server1, they get winmail.dat files. Both servers
have Exchange 2003 with SP2 installed.

My research has turned up info that Exchange sends messages within a Routing
Group via TNEF with is very similar to RTF, this seems to be the problem, but
can't turn off this "feature."

Of course, this should NOT be a problem because all users are using Outlook,
HOWEVER, they are getting winmail.dat files.

Thanks,
--
BillB


" wrote:

-kick-

Let me explain again:
These are Outlook 2000/2003 Exchange clients connecting to a local
Exchange 2003 Server, sending email to eachother in HTML format with
"Never use RTF" ticked in Exchange System Manager.

And they still get winmail.dat attachments!

I find it trully amazing after all these years of experience in IT I
finally have a "new" problem the community has no answer to :-)

You may want to look into the configuration of the Exchange Servers:

How to configure Internet e-mail message formats at the user and the domain
levels in Exchange Server 2003
http://support.microsoft.com/default...b;en-us;821750

Fixing problems recipients have with your Outlook messages
http://office.microsoft.com/en-us/as...spx?mode=print

I will check my stuff at work. I think I have more there that may help.

Nikki Peterson

"
wrote in message
...
Hi, I was wondering if you ever found the problem. I have come across it
as
well. My situation:
Two exchange server 2003 boxes. Mailboxes in either server can send
attachments to the outside world just fine. Server1 users can send
attachments to Server2 mailboxes just fine, but users on Server2 cannot
send
attachments to users on Server1, they get winmail.dat files. Both servers
have Exchange 2003 with SP2 installed.

My research has turned up info that Exchange sends messages within a
Routing
Group via TNEF with is very similar to RTF, this seems to be the problem,
but
can't turn off this "feature."

Of course, this should NOT be a problem because all users are using
Outlook,
HOWEVER, they are getting winmail.dat files.

Thanks,
--
BillB


" wrote:

-kick-

Let me explain again:
These are Outlook 2000/2003 Exchange clients connecting to a local
Exchange 2003 Server, sending email to eachother in HTML format with
"Never use RTF" ticked in Exchange System Manager.

And they still get winmail.dat attachments!

I find it trully amazing after all these years of experience in IT I
finally have a "new" problem the community has no answer to :-)

Thanks, the 821750 article is helpful, but my problem is within the exchange
org - from one server to another in the same routing group.
821750 says: Note ...Setting [RTF] to Never use so that you can communicate
with external parties will not affect the use of Exchange RTF format for
interchange between Outlook users within your internal Exchange organization.
Essentially, Exchange keeps using RTF (or actually NTEF) internally. One
would think this would not be a problem because everyone is using Outlook as
the client, but alas, they all get winmail.dat when sending attachments from
the second server's mailboxes to the first server's mailboxes -
interestingly, not the other way around. That is, all is OK from Server1 to
Server2, but not from Server2 to Server1.

Thanks, again...
--
BillB


"Nikki" wrote:

You may want to look into the configuration of the Exchange Servers:

How to configure Internet e-mail message formats at the user and the domain
levels in Exchange Server 2003
http://support.microsoft.com/default...b;en-us;821750

Fixing problems recipients have with your Outlook messages
http://office.microsoft.com/en-us/as...spx?mode=print

I will check my stuff at work. I think I have more there that may help.

Nikki Peterson

"
wrote in message
...
Hi, I was wondering if you ever found the problem. I have come across it
as
well. My situation:
Two exchange server 2003 boxes. Mailboxes in either server can send
attachments to the outside world just fine. Server1 users can send
attachments to Server2 mailboxes just fine, but users on Server2 cannot
send
attachments to users on Server1, they get winmail.dat files. Both servers
have Exchange 2003 with SP2 installed.

My research has turned up info that Exchange sends messages within a
Routing
Group via TNEF with is very similar to RTF, this seems to be the problem,
but
can't turn off this "feature."

Of course, this should NOT be a problem because all users are using
Outlook,
HOWEVER, they are getting winmail.dat files.

Thanks,
--
BillB


" wrote:

-kick-

Let me explain again:
These are Outlook 2000/2003 Exchange clients connecting to a local
Exchange 2003 Server, sending email to eachother in HTML format with
"Never use RTF" ticked in Exchange System Manager.

And they still get winmail.dat attachments!

I find it trully amazing after all these years of experience in IT I
finally have a "new" problem the community has no answer to :-)

Have you tried posting this on the microsoft.public.exchange?
There are alot of possible gotcha's with this. I would give the
Exchange Admins a try.

Nikki

"
wrote in message
...
Thanks, the 821750 article is helpful, but my problem is within the
exchange
org - from one server to another in the same routing group.
821750 says: Note ...Setting [RTF] to Never use so that you can
communicate
with external parties will not affect the use of Exchange RTF format for
interchange between Outlook users within your internal Exchange
organization.
Essentially, Exchange keeps using RTF (or actually NTEF) internally. One
would think this would not be a problem because everyone is using Outlook
as
the client, but alas, they all get winmail.dat when sending attachments
from
the second server's mailboxes to the first server's mailboxes -
interestingly, not the other way around. That is, all is OK from Server1
to
Server2, but not from Server2 to Server1.

Thanks, again...
--
BillB


"Nikki" wrote:

You may want to look into the configuration of the Exchange Servers:

How to configure Internet e-mail message formats at the user and the
domain
levels in Exchange Server 2003
http://support.microsoft.com/default...b;en-us;821750

Fixing problems recipients have with your Outlook messages
http://office.microsoft.com/en-us/as...spx?mode=print

I will check my stuff at work. I think I have more there that may help.

Nikki Peterson

"
wrote in message
...
Hi, I was wondering if you ever found the problem. I have come across
it
as
well. My situation:
Two exchange server 2003 boxes. Mailboxes in either server can send
attachments to the outside world just fine. Server1 users can send
attachments to Server2 mailboxes just fine, but users on Server2 cannot
send
attachments to users on Server1, they get winmail.dat files. Both
servers
have Exchange 2003 with SP2 installed.

My research has turned up info that Exchange sends messages within a
Routing
Group via TNEF with is very similar to RTF, this seems to be the
problem,
but
can't turn off this "feature."

Of course, this should NOT be a problem because all users are using
Outlook,
HOWEVER, they are getting winmail.dat files.

Thanks,
--
BillB


" wrote:

-kick-

Let me explain again:
These are Outlook 2000/2003 Exchange clients connecting to a local
Exchange 2003 Server, sending email to eachother in HTML format with
"Never use RTF" ticked in Exchange System Manager.

And they still get winmail.dat attachments!

I find it trully amazing after all these years of experience in IT I
finally have a "new" problem the community has no answer to :-)