L
Lee Baker
Hi
I have this problem with winmail.dat files, but even after searching the
forums, I have not found an answer.
I have a SBS 2003 Server SP2, Outlook 2003 SP3 clients
I have so far changed the outgoing email to be HTML and plain text at the
client end.
I am unable to change the way internal emails are sent using the properties
of the email address as this is info is received directly from the Exchange
system and AD.
I have set the default options in the user properties under Exchange
features Tab -Protocols- POP3 to not use Protocol defaults but to use MIME
html and unchecked the Use Microsoft Rich_Text format Box.
I have even changed the Exchange System Internet Message Format by right
clicking on the default and setting the same option, just in case its still
overiding the previous change.
Still winmail.dat is occasionally coming through, I suspect this to be an
exchange problem as it seems that outgoing mail is not affected.
This only really started about a couple of weeks ago on one of our customers
servers and now we have 3 servers both exhibiting the same issue.
I have this problem with winmail.dat files, but even after searching the
forums, I have not found an answer.
I have a SBS 2003 Server SP2, Outlook 2003 SP3 clients
I have so far changed the outgoing email to be HTML and plain text at the
client end.
I am unable to change the way internal emails are sent using the properties
of the email address as this is info is received directly from the Exchange
system and AD.
I have set the default options in the user properties under Exchange
features Tab -Protocols- POP3 to not use Protocol defaults but to use MIME
html and unchecked the Use Microsoft Rich_Text format Box.
I have even changed the Exchange System Internet Message Format by right
clicking on the default and setting the same option, just in case its still
overiding the previous change.
Still winmail.dat is occasionally coming through, I suspect this to be an
exchange problem as it seems that outgoing mail is not affected.
This only really started about a couple of weeks ago on one of our customers
servers and now we have 3 servers both exhibiting the same issue.