?
Solved

Mac OS X clients getting WINMAIL.DAT files, just not the way you expect...

Posted on 2010-11-08
11
Medium Priority
?
1,092 Views
Last Modified: 2012-05-10
Here's a simple and interesting one. Two users, both Mac OS X 10.6, both accessing Exchange 2007 server. One sends another an attachment. The recipient receives the attachment as a WINMAIL.DAT file, as if it were coming from a Windows client like Outlook Express and from the early 2000's.

Thoughts on why this is happening? How to stop it?

Thanks!
0
Comment
Question by:tregas
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
  • +1
11 Comments
 
LVL 9

Accepted Solution

by:
dmessman earned 100 total points
ID: 34087330
0
 
LVL 7

Expert Comment

by:OxygenITSolutions
ID: 34087347
I would suggest installing the latest updates for Exchange 2007.
If you are using Entourage, DO NOT install the latest Office update as it will cause crashing.
0
 

Author Comment

by:tregas
ID: 34087418
@dmessman --> I know of the issue you indicate, and this one's not it. This is a Mac sending to a Mac, both using Mail.app. They don't send in RTF, so it shouldn't be encoding the message in WINMAIL.DAT.

@OxygenITSolutions --> That I'm working on. Having come into this situation without having had hands on before is the primary complexity. I also generally refuse to deal with SBS, but either I do or I don't work. Period. I have SP3 on standby because one of the project managers says they are in a huge deadline crunch until the middle of November.

I love the fact that all businesses rely on technology to operate, but when it comes to making IT a priority, projects always get shoved to the bottom of the totem pole. They complain to me of an issue, but I can't apply the fix to that issue without them complaining.

Anything else I can look at which might be at issue before going to SP3?

Thanks!
0
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 
LVL 7

Assisted Solution

by:OxygenITSolutions
OxygenITSolutions earned 100 total points
ID: 34087473
You could check to see if any scanning software on the server is stripping the content of the email. There are a few settings in Forefront Security if this is 2008 SBS.

I did have the exact issue you described above with one client and installing the Exchange Service Pack (cant remember the exact name of it) resolved the issue.

Good Luck.
0
 

Author Comment

by:tregas
ID: 34087484
Thanks, guys! I don't think I'll be able to patch soon, but I will update this thread ASAP and let you know.
0
 
LVL 9

Expert Comment

by:dmessman
ID: 34087491
on the contrary - they are sending in RTF.  That's where winmail.dat attachments come from - RTF formatted emails being received by non-Outlook clients.
0
 

Author Comment

by:tregas
ID: 34087575
Mail.app does not generate RTF. Instead, it uses plain HTML for formatting. The issue is sending email from a Macintosh machine, through Exchange 2007, to a Macintosh machine. If it starts as HTML, it should arrive as HTML, unless Exchange is doing something on the way.

If I am unnecessarily re-clarifying, please forgive me :)

Thanks!
0
 
LVL 9

Expert Comment

by:dmessman
ID: 34087592
the point of the blog post was that even though you're sending in HTML or plain text, it arrives as RTF.  I advise you to check and confirm.
0
 

Author Comment

by:tregas
ID: 34088091
My bad. I get you now. Thanks :)

I figured it out, though it still needs to be tested. Using Exchange 2007, you need to do the following:
  1. Open the Exchange Management Console
  2. Expand the Organization Configuration option group
  3. Select Hub Transport
  4. Select the Remote Domains tab
  5. Get Properties for Default
  6. Select the "Format of original message sent as attachment to Journal report:" tab (I can see how that should have been obvious to me all this time!)
  7. Change the Exchange Rich-Text Format option to Never, or whichever option suits your needs.
I would not have found this were it not for your leads :) Thanks! Now, to see if it actually works.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34869166
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question