From majordomo-workers-owner Tue Aug 1 12:30:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA10977 for majordomo-workers-outgoing; Tue, 1 Aug 1995 12:14:49 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA10969 for ; Tue, 1 Aug 1995 12:14:47 -0700 Received: from wpdis03.wpafb.af.mil(192.12.64.11) by miles via smap (V1.3) id sma010966; Tue Aug 1 12:14:23 1995 Received: by wpdis03.wpafb.af.mil id AA27428; Tue, 1 Aug 95 15:13:22 -0400 From: akee@wpdis03.wpafb.af.mil (Earle F. Ake) Message-Id: <9508011913.AA27428@wpdis03.wpafb.af.mil> Subject: Restricting subscribes to a specific domain To: majordomo-workers@greatcircle.com Date: Tue, 1 Aug 1995 15:13:21 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 692 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I have hacked at the majordomo code to allow another subscribe_policy. This one is "restricted". It allows those listed in the restrict_list regexp open subscriptions and those that fail the regexp are treated as a closed list subscription and sent to the list owner. I would like to see these changes added to the next release. Do I post the diffs here or send them to someone? -Earle -- Earle Ake MSG/SID akee@wpdis03.wpafb.af.mil Hassler Communication Systems Technology, Inc. ake@hcst.com 2332 Grange Hall Road; Beavercreek, OH 45431-2345 Phone: 513-427-9000 Base: 4375 Chidlaw Rd. Suite 6; WPAFB, OH 45433-5006 513-257-7240 DSN:787-7240 From majordomo-workers-owner Tue Aug 1 12:33:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA11101 for majordomo-workers-outgoing; Tue, 1 Aug 1995 12:17:52 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA11069 for ; Tue, 1 Aug 1995 12:17:48 -0700 Received: from phydeaux.excell.com(204.57.128.93) by miles via smap (V1.3) id sma011057; Tue Aug 1 12:16:52 1995 Received: (from mfisher@localhost) by phydeaux.excell.com (8.6.9/8.6.9) id MAA09606; Tue, 1 Aug 1995 12:15:06 -0700 Date: Tue, 1 Aug 1995 12:15:05 -0700 (PDT) From: Matt Fisher X-Sender: mfisher@phydeaux.excell.com To: majordomo-workers@greatcircle.com Subject: Out of Memory error with Majordomo 1.93 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I'm having some problems with Majordomo. It keeps giving me Out of Memory errors. When majordomo starts I have at least 8M availible, and it still runs out. Majordomo appears to work fine except that no log file is written out. I added '-w' to the #! line in majordomo, and have include the results of running majordomo by hand, hopefully this output will help. It looks like there might be a problem in majordomo.pl, because it keeps giving Deep recursion warnings. Hopefully I've given enough info to help. If you can give me a hand that would be great, or if you need more information from me just let me know... Matt --- System info: % uname -a Linux phydeaux 1.2.9 #1 Thu Jun 29 09:05:15 PDT 1995 i486 % Perl -v This is perl, version 4.0 for Linux {36LA}-ljl- $RCSfile: perl.c,v $$Revision: 4.0.1.8 $$Date: 1993/02/05 19:39:30 $ Patch level: 36 <0>[11:48am] majordom@phydeaux /usr/local/majordomo% wrapper majordomo Possible typo: "FLAGIT" at /usr/local/majordomo/majordomo line 205. Possible typo: "GETFILE" at /usr/local/majordomo/majordomo line 992. Possible typo: "NCONFIG" at /usr/local/majordomo/majordomo line 714. Possible typo: "PASSWD" at /usr/local/majordomo/majordomo line 427. Possible typo: "command_noadvert" at /usr/local/majordomo/majordomo line 856. Possible typo: "command_advert" at /usr/local/majordomo/majordomo line 856. Possible typo: "majordomo_version" at /usr/local/majordomo/majordomo line 1130. Possible typo: "program_name" at /usr/local/majordomo/majordomo line 27. Possible typo: "return_subject" at /usr/local/majordomo/majordomo line 118. Possible typo: "time" at /usr/local/majordomo/majordomo line 592. sort (...) interpreted as function at /usr/local/majordomo/config_parse.pl line 455. From: mfisher To: majordomo Subject: blah help Use of uninitialized variable at /usr/local/majordomo/majordomo.pl line 68, line 1. Use of uninitialized variable at /usr/local/majordomo/majordomo.pl line 145, line 1. Deep recursion on subroutine "log" at /usr/local/majordomo/majordomo.pl line 195, <> line 1. Deep recursion on subroutine "lopen" at /usr/local/majordomo/majordomo.pl line 230, <> line 1. Deep recursion on subroutine "shlock" at /usr/local/majordomo/shlock.pl line 171, <> line 1. Deep recursion on subroutine "xtmpfile" at /usr/local/majordomo/shlock.pl line 30, <> line 1. Deep recursion on subroutine "open_temp" at /usr/local/majordomo/shlock.pl line 130, <> line 1. Deep recursion on subroutine "abort" at /usr/local/majordomo/majordomo.pl line 491, <> line 1. Out of memory! From majordomo-workers-owner Tue Aug 1 13:02:12 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA12536 for majordomo-workers-outgoing; Tue, 1 Aug 1995 12:52:05 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA12505 for ; Tue, 1 Aug 1995 12:52:00 -0700 Received: from phydeaux.excell.com(204.57.128.93) by miles via smap (V1.3) id sma012493; Tue Aug 1 12:51:36 1995 Received: (from mfisher@localhost) by phydeaux.excell.com (8.6.9/8.6.9) id MAA09838; Tue, 1 Aug 1995 12:49:50 -0700 Date: Tue, 1 Aug 1995 12:49:50 -0700 (PDT) From: Matt Fisher X-Sender: mfisher@phydeaux.excell.com To: majordomo-workers@greatcircle.com Subject: Re: Out of Memory error with Majordomo 1.93 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Problem solved. I should have waited a little longer before I piped off a bug report. It turns out that I didn't have the right permissions set for the majordomo working directory. When majordom tried to write this error message to a log, it sent itself into a loop... From majordomo-workers-owner Tue Aug 1 14:31:05 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA15525 for majordomo-workers-outgoing; Tue, 1 Aug 1995 14:18:27 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA15509 for ; Tue, 1 Aug 1995 14:18:24 -0700 Received: from leibniz.math.psu.edu(146.186.130.2) by miles via smap (V1.3) id sma015500; Tue Aug 1 14:17:56 1995 Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by leibniz.math.psu.edu (8.6.12/8.6.9) with ESMTP id RAA08831; Tue, 1 Aug 1995 17:16:57 -0400 Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.6.12/8.6.9) with ESMTP id RAA21984; Tue, 1 Aug 1995 17:16:56 -0400 Message-Id: <199508012116.RAA21984@augusta.math.psu.edu> X-Mailer: exmh version 1.6.1 5/23/95 To: Matt Fisher cc: majordomo-workers@GreatCircle.COM Subject: Re: Out of Memory error with Majordomo 1.93 In-reply-to: Your message of "Tue, 01 Aug 1995 12:15:05 PDT." References: X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Aug 1995 17:16:55 -0400 From: Dave Barr Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk In message , Matt Fisher writes: > >I'm having some problems with Majordomo. It keeps giving me Out of >Memory errors. When majordomo starts I have at least 8M availible, and >it still runs out. Majordomo appears to work fine except that no log >file is written out. Gee, this sounds just like something mentioned in the FAQ. --Dave From majordomo-workers-owner Wed Aug 2 21:30:35 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id VAA17012 for majordomo-workers-outgoing; Wed, 2 Aug 1995 21:03:27 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id VAA16989 for ; Wed, 2 Aug 1995 21:03:23 -0700 Received: from cs2-gw.cs.binghamton.edu(128.226.171.56) by miles via smap (V1.3) id sma016976; Wed Aug 2 21:02:45 1995 Date: Wed, 2 Aug 1995 23:54:53 -0400 From: "Alex J. Bernardin" Message-Id: <199508030354.XAA20106@hcirisc.cs.binghamton.edu> To: Majordomo-Workers@GreatCircle.COM Subject: forwarded message from alexjb Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk ------- start of forwarded message (RFC 934 encapsulation) ------- In-Reply-To: References: To: Brent@GreatCircle.COM (Brent Chapman) Subject: Re: mail echoes or errors >From the majordomo-users mailing list... > At 8:07 PM 7/25/95, jeff dunn wrote: > >Most of my list members are complaining about receiving mail that they > >have sent to the list. I am aware that this is a default, as I have seen > Brent Chapman writes: > That's the way it works, and there's not much you can do about it. - -- I was discussing this with a friend, and he seems to think that it would simply be a matter of having majordomo parse the /etc/aliases file, and then invoke sendmail with an abbreviated version of the mailing list list. Are there other issues involved, about which we are not aware? While I am not trying to diminish the task, I am curious about whether or not it is planned for any future versions.... Please respond via direct e-mail, as I am not on the workers list (is it an open list ?) - --AlexJB ------- end ------- From majordomo-workers-owner Fri Aug 4 14:30:08 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA09801 for majordomo-workers-outgoing; Fri, 4 Aug 1995 14:15:16 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA09771 for ; Fri, 4 Aug 1995 14:15:11 -0700 Received: from mycroft.greatcircle.com(198.102.244.35) by miles via smap (V1.3) id sma009764; Fri Aug 4 14:15:07 1995 Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-950602) id OAA29025; Fri, 4 Aug 1995 14:09:16 -0700 Received: from ns.dkfz-heidelberg.de(192.55.188.199) by mycroft via smap (V1.3mjr) id sma029021; Fri Aug 4 14:09:00 1995 Received: from borneo.inet.dkfz-heidelberg.de (borneo.inet.dkfz-heidelberg.de [193.174.48.166]) by ns.DKFZ-Heidelberg.de (8.6.10/DKFZ-8.6.9) with SMTP id WAA02325; Fri, 4 Aug 1995 22:43:58 +0200 Received: by borneo.inet.dkfz-heidelberg.de (5.65/Ultrix3.0-C) id AA11277; Fri, 4 Aug 1995 22:43:56 +0200 From: U.Engelmann@DKFZ-Heidelberg.DE (Dr. Uwe Engelmann) Message-Id: <9508042243.ZM11275@borneo.inet.dkfz-heidelberg.de> Date: Fri, 4 Aug 1995 22:43:56 +0200 X-Mailer: Z-Mail (3.2.0 15sep94) To: majordomo-workers@greatcircle.com Subject: Problems with Majordomo Version 1.93 Cc: U.Engelmann@DKFZ-Heidelberg.DE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk We have problems to run majordomo 1.93 on an Ultrix system (ULTRIX V4.3 (Rev. 44)). When we run the test: echo help | /usr/lib/sendmail -v majordomo we get the following: > > majordomo... aliased to "|/usr/local/majordomo-1.93/wrapper majordomo" > "|/usr/local/majordomo-1.93/wrapper majordomo"... Connecting to (prog)... > sh: 1038 Memory fault"|/usr/local/majordomo-1.93/wrapper majordomo"... unknown mailer error 139 > owner-majordomo... aliased to phdoos-master > ... The problem seems to be a memory fault of the wrapper or the majordomo script. Furthermore, we noticed a warning in line 65 of the wrapper: ccom: Warning: wrapper.c, line 65: illegal combination of pointer and integer, op != if ( strchr(argv[1], '/') != (char *) 0) { -------------------------------------------^ We would appreciate any help. Thanks in advance Uwe Engelmann -- ---------------------------------------------------------------------------- Dr. Uwe Engelmann Tel. (+49) 6221 - 42 2382 Deutsches Krebsforschungszentrum Fax. (+49) 6221 - 42 2345 Abt. Medizinische und Biologische Informatik Im Neuenheimer Feld 280 e-mail: U.Engelmann@DKFZ-Heidelberg.de D-69120 Heidelberg, Germany http://mbi.DKFZ-Heidelberg.de/ ---------------------------------------------------------------------------- From majordomo-workers-owner Sun Aug 6 16:00:56 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA24903 for majordomo-workers-outgoing; Sun, 6 Aug 1995 15:43:23 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA24866 for ; Sun, 6 Aug 1995 15:43:17 -0700 Received: from phloem.uoregon.edu(128.223.32.35) by miles via smap (V1.3) id sma024854; Sun Aug 6 15:43:07 1995 Received: (from chandra@localhost) by phloem.uoregon.edu (8.6.12/8.6.12) id PAA21618; Sun, 6 Aug 1995 15:41:56 -0700 Date: Sun, 6 Aug 1995 15:41:55 -0700 (PDT) From: Chandra S Chitneni To: majordomo-workers@greatcircle.com Subject: Re: Majordomo Installation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I am trying to install Majordomo on a sparc-10 running solaris. I have set the W_BIN to be /usr/local/majordomo. I created a directory /usr/local/majordomo and when I try to run the make, it breaks pretty badly saying sh: -DBN="/usr/local/majordomo":not found *** Error code 1 make: Fatal error: Command failed for target wrapper. (I made the user majordom to be the owner and group with id54 and gave 777 to see if it works). It happens right after I start the make. I statements under the BSD are commented and I am using the POSIX. Any help will be appreciated. Thanks, -chandra chandra@oregon.uoregon.edu From majordomo-workers-owner Sun Aug 6 16:01:59 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA22731 for majordomo-workers-outgoing; Sun, 6 Aug 1995 15:30:19 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA20639 for ; Sun, 6 Aug 1995 15:20:42 -0700 Received: from mycroft.greatcircle.com(198.102.244.35) by miles via smap (V1.3) id smama8984; Sun Aug 6 15:18:56 1995 Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-950602) id NAA14369; Sun, 6 Aug 1995 13:57:37 -0700 Received: from darkwing.uoregon.edu(128.223.142.13) by mycroft via smap (V1.3mjr) id sma014344; Sun Aug 6 13:57:09 1995 Received: (from rhaller@localhost) by darkwing.uoregon.edu (8.6.12/8.6.12) id NAA22135; Sun, 6 Aug 1995 13:58:25 -0700 Date: Sun, 6 Aug 1995 13:58:25 -0700 (PDT) From: Rich Haller x6-1716 To: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Subject: bug in config_parse.pl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I got the following error after sending a mkdigest. The digest went out OK. It appears that the reason is that digest tried to update the version number in the .config file and couldn't because I had the wrong protections. This exposed a bug in config_parse.pl. Namely, it calls &abort which is not defined. Perhaps what was meant is &main'abort ? (I note that digest itself has an abort routine, but it defines it as digest'abort and it calls die to do the work.) Here is the offending line from config_parse.pl: open(MCONFIG, "> $listdir/$list.config") || &abort("Can't create new config file $listdir/$list.config"); There is another call which also seems problematic. &main'open_temp(OUT, "$listdir/$list.config.out") || &abort("Can't create new config file $listdir/$list.config.out"); ---------- Forwarded message ---------- >>>> mkdigest testlist-digest *** digest: failed errors follow producing testlist-digest V1 #1 processing /usr/local/majordomo/digests/testlist-digest/001 processing /usr/local/majordomo/digests/testlist-digest/002 Undefined subroutine &config::abort called at config_parse.pl line 526. >>>> From majordomo-workers-owner Tue Aug 8 11:32:33 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA15451 for majordomo-workers-outgoing; Tue, 8 Aug 1995 11:28:01 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA15256 for ; Tue, 8 Aug 1995 11:27:35 -0700 Received: from unknown(142.97.226.11) by miles via smap (V1.3) id sma015226; Tue Aug 8 11:27:01 1995 Received: by wto11.tor.on.doe.ca (1.38.193.4/16.2) id AA13977; Tue, 8 Aug 1995 14:16:32 -0400 Date: Tue, 8 Aug 1995 14:16:32 -0400 (EDT) From: Jean Charest To: majordomo-workers@greatcircle.com Subject: use of restrict post and message fronter/footer Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I am managing a list remotely i.e. configuring the list through e-mail. I do not have login priviledges on the machine running majordomo. My list has been sucessfully running for a few weeks now with both a message fronter and message footer. On friday, I had a problem poster which forced me to activate the restrict_post option. I simply put in the name of the list and all went well except that the fronter and footer do not appear on posted messages anymore. I temporarily removed the restrict_post option and they re-appeared. Is this possibly a problem with majordomo-1.93? Will this be resolved in version 2? Any assistance will be very much appreciated. I am not a suubscriber to this list hence please reply directly. Thank You in advance Jean Charest .------------------------------------------------------. | Jean Charest | | Atmospheric Environment Service | | Environment Canada | | e-mail: charestj@tor.on.doe.ca | | or charestj@aestor.am.doe.ca | '------------------------------------------------------` From majordomo-workers-owner Tue Aug 8 12:32:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA19617 for majordomo-workers-outgoing; Tue, 8 Aug 1995 12:29:21 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA19609 for ; Tue, 8 Aug 1995 12:29:18 -0700 Received: from spsgate.sps.mot.com(192.70.231.1) by miles via smap (V1.3) id sma019603; Tue Aug 8 12:28:53 1995 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA11741 for majordomo-workers@greatcircle.com; Tue, 8 Aug 95 12:27:45 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA28805; Tue, 8 Aug 95 12:27:43 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA08224 for majordomo-workers@greatcircle.com; Tue, 8 Aug 95 12:27:41 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA10052; Tue, 8 Aug 95 14:27:38 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA18840; Tue, 8 Aug 1995 14:27:36 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9508081927.AA18840@miaow.sps.mot.com> Subject: Re: use of restrict post and message fronter/footer To: uunet!tor.on.doe.ca!charestj (Jean Charest) Date: Tue, 8 Aug 1995 14:27:35 -0500 (CDT) Cc: majordomo-workers@greatcircle.com (Majordomo developer's mailing list) In-Reply-To: from "Jean Charest" at Aug 8, 95 02:16:32 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1079 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ Jean Charest writes: ] > > My list has been sucessfully running for a few weeks now with both a > message fronter and message footer. On friday, I had a problem poster > which forced me to activate the restrict_post option. I simply put in the > name of the list and all went well except that the fronter and footer do > not appear on posted messages anymore. I temporarily removed the > restrict_post option and they re-appeared. Works fine for me. Are you sure you didn't get a bounced message and think it was from the list? (Look for BOUNCE in the subject header.) Note that resend doesn't use the same headers to determine the sender that majordomo uses when it subscribes a sender. This can cause problems, for example when one uses a Reply-To header. The reply-to address gets subscribed, but resend ignores it and uses the envelope address to compare against the restrict_post list, fails to find it and bounces the message. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-workers-owner Tue Aug 8 13:30:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA21902 for majordomo-workers-outgoing; Tue, 8 Aug 1995 13:21:42 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA21879 for ; Tue, 8 Aug 1995 13:21:38 -0700 Received: from unknown(142.97.226.11) by miles via smap (V1.3) id sma021869; Tue Aug 8 13:20:52 1995 Received: by wto11.tor.on.doe.ca (1.38.193.4/16.2) id AA20196; Tue, 8 Aug 1995 16:19:32 -0400 Date: Tue, 8 Aug 1995 16:19:32 -0400 (EDT) From: Jean Charest To: David Wolfe Cc: "Majordomo developer's mailing list" Subject: Re: use of restrict post and message fronter/footer In-Reply-To: <9508081927.AA18840@miaow.sps.mot.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On Tue, 8 Aug 1995, Dave Wolfe wrote: > Works fine for me. Are you sure you didn't get a bounced message and > think it was from the list? (Look for BOUNCE in the subject header.) > Note that resend doesn't use the same headers to determine the sender > that majordomo uses when it subscribes a sender. This can cause > problems, for example when one uses a Reply-To header. The reply-to > address gets subscribed, but resend ignores it and uses the envelope > address to compare against the restrict_post list, fails to find it and > bounces the message. > Thanks David. I am getting the BOUNCE messages Okay from majordomo when a non-subscriber tries to post. I reloaded the config file and now the fronter/footer appear fine. I dont know what happened. Sorry to have troubled you. Jean Charest .------------------------------------------------------. | Jean Charest | | Atmospheric Environment Service | | Environment Canada | | e-mail: charestj@tor.on.doe.ca | | or charestj@aestor.am.doe.ca | '------------------------------------------------------` From majordomo-workers-owner Wed Aug 9 11:30:29 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA06647 for majordomo-workers-outgoing; Wed, 9 Aug 1995 11:04:16 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA06624 for ; Wed, 9 Aug 1995 11:04:13 -0700 Received: from glacier.binc.net(205.173.176.10) by miles via smap (V1.3) id sma006598; Wed Aug 9 11:03:23 1995 Received: from [144.92.180.31] by glacier.binc.net (8.6.9/4.03) id NAA24562; Wed, 9 Aug 1995 13:02:11 -0500 Date: Wed, 9 Aug 1995 13:02:11 -0500 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-workers@greatcircle.com From: Kurt Foss Subject: conflict with bounces, send-to? Cc: ggernert@emrg.com Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk We launched a new list last week -- PDF-L -- which is the first list at our IPS, Berbee Systems (majordomo@binc.net). We had a problem in the first days when all bounced mail went back to everyone on the list. The IPS adminstrator remedied that so that all bounces now just come to the two list-owners. But in doing so, the list now does not support "reply" to the full list, but only to the message sender. The administrator says we'll have to choose between having bounces go to the entire list *or* having auto-reply to the entire list. Is that true? ---> > James {PDF-L list-admin}, > > It seems suddenly that when I hit "reply" my message is being sent only to > the message sender, not to the entire PDF-L list. We prefer that a "reply" > would send the response to the entire list by default. Can we get this > changed? > > DIGEST seems very popular! > > Tks ~ Kurt > This cannot be changed unless you want what happened last friday to happen again. Right now, the digest is setup to reply to the list itself but that's dangerous for the same reasons the reply to the list is dangerous, but a little less so. Last friday, the problem was that a broken mailer was accepting a message for a user which was not on their system (bad address). First, it shouldn't have accepted the message. Second, it should have returned the message using the Return-Path: instead of the Reply to: address. Because it used the reply to address, there was no way to determine that the message was a "bounced" email message so it was accepted in the outgoing list. If I make the reply to: pdf-l@emrg.com, we risk the same problem happening again. If I remove the Reply to: header or have it set to the original sender, then only that sender would receive the undeliverable message instead of the entire list. So if I set the reply-to: to be pdf-l@emrg.com, some other broken mailer could use that address to cause a mail loop. The digest bouncing back to the list itself is a risk, but it would only bounce once a night because that "bad address" would only receive a digest message once a night. This would be easy to spot for either a digest or a normal list subscriber because the full digest would be sent to everyone, including the pdf-l people. -James ---<<~k>>--- KURT FOSS, electronic publishing and training E M E R G E (formerly Knowledge In Motion) 579 D'Onofrio, Suite 101 Madison, WI 53719 Ph= 800/829-2459 or 608/829-3454 FAX= 608/829-3561 email1= kfoss@emrg.com email2= kfoss@pobox.com ---<<#>>--- From majordomo-workers-owner Thu Aug 10 01:31:00 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id BAA12898 for majordomo-workers-outgoing; Thu, 10 Aug 1995 01:15:42 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id BAA12890 for ; Thu, 10 Aug 1995 01:15:40 -0700 Received: from newton.space.net(194.45.12.1) by miles via smap (V1.3) id sma012488; Thu Aug 10 01:14:53 1995 Received: from GI020X.goethe.de ([193.174.244.2]) by newton.Space.NET with SMTP id <82439-2>; Thu, 10 Aug 1995 10:13:37 +0200 Received: from gi011l.goethe.de by GI020X.goethe.de; (5.65/1.1.8.2/22Mar95-0153PM) id AA19879; Thu, 10 Aug 1995 10:14:02 +0200 Received: by GI011L.GOETHE.DE (MX V4.1 VAX) id 1; Thu, 10 Aug 1995 09:01:47 +0200 Date: Thu, 10 Aug 1995 09:01:46 +0200 From: reisacher@goethe.de To: X-Vmsmail-To: GI011L::MX%"majordomo-workers@greatcircle.com" Message-Id: <00994A88.62A94B00.1@GI011L.GOETHE.DE> Subject: Memory fault V1.93 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I have following problems to install Majordomo V1.93. The system i use is Digital-Unix OSF/1 V3.0x. This Version is POSIX compliant. After i have checked the Makefile for POSIX flags, I compiled the source. ##### # make cc -DBIN=\"/rz1c/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/rz 1c/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF=\"MAJORDOMO_CF=/rz1c/majordo mo/majordomo.cf\" -DPOSIX_UID=54 -DPOSIX_GID=54 -DSETGROUP -o wrapper wrapper.c /usr/lib/cmplrs/cc/cfe: Warning: wrapper.c, line 65: illegal combination of pointer an d integer if (strchr(argv[1], '/') != (char *) 0L) { -----------------------------^ /usr/lib/cmplrs/cc/cfe: Warning: wrapper.c, line 99: illegal combination of pointer an d integer char setgroups_used = "setgroups_was_included"; ---------^ # make install-wrapper #### The owner and group of all files are set to majordom:majordom. My ALIASES-File looks like this: #### # Majordomo majordomo: "|/rz1c/majordomo/wrapper majordomo" majordom: owner-majordomo majordomo-owner: reisacher owner-majordomo: majordomo-owner # # Mailing Lists # owner-deutschstunde: deutschstunde-owner deutschstunde-owner: reisacher deutschstunde-approval: deutschstunde-owner deutschstunde: "|/rz1c/majordomo/wrapper resend -p bulk -M 10000 -l deutschstunde deutschstunde-owner -h mail.goethe.de -s deutschstunde-outgoing" deutschstunde-outgoing: :include:/rz1c/majordomo/lists/deutschstunde,deutschstunde-archive owner-deutschstunde-outgoing: deutschstunde-owner deutschstunde-archive: /rz1c/majordomo/lists/deutschstunde owner-deutschstunde-archive: deutschstunde-owner deutschstunde-request: "|/rz1c/majordomo/wrapper request-answer deutschstunde" owner-deutschstunde-request: deutschstunde-owner #### First i didn't install wrapper by user majordom and i got the following bounce, when i mailed to "deutschstunde": #### ----- Transcript of session follows ----- /rz1c/majordomo/wrapper: error: recompile with POSIX flags. 554 "|/rz1c/majordomo/wrapper resend -p bulk -M 10000 -l deutschstunde deutschstunde-owner -h mail.goethe.de -s deutschstunde-outgoing" ... unknown mailer error 4 ----- Unsent message follows ----- #### After i installed wrapper under the user majordom: #### # install -f /rz1c/majordomo -u majordom wrapper wrapper installed as /rz1c/majordomo/wrapper chown majordom /rz1c/majordomo/wrapper # # ./wrapper test euid is: 54 egid is: 54 54 ruid is: 54 rgid is: 54 54 #### all seems okay, but i get following error. #### ----- Transcript of session follows ----- sh: 17264 Memory fault 554 "|/rz1c/majordomo/wrapper resend -p bulk -M 10000 -l deutschstunde deutschstunde-owner -h mail.goethe.de -s deutschstunde-outgoing" ... unknown mailer error 139 ----- Unsent message follows ----- #### What goes wrong? _______________________________________________________________ | Georg Reisacher, Goethe-Institut Munic, System+Network Mgmt. | | D 80637 Muenchen, Helene-Weber-Allee 1 | /) Phone: +49 89 15921-399 ! FAX: +49 89 15921-435 (\ / ) Internet: reisacher@goethe.de ! WWW: http://www.goethe.de ( \ _( (|________________________________________________________________) ) /> (((\ \) /,) / ) / //))/ (\\\\ \_/ / \ \_/ ///// \ / \ / \ _/ \_ / From majordomo-workers-owner Fri Aug 11 13:30:25 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA15525 for majordomo-workers-outgoing; Fri, 11 Aug 1995 13:18:38 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA15447; Fri, 11 Aug 1995 13:18:28 -0700 Received: from spsgate.sps.mot.com(192.70.231.1) by miles via smap (V1.3) id sma015355; Fri Aug 11 13:17:27 1995 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA25984 for majordomo-workers@greatcircle.com; Fri, 11 Aug 95 13:16:22 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA08486; Fri, 11 Aug 95 13:16:20 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA06501 for majordomo-workers@greatcircle.com; Fri, 11 Aug 95 13:16:18 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA01446; Fri, 11 Aug 95 15:16:14 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA11430; Fri, 11 Aug 1995 15:16:11 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9508112016.AA11430@miaow.sps.mot.com> Subject: Re: message approval; doing it manually... To: close@lunch.engr.sgi.com (Diane Barlow Close) Date: Fri, 11 Aug 1995 15:16:11 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list), majordomo-workers@greatcircle.com (Majordomo developer's mailing list) In-Reply-To: <199508111948.MAA29024@lunch.engr.sgi.com> from "Diane Barlow Close" at Aug 11, 95 12:48:22 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 822 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ I wrote: ] > At least one blank line is *required* between the approval message > headers and the Approved: header, between the Approved: header and > the bounced headers, and between the bounced headers and the bounced > message. If any of these blank lines are missing, the context switch > is missed. It's been pointed out to me that the second case isn't strictly true, a blank line is *not* required (but is allowed) between the Approved: header and the bounced headers. This is because the Approved: header processing in resend doesn't set $pre_hdr to change the state. Probably not worth breaking compatibility to fix, although it apparently isn't what the designer intended. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-workers-owner Fri Aug 11 19:00:06 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA03938 for majordomo-workers-outgoing; Fri, 11 Aug 1995 18:30:55 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA03923 for ; Fri, 11 Aug 1995 18:30:52 -0700 Received: from sgi.com(192.48.153.1) by miles via smap (V1.3) id sma003919; Fri Aug 11 18:30:35 1995 Received: from lunch.engr.sgi.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id SAA23228; Fri, 11 Aug 1995 18:29:30 -0700 Received: by lunch.engr.sgi.com (950413.SGI.8.6.12/911001.SGI) id SAA05713; Fri, 11 Aug 1995 18:29:25 -0700 From: pdc@lunch.engr.sgi.com (Paul Close) Message-Id: <199508120129.SAA05713@lunch.engr.sgi.com> Subject: Re: message approval; doing it manually... To: david_wolfe@risc.sps.mot.com Date: Fri, 11 Aug 1995 18:29:23 -0700 (PDT) Cc: close@risc.sps.mot.com, majordomo-workers@greatcircle.com In-Reply-To: <9508112016.AA11430@miaow.sps.mot.com> from "Dave Wolfe" at Aug 11, 95 03:16:11 pm X-Mailer: ELM [version 2.5 PL0a5] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 877 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk > > At least one blank line is *required* between the approval message > > headers and the Approved: header, between the Approved: header and > > the bounced headers, and between the bounced headers and the bounced > > message. If any of these blank lines are missing, the context switch > > is missed. > > It's been pointed out to me that the second case isn't strictly true, > a blank line is *not* required (but is allowed) between the Approved: > header and the bounced headers. This is because the Approved: header > processing in resend doesn't set $pre_hdr to change the state. Probably > not worth breaking compatibility to fix, although it apparently isn't > what the designer intended. It's documented without a blank line in O'Reilly. Leave it be.... -- Paul Close pdc@sgi.com http://reality.sgi.com/employees/pdc/ No fate but what we make From majordomo-workers-owner Sat Aug 12 18:31:02 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA08204 for majordomo-workers-outgoing; Sat, 12 Aug 1995 18:06:53 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA27328 for ; Wed, 9 Aug 1995 07:00:31 -0700 Received: from wpdis03.wpafb.af.mil(192.12.64.11) by miles via smap (V1.3) id sma027255; Wed Aug 9 06:59:49 1995 Received: by wpdis03.wpafb.af.mil id AA18903; Wed, 9 Aug 95 09:58:39 -0400 From: akee@wpdis03.wpafb.af.mil (Earle F. Ake) Message-Id: <9508091358.AA18903@wpdis03.wpafb.af.mil> Subject: Restricting subscribe to a specific domain To: majordomo-workers@greatcircle.com Date: Wed, 9 Aug 1995 09:58:39 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 12357 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I have patched my version of majordomo to add a restricted option to the subscribe_policy. The idea is some companies want users to be able to have an open list type of environment for all those within the company but have the list be closed to those outside the company. The new option also carries a new variable called restrict_list. This is a regexp which when matched to the requestors address, will allow the list to be open. If the match fails, the request is sent to the list owner as in the case of a closed list. I also made two small changes to the welcome message. The first involved adding a space after the list name which changed this line: local($listrequest) = "or to \"-request@$whereami\".\n"; to this line: local($listrequest) = " or to \"-request@$whereami\".\n"; The second also involved the welcome message. It seems that when $whoami was expanded, the following line was more than 80 characters: you can send mail to "$whoami" with the following command I simply moved the "command" word at the end down to the next line. I hope you will add these changes into the next version of majordomo be it 1.94? or 2.0. These patches are for majordomo 1.93. -Earle -- Earle Ake MSG/SID akee@wpdis03.wpafb.af.mil Hassler Communication Systems Technology, Inc. ake@hcst.com 2332 Grange Hall Road; Beavercreek, OH 45431-2345 Phone: 513-427-9000 Base: 4375 Chidlaw Rd. Suite 6; WPAFB, OH 45433-5006 513-257-7240 DSN:787-7240 #! /bin/sh # This is a shell archive. Remove anything before this line, then unpack # it by saving it into a file and typing "sh file". To overwrite existing # files, type "sh file -c". You can also feed this as standard input via # unshar, or by typing "sh 'config_parse.diff' <<'END_OF_FILE' X*** config_parse.pl~ Wed May 24 15:25:26 1995 X--- config_parse.pl Tue Aug 1 13:51:37 1995 X*************** X*** 86,93 X 'noadvertise', '', # if regexp matches address X # don't show list X 'description', '', # description of list, one line 55 char X! 'subscribe_policy', "open\001closed\001auto\001open", X! # open, closed, or auto. X 'mungedomain', 'no', # is user@foo.com == user@host.foo.com X 'admin_passwd', '#!$list.".admin"', # administration password X 'strip', 'yes', # remove comments from address on list X X--- 86,93 ----- X 'noadvertise', '', # if regexp matches address X # don't show list X 'description', '', # description of list, one line 55 char X! 'subscribe_policy', "open\001closed\001auto\001restricted\001open", X! # open, closed, auto, or restricted. X 'mungedomain', 'no', # is user@foo.com == user@host.foo.com X 'restrict_list', '', # Restrict those that can openly subscribe X 'admin_passwd', '#!$list.".admin"', # administration password X*************** X*** 89,94 X 'subscribe_policy', "open\001closed\001auto\001open", X # open, closed, or auto. X 'mungedomain', 'no', # is user@foo.com == user@host.foo.com X 'admin_passwd', '#!$list.".admin"', # administration password X 'strip', 'yes', # remove comments from address on list X 'date_info', 'yes', # date the info file when installed X X--- 89,95 ----- X 'subscribe_policy', "open\001closed\001auto\001restricted\001open", X # open, closed, auto, or restricted. X 'mungedomain', 'no', # is user@foo.com == user@host.foo.com X+ 'restrict_list', '', # Restrict those that can openly subscribe X 'admin_passwd', '#!$list.".admin"', # administration password X 'strip', 'yes', # remove comments from address on list X 'date_info', 'yes', # date the info file when installed X*************** X*** 181,187 X characters.", X X 'subscribe_policy', X! "One of 3 possible values: open, closed, auto. Open allows people to X subscribe themselves to the list. Auto allows anybody to subscribe X anybody to the list without maintainer approval. The existence of the X file .auto is the same as specifying the value auto. Closed X X--- 182,189 ----- X characters.", X X 'subscribe_policy', X! "One of 4 possible values: open, closed, auto, or restricted. Open allows X! people to X subscribe themselves to the list. Auto allows anybody to subscribe X anybody to the list without maintainer approval. The existence of the X file .auto is the same as specifying the value auto. Closed X*************** X*** 188,194 X requires maintainer approval for all subscribe requests to the X list. In addition to the keyword, if the file .closed X exists, it is the same as specifying the value closed. The value of X! this keyword overrides the value supplied by any existent files.", X X 'mungedomain', X "If set to yes, a different method is used to determine a matching X X--- 190,198 ----- X requires maintainer approval for all subscribe requests to the X list. In addition to the keyword, if the file .closed X exists, it is the same as specifying the value closed. The value of X! this keyword overrides the value supplied by any existent files. X! Restricted means you want the list to be open only for a select group of X! people. See restrict_list", X X 'mungedomain', X "If set to yes, a different method is used to determine a matching X*************** X*** 256,261 X do not have access to the machine running resend. This mechanism will X be replaced in a future version of majordomo/resend.", X X 'resend_host', X "The host name that is appended to all address X strings specified for resend.", X X--- 260,272 ----- X do not have access to the machine running resend. This mechanism will X be replaced in a future version of majordomo/resend.", X X+ 'restrict_list', X+ "If the requestor email address matches one of these X+ regexps, and if subscribe_policy is set to restricted, then the X+ requestor will be subscribed to the list. X+ Failure to match any regexp will send the subscription request to X+ the list owner.", X+ X 'resend_host', X "The host name that is appended to all address X strings specified for resend.", X*************** X*** 344,349 X 'noadvertise', 'majordomo', X 'description', 'majordomo', X 'subscribe_policy', 'majordomo', X 'mungedomain', 'majordomo', X 'admin_passwd', 'majordomo', X 'strip', 'majordomo', X X--- 355,361 ----- X 'noadvertise', 'majordomo', X 'description', 'majordomo', X 'subscribe_policy', 'majordomo', X+ 'restrict_list', 'majordomo', X 'mungedomain', 'majordomo', X 'admin_passwd', 'majordomo', X 'strip', 'majordomo', X*************** X*** 390,395 X 'noadvertise', 'grab_regexp_array', X 'description', 'grab_string', X 'subscribe_policy', 'grab_enum', X 'mungedomain', 'grab_bool', X 'admin_passwd', 'grab_word', X 'strip', 'grab_bool', X X--- 402,408 ----- X 'noadvertise', 'grab_regexp_array', X 'description', 'grab_string', X 'subscribe_policy', 'grab_enum', X+ 'restrict_list', 'grab_regexp_array', X 'mungedomain', 'grab_bool', X 'admin_passwd', 'grab_word', X 'strip', 'grab_bool', END_OF_FILE if test 5457 -ne `wc -c <'config_parse.diff'`; then echo shar: \"'config_parse.diff'\" unpacked with wrong size! fi # end of 'config_parse.diff' fi if test -f 'majordomo.diff' -a "${1}" != "-c" ; then echo shar: Will not clobber existing file \"'majordomo.diff'\" else echo shar: Extracting \"'majordomo.diff'\" \(3739 characters\) sed "s/^X//" >'majordomo.diff' <<'END_OF_FILE' X*** majordomo~ Mon Jul 31 10:57:56 1995 X--- majordomo Tue Aug 1 15:15:49 1995 X*************** X*** 202,208 X return 0; X } X X! local($FLAGIT); X if ($clean_list ne "") { X # The list is valid X # parse its config file if needed X X--- 202,208 ----- X return 0; X } X X! local($FLAGIT) = 0; X if ($clean_list ne "") { X # The list is valid X # parse its config file if needed X*************** X*** 218,223 X || (($config_opts{$clean_list,"subscribe_policy"} ne "closed" ) X && &addr_match($reply_to, $subscriber, X (&cf_ck_bool($clean_list,"mungedomain") ? 2 : undef)))) { X # Either the request is approved, or the list is open and the X # subscriber is the requester, so check to see if they're X # already on the list, and if not, add them to the list. X X--- 218,248 ----- X || (($config_opts{$clean_list,"subscribe_policy"} ne "closed" ) X && &addr_match($reply_to, $subscriber, X (&cf_ck_bool($clean_list,"mungedomain") ? 2 : undef)))) { X+ X+ if ($config_opts{$clean_list,"subscribe_policy"} eq "restricted" ) { X+ # The list is restricted so we now have to parse the X+ # restrict_list to see if the requestor matches X+ if ($config_opts{$clean_list,"restrict_list"} ne '') { X+ local(@array) = (); X+ @array = split(/\001/, $config_opts{$clean_list,"restrict_list"}); X+ # We just want the actual address, not the personal name X+ local($parsed_subscriber) = ""; X+ if ( &cf_ck_bool($clean_list,"strip") ) { X+ $parsed_subscriber = &valid_addr($subscriber); X+ } else { X+ $parsed_subscriber = $subscriber; X+ } X+ # Now for each of the regexp's listed, see if any match X+ foreach $i (@array) { X+ $command = "(qq~$parsed_subscriber~ =~ $i)"; X+ $FLAGIT = 1, last if (eval $command); X+ } X+ } X+ } else { X+ $FLAGIT = 1; X+ } X+ } X+ if ($FLAGIT) { X # Either the request is approved, or the list is open and the X # subscriber is the requester, so check to see if they're X # already on the list, and if not, add them to the list. X*************** X*** 1074,1080 X X local($list4help) = $majordomo_request ? "[]" : ""; X X! local($listrequest) = "or to \"-request@$whereami\".\n"; X $listrequest .= "\nThe parameter is only optional if the "; X $listrequest .= "message is sent to an address\nof the form "; X $listrequest .= "\"-request@$whereami\".\n"; X X--- 1099,1105 ----- X X local($list4help) = $majordomo_request ? "[]" : ""; X X! local($listrequest) = " or to \"-request@$whereami\".\n"; X $listrequest .= "\nThe parameter is only optional if the "; X $listrequest .= "message is sent to an address\nof the form "; X $listrequest .= "\"-request@$whereami\".\n"; X*************** X*** 1246,1252 X X unsubscribe X X! Or you can send mail to "$whoami" with the following command X EOM X X } else { X X--- 1271,1277 ----- X X unsubscribe X X! Or you can send mail to "$whoami" with the following X EOM X X } else { X*************** X*** 1253,1259 X print MSG <<"EOM"; X X If you ever want to remove yourself from this mailing list, X! you can send mail to "$whoami" with the following command X EOM X } X X X--- 1278,1284 ----- X print MSG <<"EOM"; X X If you ever want to remove yourself from this mailing list, X! you can send mail to "$whoami" with the following X EOM X } X X*************** X*** 1258,1264 X } X X print MSG <<"EOM"; X! in the body of your email message: X X unsubscribe $list $subscriber X X X--- 1283,1289 ----- X } X X print MSG <<"EOM"; X! command in the body of your email message: X X unsubscribe $list $subscriber X END_OF_FILE if test 3739 -ne `wc -c <'majordomo.diff'`; then echo shar: \"'majordomo.diff'\" unpacked with wrong size! fi # end of 'majordomo.diff' fi echo shar: End of shell archive. exit 0 From majordomo-workers-owner Tue Aug 15 10:31:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA18910 for majordomo-workers-outgoing; Tue, 15 Aug 1995 10:24:43 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA18855 for ; Tue, 15 Aug 1995 10:24:35 -0700 Received: from is.terc.edu(140.245.194.20) by miles via smap (V1.3) id sma018844; Tue Aug 15 10:24:29 1995 Received: from qm.terc.edu by is.TERC.EDU (5.x/SMI-SVR4) id AA01070; Tue, 15 Aug 1995 13:21:42 -0400 Message-Id: Date: 15 Aug 1995 13:32:34 -0400 From: "Blake Meike" Subject: Ok, what gives (probably ol To: "md" X-Mailer: Mail*Link SMTP-QM 3.0.1 GM Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk RE:Ok, what gives (probably old question) 15/8/95 1:08 PM For the most part, Majordomo has been working pretty well on our system. Since I have plenty to do, I've pretty much left it alone and not poked at it. Recently, however, several annoying problems have been cropping up, and I've finally taken a look at it. One of the problems is that the administrivia flag seems to have no effect whatsoever. On looking at the code in Resend, I find the following: $opt_s = $cf_ck_bool{$opt_l,"administrivia"} if &cf_ck_bool($opt_l,"administrivia"); Although "&cf_ck_bool" seems to do the right thing, getting an appropriate value from the config file, %&cf_ck_bool doesn't seem to exist! opt_s, used throughout the program to see whether or not to perform administrivia checks is always false. Anybody understand what's supposed to happen here? The other problem, which I suspect I will just have to track down, is that the resend.$$.{in, out} files are not being deleted from /tmp when resend gets done with them. Any suggestions? Thank you, Blake Meikeq TERC From majordomo-workers-owner Tue Aug 15 12:00:58 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA23433 for majordomo-workers-outgoing; Tue, 15 Aug 1995 11:57:54 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA23368 for ; Tue, 15 Aug 1995 11:57:45 -0700 Received: from ssi.edc.org(155.38.10.5) by miles via smap (V1.3) id sma023355; Tue Aug 15 11:56:52 1995 Received: from ssi.edc.org by ssi.edc.org id aa11648; 15 Aug 95 14:54 EDT Date: Tue, 15 Aug 1995 14:54:25 -0400 (EDT) From: Gunther Anderson To: Blake Meike cc: md Subject: Re: Ok, what gives (probably ol In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [Other things I don't know deleted...] > The other problem, which I suspect I will just have to track down, is that > the resend.$$.{in, out} files are not being deleted from /tmp when resend > gets done with them. Any suggestions? Definitely bite the bullet and upgrade to Majordomo 1.93. The extra resend files problem is solved there. Failing that, go look through resend and look for the "unlink" commands. Some of them have improper syntax for globbing the names, though not all. When I had this problem on SCO Unix, I replaced the offending lines with explixit unlinks of each file. However, you could just as easily fix the syntax for the ones that are incorrect. What is the correct syntax? I don't know off the top of my head, but I could certainly look it up in the 1.93 code if you'd like. Gunther Anderson Education Development Center From majordomo-workers-owner Tue Aug 15 13:00:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA27352 for majordomo-workers-outgoing; Tue, 15 Aug 1995 12:41:11 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA27273 for ; Tue, 15 Aug 1995 12:40:58 -0700 Received: from spsgate.sps.mot.com(192.70.231.1) by miles via smap (V1.3) id sma027218; Tue Aug 15 12:40:21 1995 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA24771 for majordomo-workers@greatcircle.com; Tue, 15 Aug 95 12:39:02 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA05377; Tue, 15 Aug 95 12:39:01 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA16608 for majordomo-workers@greatcircle.com; Tue, 15 Aug 95 12:38:58 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA18781; Tue, 15 Aug 95 14:38:55 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA11821; Tue, 15 Aug 1995 14:38:47 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9508151938.AA11821@miaow.sps.mot.com> Subject: Re: Ok, what gives (probably ol To: uunet!TERC.EDU!Blake_Meike (Blake Meike) Date: Tue, 15 Aug 1995 14:38:46 -0500 (CDT) Cc: majordomo-workers@greatcircle.com (Majordomo developer's mailing list) In-Reply-To: from "Blake Meike" at Aug 15, 95 01:32:34 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1228 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ Blake Meike writes: ] > > One of the problems is that the administrivia flag seems to have no > effect whatsoever. On looking at the code in Resend, I find the following: > > $opt_s = $cf_ck_bool{$opt_l,"administrivia"} > if &cf_ck_bool($opt_l,"administrivia"); > > Although "&cf_ck_bool" seems to do the right thing, getting an appropriate > value from the config file, %&cf_ck_bool doesn't seem to exist! opt_s, used > throughout the program to see whether or not to perform administrivia checks > is always false. Anybody understand what's supposed to happen here? At least in 1.93, these lines read a little differently: $opt_s = &cf_ck_bool($opt_l,"administrivia") if &cf_ck_bool($opt_l,"administrivia"); No %&cf_ck_bool or even %cf_ck_bool in evidence. And it works just fine. > The other problem, which I suspect I will just have to track down, is that > the resend.$$.{in, out} files are not being deleted from /tmp when resend > gets done with them. Any suggestions? Not a problem in 1.93, but I think it's also addressed in the FAQ. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-workers-owner Wed Aug 16 06:48:16 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA06956 for majordomo-workers-outgoing; Wed, 16 Aug 1995 06:06:53 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA06939 for ; Wed, 16 Aug 1995 06:06:50 -0700 Received: from agisgate.agis.net(205.137.48.30) by miles via smap (V1.3) id sma006935; Wed Aug 16 06:05:59 1995 Received: (from tom@localhost) by agisgate.agis.net (8.6.9/8.6.9) id JAA17401 for majordomo-workers@greatcircle.com; Wed, 16 Aug 1995 09:04:44 -0400 Date: Wed, 16 Aug 1995 09:04:44 -0400 From: Tom Earl Message-Id: <199508161304.JAA17401@agisgate.agis.net> To: majordomo-workers@greatcircle.com Subject: Majordomo-1.93.Z Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hello. I am attempting to unzip majordomo-1.93.Z. I keep getting an error, able to unzip central directory and zipcomments in another file. In a nutshell, It;s saing that there is suspost to be another file, but I've searched high and low and still can not find one... I am FTPing off src.doc.ic.ac.uk site. Is there another way go get this file? I.e. mailing it to me uuencoded? or mailed to me on disk? Please let me know, I'm very interested in this product... Thanks Tom Earl ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ Thomas L. Earl Jr. "He who has the gold ~ ~ Apex Global Information Services make the rules..." ~ ~ Tom@agis.net ~ ~ Phone: +1 313 730 1130 ~ ~ F.A.X. +1 313 563 6119 "Riddle me this, Riddle me that..." ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From majordomo-workers-owner Wed Aug 16 07:00:08 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA07853 for majordomo-workers-outgoing; Wed, 16 Aug 1995 06:56:57 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA07831 for ; Wed, 16 Aug 1995 06:56:53 -0700 Received: from atlantis.eng.umd.edu(129.2.90.28) by miles via smap (V1.3) id sma007820; Wed Aug 16 06:56:32 1995 Received: (from rsw@localhost) by atlantis.eng.umd.edu (8.7.Beta.12/8.7.Beta.4) id JAA13732; Wed, 16 Aug 1995 09:55:01 -0400 (EDT) Date: Wed, 16 Aug 1995 09:54:59 -0400 (EDT) From: "Randall S. Winchester" X-Sender: rsw@atlantis.eng.umd.edu To: Tom Earl cc: majordomo-workers@GreatCircle.COM Subject: Re: Majordomo-1.93.Z In-Reply-To: <199508161304.JAA17401@agisgate.agis.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Majordomo-1.93.Z needs "compress" not "zip". Randall From majordomo-workers-owner Wed Aug 16 10:03:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA12632 for majordomo-workers-outgoing; Wed, 16 Aug 1995 09:31:33 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA12617; Wed, 16 Aug 1995 09:31:30 -0700 Received: from spsgate.sps.mot.com(192.70.231.1) by miles via smap (V1.3) id sma012605; Wed Aug 16 09:30:51 1995 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA19444 for majordomo-workers@greatcircle.com; Wed, 16 Aug 95 09:00:52 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA22638; Wed, 16 Aug 95 09:00:51 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA22788 for majordomo-workers@greatcircle.com; Wed, 16 Aug 95 09:00:49 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA23411; Wed, 16 Aug 95 11:00:48 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA04800; Wed, 16 Aug 1995 11:00:45 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9508161600.AA04800@miaow.sps.mot.com> Subject: Re: restricted post question... To: uunet!euler.math.USMA.EDU!ae6244 Date: Wed, 16 Aug 1995 11:00:45 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list), majordomo-workers@greatcircle.com (Majordomo developer's mailing list) In-Reply-To: <9508161311.AA25419@euler.math.usma.edu> from "Markert Erich Mr." at Aug 16, 95 09:11:14 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 789 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ Markert Erich Mr. writes: ] > > I have an active list that also has a digest version. I would > like to be able to restrict posting the the active list to those > people on the active list and the digest version. Can you specify > two lists for with the restrict post variable? Yes. Separate the file names with colons (:), tabs, or newlines, as described in the comments of any standard list config file (it says space- or colon-separated, but it's wrong). Majordomo-Workers list: consider this a bug report for the config file comments and/or resend. I think whitespace, i.e. the \s Perl metacharacter, should be used to split the $opt_I list. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-workers-owner Wed Aug 16 15:30:32 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA23203 for majordomo-workers-outgoing; Wed, 16 Aug 1995 15:01:10 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA23165 for ; Wed, 16 Aug 1995 15:01:02 -0700 Received: from spsgate.sps.mot.com(192.70.231.1) by miles via smap (V1.3) id sma023156; Wed Aug 16 15:00:16 1995 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA24275 for majordomo-workers@greatcircle.com; Wed, 16 Aug 95 14:59:00 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA01358; Wed, 16 Aug 95 14:58:58 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA26337 for majordomo-workers@greatcircle.com; Wed, 16 Aug 95 14:58:57 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA25840; Wed, 16 Aug 95 16:58:56 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA17843; Wed, 16 Aug 1995 16:58:55 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9508162158.AA17843@miaow.sps.mot.com> Subject: Another restricted post question... (fwd) To: majordomo-workers@greatcircle.com (Majordomo developer's mailing list) Date: Wed, 16 Aug 1995 16:58:55 -0500 (CDT) Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 934 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ George Miller - The CyberMarketing Group writes: ] > > Can someone help me with the correct syntax for restrict_post? Currently it > is set to: > > restrict_post = /usr/local/bin/majordomo/Lists/herky > > When I try to change the config file, I get the following error: > > The new config file for herky was NOT accepted because: > Can't find restrict_post file > /usr/local/bin/majordomo/Lists/usr/local/bin/majordomo/Lists/herky at line 264 Another restrict_post bug: while resend adds $listdir only if the pathname doesn't have a leading '/', sub grab_restrict_post in config_parse.pl won't accept the pathname unless it can find a file "$main'listdir/pathname". They need to agree on the semantics (and the delimiter: see my earlier report re restrict_post pathname delimeters). -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-workers-owner Thu Aug 17 07:01:17 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA20222 for majordomo-workers-outgoing; Thu, 17 Aug 1995 06:57:52 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA20178 for ; Thu, 17 Aug 1995 06:57:45 -0700 Received: from melmac.risc.uni-linz.ac.at(193.170.36.100) by miles via smap (V1.3) id sma020165; Thu Aug 17 06:57:12 1995 Received: from localhost by melmac.risc.uni-linz.ac.at with SMTP id AA26364 (5.67b8/IDA-1.5 for ); Thu, 17 Aug 1995 15:55:54 +0200 Message-Id: <199508171355.AA26364@melmac.risc.uni-linz.ac.at> To: Majordomo-Workers@greatcircle.com Subject: Infinite loop trying to open the Log file Date: Thu, 17 Aug 95 15:55:51 +0200 From: Kurt Siegl Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Hi, Just installed majordomo on our site and imediately got a Perl core dump :( The problem comes from the following fact: If you don't have created the Log file and the write permissions to the directory haven't been set proper majordomo trys to log that problem. That obviosely fails again and majordomo again trys to log that, which can't be done neither, so it want's to log that, .... finaly the stack is full and perl core dumps ;) Would be nice if you could fix that problem, took me just 3 hours to trak down the problem :( Kurt - --------------------------------------------------------------- You should not base your entertainment on other peoples' deaths. - --------------------------------------------------------------- Kurt Siegl / RISC, Johannes Kepler University, A-4040 Linz, Austria email: siegl@risc.uni-linz.ac.at Tel: *(7236)3231-62 Fax: *(7236)3231-30 URL: http://www.risc.uni-linz.ac.at/people/siegl PGP Public Key: finger siegl@risc.uni-linz.ac.at -----BEGIN PGP SIGNATURE----- Version: 2.6.1 iQBVAgUBMDNKZR7Hvf+mKclrAQF8YgH/RITqrdcJaCReVAzJzILqa1sI80Qf8l5H nv1xqlwQoD6gZzpu14+nwRdUhzDDhOkYyM+NmlFjkMl/R8wMBQXVSQ== =IB61 -----END PGP SIGNATURE----- From majordomo-workers-owner Thu Aug 17 09:01:36 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA23632 for majordomo-workers-outgoing; Thu, 17 Aug 1995 08:35:05 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA23594 for ; Thu, 17 Aug 1995 08:34:58 -0700 Received: from mercury.ftech.net(193.133.17.69) by miles via smap (V1.3) id sma023585; Thu Aug 17 08:34:15 1995 Received: (from pdcawley@localhost) by mercury.ftech.net (8.6.11/8.6.9) id QAA09884; Thu, 17 Aug 1995 16:30:55 +0100 Date: Thu, 17 Aug 1995 16:30:54 +0100 (BST) From: Piers Cawley To: Kurt Siegl cc: Majordomo-Workers@GreatCircle.COM Subject: Re: Infinite loop trying to open the Log file In-Reply-To: <199508171355.AA26364@melmac.risc.uni-linz.ac.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On Thu, 17 Aug 1995, Kurt Siegl wrote: > Just installed majordomo on our site and imediately got a Perl core dump :( > > The problem comes from the following fact: > > If you don't have created the Log file and the write permissions > to the directory haven't been set proper majordomo trys to log > that problem. That obviosely fails again and majordomo again trys to log > that, which can't be done neither, so it want's to log that, > > .... > > finaly the stack is full and perl core dumps ;) > > Would be nice if you could fix that problem, took me just 3 hours > to trak down the problem :( This is majordomo's problem? If you can't set up the files and permissions correctly you should expect the thing to fall over. Piers Cawley -- Systems Sheriff on the Frontier Internet Service Purveyors of fine connections to the Internet Phone:+44 171 242 3383 From majordomo-workers-owner Thu Aug 17 10:00:56 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA26258 for majordomo-workers-outgoing; Thu, 17 Aug 1995 09:44:27 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA26232 for ; Thu, 17 Aug 1995 09:44:23 -0700 Received: from basis.basis.com(204.52.207.1) by miles via smap (V1.3) id sma026227; Thu Aug 17 09:43:47 1995 Received: (from mail@localhost) by basis.basis.com (8.6.9/8.6.9) id KAA01276 for ; Thu, 17 Aug 1995 10:40:00 -0600 Received: from bbx.basis.com(204.134.1.133) by basis.basis.com via smap (V1.3) id sma001266; Thu Aug 17 10:39:48 1995 Received: from speedyg.basis.com (speedyg.basis.com [204.134.1.191]) by bbx.basis.com (8.6.9/8.6.9) with ESMTP id QAA16801 for ; Thu, 17 Aug 1995 16:41:39 GMT Received: (from elongmi@localhost) by speedyg.basis.com (8.6.9/8.6.9) id QAA07262 for majordomo-workers@greatcircle.com; Thu, 17 Aug 1995 16:46:55 GMT From: Ernie Longmire Message-Id: <199508171646.QAA07262@speedyg.basis.com> Subject: Re: Infinite loop trying to open the Log file To: majordomo-workers@greatcircle.com Date: Thu, 17 Aug 1995 10:46:54 -0600 (MDT) X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 609 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >> If you don't have created the Log file and the write permissions to the >> directory haven't been set proper majordomo trys to log that problem. >> That obviosely fails again and majordomo again trys to log that, which >> can't be done neither, so it want's to log that, > > This is majordomo's problem? Yes, this is majordomo's problem. It's pretty silly to try to log the fact that you can't write to the logs. There are other cases where it might not be possible to write to the logs, so there ought to be some kind of graceful exit under those circumstances. -- Ernie Longmire (elongmi@basis.com) From majordomo-workers-owner Tue Aug 22 15:00:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA15127 for majordomo-workers-outgoing; Tue, 22 Aug 1995 14:52:41 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA15054 for ; Tue, 22 Aug 1995 14:52:27 -0700 Received: from aix.wingra.com(192.101.144.86) by miles via smap (V1.3) id sma014840; Tue Aug 22 14:51:46 1995 Received: by aix.wingra.com (AIX 3.2/UCB 5.64/4.03) id AA24263; Tue, 22 Aug 1995 16:50:38 -0500 From: miller@aix.wingra.com (Steven M. Miller) Message-Id: <9508221650.ZM29637@aix.wingra.com> Date: Tue, 22 Aug 1995 16:50:37 -0500 X-Mailer: Z-Mail (3.2.1 10apr95) To: majordomo-workers@greatcircle.com Subject: Bug in restrict_post in 1.93 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk If restrict_post is set and mungedomain is set then users whose mail address is a source route address cannot post. I have hacked my local copy to skip the mungedomain checks if the 'split' returns more than 2 parts. -Steve -- Steven 'we're liquidating the kennel' Miller is miller@wingra.com From majordomo-workers-owner Wed Aug 23 10:00:37 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA01405 for majordomo-workers-outgoing; Wed, 23 Aug 1995 09:58:59 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA01358 for ; Wed, 23 Aug 1995 09:58:51 -0700 Received: from internet.goodyear.com(134.200.12.2) by miles via smap (V1.3) id sma001349; Wed Aug 23 09:58:23 1995 Received: from rdsrv2 (rdsrv2.goodyear.com) by goodyear.com (4.1/SMI-4.1) id AA25716; Wed, 23 Aug 95 09:03:05 EDT Received: from rds1146 by rdsrv2 (4.1/SMI-4.1) id AA19860; Wed, 23 Aug 95 09:03:05 EDT Message-Id: <9508231303.AA19860@rdsrv2> Received: by rds1146 (1.37.109.15/16.2) id AA055712738; Wed, 23 Aug 1995 08:58:58 -0400 Date: Wed, 23 Aug 1995 08:58:58 -0400 From: Deborah Johnson Apparently-To: majordomo-workers@greatcircle.com Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk  From majordomo-workers-owner Wed Aug 23 10:02:17 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA01409 for majordomo-workers-outgoing; Wed, 23 Aug 1995 09:58:59 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA01357 for ; Wed, 23 Aug 1995 09:58:51 -0700 Received: from internet.goodyear.com(134.200.12.2) by miles via smap (V1.3) id sma001345; Wed Aug 23 09:58:18 1995 Received: from rdsrv2 (rdsrv2.goodyear.com) by goodyear.com (4.1/SMI-4.1) id AA29919; Wed, 23 Aug 95 12:44:15 EDT Received: from rds1146 by rdsrv2 (4.1/SMI-4.1) id AA01637; Wed, 23 Aug 95 12:44:14 EDT Message-Id: <9508231644.AA01637@rdsrv2> Received: by rds1146 (1.37.109.15/16.2) id AA060196007; Wed, 23 Aug 1995 12:40:07 -0400 Date: Wed, 23 Aug 1995 12:40:07 -0400 From: Deborah Johnson Apparently-To: majordomo-workers@greatcircle.com Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk   From majordomo-workers-owner Wed Aug 23 16:30:49 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA00958 for majordomo-workers-outgoing; Wed, 23 Aug 1995 16:08:21 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA00635 for ; Wed, 23 Aug 1995 16:07:41 -0700 Received: from mycroft.greatcircle.com(198.102.244.35) by miles via smap (V1.3) id smai00581; Wed Aug 23 16:07:02 1995 Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-950602) id OAA11835; Wed, 23 Aug 1995 14:22:44 -0700 Received: from internet.goodyear.com(134.200.12.2) by mycroft via smap (V1.3mjr) id sma011833; Wed Aug 23 14:22:13 1995 Received: from rdsrv2 (rdsrv2.goodyear.com) by goodyear.com (4.1/SMI-4.1) id AA01151; Wed, 23 Aug 95 14:54:15 EDT Received: from rds1146 by rdsrv2 (4.1/SMI-4.1) id AA09085; Wed, 23 Aug 95 14:54:15 EDT Message-Id: <9508231854.AA09085@rdsrv2> Received: by rds1146 (1.37.109.15/16.2) id AA062603808; Wed, 23 Aug 1995 14:50:08 -0400 From: Deborah Johnson Subject: Majordomo results: Presentation Graphics (fwd) To: majordomo-workers@greatcircle.com Date: Wed, 23 Aug 95 14:50:08 EDT" Mailer: Elm [revision: 70.85] Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Please don't flame me for this! Does anyone have any nice Presentation Overheads online that they could send me. I have to give a presentation to our research organization in a couple of weeks. I can probably use any type of graphics charts (ie post- script, GDF, PowerPoint, etc). I appreciate any help. dljohnson@goodyear.com From majordomo-workers-owner Wed Aug 23 20:30:16 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id UAA04280 for majordomo-workers-outgoing; Wed, 23 Aug 1995 20:04:04 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id TAA03584 for ; Wed, 23 Aug 1995 19:38:42 -0700 Received: from mycroft.greatcircle.com(198.102.244.35) by miles via smap (V1.3) id smajb3093; Wed Aug 23 19:37:52 1995 Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-950602) id RAA12461; Wed, 23 Aug 1995 17:00:55 -0700 Received: from unknown(194.59.182.1) by mycroft via smap (V1.3mjr) id sma012456; Wed Aug 23 17:00:16 1995 Received: from GI020X.goethe.de ([193.174.244.2]) by newton.Space.NET with SMTP id <82495-1>; Wed, 23 Aug 1995 12:00:46 +0200 Received: from gi011l.goethe.de by GI020X.goethe.de; (5.65/1.1.8.2/22Mar95-0153PM) id AA22433; Wed, 23 Aug 1995 12:01:36 +0200 Received: by GI011L.GOETHE.DE (MX V4.1 VAX) id 1; Wed, 23 Aug 1995 12:00:56 +0200 Date: Wed, 23 Aug 1995 12:00:56 +0200 From: reisacher@goethe.de To: X-Vmsmail-To: GI011L::MX%"majordomo-workers@greatcircle.com" Message-Id: <009954D8.912DD720.1@GI011L.GOETHE.DE> Subject: Memory fault V1.93 (more detailed) Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hi, i still have this Memory fault. (Now it's more detailed) # uname -a OSF1 GI020X.goethe.de V3.0 358.78 alpha # # echo help | /usr/lib/sendmail -v deutschstunde deutschstunde... aliased to "|/rz1c/majordomo/wrapper resend -p bulk -M 10000 -l deut schstunde deutschstunde-owner -h mail.goethe.de -s deutschstunde-outgoing" "|/rz1c/majordomo/wrapper resend -p bulk -M 10000 -l deutschstunde deutschstunde-owner -h mail.goethe.de -s deutschstunde-outgoing"... Connecting to (prog)... about to exec Unaligned access pid=21960 va=206432302520732d pc=12006b6dc ra=12001c774 type=ldq sh: 21960 Memory fault "|/rz1c/majordomo/wrapper resend -p bulk -M 10000 -l deutschstunde deutschstunde-owner -h mail.goethe.de -s deutschstunde-outgoing"... unknown mailer error 139 owner-deutschstunde... aliased to deutschstunde-owner deutschstunde-owner... aliased to reisacher reisacher... aliased to Z8222%A1MBX_GI011L.GI014R.mrgate@gi011l.goethe.de Z8222%A1MBX_GI011L.GI014R.mrgate@gi011l.goethe.de... Connecting to gi011l.goethe.de (smtpl)... 220 GI011L.GOETHE.DE MX V4.1 VAX SMTP server ready at Wed, 23 Aug 1995 10:15:57 +0200 >>> HELO GI020X.goethe.de 250 Hello, GI020X.goethe.de >>> MAIL From: 250 MAIL command accepted. >>> RCPT To: 250 Recipient okay (at least in form) >>> DATA 354 Start mail input; end with . >>> . 250 Message received and queued. >>> QUIT 221 GI011L.GOETHE.DE Service closing transmission channel Z8222%A1MBX_GI011L.GI014R.mrgate@gi011l.goethe.de... Sent David Wolfe wrotes to me: >Wrapper should be owned by root and installed setuid. Installing wrapper >setuid root is necessary for wrapper to be able to change the r/euid to >majordom when run as another user from sendmail. This was done. What to do now? _______________________________________________________________ | Georg Reisacher, Goethe-Institut Munic, System+Network Mgmt. | | D 80637 Muenchen, Helene-Weber-Allee 1 | /) Phone: +49 89 15921-399 ! FAX: +49 89 15921-435 (\ / ) Internet: reisacher@goethe.de ! WWW: http://www.goethe.de ( \ _( (|________________________________________________________________) ) /> (((\ \) /,) / ) / //))/ (\\\\ \_/ / \ \_/ ///// \ / \ / \ _/ \_ / From majordomo-workers-owner Thu Aug 24 21:02:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id UAA03607 for majordomo-workers-outgoing; Thu, 24 Aug 1995 20:29:43 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id UAA03281 for ; Thu, 24 Aug 1995 20:29:03 -0700 Received: from mycroft.greatcircle.com(198.102.244.35) by miles via smap (V1.3) id sma003152; Thu Aug 24 20:28:02 1995 Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-950602) id UAA20009; Thu, 24 Aug 1995 20:19:27 -0700 Received: from lunch.engr.sgi.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for <@sgi.sgi.com:majordomo-workers@greatcircle.com> id KAA14779; Thu, 24 Aug 1995 10:52:33 -0700 Received: by lunch.engr.sgi.com (950413.SGI.8.6.12/911001.SGI) for majordomo-workers@greatcircle.com id KAA21564; Thu, 24 Aug 1995 10:52:32 -0700 From: pdc@lunch.engr.sgi.com (Paul Close) Message-Id: <199508241752.KAA21564@lunch.engr.sgi.com> Subject: mysterious behavior! To: majordomo-workers@greatcircle.com (Majordomo Workers list) Date: Thu, 24 Aug 1995 10:52:30 -0700 (PDT) X-Mailer: ELM [version 2.5 PL0a5] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1561 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk The other day, I noticed the following post to a list I run. I was very surprised, because I filter out admin messages: ========== From owner-bass Sun Aug 20 20:20:27 1995 Received: by lunch.engr.sgi.com (950413.SGI.8.6.12/911001.SGI) id UAA25151; Sun, 20 Aug 1995 20:19:53 -0700 Sender: owner-bass Precedence: bulk Reply-To: bass@lunch.engr.sgi.com.id.m0skNNY-0003gAC;Mon, 21.Aug.95.13:18.EST Message-Id: From: rjl@gondwana.admin.aw.latrobe.edu.au (Richard Lindner) To: bass-digest Date: Mon, 21 Aug 1995 13:18:24 +1000 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 167 subscribe -- Richard Lindner PO Box 1555, Wodonga, Vic. 3689, Oz rjl@gondwana.admin.aw.latrobe.edu.au Ph: 060 562072 (bh) 060 208813 (ah) ========== Aside from the obvious peculiarity that an obvious admin request got through, check out the Reply-To field! I have a reply-to address set in the config file (bass@lunch.engr.sgi.com), and I can't imagine what would go wrong to cause the reply-to that's present! And just to check my sanity, I piped the address through resend with debug, and it got trapped, just as it should have. Unfortunately, I do not have the original.... Any ideas? Could sendmail have munged my message? Even so, I don't see how subscribe got through! -- Paul Close pdc@sgi.com http://reality.sgi.com/employees/pdc/ No fate but what we make From majordomo-workers-owner Fri Aug 25 10:01:17 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA09402 for majordomo-workers-outgoing; Fri, 25 Aug 1995 09:34:27 -0700 Received: (smap@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA09220; Fri, 25 Aug 1995 09:34:02 -0700 Received: from spsgate.sps.mot.com(192.70.231.1) by miles via smap (V1.3) id sma009207; Fri Aug 25 09:33:21 1995 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA22820 for majordomo-users@greatcircle.com; Fri, 25 Aug 95 09:08:15 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA15103; Fri, 25 Aug 95 09:08:14 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA24663 for majordomo-users@greatcircle.com; Fri, 25 Aug 95 09:08:11 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA10489; Fri, 25 Aug 95 11:08:09 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA19923; Fri, 25 Aug 1995 11:08:07 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9508251608.AA19923@miaow.sps.mot.com> Subject: Truncated messages on MS-Mail To: majordomo-workers@greatcircle.com (Majordomo developer's mailing list) Date: Fri, 25 Aug 1995 11:08:07 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1521 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk This might be old news, but it was new to me, so I thought I'd pass it along for general information. We have Windows NT systems on our network and the resulting Microsoft Mail users. Since MS-Mail has a problem with correctly resolving the original sender of Majordomo mailing list messages, we added message "fronters" to identify the original sender and mailing list. However, we soon discovered that messages that originated from MS-Mail to such a Mj list (with fronters) and were subsequently received by MS-Mail had trailing lines missing (the same number of lines as were added for fronters...duh). The same message received elsewhere (e.g. Unix) was complete, as were messages originating elsewhere. I tracked the problem down to an Encoding header that specifies the number of lines in the original message. Of course the solution was simply to drop the header in resend. Here's my patch against 1.93: --- resend 1995/08/23 17:45:48 *************** *** 193,198 **** --- 193,199 ---- || /^return-receipt-to:/i || /^errors-to:/i || /^return-path:/i + || /^encoding:/i || (/^reply-to:/i && defined($opt_r)) # skip only if "-r" set || (/^precedence:/i && defined($opt_p)) # skip only if "-p" set || (/^received:/i && defined($opt_R)) # skip only if "-R" set -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-workers-owner Mon Aug 28 08:21:27 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA01964 for majordomo-workers-outgoing; Mon, 28 Aug 1995 08:15:03 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA01939; Mon, 28 Aug 1995 08:14:47 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA09937 for majordomo-workers@greatcircle.com; Mon, 28 Aug 95 08:13:20 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA02779; Mon, 28 Aug 95 08:13:19 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA22833 for majordomo-workers@greatcircle.com; Mon, 28 Aug 95 08:13:17 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA19776; Mon, 28 Aug 95 10:13:14 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA11618; Mon, 28 Aug 1995 10:13:10 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9508281513.AA11618@miaow.sps.mot.com> Subject: Re: Can't stat . To: peter@i3.informatik.rwth-aachen.de (Peter Heimann) Date: Mon, 28 Aug 1995 10:13:10 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list), majordomo-workers@greatcircle.com (Majordomo developer's mailing list) In-Reply-To: <9508281431.AA04438@grieg.informatik.rwth-aachen.de.informatik.rwth-aachen.de> from "Peter Heimann" at Aug 28, 95 04:31:40 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1660 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ Peter Heimann writes: ] > > On the majordomo-users list, you write > > > I put some diagnostic prints in majordomo.cf to verify that $listdir > > is defined at that point and to check what `pwd` returned (nothing, > > undefined, but generates another "can't stat ." message). The problem > > seems to be that perl has no current directory when started via > > sendmail. > > I would guess: it has a current directory, inherited from the sendmail > process, but this directory is not readable to the majordomo user. > This results in pwd's "can't stat ." message. Of course! I was overlooking the obvious. It's not that there's no current directory, archive2.pl just doesn't have permission to read it (and the shell invoked by the glob wants to know where it is as part of its initialization). I guess I was assuming that wrapper handled that. Since a lot of the Mj scripts do chdir($homedir) anyway, I suggest that it be added to wrapper.c just before the exec. It looks like the immediate fix for my problem is to add a chdir($ENV{'HOME'}) to archive2.pl: *** archive2.pl.orig Wed Mar 1 08:43:29 1995 --- archive2.pl Mon Aug 28 10:09:52 1995 *************** *** 46,51 **** --- 46,54 ---- # come along in the 1.91 patch I guess. $main'program_name = 'mj_archive'; + # Change directory to our home + chdir($ENV{'HOME'}) if $ENV{'HOME'}; + # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; if ($ARGV[0] eq "-C") { Thanks to all who responded, especially to Peter. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-workers-owner Mon Aug 28 16:00:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA00532 for majordomo-workers-outgoing; Mon, 28 Aug 1995 15:55:42 -0700 Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id PAA00524 for ; Mon, 28 Aug 1995 15:55:34 -0700 Received: from lunch.engr.sgi.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for <@sgi.sgi.com:majordomo-workers@greatcircle.com> id PAA18877; Mon, 28 Aug 1995 15:54:07 -0700 Received: by lunch.engr.sgi.com (950413.SGI.8.6.12/911001.SGI) for majordomo-workers@greatcircle.com id PAA22967; Mon, 28 Aug 1995 15:53:20 -0700 From: pdc@lunch.engr.sgi.com (Paul Close) Message-Id: <199508282253.PAA22967@lunch.engr.sgi.com> Subject: bug in resend To: majordomo-workers@greatcircle.com (Majordomo Workers list) Date: Mon, 28 Aug 1995 15:53:18 -0700 (PDT) X-Mailer: ELM [version 2.5 PL0a6] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1811 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk "Thanks" to some bizzare headers from one site, I found an obscure bug in majorodomo. The problem is the cause of my last post, where I noticed some posting had snuck past the admin filter. The problem is caused by headers like this: Received: by gondwana.admin.aw.latrobe.edu.au (Linux Smail3.1.28.1 #10) id m0snChR-0003evC; Tue, 29 Aug 95 08:30 EST Majordomo mistakenly views the blank line as the end of headers, but it's not completely empty (there are spaces), so it's really just a continuation. Since sendmail sees it as a continuation, and majordomo thinks that the body follows, things get really messed up!! The combination results in Reply-To: bass@lunch.engr.sgi.com (all blanks) id m0snChR-0003evC; Tue, 29 Aug 95 08:30 EST which sendmail converts into: Reply-To: bass@lunch.engr.sgi.com.id.m0smyTd-0003UEC;Mon, 29.Aug.95.08:30.EST The solution is simple. Change: if ($in_hdr) { if (/^\s*$/) { # end of header; add new header fields to: if ($in_hdr) { if (/^$/) { # end of header; add new header fields I've looked at RFC 822, and it says pretty specifically that "[the body] is separated from the headers by a null line (i.e., a line with nothing preceding the CRLF)", and also that anywhere whitespace is allowed, CR plus whitespace is allowed (paraphrased). The actual text reads: The general rule is that wherever there may be linear-white-space (NOT simply LWSP-chars), a CRLF immediately followed by AT LEAST one LWSP-char may instead be inserted. This doesn't seem to prohibit a CR + whitespace + CR + whitespace combination. -- Paul Close pdc@sgi.com http://reality.sgi.com/employees/pdc/ No fate but what we make From majordomo-workers-owner Tue Aug 29 09:51:47 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA06321 for majordomo-workers-outgoing; Tue, 29 Aug 1995 09:31:47 -0700 Received: from goodyear.com (internet.goodyear.com [134.200.12.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA06299 for ; Tue, 29 Aug 1995 09:31:41 -0700 Received: from rdsrv2 (rdsrv2.goodyear.com) by goodyear.com (4.1/SMI-4.1) id AA25508; Tue, 29 Aug 95 12:30:15 EDT Received: from rds1146 by rdsrv2 (4.1/SMI-4.1) id AA28616; Tue, 29 Aug 95 12:30:14 EDT Message-Id: <9508291630.AA28616@rdsrv2> Received: by rds1146 (1.37.109.15/16.2) id AA245173568; Tue, 29 Aug 1995 12:26:08 -0400 From: Deborah Johnson Subject: mysterious behavior! (fwd) To: majordomo-workers@greatcircle.com Date: Tue, 29 Aug 95 12:26:08 EDT" Mailer: Elm [revision: 70.85] Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I had a similar experience, when I first set up a list. I set up the list and did a request to generate the .config file. THEN I added the .closed file without changing the subscription policy in the .config file (didn't realize it needed to be added) . As long as the requests were formatted: subscribe it worked as a closed list (that is, subscription requests were sent to the owner). But when I had a co-worker try to subscribe she just sent the subscribe message, and sure enough, it auto subscribed her. I have not gotten through all the code yet to see where the problem is, but apparently it checks different things depending on how the request is done. So, check your .config file to make sure your subscription policy is set to closed. > > The other day, I noticed the following post to a list I run. I was very > surprised, because I filter out admin messages: > > ========== > > >From owner-bass Sun Aug 20 20:20:27 1995 > Received: by lunch.engr.sgi.com (950413.SGI.8.6.12/911001.SGI) > id UAA25151; Sun, 20 Aug 1995 20:19:53 -0700 > Sender: owner-bass > Precedence: bulk > Reply-To: bass@lunch.engr.sgi.com.id.m0skNNY-0003gAC;Mon, 21.Aug.95.13:18.EST > Message-Id: > From: rjl@gondwana.admin.aw.latrobe.edu.au (Richard Lindner) > To: bass-digest > Date: Mon, 21 Aug 1995 13:18:24 +1000 (EST) > X-Mailer: ELM [version 2.4 PL24] > MIME-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > Content-Length: 167 > > subscribe > > -- > Richard Lindner PO Box 1555, Wodonga, Vic. 3689, Oz > rjl@gondwana.admin.aw.latrobe.edu.au Ph: 060 562072 (bh) 060 208813 (ah) > > ========== > > Aside from the obvious peculiarity that an obvious admin request got > through, check out the Reply-To field! I have a reply-to address set > in the config file (bass@lunch.engr.sgi.com), and I can't imagine what > would go wrong to cause the reply-to that's present! And just to check > my sanity, I piped the address through resend with debug, and it got > trapped, just as it should have. > > Unfortunately, I do not have the original.... Any ideas? Could sendmail > have munged my message? Even so, I don't see how subscribe got through! > -- > Paul Close pdc@sgi.com http://reality.sgi.com/employees/pdc/ > > No fate but what we make > From majordomo-workers-owner Tue Aug 29 10:21:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA07868 for majordomo-workers-outgoing; Tue, 29 Aug 1995 10:11:26 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA07849 for ; Tue, 29 Aug 1995 10:11:17 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA22472 for majordomo-workers@greatcircle.com; Tue, 29 Aug 95 10:09:41 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA00558; Tue, 29 Aug 95 10:09:40 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA02516 for majordomo-workers@greatcircle.com; Tue, 29 Aug 95 10:09:39 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA00679; Tue, 29 Aug 95 12:09:37 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA11627; Tue, 29 Aug 1995 12:09:36 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9508291709.AA11627@miaow.sps.mot.com> Subject: Re: mysterious behavior! (fwd) To: uunet!goodyear.com!dljohnson (Deborah Johnson) Date: Tue, 29 Aug 1995 12:09:35 -0500 (CDT) Cc: majordomo-workers@greatcircle.com (Majordomo developer's mailing list) In-Reply-To: <9508291630.AA28616@rdsrv2> from "Deborah Johnson" at Aug 29, 95 12:26:08 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1226 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ Deborah Johnson writes: ] > > I had a similar experience, when I first set up a list. I set up the list > and did a request to generate the .config file. THEN I added the .closed file > without changing the subscription policy in the .config file (didn't realize > it needed to be added) . As long as the requests were formatted: > > subscribe > > it worked as a closed list (that is, subscription requests were sent to the > owner). But when I had a co-worker try to subscribe she just sent > the > > subscribe > > message, and sure enough, it auto subscribed her. > > I have not gotten through all the code yet to see where the problem is, but > apparently it checks different things depending on how the request is done. Nothing mysterious here. The settings in the list.config file override command line options and file options (list.passwd is a different situation); see get_config in config_parse.pl. The "subscribe " requests were sent to the list owner because the "" apparently didn't match the headers on the message. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-workers-owner Wed Aug 30 13:30:56 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA08063 for majordomo-workers-outgoing; Wed, 30 Aug 1995 13:12:33 -0700 Received: from atc.boeing.com (atc.boeing.com [130.42.28.80]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA08056 for ; Wed, 30 Aug 1995 13:12:30 -0700 Received: by atc.boeing.com (5.65/splinter.boeing.com) id AA20626; Wed, 30 Aug 1995 13:13:37 -0700 Received: from aw102 (aw102.iasl.ca.boeing.com) by aw101.iasl.ca.boeing.com with SMTP id AA16054 (5.67a/IDA-1.4.4 for ); Wed, 30 Aug 1995 13:11:05 -0700 From: "Vincent D. Skahan" Received: by aw102 (5.65c/client-1.3) id AA10651; Wed, 30 Aug 1995 13:11:03 -0700 Message-Id: <199508302011.AA10651@aw102> Subject: Is there still majordomo 1.94 or 2.00 development being done ? To: majordomo-workers@greatcircle.com Date: Wed, 30 Aug 1995 13:11:02 -0700 (PDT) X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 1053 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [...the following is NOT any type of complaint or flame...] I'm looking to set my expectations in tune with reality since I know that most of us have 'real jobs' that take priority. Many of us are now dependent on majordomo and maybe an authoritative status message regarding who's carrying the ball and where development is at would be helpful. It sure seems that there are lots'o folks finding lots'o bugs and developing lots'o features and posting individual fixes for majordomo 1.93 that might need rolling into the official distribution. Is there still official majordomo development and a development coordinator? Will there be a version 1.9x that rolls up all the fixes/features that people have posted ? Is version 2.00 imminent, real-soon-now, no-clue-if-in-my-lifetime ? -- ----------- Vince Skahan ------ vds7789@aw101.iasl.ca.boeing.com ----------- Nobody over the age of 35 should be permitted to try to stretch a double into a triple (unless you're talking alcohol or caffeine). - me after tearing ligaments (ouch!) From majordomo-workers-owner Wed Aug 30 17:01:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA22161 for majordomo-workers-outgoing; Wed, 30 Aug 1995 16:44:12 -0700 Received: from [198.102.244.40] (pm-ppp-2.greatcircle.com [198.102.244.40]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id QAA22144; Wed, 30 Aug 1995 16:44:02 -0700 X-Sender: brent@miles.greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 30 Aug 1995 19:43:13 -0400 To: "Vincent D. Skahan" , majordomo-workers@greatcircle.com From: Brent@GreatCircle.COM (Brent Chapman) Subject: Re: Is there still majordomo 1.94 or 2.00 development being done ? Cc: cwilson@engr.sgi.com Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk At 1:11 PM 8/30/95, Vincent D. Skahan wrote: >[...the following is NOT any type of complaint or flame...] > >I'm looking to set my expectations in tune with reality since I know that >most of us have 'real jobs' that take priority. > >Many of us are now dependent on majordomo and maybe an authoritative status >message regarding who's carrying the ball and where development is at would >be helpful. > >It sure seems that there are lots'o folks finding lots'o bugs and developing >lots'o features and posting individual fixes for majordomo 1.93 that might >need rolling into the official distribution. > >Is there still official majordomo development and a development coordinator? Funny you should ask... :-) A couple of weeks ago, I exchanged email with John Rouillard and had lunch with Chan Wilson to discuss this very issue. Basicly, the situation is this: I'm completely swamped with other projects, John is completely swamped with other projects, and Chan has tentatively agreed to take over as the new Majordomo release coordinator. We certainly appreciate all the work John has done, but he thinks its time to turn the reigns over to somebody else (just as I turned them over to him, some time ago). However, Chan is moving from the USA to SGI's manufacturing site in Switzerland next month, and probably won't be able to do much before he gets there and gets settled in (late September or early October, say); once in Switzerland, he actually expects to have more time for Majordomo-related stuff than he does in his current job in Mountain View. >Will there be a version 1.9x that rolls up all the fixes/features that people >have posted ? Chan and I discussed this when we met. We both want to get a 1.94 release out as soon as we can, incorporating bug fixes and straightforward feature additions (basically, stuff that's already been implemented and posted here, like my "taboo" patches and various patches from other folks). Chan was _hoping_ to get that out the door before he dropped off the net for a month to move to Switzerland, but I'm not sure he's going to have enough time; he's awful busy getting things wrapped up here and ready to move. One stumbling block is that neither of us is sure we have a complete set of the patches folks have submitted. We could go back through the archives to find them, but we'd have to sift through a lot of other messages, and we really don't have time. I'll let Chan comment on how he wants to handle this, but I suspect that we may ask folks to resend patches (using the released version of 1.93 as a base) to us for consideration and potential inclusion (DON'T send us any yet, though). I suspect that Chan will probably want to pick only a handful of "major" patches to apply; the more parallel patches you apply, the harder it gets to apply further patches, as the code diverges from what the patches were diff'd against. The more we try to fit in, the longer it's going to take to get it out the door. >Is version 2.00 imminent, real-soon-now, no-clue-if-in-my-lifetime ? I'd say it's on indefinite hold, at least in the form designed and outlined by John. It's a pretty ambitious project, and nobody has time to undertake it right now. We'll probably release _something_ called "2.0" somewhere down the road, but it will probably be much more modest than what John has outlined on this list. -Brent -- Brent Chapman | Great Circle Associates | For Firewalls Tutorial info: Brent@GreatCircle.COM | 1057 West Dana Street | Tutorial-Info@GreatCircle.COM +1 415 962 0841 | Mountain View, CA 94041 | http://www.greatcircle.com From majordomo-workers-owner Wed Aug 30 17:30:47 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id RAA23894 for majordomo-workers-outgoing; Wed, 30 Aug 1995 17:12:57 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id RAA23887 for ; Wed, 30 Aug 1995 17:12:53 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA12879 (5.65c/IDA-1.4.4 for ); Wed, 30 Aug 1995 20:11:36 -0400 Message-Id: <199508310011.AA12879@cs.umb.edu> To: "Vincent D. Skahan" Cc: majordomo-workers@greatcircle.com Subject: Re: Is there still majordomo 1.94 or 2.00 development being done ? In-Reply-To: Your message of "Wed, 30 Aug 1995 13:11:02 PDT." <199508302011.AA10651@aw102> Date: Wed, 30 Aug 1995 20:10:40 -0400 From: "John P. Rouillard" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Since I will be leaving soon, I am trying to find a replacement to handle future majordomo releases. My intended victim (um person) is Chan Wilson, but I don't know precisely what he is up to at the moment. I know Brent and he had a meeting, but I wasn't privy to the discussion. I will let Chan or Brent handle future discussion on this. -- John =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-workers-owner Wed Aug 30 18:00:12 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id RAA25242 for majordomo-workers-outgoing; Wed, 30 Aug 1995 17:56:39 -0700 Received: from j51.com (j51.com [199.224.7.51]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id RAA25228 for ; Wed, 30 Aug 1995 17:56:35 -0700 Received: from pm4.j51.com (pm4.j51.com [199.224.7.228]) by j51.com (8.6.12/8.6.9) with SMTP id AAA01493 for ; Thu, 31 Aug 1995 00:55:35 GMT Message-Id: <199508310055.AAA01493@j51.com> X-Sender: genesis@j51.com X-Mailer: Windows Eudora Version 2.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 30 Aug 1995 20:49:46 -0400 To: majordomo-workers@greatcircle.com From: Project Genesis Subject: Re: Is there still majordomo 1.94 or 2.00 development being done ? Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I can only say that any news of upcoming development... is good news. I'm new to majordomo, but I've been running several lists for a while and hope to be helpful developing patches and additions. I hope the plans currently on board include the anon-who and anon-which patches that I just received - for those running moderated lists, it is often worthwhile to make it impossible for others to simply get a copy of any list's recipients, and spam them... Ken Menken genesis@j51.com From majordomo-workers-owner Wed Aug 30 18:30:02 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA25701 for majordomo-workers-outgoing; Wed, 30 Aug 1995 18:05:52 -0700 Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id SAA25692; Wed, 30 Aug 1995 18:05:49 -0700 Received: from snarf.engr.sgi.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id SAA08889; Wed, 30 Aug 1995 18:04:14 -0700 Received: from localhost by snarf.engr.sgi.com via SMTP (940816.SGI.8.6.9/911001.SGI) id SAA07861; Wed, 30 Aug 1995 18:04:07 -0700 Message-Id: <199508310104.SAA07861@snarf.engr.sgi.com> To: Brent@GreatCircle.COM (Brent Chapman) cc: "Vincent D. Skahan" , majordomo-workers@GreatCircle.COM Subject: Re: Is there still majordomo 1.94 or 2.00 development being done ? In-reply-to: Your message of "Wed, 30 Aug 1995 19:43:13 EDT." Date: Wed, 30 Aug 1995 18:04:06 -0700 From: Chan Wilson Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk > Basicly, the situation is this: I'm completely swamped with other projects, > John is completely swamped with other projects, and Chan has tentatively > agreed to take over as the new Majordomo release coordinator. We certainly > appreciate all the work John has done, but he thinks its time to turn the > reigns over to somebody else (just as I turned them over to him, some time > ago). Ah yes, swamped is the name of the game... the life of a Sys Admin. Fortunately, I'm about to become a "Network Analyst", which is almost as good a title, and since my Mission will be "WAN Stuff", I'm making majordomo part of that. > One stumbling block is that neither of us is sure we have a complete set of > the patches folks have submitted. We could go back through the archives to > find them, but we'd have to sift through a lot of other messages, and we > really don't have time. I'll let Chan comment on how he wants to handle Arbitrarilly going back to mid June, I see the following useful patches I've squirrled away in my +majordomo folder: main'log can be called infinitely. From: "SethMeister G." request-answer busted (main'lopen unknown, do_exec_sendmail mismatch) From: Majordomo maintenance account taboo-headers patch (the olga special) From: Brent Chapman ( & friends ) drop Encoding: header for msmail From: dwolfe@risc.sps.mot.com (Dave Wolfe) archive2.pl doesn't do a chdir From: dwolfe@risc.sps.mot.com (Dave Wolfe) resend buglet in received headers From: pdc@lunch (Paul Close) Are there other fixes that should be rolled into a 1.94 release? I don't want new features for 1.94, but rather a consolidation of the potpourri of fixes since 1.93. I'll make a strong effort to get something ready for testing before I'm off the air Sept 15 - Oct 1... --Chan From majordomo-workers-owner Thu Aug 31 02:00:27 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id BAA07151 for majordomo-workers-outgoing; Thu, 31 Aug 1995 01:34:47 -0700 Received: from isp1.isp.net (isp1.isp.net [204.139.9.12]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id BAA07144 for ; Thu, 31 Aug 1995 01:34:42 -0700 Received: from outsider.bolis.sf-bay.org ([204.153.195.10]) by mail.isp.net (8.6.9/8.6.9) with SMTP id BAA04688 for ; Thu, 31 Aug 1995 01:32:00 -0700 Received: from hock.bolis.sf-bay.org by outsider.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0so4v4-0006vJC; Thu, 31 Aug 95 01:24 PDT Received: from amillar by hock.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0so4vq-000UpuC; Thu, 31 Aug 95 01:25 PDT Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: majordomo-workers@GreatCircle.COM Date: Thu, 31 Aug 1995 00:19:47 -800 Subject: Re: Is there still majordomo 1.94 or 2.00 development being Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk > Are there other fixes that should be rolled into a 1.94 release? I > don't want new features for 1.94, but rather a consolidation of the > potpourri of fixes since 1.93. There was also a patch to check the return status of all "close" calls. This fixed the disappearing list problem for me. I picked it up from a re-posting in the last few months; I don't remember it being in the 1.93 release. On a related note- John: did you ever send out a patch for unsubscribe where you replaced the entry with a filler instead of rewriting the entire list? I remember you mentioning it, but I didn't remember seeing any code. - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: http://metro.turnpike.net/metro/amillar From majordomo-workers-owner Thu Aug 31 06:30:33 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA12771 for majordomo-workers-outgoing; Thu, 31 Aug 1995 06:25:19 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA12758 for ; Thu, 31 Aug 1995 06:25:16 -0700 Received: from se.cs.umb.edu by cs.umb.edu with SMTP id AA00813 (5.65c/IDA-1.4.4 for ); Thu, 31 Aug 1995 09:23:55 -0400 Message-Id: <199508311323.AA00813@cs.umb.edu> To: "Alan Millar" Cc: majordomo-workers@greatcircle.com Subject: Re: Is there still majordomo 1.94 or 2.00 development being In-Reply-To: Your message of "Thu, 31 Aug 1995 00:19:47." Date: Thu, 31 Aug 1995 09:24:37 -0400 From: "John P. Rouillard" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk No. I never got to coding that. Its one of the reasons I decided to give up majordomo. In message , "Alan Millar" writes: >> Are there other fixes that should be rolled into a 1.94 release? I >> don't want new features for 1.94, but rather a consolidation of the >> potpourri of fixes since 1.93. > >There was also a patch to check the return status of all "close" >calls. This fixed the disappearing list problem for me. I picked it >up from a re-posting in the last few months; I don't remember it >being in the 1.93 release. > >On a related note- John: did you ever send out a patch for >unsubscribe where you replaced the entry with a filler instead of >rewriting the entire list? I remember you mentioning it, but I >didn't remember seeing any code. > >- Alan >---- >Alan Millar E-Mail: amillar@bolis.SF-Bay.org >System Administrator Web: http://metro.turnpike.net/metro/amillar From majordomo-workers-owner Thu Aug 31 09:11:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA19374 for majordomo-workers-outgoing; Thu, 31 Aug 1995 08:59:59 -0700 Received: from journal.biology.carleton.ca (spiff.ccs.carleton.ca [134.117.32.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA19367 for ; Thu, 31 Aug 1995 08:59:55 -0700 Received: by journal.biology.carleton.ca (4.1/SMI-4.0-cmh) id AA17317; Thu, 31 Aug 95 11:58:36 EDT From: cmh@spiff.ccs.carleton.ca (Colin Henein) Message-Id: <9508311558.AA17317@journal.biology.carleton.ca> Subject: listdir gets huge... To: majordomo-workers@greatcircle.com Date: Thu, 31 Aug 1995 11:58:35 -0400 (EDT) X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1230 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I've been running a hacked up version of Majordomo for some time now, that has a full directory tree rooted at the listdir. Each list has its own directory, so for example my mailing list "orange-carb" is set up as follows: my way majordomo way $listdir/orange-carb/members $listdir/orange-carb.members $listdir/orange-carb/passwd $listdir/orange-carb.passwd $listdir/orange-carb/info $listdir/orange-carb.info etc... Its an old version 1.60 majordomo. I've resisted upgrading it because I really like the "neat-and-tidiness" of this rooted directory structure, and it would be a pain to hack it back in (mcr on this list originally did it when he was working on this project) If people are interested I'd patch a clean distribution of 1.93 to allow a $separate_char variable that could be set to "." for traditional operation or "/" for tree operation. Would people be willing to include such a patch in the famous 1.94 patch release? Colin -- =================================+================================= Colin Henein (Code guy) | 3rd year Computer Science Co-op. cmh@ccs.carleton.ca | Chief Informatics Officer, root@journal.biology.carleton.ca | COBRA (aka. Orange-Carb) From majordomo-workers-owner Thu Aug 31 15:30:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA04224 for majordomo-workers-outgoing; Thu, 31 Aug 1995 15:16:40 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA04197 for ; Thu, 31 Aug 1995 15:16:33 -0700 Received: from se.cs.umb.edu by cs.umb.edu with SMTP id AA09824 (5.65c/IDA-1.4.4 for ); Thu, 31 Aug 1995 18:15:15 -0400 Message-Id: <199508312215.AA09824@cs.umb.edu> To: cmh@spiff.ccs.carleton.ca (Colin Henein) Cc: majordomo-workers@greatcircle.com Subject: Re: listdir gets huge... In-Reply-To: Your message of "Thu, 31 Aug 1995 11:58:35 EDT." <9508311558.AA17317@journal.biology.carleton.ca> Date: Thu, 31 Aug 1995 18:15:57 -0400 From: "John P. Rouillard" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk In message <9508311558.AA17317@journal.biology.carleton.ca>, Colin Henein writes: >I've been running a hacked up version of Majordomo for some time now, >that has a full directory tree rooted at the listdir. Each list has >its own directory, so for example my mailing list "orange-carb" is set >up as follows: > >my way majordomo way >$listdir/orange-carb/members $listdir/orange-carb.members >$listdir/orange-carb/passwd $listdir/orange-carb.passwd >$listdir/orange-carb/info $listdir/orange-carb.info >etc... One problem with this approach is that is prevents you from doing some things like precaching the config files to speed up majordomo startup. In order to tell if your cache is out of date, you would have to stat every file rather than just stating the directory all of the config files reside in. I don't know what the future is for majordomo, but performance issues always seems to be a major one. the main costs of the current majordomo are: 1) loading/parsing lots of config files 2) manipulating large lists of addresses (specifically deleting them) Number 1 can be handled by "precompiling" all of the config files into a single perl array that is kept in a cache file. Then the code to load it runs something like: if (mtime on directory < mtime on cache) { # cache is current since a new cache file is written # on update, and this changes the directory mtime require 'cache.pl'; } else { require 'cache.pl'; for every file in the cache directory { if (mtime of config file > mtime of cache) { eliminate all entries in loaded cache file that deal with that list and load new config file } } write new cache file } I ran a harness around config_parse.pl that implemented the code above versus loading all config files. The cost of loading 128 preparsed config files from a cache was the same as parsing one config file. This was on a sparc 20 64MB of memory 128mb swap solaris 2.3. To load 28 out of date config files took one equivelent load of a config file. (I.E. the time taken to load 28 new config files into the cache file was equivalent to parsing 29 config files originally). These are rough measurements since most of my config file didn't have more than 10 items per array type entry. I really couldn't come up with much in the way of speeding up the config file parsing that didn't make me worry about not doing enough safety checks that might compromise the majordomo host. I did try rewritng the config parser into a lighter weight animal that assumed that the data it was getting was safe (safety parsing was done during the submission of the config file via email), but this only allowed 14 config file loads in the time of 1. -- John =============================================================================== My employers don't acknowledge my existence much less my opinions.