In some situations you may need to override server defaults for specific clients. For example, the majority of your POP3 clients can interpret HTML, so you set the server to provide message bodies in HTML by default. However, there are a few clients that use the POP3 server but cannot interpret HTML. To provide plain text messages for those clients, you can override the MIME encoding set on the server. Overriding server defaults at the user level allows you to support clients with different needs that are accessing the same POP3 virtual server.
Note You can also create additional virtual servers on a single computer to provide administration for a number of different messaging scenarios. This solution may be best suited for organizations that have a large number of clients with varying needs.
To set per-user options:
Tip If Active Directory Users and Computers doesn't appear on the Administrative tools menu, on the Start menu, click Run, type dsa.msc, and then click OK.
|MIME Encoding||MIME provides a way to describe a
message consisting of different parts. Options include:
|uuencode||UNIX to UNIX encoding (uuencode) converts a binary file into printable 7-bit ASCII characters without loss of information.|
|Default character set||If multiple character sets can be used
to convert a message, a default character set is used.
Note Early MAPI clients, such as Outlook 97, do not allow the user to specify a character set. It is for these clients only that the character set conversion settings apply.
|Use Exchange Rich Text Format||If enabled, POP3 clients receive messages in Exchange RTF. Although all POP3 clients receive the information as an attachment, the attachment is opened and displayed as a normal message for POP3 clients that can interpret Exchange rich-text format. For POP3 clients that cannot interpret Exchange rich-text format, an attachment is displayed.|