Outlook users' problems with Apple mail attachments
Folks on Windows XP using Outlook 2003 are having problems with email from Apple mail. Apple mail is using Windows Friendly Attachments and Rich Text as the settings. Sometimes attachments (Word, Excel, PDF) come in fine with an additional .htm attachment, but the body text of the message is missing. If the Outlook user opens the .htm file, there is the body of the Apple mail. Testing with Plain Text results in the body text appearing fine in Outlook, but the attachment is seen as a *.dat file and of course can't be opened. The Macs are all on OS X Tiger with all OS updates applied. Users of Outlook in other offices don't have this problem, and users of Thunderbird on Windows don't have this problem. Any ideas on what is causing this and how to resolve it? Is there a setting on Outlook that needs to be tweaked? Is there a setting on Apple mail that needs to be tweaked? Apple mail attachments to this Windows office worked fine until a few weeks ago. I do not know what changed between then and now as I am not in charge of the computers at the Windows office. Could a Mac OS update have caused a problem? Something on Windows or Outlook specifically? Thanks for any help you can provide. I've scoured the web and have tried everything to no avail. Zipping attachments, while a workaround, is not a long-term solution. Thanks!
I've tried Plain Text and the body of the message came through fine, but it killed the attachment. It was a Word 2004 attachment, and it came through as a *.dat file. When using Rich Text, the attachment comes through fine (though with an additional .htm attachment), then the body text doesn't show up!
That's what I've been thinking all along, but don't know how to "prove" it, nor what to recommend for that Windows office outside of webmail. They think the problem is on the Mac end. I think the problem is on their end. Don't want to get into any conflicts about this. 🙂
Spoke to their Windows IT person and they are going to test with Thunderbird for Windows to see if there are problems with that. In the meantime, a Windows colleague of mine pointed out the following:
http://msdn.microsoft.com/en-us/library/aa338201.aspx for information about what may be going on.
Since you are running 10.4.11, I have to wonder if 10.5.6's Mail application better supports the new CSS formatting. Is there any way you can try to send the same documents from an Apple Store and see if the formatting is different? That might at least let you know if it is worth while updating to 10.5.6 on a separate boot volume just for sending messages to these people. I wouldn't update to everything unless you have known applications that all will work with that operating system.
Good suggestion. We did a test from a Leopard Mac with Apple mail and the recipient could see both the body text and attachments just fine. My Windows co-worker pointed me to this:
http://msdn.microsoft.com/en-us/library/aa338201.aspx
It annoys me no end that it looks like MS changed something that lots of people are complaining about, including Windows users, and as a result, I now have to upgrade my clients to OS X Leopard, which wasn't in our plans for the immediate future. Sigh...
Well just keep around a hard drive that is designed to boot a few machines into 10.5.6. If you have a mixture of Intel and PowerPC Macs, make sure that the partitions are designed to boot PowerPC and Intel separately. A procedure for doing that is described here:
Interestingly, it turns out that under Tiger, if you change the Text Encoding to Unicode (UTL-8) the attachments go through fine. We are still going to go with the plan to upgrade folks to Leopard, but it's still something I wanted to note.
Changing to the current version of OSX does not seem to affect this issue. When you have the confluence (effluence?) of Exchange server, vista and Office 07 the only way i have found to get attachments through every time is to zip them... and then spend some time trying to figure out how to tell a Vista user (which i ain't) how to get unzip to put the file on their desk top...
just shoot me.
I would welcome a workaround that takes into account the helplessness of vista users.
It may be their FAULT but when they are not tech-compatible and either partners in a transaction or clients... telling them it is their fault doesn't get it