And verily didst WJCarpenter spake of these matters:
> millar> lean towards something in Majordomo where you told it
> millar> explicitly the files that make up list D instead of trying to
> millar> read the aliases file.
> How about a command line that would produce the list contents on
> stdout or something similar? That way, Majordomo doesn't have to know
> about every strange file format or other local convention for keeping
> track of mailing lists.
Ironically, Majordomo should be just about the last program that would
need this, because by and large all the lists in question are ones
that Majordomo is doing the maintenance for....
Is there any reason that the inclusion of A, B, and C into D needs to
happen in the aliases file? Can the A, B, and C lists be *in* list
D? A quick and dirty fix is to put a comment in parentheses at the
beginning of the list D file telling the requestor to check the other
lists also. This comment would show up in a "who" command. Example
contents of list D file:
listA (Note: see list A for additional subscribers of list D)
listB (Note: see list B for additional subscribers of list D)
listC (Note: see list C for additional subscribers of list D)
xxxx@yyyyy (misc D subscriber)
email@example.com (other misc D subscr.)
And so on. This makes the user do a little more work, but it could
be done immediately with no changes to Majordomo.
Alan Millar amillar@bolis.SF-Bay.org __oo \
System Administrator =___/
Batteries not included.