Outlook 2003 Group Policy and encoding settings
 

I am trying to deploy the following Outlook 2003 settings via group policy:

Auto-select encoding for outgoing messages - Enabled
Encoding for outgoing messages - Enabled.

But when I configure "Encoding for outgoing messages - Enabled", the setting
"Auto-select encoding for outgoing messages" is ignored and on the client
side is applied as Disabled, although I have set it to Enabled. When I
configure "Encoding for outgoing messages - Not Configured", the setting
"Auto-select encoding for outgoing messages" works as expected. Is this some
kind of a bug?

Outlook 2003 Group Policy and encoding settings
 

I think those two settings are mutually exclusive. In other words, if you mandate an encoding with the first setting, Outlook can't auto-select.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Fluke" wrote in message ...
I am trying to deploy the following Outlook 2003 settings via group policy:

Auto-select encoding for outgoing messages - Enabled
Encoding for outgoing messages - Enabled.

But when I configure "Encoding for outgoing messages - Enabled", the setting
"Auto-select encoding for outgoing messages" is ignored and on the client
side is applied as Disabled, although I have set it to Enabled. When I
configure "Encoding for outgoing messages - Not Configured", the setting
"Auto-select encoding for outgoing messages" works as expected. Is this some
kind of a bug?

Outlook 2003 Group Policy and encoding settings
 

No, they are not, here is an abstract from Microsoft Office online:

--
Setting default encoding for outbound messages:

You can set a registry key to establish a default encoding for outbound
e-mail messages. This encoding is used for all outbound messages if
Auto-Select encoding is not enabled. This encoding is also used as the
preferred encoding if the Auto-Select encoding algorithm finds multiple
suitable encodings for the message.
--

Also, I can configure Outlook 2003 to have Auto-select encoding AND
Preffered encoding for outgoing messages. For example, I want to set the
preferred encoding to UTF-8. So when I write message which contains for
example cyrillic letters, there are multiple suitable encodings for this
message: KOI8-R, Windows 1251, Unicode (UTF-8) - the Preffered encoding for
outgoing messages determines which of these is used - in my case it will be
UTF-8. This is, what I want to achieve via Group Policy.

Thanks.



"Sue Mosher [MVP-Outlook]" wrote in message
...
I think those two settings are mutually exclusive. In other words, if you
mandate an encoding with the first setting, Outlook can't auto-select.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Fluke" wrote in message
...
I am trying to deploy the following Outlook 2003 settings via group policy:

Auto-select encoding for outgoing messages - Enabled
Encoding for outgoing messages - Enabled.

But when I configure "Encoding for outgoing messages - Enabled", the
setting
"Auto-select encoding for outgoing messages" is ignored and on the client
side is applied as Disabled, although I have set it to Enabled. When I
configure "Encoding for outgoing messages - Not Configured", the setting
"Auto-select encoding for outgoing messages" works as expected. Is this
some
kind of a bug?