MHonArc
view release on metacpan or search on metacpan
doc/app-mimeconf.html view on Meta::CPAN
<li><p>At a minumum provide facilities to treat any
unrecognized subtypes as if they were
"application/octet-stream".
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>All image, audio, and video types are saved to an external file
with a link to the file created in the HTML. For applicable image types, they
are inlined unless the image has an attachment content-disposition.
</p>
</td>
</tr>
</table>
</ul>
<p>
Application:
</p>
<ul>
<li><p>Offer the ability to remove either of the quoted-printable or base64 encodings defined in this
document if they were used and put the resulting
information in a user file.
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>Most application types are decoded and saved to an external file
with a link to the file created in the HTML. Some application types
can be converted directly to HTML.
</p>
</td>
</tr>
</table>
</ul>
<p>
Multipart:
</p>
<ul>
<li><p>Recognize the mixed subtype. Display all relevant
information on the message level and the body part
header level and then display or offer to display
each of the body parts individually.
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>Yes. Each part is automatically processed according to its
media-type.
</p>
</td>
</tr>
</table>
<li><p>Recognize the "alternative" subtype, and avoid
showing the user redundant parts of
multipart/alternative mail.
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>Yes. MHonArc also provides the
<a href="resources/mimealtprefs.html">MIMEALTPREFS</a> resource to
allow users to control media-type preferences for
<tt>multipart/alternative</tt> mail.
</p>
</td>
</tr>
</table>
<li><p>Recognize the "multipart/digest" subtype,
specifically using "message/rfc822" rather than
"text/plain" as the default media type for body parts
inside "multipart/digest" entities.
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>Yes.
</p>
</td>
</tr>
</table>
<li><p>Treat any unrecognized subtypes as if they were
"mixed".
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>Yes.
</p>
</td>
</tr>
</table>
</ul>
<p>
Message:
</p>
<ul>
<li><p>Recognize and display at least the RFC822 message
encapsulation (message/rfc822) in such a way as to
preserve any recursive structure, that is, displaying
or offering to display the encapsulated data in
accordance with its media type.
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>Yes.
</p>
</td>
</tr>
</table>
<li><p>Treat any unrecognized subtypes as if they were
"application/octet-stream".
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>Yes.
</p>
</td>
</tr>
</table>
doc/app-mimeconf.html view on Meta::CPAN
begins with "=?" and ends with "?=" must be a valid
encoded-word.
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>Yes.
</p>
</td>
</tr>
</table>
<li><p>Conforming user agents must be able to distinguish
encoded-words from "text", "ctext", or "word"s,
according to the rules in section 4, anytime they
appear in appropriate places in message headers. It
must support both the "B" and "Q" encodings for any
character set which it supports. The program must be
able to display the unencoded text if the character set
is "US-ASCII". For the ISO-8859-* character sets, the
mail reading program must at least be able to display
the characters which are also in the US-ASCII set.
</p>
<table border=0 cellpadding=4>
<tr valign=top>
<td><strong><img src="monicon.png" alt="MHonArc"></strong></td>
<td><p>MHonArc supports non-ASCII encoding of text in message headers,
including the "B" and "Q" encodings. See
<a href="resources/charsetconverters.html">CHARSETCONVERTERS</a> for
a list of charsets supported.
</p>
</td>
</tr>
</table>
</ol>
<hr>
<H2><a name="otherstuff">Other Stuff Supported</a></H2>
<p>The following lists other MIME-related features supported
by MHonArc:</p>
<ul>
<li><p>Support for uuencoding as a Content-Transfer-Encoding.
</p>
</li>
<li><p>Support for many media-types (including the ability to extend
that support). For a complete list, along with more
information, see the
<a href="resources/mimefilters.html">MIMEFILTERS</a> resource.
Note, many media-types cannot be directly converted into HTML. For
these types, they are saved to a separate file with a link to the
file inserted in the converted HTML message data.
</p>
</li>
<li><p>The ability to explicitly control media-type preferences
of <tt>multipart/alternative</tt> data via the
<a href="resources/mimealtprefs.html">MIMEALTPREFS</a> resource
</p>
</li>
<li><p>Support for <b><tt>multipart/related</tt></b> by allowing
<a href="resources/mimefilters.html">filters</a> to access other
message parts via content-ids.
</p>
</li>
<li><p>Support for <b><tt>cid:</tt></b> URLs in <b><tt>text/html</tt></b>
data. The provides support for things like MHTML:
<em>MIME E-mail Encapsulation of Aggregate Documents</em>,
<a href="http://www.ietf.org/rfc/rfc2110.txt">RFC 2110</a>.
</p>
</li>
<li><p>Support for
<a href="http://www.ietf.org/rfc/rfc2369.txt">RFC 2369</a>,
<em>The Use of URLs as Meta-Syntax for Core Mail List Commands
and their Transport through Message Header Fields</em>. The
URLs in list header fields will be converted into hypertext links.
</p>
</li>
</ul>
<hr>
<!--X-NavButtons-Start-->
<table width="100%">
<tr valign="top">
<td align="left"><nobr><a href="app-api.html"><img src="prev.png"border=0 alt="[Prev]"></a> </nobr></td><td align="center" width="99%"><a href="mhonarc.html"><img src="up.png" border=0 alt="[TOC]"></a><a href="faq/faq.html"><img src=...
<!--X-NavButtons-End-->
<HR>
<address>
$Date: 2003/10/06 22:04:14 $ <br>
<img align="top" src="monicon.png" alt="">
<a href="http://www.mhonarc.org/"><strong>MHonArc</strong></a><br>
Copyright © 1999, <a href="http://www.mhonarc.org/~ehood/"
>Earl Hood</a>, <a href="mailto:mhonarc%40mhonarc.org"
>mhonarc<!--
-->@<!--
-->mhonarc.org</a><br>
</address>
</BODY>
</HTML>
( run in 0.776 second using v1.01-cache-2.11-cpan-8f98c5d2c55 )