| [TOC][Manual][Home] |
|
What is MIME? |
MIME stands for Multipurpose Internet Mail Extensions. An HTML version of the RFCs that define MIME are available at (http://www.mhonarc.org/~ehood/MIME/).
In sum, MIME "redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information." [RFC 1521]
|
Does MHonArc support message header extensions for non-ASCII text? |
v2.0 or later. Review the CHARSETCONVERTERS resource page for which character sets are supported by MHonArc and how to extend MHonArc to support other character sets.
|
How can I get MHonArc to recognize content-types it states it does not recognize? |
This question can be answered by reading about the MIMEFILTERS resource of the MHonArc documentation. The solution may require registering a pre-existing filter for the given content-type, or hooking in a new filter.
| NOTE: | MHonArc treats unknown content-types as application/octet-stream for purposes of filtering. |
|
Can I override the default filters in MHonArc? |
Yes. MHonArc's default filters are hooked in as described in the MIMEFILTERS resource. Note, please review the options available for the default filters described in the MIMEFILTERS resource page since they may already provide the capabilities you need.
|
Can I override the multipart/* processing of MHonArc? |
Yes, but not recommended. Make sure you are familiar with how MHonArc does things before considering implementing your own multipart filter. In sum, you can completely replace MHonArc's filters with your own if you so desire.
|
Why are attachments saved as a ".bin" files? |
MHonArc uses the Content-Type field in messages to determine the type of data that is being processed. If data is gettings saved to a ".bin" file, it means the data has a content-type of application/octet-stream. The best solution to the problem is have the senders of the messages label the data properly. You can also check out the m2h_external::filter options documented in the MIMEFILTERS page of the documentation for some alternate solutions.
|
Can attachments get saved with the filename specified in the message header? |
Yes. See the m2h_external::filter options documented in the MIMEFILTERS page of the documentation. Make note of the security cautions in the documentation. Example:
<MIMEArgs> m2h_external::filter; usename </MIMEArgs>
|
Can the <PRE> tags be removed from converted messages? |
Yes. See the options available for the m2h_text_plain::filter described in the MIMEFILTERS resource page of the documentation. Example:
<MIMEArgs> m2h_text_plain::filter; nonfixed </MIMEArgs>
|
Can long lines be wrapped in converted messages? |
Yes. See the options available for the m2h_text_plain::filter described in the MIMEFILTERS resource page of the documentation. Example:
<-- Make sure lines are no longer than 80 characters --> <MIMEArgs> m2h_text_plain::filter; maxwidth=80 </MIMEArgs>
|
Can I exclude specific media-types? |
Yes. See the MIMEEXCS resource. Example:
<-- Exclude all HTML and binary data --> <MIMEExcs> text/html application/octet-steam </MIMEExcs>
|
Can I tell MHonArc to use the text/plain part over a text/html part in a multipart/alternative message? |
Yes, in v2.5.8, and later, via the MIMEALTPREFS resource. Example:
<MIMEAltPrefs> text/plain text/html </MIMEAltPrefs>
|
How do I exclude attachments from my archives? |
See the following archived message to the mhonarc-users list: Re: Disabling attachments.
| NOTE: | The MIMEINCS resource mentioned in the list message is available in MHonArc v2.6.12 and later. |
| [TOC][Manual][Home] |
MHonArc