> >You might take a look at Mhonarc, which is what we moved to after using
> >hypermail for a while). Check out the following URL for an example:
>
> why did you move?? It's look somewhat ... well simpler ... which is one reason
> to perhaps not get HyperMail going in the first place but once you had it set up
I'm not completely sure, as the conversion occurred before I took over
maintenance of lists this year. However, I asked the previous list
archive maintainer why he switched from hypermail, and here's what he came
up with:
<quote>
yeah - about every week or so hypermail would choke inexplicably on an
archived message's header and coredump every time a new message arrived
and it had to recompile the index (!). As the docs explicitly stated that
hypermail was not liikely to undergo significant upgrades, and i couldn't
find anyone else with the problem, mhonrc seemed like a good solution,
especially given it's enhanced customizability. You can't really (unless
there's an upgrade) tweek the appearance of the file generaetd by
hypermail.
i'd be happy to use HM if these things didn't exist because it's faster
(being a compiled C program) than mhonarc, a perl script.
<end quote>
Aside: I've been really pleased with Mhonarc, and have found several
useful features (such as not having to redefine all the configuration
parameters each time we update the index) that make using Mhonarc quite
easy. The following URL details the specs on Mhonarc:
http://www.oac.uci.edu/indiv/ehood/MHonArc/doc/mhonarc.html
regards,
Zach
_________
Zachariah Nobel, Assistant in Internet Services
Center for Renewable Energy and Sustainable Technology (CREST)
zach@crest.org
|
|
