From: Kent Landfield (kent@hypermail.org)
Date: Fri Jun 14 2002 - 16:27:49 CDT
# Sounds OK, if you want to add a more general feature. Yet I don't see the need
# for such a complex development if you have in mind such a simple issue as
# mine. In my case for example, it would be enough for me if a simple text file
# is created by Hypermail containing the stuff I request each time it is
# executed. I wouldn't want it to require more resources or bandwidth. Also, I
# don't particularly like something as general as 'executing external commands'.
# If I wanted something so general I could start looking how to do the whole
# thing using a Perl script. I believe the purpose here is ease of
# administration.
Then take mbox2hypermail.c or msg2archive.c in the archive directory,
hack them a bit to support your needs and wrapper the hypermail executable.
(or do it with a perl wrapper... :))
# And, as far as another issue that occured in my network is concerned, you
# should examine the case that someone would want to use Hypermail in a
# different machine than the one acting as a mail server. I had to develop a
# whole series of scripts to achieve this.
I do that now on certain systems. On the remote system, I just install the
hypermail executable, the appropriate .rc and .hyp header and footer files
and then set the email alias to execute the hypermail executable when email
comes to the remote machine for final delivery.
-- Kent Landfield Phone: 1-817-545-2502 Email: kent@landfield.com http://www.landfield.com/ Search the Usenet FAQ Archive at http://www.faqs.org/faqs/ Search the RFC/FYI/STD/BCP Archive at http://www.faqs.org/rfcs/