hmLoadTopic({
hmKeywords:"ActiveSync,ActiveSync assigning client settings to Groups,ActiveSync Groups,Groups,Groups ActiveSync,Groups assigning ActiveSync Client Settings",
hmTitle:"Groups",
hmDescription:"If you wish to define customized ActiveSync Client Settings for an account Group, use this screen to manage those settings. All groups are listed here, and each group\'s entry...",
hmPrevLink:"activesync--devices.html",
hmNextLink:"activesync--client-types.html",
hmParentLink:"index.html",
hmBreadCrumbs:"Setup Menu &gt; ActiveSync",
hmTitlePath:"Setup Menu > ActiveSync > Groups",
hmHeader:"<h1 class=\"p_Heading1\" style=\"page-break-after: avoid;\"><span class=\"f_Heading1\">Groups<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_BodyText_Center\"><img style=\"margin:0 auto 0 auto;width:26.0625rem;height:25.0000rem;border:none\" src=\".\/images\/mobile_activesync_groups.png\"\/><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">If you wish to define customized ActiveSync Client Settings for an account <a href=\"groups_group-manager.html\" class=\"topiclink\">Group<\/a>, use this screen to manage those settings. All groups are listed here, and each group\'s entry indicates whether or not customized settings have been defined for it. To edit a Group\'s Client Settings, double-click the Group, or right-click the Group and click <\/span><span class=\"f_BodyText\" style=\"font-weight: bold;\">Customize Client Settings<\/span><span class=\"f_BodyText\">.<\/span><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Group Client Settings<\/span><\/p>\n\r<p class=\"p_BodyText_Center\"><img style=\"margin:0 auto 0 auto;width:36.0000rem;height:32.6250rem;border:none\" src=\".\/images\/mobile_activesync_groups_client-settings.png\"\/><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">By default each Group client setting is set to inherit its state from the user\'s <a href=\"domain-manager_activesync_client-settings.html\" class=\"topiclink\">Domain Client Settings<\/a>. Changing a group setting will override the domain setting for any account that is a member of the group. If you do not want the Group Client Settings to apply to a specific group member or device, then you can override the group settings by editing the Client Settings for the <a href=\"activesync--accounts.html\" class=\"topiclink\">Account<\/a>, <a href=\"activesync--client-types.html\" class=\"topiclink\">Client Type<\/a>, or <a href=\"activesync--devices.html\" class=\"topiclink\">Client<\/a>.<\/span><\/p>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><span class=\"f_Heading2\">General<\/span><\/h2>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Troubleshooting<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Log level<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">ActiveSync for MDaemon supports six levels of logging, from the highest to lowest amount of data logged:<\/span><\/p>\n\r<div style=\"text-align: left; text-indent: 0; padding: 0 0 0 0; margin: 0 0.3125rem 0.8750rem 2.6250rem;\"><table style=\"width:40.6250rem; border:none; border-spacing:0.1250rem;\">\n\r<tr>\n\r<td style=\"vertical-align:top; width:7.5000rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\" style=\"text-align: right;\"><span class=\"f_BodyText\" style=\"font-weight: bold;\">Debug<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:47.1875rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\"><span class=\"f_BodyText\">This is the most extensive log level. Logs all available entries, and is typically only used when diagnosing a problem.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:7.5000rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\" style=\"text-align: right;\"><span class=\"f_BodyText\" style=\"font-weight: bold;\">Info<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:47.1875rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\"><span class=\"f_BodyText\">Moderate logging. Logs general operations without details. This is the default log level.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:7.5000rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\" style=\"text-align: right;\"><span class=\"f_BodyText\" style=\"font-weight: bold;\">Warning<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:47.1875rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\"><span class=\"f_BodyText\">Warnings, errors, critical errors, and startup\/shutdown events are logged.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:7.5000rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\" style=\"text-align: right;\"><span class=\"f_BodyText\" style=\"font-weight: bold;\">Error<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:47.1875rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\"><span class=\"f_BodyText\">Errors, critical errors, and startup\/shutdown events are logged.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:7.5000rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\" style=\"text-align: right;\"><span class=\"f_BodyText\" style=\"font-weight: bold;\">Critical<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:47.1875rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\"><span class=\"f_BodyText\">Critical errors and startup\/shutdown event are logged.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:7.5000rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\" style=\"text-align: right;\"><span class=\"f_BodyText\" style=\"font-weight: bold;\">None<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:47.1875rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\"><span class=\"f_BodyText\">Only startup and shutdown events are logged.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:7.5000rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\" style=\"text-align: right;\"><span class=\"f_BodyText\" style=\"font-weight: bold;\">Inherit<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:47.1875rem; padding:0.0625rem; border:none\"><p class=\"p_BodyText\"><span class=\"f_BodyText\">By default, the Log Level setting is inherited from the Client Settings hierarchy. So, Clients inherit their setting from Client Types, Client Types from Accounts, Accounts from Groups, and so on. The Global Client Setting for this option is determined by the Log Level setting on the <a href=\"activesync--diagnostics.html\" class=\"topiclink\">Diagnostics<\/a> dialog.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<\/table>\n\r<\/div>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Archive transactions as [XML | WBXML]<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Use the <\/span><span class=\"f_ControlIndent\" style=\"font-style: italic;\">Archive XML...<\/span><span class=\"f_ControlIndent\"> and <\/span><span class=\"f_ControlIndent\" style=\"font-style: italic;\">WBXML<\/span><span class=\"f_ControlIndent\"> options if you wish to save this data, which can sometimes be useful for debugging purposes. The global options are disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Validate\/correct PIM mrk file integrity<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">This option runs a validation and correction process on the client\'s PIM data to look for known issues that could prevent it from syncing correctly, such as duplicate iCal UIDs or empty required fields. The global option is disabled by default.<\/span><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Client Options<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Enforce protocol restrictions<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enable this option if you wish to deny connections from any client that attempts to use a protocol other than the the <\/span><span class=\"f_ControlIndent\" style=\"font-style: italic;\">Allowed Protocol Versions<\/span><span class=\"f_ControlIndent\"> specified for the client. By default this option is disabled, which means that protocol restrictions do not prevent a client from using a different protocol; they simply tell the client which protocols to use. If a client attempts to use a restricted protocol anyway, MDaemon will still allow the connection. See: <a href=\"activesync--restrictions.html\" class=\"topiclink\">Protocol Restrictions<\/a> for more information.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Respond with logon alias as \'PrimarySmtpAddress\' in Get\/UserInformation<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">This allows the service to return an alias\/secondary address as the primary address in response to a Settings\/Get\/UserInformation request. This works around an issue caused by a post iOS9.x update that resulted in clients not being able to send mail using an alias. Using this option results in a non-specification compliant response to Settings\/Get\/UserInformation.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">New clients require administrative approval<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enable this option if you wish to require new clients to be authorized by an administrator before they can begin synchronizing with an account. The <\/span><span class=\"f_ControlIndent\"><a href=\"activesync--devices.html\" class=\"topiclink\">Clients<\/a> list indicates any clients awaiting authorization, and the administrator can authorize them from the same screen. This setting it is Off by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Max clients per user<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">If you wish to limit the number of ActiveSync clients or devices that can be associated with an MDaemon account, specify the desired number in this option. The global option is set to &quot;unlimited&quot; by default. This option is available on the Global, Domain, and Account client settings screens, not the individual Clients screens.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Bandwidth reset day<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Use this option if you wish to reset the bandwidth usage statistics for ActiveSync devices on a specific day of each month. The reset event takes place as part of the normal nightly maintenance process and is logged to the System log like other maintenance routines. The global option is set to &quot;0 (Never)&quot; by default, meaning the usage stats will never be reset. Set the child options to a different day if, for example, you want the reset day to coincide with a user or client\'s wireless carrier billing reset date.<\/span><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Security<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Exempt from Location Screen<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enable this option on an ActiveSync client\'s settings screen if you want the device to be able to bypass <a href=\"screening_location-screening.html\" class=\"topiclink\">Location Screening<\/a>. This makes it possible for a valid user to continue to access his or her account via ActiveSync when, for example, traveling to a location that is otherwise blocked from authentication attempts. In order to exempt the device it must have connected and authenticated using ActiveSync within the time-frame configured in the <a href=\"activesync--options.html\" class=\"topiclink\">Remove inactive clients after this many days<\/a> setting located on the Tuning screen.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Dynamically allow remote address<\/span><span class=\"f_Comment\"> <\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">When exempting a device from Location Screening, enable this option if you also wish to<\/span><span class=\"f_ControlIndent2\"> allow the remote IP address from which it is connecting. This can be useful for allowing other clients that might be connecting from the same IP address.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Allow clients provisioned\/managed by other servers<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">By default, when the ActiveSync server sends provisioning data\/policy specifics to a client and it reports that it is also managed by another ActiveSync server, the client will still be allowed to connect to MDaemon. In this circumstance, however, there is no way to ensure that your policy specifics will be applied where they conflict with the other ActiveSync server\'s policy. Generally clients default to using the most restrictive option where policies conflict. Disable this option if you do not wish to allows those clients to connect.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Disallow Factory Reset Wipes<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">If set to On\/Yes, the ability to <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\">Full Wipe<\/span><span class=\"f_ControlIndent\"> an ActiveSync Client will not be available. If you wish to be able to do a full remote wipe on a client, you must first disable this option. The option is disabled by default. For more information, see: <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\"><a href=\"activesync--devices.html\" class=\"topiclink\">Full Wiping an ActiveSync Client<\/a><\/span><span class=\"f_ControlIndent\"> on the Clients page.<\/span><\/p>\n\r<p class=\"p_CenteredHLine\" style=\"border-right: none; border-bottom: none; border-left: none;\"><span class=\"f_CenteredHLine\">&nbsp;<\/span><\/p>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><span class=\"f_Heading2\">FolderSync Options<\/span><\/h2>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">FolderSync Options<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Exclude<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Allowed\/Blocked Senders folder<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">By default the user\'s Allowed Senders and Blocked Senders contact folders are not synced with devices. They are generally only used by MDaemon to help with automatic spam prevention. For that reason they do not need to be displayed on devices as contacts.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Non-default mail folders<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">By default all user-created and default mail folders can be synced with the device. Enable this option if you wish to allow only the default mail folders to be synced, i.e. the Inbox, Sent Items, Deleted Items, Drafts, and so on. No user-created folders will be included. This option is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Non-default PIM folders<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">By default all of the user\'s PIM folders (i.e. contacts, calendar, notes, tasks, etc.) will be synced with the device. Enable this option if you wish to allow only the default PIM folders to be synced. For example, if this option is enabled and a user has multiple calendar folders, only the default calendar will be synced. This option is disabled by default.<\/span><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Include<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Public Folder hierarchy<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Check this box if you want the <a href=\"public_folder_manager.html\" class=\"topiclink\">public folders<\/a> to which a user has access to be included in the user\'s folder list on ActiveSync devices. This is enabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Allow searching<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Allows the client to search the <a href=\"public_folder_manager.html\" class=\"topiclink\">Public Folders<\/a> to which it has access. This is allowed by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Public Folder traversal (exposes folder names)<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">By default, in order for a client to sync\/access a public subfolder, the account must have <a href=\"access_control_list.html\" class=\"topiclink\">Lookup permission<\/a> for both the subfolder (i.e. child folder) and all parent <a href=\"public_folder_manager.html\" class=\"topiclink\">public folders<\/a> above it. If the account does not have permission to see the parent folders then it cannot see the child folder either, even if the account has permission to do so. Enable this option if you wish to allow the client to access these child folders. <\/span><span class=\"f_ControlIndent2\" style=\"font-weight: bold;\">Note:<\/span><span class=\"f_ControlIndent2\"> enabling this option must necessarily reveal the names of the parent folders to the client, which could be deemed a security risk. This option is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Maximum number of Public folders<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Use this option if you wish to limit the number of Public Folders allowed on the device. When a limit is set, the server iterates through the list of folders until the limit is reached, and then no more are sent to the device. There is no way to ensure the order in which folders will be processed. By default there is no global limit set.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Shared folders<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Check this box if you want the <a href=\"public-shared-folders.html\" class=\"topiclink\">shared folders<\/a> to which a user has access to be included in the user\'s folder list on ActiveSync devices. This is enabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Allow searching<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Allows the client to search the <a href=\"ae_shared_folders.html\" class=\"topiclink\">Shared Folders<\/a> to which it has access. This is allowed by default.<\/span><\/p>\n\r<p class=\"p_CenteredHLine\" style=\"border-right: none; border-bottom: none; border-left: none;\"><span class=\"f_CenteredHLine\">&nbsp;<\/span><\/p>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><span class=\"f_Heading2\">Content Handling<\/span><\/h2>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Content Handling Options<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Create tasks\/reminders for mail items when flagged by client<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">This option makes it possible for MDaemon to remind the user about flagged items, by creating a task item for each flagged email<\/span><span class=\"f_ControlIndent\"> when the client requests it. The global option for this control is enabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Always send meeting updates when event modified<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Some clients do not properly send meeting update emails when modifying a meeting. This instructs the ActiveSync Service to send out a meeting update when a meeting item is updated by the organizer. This should only be set on <a href=\"activesync--devices.html\" class=\"topiclink\">clients<\/a> and <a href=\"activesync--client-types.html\" class=\"topiclink\">client types<\/a> that fail to send out meeting updates properly, otherwise, it will result in duplicate meeting updates being sent. Consequently, this option is only available on the settings pages for Clients and Client-Types.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Request Read Receipts on all sent mail<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enable this option if you want the server to request read confirmation for all mail sent by a client. This is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Send Read Receipt from Server when mail marked as read and when requested by sender<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enable this option if you want the server to support read confirmation requests and issue a read receipt when a message is flagged as read by a client. This is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Send as Alias specified in ReplyTo Address<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Some clients may not allow a sender to send mail using an Alias. This feature was added to the <a href=\"activesync--restrictions.html\" class=\"topiclink\">Exchange ActiveSync (EAS) protocol<\/a> 16.x, but<\/span><span class=\"f_ControlIndent\"> some clients do not support 16.x. For instance, Outlook for Windows only uses EAS 14.0, and while it does allow a user to specify an alternate address to send as, the message generated does not reflect the user\'s choices correctly. This option allows the use of the ReplyTo field to send the email, as long as that ReplyTo address is a <a href=\"alias_aliases.html\" class=\"topiclink\">valid alias<\/a> for that user.<\/span><span class=\"f_ControlIndent\"> The global option is enabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Virtually merge public contacts into default contacts<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enable this option if you wish to merge the public contacts with the user\'s default contacts on the device. This is only a virtual merge, that is they are not actually copied to the user\'s contacts folder. This can be useful on clients that do not support Global Address List (GAL) searches. This is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Block Sender when moving mail into Junk-Email folder<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">When enabled, upon a client moving an email to the account\'s Junk Email folder, the service will add the Sender or From address of that email to the Blocked Senders Contacts folder.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Force sending meeting responses when a meeting request is accepted\/declined, etc.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">When enabled, upon a client accepting, declining or otherwise choosing an action in response to a meeting request, the service will send a meeting response to the meeting organizer. This is for specific clients that don\'t properly send those updates themselves.<\/span><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Preview Effective Settings<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">This button is available on all of the child Client Settings screens (i.e. <a href=\"activesync--domains.html\" class=\"topiclink\">domains<\/a>, <a href=\"activesync--accounts.html\" class=\"topiclink\">accounts<\/a>, and <a href=\"activesync--devices.html\" class=\"topiclink\">clients<\/a>). Since by default the options on those screens are set to inherit their settings from a parent screen, use this feature to see what settings are currently being applied to the displayed screen.<\/span><\/p>\n\r<p class=\"p_SeeAlso\" style=\"page-break-after: avoid; border-right: none; border-bottom: none; border-left: none;\"><span class=\"f_SeeAlso\">See:<\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"activesync--domains.html\" class=\"topiclink\">ActiveSync » Domains<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"activesync--accounts.html\" class=\"topiclink\">ActiveSync » Accounts<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"activesync--devices.html\" class=\"topiclink\">ActiveSync » Clients<\/a><\/span><\/p>\n\r"
})
