Office 2013 Email Attachments Not Received
The emails are from inside a domain to an external email address.
On Premise Exchange 2010 server.
Office 2012, Office 2013
The latest Symantec End Point Antivirus
Postini
I've tried all kinds of solutions but nothing fixes the problem. I send an attachment (doc, docx, txt, pdf, etc). When the recipient (gmail, Hotmail, etc) receives it the original attachment is no longer attached and in it's place was winmail.dat
I know there are lots of solutions on the web but none that I've tried a lot and none seem to work.
On Premise Exchange 2010 server.
Office 2012, Office 2013
The latest Symantec End Point Antivirus
Postini
I've tried all kinds of solutions but nothing fixes the problem. I send an attachment (doc, docx, txt, pdf, etc). When the recipient (gmail, Hotmail, etc) receives it the original attachment is no longer attached and in it's place was winmail.dat
I know there are lots of solutions on the web but none that I've tried a lot and none seem to work.
winmail.dat means that Outlook cannot tell what the attachment is.
Classic case of interference.
If you leave Outlook closed and use OWA, are you able to see the attachment then?
Simon.
Classic case of interference.
If you leave Outlook closed and use OWA, are you able to see the attachment then?
Simon.
ASKER
Yes
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"The latest Symantec End Point Antivirus"
I work on a simple basis when Symantec's products are involved.
It doesn't matter what the problem is, they are the cause until proven otherwise by the complete removal of the product and a reboot of the machine.
90% of the time I am right.
Remove the product, reboot and test again. Disabling it is not enough, as with AV software that is just like putting a blindfold over the product, it doesn't actually stop it from scanning anything.
Simon.
I work on a simple basis when Symantec's products are involved.
It doesn't matter what the problem is, they are the cause until proven otherwise by the complete removal of the product and a reboot of the machine.
90% of the time I am right.
Remove the product, reboot and test again. Disabling it is not enough, as with AV software that is just like putting a blindfold over the product, it doesn't actually stop it from scanning anything.
Simon.
ASKER