#
# I was setting up some aliases where a mailing list is actually the sum of
# multiple mailing lists like the following...
#
# listA :include:/lists/listA
# listB :include:/lists/listB
# listC :include:/lists/listC
# listD :include:/lists/listA,:include:/lists/listB,:include:/lists/listC
#
# What I noticed was that if you ask for a list of users for listD, that
# majordomo parses the /lists/listD file (which is empty) and you get a
# report saying nobody is subscribed when in fact there are lots of people
# suscribed to the others pieces that (when added up) make listD.
#
# Is there a reasonable way to try to get a little more smarts to be able
# to look at the aliases file to figure out the truth ? I was thinking that
# a majordomo.cf entry that points to the mail aliases file might be a place
# to start...
I have carefully avoided having Majordomo make ANY reference at all to
the aliases file, in order to avoid being dependant on Sendmail.
Hell, even where the aliases file lives isn't the same from one
version of sendmail to another, or from one site to another (it might
be /etc/aliases, /usr/lib/aliases, /etc/mail/aliases, or it might be
in a YP map rather than a file).
If I were going to do something like this, I'd make it independant of
the aliases file. I'd implement something like a <list>.sublists file
in Majordomo that would list the names of the subsidiary lists. It
would require some fairly substantial changes in Majordomo, however,
to make it look at groups of lists instead of individual lists for all
the various commands. It looks like a swamp to me, so I'm not
inclined to wade in...
-Brent
--
Brent Chapman Great Circle Associates
Brent@GreatCircle.COM 1057 West Dana Street
+1 415 962 0841 Mountain View, CA 94041
|
|
