hmLoadTopic({
hmKeywords:"Route Slips",
hmTitle:"Route Slips",
hmDescription:"A message file waiting in a queue typically contains within its headers all the information that is needed to get the message delivered to the proper location. There are...",
hmPrevLink:"semaphore_files.html",
hmNextLink:"ssl_creating_and_using_ssl_certifi.html",
hmParentLink:"index.html",
hmBreadCrumbs:"Additional MDaemon Features",
hmTitlePath:"Additional MDaemon Features > Route Slips",
hmHeader:"<h1 class=\"p_Heading1\" style=\"page-break-after: avoid;\"><span class=\"f_Heading1\">Route Slips<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_BodyText\"><span class=\"f_BodyText\">A message file waiting in a queue typically contains within its headers all the information that is needed to get the message delivered to the proper location. There are headers stored within the file (such as the X-MDaemon-Deliver-To header) which provide MDaemon with instructions as to where and to whom the message should be delivered. Sometimes however it is necessary or useful to override this information and provide specific alternatives to where and to whom a message must be sent. Route Slips provide just such a mechanism. A route slip is a file that provides MDaemon with very specific instructions as to where and to whom a message should be sent. If a route slip is present for a particular message file then the settings within the route slip, and not those within the .MSG file itself, control where and to whom the message is sent.<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">Route slips end with the extension <\/span><span class=\"f_PlainText\">.RTE<\/span><span class=\"f_BodyText\">. &nbsp;For example, if a message file waiting to be sent is called &quot;<\/span><span class=\"f_PlainText\">MD0000.MSG<\/span><span class=\"f_BodyText\">,&quot; then the corresponding route slip file for this message will be called <\/span><span class=\"f_PlainText\">MD0000.RTE<\/span><span class=\"f_BodyText\"> and must be located in the same folder (mail queue) as the message file.<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_ControlIndent\">The format of a route slip is as follows:<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">[RemoteHost]<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">DeliverTo=example.net<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span style=\"font-family: Arial,Helvetica,sans-serif; color: #000000;\">&nbsp;<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">This section of a route slip provides MDaemon with the server to which the corresponding <\/span><span class=\"f_PlainText\">.MSG<\/span><span class=\"f_BodyText\"> file is to be sent. MDaemon will always attempt a direct connection to this host attempting to route the message in as short a time as possible. Only one host may be specified.<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">[Port]<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">Port=xxx<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span style=\"font-family: Arial,Helvetica,sans-serif; color: #000000;\">&nbsp;<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">This switch specifies the port that the TCP\/IP connection and delivery attempt should be made on. Port 25 is the default for SMTP email.<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">[LocalRcpts]<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">Rcpt0=address@example.com<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">Rcpt1=other-address@example.com<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">Rcpt2=yet-another-address@example.com<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span style=\"font-family: Arial,Helvetica,sans-serif; color: #000000;\">&nbsp;<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">[RemoteRcpts]<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">Rcpt0=address@example.net<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">Rcpt1=other-address@example.net<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span class=\"f_PlainText\">Rcpt2=yet-another-address@example.net<\/span><\/p>\n\r<p style=\"margin: 0 0 0 1.5000rem;\"><span style=\"font-family: Arial,Helvetica,sans-serif; color: #000000;\">&nbsp;<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">These sections of the route slip allow you to specify any number of local and remote recipients who should receive a copy of the associated <\/span><span class=\"f_PlainText\">.MSG<\/span><span class=\"f_BodyText\"> file. Local and remote recipient addresses must be kept separate and placed in their corresponding <\/span><span class=\"f_PlainText\">[LocalRcpts]<\/span><span class=\"f_BodyText\"> and <\/span><span class=\"f_PlainText\">[RemoteRcpts]<\/span><span class=\"f_BodyText\"> sections.<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">Route slips provide a good mechanism for delivering or redirecting email but they are not generally necessary. One use that MDaemon makes of route slips is in the case of &quot;routed&quot; mailing list mail. When you have a mailing list that is set to route a single copy of the list message to some remote host, a route slip is employed to accomplish this. It is a very efficient method of mail delivery when you have bulk addresses to deliver mail to since only a single copy of the message is required while any number of recipients of the message can be specified. Not all remote hosts allow this sort of routing to occur however. Since it is ultimately they who will have to deliver a copy of the message file to each address, some hosts place an upper limit on the number of recipients they will allow you to specify.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">&nbsp;<\/span><\/p>\n\r"
})
