The behavior of MHonArc is controled by resources.
Resources are set, or defined, by command-line options, environment
variables, or a resource file. For example, the MAXSIZE resource tells
MHonArc the maximum number of messages in an archive. To set
the resource, you can use the -maxsize
command-line option, the M2H_MAXSIZE envariable, or the
<MAXSIZE>
resource file element.
See the documentation for more information.
newgetopt.pl comes with the standard Perl distribution. Check with your sys admin on where it is located (it should be in the default Perl search path).
No, but a searching can be provided by another utility. See the MHonArc home page (http://www.oac.uci.edu/indiv/ehood/mhonarc.html) to some links to contributed programs for searching MHonArc archives. Also, any standard search engine can be used. For example, the MHonArc mailing list archive (http://www.rosat.mpe-garching.mpg.de/mailing-lists/mhonarc/) provides a Glimpse (http://glimpse.cs.arizona.edu:1994/) search engine for searching messages. For more information, see the respective documentation of the search engine software of interest.
Through MHonArc's resources, it is easy to provide a search form to whatever search utility you may use without modifying MHonArc source code.
There is no known Web interface that uses MHonArc to allow people to read incoming mail or perform archive administration function. If you know of one, please contact the author of the FAQ.
No. Once a message is archived, the original can be stored away. MHonArc preserves all relevant information in its database. For possible recovering purposes, it is recommended to preserve original messages in a storage archive. This allows you to rebuild MHonArc archives in case of data corruption.
No. The archive database stores all resource settings. The only time you need to respecify the resource file is if changes are required in the layout of the archive.
When utilizing the OTHERINDEXES resource, the resource filenames listed in the main resource file are stored in the database, but the resources for each additional index are NOT. Hence, the resource files defining the additional indexes must be accesible.
Yes. MH mail folder processing is just processing a bunch of separate message files in a directory. MHonArc uses the MHPATTERN resource to determine which files to process. Therefore, all you need to do is redefine the MHPATTERN resource and pass the directory your message files are in when invoking MHonArc.
For example, say I want to process all files in a directory called "messages". I'd do the following:
% mhonarc -mhpattern "^[^.]" messages
MHPATTERN can be any Perl regular expression. The one in the example matches any file not beginning with ".". This is to avoid the special files "." and ".." which are directories.
The other way to process individual message files is to do it one at a time. For example:
% mhonarc -add < file1.822 % mhonarc -add < file2.822 ...
Yes, but only in v2.0 or later (v2.0 beta releases do not have the capability). The syntax is something like the following:
% mhonarc [options-here] -- -
The "--" tells MHonArc to terminate all command-line option processing and treat all following arguments as mail folders. The "-" signifies to use standard input as a mailbox source.
Since MHonArc can read a mailbox from stdin, this allows MHonArc to be part of a pipeline where MHonArc takes input from some preprocessor that massages some data to make it suitable for processing by MHonArc. For example:
% mypreproc | mhonarc -- -