view release on metacpan or  search on metacpan

doc/faq/msgpgs.html  view on Meta::CPAN

<b>&lt;<a href="../resources/fieldsbeg.html">FIELDSBEG</a>&gt;</b>
&lt;table&gt;
<b>&lt;/FIELDSBEG&gt;</b>
<b>&lt;<a href="../resources/labelbeg.html">LABELBEG</a>></b>
&lt;tr&gt;
&lt;td align="right" valign="top"&gt;
<b>&lt;/LABELBEG&gt;</b>
<b>&lt;<a href="../resources/labelend.html">LABELEND</a>&gt;</b>
&lt;/td&gt;
<b>&lt;/LABELEND&gt;</b>
<b>&lt;<a href="../resources/fldbeg.html">FLDBEG</a>&gt;</b>
&lt;td align="left"&gt;
<b>&lt;/FLDBEG&gt;</b>
<b>&lt;<a href="../resources/fldend.html">FLDEND</a>&gt;</b>
&lt;/td&gt;
&lt;/tr&gt;
<b>&lt;/FLDEND&gt;</b>
<b>&lt;<a href="../resources/fieldsend.html">FIELDSEND</a>&gt;</b>
&lt;/table&gt;
<b>&lt;/FIELDSEND&gt;</b>
</pre>

<p>You can also control the order message fields are displayed:
</p>
<pre class="code">
<b>&lt;<a href="../resources/fieldorder.html">FIELDORDER</a>&gt;</b>
from
subject
date
-extra-
<b>&lt;/FIELDORDER&gt;</b>
</pre>
<p>The "-extra-" signifies all other message fields in alphabetic
order.
</p>

<p>You can also exclude specific message fields:
</p>
<pre class="code">
<b>&lt;<a href="../resources/excs.html">EXCS</a>&gt;</b>
x-
precendence
<b>&lt;/EXCS&gt;</b>
</pre>
<p>Here, we are exluding all "X-..." fields and the Precendence
field.
</p>

<p>Consult the MHonArc documentation for more information
on how to use the resources shown here and other resources for
controlling message header formatting.
</p>

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td>
<h3><b><a name="msgbody">How can I change how message body data gets formatted?</a></b></h3>
</td></tr></table>

<p>Message body conversion are controlled by content-type filters.
See the <a href="mime.html">MIME</a> section of this FAQ for
more information.
</p>

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td>
<h3><b><a name="headnbody">Can I have the message header come after the body?</a></b></h3>
</td></tr></table>

<p>In general, no.  A limitation of MHonArc is that you cannot change
the relative order of the resources/message-data in the output (but see
other questions in this section).  MHonArc expects
a specific order so it can edit archived messages when needed w/o
using a bunch of logic and performance degradation (special comment
declarations are used to mark off the different sections of a message).
Therefore, you cannot have the body come before the message header.
The best you can do is suppress the header (via <a href="../resources/excs.html">EXCS</a>) and create a
bogus header via the resource variables available.  For example:
</p>
<pre class="code">
<b>&lt;<a href="../resources/excs.html">EXCS</a> override&gt;</b>
.
<b>&lt;/EXCS&gt;</b>
<b>&lt;<a href="../resources/msgfoot.html">MSGFOOT</a>&gt;</b>
&lt;ul&gt;
&lt;li&gt;From: $FROM$
&lt;li&gt;Subject: $SUBJECTNA$
&lt;li&gt;Date: $DATE$
&lt;ul&gt;
<b>&lt;/MSGFOOT&gt;</b>
</pre>

<p>In v2.6, you can include additional header fields by using the
<a href="../resources/fieldstore.html">FIELDSTORE</a> resource
and the <tt>$MSGHFIELD$</tt> resource variable.  For example, say
you want to include the <tt>To:</tt> field in the previous example.
You can do the following:
</p>
<pre class="code">
<b>&lt;<a href="../resources/excs.html">EXCS</a> override&gt;</b>
.
<b>&lt;/EXCS&gt;</b>
<b>&lt;<a href="../resources/fieldstore.html">FIELDSTORE</a>&gt;</b>
to
<b>&lt;/FIELDSTORE&gt;</b>
<b>&lt;<a href="../resources/msgfoot.html">MSGFOOT</a>&gt;</b>
&lt;ul&gt;
&lt;li&gt;To: $MSGHFIELD(CUR;to)$
&lt;li&gt;From: $FROM$
&lt;li&gt;Subject: $SUBJECTNA$
&lt;li&gt;Date: $DATE$
&lt;ul&gt;
<b>&lt;/MSGFOOT&gt;</b>
</pre>

<!-- ??????????????????????????????????????????????????????????????? -->
<hr noshade size=1>
<table border=0>