cpshelle@logos.uwaterloo.ca (cameron shelley) (03/29/91)
Hi! I've been using Mush (7.1.2) for a short time and reading
the group etc, but I haven't seen an faq yet. So, I'll just
ask my silly question: what's the best way to manage a mailing
list with mush? Many thanks,
Cam
--
Cameron Shelley | "Peace, n. In international affairs, a
cpshelley@logos.waterloo.edu | period of cheating between two periods
Davis Centre Rm 2136 | of fighting."
Phone (519) 885-1211 x3390 | Ambrose Bierceschaefer@ogicse.ogi.edu (Barton E. Schaefer) (03/31/91)
In article <1991Mar29.022207.26665@watdragon.waterloo.edu> cpshelle@logos.uwaterloo.ca (cameron shelley) writes: } Hi! I've been using Mush (7.1.2) for a short time and reading } the group etc, but I haven't seen an faq yet. Anybody want to volunteer to make one up? I don't think I've seen the same question come by more than 2 or 3 times, except of course for "where do I get mush?" which seems to be repeated monthly. :-) BTW, I have word that Rich $alz will be posting 7.2.2 to comp.sources.unix in the near future -- sometime after April 7. } So, I'll just } ask my silly question: what's the best way to manage a mailing } list with mush? Many thanks, } } Cam Depends on what you need to do. Some very general recommendations: 1. Make sure mush was compiled with a large HDRSIZ. I had to compile with HDRSIZ 10240 to support a mailing list that was being run from ogicse. 2. Break the mailing list up into groups and create an aliases for each group. Keep in mind that mush won't accept a backslash-continued line longer than BUFSIZ (usually 1024 characters) in .mushrc. Then make the mailing list name an alias for all the groups' aliases. This will avoid the BUFSIZ limitations and help organize the list. It also means you can have one or more groups of recipients that are Bcc'd, so that they are "anonymous" recipients of the list. 3. Unless you are planning to moderate the list -- e.g., examine all submissions and decide which to send out -- the best way to run a mailing list is to get your system adminstrator to make an entry for the list in /usr/lib/aliases (or whatever your MTA uses) and bypass mush altogether. 4. If there is such an entry in /usr/lib/aliases, but you still want use mush's alias mechanism to send mail to the list, you can set no_expand to leave the alias name unexpanded in the To: line. You shouldn't do this if the mailing list name is not a legitimate mail recipient, though. -- Bart Schaefer schaefer@zipcode.com Z-Code Software Corporation schaefer@cse.ogi.edu