[ Jason L Tibbitts III writes: ]
While we're throwing ideas around, I assume the semantics here that
"rude_message" is a filespec with some default directory assumed. Would
the '<<' syntax to inline the file be allowed (i.e. << SUBTAG within <<
TAG)? What about variable substitution, e.g. $SENDER, $LISTNAME, etc.,
in either case? What about a means for list owners to install/update/
remove/list arbitrary message files, e.g. "rude_message", without direct
access to the Mj machine?
Any thoughts of compartmentalizing lists in separate directories? E.g.:
$listdir/alist/ directory for list "alist"
_stripped database of stripped addresses
_unstripped database of unstripped addresses
_whatever the other database (I forget what it's for)
_config config file
_intro intro message
_info info message
rude_message user message file
$listdir/blist/ directory for list "blist"
In this example I've used a leading underscore to reserve file names for
Mj's "well known" files, but it could be *.Mj or Mj.* or whatever.