ftp.uu.net	[137.39.1.9]    comp.sources.unix/volume12/vmail/part0*.Z		46KB    ftp.ucs.ubc.ca 	[137.82.27.61]	pub/mh/vmail[1-3]of3.Z	58KB    Or mail requests to James Perkins <jamesp@sp-eug.com>.  [1.93]  vmailtool    If you have a Sun workstation, vmailtool may be for you.  It is a    button gadget panel for the above-mentioned vmail program.  It    brings vmail into the windows era where people no longer need to    memorize specific command keystrokes.  It also provides a mail    icon with the flag that pops up when new mail arrives.  Again,    this is a compact, simple tool, unlike the powerful xmh program.    Still, it's a welcome alternative for many people who are running    SunView or OpenWindows.  --James Perkins <jamesp@sp-eug.com> [1.93]    ftp.ucs.ubc.ca 	[137.82.27.61]	pub/mh/vmailtool.Z	18KB    or mail requests to James Perkins <jamesp@sp-eug.com>. [1.93]  plum    Plum is a highly configurable and extensible screen-oriented front-end    for processing MH mail on ASCII terminals.  Unlike mh-e, the extension    language used in plum is perl, not LISP.  Plum offers many of the    advantages of xmh, but lacks several of xmh's disadvantages.  The    look&feel derives more from vi than from emacs.  Key bindings and    functions may be changed on the fly to suit the user's preference.  It    offers filename and word completion on folder, variables, and command    names.    Until it is included in the standard distribution (under miscellany),    you can find a copy on:    convex.com	[130.168.1.1]	pub/plum/plum*		55KB    or mail requests to Tom Christiansen <tchrist@convex.com>.  mmh	     MMH, My Mail Handler, is a Motif interface for reading and sending mail.    It uses the MH commands to actually handle sending a receiving messages.    It does not support all the capabilities of MH, but offers a large    enough subset to handle the majority of users.  Its intended user is    someone between "bumbling e-mail novice" and "sophisticated user".    Hooks are provided to allow the user to customize and add new commands.    ftp.eos.ncsu.edu	[152.1.9.25]	/pub/bill.tar.Z  metamail    Metamail is a package that can be used to convert virtually ANY    mail-reading program on UNIX into a multimedia mail-reading program.    It is an extremely generic implementation of MIME (Multipurpose    Internet Mail Extensions), the proposed standard for multimedia mail    formats on the Internet.  The implementation is extremely flexible and    extensible, using a "mailcap" file mechanism for adding support for new    data formats when sent through the mail.  At a heterogeneous site where    many mail readers are in use, the mailcap mechanism can be used to    extend them all to support new types of multimedia mail by a single    addition to a mailcap file.    The metamail distribution comes complete with a small patch for    each of over a dozen popular mail reading programs, including    Berkeley mail, mh, Elm, Xmh, Xmail, Mailtool, Emacs Rmail, Emacs    VM, Andrew, and others.  Note that the MH patches are now integrated    into MH 6.8 --Nathaniel Borenstein <nsb@thumper.bellcore.com>    thumper.bellcore.com 	[128.96.41.1]	/pub/nsb/mm.tar.Z  X.500 lookups      If a name is enclosed in square brackets, when entering a destination    address, ie:	To: [Greg Wickham,CSIRO]    a search will be made in the X.500 Directory for the individual's entry.    If an address exists then it will be extracted and placed into the    headers.  Mail requests for the software to the author.  --Andrew    Waugh <ajw@mel.dit.csiro.au>  QueueMH    QuemeMH is an e-mail based service request and tracking system    based on the Rand Mail Handler. --Barbara Dyker    <dyker@teal.csn.org>  [1.93]    ftp.cs.colorado.edu		pub/cs/sysadmin/utilities/queuemh.tar.Z  QMH:    Qmh is an MH-based group mail management tool. Written entirely in    perl, Qmh combines the best aspects of MH with group mail    heuristics and delivers a sensible package for all levels of UNIX    users. A limitless number of individual queues and associated    groups of permitted users can be established.    Specific functionality includes the following modes of operation;    checking header dates and sending reminder/deadline mail, editing    existing messages, help screens, creating new messages from    scratch or exiting messages, resolving messages, scanning queue    folders, and annotating with status both by editing and sending    mail.    Qmh is a single generic program in and of itself from which all    modes of operation are invoked. Additionally, each separate queue    may be accessed via a link to the single program. All system    configuration is maintained in a single file that is read upon    each invocation of Qmh.  Formatting and template files are    provided in the system library, although individual users can    override the defaults simply by creating equivalent files in their    own MH mail directory.    Qmh provides a powerful database-like functionality by allowing    limitless per-queue X-Qmh-<$value> headers to be included in    messages.  These "fields" then form the context of the queue    messages and provide a user-defined, but yet structured    environment for queries, reporting, and random information.    Qmh is designed to provide a complete solution for SA groups, help    desks, support organizations, or wherever two or more individuals    are trying to manage multiple mail requests.    Qmh is also compatible with versions of xmh that provide    user-level command buttons. Provided in the Qmh package is a    ~/.Xdefaults template file that's setup to harness the power of    Qmh.    For more info, write to <info@rootgroup.com>.  [3.93]  MacMH and PC/MH:    These were available only for non-commercial degree-granting    institutions from:	Networking & Communication Systems	115 Pine Hall	Stanford University	Stanford, CA 94305-4122	Phone: +1 415-723-3909    --Jerry Peek <jerry@ora.com>    The authorized distributor for PC/MH is:	NEI, Inc.	210 Technology Drive, STE 210	Irvine, Ca 92718	Phone: +1 714-753-8588	FAX:   +1 714-753-8593	Internet: info@netix.com    --Shannon Yeh <yeh@orion.oac.uci.edu>    In addition, you might try Wollongong, to see if they have something you    can get.  Subject: How can I print a MH manual?From: Intro-6  To order a copy by mail, see the section on how to get MH by mail in  "Where can I get MH?"  Also, check "What references exist for MH?"  To print your own copy, first obtain the MH sources ("Where can I  get MH?") if you don't already have it.  Go into the "doc" directory  and run "make guide" to create the administrators guide and "make  manual" to create a user's manual which includes tutorials and man  pages.  If the doc directory is empty or is missing the Makefile,  you'll have to run "mhconfig MH" in the conf directory so that the  documentation with correct local information is created.  For properly formatting the documentation (at least the manual  pages) you might even have to install MH, because a reference to a  tmac.h file in the MH lib directory is made in the manual pages.  You can also ftp the ASCII or postscript versions:    ftp.ics.uci.edu	[128.195.1.1]	mh/doc/tutorial.ps.Z		64KB					mh/doc/ADMIN.ps.Z		57KB					mh/doc/MH.ps.Z (man pages)	273KB      ftp.uu.net		[137.39.1.9]	same files, but in dir mail/mh/doc  Or, you can send a note to mail-server@nluug.nl with a body containing the  following:    send mail/mh/papers-ps/tutorial.ps.Z  --Bill Wohler and Jos Vos <jos@bull.nl> [1.93]    Subject: How should I report bugs?From: Intro-7  Mail them to Bug-MH@ics.uci.edu and be sure to include the output of  the -help option as well as what hardware and operating system you  are using.  Subject: How can I convert from my mailer to MH?From: Intro-8  If you use one of a mail agent like 'mail', 'mailx', 'elm' or  'mush', converting to MH is easy.  When you run the 'inc' command,  it reads all new messages from the system mailbox into your 'inbox'  folder.  Those mail agents also have separate files or "folders"  that hold messages in the same format as the system mailbox.  You  can read them with the 'inc -file' command.  For example, to read  the messages from your 'mbox' mail file into your MH 'inbox' folder,  you'd type:	% cd	% cp mbox mbox.backup	% inc -file mbox  If you see the usual "Incorporating new mail into inbox..." message  and a scan listing, the messages probably were converted.  Read some  or all of them (with the 'show' command) and be sure.  The 'inc'  won't remove your mbox unless you use '-truncate'.   Section D.4 (C.4) of the MH book lists two scripts to convert mail  files to MH folders: babyl2mh to convert from rmail's babyl format;  vmsmail2mh to convert from VMS's mail (see "What references exist  for MH" to see where the book's examples can be ftped from).  --Jerry Peek <jerry@ora.com>  Vivek Khera <khera@cs.duke.edu> rewrote this in Perl since the  original script doesn't work for some people.  See appendix  "babyl2mh.pl." [1.93]  Juergen Nickelsen <nickel@cs.tu-berlin.de> provides yet another  short script.  He says,  "You can remove the second to last second line ("> $input"), so  that the script doesn't zero out your RMAIL file.  "Another alternative is to replace this line with "inc -file $tmpmbox  $folder && > $input", so that the RMAIL is only zeroed if inc  successfully incorporated the mail.  Finally one could add a switch  -z, so that the RMAIL file is only zeroed if the switch is given.  See appendix "inco." [1.93]  Use the following to convert a Babyl format file to UNIX mail format.  --Barry A. Warsaw <warsaw@nlm.nih.gov>.  durer.cme.nist.gov	[129.6.32.4]	pub/gnu/rmailtovm.el  See also MH book appendix D (appendix C).  Subject: What machines does MH run on?From: Building MH-10  If you have a computer running UNIX, you can probably run MH.  --Jerry Peek <jerry@ora.com>  Subject: How do I build MH?From: Building MH-11  By carefully reading the READ-ME in the root of the source  hierarchy, one should not have any trouble building MH.  Subject: What options should I use?From: Building MH-12  BERK: Do NOT include the BERK option (in versions 6.7 or later)!  BERK breaks the mh-format functions that take apart address lines,  for example mbox, from, and friendly.  This would really put a crimp  on my replcomps file.  LOCKF: if you have NFS, you need to lock your mailbox with lockf()  so the lock will be honored by all machines on the local network.  If you have the lockf() system call, include LOCKF.  JQ Johnson <jqj@duff.uoregon.edu> makes the point that one should  use this option carefully since it requires a roboust lockf() call.  For example, this option caused serious problems on his SunOS 4.1.1.  He suggested using LOK_BELL instead, and adding "lockstyle: 1" to  mtstailor.  ATZ: makes your timezones print like "EST" instead of "-0500".  Much  prettier.  --Stephen Gildea <gildea@expo.lcs.mit.edu>  However, Tony Landells <ahl@technix.oz.au> replies: "Yes; very  pretty.  How unfortunate that timezone names are so ambiguous, so  that EST can be interpreted, at a minimum, as (American) Eastern  Standard Time, (Australian) Eastern Standard Time, or (Australian)  Eastern Summer Time (and yes, I think it's dumb having the same  acronym for both normal and Summer time, but that's a different  problem).  While the numeric timezones may not look as nice, they  are, at least, reasonably unambiguous.  I would urge anyone who ever  intends/hopes/expects to use e-mail outside the U.S. to NOT use ATZ  (sorry Stephen)."  At any rate, the conf/examples directory has been updated and  contains many examples show you which options are required on your  platform and which are optional (in the upcoming version MH 6.8).  At  any rate, it is recommended that you examine the options in the  example configuration files, and read about them in READ-ME.  RPATHS: a side-effect is that slocal writes messages to your system  maildrop without the MMDF C-A's that separate messages, so your BSD  tools like from work. [12.92]  Subject: Fixing "post: problem initializing server; [BHST] no servers available"From: Building MH-13  The error message itself is essentially correct.  However, what this  really means is: MH's post cannot connect to a running sendmail over  an SMTP port (MH configured with SMTP and SENDMTS).  The potential problems:  1. Your local sendmail daemon is dying or not running for some  reason.  2. You use BIND and your local nameserver is not responding.  3. Your mtstailor has its "servers:" pointing to a non-existant  machine or a machine which is a) not reachable or b) not running the  sendmail daemon.  --Peter Marvit <marvit@hplabs.hpl.hp.com>  Subject: Where can I get POP3?From: Building MH-14  MH6.7 (and earlier versions too) include a server for version 3 of POP.  Subject: What do I do if scan shows the wrong date?From: Building MH-15  Upgrade to MH 6.8. [1.93]  Subject: Why slocal writes messages to system maildrop that from(1) can't read.From: Building MH-16  Upgrade to MH 6.8 and set the RPATHS option.  Better yet, use a more  MH-like command instead: "scan -file $MAIL".  [1.93] Subject: Why does repl add a "Re:" to a message that already has one?From: Building MH-17  I carefully reconfigured and rebuilt MH from scratch and the problem  went away.  --Larry McVoy <lm@slovax.Eng.Sun.COM>  Subject: Does MH support IMAP2 (RFC 1064)?From: Building MH-18  No.  MH only supports retrieving mail using POP3.  POP3 is on the  "standards track"--it is now an elective Internet Draft Standard  (see RFC1280 for more details).  At this point, IMAP[23] are  "experimental, limited use" protocols; it is unlikely that MH will  support them.  --John Romine <jromine@ics.uci.edu>  Subject: Why does "mailgroup mail" only affect inc but not slocal?From: Building MH-19  If "mailgroup" is set, inc is made set-group-id to this group name.  Some SYS5 systems want this to be set to "mail".  Set this if  /usr/spool/mail (or /usr/mail) is not world-writeable.  These  changes were contributed by Peter Marvit, and "inc" is very careful  about its use of the set-gid privilege.  Note that slocal doesn't know how to deal with this, and will not  work under these systems; just making it set-group-id will open a  security hole (since it doesn't know when to drop the set-gid  privileges).  If you're using "mailgroup", you should remove slocal  (and its man page) from your system. --John Romine  <jromine@ics.uci.edu> [1.93]  Alternatives to slocal include deliver, procmail, and mailagent.  Archie can help you find where they are kept.  Subject: Where can I read about slocal and the format of the .maildelivery file?From: Using MH-30  See the slocal man page.  Here is brief example of a .maildelivery file that stores messages  to babble in a folder and the system mailbox, stores mh-users in a  folder but not the system mailbox, and puts the rest in the system  mailbox.	to  mh-users  | A "/usr/local/lib/mh/rcvstore -create +lists/mh-users"	cc  mh-users  | A "/usr/local/lib/mh/rcvstore -create +lists/mh-users"	to  babble    | R "/usr/local/lib/mh/rcvstore -create +lists/babble"	cc  babble    | R "/usr/local/lib/mh/rcvstore -create +lists/babble"	default -     > ? /usr/spool/mail/wohler  Your .forward file may look like (quotes necessary):	"| /usr/local/lib/mh/slocal -user your_login"  In some implentations, the "-user your_login" is not needed.  If  not, manually running slocal with the flag will produce an error.  See also chapter 11 in the MH book.  Alternatives to slocal include deliver, procmail, and mailagent.  Archie can help you find where they are kept.  Subject: How do I include messages in repl with or without ">"?From: Using MH-31      When making a reply, specify a filter file on the command line:	repl -filter repl.format  This filter file must be in your MH mail directory (usually "Mail",  in your home directory).  Here are a couple of example repl.format  files:	overflowtext="",overflowoffset=0	message-id:nocomponent,formatfield=\	"In message %{text}you write:"	body:component=">",overflowtext=">",overflowoffset=0	      or