Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
O365 mailbox users receive Winmail.dat file from on-prem users in Hybrid setup
We have Hybrid environment configured a few weeks ago. Started migrating users from on-Prem to O365.
Everything was working ok for the last two weeks. This morning cloud (O365) users started complaining that they receive Winmail.dat file attachments from On-premises users. Nothing that we changed on our end. When on-prem users send email to O365 user, winmail.dat file is getting attached. Our users have formatted signature in the body of the email.
According to some articles, the recommendation is to set MailFlow\RemoteDomains\Def
After making this change and waiting for a couple of hours basically nothing changed.
Any thoughts?
Everything was working ok for the last two weeks. This morning cloud (O365) users started complaining that they receive Winmail.dat file attachments from On-premises users. Nothing that we changed on our end. When on-prem users send email to O365 user, winmail.dat file is getting attached. Our users have formatted signature in the body of the email.
According to some articles, the recommendation is to set MailFlow\RemoteDomains\Def
After making this change and waiting for a couple of hours basically nothing changed.
Any thoughts?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Please see if this solution enclosed in this link works for you. A change apparently made to Exchange.
https://community.spiceworks.com/topic/1977092-contact-receiving-attachments-as-winmail-dat
https://community.spiceworks.com/topic/1977092-contact-receiving-attachments-as-winmail-dat
I already made that change on my Office 365 admin center.
I made that change this morning but still receive Winmail.Bat file when email sent from onprem to O365.
If I am not mistaking this change has to be made on the receiving side right ?
I made that change this morning but still receive Winmail.Bat file when email sent from onprem to O365.
If I am not mistaking this change has to be made on the receiving side right ?
Did not understand what link ?
Also, do you have an idea how long does it take for TNEFEnabled setting to take effect in o365?
Also, do you have an idea how long does it take for TNEFEnabled setting to take effect in o365?
This link above
https://community.spiceworks.com/topic/1977092-contact-receiving-attachments-as-winmail-dat
With regard to the second question, no. But it is now late here and the change should be in place when people show up tomorrow.
https://community.spiceworks.com/topic/1977092-contact-receiving-attachments-as-winmail-dat
With regard to the second question, no. But it is now late here and the change should be in place when people show up tomorrow.
John, after reading little more about TNEF, I understood that the setting must be set on the sending side not receiving.
What I did is I looked for the Remote domains that were created when I ran HCW to configure hybrid and set TNEFEnabled to $false on them.
Basically, my On-premises Exchange Server had three remote domains: One Default and two created by HSW. I set all three TNEFEnabled to $false.
>Set-RemoteDomain "Hybrid Domain - DomainName.mail.onmicrosof
>Set-RemoteDomain "Hybrid Domain - DomainName.onmicrosoft.com
>Set-RemoteDomain Default -TNEFEnabled $false
Thanks
What I did is I looked for the Remote domains that were created when I ran HCW to configure hybrid and set TNEFEnabled to $false on them.
Basically, my On-premises Exchange Server had three remote domains: One Default and two created by HSW. I set all three TNEFEnabled to $false.
>Set-RemoteDomain "Hybrid Domain - DomainName.mail.onmicrosof
>Set-RemoteDomain "Hybrid Domain - DomainName.onmicrosoft.com
>Set-RemoteDomain Default -TNEFEnabled $false
Thanks
Premium Content
You need an Expert Office subscription to comment.Start Free Trial