From Majordomo-Users-Owner Fri Oct 1 06:25:34 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA20666; Fri, 1 Oct 93 06:25:34 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA20659; Thu, 30 Sep 93 23:25:25 PDT Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA29414; Thu, 30 Sep 93 23:14:13 PDT Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0oidUE-00032gC; Thu, 30 Sep 93 22:57 PDT Message-Id: From: Alan Millar Subject: Re: questions for the group to answer... To: tom_limoncelli@Warren.MENTORG.COM Date: Thu, 30 Sep 1993 22:57:00 -0800 (PDT) Cc: CCRAY@MIZZOU1.missouri.edu, Majordomo-Users@GreatCircle.COM In-Reply-To: <9309301909.AA03571@worf.Warren.MENTORG.COM> from "tom_limoncelli@Warren.MENTORG.COM" at Sep 30, 93 03:09:45 pm Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1884 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst tom_limoncelli@Warren.MENTORG.COM spake of these matters: > > -- We currently have about 100 listserv-s on VM. It is > > growing at about 5 per week. The total mail traffic > > generated by those 100 is estimated at 5,000 e-mails per > > day. > > QUESTION: anyone out there doing majordomo at this > > scale? > I can't answer this, but if you do this I would HIGHLY recommend using > sendmail 8.5 (or whatever the latest rev. is) since it handles huge, > huge, huge volumes of mail much better than the stock sendmail that > most Unix's have. This is really the key point, which has been mentioned/inferred but not clarified: Majordomo doesn't do the actual list message distribution. The "resend" script which comes with Majordomo is optional. The workload and therefore the performance questions are all in the system mailer. This is likely to be sendmail, but there are other choices. Sendmail is the nuclear aircraft carrier of Unix mailers. SO, anyone who's running that volume of lists on the same operating system and hardware will be good enough for a reference point. The best place to ask that comes to mind is on Usenet in comp.mail.sendmail and comp.mail.misc. > > QUESTION: Does MajorDomo have the ability to archive > > activity MajorDom and does the subscriber have > > the ability to request these? > However, there is no "index" and "get" service like Listserv > has. I believe someone has written something similar. These commands are in the latest version of Majordomo. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ And Moses said, "Oh, Lord, please send someone else to do it!" -Exodus 4:13 From Majordomo-Users-Owner Fri Oct 1 00:14:09 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21193; Fri, 1 Oct 93 06:58:26 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21185; Thu, 30 Sep 93 23:58:15 PDT Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA00953; Thu, 30 Sep 93 23:54:16 PDT Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0oidkq-00032gC; Thu, 30 Sep 93 23:14 PDT Message-Id: From: Alan Millar Subject: Re: questions for the group to answer... To: CCRAY@MIZZOU1.missouri.edu (ray harder) Date: Thu, 30 Sep 1993 23:14:11 -0800 (PDT) Cc: Majordomo-Users@GreatCircle.COM In-Reply-To: <9309301608.AA13374@mycroft.GreatCircle.COM> from "ray harder" at Sep 30, 93 11:11:39 am Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1914 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst ray harder spake of these matters: > -- I have hacked at installing Majordomo on an IBM RS/6000 > workstation at 3.2.4 level. It is mostly not working > griping about permissions. > QUESTION: Is there anyone out there successfully running > MajorDomo on an AIX system? Can you give > advice or do I just have to go thru the > install slowly and methodically. Nothing specific, but a general comment: Getting "wrapper" compiled with the right options is the only compiling you need to do to set up Majordomo. My eyes glazed over when I looked at listproc's installation. > QUESTION: Does MajorDomo have the ability to archive > activity MajorDom and does the subscriber have > the ability to request these? With the minimal recommended installation, you get a text file which holds copies of all of the list messages. This is a one-liner in the system's "aliases" file. I also recently posted a perl script which will create archives in a format which is very close to the Revised Listserv format (one file per month LOGYYMM, stripped-down headers as you like). > QUESTION: Does any UNIX mailer has the ability to > consolidate users mail going to a single host > and expand it at the destination node? This is not uncommon, but varies from one version to the next. If you are doing uucp, SMail 3.1 will do this for UUCP neighbors. Multiple recipients are sent as a single "rmail" command with multiple arguments, up to a configurable maximum command-line length. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ The skill of accurate perception is called cynicism by those who don't possess it. From Majordomo-Users-Owner Fri Oct 1 10:34:31 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21892; Fri, 1 Oct 93 10:34:31 GMT Received: from uu.psi.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21885; Fri, 1 Oct 93 03:34:22 PDT Received: from kerner.UUCP by uu.psi.com (5.65b/4.1.031792-PSI/PSINet) via UUCP; id AA01665 for ; Fri, 1 Oct 93 06:21:16 -0400 Received: from proton.kerner.com by kerner.com (4.1/NBN-11/KERNER-7) id AA09157; Thu, 30 Sep 93 12:17:21 PDT Received: by proton.kerner.com (5.67-KERNER.4/TDM-4.01) id AA01920; Thu, 30 Sep 93 12:10:40 -0700 Message-Id: <9309301910.AA01920@proton.kerner.com> To: Kingsley Kerce Cc: Majordomo-Users@GreatCircle.COM Subject: Re: questions for the group to answer... In-Reply-To: Your message of "Thu, 30 Sep 1993 14:15:54 PDT." <199309301815.AA96858@dirac.scri.fsu.edu> Date: Thu, 30 Sep 1993 12:10:40 -0700 From: Tim Irvin Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199309301815.AA96858@dirac.scri.fsu.edu> you write: > I ended up replacing the above code with: > > open(LS,"(cd $listdir; ls -1) |"); > > while() { > $_ = &chop_nl($_); # strip any trailing newline > > followed by the while's body, finishing up with: > > close LS; > > I'm taking this opportunity to ask if this is a reasonable solution to > the problem, and if the problem was really a problem. This is the > first bit of Perl that I've ever written. A better solution would be: opendir(DIR, $listdir); while (grep(!/^\.\.?$/, readdir(DIR))) { # The grep removes "." and ".." } closedir(DIR); Tim Irvin From Majordomo-Users-Owner Fri Oct 1 19:41:34 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA22977; Fri, 1 Oct 93 19:41:34 GMT Received: from terc.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA22970; Fri, 1 Oct 93 12:41:28 PDT Received: from qm.terc.edu by terc.edu (4.1/SMI-4.1) id AA18168; Fri, 1 Oct 93 15:43:14 EST Message-Id: <9310012043.AA18168@terc.edu> Date: 1 Oct 1993 15:43:49 -0500 From: "Stephen Bannasch" Subject: moderated lists To: Majordomo-Users@GreatCircle.COM Cc: andrew_boyd@terc.edu, blake_meike@terc.edu Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Subject: moderated lists To: Majordomo-users Is there a way to make a "moderated" list with Majordomo? What I want to be able to do is have a list where submissions to the list go to the owner (or to someone designated as a facillitator). At regular intervals the owner posts an annotated compilation of messages to all members of the list. --Stephen Bannasch From Majordomo-Users-Owner Sun Oct 3 02:48:59 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA26036; Sun, 3 Oct 93 02:48:59 GMT Received: from plinius.rutgers.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA26029; Sat, 2 Oct 93 19:48:53 PDT Received: by plinius.rutgers.edu (5.59/SMI4.0/RU1.5/3.08) id AA25367; Sat, 2 Oct 93 22:51:38 EDT Date: Sat, 2 Oct 93 22:51:37 EDT From: "Beth E. Binde" To: majordomo-users@GreatCircle.COM Subject: POSIX compliant compilation of majordomo Message-Id: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've compiled majordomo under Solaris, and it seems to work well in my initial tests. However, the Makefile distributed with the package suggests on a gid=15 for the POSIX compile. At our site, the gid 15 is already assigned and so not available -- I've simply used the gid that I assigned to majordomo (i. e., 2011). Is there anything "magic" about the gid 15? Is the other gid just fine? (This isn't quite as compulsive as it sounds -- we are quite a large site and assignment of gids is mandatory for keeping our automatic software distribution sane.) Thanks for your help. Beth E. Binde, Systems Programmer Rutgers University Computing Services, Piscataway, NJ 08855-0879 USA EMAIL: binde@noc.rutgers.edu VOICE: 908-932-5019 From Majordomo-Users-Owner Mon Oct 4 06:19:25 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA28544; Mon, 4 Oct 93 06:19:25 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA28534; Sun, 3 Oct 93 23:18:49 PDT Message-Id: <9310040618.AA28534@mycroft.GreatCircle.COM> To: "Beth E. Binde" Cc: majordomo-users@GreatCircle.COM Subject: Re: POSIX compliant compilation of majordomo In-Reply-To: Your message of Sat, 2 Oct 93 22:51:37 EDT Date: Sun, 03 Oct 1993 23:18:48 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Beth E. Binde" writes: # I've compiled majordomo under Solaris, and it seems to work well in my initia # l # tests. # # However, the Makefile distributed with the package suggests on a # gid=15 for the POSIX compile. At our site, the gid 15 is already # assigned and so not available -- I've simply used the gid that I # assigned to majordomo (i. e., 2011). # # Is there anything "magic" about the gid 15? Is the other gid just fine? No. Yes. 15 is just an example. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Mon Oct 4 18:37:04 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA00583; Mon, 4 Oct 93 18:37:04 GMT Received: from zoso.quintus.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA00576; Mon, 4 Oct 93 11:36:39 PDT From: Karen Vazquez Date: Mon, 4 Oct 93 11:40:09 PDT Message-Id: <2464.9310041840@zoso.quintus.com> Received: from quintus.com (niners.quintus.com) by zoso.quintus.com; Mon, 4 Oct 93 11:40:09 PDT To: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I need help. I have not been able to install the majordomo software. There may be some problems we are encountering with our Yellow Pages/NIS setup, so I thought I would at least try to set it up on a stand-alone machine to test it out. I have the majordomo software in /usr/majordomo: -rw-rw-r-- 1 majordom majrdomo 3536 Oct 4 07:55 Changes -rw-rw-r-- 1 majordom majrdomo 2831 Oct 4 07:55 Description drwxrwxr-x 2 majordom majrdomo 512 Oct 4 07:55 Log -rw-rw-r-- 1 majordom majrdomo 1875 Oct 4 08:36 Makefile -rw-rw-r-- 1 majordom majrdomo 860 Oct 4 07:55 Manifest -rw-rw-r-- 1 majordom majrdomo 5164 Oct 4 07:55 README -rw-rw-r-- 1 majordom majrdomo 6430 Oct 4 07:55 README.UIUC -rw-rw-r-- 1 majordom majrdomo 576 Oct 4 07:55 TODO drwxrwxr-x 2 majordom majrdomo 512 Oct 4 07:55 Tools -rw-rw-r-- 1 majordom majrdomo 3086 Oct 4 07:55 approve -rw-rw-r-- 1 majordom majrdomo 3543 Oct 4 07:55 auto_email -rw-rw-r-- 1 majordom majrdomo 1736 Oct 4 07:55 autoemail -rw-rw-r-- 1 majordom majrdomo 2870 Oct 4 07:55 bounce -rw-rw-r-- 1 majordom majrdomo 2572 Oct 4 07:55 bounce-remind -rw-rw-r-- 1 majordom majrdomo 432 Oct 4 07:55 initlist -rw-rw-r-- 1 majordom majrdomo 465 Oct 4 07:55 initlist.orig -rw-rw-r-- 1 majordom majrdomo 3418 Oct 4 07:55 list.info -rw-rw-r-- 1 majordom majrdomo 21787 Oct 4 07:55 majordomo -rw-rw-r-- 1 majordom majrdomo 322 Oct 4 08:43 majordomo.cf -rw-rw-r-- 1 majordom majrdomo 360 Oct 4 07:55 majordomo.cf.orig -rw-rw-r-- 1 majordom majrdomo 44636 Oct 4 07:55 majordomo.paper.ps.Z -rw-rw-r-- 1 majordom majrdomo 9070 Oct 4 07:55 majordomo.pl -rw-rw-r-- 1 majordom majrdomo 1320 Oct 4 07:55 medit -rw-rw-r-- 1 majordom majrdomo 2126 Oct 4 07:55 new-list -rw-rw-r-- 1 majordom majrdomo 1914 Oct 4 07:55 request-answer -rw-rw-r-- 1 majordom majrdomo 5995 Oct 4 07:55 resend -rw-rw-r-- 1 majordom majrdomo 1452 Oct 4 07:55 resend.README -rw-rw-r-- 1 majordom majrdomo 772 Oct 4 07:55 sample.aliases -rw-rw-r-- 1 majordom majrdomo 344 Oct 4 07:55 sample.cf -rw-rw-r-- 1 majordom majrdomo 6045 Oct 4 07:55 shlock.pl -rw-rw-r-- 1 majordom majrdomo 607 Oct 4 07:55 uiuc.aliases -rwsr-sr-x 1 daemon majrdomo 24576 Oct 4 08:44 wrapper -rw-rw-r-- 1 majordom majrdomo 2192 Oct 4 08:44 wrapper.c I have a link in the /etc directory to /usr/majordomo/majordomo.cf. I have entries in the /etc/aliases file as follows: majordomo: "|/usr/majordomo/wrapper majordomo" owner-majordomo: karen majordomo-owner: karen The majordomo.cf file looks like this: $whereami = "quintus.com"; $whoami = "Majordomo@$whereami"; $whoami_owner = "Majordomo-Owner@$whereami"; $homedir = "/usr/majordomo"; $listdir = "/usr/majordomo"; $log = "$homedir/Log"; $mailer = "/usr/lib/sendmail -f\$sender \$to"; # $Header: /mycroft/brent/majordomo/RCS/sample.cf,v 1.1 1993/04/16 23:26:25 brent Exp $ The Makefile is set up as follows: # $Source: /mycroft/brent/majordomo/RCS/Makefile,v $ # $Revision: 1.10 $ # $Date: 1993/04/16 23:21:31 $ # $Author: brent $ # $State: Exp $ # # $Header: /mycroft/brent/majordomo/RCS/Makefile,v 1.10 1993/04/16 23:21:31 brent Exp $ # # $Locker: $ # # This is where "wrapper" looks for the programs it's supposed to run. W_BIN=/usr/majordomo # This is the environment that (along with LOGNAME and USER inherited from the # parent process, and without the leading "W_" in the variable names) gets # passed to processes run by "wrapper" W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh # Use these settings for BSD-based systems, including SunOS 4.x. If you're # using a POSIX-compliant system (including SysV and BSDI), comment these # settings out, and uncomment the POSIX settings below. W_USER=daemon W_GROUP=majrdomo When I mail to majordomo, I get: majordomo... aliased to "|/usr/majordomo/wrapper majordomo" "|/usr/majordomo/wrapper majordomo"... connected to via prog... majordomo: permission denied "|/usr/majordomo/wrapper/majordomo"... unknown mailer error 5 Then, the mail is returned like this: Return-Path: Received: by (4.1/SMI-4.1) id AB00388; Mon, 4 Oct 93 09:09:28 PDT Date: Mon, 4 Oct 93 09:09:28 PDT From: Mailer-Daemon (Mail Delivery Subsystem) Subject: Returned mail: unknown mailer error 5 Message-Id: <9310041609.AB00388@> To: Postmaster ----- Transcript of session follows ----- 554 "|/usr/majordomo/wrapper majordomo"... unknown mailer error 5 ----- Message header follows ----- Return-Path: Received: by (4.1/SMI-4.1) id AA00388; Mon, 4 Oct 93 09:09:28 PDT Date: Mon, 4 Oct 93 09:09:28 PDT From: karen (Karen Vazquez) Message-Id: <9310041609.AA00388@> Errors-To: karen Apparently-To: majordomo Any help on this would be appreciated. Thanks, Karen karen@quintus.com From Majordomo-Users-Owner Mon Oct 4 18:59:58 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA00618; Mon, 4 Oct 93 18:59:58 GMT Received: from sph.umich.edu (stonewall.sph.umich.edu) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA00611; Mon, 4 Oct 93 11:59:49 PDT Received: from stonewall.sph.umich.edu by sph.umich.edu (5.67/2.2) id AA06920; Mon, 4 Oct 93 15:04:03 -0400 Date: Mon, 4 Oct 1993 15:02:30 -0400 (EDT) From: Richard Foote Subject: Re: your mail To: Karen Vazquez Cc: majordomo-users@GreatCircle.COM In-Reply-To: <2464.9310041840@zoso.quintus.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Make sure that majordomo is executable, ie: chmod 755 majordomo... That'd be my first guess... Richard Foote rfoote@umich.edu On Mon, 4 Oct 1993, Karen Vazquez wrote: > > I need help. I have not been able to install the > majordomo software. There may be some problems we > are encountering with our Yellow Pages/NIS setup, so > I thought I would at least try to set it up on a > stand-alone machine to test it out. > > I have the majordomo software in /usr/majordomo: > > -rw-rw-r-- 1 majordom majrdomo 3536 Oct 4 07:55 Changes > -rw-rw-r-- 1 majordom majrdomo 2831 Oct 4 07:55 Description > drwxrwxr-x 2 majordom majrdomo 512 Oct 4 07:55 Log > -rw-rw-r-- 1 majordom majrdomo 1875 Oct 4 08:36 Makefile > -rw-rw-r-- 1 majordom majrdomo 860 Oct 4 07:55 Manifest > -rw-rw-r-- 1 majordom majrdomo 5164 Oct 4 07:55 README > -rw-rw-r-- 1 majordom majrdomo 6430 Oct 4 07:55 README.UIUC > -rw-rw-r-- 1 majordom majrdomo 576 Oct 4 07:55 TODO > drwxrwxr-x 2 majordom majrdomo 512 Oct 4 07:55 Tools > -rw-rw-r-- 1 majordom majrdomo 3086 Oct 4 07:55 approve > -rw-rw-r-- 1 majordom majrdomo 3543 Oct 4 07:55 auto_email > -rw-rw-r-- 1 majordom majrdomo 1736 Oct 4 07:55 autoemail > -rw-rw-r-- 1 majordom majrdomo 2870 Oct 4 07:55 bounce > -rw-rw-r-- 1 majordom majrdomo 2572 Oct 4 07:55 bounce-remind > -rw-rw-r-- 1 majordom majrdomo 432 Oct 4 07:55 initlist > -rw-rw-r-- 1 majordom majrdomo 465 Oct 4 07:55 initlist.orig > -rw-rw-r-- 1 majordom majrdomo 3418 Oct 4 07:55 list.info > -rw-rw-r-- 1 majordom majrdomo 21787 Oct 4 07:55 majordomo > -rw-rw-r-- 1 majordom majrdomo 322 Oct 4 08:43 majordomo.cf > -rw-rw-r-- 1 majordom majrdomo 360 Oct 4 07:55 majordomo.cf.orig > -rw-rw-r-- 1 majordom majrdomo 44636 Oct 4 07:55 majordomo.paper.ps.Z > -rw-rw-r-- 1 majordom majrdomo 9070 Oct 4 07:55 majordomo.pl > -rw-rw-r-- 1 majordom majrdomo 1320 Oct 4 07:55 medit > -rw-rw-r-- 1 majordom majrdomo 2126 Oct 4 07:55 new-list > -rw-rw-r-- 1 majordom majrdomo 1914 Oct 4 07:55 request-answer > -rw-rw-r-- 1 majordom majrdomo 5995 Oct 4 07:55 resend > -rw-rw-r-- 1 majordom majrdomo 1452 Oct 4 07:55 resend.README > -rw-rw-r-- 1 majordom majrdomo 772 Oct 4 07:55 sample.aliases > -rw-rw-r-- 1 majordom majrdomo 344 Oct 4 07:55 sample.cf > -rw-rw-r-- 1 majordom majrdomo 6045 Oct 4 07:55 shlock.pl > -rw-rw-r-- 1 majordom majrdomo 607 Oct 4 07:55 uiuc.aliases > -rwsr-sr-x 1 daemon majrdomo 24576 Oct 4 08:44 wrapper > -rw-rw-r-- 1 majordom majrdomo 2192 Oct 4 08:44 wrapper.c > > > I have a link in the /etc directory to /usr/majordomo/majordomo.cf. > > I have entries in the /etc/aliases file as follows: > > majordomo: "|/usr/majordomo/wrapper majordomo" > owner-majordomo: karen > majordomo-owner: karen > > > The majordomo.cf file looks like this: > > $whereami = "quintus.com"; > $whoami = "Majordomo@$whereami"; > $whoami_owner = "Majordomo-Owner@$whereami"; > $homedir = "/usr/majordomo"; > $listdir = "/usr/majordomo"; > $log = "$homedir/Log"; > $mailer = "/usr/lib/sendmail -f\$sender \$to"; > > # $Header: /mycroft/brent/majordomo/RCS/sample.cf,v 1.1 1993/04/16 23:26:25 brent Exp $ > > > > The Makefile is set up as follows: > > # $Source: /mycroft/brent/majordomo/RCS/Makefile,v $ > # $Revision: 1.10 $ > # $Date: 1993/04/16 23:21:31 $ > # $Author: brent $ > # $State: Exp $ > # > # $Header: /mycroft/brent/majordomo/RCS/Makefile,v 1.10 1993/04/16 23:21:31 brent Exp $ > # > # $Locker: $ > # > > # This is where "wrapper" looks for the programs it's supposed to run. > W_BIN=/usr/majordomo > > # This is the environment that (along with LOGNAME and USER inherited from the > # parent process, and without the leading "W_" in the variable names) gets > # passed to processes run by "wrapper" > > W_PATH=/bin:/usr/bin:/usr/ucb > W_HOME=${W_BIN} > W_SHELL=/bin/csh > > # Use these settings for BSD-based systems, including SunOS 4.x. If you're > # using a POSIX-compliant system (including SysV and BSDI), comment these > # settings out, and uncomment the POSIX settings below. > W_USER=daemon > W_GROUP=majrdomo > > > When I mail to majordomo, I get: > > majordomo... aliased to "|/usr/majordomo/wrapper majordomo" > "|/usr/majordomo/wrapper majordomo"... connected to via prog... > majordomo: permission denied > "|/usr/majordomo/wrapper/majordomo"... unknown mailer error 5 > > > Then, the mail is returned like this: > > Return-Path: > Received: by (4.1/SMI-4.1) > id AB00388; Mon, 4 Oct 93 09:09:28 PDT > Date: Mon, 4 Oct 93 09:09:28 PDT > From: Mailer-Daemon (Mail Delivery Subsystem) > Subject: Returned mail: unknown mailer error 5 > Message-Id: <9310041609.AB00388@> > To: Postmaster > > ----- Transcript of session follows ----- > 554 "|/usr/majordomo/wrapper majordomo"... unknown mailer error 5 > > ----- Message header follows ----- > Return-Path: > Received: by (4.1/SMI-4.1) > id AA00388; Mon, 4 Oct 93 09:09:28 PDT > Date: Mon, 4 Oct 93 09:09:28 PDT > From: karen (Karen Vazquez) > Message-Id: <9310041609.AA00388@> > Errors-To: karen > Apparently-To: majordomo > > > Any help on this would be appreciated. > > Thanks, Karen > > karen@quintus.com > From Majordomo-Users-Owner Mon Oct 4 22:18:44 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA01200; Mon, 4 Oct 93 22:18:44 GMT Received: from zoso.quintus.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA01180; Mon, 4 Oct 93 15:17:36 PDT From: Karen Vazquez Date: Mon, 4 Oct 93 15:21:20 PDT Message-Id: <3783.9310042221@zoso.quintus.com> Received: from quintus.com (niners.quintus.com) by zoso.quintus.com; Mon, 4 Oct 93 15:21:20 PDT To: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thanks for all the responses. I've changed the scripts to 775 and my listdir is pointing to a different directory. Now I am receiving a different error: majordomo... aliased to "|/usr/majordomo/wrapper majordomo" "|/usr/majordomo/wrapper majordomo"... connected to via prog... majordomo: directory or file not found "|/usr/majordomo/wrapper/majordomo"... unknown mailer error 5 I thought this should be resolved by setting the W_BIN value in the Makefile. My Makefile is set up as follows: # This is where "wrapper" looks for the programs it's supposed to run. W_BIN=/usr/majordomo # This is the environment that (along with LOGNAME and USER inherited from the # parent process, and without the leading "W_" in the variable names) gets # passed to processes run by "wrapper" W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh # Use these settings for BSD-based systems, including SunOS 4.x. If you're # using a POSIX-compliant system (including SysV and BSDI), comment these # settings out, and uncomment the POSIX settings below. W_USER=daemon W_GROUP=majrdomo Any ideas on this? Thanks, Karen karen@quintus.com From Majordomo-Users-Owner Tue Oct 5 14:55:33 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03721; Tue, 5 Oct 93 14:55:33 GMT Received: from zoso.quintus.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03714; Tue, 5 Oct 93 07:55:19 PDT From: Karen Vazquez Date: Tue, 5 Oct 93 07:58:58 PDT Message-Id: <659.9310051458@zoso.quintus.com> Received: from quintus.com (niners.quintus.com) by zoso.quintus.com; Tue, 5 Oct 93 07:58:58 PDT To: majordomo-users@GreatCircle.COM Subject: ctime.pl Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi Majordomo is looking for the file - ctime.pl. I don't have this file on my system. Where can I get this? Thanks, Karen From Majordomo-Users-Owner Tue Oct 5 15:13:37 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03762; Tue, 5 Oct 93 15:13:37 GMT Received: from noc.ocs.drexel.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03755; Tue, 5 Oct 93 08:13:30 PDT Received: from dunx1.ocs.drexel.edu by noc.ocs.drexel.edu (4.1/SMI-4.1) id AA20020; Tue, 5 Oct 93 11:16:30 EDT Received: from localhost.ocs.drexel.edu by dunx1.ocs.drexel.edu (4.1/SMI-4.1) id AA22343; Tue, 5 Oct 93 11:16:57 EDT Message-Id: <9310051516.AA22343@dunx1.ocs.drexel.edu> To: majordomo-users@GreatCircle.COM Subject: Re: ctime.pl In-Reply-To: Your message of "Tue, 05 Oct 1993 07:58:58 PDT." <659.9310051458@zoso.quintus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Date: Tue, 05 Oct 1993 11:16:57 -0400 From: Bob Snyder Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > Hi > > Majordomo is looking for the file - ctime.pl. I don't > have this file on my system. Where can I get this? It's part of the perl distribution, and should have been installed in the perl library directory. Bob From Majordomo-Users-Owner Tue Oct 5 15:21:53 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03785; Tue, 5 Oct 93 15:21:53 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03778; Tue, 5 Oct 93 08:21:45 PDT Received: by interlock.ans.net id AA12486 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Tue, 5 Oct 1993 11:18:34 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Tue, 5 Oct 1993 11:18:34 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Tue, 5 Oct 1993 11:18:34 -0400 From: Dan Simoes Message-Id: <199310051522.AA81950@foo.ans.net> Subject: majordomo with moderators To: majordomo-users@GreatCircle.COM Date: Tue, 5 Oct 1993 11:22:38 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 657 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm looking into majordomo for a project I'm working on, as well as for my own use. There are 2 situations I'm looking for, and if you've dealt with them I'd love to hear from you. 1) majordomo used with a moderated list, particularly with multiple moderators 2) majordomo used under smail - I think this depends on smail supporting pipes, which I don't think it does, but if you know a workaround, let me know. You can mail directly to the list or reply to me - either way, replies are appreciated. | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5300 Advanced Network & Services Elmsford, NY From Majordomo-Users-Owner Tue Oct 5 09:14:21 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA04185; Tue, 5 Oct 93 16:01:18 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA04177; Tue, 5 Oct 93 09:01:03 PDT Message-Id: <9310051601.AA04177@mycroft.GreatCircle.COM> To: Karen Vazquez Cc: majordomo-users@GreatCircle.COM Subject: Re: ctime.pl In-Reply-To: Your message of Tue, 5 Oct 93 07:58:58 PDT Date: Tue, 05 Oct 1993 09:01:01 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Karen Vazquez writes: # # Hi # # Majordomo is looking for the file - ctime.pl. I don't # have this file on my system. Where can I get this? # # Thanks, Karen It's part of the standard perl release. It's usually installed in /usr/local/lib/perl, but that depends on how you configured perl when you installed it. If your version of perl doesn't have it, you don't have a recent enough version to run Majordomo, and you need to get a newer version. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Wed Oct 6 03:14:53 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA06717; Wed, 6 Oct 93 08:56:46 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA06710; Wed, 6 Oct 93 01:56:37 PDT Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA01087; Wed, 6 Oct 93 01:57:40 PDT Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0okSlJ-00030ZC; Tue, 5 Oct 93 23:54 PDT Message-Id: From: Alan Millar Subject: Re: majordomo with moderators To: dans@ans.net (Dan Simoes) Date: Tue, 5 Oct 1993 23:54:11 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199310051522.AA81950@foo.ans.net> from "Dan Simoes" at Oct 5, 93 11:22:38 am Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1314 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Dan Simoes spake of these matters: > I'm looking into majordomo for a project I'm working on, as > well as for my own use. There are 2 situations I'm looking > for, and if you've dealt with them I'd love to hear from you. > > 1) majordomo used with a moderated list, particularly with > multiple moderators I haven't dealt with it myself, but in general this is a message distribution issue and not a subscription issue. Therefore Majordomo won't have much. The "resend" script is updated regularly, so I don't know where it stands now. > 2) majordomo used under smail - I think this depends on smail > supporting pipes, which I don't think it does, but if you know > a workaround, let me know. SMail 3.1 works just fine; I use it. It is a fairly complete drop-in replacement for sendmail in most functions, with only a few minor cosmetic differences. SMail 2.5 is old enough that you probably don't want it, but I seem to remember it supporting pipes anyways. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ Ren: Stimpy, your wealth of ignorance astounds me! Stimpy: They don't call me stupid for nothing! From Majordomo-Users-Owner Wed Oct 6 15:12:58 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA07395; Wed, 6 Oct 93 15:12:58 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA07387; Wed, 6 Oct 93 08:12:30 PDT Message-Id: <9310061512.AA07387@mycroft.GreatCircle.COM> To: Alan Millar Cc: dans@ans.net (Dan Simoes), majordomo-users@GreatCircle.COM Subject: Re: majordomo with moderators In-Reply-To: Your message of Tue, 5 Oct 1993 23:54:11 -0800 (PDT) Date: Wed, 06 Oct 1993 08:12:28 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Alan Millar writes: # And verily didst Dan Simoes spake of these matters: # > I'm looking into majordomo for a project I'm working on, as # > well as for my own use. There are 2 situations I'm looking # > for, and if you've dealt with them I'd love to hear from you. # > # > 1) majordomo used with a moderated list, particularly with # > multiple moderators # # I haven't dealt with it myself, but in general this is a message # distribution issue and not a subscription issue. Therefore # Majordomo won't have much. The "resend" script is updated # regularly, so I don't know where it stands now. Yes, resend now supports moderation. See the "resend.README" file in the current distribution. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Thu Oct 7 01:23:45 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA08513; Thu, 7 Oct 93 01:23:45 GMT Received: from de5.ctd.ornl.gov by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA07856; Wed, 6 Oct 93 11:59:47 PDT Received: by de5.ctd.ornl.gov id AA17928 (5.65a/IDA-1.4.2 for majordomo-users@greatcircle.com); Wed, 6 Oct 93 15:03:06 -0400 Date: Wed, 6 Oct 93 15:03:06 -0400 From: Dave Sill Message-Id: <9310061903.AA17928@de5.ctd.ornl.gov> To: majordomo-users@GreatCircle.COM Subject: Two questions Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk 1) How hard would it be to have Majordomo verify that the addresses specified in unsubscribe requests are actually subscribed? If this is in the current release, please excuse me. 2) Why doesn't Majordomo process commands in the Subject? Seems like a trivial hack to check it, and it'd sure be convenient. Again, if it's in the current release, please excuse me. -- Dave Sill (de5@ornl.gov) Computers should work the way beginners Martin Marietta Energy Systems expect them to, and one day they will. Workstation Support -- Ted Nelson From Majordomo-Users-Owner Thu Oct 7 02:16:07 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA08770; Thu, 7 Oct 93 02:16:07 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA08614; Wed, 6 Oct 93 18:32:38 PDT Message-Id: <9310070132.AA08614@mycroft.GreatCircle.COM> To: Dave Sill Cc: majordomo-users@GreatCircle.COM Subject: Re: Two questions In-Reply-To: Your message of Wed, 6 Oct 93 15:03:06 -0400 Date: Wed, 06 Oct 1993 18:32:36 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dave Sill writes: # 1) How hard would it be to have Majordomo verify that the addresses # specified in unsubscribe requests are actually subscribed? If this # is in the current release, please excuse me. It is in the current release. # 2) Why doesn't Majordomo process commands in the Subject? Seems like # a trivial hack to check it, and it'd sure be convenient. Again, if # it's in the current release, please excuse me. Because I was in a hurry when I wrote it, and didn't want to merge the subject line into the body. Now, "everybody knows" that Majordomo doesn't process commands in the subject line, and people would bitch if I changed that. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Thu Oct 7 06:43:29 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA10382; Thu, 7 Oct 93 06:43:29 GMT Received: from tsunami.berkeley.edu (tsunami-ether.Berkeley.EDU) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA10375; Wed, 6 Oct 93 23:43:19 PDT Received: by tsunami.berkeley.edu (5.65c/CHAOS) id AA21004; Wed, 6 Oct 1993 23:46:27 -0700 Date: Wed, 6 Oct 1993 23:46:27 -0700 From: Dave Friedman Message-Id: <199310070646.AA21004@tsunami.berkeley.edu> To: majordomo-users@GreatCircle.COM Subject: mail -v majorc Cc: @ocf.Berkeley.EDU Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk  From Majordomo-Users-Owner Thu Oct 7 06:49:04 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA10407; Thu, 7 Oct 93 06:49:04 GMT Received: from tsunami.berkeley.edu (tsunami-ether.Berkeley.EDU) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA10400; Wed, 6 Oct 93 23:48:57 PDT Received: by tsunami.berkeley.edu (5.65c/CHAOS) id AA21111; Wed, 6 Oct 1993 23:52:15 -0700 Date: Wed, 6 Oct 1993 23:52:15 -0700 From: Dave Friedman Message-Id: <199310070652.AA21111@tsunami.berkeley.edu> To: majordomo-users@GreatCircle.COM Subject: Question on installation Cc: \davidf@tsunami.berkeley.edu Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk First, sorry about that last message. My machine went slightly berzerk as I was trying to type. I'm trying to install majordomo on an Apollo DN3500/4500 token ring network. EWWe are running DOMAIN'/OS 10.4. I'm wondering what exactly has to go on the alias line for majordomo itesself - According to all the docs it's: majordomo: "|include /mycroft/brent/majordomo/wrapper majordomo" But on my system, the wrapper is in //planecrash/accounts/domo/bin/wrapper And the username is domo. But wherther I put majordomo: "|//planecrash/accounts/domo/bin/wrapper majordomo" or majordomo: "|//planecrash/accounts/domo/bin/wrapper domo" It complainms that 'majordomo: directory does not exist' or 'domo: direectory does not exist'. When I finally changed all that to majordomo: "|p//poalanecrash/accounts/domo/bin/wrapper //planecrash/accounts/domo" it complained about insecure usage, even though this is noat a true POSIX machine. Attemnpting to compile with the POSICX options causes the make to fail. I've got all files chown'd domo.domo, except /wrapper, which is daemon.domo. Can anyone explain what they might thingk is wrong? Sorry for the long post, but I find it helps to give more details... -Dave Friedman davidf@ocf.Berkeley.EDU From Majordomo-Users-Owner Fri Oct 8 15:04:20 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA15446; Fri, 8 Oct 93 15:04:20 GMT Received: from zoso.quintus.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA15439; Fri, 8 Oct 93 08:04:05 PDT From: Karen Vazquez Date: Fri, 8 Oct 93 08:06:51 PDT Message-Id: <935.9310081506@zoso.quintus.com> Received: from quintus.com (niners.quintus.com) by zoso.quintus.com; Fri, 8 Oct 93 08:06:51 PDT To: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello: I've installed majordomo on our mailhost in a directory local to the mailhost and not exported. My majordomo.cf file looks like this: $whereami = "quintus.com"; $whoami = "wpadmin@$whereami"; $whoami_owner = "wpadmin-owner@$whereami"; $homedir = "/usr/majordomo $listdir = "/usr/majordomo/mlists"; $log = "$homedir/Log"; $mailer = "/usr/lib/sendmail -f\$sender \$to"; If I try to mail on the mailhost with the wpadmin alias set up in yellow pages, this is what happens: karen@zoso 9: mail -v wpadmin Subject: help From Majordomo-Users-Owner Fri Oct 8 15:38:06 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA15679; Fri, 8 Oct 93 15:38:06 GMT Received: from zoso.quintus.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA15671; Fri, 8 Oct 93 08:37:45 PDT From: Karen Vazquez Date: Fri, 8 Oct 93 08:41:25 PDT Message-Id: <1143.9310081541@zoso.quintus.com> Received: from quintus.com (niners.quintus.com) by zoso.quintus.com; Fri, 8 Oct 93 08:41:25 PDT To: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello: Sorry for the last message - this is my entire question: I've installed majordomo on our mailhost in a directory local to the mailhost and not exported. My majordomo.cf file looks like this: $whereami = "quintus.com"; $whoami = "wpadmin@$whereami"; $whoami_owner = "wpadmin-owner@$whereami"; $homedir = "/usr/majordomo $listdir = "/usr/majordomo/mlists"; $log = "$homedir/Log"; $mailer = "/usr/lib/sendmail -f\$sender \$to"; If I try to mail on the mailhost with the wpadmin alias set up in yellow pages, this is what happens: karen@zoso 9: mail -v wpadmin Subject: help EOT karen@zoso 10: wpadmin... aliased to "|/usr/majordomo/wrapper majordomo" "|/usr/majordomo/wrapper majordomo"... Connecting to via prog... majordomo[646] {Karen Vazquez } help karen.vazquez@quintus.com... Recipient names must be specified Saving message in /usr/majordomo/dead.letter /usr/majordomo/dead.letter... Can't create output "|/usr/majordomo/wrapper majordomo"... Sent If I try to mail on the mailhost with the wpadmin alias not exported in yellow pages, this is what happens: karen@zoso 11: mail -v wpadmin Subject: help EOT karen@zoso 12: Warning: alias database out of date wpadmin... User unknown Saving message in /q/apg/home/karen/dead.letter /q/apg/home/karen/dead.letter... Sent Everything works fine with a standalone system; however as soon as I try it in our yellowpages environment, I get the errors. Any ideas on what this means: karen.vazquez@quintus.com... Recipient names must be specified Any help on this would be appreciated. Thanks, Karen From Majordomo-Users-Owner Fri Oct 8 18:42:11 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA16082; Fri, 8 Oct 93 18:42:11 GMT Received: from david.zfe.siemens.de by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA16075; Fri, 8 Oct 93 11:41:37 PDT Received: from ztivax.zfe.siemens.de by david.zfe.siemens.de with SMTP id AA04152 (5.65c/IDA-1.4.4 for ); Fri, 8 Oct 1993 19:44:19 +0100 Received: from hl.siemens.de (dumbo.hl.siemens.de) by ztivax.zfe.siemens.de with SMTP id AA29992 (5.65c/IDA-1.4.4 for ); Fri, 8 Oct 1993 19:44:29 +0100 Received: from troja.hl.siemens.de by hl.siemens.de (4.1/SMI-4.1) id AA11902; Fri, 8 Oct 93 19:44:42 +0100 Received: from ricochet.hl.siemens.de by troja.hl.siemens.de (4.1/SMI-4.1-Ag-1.0-pwo-42) id AA10630; Fri, 8 Oct 93 19:43:03 +0100 From: pwo@troja.hl.siemens.de (Peter W Osel) Message-Id: <9310081843.AA10630@troja.hl.siemens.de> Subject: Shall we add these features to majordomo? To: majordomo-users@GreatCircle.COM Date: Fri, 8 Oct 1993 19:43:06 +0100 (MET) Organization: Siemens AG, HL CAD 44, Munich, Germany Phone: +49 (89) 4144-3825 X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1054 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I would like to be able to define the type of mailing list (closed, open, private) as a function of where the mail comes from. i.e. I have a mailing list, where all users of my own domain shall be allowed to join, but all requests from one external domain have to be approved, and requests from all other domains shall be piped to /dev/null. I think of a lists/mailing-list.cfg file: # This is the configuration file for mailing list mailing-list local accept # Accept everyone from own domain *.xy.de accept # ... and from domain xy.de *.friend.com approve # But requests from friend.com have to be approved * reject # Throw away all other request This configuration file could also be extended to define whether a list is private, is archived, etc. What do you think about this feature? Any takers? --pwo -- Peter W. Osel Email: pwo@zfe.siemens.de Siemens AG - HL CAD 4 Phone: +49 (89) 4144-3825 PO Box: 80 17 09 Fax: +49 (89) 4144-8159 D-81617 Munich Home: pwo@guug.de Fed. Rep. of Germany Home (Voice): +49 (89) 613-6209 From Majordomo-Users-Owner Fri Oct 8 19:03:22 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA16130; Fri, 8 Oct 93 19:03:22 GMT Received: from alfred.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA16123; Fri, 8 Oct 93 12:03:12 PDT Received: from spiff.YP.nobel (spiff.ccs.carleton.ca) by alfred.ccs.carleton.ca (4.1/SMI-4.0) id AA05849; Fri, 8 Oct 93 15:06:05 EDT From: mcr@ccs.carleton.ca (Michael Richardson) Received: by spiff.YP.nobel (4.1/Sun-Client) id AA18292; Fri, 8 Oct 93 15:07:21 EDT Date: Fri, 8 Oct 93 15:07:21 EDT Message-Id: <9310081907.AA18292@spiff.YP.nobel> To: pwo@troja.hl.siemens.de Cc: majordomo-users@GreatCircle.COM In-Reply-To: Peter W Osel's message of Fri, 8 Oct 1993 19:43:06 +0100 (MET) <9310081843.AA10630@troja.hl.siemens.de> Subject: Shall we add these features to majordomo? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >>>>> "pwo" == Peter W Osel writes: pwo> I would like to be able to define the type of mailing list pwo> (closed, open, private) as a function of where the mail comes pwo> from. i.e. I have a mailing list, where all users of my own Hmm. Funny you should mention this. pwo> This configuration file could also be extended to define pwo> whether a list is private, is archived, etc. What I want to do is change my welcome message depending on whether I think the subscriber is on an open portion of the internet or not. I think I can make some pretty educated guesses. a) if the host is ping'able, then probably. I might go to the extent of trying to open a telnet, or doing a finger, but I don't think this is very social. b) if the host doesn't exist, but MX's to a host that is pingable, and the host is a more general form of the MX host. (This isn't worded right. I mean say ccs.carleton.ca MX's to alfred.ccs.carleton.ca), then yes. This should take care of people that are on internal domains, like, say Sun or HP. It fails for bnr.ca for instance though. I'll probably be pessimistic about MX hosts that include things like 'relay' or 'gateway' in their names. Since, the real reason I want to do this is because many subscribers won't know the difference themselves, I figure an educated guess (with a warning) is pretty good. People who live behind too restrictive firewalls will have to settle for reading the e-journal by email. The mailing list exists to make table of contents announcements and remind people on how to read the articles via WWW/gopher. If I'm sure they are on the open internet, (which academics tend to be if they are on the internet at all) then I don't want to mention email-access to them at all, except as an ``if you can't do any of these things, please get other file'' pwo> What do you think about this feature? Any takers? I plan on making it possible to run an external command to make a decision. I realize that this isn't exactly what you want. From Majordomo-Users-Owner Fri Oct 8 21:10:44 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA16423; Fri, 8 Oct 93 21:10:44 GMT Received: from terc.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA22923; Fri, 1 Oct 93 12:08:27 PDT Received: from qm.terc.edu by terc.edu (4.1/SMI-4.1) id AA17648; Fri, 1 Oct 93 15:10:05 EST Message-Id: <9310012010.AA17648@terc.edu> Date: 1 Oct 1993 15:11:48 -0500 From: "Stephen Bannasch" Subject: multiple unsubscribes To: Majordomo-Users@GreatCircle.COM Cc: andrew_boyd@terc.edu, blake_meike@terc.edu Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Subject: multiple unsubscribes I am the owner of a list and wanted to remove a bunch a bad addresses so I tried the following commands: approve PASSWORD unsubscribe MYLIST USER1 approve PASSWORD unsubscribe MYLIST USER2 approve PASSWORD unsubscribe MYLIST USER3 Majordomo responded by only unsubcribing the first person on the list. The second and third were reported as not being members of MYLIST. When the unsubscribe requests for users 2 and 3 were placed in their own messages the unsubscribe operations were successful. Is this a bug? Is there a fix? --thanks, Stephen Bannasch From Majordomo-Users-Owner Fri Oct 8 21:26:03 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA16578; Fri, 8 Oct 93 21:26:03 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA16563; Fri, 8 Oct 93 14:25:44 PDT Message-Id: <9310082125.AA16563@mycroft.GreatCircle.COM> To: "Stephen Bannasch" Cc: Majordomo-Users@GreatCircle.COM, andrew_boyd@terc.edu, blake_meike@terc.edu Subject: Re: multiple unsubscribes In-Reply-To: Your message of 1 Oct 1993 15:11:48 -0500 Date: Fri, 08 Oct 1993 14:25:43 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Stephen Bannasch" writes: # Subject: multiple unsubscribes # I am the owner of a list and wanted to remove a bunch a bad addresses # so I tried the following commands: # # approve PASSWORD unsubscribe MYLIST USER1 # approve PASSWORD unsubscribe MYLIST USER2 # approve PASSWORD unsubscribe MYLIST USER3 # # Majordomo responded by only unsubcribing the first person on the # list. # The second and third were reported as not being members of MYLIST. # When # the unsubscribe requests for users 2 and 3 were placed in their own # messages the unsubscribe operations were successful. # # Is this a bug? Is there a fix? It should work. I suspect some sort of locking/caching problem. Are your list files on the local disk of the machine Majordomo is running on, or are they accessed via NFS? -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Sat Oct 9 00:05:16 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA17556; Sat, 9 Oct 93 00:05:16 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA17547; Fri, 8 Oct 93 17:05:08 PDT Message-Id: <9310090005.AA17547@mycroft.GreatCircle.COM> To: majordomo-users@GreatCircle.COM, majordomo-docs@GreatCircle.COM Subject: New UNIX online manual page for Majordomo Date: Fri, 08 Oct 1993 17:05:07 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Appended is a new online UNIX manual page for Majordomo, courtesy of Jim Duncan . This will be in the next Majordomo release. Thanks, Jim! -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 .TH MAJORDOMO 8 .SH NAME Majordomo \- manage multiple mailing lists .SH SYNOPSIS .B Majordomo .SH "DESCRIPTION" .B Majordomo is a perl script which automates the management of Internet mailing lists. It is executed via electronic mail; users send e-mail to .B Majordomo with instructions in the body of the message, and the perl script performs the requested actions and responds with the results. Any text in the "Subject:" line is ignored. .SH "COMMANDS" .B Majordomo understands the following commands (arguments in "[]" are optional): .TP 5 .B subscribe \fIlist\fR [\fIaddress\fR] .P Subscribe yourself (or .I address if specified) to the named .IR list . .TP 5 .B unsubscribe \fIlist\fR [\fIaddress\fR] .P Unsubscribe yourself (or .I address if specified) from the named .IR list . .TP 5 .B get \fIlist\fR \fIfile\fR .P Get the .I file related to .IR list . .TP 5 .B index \fIlist\fR .P Return an index of the files you can .I get associated with .IR list . .TP 5 .B which [\fIaddress\fR] .P Find out to which lists you (or .I address if specified) are subscribed. .TP 5 .B who \fIlist\fR .P Find out who is on the named .IR list . .TP 5 .B info \fIlist\fR .P Retrieve the general introductory information for the named .IR list . .TP 5 .B lists .P Show the lists served by this Majordomo server. .TP 5 .B help .P Retrieve an informational message, a brief synopsis of the user portion of this manual page. .TP 5 .B end .P Stop processing commands (useful if your mailer adds a signature). .PP In addition, the owner of the list can issue the following commands: .TP 5 .B approve \fIpassword\fR subscribe \fIlist\fR \fIaddress\fR .P Instruct Majordomo to add .I address to .IR list . The password is required to authenticate the list owner. This is very weak authentication as the password is transmitted in the clear in an e-mail message. No claims are made that it will provide anything other than rudimentary protection against abuse of the Majordomo server. .TP 5 .B approve \fIpassword\fR unsubscribe \fIlist\fR \fIaddress\fR .P Instruct Majordomo to delete .I address from .IR list . The password is required to authenticate the list owner. See the comments above regarding the password. .TP 5 .B newinfo \fIlist\fR \fIpassword\fR .P Update the informational message for .I list with the text which follows on subsequent lines. No formatting of the message occurs, so the list owner should be careful to constrain the message to eighty columns. Majordomo will include everything up to the string .B EOF or to the end of the mail message, whichever comes first. This is useful in case the owner wants to verify the new message immediately, e.g., .sp 1 .RS 10 To: majordomo .sp 0 newinfo list password .sp This is new information for the "list" list. .sp EOF .sp 0 info list .sp .RE .RS 5 This will simultaneously update the information for the list, and then retrieve it for verification. Note that blank lines are preserved in the message. .RE .TP 5 .B passwd \fIlist\fR \fIold-password\fR \fInew-password\fR .P Replace the password for .I list with .IR new-password . .SH CONFIGURATION .B Majordomo supports .I open and .I closed lists. An .I open list is one to which anyone can subscribe themselves. A subscription request sent to .B Majordomo for a .I closed list is forwarded to the owner of the list for approval. If a user tries to subscribe an address which is different from their own (for example, a local list exploder), .B Majordomo will forward the request to the list owner for approval, regardless of the open or closed status of the list. .PP .B Majordomo depends on the existence of certain system mail aliases. The first three are for running the perl script on incoming e-mail and specifying the responsible person in charge of the server: .sp 1 majordomo: "|/usr/local/mail/majordomo/wrapper majordomo" .sp 0 majordomo-owner: brent .sp 0 owner-majordomo: brent .sp 1 These next few aliases are for a list called "sample": .sp 1 sample: :include:/usr/local/mail/lists/sample .sp 0 owner-sample: sample-owner .sp 0 sample-request: "|/usr/local/mail/majordomo/wrapper request-answer sample" .sp 0 owner-sample-request: sample-owner .sp 0 sample-owner: brent .sp 0 sample-approval: brent .sp 1 .SH FILES /etc/majordomo.cf .sp 0 /usr/local/lib/mail/majordomo/ .SH AUTHORS Majordomo and most of the ancillary perl code was written by Brent Chapman, . The latest version of the code is available by anonymous FTP from FTP.GreatCircle.COM, in directory pub/majordomo. This man page was written by Jim Duncan, . From Majordomo-Users-Owner Sat Oct 9 22:36:51 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA20707; Sat, 9 Oct 93 22:36:51 GMT Received: from relay2.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA18398; Fri, 8 Oct 93 21:06:22 PDT Received: from unpc.queernet.org by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA19848; Sat, 9 Oct 93 00:09:40 -0400 Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0olVcd-000MS7C; Fri, 8 Oct 93 21:09 PDT Message-Id: To: "Stephen Bannasch" Cc: Majordomo-Users@GreatCircle.COM, andrew_boyd@terc.edu, blake_meike@terc.edu Subject: Re: multiple unsubscribes In-Reply-To: Your message of 01 Oct 93 15:11:48 -0500. <9310012010.AA17648@terc.edu> Date: Fri, 08 Oct 93 21:09:34 PDT From: rogerk@queernet.org Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I am the owner of a list and wanted to remove a bunch a bad addresses > so I tried the following commands: > > approve PASSWORD unsubscribe MYLIST USER1 > approve PASSWORD unsubscribe MYLIST USER2 > approve PASSWORD unsubscribe MYLIST USER3 > > Majordomo responded by only unsubcribing the first person on the > list. > The second and third were reported as not being members of MYLIST. > When > the unsubscribe requests for users 2 and 3 were placed in their own > messages the unsubscribe operations were successful. > > Is this a bug? Is there a fix? What version are you running? There was a bug like this, involving locking logic I think, in earlier versions. (PS: Hi, Blake!) --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From Majordomo-Users-Owner Sun Oct 10 17:19:53 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23003; Sun, 10 Oct 93 17:19:53 GMT Received: from cgl.ucsf.EDU by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA22996; Sun, 10 Oct 93 10:19:46 PDT Received: from ccnext.ucsf.EDU by cgl.ucsf.EDU (5.65/GSC4.22) id AA17211 for majordomo-users@greatcircle.com; Sun, 10 Oct 93 10:23:09 -0700 Received: by ccnext.ucsf.edu (NeXT-1.0 (From Sendmail 5.52)/NeXT-1.0) id AA24985; Sun, 10 Oct 93 10:22:12 PDT Date: Sun, 10 Oct 93 10:22:12 PDT From: dick@ccnext.ucsf.edu (Dick Karpinski) Message-Id: <9310101722.AA24985@ccnext.ucsf.edu> To: majordomo-users@GreatCircle.COM Subject: Majordomo on AIX (RISC/6000) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk If you get the permissions screwed up, majordomo manages to try some six hundred times and thus generates quarter-megabyte error mails to postmaster about the problem. This suggests that an early mod might reduce the loop counts for initial testing. The Makefile and README files might be adjusted to indicate that the literal 15 for gid for POSIX should be changed to the actual gid for the directory where lists live. If they already say that, I did not notice it, so please point it out to me. Could the Makefile discover whether the BSD or POSIX style version were appropriate by itself? Could it reset the gid to match the list directory on its own? I think I got everything right the first time, except for those two. Dick Dick Karpinski Minicomputer Manager, UCSF Information Technology Services Domain: dick@ccnext.ucsf.edu FAX: (415) 476-5523 (415) 476-4529 (10-6) BITNET: dick@ucsfvm (510) 658-6803 (Home) USPS: Box 0704 UCSF, San Francisco, CA 94143-0704 (510) 658-3797 (ans) Dick Karpinski dick@ccnext Ad for the day: LET EVERYBODY HELP Point Gopher at itsa.ucsf.edu (port 70) and take a look at "A Guide to Questions, Answers, and Information about Everything" in "Questions, ...", in "Computers...", in the root menu. Send email. From Majordomo-Users-Owner Sun Oct 10 18:17:32 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23066; Sun, 10 Oct 93 18:17:32 GMT Received: from illuminati.IO.COM by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23059; Sun, 10 Oct 93 11:17:26 PDT Received: by illuminati.IO.COM (5.67/PERFORMIX-0.9/08-16-92) id AA00679; Sun, 10 Oct 93 13:18:27 -0500 From: zeek@IO.COM (zeek) Message-Id: <9310101818.AA00679@illuminati.IO.COM> Subject: compiling problem... To: majordomo-users@GreatCircle.COM (majord) Date: Sun, 10 Oct 1993 13:18:26 -40962758 (CDT) In-Reply-To: from "root@underg.ucf.org" at Oct 8, 93 09:12:00 pm X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 761 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In compiling the wrapper on a LINUX system, we (the computer and I) experienced the following problem below: /home/zeek/Md> make cc -DBIN=\"/usr/local/etc/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -Dc wrapper.c: In function `main': wrapper.c:65: warning: comparison between pointer and integer This machine is running Smail, which I think has been causing additional problems. Is it necessary to run Sendmail in order for major-d to run? Please let me know if any of you have suggestions/answers/questions. Thank you, -zeek ps. This has been an excellent list, very informative. I'm currently running majordomo on a university machine (3 lists), but moving it to something privately owned so I don't have to bother the sysadmins at ut. From Majordomo-Users-Owner Sun Oct 10 18:39:27 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23099; Sun, 10 Oct 93 18:39:27 GMT Received: from relay2.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23092; Sun, 10 Oct 93 11:39:20 PDT Received: from unpc.queernet.org by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA25177; Sun, 10 Oct 93 14:27:05 -0400 Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0om5U3-000MS1C; Sun, 10 Oct 93 11:27 PDT Message-Id: To: zeek@IO.COM (zeek) Cc: majordomo-users@GreatCircle.COM (majord) Subject: Re: compiling problem... In-Reply-To: Your message of Sun, 10 Oct 93 13:18:26 -0800. <9310101818.AA00679@illuminati.IO.COM> Date: Sun, 10 Oct 93 11:27:06 PDT From: rogerk@queernet.org Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > /home/zeek/Md> make > cc -DBIN=\"/usr/local/etc/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -Dc > wrapper.c: In function `main': > wrapper.c:65: warning: comparison between pointer and integer It's a warning; it can probably be avoided with type-casting voodoo. > This machine is running Smail, which I think has been causing additional > problems. Is it necessary to run Sendmail in order for major-d to run? Nope. I'm running smail-3.1.28, and have been (with Majordomo) for the better part of a year. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From Majordomo-Users-Owner Sun Oct 10 19:05:35 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23175; Sun, 10 Oct 93 19:05:35 GMT Received: from illuminati.IO.COM by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23168; Sun, 10 Oct 93 12:05:28 PDT Received: by illuminati.IO.COM (5.67/PERFORMIX-0.9/08-16-92) id AA01405; Sun, 10 Oct 93 14:05:55 -0500 From: zeek@IO.COM (zeek) Message-Id: <9310101905.AA01405@illuminati.IO.COM> Subject: type-cast voodoo (?) To: rogerk@queernet.org Date: Sun, 10 Oct 1993 14:05:54 -40962758 (CDT) Cc: majordomo-users@GreatCircle.COM (majord) In-Reply-To: from "rogerk@queernet.org" at Oct 10, 93 11:27:06 am X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 837 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Roger, *> It's a warning; it can probably be avoided with type-casting voodoo. Sorry, I'm not aware of "type-casting voodoo", sounds very strange. Where should I look to correct this problem? *> > problems. Is it necessary to run Sendmail in order for major-d to run? *> Nope. I'm running smail-3.1.28, and have been (with Majordomo) for the better *> part of a year. I think I'm running the same version (the machine is only accessible dial-up, 1 line) so it may take me awhile to check this. Are there any special considerations to take into mind with smail? Thanks for the help, -z ps. Please forgive the begging, I'm a humanities student with an obsessive interest in computer mediated commo, I really don't know much about the real guts of these machines, but I'm willing to thrash with the obstacles and learn. From Majordomo-Users-Owner Sun Oct 10 19:08:08 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23189; Sun, 10 Oct 93 19:08:08 GMT Received: from relay2.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23182; Sun, 10 Oct 93 12:08:02 PDT Received: from unpc.queernet.org by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA01850; Sun, 10 Oct 93 15:11:26 -0400 Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0om6Av-000MS1C; Sun, 10 Oct 93 12:11 PDT Message-Id: To: zeek@IO.COM (zeek) Cc: majordomo-users@GreatCircle.COM (majord) Subject: Re: type-cast voodoo (?) In-Reply-To: Your message of Sun, 10 Oct 93 14:05:54 -0800. <9310101905.AA01405@illuminati.IO.COM> Date: Sun, 10 Oct 93 12:11:22 PDT From: rogerk@queernet.org Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > *> It's a warning; it can probably be avoided with type-casting voodoo. > > Sorry, I'm not aware of "type-casting voodoo", sounds very strange. Where > should I look to correct this problem? "Oh, stewardess, I speak geek..." Sorry. It is a by-product of too-strict compilers and/or sloppy coding (knowing the author, my money's on the former). I think I wouldn't do anything about it were I you. > I think I'm running the same version (the machine is only accessible > dial-up, 1 line) so it may take me awhile to check this. Are there any > special considerations to take into mind with smail? Absolutely none, especially if you have the link of "sendmail" to smail set up as the installation procedures state. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From Majordomo-Users-Owner Sun Oct 10 19:46:16 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23233; Sun, 10 Oct 93 19:46:16 GMT Received: from illuminati.IO.COM by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23226; Sun, 10 Oct 93 12:46:09 PDT Received: by illuminati.IO.COM (5.67/PERFORMIX-0.9/08-16-92) id AA01759; Sun, 10 Oct 93 14:46:41 -0500 From: zeek@IO.COM (zeek) Message-Id: <9310101946.AA01759@illuminati.IO.COM> Subject: Re: New UNIX online manual page for Majordomo To: brent@GreatCircle.COM (Brent Chapman) Date: Sun, 10 Oct 1993 14:46:40 -40962758 (CDT) Cc: majordomo-users@GreatCircle.COM (majord) In-Reply-To: <9310090005.AA17547@mycroft.GreatCircle.COM> from "Brent Chapman" at Oct 8, 93 05:05:07 pm X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 305 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Well, I removed all the unecessary text from this manual page (mailer header, etc.), renamed it majordomo.1, copied it to the /man directory, but "man majordomo" does not respond. Does this need to be "troff-ed" or put through some other special treatment? I'm obviously missing something. :| -z From Majordomo-Users-Owner Sun Oct 10 19:56:07 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23252; Sun, 10 Oct 93 19:56:07 GMT Received: from relay2.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23245; Sun, 10 Oct 93 12:56:00 PDT Received: from unpc.queernet.org by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA09153; Sun, 10 Oct 93 15:58:52 -0400 Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0om6uu-000MS1C; Sun, 10 Oct 93 12:58 PDT Message-Id: To: zeek@IO.COM (zeek) Cc: majordomo-users@GreatCircle.COM (majord) Subject: Re: New UNIX online manual page for Majordomo In-Reply-To: Your message of Sun, 10 Oct 93 14:46:40 -0800. <9310101946.AA01759@illuminati.IO.COM> Date: Sun, 10 Oct 93 12:58:55 PDT From: rogerk@queernet.org Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Well, I removed all the unecessary text from this manual page (mailer > header, etc.), renamed it majordomo.1, copied it to the /man directory, > but "man majordomo" does not respond. Does this need to be "troff-ed" or > put through some other special treatment? > Depends on your UNIX. What type of system, and what operating system, are you running? Some will nroff the page at request-time; others need it pre-processed. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From Majordomo-Users-Owner Sun Oct 10 21:38:00 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23447; Sun, 10 Oct 93 21:38:00 GMT Received: from tsunami.berkeley.edu (tsunami-ether.Berkeley.EDU) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23440; Sun, 10 Oct 93 14:37:45 PDT Received: by tsunami.berkeley.edu (5.65c/CHAOS) id AA06767; Sun, 10 Oct 1993 14:40:33 -0700 Date: Sun, 10 Oct 1993 14:38:00 From: Dave Friedman Subject: Re: New UNIX online manual page for Majordomo To: zeek@io.com Cc: majord In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk zeek: > > Well, I removed all the unecessary text from this manual page (mailer > > header, etc.), renamed it majordomo.1, copied it to the /man directory, > > but "man majordomo" does not respond. Does this need to be "troff-ed" or > > put through some other special treatment? > > > rogerk: > Depends on your UNIX. What type of system, and what operating system, > are you running? Some will nroff the page at request-time; others need it > pre-processed. Just as far as what *I* had to do... I went through a lot of fumbling to figure out where it goes. I searched and searched to find /usr/man/man8. It didn't exist. Finally, I found it. I had to rename it to majordomo.8 and put it in /usr/local/man/man8. If that doesn't work, then your system most likely requires preprocessing. Dave Friedman davidf@ocf.Berkeley.EDU From Majordomo-Users-Owner Sun Oct 10 21:47:20 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23531; Sun, 10 Oct 93 21:47:20 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23504; Sun, 10 Oct 93 14:45:41 PDT Message-Id: <9310102145.AA23504@mycroft.GreatCircle.COM> To: Dave Friedman Cc: zeek@io.com, majord Subject: Re: New UNIX online manual page for Majordomo In-Reply-To: Your message of Sun, 10 Oct 1993 14:38:00 Date: Sun, 10 Oct 1993 14:45:39 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dave Friedman writes: # zeek: # > > Well, I removed all the unecessary text from this manual page (mailer # > > header, etc.), renamed it majordomo.1, copied it to the /man directory, # > > but "man majordomo" does not respond. Does this need to be "troff-ed" or # > > put through some other special treatment? # > > # > # rogerk: # > Depends on your UNIX. What type of system, and what operating system, # > are you running? Some will nroff the page at request-time; others need it # > pre-processed. # # Just as far as what *I* had to do... I went through a lot of fumbling to # figure out where it goes. I searched and searched to find /usr/man/man8. # It didn't exist. Finally, I found it. I had to rename it to majordomo.8 # and put it in /usr/local/man/man8. If that doesn't work, then your system # most likely requires preprocessing. I intentionally didn't say anything about where or how to install the man page, because that varies so much from system to system. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Sun Oct 10 15:14:36 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23573; Sun, 10 Oct 93 21:55:53 GMT Received: from illuminati.IO.COM by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA23566; Sun, 10 Oct 93 14:55:44 PDT Received: by illuminati.IO.COM (5.67/PERFORMIX-0.9/08-16-92) id AA03292; Sun, 10 Oct 93 16:56:08 -0500 From: zeek@IO.COM (zeek) Message-Id: <9310102156.AA03292@illuminati.IO.COM> Subject: getting that online manual page working... To: davidf@ocf.Berkeley.EDU (Dave Friedman) Date: Sun, 10 Oct 1993 16:56:07 -40962758 (CDT) Cc: majordomo-users@GreatCircle.COM (majord) In-Reply-To: from "Dave Friedman" at Oct 10, 93 02:38:00 pm X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 410 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Gee, I shouldn't have been a "lurker" for so long. You have all been very helpful! My friend and I are running LINUX on a 386/33 (33 I think). I'll go with the suggestions you have given me and see if that works. Since the computer (underg.ucf.org) is only accessible dialup, and we only have 1 line installed, it may take awhile until I get back with a report. Thanks! -z From Majordomo-Users-Owner Mon Oct 11 14:57:25 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA26270; Mon, 11 Oct 93 14:57:25 GMT Received: from dirac.scri.fsu.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA26263; Mon, 11 Oct 93 07:57:17 PDT Received: by dirac.scri.fsu.edu id AA96118 (5.65c/IDA-1.4.4 for Majordomo-Users@GreatCircle.COM); Mon, 11 Oct 1993 11:00:45 -0400 Date: Mon, 11 Oct 1993 11:00:45 -0400 From: Kingsley Kerce Message-Id: <199310111500.AA96118@dirac.scri.fsu.edu> To: Majordomo-Users@GreatCircle.COM Subject: Re: multiple unsubscribes Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Brent Chapman" writes: "Stephen Bannasch" writes: > # Subject: multiple unsubscribes > # I am the owner of a list and wanted to remove a bunch a bad addresses > # so I tried the following commands: > # > # approve PASSWORD unsubscribe MYLIST USER1 > # approve PASSWORD unsubscribe MYLIST USER2 > # approve PASSWORD unsubscribe MYLIST USER3 > # > # Majordomo responded by only unsubcribing the first person on the > # list. > # The second and third were reported as not being members of MYLIST. > # When > # the unsubscribe requests for users 2 and 3 were placed in their own > # messages the unsubscribe operations were successful. > # > # Is this a bug? Is there a fix? > > It should work. I suspect some sort of locking/caching problem. Are > your list files on the local disk of the machine Majordomo is running > on, or are they accessed via NFS? I'm having the same problem. The list files are definitely on the disk of the machine upon which Majordomo is running. I put some log statements in majordomo.pl, specifically in the is_list_member function. The function operates properly for the first call to it (from do_unsubscribe), but subsequent calls never enter the while loop after opening the list file. (Note that the open doesn't give an error.) Any ideas? Kingsley F. Kerce (kerce@scri.fsu.edu) Supercomputer Computations Research Institute Florida State University Tallahassee, FL, USA 32306 From Majordomo-Users-Owner Mon Oct 11 15:54:09 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA26452; Mon, 11 Oct 93 15:54:09 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA26442; Mon, 11 Oct 93 08:53:56 PDT Message-Id: <9310111553.AA26442@mycroft.GreatCircle.COM> To: Kingsley Kerce Cc: Majordomo-Users@GreatCircle.COM Subject: Re: multiple unsubscribes In-Reply-To: Your message of Mon, 11 Oct 1993 11:00:45 -0400 Date: Mon, 11 Oct 1993 08:53:54 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Kingsley Kerce writes: # I'm having the same problem. The list files are definitely on the # disk of the machine upon which Majordomo is running. # # I put some log statements in majordomo.pl, specifically in the # is_list_member function. The function operates properly for the first # call to it (from do_unsubscribe), but subsequent calls never enter the # while loop after opening the list file. (Note that the open doesn't # give an error.) This sounds like a perl bug. That code is pretty simple; it opens a file, reads through it, and closes the file. What you're describing makes it seem like it's opening the wrong file, or is opening the file but not starting at the beginning of it. You might try putting in a "seek(LIST, 0, 0);" after the "open" but before the "while" loop in the "is_list_member" function. It shouldn't be necessary, but it might help. Anybody having this problem, please tell me: Majordomo version (from a "help" command) Perl version (from "perl -v" output) Hardware platform Operating system release -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Mon Oct 11 23:31:00 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA28088; Mon, 11 Oct 93 23:31:00 GMT Received: from cactus.org by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA28079; Mon, 11 Oct 93 16:30:51 PDT Received: from underg.UUCP by cactus.org (4.1/SMI-4.1) id AA13948; Mon, 11 Oct 93 18:34:17 CDT Received: by underg.ucf.org (Smail3.1.28.1 #6) id m0omTpY-000023C; Mon, 11 Oct 93 15:26 CDT Message-Id: Subject: majordomo manual page To: majordomo-users@GreatCircle.COM Date: Mon, 11 Oct 1993 20:26:54 +0000 () Reply-To: zeek@underg.ucf.org From: zeek@underg.ucf.org X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 226 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I finally got the majordomo manual page to work over here. I copied the file to majordomo.8 and put it in the /usr/man/cat8 directory. -z ---- Underground Computing Foundation Public Access Linux -=- (512) 339-8221 From Majordomo-Users-Owner Tue Oct 12 07:55:27 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA29352; Tue, 12 Oct 93 07:55:27 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA29345; Tue, 12 Oct 93 00:55:18 PDT Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA05228; Tue, 12 Oct 93 00:46:12 PDT Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0omdtP-0002zCC; Tue, 12 Oct 93 00:11 PDT Message-Id: From: Alan Millar Subject: Re: type-cast voodoo (?) To: zeek@IO.COM (zeek) Date: Tue, 12 Oct 1993 00:11:34 -0800 (PDT) Cc: rogerk@queernet.org, majordomo-users@GreatCircle.COM In-Reply-To: <9310101905.AA01405@illuminati.IO.COM> from "zeek" at Oct 10, 93 02:05:54 pm Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1112 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I think I'm running the same version (the machine is only accessible > dial-up, 1 line) so it may take me awhile to check this. Are there any > special considerations to take into mind with smail? I'm running SMail 3.1.28 on Linux also, and I have encountered two very minor quirks. The first is that multi-line aliases (such as when using "resend") need backslash continuation lines like this: Imagen-L: "|/usr/local/mail/majordomo/wrapper resend -M 100000 \ -l Imagen-L -f Owner-Imagen-L -h Bolis.SF-Bay.org -s -R \ Imagen-L-outgoing" The other quirk I found is that mixing addresses with angle brackets <> and without in an aliase file sometimes has problems. The easy fix is to either turn on the .strip option for the list, or add a comma at the end of each address line. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ Ren: Stimpy, your wealth of ignorance astounds me! Stimpy: They don't call me stupid for nothing! From Majordomo-Users-Owner Tue Oct 12 23:39:12 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA01489; Tue, 12 Oct 93 23:39:12 GMT Received: from noc4.dccs.upenn.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA01482; Tue, 12 Oct 93 16:39:05 PDT Received: from CCAT.SAS.UPENN.EDU by noc4.dccs.upenn.edu id AA05040; Tue, 12 Oct 93 19:42:36 -0400 Received: by ccat.sas.upenn.edu (AIX 3.2/UCB 5.64/4.03) id AA39305; Tue, 12 Oct 1993 19:43:28 -0400 From: sysadmin@ccat.sas.upenn.edu (System Administrator) Message-Id: <9310122343.AA39305@ccat.sas.upenn.edu> Subject: Majordomo archive To: majordomo-users@GreatCircle.COM Date: Tue, 12 Oct 1993 19:43:27 -0400 (EDT) X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 724 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here are the aliases in my /usr/lib/aliases: ----------- mike: "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l mike -f michael -h ccat.sas.upenn.edu -s mike-outgoing" owner-mike: michael mike-outgoing: :include:/usr/local/majordomo/lists/mike, mike-archive owner-mike-outgoing: michael mike-archive: /usr/local/majordomo/archive/mike owner-mike-archive: michael mike-request: "|/usr/local/majordomo/wrapper request-answer mike" owner-mike-request: michael mike-approval: michael mike-owner: michael owner-mike-owner: michael ------------ What else should I do to get the messages archived ? The /usr/local/majordomo/archive directory exists. No error messages. No archived messages. Thank you. Michael. From Majordomo-Users-Owner Wed Oct 13 00:33:03 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA01658; Wed, 13 Oct 93 00:33:03 GMT Received: from relay1.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA01639; Tue, 12 Oct 93 17:32:51 PDT Received: from unpc.queernet.org by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA09100; Tue, 12 Oct 93 20:36:09 -0400 Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0omuBO-000MS1C; Tue, 12 Oct 93 17:35 PDT Message-Id: To: Alan Millar Cc: majordomo-users@GreatCircle.COM Subject: Re: type-cast voodoo (?) In-Reply-To: Your message of Tue, 12 Oct 93 00:11:34 -0800. Date: Tue, 12 Oct 93 17:35:13 PDT From: rogerk@queernet.org Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I'm running SMail 3.1.28 on Linux also, and I have encountered two > very minor quirks. The first is that multi-line aliases (such as when > using "resend") need backslash continuation lines like this: > > Imagen-L: "|/usr/local/mail/majordomo/wrapper resend -M 100000 \ > -l Imagen-L -f Owner-Imagen-L -h Bolis.SF-Bay.org -s -R \ > Imagen-L-outgoing" I didn't think of this one as a quirk, as I didn't think sendmail supported it either before you pointed out that it did... ;-) > The other quirk I found is that mixing addresses with angle brackets <> > and without in an aliase file sometimes has problems. The easy fix is > to either turn on the .strip option for the list, or add a comma at the > end of each address line. It doesn't "sometimes have problems"; this is a specific and deliberate mode of operation. Smail treats the entire expansion of an alias as a header field, and does not treat a newline as a field delimiter. So: joe bob sue is equivalent to "To: joe bob sue" And: Jimmy works the way you might expect. So: joe bob sue Jimmy is equivalent to "To: joe bob sue Jimmy " which only has one address in it. (Poor Joe Bob Sue Jimmy -- I wonder if Johnny Cash knows him?) --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From Majordomo-Users-Owner Wed Oct 13 12:49:03 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03600; Wed, 13 Oct 93 12:49:03 GMT Received: from bolero.rahul.net by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03593; Wed, 13 Oct 93 05:48:54 PDT Received: by bolero.rahul.net id AA11776 (5.65c/IDA-1.4.4 for Majordomo-Users@greatcircle.com); Wed, 13 Oct 1993 05:52:12 -0700 From: Kasuga Jingoro Message-Id: <199310131252.AA11776@bolero.rahul.net> Subject: Re: multiple unsubscribes To: kerce@dirac.scri.fsu.edu (Kingsley Kerce) Date: Wed, 13 Oct 1993 05:52:11 -0700 (PDT) Cc: Majordomo-Users@GreatCircle.COM In-Reply-To: <199310111500.AA96118@dirac.scri.fsu.edu> from "Kingsley Kerce" at Oct 11, 93 11:00:45 am Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2548 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > "Brent Chapman" writes: > "Stephen Bannasch" writes: > > # Subject: multiple unsubscribes > > # I am the owner of a list and wanted to remove a bunch a bad addresses > > # so I tried the following commands: > > # > > # approve PASSWORD unsubscribe MYLIST USER1 > > # approve PASSWORD unsubscribe MYLIST USER2 > > # approve PASSWORD unsubscribe MYLIST USER3 > > # > > # Majordomo responded by only unsubcribing the first person on the > > # list. > > # The second and third were reported as not being members of MYLIST. > > # When > > # the unsubscribe requests for users 2 and 3 were placed in their own > > # messages the unsubscribe operations were successful. > > # > > # Is this a bug? Is there a fix? This might be related to a related bug in Majordomo. This is a bug that was reported on this list ages ago but has never been fixed in the official release. In the do_unsubscribe subroutine, the file NEW is opened to write out the new version of the subscriber list. But this file is NEVER closed. The result is that the new version of the list is held open AND unlocked for the duration of the process. This can cause numerous problems, one of which may be the one you are experiencing. The problem I saw was that if one would place a unsub command followed by a sub command in the same message, the sub command would appear to work, but a later inspection of the list would show that the address was not added. My theory is that since the new version of the list is held open during the subscribe command, that the changes made to the file in the subscribe command will be superseded once the process ends since perl will then automatically close the NEW file which will revert the file back to the original contents after the unsub command. Although this bug does not manifest itself on Brent's system, this bug is legitimate and should be fixed in the official Majordomo release. The fix is trivial. Simply put a close(NEW); at a strategic place in the do_unsubscribe routine. I put it right before the block of code starting with the line 'if ($match_count == 1) {'. So, Brent, how about getting this bug fixed at last? ---- jingoro@tcp.com -- Jim Lick -- jingoro@rahul.net -- jIngOrO@CaveMUCK ---- --:):-- perfect little dream the kind that hurts the most -- |\| | |/| --:(:-- --- CaveMUCK is back! --- Telnet to cave.tcp.com (128.95.10.106) port 2283 --- -- Finger me for fun, excitement or for my PGP Public Key Encryption Block -- From Majordomo-Users-Owner Wed Oct 13 13:14:52 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03675; Wed, 13 Oct 93 13:14:52 GMT Received: from dirac.scri.fsu.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA03659; Wed, 13 Oct 93 06:14:39 PDT Received: by dirac.scri.fsu.edu id AA38422 (5.65c/IDA-1.4.4 for Majordomo-Users@greatcircle.com); Wed, 13 Oct 1993 09:18:00 -0400 Date: Wed, 13 Oct 1993 09:18:00 -0400 From: Kingsley Kerce Message-Id: <199310131318.AA38422@dirac.scri.fsu.edu> To: Kasuga Jingoro Cc: Majordomo-Users@GreatCircle.COM Subject: Re: multiple unsubscribes In-Reply-To: <199310131252.AA11776@bolero.rahul.net> References: <199310111500.AA96118@dirac.scri.fsu.edu> <199310131252.AA11776@bolero.rahul.net> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The following fix works for us. Thanks, Kasuga (or is it Jim?) Kingsley F. Kerce (kerce@scri.fsu.edu) Supercomputer Computations Research Institute Florida State University Tallahassee, FL, USA 32306 Kasuga Jingoro writes: > > "Brent Chapman" writes: > > "Stephen Bannasch" writes: > > > # Subject: multiple unsubscribes > > > # I am the owner of a list and wanted to remove a bunch a bad addresses > > > # so I tried the following commands: > > > # > > > # approve PASSWORD unsubscribe MYLIST USER1 > > > # approve PASSWORD unsubscribe MYLIST USER2 > > > # approve PASSWORD unsubscribe MYLIST USER3 > > > # > > > # Majordomo responded by only unsubcribing the first person on the > > > # list. > > > # The second and third were reported as not being members of MYLIST. > > > # When > > > # the unsubscribe requests for users 2 and 3 were placed in their own > > > # messages the unsubscribe operations were successful. > > > # > > > # Is this a bug? Is there a fix? > > This might be related to a related bug in Majordomo. This is a bug that > was reported on this list ages ago but has never been fixed in the > official release. In the do_unsubscribe subroutine, the file NEW is > opened to write out the new version of the subscriber list. But this > file is NEVER closed. The result is that the new version of the list > is held open AND unlocked for the duration of the process. This can cause > numerous problems, one of which may be the one you are experiencing. > The problem I saw was that if one would place a unsub command followed > by a sub command in the same message, the sub command would appear to > work, but a later inspection of the list would show that the address > was not added. My theory is that since the new version of the list is > held open during the subscribe command, that the changes made to the > file in the subscribe command will be superseded once the process ends > since perl will then automatically close the NEW file which will revert > the file back to the original contents after the unsub command. Although > this bug does not manifest itself on Brent's system, this bug is > legitimate and should be fixed in the official Majordomo release. > > The fix is trivial. Simply put a close(NEW); at a strategic place in > the do_unsubscribe routine. I put it right before the block of code > starting with the line 'if ($match_count == 1) {'. > > So, Brent, how about getting this bug fixed at last? > > ---- jingoro@tcp.com -- Jim Lick -- jingoro@rahul.net -- jIngOrO@CaveMUCK ---- > --:):-- perfect little dream the kind that hurts the most -- |\| | |/| --:(:-- > --- CaveMUCK is back! --- Telnet to cave.tcp.com (128.95.10.106) port 2283 --- > -- Finger me for fun, excitement or for my PGP Public Key Encryption Block -- From Majordomo-Users-Owner Thu Oct 14 03:59:19 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA06013; Thu, 14 Oct 93 03:59:19 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA06006; Wed, 13 Oct 93 20:59:11 PDT Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA22678; Wed, 13 Oct 93 20:47:13 PDT Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0onJEk-00031NC; Wed, 13 Oct 93 20:20 PDT Message-Id: From: Alan Millar Subject: Re: type-cast voodoo (?) To: rogerk@queernet.org Date: Wed, 13 Oct 1993 20:20:18 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "rogerk@queernet.org" at Oct 12, 93 05:35:13 pm Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1076 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst rogerk@queernet.org spake of these matters: > > The other quirk I found is that mixing addresses with angle brackets <> > > and without in an aliase file sometimes has problems. > It doesn't "sometimes have problems"; this is a specific and deliberate > mode of operation. > joe > bob > sue > Jimmy > is equivalent to > "To: joe bob sue Jimmy " Yes, this is exactly what SMail does. I used the ambiguous phrase "sometimes" because several people have attempted to "educate" me that SMail 3 does something else, and I wanted to avoid hashing out the whole thing again.... :-) And while it is a deliberate design choice, I simply find it annoying that (considering all the other features in Smail that do mimic sendmail) they didn't make this feature operate just like sendmail. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ Batteries not included. From Majordomo-Users-Owner Thu Oct 14 14:57:19 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA07269; Thu, 14 Oct 93 14:57:19 GMT Received: from dirac.scri.fsu.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA07262; Thu, 14 Oct 93 07:57:09 PDT Received: by dirac.scri.fsu.edu id AA39335 (5.65c/IDA-1.4.4 for Majordomo-Users@greatcircle.com); Thu, 14 Oct 1993 11:00:09 -0400 Date: Thu, 14 Oct 1993 11:00:09 -0400 From: Kingsley Kerce Message-Id: <199310141500.AA39335@dirac.scri.fsu.edu> To: Majordomo-Users@GreatCircle.COM Subject: majordomo.pl: problem with main'is_list_member Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In majordomo.pl, sub main'is_list_member (included at the end of this message), should the "&abort" be "&main'abort"? I'd received this mailer error: > From: Mail Delivery Subsystem > To: owner-majordomo@scri.fsu.edu > Cc: postmaster@scri.fsu.edu > Subject: Returned mail: unknown mailer error 2 > Date: Thu, 14 Oct 1993 09:36:07 -0400 > > ----- Transcript of session follows ----- > Undefined subroutine "Majordomo'abort" called at /usr/local/mail/majordomo/majordomo.pl line 378, <> line 3. > 554 "|/usr/local/mail/majordomo/wrapper majordomo"... unknown mailer error 2 Thanks, Kingsley F. Kerce (kerce@scri.fsu.edu) Supercomputer Computations Research Institute Florida State University Tallahassee, FL, USA 32306 sub main'is_list_member { local($subscriber) = shift; local($listdir) = shift; local($clean_list) = shift; local($matches); open(LIST, "$listdir/$clean_list") || &abort("Can't read $listdir/$clean_list: $!"); while () { if (&main'addr_match($_, $subscriber)) { $matches++; } } close(LIST); return($matches); } From Majordomo-Users-Owner Thu Oct 14 18:48:50 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA07956; Thu, 14 Oct 93 18:48:50 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA07949; Thu, 14 Oct 93 11:48:38 PDT Received: by interlock.ans.net id AA22702 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Thu, 14 Oct 1993 14:50:46 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 14 Oct 1993 14:50:46 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 14 Oct 1993 14:50:46 -0400 From: Dan Simoes Message-Id: <199310141850.AA109117@foo.ans.net> Subject: moderators To: majordomo-users@GreatCircle.COM Date: Thu, 14 Oct 1993 14:50:02 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1454 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've got majordomo up and running now. It works great, and not to be a whiner, but the docs are very sparse and seemingly inconsistent. I had no idea there was a 'resend' that can do moderation until Brent mailed me about it. Also, the way you set up aliases with resend is very different than the way you set up with just majordomo. Before I try adding moderators to my test list, I want to test the other options of resend. I can't get -I to work, no matter what. I've tried -I , -I -outgoing, and the example below: # entries for test list "tennis" #tennis: :include:/home/majordom/lists/tennis tennis: "| /home/majordom/wrapper resend -l tennis -f tennis-owner -h iss.ans.net -s tennis-outgoing -I /home/majordom/lists/tennis" tennis-outgoing: :include:/home/majordom/lists/tennis owner-tennis-outgoing: tennis-owner owner-tennis: tennis-owner tennis-owner: dans@ans.net tennis-request: "| /home/majordom/wrapper request-answer tennis" tennis-approval: dans@ans.net In this case, watching with mail -v: -I... User unknown /home/majordom/lists/tennis... Cannot mail directly to files Help? The resnd.README file says to use -I . Do I need colons for just 1 file? Thanks, | Dan | | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From Majordomo-Users-Owner Thu Oct 14 18:54:55 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA07972; Thu, 14 Oct 93 18:54:55 GMT Received: from alfred.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA07965; Thu, 14 Oct 93 11:54:47 PDT Received: from spiff.YP.nobel (spiff.ccs.carleton.ca) by alfred.ccs.carleton.ca (4.1/SMI-4.0) id AA07582; Thu, 14 Oct 93 14:58:13 EDT From: mcr@ccs.carleton.ca (Michael Richardson) Received: by spiff.YP.nobel (4.1/Sun-Client) id AA03536; Thu, 14 Oct 93 14:59:32 EDT Date: Thu, 14 Oct 93 14:59:32 EDT Message-Id: <9310141859.AA03536@spiff.YP.nobel> To: kerce@dirac.scri.fsu.edu Cc: Majordomo-Users@GreatCircle.COM In-Reply-To: Kingsley Kerce's message of Thu, 14 Oct 1993 11:00:09 -0400 <199310141500.AA39335@dirac.scri.fsu.edu> Subject: majordomo.pl: problem with main'is_list_member Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hmm. Mine, *is* &main'abort(). Maybe it has been fixed? From Majordomo-Users-Owner Thu Oct 14 19:28:35 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA08041; Thu, 14 Oct 93 19:28:35 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA08034; Thu, 14 Oct 93 12:28:22 PDT Received: by interlock.ans.net id AA13112 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Thu, 14 Oct 1993 15:30:28 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 14 Oct 1993 15:30:28 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 14 Oct 1993 15:30:28 -0400 From: Dan Simoes Message-Id: <199310141929.AA112924@foo.ans.net> Subject: more moderator stuff To: majordomo-users@GreatCircle.COM Date: Thu, 14 Oct 1993 15:29:43 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 954 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I think I know what the earlier problem was: The resend line has to end with tennis-outgoing, and I was ending it with the -I statement. Now, I'm using the following to test moderation. I didn't realize that if you use -a/-A, the -I is redundant. This cause endless bounces by trying to resend itself to tennis every time instead of to the approval: tennis: "| /home/majordom/wrapper resend -l tennis -h iss.ans.net -f tennis -a itsokbyme -A tennis-outgoing" tennis-outgoing: :include:/home/majordom/lists/tennis owner-tennis-outgoing: tennis-owner owner-tennis: tennis-owner tennis-owner: dans@ans.net tennis-request: "| /home/majordom/wrapper request-answer tennis" tennis-approval: dans@ans.net This might be painfully obvious, but I can't seem to get this going. Thanks, | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From Majordomo-Users-Owner Fri Oct 15 16:21:26 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA10684; Fri, 15 Oct 93 16:21:26 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA10677; Fri, 15 Oct 93 09:21:04 PDT Received: by interlock.ans.net id AA10983 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Fri, 15 Oct 1993 12:23:07 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Fri, 15 Oct 1993 12:23:07 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Fri, 15 Oct 1993 12:23:07 -0400 From: Dan Simoes Message-Id: <199310151622.AA38474@foo.ans.net> Subject: more moderating woes To: majordomo-users@GreatCircle.COM Date: Fri, 15 Oct 1993 12:22:22 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2172 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk OK folks, I've got aliases running correctly and I no longer gets hundreds of looped messages. I *will* write a doc on how to use moderators with majordomo when I'm done, so your attention is not in vain. I've included below my aliases file. So far, any messages sent to tennis get sent to tennis-approval for approval. I created a .majordomo file for that user that looks like: tennis itsokby majordomo@iss.ans.net I use elm as my mailer, so I tried forwarding the message to tennis, adding the line: Approved: itsokbyme It goes through, but all the lines get prefaced with '>', the subject is blank, and some header lines go through. After reading resend.README for the umpteenth time, I had the brilliant idea of just piping the message to approve. This does nothing. Then, I saved the message to a file called /tmp/foo. If I run approve /tmp/foo, 2 files get created in /tmp, resend.$$$$.in and .out, where $$$$ is a number (4536,4638,etc) each time I run this. Now what? Oh, those files are owned by daemon, so I suppose sendmail is supposed to resend them, but how? Thanks for any light you can shed on the matter. | Dan | *** aliases file follows (partial): # aliases for majordomo majordomo: "| /home/majordom/wrapper majordomo" majordomo-owner: dans@ans.net owner-majordomo: dans@ans.net # entries for test list "tennis" # this was the original entry for a straight list, no moderators #tennis: :include:/home/majordom/lists/tennis # the following add (?) moderator capability using resend tennis: "| /home/majordom/wrapper resend -l tennis -h iss.ans.net -f tennis-approval -r tennis -I tennis -a /home/majordom/lists/tennis.passwd -A -R tennis-outgoing" tennis-outgoing: :include:/home/majordom/lists/tennis owner-tennis-outgoing: tennis-owner owner-tennis: tennis-owner tennis-owner: dans@ans.net tennis-request: "| /home/majordom/wrapper request-answer tennis" # changed tennis-approval to a a different system so that # I could test moderating tennis-approval: dans@iss.ans.net # end /etc/aliases -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From Majordomo-Users-Owner Sun Oct 17 08:21:20 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA15504; Sun, 17 Oct 93 08:21:20 GMT Received: from relay2.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA15163; Sat, 16 Oct 93 23:06:54 PDT Received: from spool.uu.net (via LOCALHOST) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA23101; Sun, 17 Oct 93 02:10:03 -0400 Received: from rde.UUCP by uucp3.uu.net with UUCP/RMAIL (queueing-rmail) id 020852.16117; Sun, 17 Oct 1993 02:08:52 EDT Received: by cyan.vistachrome.COM (4.1/SMI-4.1) id AA17767; Sun, 17 Oct 93 01:34:49 EDT From: andy@vistachrome.com (Andrew Finkenstadt) Message-Id: <9310170534.AA17767@cyan.vistachrome.COM> Subject: Anonymous / Secret mailing lists To: majordomo-users@GreatCircle.COM Date: Sun, 17 Oct 1993 01:34:48 -0400 (EDT) X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 1214 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have finally installed majordomo as available at ftp.greatcircle.com last Thursday, and have applied one patch for the multiple unsubscribe bug referenced here earlier. I now have two questions: Has anyone developed the code to implement anonymous lists where no one can find out the subscriber list without the password? I implemented a very simple modification to the main'do_who to check for the presence of "listname.nowho" to disable the WHO command period. This is along the lines of "program by example" since I don't yet know PERL well enough to write original code. Has anyone developed the code to implement secret lists where one must know the list name in order to subscribe, without being able to use the 'lists' command to find the list? This is a bit more complicated, although perhaps simple by checking for the presence of listname.secret before outputting it in the main'do_lists procedure. Thanks in advance. Andy -- Andrew Finkenstadt | Systems Analyst, Homes & Land Publishing Corporation +1 904-575-0189 | GEnie Sysop andy@genie.geis.com | THE RELATIONAL OATH: "I promise to use the key, the andy@homes.com | whole key, and nothing but the key, so help me Codd." From Majordomo-Users-Owner Sun Oct 17 23:17:39 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA17275; Sun, 17 Oct 93 23:17:39 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA17266; Sun, 17 Oct 93 16:17:32 PDT Message-Id: <9310172317.AA17266@mycroft.GreatCircle.COM> To: majordomo-users@GreatCircle.COM Subject: Another online manual page from Jim Duncan: approve Date: Sun, 17 Oct 1993 16:17:31 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here's another new online manual page from Jim Duncan , this time for "approve". This manual page will be included with the next release. Note that there is a bug in the current released version of approve: it won't work on standard input. You have to save the message to be approved in a file, then run "approve" with that filename as an argument. This will be fixed in the next release. Thanks, Jim! -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 '\" t .TH APPROVE 1 .SH NAME approve \- approve a Majordomo request .SH SYNOPSIS .B approve [filename] .SH "DESCRIPTION" .B approve automates the task of replying to an approval request from Majordomo. Input is the e-mail message containing Majordomo's request, read from .IR filename , or read from standard input if no filename is specified. .PP .B approve currently understands two types of requests; those requesting subscription to a .I closed list, and those which bounced due to a lack of permission to post to a moderated, or .IR private , mailing list. .B approve reads the body of the message from Majordomo to determine the appropriate action. Assuming a message containing a subscription request like the following: .sp 1 .RS 3 From: Majordomo@This.COM .sp 0 To: this-list-approval@This.COM .sp 1 Joe User requests you approve the following: .sp 1 .RS 3 subscribe this-list Joe User .RE .sp 1 If you approve, send a line such as the following to Majordomo@This.COM: .sp 1 .RS 3 approve PASSWD subscribe this-list Joe User .RE .RE .sp 1 then running .B approve on the message by saving it in a file, e.g., .sp 1 .RS 3 approve /tmp/request .RE .sp 1 or .sp 1 .RS 3 approve < /tmp/request .RE .sp 1 will result in the following reply to Majordomo: .sp 1 .RS 3 To: Majordomo@This.COM .sp 1 approve PASSWD subscribe this-list User@Fubar.COM (Joe User) .sp 1 .RE If .B approve is on the user's path, then it's possible to execute it via a shell escape, piping the current message to .B approve from a mail program, e.g., .sp .RS 3 !approve .RE .sp would .I approve the current message in /usr/ucb/Mail. .PP If, in the latter case, the "Subject:" line of the request from Majordomo is "BOUNCE : ", the message is treated as a posting rejected by .B resend for some reason, and is reformatted with appropriate "Approved:" headers to cause it to succeed, and then it is resubmitted to Majordomo for posting. This provides an easy mechanism for the moderator of a mailing list to approve postings to the list. .SH CONFIGURATION .B approve assumes that the .I approve password for each list is the same as the .I approval password used by .BR resend , and that this password is stored in a file called .I .majordomo in the user's home directory. The file has the following format: .RS 5 .TS l l l . .sp this-list passwd1 Majordomo@This.COM other-list passwd2 Majordomo@Other.GOV .sp .TE .RE The first column specifies the name of the mailing list, the second column specifies the list-owner's password for the given list, and the third column specifies the e-mail address of the associated Majordomo server. It is assumed that the value in the third column is an Internet-style "something@somewhere" address, and that postings for "List" should be sent to "List@somewhere". Since this file .B only needs to be read by the user, it should be mode 600 to protect the passwords. .SH FILES ~/.majordomo .sp 0 /usr/local/lib/mail/majordomo/ .SH SEE ALSO majordomo(8),perl(1),resend(1). .SH BUGS There is no direct support for MH(1), so MH users will have to run .B approve directly on the message file in their inbox. .sp The .I .majordomo file requires an at-sign, "@", in the address of the Majordomo server, even if it colocated on the same system as the list-owner. .SH AUTHORS Majordomo and most of the ancillary perl code was written by Brent Chapman, . This man page was written by Jim Duncan, . From Majordomo-Users-Owner Mon Oct 18 03:08:58 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA18336; Mon, 18 Oct 93 03:08:58 GMT Received: from jasper.berkeley.edu (infocal.Berkeley.EDU) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA18329; Sun, 17 Oct 93 20:08:51 PDT Received: from localhost by jasper.berkeley.edu (5.64/1.33(web)) id AA09070; Sun, 17 Oct 93 20:12:35 -0700 To: majordomo-users@GreatCircle.COM Subject: Re: a directory for each mailing list In-Reply-To: Message of Tue, 14 Sep 1993 10:37:24 -0400. <199309141437.AA24853@Warren.MENTORG.COM> Date: Sun, 17 Oct 1993 20:12:35 PDT Message-Id: <9069.750913955@jasper.berkeley.edu> From: ( We are everywhere ) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Tom Limoncelli suggested a schema like the following, whereby we implement each mailing list as a directory containing the pertinent files. -------- $listdir/$listname/members --the membership $listdir/$listname/info --the long description $listdir/$listname/description --the short description $listdir/$listname/no-advertise --if it exists, don't advertise in "info" $listdir/$listname/secret-membership --don't let anyone see membership $listdir/$listname/auto-accept --auto approve $listdir/$listname/closed-membership --always require approval. $listdir/$listname/pre-edit-perl --code to eval before adding members $listdir/$listname/post-edit-perl --code to eval after adding members -------- We currently have installed a half-baked command (currently called maillist) by which users can create public mailing lists (without danger of colliding with login names or system aliases), and delete (only) their own creations. Its invocation creates, in a directory in which the user normally cannot write, a file owned by the user, and arranges for the corresponding :include: and owner- aliases to appear in the system aliases files. I am loathe to add an unbounded number of flags to this command, one each to create and rm each of the (growing) number of majordomo-feature .-files. However, if we changed `maillist` to creat a directory owned by the user, the user could use any ordinary commands to populate it with whatever files were useful for whatever mail distribution agent the user happened to be fond of. I have refrained from grabbing our corrent installation of majordomo and running with it off in this direction, because we would forfeit future developments (or make difficult their importation). If you think this idea has sufficient merit to incorporate into the base majordomo distribution, I could attempt the changes and feed them back for inclusion into the base sources. -------- Actually, as soon as you give up the idea that it must be perfect, it's pretty easy. -- Michael H. Morse From Majordomo-Users-Owner Mon Oct 18 06:24:35 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA19243; Mon, 18 Oct 93 06:24:35 GMT Received: from relay1.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA19236; Sun, 17 Oct 93 23:24:25 PDT Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA05759; Mon, 18 Oct 93 02:28:03 -0400 Received: from rde.UUCP by uucp4.uu.net with UUCP/RMAIL (queueing-rmail) id 022656.16824; Mon, 18 Oct 1993 02:26:56 EDT Received: from homebase.vistachrome.com by cyan.vistachrome.com (4.1/SMI-4.1) id AA11292; Mon, 18 Oct 93 02:09:19 EDT Received: by homebase.vistachrome.com (5.65/1.35) id AA09572; Mon, 18 Oct 93 02:11:23 -0400 From: andy@homebase.vistachrome.com (Andy Finkenstadt) Message-Id: <9310180611.AA09572@homebase.vistachrome.com> Subject: Re: a directory for each mailing list To: rhc@infocal.berkeley.edu, majordomo-users@GreatCircle.COM Date: Mon, 18 Oct 1993 02:11:23 -0400 (EDT) In-Reply-To: <9069.750913955@jasper.berkeley.edu> from "rhc@infocal.berkeley.edu" at Oct 17, 93 08:12:35 pm X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 1769 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk rhc@infocal.berkeley.edu said in a letter: > > Tom Limoncelli suggested a schema > like the following, whereby we implement each mailing list as a > directory containing the pertinent files. > > -------- > $listdir/$listname/members --the membership > $listdir/$listname/info --the long description > $listdir/$listname/description --the short description > $listdir/$listname/no-advertise --if it exists, don't advertise in "info" > $listdir/$listname/secret-membership --don't let anyone see membership > $listdir/$listname/auto-accept --auto approve > $listdir/$listname/closed-membership --always require approval. > $listdir/$listname/pre-edit-perl --code to eval before adding members > $listdir/$listname/post-edit-perl --code to eval after adding members > -------- I did a lot of thinking today (and dreaming this morning) about Majordomo and its inherent flexibility. It's written in PERL, whose manual I read most of today. You can, in effect, "source" (eval?) a file which contains configuration data instead of depending on the existence (or not) of a file to control said configuration. I don't know if two-dimensional associative arrays are possible in PERL, but this construct may work: lists[$listname][$feature] where returning NULL from this indicates either a lack of list, or a lack of feature setting. This permits expandability without sacrificing future compatibility at the price of a one-time change from file-access to a listname.cf (configuration) file controlling features. How does that sound? Is it sound? Andy > I am loathe to add an unbounded number of flags to this command, one > each to create and rm each of the (growing) number of majordomo-feature > .-files. > From Majordomo-Users-Owner Mon Oct 18 06:33:58 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA19273; Mon, 18 Oct 93 06:33:58 GMT Received: from aqueous (aqueous.ml.csiro.au) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA19266; Sun, 17 Oct 93 23:33:29 PDT Received: from ocean by aqueous with SMTP id AA07864 (5.65c/IDA-1.4.4 for ); Mon, 18 Oct 1993 17:37:01 +1100 From: Bill Hart Received: by ocean (4.1/Spike-2.2) id AA04576; Mon, 18 Oct 93 17:36:58 EST Date: Mon, 18 Oct 93 17:36:58 EST Message-Id: <9310180636.AA04576@ocean> To: Majordomo-Users@GreatCircle.COM Subject: Digest Software Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I've been happily using Majordomo for the past 12 months now, without hardly a problem (thats the kind of software I like to administer!!). Thinking that it was time to upgrade I got the latest version (with some trepadation, I expected it to be overcome with creeping featurism) and had it up and running again in half an hour. The one new feature I was looking for, the ability to digest mail and mail it out to a list once a day or week I couldn't find. Does anybody have a digesting feature, or did I miss something in the docs ? Cheers ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bill Hart Internet : hart@ml.csiro.au Network Manager Phone : +61 02 325 442 CSIRO Division of Oceanography Fax : +61 02 325 000 Hobart, Tas., 7000 Australia Paging: +61 08 001 234 (quote #29474) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From Majordomo-Users-Owner Mon Oct 18 07:18:42 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA19401; Mon, 18 Oct 93 07:18:42 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA19391; Mon, 18 Oct 93 00:18:28 PDT Message-Id: <9310180718.AA19391@mycroft.GreatCircle.COM> To: Bill Hart Cc: Majordomo-Users@GreatCircle.COM Subject: Re: Digest Software In-Reply-To: Your message of Mon, 18 Oct 93 17:36:58 EST Date: Mon, 18 Oct 1993 00:18:26 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Bill Hart writes: # Hi, # # I've been happily using Majordomo for the past 12 months now, # without hardly a problem (thats the kind of software I like to # administer!!). Thinking that it was time to upgrade I got the latest # version (with some trepadation, I expected it to be overcome with # creeping featurism) and had it up and running again in half an hour. # # The one new feature I was looking for, the ability to digest mail # and mail it out to a list once a day or week I couldn't find. # # Does anybody have a digesting feature, or did I miss something in the # docs ? It's packaged separately from Majordomo. Get file pub/list-managers/tools/digest.shar from FTP.GreatCircle.COM. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Mon Oct 18 14:33:48 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA20572; Mon, 18 Oct 93 14:33:48 GMT Received: from relay1.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA20565; Mon, 18 Oct 93 07:33:40 PDT Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA06264; Mon, 18 Oct 93 10:37:19 -0400 Received: from rayssd.UUCP by uucp6.uu.net with UUCP/RMAIL (queueing-rmail) id 103517.14350; Mon, 18 Oct 1993 10:35:17 EDT Received: from fluke.ssd.ray.com by rayssd.ssd.ray.com with SMTP id AA05783 (5.65c/IDA-1.5 for ); Mon, 18 Oct 1993 10:06:57 -0400 Received: by fluke.ssd.ray.com id AA16492 (5.65c/IDA-1.5 for majordomo-users@GreatCircle.COM); Mon, 18 Oct 1993 10:06:56 -0400 Message-Id: <199310181406.AA16492@fluke.ssd.ray.com> From: dhb@ssd.ray.com (David H. Brierley) Date: Mon, 18 Oct 1993 10:06:56 -0400 X-Mailer: Mail User's Shell (7.2.2 4/12/91) To: majordomo-users@GreatCircle.COM Subject: Re: a directory for each mailing list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Oct 17, 20:12, ( We are everywhere ) wrote: > Subject: Re: a directory for each mailing list > Tom Limoncelli suggested a schema > like the following, whereby we implement each mailing list as a > directory containing the pertinent files. ... > However, if we changed `maillist` to creat a directory owned by the > user, the user could use any ordinary commands to populate it with > whatever files were useful for whatever mail distribution agent the > user happened to be fond of. I like the idea of creating a separate directory for each mailing list because it cleans up the name space in the "lists" directory. I've got 30 or 40 internal mailing lists being managed by majordomo and if you just do an "ls" in the directory it has become difficult to read. However, I am leary of letting a general user create and modify any of the files without going through majordomo to do it. It is too easy for the user to break something. What I have been contemplating doing is to modify majordomo so that it has commands to create or remove any of the files that it uses, probably through extensions to the approve command. This way the list owner can make the list open, closed, secret, private, whatever, simply by sending the appropriate command to the majordomo server. I also have an additional problem with the user being able to directly manipulate the files in the list directory. All of my list are being handled by a central mail server and general users are not allowed to directly log in on that machine so there is no way for them to do this in my environment. -- David H. Brierley; Raytheon Submarine Signal Division Work: dhb@ssd.ray.com Home: dave@galaxia.network23.com From Majordomo-Users-Owner Mon Oct 18 17:06:06 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21085; Mon, 18 Oct 93 17:06:06 GMT Received: from bernina.ethz.ch by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21077; Mon, 18 Oct 93 10:05:54 PDT Received: from kontiki by bernina.ethz.ch with SMTP inbound id <21201-0@bernina.ethz.ch>; Mon, 18 Oct 1993 18:09:19 +0100 Received: by zellbio.ethz.ch (920330.SGI/) for Majordomo-Users@GreatCircle.COM id AA29373; Mon, 18 Oct 93 18:08:31 +0200 From: messerli@zellbio.ethz.ch (Marius Messerli) Message-Id: <9310181608.AA29373@zellbio.ethz.ch> Subject: No Response form System? To: Majordomo-Users@GreatCircle.COM (Majordomo Mailing List) Date: Mon, 18 Oct 93 18:08:30 MES X-Mailer: ELM [version 2.3 PL11] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, I installed majordomo (source ftp.greatcircle.com) on a Silicon Graphics PI (SysV), and used the POSIX set of defines. (I followed the instructions in README closely) The problem is that I cannot subscribe (or do any other action). I don't get an error message. ---> If I change the uid of wrapper from 'root' to 'daemon' the system works (I do get added to the list) but instead of the confirmation I get the following ----- Transcript of session follows ----- /usr1/people/majordomo/wrapper: error: recompile with POSIX flags. 554 "|/usr1/people/majordomo/wrapper majordomo"... unknown mailer error 4 ---> If I call majordomo manually (as root) and supply the mail message on the stdin, then everything works fine. I get added to the list and get a confirmation. Why is the wrapper not called properly? (-rwsr-sr-x 1 root majordomo 49600 Oct 18 17:49 wrapper*) Thanks for any help, Marius. ------------------------DETAILS ----------------------------------- Makefile: -------- I changed the W_GID to 103 (majordomo). W_UID = 1 W_GID = 103 W_CHOWN=root W_CHMOD=4755 I changed the following line to get rid of the error: -DMAJORDOMO_CF=\MAJORDOMO_CF=${W_MAJORDOMO_CF}\" \ with -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" \ ------------------------^ (cpp: error wrapper.c:43: MAJORDOMO_CF: macro recursion) Then I compiled. -rwsr-sr-x 1 root majordomo 49600 Oct 18 17:49 wrapper* Aliases: ------- majordomo: "|/usr1/people/majordomo/wrapper majordomo" owner-majordomo: postmaster majordomo-owner: postmaster ls-test-priv: :include:/usr1/people/majordomo/lists/ls-test-priv owner-ls-test-priv: messerli ls-test-priv-request: "|/usr1/people/majordomo/wrapper request-answer ls-test-priv" ls-test-priv-approval: messerli -------------------------------------------------- J.M. Messerli, PhD, messerli@zellbio.ethz.ch HPM F, 8093 Zurich, Switzerland Tel: +41.1.633.3355, FAX: ++41 1 371 28 94 From Majordomo-Users-Owner Mon Oct 18 17:13:27 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21136; Mon, 18 Oct 93 17:13:27 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21129; Mon, 18 Oct 93 10:13:07 PDT Received: from cs.umb.edu by cs.umb.edu with SMTP id AA27776 (5.65c/IDA-1.4.4 for ); Mon, 18 Oct 1993 13:16:41 -0400 Message-Id: <199310181716.AA27776@cs.umb.edu> To: majordomo-users@GreatCircle.COM Subject: Re: a directory for each mailing list Date: Mon, 18 Oct 1993 13:16:39 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9069.750913955@jasper.berkeley.edu>, We are everywhere writes: > Tom Limoncelli suggested a schema > like the following, whereby we implement each mailing list as a > directory containing the pertinent files. > [example deleted] > We currently have installed a half-baked command (currently called > maillist) by which users can create public mailing lists (without > danger of colliding with login names or system aliases), and delete > (only) their own creations. Its invocation creates, in a directory in > which the user normally cannot write, a file owned by the user, and > arranges for the corresponding :include: and owner- aliases to appear > in the system aliases files. Nice, but how does somebody wwithout access to your system run this command? > I am loathe to add an unbounded number of flags to this command, one > each to create and rm each of the (growing) number of majordomo-feature > .-files. But that's what you have to do to allow remote email administration of the mailings list. The ability to remotely administer the list is THE most important and useful feature in majordomo. That is why Alan and I (and Brent too) have pretty much decided that the file per feature paradigm doesn't really scale well. Hence the configuration file battle that Alan and I have been going on about for the past couple of months. > However, if we changed `maillist` to creat a directory owned by the > user, the user could use any ordinary commands to populate it with > whatever files were useful for whatever mail distribution agent the > user happened to be fond of. True, this does have some added flexibility, but it is useless if the list maintainer is unable to log into the mailing list server. Andy Finkenstadt (andy@homebase.vistachrome.com) in message <9310180611.AA09572@homebase.vistachrome.com> said: > I did a lot of thinking today (and dreaming this morning) about Majordomo > and its inherent flexibility. It's written in PERL, whose manual I read > most of today. You can, in effect, "source" (eval?) a file which > contains configuration data instead of depending on the existence (or not) > of a file to control said configuration. I don't know if two-dimensional > associative arrays are possible in PERL, but this construct may work: > > lists[$listname][$feature] Actually you have a double dimensional regular (not associative) array, but multi-dimensional arrays don't work in perl. They are faked by pasting multiple indices together with some character ($; is the usually one I think). Anyway, no need to do multi-dimensioning, just create a single configuration file per list. > where returning NULL from this indicates either a lack of list, or a > lack of feature setting. This permits expandability without sacrificing > future compatibility at the price of a one-time change from file-access > to a listname.cf (configuration) file controlling features. True, but with the hooks that Alan and I have put into majordomo, some error checking etc is needed. Also, allowing pure perl code is a disaster from a security point of view. My config file parser goes to great lengths to make sure that strings with wildcards that may be passed to the shell aren't expanded, conflicting options don't (actually at Alan's suggestion I side stepped the issue with a new enumerated keyword). I test the regular expressions that determine what users get to see the list in the lists command to make sure that they don't expand weirdly, and that they only contain valid address specs etc. Basically I try to detaint all of the data that I receive from the config file before allowing it to be used by majordomo proper. > How does that sound? Is it sound? Right idea, but having it be perl code is definitely the wrong implementation from a security viewpoint. -- John From Majordomo-Users-Owner Mon Oct 18 17:29:12 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21197; Mon, 18 Oct 93 17:29:12 GMT Received: from noc4.dccs.upenn.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21179; Mon, 18 Oct 93 10:29:01 PDT Received: from CCAT.SAS.UPENN.EDU by noc4.dccs.upenn.edu id AA04728; Mon, 18 Oct 93 13:32:40 -0400 Received: by ccat.sas.upenn.edu (AIX 3.2/UCB 5.64/4.03) id AA28498; Mon, 18 Oct 1993 13:33:33 -0400 From: michael@ccat.sas.upenn.edu (Michael Nenashev) Message-Id: <9310181733.AA28498@ccat.sas.upenn.edu> Subject: Make List script To: Majordomo-Users@GreatCircle.COM Date: Mon, 18 Oct 1993 13:33:33 -0400 (EDT) X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1993 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I sure missed at list a year worth of discussion, but I'm surprised there is no "make.list" script in the distribution, that would take a list name and owner as arguments and make all the entries in ../lists, ../archive, and /etc/aliases. Being probably the laziest list owner ever, I spent some five minutes to scribble the next primitive script, which I'm sure might be greatly improved by anyone willing to spend a few minutes more on it. (And I'd appreciate seeing the improved version, if you did not guessed it already ;-) ) Mike. ---------------- chop here -------------- #!/bin/sh # @(#) Usage: make.list list_name owner # The make.list sits in majordomo root dir # touch lists/$1 touch lists/$1".info" touch lists/$1".passwd" # I have "alist" user and "alist" group to manage the majordomo chown alist lists/* chgrp alist lists/* # chmod 664 lists/* # # $1 - list name # touch archive/$1 # # Somehow my archive won't grow if it's more restricted than 666 # chmod 666 archive/$1 chown alist archive/$1 chgrp alist archive/$1 # # $2 - owner name # This all should be done with single >>/etc/aliases, of course. I know. # echo "# $1 mailing list" >> /etc/aliases echo "#" >> /etc/aliases # # Change /program/usr/local/majordomo to where your scripts are # echo "$1: \"|/program/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l $1 -f $2 -h mec.sas.upenn.edu -s $1-outgoing\"" >> /etc/aliases echo "owner-$1: $2" >> /etc/aliases echo "$1-outgoing: :include:/program/usr/local/majordomo/lists/$1, $1-archive" >> /etc/aliases echo "owner-$1-outgoing: $2" >> /etc/aliases echo "$1-archive: /program/usr/local/majordomo/archive/$1" >> /etc/aliases echo "owner-$1-archive: $2" >> /etc/aliases echo "$1-request:" >> /etc/aliases echo " \"|/program/usr/local/majordomo/wrapper request-answer $1\" " >> /etc/aliases echo "owner-$1-request: $2" >> /etc/aliases echo "$1-approval: $2" >> /etc/aliases echo "$1-owner: $2" >> /etc/aliases echo "owner-$1-owner: $2" >> /etc/aliases From Majordomo-Users-Owner Mon Oct 18 17:32:13 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21223; Mon, 18 Oct 93 17:32:13 GMT Received: from alfred.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA21216; Mon, 18 Oct 93 10:32:05 PDT Received: from spiff.YP.nobel (spiff.ccs.carleton.ca) by alfred.ccs.carleton.ca (4.1/SMI-4.0) id AA04016; Mon, 18 Oct 93 13:35:30 EDT From: mcr@ccs.carleton.ca (Michael Richardson) Received: by spiff.YP.nobel (4.1/Sun-Client) id AA07340; Mon, 18 Oct 93 13:36:04 EDT Date: Mon, 18 Oct 93 13:36:04 EDT Message-Id: <9310181736.AA07340@spiff.YP.nobel> To: rhc@infocal.berkeley.edu Cc: majordomo-users@GreatCircle.COM In-Reply-To: ( We are everywhere )'s message of Sun, 17 Oct 1993 20:12:35 PDT <9069.750913955@jasper.berkeley.edu> Subject: a directory for each mailing list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >>>>> "rhc" == We are everywhere writes: rhc> Tom Limoncelli suggested rhc> a schema like the following, whereby we implement each rhc> mailing list as a directory containing the pertinent files. rhc> -------- $listdir/$listname/members --the I did this as well, except that s/members/list/; rhc> If you think this idea has sufficient merit to incorporate rhc> into the base majordomo distribution, I could attempt the rhc> changes and feed them back for inclusion into the base rhc> sources. Yes, *I* think so. -- :!mcr!: HOME: mcr@sandelman.ocunix.on.ca +1 613 788 2600 3853 Michael Richardson WORK: mcr@ccs.carleton.ca (Conservation Ecology) Here is an HTML reference to my bio. foreach $X ("E-Journal","NetBSD","Perl","Physics") { print "MCR hacks $X\n"; }; From Majordomo-Users-Owner Mon Oct 18 23:53:40 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA22446; Mon, 18 Oct 93 23:53:40 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA22438; Mon, 18 Oct 93 16:53:21 PDT Message-Id: <9310182353.AA22438@mycroft.GreatCircle.COM> To: messerli@zellbio.ethz.ch (Marius Messerli) Cc: Majordomo-Users@GreatCircle.COM (Majordomo Mailing List) Subject: Re: No Response form System? In-Reply-To: Your message of Mon, 18 Oct 93 18:08:30 MES Date: Mon, 18 Oct 1993 16:53:20 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk messerli@zellbio.ethz.ch (Marius Messerli) writes: # # Hello, # # I installed majordomo (source ftp.greatcircle.com) on a Silicon # Graphics PI (SysV), and used the POSIX set of defines. # # (I followed the instructions in README closely) # # The problem is that I cannot subscribe (or do any other action). # I don't get an error message. Your setup looks correct, as far as I can tell. Some further things to check: Is Majordomo getting invoked? Is it logging anything? Is Sendmail logging anything interesting about the delivery of these particular messages? -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Tue Oct 19 13:22:16 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA24352; Tue, 19 Oct 93 13:22:16 GMT Received: from bernina.ethz.ch by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA24340; Tue, 19 Oct 93 06:22:06 PDT Received: from kontiki by bernina.ethz.ch with SMTP inbound id <15308-0@bernina.ethz.ch>; Tue, 19 Oct 1993 14:25:46 +0100 Received: by zellbio.ethz.ch (920330.SGI/) for Majordomo-Users@GreatCircle.COM id AA01458; Tue, 19 Oct 93 14:24:57 +0200 From: messerli@zellbio.ethz.ch (Marius Messerli) Message-Id: <9310191224.AA01458@zellbio.ethz.ch> Subject: Wrapper Problem? (additional info) To: Majordomo-Users@GreatCircle.COM (Majordomo Mailing List) Date: Tue, 19 Oct 93 14:24:56 MES X-Mailer: ELM [version 2.3 PL11] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, trying to solve the wrapper problem I performed the following tests: - run majordomo (as user majordomo, group majordomo) majordomo < /tmp/xx where /tmp/xx is: ---------------- From: imaris (Imaris Top Level) Message-Id: <9310191149.AA01074@zellbio.ethz.ch> Subject: test To: majordomo@zellbio.ethz.ch Date: Tue, 19 Oct 93 13:49:57 MES X-Mailer: ELM [version 2.3 PL11] Status: RO subscribe ls-test-priv ----> works fine - run majordomo (as user majordomo, group majordomo) via wrapper wrapper majordomo < /tmp/xx (-rwsr-sr-x 1 root majordomo 49892 Oct 19 14:07 wrapper) wrapper majordomo < /tmp/xx new env: HOME=/usr1/people/majordomo PATH=/bin:/usr/bin:/usr/sbin:/usr/local/bin SHELL=/bin/csh MAJORDOMO_CF=/usr1/people/majordomo/majordomo.cf LOGNAME=majordomo imaris... Recipient names must be specified shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. (don't worry about the new_env which is printed at the beginning, I added this statement to see what's happening) ---> apparently there is a permission problem Actually the wrapper makes things worse (in terms of permissions) not better. Where is the problem? Regards, Marius. From Majordomo-Users-Owner Tue Oct 19 13:48:11 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA24425; Tue, 19 Oct 93 13:48:11 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-930913) id AA24418; Tue, 19 Oct 93 06:47:54 PDT Received: by interlock.ans.net id AA16653 (InterLock SMTP Gateway 1.1 for Majordomo-Users@greatcircle.com); Tue, 19 Oct 1993 09:49:45 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Tue, 19 Oct 1993 09:49:45 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Tue, 19 Oct 1993 09:49:45 -0400 From: Dan Simoes Message-Id: <199310191348.AA96590@foo.ans.net> Subject: Re: Wrapper Problem? (additional info) To: messerli@zellbio.ethz.ch (Marius Messerli) Date: Tue, 19 Oct 1993 09:48:58 -0400 (EDT) Cc: Majordomo-Users@GreatCircle.COM In-Reply-To: <9310191224.AA01458@zellbio.ethz.ch> from "Marius Messerli" at Oct 19, 93 02:24:56 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 791 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. > shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. > shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. > shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. > shlock: open(">shlock1431"): Permission denied at shlock.pl line 131, <> line 2. I've seen this frequently where the permissions on the files are incorrect. Typical settings for files are 644 and 755 for dirs. But majordomo wants 664 and 775 respectively. Check your permissions and try again. | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From Majordomo-Users-Owner Tue Oct 19 20:11:14 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA25840; Tue, 19 Oct 93 20:11:14 GMT Received: from relay1.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA25827; Tue, 19 Oct 93 13:11:03 PDT Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA08538; Tue, 19 Oct 93 16:14:14 -0400 Received: from rde.UUCP by uucp6.uu.net with UUCP/RMAIL (queueing-rmail) id 161215.15536; Tue, 19 Oct 1993 16:12:15 EDT Received: from homebase.vistachrome.com by cyan.vistachrome.com (4.1/SMI-4.1) id AA05001; Tue, 19 Oct 93 15:58:41 EDT Received: by homebase.vistachrome.com (5.65/1.35) id AA25193; Tue, 19 Oct 93 16:00:47 -0400 From: andy@homebase.vistachrome.com (Andy Finkenstadt) Message-Id: <9310192000.AA25193@homebase.vistachrome.com> Subject: Coping with "MAJORDOMO ABORT" ? To: majordomo-users@greatcircle.com Date: Tue, 19 Oct 1993 16:00:47 -0400 (EDT) X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 1602 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Well, I managed to stress out majordomo. :-) I am taking over the rec.arts.erotica mailing list reflector, and have had subscription requests out the wazoo. Apparently when someone asks to be subscribed to the list and someone else asks for a list of lists, they collide and the lists command aborts out. Please note the times in the capture below: Oct 19 12:31:18 cyan majordomo[2761] {person1} subscribe erotica person1 Oct 19 12:31:23 cyan majordomo[2821] {person2} lists Oct 19 12:31:28 cyan majordomo[2808] {person3} subscribe erotica person3 Oct 19 12:31:29 cyan majordomo[2821] {person2} (split to next line) ABORT Can't open list /usr/local/lib/majordomo/lists/shlock2781 Oct 19 12:31:31 cyan majordomo[2808] {person3} help Notice that person3's job is still being processed apparently with a "subscribe" "help" set of lines. I can think of three things that can help this situation: 1. change shlock.pl to use the parent directory or /tmp for its lock file 2. change lists to lock the directory while it does its stuff 3. change lists to skip any files beginning 'shlock' Could this be a real bug, or do I have my system configured incorrectly, or should I already have done 1 or 2 by virtue of applying previously mentioned patches? (I am using the release of majordomo available a week ago.) Andy -- Andrew Finkenstadt | Systems Analyst, Homes & Land Publishing Corporation +1 904-575-0189 | GEnie Sysop andy@genie.geis.com | THE RELATIONAL OATH: "I promise to use the key, the andy@homes.com | whole key, and nothing but the key, so help me Codd." From Majordomo-Users-Owner Tue Oct 19 20:24:00 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA25931; Tue, 19 Oct 93 20:24:00 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA25921; Tue, 19 Oct 93 13:23:46 PDT Message-Id: <9310192023.AA25921@mycroft.GreatCircle.COM> To: andy@homebase.vistachrome.com (Andy Finkenstadt) Cc: majordomo-users@greatcircle.com Subject: Re: Coping with "MAJORDOMO ABORT" ? In-Reply-To: Your message of Tue, 19 Oct 1993 16:00:47 -0400 (EDT) Date: Tue, 19 Oct 1993 13:23:45 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk andy@homebase.vistachrome.com (Andy Finkenstadt) writes: # Well, I managed to stress out majordomo. :-) # # I am taking over the rec.arts.erotica mailing list reflector, and have # had subscription requests out the wazoo. Apparently when someone asks # to be subscribed to the list and someone else asks for a list of lists, # they collide and the lists command aborts out. Please note the times # in the capture below: # # Oct 19 12:31:18 cyan majordomo[2761] {person1} subscribe erotica person1 # Oct 19 12:31:23 cyan majordomo[2821] {person2} lists # Oct 19 12:31:28 cyan majordomo[2808] {person3} subscribe erotica person3 # Oct 19 12:31:29 cyan majordomo[2821] {person2} (split to next line) # ABORT Can't open list /usr/local/lib/majordomo/lists/shlock2781 # Oct 19 12:31:31 cyan majordomo[2808] {person3} help # # Notice that person3's job is still being processed apparently with # a "subscribe" "help" set of lines. # # I can think of three things that can help this situation: # 1. change shlock.pl to use the parent directory or /tmp for its lock file # 2. change lists to lock the directory while it does its stuff # 3. change lists to skip any files beginning 'shlock' # # Could this be a real bug, or do I have my system configured incorrectly, # or should I already have done 1 or 2 by virtue of applying previously # mentioned patches? (I am using the release of majordomo available a # week ago.) No, it's a real bug, which I first stumbled across last month. Basicly, the problem is that, as far as Majordomo is concerned, "shlock12345" (which is the form of temporary files that "shlock" creates) is a valid name for a mailing list. The solution is to use "shlock.12345" instead; since this has a "." in it, Majordomo doesn't think it's a valid list name. A patch to do this is included below; this is in the next release. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 6,7c6,7 < # $Revision: 1.6 $ < # $Date: 1993/04/16 23:21:31 $ --- > # $Revision: 1.7 $ > # $Date: 1993/10/19 20:21:34 $ 114c114 < $tempname .= "shlock$$"; --- > $tempname .= "shlock.$$"; 116c116 < $tempname = "shlock$$"; --- > $tempname = "shlock.$$"; From Majordomo-Users-Owner Tue Oct 19 21:36:11 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA26263; Tue, 19 Oct 93 21:36:11 GMT Received: from NDA.COM (nda.nda.COM) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA26255; Tue, 19 Oct 93 14:36:04 PDT Received: by NDA.COM (4.1/SMI-4.1) id AA10464; Tue, 19 Oct 93 17:39:47 EDT From: kovar@NDA.COM (David Kovar) Message-Id: <9310192139.AA10464@NDA.COM> Subject: Creation of mailing lists via email? To: majordomo-users@greatcircle.com Date: Tue, 19 Oct 1993 17:39:46 -0400 (EDT) X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 646 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We'd like to be able to create mailing lists via email, not just add people to them. This seems a) relatively easy to do and b) relatively easy to screw up and open up a major security hole. Before I head off and do this, has anyone else already done it? What I'd like to do is: 1) Accept a mail message. 2) Validate the user as someone who is allowed to create a list. 3) Set up the necessary files. * The password can come from the mail message. * The info file probably comes from the mail message as well. 4) Add the appropriate entries to the aliases file. 5) Log the activity. Anything else that it should do? -David From Majordomo-Users-Owner Wed Oct 20 04:50:09 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA28332; Wed, 20 Oct 93 04:50:09 GMT Received: from illuminati.IO.COM by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA28322; Tue, 19 Oct 93 21:50:01 PDT Received: by illuminati.IO.COM (5.67/PERFORMIX-0.9/08-16-92) id AA16244; Tue, 19 Oct 93 23:50:38 -0500 From: zeek@IO.COM (zeek) Message-Id: <9310200450.AA16244@illuminati.IO.COM> Subject: unexpected eof To: majordomo-users@GreatCircle.COM (majord) Date: Tue, 19 Oct 1993 23:50:37 -40962758 (CDT) X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1361 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've probably the record for unsuccessful majordomo installation attempts (yes, I'm still trying). I've modified just about each and every file, adjusted and readjusted the makefile... I get a wrapper, but upon requesting "make install" belched out is the below. Gee whiz, I'm just trying to install majordomo on linux running smail. Somebody out there told me they have done the same and was successful. If anyone could help with this failing endeavor, I would be very thankful. frustrated, -z Unexpected EOF. Looking for `''. Syntax error + install -c -m 755 -o daemon -g majordom new-list /usr/local/etc/majordomo/new- list Unexpected EOF. Looking for `''. Syntax error + install -c -m 755 -o daemon -g majordom request-answer /usr/local/etc/majordom o/request-answer Unexpected EOF. Looking for `''. Syntax error + install -c -m 755 -o daemon -g majordom resend /usr/local/etc/majordomo/resend Unexpected EOF. Looking for `''. Syntax error + install -c -m 755 -o daemon -g majordom majordomo.pl /usr/local/etc/majordomo/ majordomo.pl Unexpected EOF. Looking for `''. Syntax error + install -c -m 755 -o daemon -g majordom majordomo_version.pl /usr/local/etc/ma jordomo/majordomo_version.pl Unexpected EOF. Looking for `''. Syntax error + install -c -m 755 -o daemon -g majordom shlock.pl /usr/local/etc/majordomo/shl ock.pl /home/zeek/Md> From Majordomo-Users-Owner Wed Oct 20 05:27:15 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA28517; Wed, 20 Oct 93 05:27:15 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA28509; Tue, 19 Oct 93 22:27:07 PDT Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA02418; Tue, 19 Oct 93 22:26:47 PDT Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0opUuT-00031uC; Tue, 19 Oct 93 21:12 PDT Message-Id: From: Alan Millar Subject: Re: a directory for each mailing list To: andy@homebase.vistachrome.com (Andy Finkenstadt) Date: Tue, 19 Oct 1993 21:12:26 -0800 (PDT) Cc: rhc@infocal.berkeley.edu, majordomo-users@GreatCircle.COM In-Reply-To: <9310180611.AA09572@homebase.vistachrome.com> from "Andy Finkenstadt" at Oct 18, 93 02:11:23 am Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1061 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Andy Finkenstadt spake of these matters: > > rhc@infocal.berkeley.edu said in a letter: > > > > Tom Limoncelli suggested a schema > > like the following, whereby we implement each mailing list as a > > directory containing the pertinent files. > associative arrays are possible in PERL, but this construct may work: > > lists[$listname][$feature] > How does that sound? Is it sound? Well, I thought that we hashed through all this about a month ago and at that time the discussion was pointing toward a configuration file for each list that would hold all the options, instead of the presence/absence of all the "list.something" files. John Rouillard was workign on this; where are things at, John? - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ I believe the word you're looking for is "AAAAAAGHHHHHH!!!!" -Batman Returns From Majordomo-Users-Owner Wed Oct 20 05:53:01 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA28683; Wed, 20 Oct 93 05:53:01 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA28674; Tue, 19 Oct 93 22:52:24 PDT Message-Id: <9310200552.AA28674@mycroft.GreatCircle.COM> To: Alan Millar Cc: andy@homebase.vistachrome.com (Andy Finkenstadt), rhc@infocal.berkeley.edu, majordomo-users@GreatCircle.COM Subject: Re: a directory for each mailing list In-Reply-To: Your message of Tue, 19 Oct 1993 21:12:26 -0800 (PDT) Date: Tue, 19 Oct 1993 22:52:23 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Alan Millar writes: # Well, I thought that we hashed through all this about a month ago # and at that time the discussion was pointing toward a configuration # file for each list that would hold all the options, instead of the # presence/absence of all the "list.something" files. # # John Rouillard was workign on this; where are things at, John? Waiting on me. I have about 100 messages related to that discussion sitting in my +inbox that I just haven't had time to read and consider. With my current workload, I don't expect to get to the changes for at least another month or two. In the mean time, I've avoided making any major changes to Majordomo (basicly, nothing but bug fixes) in order to ease the integration process. I _might_ make an interim bugfix release soon. A few minor and a couple of not-minor but not-major bugs have cropped up and been fixed. If another not-minor bug crops up and gets fixed, I'll probably break down and put out an interim release. I apologize for the delay, but Majordomo is something I do in my spare time; as such, it has some stiff competition (including sometimes life&death stuff like looking for missing airplanes) for attention. I _wish_ I could support Majordomo to the extent that, for instance, Sam Leffler supports the FlexFAX package, but I just don't have that kind of time available to spend on this project. If you want new features in a stable, released package, you're just going to have to wait a while longer. If you've got to have them RIGHT NOW, then feel free to apply the patches yourself; most of them have been posted to this mailing list. Before you do that, though, you should consider carefully your strategy for upgrading to future Majordomo releases; if I don't select the same patches you do, or if I change things somewhat from the basic patch posted to this list (both of which are quite likely), you're going to have a hard time upgrading. I don't intend to let Majordomo fall victim to the kind of situation that Sendmail has found itself in, with multiple independent releases and development efforts going on all at the same time. Majordomo carries a Copyright that says "For Use By Permission Only"; I specificly have NOT granted anyone permission to distribute a modified version of Majordomo, nor do I intend to. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Wed Oct 20 16:54:10 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA00893; Wed, 20 Oct 93 16:54:10 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA00885; Wed, 20 Oct 93 09:53:54 PDT Received: from cs.umb.edu by cs.umb.edu with SMTP id AA04138 (5.65c/IDA-1.4.4 for ); Wed, 20 Oct 1993 12:57:35 -0400 Message-Id: <199310201657.AA04138@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: a directory for each mailing list In-Reply-To: Your message of "Tue, 19 Oct 1993 22:52:23 PDT." <9310200552.AA28674@mycroft.GreatCircle.COM> Date: Wed, 20 Oct 1993 12:57:33 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9310200552.AA28674@mycroft.GreatCircle.COM>, Brent Chapman writes: > Alan Millar writes: > > # Well, I thought that we hashed through all this about a month ago > # and at that time the discussion was pointing toward a configuration > # file for each list that would hold all the options, instead of the > # presence/absence of all the "list.something" files. > # > # John Rouillard was workign on this; where are things at, John? Actually Alan, a question for you. What is the status of your pre/post adding command code? > Waiting on me. Well that's true. But Brent doesn't have the most up to date version of that code. I have some code that cleans up the logic, and that fixes a couple of bugs. It also adds a callable interface to the config file parser that allows addin modules to use the parser. One thing I still haven't figured out yet is a mechanism for handing/inputting lists of items, as might be required for excluding addresses. Does anybody have any ideas for a syntax for multiple items. The following are what I have been playing with: # [regexp] (undef) # If the requestor email address matches any of these regexps, # then the list # will be listed in the output of a lists command. failure to match # excludes the list from the output. advertise = EOF /^.*cs.umb.edu$/ /^bbn.com$/ /^athena.mit.edu$/ EOF (or empty line) Advantages: Since its a single command, its easy to parse. The entire value of the option is specified at once, so I don't have to look for conflicts etc. Similar to shell, or perl here document, or majordomo newinfo command. Easy to encode into the keyword associative array by pasting all of the items together with a \001 charater making an array string representation. Disadvanges: Any change to the list requires that the entire list be specified. or advertise.item1 = /^.*cs.umb.edu$/ advertise.item2 = /^bbn.com$/ advertise.item3 = /^athena.mit.edu$/ Advantages: Somewhat more difficult to parse since there needs to be a reserved character that seperates the keyword (advertize) from the place/order modifier. The string representation needs to be turned into an array representation for manpiulation efficiency, and then reconverted to the string representation before use. The keywords themselves seem somewhat grody, and inelegant. Disadvanges: Its possible to replace just one element (say the second one) in the list. This makes it a lot easier to make small changes to the list, and would support Alan's requested style of config file modification. Ideas, comments, quips etc. If you don't know what I am referring to, please check the archives for the mailing list first. Also, I have a few other things that are going on that Brent doesn't have yet, including a couple of extra hooks, like a validate procedure for the inbound address, and code changes that defer reply sending until the last minute (Hi Jennifer). Basically it creates an array called @Reply (wow what a great name huh), and removes the sendmail open code from the main loop. All of the calls that print to the REPLY filehandle instead push onto the array. Then a call to "send_reply" (and to pre_send_reply if defined) opend the sendmail process, and spits all of the goodies. Also the first element of the @reply array is a Send-to: pseudo header line. This line is stripped by send_reply, and the addresses on the line are passed as arguments to the sendmail process. The special case where there are no addresses on the Send-to: line supresses mail. > I have about 100 messages related to that discussion sitting in my > +inbox that I just haven't had time to read and consider. With my > current workload, I don't expect to get to the changes for at least > another month or two. In the mean time, I've avoided making any major > changes to Majordomo (basicly, nothing but bug fixes) in order to ease > the integration process. > > I _might_ make an interim bugfix release soon. A few minor and a > couple of not-minor but not-major bugs have cropped up and been fixed. > If another not-minor bug crops up and gets fixed, I'll probably break > down and put out an interim release. Actually I would appreciate the release in any case, since it will give me an excuse to rework some of the changes I have made. > I apologize for the delay, but Majordomo is something I do in my spare > time; as such, it has some stiff competition (including sometimes > life&death stuff like looking for missing airplanes) for attention. Bah humbug. Missing airplanes indeed, we all know you Civil Air Patrol people are just looking for an excuse to fly 8-) 8-) 8-). On the otherhand us EMT's are just looking for a truck with lots of pretty lights to go crusing in. > If you want new features in a stable, released package, you're just > going to have to wait a while longer. If you've got to have them > RIGHT NOW, then feel free to apply the patches yourself; most of them > have been posted to this mailing list. Before you do that, though, > you should consider carefully your strategy for upgrading to future > Majordomo releases; if I don't select the same patches you do, or if I > change things somewhat from the basic patch posted to this list (both > of which are quite likely), you're going to have a hard time > upgrading. My changes haven't been posted to the list for just this reason. As a matter of fact Brent brought out the 1.6* release just as I was putting the finishing touches on my changes for the 1.56 release (I was in the bloody editor composing my message to him actually). Needless to say I read him the riot act 8-). I was using cvs, so I managed to integrate my changes, and get everything working with 1.6* in 20 or so minutes, but I had to rerun my regression suite that took an hour or so to check. Some of the mods I have made since then (especially for the delayed reply code) make some changes to the internals that seems to have unccovered a bug that occasionally drops mail on the floor, and leaves a hung sendmail and majordomo process. So I won't be releasing any of my mods to the list in general. I hope to meet with Brent at LISA and hash out a few structural changes to the majordomo code. How many people on the list are going to LISA, we may want to think about a bof? > I don't intend to let Majordomo fall victim to the kind of situation > that Sendmail has found itself in, with multiple independent releases > and development efforts going on all at the same time. > > Majordomo carries a Copyright that says "For Use By Permission Only"; I > specificly have NOT granted anyone permission to distribute a modified > version of Majordomo, nor do I intend to. Agreed. That would be bad for majordomo. Already a majordomo user has advertized a nonstandard majordomo command to a large group of people, and I have had a complaint that the majordomo I run "don't work the same". -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 Consulting Systems Programmer Bose rouilj@bose.com Framingham, MA (508) 879-1916 x6483 =============================================================================== My employers don't acknowledge my existence much less my opinions. From Majordomo-Users-Owner Fri Oct 22 18:49:10 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA08072; Fri, 22 Oct 93 18:49:10 GMT Received: from eng.auburn.edu (edison.eng.auburn.edu) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA08064; Fri, 22 Oct 93 11:49:02 PDT Received: from netman.eng.auburn.edu by eng.auburn.edu (4.1/SMI-4.0 edison 1.21) id AA25575; Fri, 22 Oct 93 13:52:50 CDT Date: Fri, 22 Oct 93 13:52:50 CDT From: Richard Elling Message-Id: <9310221852.AA25575@eng.auburn.edu> To: majordomo-users@GreatCircle.COM Subject: majordomo resend options X-Sun-Charset: US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm finally getting around to looking into using majordomo instead of a more-or-less home grown listserv program. I am particularly interested in the moderation possibilities in majordomo. However, I've got a problem with the resend script. If it works as advertised it is just the thing I need. The problem is that some of the options are upper case letters (-A, -C, -M, -R). Once my mailer gets ahold of the alias for the resend, it converts everything to lower case. So the upper case options don't work :-(. What to do? 1. change the resend script's options. 2. change my mailer and potentially break lots of other stuff. 3. change the option in sendmail.cf, if there is one, and see what that breaks. Thanks for any suggestions. -- richard Richard Elling, Manager of Network Support, Engineering Administration Auburn University richard.elling@eng.auburn.edu kb4hb.ampr.org Where is Auburn? Go to Margaritaville, take a right, and go until you have to ask yourself where in the hell you are. From Majordomo-Users-Owner Fri Oct 22 21:10:37 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA08318; Fri, 22 Oct 93 21:10:37 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931019) id AA08309; Fri, 22 Oct 93 14:10:25 PDT Message-Id: <9310222110.AA08309@mycroft.GreatCircle.COM> To: Richard Elling Cc: majordomo-users@GreatCircle.COM Subject: Re: majordomo resend options In-Reply-To: Your message of Fri, 22 Oct 93 13:52:50 CDT Date: Fri, 22 Oct 1993 14:10:24 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Richard Elling writes: # I'm finally getting around to looking into using majordomo instead # of a more-or-less home grown listserv program. I am particularly # interested in the moderation possibilities in majordomo. However, # I've got a problem with the resend script. If it works as advertised # it is just the thing I need. The problem is that some of the options # are upper case letters (-A, -C, -M, -R). Once my mailer gets ahold # of the alias for the resend, it converts everything to lower case. # So the upper case options don't work :-(. What to do? # 1. change the resend script's options. # 2. change my mailer and potentially break lots of other stuff. # 3. change the option in sendmail.cf, if there is one, and see # what that breaks. Well, your mailer is definitely broken, but how about a workaround... Why not just set up a separate shell script that invokes "resend" with the options you want, and have your alias invoke that shell script? -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Sat Oct 23 00:43:06 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA09837; Sat, 23 Oct 93 00:43:06 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA09828; Fri, 22 Oct 93 17:42:53 PDT Message-Id: <9310230042.AA09828@mycroft.GreatCircle.COM> To: kovar@NDA.COM (David Kovar) Cc: majordomo-users@greatcircle.com Subject: Re: Creation of mailing lists via email? In-Reply-To: Your message of Tue, 19 Oct 1993 17:39:46 -0400 (EDT) Date: Fri, 22 Oct 1993 17:42:51 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk kovar@NDA.COM (David Kovar) writes: # We'd like to be able to create mailing lists via email, not just add # people to them. This seems a) relatively easy to do and b) relatively # easy to screw up and open up a major security hole. Before I head off # and do this, has anyone else already done it? # # What I'd like to do is: # # 1) Accept a mail message. # 2) Validate the user as someone who is allowed to create a list. # 3) Set up the necessary files. # * The password can come from the mail message. # * The info file probably comes from the mail message # as well. # 4) Add the appropriate entries to the aliases file. # 5) Log the activity. Step 4 ("Add appropriate entries to the aliases file") has always been the one that's worried me. How to do this is going to vary greatly from site to site. Some of the issues: Not everybody keeps their alias file in the same place (I've seen /etc/aliases, /var/yp/master/aliases, /usr/lib/aliases, /etc/ypaliases, ...) Not everybody uses the same mailer (and thus not necessarily the same format for the aliases file) You've got to ensure that the "new" aliases don't conflict with any existing aliases And so forth All in all, I've avoided this can of worms to the extent possible. Coming up with a solution for a particular site is pretty easy. I'm not sure anyone can come up with a general solution, but if they do, I'd sure love to hear about it. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Mon Oct 25 13:36:30 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA29490; Mon, 25 Oct 93 20:32:33 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA29469; Mon, 25 Oct 93 13:32:07 PDT Message-Id: <9310252032.AA29469@mycroft.GreatCircle.COM> To: Majordomo-Announce@GreatCircle.COM Cc: Majordomo-Users@GreatCircle.COM Subject: Majordomo version 1.62 released Date: Mon, 25 Oct 1993 13:32:06 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've just released version 1.62 of Majordomo. Like always, it's available for anonymous FTP from FTP.GreatCircle.COM, file pub/majordomo/majordomo.tar.Z. Version 1.62 fixes a couple of bugs and adds some much-needed documentation; see below for a list of changes. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 Changes since release 1.60 ========================== Fixed a major bug in "majordomo" where a file wasn't properly being closed during an "unsubscribe" operation; this would cause (on some platforms, under some circumstances) multiple "unsubscribe" operations contained in a single message to Majordomo to fail silently. Added "Doc" directory, with documentation (well, more documentation than was there previously, anyway) for Majordomo. Included in the directory is the original paper on Majordomo and a file of instructions and explanations about Majordomo for new list owners. Added "Doc/samples" directory of sample list configuration files; thanks to Vince Skahan . Added "Doc/man" directory of online manual pages. Added "majordomo.8" and "approve.1" as the first entries; thanks to Jim Duncan . Fixed a major bug in "approve" that was keeping it from working on standard input. Fixed a minor bug in "approve" that was causing an extra blank line to be added after each "approve" line generated. Changes since release 1.56 ========================== "resend" will now look for an "Approved:" line as the first line of the body, in addition to as a header. This makes it easier for folks who can't insert headers with their mailer to generate "Approved:" lines. "approve" will now approve messages that have been bounced by "resend", in addition to "request for approval" messages generated by Majordomo. This means that you can now easily set up a moderated mailing list by specifying the "-A" and "-a " arguments to "resend", which will cause "resend" to send messages without a valid "Approved:" line to the list owner, who can then use "approve" to OK the messages that they want to be posted. Added support for a "majordomo_version.pl" file, which now lists the official version number for a particular release of the Majordomo package. A "help" command will now return this number, reflecting the version number of the entire package, rather than the version number of the "majordomo" PERL file (which is what "help" returned before). Fixed minor bug where list names were not always being converted to lower case. Thanks to Roger Klorese . Changes since release 1.54 ========================== Added "--" as the first line of responses generated by Majordomo. This keeps bounces of Majordomo-generated messages from being reprocessed as input if some broken mailer bounces them back to Majordomo instead of Majordomo-Owner. Added check to ensure that an address really is subscribed to a list before attempting to process an "unsubscribe" request for that address. This should stop the generation of "approve unsubscribe" requests for addresses that aren't really on the list anyway. Added comments to "sample.cf" file to document all variables set there. Added "get" and "index" commands to access files related to a list. Courtesy of Alan Millar and Paul Haas . Added "-I" (restrict incoming messages to list members) and "-r" (add a "Reply-To:" field) flags to "resend"; see "resend.README" for details. Courtesy of Jon Luini . Renamed "sendmail" subroutine in "resend" to "resend_sendmail", to avoid conflict with "sendmail" subroutine in "majordomo.pl" file. This should put an end to the "Malformed command links" warnings from "resend". Added "-a" (set an "approval" password) and "-A" (require approval of all messages; i.e., make this a moderated mailing list) flags to "resend"; see "resend.README" for details. Added a comment to "README" about running setuid to a sendmail "trusted" user. Added "W_MAJORDOMO_CF" environment variable support to "Makefile" and "wrapper.c", so that this can be hard-coded into "wrapper", rather than inheireted from the environment of "wrapper" (which is a security problem). Changed "request-answer" by expanding recording to include info about the "unsubscribe" command. Changes since release 1.46 ========================== Updated README file. Removed MH dependencies from "approve"; it now works on stdin or file names passed as arguments. Changed "approve" from using multiple ~/.passwd/* files to using a single file ~/.majordomo. See the comments at the start of "approve" for more info. Changed "bounce" from using multiple ~/.passwd/* files to using a single file ~/.majordomo. See the comments at the start of "bounce" for more info. Changes in 1.46 =============== NOTE WELL: existance of a ".private" file used to mean the same thing as existance of a ".closed" file. ".private" now means something different (see below). If you've got lists that are currently ".private", you should make them ".closed" before you install this version of Majordomo. Filename changes (mostly to accomodate 14-character limits): bounce-reminder bounce-remind majordomo.cf.sample sample.cf request-recording request-answer mailstuff.pl majordomo.pl Code reorganization; moved must support functions to "majordomo.pl". Fixed log locking bug; log now locked before each write. Fixed truncation bug caused by indiscriminate "chop"; now only chops trailing newlines. Both "subscribe" and "unsubscribe" now check to see if a requesting address looks like a real name rather than an email address (i.e., if the user issued a LISTSERV-style "subscribe " command, rather than a Majordomo-style "subscribe []" command). If it doesn't look like an email address, it squawks to the user and punts the request. Majordomo now slightly more liberal in accepting list names; it will now take "", "list@site", and "" as synonyms for "list". Majordomo now recognizes any line beginning with a "-" as equivalent to an "end" command, so it won't process automatically-added signatures any more. All requests to a given list can now be automatically approved by creating a file "$listdir/.auto". The list owner still gets the standard "SUBSCRIBE" and "UNSUBSCRIBE" advisories. Responses to "info" requests now include a "last updated " line at the end, telling when the ".info" file was last updated. If you want the date printed and labelled in a particular timezone (GMT, say), you need to set that timezone in your TZ environment variable; something like this in your majordomo.cf file works well: $ENV{"TZ"} = "GMT"; Which mailer to use, and what arguments to pass it, can now be configured in the .cf file. You have to use a mailer that will accept the header along with the text of the message (such as sendmail). To set your own mailer, set the "$mailer" variable in the .cf file to the string to use to invoke the mailer. The default, if none is specified, is: "/usr/lib/sendmail -f\$sender \$to" You can use "\$sender", "\$to", "\$from", and/or "\$subject" in your command. Make sure you use the "\", so that these variables will be expanded later, rather than when the .cf file is read. The "which" command now does a case-insensitive substring match, rather than an address match. Any address which matches the argument to "which" is included in the output to "which". I.e., "which brent" will now match "brent", "Brent@GreatCircle.COM", "Chapman@GreatCircle.COM (Brent Chapman)", etc. You can now tell Majordomo, on a per-list basis, to strip comments from addresses before writing them to the list file by creating a file "$listdir/.strip". For example, in both "Brent@GreatCircle.COM (Brent Chapman)" and "Brent Chapman ", "Brent Chapman" is a comment, and the address can be simplified to "brent@greatcircle.com". You can now tell Majordomo, on a per-list basis, that a list is "private" by creating a file "$listdir/.private". If such a file exists, then only members of the list can access the list with "who" and "which" commands. $Header: /mycroft/brent/majordomo/RCS/Changes,v 1.5 1993/10/25 20:22:55 brent Exp brent $ From Majordomo-Users-Owner Mon Oct 25 21:38:42 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA00157; Mon, 25 Oct 93 21:38:42 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA29984; Mon, 25 Oct 93 14:34:40 PDT Received: from bolis by sgiblab.sgi.com via UUCP (920330.SGI/911001.SGI) id AA17674; Mon, 25 Oct 93 14:29:56 -0700 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0orYrT-00031hC; Mon, 25 Oct 93 13:49 PDT Message-Id: From: Alan Millar Subject: Re: a directory for each mailing list To: rouilj@cs.umb.edu (John P. Rouillard) Date: Mon, 25 Oct 1993 13:49:50 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199310201657.AA04138@cs.umb.edu> from "John P. Rouillard" at Oct 20, 93 12:57:33 pm Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1110 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst John P. Rouillard spake of these matters: > Actually Alan, a question for you. What is the status of your pre/post > adding command code? Uhh, well, um,... actually, I forget. I haven't worked on it for a few weeks. Time to look it over again. > Agreed. That would be bad for majordomo. Already a majordomo user has > advertized a nonstandard majordomo command to a large group of people, > and I have had a complaint that the majordomo I run "don't work the > same". One of the discussion topics previously was how to integrate new, local commands into the "help" message. Based on the problem of diverging versions mentioned above, perhaps the help response should always distinguish between standard commands and locally-added (no matter how common) commands. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ Ren: Stimpy, your wealth of ignorance astounds me! Stimpy: They don't call me stupid for nothing! From Majordomo-Users-Owner Tue Oct 26 00:14:44 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA00937; Tue, 26 Oct 93 00:14:44 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA00928; Mon, 25 Oct 93 17:14:34 PDT Message-Id: <9310260014.AA00928@mycroft.GreatCircle.COM> To: Alan Millar Cc: rouilj@cs.umb.edu (John P. Rouillard), majordomo-users@GreatCircle.COM Subject: Re: a directory for each mailing list In-Reply-To: Your message of Mon, 25 Oct 1993 13:49:50 -0800 (PDT) Date: Mon, 25 Oct 1993 17:14:33 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Alan Millar writes: # One of the discussion topics previously was how to integrate new, local # commands into the "help" message. Based on the problem of diverging # versions mentioned above, perhaps the help response should always # distinguish between standard commands and locally-added (no matter # how common) commands. Not a bad idea. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Wed Oct 27 18:31:47 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA09630; Wed, 27 Oct 93 18:31:47 GMT Received: from atlantis.eng.umd.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA09620; Wed, 27 Oct 93 11:31:38 PDT Received: by atlantis.eng.umd.edu (5.65c/IDA-1.4.4) id AA02312; Wed, 27 Oct 1993 14:29:31 -0400 Rcpt to: Date: Wed, 27 Oct 1993 14:29:31 -0400 From: "Randall S. Winchester" Message-Id: <199310271829.AA02312@atlantis.eng.umd.edu> To: Majordomo-Users@greatcircle.com, brent@greatcircle.com Subject: Has there been any consideration to putting the "lists" in directories? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have about 70 lists at the moment and could see this grow to 100+ by the summer. It is becoming painful to work in a directory with 350 files in it. By summer this will be around 500. It would seem resonable to put the lists in lists/$list/ instead of the current arraingment. I would prefer to follow along with the same code that you release, and not diverge. Have others run into the situation? Thanks, Randall From Majordomo-Users-Owner Wed Oct 27 19:21:03 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA09839; Wed, 27 Oct 93 19:21:03 GMT Received: from spiff.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA09831; Wed, 27 Oct 93 12:20:40 PDT Received: by spiff.ccs.carleton.ca (4.1/SMI-4.0-mcr) id AA22049; Wed, 27 Oct 93 15:10:26 EDT Date: Wed, 27 Oct 93 15:10:26 EDT From: mcr@ccs.carleton.ca (Michael Richardson) Message-Id: <9310271910.AA22049@spiff.ccs.carleton.ca> To: rsw@eng.umd.edu Cc: Majordomo-Users@GreatCircle.COM, brent@GreatCircle.COM In-Reply-To: "Randall S. Winchester"'s message of Wed, 27 Oct 1993 14:29:31 -0400 <199310271829.AA02312@atlantis.eng.umd.edu> Subject: Has there been any consideration to putting the "lists" in directories? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I hacked a lot of the code already, and with Brent's blessing would post patches. I think I already offered them back to Brent, didn't I? -- :!mcr!: HOME: mcr@sandelman.ocunix.on.ca +1 613 788 2600 3853 Michael Richardson WORK: mcr@ccs.carleton.ca (Conservation Ecology) Here is an HTML reference to my bio. foreach $X ("E-Journal","NetBSD","Perl","Physics") { print "MCR hacks $X\n"; }; From Majordomo-Users-Owner Wed Oct 27 19:40:11 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA09874; Wed, 27 Oct 93 19:40:11 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA09864; Wed, 27 Oct 93 12:40:01 PDT Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA10646 (5.65c/IDA-1.4.4 for ); Wed, 27 Oct 1993 15:42:42 -0400 Message-Id: <199310271942.AA10646@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: Has there been any consideration to putting the "lists" in directories? In-Reply-To: Your message of "Wed, 27 Oct 1993 14:29:31 EDT." <199310271829.AA02312@atlantis.eng.umd.edu> Date: Wed, 27 Oct 1993 15:42:37 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199310271829.AA02312@atlantis.eng.umd.edu>, "Randall S. Winchester" writes: > > [yet again the question of what to do with the files explosion occurs] GET AND READ THE ARCHIVES. Alan, Brent, Jenniffer and I have been around and around with this, and the same question and an number of answers were posted less than a week ago. The answer is we are working on it. We are not sure exactly when the config file will be here. I was up till 3AM this morning trying to get all of my changes straightened out and working right before I leave for LISA, so I can do a decent dog and pony show. I personally would like to see it early Q1 of 94, but if things go well, we may be able to get someting out before that. For now just persevere because chances are that any changes you make will be totally clobbered by the changes we make. In fact these changes that Alan and I have proposed may be radical enough to require Majordomo 2.0. In fact, you might have to restructure your mailing list files if we don't provide backward compatibility for the .auto, .xxx files. When it does come, there will be three (maybe 4) files per mailing list. listname, listname.config, listname.passwd, [listname.info] My preference is to fold listname.info into the config file with a info << EOF This is the info for this list EOF style of multiline document. Technically listname.passwd could also be done away with since there is equivalent functionality in the config file, but for safety's sake a "trapdoor" password will be kept in the listname.passwd file, that would work in the case that a bogus config file made it through the sanity checks. Also it is likely that the password will change more often than most other parameters, so a fast way of changing it would be useful. Now for a question: How often to people change the listname.x files? Once a day, once a week, once a month ... I am interested in changes to the following groups: subscription policy files .auto, .closed info file .info ancillary files strip file .strip, hidden file .hidden, or .domain password file .passwd approval password (if in a file) Note the approval password and admin password are seperate because there may be more moderators than actual administrators of the list due to the workload associated with moderating a busy list. Also to the person who (sorry I lost the email, mailer driving error at 2:30 ish) suggested that old config files should be automatically checked into rcs before being supplanted, nice idea, but that would need a mechanism to pull a particular revision of the file out to be useful, so I don't think so. but I think all of the hooks would be there to make an addon module do it. -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 Consulting Systems Programmer Bose (until 10/29/93) rouilj@bose.com Framingham, MA (508) 879-1916 x6483 =============================================================================== My employers don't acknowledge my existence much less my opinions. From Majordomo-Users-Owner Wed Oct 27 21:05:43 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA10175; Wed, 27 Oct 93 21:05:43 GMT Received: from atc.boeing.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA10167; Wed, 27 Oct 93 14:05:32 PDT Received: by atc.boeing.com (5.57) id AA11547; Wed, 27 Oct 93 13:45:44 -0700 Received: from aw137.iasl.ca.boeing.com by aw101.iasl.ca.boeing.com with SMTP id AA14127 (5.65b/IDA-1.4.4 for rouilj@terminus.cs.umb.edu); Wed, 27 Oct 93 13:44:46 -0700 From: "Vincent D. Skahan" Received: by aw137. (5.65c/client-1.3) id AA07181; Wed, 27 Oct 1993 13:45:05 -0700 Message-Id: <199310272045.AA07181@aw137.> Subject: Re: Has there been any consideration to putting the "lists" in directories? To: rouilj@terminus.cs.umb.edu (John P. Rouillard) Date: Wed, 27 Oct 1993 13:45:04 -0700 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199310271942.AA10646@cs.umb.edu> from "John P. Rouillard" at Oct 27, 93 03:42:37 pm X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 1339 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk (John P. Rouillard writes:) > The answer is we are working on it. We are not sure exactly when the > config file will be here. I was up till 3AM this morning trying to get > all of my changes straightened out and working right before I leave > for LISA, so I can do a decent dog and pony show. cool...when and where is the show at LISA ? > How often to people change the listname.x files? Once a day, once a > week, once a month ... I am interested in changes to the following groups: I could see the .info file changing rather frequently on a new list as you get the info you want to provide fine-tuned. > Also to the person who (sorry I lost the email, mailer driving error > at 2:30 ish) suggested that old config files should be automatically > checked into rcs before being supplanted, nice idea, but that would > need a mechanism to pull a particular revision of the file out to be > useful, so I don't think so. but I think all of the hooks would be > there to make an addon module do it. Don't forget that we all do not have RCS...many of us are stuck with SCCS. Also, please make it an optional feature. -- ----------- Vince Skahan ------ vds7789@aw101.iasl.ca.boeing.com ----------- Speaking soon at "Future Unemployed of Philadelphia" - Mitch Williams on the subject "negative feedback can be your friend" From Majordomo-Users-Owner Wed Oct 27 22:16:23 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA10541; Wed, 27 Oct 93 22:16:23 GMT Received: from skat.usc.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA10530; Wed, 27 Oct 93 15:16:16 PDT Received: from sol.usc.edu by skat.usc.edu (4.1/SMI-4.1+ucs-3.6) id AA28608; Wed, 27 Oct 93 15:20:07 PDT Received: by sol.usc.edu (4.1/SMI-4.1+ucs-3.6) id AA22673; Wed, 27 Oct 93 15:20:05 PDT Date: Wed, 27 Oct 93 15:20:05 PDT From: John Riehl To: majordomo-users@greatcircle.com Subject: question Message-Id: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am reviewing unix based list servers. I have a need to replace our vm listserv (by Eric Thomas). Does Majordomo have an option to hide the names of some lists? This would be the equivalent of the confidential option on the VM listserv. thanks. jr (john riehl) From Majordomo-Users-Owner Wed Oct 27 23:11:42 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA10842; Wed, 27 Oct 93 23:11:42 GMT Received: from relay2.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA10833; Wed, 27 Oct 93 16:11:33 PDT Received: from unpc.queernet.org by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA10779; Wed, 27 Oct 93 19:14:27 -0400 Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0osK4m-000MQzC; Wed, 27 Oct 93 16:14 PDT Message-Id: To: John Riehl Cc: majordomo-users@GreatCircle.COM Subject: Re: question In-Reply-To: Your message of Wed, 27 Oct 93 15:20:05 -0700. Date: Wed, 27 Oct 93 16:14:48 PDT From: rogerk@queernet.org Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I am reviewing unix based list servers. I have a need to replace our > vm listserv (by Eric Thomas). Does Majordomo have an option to hide the > names of some lists? This would be the equivalent of the confidential > option on the VM listserv. I coded an "anonymous" capability, and Brent has it for inclusion (hint, hint). If LISTSERV calls this "confidential" I'm inclined to change mine. If you'd like the code for now, I'll gladly send you a diff. It allows "who" only if you specify the list password. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From Majordomo-Users-Owner Thu Oct 28 04:10:36 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA11400; Thu, 28 Oct 93 04:10:36 GMT Received: from relay1.UU.NET by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA11392; Wed, 27 Oct 93 21:10:29 PDT Received: from unpc.queernet.org by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AB05501; Thu, 28 Oct 93 00:14:25 -0400 Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0osOk9-000MQzC; Wed, 27 Oct 93 21:13 PDT Message-Id: To: majordomo-users@greatcircle.com Subject: Two Enhancement Requests Date: Wed, 27 Oct 93 21:13:48 PDT From: rogerk@queernet.org Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'd like the ability to: 1) Log even failed commands 2) Log the entire input message (of course, a mail alias could be used too). This would facilitate helping the frustrated user who can't figure out the directions. By the way, syntax diagrams with []{}| are particularly confusing to most non-compunerds. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From Majordomo-Users-Owner Thu Oct 28 11:06:52 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA12546; Thu, 28 Oct 93 11:06:52 GMT Received: from de5.ctd.ornl.gov by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA12538; Thu, 28 Oct 93 04:06:43 PDT Received: from localhost (de5@localhost) by de5.ctd.ornl.gov (8.6.3/8.6.3) id HAA05362; Thu, 28 Oct 1993 07:10:42 -0400 Date: Thu, 28 Oct 1993 07:10:42 -0400 From: Dave Sill Message-Id: <199310281110.HAA05362@de5.ctd.ornl.gov> To: majordomo-users@greatcircle.com Subject: Re: Has there been any consideration to putting the "lists" in directories? In-Reply-To: <199310272045.AA07181@aw137.> References: <199310271942.AA10646@cs.umb.edu> <199310272045.AA07181@aw137.> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >Don't forget that we all do not have RCS...many of us are stuck with SCCS. >Also, please make it an optional feature. Nobody has to be stuck with SCCS...RCS is free. -- Dave Sill (de5@ornl.gov) Computers should work the way beginners Martin Marietta Energy Systems expect them to, and one day they will. Workstation Support -- Ted Nelson URL http://gatekeeper.dec.com/archive/pub/DEC/DECinfo/html/dsill.html From Majordomo-Users-Owner Thu Oct 28 13:25:21 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA12834; Thu, 28 Oct 93 13:25:21 GMT Received: from eng.auburn.edu (edison.eng.auburn.edu) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA12826; Thu, 28 Oct 93 06:25:14 PDT Received: from netman.eng.auburn.edu by eng.auburn.edu (4.1/SMI-4.0 edison 1.21) id AA23597; Thu, 28 Oct 93 08:29:05 CDT Date: Thu, 28 Oct 93 08:29:05 CDT From: Richard Elling Message-Id: <9310281329.AA23597@eng.auburn.edu> To: majordomo-users@GreatCircle.COM, de5@de5.ctd.ornl.gov Subject: Re: Has there been any consideration to putting the "lists" in directories? X-Sun-Charset: US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > From: Dave Sill > > >Don't forget that we all do not have RCS...many of us are stuck with SCCS. > >Also, please make it an optional feature. > > Nobody has to be stuck with SCCS...RCS is free. It's not free if someone has to retrieve, install and maintain it. SCCS on the other hand ships with several OSes and thus requires no additional work. Richard Elling, Manager of Network Support, Engineering Administration Auburn University richard.elling@eng.auburn.edu kb4hb.ampr.org From Majordomo-Users-Owner Thu Oct 28 14:45:21 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA12985; Thu, 28 Oct 93 14:45:21 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA12976; Thu, 28 Oct 93 07:45:07 PDT Received: from cs.umb.edu by cs.umb.edu with SMTP id AA03308 (5.65c/IDA-1.4.4 for ); Thu, 28 Oct 1993 10:44:30 -0400 Message-Id: <199310281444.AA03308@cs.umb.edu> To: rogerk@queernet.org, riehl@skat.usc.edu Cc: majordomo-users@greatcircle.com Subject: Re: question In-Reply-To: Your message of "Wed, 27 Oct 1993 16:14:48 PDT." Date: Thu, 28 Oct 1993 10:44:29 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , rogerk@queernet.org writes: rtiehl@skat.usc.edu wrote: > > I am reviewing unix based list servers. I have a need to replace our > > vm listserv (by Eric Thomas). Does Majordomo have an option to hide the > > names of some lists? This would be the equivalent of the confidential > > option on the VM listserv. > > I coded an "anonymous" capability, and Brent has it for inclusion > (hint, hint). If LISTSERV calls this "confidential" I'm inclined to > change mine. If you'd like the code for now, I'll gladly send you a > diff. It allows "who" only if you specify the list password. I think the original requestor was looking for a mechanism to stop a list from being listed with a "lists" command. There is good news and bad news. The good news is that it works fine and it is in my config file patches. Of course the bad news is that its in my config file patches and won't be available until the next majordomo release. The way it works is that I have two keywords advertise and noadvertise that accept a list of perl style regular expressions that are matched against the letter's From address in order. The logic table is below: advertise noadvertise listed empty empty yes nomatch X no match empty yes empty nomatch yes match nomatch yes X match no empty means that nothing is specified, nomatch means none of the regexps matched the from line, match means that there was a match. X means it doesn't matter. I have a private-who keyword that allows who queries only if you are on the list. It seems to me that implementing the need for a password (a who password, not the general list password) would be ideal for a pre_who command pulled from a majordomo addin library. -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 Consulting Systems Programmer Bose (until 10/29/93) rouilj@bose.com Framingham, MA (508) 879-1916 x6483 =============================================================================== My employers don't acknowledge my existence much less my opinions. From Majordomo-Users-Owner Thu Oct 28 14:58:22 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA13042; Thu, 28 Oct 93 14:58:22 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA13034; Thu, 28 Oct 93 07:58:12 PDT Received: from bolis by sgiblab.sgi.com via UUCP (920330.SGI/911001.SGI) id AA12657; Thu, 28 Oct 93 08:02:10 -0700 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0osYXG-0002xVC; Thu, 28 Oct 93 07:41 PDT Message-Id: From: Alan Millar Subject: Re: Has there been any consideration to putting the "lists" in directories? To: vds7789@aw101.iasl.ca.boeing.com (Vincent D. Skahan) Date: Thu, 28 Oct 1993 07:41:07 -0800 (PDT) Cc: rouilj@terminus.cs.umb.edu, majordomo-users@GreatCircle.COM In-Reply-To: <199310272045.AA07181@aw137.> from "Vincent D. Skahan" at Oct 27, 93 01:45:04 pm Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 953 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > Also to the person who (sorry I lost the email, mailer driving error > > at 2:30 ish) suggested that old config files should be automatically > > checked into rcs before being supplanted, nice idea, but that would > > need a mechanism to pull a particular revision of the file out to be > > useful, so I don't think so. but I think all of the hooks would be > > there to make an addon module do it. > > Don't forget that we all do not have RCS...many of us are stuck with SCCS. > Also, please make it an optional feature. And I wouldn't be surprised if many Majordomo sites have neither. Optional features like this are great, as long as they are optional... - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ I am the great Oz! Pay no attention to that man behind the curtain! From Majordomo-Users-Owner Thu Oct 28 15:21:49 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA13162; Thu, 28 Oct 93 15:21:49 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA13154; Thu, 28 Oct 93 08:21:31 PDT Received: from cs.umb.edu by cs.umb.edu with SMTP id AA05391 (5.65c/IDA-1.4.4 for ); Thu, 28 Oct 1993 11:25:25 -0400 Message-Id: <199310281525.AA05391@cs.umb.edu> To: "Vincent D. Skahan" Cc: majordomo-users@greatcircle.com Subject: Re: Has there been any consideration to putting the "lists" in directories? In-Reply-To: Your message of "Wed, 27 Oct 1993 13:45:04 PDT." <199310272045.AA07181@aw137.> Date: Thu, 28 Oct 1993 11:25:24 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199310272045.AA07181@aw137.>, "Vincent D. Skahan" writes: > (John P. Rouillard writes:) > > The answer is we are working on it. We are not sure exactly when > > the config file will be here. I was up till 3AM this morning > > trying to get all of my changes straightened out and working right > > before I leave for LISA, so I can do a decent dog and pony show. > > cool...when and where is the show at LISA ? Good question. Actually the dog an pony show was more meant for Brent and Alan i(f he is going to be there), but I guess a few extra people doing review wouldn't hurt. I am currently scheduling a list managers BOF for sometime after 8PM on Tuesday, so the show won't occur before the BOF. > > How often to people change the listname.x files? Once a day, once a > > week, once a month ... I am interested in changes to the following > > groups: > > I could see the .info file changing rather frequently on a new list as you > get the info you want to provide fine-tuned. Yes, I could see that too. Actually I think it may not be a problem because I think I have a scheme to allow Alan's method of single keyword setting to work. > > Also to the person who (sorry I lost the email, mailer driving error > > at 2:30 ish) suggested that old config files should be automatically > > checked into rcs before being supplanted, nice idea, but that would > > need a mechanism to pull a particular revision of the file out to be > > useful, so I don't think so. but I think all of the hooks would be > > there to make an addon module do it. I just realized that the full add in modules discussion (mixins if you will) may not have made it to the list. This is the way I envision it working: majordomo loads all of the files in a directory "addins". Each addin has perl code to register its new commands with the main majordomo parser, and most importantly to provide help info for the commands. Each addin could also register its keywords with the config file parser, so that it would share the same configuration mechanism as the rest of the majordomo package. The addin code could easily provide stubs to trigger an autoload of the real code when it is needed. This would help to reduce the startup time. If a help directive was needed, the newly registered function names would be displayed with a tag indicating that they were non-standard majordomo commands. This should allow easy differentiation between the standard and non-standard commands. > Don't forget that we all do not have RCS...many of us are stuck with SCCS. > Also, please make it an optional feature. Actually I would like to make it a non-existant feature 8-). However, since it should be able to be implimented as an addon (post_newconfig, do_get_config_version ...), you just don't put the file implementing the function in your addon directory. Also implementing one in rcs, and one is sccss shouldn't be all that hard. Then a site can choose which version of the "scs_config" package thay want. Heck you can even create one based on cvs if you like. -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 Consulting Systems Programmer Bose (until 10/29/93) rouilj@bose.com Framingham, MA (508) 879-1916 x6483 =============================================================================== My employers don't acknowledge my existence much less my opinions. From Majordomo-Users-Owner Thu Oct 28 17:15:16 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA13595; Thu, 28 Oct 93 17:15:16 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA13560; Thu, 28 Oct 93 10:14:39 PDT Received: from cs.umb.edu by cs.umb.edu with SMTP id AA10619 (5.65c/IDA-1.4.4); Thu, 28 Oct 1993 13:18:35 -0400 Message-Id: <199310281718.AA10619@cs.umb.edu> To: majordomo-users@greatcircle.com, list-managers@greatcircle.com Subject: List Managers/Majordomo BOF at LISA Date: Thu, 28 Oct 1993 13:18:33 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The BOF on List Management and Majordomo is scheduled for Tuesday evening from 7 - 8pm. The blurb for it is: This BOF will provide a forum for people who manage mailing lists to get togther and exchange ideas. Additionally, there will be a discussion on the future development directions for the majordomo list management package. Given the changes that are occurring in the majordomo world, a portion of this BOF will revolve around Majordomo. However Brent and I hope that this BOF will not devolve into a Majordomo BOF. I would very much appreciate it if list managers who don't use majordomo would also show up. I think it would be useful to hear about problems that you have with your lists, and other list management software. (Maybe your ideas would make good additions to the majordomo software.) I also realize that list management has many tricky issues that are totally outside the realm of list management software, and those issues neeed to be brought forward regardless of majordomo. I hope to see you there. -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 Consulting Systems Programmer Bose (until 10/29/93) rouilj@bose.com Framingham, MA (508) 879-1916 x6483 =============================================================================== My employers don't acknowledge my existence much less my opinions. From Majordomo-Users-Owner Thu Oct 28 19:52:34 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA14375; Thu, 28 Oct 93 19:52:34 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA13924; Thu, 28 Oct 93 11:14:52 PDT Received: from cs.umb.edu by cs.umb.edu with SMTP id AA13586 (5.65c/IDA-1.4.4 for ); Thu, 28 Oct 1993 14:18:26 -0400 Message-Id: <199310281818.AA13586@cs.umb.edu> To: Alan Millar Cc: majordomo-users@greatcircle.com Subject: Re: a directory for each mailing list In-Reply-To: Your message of "Mon, 25 Oct 1993 13:49:50 -0800." Date: Thu, 28 Oct 1993 14:18:24 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Alan Millar writes: > And verily didst John P. Rouillard spake of these matters: > > > Actually Alan, a question for you. What is the status of your pre/post > > adding command code? > > Uhh, well, um,... actually, I forget. I haven't worked on it for a > few weeks. Time to look it over again. Also, while you are looking it and my comments about the interface to it over, here is my code that handles the config files, and a sample config file. I was hoping you could look it over. I think I can do the incremental updates you want in a sort of novel way. As it currently stands, a new config file comes in, is parsed, and if found ok, is read in AFTER deleting all configuration info for the list. however, I have put in a variable that prevents clobbering of the previous info. So I was thinking that a new command incrconfig test testpasswd subscription_policy = auto EOF Could be used that would take the info in the incrconfig block, parse it to make sure then entire block made sense, then it would reload the info after disabiling the flag ($config'clobber) that would clear the old info. Then it would call &mk_default_config() to rewrite the config file with the new info. Would that work for you. I know it's not ideal but it certainly is better than having to supply the entire file. Also asking for an item wouldn't be bad either, you would just have to pretty print the value of $config_opts{$list,"keyword"}. (note there are still a couple of bugs in the code below, I hope to get them fixed before LISA. This should give you an idea of how things work though. If you want to test it, uncomment the functions at the end, and invoke the script as "perl config_parse.pl " e.g. "perl config_parse.pl . foo" will read/parse the file foo.config, or create it if it doesn't exist) #!/bin/sh # This is a shell archive. # Run the file through sh to extract its contents. # shar: Shell Archiver # Run the following text with /bin/sh to create: # config_parse.pl # foo.config # This archive created: Thu Oct 28 14:10:32 1993 cat << \SHAR_EOF > config_parse.pl # A file to parse a majordomo mailing list config file # # writes into the global variable %main'config_opts # # this array holds the interesting info for use by all tools %main'config_opts=(); require 'majordomo.pl'; require 'shlock.pl'; require 'majordomo.cf' ; # here is the config package package config; $config'debug = 2; #Set to non-zero for various debugging levels $clobber = 1; # if 0 don't empty previous list entries for configuration @errors = (); # The config'errors array is used to store error messages # if the array is not empty, it causes main'get_config() # to return 1. $installing_defaults = 0; # Set to 1 when installing defaults, in case # a grab_ function needs to act differently # when dealing with a default item. ## Begin ## The following associative arrays are used: ## ## %comments(keyword, comment) -- keeps comments for each keyword ## The comments are printed out when making a config ## file. So that they will document the use of ## the keyword. ## ## %known_keys(keyword,default value) -- defines the known keys in the ## config file. A null value implies that the ## string is undefined. A default value with '#!' ## at the beginning causes the string to be ## eval'ed. This is useful for substituting the ## list name etc into the string. If the keyword ## takes on a descrete set of values, the ## parse function MUST be grab_enum. The value of ## known_keys is the list of ## enumerated values. The seperator character is ## "\001". Added onto the end is the default ## value. If the value can take on numerous ## values (i.e. is an array), the value is a ## string with each element in the array ## seperated by "\001". ## ## %parse_function(key, function) -- The function to use to parse the ## value for a given key. All functions for this ## purpose begin with "grab_", and are in package ## config. The type of the function can be ## appended with __ to the name of the ## function. There are some special names for ## some of the functions. Any function that ## allows array values must end in _array. This ## allows the main parser to determine that an ## array syntax is allowable for the keyword. ## ## %subsystem(keyword, subsystem) -- tells what subsystem each keyword ## belongs to. By default only majordomo, and ## resend are used as subsystems. This is meant ## for extentions such as majordomo-mh that ## allows access to the mh mail package via ## majordomo. ## End # An associative array of comments for all of the keys # The text is wrapped and filled on output. %comments = ( 'private-get', "Must be on mailing list in order to get files", 'private-index', "Must be on mailing list in order to get file index", 'private-who', "Must be on mailing list in order to use who command", 'private-which', "Must be on mailing list in order to use which command", 'private-info', "Must be on mailing list to use info ", 'advertise', "If the requestor email address matches one of these regexps, then the list will be listed in the output of a lists command. failure to match excludes the list from the output.", 'comments', "Comment string that will be retained across config file rewrites", 'noadvertise', "If the requestor name matches this regexp, then the list will not be listed in the output of a lists command. Noadvertise overrides advertise.", 'description', "Used as description for mailing list when replying to the lists command There is no quoting mechinism, and there is only room for 50 or so characters.", 'subscribe_policy', "One of 3 possible values: open, closed, auto. Open allows people to subscribe themseleves to the list. Closed requires maintainer approval for all subscribe requests to the list. In additon to the keyword, if the file .closed exists, it is the same as specifying the value closed. Auto allows anybody to subscribe anybody to the list without maintainer approval. The existance of the file is the same as specifying the value auto. The value of the keyword overrides any existant files.", 'mungedomain', "When checking to see if the address the user is requesting a subscription for is the same as the users address, this flag makes user@bar.baz.com equivalent to user@baz.com", 'admin_passwd', "(Default is specified in the file .passwd) The password for handling administrative tasks on the list.", 'getconfig_passwd', "A seperate password to allow people to look at the config file for a list. It does not allow write access to the config file.", 'strip', "when adding address to the list, strip off all comments etc, and just put the raw address in the list file. In addition to the keyword, if the file .strip exists, it is the same as specifying a yes value. That yes value is overridden by the value of this keyword.", 'date_info', "put the last updated date for the info file at the top of the info file rather than having it appended with an info command. This is useful if the file is being looked at by some means other than majordomo (e.g. finger).", 'moderate', "(Default is no, but it can also be specified with the -A flag) All posting to group must be approved by moderator.", 'approve_passwd', "(Default is undef, but it can be specified with the -a flag) password to be used in the approved header to allow posting to moderated list, or to bypass resend checks.", 'sender', "(Default can be -request, or specified with the -f flag) the envelope and sender address for the resent mail. This string has \"@\" and the value of resend_host appended to it to make a complete address.", 'maxlength', "(Default is usually undef, or specified with the -M flag) the maximum size of an unapproved message.", 'precedence', "(Default is undef, or specified with -p flag) Put a precedence header with value into the outgoing message.", 'reply_to', "Default value is undef or -specified with -r flag) Put a reply-to header with value into the outgoing message.", 'restrict_post', "(Default value is undef, or specified with -I flag) If defined only address listed in one of the files (colon or space seperated) can post to the mailing list.", 'resend_host', "(Default is specified with -h flag) The host name that is appended to all address strings specified for resend.", 'purge_received', "remove all received lines before resending the message.", 'administrivia', "look for administrative requests e.g. subscribe/unsubscribe and forward those to the list maintainer and not the list.", 'debug', "don't actually forward message, just go though the motions.", 'archive_dir', "The directory where archive programs are kept" ); # match commands to their subsystem, by default only two subsystems # exist, majordomo, and resend %subsystem = ( # 'private', 'majordomo', 'private-get', 'majordomo', 'private-index', 'majordomo', 'private-info', 'majordomo', 'private-who', 'majordomo', 'private-which', 'majordomo', 'advertise', 'majordomo', 'noadvertise', 'majordomo', 'description', 'majordomo', 'subscribe_policy', 'majordomo', 'mungedomain', 'majordomo', 'admin_passwd', 'majordomo', 'getconfig_passwd', 'majordomo', 'strip', 'majordomo', # 'auto', 'majordomo', 'date_info', 'majordomo', 'archive_dir', 'majordomo', # stuff for resend below 'moderate', 'resend', 'approve_passwd', 'resend', 'sender', 'resend', 'maxlength', 'resend', 'precedence', 'resend', 'reply_to', 'resend', 'restrict_post', 'resend', 'purge_received', 'resend', 'administrivia', 'resend', 'resend_host', 'resend', 'debug', 'resend', # general stuff here 'comments', 'config', ); # provide list of known keys. If value is '', then the key is undefined # I.e. the action is just as though there was no keyword found. # otherwise the value is the default value for the keyword. # if the value starts with #!, the rest of the value is eval'ed %known_keys = ( # 'private', '', # like # NOTE: for the purpose of a default, # the value of private has no effect whatsoever # you must set the individual private # elements directly. Leave it undefined 'private-get', 'yes', # must be on list to use get 'private-index', 'no', # must be on list to use index 'private-who', 'no', # must be on list to use who 'private-which', 'no', # must be on list to use which 'private-info', 'no', # must be on list to use info 'advertise', '', #"/cs.umb.edu/\001/bbn.com/", # regexp matches address show list 'noadvertise', '', # regexp matches address # don't show list 'description', 'A list description', # description of list, one line 'subscribe_policy', "open\001closed\001auto\001open", # open, closed, or auto. 'mungedomain', 'no', # is user@foo.com == user@host.foo.com 'admin_passwd', '#!$list.".admin"', # administration password 'getconfig_passwd', '', #password to get a config file 'strip', 'yes', # remove comments from address on list 'date_info', 'yes', # date the info file when installed 'archive_dir', '#!$main\'filedir', # stuff for resend below 'moderate', 'no', # Is list moderated 'approve_passwd', '#!$list.".pass"', # password for approving postings 'sender', '#!$list."-Owner"', # Set sender name 'maxlength', '', # Set max article length 'precedence', 'bulk', # Set/install precendence header 'reply_to', '', # Set/install reply-to header 'restrict_post', '', # Like -I in resend 'purge_received', 'no', # Remove received lines 'administrivia', 'yes',# Enable administrivia checks 'resend_host', '', # Change the host name 'debug', 'no', # enable resend debugging # general stuff below 'comments', '', #comments about config file ); # match a parse function to a keyword # the parse function will be called to parse the value string for # the keyword %parse_function = ( # 'private', 'grab_bool', 'private-get', 'grab_bool', 'private-index', 'grab_bool', 'private-info', 'grab_bool', 'private-who', 'grab_bool', 'private-which', 'grab_bool', 'advertise', 'grab_regexp_array', 'noadvertise', 'grab_regexp_array', 'description', 'grab_string', 'subscribe_policy', 'grab_enum', 'mungedomain', 'grab_bool', 'admin_passwd', 'grab_word', 'getconfig_passwd', 'grab_word', 'strip', 'grab_bool', 'date_info', 'grab_bool', 'archive_dir', 'grab_absolute_dir', # stuff for resend below 'moderate', 'grab_bool', 'approve_passwd', 'grab_word', 'sender', 'grab_word', 'maxlength', 'grab_integer', 'precedence', 'grab_word', 'reply_to', 'grab_word', 'restrict_post', 'grab_restrict_post', 'purge_received', 'grab_bool', 'administrivia', 'grab_bool', 'resend_host', 'grab_word', 'debug', 'grab_bool', # general stuff below 'comments', 'grab_string_array', ); # this function is called to set up a default config file # if majordomo runs and access a list for which no config # file exists. The config file must already be locked. sub mk_default_config { local($listname,$list) = @_; local($i,$intro,$type,$value,$default,$subsystem,$comment) = (); local($op) = '='; format OUT = @<<<<<<<<<<<<<<< @<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< $i, $intro ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~ $comment @<<<<<<<<<<<<<<<< @<< @<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< $i, $op, $value From Majordomo-Users-Owner Thu Oct 28 20:22:03 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA14618; Thu, 28 Oct 93 20:22:03 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA14609; Thu, 28 Oct 93 13:21:46 PDT Received: from cs.umb.edu by cs.umb.edu with SMTP id AA20190 (5.65c/IDA-1.4.4 for ); Thu, 28 Oct 1993 16:25:27 -0400 Message-Id: <199310282025.AA20190@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: a directory for each mailing list (oops) In-Reply-To: Your message of "Thu, 28 Oct 1993 14:18:24 EDT." <199310281818.AA13586@cs.umb.edu> Date: Thu, 28 Oct 1993 16:25:26 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Oops 8-(. In message <199310281818.AA13586@cs.umb.edu>, "John P. Rouillard" writes: >[Some intersting stuff to Alan Miller, and a scheme for allowing > incremental updates to the config files] For those of you who are up on Alan's points regarding my config file change mecanism this may have been interesting. >[A shar of some code for implementing config files, and a sample config file] Actually a partial shar since I forceably rm'ed the queue files while sendmail was running. Please ignore this part. In fact if everyone except Alan would ignore the original letter, I would like it a lot better 8-). My apoligies to Brent for almost releasing the guts of the config file mechanism to the list, and my apoligies to the list for teasing you. ( Yes, yes, I know I have to lay off the majordomo hacking with anchovies after midnight, but it tastes so good 8-). ) -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 Consulting Systems Programmer Bose (until 10/29/93) rouilj@bose.com Framingham, MA (508) 879-1916 x6483 =============================================================================== My employers don't acknowledge my existence much less my opinions. From Majordomo-Users-Owner Sat Oct 30 02:55:06 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA20128; Sat, 30 Oct 93 02:55:06 GMT Received: from sws1.ctd.ornl.gov by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA20116; Fri, 29 Oct 93 19:54:55 PDT Received: from localhost (de5@localhost) by sws1.ctd.ornl.gov (8.6.3/8.6.3) id WAA04065; Fri, 29 Oct 1993 22:58:56 -0400 Date: Fri, 29 Oct 1993 22:58:56 -0400 From: Dave Sill Message-Id: <199310300258.WAA04065@sws1.ctd.ornl.gov> To: majordomo-users@greatcircle.com Subject: question & 2 gotchas Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk First the question. I'm running two 1.60's on an Ultrix system running sendmail 8--everything's working fine. I installed 1.62 for testing, and I'm seeing 10-minute (almost exactly) delays between request and response--even when the request is submitted locally. Responses from the 1.60's are ~30 seconds or less. My guess is that something's having to time out--maybe because a file/dir owner/mode is wrong--but I can't find it. First gotcha: subscribers aren't notified when they're unsubscribed, even when they didn't unsubscribe themselves. I recently received a request to approve an "unsubscribe turner@foo.com" from "turner@bar.baz.edu". I approved it, assuming "turner" had simply moved, but it turns out they were two different Turners. Oops...my fault, of course, but I'd mistakenly thought Majordomo would notify turner@foo.com. Would it be a good idea to send a short notification to unsubscribees? Should it only go to "approve"'d unsubs? Second gotcha: people don't need approval to unsubscribe from closed lists. I don't know why I assumed unsubs would be treated like subs--the documentation never says unsubs require approval, and the comment in the code makes it clear they're not. Just to make it clear, though, the docs should explicitly state that people can unsub from closed lists. We have at least one local list that is mandatory--people aren't allowed to unsubscribe. I can hack in a listname.mandatory to disable unsubs. Any problem with that? I'll see some of you at the BOF... -- Dave Sill (de5@ornl.gov) Computers should work the way beginners Martin Marietta Energy Systems expect them to, and one day they will. Workstation Support -- Ted Nelson URL http://gatekeeper.dec.com/archive/pub/DEC/DECinfo/html/dsill.html From Majordomo-Users-Owner Sat Oct 30 03:16:00 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA20298; Sat, 30 Oct 93 03:16:00 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA20289; Fri, 29 Oct 93 20:15:47 PDT Message-Id: <9310300315.AA20289@mycroft.GreatCircle.COM> To: Dave Sill Cc: majordomo-users@greatcircle.com Subject: Re: question & 2 gotchas In-Reply-To: Your message of Fri, 29 Oct 1993 22:58:56 -0400 Date: Fri, 29 Oct 1993 20:15:46 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dave Sill writes: # First the question. I'm running two 1.60's on an Ultrix system # running sendmail 8--everything's working fine. I installed 1.62 for # testing, and I'm seeing 10-minute (almost exactly) delays between # request and response--even when the request is submitted locally. # Responses from the 1.60's are ~30 seconds or less. My guess is that # something's having to time out--maybe because a file/dir owner/mode is # wrong--but I can't find it. The _only_ change in the "majordomo" file between version 1.60 and version 1.62 was the addition of a "close(NEW)" statement in the "do_unsubscribe" function. There were no changes to "majordomo.pl". The only change to "shlock.pl" was to change the temp file name from "shlock$$" to "shlock.$$". I can't see how any of those very limited changes would account for the behavior you describe above. There aren't any timeouts in Majordomo except in the "shlock" code. If the "shlock" code times out, Majordomo aborts. The only timeout in that code is in the "&lopen()" routine; it tries for 600 seconds (10 minutes) to open a file. Everything that calls &lopen() checks its return value. In almost all cases, a failed &lopen() leads to an abort. The exceptions are: A failed attempt to open a ".info" file leads to a "No info available for list $clean_list" message being returned to the user. A failed attempt to open a file referenced in a "get" command results in a "no such file" message being returned to the user. A failed attempt to open the log file results in the error messages being printed on STDERR. Is your Majordomo log file getting updated? # First gotcha: subscribers aren't notified when they're unsubscribed, # even when they didn't unsubscribe themselves. I recently received a # request to approve an "unsubscribe turner@foo.com" from # "turner@bar.baz.edu". I approved it, assuming "turner" had simply # moved, but it turns out they were two different Turners. Oops...my # fault, of course, but I'd mistakenly thought Majordomo would notify # turner@foo.com. Would it be a good idea to send a short notification # to unsubscribees? Should it only go to "approve"'d unsubs? Yeah, I keep thinking I should add this, and I keep forgetting about it. If somebody _does_ add it, please send me diffs. # Second gotcha: people don't need approval to unsubscribe from closed # lists. I don't know why I assumed unsubs would be treated like # subs--the documentation never says unsubs require approval, and the # comment in the code makes it clear they're not. Just to make it # clear, though, the docs should explicitly state that people can unsub # from closed lists. We have at least one local list that is # mandatory--people aren't allowed to unsubscribe. I can hack in a # listname.mandatory to disable unsubs. Any problem with that? I've always seen this as a feature. If you hack it in, send me the diffs, and I'll try to include them in some future release. I'd suggest a more suggestive name for the flag file, though; how about ".approve_unsub"? # I'll see some of you at the BOF... Yup! -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner Sat Oct 30 04:45:39 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA20535; Sat, 30 Oct 93 04:45:39 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931022) id AA20527; Fri, 29 Oct 93 21:45:27 PDT Received: by interlock.ans.net id AA25184 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Sat, 30 Oct 1993 00:48:02 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Sat, 30 Oct 1993 00:48:02 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Sat, 30 Oct 1993 00:48:02 -0400 From: Dan Simoes Message-Id: <199310300449.AA90978@foo.ans.net> Subject: Re: question & 2 gotchas To: de5@sws1.ctd.ornl.gov (Dave Sill) Date: Sat, 30 Oct 1993 00:49:21 -0400 (EDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <199310300258.WAA04065@sws1.ctd.ornl.gov> from "Dave Sill" at Oct 29, 93 10:58:56 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1587 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > First the question. I'm running two 1.60's on an Ultrix system > running sendmail 8--everything's working fine. I installed 1.62 for > testing, and I'm seeing 10-minute (almost exactly) delays between > request and response--even when the request is submitted locally. > Responses from the 1.60's are ~30 seconds or less. My guess is that > something's having to time out--maybe because a file/dir owner/mode is > wrong--but I can't find it. I've noticed the same thing under linux on a 386. You mean it's not my system? :-) > Second gotcha: people don't need approval to unsubscribe from closed > lists. I don't know why I assumed unsubs would be treated like > subs--the documentation never says unsubs require approval, and the > comment in the code makes it clear they're not. Just to make it > clear, though, the docs should explicitly state that people can unsub > from closed lists. We have at least one local list that is > mandatory--people aren't allowed to unsubscribe. I can hack in a > listname.mandatory to disable unsubs. Any problem with that? I noticed the same thing. I guess if you're responsible enough to belong to the list, then you're also responsible enough to unsub yourself. Subscribing is different because you don't know who the person is. I'd be interested in finding a cure to the long delays. ps doesn't report anything abnormal as far as I can tell, although I'll have to double check... | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY