hmLoadTopic({
hmKeywords:"Account Editor,Account Editor Settings",
hmTitle:"Settings",
hmDescription:"Settings Hide account from \"Everyone\" lists and domain\'s public contacts folder MDaemon can automatically create and maintain \"Everyone@\" and \"MasterEveryone@\" mailing lists, w",
hmPrevLink:"ae_white-list.html",
hmNextLink:"ae_activesync-for-md.html",
hmParentLink:"account_manager.html",
hmBreadCrumbs:"Accounts Menu &gt; <a href=\"account_manager.html\">Account Manager<\/a> &gt; Account Editor",
hmTitlePath:"Accounts Menu > Account Manager > Account Editor > Settings",
hmHeader:"<h1 class=\"p_Heading1\" style=\"page-break-after: avoid;\"><span class=\"f_Heading1\">Settings<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_BodyText_Center\"><img style=\"margin:0 auto 0 auto;width:41.3125rem;height:28.8750rem;border:none\" src=\".\/images\/account-editor_options.png\"\/><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Settings<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Hide account from &quot;Everyone&quot; lists and domain\'s public contacts folder<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">MDaemon can automatically create and maintain <a href=\"ml_manager_settings.html\" class=\"topiclink\">&quot;Everyone@&quot; and &quot;MasterEveryone@&quot; mailing lists<\/a>, which can be used to send a message to all of a domain\'s users and all MDaemon users, respectively. By default these lists include all accounts of each domain, but you can check this box if you wish to hide this account from those lists—messages to those lists will not be sent to the account. This will also hide the account from the domain\'s public contacts folder.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Automatically place new meeting requests on calendar, marked Tentative<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">By default when an account receives a new meeting request, the meeting is placed on the user\'s calendar and marked as <\/span><span class=\"f_ControlIndent\" style=\"font-style: italic;\">Tentative<\/span><span class=\"f_ControlIndent\">.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Account automatically processes meeting and cancellation requests<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Click this checkbox if you wish to cause automatic processing of meeting requests, changes, and cancellations for this account. When the account receives a message that contains a meeting request, the account’s calendar will be updated automatically. This option is disabled for all accounts by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Automatically decline requests that conflict with an existing event<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">If automatic processing of meeting requests and cancellations is enabled for this account, those meeting requests will be automatically declined by default when they conflict with an existing event. Clear this checkbox if you wish to allow the conflicting event to be created.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Automatically decline recurring meeting requests<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Click this box if automatic processing of meeting requests and cancellations is enabled for this account but you wish to decline those requests when they are for recurring meetings.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Only process requests when sent from these email addresses<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">If you wish to automatically process requests only from certain email addresses, list those addresses here. Separate each address with a comma. Wildcards in addresses are permitted (e.g. <a href=\"mailto:*@example.com)\" target=\"_blank\" class=\"weblink\">*@example.com)<\/a>. If you leave this box blank then any address is allowed.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Account can use subaddressing to route incoming mail into folders<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Click this checkbox if you wish to permit <a href=\"ae_options.html#subaddressinganchor\" class=\"topiclink\">subaddressing<\/a> for this account.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Apply domain signature to all messages from this account<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">When there is a <a href=\"domain-manager_signatures.html\" class=\"topiclink\">Domain Signature<\/a> for the domain to which this account belongs, this option causes it to be added to all emails sent by the account. It is enabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Account is exempt from the &quot;Authentication credentials must match those of the email sender&quot; requirement<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Use this option if you wish to exempt the account from the &quot;<\/span><span class=\"f_ControlIndent\" style=\"font-style: italic;\">Authentication credentials must match those of the email sender<\/span><span class=\"f_ControlIndent\">&quot; global option located on the <a href=\"security--smtp_authentication.html\" class=\"topiclink\">SMTP Authentication<\/a> screen. This option is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Require app password to log in to SMTP, IMAP, ActiveSync, etc.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Check this box if you wish to require that the account use <a href=\"ae_app_passwords.html\" class=\"topiclink\">App Passwords<\/a> in mail clients, to log in to SMTP, IMAP, ActiveSync, or other mail service protocols. The account\'s regular <a href=\"passwords.html\" class=\"topiclink\">password<\/a>, however, must still be used to sign in to Webmail or Remote Admin.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Requiring App Passwords can help protect an account\'s password from dictionary and brute force attacks via SMTP, IMAP, etc. This is more secure because even if an attack of this sort were to guess an account\'s actual password, it wouldn\'t work and the attacker wouldn\'t know, because MDaemon would only accept a correct App Password. Additionally, if your accounts in MDaemon are using <a href=\"active-directory_overview.html\" class=\"topiclink\">Active Directory<\/a> authentication and Active Directory is set to lock an account after a number of failed attempts, this option can help prevent accounts from being locked out, because MDaemon will only check the App Passwords, not try to authenticate to Active Directory.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Show me all shared folders that this account has access to<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Click this button to display all shared folders to which the account has been given access.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Show me all mailing lists that have this account as a member<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Click this button to open a list of all <a href=\"ml_mailing_lists.html\" class=\"topiclink\">Mailing Lists<\/a> that have this account as a member.<\/span><\/p>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><a id=\"subaddressinganchor\" class=\"hmanchor\"><\/a><span class=\"f_Heading2\">Subaddressing<\/span><\/h2>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Subaddressing is a system for including a folder name in the mailbox portion of an account\'s email address. Using this system, messages addressed to the <\/span><span class=\"f_ControlIndent\" style=\"font-style: italic;\">mailbox+folder<\/span><span class=\"f_ControlIndent\"> name combination will be routed automatically to the account\'s folder included in the address (assuming that folder actually exists), without the need to create specific filtering rules to make that happen.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">For example, if <\/span><span class=\"f_T_Code\">bill.farmer@example.com<\/span><span class=\"f_ControlIndent\"> has an IMAP mail folder called &quot;<\/span><span class=\"f_T_Code\">stuff<\/span><span class=\"f_ControlIndent\">,&quot; then mail arriving addressed to &quot;<\/span><span class=\"f_T_Code\">bill.farmer+stuff@example.com<\/span><span class=\"f_ControlIndent\">&quot; would be routed automatically to that folder. Subfolders can be designated by including the folder and subfolder names separated by an additional &quot;+&quot; character, and underscores are used to replace spaces in folder names. So, using the example above, if Bill\'s &quot;<\/span><span class=\"f_T_Code\">stuff<\/span><span class=\"f_ControlIndent\">&quot; folder had a subfolder called &quot;<\/span><span class=\"f_T_Code\">my older stuff<\/span><span class=\"f_ControlIndent\">,&quot; then messages addressed to &quot;<\/span><span class=\"f_T_Code\">bill.farmer+stuff+my_older_stuff@example.com<\/span><span class=\"f_ControlIndent\">&quot; would be routed automatically to Bill\'s &quot;<\/span><span class=\"f_T_Code\">\\stuff\\my older stuff\\<\/span><span class=\"f_ControlIndent\">&quot; mail folder.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Since subaddressing requires the use of the &quot;<\/span><span class=\"f_T_Code\">+<\/span><span class=\"f_ControlIndent\">&quot; character, mailboxes that contain &quot;<\/span><span class=\"f_T_Code\">+<\/span><span class=\"f_ControlIndent\">&quot; cannot be subaddressed. So, in the example above, if the actual address were &quot;<\/span><span class=\"f_T_Code\">bill+farmer@example.com<\/span><span class=\"f_ControlIndent\">&quot; instead of &quot;<\/span><span class=\"f_T_Code\">bill.farmer@example.com<\/span><span class=\"f_ControlIndent\">&quot; then it could not be subaddressed. Further, you cannot use an address alias in a subaddress. You can, however, create an alias that refers to an entire subaddressed form. So, even though &quot;<\/span><span class=\"f_T_Code\">alias+stuff@example.com<\/span><span class=\"f_ControlIndent\">&quot; is not permitted, using &quot;<\/span><span class=\"f_T_Code\">alias@example.com<\/span><span class=\"f_ControlIndent\">&quot; to point to &quot;<\/span><span class=\"f_T_Code\">bill.farmer+stuff@example.com<\/span><span class=\"f_ControlIndent\">&quot; would be fine.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">To prevent exploits or abuse, the IMAP folder included in the subaddress <\/span><span class=\"f_ControlIndent\" style=\"font-weight: bold;\">must<\/span><span class=\"f_ControlIndent\"> be valid. If a subaddressed message arrives for an account that does not have a folder matching the name of the folder defined in the subaddress, then the subaddress will be treated as an unknown email address and handled accordingly, based on your other MDaemon settings. For example, if <\/span><span class=\"f_T_Code\">bill.farmer@example.com<\/span><span class=\"f_ControlIndent\"> does not have a folder named &quot;<\/span><span class=\"f_T_Code\">stuff<\/span><span class=\"f_ControlIndent\">&quot; and yet a message arrives for &quot;<\/span><span class=\"f_T_Code\">bill.farmer+stuff@example.com<\/span><span class=\"f_ControlIndent\">&quot; then that message will be treated as if were addressed to an unknown user, and it will most likely be rejected.<\/span><\/p>\n\r<div style=\"text-align: left; text-indent: 0; padding: 0 0 0 0; margin: 0 3.0625rem 0.8750rem 3.0000rem;\"><table style=\"background-color:#ffffe6; border:solid thin #000000; border-spacing:0;\">\n\r<tr>\n\r<td style=\"vertical-align:top; width:3.1250rem; height:3.1250rem; padding:0.3125rem; border:none\"><p class=\"p_NoFormat\"><img style=\"margin:0;width:3.1250rem;height:3.1250rem;border:none\" src=\".\/images\/lightbulb_on_50_yback.gif\"\/><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; padding:0.3125rem; border:none\"><p class=\"p_Notes\"><span class=\"f_Notes\">By default, each account has the subaddressing feature disabled. You can, however, disable this feature globally via the <\/span><span class=\"f_Notes\" style=\"font-style: italic;\">Disable subaddressing feature for all accounts<\/span><span class=\"f_Notes\"> option located on the <a href=\"preferences_miscellaneous.html\" class=\"topiclink\">Miscellaneous<\/a> screen of the Preferences dialog. If Subaddressing is disabled via that option, it will not be permitted for any account, regardless of the individual account settings.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<\/table>\n\r<\/div>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">&nbsp;<\/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=\"sf_white_list_auto.html\" class=\"topiclink\">Allow List (automatic)<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"webadmin_web-config.html\" class=\"topiclink\">Remote Administration<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"template_manager.html\" class=\"topiclink\">Template Manager<\/a><\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"passwords.html\" class=\"topiclink\">Passwords<\/a><\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">&nbsp;<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">&nbsp;<\/span><\/p>\n\r"
})
