- #GMAIL FOR OUTLOOK 2016 MAC MAC OS X#
- #GMAIL FOR OUTLOOK 2016 MAC PC#
- #GMAIL FOR OUTLOOK 2016 MAC PLUS#
This brings up a separate page that allows you to start the process of configuring the rules for the recipient domain(s).
#GMAIL FOR OUTLOOK 2016 MAC PLUS#
#GMAIL FOR OUTLOOK 2016 MAC MAC OS X#
The problem: Some email recipients on Mac OS X using Apple Mail and Gmail receive winmail.dat attachments in place of correctly-encoded MIME attachments from users running Outlook 2016/Windows 10/Office 365 hosted mail. We appear to have found the solution - which I'm posting here to (hopefully) save some other poor b*stard from having to wade through weeks of poor documentation, support calls and forum posts. Two separate tickets raised on two Help Desks. It would be nice to actually get some forward progress on this - so far, this is the third Microsoft forum I've logged the issue with, and there have been 2056, and a check reveals that it's the latest version - no newer updates are available. There are no problems sending attachments from the offending account using OWA There are no problems sending attachments from Outlook 2016/Mac to the problematic Gmail/AppleMail account There are no problems reported from any external recipients using PCs, irrespective of mail server platform (including Gmail)
#GMAIL FOR OUTLOOK 2016 MAC PC#
The PC user is able to send attachments to other internal Exchange-based accounts without problems, and no errors occur when internal Mac users read the messages using Apple Mail We only have one PC running Outlook 2016 (all other users are on Mac) I've run the (I can't insert the link because of yet another Microsoft account mess-up) fix twice to no avail on the Microsoft-hosted Exchange instance. We're getting persistent problems with one of our users sending attachments from Outlook 2016/Win 10 to a client on Gmail/Mac OS10.10/Apple Mail, where all attachments appear as the dreaded winmail.dat files. This has now persisted for more than two months, and our company is increasingly looking like clowns in front of our customers. I've been bounced to this forum from the Office 365 forum, to try and get a resolution to this persistent winmail.dat issue.