Here's the cleaned-up version of my digestifier: it follows RFC 934,
and so should be compatible with most any digest-digester that comes
along.  I think I cribbed the precise format from the RISKS digest way
back when.

  This does not automatically increment issue numbers or send the
message; it just creates a properly formatted digest and spits it to
stdout.  Both of these can be done in a simple wrapper tailored to how
things are set up at your end.

  To make a digest, you need four things:
	- a digest config file, ~/.digestrc by default (sample in
	  digest.cf)
	- a digest header file (administrivia, sample is foo-header.txt)
	- a digest trailer file (ditto, see foo-trailer.txt)
	- RFC-822 messages, stored one per file

  usage is "digest [-c configfile] messagefile ...".  The few times I
actually used this, I just piped it into "/usr/lib/sendmail -oi -t".

  The config file is commented, and the format should be obvious.  the
only two things to watch for in the header and trailer files are:
	- a line containing _SUBJECTS_ in the header file will be
	  replaced by lines consisting of all of the subjects in the
	  included messages, in order, indented as far as _SUBJECTS_ is.
	- lines beginning with "-" in these files will not be
	  properly encapsulated, and will be interpreted by
	  undigesting software as message breaks.
