hmLoadTopic({
hmKeywords:"List Routing,Macros in mailing list messages,Mailing List message macros,Mailing Lists,Mailing Lists Routing,Routing",
hmTitle:"Routing",
hmDescription:"Routing Deliver list mail to each member individually If selected, when messages are received for distribution to the list, a separate copy of each message will be created and",
hmPrevLink:"ml_moderation.html",
hmNextLink:"ml_support_files.html",
hmParentLink:"ml_mailing_lists.html",
hmBreadCrumbs:"Setup Menu &gt; <a href=\"ml_mailing_lists.html\">Mailing List Manager<\/a> &gt; Mailing List Editor",
hmTitlePath:"Setup Menu > Mailing List Manager > Mailing List Editor > Routing",
hmHeader:"<h1 class=\"p_Heading1\" style=\"page-break-after: avoid;\"><span class=\"f_Heading1\">Routing<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_BodyText_Center\"><img style=\"margin:0 auto 0 auto;width:32.5000rem;height:27.5625rem;border:none\" src=\".\/images\/mailing-list_routing.png\"\/><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">Routing<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Deliver list mail to each member individually<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">If selected, when messages are received for distribution to the list, a separate copy of each message will be created and dispatched to each list member. This will result in numerous individual messages being created which could affect the server<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s performance, depending on the size of the list and the load on the server. This option is selected by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Replace Message-ID with unique value for each member<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">When MDaemon is set to generate a separate copy of each message for each member, click this checkbox if wish each of those messages to have a unique Message-ID. This option is disabled by default and is not recommended unless you have special circumstances that require it.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Replace macros found within message body<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Enable this option if you wish to allow the use of special macros in mailing list messages. When a macro is found, MDaemon will replace it with the corresponding value the macro represents, for each separate message before sending it to each list member.<\/span><\/p>\n\r<p class=\"p_ControlHeading3\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading3\">...but only when the sender provides the list\'s password<\/span><\/p>\n\r<p class=\"p_ControlIndent3\"><span class=\"f_ControlIndent3\">When allowing macros within the message body, click this option if you wish to require the <a href=\"ml_moderation.html\" class=\"topiclink\">list\'s password<\/a> in order for someone to use macros in their message. When this option is disabled, anyone who can send a message to the list will be able to use macros.<\/span><\/p>\n\r<p class=\"p_ControlHeading3\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading3\">Macros:<\/span><\/p>\n\r<div style=\"text-align: left; text-indent: 0; padding: 0 0 0 0; margin: 0 0.3125rem 0.8750rem 5.1250rem;\"><table style=\"width:50%; border:none; border-spacing:0;\">\n\r<tr>\n\r<td style=\"vertical-align:top; width:8.3125rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">\$LISTNAME\$<\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:34.5000rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">The name of the list, or the &quot;mailbox&quot; portion of the list\'s address (e.g. &quot;MyList&quot; of MyList@example.com).<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:8.3125rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">\$LISTDOMAIN\$<\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:34.5000rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">The list\'s domain (e.g. &quot;example.com&quot; of MyList@example.com).<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:8.3125rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">\$SENDER\$<\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:34.5000rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">The message sender\'s email address.<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:8.3125rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">\$FULLNAME\$<\/p>\n\r<p class=\"p_Normal\">\$FIRSTNAME\$<\/p>\n\r<p class=\"p_Normal\">\$LASTNAME\$<\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:34.5000rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">The list member\'s full name, first name, or last name, respectively (if available).<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:8.3125rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">\$EMAIL\$<\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:34.5000rem; padding:0.2500rem; border:none\"><p class=\"p_Normal\">The list member\'s email address.<\/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\">Deliver list mail using individual RCPT commands for each member<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">If selected, MDaemon will route a single copy of each list message to the specified smart host, rather then send individual messages to each member. This method employs multiple <\/span><span class=\"f_PlainText\">RCPT To<\/span><span class=\"f_ControlIndent\"> statements during the SMTP session with the specified host.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Deliver to this host<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Designate the smart host to which you wish to pass all of the list\'s messages for delivery, using RCPT To statements for each member.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">AUTH Logon\/Password<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Any logon credentials required by the host.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Limit RCPTs to [xx] per message (0=no limit)<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Some hosts limit the number of <\/span><span class=\"f_PlainText\">RCPT To<\/span><span class=\"f_ControlIndent2\"> statements that they will accept when you are attempting to route a single copy of a message through them. If you specify the limit in this control then MDaemon will work around it by creating additional copies of the message and dividing the list into smaller groups. Then it will deliver the message to those groups thus avoiding the need to exceed the limitation. This is similar to the <\/span><span class=\"f_ControlIndent2\" style=\"font-style: italic;\">Deliver list mail to each member individually<\/span><span class=\"f_ControlIndent2\"> option above, but it generates less copies, sending each copy to groups of addresses rather than generating a separate copy for each member.<\/span><\/p>\n\r<p class=\"p_ControlHeading2\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading2\">Ignore RCPT errors when sending to host<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Since some smart hosts will refuse to queue or spool mail for certain domains, the routed approach to list delivery could cause numerous problems. An error code returned from the smart host as a result of this refusal would ordinarily cause MDaemon to abort the delivery attempt. Check this option if you want MDaemon to ignore error codes returned from the smart host during delivery of routed list mail, thus allowing those members that are accepted a chance to receive the message.<\/span><\/p>\n\r<p class=\"p_ControlIndent\" style=\"margin: 0 0.3125rem 0.8750rem 3.0000rem;\"><span class=\"f_ControlIndent\">&nbsp;<\/span><\/p>\n\r"
})
