From majordomo-users-owner Tue Mar 1 00:38:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA18184; Tue, 1 Mar 1994 08:28:45 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA16922; Mon, 28 Feb 1994 17:18:42 -0800 Message-Id: <199403010118.RAA16922@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.37.109.4/16.2) id AA22715; Mon, 28 Feb 94 19:18:07 -0600 From: Larry Sheldon Subject: Header Hack needed To: majordomo-users@greatcircle.com Date: Mon, 28 Feb 94 19:18:06 CST Mailer: Elm [revision: 70.85] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We have a large number of customers on Novell servers who use Pegasus through a CHARON gateway. Several of them subscribe to lists I manage, and several of _them_ are madly in love with "delivery confirmation" and "receipt confirmation", so that when they post, every other Pegasus user sends out two confirmations, which every other Pegasus gets (off the list) triggering an avalanche of confirmations. It looks to me like I could put a couple of greps in the alias file to eat up the triggering headers on the way in, but it seems like there is a better way. There always is. Anybody done this yet? I'm sort of afraid to wander into resend by myself--did that some this past weekend with Brent's constant assistance, but still came away from that afraid to go back and find the one last problem. And I have no clue as to where to start on this one. -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . L. F. (Larry) Sheldon, Jr. . - Unix Systems Administration - . Creighton University Computer Center - Old Gym . - 2500 California Plaza - . Omaha, Nebraska, U.S.A. 68178 . - 402 280 2254 lsheldon@creighton.edu - . . - A hundred thousand lemmings can't be wrong. - .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Tue Mar 1 13:04:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA19177; Tue, 1 Mar 1994 13:04:09 GMT Received: from sun2.nsfnet-relay.ac.uk by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA19171; Tue, 1 Mar 1994 05:04:02 -0800 Via: uk.ac.leicester; Tue, 1 Mar 1994 11:24:22 +0000 Received: from lily.le.ac.uk by venus.le.ac.uk with SMTP (PP); Tue, 1 Mar 1994 11:27:27 +0000 Received: from LILY/MAILQUEUE by lily.le.ac.uk (Mercury 1.11); Tue, 1 Mar 94 11:24:28 GMT0BST Received: from MAILQUEUE by LILY (Mercury 1.11); Tue, 1 Mar 94 11:24:09 GMT0BST To: Majordomo-users@greatcircle.com From: "S.A. CHOPDAT" Date: Tue, 1 Mar 1994 11:24:01 GMT0BST Priority: normal X-mailer: WinPMail v1.0 (R2) Message-ID: <4184F234C@lily.le.ac.uk> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk lists which From majordomo-users-owner Tue Mar 1 15:06:59 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA19565; Tue, 1 Mar 1994 15:06:59 GMT Received: from noc1.dccs.upenn.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA19559; Tue, 1 Mar 1994 07:06:52 -0800 Received: from BIBLE.SAS.UPENN.EDU by noc1.dccs.upenn.edu id AA04183; Tue, 1 Mar 94 10:08:40 -0500 Received: by bible.sas.upenn.edu id AA18530; Tue, 1 Mar 94 09:05:39 EST Date: Tue, 1 Mar 94 09:05:39 EST From: schoi@bible.sas.upenn.edu (Sam Choi) Posted-Date: Tue, 1 Mar 94 09:05:39 EST Message-Id: <9403011405.AA18530@bible.sas.upenn.edu > To: majordomo-users@greatcircle.com Subject: listserve problem Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Recently the department has been going crazy with listserves and now I think there are easily 30 or so listserves operating out of a single machine . . . Also recently, a number of users, including me, have been experiencing two problems. 1) We receive multiple copies of messages . . . I have checked the list and I am only subscribed once. 2) We receive messages DAYS after they were sent out . . . most of the time this is only a minor annoyance, but once I received information on an event, sent three days before the event, two days after the event . . . Has anyone else experienced this before? Any ideas? Sam schoi@ccat.sas.upenn.edu From majordomo-users-owner Tue Mar 1 09:07:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA20056; Tue, 1 Mar 1994 16:55:33 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA20050; Tue, 1 Mar 1994 08:55:20 -0800 Received: by bluejay.creighton.edu (1.37.109.4/16.2) id AA24312; Tue, 1 Mar 94 10:56:59 -0600 Date: Tue, 1 Mar 1994 10:56:58 -0500 (CDT) From: Chuck Buda Subject: Re: listserve problem To: majordomo-users@GreatCircle.com In-Reply-To: <9403011405.AA18530@bible.sas.upenn.edu > Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Tue, 1 Mar 1994, Sam Choi wrote: > Recently the department has been going crazy with listserves and now > I think there are easily 30 or so listserves operating out of a single > machine . . . > > Also recently, a number of users, including me, have been experiencing > two problems. 1) We receive multiple copies of messages . . . I have > checked the list and I am only subscribed once. 2) We receive messages > DAYS after they were sent out . . . most of the time this is only a > minor annoyance, but once I received information on an event, sent > three days before the event, two days after the event . . . > > Has anyone else experienced this before? Any ideas? > > Sam > schoi@ccat.sas.upenn.edu > I have no idea about your #1. I think your #2 may be a function of your sendmail configuration. We've had something like this occur on our machines. While digging thru sendmail and sendmail.cf, I came across something that related to our problem. On our UNIX systems, sendmail looks at the load levels (5 minute average) on the UNIX machine. At one level, sendmail will not accept/established SMTP connections with other machines. At the next (higher) level, sendmail will only deliver messages with a priority established thru a algorithm. Working my way thru the algorithm, I calculated that most messages would be held in the mail queue until the system load dropped below this second level. Watching our machines, sendmail did appear to work in this manner. Of course, I could be totally wrong (I'm only human :-) )! *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* * * * Chuck Buda (AKA "Sancho") (cbuda@creighton.edu) * * Unix System(s) Administrator also * * Network Operations Manager ( (cbuda@cu (in JAYNet))* * Creighton University Computer Center * * 2500 California St. Phone: (402) 280-2260 * * Omaha NE 68178-0002 FAX : (402) 280-2573 * * * *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* From majordomo-users-owner Wed Mar 2 07:34:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA25316; Wed, 2 Mar 1994 07:34:12 GMT Received: from monsoon.berkeley.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA25307; Tue, 1 Mar 1994 23:34:00 -0800 Received: by monsoon.berkeley.edu (5.65c/CHAOS) id AA19601; Tue, 1 Mar 1994 23:36:18 -0800 Date: Tue, 1 Mar 1994 23:36:18 -0800 From: Dave Friedman Message-Id: <199403020736.AA19601@monsoon.berkeley.edu> To: majordomo-users@greatcircle.com Subject: Help w/digest? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I was hoping someone might be able to help me get digest running properly. I've configured everything in the .cf files to the best of my ability, and created all the necessary aliases, but when I send mail to the list "gobears" (see aliases below) it connects to the program (wrapper resend) then moves to the gobears-outgoing, then to digestify. In digestify, I get a "can't create output" error, although it continues sending the mail to the members of the original gobears-outgoing list. As far as permissions go, everything is owed by domo.domo. Wrapper is owned by root.domo, setuid root. I've never had any problems with majordomo managing lists, but the digest feature is giving me a challenge. I'm on v1.60, btw. I'm happy to answer any other questions if the information above and below is not enough. I just want to get it working so I don't kep getting complaints aout the current format and ccapabilities of my makeshift digests. Thanks, Dave Friedman davidf@ocf.Berkeley.EDU =======================RELEVANT FILES BELOW=========================== ## Here are my aliases: (Note that the "\" at the end of lines is just to make it easier for *you* to read - the actual aliasesll one-line aliases each) gobears: "|//planecrash/accounts/domo/bin/wrapper resend -l GoBears \ -f GoBears-Owner -h ocf.Berkeley.EDU -s gobears-outgoing" gobears-outgoing: :include://planecrash/accounts/domo/lists/gobears, \ gobears-digestify gobears-request: "|//planecrash/accounts/domo/bin/wrapper request-answer \ gobears" gobears-approval: rez gobears-owner: rez gobears-digest: gobears gobears-digestify: "//planecrash/accounts/domo/bin/wrapper digest -r -c \ //planecrash/accounts/domo/files/gobears-digest.cf" gobears-digest-send: "|//planecrash/accounts/domo/bin/wrapper resend -p \ bulk -l GoBears-Digest -f GoBears-Digest-Owner -h ocf.Berkeley.EDU \ -s gobears-digest-outgoing" gobears-digest-outgoing: :include://planecrash/accounts/domo/lists/gobears-digest gobears-digest-request: "|//planecrash/accounts/domo/bin/wrapper \ request-answer gobears-digest" gobears-digest-approval: rez gobears-digest-owner: rez ## Here is //planecrash/accounts/domo/files/gobears-digest.cf #Digest configuration file # #name that appears in subject line and digest banner NAME=GoBears Digest #address reader send to to reply to the entire list REPLY-TO=gobears@ocf.Berkeley.EDU #address error messages should go to ERRORS-TO=gobears-owner@ocf.Berkeley.EDU #address the digest itself appears to be sent to TO=GoBears-Digest@ocf.Berkeley.EDU #address the digest really is sent to REALLY-TO=gobears-digest-send@ocf.Berkeley.EDU #address administrative nonsense should go to FROM=gobears-owner@ocf.berkeley.edu #file containing header text HEADER=//planecrash/accounts/domo/files/digest-files/gobears-digest.header #file containing trailer text TRAILER=//planecrash/accounts/domo/files/digest-files/gobears-digest.trailer #directory to store incoming messages #INCOMING=/usr/local/mail/digests/incoming/firewalls #INCOMING=/mycroft/brent/digest/incoming INCOMING=//planecrash/accounts/domo/files/digest-files/incoming #file containing volume number VOL_FILE=//planecrash/acounts/domo/files/digest-files/gobears-digest.vol #file containing issue number NUM_FILE=//planecrash/accounts/domo/files/digest-files/gobears-digest.num #directory to archive outgoing issues ARCHIVE=//planecrash/accounts/domo/files/digest-files/gobears-archive #directory containing shlock.pl and other stuff HOME=//planecrash/accounts/domo/files/digest-files #how big do we let digests get before sending? DIGEST_SIZE=30000 From majordomo-users-owner Wed Mar 2 12:07:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA26264; Wed, 2 Mar 1994 12:07:20 GMT Received: from mole.cis.ufl.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id EAA26258; Wed, 2 Mar 1994 04:07:10 -0800 From: spp@cis.ufl.edu Received: from localhost by mole.cis.ufl.edu (8.6.4/4.11) id HAA09983; Wed, 2 Mar 1994 07:09:41 -0500 Message-Id: <199403021209.HAA09983@mole.cis.ufl.edu> To: Dave Friedman cc: majordomo-users@greatcircle.com Subject: Re: Help w/digest? In-reply-to: Some random ramblings on Tue, 01 Mar 94 23:36:18 -0800. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Wed, 02 Mar 94 07:09:40 EST Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused Dave Friedman to writ e: | gobears-digestify: "//planecrash/accounts/domo/bin/wrapper digest -r -c \ | //planecrash/accounts/domo/files/gobears-digest.cf" Assuming this really is what your alias says, you need to | through wrapper. Steve From majordomo-users-owner Wed Mar 2 16:13:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA27049; Wed, 2 Mar 1994 16:13:56 GMT Received: from udlapvms.pue.udlap.mx by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA27043; Wed, 2 Mar 1994 08:13:48 -0800 Received: by udlapvms.pue.udlap.mx (4.1/SMI-4.0) id AA11559; Wed, 2 Mar 94 10:21:24 CST Date: Wed, 2 Mar 1994 10:15:10 -0600 (CST) From: Alfredo De Regil Subject: Documentation( Was Re: insecure usage? ) To: majordomo-users@GreatCircle.COM In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thanks to all the replys I received! On Fri, 25 Feb 1994, Alfredo De Regil wrote: > Hello, I'm trying to install majordomo and after putting everything the > way the documentation told me I'm getting the following error message when > I send a message to majordomo: > > /usr/local/udla/etc/majordomo/wrapper: error: insecure usage > 554 "|/usr/local/udla/etc/majordomo/wrapper > /usr/local/udla/etc/majordomo"... > unknown mailer error 2 > > > I double checked the permissions and everything looks fine to me, does any > have any tip that would help me? Thanks in advance. > The problem is fixed now but I would like to make some comments: 1) I put the whole path in the argument to the wrapper program because I was getting a 'command not found' error. 2) I had to look at the code of wrapper.c to figure out the problem. 3) The problem was simple: my perl program was NOT in the standard place. 4) I *think* the documentation should give you an advice about that! At least some pointer to that *fixed* paths... Maybe everybody can put the public software in the standard places but I hardly think that's usual. Anyway, I think I just entered in the majordomo community 5) I tried another mailing list software but I had to admit this one (majordomo) *even with all the problems it caused to me* is much much easier to install that, let's say, listproc!!! :) Thanks again for the tips Alfredo De Regil Coordinador Servicios De Informacion Centro De Computo - Universidad de las Americas Puebla ___________________________________________________________________________ Sugiere, Avisa, Pide, Alaba, Dona, Exige, Disculpate, Inventa, Grita, Sincerate, Ignora, Saluda, Desea, Sonrie... ESCRIBE! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ alfredo@udlapvms.pue.udlap.mx From majordomo-users-owner Wed Mar 2 16:41:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA27195; Wed, 2 Mar 1994 16:41:24 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA27183; Wed, 2 Mar 1994 08:41:13 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id LAA18896; Wed, 2 Mar 1994 11:43:22 -0500 Message-Id: <199403021643.LAA18896@bosnia.pop.psu.edu> To: Alfredo De Regil Cc: majordomo-users@greatcircle.com Subject: Re: Documentation( Was Re: insecure usage? ) In-reply-to: Your message of "Wed, 02 Mar 1994 10:15:10 CST." 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 X-Mailer: exmh version 1.3beta 2/17/94 Date: Wed, 02 Mar 1994 11:43:21 -0500 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Alfredo De Regil wri tes: >The problem is fixed now but I would like to make some comments: > >1) I put the whole path in the argument to the wrapper program because > I was getting a 'command not found' error. > >2) I had to look at the code of wrapper.c to figure out the problem. >4) I *think* the documentation should give you an advice about that! Well, it is documented pretty clearly at the very top of the Makefile: # This is where "wrapper" looks for the programs it's supposed to run. W_BIN=/usr/local/majordomo It's also mentioned again in the README under the "To install majordomo:" section: edit the "Makefile" to set W_BIN and the environment for "wrapper"; >5) I tried another mailing list software but I had to admit this one > (majordomo) > *even with all the problems it caused to me* is much much easier to > install that, let's say, listproc!!! :) Yep. I had no end of headaches with ListProcessor. It's probably one of the worst designed mail programs I ever have seen. It's hard to install, use, maintain, and to top it off it doesn't even work right. --Dave From majordomo-users-owner Wed Mar 2 16:46:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA27245; Wed, 2 Mar 1994 16:46:52 GMT Received: from udlapvms.pue.udlap.mx by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA27239; Wed, 2 Mar 1994 08:46:41 -0800 Received: by udlapvms.pue.udlap.mx (4.1/SMI-4.0) id AA12614; Wed, 2 Mar 94 10:53:54 CST Date: Wed, 2 Mar 1994 10:51:45 -0600 (CST) From: Alfredo De Regil Subject: Re: Documentation( Was Re: insecure usage? ) To: David Barr Cc: majordomo-users@greatcircle.com In-Reply-To: <199403021643.LAA18896@bosnia.pop.psu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Wed, 2 Mar 1994, David Barr wrote: > In message , Alfredo De Regil wri > tes: > > >The problem is fixed now but I would like to make some comments: > > > > >4) I *think* the documentation should give you an advice about that! > > Well, it is documented pretty clearly at the very top of the Makefile: > > # This is where "wrapper" looks for the programs it's supposed to run. > W_BIN=/usr/local/majordomo > > It's also mentioned again in the README under the "To install majordomo:" > section: > > edit the "Makefile" to set W_BIN and the environment for "wrapper"; > Well I'm talking about the path for the perl program (the majordomo perl script expects it will be /usr/local/bin/perl). I had to change that fixed path to my particular path. And I'm pretty sure the documentation makes no advice about that. > > --Dave Alfredo De Regil Coordinador Servicios De Informacion Centro De Computo - Universidad de las Americas Puebla ___________________________________________________________________________ Sugiere, Avisa, Pide, Alaba, Dona, Exige, Disculpate, Inventa, Grita, Sincerate, Ignora, Saluda, Desea, Sonrie... ESCRIBE! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ alfredo@udlapvms.pue.udlap.mx From majordomo-users-owner Wed Mar 2 18:56:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA28095; Wed, 2 Mar 1994 18:56:14 GMT Received: from zaphod.b17d.ingr.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA28081; Wed, 2 Mar 1994 10:55:47 -0800 Received: by zaphod.b17d.ingr.com (5.65c/1.921207) id AA03398; Wed, 2 Mar 1994 12:55:51 -0600 From: mgpalmer@zaphod.b17d.ingr.com (Michael Palmer) Message-Id: <199403021855.AA03398@zaphod.b17d.ingr.com> Subject: Re: Documentation( Was Re: insecure usage? ) To: alfredo@udlapvms.pue.udlap.mx (Alfredo De Regil) Date: Wed, 2 Mar 94 12:55:50 CST Cc: majordomo-users@greatcircle.com Reply-To: mgpalmer@zaphod.b17d.ingr.com (Michael G. Palmer) In-Reply-To: ; from "Alfredo De Regil" at Mar 2, 94 10:51 am X-Mailer: ELM [version 07.00.00.00 (2.3 PL11)] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk said: >On Wed, 2 Mar 1994, David Barr wrote: > >> In message , Alfredo De Regil wri >> tes: >> >4) I *think* the documentation should give you an advice about that! >> >> Well, it is documented pretty clearly at the very top of the Makefile: >> >> It's also mentioned again in the README under the "To install majordomo:" >> section: > > Well I'm talking about the path for the perl program (the majordomo > perl script expects it will be /usr/local/bin/perl). I had to change that > fixed path to my particular path. And I'm pretty sure the documentation > makes no advice about that. You are correct here. Actually, all of the perl scripts expect perl to be in a fixed place. Each perl script had to be edited to get it to run on my system since perl resides in /usr/bin/perl and not it /usr/local/bin/perl (on Intergraphs CLIX system.) I, also, found no documentation for this, but didn't find it to be much of a problem. The biggest problem that I had was in getting the wrapper program to work successfully on my system. Additionally, I had no perl experience and was daunted slightly by that. All in all I find majordomo to be very reliable and quite a time saver. Now if I could just get others in my department to use it for mailing lists.... most lists are manually maintained and it is _hard_ to get off of a list :( >> --Dave > >Alfredo De Regil Coordinador Servicios De Informacion -- Michael G. Palmer From majordomo-users-owner Wed Mar 2 21:24:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA28652; Wed, 2 Mar 1994 21:24:18 GMT Received: from scr.siemens.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA28646; Wed, 2 Mar 1994 13:24:08 -0800 Received: from plunger.siemens.com (plunger.siemens.com [129.73.2.60]) by scr.siemens.com (8.6.5/8.6.4) with ESMTP id QAA19716 for ; Wed, 2 Mar 1994 16:26:14 -0500 Received: from localhost (bmh@localhost) by plunger.siemens.com (8.6.5/8.6.4) id QAA26399 for majordomo-users@GreatCircle.COM; Wed, 2 Mar 1994 16:26:06 -0500 Date: Wed, 2 Mar 1994 16:26:06 -0500 From: Beatrice M Hwong Message-Id: <199403022126.QAA26399@plunger.siemens.com> To: majordomo-users@GreatCircle.COM Subject: Re: Gotcha with arcive subdirectory permissions Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > From majordomo-users-owner@GreatCircle.COM Sat Feb 26 17:37:02 1994 > To: majordomo-users@GreatCircle.COM > Subject: Gotcha with arcive subdirectory permissions > Date: Sat, 26 Feb 1994 14:20:07 -0800 > From: Brent Chapman > Sender: Majordomo-Users-Owner@GreatCircle.COM > Content-Length: 1199 From majordomo-users-owner Wed Mar 2 22:05:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA28962; Wed, 2 Mar 1994 22:05:43 GMT Received: from scr.siemens.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA28956; Wed, 2 Mar 1994 14:05:35 -0800 Received: from plunger.siemens.com (plunger.siemens.com [129.73.2.60]) by scr.siemens.com (8.6.5/8.6.4) with ESMTP id RAA20852 for ; Wed, 2 Mar 1994 17:07:43 -0500 Received: from localhost (bmh@localhost) by plunger.siemens.com (8.6.5/8.6.4) id RAA26463; Wed, 2 Mar 1994 17:07:42 -0500 Date: Wed, 2 Mar 1994 17:07:42 -0500 From: Beatrice M Hwong Message-Id: <199403022207.RAA26463@plunger.siemens.com> To: majordomo-users@GreatCircle.COM Subject: Re: Gotcha with arcive subdirectory permissions Cc: bmh@scr.siemens.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > From majordomo-users-owner@GreatCircle.COM Sat Feb 26 17:37:02 1994 > > To: majordomo-users@GreatCircle.COM > > Subject: Gotcha with arcive subdirectory permissions > > Date: Sat, 26 Feb 1994 14:20:07 -0800 > > From: Brent Chapman > > Sender: Majordomo-Users-Owner@GreatCircle.COM > > Content-Length: 1199 > stuff about regretting implementing "get" and suggesting that FTPMail does > the job. Whoops, I used . in my mail message, so here it goes again. I, for one, thank you for implementing "get". It is the main reason we are using it for mailing lists here. For security it has that nice "approve" feature. For ease of use and admin it is compact and has a simple command set. We would like our secretaries and librarian to use this mailing list, and although they'll have to deal with some unix'isms, they won't have to fight ftp with its requirements for "connect", "chdir", "get" vs "put", and other ugly ftp'isms. From majordomo-users-owner Wed Mar 2 22:14:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA29033; Wed, 2 Mar 1994 22:14:37 GMT Received: from disserv.stu.umn.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA29024; Wed, 2 Mar 1994 14:14:01 -0800 Received: by disserv.stu.umn.edu (Smail3.1.28.1 #1) id m0pbzDO-0002yWC; Wed, 2 Mar 94 16:16 CST Message-Id: From: thingles@disserv.stu.umn.edu (Jamie Thingelstad) Subject: Re: Documentation( Was Re: insecure usage? ) To: mgpalmer@zaphod.b17d.ingr.com Date: Wed, 2 Mar 1994 16:16:25 -0600 (CST) Cc: alfredo@udlapvms.pue.udlap.mx, majordomo-users@GreatCircle.COM In-Reply-To: <199403021855.AA03398@zaphod.b17d.ingr.com> from "Michael Palmer" at Mar 2, 94 12:55:50 pm X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 726 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk According to Michael Palmer: # # You are correct here. Actually, all of the perl scripts expect perl to # be in a fixed place. Each perl script had to be edited to get it to run # on my system since perl resides in /usr/bin/perl and not it # /usr/local/bin/perl (on Intergraphs CLIX system.) I, also, found no % ln -s /usr/local/bin/perl /usr/bin/perl Problem solved. -- = * File Edit View Label Special ================== Jamie Thingelstad 612.626.7846 (W) 612.625.5572 (F) Technical Coordinator 101 Pleasant St SE, 12 Johnston, Mpls, MN 55455 Disability Services = thingles@disserv.stu.umn.edu =================== University of Minnesota http://disserv.stu.umn.edu/~thingles/home.html From majordomo-users-owner Wed Mar 2 23:31:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA29484; Wed, 2 Mar 1994 23:31:40 GMT Received: from inet-gw-2.pa.dec.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA29478; Wed, 2 Mar 1994 15:31:24 -0800 Received: from us1rmc.bb.dec.com by inet-gw-2.pa.dec.com (5.65/13Jan94) id AA21234; Wed, 2 Mar 94 15:19:53 -0800 Received: from wrksys.enet by us1rmc.bb.dec.com (5.65/rmc-22feb94) id AA24693; Wed, 2 Mar 94 18:19:15 -0500 Message-Id: <9403022319.AA24693@us1rmc.bb.dec.com> Received: from wrksys.enet; by us1rmc.enet; Wed, 2 Mar 94 18:19:46 EST Date: Wed, 2 Mar 94 18:19:47 EST From: Jim Reisert - Alpha Personal Systems 02-Mar-1994 1752 To: barr@pop.psu.edu Cc: alfredo@udlapvms.pue.udlap.mx, majordomo-users@greatcircle.com Apparently-To: majordomo-users@greatcircle.com, alfredo@udlapvms.pue.udlap.mx, barr@pop.psu.edu Subject: RE: Documentation( Was Re: insecure usage? ) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk David Barr (barr@pop.psu.edu) wrote: >Well, it is documented pretty clearly at the very top of the Makefile: ># This is where "wrapper" looks for the programs it's supposed to run. >W_BIN=/usr/local/majordomo >It's also mentioned again in the README under the "To install majordomo:" >section: > edit the "Makefile" to set W_BIN and the environment for "wrapper"; Actually, it's not clear at all. The problem he was referring to (and I got bitten by this also), is that at the top of majordomo.pl, the path to perl is given as: /usr/local/bin/perl When you run "wrapper" some versions of Unix report "program not found" but don't tell you what isn't found - in his (and my case) /usr/local/bin/perl. We assumed (incorrectly) that the program that wasn't found was majordomo.pl itself, so we tried to give wrapper an explicit path to find majordomo.pl. It should say somewhere in the instructions that the PERL scripts expect PERL to be installed in /usr/local/bin/perl. - Jim From majordomo-users-owner Thu Mar 3 01:36:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA29972; Thu, 3 Mar 1994 01:36:53 GMT Received: from whirlwind.berkeley.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA29966; Wed, 2 Mar 1994 17:36:45 -0800 Received: by whirlwind.berkeley.edu (5.65c/CHAOS) id AA28460; Wed, 2 Mar 1994 17:39:17 -0800 Date: Wed, 2 Mar 1994 17:39:17 -0800 From: Dave Friedman Message-Id: <199403030139.AA28460@whirlwind.berkeley.edu> To: majordomo-users@greatcircle.com Subject: The digest problem Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk It's fixed - thanks to those who responded. The problems were (in no particular order): 1) Failure to pipe the mail through a program (i.e. "//program" should have been "|//program") 2) Incorrect permissions (the files were duplicated all over the place, so I'd set the correct permissions on the wrong files) 3) Typo in file name. In other words, had I typed everything right, digest would have installed perfectly thefirst time. -Dave From majordomo-users-owner Thu Mar 3 03:56:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id DAA00665; Thu, 3 Mar 1994 03:56:18 GMT Received: from cubetech.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA00659; Wed, 2 Mar 1994 19:56:06 -0800 Received: from valinor by cubetech.com (NX5.67e/NX3.0/CT1.3/1.12.93) id AA26662; Wed, 2 Mar 94 21:58:42 -0600 Received: by valinor.cubetech.com (NX5.67e/NX3.0S) id AA26545; Wed, 2 Mar 94 21:58:35 -0600 Date: Wed, 2 Mar 94 21:58:35 -0600 From: Andrew Loewenstern Message-Id: <9403030358.AA26545@valinor.cubetech.com> Received: by NeXT.Mailer (1.95) Received: by NeXT Mailer (1.95) To: majordomo-users@GreatCircle.COM Subject: cannot execute unknown mailer error 1 Reply-To: andrew@cubetech.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am having a weird problem with Majordomo. It has suddenly stopped working. Whenever a request is sent in, the mail bounces with something like the following: ----- Transcript of session follows ----- sh: /home/CTStaff/andrew/Library/Majordomo/wrapper: cannot execute 554 "|/home/CTStaff/andrew/Library/Majordomo/wrapper majordomo"... 554 unknown mailer error 1 What is strange is that *i* can operate Majordomo locally, but any requests from outside bounce. This problem has stumped me for some time... help please! thanks! andrew From majordomo-users-owner Fri Mar 4 16:49:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA10624; Fri, 4 Mar 1994 16:49:43 GMT Received: from scr.siemens.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA10618; Fri, 4 Mar 1994 08:49:36 -0800 Received: from plunger.siemens.com (plunger.siemens.com [129.73.2.60]) by scr.siemens.com (8.6.5/8.6.4) with ESMTP id LAA17109 for ; Fri, 4 Mar 1994 11:51:43 -0500 Received: from localhost (bmh@localhost) by plunger.siemens.com (8.6.5/8.6.4) id LAA28392 for majordomo-users@GreatCircle.COM; Fri, 4 Mar 1994 11:51:41 -0500 Date: Fri, 4 Mar 1994 11:51:41 -0500 From: Beatrice M Hwong Message-Id: <199403041651.LAA28392@plunger.siemens.com> To: majordomo-users@GreatCircle.COM Subject: security of majordomo Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk When a new list is set up, the recommendation is to make files, mode 664 and directories, mode 775. I have found that such open permissions negates the value of the approve feature of majordomo. Unsubscribed users, as long as they know the name of a list, can retrieve indices and do "gets" on files. They don't have to be subscribed which defeats the purpose of subscription and the notion of a closed list. If a particular mailing is changed so that its files and directories are, mode 660, an "index" command for that list results in a listing of all other files and directories that majordomo does know about. There's been recent discussion about ownerships and permissions in order to make majordomo work properly. My question is how to restrict permissions in order to make the lists truly closed. From majordomo-users-owner Sat Mar 5 05:24:32 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA15173; Sat, 5 Mar 1994 05:24:32 GMT Received: from tsunami.berkeley.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA15167; Fri, 4 Mar 1994 21:24:18 -0800 Received: by tsunami.berkeley.edu (5.65c/CHAOS) id AA22940; Fri, 4 Mar 1994 21:26:47 -0800 Date: Fri, 4 Mar 1994 21:26:47 -0800 From: Dave Friedman Message-Id: <199403050526.AA22940@tsunami.berkeley.edu> To: majordomo-users@greatcircle.com Subject: Another digest question Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Does anyone know of a good way to make sure that a digest gets sent at least once a day, even if it hasn't hit the defined limited size? In other words, I've set my size limit at 30K. But the list members want to receive the digest AT LEAST once per day. I'd figure it to be a cron job, but I'm not sure of the syntax of running digest without receiving mail. Please respond directly to me, or at least with a cc, as I'm no longer active on the majordomo-users list. Thanks, Dave Friedman davidf@ocf.berkeley.edu ., From majordomo-users-owner Fri Mar 4 21:27:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA15094; Sat, 5 Mar 1994 05:18:56 GMT Received: from callisto.pas.rochester.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA14917; Fri, 4 Mar 1994 21:02:59 -0800 Received: by callisto.pas.rochester.edu (4.1/1.16) id AA11230; Sat, 5 Mar 94 00:09:40 EST Date: Sat, 5 Mar 94 00:09:40 EST From: Colin Sebastian Roald Message-Id: <9403050509.AA11230@callisto.pas.rochester.edu> To: majordomo-users@greatcircle.com Subject: what does this error mean? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I was trying to test the "subscribe" function, and it works fine when i mail from my own account. but when i mail from a friend's account, i get two crash messages. One says: > MAJORDOMO ABORT > > Can't append to /u/ath/colin/admin/gog: Interrupted system call and the other says: > From: Mail Delivery Subsystem > To: owner-majordomo > Subject: Returned mail: unknown mailer error 4 > > ----- Transcript of session follows ----- > shlock: open(">/u/ath/colin/admin/shlock.11149"): Permission denied at > /u/ath/colin/admin/majordomo/shlock.pl line 131, <> line 1. > shlock: open... the "permission denied" message is repeated more times than i care to count. ownership of shlock.pl is daemon.majordom, which i believe is what the docs instructed. -- colin roald | gods by the bushel, gods by the pound, gods for all occasions... From majordomo-users-owner Sat Mar 5 05:32:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA15237; Sat, 5 Mar 1994 05:32:46 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA15227; Fri, 4 Mar 1994 21:32:39 -0800 Message-Id: <199403050532.VAA15227@mycroft.GreatCircle.COM> To: Dave Friedman cc: majordomo-users@greatcircle.com Subject: Re: Another digest question In-reply-to: Your message of Fri, 4 Mar 1994 21:26:47 -0800 Date: Fri, 04 Mar 1994 21:32:38 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dave Friedman writes: # Does anyone know of a good way to make sure that a digest gets sent at # least once a day, even if it hasn't hit the defined limited size? # # In other words, I've set my size limit at 30K. But the list members want # to receive the digest AT LEAST once per day. I'd figure it to be a cron # job, but I'm not sure of the syntax of running digest without receiving # mail. Assuming you're using my "digest" program: 0 1 * * * /usr/local/mail/majordomo/wrapper digest -m -c /usr/local/mail/digest/firewalls-digest.cf >/dev/null 2>&1 -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Sun Mar 6 01:04:34 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA18972; Sun, 6 Mar 1994 01:04:34 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA18747; Sat, 5 Mar 1994 15:44:15 -0800 Message-Id: <199403052344.PAA18747@mycroft.GreatCircle.COM> To: Larry Sheldon cc: majordomo-users@greatcircle.com Subject: Re: Header Hack needed In-reply-to: Your message of Mon, 28 Feb 94 19:18:06 CST Date: Sat, 05 Mar 1994 15:44:14 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Larry Sheldon writes: # We have a large number of customers on Novell servers who use Pegasus # through a CHARON gateway. Several of them subscribe to lists I manage, # and several of _them_ are madly in love with "delivery confirmation" # and "receipt confirmation", so that when they post, every other Pegasus # user sends out two confirmations, which every other Pegasus gets (off the # list) triggering an avalanche of confirmations. # # It looks to me like I could put a couple of greps in the alias file to # eat up the triggering headers on the way in, but it seems like there # is a better way. # # There always is. # # Anybody done this yet? I'm sort of afraid to wander into resend by # myself--did that some this past weekend with Brent's constant assistance, # but still came away from that afraid to go back and find the one last # problem. # # And I have no clue as to where to start on this one. You're going to have to dive back in to "resend"... :-) Look for the comment "# skip all these headers" in "resend". These are the headers that "resend" ignores in input (often because it creates its own versions of those same headers). Add the the problem header to that list, in much the same way as the "return-receipt-to:" header is in the list (which happens to be the Sendmail header that generates return receipts, analagous to what you're trying to suppress). -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Sun Mar 6 02:32:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA19631; Sun, 6 Mar 1994 02:32:30 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA19624; Sat, 5 Mar 1994 18:32:22 -0800 Message-Id: <199403060232.SAA19624@mycroft.GreatCircle.COM> To: Jim Reisert - Alpha Personal Systems cc: majordomo-users@greatcircle.com Subject: Re: Hostile address code In-reply-to: Your message of Mon, 28 Feb 94 18:55:29 EST Date: Sat, 05 Mar 1994 18:32:21 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Jim Reisert - Alpha Personal Systems writes: # I disabled the hostile address checking code, since my system can handle # mail to users with "/" in the name: # # # if (tr/|\//|\// != 0) { # # &main'abort("HOSTILE ADDRESS $addr"); # # return undef; # # } # # Is this going to break anything else? Not if you trust your mailer to "do the right thing" when folks try to give it filenames or command pipes as email addresses. I use Sendmail; I _don't_ trust it to do the right thing (though I trust the new 8.6.* version a lot more than the previous versions). -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Sat Mar 5 19:07:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA19910; Sun, 6 Mar 1994 02:59:54 GMT Received: from pilot.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA19904; Sat, 5 Mar 1994 18:59:39 -0800 Received: by pilot.com (NX5.67d/NX3.0M) id AA01348; Sat, 5 Mar 94 19:00:13 -0800 Date: Sat, 5 Mar 94 19:00:13 -0800 From: Randy Antler Message-Id: <9403060300.AA01348@pilot.com> Received: by NeXT.Mailer (1.100) Received: by NeXT Mailer (1.100) To: majordomo-users@GreatCircle.COM Subject: Syntax error in majordomo.pl Reply-To: randy@pilot.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am a new Majordomo user and after spending some time setting up the software I am encountering a syntax error (apparently) in the majordomo.pl perl script. I am not fluent in perl by any stretch of the imagination (not yet at least) so I am hesitant to attempt to debug the script on my own. I am using version 1.62 of Majordomo and the following version of perl on a NeXTstation: bash$ perl -v This is perl, version 4.0 $Header: perl.c,v 4.0 91/03/20 01:37:44 lwall Locked $ Patch level: 0 Copyright (c) 1989, 1990, 1991, Larry Wall Perl may be copied only under the terms of the GNU General Public License, a copy of which can be found with the Perl 4.0 distribution kit. The error I am getting after executing "wrapper majordomo" is the following: bash$ wrapper majordomo syntax error in file /majord/majordomo.pl at line 58, next 2 tokens "m/^([^:]+):\s*(.*\S)\s*$/g" The corresponding code fragment in majordomo.pl is: foreach $_ (@array) { --> ($keyw, $val) = m/^([^:]+):\s*(.*\S)\s*$/g; $keyw =~ y/A-Z/a-z/; Feel free to respond to this list and/or to my email address. Thanks in advance. -- randy@pilot.com (home address) NeXTMAIL randy@nacm.com (work address) Welcome! *Out* and _proud_ of it! (finger me for my public key!) ________________________________________________________________________ "We are here! We are here! We are here!" -- Horton and the Who ________________________________________________________________________ DOLLAR HAS SPIRITUAL VALUE! JERUSALEM - Israel's chief rabbi, Mordechai Eliahu, says people should keep U.S. dollars in their pockets when in a restroom or an unclean place. His office said Wednesday that an American Jew raised the question because the bills say: "In God We Trust." The rabbi's religious ruling said that because of the motto, dollars must be treated the same way as holy documents and not be exposed to filth. --Reuters From majordomo-users-owner Sun Mar 6 05:41:35 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA20288; Sun, 6 Mar 1994 05:41:35 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA20281; Sat, 5 Mar 1994 21:41:28 -0800 Message-Id: <199403060541.VAA20281@mycroft.GreatCircle.COM> To: randy@pilot.com cc: majordomo-users@GreatCircle.COM Subject: Re: Syntax error in majordomo.pl In-reply-to: Your message of Sat, 5 Mar 94 19:00:13 -0800 Date: Sat, 05 Mar 1994 21:41:27 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Randy Antler writes: # I am a new Majordomo user and after spending some time setting up the softwar # e I am # encountering a syntax error (apparently) in the majordomo.pl perl script. I # am not fluent in # perl by any stretch of the imagination (not yet at least) so I am hesitant to # attempt to debug # the script on my own. # # I am using version 1.62 of Majordomo and the following version of perl on a N # eXTstation: # # bash$ perl -v # # This is perl, version 4.0 # # $Header: perl.c,v 4.0 91/03/20 01:37:44 lwall Locked $ # Patch level: 0 You're using a VERY old version of Perl; Majordomo requires patch level 35 (also known as "4.035") or later. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Sun Mar 6 21:35:32 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA22600; Sun, 6 Mar 1994 21:35:32 GMT Received: from jade.saintmarys.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA22594; Sun, 6 Mar 1994 13:35:25 -0800 Received: by jade.saintmarys.edu (1.37.109.8/16.2) id AA04520; Sun, 6 Mar 1994 16:41:55 -0500 Date: Sun, 6 Mar 1994 16:41:55 -0500 (EST) From: Dan Mandell Subject: Error: All recipients suppressed (fwd) To: majordomo-users@GreatCircle.COM Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk From: Dan Mandell To: Majordomo Subject: Error: All recipients suppressed (fwd) We are trying to get majordomo running under hpux on an HP Series 9000 Model 827. The make went ok but after creating "testlist" attempts to subscribe result in the following message... Dan ============ Date: Sun, 6 Mar 1994 15:44:24 -0500 (EST) From: Mail Delivery Subsystem To: dmandell@jade.saintmarys.edu Subject: Returned mail: All recipients suppressed ^^^^^^^^^^^^^^^^^^^^^^^^^ To: testlist@jade.saintmarys.edu subscribe testlist Dan Mandell -- ===================================== Dan Mandell, Computer Services, Saint Mary's College Internet: dmandell@saintmarys.edu "Always promise a little less than you can deliver" : Montaigne From majordomo-users-owner Sun Mar 6 22:47:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA23044; Sun, 6 Mar 1994 22:47:49 GMT Received: from jade.saintmarys.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA23038; Sun, 6 Mar 1994 14:47:40 -0800 Received: by jade.saintmarys.edu (1.37.109.8/16.2) id AA05275; Sun, 6 Mar 1994 17:54:52 -0500 Date: Sun, 6 Mar 1994 17:54:51 -0500 (EST) From: Dan Mandell Reply-To: Dan Mandell Subject: Re: Error: All recipients suppressed (fwd) To: majordomo-users@GreatCircle.COM In-Reply-To: <199403062207.AA20007@cs.umb.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thanks to John Rouillard for helping with the subscription protocol. But, I apparently still have a serious problem in my setup because now subscription attempts directed to majordomo result in the following error message coming to owner-majordomo. ===================== From MAILER-DAEMON@jade.saintmarys.edu Sun Mar 6 17:43:42 1994 Date: Sun, 6 Mar 1994 17:35:25 -0500 (EST) From: Mail Delivery Subsystem To: owner-majordomo@jade.saintmarys.edu Subject: Returned mail: unknown mailer error 5 ----- Transcript of session follows ----- majordomo: Permission denied 554 "|/conv9/majordomo/wrapper majordomo"... unknown mailer error 5 ----- Unsent message follows ----- Received: by jade.saintmarys.edu (1.37.109.8/16.2) id AA05184; Sun, 6 Mar 1994 17:35:25 -0500 Return-Path: Date: Sun, 6 Mar 1994 17:35:25 -0500 (EST) From: Dan Mandell Subject: To: majordomo@jade.saintmarys.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII subscribe testlist dmandell@saintmarys.edu help From majordomo-users-owner Mon Mar 7 17:01:36 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA27056; Mon, 7 Mar 1994 17:01:36 GMT Received: from dragonfly.cis.ufl.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA26177; Mon, 7 Mar 1994 05:18:11 -0800 Received: from localhost by dragonfly.cis.ufl.edu (8.6.4/4.11) id IAA06503; Mon, 7 Mar 1994 08:20:16 -0500 Message-Id: <199403071320.IAA06503@dragonfly.cis.ufl.edu> To: Dan Mandell cc: majordomo-users@greatcircle.com Subject: Re: Error: All recipients suppressed (fwd) In-reply-to: Some random ramblings on Sun, 06 Mar 1994 16:41:55 -0500. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Mon, 07 Mar 1994 08:20:15 EST From: Stephen P Potter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused Dan Mandell to write: | We are trying to get majordomo running under hpux on an HP Series 9000 | Model 827. The make went ok but after creating "testlist" attempts to | subscribe result in the following message... | | Dan | ============ | To: testlist@jade.saintmarys.edu | | subscribe testlist Dan Mandell Unless your mailer is doing something screwy and I'm completely missing what is happening here, you need to send the mail to "majordomo", not to the list itself. Majordomo will surpress administrative mail sent to the list address, which is what happened with the above. Also, re your earlier problems, check that the permissions and ownership are set correctly, and that wrapper is setuid to whatever runs your sendmail (probably deamon). Steve From majordomo-users-owner Mon Mar 7 09:47:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA27578; Mon, 7 Mar 1994 17:38:49 GMT Received: from ag.srnr.Arizona.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA27572; Mon, 7 Mar 1994 09:38:36 -0800 Received: by ag.srnr.Arizona.EDU (5.0/SMI-SVR4) id AA14474; Mon, 7 Mar 1994 10:40:43 +0700 Date: Mon, 7 Mar 1994 10:40:43 +0700 From: schmitt@ag.srnr.Arizona.EDU (Jennifer A. Schmitt) Message-Id: <9403071740.AA14474@ ag.srnr.Arizona.EDU> To: majordomo-users@greatcircle.com Subject: Returned mail: Can't create output X-Sun-Charset: US-ASCII content-length: 1699 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am setting up majordomo on our server. I am trying to get archiving working. I guess first-off I don't fully understand how archiving works, so could someone explain this for me? Secondly, from what I do understand, I have set up an archive directory which $filedir is set to in the majordomo.cf file. Within this directory I have a test.archive directory set up. $filedir.suffix is set to .archive. My mail alias to send the mail is set up like this: test: "|/opt/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l test -f test-owner -h ag.srnr.arizona.edu -s test-outgoing" owner-test: test-owner test-outgoing: :include:/opt/local/mail/lists/test, test-archive test-archive: /opt/local/mail/archive/test When I send out mail to my group test, I am getting the following error message. Can anyone help me with this? Thanks, Jen ----- Begin Included Message ----- >From Mailer-Daemon Mon Mar 7 10:23 MST 1994 Date: test From: to Subject: Returned mail: Can't create output To: owner-test-archive ----- Transcript of session follows ----- 550 /opt/local/mail/archive/test... Can't create output ----- Unsent message follows ----- Return-Path: Received: by ag.srnr.Arizona.EDU (5.0/SMI-SVR4) id AA14368; Mon, 7 Mar 1994 10:23:28 +0700 Errors-To: schmitt Received: by ag.srnr.Arizona.EDU (5.0/SMI-SVR4) id AA14361; Mon, 7 Mar 1994 10:23:27 +0700 Date: Mon, 7 Mar 1994 10:23:27 +0700 From: schmitt (Jennifer A. Schmitt) Message-Id: <9403071723.AA14361@ ag.srnr.Arizona.EDU> To: test X-Sun-Charset: US-ASCII Content-Length: 33 Sender: test-owner@ag.srnr.Arizona.EDU Precedence: bulk Test message 3 on Monday morning ----- End Included Message ----- From majordomo-users-owner Mon Mar 7 21:02:34 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA29756; Mon, 7 Mar 1994 21:02:34 GMT Received: from nd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA29750; Mon, 7 Mar 1994 13:02:24 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Mon, 7 Mar 1994 16:04:37 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA01855; Mon, 7 Mar 94 16:12:53 -0500 Date: Mon, 7 Mar 94 16:12:53 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9403072112.AA01855@nowaksg.chem.nd.edu> To: majordomo-users@greatcircle.com Subject: Using Majordomo on an SGI machine Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all. I'm very new to this but I was told that if I wanted to run a mail list that I should get majordomo. I've done that. And I've obviously subscribed to this list in search of wisdom. I want to run Majordomo on a SGI Personal Iris 4D/25 running IRIX 4.0.5c and would like to hear from anyone who has any similar experience to find out if there are problems I should be made aware of as I start on this journey. I'm not a UNIX guru (nor am I a total newbie) and I'm not a system admin (though I play one on TV...actually I am root user on this specific machine but I depend soley on the advice of those more knowledgable than I.). Thanks in advance for you kindness. Mike | Mike Buening Why's the rich man busy dancing | | Beamer (the monster cocker) while the poor man pays the band? | | mike@nowaksg.chem.nd.edu | From majordomo-users-owner Mon Mar 7 21:17:41 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA29924; Mon, 7 Mar 1994 21:17:41 GMT Received: from aruba.lerc.nasa.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA29917; Mon, 7 Mar 1994 13:17:28 -0800 Received: from sandman.lerc.nasa.gov by aruba.lerc.nasa.gov with SMTP (920330.SGI/LeRC/DLW/TAF(1.22-main)) id AA06827; Mon, 7 Mar 94 16:20:07 -0500 Received: by sandman.lerc.nasa.gov (931110.SGI/LeRC/DLW/TAF(1.22-local)) id AA25839; Mon, 7 Mar 94 16:21:29 -0500 Date: Mon, 7 Mar 94 16:21:29 -0500 From: drich@lerc.nasa.gov (Daniel Rich) Message-Id: <9403072121.AA25839@sandman.lerc.nasa.gov> To: mike@nowaksg.chem.nd.edu (Mike Buening) Cc: majordomo-users@greatcircle.com Subject: Re: Using Majordomo on an SGI machine In-Reply-To: <9403072112.AA01855@nowaksg.chem.nd.edu> References: <9403072112.AA01855@nowaksg.chem.nd.edu> Reply-To: drich@corp.sgi.com X-Face: >>@YIrj6h(9FH@Qs_-ob2y~:HhB3j#fE)'04Kv^h\Yc+PG%t~'xXevX509R X-Planation: X-Face can be viewed with "faces" or "xmail" (X11R5 contrib tape). Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >>>>> On Mon, 7 Mar 94 16:12:53 -0500, mike@nowaksg.chem.nd.edu (Mike Buening) said: Mike> Hi all. I'm very new to this but I was told that if I wanted to run a Mike> mail list that I should get majordomo. I've done that. And I've Mike> obviously subscribed to this list in search of wisdom. I want to run Mike> Majordomo on a SGI Personal Iris 4D/25 running IRIX 4.0.5c and would Mike> like to hear from anyone who has any similar experience to find out Mike> if there are problems I should be made aware of as I start on this Mike> journey. I have had an older version of Majordomo (1.40, if it ain't broke, don't fix it) running on an Indigo here for over a year with very few problems. Just follow the instructions, and everything should go fine. And most importantly, when it doesn't let the rest of us know... :-) -- Dan Rich | drich@corp.sgi.com | (216) 433-8624 System Support Engineer | "Danger, you haven't seen the last of me!" Silicon Graphics Inc. | "No, but the first of you turns my stomach!" NASA Lewis Research Center | -- The Firesign Theatre's Nick Danger http://www.lerc.nasa.gov/hyplan/drich From majordomo-users-owner Mon Mar 7 22:27:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA00526; Mon, 7 Mar 1994 22:27:37 GMT Received: from uu5.psi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA00520; Mon, 7 Mar 1994 14:27:26 -0800 From: pcrossma@avid.com Received: by uu5.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP; id AA24837 for ; Mon, 7 Mar 94 17:21:19 -0500 Received: from gallifrey by avid (1.37.109.4/3.2.083191-Avid Technology) id AA28089; Mon, 7 Mar 94 17:00:16 -0500 Received: by gallifrey.avid.com (931110.SGI/ASI-1.0) id AA00771; Mon, 7 Mar 94 17:00:15 -0500 Message-Id: <9403072200.AA00771@gallifrey.avid.com> Subject: Re: Using Majordomo on an SGI machine To: drich@corp.sgi.com Date: Mon, 7 Mar 1994 17:00:15 -0500 (EST) Cc: mike@nowaksg.chem.nd.edu, majordomo-users@greatcircle.com In-Reply-To: <9403072121.AA25839@sandman.lerc.nasa.gov> from "Daniel Rich" at Mar 7, 94 04:21:29 pm X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 1347 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > >>>>>> On Mon, 7 Mar 94 16:12:53 -0500, mike@nowaksg.chem.nd.edu (Mike Buening) said: > > >Mike> Hi all. I'm very new to this but I was told that if I wanted to run a >Mike> mail list that I should get majordomo. I've done that. And I've >Mike> obviously subscribed to this list in search of wisdom. I want to run >Mike> Majordomo on a SGI Personal Iris 4D/25 running IRIX 4.0.5c and would >Mike> like to hear from anyone who has any similar experience to find out >Mike> if there are problems I should be made aware of as I start on this >Mike> journey. > >I have had an older version of Majordomo (1.40, if it ain't broke, >don't fix it) running on an Indigo here for over a year with very few >problems. Just follow the instructions, and everything should go >fine. And most importantly, when it doesn't let the rest of us >know... :-) This isn't a slam, but one of the first things I'd try to do is get upgraded to 4.0.5H... When we were running 4.0.5C, we found it to be quite buggy. We are currently beta testing the IRIX 5.2 on two platforms, and personally, I think this will be the IRIX I've beeen waiting for. -- Paul Crossman "For?!? I don't work FOR Metro. Tech. Park UNIX System Manager anybody. I'm just having 1 Park West Avid Technology fun." - Dr. Who Tewksbury, MA 01876 crossman@avid.com (508) 640-3147 From majordomo-users-owner Mon Mar 7 23:24:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA00925; Mon, 7 Mar 1994 23:24:31 GMT Received: from ricohgwy.ricoh.co.jp by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA00917; Mon, 7 Mar 1994 15:24:15 -0800 Received: from cosmos.cs.ricoh.co.jp by ricohgwy.ricoh.co.jp (5.65+1.5W) id AA06848; Tue, 8 Mar 94 08:26:52 JST Received: from daisy.cs.ricoh.co.jp by cosmos.cs.ricoh.co.jp (5.67+1.6W/2.8Wb-91Jan07) id AA09734; Tue, 8 Mar 94 08:26:41 JST Received: by daisy.cs.ricoh.co.jp (4.1/6.4J.6-90sep08) id AA19310; Tue, 8 Mar 94 08:26:38 JST Date: Tue, 8 Mar 94 08:26:38 JST From: saito@daisy.cs.ricoh.co.jp (Hirohisa Saito (=?ISO-2022-JP?B?GyRCQEZGIzlANVcbKEI=?= )) Message-Id: <9403072326.AA19310@daisy.cs.ricoh.co.jp> To: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk who majordomo-users From majordomo-users-owner Tue Mar 8 02:18:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA01810; Tue, 8 Mar 1994 02:18:52 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA01804; Mon, 7 Mar 1994 18:18:38 -0800 Message-Id: <199403080218.SAA01804@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.37.109.4/16.2) id AA06438; Mon, 7 Mar 94 20:20:48 -0600 From: Larry Sheldon Subject: Resend fix To: majordomo-users@greatcircle.com Date: Mon, 7 Mar 94 20:20:48 CST Mailer: Elm [revision: 70.85] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I put in the fix suggested to resend to eat the "X-Pmrqc" and "Return-Receipt- To" headers, and to the extent that I am able to simulate the trigger-headers with elm, it seems to work. I still got a return receipt from somebody-- I assume it was sendmail or even resend--but so far only one. I'll have to wait until the Novelle-users come on-line tommorrow to know for sure if I fixed it. (I should be saying "we fixed it"--bren pointed me to the place where the hurt is. Which leads me to one of two questions--This is the second or third thing where the code has had all-lower-case literals being compared to MiXeD cAsE stuff. Is perl supposed to be case in-sensitive, or are there a lot of bugs in the literal code? ("approve would not work until I fixed some of that.) Second question--while looking up the list address for this message, I noticed a reference to a "majordomo-workers" list. Have I earned entrance to that list yet? Thanks for the help. -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . L. F. (Larry) Sheldon, Jr. . - Unix Systems Administration - . Creighton University Computer Center - Old Gym . - 2500 California Plaza - . Omaha, Nebraska, U.S.A. 68178 . - 402 280 2254 lsheldon@creighton.edu - . . - A hundred thousand lemmings can't be wrong. - .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Tue Mar 8 16:44:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA04357; Tue, 8 Mar 1994 16:44:11 GMT Received: from nd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA04351; Tue, 8 Mar 1994 08:44:03 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Tue, 8 Mar 1994 11:46:12 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA05744; Tue, 8 Mar 94 11:54:32 -0500 Date: Tue, 8 Mar 94 11:54:32 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9403081654.AA05744@nowaksg.chem.nd.edu> To: majordomo-users@greatcircle.com Subject: Getting closer Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Okay so I've got majordomo happy in it's own little world and I have sucessfully assigned myself as the majordomo-owner and someone else as the list-owner. As a test of all the functions I think I'll need at the moment I've made the test list a closed list with the presence of spanie-l.closed file in the spanie-l directory in the lists directory. Any mail directed at the majordomo-owner goes to the right place and when I sent a subscribe command for this test list to the majordomo alias the approve request was sent to the list-owner. This all sounds huncky dorey until I use the list-owner account (I'm acting as both but from different accounts for this test) to try and send the approve command to majordomo. There is a file called spanie-l.passwd in the lists directory with the password in it. But when I use the list owner account and send the following command: approve password spanie-l mike@nowaksg.chem.nd.edu end to majordomo I get back a bad list or password error and no action is taken. Am I doing something wrong or am I missing something in how this works? Is there a case-sensitive problem here (the password in the spanie-l.passwd file is lower case and I've always typed all the command lines to majordomo in lower case...) Thanks Mike | Mike Buening Why's the rich man busy dancing | | Beamer (the monster cocker) while the poor man pays the band? | | mike@nowaksg.chem.nd.edu | From majordomo-users-owner Tue Mar 8 17:20:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA04454; Tue, 8 Mar 1994 17:20:25 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA04448; Tue, 8 Mar 1994 09:20:15 -0800 From: rogerk@queernet.org Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0pe5XC-000MS1C; Tue, 8 Mar 94 09:25 PST Message-Id: To: mike@nowaksg.chem.nd.edu (Mike Buening) cc: majordomo-users@GreatCircle.COM Subject: Re: Getting closer In-reply-to: Your message of Tue, 08 Mar 94 11:54:32 -0500. <9403081654.AA05744@nowaksg.chem.nd.edu> Date: Tue, 08 Mar 94 09:25:33 PST Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > approve password spanie-l mike@nowaksg.chem.nd.edu > end > > to majordomo I get back a bad list or password error and no action is > taken. Am I doing something wrong or am I missing something in how > this works? Is there a case-sensitive problem here (the password in > the spanie-l.passwd file is lower case and I've always typed all the > command lines to majordomo in lower case...) What are you trying to approve? The syntax is approve For example, approve foobar subscribe spanie-l mike@nowaksg.chem.nd.edu --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Tue Mar 8 18:10:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA04631; Tue, 8 Mar 1994 18:10:29 GMT Received: from dragonfly.cis.ufl.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA04625; Tue, 8 Mar 1994 10:10:18 -0800 Received: from localhost by dragonfly.cis.ufl.edu (8.6.4/4.11) id NAA12530; Tue, 8 Mar 1994 13:12:33 -0500 Message-Id: <199403081812.NAA12530@dragonfly.cis.ufl.edu> To: mike@nowaksg.chem.nd.edu (Mike Buening) cc: majordomo-users@greatcircle.com Subject: Re: Getting closer In-reply-to: Some random ramblings on Tue, 08 Mar 1994 11:54:32 -0500. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Tue, 08 Mar 1994 13:12:32 EST From: Stephen P Potter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused mike@nowaksg.chem.nd.edu (Mike Buening) to writ e: | | approve password spanie-l mike@nowaksg.chem.nd.edu | end | This should be: approve password subscribe spanie-l mike@nowaksg.chem.nd.edu Steve From majordomo-users-owner Tue Mar 8 19:25:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA05123; Tue, 8 Mar 1994 19:25:12 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA05115; Tue, 8 Mar 1994 11:25:04 -0800 Message-Id: <199403081925.LAA05115@mycroft.GreatCircle.COM> To: Larry Sheldon cc: majordomo-users@greatcircle.com Subject: Re: Resend fix In-reply-to: Your message of Mon, 7 Mar 94 20:20:48 CST Date: Tue, 08 Mar 1994 11:25:03 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Larry Sheldon writes: # I put in the fix suggested to resend to eat the "X-Pmrqc" and "Return-Receipt # - # To" headers, and to the extent that I am able to simulate the trigger-headers # with elm, it seems to work. I still got a return receipt from somebody-- # I assume it was sendmail or even resend--but so far only one. I'll have # to wait until the Novelle-users come on-line tommorrow to know for sure if I # fixed it. (I should be saying "we fixed it"--bren pointed me to the place # where the hurt is. # # Which leads me to one of two questions--This is the second or third thing # where the code has had all-lower-case literals being compared to MiXeD cAsE # stuff. Is perl supposed to be case in-sensitive, or are there a lot of # bugs in the literal code? ("approve would not work until I fixed some of # that.) Most of the matches in "resend" (and the rest of Majordomo, for that matter) have the "i" option specified (i.e., they're something like "/^keyword:/i"); this tells Perl to do a case-insensitive match. # Second question--while looking up the list address for this message, I notice # d # a reference to a "majordomo-workers" list. Have I earned entrance to that # list yet? It's not a closed-membership list, and anybody who wants to join is welcome there. It's mainly where we talk about nitty-gritty fixes and features for future releases and so forth. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Tue Mar 8 11:41:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA05232; Tue, 8 Mar 1994 19:30:10 GMT Received: from de5.ctd.ornl.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA05212; Tue, 8 Mar 1994 11:29:59 -0800 Received: from localhost (de5@localhost) by de5.ctd.ornl.gov (8.6.5/8.6.5) id OAA02716; Tue, 8 Mar 1994 14:32:35 -0500 Date: Tue, 8 Mar 1994 14:32:35 -0500 From: Dave Sill Message-Id: <199403081932.OAA02716@de5.ctd.ornl.gov> To: mike@nowaksg.chem.nd.edu (Mike Buening) Cc: majordomo-users@GreatCircle.COM Subject: Getting closer In-Reply-To: <9403081654.AA05744@nowaksg.chem.nd.edu> References: <9403081654.AA05744@nowaksg.chem.nd.edu> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >But when I use the list >owner account and send the following command: > >approve password spanie-l mike@nowaksg.chem.nd.edu >end > >to majordomo I get back a bad list or password error and no action is >taken. Am I doing something wrong or am I missing something in how >this works? What are you trying to do? The above approve command looks like a subscribe or unsubscribe missing the appropriate keyword. I though you said subscribes were working, though. Perhaps you're trying to send something out to a moderated list? If so, show us your aliases. If you are trying to send to a moderated list, you don't send your submission to majordomo, you send to the list address. And you don't use an approve *command*, you add an Approved header. -- Dave Sill (de5@ornl.gov) I dream of a televisionland where it will be Martin Marietta Energy Systems as hard for a network to expose us to violence Workstation Support as it is for me to tell someone they have spinach on their teeth. --Paula Poundstone URL http://www.dec.com/pub/DEC/DECinfo/html/dsill.html From majordomo-users-owner Tue Mar 8 21:21:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA06032; Tue, 8 Mar 1994 21:21:06 GMT Received: from nd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA05643; Tue, 8 Mar 1994 12:29:17 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Tue, 8 Mar 1994 15:31:58 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA06692; Tue, 8 Mar 94 15:40:19 -0500 Date: Tue, 8 Mar 94 15:40:19 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9403082040.AA06692@nowaksg.chem.nd.edu> To: Dave Sill Subject: Re: Getting closer Cc: majordomo-users@greatcircle.com References: <9403081654.AA05744@nowaksg.chem.nd.edu> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >What are you trying to do? The above approve command looks like a >subscribe or unsubscribe missing the appropriate keyword. That's exactly what it was but that was a typo...I sent the proper command to majordomo (and I resent it to double check). >I though you said subscribes were working, though. What's really happening is that I've created a closed list and when I said that the subscribe was working I meant that when I send a subscribe message to majordomo I get the appropriate response that the request was sent to the list owner. And the list owner gets the APPROVE request. The problem is that when the list owner sends the approve command it isn't accepted and I'm not sure why. Here's the list as I've set it up thus far: drwxrwxr-x 2 majordomonowak 512 Mar 7 16:51 spanie-l/ -rw-rw-r-- 1 majordomonowak 0 Mar 7 22:51 spanie-l.closed -rw-rw-r-- 1 majordomonowak 91 Mar 7 22:50 spanie-l.info -rw-rw-r-- 1 majordomonowak 7 Mar 7 22:48 spanie-l.passwd spanie-l.passwd: buffer This is the full contents of the listdir for majordomo as I've set it up. The aliases I've used are thus: #Majordomo aliases for running lists list-server: "|/usr/people/majordomo/majordomo/wrapper majordomo" list-server-owner:mike owner-list-server:mike #Specific for Spanie-L list spanie-l:"/usr/people/majordomo/majordomo/wrapper resend -p bulk -M 10000 -l smapie-l -f spanie-l-owner -h nowaksg.chem.nd.edu -s spanie-l-outgoing" owner-spanie-l:spanie-l-owner spanie-l-outgoing: :include:/usr/people/majordomo/majordomo/lists/spanie-l owner-spanie-l-outgoing:spanie-l-owner #spanie-l-archive: /usr/people/majordomo/majordomo/archive/spanie-l spanie-l-request: "|/usr/people/majordomo/majordomo/wrapper request-answer spanie-l" owner-spanie-l-request:spanie-l-owner spanie-l-approval:spanie-l-owner spanie-l-owner:ruth owner-spanie-l-owner:spanie-l-owner So I don't see where the error is coming from. I haven't yet tried this as a open list. Following is a copy of the error message I get from majordomo: >>>> approve buffer subscribe spanie-l mike@nowaksg.chem.nd.edu **** approve: invalid list or password. >>>> end END OF COMMANDS Any thoughts? Mike | Mike Buening Why's the rich man busy dancing | | Beamer (the monster cocker) while the poor man pays the band? | | mike@nowaksg.chem.nd.edu | From majordomo-users-owner Tue Mar 8 21:50:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA06172; Tue, 8 Mar 1994 21:50:56 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA06166; Tue, 8 Mar 1994 13:50:45 -0800 From: rogerk@queernet.org Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0pe9ky-000MS8C; Tue, 8 Mar 94 13:56 PST Message-Id: To: mike@nowaksg.chem.nd.edu (Mike Buening) cc: majordomo-users@GreatCircle.COM Subject: Re: Getting closer In-reply-to: Your message of Tue, 08 Mar 94 15:40:19 -0500. <9403082040.AA06692@nowaksg.chem.nd.edu> Date: Tue, 08 Mar 94 13:56:03 PST Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Here's the list as I've set it up thus far: > > drwxrwxr-x 2 majordomonowak 512 Mar 7 16:51 spanie-l/ > -rw-rw-r-- 1 majordomonowak 0 Mar 7 22:51 spanie-l.closed > -rw-rw-r-- 1 majordomonowak 91 Mar 7 22:50 spanie-l.info > -rw-rw-r-- 1 majordomonowak 7 Mar 7 22:48 spanie-l.passwd Why is "spanie-l" a directory? It should be a simple file, which contains the list itself. > I haven't yet tried this as a open list. Following is a copy of the > error message I get from majordomo: > > >>>> approve buffer subscribe spanie-l mike@nowaksg.chem.nd.edu > **** approve: invalid list or password. > >>>> end > END OF COMMANDS > > Any thoughts? Yup. "spanie-l" is an invalid list, because $listdir/spanie-l is not the list file. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Tue Mar 8 23:53:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA07070; Tue, 8 Mar 1994 23:53:14 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA07064; Tue, 8 Mar 1994 15:52:58 -0800 Message-Id: <199403082352.PAA07064@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.37.109.4/16.2) id AA14001; Tue, 8 Mar 94 17:55:02 -0600 From: Larry Sheldon Subject: Re: Your mail to jaynet-forum-request@bluejay To: cferrin@pigeon.creighton.edu Date: Tue, 8 Mar 94 17:54:58 CST Cc: majordomo-users@greatcircle.com In-Reply-To: ; from "Chuck Ferrin" at Mar 8, 94 5:05 pm Mailer: Elm [revision: 70.85] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > Hi Larry, > > I seem to be getting alot of these! About 30 so far. > > Is this a result of the confirm reading test I sent to the list? > Why would confirm reading give this command to the listserver? > > Or did you purposely add this hack to serve me right!! ha ha? :-) > I don't know why in hell those things come out--I get one every once in a while. I don't know enough about the code to figure it out -- and I don't thing the header hack had anything to do with it--who knows? I think I'll cc the majordomo wizards list to see if anybody has an idea. I could use an idea. Just had one! All the traffic for univcoll is finally timing out--I wonder if these damn things are triggered by a bounce to majordomo? There is never a clue in them as to what it is bellaching about. > > > ------- Forwarded Message Follows ------- > > Date sent: Tue, 8 Mar 94 17:59:17 -0500 > From: jaynet-forum-request@bluejay.creighton.edu > To: Postmaster@atlas.creighton.edu > Subject: Your mail to jaynet-forum-request@bluejay > Send reply to: jaynet-forum-approval@bluejay.creighton.edu > > This pre-recorded message is being sent in response to your recent > email to jaynet-forum-request@bluejay. > > All routine administrative requests (including subscriptions and > unsubscriptions) concerning this mailing list are handled by an > automated server. Please read this message carefully to find the > information relevant to you. > > SUBSCRIBING > =========== > > To subscribe to jaynet-forum, send the following in the body (not > the subject line) of an email message to "majordomo@bluejay": > > subscribe jaynet-forum > > This will subscribe the account from which you send the message to > the jaynet-forum list. > > If you wish to subscribe another address instead (such as a local > redistribution list), you can use a command of the form: > > subscribe jaynet-forum other-address@your_site.your_net > > UNSUBSCRIBING > ============= > > To unsubscribe from jaynet-forum, send the following in the body (not > the subject line) of an email message to "majordomo@bluejay": > > unsubscribe jaynet-forum > > This will unsubscribe the account from which you send the message. > If you are subscribed with some other address, you'll have to send > a command of the following form instead: > > unsubscribe jaynet-forum other-address@your_site.your_net > > If you don't know what address you are subscribed with, you can send > the following command to see who else is on the list (assuming that > information isn't designated "private" by the owner of the list):o > > who jaynet-forum > > If you want to search non-privte lists at this server, you can do that > by sending a command like: > > which string > > This will return a list of all entries on all lists that contain "string". > > HELP > ==== > > To find out more about the automated server and the commands it > understands, send the following command to "majordomo@bluejay": > > help > > If you feel you need to reach a human, send email to > > jaynet-forum-approval@bluejay > > > > CUL > > _____________________________________________________ > Chuck Ferrin - Creighton University > Omaha Nebraska > cferrin@creighton.edu > -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . L. F. (Larry) Sheldon, Jr. . - Unix Systems Administration - . Creighton University Computer Center - Old Gym . - 2500 California Plaza - . Omaha, Nebraska, U.S.A. 68178 . - 402 280 2254 lsheldon@creighton.edu - . . - A hundred thousand lemmings can't be wrong. - .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Thu Mar 10 22:13:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA18197; Thu, 10 Mar 1994 22:13:52 GMT Received: from ag.srnr.Arizona.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA18190; Thu, 10 Mar 1994 14:13:44 -0800 Received: by ag.srnr.Arizona.EDU (5.0/SMI-SVR4) id AA01381; Thu, 10 Mar 1994 15:15:53 +0700 Date: Thu, 10 Mar 1994 15:15:53 +0700 From: schmitt@ag.srnr.Arizona.EDU (Jennifer A. Schmitt) Message-Id: <9403102215.AA01381@ ag.srnr.Arizona.EDU> To: majordomo-users@greatcircle.com Subject: index X-Sun-Charset: US-ASCII content-length: 469 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk It seems as if the index command will give anyone a list of archive files for any group. What about those lists where you don't want anyone reading the info? Thanks, Jennifer Schmitt ---- Jennifer A. Schmitt College of Agriculture schmitt@ag.srnr.arizona.edu University of Arizona +1 602 621 2489 BioSciences East 204B Tucson, AZ 85721 From majordomo-users-owner Fri Mar 11 03:11:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id DAA19322; Fri, 11 Mar 1994 03:11:31 GMT Received: from nd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA19316; Thu, 10 Mar 1994 19:11:22 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Thu, 10 Mar 1994 22:11:05 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA14273; Thu, 10 Mar 94 22:19:29 -0500 Date: Thu, 10 Mar 94 22:19:29 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9403110319.AA14273@nowaksg.chem.nd.edu> To: majordomo-users@greatcircle.com Subject: Permission troubles Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Okay...I'm sorry if some of my other questions have been to simplistic but I've reached a point where I don't know where to go again: I've setup an open list (removing the approve step from the process to find out if basic subscribe for an open list will work) and I can't subscribe to it. First of all, it takes an incredible amount of time for majordomo to respond (because there is a permission problem in the shlock.pl script) and when I do finally get a reply it tells me that: can't append to /usr/people/majordomo/majordomo/lists/spanie-l: Permission denied And when I look at the actual spool files in the mail queue I see a very large file which tells me that shlock.pl has a permission denied error at line 131. I'm not sure why this occurs but I've a couple of questions: 1) since I am appearantly supposed to compile wrapper with the POSIX flags on why is the uid set to 1 and the gid to 15? What does this do for it? I had thought that it was supposed to setuid to root (which has a uid of 0) and if it were suid root then file permissions (except for write) should matter little. And 2) if majordomo owns the spanie-l file and it is user and group writable and readable why can't it append to the file? Unless the uid being set to 1 causes trouble (I think uid 1 is for daemon which I guess wouldn't have permission although I've moved majordomo to group daemon...) Mike | Mike Buening Why's the rich man busy dancing | | Beamer (the monster cocker) while the poor man pays the band? | | mike@nowaksg.chem.nd.edu | From majordomo-users-owner Fri Mar 11 13:32:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA21384; Fri, 11 Mar 1994 13:32:56 GMT Received: from nd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA21378; Fri, 11 Mar 1994 05:32:48 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Fri, 11 Mar 1994 08:32:30 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA14742; Fri, 11 Mar 94 08:40:55 -0500 Date: Fri, 11 Mar 94 08:40:55 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9403111340.AA14742@nowaksg.chem.nd.edu> To: majordomo-users@greatcircle.com Subject: It works! Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Okay...that last bit of advice seems to have fixed it. I'll admit I'm still very confused (but that's not the point of this group...getting majordomo is...). Once I changed the W_GID to the daemon group in the Makefile and left the wrapper as owner root (this I certainly don't under- stand) I can now easily subscribe to the open list. Now to test a closed list. So it seems to me that a private list will only allow those who belong to the list to use the who command...but I'm curious if there is a way in which only those with the list.passwd could use the who command? In addition to using majordomo to create a mail list I'm also interested in using it to handle invitation to a closed talker. This way I could have a committee of wizards who would all have approve capabilities on the "mail list" and I'd be apprised of new users but we wouldn't want the users to be able to get a list of all the other users (especially since the email addresses would be included). Is this possible with majordomo or is it possible to disable the who command from a list entirely? Thanks again for all your help. Mike | Mike Buening Why's the rich man busy dancing | | Beamer (the monster cocker) while the poor man pays the band? | | mike@nowaksg.chem.nd.edu | From majordomo-users-owner Fri Mar 11 14:07:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA21492; Fri, 11 Mar 1994 14:07:57 GMT Received: from zaphod.b17d.ingr.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA21486; Fri, 11 Mar 1994 06:07:37 -0800 Received: by zaphod.b17d.ingr.com (5.65c/1.921207) id AA04109; Fri, 11 Mar 1994 08:07:19 -0600 From: mgpalmer@zaphod.b17d.ingr.com (Michael Palmer) Message-Id: <199403111407.AA04109@zaphod.b17d.ingr.com> Subject: Re: index To: majordomo-users@greatcircle.com Date: Fri, 11 Mar 94 8:07:17 CST Cc: schmitt@ag.srnr.Arizona.EDU (Jennifer A. Schmitt) Reply-To: mgpalmer@zaphod.b17d.ingr.com (Michael G. Palmer) In-Reply-To: <9403102215.AA01381@ ag.srnr.Arizona.EDU>; from "Jennifer A. Schmitt" at Mar 10, 94 3:15 pm X-Mailer: ELM [version 07.00.00.00 (2.3 PL11)] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk said: >It seems as if the index command will give anyone a list of archive >files for any group. What about those lists where you don't want >anyone reading the info? I don't seem to have this problem on my majordomo server. Here is the output from an index command that I sent to majordomo from an account not in the wc list. >>>> index wc **** List 'wc' is a private list. **** Only members of the list can do an 'index'. **** You aren't a member of list 'wc'. >Jennifer Schmitt >---- >Jennifer A. Schmitt College of Agriculture >schmitt@ag.srnr.arizona.edu University of Arizona >+1 602 621 2489 BioSciences East 204B -- Michael G. Palmer DoD#0886 In the landscape of spring, there is neither better nor worse. The flowering branches grow, some short, some long. -- Zen proverb From majordomo-users-owner Fri Mar 11 15:04:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA21658; Fri, 11 Mar 1994 15:04:30 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA21652; Fri, 11 Mar 1994 07:04:23 -0800 From: rogerk@queernet.org Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0pf8mx-000MSHC; Fri, 11 Mar 94 07:06 PST Message-Id: To: mike@nowaksg.chem.nd.edu (Mike Buening) cc: majordomo-users@GreatCircle.COM Subject: Re: It works! In-reply-to: Your message of Fri, 11 Mar 94 08:40:55 -0500. <9403111340.AA14742@nowaksg.chem.nd.edu> Date: Fri, 11 Mar 94 07:06:10 PST Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > So it seems to me that a private list will only allow those who belong to > the list to use the who command...but I'm curious if there is a way in > which only those with the list.passwd could use the who command? I have a patch which does this, and I can get it to you; I hope John et al. are planning on it for 2.0 as well. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Fri Mar 11 19:26:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA23040; Fri, 11 Mar 1994 19:26:12 GMT Received: from welch.ncd.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA23034; Fri, 11 Mar 1994 11:26:03 -0800 Received: from bryant.ncd.com (mfrost@bryant.ncd.com [192.43.159.209]) by welch.ncd.com (8.6.5/8.6.5) with ESMTP id LAA02789 for ; Fri, 11 Mar 1994 11:26:00 -0800 Received: from localhost (mfrost@localhost) by bryant.ncd.com (8.6.5/8.6.5.Beta11) id LAA28790 for majordomo-users@greatcircle.com; Fri, 11 Mar 1994 11:25:58 -0800 From: "Mark Frost" Message-Id: <9403111125.ZM28788@bryant.ncd.com> Date: Fri, 11 Mar 1994 11:25:58 -0800 X-Mailer: Z-Mail (3.0.1 23feb94) To: majordomo-users@greatcircle.com Subject: What is causing this? Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have found that I need to have two majordomo's running internally: one for mailing lists that are to be used by those inside the company only and one for mailing lists that are open to those outside the company. I can't find a way to prevent someone from outside the company from probing the company proprietary mailing lists. So I created a second server called "domo" and moved the restricted lists there. So I just attempted to send the message below to 3 internal aliases and I always get a "BOUNCE listname@ncd.com: Admin request" message sent back to me. However, when I send a message that has a simple "test" type message in the body with a subject of something like "test #3" it works fine. It's as if the content of my message to the mailing list will make it generate one of these "BOUNCE" messages. I'm totally confused. Thanks -mark frost network computing devices ---- begin ---- It has been indicated that "domo" is perhaps a little too cryptic for the general public to use to get mailing list administration done. I have created an alias for it called "lists". So to subscribe/unsubscribe or get general info about mailing lists, you can send to either "domo@ncd.com" or "lists@ncd.com". The same is true for contacting the person who administers the main majordomo server as well ("domo-owner@ncd.com" or "lists-owner@ncd.com"). -mark --- end ---- From majordomo-users-owner Sat Mar 12 00:03:16 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA23665; Sat, 12 Mar 1994 00:03:16 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA23659; Fri, 11 Mar 1994 16:03:06 -0800 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA12901 (5.65c/IDA-1.4.4 for ); Fri, 11 Mar 1994 19:00:18 -0500 Message-Id: <199403120000.AA12901@cs.umb.edu> To: rogerk@queernet.org Cc: mike@nowaksg.chem.nd.edu (Mike Buening), majordomo-users@greatcircle.com Subject: Re: It works! In-Reply-To: Your message of "Fri, 11 Mar 1994 07:06:10 PST." Date: Fri, 11 Mar 1994 19:00:17 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , rogerk@queernet.org writes: > > So it seems to me that a private list will only allow those who belong to > > the list to use the who command...but I'm curious if there is a way in > > which only those with the list.passwd could use the who command? > > I have a patch which does this, and I can get it to you; I hope John et al. > are planning on it for 2.0 as well. Actually there is no et. al. yet. I hope there will be, but et. al, hasn't materialized. In any case, the answer is yes and no. There will be a password ability, but since the file .password is no longer required (and you don't want to advertize that password anyway since it would allow anybody in the world to reconfigure your list), it will be handled in the config file by an extention to the private_who configuration option. The syntax will be: private_who = {yes|no|word} Where word is the password to be used to activate the who function. The question is what will allow the use of the password. As the spec for 2.0 currently stands, approve becomes table driven, so: approve password who listname is the preferred command. private_index, private_get, private_info would all work the same as well. Requiring a password for private_which is also possible, but it would limit the use of which to only one list. -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Sat Mar 12 02:26:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA24422; Sat, 12 Mar 1994 02:26:46 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA24415; Fri, 11 Mar 1994 18:26:40 -0800 Message-Id: <199403120226.SAA24415@mycroft.GreatCircle.COM> To: "Mark Frost" cc: majordomo-users@greatcircle.com Subject: Re: What is causing this? In-reply-to: Your message of Fri, 11 Mar 1994 11:25:58 -0800 Date: Fri, 11 Mar 1994 18:26:39 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Mark Frost" writes: # # I have found that I need to have two majordomo's running internally: one # for mailing lists that are to be used by those inside the company only and # one for mailing lists that are open to those outside the company. I # can't find a way to prevent someone from outside the company from probing # the company proprietary mailing lists. So I created a second server # called "domo" and moved the restricted lists there. # # So I just attempted to send the message below to 3 internal aliases and I # always get a "BOUNCE listname@ncd.com: Admin request" message sent back to # me. However, when I send a message that has a simple "test" type message # in the body with a subject of something like "test #3" it works fine. # # It's as if the content of my message to the mailing list will make it generat # e # one of these "BOUNCE" messages. I'm totally confused. # # Thanks # # -mark frost # network computing devices # # # ---- begin ---- # # It has been indicated that "domo" is perhaps a little too cryptic for # the general public to use to get mailing list administration done. I have # created an alias for it called "lists". So to subscribe/unsubscribe or # get general info about mailing lists, you can send to either # "domo@ncd.com" or "lists@ncd.com". # # The same is true for contacting the person who administers the main majordomo # server as well ("domo-owner@ncd.com" or "lists-owner@ncd.com"). # # -mark # # --- end ---- You're running "resend" with the "-s" flag, which tells Majordomo to "enable administrivia checks". One of these heuristics is to check for the word "subscribe" anywhere in the first 5 lines of the body of a message. Your message has "subscribe" on line 3... So, to get around this, either turn off the administrivia checks (drop the "-s" argument to "resend"), or set up an approval password for the list (a "-a" argument to resend) and "approve" the message that's being bounced (see the "resend.README" file and/or the "approve" perl script). -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Sun Mar 13 20:21:15 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA01627; Sun, 13 Mar 1994 20:21:15 GMT Received: from nd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA01621; Sun, 13 Mar 1994 12:21:08 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Sun, 13 Mar 1994 15:20:34 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA19752; Sun, 13 Mar 94 15:29:00 -0500 Date: Sun, 13 Mar 94 15:29:00 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9403132029.AA19752@nowaksg.chem.nd.edu> To: majordomo-users@greatcircle.com Subject: What's wrong with this line? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I changed the test list I've been setting up and I'm currently using the following line in the aliases file: spanie-l:"|/usr/people/majordomo/majordomo/wrapper resend -p bulk -M 10000 \ -l spanie-l -h nowaksg.chem.nd.edu -f spanie-l -s spanie-l-outgoing \ -r spanie-l@nowaksg.chem.nd.edu" But I'm getting a loop and the message shows up at least 20 times before I can try and kill it from the spooler. What I had been using was simply: spanie-l: :include:/usr/people/majordomo/majordomo/lists/spanie-l and the messages were being delivered. However, I want to be able to specify the -r and -f flags so I used the first line. What am I doing wrong? Mike | Mike Buening Why's the rich man busy dancing | | Beamer (the monster cocker) while the poor man pays the band? | | mike@nowaksg.chem.nd.edu | From majordomo-users-owner Sun Mar 13 21:12:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA01762; Sun, 13 Mar 1994 21:12:14 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA01755; Sun, 13 Mar 1994 13:12:08 -0800 Message-Id: <199403132112.NAA01755@mycroft.GreatCircle.COM> To: mike@nowaksg.chem.nd.edu (Mike Buening) cc: majordomo-users@greatcircle.com Subject: Re: What's wrong with this line? In-reply-to: Your message of Sun, 13 Mar 94 15:29:00 -0500 Date: Sun, 13 Mar 1994 13:12:07 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk mike@nowaksg.chem.nd.edu (Mike Buening) writes: # # I changed the test list I've been setting up and I'm currently using the # following line in the aliases file: # # spanie-l:"|/usr/people/majordomo/majordomo/wrapper resend -p bulk -M 10000 \ # -l spanie-l -h nowaksg.chem.nd.edu -f spanie-l -s spanie-l-outgoing \ # -r spanie-l@nowaksg.chem.nd.edu" # # But I'm getting a loop and the message shows up at least 20 times before I # can try and kill it from the spooler. The name of the real list ("spanie-l-outgoing", in this case) needs to be the VERY LAST argument. It's reading "spanie-l@nowaksg.chem.nd.edu" as the name of the list to send to, and looping. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Mon Mar 14 03:11:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA04366; Mon, 14 Mar 1994 10:41:09 GMT Received: from nova.unix.portal.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA04360; Mon, 14 Mar 1994 02:41:00 -0800 Received: from jobe.shell.portal.com (jobe.shell.portal.com [156.151.1.104]) by nova.unix.portal.com (8.6.4/8.6.5) with ESMTP id CAA02453 for ; Mon, 14 Mar 1994 02:42:01 -0800 Received: from localhost (chan@localhost) by jobe.shell.portal.com (8.6.4/8.6.4) id CAA13511 for majordomo-users@greatcircle.com; Mon, 14 Mar 1994 02:42:00 -0800 Date: Mon, 14 Mar 1994 02:42:00 -0800 From: Jeff Chan Message-Id: <199403141042.CAA13511@jobe.shell.portal.com> To: majordomo-users@greatcircle.com Subject: newbie question: uid, gid Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm trying to set up majordomo here under my home directory with me as the owner of everything (as opposed to daemon and majordom for wrapper as Brent recommends). So far sendmail/wrapper/majordomo seems unable to see any wrapper environment variables like $whereami, etc. wrapper perms were tried at 4755 (the Makefile default), 777, and 755. wrapper gid is mine & owner is me. (Admittedly with non-4000 wrapper perms, this might conflict with sendmail's perms.) I am a trusted user, though my system administrator tells me that sendmail has ignored this for several versions. Unfortunately I do not have root priviledges, which complicates setting up & debugging considerably. home & list directory and file perms are all 777 for now. Any suggestions would be appreciated. Has anyone gotten theirs to run without doing chown or chgrp? Oh yes, my machine is running SunOS 4.1.3 & majordomo version is the latest released, 1.62. Jeff Chan chan@shell.portal.com From majordomo-users-owner Mon Mar 14 14:20:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA05039; Mon, 14 Mar 1994 14:20:14 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA05033; Mon, 14 Mar 1994 06:20:05 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id JAA21652; Mon, 14 Mar 1994 09:19:51 -0500 Message-Id: <199403141419.JAA21652@bosnia.pop.psu.edu> To: mike@nowaksg.chem.nd.edu (Mike Buening) cc: majordomo-users@GreatCircle.COM Subject: Re: What's wrong with this line? In-reply-to: Your message of "Sun, 13 Mar 1994 15:29:00 EST." <9403132029.AA19752@nowaksg.chem.nd.edu> 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 X-Mailer: exmh version 1.3beta 2/17/94 Date: Mon, 14 Mar 1994 09:19:50 -0500 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9403132029.AA19752@nowaksg.chem.nd.edu>, Mike Buening writes: > >I changed the test list I've been setting up and I'm currently using the >following line in the aliases file: > >spanie-l:"|/usr/people/majordomo/majordomo/wrapper resend -p bulk -M 10000 \ >-l spanie-l -h nowaksg.chem.nd.edu -f spanie-l -s spanie-l-outgoing \ ^^^^^^^^^^^ >-r spanie-l@nowaksg.chem.nd.edu" Note that this is a very bad idea. With this, any bounce messages will be sent back to the list, with rather nasty results. You want "-f owner-spanie-l" --Dave From majordomo-users-owner Mon Mar 14 21:35:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA06919; Mon, 14 Mar 1994 21:35:29 GMT Received: from nd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA06913; Mon, 14 Mar 1994 13:35:15 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Mon, 14 Mar 1994 16:34:39 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA22565; Mon, 14 Mar 94 16:43:08 -0500 Date: Mon, 14 Mar 94 16:43:08 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9403142143.AA22565@nowaksg.chem.nd.edu> To: majordomo-users@greatcircle.com Subject: New-list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm not yet sure how to implement the new-list program. What is the syntax of the alias when you use new-list? I couldn't find it in any of the instructions. Mike | Mike Buening Why's the rich man busy dancing | | Beamer (the monster cocker) while the poor man pays the band? | | mike@nowaksg.chem.nd.edu | From majordomo-users-owner Mon Mar 14 21:43:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA06989; Mon, 14 Mar 1994 21:43:29 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA06983; Mon, 14 Mar 1994 13:43:14 -0800 Received: from [192.102.132.29] by sgi.sgi.com via SMTP (931110.SGI/910110.SGI) for Majordomo-Users@GreatCircle.COM id AA19351; Mon, 14 Mar 94 13:43:06 -0800 Received: by questa.esd.sgi.com (931110.SGI/930416.SGI.AUTO) for @sgi.sgi.com:Majordomo-Users@GreatCircle.COM id AA11620; Mon, 14 Mar 94 13:39:50 -0800 From: "Mats Wichmann (mipsABI Consultant)" Message-Id: <9403141339.ZM11618@questa.esd.sgi.com> Date: Mon, 14 Mar 1994 13:39:37 -0800 X-Mailer: Z-Mail (3.1.0 22feb94 MediaMail) To: Majordomo-Users@GreatCircle.COM Subject: maling list with seq.# in Subject Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We've got some mailing lists over here that are being transferred to a new home from the now-defunct Unix International. The lists have been all converted over to Majordomo and are working. However, there's a function the old lists had which there's some desire to preserve: the subject line had a sequence number automatically inserted by the list server so it would look something like this for listname "sample": >Subject: (sample 1357) This is a dummy subject Brent suggested that adding something to "resend" might be the way to go; does anyone have a working implementation of something like this they might want to share? (I'm not on this mailing list, so sending a reply directly to me would be appreciated). thanks, Mats Wichmann // Consultant mats@esd.sgi.com - current home mats@netcom.com - permanent home From majordomo-users-owner Mon Mar 14 22:10:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA07094; Mon, 14 Mar 1994 22:10:06 GMT Received: from zaphod.b17d.ingr.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA07071; Mon, 14 Mar 1994 14:09:45 -0800 Received: by zaphod.b17d.ingr.com (5.65c/1.921207) id AA22618; Mon, 14 Mar 1994 16:10:03 -0600 From: mgpalmer@zaphod.b17d.ingr.com (Michael Palmer) Message-Id: <199403142210.AA22618@zaphod.b17d.ingr.com> Subject: Re: New-list To: majordomo-users@greatcircle.com Date: Mon, 14 Mar 94 16:10:01 CST Reply-To: mgpalmer@zaphod.b17d.ingr.com (Michael G. Palmer) X-Mailer: ELM [version 07.00.00.00 (2.3 PL11)] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk said: >I'm not yet sure how to implement the new-list program. What is the >syntax of the alias when you use new-list? I couldn't find it in any of >the instructions. I have never used the new-list program, so I feel qualified to answer your question :) It appears that it should be invoked by sendmail by including a line like the following in your /usr/lib/aliases (or equivalent) file. list_name: "| /usr/majordom/mjdm/wrapper new-list" -or- list_name: "| /usr/majordom/mjdm/new-list" (?) to be invoked whenever mail is sent to the list before it is open for business. Later, when the list is open for business, it would be replaced by list_name: "include:/usr/majordom/lists/list_name" (your pathnames are quite probably different.) -- Michael G. Palmer DoD#0886 In the landscape of spring, there is neither better nor worse. The flowering branches grow, some short, some long. -- Zen proverb Mail to wn-l-request@zaphod.b17d.ingr.com for weird news mailing list info. From majordomo-users-owner Tue Mar 15 01:57:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA07766; Tue, 15 Mar 1994 01:57:09 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA07760; Mon, 14 Mar 1994 17:57:00 -0800 Message-Id: <199403150157.RAA07760@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.37.109.4/16.2) id AA13061; Mon, 14 Mar 94 19:56:15 -0600 From: Larry Sheldon Subject: unidentifiable message going to inexplicable destination To: majordomo-users@greatcircle.com Date: Mon, 14 Mar 94 19:56:14 CST Mailer: Elm [revision: 70.85] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I an still trying to figure out what causes majordomo to blat these out--now I _also_ get to figure out why they are looping. Any ideas at all? > > ----- Transcript of session follows ----- > 550 MAILER-DAEMON@bluejay.creighton.edu... User unknown > > ----- Unsent message follows ----- > Received: by bluejay.creighton.edu > (1.37.109.4/16.2) id AA23044; Mon, 14 Mar 94 18:16:05 -0500 > Date: Mon, 14 Mar 94 18:16:05 -0500 > From: jaynet-forum-request@bluejay.creighton.edu > Return-Path: > To: MAILER-DAEMON@bluejay.creighton.edu > Subject: Your mail to jaynet-forum-request@bluejay > In-Reply-To: , from Mail Delivery Subsystem > Reply-To: jaynet-forum-approval@bluejay.creighton.edu > > This pre-recorded message is being sent in response to your recent > email to jaynet-forum-request@bluejay. > > All routine administrative requests (including subscriptions and > unsubscriptions) concerning this mailing list are handled by an > automated server. Please read this message carefully to find the > information relevant to you. > > SUBSCRIBING > =========== > > To subscribe to jaynet-forum, send the following in the body (not > the subject line) of an email message to "majordomo@bluejay": > > subscribe jaynet-forum > > This will subscribe the account from which you send the message to > the jaynet-forum list. > > If you wish to subscribe another address instead (such as a local > redistribution list), you can use a command of the form: > > subscribe jaynet-forum other-address@your_site.your_net > > UNSUBSCRIBING > ============= > > To unsubscribe from jaynet-forum, send the following in the body (not > the subject line) of an email message to "majordomo@bluejay": > > unsubscribe jaynet-forum > > This will unsubscribe the account from which you send the message. > If you are subscribed with some other address, you'll have to send > a command of the following form instead: > > unsubscribe jaynet-forum other-address@your_site.your_net > > If you don't know what address you are subscribed with, you can send > the following command to see who else is on the list (assuming that > information isn't designated "private" by the owner of the list):o > > who jaynet-forum > > If you want to search non-privte lists at this server, you can do that > by sending a command like: > > which string > > This will return a list of all entries on all lists that contain "string". > > HELP > ==== > > To find out more about the automated server and the commands it > understands, send the following command to "majordomo@bluejay": > > help > > If you feel you need to reach a human, send email to > > jaynet-forum-approval@bluejay > > -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . L. F. (Larry) Sheldon, Jr. . - Unix Systems Administration - . Creighton University Computer Center - Old Gym . - 2500 California Plaza - . Omaha, Nebraska, U.S.A. 68178 . - 402 280 2254 lsheldon@creighton.edu - . . - A hundred thousand lemmings can't be wrong. - .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Tue Mar 15 15:11:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA10429; Tue, 15 Mar 1994 15:11:07 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA10423; Tue, 15 Mar 1994 07:10:59 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id KAA02995; Tue, 15 Mar 1994 10:10:53 -0500 Message-Id: <199403151510.KAA02995@bosnia.pop.psu.edu> To: majordomo-users@GreatCircle.COM Cc: Larry Sheldon Subject: Re: unidentifiable message going to inexplicable destination In-reply-to: Your message of "Mon, 14 Mar 1994 19:56:14 CST." <199403150157.RAA07760@mycroft.GreatCircle.COM> 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 X-Mailer: exmh version 1.3beta 2/17/94 Date: Tue, 15 Mar 1994 10:10:52 -0500 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199403150157.RAA07760@mycroft.GreatCircle.COM>, Larry Sheldon write s: >I an still trying to figure out what causes majordomo to blat these out--now >I _also_ get to figure out why they are looping. Again, that's probably because you're using "resend" on the list, and using the "-f jaynet-forum-request". That means all bounces go back to the -request alias, which is just a script that sends out the reqest-answer. You want "-f owner-jaynet-forum". This should probably be explained more clearly in the resend.README file. --Dave From majordomo-users-owner Tue Mar 15 15:42:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA10567; Tue, 15 Mar 1994 15:42:23 GMT Received: from thelma.hq.af.mil by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA10558; Tue, 15 Mar 1994 07:39:08 -0800 Received: from wayne by thelma.hq.af.mil (NX5.67e/NX3.0M) id AA12917; Tue, 15 Mar 94 10:36:09 -0500 From: "Stacy W. Smith" Message-Id: <9403151536.AA12917@thelma.hq.af.mil> Received: by wayne.hq.af.mil (NX5.67e/NX3.0X) id AA02381; Tue, 15 Mar 94 10:35:25 -0500 Date: Tue, 15 Mar 94 10:35:25 -0500 Received: by NeXT.Mailer (1.100) Received: by NeXT Mailer (1.100) To: majordomo-users@GreatCircle.COM Subject: WHO on private lists? Reply-To: smith@hq.af.mil Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, After a little sweat (mainly due to compiling the latest version of perl), I have majordomo up and running under NEXTSTEP 3.2. Everything seems to be working correctly with one minor exception. Non-members are able to do a WHO on private lists. I was under the impression that only list members could do a who on private lists. Do I have something misconfigured? Thanks in advance, Stacy --- LT Stacy W. Smith 7th Communications Group USAF 7CG/SMOS Room 1A1056B 1600 Air Force Pentagon Washington, DC 20330-1600 (703)695-5060 DSN:225-5060 smith@hq.af.mil -------------------------------------------------------- Here's the directory listing: /usr/local/mail/lists drwxrwxr-x 2 majordom majordom 1024 Mar 15 08:53 . drwxrwxr-x 5 root wheel 1024 Mar 14 15:23 .. -rw-rw-r-- 1 majordom majordom 55 Mar 14 14:22 core -rw-rw-r-- 1 majordom majordom 0 Mar 7 16:33 core.closed -rw-rw-r-- 1 majordom majordom 66 Mar 14 08:20 core.info -rw-rw-r-- 1 majordom majordom 7 Mar 7 15:25 core.passwd -rw-rw-r-- 1 majordom majordom 138 Mar 15 08:53 core.resend And here are the aliases: majordomo: "|/usr/local/mail/majordomo/wrapper majordomo" majordomo-owner: smith owner-majordomo: smith core: "|/usr/local/mail/majordomo/wrapper resend @/usr/local/mail/lists/core.resend" owner-core: core-owner core-owner: smith owner-core-owner: smith core-outgoing: :include:/usr/local/mail/lists/core,core-archive owner-core-outgoing: core-owner core-archive: "| /usr/local/mail/majordomo/wrapper archive -f /usr/local/mail/archive/core -m -a" owner-core-archive: core-owner owner-core-request: core-owner core-request: "|/usr/local/mail/majordomo/wrapper request-answer core" core-approval: smith From majordomo-users-owner Tue Mar 15 19:31:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA12042; Tue, 15 Mar 1994 19:31:53 GMT Received: from heinous.isca.uiowa.edu.isca.uiowa.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA12036; Tue, 15 Mar 1994 11:31:43 -0800 Received: from localhost by isca.uiowa.edu (8.5-A/1.1) id TAA25060.198A7 on Tue, 15 Mar 1994 19:33:04 GMT. Organization: Heinous Owners Club And Persons With Nine Letter Names Date: Tue, 15 Mar 1994 13:32:27 +662900 (??) From: Ronnie Raygun Reply-To: Ronnie Raygun Subject: Setting Reply-to: field to list name as default To: majordomo Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Is there any way to get majordomo/wrapper to automagically create a Reply to: field with the name of the mailing list as a default? If so, how would I go about doing that? I didn't see anything about it in the docs. E.g.: Foo Bar sends mail to list-name@site.name. The header which subscribers would see looks like the following: From: Foo Bar Reply to: Mailing List To: Mailing List Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA12278; Tue, 15 Mar 1994 20:04:02 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA12267; Tue, 15 Mar 1994 12:03:44 -0800 Received: by interlock.ans.net id AA14571 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Tue, 15 Mar 1994 14:58:50 -0500 Received: by interlock.ans.net (Internal Mail Agent-2); Tue, 15 Mar 1994 14:58:50 -0500 Received: by interlock.ans.net (Internal Mail Agent-1); Tue, 15 Mar 1994 14:58:50 -0500 From: Dan Simoes Message-Id: <199403151957.AA30538@foo.ans.net> Subject: Re: Setting Reply-to: field to list name as default To: sample@heinous.isca.uiowa.edu Date: Tue, 15 Mar 1994 14:57:33 -0500 (EST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Ronnie Raygun" at Mar 15, 94 01:32:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 663 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > E.g.: Foo Bar sends mail to list-name@site.name. The header which > subscribers would see looks like the following: > > From: Foo Bar > Reply to: Mailing List > To: Mailing List > Anyone know how to make majordomo do this? If you are using resend, use the '-r ' flag to set the Reply-to field to the list. Interestingly, I've found this to be a source of disagreement among list members, as well as the 'From:' field... | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From majordomo-users-owner Tue Mar 15 20:51:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA12506; Tue, 15 Mar 1994 20:51:11 GMT Received: from mail.massey.ac.nz by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA12500; Tue, 15 Mar 1994 12:51:00 -0800 From: A.G.Bishop@massey.ac.nz Message-Id: <199403152051.MAA12500@mycroft.GreatCircle.COM> Received: from cc-pc7.massey.ac.nz (actually cc-pc7) by cc-server9 with SMTP(PP); Wed, 16 Mar 1994 09:50:51 +1300 Date: Wed, 16 Mar 94 09:36:47 +1200 Subject: majordomo + PP anyone? To: majordomo-users@GreatCircle.COM X-Organisation: Massey University, Palmerston North, New Zealand X-Mailer: MUMail 0.04 Development Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We are currently moving a sendmail-based mail system over to PP, we also support about 100 mailing lists but are looking for a better system (such as majordomo.) Has anyone used majordomo or parts of it with PP? Massey University Palmerston North New Zealand GMT +1200 From majordomo-users-owner Tue Mar 15 21:48:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA12928; Tue, 15 Mar 1994 21:48:24 GMT Received: from news.std.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA12922; Tue, 15 Mar 1994 13:48:17 -0800 Received: from world.std.com by news.std.com (5.65c/Spike-2.1) id AA08194; Tue, 15 Mar 1994 16:46:49 -0500 Received: by world.std.com (5.65c/Spike-2.0) id AA21909; Tue, 15 Mar 1994 16:46:34 -0500 Date: Tue, 15 Mar 1994 16:46:33 -0500 (EST) From: "Richard L. Lunn" Subject: Re: Setting Reply-to: field to list name as default To: Dan Simoes Cc: sample@heinous.isca.uiowa.edu, majordomo-users@GreatCircle.COM In-Reply-To: <199403151957.AA30538@foo.ans.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Tue, 15 Mar 1994, Dan Simoes wrote: > If you are using resend, use the '-r ' flag to set the > Reply-to field to the list. > > Interestingly, I've found this to be a source of disagreement among > list members, as well as the 'From:' field... I run a couple of lists, and I'll second the disagreement among list members. From time to time, people want the sender to be the from, and vica versa..., and some want the list to be the sender, as opposed to in my case list-name-approval... Is there some agreement among list managers of what the basic rules should be? I've been reluctant to change anything, as I'd rather go for consitency (even if it does/doesn't make logical sense to some users) -- Regards, >>Dick<< From majordomo-users-owner Tue Mar 15 14:03:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA12973; Tue, 15 Mar 1994 21:57:47 GMT Received: from heinous.isca.uiowa.edu.isca.uiowa.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA12967; Tue, 15 Mar 1994 13:57:36 -0800 Received: from localhost by isca.uiowa.edu (8.5-A/1.1) id VAA25730.198A7 on Tue, 15 Mar 1994 21:59:10 GMT. Organization: Heinous Owners Club And Persons With Nine Letter Names Date: Tue, 15 Mar 1994 15:53:02 +3516000 (??) From: Ronnie Raygun Subject: reply-to To: majordomo Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Well, I use pine, so I prefer the Reply to defaulting to the list, because pine will prompt me, asking whether I want to respond to the From: address or the Reply to: address. When there is no Reply to: address, I have to enter it manually; when there is one, I can choose between the two with a single keystroke. Back to the original question -- I noticed that resend is picky about -r not being the last option in the list of resend options. Have others had this problem too, or is it just a curse on my particular computer? In any case, thanks for the help. From majordomo-users-owner Tue Mar 15 22:13:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA13140; Tue, 15 Mar 1994 22:13:25 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA13127; Tue, 15 Mar 1994 14:12:55 -0800 Received: by interlock.ans.net id AA38582 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Tue, 15 Mar 1994 17:12:10 -0500 Received: by interlock.ans.net (Internal Mail Agent-2); Tue, 15 Mar 1994 17:12:10 -0500 Received: by interlock.ans.net (Internal Mail Agent-1); Tue, 15 Mar 1994 17:12:10 -0500 From: Dan Simoes Message-Id: <199403152210.AA42121@foo.ans.net> Subject: Re: Setting Reply-to: field to list name as default To: Eaco@terrasys.com (Richard L. Lunn) Date: Tue, 15 Mar 1994 17:10:53 -0500 (EST) Cc: dans@ans.net, sample@heinous.isca.uiowa.edu, majordomo-users@greatcircle.com In-Reply-To: from "Richard L. Lunn" at Mar 15, 94 04:46:33 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1064 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Is there some agreement among list managers of what the basic > rules should be? I've been reluctant to change anything, as I'd rather > go for consitency (even if it does/doesn't make logical sense to some users) I've decided in most cases to set the 'From' to the original sender, and the 'Reply-to:' to the list. After all, the reason a list exists is to further discussion amongst a group of people - odds are, in most cases you'd rather email the group and not just the sender, who will see the message anyway. The 'From' will let you do the latter if you really just want to send a private message to the sender. A related problem: users at a cc:mail site don't see the >From line (neither do MS Mail users). Is there a way to force 'double headers' if necessary, or a better workaround? The best fix would be to fix the bloody ccmail-to-smtp gateways and the like, but that's out of my hands... | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From majordomo-users-owner Tue Mar 15 14:13:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA13075; Tue, 15 Mar 1994 22:07:11 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA13068; Tue, 15 Mar 1994 14:07:04 -0800 Message-Id: <199403152207.OAA13068@mycroft.GreatCircle.COM> To: "Richard L. Lunn" cc: Dan Simoes , sample@heinous.isca.uiowa.edu, majordomo-users@GreatCircle.COM Subject: Re: Setting Reply-to: field to list name as default In-reply-to: Your message of Tue, 15 Mar 1994 16:46:33 -0500 (EST) Date: Tue, 15 Mar 1994 14:07:03 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Richard L. Lunn" writes: # Is there some agreement among list managers of what the basic # rules should be? I've been reluctant to change anything, as I'd rather # go for consitency (even if it does/doesn't make logical sense to some users) Every posting to a list should have a "Sender:" field that points to something _other_ than the list input address. Mailers are supposed to use "Sender:" to send back bounces. You want to have a "Sender:", so that the list manager gets the bounces; if you don't, mailers fall back to "From:", and whoever posted the original message gets the bounces. That doesn't do any good, because there's nothing they can do about the bouncing addresses (like drop them from the list). Obviously, you don't want the bounces coming back to the list input address, which would cause them to be reposted to the list. Whether you should have a "Reply-To:" or not depends on the charter of your list and the nature of its users. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Tue Mar 15 23:33:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA13478; Tue, 15 Mar 1994 23:33:10 GMT Received: from leibniz.math.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA13471; Tue, 15 Mar 1994 15:33:01 -0800 Received: from augusta.math.psu.edu (jim@augusta.math.psu.edu [146.186.131.77]) by leibniz.math.psu.edu (8.6.4/8.5) with ESMTP id SAA04645; Tue, 15 Mar 1994 18:33:03 -0500 Received: from localhost by augusta.math.psu.edu id ; Tue, 15 Mar 1994 18:33:00 -0500 Message-Id: <199403152333.SAA06660@augusta.math.psu.edu> To: Dan Simoes cc: Eaco@terrasys.com (Richard L. Lunn), sample@heinous.isca.uiowa.edu, majordomo-users@GreatCircle.COM Subject: Re: Setting Reply-to: field to list name as default In-reply-to: Your message of "Tue, 15 Mar 1994 17:10:53 EST." <199403152210.AA42121@foo.ans.net> X-Mailer: exmh version 1.2 1/14/94 Date: Tue, 15 Mar 1994 18:32:57 -0500 From: Jim Duncan Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dan Simoes writes: > A related problem: users at a cc:mail site don't see the > >From line (neither do MS Mail users). Is there a way to > force 'double headers' if necessary, or a better workaround? > The best fix would be to fix the bloody ccmail-to-smtp > gateways and the like, but that's out of my hands... Please bear in mind that "From " (sometimes called "From_") has nothing to do with SMTP or RFC-822. It is an artifact of Unix "mailbox" format, and delimits messages within a mailbox. I suspect the reason that cc:mail users don't see it is because it's not there, and if it is, it's not supposed to be. If you were referring to "From:", that's an entirely different matter. If you already knew all of this, please accept my apologies. Jim From majordomo-users-owner Tue Mar 15 23:49:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA13509; Tue, 15 Mar 1994 23:49:07 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA13503; Tue, 15 Mar 1994 15:48:51 -0800 Message-Id: <199403152348.PAA13503@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.37.109.4/16.2) id AA17736; Tue, 15 Mar 94 17:48:12 -0600 From: Larry Sheldon Subject: Re: unidentifiable message going to inexplicable destination To: barr@pop.psu.edu Date: Tue, 15 Mar 94 17:48:11 CST Cc: majordomo-users@greatcircle.com, cbuda@pigeon.creighton.edu In-Reply-To: <199403151510.KAA02995@bosnia.pop.psu.edu>; from "David Barr" at Mar 15, 94 10:10 am Mailer: Elm [revision: 70.85] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > >I an still trying to figure out what causes majordomo to blat these out--now > >I _also_ get to figure out why they are looping. > > Again, that's probably because you're using "resend" on the list, >jand using the "-f jaynet-forum-request". That means all bounces go > back to the -request alias, which is just a script that sends out the > reqest-answer. > > You want "-f owner-jaynet-forum". > > This should probably be explained more clearly in the resend.README file. I didn't do e original set-up--but I thought the person who did "followed the book", so to speak. I'll look into it--this is the first clue I've seen--I still don't knwo what provokes the message in the first place-- guess I should go over to the workers list and suggest that the id and trigger phrase of the offending message be included in the response. I don't understand the "probably because you're using "resend" intro--what else might we be using? Thanks for the help. Hey! Chuck! . . . -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . L. F. (Larry) Sheldon, Jr. . - Unix Systems Administration - . Creighton University Computer Center - Old Gym . - 2500 California Plaza - . Omaha, Nebraska, U.S.A. 68178 . - 402 280 2254 lsheldon@creighton.edu - . . - A hundred thousand lemmings can't be wrong. - .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Wed Mar 16 00:03:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA13565; Wed, 16 Mar 1994 00:03:18 GMT Received: from gasco.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA13559; Tue, 15 Mar 1994 16:03:10 -0800 Received: by gasco.com (/\==/\ Smail3.1.28.1 #28.4) id ; Tue, 15 Mar 94 16:03 PST Received: by gasco.com (/\==/\ Smail3.1.28.1 #28.5) id ; Tue, 15 Mar 94 16:03 PST Received: by nehalem.rain.com (4.1/SMI-4.1) id AA11900; Tue, 15 Mar 94 16:04:09 PST From: dlc@gasco.com (Darci L. Chapman, Paradise Cowgirl) Message-Id: <9403151604.ZM11897@gasco.com> Date: Tue, 15 Mar 1994 16:04:08 -0800 In-Reply-To: Brent Chapman "Re: Setting Reply-to: field to list name as default" (Mar 15, 14:07) References: <199403152207.OAA13068@mycroft.GreatCircle.COM> Reply-To: dlc@gasco.com (Darci L. Chapman, Paradise Cowgirl) X-Mailer: Z-Mail (2.1.0 10/27/92) To: majordomo-users@GreatCircle.COM Subject: Re: Setting Reply-to: field to list name as default Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Tue, Mar 15 at 14:07, Brent Chapman typed: +"Richard L. Lunn" writes: + +# Is there some agreement among list managers of what the basic +# rules should be? I've been reluctant to change anything, as I'd rather +# go for consitency (even if it does/doesn't make logical sense to some users) + +Every posting to a list should have a "Sender:" field that points to +something _other_ than the list input address. Mailers are supposed +to use "Sender:" to send back bounces. You want to have a "Sender:", +so that the list manager gets the bounces; if you don't, mailers fall +back to "From:", and whoever posted the original message gets the +bounces. That doesn't do any good, because there's nothing they can +do about the bouncing addresses (like drop them from the list). +Obviously, you don't want the bounces coming back to the list input +address, which would cause them to be reposted to the list. Unfortunately, not even the above will guarantee the "right thing" will happen )-: I manage a digested version of a list (that is hosted elsewhere). The headers include Sender:, Errors-To:, and From: all of which point to me. The Reply-To: line points to the original list address and guess what. Every once in a while, a site will bounce the entire digest back to the original list (Reply-To: line) totally ignoring all the other address choices it has... Talk about unhappy/irate users on the other end; and of course, I don't see the problem until the digest gets re-digested. On a busy day (75 messages or so to the list), serveral digests will go round and round before I can get a hold of a header that shows me where the problem originates. Just so you're warned. >>-Darci-> From majordomo-users-owner Wed Mar 16 00:05:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA13583; Wed, 16 Mar 1994 00:05:27 GMT Received: from midway.uchicago.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA13577; Tue, 15 Mar 1994 16:05:16 -0800 From: ckoenig@midway.uchicago.edu Received: from kimbark.uchicago.edu by midway.uchicago.edu for majordomo-users@greatcircle.com Tue, 15 Mar 94 18:05:12 CST Received: from localhost.uchicago.edu by kimbark.uchicago.edu (4.1/UCCO-1.0A) id AA07846; Tue, 15 Mar 94 18:04:17 CST Message-Id: <9403160004.AA07846@kimbark.uchicago.edu> To: majordomo-users@greatcircle.com Subject: Re: Setting Reply-to: field to list name as default In-Reply-To: Your message of "Tue, 15 Mar 94 14:07:03 PST." <199403152207.OAA13068@mycroft.GreatCircle.COM> Date: Tue, 15 Mar 94 18:04:17 -0600 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Several interesting issues I can think of: 1.) what if there is already a Reply-To: that the sending user put in? (leave it intact instead of adding "resend"'s new one, or delete it? But if "resend" should override their original Reply-To: with a new one of its own, then what if the user's original "From:" is garbled due to brain-damaged system configurations they have no control over, and that's why they've inserted their own Reply-To: with a valid address instead?) 2.) A number of gateways from Internet SMTP to various LAN mail systems have room to transfer only one sender and one recipient when they build their new headers from the incoming Internet message. It's a limitation of the LAN-based mail systems; they don't have the rich envelope and header specification of Internet RFC821/2 etc. mail. They only have one From and one To to work with, so they have to choose from the multiple ones offered by Internet mail, and demote the rest to comments.... I've noticed SMTP gateways on this campus for Microsoft Mail, cc:Mail, Quickmail, and even Multinet VMS mail which all have this problem. Usually they do what I consider to be the "wrong thing", they use the SMTP envelope "MAIL FROM:" and make that the "From" on the LAN message. Other Internet headers, including the real "From:" and even "Reply-To:" are demoted to comments, at the end of the message body, perhaps prefixed by "X-" as in "X-From:", where they're not available for any user software to construct replies (unless the user is clever enough, rarely, to read them by hand and manually use them to fix the header of their new reply). So no matter what we do regarding the addition of Reply-To: or the mucking with From: header, all these brain-damaged gateways to LAN and VMS systems are going to just use the envelope sender.... I only found out when the envelope sender information from our main front-end host was temporarily garbled by a bad "PHQuery" & sendmail configuration combination (sendmail didn't "trust" the "agent" user that was forwarding all messages passing through PH aliases), and suddenly no one on these LAN systems could reply to any mail that had come to them through our front-end and through their gateways, because all they had for constructing replies was the garbled envelope sender! (all their replies went to "agent@prism" instead of to whoever had written to them in the first place.... and it was all forwarded to ME! :-) Chris Koenigsberg: ckk@uchicago.edu, ckoenig@midway.uchicago.edu U. of Chicago Academic Information Technologies Voice 1-312-702-8189, FAX 1-312-702-3219 From majordomo-users-owner Wed Mar 16 00:09:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA13600; Wed, 16 Mar 1994 00:09:04 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA13594; Tue, 15 Mar 1994 16:08:50 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id TAA10503; Tue, 15 Mar 1994 19:08:54 -0500 Message-Id: <199403160008.TAA10503@bosnia.pop.psu.edu> To: Brent Chapman cc: majordomo-users@GreatCircle.COM Subject: Re: Setting Reply-to: field to list name as default In-reply-to: Your message of "Tue, 15 Mar 1994 14:07:03 PST." <199403152207.OAA13068@mycroft.GreatCircle.COM> 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 X-Mailer: exmh version 1.3beta 2/17/94 Date: Tue, 15 Mar 1994 19:08:54 -0500 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199403152207.OAA13068@mycroft.GreatCircle.COM>, Brent Chapman write s: >"Richard L. Lunn" writes: > ># Is there some agreement among list managers of what the basic ># rules should be? I've been reluctant to change anything, as I'd rather ># go for consitency (even if it does/doesn't make logical sense to some users) > >Every posting to a list should have a "Sender:" field that points to >something _other_ than the list input address. Mailers are supposed >to use "Sender:" to send back bounces. No no no! "Sender:" is an informational field only. It is and should NOT used automatically for bounces or any other purpose by mailers. It is an indication to specify who is the actual person who is responsible for sending the message. RFC 822 says that it doesn't even need to be an e-mail address. The bounce address is from the out-of-band "RCPT FROM" line, which usually appears in the body of the message as "Return-Path:". > You want to have a "Sender:", >so that the list manager gets the bounces; if you don't, mailers fall >back to "From:", and whoever posted the original message gets the >bounces. I'm not aware of any fall-back mechanism for bounces. I would argue that that is non-compliant, but I don't have the chapter and verse in front of me. I think the mcimail and attmail people operate this way, and they are flamed regularly for their broken behavior. The solution IMHO is to modify "resend" to allow you to specify a "To:" line, and have the original "To:" and "Cc:" lines be changed to "X-To:" and "X-cc:" a la LISTSERV. (LISTSERV also replaces the Sender:, and keeps the old in a "Comments:", but I don't agree with this) --Dave From majordomo-users-owner Wed Mar 16 00:20:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA13689; Wed, 16 Mar 1994 00:20:25 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA13683; Tue, 15 Mar 1994 16:20:15 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id TAA10687 for ; Tue, 15 Mar 1994 19:20:18 -0500 Message-Id: <199403160020.TAA10687@bosnia.pop.psu.edu> To: majordomo-users@greatcircle.com Subject: Re: unidentifiable message going to inexplicable destination In-reply-to: Your message of "Tue, 15 Mar 1994 17:48:11 CST." <199403152348.SAA10237@bosnia.pop.psu.edu> 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 X-Mailer: exmh version 1.3beta 2/17/94 Date: Tue, 15 Mar 1994 19:20:17 -0500 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199403152348.SAA10237@bosnia.pop.psu.edu>, Larry Sheldon writes: >I don't understand the "probably because you're using "resend" intro--what >else might we be using? I say that because that's resend's default behavior, which is bad if you're using it on outgoing mail. I don't really know why that is the default, but I didn't write it. The other possibility is that you're not using 'resend' and that you are running a sendmail (like v8) that automatically puts the "owner-listname" alias as the out-of-band FROM address. That is, if you have: owner-listname: listname-request listname-approval: joe@some.site listname-request: |"/foo/bar/request-answer listname" listname: :include:/bar/baz/listname Then you'll have problems too. --Dave From majordomo-users-owner Tue Mar 15 16:22:02 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA13701; Wed, 16 Mar 1994 00:20:41 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA13694; Tue, 15 Mar 1994 16:20:31 -0800 Message-Id: <199403160020.QAA13694@mycroft.GreatCircle.COM> To: Jim Duncan cc: Dan Simoes , Eaco@terrasys.com (Richard L. Lunn), sample@heinous.isca.uiowa.edu, majordomo-users@GreatCircle.COM Subject: Re: Setting Reply-to: field to list name as default In-reply-to: Your message of Tue, 15 Mar 1994 18:32:57 -0500 Date: Tue, 15 Mar 1994 16:20:29 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Jim Duncan writes: # Dan Simoes writes: # > A related problem: users at a cc:mail site don't see the # > >From line (neither do MS Mail users). Is there a way to # > force 'double headers' if necessary, or a better workaround? # > The best fix would be to fix the bloody ccmail-to-smtp # > gateways and the like, but that's out of my hands... # # Please bear in mind that "From " (sometimes called "From_") has nothing to do # # with SMTP or RFC-822. It is an artifact of Unix "mailbox" format, and delimits # messages within a mailbox. I suspect the reason that cc:mail users don't see # it is because it's not there, and if it is, it's not supposed to be. # # If you were referring to "From:", that's an entirely different matter. If you # already knew all of this, please accept my apologies. Well, not really... This is more an SMTP issue than an RFC822 issue. RFC822 only talks about the "contents" of messages, but it says there's a separate "envelope" that contains whatever information is necessary to deliver the message. Think about how a Majordomo-Users posting gets to your site: your email address doesn't appear anywhere that you can see; "contents" says "To: Majordomo-Users@GreatCircle.COM". Your address is in the invisible "envelope". One of the other things in the envelope is the "sender". This is distinct from the "Sender:" field in the contents, though they may (and often do) point to the same address. UNIX mailers often reflect this supposedly-invisible "envelope sender" into the not-so-invisible "From " line. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Wed Mar 16 00:27:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA13739; Wed, 16 Mar 1994 00:27:52 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA13731; Tue, 15 Mar 1994 16:27:45 -0800 Message-Id: <199403160027.QAA13731@mycroft.GreatCircle.COM> To: David Barr cc: majordomo-users@GreatCircle.COM Subject: Re: Setting Reply-to: field to list name as default In-reply-to: Your message of Tue, 15 Mar 1994 19:08:54 -0500 Date: Tue, 15 Mar 1994 16:27:43 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk David Barr writes: # No no no! "Sender:" is an informational field only. It is and should # NOT used automatically for bounces or any other purpose by mailers. # It is an indication to specify who is the actual person who is responsible # for sending the message. RFC 822 says that it doesn't even # need to be an e-mail address. # # The bounce address is from the out-of-band "RCPT FROM" line, which # usually appears in the body of the message as "Return-Path:". I'm sorry, but you are mistaken. See section 4.4.4 of RFC822: 4.4.4. AUTOMATIC USE OF FROM / SENDER / REPLY-TO For systems which automatically generate address lists for replies to messages, the following recommendations are made: o The "Sender" field mailbox should be sent notices of any problems in transport or delivery of the original messages. If there is no "Sender" field, then the "From" field mailbox should be used. o The "Sender" field mailbox should NEVER be used automatically, in a recipient's reply message. o If the "Reply-To" field exists, then the reply should go to the addresses indicated in that field and not to the address(es) indicated in the "From" field. # > You want to have a "Sender:", # >so that the list manager gets the bounces; if you don't, mailers fall # >back to "From:", and whoever posted the original message gets the # >bounces. # # I'm not aware of any fall-back mechanism for bounces. I would argue # that that is non-compliant, but I don't have the chapter and verse # in front of me. I think the mcimail and attmail people operate # this way, and they are flamed regularly for their broken behavior. You are mistaken here as well; see the quote from RFC822 above. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Wed Mar 16 00:55:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA13869; Wed, 16 Mar 1994 00:55:46 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA13862; Tue, 15 Mar 1994 16:55:37 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id TAA11197 for ; Tue, 15 Mar 1994 19:55:24 -0500 Message-Id: <199403160055.TAA11197@bosnia.pop.psu.edu> To: majordomo-users@greatcircle.com Subject: Re: Setting Reply-to: field to list name as default In-reply-to: Your message of "Tue, 15 Mar 1994 16:27:43 PST." <199403160027.QAA13731@mycroft.GreatCircle.COM> 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 X-Mailer: exmh version 1.3beta 2/17/94 Date: Tue, 15 Mar 1994 19:55:23 -0500 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199403160027.QAA13731@mycroft.GreatCircle.COM>, Brent Chapman write s: >David Barr writes: > ># No no no! "Sender:" is an informational field only. >I'm sorry, but you are mistaken. Well, then someone should tell Eric Allman, since that's not how sendmail behaves. I just tested it: bosnia:~#/usr/lib/sendmail -fbarr nosuchuser@nowhere Sender: nonexistent@nowhere From: barr@pop.psu.edu To: nosuchuser@nowhere hi ^D This one bounced to me (barr, not barr@pop.psu.edu) since I was the envelope from. bosnia:~#/usr/lib/sendmail -fnosuchsender@nowhere nosuchuser@nowhere Sender: nonexistent@nowhere From: barr@pop.psu.edu To: nosuchuser@nowhere hi ^D This one bounced to "nosuchSENDER@nowhere", which then bounced and was sent to the postmaster. If you want, I can show you the logs and the bounce messages. Your quote of RFC 822 is talking about something different. It's talking about software which generates lists of addresses given a reply, not mailing list software. Where it talks about "Reply-To:" should tip you off. Bounces should NEVER EVER go to a "Reply-To:". Reply-To is strictly a user field, to redirect human responses, not automatic ones. --Dave From majordomo-users-owner Wed Mar 16 02:16:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA14337; Wed, 16 Mar 1994 02:16:08 GMT Received: from antares.mcs.anl.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA14330; Tue, 15 Mar 1994 18:16:00 -0800 Received: from mcs.anl.gov (godzilla.mcs.anl.gov [140.221.5.136]) by antares.mcs.anl.gov (8.6.4/8.6.4) with ESMTP id UAA22815; Tue, 15 Mar 1994 20:15:58 -0600 Message-Id: <199403160215.UAA22815@antares.mcs.anl.gov> To: "Richard L. Lunn" cc: majordomo-users@GreatCircle.COM, rackow@antares.mcs.anl.gov Subject: Re: Setting Reply-to: field to list name as default Reply-to: rackow@mcs.anl.gov In-reply-to: Your message of "Tue, 15 Mar 1994 16:46:33 EST." Date: Tue, 15 Mar 1994 20:15:57 -0600 From: Gene Rackow Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I think this was a flame war several months ago as to what to set what how. Various (broken by some standards) mail readers do not support anthing other than "to" and "from" fields, so there are some legitimate gripes as to what gets put where. The feeling for most people that have mailers that do understand full headers, is that the others should be yelling at their mail vendors and not messing with mail headers at all. It really comes down to "my little view of the world is this and everyone should conform to a the smallest subset of what is real in my world vs the real world". In anything, the value of the various fields will depend on the focus and intent of the list. For all practical purposes, the From: line should be the person that sent the message. The message did not magicly originate from the list, the author of the message did that, so it is From: them. The debate goes into what should go into a "reply-to" field if anything. This is going to be list dependant. For some lists, what you want is that every reply be directed back to the author of the first message. Let them summarize and post a follow-up to eht list. Other lists are more of a discussion list and people expect to see " by default" all the discussion going on in the list. Private messages are almost discouraged. -_gene From majordomo-users-owner Wed Mar 16 02:44:02 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA14499; Wed, 16 Mar 1994 02:44:02 GMT Received: from pjl53ig.i-p.attmail.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA14493; Tue, 15 Mar 1994 18:43:49 -0800 Date: Wed 16 Mar 1994 02:43:11 +0000 From: billc@pegasus.mail.att.net (WJCarpenter) Received: from pegasus by attmail; Wed Mar 16 02:43 GMT 1994 Subject: RE: Setting Reply-to: field to list name as default In-Reply-To: Brent Chapman's note of 16:27:43, 15 Mar 1994 To: majordomo-users@GreatCircle.COM Message-ID: Reference: <199403160027.QAA13731@mycroft.GreatCircle.COM> Content-Type: text Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk brent> I'm sorry, but you are mistaken. See section 4.4.4 of RFC822: Oh, cool! Duelling RFCs. Here's mine ... RFC-1123, para 5.3.6 (to whatever extent you want to follow RFCs as standards, this certainly takes precedence over RFC-822; RFC-822 has enough other cloudy bits to keep things rolling for quite a while): 5.3.6 Mailing Lists and Aliases An SMTP-capable host SHOULD support both the alias and the list form of address expansion for multiple delivery. When a message is delivered or forwarded to each address of an expanded list form, the return address in the envelope ("MAIL FROM:") MUST be changed to be the address of a person who administers the list, but the message header MUST be left unchanged; in particular, the "From" field of the message is unaffected. DISCUSSION: An important mail facility is a mechanism for multi- destination delivery of a single message, by transforming or "expanding" a pseudo-mailbox address into a list of destination mailbox addresses. When a message is sent to such a pseudo-mailbox (sometimes called an "exploder"), copies are forwarded or redistributed to each mailbox in the expanded list. We classify such a pseudo-mailbox as an "alias" or a "list", depending upon the expansion rules: (a) Alias To expand an alias, the recipient mailer simply replaces the pseudo-mailbox address in the envelope with each of the expanded addresses in turn; the rest of the envelope and the message body are left unchanged. The message is then delivered or forwarded to each expanded address. (b) List A mailing list may be said to operate by "redistribution" rather than by "forwarding". To expand a list, the recipient mailer replaces the pseudo-mailbox address in the envelope with each of the expanded addresses in turn. The return address in the envelope is changed so that all error messages generated by the final deliveries will be returned to a list administrator, not to the message originator, who generally has no control over the contents of the list and will typically find error messages annoying. -- Bill@attmail.com billc@pegasus.ATT.COM or +1 908 576 2932, Fax x6406 William_J_Carpenter@ATT.COM AT&T Bell Labs / AT&T EasyLink Services LZ 3C-207 From majordomo-users-owner Wed Mar 16 03:37:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id DAA14662; Wed, 16 Mar 1994 03:37:09 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA14649; Tue, 15 Mar 1994 19:36:56 -0800 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA05018 (5.65c/IDA-1.4.4 for ); Tue, 15 Mar 1994 22:35:49 -0500 Message-Id: <199403160335.AA05018@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: Setting Reply-to: field to list name as default In-Reply-To: Your message of "Tue, 15 Mar 1994 19:55:23 EST." <199403160055.TAA11197@bosnia.pop.psu.edu> Date: Tue, 15 Mar 1994 22:35:49 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199403160055.TAA11197@bosnia.pop.psu.edu>, David Barr writes: > In message <199403160027.QAA13731@mycroft.GreatCircle.COM>, > Brent Chapman writes: > >David Barr writes: > > > ># No no no! "Sender:" is an informational field only. > > >I'm sorry, but you are mistaken. > > Well, then someone should tell Eric Allman, since that's not how > sendmail behaves. I just tested it: Excuse me, but you are being SMTPocentric. Try using sendmail from a uucp feed, and see what happens. In any case here are Eric's comments on the subject from the op.me packaged with sendmail: For example, the "Sender:" and "From:" fields are always scanned on ARPANET mail to deter- mine the sender[19]; this is used to perform the "return to sender" function. The "From:" and "Full-Name:" fields are used to determine the full name of the sender if possible; this is stored in the macro $_x and used in a number of ways. [19]Actually, this is no longer true in SMTP; this infor- mation is contained in the envelope. The older ARPANET pro- tocols did not completely distinguish envelope from header. > Your quote of RFC 822 is talking about something different. It's > talking about software which generates lists of addresses given > a reply, not mailing list software. Brent never mentioned majordomo in the entire conversation you are replying to. The line from 822 is: For systems which automatically generate address lists for replies to messages, the following recommendations... They couldn't possibly mean sendmail could they?? Nah, sendmail doesn't qualify as a system that automatically generates an address list (with a single element) to use as a reply to a (inbound) message. Although you could say that sendmail's "reply" says that the message failed delivery, but it isn't really a reply is it? > Where ittalks about "Reply-To:" should tip you off. I think you are mixing the delivery paths. Applies to MTA type reply generator. What else could determine delivery failure? The MUA? Not quite. o The "Sender" field mailbox should be sent notices of any problems in transport or delivery of the original messages. If there is no "Sender" field, then the "From" field mailbox should be used. Recipient implies that the delivery is successful and that we are now discussing an MUA type reply generator. o The "Sender" field mailbox should NEVER be used automatically, in a recipient's reply message. o If the "Reply-To" field exists, then the reply should go to the addresses indicated in that field and not to the address(es) indicated in the "From" field. > Bounces should NEVER EVER go to a "Reply-To:". > Reply-To is strictly a user field, to redirect human responses, > not automatic ones. Tell that to an old Mail-11/SMTP gateway I once had the misfortune of running across. It thought Reply-to was just a dandy address to send bounce notifications too. If Darci's problems are any indication that one gateway is alive and well, and still using the %#%$&*#^$*#$^*(%&%%$ Reply-to address 8-). -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Wed Mar 16 18:13:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA17757; Wed, 16 Mar 1994 18:13:42 GMT Received: from SERV02.SLAC.STANFORD.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA17751; Wed, 16 Mar 1994 10:13:28 -0800 From: BEBO@SLAC.Stanford.EDU Received: from unixhub.SLAC.Stanford.EDU by SERV02.SLAC.STANFORD.EDU (PMDF V4.2-12 #4747) id <01HA1BCCBS2O001MSB@SERV02.SLAC.STANFORD.EDU>; Wed, 16 Mar 1994 10:12:35 PST Received: by unixhub.SLAC.Stanford.EDU (4.1/SLAC 920508) from hebe.SLAC.Stanford.EDU id AA01502; Wed, 16 Mar 94 10:12:08 PST Received: by hebe.SLAC.Stanford.EDU (AIX 3.2/UCB 5.64/SLAC 920508) id AA65182; Wed, 16 Mar 1994 10:12:09 -0800 Date: Wed, 16 Mar 1994 10:12:09 -0800 Subject: Some Help Please.. To: majordomo-users@greatcircle.com Message-id: <9403161812.AA65182@hebe.SLAC.Stanford.EDU> X-Envelope-to: majordomo-users@greatcircle.com Content-transfer-encoding: 7BIT Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I suspect that these are FAQs, so please be patient - I've tried to dig the answers out of the documentation that I have, but with no success. Thanks in advance for any help. 1) What steps are required to set up a list where: * only the owners can subscribe new folks * only the owners can send messages to the list 2) What steps are required to set up a list where: * only the owners can subscribe new folks * any subscribers can send to the list 3) What steps are required to set up a list where: * there is a 2-way gateway with a Usenet newsgroup Thanks again -- Bebo White Stanford Linear Accelerator Center e-mail: bebo@slac.stanford.edu phone: 415-926-2907 fax: 415-926-3329 From majordomo-users-owner Wed Mar 16 22:26:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA18857; Wed, 16 Mar 1994 22:26:30 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA18850; Wed, 16 Mar 1994 14:26:19 -0800 Received: from [192.26.65.78] by sgi.sgi.com via SMTP (931110.SGI/910110.SGI) for majordomo-users@greatcircle.com id AA06466; Wed, 16 Mar 94 14:26:24 -0800 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:majordomo-users@greatcircle.com id AA23397; Wed, 16 Mar 94 14:26:20 -0800 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9403162226.AA23397@lunch.asd.sgi.com> Subject: Digest chages -- line count and max age To: majordomo-users@greatcircle.com Date: Wed, 16 Mar 1994 14:26:19 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 3434 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I made some changes to digest I consider pretty useful. Primarily, I found that issuing digests based on the number of characters was not satisfactory. Instead, I wanted the number of lines, and I didn't want to count all the header fields that get stripped later (some headers are short, some huge). In short, I wanted a reasonable predictor of the resulting archive. Now you can "push" an archive based on number of bytes, by number of lines, or by the age of the oldest file. It's an "OR" relationship, i.e. if ANY of the conditions are true, out it goes. I added the age parameter so digests don't get too stale. However, it is only consulted when new mail comes in, so if you really care, you'll need a cron job too. If you don't define the size/lines/age fields in your .cf, digest doesn't use them. The new fields are: #how big do we let digests get before sending? # (size or lines or age, whichever comes first) # size in bytes DIGEST_SIZE=25000 # size in lines DIGEST_LINES=325 # age in days (can inlcude fractions) MAX_AGE=3 I hope that just mailing these diffs here will get them considered for inclusion in digest and the "new" majordomo. If not, who should I mail to? enjoy! *** digest.old Tue Mar 15 15:25:42 1994 --- digest Tue Mar 15 15:25:08 1994 *************** *** 63,82 **** sub receive_message { $sum = 0; $i = 0; do { $i++; $file = sprintf("%s/%03d", $V{'INCOMING'}, $i); $sum += (-s $file); } until (! -e $file); print STDERR "Receiving $i\n"; open(MSG, ">$file") || &abort("open(MSG, \">$file\"): $!"); while () { print MSG $_; } close(MSG); $sum += (-s $file); ! if ($sum > $V{'DIGEST_SIZE'}) { &make_digest; } return(1); --- 63,117 ---- sub receive_message { $sum = 0; + $lines = 0; + $push = 0; # true if maximum age exceeded $i = 0; do { $i++; $file = sprintf("%s/%03d", $V{'INCOMING'}, $i); $sum += (-s $file); + if (defined($V{'DIGEST_LINES'}) && open(LINECNT, "<$file")) { + for () { + $lines++; + } + close(LINECNT); + } + if (defined($V{'MAX_AGE'}) && (-M $file) > $V{'MAX_AGE'}) { + $push = 1; + } } until (! -e $file); print STDERR "Receiving $i\n"; open(MSG, ">$file") || &abort("open(MSG, \">$file\"): $!"); + + # eat the header + $/ = ''; + $head = ; + $head =~ s/\n\s+/ /g; + + # only pass through From/Date/Subject header fields to get a + # more accurate size and line count. + $head =~ /^(from:\s+.*)/i && print MSG $1, "\n"; + $head =~ /^(subject:\s+.*)/i && print MSG $1, "\n"; + $head =~ /^(date:\s+.*)/i && print MSG $1, "\n"; + print MSG "\n"; + + # now copy the body of the message + $/ = "\n"; while () { + s/^From />From /; print MSG $_; } close(MSG); + $lines += $. + 3; # input lines + three lines of header (whole header + # counted as one "line" due to $/ = '') $sum += (-s $file); ! if (!defined($V{'DIGEST_LINES'})) { ! $V{'DIGEST_LINES'} = $lines; ! } ! if (!defined($V{'DIGEST_SIZE'})) { ! $V{'DIGEST_SIZE'} = $sum; ! } ! if ($push || $sum > $V{'DIGEST_SIZE'} || $lines > $V{'DIGEST_LINES'}) { &make_digest; } return(1); -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Wed Mar 16 22:45:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA18904; Wed, 16 Mar 1994 22:45:44 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA18898; Wed, 16 Mar 1994 14:45:36 -0800 Received: from [192.26.65.78] by sgi.sgi.com via SMTP (931110.SGI/910110.SGI) for majordomo-users@greatcircle.com id AA10674; Wed, 16 Mar 94 14:45:37 -0800 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:majordomo-users@greatcircle.com id AA23520; Wed, 16 Mar 94 14:45:32 -0800 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9403162245.AA23520@lunch.asd.sgi.com> Subject: my version of the one-liner fix To: majordomo-users@greatcircle.com Date: Wed, 16 Mar 1994 14:45:32 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 2858 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk To implement my version of "one-liners", I introduced a new file: $listdir/$list.name. If present, majordomo gets the name of the list from (the first line of) that file. This is used in the welcome message primarily, but also in the index. There are probably other places this would be appropriate, but in my limited time with majordomo, that's all I've done. This way the welcome says: Welcome to the Antique Car, Road Race and Floor Polish mailing list! instead of: Welcome to the antcar-race-wax mailing list! And index would look like: antcar-race-wax Antique Car, Road Race and Floor Polish mailing list instead of: antcar-race-wax As usual, if the file is not present, or zero length, the old behvaior prevails. *** majordomo.old Sun Oct 17 16:47:25 1993 --- majordomo Wed Mar 16 14:39:48 1994 *************** *** 490,496 **** while(<${listdir}/*>) { s,^.*/,,; # strip off leading path /[^-_0-9a-zA-Z]/ && next; # skip non-list files (*.info, etc.) ! print REPLY "\t", $_, "\n"; } print REPLY "\nUse the 'info ' command to get more information\n"; print REPLY "about a specific list.\n"; --- 490,504 ---- while(<${listdir}/*>) { s,^.*/,,; # strip off leading path /[^-_0-9a-zA-Z]/ && next; # skip non-list files (*.info, etc.) ! if (-s "${listdir}/$_.name" && # use list.name file if >0 length ! open(NAME, "$listdir/$_.name") > 0) { ! chop($listname = ); ! close(NAME); ! printf REPLY " %-20s %s mailing list\n", $_, $listname; ! } ! else { ! print REPLY "\t", $_, "\n"; ! } } print REPLY "\nUse the 'info ' command to get more information\n"; print REPLY "about a specific list.\n"; *************** *** 774,784 **** sub welcome { local($list) = shift; local($subscriber) = join(" ", @_); # Set up the sendmail process to welcome the new subscriber &sendmail(MSG, $subscriber, "Welcome to $list"); print MSG <<"EOM"; ! Welcome to the $list mailing list! If you ever want to remove yourself from this mailing list, send the following command in email to "$whoami": --- 782,800 ---- sub welcome { local($list) = shift; local($subscriber) = join(" ", @_); + local($listname) = $list; + + if (-s "$listdir/$clean_list.name") { + if (open(NAME, "$listdir/$clean_list.name") > 0) { + chop($listname = ); + close(NAME); + } + } # Set up the sendmail process to welcome the new subscriber &sendmail(MSG, $subscriber, "Welcome to $list"); print MSG <<"EOM"; ! Welcome to the $listname mailing list! If you ever want to remove yourself from this mailing list, send the following command in email to "$whoami": -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Wed Mar 16 15:02:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA18939; Wed, 16 Mar 1994 22:50:25 GMT Received: from eagle.is.lmsc.lockheed.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA18932; Wed, 16 Mar 1994 14:50:10 -0800 Received: from sedbsvr.ssd.lmsc.lockheed.com by eagle.is.lmsc.lockheed.com (5.65/Ultrix4.3-C) id AA01568; Wed, 16 Mar 1994 14:47:46 -0800 Message-Id: <9403162247.AA01568@eagle.is.lmsc.lockheed.com> Received: by sedbsvr.se.ssd.lmsc.lockheed.com (1.36.108.7/16.2) id AA22664; Wed, 16 Mar 1994 14:47:22 -0800 From: Bob Kaehms Subject: HTML wish list To: majordomo-users@greatcircle.com Date: Wed, 16 Mar 94 14:47:22 PST Mailer: Elm [revision: 70.30] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Brent (anyone), Has anyone seen the hypermail program that Tom Gruber at Stanford did for EIT? I would love to see something as a add on archiver program do the same thing through perl that he does through lisp, only do it incrementally... Also, would be nice to be able to do the following: subscribe list-name num-lines so that only num-lines of each message is sent. This would be especially usefull when combined with a html browsable archive. You would be flaged as to discussion flow without having to wade through entire messages.... plus it would (could) keep mail traffic to a (?)minimum... thoughts? From majordomo-users-owner Wed Mar 16 23:02:50 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA19007; Wed, 16 Mar 1994 23:02:50 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA19001; Wed, 16 Mar 1994 15:02:35 -0800 Received: from [192.26.65.78] by sgi.sgi.com via SMTP (931110.SGI/910110.SGI) for majordomo-users@GreatCircle.COM id AA13662; Wed, 16 Mar 94 15:02:29 -0800 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:majordomo-users@GreatCircle.COM id AA23617; Wed, 16 Mar 94 15:02:14 -0800 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9403162302.AA23617@lunch.asd.sgi.com> Subject: Re: Setting Reply-to: field to list name as default To: rackow@mcs.anl.gov Date: Wed, 16 Mar 1994 15:02:14 -0800 (PST) Cc: Eaco@TerraSys.com, majordomo-users@GreatCircle.COM In-Reply-To: <199403160215.UAA22815@antares.mcs.anl.gov> from "Gene Rackow" at Mar 15, 94 08:15:57 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 1651 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > For all practical purposes, the From: line should be the person that > sent the message. The message did not magicly originate from the > list, the author of the message did that, so it is From: them. This I think we all agree on. > The debate goes into what should go into a "reply-to" field if anything. > This is going to be list dependant. For some lists, what you want is that > every reply be directed back to the author of the first message. Let them > summarize and post a follow-up to eht list. Other lists are more of a > discussion list and people expect to see " by default" all the discussion > going on in the list. Private messages are almost discouraged. One other issue you neglected is what if there's already a Reply-To header? Do you move that to From:? Overwriting it is clearly bad form. Also, from a MUA perspective, a reply goes to the From: or Reply-To: field, but a "group" reply only adds everyone on the Cc: list. In neither case is the From: line used if a Reply-To: field is present. Sure I know there are mailers that do this, but it's not really appropriate. RFC 822 says: If the "Reply-To" field exists, then the reply should go to the addresses indicated in that field and not to the address(es) indicated in the "From" field. Anyway, my point is that if Reply-To is the list, it's VERY difficult to reply to just the original author. Perhaps in this case, the author should be added to the Cc: list. On the other hand, if the intent is to discourage private messages, you're all set :-) -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Thu Mar 17 03:59:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id DAA25500; Thu, 17 Mar 1994 03:59:47 GMT Received: from de5.CTD.ORNL.GOV by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA17962; Wed, 16 Mar 1994 10:56:50 -0800 Received: (from de5@localhost) by de5.CTD.ORNL.GOV (8.6.7/8.6.6) id NAA07400; Wed, 16 Mar 1994 13:56:21 -0500 Date: Wed, 16 Mar 1994 13:56:21 -0500 From: Dave Sill Message-Id: <199403161856.NAA07400@de5.CTD.ORNL.GOV> To: BEBO@SLAC.Stanford.EDU CC: majordomo-users@GreatCircle.COM Subject: Some Help Please.. In-Reply-To: <9403161812.AA65182@hebe.SLAC.Stanford.EDU> References: <9403161812.AA65182@hebe.SLAC.Stanford.EDU> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >1) What steps are required to set up a list where: > * only the owners can subscribe new folks > * only the owners can send messages to the list Create listname.closed in the list directory. Alias incoming list submissions to go through "resend" with the -A and -a options. >2) What steps are required to set up a list where: > * only the owners can subscribe new folks > * any subscribers can send to the list Same as above, except leave of the -A and -a options. >3) What steps are required to set up a list where: > * there is a 2-way gateway with a Usenet > newsgroup On the news server, create a mail->news gateway by setting up a mail alias that pipes incoming messages to something that reformats the message and passes it off to inews or rnews. Also create a news->mail gateway that passes non-mail->news-gateway-originated messages back to the mailing list. There are numereous bits and pieces floating around that do this for one or more news server systems. I use Rich Salz' newsgate with INN. E-mail Rich for a copy of the lastest version of newsgate. The one in the archives is ancient. See also the INN FAQ. If you had a hard time configuring Majordomo, you're in for a real treat getting bidirectional mail<->news gateways set up right. :-) -Dave From majordomo-users-owner Thu Mar 17 15:31:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA28812; Thu, 17 Mar 1994 15:31:22 GMT Received: from hub.terc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA28806; Thu, 17 Mar 1994 07:31:14 -0800 Received: from qm.terc.edu (qm.terc.edu [140.245.2.16]) by hub.terc.edu (8.6.4/8.6.4) with SMTP id KAA26022; Thu, 17 Mar 1994 10:29:05 -0500 Message-ID: Date: 17 Mar 1994 10:33:13 -0500 From: "Stephen Bannasch" Subject: Re: HTML wish list To: "Bob Kaehms" Cc: majordomo-users@GreatCircle.COM, "Hamilton Gilbert" , "Bruce Rigby" X-Mailer: Mail*Link SMTP/QM 3.0.0b2 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk RE>HTML wish list Bob, You mention HTML browsable archives -- > Has anyone seen the hypermail program that Tom Gruber at Stanford did > for EIT? I would love to see something as a add on archiver program > do the same thing through perl that he does through lisp, only do it > incrementally... Also, would be nice to be able to do the following: > > subscribe list-name num-lines > > so that only num-lines of each message is sent. This would be > especially usefull when combined with a html browsable archive. > You would be flaged as to discussion flow without having to wade through > entire messages.... plus it would (could) keep mail traffic to a > (?)minimum... I am very interested in doing that. Could you describe a bit more of the details? Or provide some pointers to further references or a URL to an example. --thanks, Stephen Bannasch From majordomo-users-owner Thu Mar 17 17:31:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA29245; Thu, 17 Mar 1994 17:31:44 GMT Received: from SERV02.SLAC.STANFORD.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA29239; Thu, 17 Mar 1994 09:31:34 -0800 From: BEBO@SLAC.Stanford.EDU Received: from unixhub.SLAC.Stanford.EDU by SERV02.SLAC.STANFORD.EDU (PMDF V4.2-12 #4747) id <01HA2O5SYUY80021EH@SERV02.SLAC.STANFORD.EDU>; Thu, 17 Mar 1994 09:30:11 PST Received: by unixhub.SLAC.Stanford.EDU (4.1/SLAC 920508) from hebe.SLAC.Stanford.EDU id AA29267; Thu, 17 Mar 94 09:25:01 PST Received: by hebe.SLAC.Stanford.EDU (AIX 3.2/UCB 5.64/SLAC 920508) id AA57131; Thu, 17 Mar 1994 09:25:01 -0800 Date: Thu, 17 Mar 1994 09:25:01 -0800 Subject: Re: Some Help Please.. To: de5@de5.ctd.ornl.gov Cc: majordomo-users@greatcircle.com Message-id: <9403171725.AA57131@hebe.SLAC.Stanford.EDU> X-Envelope-to: majordomo-users@greatcircle.com Content-transfer-encoding: 7BIT Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dave, Thanks do much for your reply - it was just what I needed. I *might* have been able to figure it out myself if I had had documentation re: resend and its options. Do such docs exist? Thanks again -- Bebo White Stanford Linear Accelerator Center e-mail: bebo@slac.stanford.edu phone: 415-926-2907 fax: 415-926-3329 From majordomo-users-owner Thu Mar 17 18:18:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA29603; Thu, 17 Mar 1994 18:18:44 GMT Received: from sequent.do.losrios.cc.ca.us by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA29597; Thu, 17 Mar 1994 10:18:37 -0800 Received: by sequent.do.losrios.cc.ca.us (5.65/1.35) id AA06724; Thu, 17 Mar 94 10:18:08 -0800 Date: Thu, 17 Mar 1994 10:16:22 -0800 (PST) From: Randy Jones Subject: Re: Some Help Please.. To: BEBO@SLAC.Stanford.EDU Cc: majordomo-users@GreatCircle.COM In-Reply-To: <9403171725.AA57131@hebe.SLAC.Stanford.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The distribution I used, majordomo.1.62.tar, contained a resend.README file that gives the options. On Thu, 17 Mar 1994 BEBO@SLAC.Stanford.EDU wrote: > I *might* have been able to figure it out myself if > I had had documentation re: resend and its options. > Do such docs exist? From majordomo-users-owner Thu Mar 17 19:16:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA29891; Thu, 17 Mar 1994 19:16:46 GMT Received: from nd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA29885; Thu, 17 Mar 1994 11:16:38 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Thu, 17 Mar 1994 14:16:19 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA01982; Thu, 17 Mar 94 14:24:47 -0500 Date: Thu, 17 Mar 94 14:24:47 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9403171924.AA01982@nowaksg.chem.nd.edu> To: majordomo-users@greatcircle.com Subject: Hostile Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I got a message from Majordomo today I don't understand. "MAJORDOMO ABORT HOSTILE ADDRESS .........." What does this mean and what am I supposed to do about it? Mike | Mike Buening Why's the rich man busy dancing | | Beamer (the monster cocker) while the poor man pays the band? | | mike@nowaksg.chem.nd.edu | From majordomo-users-owner Fri Mar 18 08:14:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA02915; Fri, 18 Mar 1994 08:14:21 GMT Received: from nova.unix.portal.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA02909; Fri, 18 Mar 1994 00:14:14 -0800 Received: from jobe.shell.portal.com (jobe.shell.portal.com [156.151.1.104]) by nova.unix.portal.com (8.6.7/8.6.5) with ESMTP id AAA14064 for ; Fri, 18 Mar 1994 00:15:27 -0800 Received: (chan@localhost) by jobe.shell.portal.com (8.6.7/8.6.5) id AAA28195 for majordomo-users@greatcircle.com; Fri, 18 Mar 1994 00:15:25 -0800 Date: Fri, 18 Mar 1994 00:15:25 -0800 From: Jeff Chan Message-Id: <199403180815.AAA28195@jobe.shell.portal.com> To: majordomo-users@greatcircle.com Subject: mysterious error message Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm still trying to get my majordomo running. We made a user and group majordomo & setuid wrapper to daemon & setgid to majordomo. everything else is 777 for chan & my group. I'm getting a mysterious error message. Does this right any bells? Any suggestions would be greatly appreciated. Jeff Chan ----- From daemon Fri Mar 18 00:02:24 1994 Received: from localhost (localhost) by jobe.shell.portal.com (8.6.7/8.6.5) with internal id AAA27195; Fri, 18 Mar 1994 00:02:23 -0800 Date: Fri, 18 Mar 1994 00:02:23 -0800 From: Mail Delivery Subsystem Subject: Returned mail: unknown mailer error 255 Message-Id: <199403180802.AAA27195@jobe.shell.portal.com> To: chan Status: R The original message was received at Fri, 18 Mar 1994 00:02:23 -0800 from chan@localhost ----- The following addresses had delivery problems ----- "|/u1/chan/majordomo/wrapper majordomo" (unrecoverable error) (expanded from: majordomo) ----- Transcript of session follows ----- YOU HAVEN'T DISABLED SET-ID SCRIPTS IN THE KERNEL YET! FIX YOUR KERNEL, PUT A C WRAPPER AROUND THIS SCRIPT, OR USE -u AND UNDUMP! 554 "|/u1/chan/majordomo/wrapper majordomo"... unknown mailer error 255 ----- Original message follows ----- Return-Path: chan Received: (chan@localhost) by jobe.shell.portal.com (8.6.7/8.6.5) id AAA27193 for majordomo; Fri, 18 Mar 1994 00:02:23 -0800 Date: Fri, 18 Mar 1994 00:02:23 -0800 From: Jeff Chan Message-Id: <199403180802.AAA27193@jobe.shell.portal.com> To: majordomo help From majordomo-users-owner Fri Mar 18 08:43:32 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA02974; Fri, 18 Mar 1994 08:43:32 GMT Received: from LUGA.latrobe.edu.au by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA02968; Fri, 18 Mar 1994 00:43:21 -0800 Received: from indigo.latrobe.edu.au by LUGA.latrobe.edu.au with SMTP id AA21489 (5.67a/IDA-1.5/LTU-1.0 for <@luga.latrobe.edu.au:majordomo-users@GreatCircle.COM>); Fri, 18 Mar 1994 17:43:07 +1000 Received: by indigo.latrobe.edu.au (931110.SGI/911001.SGI) for @luga.latrobe.edu.au:majordomo-users@GreatCircle.COM id AA26448; Fri, 18 Mar 94 18:41:47 +1100 Date: Fri, 18 Mar 1994 18:41:46 +1100 (EDT) From: Darelle Ng Reply-To: Darelle Ng Subject: control characters in subscriber's address To: majordomo-users@GreatCircle.COM Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have the problem of someone accidentally put a control character in his email address when subscribing. The mailing list that he subscribed to will contain the control character and no one can send mail to that mailing list as it will bounce. Here is the part of the bounce message that I received: While talking to luga.latrobe.edu.au: >>> RCPT To: <<< 554 /local/mail-lists/Majordomo/lists/demo-test: line 4: ?latrobe.edu.au... address contained invalid control char(s) 554 demo-test@latrobe.edu.au... Service unavailable The ? in front of the address is actually the control character. The test message did not even get to those 'normal' addresses before the control character. Has any one have this problem before? Regards, Darelle Ng La Trobe University From majordomo-users-owner Fri Mar 18 20:53:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA05074; Fri, 18 Mar 1994 20:53:04 GMT Received: from mailhost.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA05068; Fri, 18 Mar 1994 12:52:56 -0800 Received: by mailhost.interaccess.com (5.67/1.37) id AA27785; Fri, 18 Mar 94 14:51:34 -0600 From: steve@mailhost.interaccess.com (Steve Norton) Message-Id: <9403182051.AA27785@mailhost.interaccess.com> Subject: Re: control characters in subscriber's address To: D.Ng@latrobe.edu.au Date: Fri, 18 Mar 1994 14:51:33 -40962758 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Darelle Ng" at Mar 18, 94 06:41:46 pm X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 1023 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I have the problem of someone accidentally put a control character in his > email address when subscribing. The mailing list that he subscribed to > will contain the control character and no one can send mail to that > mailing list as it will bounce.... > ... > Has any one have this problem before? Yes, I've seen this happen several times. My problem has always been with Eudora for the Macintosh. Apparently (I'm 50% sure this is what happens) the user can enter a delete key in the name field (instead of using backspace) and messages get tagged with 'reply to: luzer@yomama.com'. Some email programs (i.e. pine) will ignore it, some (i.e. elm) will barf on seeing this. My solution has been to beat the user on the head and tell them to re-enter their return address. However, I have been looking into 1) adding a rule or two to sendmail.cf (difficult at best because I'm not sure sendmail will like having the char in it), and 2) adding a little bit of code to majordomo to ignore it. Any other ideas? From majordomo-users-owner Fri Mar 18 23:24:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA05532; Fri, 18 Mar 1994 23:24:58 GMT Received: from midway.uchicago.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA05526; Fri, 18 Mar 1994 15:24:44 -0800 From: ckoenig@midway.uchicago.edu Received: from kimbark.uchicago.edu by midway.uchicago.edu for majordomo-users@greatcircle.com Fri, 18 Mar 94 17:24:50 CST Received: from localhost.uchicago.edu by kimbark.uchicago.edu (4.1/UCCO-1.0A) id AA05889; Fri, 18 Mar 94 17:23:18 CST Message-Id: <9403182323.AA05889@kimbark.uchicago.edu> To: majordomo-users@greatcircle.com Subject: Fwd: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager Date: Fri, 18 Mar 94 17:23:18 -0600 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Someone just forwarded this to me. Comments from Majordomo people? -- Chris Koenigsberg, ckk@uchicago.edu. ------- Forwarded Message Date: Fri, 18 Mar 1994 16:06:28 -0600 To: ckk@uchicago.edu From: Gleason Sackman (by way of Hal Bloom ) Subject: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager (fwd) Forwarded by Gleason Sackman - InterNIC net-happenings moderator ()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()() - ---------- Text of forwarded message ---------- Date: Fri, 18 Mar 94 15:38:14 EST From: Marco Hernandez To: Multiple recipients of list Subject: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager CREN is pleased to announce that it has acquired ownership rights to the Unix(TM)-TCP/IP list management and file distribution software developed by Anastasios Kotsikonas ("Tasos") and known as "ListProcessor" and "ListProc". List managers are essential for supporting global scholarly discussion and collaboration over the Internet and for distributing materials in electronic formats. Version 6.0c of ListProc is presently being used at more than 320 sites throughout the world to manage some 4500 electronic mailing lists. Testing and production experience by CREN and others has proved that ListProc, when used with the ZMAILER Mail Transfer Agent (available at no cost from the University of Toronto via anonymous ftp at cs.toronto.edu in /pub/zmailer.tar), can easily support active lists with several thousand subscribers on even a small Unix host. or example, CREN is currently hosting 11 public lists and sending an average of 20,000 pieces of SMTP mail daily, over 2 Megabytes per day, on a small Unix processor. EDUCOM's EDUPAGE list has close to 12,000 subscribers and takes around an hour for distribution. Alternatively, other mail transfer agents are also supported. CREN in partnership with Tasos is developing enhanced versions of this software. The first release of the CREN version of ListProcessor is scheduled to be available in the June 1994 time frame. A later release scheduled for the end of 1994 will include the capability of hierarchically distributing list postings and other enhancements not available in the first release. CREN will thereafter continue to improve and develop this software in support of its strategic plan, adding new capabilities as requirements and standards evolve. Version 6.0c (the current version) of ListProc will remain available at no cost for non-commercial use but all further development of this software will be owned and licensed by CREN. CREN will provide each of its non-profit members one free copy of each of these two releases of its ListProcessor software (for use on a single computer of any size), and additional copies will be priced to encourage departmental use. CREN's international Cooperating Networks that are willing to provide support to their member organizations for CREN's ListProcessor will be able to arrange with CREN to similarly make available a single free copy of the first and second release of this software for each of their non-profit educational member organizations, and to license additional copies for these member organizations. For-profit CREN members and organizations that are neither CREN members nor members of participating Cooperative Networks will also be able to license ListProcessor at very competitive fees that will be announced at the time of release of the CREN versions. Several popular implementations of Unix will be supported. In addition to development of the ListProcessor server, CREN expects to contract for the development of Mac and Windows-based list management client software. That software will be a part of CREN's "plug and play" client software suite and will be designed to facilitate the use of the server for list subscription, unsubscription, information requests, and other list-management functions required of list owners and list initiators. The "plug and play" initiative is discussed in the CREN strategic plan described in the CREN Brochure and newsletters available via ftp or Gopher from info.cren.net. CREN is also pursuing plans that will enable the distribution of scholarly materials such as electronic journals in multimedia formats. Continuing support for the use of this software will be provided electronically by CREN for its members and other organizations that license the software from CREN. Cooperating Networks are responsible for supporting the use of the software by their member organizations. Feedback from all users of the software, on their requirements, will be encouraged by CREN as part of the continuing development process. The CREN versions are being developed consistent with the ideas published last fall in CREN's RFP for list-management software (available from info.cren.net via Gopher and ftp). CREN will actively cooperate with the Internet Engineering Task Force (IETF) in the development of open Internet standards leading to improvements in the performance and functionality of this and related software. CREN will also develop improved documentation for users, list owners, and installers/managers of the software. Ken King Executive Director, CREN Jim Conklin Director, BITNET/CREN Network Information Center ------- End of Forwarded Message From majordomo-users-owner Fri Mar 18 23:36:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA05576; Fri, 18 Mar 1994 23:36:43 GMT Received: from rip.psg.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA05570; Fri, 18 Mar 1994 15:36:36 -0800 Received: by rip.psg.com (Smail3.1.28.1 #6) id m0pho5r-00030YC; Fri, 18 Mar 94 15:36 PST Message-Id: Date: Fri, 18 Mar 94 15:36 PST From: randy@psg.com (Randy Bush) To: majordomo-users@greatcircle.com Subject: Re: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager References: <9403182323.AA05889@kimbark.uchicago.edu> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Someone just forwarded this to me. Comments from Majordomo people? -- > Subject: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager BITNET and Tasos's ListProcessor, a marriage made in heaven. From majordomo-users-owner Sat Mar 19 19:49:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA08113; Sat, 19 Mar 1994 19:49:29 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA08107; Sat, 19 Mar 1994 11:49:19 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id OAA29991 for ; Sat, 19 Mar 1994 14:49:10 -0500 Message-Id: <199403191949.OAA29991@bosnia.pop.psu.edu> To: majordomo-users@GreatCircle.COM Subject: Re: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager In-reply-to: Your message of "Fri, 18 Mar 1994 15:36:00 PST." 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 Date: Sat, 19 Mar 1994 14:49:09 -0500 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Randy Bush writes: >> Someone just forwarded this to me. Comments from Majordomo people? -- >> Subject: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager > >BITNET and Tasos's ListProcessor, a marriage made in heaven. Hey I didn't see your smiley.. :-) ListProcessor has got to be the single worst mailing list package I have ever seen. I hope it gets a total rewrite, cause it sure could use it. Gimme Majordomo any day of the week. (he says as he turns to the choir...) BTW those with access, there's an interesting thread regarding this in bit.listserv.lstsrv-l --Dave From majordomo-users-owner Sun Mar 20 00:32:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA08939; Sun, 20 Mar 1994 00:32:46 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA08931; Sat, 19 Mar 1994 16:32:40 -0800 Message-Id: <199403200032.QAA08931@mycroft.GreatCircle.COM> To: ckoenig@midway.uchicago.edu cc: majordomo-users@greatcircle.com Subject: Re: Fwd: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager In-reply-to: Your message of Fri, 18 Mar 94 17:23:18 -0600 Date: Sat, 19 Mar 1994 16:32:39 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk ckoenig@midway.uchicago.edu writes: # Someone just forwarded this to me. Comments from Majordomo people? -- # Chris Koenigsberg, ckk@uchicago.edu. What kind of comments do you expect? Something like indignant outrage and condemnation? More power to 'em; I looked at ListProc before I decided to write Majordomo, and decided it didn't meet my needs. I released Majordomo because I thought other people might find it useful too. If ListProc meets someone's needs better than Majordomo, then they should use ListProc. I'm _really_ not interested in getting involved with any sort of "competition" between Majordomo and ListProc (or any other list management package, for that matter). -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Mon Mar 21 03:09:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA13951; Mon, 21 Mar 1994 09:35:38 GMT Received: from sun2.nsfnet-relay.ac.uk by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA13945; Mon, 21 Mar 1994 01:35:24 -0800 Via: uk.ac.exeter; Mon, 21 Mar 1994 09:34:56 +0000 Received: from noether by exub.exeter.ac.uk with SMTP (PP) id <14692-0@exub.exeter.ac.uk>; Mon, 21 Mar 1994 09:34:33 +0000 Received: from euclid by noether.maths.exeter.ac.uk; Mon, 21 Mar 94 09:34:29 GMT From: james@maths.exeter.ac.uk Message-Id: <4317.9403210934@maths.exeter.ac.uk> Subject: Re: Fwd: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager To: majordomo-users@greatcircle.com Date: Mon, 21 Mar 94 9:34:25 GMT In-Reply-To: <199403200032.QAA08931@mycroft.GreatCircle.COM>; from "Brent Chapman" at Mar 19, 94 4:32 pm X-Mailer: ELM [version 2.3 PL3] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Brent Chapman wrote > >ckoenig@midway.uchicago.edu writes: > ># Someone just forwarded this to me. Comments from Majordomo people? -- ># Chris Koenigsberg, ckk@uchicago.edu. > >What kind of comments do you expect? Something like indignant outrage >and condemnation? I suppose the point is that listserv was free but it wont be in the near future so there might be some migration away from it- towards majordomo -- James Andrews, Computer Development Officer, Exeter University Maths Dept From majordomo-users-owner Mon Mar 21 16:37:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA15422; Mon, 21 Mar 1994 16:37:28 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA15416; Mon, 21 Mar 1994 08:37:21 -0800 Received: from bolis by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA04907; Mon, 21 Mar 94 08:36:58 -0800 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0pimal-0002Z1C; Mon, 21 Mar 94 08:12 PST Message-Id: From: Alan Millar Subject: Re: Fwd: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager To: ckoenig@midway.uchicago.edu Date: Mon, 21 Mar 1994 08:12:38 -0800 (PST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <9403182323.AA05889@kimbark.uchicago.edu> from "ckoenig@midway.uchicago.edu" at Mar 18, 94 05:23:18 pm Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1011 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst ckoenig@midway.uchicago.edu spake of these matters: > Someone just forwarded this to me. Comments from Majordomo people? -- > CREN is pleased to announce that it has acquired ownership rights to > the Unix(TM)-TCP/IP list management and file distribution software > developed by Anastasios Kotsikonas ("Tasos") and known as "ListProcessor" > and "ListProc". It seems to me rather surprising, considering that CREN already bought the rights to LISTSERV, which was in the process of being ported to Unix last I heard a few months ago. Perhaps that project didn't pan out. I would expect an increase in Majordomo sites as people look elsewhere for free list management software. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ If only we were all weiner dogs, our problems would be solved! -Brave Little Toaster From majordomo-users-owner Mon Mar 21 16:53:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA15671; Mon, 21 Mar 1994 16:53:56 GMT Received: from trantor.harris-atd.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA15665; Mon, 21 Mar 1994 08:53:48 -0800 Received: from melmac.harris-atd.com by trantor.harris-atd.com (4.1/1.14) id AA16479; Mon, 21 Mar 94 11:52:52 EST Message-Id: <9403211652.AA16479@trantor.harris-atd.com> Received: by melmac.harris-atd.com (5.0/SMI-SVR4) id AA02910; Mon, 21 Mar 1994 11:52:50 +0500 Date: Mon, 21 Mar 1994 11:52:50 +0500 From: chuck@trantor.harris-atd.com (Chuck Musciano) To: majordomo-users@greatcircle.com Subject: Address rewrites? X-Sun-Charset: US-ASCII Content-Length: 919 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk When messages get forwarded to members of my lists, the sender's address gets rewritten as a composite Usenet/Internet address. For example, my machine is melmac.ess.harris.com, the lists are on info.ess.harris.com. If I send a message to "some-list@info.ess.harris.com", the resulting message that gets broadcast has these headers: From some-list-owner@info Mon Mar 21 11:07:43 1994 To: some-list@info.ess.harris.com Date: Mon, 21 Mar 1994 16:06:48 GMT From: melmac!chuck@info.ess.harris.com (Chuck Musciano) Why does it rewrite my addres that way? Why doesn't the address come through as "chuck@melmac.ess.harris.com"? Chuck Musciano ARPA: chuck@trantor.harris-atd.com Harris Corporation AOL : CMusciano PO Box 37, MS 16/1912 AT&T: (407) 727-6131 Melbourne, FL 32902 Fax : (407) 729-3363 A good newspaper is never good enough, but a lousy newspaper is a joy forever. -- Garrison Keillor From majordomo-users-owner Mon Mar 21 17:21:35 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA15889; Mon, 21 Mar 1994 17:21:35 GMT Received: from ora.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA15883; Mon, 21 Mar 1994 09:21:28 -0800 Received: from localhost by ruby (8.6.5/) Message-Id: <199403211720.JAA16938@ruby> From: Jerry Peek Date: Mon, 21 Mar 1994 09:20:25 EST In-Reply-To: james@maths.ex.ac.uk "Re: Fwd: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager" (Mar 21, 9:34) X-Mailer: Mail User's Shell (7.2.0 10/31/90) To: james@maths.ex.ac.uk, majordomo-users@GreatCircle.COM Subject: Re: Fwd: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Mar 21, 9:34, james@maths.ex.ac.uk wrote: } I suppose the point is that listserv was free but it wont be in the near } future so there might be some migration away from it- towards majordomo There's been more info on the unix-listproc since that original posting. Tasos has made it clear that listproc 6.0c will be around, that it'll be free, and that he'll keep doing bug fixes. I'm glad -- because some of the features, like the interactive TCP access to listproc, are really useful; I don't think any other MLMs have them. Of course, listproc is slightly ;-) more complicated to install/maintain than Majordomo... --Jerry Peek, jerry@ora.com From majordomo-users-owner Mon Mar 21 19:51:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA16490; Mon, 21 Mar 1994 19:51:18 GMT Received: from utdallas.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA16484; Mon, 21 Mar 1994 11:51:11 -0800 Received: from frog.utdallas.edu by utdallas.edu (ZMailer 2.1.3 #231) with BLIMP id <13918>; Mon, 21 Mar 1994 13:51:08 -0600 Subject: Re: Fwd: CREN Announces Acquisition of UNIX(TM) TCP/IP List Manager From: Billy Barron To: AMillar@bolis.sf-bay.org Date: Mon, 21 Mar 1994 13:48:14 -0600 Cc: ckoenig@midway.uchicago.edu, majordomo-users@GreatCircle.COM In-Reply-To: from "Alan Millar" at Mar 21, 94 10:12:38 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 506 Message-Id: <94Mar21.135108cst.13918@utdallas.edu> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In reply to Alan Millar's message: > >It seems to me rather surprising, considering that CREN already bought >the rights to LISTSERV, which was in the process of being ported to Unix >last I heard a few months ago. Perhaps that project didn't pan out. > They bought the rights to the VM version of LISTSERV not the future UNIX version of LISTSERV from Lsoft. Note: I heard this directly from a CREN board member. --- Billy Barron, Network Services Manager, Univ of Texas at Dallas billy@utdallas.edu From majordomo-users-owner Tue Mar 22 18:00:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA21544; Tue, 22 Mar 1994 18:00:53 GMT Received: from Post-Office.UH.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA21537; Tue, 22 Mar 1994 10:00:23 -0800 Received: from tcamc.uh.edu (Sina.TCAMC.UH.EDU) by Post-Office.UH.EDU (PMDF V4.2-14 #5185) id <01HA9SULY0N400AOJI@Post-Office.UH.EDU>; Tue, 22 Mar 1994 11:59:59 CST Received: from sina (localhost) by tcamc.uh.edu (5.0/SMI-SVR4) id AA26686; Tue, 22 Mar 1994 11:58:40 +0600 Date: Tue, 22 Mar 1994 11:58:40 -0600 From: Jason L Tibbitts III Subject: Several questions To: majordomo-users@greatcircle.com Message-id: <9403221758.AA26686@tcamc.uh.edu> Content-transfer-encoding: 7BIT content-length: 1194 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm just getting set up after installing Majordomo. As I'm the hacking type, I went with the current beta. Good stuff. I have a couple of general questions: 1. I use MH, more specifically MH-E under Emacs. In browsing the archives I see that there are other MH users here, so perhaps you can help. I notice that when a bounce comes to my maildrop, doing an inc splits it into two messages, probably based on the second From: header in the bounce. This makes it difficult to send the bounce to approve. Can I keep MH from splitting the message? Failing that, is there some way to make majordomo quote the bounced message and have approve unquote it? 2. Does anyone have any MH-E - Emacs code for easy approvals? 3. When browsing the archives I see that originally approve was just a hack to use in MH. Now in the BUGS section of the approve manpage it says that MH is not supported. What happened? Thanks! --- Jason L. Tibbitts III - tibbs@math.uh.edu - 713/743-8687 - 221SR1 System Admin: University of Houston Supercomputing Support Services Texas Center for Advanced Molecular Computation GM/CS/S d--- -p+ c++++ l++ u+++ e+ m---(++) n--- s/-- h* f+ g+ w+ t- r- x+** From majordomo-users-owner Tue Mar 22 19:26:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA21815; Tue, 22 Mar 1994 19:26:24 GMT Received: from deeptht.armory.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA21809; Tue, 22 Mar 1994 11:26:17 -0800 Subject: New list To: majordomo-users@greatcircle.com Date: Tue, 22 Mar 1994 11:26:23 -0800 (PST) From: Sylvia Caras Organization: Mood Matters X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 501 Message-ID: <9403221126.aa08293@deeptht.armory.com> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am just starting a list, and my sysop has just installed majordomo. I receive mail from digested lists via majordomo, and would like to add this feature to my own list. How? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ sc@armory.com v/f:408 426 5335 Sylvia Caras, 146-5 Chrystal Ter, Santa Cruz CA 95060 It is not up to you to finish the work, but neither are you free to not take it up. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From majordomo-users-owner Tue Mar 22 22:09:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA22303; Tue, 22 Mar 1994 22:09:43 GMT Received: from ramsay.stat.uiuc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA22290; Tue, 22 Mar 1994 14:09:33 -0800 Received: from atropa.stat.uiuc.edu by ramsay.stat.uiuc.edu with SMTP id AA13974 (5.67a/IDA-1.5 for ); Tue, 22 Mar 1994 16:09:45 -0600 Date: Tue, 22 Mar 1994 16:09:45 -0600 From: Arek Dreyer Message-Id: <199403222209.AA13974@ramsay.stat.uiuc.edu> To: Majordomo-Users@greatcircle.com Subject: -a and other flags Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk When I use -a and -A flags in a list alias, it seems that other flags get stripped out, like the "-p bulk" flag. I want to be able to set a simple password to moderate traffic, but I also want to flag other mailers that this is bulk mail. I tried putting the -a and -A flags before the other flags but this doesn't seem to work. How can I get these two flags to work together? Thanks -arek ------------------------------------------------------------------------- Arek Dreyer; Department of Statistics; University of IL at Urbana Champaign 101 Illini Hall; 725 South Wright Street; Champaign, IL 61820 arek@uiuc.edu (217)-333-2167voice (217)-244-7190fax From majordomo-users-owner Fri Mar 25 19:01:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA09594; Fri, 25 Mar 1994 19:01:57 GMT Received: from info.census.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA09588; Fri, 25 Mar 1994 11:01:50 -0800 Received: (from cstuber@localhost) by info.census.gov (8.6.8/8.6.6) id OAA05173 for majordomo-users@greatcircle.com; Fri, 25 Mar 1994 14:01:41 -0500 Date: Fri, 25 Mar 1994 14:01:41 -0500 From: Chris.Stuber@Census.GOV (Chris Stuber (TCO)) Message-Id: <199403251901.OAA05173@info.census.gov> To: majordomo-users@greatcircle.com Subject: Can you have multiple owners? Content-Length: 286 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Fellow Majordomo Users, Is there a way to multiple list-owners for a particular list? I had it set up like: List-Owner: user1, user2, user3 but only user1 got the approvals. The others got nothing. Any ideas how to have multiple owners? Thanks -Chris Stuber (cstuber@census.gov) From majordomo-users-owner Sat Mar 26 07:14:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA06755; Sat, 26 Mar 1994 07:14:43 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA06749; Fri, 25 Mar 1994 23:14:34 -0800 Received: from bolis by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA28142; Fri, 25 Mar 94 22:55:34 -0800 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0pkRtd-0002a9C; Fri, 25 Mar 94 22:31 PST Message-Id: From: Alan Millar Subject: Re: Can you have multiple owners? To: Chris.Stuber@Census.GOV (Chris Stuber (TCO)) Date: Fri, 25 Mar 1994 22:30:58 -0800 (PST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199403251901.OAA05173@info.census.gov> from "Chris Stuber (TCO)" at Mar 25, 94 02:01:41 pm Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2557 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Chris Stuber (TCO) spake of these matters: > > > Fellow Majordomo Users, > Is there a way to multiple list-owners for a particular list? > I had it set up like: > > List-Owner: user1, user2, user3 > > but only user1 got the approvals. The others got nothing. > Any ideas how to have multiple owners? Approval messages don't go to list-owner. They go to list-approval. If you don't have list-approval pointing to list-owner, there's your problem. On a related note, here's what I did for a list that has ownership changes: I made the owner/approval of the main list a closed, private list itself, so the owner(s) can be changed remotely by password. Here's the aliases: #---------------------------------------------------------- ACT: "|/usr/local/mail/majordomo/wrapper resend -M 795000 \ -l ACT -f Owner-ACT -h Bolis.SF-Bay.org \ ACT-outgoing" owner-ACT: ACT-owner ACT-outgoing: :include:/usr/local/mail/lists/act, ACT-archive owner-ACT-outgoing: ACT-owner ACT-archive: "|/usr/local/mail/majordomo/wrapper archive.pl \ /usr/local/mail/files/act" owner-ACT-archive: ACT-owner ACT-request: listserv owner-ACT-request: ACT-owner ACT-approval: :include:/usr/local/mail/lists/act-owner, AMillar owner-ACT-approval: amillar ACT-owner: act-approval owner-ACT-owner: amillar #---------------------------------------------------------- These are all standard except for the "ACT-approval" line, where the owner list is included. Putting myself on there assures that things won't fall apart even if the list is accidentally emptied. The list files are normal: -rw-rw-r-- 1 listserv listserv 2442 Mar 25 19:28 act -rw-r--r-- 1 listserv listserv 2283 Sep 9 1993 act.info -rw-rw---- 1 listserv listserv 9 Feb 12 01:53 act.passwd Except that the following files are also required: -rw-r--r-- 1 listserv listserv 97 Mar 2 20:42 act-owner -rw-r--r-- 1 listserv listserv 0 Dec 3 14:08 act-owner.closed -rw------- 1 listserv listserv 7 Dec 3 13:32 act-owner.passwd -rw-r--r-- 1 listserv listserv 0 Dec 3 14:08 act-owner.private The only thing I don't like about it is that the act-owner list shows up in the "lists" command, but that will be fixed in Majordomo 2.0 (right?) - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ I believe the word you're looking for is "AAAAAAGHHHHHH!!!!" -Batman Returns From majordomo-users-owner Sun Mar 27 16:49:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA21483; Sun, 27 Mar 1994 16:49:30 GMT Received: from algol.cs.umbc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA21477; Sun, 27 Mar 1994 08:49:22 -0800 Received: from topdog.cs.umbc.edu by algol.cs.umbc.edu with SMTP id AA06975 (5.65c/IDA-1.4.4 for ); Sun, 27 Mar 1994 11:49:43 -0500 Received: by topdog.cs.umbc.edu id AA10285 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Sun, 27 Mar 1994 11:49:42 -0500 Date: Sun, 27 Mar 1994 11:49:42 -0500 From: Timothy Finin Message-Id: <199403271649.AA10285@topdog.cs.umbc.edu> To: majordomo-users@greatcircle.com Cc: finin@cs.umbc.edu Subject: files visible via INDEX, but can't GET them. Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have a list with a set of files. If I do an INDEX, I can see the files: From: majordomo To: Tim.Finin Subject: Majordomo results Date: Sun, 27 Mar 1994 10:57:19 -0500 -- >>>> >>>> index kqml total 1892 -rw-r--r-- 1 finin 268417 Oct 29 1992 KR92-KQML-slides.ps -rw-r--r-- 1 finin 445 Aug 14 1992 README ... But if I try to retrieve a file, I get: From: majordomo To: Tim.Finin Subject: Majordomo results Date: Sun, 27 Mar 1994 11:02:07 -0500 -- >>>> get kqml README #### No such file 'README' for list 'kqml' Any suggestions? Tim From majordomo-users-owner Sun Mar 27 20:14:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA22396; Sun, 27 Mar 1994 20:14:14 GMT Received: from elroy.ocis.temple.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA22387; Sun, 27 Mar 1994 12:13:55 -0800 Received: by elroy.ocis.temple.edu (5.61/25) id AA18738; Sun, 27 Mar 94 15:13:45 -0500 Date: Sun, 27 Mar 1994 15:04:18 -0500 (EST) From: The Shrimmer Subject: What am i doing wrong.? To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Greets- Tell me where/what I am doing wrong. As after compiling mjdomo nuffin happens. Where is that thingy that is hiding from my eyes. uid=major gid=majordom wbin=/majordom (for now, after it works fine will be moved elsewhere) system=MIPS 2.*.*, CDC 4680 sendmail.cf has an entry as trusted-T for major. ________________________________________________________________________ Relevant extract of Makefile: ------------------------------------------------------- # This is where "wrapper" looks for the programs it's supposed to run. W_BIN=/majordom # This is the environment that (along with LOGNAME and USER inherited from the # parent process, and without the leading "W_" in the variable names) gets # passed to processes run by "wrapper" W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=/etc/majordomo.cf # Use these settings for BSD-based systems, including SunOS 4.x. If you're # using a POSIX-compliant system (including SysV and BSDI), comment these # settings out, and uncomment the POSIX settings below. W_USER=major W_GROUP=majordom W_CHOWN=${W_USER}.${W_GROUP} W_CHMOD=6755 Result = compiles fine.(without errors showing up) Relevant extract of /etc/majordomo.cf: ----------------------------------------------------------- $whereami = "elroy.ocis.temple.edu"; # $whoami -- Who do users send requests to me as? $whoami = "major@$whereami"; # $whoami_owner -- Who is the owner of the above, in case of problems? $whoami_owner = "Major-Owner@$whereami"; # $homedir -- Where can I find my extra .pl files, like majordomo.pl, # shlock.pl, and majordomo_version.pl? $homedir = "/majordom"; # $listdir -- Where are the mailing lists? $listdir = "/majordom/Doc/samples"; (for now just to test, later another dir) Relevant extract of /etc/aliases: ----------------------------------------------------------- # Majordomo # majordomo: "|/majordom/wrapper majordomo" majordomo-owner: major owner-majordomo: major # # Sample mailing list # sample: "|/majordom/wrapper resend -p bulk -M 10000 -l Sample -f Sample-Owner -h elroy.ocis.temple.edu -s sample-outgoing" owner-sample: sample-owner sample-outgoing: :include:/majordom/Doc/samples/sample, sample-archive owner-sample-outgoing: sample-owner sample-archive: /majordom/Doc/samples/archive/sample owner-sample-archive: sample-owner sample-request: "|/majordom/wrapper request-answer sample" owner-sample-request: sample-owner sample-approval: major sample-owner: major owner-sample-owner: major Dir. permissions and stuff --------------------------------------------------- drwx------ 5 root bin 1024 Mar 8 17:01 . drwxr-xr-x 26 bin bin 1024 Mar 8 13:54 .. -rw------- 1 major majordom 8012 Oct 25 16:23 Changes -r-------- 1 major majordom 2831 Apr 16 1993 Description drwx------ 4 major majordom 512 Oct 25 16:24 Doc -rw------- 1 major majordom 1636 Mar 8 11:07 Makefile -r-------- 1 major majordom 1677 Sep 30 13:30 Makefile.orig -r-------- 1 major majordom 906 Oct 25 16:24 Manifest -r-------- 1 major majordom 6322 Oct 17 18:43 README -r-------- 1 major majordom 576 Apr 16 1993 TODO drwx------ 2 major majordom 512 Dec 24 1992 Tools -r-x------ 1 major majordom 6082 Oct 17 19:29 approve -r-x------ 1 major majordom 2870 Apr 16 1993 bounce -r-x------ 1 major majordom 2572 Apr 16 1993 bounce-remind drwx------ 2 root bin 512 Mar 8 17:01 lists -r-x------ 1 major majordom 27610 Oct 17 19:47 majordomo -r-------- 1 major majordom 9746 Aug 30 1993 majordomo.pl -rw------- 1 major majordom 33 Oct 25 16:24 majordomo_version.pl -r-x------ 1 major majordom 1320 Apr 12 1993 medit -r-x------ 1 major majordom 2126 Feb 16 1993 new-list -r-x------ 1 major majordom 2922 Jul 24 1993 request-answer -r-x------ 1 major majordom 8302 Sep 5 1993 resend -r-------- 1 major majordom 3738 Sep 3 1993 resend.README -r-------- 1 major majordom 772 Apr 16 1993 sample.aliases -r-------- 1 major majordom 1528 Sep 3 1993 sample.cf -r-------- 1 major majordom 6047 Oct 19 16:21 shlock.pl -rwsr-sr-x 1 major majordom 18050 Mar 8 11:22 wrapper -r-------- 1 major majordom 2329 May 18 1993 wrapper.c -- _I_____________________________________________________________________I_ (_@_) _______ (_@_) | | Sriram N CV | | | | | | | Computer Services | shrim@astro.ocis.temple.edu | | | | Temple University | shrim@elroy.ocis.temple.edu | | | | Philadelphia PA - 19122 --- MIME enclosures ok PGP: | | (___)-----------------------------------------------------------------(___) I I From majordomo-users-owner Sun Mar 27 22:01:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA22814; Sun, 27 Mar 1994 22:01:10 GMT Received: from nd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA22808; Sun, 27 Mar 1994 14:01:00 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Sun, 27 Mar 1994 17:01:17 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA27205; Sun, 27 Mar 94 17:10:00 -0500 Date: Sun, 27 Mar 94 17:10:00 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9403272210.AA27205@nowaksg.chem.nd.edu> To: majordomo-users@greatcircle.com Subject: Digesting Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk If I'm not mistaken I thought I read somewhere that you can arrange a digest format of a list. If so could someone point me in the direction of some instructions for this? Do I need more code? Also, does this mean that all subscribers on a list have to receive the digest or only those subscribers who want digests? Thanks in advance for the information. Mike | Mike Buening Why's the rich man busy dancing | | Beamer (the monster cocker) while the poor man pays the band? | | mike@nowaksg.chem.nd.edu | From majordomo-users-owner Mon Mar 28 09:12:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA24529; Mon, 28 Mar 1994 09:12:08 GMT Received: from nova.unix.portal.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA24523; Mon, 28 Mar 1994 01:11:55 -0800 Received: from jobe.shell.portal.com (jobe.shell.portal.com [156.151.1.104]) by nova.unix.portal.com (8.6.7/8.6.5) with ESMTP id BAA15537 for ; Mon, 28 Mar 1994 01:13:22 -0800 Received: (chan@localhost) by jobe.shell.portal.com (8.6.7/8.6.5) id BAA17426 for majordomo-users@greatcircle.com; Mon, 28 Mar 1994 01:13:21 -0800 Date: Mon, 28 Mar 1994 01:13:21 -0800 From: Jeff Chan Message-Id: <199403280913.BAA17426@jobe.shell.portal.com> To: majordomo-users@greatcircle.com Subject: Any obvious solution? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm trying without sucess to get majordomo up on my machine here. It's a SPARC 10 running SunOS 4.1.3 and sendmail 8.6.7. Here are some relevant files & output. Is there anything obvious I'm doing wrong? Any and all help would be greatly appreciated. Jeff Chan chan@shell.portal.com ----- Script started on Sun Mar 20 23:30:56 1994 /dev/ttyQ5: Not owner jobe: [1]% mail majordomo Subject: help From majordomo-users-owner Mon Mar 28 09:23:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA24593; Mon, 28 Mar 1994 09:23:13 GMT Received: from nova.unix.portal.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA24587; Mon, 28 Mar 1994 01:23:01 -0800 Received: from jobe.shell.portal.com (jobe.shell.portal.com [156.151.1.104]) by nova.unix.portal.com (8.6.7/8.6.5) with ESMTP id BAA15951 for ; Mon, 28 Mar 1994 01:24:30 -0800 Received: (chan@localhost) by jobe.shell.portal.com (8.6.7/8.6.5) id BAA17961; Mon, 28 Mar 1994 01:24:29 -0800 Date: Mon, 28 Mar 1994 01:24:29 -0800 From: Jeff Chan Message-Id: <199403280924.BAA17961@jobe.shell.portal.com> To: chan@shell.portal.com, majordomo-users@GreatCircle.COM Subject: Re: Any obvious solution? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Trying again; Sorry for the long post. Jeff C. ----- >Script started on Sun Mar 20 23:30:56 1994 >/dev/ttyQ5: Not owner >jobe: [1]% mail majordomo >Subject: >help >. >EOT >jobe: [2]% wrapper majordomo >wrapper: Command not found. >jobe: [3]% ./wrapper majorxo  domo >From: chan > >help >majordomo[15462] {chan} chan... Recipient names must be specified >help >^DSaving message in /u1/chan/dead.letter >jobe: [4]% cat ~/dead.letter >From chan Sun Mar 20 23:31:05 1994 >Return-Path: chan >Received: (chan@localhost) by jobe.shell.portal.com (8.6.7/8.6.5) id XAA15148; Sun, 20 Mar 1994 23:31:05 -0800 >Date: Sun, 20 Mar 1994 23:31:05 -0800 >Message-Id: <199403210731.XAA15148@jobe.shell.portal.com> >To: chan >From: >Subject: Majordomo results >Reply-To: > >-- > >>>>> help >This is Brent Chapman's "Majordomo" mailing list manager, version 1.62. > >It understands the following commands: > > subscribe [
] > Subscribe yourself (or
if specified) to the named . > > unsubscribe [
] > Unsubscribe yourself (or
if specified) from the named . > > get > Get a file related to . > > index > Return an index of files you can "get" for . > > which [
] > Find out which lists you (or
if specified) are on. > > who > Find out who is on the named . > > info > Retrieve the general introductory information for the named . > > lists > Show the lists served by this Majordomo server. > > help > Retrieve this message. > > end > Stop processing commands (useful if your mailer adds a signature). > >Commands should be sent in the body of an email message to >"". > >Commands in the "Subject:" line NOT processed. > >If you have any questions or problems, please contact >"". > > >From chan Sun Mar 20 23:31:25 1994 >Return-Path: chan >Received: (chan@localhost) by jobe.shell.portal.com (8.6.7/8.6.5) id XAA15565; Sun, 20 Mar 1994 23:31:25 -0800 >Date: Sun, 20 Mar 1994 23:31:25 -0800 >Message-Id: <199403210731.XAA15565@jobe.shell.portal.com> >To: chan >From: >Subject: Majordomo results >Reply-To: > >-- > >>>>> help >This is Brent Chapman's "Majordomo" mailing list manager, version 1.62. > >It understands the following commands: > > subscribe [
] > Subscribe yourself (or
if specified) to the named . > > unsubscribe [
] > Unsubscribe yourself (or
if specified) from the named . > > get > Get a file related to . > > index > Return an index of files you can "get" for . > > which [
] > Find out which lists you (or
if specified) are on. > > who > Find out who is on the named . > > info > Retrieve the general introductory information for the named . > > lists > Show the lists served by this Majordomo server. > > help > Retrieve this message. > > end > Stop processing commands (useful if your mailer adds a signature). > > >jobe: [6]% tail /etc/aliases > ># ># Majordomo lists run by Jeff Chan (shell user chan) ># >majordomo: "|/u1/chan/majordomo/wrapper majordomo" >majordomo-owner: chan >owner-majordomo: chan > >jobe: [7]% cat majordomo.cf ># $whereami -- What machine am I running on? >$whereami = "shell.portal.com" > ># $whoami -- Who do users send requests to me as? >$whoami = "majordomo@$whereami"; > ># $whoami_owner -- Who is the owner of the above, in case of problems? >$whoami_owner = "majordomo-Owner@$whereami"; > ># $homedir -- Where can I find my extra .pl files, like majordomo.pl, ># shlock.pl, and majordomo_version.pl? >$homedir = "/u1/chan/majordomo"; > ># $listdir -- Where are the mailing lists? >$listdir = "/u1/chan/majordomo-lists"; > ># $log -- Where do I write my log? >$log = "$homedir/Log"; > ># $mailer -- What program and args do I use to send mail? >$mailer = "/usr/lib/sendmail -f\$sender \$to"; > ># Majordomo will look for "get" and "index" files related to $list in ># directory "$filedir/$list$filedir_suffix", so set $filedir and ># $filedir_suffix appropriately. For instance, to look in ># /usr/local/mail/files/$list, use: ># $filedir = "/usr/local/mail/files"; ># $filedir_suffix = ""; # empty string ># or to look in $listdir/$list.archive, use: ># $filedir = "$listdir"; ># $filedir_suffix = ".archive"; > >$filedir = "$listdir"; >$filedir_suffix = ".archive"; > ># What command should I use to process an "index" request? >$index_command = "/bin/ls -lRL"; > ># If you want to use FTPMAIL, rather than local access, for file transfer ># and access, define the following: ># $ftpmail_address = "ftpmail@decwrl.dec.com"; ># $ftpmail_location = "FTP.$whereami"; > ># $Header: /mycroft/brent/majordomo/RCS/sample.cf,v 1.4 1993/09/03 05:35:47 brent Exp $ >jobe: [8]% cat Makefile ># $Source: /mycroft/brent/majordomo/RCS/Makefile,v $ ># $Revision: 1.12 $ ># $Date: 1993/09/30 17:29:42 $ ># $Author: brent $ ># $State: Exp $ ># ># $Header: /mycroft/brent/majordomo/RCS/Makefile,v 1.12 1993/09/30 17:29:42 brent Exp $ ># ># $Locker: $ ># > ># This is where "wrapper" looks for the programs it's supposed to run. >W_BIN=/u1/chan/majordomo > ># This is the environment that (along with LOGNAME and USER inherited from the ># parent process, and without the leading "W_" in the variable names) gets ># passed to processes run by "wrapper" > >W_PATH=/bin:/usr/bin:/usr/ucb >W_HOME=${W_BIN} >W_SHELL=/bin/csh >W_MAJORDOMO_CF=/u1/chan/majordomo/majordomo.cf > ># Use these settings for BSD-based systems, including SunOS 4.x. If you're ># using a POSIX-compliant system (including SysV and BSDI), comment these ># settings out, and uncomment the POSIX settings below. >W_USER=chan >W_GROUP=vip >W_CHOWN=${W_USER}.${W_GROUP} >W_CHMOD=6755 >WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ > -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ > -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" -ldl > ># If you're using a POSIX-compliant system, uncomment this set of parameters ># and comment out the BSD settings above. ># W_UID = 1 ># W_GID = 15 ># W_CHOWN=root ># W_CHMOD=4755 ># WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ ># -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ ># -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" \ ># -DPOSIX_UID=${W_UID} -DPOSIX_GID=${W_GID} -ldl > >default: wrapper > >install: wrapper > >wrapper: wrapper.c > cc ${WRAPPER_FLAGS} -o wrapper wrapper.c > chown ${W_CHOWN} wrapper > chmod ${W_CHMOD} wrapper > >jobe: [9]% ls -Falsg * >total 600 > 1 drwxrwxrwx 4 chan vip 1024 Mar 20 23:35 ./ > 4 drwx--x--x 84 chan vip 4096 Mar 20 16:03 ../ > 8 -rwxrwxrwx 1 chan vip 8012 Oct 25 13:23 Changes* > 3 -rwxrwxrwx 1 chan vip 2831 Apr 16 1993 Description* > 1 drwxrwxrwx 4 chan vip 512 Oct 25 13:24 Doc/ > 2 -rwxrwxrwx 1 chan vip 1666 Mar 20 22:04 Makefile* > 2 -rwxrwxrwx 1 chan vip 1677 Mar 13 13:52 Makefile.bak* > 2 -rwxrwxrwx 1 chan vip 1699 Mar 18 00:21 Makefile.chan* > 1 -rwxrwxrwx 1 chan vip 906 Oct 25 13:24 Manifest* > 7 -rwxrwxrwx 1 chan vip 6322 Oct 17 15:43 README* > 1 -rwxrwxrwx 1 chan vip 576 Apr 16 1993 TODO* > 1 drwxrwxrwx 2 chan vip 512 Dec 24 1992 Tools/ > 6 -rwxrwxrwx 1 chan vip 6082 Oct 17 16:29 approve* > 3 -rwxrwxrwx 1 chan vip 2870 Apr 16 1993 bounce* > 3 -rwxrwxrwx 1 chan vip 2572 Apr 16 1993 bounce-remind* > 2 -rwxrwxrwx 1 chan vip 1057 Mar 13 23:01 f-a.aliases* > 24 -rwxrwxrwx 1 chan vip 24576 Mar 13 21:50 getgroup* > 1 -rwxrwxrwx 1 chan vip 69 Mar 13 21:50 getgroup.c* > 28 -rwxrwxrwx 1 chan vip 27677 Mar 20 23:29 majordomo* > 2 -rwxrwxrwx 1 chan vip 1524 Mar 20 22:12 majordomo.cf* > 28 -rwxrwxrwx 1 chan vip 27657 Mar 13 19:25 majordomo.chan* > 27 -rwx------ 1 chan vip 27610 Mar 20 23:29 majordomo.old* > 10 -rwxrwxrwx 1 chan vip 9746 Aug 30 1993 majordomo.pl* > 288 -rwxrwxrwx 1 chan vip 286720 Feb 13 22:47 majordomo.tar* > 1 -rwxrwxrwx 1 chan vip 33 Oct 25 13:24 majordomo_version.pl* 1 -rwxrwxrwx 1 chan vip 15 Mar 18 00:24 makeme* > 3 -rwxrwxrwx 1 chan vip 2535 Feb 25 09:09 mbox* > 2 -rwxrwxrwx 1 chan vip 1320 Apr 12 1993 medit* > 3 -rwxrwxrwx 1 chan vip 2126 Feb 16 1993 new-list* > 3 -rwxrwxrwx 1 chan vip 2515 Mar 13 23:57 request-answer* > 3 -rwxrwxrwx 1 chan vip 2922 Mar 13 23:43 request-answer.bak* > 9 -rwxrwxrwx 1 chan vip 8302 Sep 5 1993 resend* > 4 -rwxrwxrwx 1 chan vip 3738 Sep 2 1993 resend.README* > 1 -rwxrwxrwx 1 chan vip 772 Apr 16 1993 sample.aliases* > 2 -rwxrwxrwx 1 chan vip 1528 Sep 2 1993 sample.cf* > 6 -rwxrwxrwx 1 chan vip 6047 Oct 19 13:21 shlock.pl* > 1 -rwxrwxrwx 1 chan vip 832 Feb 23 01:27 tar.log* > 7 -rw------- 1 chan vip 6593 Mar 20 23:35 ts0 > 0 -rw------- 1 chan vip 0 Mar 20 23:35 typescript > 24 -rwsr-sr-x 1 chan vip 24576 Mar 20 23:28 wrapper* > 3 -rwxrwxrwx 1 chan vip 2329 May 18 1993 wrapper.c* > 24 -rwxrwxrwx 1 chan vip 24576 Mar 15 14:19 wrapper.chan* > 24 -rwsr-sr-x 1 chan vip 24576 Mar 17 23:58 wrapper.d* > 24 -rwsrwxrwx 1 chan vip 24576 Mar 14 02:08 wrapper.daemon* >jobe: [10]% exit >jobe: [11]% >script done on Sun Mar 20 23:35:47 1994 From majordomo-users-owner Mon Mar 28 14:05:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA25791; Mon, 28 Mar 1994 14:05:00 GMT Received: from beach.cis.ufl.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA25779; Mon, 28 Mar 1994 06:04:51 -0800 Received: from localhost by beach.cis.ufl.edu (8.6.7/8.6.7-cis.ufl.edu) id JAA15162; Mon, 28 Mar 1994 09:04:46 -0500 Message-Id: <199403281404.JAA15162@beach.cis.ufl.edu> To: majordomo-users@greatcircle.com Subject: Majordomo on Linux Date: Mon, 28 Mar 1994 09:04:45 EST From: Stephen P Potter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Does anyone who has used majordomo on linux, with smail, know what the error: 03/27/94 16:10:58: [m0pl26j-0003EUC] note: "|/home/majordomo/bin/wrapper request-answer testlist" ... transport pipe: child returned status EX_5 (5) means? I'm having a hell of a time getting this to work under linux, which is needed for a project I'm working on in another department. Steve From majordomo-users-owner Mon Mar 28 14:59:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA26003; Mon, 28 Mar 1994 14:59:57 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA25997; Mon, 28 Mar 1994 06:59:49 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id KAA01938 for ; Mon, 28 Mar 1994 10:00:10 -0500 Message-Id: <199403281500.KAA01938@bosnia.pop.psu.edu> To: majordomo-users@GreatCircle.COM Subject: Re: Majordomo on Linux In-reply-to: Your message of "Mon, 28 Mar 1994 09:04:45 EST." <199403281404.JAA15162@beach.cis.ufl.edu> 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 Date: Mon, 28 Mar 1994 10:00:09 -0500 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199403281404.JAA15162@beach.cis.ufl.edu>, Stephen P Potter writes: >Does anyone who has used majordomo on linux, with smail, know what the >error: > >03/27/94 16:10:58: [m0pl26j-0003EUC] note: "|/home/majordomo/bin/wrapper >request-answer testlist" ... transport pipe: child returned status EX_5 (5) > >means? According to the original source, wrapper will exit(5) if the execve() fails. This is usually because you compiled with the wrong W_BIN in the Makefile, or the permissions on W_BIN, its parent directories, or on the executables in W_BIN are wrong. Check the actual bounce message that comes back - it should include any error messages that were output by the wrapper. --Dave From majordomo-users-owner Mon Mar 28 16:34:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA26302; Mon, 28 Mar 1994 16:34:37 GMT Received: from beach.cis.ufl.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA26296; Mon, 28 Mar 1994 08:34:27 -0800 Received: from localhost by beach.cis.ufl.edu (8.6.7/8.6.7-cis.ufl.edu) id LAA20935; Mon, 28 Mar 1994 11:34:18 -0500 Message-Id: <199403281634.LAA20935@beach.cis.ufl.edu> To: David Barr cc: majordomo-users@greatcircle.com Subject: Re: Majordomo on Linux In-reply-to: Some random ramblings on Mon, 28 Mar 1994 10:00:09 -0500. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Mon, 28 Mar 1994 11:34:17 EST From: Stephen P Potter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused David Barr to write: | In message <199403281404.JAA15162@beach.cis.ufl.edu>, Stephen P Potter writes > : | >03/27/94 16:10:58: [m0pl26j-0003EUC] note: "|/home/majordomo/bin/wrapper | >request-answer testlist" ... transport pipe: child returned status EX_5 (5) | | Check the actual bounce message that comes back - it should include | any error messages that were output by the wrapper. No bounce message. According to the log file it got delivered to "/home/majordomo/bin/wrapper majordomo", but I never see perl start up, get a bounce, or even get anything to postmaster. Steve From majordomo-users-owner Mon Mar 28 17:39:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA26859; Mon, 28 Mar 1994 17:39:29 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA26851; Mon, 28 Mar 1994 09:39:22 -0800 Message-Id: <199403281739.JAA26851@mycroft.GreatCircle.COM> To: Stephen P Potter cc: majordomo-users@greatcircle.com Subject: Re: Majordomo on Linux In-reply-to: Your message of Mon, 28 Mar 1994 09:04:45 EST Date: Mon, 28 Mar 1994 09:39:21 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Stephen P Potter writes: # Does anyone who has used majordomo on linux, with smail, know what the # error: # # 03/27/94 16:10:58: [m0pl26j-0003EUC] note: "|/home/majordomo/bin/wrapper # request-answer testlist" ... transport pipe: child returned status EX_5 (5) # # means? # # I'm having a hell of a time getting this to work under linux, which is # needed for a project I'm working on in another department. # # Steve "exit(5)" is what "wrapper" does when the "exec" of the script it's trying to run fails. So, looks like "wrapper" isn't finding "request-answer" where it expects to (maybe it's in the wrong place, or isn't executable, or "wrapper" has W_BIN compiled-in wrong and is looking in the wrong place), or can't run it for some other reason (maybe PERL isn't /usr/local/bin/perl on this system, and the first line of "request-answer" hasn't been changed appropriately). -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From majordomo-users-owner Mon Mar 28 20:53:36 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA28308; Mon, 28 Mar 1994 20:53:36 GMT Received: from acadvm1.uottawa.ca by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA28302; Mon, 28 Mar 1994 12:53:23 -0800 Message-Id: <199403282053.MAA28302@mycroft.GreatCircle.COM> Received: from ACADVM1.UOTTAWA.CA by acadvm1.uottawa.ca (IBM VM SMTP V2R2) with BSMTP id 1790; Mon, 28 Mar 94 15:55:29 EST X-Delivery-Notice: SMTP MAIL FROM does not correspond to sender. Received: from ACADVM1.UOTTAWA.CA (TRAMNG) by ACADVM1.UOTTAWA.CA (Mailer R2.07) with BSMTP id 2659; Mon, 28 Mar 94 15:55:28 EST Date: Mon, 28 Mar 94 15:48:31 EST From: Tram Nguyen Subject: Error : Insecure Usage To: majordomo-users@greatcircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I am trying to install Majordomo on our SunOS system but keep running into this error when sending mail to majordomo : /users/majordomo/wrapper: error: insecure usage 554 "º/users/majordomo/wrapper /users/majordomo/majordomo" .. unknown mailer error 2 The wrapper was compiled with no error. I also changed the first lines of the Perl scripts to be /usr/bin/perl instead of /usr/local/bin/perl to correspond with the Perl location on our system. The settings in the Makefile are as follows : # This is where "wrapper" looks for the programs it's supposed to run. W_BIN=/users/majordomo/majordomo # This is the environment that (along with LOGNAME and USER inherited from the # parent process, and without the leading "W_" in the variable names) gets # passed to processes run by "wrapper" W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=/etc/majordomo.cf # Use these settings for BSD-based systems, including SunOS 4.x. If you're # using a POSIX-compliant system (including SysV and BSDI), comment these # settings out, and uncomment the POSIX settings below. W_USER=daemon W_GROUP=majordom W_CHOWN=${W_USER}.${W_GROUP} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" And the majordomo.cf : $whereami = "panda1.uottawa.ca"; $whoami = "Majordomo@$whereami"; $whoami_owner = "Majordomo-Owner@$whereami"; $listdir = "/users/majordomo/lists"; Any ideas or pointers where I might have gone wrong are greatly appreciated. Thanks for your help. Tram Nguyen, University of Ottawa. From majordomo-users-owner Mon Mar 28 21:09:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA28401; Mon, 28 Mar 1994 21:09:27 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA28393; Mon, 28 Mar 1994 13:09:16 -0800 From: rogerk@queernet.org Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0plObX-000MU8C; Mon, 28 Mar 94 13:12 PST Message-Id: To: Tram Nguyen cc: majordomo-users@GreatCircle.COM Subject: Re: Error : Insecure Usage In-reply-to: Your message of Mon, 28 Mar 94 15:48:31 -0500. <199403282053.MAA28302@mycroft.GreatCircle.COM> Date: Mon, 28 Mar 94 13:12:13 PST Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I am trying to install Majordomo on our SunOS system but keep running > into this error when sending mail to majordomo : > > /users/majordomo/wrapper: error: insecure usage > 554 ":/users/majordomo/wrapper /users/majordomo/majordomo" .. unknown mailer > error 2 FAQ #1. After the document was written, wrapper was changed so that it always runs files in the binary directory, and takes only the filename, not a pathname. Your alias should say: |/users/majordomo/wrapper majordomo --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Mon Mar 28 21:21:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA28487; Mon, 28 Mar 1994 21:21:37 GMT Received: from dragonfly.cis.ufl.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA28481; Mon, 28 Mar 1994 13:21:30 -0800 Received: from localhost by dragonfly.cis.ufl.edu (8.6.7/8.6.7-cis.ufl.edu) id QAA23230; Mon, 28 Mar 1994 16:21:46 -0500 Message-Id: <199403282121.QAA23230@dragonfly.cis.ufl.edu> To: Tram Nguyen cc: majordomo-users@greatcircle.com Subject: Re: Error : Insecure Usage In-reply-to: Some random ramblings on Mon, 28 Mar 1994 15:48:31 -0500. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Mon, 28 Mar 1994 16:21:45 EST From: Stephen P Potter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused Tram Nguyen to writ e: | Hi, | | I am trying to install Majordomo on our SunOS system but keep running | into this error when sending mail to majordomo : | | /users/majordomo/wrapper: error: insecure usage | 554 ":/users/majordomo/wrapper /users/majordomo/majordomo" .. unknown mailer | error 2 | Replace the above with "/users/majordomo/wrapper majordomo" For security reasons, wrapper will not run anything with a "/" as part of the name. Steve From majordomo-users-owner Mon Mar 28 21:25:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA28517; Mon, 28 Mar 1994 21:25:42 GMT Received: from aisdb1.llnl.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA28510; Mon, 28 Mar 1994 13:25:35 -0800 Message-Id: <199403282125.NAA28510@mycroft.GreatCircle.COM> Received: by aisdb1.llnl.gov (1.37.109.8/16.2) id AA05445; Mon, 28 Mar 1994 13:25:46 -0800 From: "Leland K. Neely" Subject: Re: Error : Insecure Usage To: TRAMNG@acadvm1.uottawa.ca (Tram Nguyen) Date: Mon, 28 Mar 94 13:25:45 PST Cc: majordomo-users@greatcircle.com In-Reply-To: <199403282053.MAA28302@mycroft.GreatCircle.COM>; from "Tram Nguyen" at Mar 28, 94 3:48 pm Mailer: Elm [revision: 70.85] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > Hi, > > I am trying to install Majordomo on our SunOS system but keep running > into this error when sending mail to majordomo : > > /users/majordomo/wrapper: error: insecure usage > 554 ":/users/majordomo/wrapper /users/majordomo/majordomo" .. unknown mailer > error 2 Don't pass the full pathname for majordomo in your alias.. ie |/users/majordomo/wrapper majordomo or |/users/majordomo/wrapper resend Cheers! Lee -- _______ ______________ | | | | Leland K. Neely | ________ | | | | | U.C.L.L.N.L | |` | | | | | |_____ P.O. Box 808 L-613 | |________| | | | \______/ Livermore CA 94551 |____________| | \_______/ Email: lkn@llnl.gov ___|______|___ \________/ Voice: (510) 422-0140 |____________| \ / || From majordomo-users-owner Tue Mar 29 03:46:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA01337; Tue, 29 Mar 1994 09:48:09 GMT Received: from cc1.kuleuven.ac.be by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA01331; Tue, 29 Mar 1994 01:47:42 -0800 Message-Id: <199403290947.BAA01331@mycroft.GreatCircle.COM> Received: from CC1.KULEUVEN.AC.BE by cc1.kuleuven.ac.be (IBM VM SMTP V2R2) with BSMTP id 3268; Tue, 29 Mar 94 11:46:57 +0200 Received: from cc.kuleuven.ac.be (NJE origin SYSTHVU@BLEKUL11) by CC1.KULEUVEN.AC.BE (LMail V1.2a/1.8a) with BSMTP id 4047; Tue, 29 Mar 1994 11:46:56 +0200 Date: Tue, 29 Mar 94 11:36:53 +0200 From: Herman Van Uytven Subject: comparision between listserv and Majordomo To: lstsrv-l%searn.bitnet@cc1.kuleuven.ac.be, Majordomo-Users@GreatCircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, I have been asked to make a comparision between Revised Listserv and the Unix mailing list managers. Because there are too much of the latest, I will start only with Majordomo. The comparision is only in terms of functionality, and of course we do not want to go too much into detail. I have made a comparision starting from my own viewpoint (I guess I am not really neutral because I maintain a backbone listserv, am a list-owner and end user of several listserv mailing lists, and I have only one subscription on a Majordomo mailing list). Please mail me if you think I forgot something important, or if I missed something. Thanks in advance, -Herman- Listserv | Majordomo | ========================================================= | | | subscribe by user y | y unsubscribe by user y | y review of a list y | y on which lists am I subscribed ? n | y (on the same site) logs of list y | y search these logs y | n file server functions (get a file) y | y (only logs ?) Automatic File Distribution y | n Overview of all lists (worldwide) y | n distribute function (to reduce load) y | n remote management by list-owners y | n worldwide unsubscribe y | n digest format y | n security/privacy considerations y | n automatic removal of non-existing y (some)| n users | | From majordomo-users-owner Tue Mar 29 12:23:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA01954; Tue, 29 Mar 1994 12:23:07 GMT Received: from de5.CTD.ORNL.GOV by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id EAA01948; Tue, 29 Mar 1994 04:23:00 -0800 Received: (from de5@localhost) by de5.CTD.ORNL.GOV (8.6.7/8.6.6) id HAA13682; Tue, 29 Mar 1994 07:22:34 -0500 Date: Tue, 29 Mar 1994 07:22:34 -0500 From: Dave Sill Message-Id: <199403291222.HAA13682@de5.CTD.ORNL.GOV> To: Herman Van Uytven Cc: lstsrv-l%searn.bitnet@cc1.kuleuven.ac.be, Majordomo-Users@GreatCircle.COM Subject: comparision between listserv and Majordomo In-Reply-To: <199403290947.BAA01331@mycroft.GreatCircle.COM> References: <199403290947.BAA01331@mycroft.GreatCircle.COM> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Herman Van Uytven > Listserv | Majordomo >file server functions (get a file) y | y (only logs ?) No, Majordomo can serve any files, not just archives. >Automatic File Distribution y | n What's this? >remote management by list-owners y | n Majordomo interaction is completely by e-mail, so remote management natural. >digest format y | n Majordomo has digests too. >security/privacy considerations y | n Majordomo has security/privacy considerations too. -- Dave Sill (de5@ornl.gov) I dream of a televisionland where it will be Martin Marietta Energy Systems as hard for a network to expose us to violence Workstation Support as it is for me to tell someone they have spinach on their teeth. --Paula Poundstone URL http://www.dec.com/pub/DEC/DECinfo/html/dsill.html From majordomo-users-owner Tue Mar 29 14:49:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA02347; Tue, 29 Mar 1994 14:49:31 GMT Received: from mane.cgrg.ohio-state.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA02341; Tue, 29 Mar 1994 06:49:24 -0800 Received: from kirk.cgrg.ohio-state.edu by mane.cgrg.ohio-state.edu (5.64/900917.11) id AA17948; Tue, 29 Mar 94 09:49:49 -0500 Received: by kirk.cgrg.ohio-state.edu. (4.1/2.0) id AA07603; Tue, 29 Mar 94 09:49:47 EST Date: Tue, 29 Mar 94 09:49:47 EST From: spencer@cgrg.ohio-state.edu (Stephen N. Spencer) Message-Id: <9403291449.AA07603@kirk.cgrg.ohio-state.edu.> To: majordomo-users@greatcircle.com Subject: Bouncing messages and perturbed postmasters. Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've got a problem with 'majordomo' -- it seems to inundate a couple of sites with messages of the following format (say, a dozen or so a day): Date: Mon, 28 Mar 1994 15:16:00 -0500 From: Majordomo@cgrg.ohio-state.edu To: MAILER-DAEMON@ux4.cso.uiuc.edu Subject: Majordomo results - -- >>>> ----- Transcript of session follows ----- END OF COMMANDS I can understand the postmaster at 'uiuc' not liking these messages, but I can't understand why they're happening. I've got 'majordomo' configured just as it should be: -- contents of "majordomo.cf": $whereami = "cgrg.ohio-state.edu"; $whoami = "Majordomo@$whereami"; $whoami_owner = "Majordomo-owner@$whereami"; $homedir = "/usr/local/majordomo"; $listdir = "/usr/local/majordomo/Lists"; $log = "$homedir/Log"; $mailer = "/usr/lib/sendmail -f\$sender \$to"; -- lines from "/etc/aliases": majordomo: "|/usr/local/majordomo/wrapper majordomo" owner-majordomo: spencer majordomo-owner: spencer I've checked the 'majordomo' log file and there are only two entries in it from 'ux4.cso.uiuc.edu', one a "subscribe" and one a "help" message. Help? I'm clueless about this. Stephen N. Spencer Graphics Research Specialist ,__o spencer@cgrg.ohio-state.edu (614) 292-3416 (vox) ---- _-\_<, spencer@siggraph.org (614) 292-7776 (fax) ---- (*)/'(*) "And the things we need the most to say are the things we never mention" - E.S. From majordomo-users-owner Tue Mar 29 15:51:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA02634; Tue, 29 Mar 1994 15:51:21 GMT Received: from kksys.mn.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA02628; Tue, 29 Mar 1994 07:51:10 -0800 Received: by kksys.mn.org (Smail3.1.28.1 #15) id m0plg2S-0001wfC; Tue, 29 Mar 94 09:49 CST Received: by cdsmn (/\==/\ Smail3.1.28.1 #28.5) id ; Tue, 29 Mar 94 09:31 CST Message-Id: X-Sender: plate@cdsmn Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 29 Mar 1994 09:16:26 -0600 To: majordomo-users@Greatcircle.COM From: plate@cdsmn.mn.org (Doug Plate Sr.) Subject: Re: files visible via INDEX, but can't GET them. X-Mailer: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > >I have a list with a set of files. If I do an INDEX, I can see the files: > > From: majordomo > To: Tim.Finin > Subject: Majordomo results > Date: Sun, 27 Mar 1994 10:57:19 -0500 > > -- > > >>>> > >>>> index kqml > total 1892 > -rw-r--r-- 1 finin 268417 Oct 29 1992 KR92-KQML-slides.ps > -rw-r--r-- 1 finin 445 Aug 14 1992 README > ... > >But if I try to retrieve a file, I get: > > From: majordomo > To: Tim.Finin > Subject: Majordomo results > Date: Sun, 27 Mar 1994 11:02:07 -0500 > > -- > > >>>> get kqml README > #### No such file 'README' for list 'kqml' > >Any suggestions? > >Tim > > First let me say hello, as I just subscribed to this list. I've been using and hacking on Majordomo for several months now and it's been a great tool, not only as a list maintainer, but also as an excellent perl learning tool. Thanks Brent and company. I would say that the error message in this case would more accurately be something like : "#### Locked open of file 'README' failed" because if the file really didn't exist, you would have gotten the error message "get: invalid file 'README' for list 'kqml'". I would guess that Majordomo was for some reason unable to create a lock file, (no write permission in the directory?). It looks like you could go into shlock.pl change "$shlock_debug = 0" to "$shlock_debug = 1", then run the thing from the command line and observe. Regards, Doug Plate Sr. ////////////////////////////////////////////////////////////////////////////// Doug Plate Sr. Digital Photo Retouch Products Senior Design Technician, Dicomed Inc. ////////////////////////////////////////////////////////////////////////////// From majordomo-users-owner Tue Mar 29 08:42:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA03027; Tue, 29 Mar 1994 16:32:09 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA03021; Tue, 29 Mar 1994 08:31:59 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) id LAA12004 for majordomo-users@greatcircle.com; Tue, 29 Mar 1994 11:32:23 -0500 Date: Tue, 29 Mar 1994 11:32:23 -0500 From: David Barr Message-Id: <199403291632.LAA12004@bosnia.pop.psu.edu> Newsgroups: bit.listserv.lstsrv-l Subject: Re: comparision between listserv and Majordomo References: Organization: Penn State Population Research Institute Apparently-To: majordomo-users@greatcircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In article , David Sitman wrote: >> Listserv | Majordomo >>[...] > moderated lists y ? moderated lists y y restricted-access list y y posting-by-members-only list y y easily customizable n y administrative checking y y (i.e. check for subscription requests sent to the list) MSP (RFC 1312) support y (need server) n >There are other important considerations not mentioned here such as >CPU load, network load, security, management of bounced mail, etc. >Herman, I would suggest that you post this on the listproc list also. Eric and I have argued on this point before; but the recent sendmail releases are quite efficient and IMHO as or more efficient than SMTP+MAILER. Sendmail is good at load balancing and connection caching, and is infinately customizable in many ways including queue handling and routing. Mail delivery is not a very CPU-intensive task. Its speed depends on how many hoops and calls the system has to go through to get the message, figure out where it goes, then open up SMTP connection, etc. LISTSERV's problem is that the messsage flies around a lot of places before it can even get anwhere. Between SMTP, MAILER, LISTSERV, that's a lot of shuffles. In sendmail, everything happens in /var/spool/mqueue. (and majordomo does stuff in /tmp) As far as Majordomo's speed, Perl is quite fast - it's often compared to C in terms of speed. I'll put it up against VM's Pascal any day. Majordomo is very modular in design - it's easy to add features. Don't like the digest format? Just modify the 'digest' program. Want a new command? Just add a line to the parsing section and write the new function to do the command. No compiler needed - and you always have the source code. One thing Majordomo doesn't do that LISTSERV does is "real" automatic bounce handling. Majordomo doesn't even attempt at parsing all the myriad different formats of bounce messages. What it does do is provide a Perl program that the list owner can run to move "bad" addresses into a special "bounces" list, and then majordomo can send out mail periodically saying "you were removed from the list thus-n-such because mail was bouncing - here's how you can get back on the list and stop getting these messages". (assuming the error was a transient one) I prefer Majordomo's method of tackling the problem. (it certainly is simpler and therefore less prone to bugs or errors) Majordomo 2.0 is in the works, which will add several features and make things even easier to customize and manage. [be sure to Cc: majordomo-users@greatcircle.com] From majordomo-users-owner Tue Mar 29 09:12:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA03314; Tue, 29 Mar 1994 17:04:00 GMT Received: from deeptht.armory.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA03308; Tue, 29 Mar 1994 09:03:50 -0800 Subject: Digests To: majordomo-users@greatcircle.com Date: Tue, 29 Mar 1994 09:04:15 -0800 (PST) From: Sylvia Caras Organization: Mood Matters X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 491 Message-ID: <9403290904.aa13275@deeptht.armory.com> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I looked at the ftp site and don't know where to find the digest feature for majordomo or what it's name is. I'd like to include that for the list I'm trying to start. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ sc@armory.com v/f:408 426 5335 Sylvia Caras, 146-5 Chrystal Ter, Santa Cruz CA 95060 It is not up to you to finish the work, but neither are you free to not take it up. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From majordomo-users-owner Tue Mar 29 09:18:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA03306; Tue, 29 Mar 1994 17:03:46 GMT Received: from heifetz.msen.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA03300; Tue, 29 Mar 1994 09:03:38 -0800 Received: from hamjudo.UUCP by heifetz.msen.com with UUCP (Smail3.1.28.1 #12) id m0plgu1-000ZWLC; Tue, 29 Mar 94 11:44 EST Received: by hamjudo (4.1/SMI-4.1) id AA07605; Tue, 29 Mar 94 11:37:13 EST Date: Tue, 29 Mar 94 11:37:13 EST From: paulh@hamjudo.mi.org (Paul Haas) Message-Id: <9403291637.AA07605@hamjudo> To: majordomo-users@GreatCircle.COM, spencer@cgrg.ohio-state.edu Subject: Re: Bouncing messages and perturbed postmasters. Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Stephen N. Spencer, spencer@cgrg.ohio-state.edu wrote: > I've got a problem with 'majordomo' -- it seems to inundate a couple of sites > with messages of the following format (say, a dozen or so a day): You can keep a copy of majordomo's incoming mail for debugging these little problems. > -- lines from "/etc/aliases": > majordomo: "|/usr/local/majordomo/wrapper majordomo" Change that to: majordomo: /some/dir/majormail,"|/usr/local/majordomo/wrapper majordomo" Replace /some/dir/ with a convenient directory. You may need to make the file world writable if your mail delivery agent runs under random user ids (many older sendmails). -- Paul Haas paulh@hamjudo.mi.org From majordomo-users-owner Tue Mar 29 10:22:48 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA03589; Tue, 29 Mar 1994 18:12:47 GMT Received: from crl.dec.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA03583; Tue, 29 Mar 1994 10:12:37 -0800 Received: by crl.dec.com; id AA29938; Tue, 29 Mar 94 13:08:44 -0500 Received: by easynet.crl.dec.com; id AA23088; Tue, 29 Mar 94 13:08:11 -0500 Message-Id: <9403291808.AA23088@easynet.crl.dec.com> Received: from wrksys.enet; by crl.enet; Tue, 29 Mar 94 13:08:12 EST Date: Tue, 29 Mar 94 13:08:12 EST From: Alpha Personal Systems -- DTN 223-5747 -- MLO5-2/36A To: majordomo-users@greatcircle.com Apparently-To: majordomo-users@greatcircle.com Subject: RE: comparision between listserv and Majordomo Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk David Barr (barr@pop.psu.edu) wrote: >One thing Majordomo doesn't do that LISTSERV does is "real" automatic >bounce handling. Majordomo doesn't even attempt at parsing all >the myriad different formats of bounce messages. What it does >do is provide a Perl program that the list owner can run to >move "bad" addresses into a special "bounces" list, and then majordomo >can send out mail periodically saying "you were removed from the >list thus-n-such because mail was bouncing - here's how you can >get back on the list and stop getting these messages". (assuming >the error was a transient one) I prefer Majordomo's method >of tackling the problem. (it certainly is simpler and therefore >less prone to bugs or errors) How can this be set up? It was my understanding that using a "passive" list, that all bounces are returned to the sender, not the list owner. How can I set things up to return bounces to me? - Jim From majordomo-users-owner Tue Mar 29 19:35:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA03994; Tue, 29 Mar 1994 19:35:04 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA03986; Tue, 29 Mar 1994 11:34:55 -0800 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id OAA13512; Tue, 29 Mar 1994 14:32:32 -0500 Message-Id: <199403291932.OAA13512@bosnia.pop.psu.edu> To: Alpha Personal Systems -- DTN 223-5747 -- MLO5-2/36A Cc: majordomo-users@GreatCircle.COM Subject: Re: comparision between listserv and Majordomo In-reply-to: Your message of "Tue, 29 Mar 1994 13:08:12 EST." <9403291808.AA23088@easynet.crl.dec.com> 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 Date: Tue, 29 Mar 1994 14:32:31 -0500 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9403291808.AA23088@easynet.crl.dec.com>, Alpha Personal Systems -- DTN 223-5747 -- MLO5-2/36A writes: >David Barr (barr@pop.psu.edu) wrote: >>[Majordomo's "bounce" system] >How can this be set up? It was my understanding that using a "passive" list, >that all bounces are returned to the sender, not the list owner. How can I >set things up to return bounces to me? No, bounces must go to the list owner. It's no good sending bounces to the original sender of the message, since they're in no position to fix the problem. If you use the "resend" that comes with Majordomo to munge your headers, you need to specify "-f owner-listname" and make sure you have an alias "owner-listname" that is the owner(s) of the list. Sendmail v.8 automatically does "the right thing" (mostly) if your list is simply a :include: alias and you have an "owner-listname" alias specified in your aliases. --Dave From majordomo-users-owner Tue Mar 29 20:38:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA04173; Tue, 29 Mar 1994 20:38:52 GMT Received: from mystech.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA04167; Tue, 29 Mar 1994 12:38:45 -0800 Received: by mystech.com (4.1/SMI-4.1) id AA04254; Tue, 29 Mar 94 15:42:52 EST Date: Tue, 29 Mar 94 15:42:52 EST From: smithr@mystech.com (Roger Smith) Message-Id: <9403292042.AA04254@mystech.com> To: majordomo-users@greatcircle.com Subject: Specified Address for Get Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk When using the get command the requested documents are sent to the address that the request came from. Is there a way to specify some other address to receive the documents? Example, something like: get list doc1.txt other@address.com I have a woman on my list who gets an invalid address appended to here mail when she sends it out. Therefore, all "get" requests bounce. As user she has notified her system manager - who can not fix it :-( Roger Smith smithr@mystech.com From majordomo-users-owner Tue Mar 29 21:17:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA04300; Tue, 29 Mar 1994 21:17:12 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA04294; Tue, 29 Mar 1994 13:17:04 -0800 From: rogerk@queernet.org Received: by unpc.queernet.org (Smail3.1.28.1 #10) id m0pllCz-000MU9C; Tue, 29 Mar 94 13:20 PST Message-Id: To: smithr@mystech.com (Roger Smith) cc: majordomo-users@GreatCircle.COM Subject: Re: Specified Address for Get In-reply-to: Your message of Tue, 29 Mar 94 15:42:52 -0500. <9403292042.AA04254@mystech.com> Date: Tue, 29 Mar 94 13:20:24 PST Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I have a woman on my list who gets an invalid address appended to > here mail when she sends it out. Therefore, all "get" requests > bounce. As user she has notified her system manager - who can not > fix it :-( 1) If a system manager "can't fix it" it's time to get a new one. 2) How does she get mail? She must be subscribed using a valid address. She should put that address in a Reply-To: header. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Tue Mar 29 14:12:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA04772; Tue, 29 Mar 1994 22:00:13 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA04754; Tue, 29 Mar 1994 14:00:01 -0800 Message-Id: <199403292200.OAA04754@mycroft.GreatCircle.COM> To: Sylvia Caras cc: majordomo-users@greatcircle.com Subject: Re: Digests In-reply-to: Your message of Tue, 29 Mar 1994 09:04:15 -0800 (PST) Date: Tue, 29 Mar 1994 13:59:59 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Sylvia Caras writes: # I looked at the ftp site and don't know where to find # the digest feature for majordomo or what it's name is. Host FTP.GreatCircle.COM, file pub/list-managers/tools/digest.shar. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Tue Mar 29 23:18:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA05448; Tue, 29 Mar 1994 23:18:33 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA05442; Tue, 29 Mar 1994 15:18:20 -0800 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA04927 (5.65c/IDA-1.4.4 for ); Tue, 29 Mar 1994 18:18:35 -0500 Message-Id: <199403292318.AA04927@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: majordomo 1.90 beta 2 (teaser) Date: Tue, 29 Mar 1994 18:18:34 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The much discussed majordomo 2.0 is still vaporware, but a number of improvements (well I consider them improvements) that will be in majordomo 2.0 have been put together and christened majordomo 1.90. It is currently beta software, but it seems to have been running properly for a number of people on the majordomo-workers list. I plan on releasing 1.90 beta 2 to the general public this weekend (with some luck and no snow). It should be available from ftp.greatcircle.com a few days after. Stay tuned to the list for a full annoucement, but now onto the teaser to whet the appetitie. Now what is in 1.90 beta 2, that you can't get just yet (hey I did say this was a teaser)? No, it won't do any good to plead and beg for an early release either 8-). The most important change is that there is now a single config file that handles all configuration options for majordomo and resend. Gone are the .option files that clutter your directories, and that can't be changed by the list managers. However, these files are still supported. Also new in majordomo 1.90 is the inclusion of more archive programs and Brent's digest program. The non-beta release of 1.90 (with some additional documentation etc) should follow in about a month or so, depending on the amount of trouble with 1.90 beta 2. There are already plans for majordomo 1.91 that add features and a few minor fixes/enhancements that didn't make it into the 1.90 release before the development/feature freeze a month ago. -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Wed Mar 30 09:12:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA09836; Wed, 30 Mar 1994 17:09:26 GMT Received: from dirac.scri.fsu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA09830; Wed, 30 Mar 1994 09:09:16 -0800 Received: by dirac.scri.fsu.edu id AA97171 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Fri, 4 Feb 1994 08:11:14 -0500 Date: Fri, 4 Feb 1994 08:11:14 -0500 From: Kingsley Kerce Message-Id: <199402041311.AA97171@dirac.scri.fsu.edu> To: majordomo-users@greatcircle.com Subject: SUMMARY: keeping bounced mail from returning to subscriber/sender Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk A few days ago, I asked: > If a subscriber sends a message to a mailing list containing addresses > that cause bounces, then the subscriber/sender gets a copy of the > bounced mail. They don't care to receive the bounce. Can this be > prevented? (Without removing the offending addresses from the list -- > I'm aware of the Majordomo `bounce' utility.) This was somewhat of a RTFM question. The answer is to use `resend' to your advantage. The following is an example of a sendmail alias that I was using: sample: :include:/usr/local/mail/lists/sample Whereas this example (from the `sample.aliases' file distributed with Majordomo) fixes the problem. sample: "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Sample -f Sample-Owner -h GreatCircle.COM -s sample-outgoing" sample-outgoing: :include:/usr/local/mail/lists/sample See the `resend.README' file for more info on resend's options. Thanks to: dlc@gasco.com (Darci Chapman, Paradise Cowgirl x5930) "John P. Rouillard" for the replies! Kingsley F. Kerce (kerce@scri.fsu.edu) WWW: http://dirac.scri.fsu.edu/~kerce Supercomputer Computations Research Institute Florida State University Tallahassee, FL, USA 32306 DEEP THOUGHT: I'd rather be rich than stupid. From majordomo-users-owner Wed Mar 30 11:12:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA10515; Wed, 30 Mar 1994 19:07:05 GMT Received: from mystech.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA10509; Wed, 30 Mar 1994 11:06:56 -0800 Received: by mystech.com (4.1/SMI-4.1) id AA23009; Wed, 30 Mar 94 14:11:08 EST Date: Wed, 30 Mar 94 14:11:08 EST From: smithr@mystech.com (Roger Smith) Message-Id: <9403301911.AA23009@mystech.com> To: majordomo-users@greatcircle.com Subject: List Ownership Changing Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am running on a Sparc II, SunOS 4.1.3. When a new address is added to one of my lists the owner of the list changes. If the message comes from outside my machine the owner of the mailing list becomes daemon.daemon with priv. -rw-rw-r-- If the message comes from my account the ownership becomes: . with priv: -rw-rw-r-- When daemon is the owner I can not edit the file. When is the owner daemon can not edit it, AND majordomo can not add new addresses to the list until I manually change the priv to -rw-rw-rw- The owner of "wrapper" and all the Majordomo scripts is majordom.majordom , which never becomes the owner. I have had the SysMan change the owner to majordom.majordom several times but it always gets changed (by sendmail?). What is causing this? How can I stop it? Roger Smith smithr@mystech.com From majordomo-users-owner Wed Mar 30 11:32:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA10571; Wed, 30 Mar 1994 19:31:20 GMT Received: from aisdb1.llnl.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA10562; Wed, 30 Mar 1994 11:31:10 -0800 Message-Id: <199403301931.LAA10562@mycroft.GreatCircle.COM> Received: by aisdb1.llnl.gov (1.37.109.8/16.2) id AA20083; Wed, 30 Mar 1994 11:31:14 -0800 From: "Leland K. Neely" Subject: Re: List Ownership Changing To: smithr@mystech.com (Roger Smith) (Roger Smith) Date: Wed, 30 Mar 94 11:31:13 PST Cc: majordomo-users@greatcircle.com In-Reply-To: <9403301911.AA23009@mystech.com>; from "Roger Smith" at Mar 30, 94 2:11 pm Mailer: Elm [revision: 70.85] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Roger Smith Writes: > > > I am running on a Sparc II, SunOS 4.1.3. > When a new address is added to one of my lists the owner of the list > changes. If the message comes from outside my machine the owner of > the mailing list becomes daemon.daemon with priv. -rw-rw-r-- > > If the message comes from my account the ownership becomes: > . > with priv: -rw-rw-r-- > > When daemon is the owner I can not edit the file. When > is the owner daemon can not edit it, AND majordomo can not add > new addresses to the list until I manually change the priv to > -rw-rw-rw- > > The owner of "wrapper" and all the Majordomo scripts is > majordom.majordom , which never becomes the owner. > I have had the SysMan change the owner to majordom.majordom > several > times but it always gets changed (by sendmail?). > > What is causing this? How can I stop it? > I suspect the perms on wrapper are wrong. Try making it mod 6750 group majordomo, owner daemon: -rwsr-sr-x 1 daemon majordom 24576 Mar 16 07:40 wrapper* This should fix the privs-- Lee Neely lkn@llnl.gov From majordomo-users-owner Thu Mar 31 07:33:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA14370; Thu, 31 Mar 1994 15:26:46 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA14364; Thu, 31 Mar 1994 07:26:13 -0800 Received: by interlock.ans.net id AA12653 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Thu, 31 Mar 1994 10:26:23 -0500 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 31 Mar 1994 10:26:23 -0500 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 31 Mar 1994 10:26:23 -0500 From: Dan Simoes Message-Id: <199403311523.AA53231@foo.ans.net> Subject: digest error To: majordomo-users@greatcircle.com (majordomo-users) Date: Thu, 31 Mar 1994 10:23:27 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1904 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I installed digest yesterday, and will share some comments on that later, but right now I am having trouble with it: processing /home/majordom/digests/incoming/039 processing /home/majordom/digests/incoming/040 open(DIGEST, ">/v01.n001"): Permission denied at /home/majordom/digest line 296. 554 "| /home/majordom/wrapper digest -r -c /home/majordom/digests/quattro-digest .cf"... unknown mailer error 13 Any ideas? Here's some more info: swiss% pwd /home/majordom/digests swiss% ls -l total 7 drwxrwsr-x 2 majordom 1024 Mar 31 09:09 incoming -rw-rw-r-- 1 majordom 1140 Mar 30 12:22 quattro-digest.cf -rw-rw-r-- 1 majordom 135 Mar 30 12:20 quattro-digest.header -rw-rw-r-- 1 majordom 2 Mar 30 12:20 quattro-digest.num -rw-rw-r-- 1 majordom 587 Mar 30 12:23 quattro-digest.trailer -rw-rw-r-- 1 majordom 2 Mar 30 12:20 quattro-digest.vol The article files in incoming are all owned by daemon and mode 666. Here are the alias entries: (quattro-digestify is a member of the quattro-outgoing alias; the other quattro aliases were left out for sake of space) owner-quattro-digest: quattro-owner quattro-digest-approval: quattro-approval quattro-digest: quattro owner-quattro-digestify: quattro-owner quattro-digestify: "| /home/majordom/wrapper digest -r -c /home/majordom/digests/quattro-digest.cf" owner-quattro-digest-send: quattro-owner quattro-digest-send: "| /home/majordom/wrapper resend -p bulk -l quattro-digest -f quattro-digest-owner -h swiss.ans.net -s quattro-digest-outgoing" quattro-digest-outgoing: :include:/home/majordom/lists/quattro-digest quattro-digest-request: "| /home/majordom/wrapper request-answer quattro-digest" Thanks for any insight you can provide. | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From majordomo-users-owner Thu Mar 31 21:06:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA15713; Thu, 31 Mar 1994 21:06:43 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA15707; Thu, 31 Mar 1994 13:06:34 -0800 Received: by interlock.ans.net id AA04784 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Thu, 31 Mar 1994 16:06:29 -0500 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 31 Mar 1994 16:06:29 -0500 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 31 Mar 1994 16:06:29 -0500 From: Dan Simoes Message-Id: <199403312103.AA43992@foo.ans.net> Subject: more on digest error To: majordomo-users@greatcircle.com (majordomo-users) Date: Thu, 31 Mar 1994 16:03:35 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 633 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Well, John R. guessed it right, I had commented out the archive part of list-digest.cf so it wouldn't work. My idea was to not archive the list, but... I can always delete them later. To my surprise, the digest did not go off until I did a digest -m by hand, thanks to an old note from Brent about running digest from cron. Does digest have to be run by hand, or will it run on its own? I assume the latter, but even after fixing the archive stuff I still saw error messages... | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From majordomo-users-owner Thu Mar 31 15:05:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA16122; Thu, 31 Mar 1994 22:49:25 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA16115; Thu, 31 Mar 1994 14:49:19 -0800 Message-Id: <199403312249.OAA16115@mycroft.GreatCircle.COM> To: Dan Simoes cc: majordomo-users@greatcircle.com (majordomo-users) Subject: Re: more on digest error In-reply-to: Your message of Thu, 31 Mar 1994 16:03:35 -0500 (EST) Date: Thu, 31 Mar 1994 14:49:17 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dan Simoes writes: # Well, John R. guessed it right, I had commented out the # archive part of list-digest.cf so it wouldn't work. # My idea was to not archive the list, but... # I can always delete them later. # # To my surprise, the digest did not go off until I did a # digest -m by hand, thanks to an old note from Brent about running # digest from cron. Does digest have to be run by hand, or will it # run on its own? I assume the latter, but even after fixing the # archive stuff I still saw error messages... Digests are created when the number of bytes of waiting messages crosses the "DIGEST_SIZE" threshold, or when a "digest -m" is done (which is usually done nightly from "cron"). -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates