hmLoadTopic({
hmKeywords:"RAW,RAW Bypassing the Content Filter,RAW Message Specification,RAW Sample messages,RAW Special fields supported by",
hmTitle:"The RAW Message Specification",
hmDescription:"MDaemon has inherent support for a simple and powerful mail message format known as RAW mail. The purpose of the RAW mail system is to provide a simple and standard format that...",
hmPrevLink:"remote_server_control--general_email_controls.html",
hmNextLink:"raw_the_raw_message_specification.html#bypassingthecontentfilter",
hmParentLink:"index.html",
hmBreadCrumbs:"Additional MDaemon Features &gt; The RAW Message Specification",
hmTitlePath:"Additional MDaemon Features > The RAW Message Specification > The RAW Message Specification",
hmHeader:"<h1 class=\"p_Heading1\" style=\"page-break-after: avoid;\"><span class=\"f_Heading1\">The RAW Message Specification<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_BodyText\"><span class=\"f_BodyText\">MDaemon has inherent support for a simple and powerful mail message format known as RAW mail. The purpose of the RAW mail system is to provide a simple and standard format that software systems such as MDaemon can use to create much more complex RFC-2822 compliant message. Use of mail transport agents such as RAW allow client software to offload to the server all the complicated work of maintaining adherence to Internet mail standards.<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">RAW mail consists of a series of required and optional text headers followed by a message body. Most headers consist of a token followed by a value enclosed in &lt;&gt; symbols. Each header line ends with a &lt;CRLF&gt; combination of characters. Headers are separated from the message body by a blank line and are case insensitive, and the <\/span><span style=\"font-family: Arial,Helvetica,sans-serif; font-style: italic; color: #010100;\">from<\/span><span class=\"f_BodyText\"> and<\/span><span style=\"font-family: Arial,Helvetica,sans-serif; font-style: italic; color: #010100;\"> to<\/span><span class=\"f_BodyText\"> headers are the only ones that are required. All text, headers and body, are plain ASCII text and must be contained in a file that ends with the extension, &quot;<\/span><span class=\"f_PlainText\">.raw<\/span><span class=\"f_BodyText\">&quot; (for example &quot;<\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">my-message.raw<\/span><span class=\"f_BodyText\">&quot;). Then, to queue the message for delivery, place the <\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">*.raw<\/span><span class=\"f_BodyText\"> file in MDaemon<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_BodyText\">s RAW queue (typically located at, &quot;<\/span><span class=\"f_PlainText\">C:\\MDaemon\\Queues\\Raw<\/span><span class=\"f_BodyText\">&quot;).<\/span><\/p>\n\r<h3 class=\"p_Heading3\" style=\"page-break-after: avoid;\"><a id=\"bypassingthecontentfilter\" class=\"hmanchor\"><\/a><span class=\"f_Heading2\">Bypassing the Content Filter<\/span><\/h3>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">By default, RAW messages are passed through the Content Filter like normal messages. If you want a given RAW message to bypass the filter then start the name of the file with &quot;<\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">p<\/span><span class=\"f_BodyText\">&quot; or &quot;<\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">P<\/span><span class=\"f_BodyText\">&quot;. For example, &quot;<\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">P_my-message.raw<\/span><span class=\"f_BodyText\">&quot; would bypass the Content Filter but &quot;<\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">my-message.raw<\/span><span class=\"f_BodyText\">&quot; would be processed through it normally.<\/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\">Bypassing the Content Filter will prevent messages from being <\/span><span class=\"f_Notes\">DKIM signed. If you have configured MDaemon to sign all messages then this could potentially cause some delivery problems. If you want MDaemon to sign RAW messages configured to bypass the Content Filter then you can do so by using the <\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace;\">x-flag=sign<\/span><span class=\"f_Notes\"> option outlined below.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<\/table>\n\r<\/div>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><a id=\"rawheaders\" class=\"hmanchor\"><\/a><span class=\"f_Heading2\">RAW Headers<\/span><\/h2>\n\r<div style=\"text-align: left; text-indent: 0; padding: 0 0 0 0; margin: 0.5000rem 0 0.1875rem 0;\"><table style=\"border:none; border-spacing:0.1875rem;\">\n\r<tr>\n\r<td style=\"vertical-align:top; width:20.3750rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0.6250rem;\"><span class=\"f_ControlIndent\">From &lt;mailbox@example.com&gt;<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:17.6250rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0;\"><span class=\"f_ControlIndent\">This field contains the email address of the sender.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:20.3750rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0.6250rem;\"><span class=\"f_ControlIndent\">To &lt;mailbox@example.com [, mailbox@example.com]<\/span><span style=\"font-family: Arial,Helvetica,sans-serif; font-style: italic; color: #010100;\">&gt;<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:17.6250rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0;\"><span class=\"f_ControlIndent\">This field contains the email address(es) of the recipient(s). &nbsp;Multiple recipients can be specified by separating each one with a comma character.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:20.3750rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0.6250rem;\"><span class=\"f_ControlIndent\">ReplyTo &lt;mailbox@example.com&gt;<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:17.6250rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0;\"><span class=\"f_ControlIndent\">An optional email address where replies to this message will be directed.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:20.3750rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0.6250rem;\"><span class=\"f_ControlIndent\">CC &lt;maibox@example.com[, mailbox@example.com]&gt;<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:17.6250rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0;\"><span class=\"f_ControlIndent\">An optional list of carbon copy recipients of this message. &nbsp;Multiple carbon recipients can be specified by separating each one with a comma character.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:20.3750rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0.6250rem;\"><span class=\"f_ControlIndent\">Subject &lt;text&gt;<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:17.6250rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0;\"><span class=\"f_ControlIndent\">An optional subject for the message.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr>\n\r<td style=\"vertical-align:top; width:20.3750rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0.6250rem;\"><span class=\"f_ControlIndent\">Header &lt;Header: Value&gt;<\/span><\/p>\n\r<\/td>\n\r<td style=\"vertical-align:top; width:17.6250rem; padding:0; border:none\"><p class=\"p_ControlIndent\" style=\"margin: 0.5000rem 0 0.1875rem 0;\"><span class=\"f_ControlIndent\">Allows you to explicitly place Header\/Value combinations into the message.<\/span><span style=\"font-size: 0.90rem; font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\"> <\/span><span class=\"f_ControlIndent\">This makes it possible for you to place custom or other non-standard headers into your *.raw messages.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<\/table>\n\r<\/div>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><a id=\"special-fields-supported-by-raw\" class=\"hmanchor\"><\/a><span class=\"f_Heading2\">Special Fields Supported by RAW<\/span><\/h2>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">File attachment and encoding<\/span><\/p>\n\r<p class=\"p_ControlIndent2\" style=\"margin: 0.3750rem 0.3125rem 0.8750rem 3.6250rem;\"><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">x-flag=attach &lt;filepath, method&gt; [-x]<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent\">Example: <\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">x-flag=attach &lt;c:\\utils\\pkzip.exe, MIME&gt; -x<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">This X-FLAG specifies the value &quot;ATTACH&quot; along with two parameters within the &lt;&gt; characters. The first parameter is a complete path to the file which should be attached to the message. The second parameter which is separated from the first by a comma character and specifies the method of encoding that is to be used when attaching the message. MDaemon supports two values for this parameter. The method of MIME instructs the server to use the Internet standard Base64 method of message encoding. The method of ASCII instructs the server to simply import the file into the message. An optional -X parameter at the end of the string instructs the server to remove the file from disk once it has been attached.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Delivery Status Notification<\/span><\/p>\n\r<p class=\"p_ControlIndent2\" style=\"margin: 0.3750rem 0.3125rem 0.8750rem 3.6250rem;\"><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">x-flag=confirm_delivery<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">When converting a RAW message which contains this flag into RFC-2822 mail, the string is transformed to the &quot;Return-Receipt-To: &lt;sender@example.com&gt;&quot; construct.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Placing Specific Header\/Value Combinations into the RFC-2822 Message<\/span><\/p>\n\r<p class=\"p_ControlIndent2\" style=\"margin: 0.3750rem 0.3125rem 0.8750rem 3.6250rem;\"><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">header &lt;header: value&gt;<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">If you wish to place a specific header\/value combination into the RFC-2822 message that will be generated from a RAW file, you will need to use the HEADER macro listed in the RAW Headers section above. For example, if you want the header &quot;Delivered-By: mail-machine@example.com&quot; to be placed into the RFC-2822 message you would place this: &quot;header &lt;Delivered-By: mail-machine@example.com&gt;&quot; in the RAW message. Note that the &quot;header&quot; macro requires both the field and value. You can place as many &quot;header&quot; macros as you need into a RAW message.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">DKIM Signing RAW Messages<\/span><\/p>\n\r<p class=\"p_ControlIndent2\" style=\"margin: 0.3750rem 0.3125rem 0.8750rem 3.6250rem;\"><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">x-flag=sign<\/span><\/p>\n\r<p class=\"p_ControlIndent2\"><span class=\"f_ControlIndent2\">Including this special command in a <\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">*.raw<\/span><span class=\"f_ControlIndent2\"> file will cause the RAW message to be DKIM signed. This should only be used in RAW messages that you have configured to bypass the Content Filter (by starting their filenames with &quot;<\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">p<\/span><span class=\"f_ControlIndent2\">&quot; or &quot;<\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">P<\/span><span class=\"f_ControlIndent2\">&quot;). You should not use this command in normal RAW Messages that are processed through the filter. Those messages will be signed normally.<\/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\">All RAW messages that are generated by the Content Filter will use the <\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace;\">x-flag=sign<\/span><span class=\"f_Notes\"> command automatically.<\/span><\/p>\n\r<\/td>\n\r<\/tr>\n\r<\/table>\n\r<\/div>\n\r<h2 class=\"p_Heading2\" style=\"page-break-after: avoid;\"><a id=\"sample-raw-mail-messages\" class=\"hmanchor\"><\/a><span class=\"f_Heading2\">Sample RAW mail messages<\/span><\/h2>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid; margin: 0.3125rem 0.3125rem 0.3750rem 2.1250rem;\"><span class=\"f_ControlHeading\">Sample 1:<\/span><\/p>\n\r<p class=\"p_Code2\"><span class=\"f_Code2\">from &lt;mdaemon@altn.com&gt;<\/span><\/p>\n\r<p class=\"p_Code2\"><span class=\"f_Code2\">to &lt;user01@example.com&gt;<\/span><\/p>\n\r<p class=\"p_Code2\"><span class=\"f_Code2\">&nbsp;<\/span><\/p>\n\r<p class=\"p_Code2_LastItem\"><span class=\"f_Code2_LastItem\">Hello John!<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid; margin: 0.3125rem 0.3125rem 0.3750rem 2.1250rem;\"><span class=\"f_ControlHeading\">Sample 2:<\/span><\/p>\n\r<p class=\"p_Code2\"><span class=\"f_Code2\">from &lt;user01@example.com&gt;<\/span><\/p>\n\r<p class=\"p_Code2\"><span class=\"f_Code2\">to &lt;user09@example.net&gt;<\/span><\/p>\n\r<p class=\"p_Code2\"><span class=\"f_Code2\">subject &lt;Requested Files&gt;<\/span><\/p>\n\r<p class=\"p_Code2\"><span class=\"f_Code2\">X-FLAG=CONFIRM_DELIVERY<\/span><\/p>\n\r<p class=\"p_Code2_LastItem\"><span class=\"f_Code2_LastItem\">X-FLAG=ATTACH &lt;c:\\docs\\files\\data01.zip, MIME&gt; -X<\/span><\/p>\n\r<p class=\"p_Code2_LastItem\"><span class=\"f_Code2_LastItem\">Here are all those files you asked for.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">&nbsp;<\/span><\/p>\n\r"
})
