🚀 go-pugleaf

In article <BxtpM2.3tE@usenet.ucs.indiana.edu> erisande@silver.ucs.indiana.edu (Kryst the Philosopher) writes:
>
>>Any replies in any form whatsoever will be appreciated.

Something I haven't seen anyone mention yet is reliability with archive
and recall capability.  This can be important in commercial environments.
I'm running home-rolled version of an old message system that provides
this.  Although I've added gateways in and out to mailers I haven't
completely replaced it yet, largely because of this function.  The
sender supplies a sequence number in the header which once upon a time
had to be correct (starting from 1 each day) but now those are mostly
ignored and a "real" input sequence number is assigned as a message
is received.  As the message is delivered an output sequence is assigned
to it, and at the end of the day a message is generated showing how
many messages were received and delivered for each station so everyone
can tell if they miss or lose any (not too long ago most of the
stations sent directly to a printer).   There is a simple command to
recall any message by it's input or output station name, date, and
sequence number (input or output).   A few days of activity are always
on line for quick access, then we archive the input data and
the output logs needed and can still recall any message through
the system for the previous year or so.

Les Mikesell
  les@chinet.chi.il.us