From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 15:34:17 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA06964; Tue, 7 Dec 93 15:34:17 GMT Received: from ac.dal.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA06957; Tue, 7 Dec 93 07:34:00 PST Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01H673CTR6AO0075P1@AC.DAL.CA>; Tue, 7 Dec 1993 11:34:34 -0400 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:majordomo-users@greatcircle.com id AA09460; Tue, 7 Dec 93 11:33:27 -0400 Date: Tue, 07 Dec 1993 11:33:26 -0400 (AST) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: About the `lists' command To: majordomo-users@greatcircle.com Message-Id: <9312071533.AA09460@biome.bio.ns.ca> Mime-Version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1226 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The command `lists' generates fairly cryptic output, like: >>>>> lists >Majordomo@GreatCircle.COM serves the following lists: > > bounces > firewalls > firewalls-digest > list-managers > list-managers-digest > majordomo-announce > majordomo-docs > majordomo-users > majordomo-workers > phonestation > phonestation-digest > >Use the 'info ' command to get more information about a specific list. It seems to me that it would not be difficult to modify the server so that if a one-line file like `majordomo-users.what' exists the contents would be appended to the filename. For example, > majordomo-users (People who operate Majordomo servers) would be more informative. Otherwise the list names are either short and confusing or long and cumbersome. I really don't want to have lists with names like `benthic-impacts-of-finfish-aquaculture' and `effects-of-acid-rain-on-salmonids'! Before I start mucking around with the code, has anyone else done this or is it seen as a reasonable enhancement? -- Bill Silvert at the Bedford Institute of Oceanography P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2 InterNet Address: silvert@biome.bio.ns.ca (the address bill@biome.bio.ns.ca is only for mailing lists) From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 16:04:21 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07167; Tue, 7 Dec 93 16:04:21 GMT Received: from beach.cis.ufl.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07159; Tue, 7 Dec 93 08:04:08 PST Received: by beach.cis.ufl.edu (5.61ufl/4.12) id AA28301; Tue, 7 Dec 93 11:04:42 -0500 From: "Stephen P. Potter" Message-Id: <9312071604.AA28301@beach.cis.ufl.edu> To: bill@biome.bio.dfo.ca (Bill Silvert) Cc: majordomo-users@greatcircle.com Subject: Re: About the `lists' command In-Reply-To: Some random ramblings on Tue, 07 Dec 93 11:33:26 -0400. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Tue, 07 Dec 93 11:04:41 EST Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused bill@biome.bio.dfo.ca (Bill Silvert) to write: | The command `lists' generates fairly cryptic output, like: | | >>>>> lists | >Majordomo@GreatCircle.COM serves the following lists: [snip] | >Use the 'info ' command to get more information about a specific list. | | It seems to me that it would not be difficult to modify the server so | that if a one-line file like `majordomo-users.what' exists the contents | would be appended to the filename. For example, | | > majordomo-users (People who operate Majordomo servers) | | would be more informative. Otherwise the list names are either short | and confusing or long and cumbersome. I really don't want to have lists | with names like `benthic-impacts-of-finfish-aquaculture' and | `effects-of-acid-rain-on-salmonids'! Before I start mucking around with | the code, has anyone else done this or is it seen as a reasonable | enhancement? | I think this would be a wonderful enhancement. I had thought of something similar, but just don't have the time currently (too busy playing with WWW and the Perl Web page. However, rather than having yet another list.file, why not have it use the first line of list.info, and specifically format that file? Or, maybe slightly better... list.info looks like this: # One line for "lists" command Whatever you want the info to be. Even if it is a number of lines. # This is a comment that won't show. With comments interspaced, starting with a # or some other character at the beginning of the line. Other's thoughts? Steve From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 16:23:24 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07259; Tue, 7 Dec 93 16:23:24 GMT Received: from spiff.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07247; Tue, 7 Dec 93 08:22:55 PST Received: by spiff.ccs.carleton.ca (4.1/SMI-4.0-mcr) id AA16368; Tue, 7 Dec 93 11:21:53 EST Date: Tue, 7 Dec 93 11:21:53 EST From: mcr@ccs.carleton.ca (Michael Richardson) Message-Id: <9312071621.AA16368@spiff.ccs.carleton.ca> To: bill@biome.bio.dfo.ca Cc: majordomo-users@GreatCircle.COM In-Reply-To: Bill Silvert's message of Tue, 07 Dec 1993 11:33:26 -0400 (AST) <9312071533.AA09460@biome.bio.ns.ca> Subject: About the `lists' command Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I moved everything into sub-directories, (I didn't introduce any new config file though) and made lists look for a ${listdir}/short-info file. Actually, there is a fifth list, but a ${listdir}/hidden exists. >>>> lists Majordomo@journal.biology.carleton.ca serves the following lists: amiga-slip Discussion of the Amiga version of NOS. TCP/IP and ham radio stuff. conservation-ecology Annoucements for the electronic journal "Conservation Ecology" public-net Discussion of Canadian alternatives in the data super-highway debate. ugrad-physics Discussion of among undergraduate physics students in Canada. Use the 'info ' command to get more information about a specific list. >>>> From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 16:33:17 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07343; Tue, 7 Dec 93 16:33:17 GMT Received: from beach.cis.ufl.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07333; Tue, 7 Dec 93 08:32:48 PST Received: by beach.cis.ufl.edu (5.61ufl/4.12) id AA29257; Tue, 7 Dec 93 11:33:26 -0500 From: "Stephen P. Potter" Message-Id: <9312071633.AA29257@beach.cis.ufl.edu> To: majordomo-users@greatcircle.com Subject: Re: About the `lists' command In-Reply-To: Some random ramblings on Tue, 07 Dec 93 12:29:00 -0400. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Tue, 07 Dec 93 11:33:26 EST Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused bill@biome.bio.dfo.ca (Bill Silvert) to write: | This is the Phycotoxins mailing list, operated by Bill Silvert of | | >list.info looks like this: | ># One line for "lists" command | >Whatever you want the info to be. What if, like my example, the first line had to be a comment, or it didn't count? Steve From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 16:43:49 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07406; Tue, 7 Dec 93 16:43:49 GMT Received: from noc4.dccs.upenn.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07398; Tue, 7 Dec 93 08:43:37 PST Received: from GRACE.WHARTON.UPENN.EDU by noc4.dccs.upenn.edu id AA03004; Tue, 7 Dec 93 11:44:09 -0500 Message-Id: <9312071644.AA03004@noc4.dccs.upenn.edu> Received: by grace.wharton.upenn.edu (1.37.109.8/16.2) id AA12324; Tue, 7 Dec 1993 11:45:16 -0500 From: Yan K. Lau Subject: How do you Approve BOUNCEd messages? To: majordomo-users@greatcircle.com Date: Tue, 7 Dec 1993 11:45:15 -0500 (EST) X-Mailer: ELM [version 2.4 PL17] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1435 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm installing and testing Majordomo, neat software esp. for Perl fans. Before making it available to our users, I wanted to test some of the features. This is probably a "been there; done it" but I can't seem to figure out how to "approve" messages for messages that arrive to the list owner because the sender is not on the list. The message comes to the sender with a subject indicating that it was BOUNCE because the sender is not on the list. I've tried putting the "Approve: passwd" line and sending it the message to the list but it just bounces to the owner with the approve line in tact and the subject being non-member sub. of the owner. I gather the same mechanism is used for moderated lists so I wanted to test it just in case there is a need for those lists at our site. I've been reading through the archives and am unsure if these items were mentioned: Has someone created a way to collect all the mail and send them out in digest form (I guess the task is difficult to implement on a per user basis)? What is used to split the archive files at greatcircle.com? By size or date would be nice. Yan. -- "I think we're both gonna make it *big*. I am very optimistic." )~ Yan K. Lau lau@grace.wharton.upenn.edu 130.91.161.2 ~/~ OPIM Department The Wharton School University of Pennsylvania /\ God/Goddess/All that is -- the source of love, light and inspiration! From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 17:08:41 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07558; Tue, 7 Dec 93 17:08:41 GMT Received: from hermes.acs.ryerson.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07551; Tue, 7 Dec 93 09:08:29 PST Received: by hermes.acs.ryerson.ca (AIX 3.2/UCB 5.64/4.03) id AA24680; Tue, 7 Dec 1993 12:08:38 -0500 Date: Tue, 7 Dec 1993 12:08:37 -0500 (EST) From: Paul Ribeiro Subject: 'resent' files in /tmp To: majordomo-users@greatcircle.com In-Reply-To: <9312071644.AA03004@noc4.dccs.upenn.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I'm running majordomo on an IBM rs/6k (aix 3.2.4) and the resend.pid.in/out files seem to hang around in /tmp forever. Any idea why this is? I'm a bit leary of deleting them before their time :-) thanks, /P From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 09:50:10 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07688; Tue, 7 Dec 93 17:23:32 GMT Received: from spiff.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07680; Tue, 7 Dec 93 09:23:24 PST Received: by spiff.ccs.carleton.ca (4.1/SMI-4.0-mcr) id AA16483; Tue, 7 Dec 93 12:24:32 EST Date: Tue, 7 Dec 93 12:24:32 EST From: mcr@ccs.carleton.ca (Michael Richardson) Message-Id: <9312071724.AA16483@spiff.ccs.carleton.ca> To: spp@cis.ufl.edu Cc: majordomo-users@GreatCircle.COM In-Reply-To: "Stephen P. Potter"'s message of Tue, 07 Dec 93 11:04:41 EST <9312071604.AA28301@beach.cis.ufl.edu> Subject: About the `lists' command Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm going to take a dissenting opinion about the use of list.info. So long as things are in sub-directories, I *like* having an individual file per ``property'' list/short-info is perfect as far as I'm concerned. From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 09:55:46 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07891; Tue, 7 Dec 93 17:40:20 GMT Received: from spiff.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07884; Tue, 7 Dec 93 09:40:12 PST Received: by spiff.ccs.carleton.ca (4.1/SMI-4.0-mcr) id AA16606; Tue, 7 Dec 93 12:41:23 EST Date: Tue, 7 Dec 93 12:41:23 EST From: mcr@ccs.carleton.ca (Michael Richardson) Message-Id: <9312071741.AA16606@spiff.ccs.carleton.ca> To: jailbait@intercon.com Cc: majordomo-users@greatcircle.com In-Reply-To: Jailbait's message of Tue, 7 Dec 93 11:52:18 -0500 <9312071652.AA01864@intercon.com> Subject: About the `lists' command Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I had a number of requests for patches. I've quite a number of modifications to majordomo along the way. I did: cvs patch -r virgin1-60 -r mcr1-60 majordomo > mcr-majordomo-patches and put the file in file://journal.biology.carleton.ca/pub/mcr/mcr-majordomo-patches I think I've removed the right headers for the patches to work, but I am doubtful. Beat on me after Saturday, and I'll try and fix things up. I made a modification to resend to do archiving, and then archive showed up. I should probably switch. The new man pages are there in the patch, as is smrsh. (Which, I decided belonged with majordomo...) -- :!mcr!: HOME: mcr@sandelman.ocunix.on.ca +1 613 788 2600 3853 Michael Richardson WORK: mcr@ccs.carleton.ca (Conservation Ecology) Here is an HTML reference to my bio. foreach $X ("E-Journal","NetBSD","Perl","Physics") { print "MCR hacks $X\n"; }; From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 19:04:33 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA08427; Tue, 7 Dec 93 19:04:33 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA08420; Tue, 7 Dec 93 11:04:24 PST Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA16039 (5.65c/IDA-1.4.4 for ); Tue, 7 Dec 1993 14:05:10 -0500 Message-Id: <199312071905.AA16039@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: About the `lists' command In-Reply-To: Your message of "Tue, 07 Dec 1993 11:33:26 -0400." <9312071533.AA09460@biome.bio.ns.ca> Date: Tue, 07 Dec 1993 14:05:10 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9312071533.AA09460@biome.bio.ns.ca>, Bill Silvert writes: > The command `lists' generates fairly cryptic output, like: > > >>>>> lists > >Majordomo@GreatCircle.COM serves the following lists: > > > > bounces > > firewalls > > firewalls-digest > > list-managers > > list-managers-digest > > majordomo-announce > > majordomo-docs > > majordomo-users > > majordomo-workers > > phonestation > > phonestation-digest > > > >Use the 'info ' command to get more information about a specific list. > > It seems to me that it would not be difficult to modify the server so > that if a one-line file like `majordomo-users.what' exists the contents > would be appended to the filename. For example, > > > majordomo-users (People who operate Majordomo servers) > > would be more informative. Otherwise the list names are either short > and confusing or long and cumbersome. I really don't want to have lists > with names like `benthic-impacts-of-finfish-aquaculture' and > `effects-of-acid-rain-on-salmonids'! Before I start mucking around with > the code, has anyone else done this or is it seen as a reasonable > enhancement? Yes, and yes. The code that will be in majordomo-2.0 to deal with configuration files has this ability. The output of majordomo@cs.umb.edu is: ===== start example >>>> lists Majordomo@cs.umb.edu serves the following lists: bblisa The Back Bay LI Systems Administration discussion list bblisa-admin The Back Bay LISA Administrators list. bblisa-announce The Back Bay LISA announcement list test This is a test, it is only a test Use the 'info ' command to get more information about a specific list. ===== end example Sadly there is not as much room on an 80 column line as I would like, but to make automated parsing of the output easier, all of the entries really should be confined to a single line. Also, the ability to hide lists is available (there are three more lists run from majordomo that don't show up, since the advertize regexp's don't match my email address) The description of the item that enables the one line descriptions is: # key name type default value subsystem # description [string] (A list description) # Used as description for mailing list when replying to the lists # command There is no quoting mechanism, and there is only room for 50 # or so characters. description = The Back Bay LISA Administrators list. This code is not yet available. Brent has a copy of the code, and I have a couple of beta sites that sadly seem quite adept at breaking it. Hopefully 2.0 will be out sometime around the middle to end of Q1 next year, but we all know about the best laid plans of mice and men (squeek). -- John John Rouillard Special Projects Volunteer University of Massachusetts at Boston (non-networked (local) mouse) Boston, MA, (617) 287-6480 rouilj@cs.umb.edu (preferred) =============================================================================== My employers don't acknowledge my existence much less my opinions. From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 19:16:47 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA08497; Tue, 7 Dec 93 19:16:47 GMT Received: from noc4.dccs.upenn.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA08490; Tue, 7 Dec 93 11:16:39 PST Received: from CCAT.SAS.UPENN.EDU by noc4.dccs.upenn.edu id AA14317; Tue, 7 Dec 93 14:17:25 -0500 Received: by ccat.sas.upenn.edu (AIX 3.2/UCB 5.64/4.03) id AA21808; Tue, 7 Dec 1993 14:17:07 -0500 From: michael@ccat.sas.upenn.edu (Michael Nenashev) Message-Id: <9312071917.AA21808@ccat.sas.upenn.edu> Subject: 'resent' files in /tmp To: majordomo-users@GreatCircle.COM Date: Tue, 7 Dec 1993 14:17:07 -0500 (EST) X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 366 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk According to Paul Ribeiro: | Hi, | I'm running majordomo on an IBM rs/6k (aix 3.2.4) and the resend.pid.in/out | files seem to hang around in /tmp forever. Any idea why this is? I'm a bit | leary of deleting them before their time :-) | thanks, | /P I've got the same problem (IBM rs/6k, 3.2.4) and I'm interested in response to that question too. Please ? Mike. From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 7 20:31:21 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA08826; Tue, 7 Dec 93 20:31:21 GMT Received: from ac.dal.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA08818; Tue, 7 Dec 93 12:30:47 PST Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01H67DI13B74006OM4@AC.DAL.CA>; Tue, 7 Dec 1993 16:25:06 -0400 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:majordomo-users@GreatCircle.COM id AA15935; Tue, 7 Dec 93 16:23:56 -0400 Date: Tue, 07 Dec 1993 16:23:55 -0400 (AST) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Re: About the `lists' command -- small patch To: majordomo-users@GreatCircle.COM Message-Id: <9312072023.AA15935@biome.bio.ns.ca> Mime-Version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3846 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I seem to have hit a responsive chord, and received several suggestions. I decided to implement one of these, which involves making sure that the first line of the *.info files contain the desired information. The patch is at the end of the message. I don't know much perl, so I'll let someone else clean it up and worry about errors, like missing *.info files. >Date: Tue, 07 Dec 1993 14:05:10 -0500 >From: "John P. Rouillard" >The code that will be in majordomo-2.0 to deal with >configuration files has this ability. The output of majordomo@cs.umb.edu >is: > >===== start example >>>>> lists >Majordomo@cs.umb.edu serves the following lists: > > bblisa The Back Bay LI Systems Administration discussion list > bblisa-admin The Back Bay LISA Administrators list. > bblisa-announce The Back Bay LISA announcement list > test This is a test, it is only a test > >The description of the item that enables the one line descriptions is: > > # key name type default value subsystem > # description [string] (A list description) > # Used as description for mailing list when replying to the lists > # command There is no quoting mechanism, and there is only room for 50 > # or so characters. > description = The Back Bay LISA Administrators list. My hack is much simpler. Here for example is my cstb.info file: ___________________________________________________________________ * Canadian Society for Theoretical Biology * This is the mailing list for the Canadian Society for Theoretical Biology, operated by Bill Silvert of the Habitat Ecology Division at the Bedford Institute of Oceanography. It is open to CSTB members and anyone else interested in any aspect of Theoretical Biology. ___________________________________________________________________ The information that comes back from the lists command is: ___________________________________________________________________ Majordomo@biome.bio.ns.ca serves the following lists: benthos * Benthic Impacts of Human Activities * bsim * BSIM Simulation Software for Ecological Modelling * cstb * Canadian Society for Theoretical Biology * dss * Decision Support Systems * ___________________________________________________________________ and so on, namely just the first line. I keep it short! Here is the patch: ___________________________________________________________________ *** vault/majordomo Tue Dec 7 14:46:13 1993 --- majordomo Tue Dec 7 16:14:15 1993 *************** *** 488,496 **** # Tell the requester what lists we serve print REPLY "$whoami serves the following lists:\n\n"; 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"; --- 488,497 ---- # Tell the requester what lists we serve print REPLY "$whoami serves the following lists:\n\n"; while(<${listdir}/*>) { + $info = `line < $_.info`; # first line of *.info file s,^.*/,,; # strip off leading path /[^-_0-9a-zA-Z]/ && next; # skip non-list files (*.info, etc.) ! print REPLY "\t", $_, "\t", $info, "\n"; } print REPLY "\nUse the 'info ' command to get more information\n"; print REPLY "about a specific list.\n"; ___________________________________________________________________ which just involves setting $info to the first line of the *.info file and then printing it. From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 00:22:19 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09795; Wed, 8 Dec 93 00:22:19 GMT Received: from welch.ncd.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09788; Tue, 7 Dec 93 16:22:12 PST Received: from bryant.ncd.com (bryant.ncd.com [192.43.159.209]) by welch.ncd.com (8.6.4/8.6.4) with ESMTP id QAA22127 for ; Tue, 7 Dec 1993 16:22:27 -0800 Received: from localhost (mfrost@localhost) by bryant.ncd.com (8.6.4/8.6.4) id QAA03053 for majordomo-users@greatcircle.com; Tue, 7 Dec 1993 16:22:51 -0800 From: mfrost@ncd.com (Mark Frost) Message-Id: <9312071622.ZM3050@bryant.ncd.com> Date: Tue, 7 Dec 1993 16:22:49 -0800 X-Mailer: Z-Mail (2.1.5 09aug93) To: majordomo-users@greatcircle.com Subject: restricting majordomo's replies Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello. I've just set up majordomo here at NCD and am in the process of testing it. One of the things that concerns me is that I need to keep access to the majordomo server limited to those inside of the company (i.e. the domain needs to have ncd.com at the end). I don't want to service any requests ("lists", "who", etc.) for any addresses outside of our domain. Is there someway to do this using the current version (1.62 is what I picked up)? Thanks -mark From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 04:48:04 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10533; Wed, 8 Dec 93 04:48:04 GMT Received: from osiris.ac.hmc.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10526; Tue, 7 Dec 93 20:47:52 PST Received: from localhost (jared@localhost) by osiris.ac.hmc.edu (8.6.4/8.6.4) id UAA06503; Tue, 7 Dec 1993 20:48:39 -0800 Date: Tue, 7 Dec 1993 20:48:39 -0800 Message-Id: <199312080448.UAA06503@osiris.ac.hmc.edu> From: Jared_Rhine@hmc.edu To: majordomo-users@GreatCircle.COM Cc: listkeeper-l@hmc.edu Subject: Proposal for recursive-capable lists References: <199312071905.AA16039@cs.umb.edu> <9312071533.AA09460@biome.bio.ns.ca> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I would like to propose the addition of a new feature. It may be the case that the functionality is not of general interest, but I believe that Majordomo, as the emerging Internet standard for mailing lists, should include the functionality. I would be fully willing to add the code myself to majordomo-2.0 (whatever shape the current source tree is in) and fully test it. Note that I believe the new feature can be implemented solely with modifications to 'resend.pl'. In short, our site would like very much to be able handle recursively defined mailing lists. We have a very large collection of mailing lists, many of include other mailing lists as subscriber members, in order to implement a heirarchical structure: cs-dept-l cs-fac-l Nancy_Mandala@hmc.edu Mark_Schaal@hmc.edu cs-majors-l cs-majors-94-l cs-majors-95-l cs-majors-96-l cs-majors-97-l or ac-employees-l consultants-l ac-staff-l We have situtations, for example in which a single person is, quite legitimately subscribed to both 'consultants-l' and 'ac-staff-l'. Such a situation comes up any time there is a mailing list with some subset of people who are supervisors of the group of people on another list. The problem with this setup is any mail to 'ac-employees-l' will cause two messages to be sent to such people. I would like to be able to add a switch to the resend script which would cause resend to: check each line of the list it is parsing if it does not match a known list, add it to an internal list of addresses (probably via a $list{$_}++ construct) if it does match a known list, expand (recursively) that list, in turn adding each of those names to the same list when done recursing, do the perl equivalent of a 'uniq' (if the $list{$_}++ construct is used, this is automatically done; it can be put into a list form via a @list = keys %list.) Great, now I have a unique list of names; to ship them off to the mailer is a little tricky. Resend will probably need to create a file on the fly containing the 'uniq'ized set of names for the mailer to use. The name of the file to create could also be passed as an argument to create. For example, if resend was currently being invoked by: ac-employees-l: "|/usr/local/etc/majordomo/wrapper resend -l ac-employees-l -f AC-Employees-l-Manager -h hmc.edu ac-employees-l-outgoing" ac-employees-l-outgoing: :include:/usr/local/lib/mail-lists/ac-employees-l, ac-employees-l-archive it could now be invoked by ac-employees-l: "|/usr/local/etc/majordomo/wrapper resend -l ac-employees-l -f AC-Employees-l-Manager -h hmc.edu --recurse /tmp/ac-employees-l.recurse ac-employees-l-outgoing" ac-employees-l-outgoing: :include:/tmp/ac-employees-l.recurse, ac-employees-l-archive I may have not stated myself well, and this may seem like a horribly complicated hack with no use to yourself personally, I urge you to consider whether it might not be very desirable in some configurations. In some sense, majordomo created this problem for us, since it has been so useful that we've created massive numbers of mailing lists! -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Jared Rhine | Remember, only users lose drugs. Jared_Rhine@hmc.edu |-- -- -- -- -- -- -- -- -- -- -- -- wibstr - Harvey Mudd College | To live is to war with trolls. http://www.hmc.edu/www/people/jared.html |-- -- -- -- -- -- -- -- -- -- -- -- From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 05:06:14 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10570; Wed, 8 Dec 93 05:06:14 GMT Received: from nda.nda.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10563; Tue, 7 Dec 93 21:06:05 PST Received: from localhost (kovar@localhost) by nda.nda.com (8.6.4/8.6.4) id AAA17680; Wed, 8 Dec 1993 00:06:49 -0500 From: David Kovar Message-Id: <199312080506.AAA17680@nda.nda.com> Subject: Re: 'resent' files in /tmp To: michael@ccat.sas.upenn.edu (Michael Nenashev) Date: Wed, 8 Dec 1993 00:06:48 -0500 (EST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <9312071917.AA21808@ccat.sas.upenn.edu> from "Michael Nenashev" at Dec 7, 93 02:17:07 pm X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 581 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > According to Paul Ribeiro: > | Hi, > | I'm running majordomo on an IBM rs/6k (aix 3.2.4) and the resend.pid.in/out > | files seem to hang around in /tmp forever. Any idea why this is? I'm a bit > | leary of deleting them before their time :-) > | thanks, > | /P > > I've got the same problem (IBM rs/6k, 3.2.4) and I'm interested in > response to that question too. Please ? Upgrading to the latest version of resend fixed this problem as well. The new version of resend was released to help close the sendmail hole announced last month. Check on ftp.greatcircle.com -David From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 06:12:43 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10817; Wed, 8 Dec 93 06:12:43 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10810; Tue, 7 Dec 93 22:12:34 PST Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA27334; Tue, 7 Dec 93 22:04:38 PST Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0p7NBD-0002ckC; Wed, 8 Dec 93 03:35 PST Message-Id: From: Alan Millar Subject: Re: About the `lists' command To: spp@cis.ufl.edu Date: Wed, 8 Dec 1993 03:35:37 -0800 (PST) Cc: bill@biome.bio.dfo.ca, majordomo-users@GreatCircle.COM In-Reply-To: <9312071604.AA28301@beach.cis.ufl.edu> from "Stephen P. Potter" at Dec 7, 93 11:04:41 am Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1241 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Stephen P. Potter spake of these matters: > > Strange sunspot activity caused bill@biome.bio.dfo.ca (Bill Silvert) to write: > | It seems to me that it would not be difficult to modify the server so > | that if a one-line file like `majordomo-users.what' exists the contents > | would be appended to the filename. For example, > | > | > majordomo-users (People who operate Majordomo servers) > However, rather than having yet another list.file, why not have it use the > first line of list.info, and specifically format that file? Or, maybe > Other's thoughts? The one-line "lists" comment is part of the much-discussed "config file" changes coming in the next major release of Majordomo. You may want to review the majordomo-users archives, but the idea is there will be a single configuration file for each list, instead of a proliferation of list.this and list.that and list.the-other files. Due out Real Soon Now.... :-) - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ I am the great Oz! Pay no attention to that man behind the curtain! From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 06:35:38 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10899; Wed, 8 Dec 93 06:35:38 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10891; Tue, 7 Dec 93 22:35:32 PST Message-Id: <9312080635.AA10891@mycroft.GreatCircle.COM> To: majordomo-users@GreatCircle.COM Subject: Re: 'resent' files in /tmp In-Reply-To: Your message of Wed, 8 Dec 1993 00:06:48 -0500 (EST) Date: Tue, 07 Dec 1993 22:35:30 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk [ No, Brent's not dead, he's just buried... :-] David Kovar writes: # > According to Paul Ribeiro: # > | Hi, # > | I'm running majordomo on an IBM rs/6k (aix 3.2.4) and the resend.pid.in/o # ut # > | files seem to hang around in /tmp forever. Any idea why this is? I'm a bi # t # > | leary of deleting them before their time :-) # > | thanks, # > | /P # > # > I've got the same problem (IBM rs/6k, 3.2.4) and I'm interested in # > response to that question too. Please ? # # Upgrading to the latest version of resend fixed this problem as well. # The new version of resend was released to help close the sendmail hole # announced last month. Check on ftp.greatcircle.com Yeah, that was a bug. I'd commented out the code that deletes the temp files while I was doing some debugging, then I forgot to uncomment it before I released. Like David says, the current version of "resend" (available for anonymous FTP from FTP.GreatCircle.COM, file pub/majordomo/resend.1.19.shar, and to be included in the next release of Majordomo) fixes this problem and adds a new feature to improve the security situation with Sendmail. -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@GreatCircle.COM Wed Dec 8 07:01:58 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11355; Wed, 8 Dec 93 07:01:58 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11334; Tue, 7 Dec 93 23:01:42 PST Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA28644; Tue, 7 Dec 93 22:53:14 PST Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0p7Oqy-0002clC; Wed, 8 Dec 93 05:22 PST Message-Id: From: Alan Millar Subject: Re: Proposal for recursive-capable lists To: Jared_Rhine@hmc.edu Date: Wed, 8 Dec 1993 05:22:50 -0800 (PST) Cc: majordomo-users@GreatCircle.COM, listkeeper-l@hmc.edu In-Reply-To: <199312080448.UAA06503@osiris.ac.hmc.edu> from "Jared_Rhine@hmc.edu" at Dec 7, 93 08:48:39 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: 1397 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Jared_Rhine@hmc.edu spake of these matters: > I would like to propose the addition of a new feature. It may be the case > In short, our site would like very much to be able handle recursively > defined mailing lists. We have a very large collection of mailing lists, > many of include other mailing lists as subscriber members, in order to > implement a heirarchical structure: This has been discussed recently on either majordomo-users or list-managers (I forget which). As you mention, this is a message distribution problem and not a subscription problem. The gist of what I've heard recently is that this elimination of duplicates should already be handled by sendmail. Are you running sendmail? If so, what platform/version? Ironically, I've recently heard Majordomo recommended over ListProc for this very reason. ListProc does its own message distribution and list expansion, and does not eliminate duplicates. Majordomo leaves it to the system mailer, typically sendmail, which in most incarnations does eliminate duplicates. It may be an easier job to look into upgrading/replacing your mailer than changing resend. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ MOSTLY harmless??!! From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 08:00:40 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11835; Wed, 8 Dec 93 08:00:40 GMT Received: from osiris.ac.hmc.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11828; Wed, 8 Dec 93 00:00:27 PST Received: from localhost (jared@localhost) by osiris.ac.hmc.edu (8.6.4/8.6.4) id AAA18163; Wed, 8 Dec 1993 00:01:09 -0800 Date: Wed, 8 Dec 1993 00:01:09 -0800 Message-Id: <199312080801.AAA18163@osiris.ac.hmc.edu> From: Jared_Rhine@hmc.edu To: AMillar@bolis.sf-bay.org Cc: listkeeper-l@hmc.edu, majordomo-users@GreatCircle.COM Subject: Re: Proposal for recursive-capable lists References: <199312080448.UAA06503@osiris.ac.hmc.edu> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Jared> I may have not stated myself well... Alas, I was correct. Jared> In short, our site would like very much to be able handle recursively Jared> defined mailing lists. Alan> The gist of what I've heard recently is that this elimination of Alan> duplicates should already be handled by sendmail. Are you running Alan> sendmail? If so, what platform/version? Sendmail 8, Ultrix 4.3, but that's irrelevant. Here is the general sequence for a sending to my discussed 'ac-employees-l': ac-employees-l consultants-l ac-staff-l When Sendmail receives mail for ac-employees-l, it looks up in one of it's numerous aliases files and finds: ac-employees-l: "|/usr/local/etc/listkeeper/wrapper resend -l ac-employees-l -f AC-Employees-l-Manager -h hmc.edu ac-employees-l-outgoing" ac-employees-l-outgoing: :include:/usr/local/lib/mail-lists/ac-employees-l,ac-employees-l-archive ac-employees-l-archive: /usr/local/lib/mail-archive/ac-employees-l ac-employees-l-manager: Josh_Smith The ac-employees-l gets expanded to the resend script, which eventually gets down to: $sendmail_cmd = "/usr/lib/sendmail $opt_m -f$sendmail_sender " . join(" ", @ARGV); where '@ARGV' is now the string 'ac-employees-l-outgoing' as passed straight to 'resend'. So sendmail (as the mail agent) expands 'ac-employees-l-outgoing', and finds it expands to a file: '/usr/local/lib/mail-lists/ac-employees-l', which is: consultants-l ac-staff-l At this point, doing cool sendmail (all hail!) tricks, it looks these addresses up in the aliases files in case they contain yet another level of indirection, which indeed they do: consultants-l: ac-consultants-l Hmmm, it looks that up again and finds: ac-consultants-l: "|/usr/local/etc/listkeeper/wrapper resend -l ac-consultants-l -f AC-Consultants-L-Manager -h HMC.Edu ac-consultants-l-outgoing" ac-consultants-l-outgoing: :include:/usr/local/lib/mail-lists/ac-consultants-l,ac-consultants-l-archive ac-consultants-l-archive: /usr/local/lib/mail-archive/ac-consultants-l ac-consultants-l-manager: Josh_Smith Ah-ha! At this point, it has found a final destination. It pipes the mail to resend, and washes its hand of the mail -- it is done with that deliver. There's the first piece of mail delivered once it expands '/usr/local/lib/mail-lists/ac-consultants-l', which contains our suffering double-recipient. However, the _same_ cycle happens with 'ac-staff-l' -- it eventually gets piped off to a script, at which point Sendmail stops doing indirection lookups. In any case, that is my view of the problem, and a correct one, if I'm not mistaken. I would absolutely _love_ it if someone could tell me how to configure sendmail to work around this, but I'm not hopeful. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Jared Rhine | Remember, only users lose drugs. Jared_Rhine@hmc.edu |-- -- -- -- -- -- -- -- -- -- -- -- wibstr - Harvey Mudd College | To live is to war with trolls. http://www.hmc.edu/www/people/jared.html |-- -- -- -- -- -- -- -- -- -- -- -- From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 03:50:46 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12301; Wed, 8 Dec 93 09:44:25 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12294; Wed, 8 Dec 93 01:44:14 PST Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA00879; Wed, 8 Dec 93 01:43:54 PST Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0p7RIf-0002coC; Wed, 8 Dec 93 07:59 PST Message-Id: From: Alan Millar Subject: Re: Proposal for recursive-capable lists To: Jared_Rhine@hmc.edu Date: Wed, 8 Dec 1993 07:59:33 -0800 (PST) Cc: listkeeper-l@hmc.edu, majordomo-users@GreatCircle.COM In-Reply-To: <199312080801.AAA18163@osiris.ac.hmc.edu> from "Jared_Rhine@hmc.edu" at Dec 8, 93 00:01:09 am Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2993 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Jared says: > Jared> In short, our site would like very much to be able handle recursively > Jared> defined mailing lists. > ac-employees-l > consultants-l > ac-staff-l > At this point, doing cool sendmail (all hail!) tricks, it looks these > addresses up in the aliases files in case they contain yet another level of > indirection, which indeed they do: > > consultants-l: ac-consultants-l > > Hmmm, it looks that up again and finds: > > ac-consultants-l: "|/usr/local/etc/listkeeper/wrapper resend > -l ac-consultants-l [...] ac-consultants-l-outgoing" > ac-consultants-l-outgoing: :include:/usr/local/lib/mail-lists/ > ac-consultants-l,ac-consultants-l-archive > Ah-ha! At this point, it has found a final destination. It pipes the mail > to resend, and washes its hand of the mail -- it is done with that deliver. This is the problem. Sendmail is handing it off to resend a second time, breaking its ability to eliminate duplicates. > There's the first piece of mail delivered once it expands > '/usr/local/lib/mail-lists/ac-consultants-l', which contains our suffering > double-recipient. However, the _same_ cycle happens with 'ac-staff-l' -- it > eventually gets piped off to a script, at which point Sendmail stops doing > indirection lookups. Indeed here is the problem (and the solution). "Resend" sits between the sub-list address and the sub-list-outgoing addresses, making a gap across which sendmail cannot do a single expansion and elimination of duplicates. The solution is to change the list configuration so that sendmail *doesn't* call resend for each sub-list, and so is able to do a single expansion of the hierarchy. To do that, you must put the "-outgoing" addresses for the sublists into the main list. ac-employees-l consultants-l-outgoing ac-staff-l-outgoing You can put this in a file, or do it explicitly in the aliases file: ac-employees-l: "|/usr/local/etc/listkeeper/wrapper resend -l ac-employees-l [...] ac-employees-l-outgoing" ac-employees-l-outgoing: consultants-l-outgoing, ac-staff-l-outgoing,ac-employees-l-archive Given that, resend is only called once at the top (ac-employees) level, and sendmail subsequently expands the ac-employees-l-outgoing list along with *all* final destination addresses in consultants-outgoing and staff-outgoing at the same time. Now sendmail can see the duplicates and eliminate them. > In any case, that is my view of the problem, and a correct one, if I'm not > mistaken. Yes. Given the fact that resend was called again for each sub-list, you are exactly right. Eliminating it should fix it. - 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@GreatCircle.COM Wed Dec 8 14:51:43 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA13244; Wed, 8 Dec 93 14:51:43 GMT Received: from spiff.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA13237; Wed, 8 Dec 93 06:51:30 PST Received: by spiff.ccs.carleton.ca (4.1/SMI-4.0-mcr) id AA18331; Wed, 8 Dec 93 09:52:37 EST Date: Wed, 8 Dec 93 09:52:37 EST From: mcr@ccs.carleton.ca (Michael Richardson) Message-Id: <9312081452.AA18331@spiff.ccs.carleton.ca> To: AMillar@bolis.sf-bay.org Cc: Jared_Rhine@hmc.edu, majordomo-users@GreatCircle.COM, listkeeper-l@hmc.edu In-Reply-To: Alan Millar's message of Wed, 8 Dec 1993 05:22:50 -0800 (PST) Subject: Proposal for recursive-capable lists Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The problem may be that the *submission* address has been placed on the list one level up. In this case, sendmail never gets to see the expanded alias until after another run through resend. Put the -outgoing address on the upper lists and then sendmail ought to get a chance to eliminate duplicates. From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 19:42:55 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA14267; Wed, 8 Dec 93 19:42:55 GMT Received: from osiris.ac.hmc.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA14260; Wed, 8 Dec 93 11:42:47 PST Received: from localhost (jared@localhost) by osiris.ac.hmc.edu (8.6.4/8.6.4) id LAA03032; Wed, 8 Dec 1993 11:43:34 -0800 Date: Wed, 8 Dec 1993 11:43:34 -0800 Message-Id: <199312081943.LAA03032@osiris.ac.hmc.edu> From: Jared_Rhine@hmc.edu To: majordomo-users@greatcircle.com Subject: Recursive lists Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I wish to thank Alan Millar and Michael Richardson for their assistance in this matter. Perhaps some mention of the matter should be made in the documentation? I will volunteer to do this. To facilitate, could anyone who feels inclined send me a brief snippet of their aliases file for representative lists. I imagine there are a number of ways to configure those files, and I'd be willing to sort through the duplicate configurations. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Jared Rhine | Remember, only users lose drugs. Jared_Rhine@hmc.edu |-- -- -- -- -- -- -- -- -- -- -- -- wibstr - Harvey Mudd College | To live is to war with trolls. http://www.hmc.edu/www/people/jared.html |-- -- -- -- -- -- -- -- -- -- -- -- From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 21:02:08 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA14492; Wed, 8 Dec 93 21:02:08 GMT Received: from dino.conicit.ve by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA14485; Wed, 8 Dec 93 13:01:40 PST Received: by dino.conicit.ve (4.1/SMI-4.1/RP-1.2) id AA17287; Wed, 8 Dec 1993 17:00:16 -0400 (AST) From: lem@conicit.ve (Luis Moreno CONICIT) Message-Id: <9312082100.AA17287@dino.conicit.ve> Subject: Avoid send mail to a list ... To: majordomo-users@greatcircle.com Date: Wed, 8 Dec 1993 17:00:16 -0400 (AST) X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 907 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi users of Majordomo ... I have a number of lists created, and there are users than not are subscribed any of this list, but send mail to list. I'd like know if I can avoid than users than not are subscribed in a list, can send mail to list. I have installed the Majordomo release 1.0. Is there other release a new release..? thank a lot of for your help ..., any suggestions would be of help. I'm sorry for may english ... Regards, Luis E. Moreno ---------------------------------------------------------------- Consejo Nacional de Investigaciones Cientificas y Tecnologicas. CONICIT @@@ Internet: lem@conicit.ve @@@ Telf: 239.04.33 Ext: 1392 @@@ Directo: 239.83.44 Fax: 239.83.44 ---------------------------------------------------------------- From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 8 23:03:43 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA14831; Wed, 8 Dec 93 23:03:43 GMT Received: from merlot.arc.nasa.gov by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA14824; Wed, 8 Dec 93 15:03:33 PST Received: Wed, 8 Dec 93 15:05:10 PST from localhost.arc.nasa.gov by merlot.arc.nasa.gov (4.1/1.2) Message-Id: <9312082305.AA18132@merlot.arc.nasa.gov> To: majordomo-users@greatcircle.com Subject: Problems with Approved: .. Date: Wed, 08 Dec 1993 15:05:10 -0800 From: Alex Deacon Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, A while back someone posted a problem they were haveing concerning the way Majordomo was posting approved messages to a moderated list. I seem to be having the same problems. I did not see any response to this question in the archives, so I was wondering if anyone else was having these problems? Here is an example of what I am talking about. The owner of this list placed the Approve: command as the first line of the message (not in the header) Here is the message that was posted to the list. There is no longer a Subject: line and the Sender: and Precedence: lines are appearing in the body of the message. Any Ideas? Thanks in advance... Alex Deacon >From livefrom-antarctica-owner@quest.arc.nasa.gov Sat Dec 4 01:42:47 1993 Return-Path: Received: from quest.arc.nasa.gov by nsipo.arc.nasa.gov (4.1/1.5) id AA28670; Sat, 4 Dec 93 01:42:47 PST From: Received: Sat, 4 Dec 93 01:42:50 PST by quest.arc.nasa.gov (4.1/1.2) Date: Sat, 4 Dec 93 01:42:50 PST Message-Id: <9312040942.AA05490@quest.arc.nasa.gov> Apparently-To: livefrom-antarctica-outgoing Status: RO 1. What has been the hottest temperature while you have been there? Sender: livefrom-antarctica-owner@quest.arc.nasa.gov Precedence: bulk Answer: During October it was very cool and the temperature never was above the freezing point. However, now that we are approaching the height of the summer(~Dec. 21st) the sun is much higher and we receive much more sunlight. Now, when the days are sunny, and the wind is calm, the temperature reaches about the freezing point. As a matter of fact, the ground, being so dark absorbs the sunlight and warms enough to cause the ice to melt forming small streams. The next few weeks are probably the most pleasant days to be here in the antarctic. But of course up on the polar plateau which is much higher and covered in ice completely its much colder ane and right now the thermometers are reading about -30C! - ------- End of Forwarded Message ------- End of Forwarded Message From Majordomo-Users-Owner@GreatCircle.COM Thu Dec 9 15:06:08 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA17570; Thu, 9 Dec 93 15:06:08 GMT Received: from mgc.mentorg.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA17563; Thu, 9 Dec 93 07:05:55 PST Received: from warren.mentorg.com by mgc.mentorg.com with SMTP (16.6/15.5+MGC-TD 2.20) id AA20406; Thu, 9 Dec 93 07:06:43 -0800 Received: from worf (worf.warren.mentorg.com) by Warren.MENTORG.COM with SMTP id AA26616 (5.65c/IDA-1.4.4 for ); Thu, 9 Dec 1993 10:06:40 -0500 Received: by worf (5.0/SMI-4.0) id AA19869; Thu, 9 Dec 1993 10:06:41 +0500 From: tom_limoncelli@Warren.MENTORG.COM Message-Id: <9312091506.AA19869@worf.Warren.MENTORG.COM> Subject: approve change To: majordomo-users@greatcircle.com Date: Thu, 9 Dec 1993 10:06:40 -0500 (EST) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1248 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk approve expects full email addresses in the header. i.e. "Reply-To: Majordomo@warren.mentorg.com" rather than "Reply-To: Majordomo". However, my mail is delivered on "warren.mentorg.com" so the hostname isn't included. (it's actually stripped out by IDA sendmail). i.e. I get headers that look like these: To: ixo-approval From: Majordomo Subject: APPROVE ixo Reply-To: Majordomo To fix this, I made a simple change: ------------------------------------------------------ begin diff -cw -r1.1 bin/approve *** 1.1 1993/12/08 23:10:29 --- bin/approve 1993/12/09 14:44:28 *************** *** 103,108 **** --- 103,109 ---- s/^\S*:\s+//; $reply_to = $_; $reply_to =~ tr/A-Z/a-z/; + $reply_to .= "@warren.mentorg.com" unless $reply_to =~ /@/; next; } if (/^subject:/i) { ------------------------------------------------------ end Could a fix similar to this be included in the next version? Thanks, Tom -- Tom Limoncelli -- tal@warren.mentorg.com (work) -- tal@plts.org (play) "Psst! Hey, Anthony! Y'know what I | Disclaimer: I do not like about existing?" "Uh... uh... what?" | speak for Mentor Graphics. "Possessing a physical extension." -TSA | From Majordomo-Users-Owner@GreatCircle.COM Thu Dec 9 08:50:15 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA17852; Thu, 9 Dec 93 16:36:21 GMT Received: from lobster.wellfleet.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA17504; Thu, 9 Dec 93 06:43:41 PST Received: from pobox.wellfleet ([192.32.75.5]) by lobster.wellfleet.com (4.1/SMI-4.1) id AA10278; Thu, 9 Dec 93 09:32:11 EST Received: from firstclass.wellfleet.com by pobox.wellfleet (4.1/SMI-4.1) id AA07571; Thu, 9 Dec 93 09:40:24 EST Received: from FirstClass (2840432400) by firstclass.wellfleet.com (PostalUnion/SMTP 1.1.5) id AA1000713.4413; Thu, 09 Dec 1993 09:41:41 EST Message-Id: <1993Dec09.093558.4413@firstclass.wellfleet.com> To: Majordomo-Users@GreatCircle.com From: Peter_Giliberti@firstclass.wellfleet.com Organization: Wellfleet Communication Date: Thu, 09 Dec 1993 09:35:58 EST Subject: Approve Commands Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Is there a time limit a list owner must adhere to responding to subscribe commands ....IE..can this be done on a weekly basis?????? Peter Giliberti Sr.Network Engineer Wellfleet Communications From Majordomo-Users-Owner@GreatCircle.COM Sat Dec 11 23:00:10 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA28864; Sat, 11 Dec 93 23:00:10 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA28842; Sat, 11 Dec 93 15:00:01 PST Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA24768; Sat, 11 Dec 93 14:51:02 PST Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0p8j9e-0002asC; Sat, 11 Dec 93 21:15 PST Message-Id: From: Alan Millar Subject: How do you deal with postings to "owner-listname"? To: list-managers@greatcircle.com Date: Sat, 11 Dec 1993 21:15:36 -0800 (PST) Cc: majordomo-users@greatcircle.com 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: 1474 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi- I'm running several mailing lists with Majordomo. I'm using the "resend" script which modifies each message so that the envelope says the message is from "owner-listname" instead of the original sender. The "owner-" addresses are aliased to me, so I receive error notices and bounces. That way the list members and the sender don't have to see them. However, on a regular basis people will send a message for the list to the owner- address instead of the list address. This is probably because they're using a lame MUA, but in actuality it doesn't really matter why; it's just annoying. If I feel like doing a little typing, sometimes I'll drop the poster a note telling them what they did. Usually I just use elm's "bounce" command to send it along to the list. How do other list owners deal with this? Do you reply to them, forward them, or just drop them? What I'd really like is a little script that would read the headers to see which "owner-...." address they sent it to, and then plug the correct address into a reply telling them what they did wrong and how to fix it. Has anyone created one of these yet? Any better suggestions? Thanks! - 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@GreatCircle.COM Sun Dec 12 06:11:20 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA29747; Sun, 12 Dec 93 06:11:20 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA29740; Sat, 11 Dec 93 22:11:13 PST Received: from cs.umb.edu by cs.umb.edu with SMTP id AA25445 (5.65c/IDA-1.4.4 for ); Sun, 12 Dec 1993 01:12:05 -0500 Message-Id: <199312120612.AA25445@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: How do you deal with postings to "owner-listname"? In-Reply-To: Your message of "Sat, 11 Dec 1993 21:15:36 PST." Date: Sun, 12 Dec 1993 01:12:04 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Alan Millar writes: > script which modifies each message so that the envelope says the > message is from "owner-listname" instead of the original sender. > [...] > The "owner-" addresses are aliased to me, so I receive error notices > and bounces. [...] > However, on a regular basis people will send a message for the list > to the owner- address instead of the list address. [...] > it's just annoying. > [...] > command to send it along to the list. > > How do other list owners deal with this? Do you reply to them, > forward them, or just drop them? I use MH, so I have a template that I use to reply to the user. The template includes the original message, and have them try again. I used to just forward their message, and send them a message saying I forwarded their message, but I was getting a lot of traffic from the same few lusers. Once I forced them to learn how to send the email message to the right place, the repeat rate dropped to nothing. -- 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@GreatCircle.COM Tue Dec 14 17:05:29 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09246; Tue, 14 Dec 93 17:05:29 GMT Received: from srlns1.srl.ford.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09232; Tue, 14 Dec 93 09:02:03 PST Received: from strange.pms.ford.com by srlns1.srl.ford.com (4.1/Ford 2.0) via id AA22766; Tue, 14 Dec 93 12:02:27 EST Received: by strange.pms.ford.com (Strange Smail3.1.28.1) id m0p9d6f-000q3yC; Tue, 14 Dec 93 12:00 EST Message-Id: From: ec@strange.pms.ford.com (Iain O'Cain) Subject: Restrict lists by domain? To: majordomo-users@greatcircle.com Date: Tue, 14 Dec 1993 12:00:17 -0500 (EST) Content-Type: text Organization: Ford Motor Company -- standard disclaimers apply Content-Length: 774 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk It seems to me I've seen messages on the subject of majordomo patches to allow restriction of lists by domain. I'm hoping there's something out there to do what I need right now. I've got a few Ford-only mailing lists now, and I'd like to create a new one that's open to the Internet at large. Currently, there's nothing sensitive in my internal lists, but it would not go over well to just open them to the world. I'd like to make some of them invisible to people outside certain domains. Should I be looking at the hidden lists patches and plan to modify them for the purpose I'm talking about? -- Iain O'Cain, TS&UR (WSD (P&MS (CPD (NAO (Ford Motor Company))))); +1(313)594-1769, FAX 390-4565, ec@strange.pms.ford.com >>> I do not speak for Ford Motor Company <<< From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 14 22:10:02 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10210; Tue, 14 Dec 93 22:10:02 GMT Received: from virginia.edu (uvaarpa.Virginia.EDU) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10201; Tue, 14 Dec 93 14:09:53 PST Received: from holmes.acc.virginia.edu by uvaarpa.virginia.edu id aa07423; 14 Dec 93 17:10 EST Received: by holmes.acc.Virginia.EDU (5.67a8/1.34) id AA156105; Tue, 14 Dec 1993 17:10:43 -0500 From: William Pemberton Message-Id: <199312142210.AA156105@holmes.acc.Virginia.EDU> Subject: Lots of lists To: majordomo-users@greatcircle.com Date: Tue, 14 Dec 1993 17:10:43 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 594 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Does anyone have any experience using Majordomo to manage a lot of lists? Currently, we have around 400 lists that are local to UVa (they are all run off of mmdf). We are looking at moving to something like Majordomo, but are concerned about things like the CPU load (especially since perl seems to be a CPU hog). Anybody have any insight on if this is going to be too much/no problem/maybe a hassle? -- Bill Pemberton wfp5p@virginia.edu ITC/Unix Systems flash@virginia.edu University of Virginia uunet!virginia!wfp5p From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 15 03:15:29 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11072; Wed, 15 Dec 93 03:15:29 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11065; Tue, 14 Dec 93 19:15:19 PST Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA21754; Tue, 14 Dec 93 19:06:49 PST Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0p9rAm-0002ZNC; Wed, 15 Dec 93 00:01 PST Message-Id: From: Alan Millar Subject: Re: Lots of lists To: wfp5p@holmes.acc.virginia.edu (William Pemberton) Date: Wed, 15 Dec 1993 00:01:27 -0800 (PST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199312142210.AA156105@holmes.acc.Virginia.EDU> from "William Pemberton" at Dec 14, 93 05:10:43 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: 1663 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst William Pemberton spake of these matters: > Does anyone have any experience using Majordomo to manage a lot of > lists? In actuality, no, so take my following comments for whatever they're worth... > Currently, we have around 400 lists that are local to UVa (they are all > run off of mmdf). We are looking at moving to something like > Majordomo, but are concerned about things like the CPU load (especially > since perl seems to be a CPU hog). > > Anybody have any insight on if this is going to be too much/no > problem/maybe a hassle? One of the *good* features about Majordomo is that it is not required to be involved in message distribution, i.e. the actual sending of list messages to all subscribers. Majordomo can simply manage the addition and deletion of addresses from the list files themselves. If you are currently happy with how mmdf handles your list postings in terms of performance, etc, (and assuming the mmdf lists are kept in a simple one-address-per-line text file), you can add Majordomo to handle the subscriptions and keep your message distribution as-is. In my experience, message postings account for nearly all the system load; subscription requests are (relatively) few and far between in comparison. Because of that, the true performance of perl in this context doesn't really matter a whole lot. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ The skill of accurate perception is called cynicism by those who don't possess it. From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 15 17:33:21 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA15432; Wed, 15 Dec 93 17:33:21 GMT Received: from bit-bucket.tcs.tulane.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA15425; Wed, 15 Dec 93 09:33:10 PST Received: by bit-bucket.tcs.tulane.edu (AIX 3.2/UCB 5.64/4.03) id AA15917; Wed, 15 Dec 1993 11:31:02 -0600 From: robyn@bit-bucket.tcs.tulane.edu (Robyn E. Williamson) Message-Id: <9312151731.AA15917@bit-bucket.tcs.tulane.edu> Subject: AIX/Majordomo installation mess To: majordomo-users@greatcircle.com Date: Wed, 15 Dec 93 11:31:01 CST X-Mailer: ELM [version 2.3 PL11] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, I am trying to install Majordomo on an RS/6000. I just installed perl 4.035 and majordomo 1.62. I set up a test list. However, when I attempt to send any queries to majordomo, I receive an empty message with an Apparently-To: field in the header instead of the usual To: field. The commands I tried to send to majordomo were info and help. Does anyone have any clues? or can point me towards a FAQ or archive? Thanks, Robyn =============================================================================== Robyn E. Williamson Tulane University Computing Services Academic Computing Analyst New Orleans LA 70118 robyn@mailhost.tcs.tulane.edu (504) 865-5631 From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 15 19:50:19 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA16050; Wed, 15 Dec 93 19:50:19 GMT Received: from bit-bucket.tcs.tulane.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA16036; Wed, 15 Dec 93 11:50:06 PST Received: by bit-bucket.tcs.tulane.edu (AIX 3.2/UCB 5.64/4.03) id AA18388; Wed, 15 Dec 1993 13:48:02 -0600 From: robyn@bit-bucket.tcs.tulane.edu (Robyn E. Williamson) Message-Id: <9312151948.AA18388@bit-bucket.tcs.tulane.edu> Subject: AIX/Majordomo installation mess, again To: majordomo-users@greatcircle.com Date: Wed, 15 Dec 93 13:48:02 CST X-Mailer: ELM [version 2.3 PL11] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk OK, Here's more info about my installation problem. >Hello, >I am trying to install Majordomo on an RS/6000. I just installed perl 4.035 >and majordomo 1.62. I set up a test list. However, when I attempt to send >any queries to majordomo, I receive an empty message with an Apparently-To: >field in the header instead of the usual To: field. The commands I tried >to send to majordomo were info and help. Does anyone have any >clues? or can point me towards a FAQ or archive? This is my majordomo.cf file # $whereami -- What machine am I running on? $whereami = "bit-bucket.tcs.tulane.edu"; # $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 = "/usr/local/apps/majordomo"; # $listdir -- Where are the mailing lists? $listdir = "/usr/local/apps/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 $ And here are the relevant lines from /etc/aliases majordomo: "|/usr/local/apps/majordomo/wrapper majordomo" majordomo-owner: robyn owner-majordomo: robyn kats: :include:/usr/local/apps/majordomo/lists/kats owner-kats: robyn@bit-bucket.tcs.tulane.edu kats-request: "|/usr/local/apps/majordomo wrapper request-answer kats" kats-approval: robyn@bit-bucket.tcs.tulane.edu =============================================================================== Robyn E. Williamson Tulane University Computing Services Academic Computing Analyst New Orleans LA 70118 robyn@mailhost.tcs.tulane.edu (504) 865-5631 From Majordomo-Users-Owner@GreatCircle.COM Thu Dec 16 08:42:23 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05321; Thu, 16 Dec 93 08:42:23 GMT Received: from deeptht.armory.com ([198.202.199.210]) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05314; Thu, 16 Dec 93 00:42:03 PST Received: by deeptht.armory.com id aa02500; 16 Dec 93 0:41 PST From: John DuBois Date: Thu, 16 Dec 1993 00:40:01 -0800 In-Reply-To: Alan Millar "Re: Lots of lists" (Dec 15, 12:01am) X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: Alan Millar , wfp5p@holmes.acc.virginia.edu (William Pemberton) Subject: Re: Lots of lists Cc: majordomo-users@GreatCircle.COM Message-Id: <9312160040.aa02471@deeptht.armory.com> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Dec 15, 12:01am, Alan Millar wrote: } If you are currently happy with how mmdf handles your list postings } in terms of performance, etc, (and assuming the mmdf lists are kept } in a simple one-address-per-line text file), you can add Majordomo } to handle the subscriptions and keep your message distribution as-is. The most common way of organizing lists under MMDF is to have them compiled into a database along with the other MMDF configuration information. But, they can also be read from files of the sort majordomo creates, and don't take significantly longer than the compiled ones to process. John From Majordomo-Users-Owner@GreatCircle.COM Thu Dec 16 08:57:28 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05509; Thu, 16 Dec 93 08:57:28 GMT Received: from wsooti22.info.win.tue.nl by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05502; Thu, 16 Dec 93 00:57:13 PST Received: from localhost by wsooti22.info.win.tue.nl (8.6.4/1.45) id JAA23519; Thu, 16 Dec 1993 09:58:04 +0100 Date: Thu, 16 Dec 1993 09:58:04 +0100 From: haroldw@info.win.tue.nl (H.T.G. Weffers) Message-Id: <199312160858.JAA23519@wsooti22.info.win.tue.nl> To: majordomo-users@GreatCircle.COM Subject: A Beginner's question Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, At the moment I maintain a small mailing list that works using 'filter' and a small script. Although this works fine I want to look a bit further and one of our sysops pointed me to majordomo. I ftp-ed the package and read the documentation. I want to stress that I am no sysop and I do not have access to the system directories with respect to writing in them. My question now is if it is possible to install majordomo in a regular user account and how I should do this. If people have done this before I would really appreciate it if they could send me some pointers or, even better, some examples. Thank you very much in advance, Harold Weffers c/o Department of Mathematics and Computing Science HG 6.57, Eindhoven University of Technology /_/ / / P.O.Box 513, 5600 MB EINDHOVEN, The Netherlands / /. /_/_/. Telephone: (+31) (0)40 - 474333 Internet: haroldw@win.tue.nl #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~# | Disclaimer: I say what? | - To err is human, to forgive divine - | #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~# From Majordomo-Users-Owner@GreatCircle.COM Fri Dec 17 08:54:28 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA00922; Fri, 17 Dec 93 08:54:28 GMT Received: from m2xenix.psg.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA00915; Fri, 17 Dec 93 00:54:19 PST Received: by m2xenix.psg.com (/\==/\ Smail3.1.25.1 #25.2) id ; Fri, 17 Dec 93 00:55 PST Received: from philapd by sun4nl.NL.net via EUnet id AA24442 (5.65b/CWI-3.3); Fri, 17 Dec 1993 09:55:03 +0100 Received: from apdnm.idca.tds.philips.nl by philapd.idca.tds.philips.nl with UUCP id AA28036 (879.1.1.13/2.18); Fri, 17 Dec 93 09:53:10 GMT (MET) X-Organisation: Digital Equipment Enterprise bv, P.O. Box 245, NL-7300 AE Apeldoorn, The Netherlands Received: from saturnus.idca.tds.philips.nl by apdnm.idca.tds.philips.nl with SMTP id AA19851 (879.1.1.13/2.18); Fri, 17 Dec 93 08:54:12 GMT (MET) Received: by saturnus.idca.tds.philips.nl (5.65/25-eef) id AA09307; Fri, 17 Dec 93 09:53:21 +0100 From: Henk de Groot Message-Id: <9312170853.AA09307@saturnus.idca.tds.philips.nl> Subject: "help" To: majordomo@psg.com Date: Fri, 17 Dec 93 9:53:18 MET X-Mailer: ELM [version 2.3 PL11] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk help "help" From Majordomo-Users-Owner@GreatCircle.COM Sun Dec 19 22:20:45 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11336; Sun, 19 Dec 93 22:20:45 GMT Received: from hub.terc.edu (terc.edu) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA02577; Fri, 17 Dec 93 12:13:48 PST 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 PAA27499; Fri, 17 Dec 1993 15:12:46 -0500 Message-Id: <199312172012.PAA27499@hub.terc.edu> Date: 17 Dec 1993 15:16:24 -0500 From: "Andrew Boyd" Subject: help- longer lines To: "majordomo-users" , "majordomo-workers" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Subject: help: longer lines Fellow majordomoteers-- I have some very long email addresses that I can't subscribe properly because I run into an 81 character limit on the length of a command line I can send to majordomo. Does anyone know of a way around this? Is there a line continuation character?.... --Andrew Andrew Boyd | Technical Education Research Centers Network Manager | 2067 Mass. Ave. Global Lab | Cambridge, MA 02140 | VOICE: 1-617-547-0430 | FAX: 1-617-349-3535 andrew_boyd@terc.edu | TOLL FREE: 1-800-277-8372 From Majordomo-Users-Owner@GreatCircle.COM Sun Dec 19 15:20:05 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11767; Sun, 19 Dec 93 22:53:35 GMT Received: from hub.terc.edu (terc.edu) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA02577; Fri, 17 Dec 93 12:13:48 PST 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 PAA27499; Fri, 17 Dec 1993 15:12:46 -0500 Message-Id: <199312172012.PAA27499@hub.terc.edu> Date: 17 Dec 1993 15:16:24 -0500 From: "Andrew Boyd" Subject: help- longer lines To: "majordomo-users" , "majordomo-workers" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Subject: help: longer lines Fellow majordomoteers-- I have some very long email addresses that I can't subscribe properly because I run into an 81 character limit on the length of a command line I can send to majordomo. Does anyone know of a way around this? Is there a line continuation character?.... --Andrew Andrew Boyd | Technical Education Research Centers Network Manager | 2067 Mass. Ave. Global Lab | Cambridge, MA 02140 | VOICE: 1-617-547-0430 | FAX: 1-617-349-3535 andrew_boyd@terc.edu | TOLL FREE: 1-800-277-8372 From Majordomo-Users-Owner@GreatCircle.COM Sun Dec 19 15:38:03 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11997; Sun, 19 Dec 93 22:59:10 GMT Received: from hub.terc.edu (terc.edu) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA02577; Fri, 17 Dec 93 12:13:48 PST 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 PAA27499; Fri, 17 Dec 1993 15:12:46 -0500 Message-Id: <199312172012.PAA27499@hub.terc.edu> Date: 17 Dec 1993 15:16:24 -0500 From: "Andrew Boyd" Subject: help- longer lines To: "majordomo-users" , "majordomo-workers" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Subject: help: longer lines Fellow majordomoteers-- I have some very long email addresses that I can't subscribe properly because I run into an 81 character limit on the length of a command line I can send to majordomo. Does anyone know of a way around this? Is there a line continuation character?.... --Andrew Andrew Boyd | Technical Education Research Centers Network Manager | 2067 Mass. Ave. Global Lab | Cambridge, MA 02140 | VOICE: 1-617-547-0430 | FAX: 1-617-349-3535 andrew_boyd@terc.edu | TOLL FREE: 1-800-277-8372 From Majordomo-Users-Owner@GreatCircle.COM Mon Dec 20 00:06:30 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12702; Mon, 20 Dec 93 00:06:30 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12693; Sun, 19 Dec 93 16:06:15 PST Message-Id: <9312200006.AA12693@mycroft.GreatCircle.COM> To: "Andrew Boyd" Cc: "majordomo-users" , "majordomo-workers" Subject: Re: help- longer lines In-Reply-To: Your message of 17 Dec 1993 15:16:24 -0500 Date: Sun, 19 Dec 1993 16:06:13 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Andrew Boyd" writes: # Subject: help: longer lines # # Fellow majordomoteers-- # # I have some very long email addresses that I can't subscribe # properly because I run into an 81 character limit on the # length of a command line I can send to majordomo. Does anyone # know of a way around this? Is there a line continuation # character?.... There is no limit within Majordomo on length of input lines; it must be your mailer. Adding a continuation character has been a minor item on the "ToDo" list for a long time, but has just never made it to the top. Maybe after 2.0 gets out. -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@GreatCircle.COM Mon Dec 20 22:14:06 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19570; Mon, 20 Dec 93 22:14:06 GMT Received: from mail.think.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19563; Mon, 20 Dec 93 14:13:59 PST Received: from Telecaster.Think.COM by mail.think.com; Mon, 20 Dec 93 17:15:00 -0500 From: Barry Margolin Received: by telecaster.think.com (4.1/Think-1.2) id AA23359; Mon, 20 Dec 93 17:15:28 EST Date: Mon, 20 Dec 93 17:15:28 EST Message-Id: <9312202215.AA23359@telecaster.think.com> To: news.comp.unix.admin@Think.COM, majordomo-users@greatcircle.com Subject: converting aliases to :include: files Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Does anyone have a tool that will take a sendmail aliases file, find all the lists that have more than N addresses, and move the contents out to a :include: file? We've been having some problems which we think may be due to frequent rebuilding of the aliases database; moving most lists out to external files would obviate most database rebuilds. Also, some automated alias management programs (e.g. majordomo) will only operate on :include: files. We have hundreds of lists that are contained directly in the aliases file, so an automated conversion tool would be nice. From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 21 03:49:40 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA21941; Tue, 21 Dec 93 10:03:57 GMT Received: from motgate.mot.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA21930; Tue, 21 Dec 93 02:03:36 PST Received: from pobox.mot.com ([129.188.137.100]) by motgate.mot.com with SMTP (5.67a/IDA-1.4.4/MOT-2.15 for ) id AA13542; Tue, 21 Dec 1993 04:04:24 -0600 Received: from glas.cork.cig.mot.com by pobox.mot.com with SMTP (5.67a/IDA-1.4.4/MOT-2.15 for ) id AA08644; Tue, 21 Dec 1993 04:04:21 -0600 Received: from bui200.cork.cig.mot.com (bui200.cork.cig.mot.com [175.3.47.200]) by glas.cork.cig.mot.com (8.6.4/8.6.4) with ESMTP id KAA02384 for ; Tue, 21 Dec 1993 10:04:31 GMT Received: from localhost (mcglough@localhost) by bui200.cork.cig.mot.com (8.6.4/8.6.4) id KAA14637 for majordomo-users@greatcircle.com; Tue, 21 Dec 1993 10:04:24 GMT From: mcglough@cork.cig.mot.com (Mark McGloughlin) Message-Id: <9312211004.ZM14635@bui200> Date: Tue, 21 Dec 1993 10:04:24 +0000 X-Mailer: Z-Mail (2.1.5 20sep93) To: majordomo-users@greatcircle.com Subject: Auto archiving for majordomo Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I just installed majordomo 1.62 and it is really neat. The one thing I want to do that I so far cannot figure out is automatically archive messages sent to a group for later "get" commands Can anyone help ?? Thanks, Mark... -- _ _ Mark McGloughlin | Ph: +353-21-357101 _/ \_/ \_ Motorola Ireland Ltd. | Fax: +353-21-357635 / \_/ \_/ \ Cellular Infrastructure Div | POST: Q10543@email.mot.com \_/ \_/ \_/ Blackrock, Cork, Ireland. | Inet: mcglough@cork.cig.mot.com <-- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ !NEW!NEW!NEW!NEW!NEW!NEW!NEW! From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 21 16:28:01 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA23013; Tue, 21 Dec 93 16:28:01 GMT Received: from m2xenix.psg.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA22997; Tue, 21 Dec 93 08:27:40 PST Received: by m2xenix.psg.com (/\==/\ Smail3.1.25.1 #25.2) id ; Tue, 21 Dec 93 08:28 PST Message-Id: Received: from afj-pc.cc.rl.ac.uk by letterbox.rl.ac.uk with SMTP (PP) id <11344-0@letterbox.rl.ac.uk>; Tue, 21 Dec 1993 16:28:42 +0000 X-Sender: andyj@letterbox.rl.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 21 Dec 1993 16:27:57 +0000 To: majordomo@psg.com From: a.jessett@rl.ac.uk (Andrew Jessett) Subject: X-Mailer: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk help list end Andrew F Jessett Telephone: 0235 44 5659 Science and Engineering Council Fax: 0235 55 6626 Rutherford Appleton Laboratory Chilton Didcot Oxon OX11 OQX England From Majordomo-Users-Owner@GreatCircle.COM Tue Dec 21 16:42:00 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA23189; Tue, 21 Dec 93 16:42:00 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA23181; Tue, 21 Dec 93 08:41:55 PST Message-Id: <9312211641.AA23181@mycroft.GreatCircle.COM> To: majordomo-users@GreatCircle.COM Subject: Majordomo commands to Majordomo-Users Date: Tue, 21 Dec 1993 08:41:54 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Just in case you're all wondering why these Majordomo commands keep coming through to the Majordomo-Users mailing list... Somebody runs Majordomo under another alias at their site, and has "majordomo" set up as an alias for "Majordomo-Users@GreatCircle.COM" so that they could post to this list conveniently. Somebody else told a lot of people that the address to use for requests at that site is "Majordomo", rather than the other alias they run Majordomo under, and all those messages are getting forwarded to the Majordomo-Users mailing list. Most of them are getting intercepted by the administrivia filters, but some are slipping through. I've asked the site to _please_ change their Majordomo alias so that it doesn't point to Majordomo-Users@GreatCircle.COM, but they haven't done it (at least, not yet). -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@GreatCircle.COM Wed Dec 22 01:47:55 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA25076; Wed, 22 Dec 93 01:47:55 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA25063; Tue, 21 Dec 93 17:47:05 PST Message-Id: <9312220147.AA25063@mycroft.GreatCircle.COM> To: mcglough@cork.cig.mot.com (Mark McGloughlin) Cc: majordomo-users@greatcircle.com Subject: Re: Auto archiving for majordomo In-Reply-To: Your message of Tue, 21 Dec 1993 10:04:24 +0000 Date: Tue, 21 Dec 1993 17:47:04 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk mcglough@cork.cig.mot.com (Mark McGloughlin) writes: # I just installed majordomo 1.62 and it is really neat. The one thing I want t # o # do that I so far cannot figure out is automatically archive messages sent to # a # group for later "get" commands # # Can anyone help ?? Here's a new script called "archive" that will be part of the next Majordomo release. I've been using it for a couple of months, and I posted it to Majordomo-Workers a couple of months ago and nobody has complained about bugs in it, so I think it's reasonably solid. Instructions (such as they are; it has the usual terse Majordomo documentation style) are in the comments at the top of the program. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 #!/usr/local/bin/perl # Copyright 1993, D. Brent Chapman. All Rights Reserved. For use by # permission only. # # $Source: /mycroft/brent/majordomo/RCS/archive,v $ # $Revision: 1.2 $ # $Date: 1993/11/09 07:17:05 $ # $Author: brent $ # $State: Exp $ # # $Locker: $ # # archive -f {-u|-a} [-d|-m|-y] [file ...] # -f REQUIRED; specifies base file name for archive # -u Input is a UNIX archive (separated by "From " lines) to split # -a Input is a message to append to archive # -d Archive file is .YYMMDD # -m Archive file is .YYMM # -y Archive file is .YY # Exactly one of "-u" or "-a" must be specified. # At most one of "-d", "-m", or "-y" may be specified; if none is # specified, archive name is simply # # An example of using "archive" to split an existing UNIX-style archive # named "my-list.archive" into by-day archive files named "my-list.YYMMDD": # # archive -f my-list -d -u my-list.archive # # A sample /etc/aliases file entry to use "archive" add each incoming message # to a "my-list.YYMM" file in the "/usr/local/mail/lists/my-list.archive" # directory: # # my-list-archive: "|/usr/local/mail/majordomo/wrapper archive # -f /usr/local/mail/lists/my-list.archive/my-list # -m -a" # set our path explicitly $ENV{'PATH'} = "/bin:/usr/bin:/usr/ucb"; # What shall we use for temporary files? $tmp = "/tmp/majordomo.$$"; # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; if ($ARGV[0] eq "-C") { $cf = $ARGV[1]; shift(@ARGV); shift(@ARGV); } if (! -r $cf) { die("$cf not readable; stopped"); } eval(`cat $cf`); # All these should be in the standard PERL library unshift(@INC, $homedir); require "ctime.pl"; # To get MoY definitions for month abbrevs require "majordomo_version.pl"; # What version of Majordomo is this? require "majordomo.pl"; # all sorts of general-purpose Majordomo subs require "shlock.pl"; # NNTP-style file locking # Here's where the fun begins... require "getopts.pl"; $m = 1; foreach (@ctime'MoY) { $MoY{$_} = $m++; } $usage = "Usage: $0 -f {-u|-a} [-d|-m|-y] [file ...]"; &Getopts("f:uadmy") || die("$usage\nStopped"); if (!defined($opt_f)) { print STDERR "'-f ' required\n$usage\n"; exit 1; } if (defined($opt_a)) { $mutex++; } if (defined($opt_u)) { $mutex++; } if ($mutex != 1) { print STDERR "Either '-a' or '-u' required\n$usage\n"; exit 2; } $mutex = 0; if (defined($opt_d)) { $mutex++; } if (defined($opt_m)) { $mutex++; } if (defined($opt_y)) { $mutex++; } if ($mutex > 1) { print STDERR "Only one of '-d', '-m', or '-y' allowed\n$usage\n"; exit 3; } if (defined($opt_a)) { ($sec, $min, $hour, $mday, $mon, $year, $wday, $yday, $isdst) = localtime(time); &open_archive(FILE, $year, $mon + 1, $mday); } while (<>) { if (/^From\s/) { if (/^From\s+\S+\s+(Sun|Mon|Tue|Wed|Thu|Fri|Sat)\s+(Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)\s+\d\d?\s+\d\d?:\d\d:\d\d\s+\d{2,4}\s*$/i) { if (defined($opt_u)) { if (defined($is_open)) { print FILE "\n"; &lclose(FILE); } &open_archive_unix(FILE, $_); } print FILE "$_"; } else { print FILE ">$_"; } } else { print FILE $_; } } print FILE "\n"; &lclose(FILE); sub open_archive_unix { local($FH) = shift; local($from) = shift; local($junk, $addr, $dow, $moy, $dom, $time, $year, @rest); ($junk, $addr, $dow, $moy, $dom, $time, $year, @rest) = split(/\s+/,$from); &open_archive($FH, $year % 100, $MoY{$moy}, $mday); } sub open_archive { local($FH) = shift; local($year) = shift; local($mon) = shift; local($mday) = shift; local($suffix); if (defined($opt_y)) { $suffix = sprintf(".%02d", $year % 100); } if (defined($opt_m)) { $suffix = sprintf(".%02d%02d", $year % 100, $mon); } if (defined($opt_d)) { $suffix = sprintf(".%02d%02d%02d", $year % 100, $mon, $mday); } &lopen($FH, ">>", "$opt_f$suffix") || die("Can't append to $opt_f$suffix: $!"); $is_open = 1; } From Majordomo-Users-Owner@GreatCircle.COM Wed Dec 22 20:36:05 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA27690; Wed, 22 Dec 93 20:36:05 GMT Received: from skycat.usask.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA27683; Wed, 22 Dec 93 12:35:51 PST Received: from skdad.USask.ca by SKYCAT.USask.CA (PMDF V4.2-14 #3676) id <01H6S83UFFE89BVVXN@SKYCAT.USask.CA>; Wed, 22 Dec 1993 14:36:45 CST Received: from graph.USask.ca by skdad.USask.ca (4.1/SMI-4.1) id AA13366; Wed, 22 Dec 93 14:36:18 CST Date: Wed, 22 Dec 1993 14:36:18 -0600 (CST) From: jones@skdad.usask.ca (Bill Jones) Subject: working around sendmail limitations To: majordomo-users@greatcircle.com Message-Id: <9312222036.AA13366@skdad.USask.ca> X-Envelope-To: majordomo-users@greatcircle.com Content-Transfer-Encoding: 7BIT Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I maintain a mailing list which has recently grown rapidly and now numbers about 250 names. Although we in the CS department run fairly recent versions of sendmail on our machines, outgoing email must pass through a campus gateway which is a VMS machine and contains the 1024 limitation on header field length. Would someone care to suggest patches to majordomo for doing splitting of address lists in such a situation? I have checked the mailing list archives and found discussion of the topic in 9302 and again in 9309 where someone found it desirable for reasons of delivery time. No patches, however. Suggestions that I change the way email is handled on this campus, or upgrade the mailer on the VMS machine, or get them to convert to Unix, or that this isn't in the majordomo philosophy, will be cheerfully ignored, thank you. None of those options is within my control. I have reported the problem and someday it will be fixed, but meanwhile I have to work around it. Changing majordomo to allow splitting when desired seems to be a cleaner solution than adding more layers of wrapper programs. I can write my own patches if necessary, but would prefer to build on work of more experienced majordomo hackers, if any of them have done this. From Majordomo-Users-Owner@GreatCircle.COM Thu Dec 23 04:49:41 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA29442; Thu, 23 Dec 93 04:49:41 GMT Received: from spiff.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA29435; Wed, 22 Dec 93 20:49:30 PST Received: by spiff.ccs.carleton.ca (4.1/SMI-4.0-mcr) id AA07157; Wed, 22 Dec 93 23:51:02 EST Date: Wed, 22 Dec 93 23:51:02 EST From: mcr@ccs.carleton.ca (Michael Richardson) Message-Id: <9312230451.AA07157@spiff.ccs.carleton.ca> To: jones@skdad.usask.ca Cc: majordomo-users@GreatCircle.COM In-Reply-To: Bill Jones's message of Wed, 22 Dec 1993 14:36:18 -0600 (CST) <9312222036.AA13366@skdad.USask.ca> Subject: working around sendmail limitations Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Since majordomo doesn't handle sending the mail, this is not an issue. Sendmail does *not* expand the To: or CC: fields, so you aren't going have a header problem. The problem would be, I assume, that the VMS SMTP server chokes when handed lots and lots of addresses on the RCPT envelope? I think you can give an option to your TCP mailer definition to limit the number of addresses that sendmail will hand to remote systems. The only other option is to chop the list up into many pieces, put each one on a master list that invokes resend for each alias. Some simple perl ought to be able to roll the list, and create new ones. At Carleton, /etc/aliases is built from several files, and it isn't too hard to add a file to the list that is fed to cat, and make that file writable to some admin pseudo user that does the list rolling, and is in the majordom group. (I would not let the majordom user be able to write to the alias file!) -- :!mcr!: HOME: mcr@sandelman.ocunix.on.ca +1 613 788 2600 3853 Michael Richardson WORK: mcr@ccs.carleton.ca (Conservation Ecology) Here is an HTML reference to my bio. foreach $X ("E-Journal","NetBSD","Perl","Physics") { print "MCR hacks $X\n"; }; From Majordomo-Users-Owner@GreatCircle.COM Thu Dec 23 23:58:15 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01067; Thu, 23 Dec 93 23:58:15 GMT Received: from Sun.COM by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01060; Thu, 23 Dec 93 15:58:03 PST Received: from EBay.Sun.COM (female.ebay.sun.com) by Sun.COM (4.1/SMI-4.1) id AA24950; Thu, 23 Dec 93 15:59:08 PST Received: from strider.EBay.Sun.COM by EBay.Sun.COM (4.1/SMI-4.1) id AA27847; Thu, 23 Dec 93 15:59:06 PST Received: by strider.EBay.Sun.COM (5.0/SMI-SVR4) id AA00518; Thu, 23 Dec 1993 15:59:39 +0800 Date: Thu, 23 Dec 1993 15:59:39 +0800 From: Gregory.Hjelmstad@EBay.Sun.COM (Greg Hjelmstad) Message-Id: <9312232359.AA00518@strider.EBay.Sun.COM> To: majordomo-users@GreatCircle.COM Subject: sorry to bother everyone....... X-Sun-Charset: US-ASCII Content-Length: 551 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk But, I am a bit confused. I just installed majordomo on my system here, running Solaris2.3. It seems to work fine if the requests are sent from the system where majordomo is running, but if I get a request from another system, sendmail seems to just hang and the reply mail is never sent and there is nothing inserted into the Log. I'm most certain that this is operator error, but I have read through the Docs and man pages and I can't find anything that appears to me to be a hint to a solution. Any help appreciated, thanks, Greg Hjelmstad From Majordomo-Users-Owner@GreatCircle.COM Fri Dec 24 19:16:32 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA03854; Fri, 24 Dec 93 19:16:32 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA03847; Fri, 24 Dec 93 11:15:39 PST Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA17591 (5.65c/IDA-1.4.4 for ); Fri, 24 Dec 1993 14:16:32 -0500 Message-Id: <199312241916.AA17591@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: A Christmas Present (Majordomo 2.0 requirement/design spec) Date: Fri, 24 Dec 1993 14:16:31 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all: I have just finished going over Alan, Brent, Jeniffer ... and my mail about majordomo 2.0. I think I have identified all of the changes needed for majordomo 2.0 above and beyond my config file stuff. Alan and I had originally planned on splitting the work between us, but Alan is up to his eyeballs in alligators at the moment and will be for a while in the future. So this is also a call for volunteers to write some of this code. However, I want to get a resonable set of specifications down so that we don't end up with majordomo 2.0 look like it was coded by a committee. This is a first pass at the design doc. It is really more of a requirements doc with some examples thrown in. I have one request: please send me your comments, quips, evasions, questions or answers on this doc ESPECIALLY if you are volunteering to do some of the coding. Lately I feel like I am the only person on the majordomo-workers list. Then again, I am probably the only person on the majordomo-workers list without a life 8-). ***'s mark items that (I think) can be handled independently. There should exist a mechanism to extend the list of acceptable command line parameters to getopts. (This could be used to add a -l command line option that specified a listname so that majordomo can be used at the -request address for a mailing list.) *** Before and after the dispatch portion of the code (where the do_ functions are called), the user will be able to provide functions to be run. These functions can be used to provide access control etc for majordomo. There should be a function that will register these pre and post functions. The interface to the pre/post dispatch functions should be well defined. Access to global variables in majordomo (e.g. $reply_to) should be through some agreed upon mechanism (e.g. copying the variable reply_to to $export{"reply_to"}) for use by the pre/post routines. This allows the internal variable names etc of majordomo to change without trashing the pre/post dispatch environments. *** Replace the main dispatching case (like) statement that calls do_ with a loop that allows 1 or more functions to be called before the main function. The loop will also allow 1 or more functions to be called after the main function is called. This main loop will be table driven so that additional command can be added. Functions will be provided to 1) add a pre command E.G.: add_pre(function_name (e.g. pre_add), majordomo_command); 2) add a (new) main command E.G. add_do(function_name (e.g. do_subscribe), majordomo_command (e.g. add), type (admin|user), approvable (yes/no) description); 3) add a post command E.G. add_post(function_name (e.g. post_add), majordomo_command); The command to register a new main command will require a description of the command. This description will be provided to the user as part of the help command. This new command will be flagged as a non-standard command in the help documentation. There will have to be a distinction between "user" and "administrative" commands, so that admin commands aren't put into the user help message. Also there will be an entry that states that the command can be the object of an approve command, and what password should be used. The interface to the pre/post commands should be well defined. Access to global variables in majordomo (e.g. $reply_to) should be through some agreed upon mechanism (e.g. copying the variable reply_to to $export{"reply_to"}) for use by the pre/post routines. This allows the internal variable names etc of majordomo to change without trashing the pre/post command environments. This idea should be extended to all interactions that the pre/post commands have with the enclosing majordomo environment. One variable that should be supplied is the name of the current majordomo command being processed. This allows a generic pre_function to be used to do something like add a etc. Two calling pardigms have been suggested: $error = &pre_command(*parts) and ($error, @parts) = &pre_command(@parts) where parts is the array that is passed into do_command. The first is more efficient and the return type is a single value, but means that the programmer will have to understand glob types, and how to manipulate them. The second mechanism is simpler for perl novices, but the return value from the routine will have to be a composite of error code and the massaged parts array. The set of error codes must have the following: 1) OK: All is ok (maybe (OK_NO_ACTION and OK_ACTION should be present to differentiate the two types of ok?) 2) OK_STOP: All is ok, but don't call more pre_commands, or do_command (i.e. the pre_command handled the entire request). 2) ERROR_STOP: Fatal error, don't call more pre_commands, or do_command (pre command reported error) 3) ERROR: Error, but continue processing with other pre and do_commands (the later commands report the error) 4) ERROR_ABORT: Abort processing of any more commands (i.e. exit majordomo through normal exit code) There should be some way to specify a required order for application of commands. By way of a contrived example: You have 2 modules: 1) one of which handles a listserv "unsubscribe *" (unsubscribe from all lists on the server) request. 2) The other allows putting majordomo at the -request address, and adds the listname to any commands that need it. If it is the bblisa-request list, it checks parts[0] to see if it is bblisa, if not it puts bblisa in parts[0]. If the request is approve, the parts[2] element is used in place of parts[0]. I get a "unsubscribe *" request to the bblisa-request mailing list. application order result for pre_ 1 then 2 Everthing works fine. Module 1 recognized the * command, and unsubscribes from the list, and returns, OK_STOP. 2 never gets called. 2 then 1 Boom. 2 checks to see if * is the same as bblisa, (it isn't) so it adds bblisa. Module 1 sees the command "unsubscribe bblisa *" doesn't recognize it as "unsubscribe *", and returns. The main loop calls do_unsubscribe. do_unsubscribe, finding no email address '*' reports an error. Granted, the user screwed up by posting an 'unsubscribe *' to a list-request address, but hey I said the example was contrived. Maybe this problem could be handled by structuring the loading algorithm. A simple hack like naming the files: mj_at_-request-3.pl mh_search_archives-99.pl restrict_access.pl rationalize_reply_to.pl listserv_unsubscribe-2.pl global_list_database.pl Loading the files accoring to the numbers following the final - produces the order: listserv_unsubscribe-2.pl mj_at_-request-3.pl mh_search_archives-99.pl restrict_access/rationalize/global (what ever order you want, since an order was not specified) and the pre-commands would be loaded/applied in the same order. This doesn't require any real perl hacking ability on the part of the majordomo maintainer. Hey, if it works for SVR4 it can't be all bad right 8-) 8-) 8-)? The approve command will have to be rewritten to be table driven just like the main dispatch loop so that new commands can use the approve functionality. *** The REPLY filehandle will be replaced with a command &add_reply(text). There will also be a command called &send_reply that takes the first line of the reply, and strips that line and uses its contents as the address to send the reply to. There will have to be commands to iterate over the reply buffer since the reply buffer may be in an @array, or may be on external disk for those machines that have limited memory. *** Some mechanism should be added to allow a help message that includes the administrative commands. Maybe approve password help listname could be overloaded. *** end Once these changes are in place, it should be possible to have an external perl module be eval'led by majordomo, and that module should be portable and compatible with all future versions of majordomo (Hmm, why does the room have a red haze all of a sudden?). Maybe some modues could be included with the majordomo distribution proper. Some needed modules seem to be: An access control module that only allows majordomo to process/reply to certain addresses. The ability to handle "subscribe" messages to the -request list. This would require the addition of a command line argument to specify the list name, and a pre subscribe command that would change the "subscribe" command into "subscribe listname" and then pass it off to the do_subscribe routine. This could be made generic enough to allow listserv style subscribe requests to be handled by majordomo. For completeness sake, all commands that take a list name could use this routine to permit bare index, get, unsubscribe ... functions to work. Happy holidays. -- 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@GreatCircle.COM Thu Dec 30 18:44:05 1993 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA26622; Thu, 30 Dec 93 18:44:05 GMT Received: from mystech.com (mystech.mystech.com) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA26615; Thu, 30 Dec 93 10:43:56 PST Received: by mystech.com (4.1/SMI-4.1) id AA12794; Thu, 30 Dec 93 13:48:37 EST Date: Thu, 30 Dec 93 13:48:37 EST From: smithr@mystech.com (Roger Smith) Message-Id: <9312301848.AA12794@mystech.com> To: Majordomo-Users@GreatCircle.COM Subject: Problem setting up the mailing list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, I am just trying to setup Majordomo for the first time. I have 50% success and 50% failure. Subscription, get, etc. sent to "listserv" (my name for majordomo) works fine. But when I send to the list alias or the list-archive I get terrible error messages, either from majordomo or sendmail - I am not sure which. Below are the messages bounced back to me when I send to the list (elecsim) and the list-archive (elecsim-archive) respectively. Can anyone give me some tips on what might be wrong? Thanks Roger Smith smithr@mystech.com ----------------------------------------------------------------- From daemon Thu Dec 30 13:41:10 1993 Return-Path: Received: by mystech.com (4.1/SMI-4.1) id AB12764; Thu, 30 Dec 93 13:41:08 EST Date: Thu, 30 Dec 93 13:41:08 EST From: Mailer-Daemon (Mail Delivery Subsystem) Subject: Returned mail: unknown mailer error 1 Message-Id: <9312301841.AB12764@mystech.com> To: owner-elecsim Status: R ----- Transcript of session follows ----- /home/aim/home/majordom/majordomo/lists/elecsim: smithr@mystech.com: execute permission denied /home/aim/home/majordom/majordomo/lists/elecsim: smithr@dmso.dtic.dla.mil: execute permission denied /home/aim/home/majordom/majordomo/lists/elecsim: smithr@source.asset.com: execute permission denied 554 "|/home/aim/home/majordom/majordomo/lists/elecsim"... unknown mailer error 1 ----- Unsent message follows ----- Return-Path: Received: by mystech.com (4.1/SMI-4.1) id AA12762; Thu, 30 Dec 93 13:41:08 EST Date: Thu, 30 Dec 93 13:41:08 EST From: smithr (Roger Smith) Message-Id: <9312301841.AA12762@mystech.com> Errors-To: smithr To: elecsim Subject: reflect reflect reflect ------------------------------------------------------------------ From daemon Thu Dec 30 13:42:51 1993 Return-Path: Received: by mystech.com (4.1/SMI-4.1) id AB12777; Thu, 30 Dec 93 13:42:48 EST Date: Thu, 30 Dec 93 13:42:48 EST From: Mailer-Daemon (Mail Delivery Subsystem) Subject: Returned mail: unknown mailer error 5 Message-Id: <9312301842.AB12777@mystech.com> To: owner-elecsim-archive Status: R ----- Transcript of session follows ----- archive: Exec format error 554 "|/home/aim/home/majordom/majordomo/wrapper archive -f /home/aim/home/majordom/majordomo/lists/elecsim.archive/archive -a -d"... unknown mailer error 5 ----- Unsent message follows ----- Return-Path: Received: by mystech.com (4.1/SMI-4.1) id AA12775; Thu, 30 Dec 93 13:42:48 EST Date: Thu, 30 Dec 93 13:42:48 EST From: smithr (Roger Smith) Message-Id: <9312301842.AA12775@mystech.com> Errors-To: smithr To: elecsim-archive Subject: archive archive this file