| 1 |
<HTML> |
| 2 |
<HEAD> |
| 3 |
<TITLE>MHonArc FAQ: Supported Environments</TITLE></HEAD> |
| 4 |
<link rel="stylesheet" type="text/css" href="../docstyles.css"> |
| 5 |
<BODY> |
| 6 |
|
| 7 |
<!--X-NavButtons-Start--> |
| 8 |
<table width="100%"><tr><td align="left"><nobr>[<a href="general.html">Prev</a>]</nobr></td><td align="center" width="100%">[<a href="faq.html">TOC</a>][<a href="../mhonarc.html">Manual</a>][<a href="http://www.mhonarc.org/">Home</a>]</td><td align="right"><nobr>[<a href="usage.html">Next</a>]</nobr></td></tr></table> |
| 9 |
</p> |
| 10 |
<!--X-NavButtons-End--> |
| 11 |
|
| 12 |
<!-- ===================================================================== --> |
| 13 |
<HR> |
| 14 |
<H2><a name="supenvs">Supported Environments</a></H2> |
| 15 |
|
| 16 |
<!--X-TOC-Start--> |
| 17 |
<ul> |
| 18 |
<li><a href="#platforms">What platforms can MHonArc run under?</a></li> |
| 19 |
<li><a href="#mac">What about Mac?</a></li> |
| 20 |
<li><a href="#vms">What about VMS?</a></li> |
| 21 |
<li><a href="#perl">What version of Perl is required to run MHonArc?</a></li> |
| 22 |
<li><a href="#muas">What mail user agents (MUA's) does MHonarc support?</a></li> |
| 23 |
<li><a href="#mdomodigests">Can MHonArc process Majordomo digests?</a></li> |
| 24 |
<li><a href="#listprocessor">Can MHonArc process Listprocessor archives?</a></li> |
| 25 |
<li><a href="#ezmlm">Can MHonArc process ezmlm archives?</a></li> |
| 26 |
<li><a href="#maildir">Can MHonArc process qmail's maildir style mail folders?</a></li> |
| 27 |
<li><a href="#netscape">Can MHonArc process Netscape Messenger folders?</a></li> |
| 28 |
<li><a href="#evolution">Can MHonArc process Evolution folders?</a></li> |
| 29 |
<li><a href="#compuserve">Can MHonArc process Compuserve messages?</a></li> |
| 30 |
<li><a href="#otherformats">What about other mailbox/folder formats?</a></li> |
| 31 |
<li><a href="#nonenglish">Can MHonArc create non-English archives?</a></li> |
| 32 |
<li><a href="#japanese">How about Japanese?</a></li> |
| 33 |
<li><a href="#bilingual">Can I create bilingual archives?</a></li> |
| 34 |
<li><a href="#unicode">Does MHonArc support Unicode?</a></li> |
| 35 |
</ul> |
| 36 |
<!--X-TOC-End--> |
| 37 |
|
| 38 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 39 |
<hr noshade size=1> |
| 40 |
<table border=0> |
| 41 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 42 |
<h3><b><a name="platforms">What platforms can MHonArc run under?</a></b></h3> |
| 43 |
</td></tr></table> |
| 44 |
|
| 45 |
<P>MHonArc is known to run under Unix-based operating systems, |
| 46 |
MS-DOS/Windows, WinNT, Win95/98, and OS/2. If Perl is available for |
| 47 |
the system you are using, you can probably run MHonArc. |
| 48 |
</p> |
| 49 |
|
| 50 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 51 |
<hr noshade size=1> |
| 52 |
<table border=0> |
| 53 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 54 |
<h3><b><a name="mac">What about Mac?</a></b></h3> |
| 55 |
</td></tr></table> |
| 56 |
|
| 57 |
<p>For OS X users, MHonArc can be used from the command-line in |
| 58 |
the same manner as a Unix-based system. |
| 59 |
<a href="http://liepins.net/">Lasar Liepins</a> provides an |
| 60 |
<a href="http://liepins.org/mhonarc/">installer</a> |
| 61 |
and a <a href="http://liepins.org/macmhonarc/">graphical front-end</a> for |
| 62 |
OS X. |
| 63 |
<p> |
| 64 |
|
| 65 |
<p>For MacPerl users, MHonArc has been coded to support MacPerl. |
| 66 |
A couple of users have reported success in running MHonArc under MacPerl. |
| 67 |
Try it out, and if you have problems, send a message |
| 68 |
to the |
| 69 |
<a href="http://www.mhonarc.org/archive/info/mhonarc-users.html" |
| 70 |
>MHonArc user's list</a>. |
| 71 |
</P> |
| 72 |
|
| 73 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 74 |
<hr noshade size=1> |
| 75 |
<table border=0> |
| 76 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 77 |
<h3><b><a name="vms">What about VMS?</a></b></h3> |
| 78 |
</td></tr></table> |
| 79 |
|
| 80 |
<P>The following includes information from Walter F.J. Mueller, |
| 81 |
<a href="mailto:W.F.J.Mueller%40gsi.de">W.F.J.Mueller<!-- |
| 82 |
-->@<!-- |
| 83 |
-->gsi.de</a>: |
| 84 |
</P> |
| 85 |
<pre> |
| 86 |
* The -outdir argument must be specified UNIX style. |
| 87 |
* Avoid any $ in a filename, some interpolation will certainly mess it up. |
| 88 |
It ended up defining a few extra logicals like |
| 89 |
$ define kp3_root kp3$root |
| 90 |
to have $ free absolute pathnames in the usual $-prone VMS environment. |
| 91 |
</pre> |
| 92 |
<p>Also, you will need to use Perl 5.004_04 or later and MHonArc |
| 93 |
v2.1.1 or later. |
| 94 |
</p> |
| 95 |
|
| 96 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 97 |
<hr noshade size=1> |
| 98 |
<table border=0> |
| 99 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 100 |
<h3><b><a name="perl">What version of Perl is required to run MHonArc?</a></b></h3> |
| 101 |
</td></tr></table> |
| 102 |
|
| 103 |
<p>Perl 5, or later. Older versions of MHonArc are Perl 4 compatible. |
| 104 |
So if you are under the unfortunate circumstances of only being able |
| 105 |
to use Perl 4, you will need to grab an older version of MHonArc. |
| 106 |
</p> |
| 107 |
|
| 108 |
<p>Perl 5 is required for MHonArc v2.3 or later. The last Perl 4 |
| 109 |
compatible release is v2.2. |
| 110 |
</p> |
| 111 |
|
| 112 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 113 |
<hr noshade size=1> |
| 114 |
<table border=0> |
| 115 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 116 |
<h3><b><a name="muas">What mail user agents (MUA's) does MHonarc support?</a></b></h3> |
| 117 |
</td></tr></table> |
| 118 |
|
| 119 |
<p>The question is better stated as: <b>"What mail message storage formats |
| 120 |
MHonArc support?"</b></p> |
| 121 |
|
| 122 |
<P>MHonArc can convert mail that is stored in UUCP mailbox |
| 123 |
format (ie. all messages are in a single file), or in the format used |
| 124 |
by the |
| 125 |
<a href="http://www.ics.uci.edu/~mh/">Rand Message Handler</a> |
| 126 |
(MH) (messages are contained in separate |
| 127 |
files within a directory). MHonArc is known to work with |
| 128 |
the following MUAs: <EM>MH/nmh</EM>, <EM>mail</EM>, <EM>Mail</EM>, |
| 129 |
<EM>Elm</EM>, <EM>Eudora</EM>, <EM>WinVN</EM>, <EM>Windows |
| 130 |
Trumpet</EM>, and <EM>NUPop</EM>. </P> |
| 131 |
|
| 132 |
<table class="note" width="100%"> |
| 133 |
<tr valign="baseline"> |
| 134 |
<td><strong>NOTE:</strong></td> |
| 135 |
<td width="100%"><p> |
| 136 |
To support some MUA's, it may require redefining the |
| 137 |
<a href="../resources/msgsep.html">MSGSEP</a> or |
| 138 |
<a href="../resources/mhpattern.html">MHPATTERN</a> |
| 139 |
resource. Please consult the documentation |
| 140 |
for more information about these resources. |
| 141 |
</p> |
| 142 |
</td> |
| 143 |
</tr> |
| 144 |
</table> |
| 145 |
|
| 146 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 147 |
<hr noshade size=1> |
| 148 |
<table border=0> |
| 149 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 150 |
<h3><b><a name="mdomodigests">Can MHonArc process Majordomo digests?</a></b></h3> |
| 151 |
</td></tr></table> |
| 152 |
|
| 153 |
<p>Here is a couple messages from the |
| 154 |
<A HREF="http://www.rosat.mpe-garching.mpg.de/mailing-lists/mhonarc/" |
| 155 |
>MHonArc mailing list</A>: |
| 156 |
</p> |
| 157 |
<BLOCKQUOTE class="mail"> |
| 158 |
<UL> |
| 159 |
<LI><em>Subject</em>: Re: Majordomo Digest -> MHonarc?</LI> |
| 160 |
<LI><em>From</em>: "Christopher P. Lindsey" <<A HREF="mailto:lindsey%40mallorn.com">lindsey<!-- |
| 161 |
-->@<!-- |
| 162 |
-->mallorn.com</A>></LI> |
| 163 |
<LI><em>Date</em>: Sun, 4 Jan 1998 22:33:31 -0600 (CST)</LI> |
| 164 |
<LI><em>List-Name</em>: mhonarc</LI> |
| 165 |
</UL> |
| 166 |
<PRE> |
| 167 |
> Hi... |
| 168 |
> |
| 169 |
> Has anyone come up with a relatively clean method of converting |
| 170 |
> majordomo digests to a mailbox format that MHonarc can read? |
| 171 |
> |
| 172 |
> I was looking at it, and from what I can see its just a matter of |
| 173 |
> changing the file so that there is a From <> line at the top of each |
| 174 |
> message, so that something like: |
| 175 |
|
| 176 |
If you have the procmail package, formail should do it for you. |
| 177 |
|
| 178 |
formail -ds < digestfile >> newmailbox |
| 179 |
|
| 180 |
It auto-generates the initial 'From ' header. Unfortunately, it |
| 181 |
also leaves the original digest message (probably). If it's the |
| 182 |
first message output, do this: |
| 183 |
|
| 184 |
formail +1 -ds < digestfile >> newmailbox |
| 185 |
|
| 186 |
This tells formail to skip the first message (the one that came from |
| 187 |
list-digest-owner or whatever). |
| 188 |
|
| 189 |
Chris |
| 190 |
</PRE> |
| 191 |
</BLOCKQUOTE> |
| 192 |
<BLOCKQUOTE class="mail"> |
| 193 |
<UL> |
| 194 |
<LI><em>Subject</em>: Majordomo Digests to mbox format for MHonarc (perl script)</LI> |
| 195 |
<LI><em>From</em>: The Hermit Hacker <<A HREF="mailto:scrappy%40hub.org">scrappy<!-- |
| 196 |
-->@<!-- |
| 197 |
-->hub.org</A>></LI> |
| 198 |
<LI><em>Date</em>: Sun, 4 Jan 1998 23:44:43 -0400 (AST)</LI> |
| 199 |
<LI><em>List-Name</em>: mhonarc</LI> |
| 200 |
</UL> |
| 201 |
<PRE> |
| 202 |
Hi... |
| 203 |
|
| 204 |
I've searched the archives for some brain dead simple way of bring in old |
| 205 |
digests so that MHonarc can use them, and couldn't find anything but some |
| 206 |
references to procmail and -msgsep...nothing which seemed to work "easily"... |
| 207 |
|
| 208 |
So, here is my contribution...a simple, brain dead script that takes a |
| 209 |
Majordomo digest and converts it to a format that can be used by MHonarc... |
| 210 |
I don't guarantee it, but if anyone can suggest what is wrong with it, I'd |
| 211 |
like to know and try to fix it |
| 212 |
|
| 213 |
Just run it as: <scriptname> <infile> > <outfile> |
| 214 |
|
| 215 |
Marc G. Fournier |
| 216 |
Systems Administrator <!-- |
| 217 |
-->@<!-- |
| 218 |
--> hub.org |
| 219 |
primary: scrappy<!-- |
| 220 |
-->@<!-- |
| 221 |
-->hub.org secondary: scrappy<!-- |
| 222 |
-->@<!-- |
| 223 |
-->{freebsd|postgresql}.org |
| 224 |
|
| 225 |
#!/usr/local/bin/perl |
| 226 |
$userid = getlogin(); |
| 227 |
|
| 228 |
$ii = 0; |
| 229 |
while (<>) { |
| 230 |
if($printline) { |
| 231 |
$line{$ii} = $_; |
| 232 |
$ii++; |
| 233 |
} |
| 234 |
if (/^----------------------------------------------------------------------/) { |
| 235 |
$printline = 1; |
| 236 |
$line{$ii} = "------------------------------"; |
| 237 |
$ii++; |
| 238 |
} |
| 239 |
} |
| 240 |
|
| 241 |
for($jj = 0; $jj < $ii; $jj++) { |
| 242 |
if(/^------------------------------/, $line{$jj}) { |
| 243 |
if($line{$jj+2} =~ "^Date:") { |
| 244 |
print "From $userid\n"; |
| 245 |
$jj += 2; |
| 246 |
} else { |
| 247 |
if($line{$jj+2} =~ "^End of") { |
| 248 |
exit; |
| 249 |
} |
| 250 |
} |
| 251 |
} |
| 252 |
print $line{$jj}; |
| 253 |
} |
| 254 |
|
| 255 |
</PRE> |
| 256 |
</BLOCKQUOTE> |
| 257 |
|
| 258 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 259 |
<hr noshade size=1> |
| 260 |
<table border=0> |
| 261 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 262 |
<h3><b><a name="listprocessor">Can MHonArc process Listprocessor archives?</a></b></h3> |
| 263 |
</td></tr></table> |
| 264 |
|
| 265 |
<p>An answer from a MHonArc user: |
| 266 |
</p> |
| 267 |
<blockquote class="mail"> |
| 268 |
<UL> |
| 269 |
<LI><em>To</em>: <A HREF="mailto:mhonarc%40rosat.mpe-garching.mpg.de">mhonarc<!-- |
| 270 |
-->@<!-- |
| 271 |
-->rosat.mpe-garching.mpg.de</A></LI> |
| 272 |
<LI><em>Subject</em>: re: digest to mbox</LI> |
| 273 |
<LI><em>From</em>: <A HREF="mailto:KMcCann%40idrc.ca">KMcCann<!-- |
| 274 |
-->@<!-- |
| 275 |
-->idrc.ca</A></LI> |
| 276 |
<LI><em>Date</em>: 12 Jun 97 09:15:27 EDT</LI> |
| 277 |
<LI><em>List-Name</em>: mhonarc</LI> |
| 278 |
</UL> |
| 279 |
<!--X-Head-Body-Sep-Begin--> |
| 280 |
<!--X-Head-Body-Sep-End--> |
| 281 |
<!--X-Body-of-Message--> |
| 282 |
<PRE> |
| 283 |
Here is a simple script I wrote to process the archives of my Listprocessor |
| 284 |
lists. |
| 285 |
|
| 286 |
#!/usr/local/bin/perl5 |
| 287 |
# |
| 288 |
# mhonarch.pl - Process all Listprocessor archives using MHonArc |
| 289 |
# |
| 290 |
# Kevin McCann |
| 291 |
# |
| 292 |
#### Directory locations: |
| 293 |
# |
| 294 |
# Listproc, Majordomo, or Listserv top archives dir |
| 295 |
$ARCHDIR = "/usr/server/archives"; |
| 296 |
# |
| 297 |
# MhonArch web archives directory |
| 298 |
$MONDIR = "/u/www/htdocs/listproc/mhonarc"; |
| 299 |
# |
| 300 |
## Let's figure out what lists exist |
| 301 |
opendir(DIR,"$ARCHDIR/") || die "Can't open directory"; |
| 302 |
<!-- |
| 303 |
-->@<!-- |
| 304 |
-->dirs = readdir(DIR); |
| 305 |
<!-- |
| 306 |
-->@<!-- |
| 307 |
-->sorteddirs = sort <!-- |
| 308 |
-->@<!-- |
| 309 |
-->dirs; |
| 310 |
closedir(DIR); |
| 311 |
for (<!-- |
| 312 |
-->@<!-- |
| 313 |
-->sorteddirs) { # processing a list |
| 314 |
$listname = $_; |
| 315 |
opendir(DIR,"$ARCHDIR/$listname") || die "Can't open directory"; |
| 316 |
<!-- |
| 317 |
-->@<!-- |
| 318 |
-->logs = readdir(DIR); |
| 319 |
<!-- |
| 320 |
-->@<!-- |
| 321 |
-->sortedlogs = sort <!-- |
| 322 |
-->@<!-- |
| 323 |
-->logs; |
| 324 |
closedir(DIR); |
| 325 |
for (<!-- |
| 326 |
-->@<!-- |
| 327 |
-->sortedlogs) { |
| 328 |
if (/log/) { # processing files with name format |
| 329 |
'logYYMM' |
| 330 |
$log = $_; |
| 331 |
|
| 332 |
system("/usr/local/bin/mhonarc -outdir $MONDIR/$listname/$log |
| 333 |
$ARCHDIR/$listname/$log") |
| 334 |
|
| 335 |
# modify the above command line as needed |
| 336 |
} |
| 337 |
} |
| 338 |
} |
| 339 |
|
| 340 |
} # end of script |
| 341 |
|
| 342 |
|
| 343 |
I processed over 100 lists that go back to 1995 with this. It took about |
| 344 |
one hour. There may be more elegant ways to do it, but this was just a |
| 345 |
quick hack to get the job done. If you are using an RCFILE, don't forget to |
| 346 |
include it in the long mhonarc command seen above. Oh, and don't forget to |
| 347 |
change the first line that specifies your Perl location if you need to - |
| 348 |
mine is set to /usr/local/bin/perl5. |
| 349 |
|
| 350 |
Good luck! |
| 351 |
|
| 352 |
- Kevin McCann |
| 353 |
kmccann<!-- |
| 354 |
-->@<!-- |
| 355 |
-->idrc.ca |
| 356 |
www.cruciverb.com |
| 357 |
</PRE> |
| 358 |
</blockquote> |
| 359 |
|
| 360 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 361 |
<hr noshade size=1> |
| 362 |
<table border=0> |
| 363 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 364 |
<h3><b><a name="ezmlm">Can MHonArc process ezmlm archives?</a></b></h3> |
| 365 |
</td></tr></table> |
| 366 |
|
| 367 |
<p>From what I read from the <b>ezmlm(5)</b> manpage, the following example |
| 368 |
command will process all messages of list: |
| 369 |
</p> |
| 370 |
<pre class="shell"> |
| 371 |
prompt> <b>mhonarc <var>/list/archive/</var>[0-9]*</b> |
| 372 |
</pre> |
| 373 |
<p>Replace "<tt>/list/archive/</tt>" to what is appropriate for your |
| 374 |
configuration. |
| 375 |
</p> |
| 376 |
<p>Basically, each numeric subdirectory in the "<var>archive</var>" directory |
| 377 |
follows the same format as MH mail directories. |
| 378 |
</p> |
| 379 |
<p>If you are using a shell that cannot handle "<tt>[0-9]*</tt>", the following |
| 380 |
should work: |
| 381 |
</p> |
| 382 |
<pre class="shell"> |
| 383 |
prompt> <b>mhonarc `find <var>/list/archive/</var> -type d -name '[0-9]*' -print`</b> |
| 384 |
</pre> |
| 385 |
<p>Note, make sure to add any additional options to mhonarc as needed |
| 386 |
to get the effects you desire. |
| 387 |
</p> |
| 388 |
|
| 389 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 390 |
<hr noshade size=1> |
| 391 |
<table border=0> |
| 392 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 393 |
<h3><b><a name="maildir">Can MHonArc process qmail's maildir style mail folders?</a></b></h3> |
| 394 |
</td></tr></table> |
| 395 |
|
| 396 |
<p>For simplicity, let "<var>MAILDIR</var>" represent the pathname |
| 397 |
to your qmail mail directory. |
| 398 |
</p> |
| 399 |
<p>To have mhonarc process <var>MAILDIR</var>, |
| 400 |
you pass "<var>MAILDIR</var><tt>/cur</tt>" and/or |
| 401 |
"<var>MAILDIR</var><tt>/new</tt>" as the mail folder arguments. |
| 402 |
Which subdirectory you choose to use depends on your needs. |
| 403 |
</p> |
| 404 |
<p>Also, you will need to define the MHPATTERN resource to process |
| 405 |
all non-dotfiles. Example: |
| 406 |
</p> |
| 407 |
<pre class="shell"> |
| 408 |
prompt> <b>mhonarc -mhpattern '^[^\.]' <var>MAILDIR</var>/cur</b> |
| 409 |
</pre> |
| 410 |
<p>If all you will ever do is process qmail maildir folders, it may be best |
| 411 |
to set the M2H_MHPATTERN environment variable so you do not have |
| 412 |
to respecify each time you invoke mhonarc. Examples: |
| 413 |
</p> |
| 414 |
<dl> |
| 415 |
<dt>csh: |
| 416 |
<dd><b><tt class="ishell">setenv M2H_MHPATTERN '^[^\.]'</tt></b> |
| 417 |
<dt>sh: |
| 418 |
<dd><b><tt class="ishell">M2H_MHPATTERN='^[^\.]'; export M2H_MHPATTERN</tt></b> |
| 419 |
</dl> |
| 420 |
|
| 421 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 422 |
<hr noshade size=1> |
| 423 |
<table border=0> |
| 424 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 425 |
<h3><b><a name="netscape">Can MHonArc process Netscape Messenger folders?</a></b></h3> |
| 426 |
</td></tr></table> |
| 427 |
|
| 428 |
<p>Yes. Each Netscape Messenger folder has a corresponding mailbox file |
| 429 |
that stores the raw mail messages for the folder. The location |
| 430 |
of the mailbox file will be in your mail directory. Under Unix, this |
| 431 |
is normally <b><tt>$HOME/nsmail</tt></b>. For Windows, this is |
| 432 |
typically |
| 433 |
<b><tt>C:\Program Files\Netscape\Users\<var><username></var>\Mail</tt></b>. |
| 434 |
</p> |
| 435 |
|
| 436 |
<p>For each Netscape folder, there are two files: |
| 437 |
<b><tt><i><folder-name></i></tt></b> and |
| 438 |
<b><tt><i><folder-name></i>.summary</tt></b> (or |
| 439 |
<b><tt><i><folder-name></i>.snm</tt></b> under Windows). |
| 440 |
The <b><tt>.summary</tt></b> can be ignored with respect to MHonArc. |
| 441 |
The other file contains the raw mail messages and can be passed |
| 442 |
directly to MHonArc for processing. For example, to process all the |
| 443 |
mail in your Inbox, do something like the following: |
| 444 |
</p> |
| 445 |
<pre class="shell"> |
| 446 |
prompt> <b>mhonarc $HOME/nsmail/Inbox</b> |
| 447 |
</pre> |
| 448 |
|
| 449 |
<p>Note, you may need to compress/compact folders in Netscape before |
| 450 |
running MHonArc. If not, messages you have deleted from a folder may |
| 451 |
show up in the archive create by MHonArc. |
| 452 |
</p> |
| 453 |
|
| 454 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 455 |
<hr noshade size=1> |
| 456 |
<table border=0> |
| 457 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 458 |
<h3><b><a name="evolution">Can MHonArc process Evolution folders?</a></b></h3> |
| 459 |
</td></tr></table> |
| 460 |
|
| 461 |
<p>Yes. Each Evolution folder has a corresponding mailbox file |
| 462 |
that stores the raw mail messages for the folder. The location |
| 463 |
of the mailbox file will be in your mail directory which is |
| 464 |
typically <b><tt>$HOME/evolution/local/<em>folder-name</em></tt></b>. |
| 465 |
In the directory is a file called <tt>mbox</tt> which contains |
| 466 |
the raw messages that can be passed into MHonArc directly. |
| 467 |
</p> |
| 468 |
|
| 469 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 470 |
<hr noshade size=1> |
| 471 |
<table border=0> |
| 472 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 473 |
<h3><b><a name="compuserve">Can MHonArc process Compuserve messages?</a></b></h3> |
| 474 |
</td></tr></table> |
| 475 |
|
| 476 |
<p>Here is a response from a user: |
| 477 |
</p> |
| 478 |
<blockquote class="mail"> |
| 479 |
<UL> |
| 480 |
<LI><em>Subject</em>: Re: CompuServe --> html</LI> |
| 481 |
<LI><em>From</em>: Steve Pacenka <<A HREF="mailto:sp17%40cornell.edu">sp17<!-- |
| 482 |
-->@<!-- |
| 483 |
-->cornell.edu</A>></LI> |
| 484 |
<LI><em>Date</em>: Thu, 06 Mar 1997 09:09:00 -0500</LI> |
| 485 |
</UL> |
| 486 |
<PRE> |
| 487 |
At 11:38 AM 3/6/97 +0100, Bernard Frit wrote: |
| 488 |
><i>Hi everybody,</i> |
| 489 |
> |
| 490 |
><i>A friend of mine has a lot of archives in CompuServe</i> |
| 491 |
><i>thread and message format. He'd like to convert them</i> |
| 492 |
><i>in a convenient format (html or whatever) with thread</i> |
| 493 |
><i>indexing features as MHonArc is doing it for mail</i> |
| 494 |
><i>archives.</i> |
| 495 |
> |
| 496 |
><i>At the first glance, I didn't find out how to configure</i> |
| 497 |
><i>MHonArc to do the job.</i> |
| 498 |
|
| 499 |
The Compuserve "file cabinet" format is too far from the basic SMTP message |
| 500 |
format that MHonArc recognizes. |
| 501 |
|
| 502 |
Your friend can find software on Compuserve to read the file cabinet format |
| 503 |
and emit ascii text that is closer to SMTP message format that MHonArc can |
| 504 |
use. A search of IBMFF using the keywords "cabinet" and "convert" yielded |
| 505 |
several items including these two: |
| 506 |
|
| 507 |
Forum Name: CSNAVSUPPORT Library: Member Uploads (6) |
| 508 |
Accesses: 839 Size: 11368 |
| 509 |
File: THRDCO.ZIP Submitted: [72662,70] 26-Aug-94 |
| 510 |
|
| 511 |
|
| 512 |
This program converts forum message threads to a plain text file called |
| 513 |
COLLECT.TXT. Your favorite word processor can then search for any message |
| 514 |
on any topic that you have downloaded. It is public domain and was |
| 515 |
created because I have so many forum thread messages which I can't search. |
| 516 |
|
| 517 |
----- |
| 518 |
Forum Name: PCEFORUM Library: Telecom/Reseaux (8) |
| 519 |
Accesses: 32 Size: 30865 |
| 520 |
File: SHWCIM.ZIP Submitted: [72241,2132] 08-Nov-96 |
| 521 |
|
| 522 |
Une fois stockes dans le "Cabinet" CompuServe, les messages des forums et |
| 523 |
les courriers sont codes dans des fichiers binaires que l'on ne peut pas |
| 524 |
relire directement. Cet utilitaire a pour but de convertir n'importe quel |
| 525 |
fichier de la base WinCIM en fichier ASCII pur. Freeware en anglais. |
| 526 |
|
| 527 |
-- SP |
| 528 |
|
| 529 |
</PRE> |
| 530 |
</blockquote> |
| 531 |
|
| 532 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 533 |
<hr noshade size=1> |
| 534 |
<table border=0> |
| 535 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 536 |
<h3><b><a name="otherformats">What about other mailbox/folder formats?</a></b></h3> |
| 537 |
</td></tr></table> |
| 538 |
|
| 539 |
<p>The common technique is to convert the foreign format into |
| 540 |
a format recognized by MHonArc: UUCP mailbox or MH mail folders. The |
| 541 |
conversion can also rely on the usage of the MSGSEP and MHPATTERN |
| 542 |
resources to make conversion potentially easier. |
| 543 |
</p> |
| 544 |
|
| 545 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 546 |
<hr noshade size=1> |
| 547 |
<table border=0> |
| 548 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 549 |
<h3><b><a name="nonenglish">Can MHonArc create non-English archives?</a></b></h3> |
| 550 |
</td></tr></table> |
| 551 |
|
| 552 |
<p>Yes. With MHonArc's page layout customizations features, |
| 553 |
you can have MHonArc create pages in any language supported |
| 554 |
by Web client software. Plus, messages containing non-English text |
| 555 |
is supported during message conversion via the CHARSETCONVERTERS |
| 556 |
resource. |
| 557 |
</p> |
| 558 |
|
| 559 |
<dl> |
| 560 |
<dt>See also:</dt> |
| 561 |
<dd><a href="#unicde" |
| 562 |
>Does MHonArc support Unicode?</a></dd> |
| 563 |
</dl> |
| 564 |
|
| 565 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 566 |
<hr noshade size=1> |
| 567 |
<table border=0> |
| 568 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 569 |
<h3><b><a name="japanese">How about Japanese?</a></b></h3> |
| 570 |
</td></tr></table> |
| 571 |
|
| 572 |
<p>Yes. For details about Japanese usage of MHonArc, goto: |
| 573 |
<a href="http://www.mhonarc.jp/"><http://www.mhonarc.jp/></a> |
| 574 |
(documents are in Japanese). |
| 575 |
</p> |
| 576 |
|
| 577 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 578 |
<hr noshade size=1> |
| 579 |
<table border=0> |
| 580 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 581 |
<h3><b><a name="bilingual">Can I create bilingual archives?</a></b></h3> |
| 582 |
</td></tr></table> |
| 583 |
|
| 584 |
<p>Yes. You can actually create archives that have as many |
| 585 |
indexes as you want in as many languages that you want. Through |
| 586 |
the OTHERINDEXES resource can define any number of extra indexes |
| 587 |
to create. For each index, you can redfine the index resources |
| 588 |
to use whatever text (English or non-English) you desire. |
| 589 |
</p> |
| 590 |
<table class="note" width="100%"> |
| 591 |
<tr valign="baseline"> |
| 592 |
<td><strong>NOTE:</strong></td> |
| 593 |
<td width="100%"><p> |
| 594 |
There is no support for mulitple variations of message |
| 595 |
pages in an archive. Therefore, a single language must be |
| 596 |
chosen for message pages, or you can include redundant information |
| 597 |
using multiple languages. |
| 598 |
</p> |
| 599 |
</td> |
| 600 |
</tr> |
| 601 |
</table> |
| 602 |
<p> </p> |
| 603 |
<table class="note" width="100%"> |
| 604 |
<tr valign="baseline"> |
| 605 |
<td><strong>NOTE:</strong></td> |
| 606 |
<td width="100%"><p> |
| 607 |
Actual message data will be in the language used in the |
| 608 |
message. MHonArc has no built-in language translation. |
| 609 |
</p> |
| 610 |
</td> |
| 611 |
</tr> |
| 612 |
</table> |
| 613 |
|
| 614 |
<dl> |
| 615 |
<dt>See also:</dt> |
| 616 |
<dd><a href="#unicde" |
| 617 |
>Does MHonArc support Unicode?</a></dd> |
| 618 |
</dl> |
| 619 |
|
| 620 |
<!-- ??????????????????????????????????????????????????????????????? --> |
| 621 |
<hr noshade size=1> |
| 622 |
<table border=0> |
| 623 |
<tr valign=baseline><td><img src="monicon.png" align="bottom" alt=""></td><td> |
| 624 |
<h3><b><a name="unicode">Does MHonArc support Unicode?</a></b></h3> |
| 625 |
</td></tr></table> |
| 626 |
|
| 627 |
<p>Yes. Check out the following for more information: |
| 628 |
</p> |
| 629 |
<ul> |
| 630 |
<li><a href="../resources/textencode.html">TEXTENCODE</a> |
| 631 |
resource.</li> |
| 632 |
<li><a href="../resources/charsetconverters.html">CHARSETCONVERTERS</a> |
| 633 |
resource.</li> |
| 634 |
<li><a href="../rcfileexs/utf-8-encode.mrc.html"><tt>utf-8-enocde.mrc</tt></a> |
| 635 |
and <a href="../rcfileexs/utf-8.mrc.html"><tt>utf-8.mrc</tt></a> |
| 636 |
resource file examples.</li> |
| 637 |
</ul> |
| 638 |
|
| 639 |
<!-- ===================================================================== --> |
| 640 |
<hr> |
| 641 |
|
| 642 |
<!--X-NavButtons-Start--> |
| 643 |
<table width="100%"><tr><td align="left"><nobr>[<a href="general.html">Prev</a>]</nobr></td><td align="center" width="100%">[<a href="faq.html">TOC</a>][<a href="../mhonarc.html">Manual</a>][<a href="http://www.mhonarc.org/">Home</a>]</td><td align="right"><nobr>[<a href="usage.html">Next</a>]</nobr></td></tr></table> |
| 644 |
</p> |
| 645 |
<!--X-NavButtons-End--> |
| 646 |
|
| 647 |
<hr> |
| 648 |
<address> |
| 649 |
$Date: 2011/01/01 02:43:26 $ <br> |
| 650 |
<img align="top" src="monicon.png" alt=""> |
| 651 |
<a href="http://www.mhonarc.org/" |
| 652 |
><strong>MHonArc</strong></a><br> |
| 653 |
Copyright © 1997-1999, <a href="http://www.earlhood.com/" |
| 654 |
>Earl Hood</a>, <a href="mailto:mhonarc%40mhonarc.org" |
| 655 |
>mhonarc<!-- |
| 656 |
-->@<!-- |
| 657 |
-->mhonarc.org</a><br> |
| 658 |
</address> |
| 659 |
</body> |
| 660 |
</html> |