Skip to main content

Office 365 mailbox (Exchange online) with winmail.dat attachments


Receiving emails in office 365 mailbox (Exchange online) with winmail.dat attachments


Issue Description:  Customer is receiving emails with winmail.dat attachments.

Cause: This is due to Office365 setting the default attachment format to TNEF. This format causes issues with mail clients that are unable to read this attachment format, thus creating the WINMAIL.DAT issue.

Resolution:  The solution is disabling the TNEF via Office365 Portal as:

  1. In Exchange Admin Centre, Go to Mailflow>>Remote Domains.
  2. Select Use Rich-text Format as Never.
  3. Save it.

One can also use PowerShell to turn the conversion off as:

  1. $Cred = Get-Credential
  2. Type in your Office365 admin user credentials
  3. Connect-msolservice -credential $Cred
  4. $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $Cred -Authentication Basic -AllowRedirection
  5. Import-PSSession $Session
  6. Set-RemoteDomain Default -TNEFEnabled $false
  7. Remove-PSSession $Session

Referenced Link:
Manage TNEF Message Formatting with Remote Domains: https://msdn.microsoft.com/en-us/library/gg263346(v=exchsrvcs.149).aspx


Comments

  1. Christina Bedford8 January 2021 at 17:17

    The good news is, if you don't need the full suite of Microsoft 365 tools, you can access a number of its apps online for free -- including Word, Excel, PowerPoint, OneDrive, Outlook, Calendar and Skype. Here's how to get them: Go to Office.com. Login to your Microsoft account (or create one for free).
    for more information click here: how to add another email account to outlook 2016

    ReplyDelete

Post a Comment

Popular posts from this blog

Error - QuarantinedAttributeValueMustBeUnique

Case History. 1. Client already had users created in office 365 2. Client wanted to setup SSO for office 365 users Approach for requirement fullfilment   1. Deployed and configured Azure AD connect      95% users were synced and soft match was successfully done  5% users were getting error - QuarantinedAttributeValueMustBeUnique  (to view the sync issues -  https://aad.portal.azure.com/#blade/Microsoft_Azure_ADHybridHealth/AadHealthMenuBlade/SyncErros )  When we checked 2 users were found under Active users  1. one in Cloud (this was created earlier/ already existed ) with active licenses and Mailbox 2. one unlicensed synced with AD Solution - 1. Delete the unwanted user in Azure or AD as per this document.  https://blogs.msdn.microsoft.com/hkong/2017/03/23/how-to-fix-attributevaluemustbeunique-error-message-when-trying-to-sync-an-object-from-on-premises-active-directory-to-office-365/ ...
Post a Comment
Read more

Error - AttributeValueMustBeUnique in Azure AD connect sync

My customer had already created accounts in office 365 and managing them in Azure, however due to some changes in business they wanted to sync AD with Azure to sync Password and Manage Identity form AD. Solution - Deploy Azure AD connect on ADDC, and post that it will do a Soft Match. However there were error with some users, their identities did not sync and their status still reflected as Azure AD. Error -  Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [ProxyAddresses SMTP:user@domain.com;].  Correct or remove the duplicate values in your local directory.  Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values. Tracking Id: b8367c95-ae67-46e1-xxxx-xxxxxxxxxx ExtraErrorDetails: [{"Key":"ObjectId","Value":["cd088468-bb6a-4...
4 comments
Read more

Get All AIP encrypted files - SharePoint Online

One of the recent project merger and acquisition.  Technology - M365 tenant to Tenant migration Areas of consolidation 1. Mailboxes  2. SharePoint online data 3. OneDrive for Business data 4. Teams data migration 5. Security and Compliance Migration  Area of concern from security and compliance side was the encrypted files within EXO, SPO, Teams, ODB. Issue with encrypted data migration - end users will not be able to access the documents once the Source tenant is decommissioned.   Solution available -  Ask end users to unencrypt the data before migration  Alternet Solution - 1. Decrypt the files, mails using eDiscovery - This will give us output in PST format will is available for offline access, but the data in source will still be encrypted.  Decryption in eDiscovery - Microsoft Purview (compliance) | Microsoft Docs   2. Use Get-AIPfileLabel and Get-AIPFileLabel but in order to use this you must be aware of all the files paths....
5 comments
Read more