From Majordomo-Users-Owner@GreatCircle.COM Mon Jan 3 00:04:54 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10561; Mon, 3 Jan 94 00:04:54 GMT Received: from scapa.cs.ualberta.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA10554; Sun, 2 Jan 94 16:04:40 PST Received: by scapa.cs.ualberta.ca id <18687>; Sun, 2 Jan 1994 17:05:45 -0700 Received: from alive.UUCP by nebulus.ampr.ab.ca with UUCP (Smail3.1.28.1 #5) id m0pGc1F-000WEKC; Sun, 2 Jan 94 16:15 CST Received: by alive (Linux Smail3.1.28.1 #14) id m0pGbRW-0002CoC; Sun, 2 Jan 94 15:38 MST Date: Sun, 2 Jan 1994 08:38:35 -0700 From: Marc Slemko Subject: Majordomo execution To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I seem to be having a wee little problem with Majordomo here. It is, like most things, a combination of different things including smail which causes the problem, but I thought that people here would have some ideas on the best way to fix the problem. When I have too many majordomo requests come in at once, my system gets completely bogged down trying to handle them. Smail executes them all right after one another, so I end up having lots of copies of majordomo running at once. That's fine, since they do have file locking and will work "together", but my system can't handle it. I'm running Linux on a very low-end system (IBM compatible 386SX-16) with 4 megs of physical memory and 8 megs of virtual memory for a total of 12 megs of memory. Today, my machine was brought to a complete standstill because a ton of majordomo requests came in all at once and used up all the memory. Each execution of majordomo (well, perl I guess) seems to take just under 1 meg of memory here. Any suggestions as to what the best way to fix this problem is? I often have quite a few requests come in at once since I'm connected via a few UUCP links. Is there any way that majordomo can exit and leave the message in the smail queue for processing later if there are too many copies of it running already? +=================================================================+ | Marc Slemko Edmonton, Alberta, Canada | | marcs@alive.ersys.edmonton.ab.ca 1:342/1003@fidonet.org | | Two wrongs don't make a right, but three lefts do. | +=================================================================+ From Majordomo-Users-Owner@GreatCircle.COM Mon Jan 3 11:10:40 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12063; Mon, 3 Jan 94 11:10:40 GMT Received: from spiff.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12056; Mon, 3 Jan 94 03:10:33 PST Received: by spiff.ccs.carleton.ca (4.1/SMI-4.0-mcr) id AA19263; Mon, 3 Jan 94 06:11:57 EST Date: Mon, 3 Jan 94 06:11:57 EST From: mcr@ccs.carleton.ca (Michael Richardson) Message-Id: <9401031111.AA19263@spiff.ccs.carleton.ca> To: marcs@alive.ersys.edmonton.ab.ca Cc: majordomo-users@GreatCircle.COM In-Reply-To: Marc Slemko's message of Sun, 2 Jan 1994 08:38:35 -0700 Subject: Majordomo execution Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >>>>> "Marc" == Marc Slemko writes: Marc> I seem to be having a wee little problem with Majordomo Marc> here. It is, like most things, a combination of different Marc> things including smail which causes the problem, but I I assume that you mean smail 3.x! Marc> Any suggestions as to what the best way to fix this problem Marc> is? I often have quite a few requests come in at once since Marc> I'm connected via a few UUCP links. Is there any way that a) don't run uuxqt from uucico, run it from the script that calls uucico to poll. b) limit number of uuxqts that can run at the same time. Probably to 1. c) I assume that smail 3.x understands things from sysexits.h. Try having Majordomo do a 'count' of itself and return 'EX_TEMPFAIL' d) if smail 3.x has the ability to just queue the messages (It has been too long since I last installed it, sorry), a la sendmail -odq, then have it do that for all messages, and run the queue from cron. I have a 12Mb (real)+60Mb swap sun 3/60 [too much swap, yeah. But X+emacs+xterms sucks up 10Mb, and when I'm not at the console, it can stay on disk]. latour.sandelman.ocunix.on.ca is the ocunix.on.ca authoritative node, and gets a medium sized newsfeed. I wish I could switch from IDA sendmail to zmailer, but I haven't gotten zmailer to work correctly with aliases. From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 5 06:32:47 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA22108; Wed, 5 Jan 94 06:32:47 GMT Received: from guardian.apple.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA22101; Tue, 4 Jan 94 22:32:39 PST Received: from federal-excess.apple.com by guardian.apple.com with SMTP (5.65/8-Oct-1993-eef) id AA19862; Tue, 4 Jan 94 22:32:38 -0800 Received: from newton.apple.com by federal-excess.apple.com with SMTP (5.64/26-Sep-1993-eef) id AA27167; Tue, 4 Jan 94 22:33:48 PST for majordomo-users@GreatCircle.com Received: from [17.205.4.47] (sandvik-kent.apple.com) by newton.apple.com (4.1/SMI-4.1) id AA17329; Tue, 4 Jan 94 22:32:19 PST Date: Tue, 4 Jan 94 22:32:18 PST Message-Id: <9401050632.AA17329@newton.apple.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@GreatCircle.com From: sandvik@newton.apple.com (Kent Sandvik) Subject: INFO: Unknown mailer error 1 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here's a hint for the archives, if someone else is struggling with the same strange problem, you install the majordomo sw, follow all the rules, daemon owns wrapper, aliases file has the right info, the majordomo.cf file is fully configured, and you still get: sh: /users/majordom/wrapper: cannot execute 554 "|/users/majordom/wrapper majordomo"... unknown mailer error 1 Check the directory of the majordomo where the wrapper is placed, if it does not have the right permissions to execute entries then sendmail will bail out! You have been warned. Maybe we should put together a nice list of gotchas for future majordomo installers? --Kent --- Kent Sandvik, PIE Developer Technical Support, Apple Net: sandvik@newton.apple.com, ALink: KSAND From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 5 13:36:39 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA23867; Wed, 5 Jan 94 13:36:39 GMT Received: from wsooti06.info.win.tue.nl by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA23860; Wed, 5 Jan 94 05:36:12 PST Received: from localhost by wsooti06.info.win.tue.nl (8.6.4/1.45) id OAA01368; Wed, 5 Jan 1994 14:37:28 +0100 Date: Wed, 5 Jan 1994 14:37:28 +0100 From: haroldw@info.win.tue.nl (H.T.G. Weffers) Message-Id: <199401051337.OAA01368@wsooti06.info.win.tue.nl> To: majordomo-users@GreatCircle.COM Subject: [Q]: Multi-user moderation Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, Currently I am moderator of a moderated mailing list at our site. However, I would like to have the possibility of having a couple of restricted users that can also distribute mail via the mailing list without me constantly approving their mails. I tried to simply add a "Approved: " as the first line of an email, but then my header information gets distorted. I also tried to use filter-rules like: if (from contains haroldw@win.tue.nl) then execute /bin/approve But when a mail that is send to a mailing list gets to the mailing list owner it contains more than one "From". The last of these "From"'s is the one I need. Did someone implement a solution to the above problem? Can anyone give me some hints to a solution? 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@info.win.tue.nl #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~# | Disclaimer: I say what? | - To err is human, to forgive divine - | #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~# From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 6 18:01:30 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA00975; Thu, 6 Jan 94 18:01:30 GMT Received: from pau.synnet.COM by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA00968; Thu, 6 Jan 94 10:01:23 PST Received: from nacho.synnet.com by pau.synnet.COM (5.64/1.34) id AA01076; Thu, 6 Jan 94 13:04:05 -0500 (EST) Received: by nacho.synnet.com (4.1/SMI-4.1) id AA14724; Thu, 6 Jan 94 11:03:30 MST Date: Thu, 6 Jan 94 11:03:30 MST From: landon@nacho.synnet.com (Landon Cox) Message-Id: <9401061803.AA14724@nacho.synnet.com> To: majordomo-users@GREATCIRCLE.COM Subject: Ancient history for moderators? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm a list owner at Colorado SuperNet (CSN) who is using version 1.32 of majordomo. I want to be able to moderate the content that gets posted to the list, but have majordomo do the subscription administration automatically. I do not have control over the actual administration of majordomo, which is done by CSN. I've made requests for them to upgrade their version to the latest, but it is so low on their priority list it'll take a long time before it ever gets done. I've had the request in for this upgrade for over 3 months already. Bottom line is I have to work with 1.32. I got a cursory response from CSN's support staff that said that a list owner can only "moderate" subscription requests but not the content that gets posted to the list. This is bogus and totally useless for my purposes and I think they must not know what they are talking about. On the other hand, 1.32 is quite an old version, is it not? and maybe that's the way it was then. Can anyone remember what the actual moderator/list owner capabilities where/are in 1.32? Am I really screwed as a true moderator of the list content which gets posted? Unless I can moderate the postings, I'm not going to be able to use this list. __________________________________________________________________________ Landon Cox landon@synnet.com "I know it's smoke; I saw it at INTEROP." From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 6 18:18:31 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01065; Thu, 6 Jan 94 18:18:31 GMT Received: from spiff.ccs.carleton.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01056; Thu, 6 Jan 94 10:18:18 PST Received: by spiff.ccs.carleton.ca (4.1/SMI-4.0-mcr) id AA12552; Thu, 6 Jan 94 13:19:29 EST Date: Thu, 6 Jan 94 13:19:29 EST From: mcr@ccs.carleton.ca (Michael Richardson) Message-Id: <9401061819.AA12552@spiff.ccs.carleton.ca> To: landon@nacho.synnet.com Cc: majordomo-users@GreatCircle.COM In-Reply-To: Landon Cox's message of Thu, 6 Jan 94 11:03:30 MST <9401061803.AA14724@nacho.synnet.com> Subject: Ancient history for moderators? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Get them to change the alias for "foo-list" to you, and then you can just post to "foo-list-outgoing", or "real-foo-list" (which would go through resend) Mail to the majordomo alias continues unchanged. From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 6 20:55:38 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA02216; Thu, 6 Jan 94 20:55:38 GMT Received: from noc4.dccs.upenn.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA02209; Thu, 6 Jan 94 12:55:24 PST Received: from CCAT.SAS.UPENN.EDU by noc4.dccs.upenn.edu id AA05145; Thu, 6 Jan 94 15:56:48 -0500 Received: by ccat.sas.upenn.edu (AIX 3.2/UCB 5.64/4.03) id AA19292; Thu, 6 Jan 1994 15:56:49 -0500 From: michael@ccat.sas.upenn.edu (Michael Nenashev) Message-Id: <9401062056.AA19292@ccat.sas.upenn.edu> Subject: Time Zone in majordomo To: majordomo-users@greatcircle.com Date: Thu, 6 Jan 1994 15:56:49 -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: 570 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, In spite of my efforts to set TZ to EST, all majordomo replies come with From lstsrv-owner@ccat.sas.upenn.edu Thu Jan 6 20:32:12 1994 Received: by ccat.sas.upenn.edu (AIX 3.2/UCB 5.64/4.03) id AA27387; Thu, 6 Jan 1994 20:32:12 GMT Date: Thu, 6 Jan 1994 20:32:12 GMT ^^^^ I have TZ set to EST5EDT in the environment as well as in majordomo.cf ($ENV{'TZ'} = "EST5EDT";). We are at revision 1.50 of majordomo if it matters. Am I missing something obvious ? Any help appreciated. michael@ccat.sas.upenn.edu From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 7 15:58:09 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05476; Fri, 7 Jan 94 15:58:09 GMT Received: from de5.ctd.ornl.gov ([128.219.128.106]) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05469; Fri, 7 Jan 94 07:58:00 PST Received: from localhost (de5@localhost) by de5.ctd.ornl.gov (8.6.4/8.6.4) id KAA22955; Fri, 7 Jan 1994 10:58:46 -0500 Date: Fri, 7 Jan 1994 10:58:46 -0500 From: Dave Sill Message-Id: <199401071558.KAA22955@de5.ctd.ornl.gov> To: majordomo-users@greatcircle.com Subject: HELP: resend bombing out Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I just moved Majordomo and a bunch of lists from a DECstation to SPARCstation, and resend is complaining that I'm not specifying both -l and -h options--when, of course, I am. I need to get this working ASAP. Here's a sample bounce message: ---------- Forwarded message ---------- Date: Fri, 7 Jan 1994 10:50:42 -0500 From: Mail Delivery Subsystem Subject: Returned mail: unknown mailer error 2 The original message was received at Fri, 7 Jan 1994 10:50:41 -0500 from 3995@de5.ctd.ornl.gov [128.219.128.106] ----- The following addresses had delivery problems ----- "|/usr/local/mail/majordomo-1.62/wrapper resend -A -a /usr/local/mail/lists/workstation-users.passwd -p list -l Workstation-Users -h MailHub.ORNL.GOV -f workstation-users-approval -s workstation-users-send" (unrecoverable error) (expanded from: ) ----- Transcript of session follows ----- resend: must specify both '-l list' and '-h host' arguments at /usr/local/mail/majordomo-1.62/resend line 41. 554 "|/usr/local/mail/majordomo-1.62/wrapper resend -A -a /usr/local/mail/lists/workstation-users.passwd -p list -l Workstation-Users -h MailHub.ORNL.GOV -f workstation-users-approval -s workstation-users-send"... unknown mailer error 2 ----- Original message follows ----- Return-Path: Received: from de5.ctd.ornl.gov by cosmail2.ctd.ornl.gov (8.6.4/1.34) id KAA14310; Fri, 7 Jan 1994 10:50:41 -0500 Received: from localhost (de5@localhost) by de5.ctd.ornl.gov (8.6.4/8.6.4) id KAA22949; Fri, 7 Jan 1994 10:50:38 -0500 Date: Fri, 7 Jan 1994 10:50:38 -0500 From: Dave Sill Message-Id: <199401071550.KAA22949@de5.ctd.ornl.gov> To: workstation-users@cosmail2.ctd.ornl.gov Subject: test blah blah blah ------- End of forwarded message ------- -- Dave Sill (de5@ornl.gov) Computers should work the way beginners Martin Marietta Energy Systems expect them to, and one day they will. Workstation Support -- Ted Nelson URL http://gatekeeper.dec.com/archive/pub/DEC/DECinfo/html/dsill.html From Majordomo-Users-Owner@GreatCircle.COM Sat Jan 8 00:38:03 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07315; Sat, 8 Jan 94 00:38:03 GMT Received: from noc4.dccs.upenn.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07308; Fri, 7 Jan 94 16:37:55 PST Received: from CCAT.SAS.UPENN.EDU by noc4.dccs.upenn.edu id AA25508; Fri, 7 Jan 94 18:06:50 -0500 Received: by ccat.sas.upenn.edu (AIX 3.2/UCB 5.64/4.03) id AA20907; Fri, 7 Jan 1994 18:06:47 -0500 From: michael@ccat.sas.upenn.edu (Michael Nenashev) Message-Id: <9401072306.AA20907@ccat.sas.upenn.edu> Subject: TZ environmental variable in wrapper.c To: majordomo-users@greatcircle.com Date: Fri, 7 Jan 1994 18:06:47 -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: 407 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I would like to add my voice to those requesting to incorporate Terry R. Coley's (terry@Pgrams.COM) patch to wrapper.c, making use of TZ variable. Since most of the mail users sort the messages by time it is not at all convenient to receive messages stamped with GMT. Besides, the patch is really simple and easy to disable if anybody prefer the original wrapper way. Michael. sysadmin@ccat.sas.upenn.edu From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 14 13:13:19 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07407; Fri, 14 Jan 94 13:13:19 GMT Received: from dino.conicit.ve by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07390; Fri, 14 Jan 94 05:12:40 PST Received: by dino.conicit.ve (4.1/SMI-4.1/RP-1.2) id AA09552; Fri, 14 Jan 1994 09:08:47 -0400 (AST) From: lem@conicit.ve (Luis Moreno CONICIT) Message-Id: <9401141308.AA09552@dino.conicit.ve> Subject: Questions..? To: majordomo-users@greatcircle.com Date: Fri, 14 Jan 1994 09:08:47 -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: 773 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi..., all users of Majordomo ...!!! Thanks in advance for your answers !!! What is the diference beetwen the request-recording y request-answer files. Where I can find documentacion's majordomo in format <> PostScript. For Example, documentacion's majordomo in ascii. Regards, I sorry, for my english ... -- 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 Tue Jan 18 00:07:35 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA25340; Tue, 18 Jan 94 00:07:35 GMT Received: from gasco.com (gasco.gasco.com) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA25332; Mon, 17 Jan 94 16:07:27 PST Received: by gasco.com (/\==/\ Smail3.1.28.1 #28.4) id ; Mon, 17 Jan 94 16:09 PST Received: by gasco.com (/\==/\ Smail3.1.28.1 #28.5) id ; Mon, 17 Jan 94 16:09 PST From: dlc@gasco.com (Paradise Cowgirl x5930) Message-Id: <9401171609.ZM3009@gasco.com> Date: Mon, 17 Jan 1994 16:09:08 -0800 Reply-To: dlc@gasco.com X-Mailer: Z-Mail (2.1.0 10/27/92) To: majordomo-users@greatcircle.com Subject: Approving when not on a private list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Situation: I'm co-owner of a list until the other (new) co-owner is fully comfortable with majordomo. I'm not on the list, which is set up to only accept posts by list members. I tried to "approve" a post to the list but it bounced saying that I was not a list member. Is there anyway around this? This is on SunOS 4.1.x, Smail3.1.28.1, majodomo v1.62, resend v1.19. Any pointers appreciated! Thanks! >>-Darci-> -- ------ Darci L. Chapman - Northwest Natural Gas - dlc@gasco.com \ --/--- Oregonians spent over $3 million on the last statewide OCA-sponsored \ \/ / anti-gay rights measure. Their measures are divisive and unnecessary. \/\ / Don't sign the OCA's latest petition! \/ (I do not speak for the Gas Company, and They do not speak for Me) From Majordomo-Users-Owner@GreatCircle.COM Tue Jan 18 10:45:57 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA29011; Tue, 18 Jan 94 18:40:31 GMT Received: from csn.org by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA29004; Tue, 18 Jan 94 10:40:20 PST Received: from stortek.stortek.com (stortek.com) by csn.org with SMTP id AA07297 (5.65c/IDA-1.4.4 for ); Tue, 18 Jan 1994 11:42:01 -0700 Received: from dcsun1.stortek.com by stortek.stortek.com with SMTP id AA10197 (5.65c/IDA-1.5 for ); Tue, 18 Jan 1994 11:41:57 -0700 Received: by dcsun1.stortek.com (4.1/SMI-4.1) id AA05587; Tue, 18 Jan 94 11:40:38 MST Date: Tue, 18 Jan 94 11:40:38 MST From: wamsley@dcsun1.stortek.com (Jim Wamsley) Message-Id: <9401181840.AA05587@dcsun1.stortek.com> To: majordomo-users@greatcircle.com Subject: Private Mailing Lists Reply-To: jim_wamsley@stortek.stortek.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Just installed Majordomo-1.62 and i must say i am impressed. However, I have a small problem. by decree here, for security reasons, all mailing lists are to be private. In testing the workings of the lists, i find that lost-owner has no ready means of identiying a message that has come from someone _not_ in the mailing list. since I have some requirements coming up that will have 50+ memebers to a closed list, i can't expect that the lost-owner will readily recognize all names in the list. can bounce be made to identify messages from people not on the list? ______________________________________________________________ [ Jim Wamsley, Postmaster, Hostmaster, Newsmaster, Ringmaster] [ StorageTek ] [ Audible: (303) 673-8163 Logical jim@stortek.com] [ Physical: 2270 S. 88th St, M.S. 4379, Louisville, CO 80028 ] [ Never appeal to a man's better judgement. ] [ He may not have any. ] [____________________________________________________________] From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 19 15:18:18 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA03179; Wed, 19 Jan 94 15:18:18 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA03172; Wed, 19 Jan 94 07:18:10 PST Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA20148 (5.65c/IDA-1.4.4 for ); Wed, 19 Jan 1994 10:19:26 -0500 Message-Id: <199401191519.AA20148@cs.umb.edu> To: jim_wamsley@stortek.stortek.com Cc: majordomo-users@greatcircle.com Subject: Re: Private Mailing Lists In-Reply-To: Your message of "Tue, 18 Jan 1994 11:40:38 MST." <9401181840.AA05587@dcsun1.stortek.com> Date: Wed, 19 Jan 1994 10:19:26 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9401181840.AA05587@dcsun1.stortek.com>, Jim Wamsley writes: > I have a small problem. by decree here, for security reasons, > all mailing lists are to be private. Private can mean three different things: 1) What majordomo refers to as closed (i.e. membership on the list by invitation only). 2) Only people on the list can post to the list. (I think this is what you mean in which case resend with the -I option should do the trick.) 3) The presence of the list shouldn't be advertized in the output of the lists command. There are patches to hide lists, but the functionality will not be in a production version until majordomo 2.0. > In testing the workings > of the lists, i find that lost-owner has no ready means of ^^^^ I assume you mean list > identiying a message that has come from someone _not_ in the > mailing list. Are you moderating these lists? If not then the only messages that should be bounced to the list maintainer (if you are using resend -I) are messages from people not on the list, or other administriva problems. > can bounce be made to identify messages from people not on the > list? I assume you mean the bounce function in resend and not the bounce(1) command. Resend already does the marking with with the -I option. The exact line is: &bounce ("Non-member submission from [$from]"); -- 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 Wed Jan 19 16:16:17 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA03306; Wed, 19 Jan 94 16:16:17 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA03299; Wed, 19 Jan 94 08:16:08 PST Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA21038 (5.65c/IDA-1.4.4 for ); Wed, 19 Jan 1994 11:17:53 -0500 Message-Id: <199401191617.AA21038@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Users of digest and majordomo please read Date: Wed, 19 Jan 1994 11:17:52 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In conjunction with a paying job, I am looking at integrating digest with the rest of the majordomo program suite. The major advantage would be that items such as the name, header and trailer text, volume and issue numbers, and the size of the digest could be set via email. These changes would use my config file code. In addition the majordomo.cf file would be used by digest. I will also keep the current code that uses a digest specific config file in place, so that digest can be used without majordomo. Here are my assumptions about the setup. If anybody has a problem with my assumptions, please let me know. The digest list may or may not have a corresponding non-digested version of the list. Digest is just a special version of resend. Resend is not being used in conjunction with the digest list. Since digest is really just a specialized version of resend, I can map the resend keywords into equivalent values in the digest code. The last item is the biggest assumption in the lot. The effect on the digest specific keywords is: (Note: config file keywords with a * after them will be overloaded between resend and digest) The keyword NAME that provides the subject line and digest banner text would be preserved and mapped to the keyword digest_name. The keyword REPLY_TO would be mapped to the reply_to* keyword. The ERRORS-TO keyword would disappear as would the FROM keyword. Their values would be specified by the sender* keyword. (Is there any reason to have ERRORS-TO and FROM be different?) The TO keyword that makes up the from line of the outgoing message would be derived from the list name (as the -l parameter to the digest command) and the value of $whereami in the majordomo config file. The REALLY-TO keyword will be specified on the command line to the digest command as the last argument to the digest command (just like resend). The HEADER keyword would be replaced by the fronter* configuration parameter which would specify the fronter text (i.e. the text at the front of the message). (There would also be a header* keyword that specifies arbitrary headers to be added to the header portion of the message.) The TRAILER keyword would be replaced by the trailer* configuration parameter which would specify thee trailer text. The INCOMING keyword would be specified by a value in the majordomo.cf file. The VOL_FILE keyword would be mapped to the digest_volume keyword, and it would show the volume number of the next digest to be created. The NUM_FILE value would be mapped to the digest_issue keyword, and it would show the issue number of the next digest to be created. The ARCHIVE value would disappear being replaced by the filedir and filedir suffix arguments in the majordomo.cf file. The HOME keyword would disappear being replaced with the $homedir variable in majordomo.cf. The DIGEST_SIZE keyword would be specified using the maxlength* keyword value. -- 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 Wed Jan 19 20:14:32 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04120; Wed, 19 Jan 94 20:14:32 GMT Received: from gasco.com (gasco.gasco.com) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04113; Wed, 19 Jan 94 12:14:25 PST Received: by gasco.com (/\==/\ Smail3.1.28.1 #28.4) id ; Wed, 19 Jan 94 12:16 PST Received: by gasco.com (/\==/\ Smail3.1.28.1 #28.5) id ; Wed, 19 Jan 94 10:13 PST From: dlc@gasco.com (Darci Chapman) Message-Id: <9401191013.ZM10404@gasco.com> Date: Wed, 19 Jan 1994 10:13:30 -0800 In-Reply-To: dlc@gasco.com (Paradise Cowgirl x5930) "Approving when not on a private list" (Jan 17, 16:09) References: <9401171609.ZM3009@gasco.com> Reply-To: dlc@gasco.com X-Mailer: Z-Mail (2.1.0 10/27/92) To: majordomo-users@GreatCircle.COM Subject: Re: Approving when not on a private list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I wrote: +Situation: + +I'm co-owner of a list until the other (new) co-owner is fully +comfortable with majordomo. I'm not on the list, which is set +up to only accept posts by list members. I tried to "approve" +a post to the list but it bounced saying that I was not a list +member. Is there anyway around this? + I have since realized that majordomo allows for multiple access lists (-I file1:file2:file3, etc) so I have merely created additional list-owner files that include my address. >>-Darci-> -- ------ Darci L. Chapman - Northwest Natural Gas - dlc@gasco.com \ --/--- Oregonians spent over $3 million on the last statewide OCA-sponsored \ \/ / anti-gay rights measure. Their measures are divisive and unnecessary. \/\ / Don't sign the OCA's latest petition! \/ (I do not speak for the Gas Company, and They do not speak for Me) From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 19 13:35:57 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04264; Wed, 19 Jan 94 21:31:25 GMT Received: from csn.org by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04257; Wed, 19 Jan 94 13:31:16 PST Received: from stortek.stortek.com (stortek.com) by csn.org with SMTP id AA17723 (5.65c/IDA-1.4.4 for ); Wed, 19 Jan 1994 14:32:57 -0700 Received: from dcsun1.stortek.com by stortek.stortek.com with SMTP id AA22722 (5.65c/IDA-1.5 for ); Wed, 19 Jan 1994 14:32:53 -0700 Received: by dcsun1.stortek.com (4.1/SMI-4.1) id AA06733; Wed, 19 Jan 94 14:32:51 MST Date: Wed, 19 Jan 94 14:32:51 MST From: wamsley@dcsun1.stortek.com (Jim Wamsley) Message-Id: <9401192132.AA06733@dcsun1.stortek.com> To: majordomo-users@greatcircle.com Subject: private mailing lists Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk first thanks to john rouillard and darci chapman for their replies to my questions about closed mailing lists. i found part of my problem here with getting the right response to message to lists from non-memebers. seems that resend wasn't finding getopts.pl. but what is peculiar is that any message sent to resend was simply forwarded to list-owner for processing with subject line Subject: BOUNCE testprivate@stortek.com: Approval required i moved getopts.pl ito the src directory, and have tried to send messages to the list both as a member and as a non-member. the perl scripts run on seemingly endlessly in the mail queue. this is what the entry in /etc/aliases looks like testprivate: "| /home/majordomo/src/wrapper resend -l testprivate \ -h stortek.com -f owner-testprivate -r testprivate -R \ -a /home/majordomo/lists/testprivate.passwd \ -I testprivate -A" owner-testprivate: LIST_OWNER testprivate-request: "|/home/majordomo/src/wrapper request-answer testprivate" testprivate-approval: LIST_OWNER i am using the getopts.pl that came with perl4.035 anyone have any ideas ______________________________________________________________ [ Jim Wamsley, Postmaster, Hostmaster, Newsmaster, Ringmaster] [ StorageTek ] [ Audible: (303) 673-8163 Logical jim@stortek.com] [ Physical: 2270 S. 88th St, M.S. 4379, Louisville, CO 80028 ] [ Never appeal to a man's better judgement. ] [ He may not have any. ] [____________________________________________________________] From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 19 15:07:10 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04633; Wed, 19 Jan 94 23:02:22 GMT Received: from uu5.psi.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04626; Wed, 19 Jan 94 15:02:09 PST Received: by uu5.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP; id AA04199 for ; Wed, 19 Jan 94 17:46:56 -0500 From: pcrossma@avid.com (Paul Crossman) Received: by avid.com (4.1/3.2.083191-Avid Technology) id AA04676; Wed, 19 Jan 94 17:41:19 EST Message-Id: <9401192241.AA04676@avid.com> Subject: need help with getting a mailinglist set up. To: majordomo-users@greatcircle.com Date: Wed, 19 Jan 1994 17:41:18 -0500 (EST) X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 2019 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi... This is my first shot a majordomo, so please bear with me... I am currently trying to set up an internet mailinglist, but I am having some problems with one of the aliases that the docs say to create. the alias is as follows; eddie-request: "|/usr/majordomo/wrapper /usr/majordomo/request-answer eddie" sending email to eddie-request yeilds the following bounce message from MAILER-DEAMON. >From MAILER-DAEMON Thu Jan 13 14:01:29 1994 >Date: Thu, 13 Jan 94 14:01:29 EST >From: MAILER-DAEMON (Mail Delivery Subsystem) >Received: by avid.com (4.1/3.2.083191-Avid Technology) > id AA27130; Thu, 13 Jan 94 14:01:29 EST >Subject: Returned mail: unknown mailer error 2 >Message-Id: <9401131901.AA27130@avid.com> >To: pcrossma >Status: RO > > ----- Transcript of session follows ----- >/usr/majordomo/wrapper: error: insecure usage >554 "|/usr/majordomo/wrapper /usr/majordomo/request-answer eddie"... unknown mailer error 2 > > ----- Unsent message follows ----- >From: pcrossma (Paul Crossman) >Received: by avid.com (4.1/3.2.083191-Avid Technology) > id AA27127; Thu, 13 Jan 94 14:01:29 EST >Message-Id: <9401131901.AA27127@avid.com> >Subject: test messag >To: eddie-request >Date: Thu, 13 Jan 1994 14:01:29 -0500 (EST) >X-Mailer: ELM [version 2.4 PL20] >Content-Type: text >Content-Length: 239 > >lkjdf;lkajdf >;lkaj;ldf > >-- >Paul Crossman "For?!? I don't work FOR Metro. Tech. Park >UNIX System Manager anybody. I'm just having 1 Park West >Avid Technology fun." - Dr. Who Tewksbury, MA 01876 >crossman@avid.com (508) 640-3147 > Can anyone help me out and tell me what's wrong??? Everthing at my site works but this. All help greatly appreciated. Thanks, Paul C. -- Paul Crossman "For?!? I don't work FOR Metro. Tech. Park UNIX System Manager anybody. I'm just having 1 Park West Avid Technology fun." - Dr. Who Tewksbury, MA 01876 crossman@avid.com (508) 640-3147 From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 19 20:44:39 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05556; Thu, 20 Jan 94 04:42:02 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05549; Wed, 19 Jan 94 20:41:37 PST Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA00483 (5.65c/IDA-1.4.4 for ); Wed, 19 Jan 1994 23:43:07 -0500 Message-Id: <199401200443.AA00483@cs.umb.edu> To: wamsley@dcsun1.stortek.com (Jim Wamsley) Cc: majordomo-users@greatcircle.com Subject: Re: private mailing lists In-Reply-To: Your message of "Wed, 19 Jan 1994 14:32:51 MST." <9401192132.AA06733@dcsun1.stortek.com> Date: Wed, 19 Jan 1994 23:43:06 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9401192132.AA06733@dcsun1.stortek.com>, Jim Wamsley writes: > i found part of my problem here with getting the right response > to message to lists from non-memebers. seems that resend wasn't finding > getopts.pl. Sounds like you may want to check the perl installation on your system. > but what is peculiar is that any message sent to > resend was simply forwarded to list-owner for processing with subject line > > Subject: BOUNCE testprivate@stortek.com: Approval required > [...] > this is what the entry in /etc/aliases looks like > > testprivate: "| /home/majordomo/src/wrapper resend -l testprivate \ > -h stortek.com -f owner-testprivate -r testprivate -R \ > -a /home/majordomo/lists/testprivate.passwd \ > -I testprivate -A" Hmm, I don't think Brent ever envisioned a restricted posted and moderated list. Looks like you have triggered a bug. The code that checks to see if the list is moderated occurs before the check for the restricted posting. I think you want to change resend so that the code that reads: if (defined($opt_A) && ! defined($approved)) { &bounce("Approval required"); } occurs after the block of code that starts: if ( defined($opt_I) && defined($from) && ! defined($approved) ) { local($infile) = 0; This should put the $opt_A code just before the definition of $sendmail_cmd. I apologize for not supplying a diff, but I am doing this from my development code, and I have hacked the code in this region a bit, so a diff would be meaningless. I claim this is the right way to order the tests, I think this is the change since both sets of test occur in straight line code (i.e. not in a loop or anything), and I don't thing there are any side effects being depended on. Comments? > i moved getopts.pl ito the src directory, and have tried to send messages > to the list both as a member and as a non-member. the perl scripts > run on seemingly endlessly in the mail queue. Hmm, it does seem that the turnaround time on the resend->sendmail loop takes a long time. What really ticks me off is that resned and perl are still running in parallel with sendmail. Can you pronounce the phrase "memory hogs" 8-). Actually, you got me here, but I claim that your perl installtion is suspect since it can't find getopt.pl. Perl really should be able to search its compiled in include file path. -- 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 Jan 20 15:26:57 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07255; Thu, 20 Jan 94 15:26:57 GMT Received: from uu5.psi.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07248; Thu, 20 Jan 94 07:26:26 PST Received: by uu5.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP; id AA11869 for ; Thu, 20 Jan 94 10:13:11 -0500 From: pcrossma@avid.com (Paul Crossman) Received: by avid.com (4.1/3.2.083191-Avid Technology) id AA11042; Thu, 20 Jan 94 10:07:29 EST Message-Id: <9401201507.AA11042@avid.com> Subject: Re: need help with getting a mailinglist set up. To: rogerk@queernet.org Date: Thu, 20 Jan 1994 10:07:29 -0500 (EST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "rogerk@queernet.org" at Jan 19, 94 06:30:54 pm X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 463 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >Wrapper is restricted to executing stuff in the Majordomo directory, and does >not allow a path... so it should be > > eddie-request: "|/usr/majordomo/wrapper request-answer eddie" Thanks to everyone that responded!!! This one worked. Paul C. -- Paul Crossman "For?!? I don't work FOR Metro. Tech. Park UNIX System Manager anybody. I'm just having 1 Park West Avid Technology fun." - Dr. Who Tewksbury, MA 01876 crossman@avid.com (508) 640-3147 From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 20 18:12:48 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07894; Thu, 20 Jan 94 18:12:48 GMT Received: from gasco.com (gasco.gasco.com) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07887; Thu, 20 Jan 94 10:12:38 PST Received: by gasco.com (/\==/\ Smail3.1.28.1 #28.4) id ; Thu, 20 Jan 94 10:14 PST Received: by gasco.com (/\==/\ Smail3.1.28.1 #28.5) id ; Thu, 20 Jan 94 10:14 PST From: dlc@gasco.com (Darci Chapman, Paradise Cowgirl x5930) Message-Id: <9401201014.ZM13581@gasco.com> Date: Thu, 20 Jan 1994 10:14:24 -0800 Reply-To: dlc@gasco.com X-Mailer: Z-Mail (2.1.0 10/27/92) To: majordomo-users@greatcircle.com Subject: private lists again Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Well, two steps forward and one step backward :-) I'm the one that wants to be able to approve submissions to private lists that I am not subscribed to. I have since implemented multiple 'approved' files where my address is included. However, this does not allow me to do 'who' and 'which' commands on these lists. Any suggestions for work arounds or am I missing something equally obvious as last time? :-) Also, where can I get patches for majordomo that allow for "hidden lists"? >>-Darci-> -- ------ Darci L. Chapman - Northwest Natural Gas - dlc@gasco.com \ --/--- Oregonians spent over $3 million on the last statewide OCA-sponsored \ \/ / anti-gay rights measure. Their measures are divisive and unnecessary. \/\ / Don't sign the OCA's latest petition! \/ (I do not speak for the Gas Company, and They do not speak for Me) From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 21 12:14:53 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA14485; Fri, 21 Jan 94 20:10:00 GMT Received: from csn.org by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA14469; Fri, 21 Jan 94 12:09:48 PST Received: from stortek.stortek.com (stortek.com) by csn.org with SMTP id AA22648 (5.65c/IDA-1.4.4 for ); Fri, 21 Jan 1994 13:11:29 -0700 Received: from dcsun1.stortek.com by stortek.stortek.com with SMTP id AA03564 (5.65c/IDA-1.5 for ); Fri, 21 Jan 1994 13:11:20 -0700 Received: by dcsun1.stortek.com (4.1/SMI-4.1) id AA08135; Fri, 21 Jan 94 13:11:12 MST Date: Fri, 21 Jan 94 13:11:12 MST From: wamsley@dcsun1.stortek.com (Jim Wamsley) Message-Id: <9401212011.AA08135@dcsun1.stortek.com> To: majordomo-users@greatcircle.com Subject: private mailing lists Reply-To: jim_wamsley@stortek.stortek.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk a couple of days ago i posted a question concerning private amiling lists. specifically, i needed a mailing list not only where the owner had to approve all postings, but that non-members could not post to. i couldn't ge the non-members part to work. well john rouillard suggested that maybe brent hadn't considered that both functions might be wanted together. john also suggested that if i hacked the code for resend so that the non-member tests came before the approved tests, that i might be able to accomplish what i wanted. well, i'm not must of a hacker. i tried to move the non-memeber test, but don't know is i messed up the syntax or what, but with the hacked code, non-member submissions bomb to the mailer- deamon with unknown mailer error 5. i would really like to have this feature. what is the right way to hack this? ______________________________________________________________ [ Jim Wamsley, Postmaster, Hostmaster, Newsmaster, Ringmaster] [ StorageTek ] [ Audible: (303) 673-8163 Logical jim@stortek.com] [ Physical: 2270 S. 88th St, M.S. 4379, Louisville, CO 80028 ] [ Never appeal to a man's better judgement. ] [ He may not have any. ] [____________________________________________________________] From Majordomo-Users-Owner@GreatCircle.COM Mon Jan 24 10:17:36 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA00823; Mon, 24 Jan 94 18:08:29 GMT Received: from world.std.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA00816; Mon, 24 Jan 94 10:08:19 PST Received: by world.std.com (5.65c/Spike-2.0) id AA02061; Mon, 24 Jan 1994 13:10:09 -0500 Message-Id: <199401241810.AA02061@world.std.com> To: Majordomo-users@GreatCircle.COM Subject: One list overwrittes another? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Date: Mon, 24 Jan 1994 13:10:08 -0500 From: Joe Ilacqua Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I put up Majordomo 1.62 about to weeks ago and there are now about 60 lists running under it. Twice now a list as been overwritten with the addresses of a different list. Is this a known problem? Is there a fix? ->Spike From Majordomo-Users-Owner@GreatCircle.COM Mon Jan 24 19:24:39 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01489; Mon, 24 Jan 94 19:24:39 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01471; Mon, 24 Jan 94 11:23:04 PST Message-Id: <9401241923.AA01471@mycroft.GreatCircle.COM> To: Joe Ilacqua Cc: Majordomo-users@GreatCircle.COM Subject: Re: One list overwrittes another? In-Reply-To: Your message of Mon, 24 Jan 1994 13:10:08 -0500 Date: Mon, 24 Jan 1994 11:23:02 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Joe Ilacqua writes: # # I put up Majordomo 1.62 about to weeks ago and there are now # about 60 lists running under it. Twice now a list as been overwritten # with the addresses of a different list. Is this a known problem? Is # there a fix? # # ->Spike Are you accessing the files via NFS? I'm not sure the locking works right in that case. Regardless, try these patches to majordomo.pl... *** /tmp/T0a01465 Mon Jan 24 11:22:45 1994 --- majordomo.pl Sat Dec 4 15:01:49 1993 *************** *** 1,12 **** # General subroutines for Majordomo # $Source: /mycroft/brent/majordomo/RCS/majordomo.pl,v $ ! # $Revision: 1.20 $ ! # $Date: 1993/08/31 00:36:46 $ # $Author: brent $ # $State: Exp $ # ! # $Header: /mycroft/brent/majordomo/RCS/majordomo.pl,v 1.20 1993/08/31 00:36:46 brent Exp $ # # $Locker: $ # --- 1,12 ---- # General subroutines for Majordomo # $Source: /mycroft/brent/majordomo/RCS/majordomo.pl,v $ ! # $Revision: 1.22 $ ! # $Date: 1993/12/04 23:01:31 $ # $Author: brent $ # $State: Exp $ # ! # $Header: /mycroft/brent/majordomo/RCS/majordomo.pl,v 1.22 1993/12/04 23:01:31 brent Exp $ # # $Locker: $ # *************** *** 374,379 **** --- 374,381 ---- local($listdir) = shift; local($clean_list) = shift; local($matches); + local(*LIST); + local($_); open(LIST, "$listdir/$clean_list") || &main'abort("Can't read $listdir/$clean_list: $!"); From Majordomo-Users-Owner@GreatCircle.COM Mon Jan 24 22:49:43 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA03698; Mon, 24 Jan 94 22:49:43 GMT Received: from world.std.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA03691; Mon, 24 Jan 94 14:49:27 PST Received: by world.std.com (5.65c/Spike-2.0) id AA19145; Mon, 24 Jan 1994 17:51:19 -0500 Message-Id: <199401242251.AA19145@world.std.com> To: Brent Chapman Cc: Majordomo-users@GreatCircle.COM Subject: Re: One list overwrittes another? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Date: Mon, 24 Jan 1994 17:51:19 -0500 From: Joe Ilacqua Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Spike From Majordomo-Users-Owner@GreatCircle.COM Tue Jan 25 14:25:38 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11134; Tue, 25 Jan 94 14:25:38 GMT Received: from trantor.harris-atd.com (v3a.ess.harris.com) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11127; Tue, 25 Jan 94 06:25:29 PST Received: from melmac.harris-atd.com by trantor.harris-atd.com (4.1/1.14) id AA07516; Tue, 25 Jan 94 09:27:21 EST Message-Id: <9401251427.AA07516@trantor.harris-atd.com> Received: by melmac.harris-atd.com (5.0/SMI-SVR4) id AA27395; Tue, 25 Jan 1994 09:27:21 +0500 Date: Tue, 25 Jan 1994 09:27:21 +0500 From: chuck@trantor.harris-atd.com (Chuck Musciano) To: majordomo-users@greatcircle.com Subject: Majordomo under Solaris 2.3? X-Sun-Charset: US-ASCII Content-Length: 962 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I hadbeen running MajorDomo under Solaris 2.2, and just upgraded to 2.3. My lists promptly began bouncing mail, and I traced it to the fact that resend was calling sendmail thusly: sendmail 10000 -f The -f option is correct, of course, but it seems that resend is picking up the value of the -M option (max message size) and using it for the -m option (other sendmail options). I removed the -M option from the mail aliases for my lists, and all seems to be well again. Has anyone else seen this? Is there odd difference in how Perl manages options under 2.3 versus 2.2? Note that I'm running the same binary of perl; only the OS has changed. Chuck Musciano ARPA: chuck@trantor.harris-atd.com Harris Corporation AOL : CMusciano PO Box 37, MS 16/1912 AT&T: (407) 727-6131 Melbourne, FL 32902 Fax : (407) 729-3363 A good newspaper is never good enough, but a lousy newspaper is a joy forever. -- Garrison Keillor From Majordomo-Users-Owner@GreatCircle.COM Tue Jan 25 16:02:56 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11659; Tue, 25 Jan 94 16:02:56 GMT Received: from trantor.harris-atd.com (v3a.ess.harris.com) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11645; Tue, 25 Jan 94 08:02:48 PST Received: from melmac.harris-atd.com by trantor.harris-atd.com (4.1/1.14) id AA07701; Tue, 25 Jan 94 11:04:30 EST Message-Id: <9401251604.AA07701@trantor.harris-atd.com> Received: by melmac.harris-atd.com (5.0/SMI-SVR4) id AA27535; Tue, 25 Jan 1994 11:04:30 +0500 Date: Tue, 25 Jan 1994 11:04:30 +0500 From: chuck@trantor.harris-atd.com (Chuck Musciano) To: majordomo-users@greatcircle.com Subject: From: gets re-written? X-Sun-Charset: US-ASCII Content-Length: 668 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Running under Solaris 2.3... Messages sent to a mailing list are being sent out with the From: field rewritten. Specifically, I send in a message. My address is chuck@melmac (Chuck Musciano) When resend gets through with things, the From: field has daemon@su102w (Chuck Musciano) when the posting goes out. ("su102w" is the machine running MajorDomo). How did my name get retained, but the address get changed? The value that resend places in the Sedner: field is oo-owner@su102w, and "oo" is the correct name of the list. Any help is appreciated. I'm fairly new to all this mailer stuff, and I'm trying to get up to speed. Chuck Musciano From Majordomo-Users-Owner@GreatCircle.COM Tue Jan 25 08:56:48 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11936; Tue, 25 Jan 94 16:39:35 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11900; Tue, 25 Jan 94 08:38:03 PST Message-Id: <9401251638.AA11900@mycroft.GreatCircle.COM> To: chuck@trantor.harris-atd.com (Chuck Musciano) Cc: majordomo-users@greatcircle.com Subject: Re: Majordomo under Solaris 2.3? In-Reply-To: Your message of Tue, 25 Jan 1994 09:27:21 +0500 Date: Tue, 25 Jan 1994 08:38:01 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk chuck@trantor.harris-atd.com (Chuck Musciano) writes: # I hadbeen running MajorDomo under Solaris 2.2, and just upgraded to # 2.3. My lists promptly began bouncing mail, and I traced it to the fact # that resend was calling sendmail thusly: # # sendmail 10000 -f # # The -f option is correct, of course, but it seems that resend is picking # up the value of the -M option (max message size) and using it for the -m # option (other sendmail options). I removed the -M option from the mail # aliases for my lists, and all seems to be well again. # # Has anyone else seen this? Is there odd difference in how Perl manages # options under 2.3 versus 2.2? Note that I'm running the same binary of perl; # only the OS has changed. It's not perl, it's sendmail. Your messages under 2.3 are apparently getting queued by sendmail before processing. When sendmail queues a message, it smashes the "destination address" (in this case, the program and arguments) to all-lower-case when writing the queue file. Two workarounds: you can either put all the resend arguments in a file, then reference the file with the "@/path/to/resend/args/file" argument to resend (make sure the path name is all-lower-case), or you can find and change the mailer flag on sendmail that causes the case smashing. -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 Tue Jan 25 19:10:21 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA00813; Tue, 25 Jan 94 19:10:21 GMT Received: from inlet.cis.ufl.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA00806; Tue, 25 Jan 94 11:10:13 PST Received: from localhost by inlet.cis.ufl.edu (8.6.4/4.11) id OAA03272; Tue, 25 Jan 1994 14:12:02 -0500 Message-Id: <199401251912.OAA03272@inlet.cis.ufl.edu> To: majordomo-users@greatcircle.com Subject: New installation Date: Tue, 25 Jan 1994 14:12:01 EST From: Stephen P Potter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Well, after installing Majordomo three times on three different machines, our admin finally decided where he wanted me to put it. ;) Now, I've only got one problem with it. It's running really slowly. It takes like 15-20 minutes to process a request through majordomo, including adding, removing, archiving, etc. Is there some way to speed this up, or did I do something extremely wrong? Steve From Majordomo-Users-Owner@GreatCircle.COM Tue Jan 25 22:07:54 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01870; Tue, 25 Jan 94 22:07:54 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01850; Tue, 25 Jan 94 14:06:55 PST Message-Id: <9401252206.AA01850@mycroft.GreatCircle.COM> To: Stephen P Potter Cc: majordomo-users@greatcircle.com Subject: Re: New installation In-Reply-To: Your message of Tue, 25 Jan 1994 14:12:01 EST Date: Tue, 25 Jan 1994 14:06:53 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Stephen P Potter writes: # Well, after installing Majordomo three times on three different machines, # our admin finally decided where he wanted me to put it. ;) Now, I've only # got one problem with it. # # It's running really slowly. It takes like 15-20 minutes to process a # request through majordomo, including adding, removing, archiving, etc. # # Is there some way to speed this up, or did I do something extremely wrong? # # Steve Usually this is a symptom that Sendmail (or whatever mailer you're using) is queuing the messages as they come in, then handing them to Majordomo later as part of a normal queue run, instead of processing them immediately. -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 Tue Jan 25 22:27:11 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA02132; Tue, 25 Jan 94 22:27:11 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA02114; Tue, 25 Jan 94 14:25:48 PST Message-Id: <9401252225.AA02114@mycroft.GreatCircle.COM> To: chuck@trantor.harris-atd.com (Chuck Musciano) Cc: majordomo-users@greatcircle.com Subject: Re: From: gets re-written? In-Reply-To: Your message of Tue, 25 Jan 1994 11:04:30 +0500 Date: Tue, 25 Jan 1994 14:25:46 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk chuck@trantor.harris-atd.com (Chuck Musciano) writes: # Running under Solaris 2.3... # # Messages sent to a mailing list are being sent out with the From: # field rewritten. Specifically, I send in a message. My address is # # chuck@melmac (Chuck Musciano) # # When resend gets through with things, the From: field has # # daemon@su102w (Chuck Musciano) # # when the posting goes out. ("su102w" is the machine running MajorDomo). # How did my name get retained, but the address get changed? The value # that resend places in the Sedner: field is oo-owner@su102w, and "oo" is # the correct name of the list. Oooh, nasty... Try running a test message by hand through "resend" with the "-d" (debug) flag in addition to all your normal flags. This will cause "resend" to tell you exactly what it's going to do, and show you the message as it will hand it to sendmail. If the "From:" line is correct there (and I suspect it will be), then Sendmail is doing something disgusting to it after resend hands it off. It _might_ be possible to solve the problem by naming whatever user you run "wrapper" setuid to as a "trusted user" in your sendmail.cf file. For instance, if you run "wrapper" setuid to "major", add a line "Tmajor" to your sendmail.cf file, along with all the other "T*" lines. -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 Jan 26 08:32:19 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04573; Wed, 26 Jan 94 08:32:19 GMT Received: from guardian.apple.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04566; Wed, 26 Jan 94 00:32:10 PST Received: from federal-excess.apple.com by guardian.apple.com with SMTP (5.65/8-Oct-1993-eef) id AA24684; Wed, 26 Jan 94 00:33:49 -0800 Received: from newton.apple.com by federal-excess.apple.com with SMTP (5.64/26-Sep-1993-eef) id AA20068; Wed, 26 Jan 94 00:35:13 PST for majordomo-users@GreatCircle.COM Received: from [17.201.242.92] (newhaven7.apple.com) by newton.apple.com (4.1/SMI-4.1) id AA10986; Wed, 26 Jan 94 00:33:40 PST Message-Id: <9401260833.AA10986@newton.apple.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Jan 1994 00:33:54 -0800 To: majordomo-users@GreatCircle.COM From: ting@newton.apple.com (Jeffrey Ting) Subject: Minor Bug Report/Fix Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I don't know whether this has been reported before or not, but here goes: Majordomo version: 1.62 majordomo file header: # majordomo: a person who speaks, makes arrangements, or takes charge # for another. # # Copyright 1992, D. Brent Chapman. All Rights Reserved. For use by # permission only. # # $Source: /mycroft/brent/majordomo/RCS/majordomo,v $ # $Revision: 1.51 $ # $Date: 1993/10/17 23:46:57 $ # $Author: brent $ # $State: Exp $ # # $Locker: $ Bug: If you have a private list which you are a member of and you do a which, majordomo will not list you as a member of that group. Fix: # diff majordomo.old majordomo 369c369 < && (! &is_list_member($reply_to, $listdir, $clean_list))) { --- > && (! &is_list_member($reply_to, "$listdir/$list", >$clean_list))) { That seemed to do the trick....... -Jeff. _________________________________________________________________ Jeff Ting AppleLink: TING Apple Computer, Inc. Internet: ting@newton.apple.com 20525 Mariani Avenue MS 305-3D Phone: (408) 974-6475 Cupertino, CA 95014 Fax: (408) 862-7868 _________________________________________________________________ From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 26 13:11:38 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05780; Wed, 26 Jan 94 13:11:38 GMT Received: from ac.dal.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05773; Wed, 26 Jan 94 05:11:28 PST Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01H84SZQKJJ4006OS8@AC.DAL.CA>; Wed, 26 Jan 1994 09:13:08 -0400 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:majordomo-users@GreatCircle.COM id AA06164; Wed, 26 Jan 94 09:13:05 -0400 Date: Wed, 26 Jan 1994 09:13:04 -0400 (AST) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Sendmail queues? To: majordomo-users@GreatCircle.COM Message-Id: <9401261313.AA06164@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: 614 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Brent recently wrote: ># It's running really slowly. It takes like 15-20 minutes to process a ># request through majordomo, including adding, removing, archiving, etc. > >Usually this is a symptom that Sendmail (or whatever mailer you're >using) is queuing the messages as they come in, then handing them to >Majordomo later as part of a normal queue run, instead of processing >them immediately. But why would sendmail be much slower on majordomo requests than on other activities? Mail usually gets through in at most a minute or two on my machine, but majordomo requests can easily take half an hour. Bill From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 26 17:29:38 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA06908; Wed, 26 Jan 94 17:29:38 GMT Received: from guardian.apple.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA06901; Wed, 26 Jan 94 09:29:20 PST Received: from federal-excess.apple.com by guardian.apple.com with SMTP (5.65/8-Oct-1993-eef) id AA05888; Wed, 26 Jan 94 09:30:57 -0800 Received: from newton.apple.com by federal-excess.apple.com with SMTP (5.64/26-Sep-1993-eef) id AA27222; Wed, 26 Jan 94 09:32:24 PST for majordomo-users@GreatCircle.COM Received: from [17.205.12.64] (ting-jeff.apple.com) by newton.apple.com (4.1/SMI-4.1) id AA18924; Wed, 26 Jan 94 09:30:53 PST Message-Id: <9401261730.AA18924@newton.apple.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Jan 1994 09:30:55 -0800 To: majordomo-users@GreatCircle.COM From: ting@newton.apple.com (Jeffrey Ting) Subject: Ignore Minor Bug Report/Fix - Bonehead in Action Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Sorry all. I goofed. -Major Bonehead _________________________________________________________________ Jeff Ting AppleLink: TING Apple Computer, Inc. Internet: ting@newton.apple.com 20525 Mariani Avenue MS 305-3D Phone: (408) 974-6475 Cupertino, CA 95014 Fax: (408) 862-7868 _________________________________________________________________ From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 26 10:30:58 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07074; Wed, 26 Jan 94 18:02:46 GMT Received: from orca.es.com (ES.COM) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07061; Wed, 26 Jan 94 10:02:36 PST Received: from slack ([130.187.198.23]) by orca.es.com (4.1/SMI-4.1) id AA13316; Wed, 26 Jan 94 11:03:40 MST Received: by slack (4.1/E&S_client-ver1.5/SMI-4.1) id AA08093; Wed, 26 Jan 94 11:03:50 MST From: pashdown@slack.sim.es.com (Pete Ashdown) Message-Id: <9401261803.AA08093@slack> Subject: Problems with Majordomo To: Majordomo-Users@GreatCircle.COM Date: Wed, 26 Jan 1994 11:03:49 -0700 (MST) X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 444 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am having two problems with Majordomo right now. If anyone can be of assistance, please mail me back. 1. Binary files are not being uuencoded for "get" commands. Instead, it is reading them directly into the message. 2. Files under a symbolic link are not seen by the "get" command. You can do an "index" of this directory with no problem, but if you try a "get" of any of the files, it will state they do not exist. Thanks in advance. From Majordomo-Users-Owner@GreatCircle.COM Wed Jan 26 19:22:10 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07325; Wed, 26 Jan 94 19:22:10 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07318; Wed, 26 Jan 94 11:22:00 PST Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA27044 (5.65c/IDA-1.4.4 for ); Wed, 26 Jan 1994 14:23:51 -0500 Message-Id: <199401261923.AA27044@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Digest alias queries Date: Wed, 26 Jan 1994 14:23:50 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The example aliases provided with digest look like (unecessary elements stripped): firewalls-digestify: "|/usr/local/mail/majordomo/wrapper digest -r -c /usr/local/mail/digest/firewalls-digest.cf" firewalls-digest-send: "|/usr/local/mail/majordomo/wrapper resend -p bulk -l Firewalls-Digest -f Firewalls-Digest-Owner -h GreatCircle.COM -s firewalls-digest-outgoing" firewalls-digest-outgoing: :include:/usr/local/mail/lists/firewalls-digest Why use resend when sending out a digest? It looks like digest will compose all of the headers etc properly without the need to run resend at all. I.E. all of the rewriting of resend is already embodied in digest, so why have resend in the loop at all. It looks like the example aliases slice may have been a historical setup before digest got enough smarts to set the To:, and Precedence:, and Reply-to: headers. The reason I bring this up, is that I am working on integrating digest into the majordomo package wrt the configuration file modifications. It would make life a lot easier if digest was able to be run without using resend at all. Then I would be able to use items like: trailer_text, precedence, reply-to for digest, if digest was being used as the output filter, or resend if resend was used as the output filter. -- 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 Wed Jan 26 22:15:14 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA08011; Wed, 26 Jan 94 22:15:14 GMT Received: from world.std.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA08003; Wed, 26 Jan 94 14:15:06 PST Received: by world.std.com (5.65c/Spike-2.0) id AA29494; Wed, 26 Jan 1994 17:16:56 -0500 Date: Wed, 26 Jan 1994 17:16:56 -0500 (EST) From: "Richard L. Lunn" Subject: Automatic Digests & Majordomo To: Majordomo-Users@GreatCircle.COM In-Reply-To: <9401250447.AA07343@mycroft.GreatCircle.COM> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have an established list using majordomo, and would like to create a separate Digested list that would automaticlly create and send a digest of the previous days messages to users who prefer it this way. This especially applies to those subscribers on CompuServe who are charged for all inbound internet messages. Can anyone point me in the right direction (software, hints, etc.) on how to do this. I've noticed a number of lists using majordomo offer digested versions. I posted a message the other day on the list-managers list, and the only reply I received was from someone asking me to let him know what I find. I suspect there are people interested in doing this besides me. Thank you. -- Regards, >>Dick<< From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 27 03:29:55 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09110; Thu, 27 Jan 94 03:29:55 GMT Received: from uhura.cc.rochester.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09103; Wed, 26 Jan 94 19:29:45 PST Received: from localhost (jh013a@localhost) by uhura.cc.rochester.edu (8.6.4/8.6.4) id WAA10403 for Majordomo-Users@GreatCircle.COM; Wed, 26 Jan 1994 22:31:29 -0500 From: Jonathan Hurwitz Message-Id: <199401270331.WAA10403@uhura.cc.rochester.edu> Subject: majordomo 1.62 docs/info To: Majordomo-Users@GreatCircle.COM Date: Wed, 26 Jan 1994 22:31:27 -0500 (EST) X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 174 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am looking for some _detailed_ docs/info on installing, customizing, etc majordomo 1.62 on to SunOs 4.1.3 any help, suggestions appreciated jh013a@uhura.cc.rochester.edu From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 27 03:34:55 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09152; Thu, 27 Jan 94 03:34:55 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09140; Wed, 26 Jan 94 19:33:02 PST Message-Id: <9401270333.AA09140@mycroft.GreatCircle.COM> To: "Richard L. Lunn" Cc: Majordomo-Users@GreatCircle.COM Subject: Re: Automatic Digests & Majordomo In-Reply-To: Your message of Wed, 26 Jan 1994 17:16:56 -0500 (EST) Date: Wed, 26 Jan 1994 19:33:01 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Richard L. Lunn" writes: # I have an established list using majordomo, and would like to # create a separate Digested list that would automaticlly create and send # a digest of the previous days messages to users who prefer it this way. # This especially applies to those subscribers on CompuServe who are # charged for all inbound internet messages. # # Can anyone point me in the right direction (software, hints, # etc.) on how to do this. I've noticed a number of lists using majordomo # offer digested versions. # # I posted a message the other day on the list-managers list, and # the only reply I received was from someone asking me to let him know what # I find. I suspect there are people interested in doing this besides me. # # Thank you. # -- # Regards, # >>Dick<< I have a digest package available for anonymous FTP from FTP.GreatCircle.COM, file pub/list-managers/tools/digest.shar. This is the package I use to produce (for instance) the Firewalls-Digest version of the Firewalls mailing list and the List-Managers-Digest version of the List-Managers mailing list. It doesn't require Majordomo, but it integrates pretty cleanly with it. -Brent -- Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 Mountain View, CA 94041 From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 27 03:36:51 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09193; Thu, 27 Jan 94 03:36:51 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09158; Wed, 26 Jan 94 19:35:09 PST Message-Id: <9401270335.AA09158@mycroft.GreatCircle.COM> To: "John P. Rouillard" Cc: majordomo-users@greatcircle.com Subject: Re: Digest alias queries In-Reply-To: Your message of Wed, 26 Jan 1994 14:23:50 -0500 Date: Wed, 26 Jan 1994 19:35:07 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "John P. Rouillard" writes: # # The example aliases provided with digest look like (unecessary # elements stripped): # # firewalls-digestify: "|/usr/local/mail/majordomo/wrapper digest -r -c /usr/lo # cal/mail/digest/firewalls-digest.cf" # firewalls-digest-send: "|/usr/local/mail/majordomo/wrapper resend -p bulk -l # Firewalls-Digest -f Firewalls-Digest-Owner -h GreatCircle.COM -s firewalls-di # gest-outgoing" # firewalls-digest-outgoing: :include:/usr/local/mail/lists/firewalls-digest # # # Why use resend when sending out a digest? It looks like digest will # compose all of the headers etc properly without the need to run resend # at all. I.E. all of the rewriting of resend is already embodied in # digest, so why have resend in the loop at all. General principles. I had more faith in "resend" being able to get all the header hacking right than "digest". # It looks like the example aliases slice may have been a historical # setup before digest got enough smarts to set the To:, and Precedence:, # and Reply-to: headers. That, too. -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 Thu Jan 27 03:48:40 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09328; Thu, 27 Jan 94 03:48:40 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA09297; Wed, 26 Jan 94 19:45:44 PST Message-Id: <9401270345.AA09297@mycroft.GreatCircle.COM> To: pashdown@slack.sim.es.com (Pete Ashdown) Cc: Majordomo-Users@GreatCircle.COM Subject: Re: Problems with Majordomo In-Reply-To: Your message of Wed, 26 Jan 1994 11:03:49 -0700 (MST) Date: Wed, 26 Jan 1994 19:45:43 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk pashdown@slack.sim.es.com (Pete Ashdown) writes: # I am having two problems with Majordomo right now. If anyone can be of # assistance, please mail me back. # # 1. Binary files are not being uuencoded for "get" commands. Instead, it is # reading them directly into the message. This was overlooked in the rush to get the "get/index" code out the door. Basicly, you need to add code like "if (-B file) { uuencode_file }" to the "do_get" subroutine. # 2. Files under a symbolic link are not seen by the "get" command. You can do # an "index" of this directory with no problem, but if you try a "get" of any o # f # the files, it will state they do not exist. I can't reproduce this problem; it works fine for me. Most of the archives accessible via "Majordomo@GreatCircle.COM" (such as the Firewalls archive) are actually symlinks to other directories on my system, and I don't have this problem. -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 Thu Jan 27 14:14:33 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11863; Thu, 27 Jan 94 14:14:33 GMT Received: from CUTL.City.UniSA.edu.au by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA11855; Thu, 27 Jan 94 06:14:23 PST Received: from localhost (deraad@localhost) by CUTL.City.UniSA.edu.au (8.3/8.3) id AAA02694; Fri, 28 Jan 1994 00:48:03 +1030 Message-Id: <199401271418.AAA02694@CUTL.City.UniSA.edu.au> Subject: Hello all.... To: majordomo-users@greatcircle.com Date: Fri, 28 Jan 1994 00:48:02 +1030 (CST) From: Mark.deRaad@UniSA.edu.au (Mark W. de Raad) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 567 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Im new to Majordomo, so please forgive me if this is a silly question, but I was wondering how do I set up archiving of received articles? There is a huge line in the sample.alias file, and I presume that this has got something to do with it, but I wish that it could be explained to me in a clearer manner? Any help is appreciated. Cheers, Mark -- Mark W. de Raad. CWIS Project Officer, Centre for University Teaching and Learning, University of South Australia, Adelaide, South Australia. Telephone: (08) 302 2071 'Life just wouldnt be any fun without BSD' From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 27 15:44:42 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12197; Thu, 27 Jan 94 15:44:42 GMT Received: from ac.dal.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12190; Thu, 27 Jan 94 07:44:29 PST Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01H86CF5CWHS007A3D@AC.DAL.CA>; Thu, 27 Jan 1994 11:39:59 -0400 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA17124; Thu, 27 Jan 94 11:39:47 -0400 Date: Thu, 27 Jan 1994 11:39:45 -0400 (AST) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Slowness of Majordomo To: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-Id: <9401271539.AA17124@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: 1287 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am carrying out a curious experiment that backs up my earlier messages about major delays in processing Majordomo requests. Due to the difficulties in running a fairly active list and the number of bounced subscription requests, the person for whom I set up the list moved it to another server and copied over the subscription file. But since subscriptions were still coming in to my server, I needed to keep the new subscriptions to forward. Of course the simplest thing to do would have been simply to delete the 160 entries he copied over, but as a test of majordomo I did the following; I took the list from the new server and edited it into a series of lines of the form: approve PASSWORD unsubscribe ListName user@address and submitted a file with 160 commands to majordomo. This message is being processed at the rate of about two commands per hour. It should take about three days for all 160 users to be unsubscribed! I have no idea what is causing the slowdown. The system is SGI running IRIX 4.0.5, Majordomo v. 1.62, perl 4.036. Any ideas? Bill -- 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 Thu Jan 27 15:59:04 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12242; Thu, 27 Jan 94 15:59:04 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12235; Thu, 27 Jan 94 07:58:55 PST Received: by interlock.ans.net id AA13067 (InterLock SMTP Gateway 1.1 for Majordomo-Users@greatcircle.com); Thu, 27 Jan 1994 11:00:34 -0500 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 27 Jan 1994 11:00:34 -0500 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 27 Jan 1994 11:00:34 -0500 From: Dan Simoes Message-Id: <199401271559.AA63494@foo.ans.net> Subject: Re: Slowness of Majordomo To: bill@biome.bio.dfo.ca (Bill Silvert) Date: Thu, 27 Jan 1994 10:59:33 -0500 (EST) Cc: Majordomo-Users@greatcircle.com In-Reply-To: <9401271539.AA17124@biome.bio.ns.ca> from "Bill Silvert" at Jan 27, 94 11:39:45 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 428 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I don't know about SGI, but on my Linux box it was taking almost an hour to process commands with only 4Mb on a 386DX25. Adding another 8Mb cut times substantially, but I'm not relying on it anymore, so I haven't run any real tests. perl is a memory hog, no doubt about it. | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 27 16:01:37 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12278; Thu, 27 Jan 94 16:01:37 GMT Received: from schooner.cis.ufl.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12271; Thu, 27 Jan 94 08:01:28 PST Received: from localhost by schooner.cis.ufl.edu (8.6.4/4.11) id LAA28007; Thu, 27 Jan 1994 11:04:14 -0500 Message-Id: <199401271604.LAA28007@schooner.cis.ufl.edu> To: bill@biome.bio.dfo.ca (Bill Silvert) Cc: majordomo-users@greatcircle.com Subject: Re: Slowness of Majordomo In-Reply-To: Some random ramblings on Thu, 27 Jan 1994 11:39:45 -0400. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Thu, 27 Jan 1994 11:04:13 EST From: Stephen P Potter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused bill@biome.bio.dfo.ca (Bill Silvert) to write: | | This message is being processed at the rate of about two commands per | hour. It should take about three days for all 160 users to be | unsubscribed! | One thing I did find out about my slowdown is that the directory where the log file was being written didn't have the proper permissions. (Majordomo wasn't reporting that at the time). Once I figured that out, things started to speed up. Now, requests are almost instantanious. Steve From Majordomo-Users-Owner@GreatCircle.COM Thu Jan 27 08:24:16 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12410; Thu, 27 Jan 94 16:13:16 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12403; Thu, 27 Jan 94 08:13:05 PST Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA28147; Thu, 27 Jan 94 08:04:16 PST Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0pPYr8-0002ZEC; Thu, 27 Jan 94 07:42 PST Message-Id: From: Alan Millar Subject: Re: Problems with Majordomo To: brent@GreatCircle.COM (Brent Chapman) Date: Thu, 27 Jan 1994 07:42:05 -0800 (PST) Cc: pashdown@slack.sim.es.com, Majordomo-Users@GreatCircle.COM In-Reply-To: <9401270345.AA09297@mycroft.GreatCircle.COM> from "Brent Chapman" at Jan 26, 94 07:45: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: 900 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Brent Chapman spake of these matters: > > pashdown@slack.sim.es.com (Pete Ashdown) writes: > > # I am having two problems with Majordomo right now. If anyone can be of > # assistance, please mail me back. > # > # 1. Binary files are not being uuencoded for "get" commands. Instead, it is > # reading them directly into the message. > > This was overlooked in the rush to get the "get/index" code out the > door. Basicly, you need to add code like "if (-B file) { > uuencode_file }" to the "do_get" subroutine. Or, install FTPMail and enable the option to use it instead. - 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 Thu Jan 27 08:42:28 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12686; Thu, 27 Jan 94 16:32:50 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12649; Thu, 27 Jan 94 08:31:56 PST Message-Id: <9401271631.AA12649@mycroft.GreatCircle.COM> To: Mark.deRaad@UniSA.edu.au (Mark W. de Raad) Cc: majordomo-users@greatcircle.com Subject: Re: Hello all.... In-Reply-To: Your message of Fri, 28 Jan 1994 00:48:02 +1030 (CST) Date: Thu, 27 Jan 1994 08:31:55 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Mark.deRaad@UniSA.edu.au (Mark W. de Raad) writes: # Im new to Majordomo, so please forgive me if this is a silly question, # but I was wondering how do I set up archiving of received articles? # # There is a huge line in the sample.alias file, and I presume that this # has got something to do with it, but I wish that it could be # explained to me in a clearer manner? # # Any help is appreciated. This program (called "archive") will be included with the next release of Majordomo. I've been using it here for several months with no trouble, and a few other people have been using it as well with no reports of problems, so it should be stable enough. Instructions and examples are in the comments at the top of the script. -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 Thu Jan 27 09:13:06 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12887; Thu, 27 Jan 94 16:59:05 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA12858; Thu, 27 Jan 94 08:58:30 PST Message-Id: <9401271658.AA12858@mycroft.GreatCircle.COM> To: Stephen P Potter Cc: bill@biome.bio.dfo.ca (Bill Silvert), majordomo-users@greatcircle.com Subject: Re: Slowness of Majordomo In-Reply-To: Your message of Thu, 27 Jan 1994 11:04:13 EST Date: Thu, 27 Jan 1994 08:58:28 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Stephen P Potter writes: # Strange sunspot activity caused bill@biome.bio.dfo.ca (Bill Silvert) to write # : # | # | This message is being processed at the rate of about two commands per # | hour. It should take about three days for all 160 users to be # | unsubscribed! # | # # One thing I did find out about my slowdown is that the directory where the # log file was being written didn't have the proper permissions. (Majordomo # wasn't reporting that at the time). Once I figured that out, things # started to speed up. Now, requests are almost instantanious. Yeah, that would definitely explain a major slowdown. Majordomo would try to lock the log file (by creating a lock file in the directory with the log file) for 10 minutes for each log message, before giving up. It's typically going to log one log message for each command in the input. -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 Thu Jan 27 19:07:41 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA13995; Thu, 27 Jan 94 19:07:41 GMT Received: from acad3.alaska.edu (aurora.alaska.edu) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA13988; Thu, 27 Jan 94 11:07:28 PST Received: from mr.alaska.edu by acad3.alaska.edu (PMDF V4.2-11 #3250) id <01H868COSMC08WW36O@acad3.alaska.edu>; Thu, 27 Jan 1994 09:43:30 -900 Received: with PMDF-MR; Thu, 27 Jan 1994 09:42:03 -900 Mr-Received: by mta ACAD3A; Relayed; Thu, 27 Jan 1994 09:42:03 -0900 (-900) Date: Thu, 27 Jan 1994 09:42:03 -0900 From: "John W. Redelfs" Subject: Testimonials Wanted To: majordomo-users@greatcircle.com Message-Id: <01H868CQCVT28WW36O@mr.alaska.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT X400-Mts-Identifier: [;30249072104991/2568564@ACAD3A] Hop-Count: 0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Gentlemen: I run two lists on a remote server under Majordomo, and I am recommending it to the University of Alaska for a listserv networking students in the rural Arctic and scientists in sixteen circumpolar nations. I have two questions: Can anyone who is happy with Majordomo in a university setting provide me with a testimonial? Can anyone assure me that Majordomo will run on a network of NeXT workstations? Your help would be deeply appreciated as I prepare my proposal. Thankyou. Yours truly, John W. Redelfs, tsjwr@aurora.alaska.edu (907-225-8897) From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 28 01:31:27 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA15438; Fri, 28 Jan 94 01:31:27 GMT Received: from tsunami.berkeley.edu (tsunami-ether.Berkeley.EDU) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA15428; Thu, 27 Jan 94 17:31:18 PST Received: by tsunami.berkeley.edu (5.65c/CHAOS) id AA10315; Thu, 27 Jan 1994 17:33:09 -0800 Date: Thu, 27 Jan 1994 17:33:09 -0800 From: Dave Friedman Message-Id: <199401280133.AA10315@tsunami.berkeley.edu> To: majordomo-users@greatcircle.com Subject: ABORT? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I just received a MAJORDOMO ABORT message, claiming that majordomo couldnm not append to the file containing the list memebers. I have no idea what prompted the ABORT message, nor can I figure out why it couldn't append. Any ideas? I'm using Majordomo v. 1.60, on a Apollo DN4500. The list in question has well over 200 members if that makes any difference. Thanks, Dave Friedman davidf@ocf.Berkeley.EDU From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 28 03:49:37 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA15966; Fri, 28 Jan 94 03:49:37 GMT Received: from brahms.wag.caltech.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA15959; Thu, 27 Jan 94 19:49:30 PST Received: by brahms.wag.caltech.edu id AA17505 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Thu, 27 Jan 1994 19:51:17 -0800 Date: Thu, 27 Jan 1994 19:51:17 -0800 From: "Terry R. Coley" Message-Id: <199401280351.AA17505@brahms.wag.caltech.edu> To: majordomo-users@greatcircle.com Subject: adding a "one-liner" to the output of the "lists" command Cc: jnh@biosym.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have modified majordomo version 1.62 to allow for the printing of a one-liner description of each list with the "lists" command. The reason is that short list names are desirable, but not always descriptive. Therefore, I wanted a bit of information to come back with the list of lists. My change is just a hack to the "do_lists" subroutine in majordomo which looks for "listname.one-liner" in the same directory that holds the .info file. If present, this one-liner is printed next to the list name. I have not added a command similar to the "newinfo" command to allow adding of this information by a non-privileged list owner. If this sounds like a good idea, consider it just a suggestion :-). At present, I do not have time to flesh out the one-liner idea myself. If someone would like to pick up on this, I'll show my (trivial) changes to majordomo. - Terry Terry R. Coley terry@Pgrams.COM Parallelograms PO Box AA Pasadena, CA 91102 818-577-5515 Voice/Fax PS: for example output, send a lists command to majordomo@pgrams.com This is a new list - no traffic yet. From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 28 04:20:40 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA16043; Fri, 28 Jan 94 04:20:40 GMT Received: from frig.mt.cs.keio.ac.jp by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA16034; Thu, 27 Jan 94 20:20:28 PST Received: by frig.mt.cs.keio.ac.jp (5.67+1.6W/2.7W) id AA11564; Fri, 28 Jan 94 13:21:23 JST To: majordomo-users@greatcircle.com Subject: index maker Dont-Return-Receipt-To: itojun@mt.cs.keio.ac.jp Date: Fri, 28 Jan 1994 13:21:22 +0900 Message-Id: <11563.759730882@mt.cs.keio.ac.jp> From: Jun-ichiro Itoh Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, this is Jun-ichiro ITOH, from Japan. It's my first post to this list. I'm using majordomo 1.62 for about a month at my site. It works really fine. It's really great! I've added a small script that does a subject-search for 'index' command. Feel free to use/modify it. itojun@mt.cs.keio.ac.jp(Jun-ichiro ITOH) ---sample output >>>> index dist-test 3 94/01/09 Jun-ichiro ITOH (dist-test 3) test 4 94/01/09 Jun-ichiro ITOH (dist-test 4) test 5 94/01/09 Jun-ichiro ITOH (dist-test 5) test 6 94/01/09 Jun-ichiro ITOH (dist-test 6) test 7 94/01/09 Jun-ichiro ITOH (distrubute test 7) test 8 94/01/09 Jun-ichiro Itoh (dist-test 8) distribute test 9 94/01/09 Jun-ichiro Itoh (dist-test 9) Re: distribute test 10 94/01/09 Koichi Moriyama (dist-test 10) test ---majordomo.cf # $index_command = "/bin/ls -lRL"; $index_command = "$homedir/indexer"; ---indexer #! /usr/local/bin/perl # output index, with caching # by itojun@mt.cs.keio.ac.jp (Jun-ichiro ITOH) # $Header$ $version = '1.0'; $versionString = '***VERSION***'; $cache = '.cache'; # for News, Sun $cachefile = "$cache.pag"; # for BSD/386 # $cachefile = "$cache.db"; if (-e $cachefile) { $cacheDate = (-M $cachefile); } else { $cacheDate = -1; } dbmopen(fileCache, $cache, 0644); # version check if ($fileCache{$versionString} < $version) { $cacheDate = -1; } # search flles below here, updating fileCache &printDir('.', 'DIR000'); # delete removed files from fileCache foreach $file (keys %fileCache) { delete $fileCache{$file} if (!$mark{$file}); } # output names, with some ordering foreach $file (sort sortstring grep(!/[0-9]+/, keys %fileCache)) { print $fileCache{$file}; } foreach $file (sort sortnumber grep(/[0-9]+/, keys %fileCache)) { print $fileCache{$file}; } $fileCache{$versionString} = $version; dbmclose(fileCache); exit 0; #------------------------------------------------------------ sub printDir { local($directory) = $_[0]; local($handle) = $_[1]; local(@allfiles); local($file, $shortfile); $handle++; opendir($handle, $directory); @allfiles = grep(!/^\./, readdir($handle)); foreach $file (@allfiles) { if (-B $file) { next; } elsif (-d $file) { &printDir("$directory/$file", $handle); } else { $shortfile = "$directory/$file"; $shortfile =~ s/^\.\///; $mark{$shortfile} = 1; # update not needed if cache is newer than target next if (0 < $cacheDate && -M $file > $cacheDate); &printFile($shortfile); } } closedir($handle); } sub printFile { local($file) = $_[0]; local($from, $subject) = ('', ''); local($time, $year, $month, $day); # binary files: will never fall into here # if (-B $file) { # $fileCache{$file} = "$file\n"; # return; # } # text files: assume mail or news open(FILE, $file); while () { chop; $from = $1 if /^From:\s+(\S.*)$/; $subject = $1 if /^Subject:\s+(\S.*)$/; last if ($from && $subject); } close(FILE); $time = (stat($file))[9]; ($year, $month, $day) = (gmtime($time))[5,4,3];; $month++; $subject = '(no subject)' if ($subject eq ''); $from = $1 if ($from =~ /^([^<]+)\s+<[^>]+>$/); $from = '(no name)' if ($from eq ''); if (length($file) <= 7) { $fileCache{$file} = sprintf("%-7s\t%8s %-20s %-40s\n", $file, &formatdate($year, $month, $day), substr($from, 0, 20), substr($subject, 0, 40)); } else { $fileCache{$file} = sprintf("%s\n\t%8s %-20s %-40s\n", $file, &formatdate($year, $month, $day), substr($from, 0, 20), substr($subject, 0, 40)); } } sub formatdate { local($year, $month, $day) = @_[0,1,2]; return sprintf("%02d/%02d/%02d", $year, $month, $day); } #------------------------------------------------------------ sub sortstring { $a cmp $b; } sub sortnumber { $a <=> $b; } From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 28 06:07:27 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA16461; Fri, 28 Jan 94 06:07:27 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA16453; Thu, 27 Jan 94 22:07:15 PST Message-Id: <9401280607.AA16453@mycroft.GreatCircle.COM> To: Dave Friedman Cc: majordomo-users@greatcircle.com Subject: Re: ABORT? In-Reply-To: Your message of Thu, 27 Jan 1994 17:33:09 -0800 Date: Thu, 27 Jan 1994 22:07:13 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dave Friedman writes: # I just received a MAJORDOMO ABORT message, claiming that majordomo couldnm # not append to the file containing the list memebers. I have no idea # what prompted the ABORT message, nor can I figure out why it couldn't # append. # # Any ideas? # # I'm using Majordomo v. 1.60, on a Apollo DN4500. The list in question # has well over 200 members if that makes any difference. # # Thanks, # # Dave Friedman # davidf@ocf.Berkeley.EDU Did it do it just once, or is it repeatable? Firewalls has over 1300 subscribers now, and SAGE is about that size as well, so I don't think the size of your list is an issue. Are you sure the ownerships of the list file, the directory it's in, and the "wrapper" program are all correct? -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 Fri Jan 28 07:11:05 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA17024; Fri, 28 Jan 94 07:11:05 GMT Received: from maelstrom.berkeley.edu (maelstrom-ether.Berkeley.EDU) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA17017; Thu, 27 Jan 94 23:10:51 PST Received: by maelstrom.berkeley.edu (5.65c/CHAOS) id AA06167; Thu, 27 Jan 1994 23:12:36 -0800 Date: Thu, 27 Jan 1994 23:12:32 -0800 (PST) From: Dave Friedman Subject: Re: ABORT? To: Brent Chapman Cc: majordomo-users@greatcircle.com In-Reply-To: <9401280607.AA16453@mycroft.GreatCircle.COM> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Just so everyone knows, the problem that apparently caused the ABORT was that the registry had died, so it didn't know who had permission to do what. This made majordomo's user unable to access the file. Thanks to those who responded, =================================================================== Dave Friedman davidf@ts.com 57 University Drive #113 Pomona, CA 91768 (909)594-8854 *** There's No Place Like Home... There's No Place Like Home... *** =================================================================== From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 28 03:02:57 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA17990; Fri, 28 Jan 94 10:19:50 GMT Received: from scapa.cs.ualberta.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA17979; Fri, 28 Jan 94 02:19:36 PST Received: by scapa.cs.ualberta.ca id <18779>; Fri, 28 Jan 1994 03:20:38 -0700 Received: from alive.UUCP by ve6kik.ampr.ab.ca with UUCP (Smail3.1.28.1 #5) id m0pPm5V-0001OzC; Thu, 27 Jan 94 22:49 GMT-11:40 Received: by alive (Linux Smail3.1.28.1 #14) id m0pPm4m-0002MOC; Thu, 27 Jan 94 22:49 MST Date: Thu, 27 Jan 1994 15:49:01 -0700 From: Marc Slemko Subject: Re: ABORT? To: Dave Friedman Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199401280133.AA10315@tsunami.berkeley.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Thu, 27 Jan 1994, Dave Friedman wrote: > I just received a MAJORDOMO ABORT message, claiming that majordomo couldnm > not append to the file containing the list memebers. I have no idea > what prompted the ABORT message, nor can I figure out why it couldn't > append. I got the same message a few times when there were many copies of majordomo running at once due to a splurge of requests that came in over my uucp link. Could have something to do with locking? Different platform--Linux so that doesn't appear to be the problem. ================================================================= Marc Slemko Edmonton, Alberta, Canada marcs@alive.ersys.edmonton.ab.ca 1:342/1003@fidonet.org From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 28 13:00:45 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA18497; Fri, 28 Jan 94 13:00:45 GMT Received: from ac.dal.ca by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA18488; Fri, 28 Jan 94 05:00:33 PST Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01H87L616UU80076L5@AC.DAL.CA>; Fri, 28 Jan 1994 09:01:36 -0400 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA26317; Fri, 28 Jan 94 09:01:20 -0400 Date: Fri, 28 Jan 1994 09:01:19 -0400 (AST) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Re: ABORT? In-Reply-To: <9401280607.AA16453@mycroft.GreatCircle.COM> from "Brent Chapman" at Jan 27, 94 10:07:13 pm To: brent@GreatCircle.COM (Brent Chapman) Cc: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-Id: <9401281301.AA26317@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: 1386 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Although in this case the problem turned out to be something else, I am getting this frequently. I have a fairly active list with about 200 members, and I know that many Majordomo users have much more active lists. If two subscription requests arrive within a few minutes of each other the second finds the file L.list-name in the Lists directory and generates an ABORT along with 5000 to 7000 lines of messages from shlock that get sent to the majordomo manager. I'm running Majordomo 1.62 with perl 4.036 on SGI, IRIX 4.0.5, and I've tried everything I can with the permission question, even making all the directories mode 777. Bill ># I just received a MAJORDOMO ABORT message, claiming that majordomo couldnm ># not append to the file containing the list memebers. I have no idea ># what prompted the ABORT message, nor can I figure out why it couldn't ># append. > >Did it do it just once, or is it repeatable? Firewalls has over 1300 >subscribers now, and SAGE is about that size as well, so I don't think >the size of your list is an issue. Are you sure the ownerships of the >list file, the directory it's in, and the "wrapper" program are all correct? -- 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 Fri Jan 28 16:13:36 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19089; Fri, 28 Jan 94 16:13:36 GMT Received: from hub.terc.edu (terc.edu) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19082; Fri, 28 Jan 94 08:13:23 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 LAA01222 for ; Fri, 28 Jan 1994 11:14:03 -0500 Message-Id: <199401281614.LAA01222@hub.terc.edu> Date: 28 Jan 1994 11:14:23 -0500 From: "Hamilton Gilbert" Subject: which hsleicesterma To: "majordomo-users" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk which hsleicesterma From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 28 08:45:21 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19262; Fri, 28 Jan 94 16:37:50 GMT Received: from trantor.harris-atd.com (v3a.ess.harris.com) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19255; Fri, 28 Jan 94 08:37:41 PST Received: from melmac.harris-atd.com by trantor.harris-atd.com (4.1/1.14) id AA15910; Fri, 28 Jan 94 11:39:35 EST Message-Id: <9401281639.AA15910@trantor.harris-atd.com> Received: by melmac.harris-atd.com (5.0/SMI-SVR4) id AA08066; Fri, 28 Jan 1994 11:39:34 +0500 Date: Fri, 28 Jan 1994 11:39:34 +0500 From: chuck@trantor.harris-atd.com (Chuck Musciano) To: majordomo-users@greatcircle.com, terry@wag.caltech.edu Subject: Re: adding a "one-liner" to the output of the "lists" command Cc: jnh@biosym.com X-Sun-Charset: US-ASCII Content-Length: 401 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I have modified majordomo version 1.62 to allow for the printing of a > one-liner description of each list with the "lists" command. The > reason is that short list names are desirable, but not always descriptive. > Therefore, I wanted a bit of information to come back with the list of > lists. This was one of the first things I wanted to add. Please post your changes! Chuck Musciano From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 28 10:49:24 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19674; Fri, 28 Jan 94 18:38:35 GMT Received: from trans2.b30.ingr.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19667; Fri, 28 Jan 94 10:38:19 PST Received: by trans2.b30.ingr.com (5.65c/1.921207) id AA03264; Fri, 28 Jan 1994 12:33:08 -0600 From: bptatro@trans2.b30.ingr.com (Brian Tatro) Message-Id: <199401281833.AA03264@trans2.b30.ingr.com> Subject: recursive directories To: majordomo-users@greatcircle.com Date: Fri, 28 Jan 94 12:33:07 CST X-Mailer: ELM [version 07.00.00.00 (2.3 PL11)] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, Anybody know how to set up for retrieving files from recursive directories. Am I missing something in the docs? Brian -- This .sig space for rent. E=mc*2 --> It's not just a good idea, It's the LAW! Brian Tatro Senior Editor Product Translation (205)730-3323 Intergraph Corporation bptatro@trans2.b30.ingr.com From Majordomo-Users-Owner@GreatCircle.COM Fri Jan 28 20:16:11 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19924; Fri, 28 Jan 94 20:16:11 GMT Received: from mgc.mentorg.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA19917; Fri, 28 Jan 94 12:15:56 PST Received: from warren.mentorg.com by mgc.mentorg.com with SMTP (16.6/15.5+MGC-TD 2.20) id AA02453; Fri, 28 Jan 94 12:17:39 -0800 Received: by Warren.MENTORG.COM id AA25840 (5.65c/IDA-1.4.4); Fri, 28 Jan 1994 15:17:29 -0500 From: Tom Limoncelli Message-Id: <199401282017.AA25840@Warren.MENTORG.COM> Subject: Re: Slowness of Majordomo To: spp@cis.ufl.edu Date: Fri, 28 Jan 1994 15:17:28 -0500 (EST) Cc: majordomo-users@greatcircle.com In-Reply-To: <199401271604.LAA28007@schooner.cis.ufl.edu> from "Stephen P Potter" at Jan 27, 94 11:04:13 am Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 832 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > One thing I did find out about my slowdown is that the directory where the > log file was being written didn't have the proper permissions. (Majordomo > wasn't reporting that at the time). Once I figured that out, things > started to speed up. Now, requests are almost instantanious. Without a doubt, the one thing that Majordomo needs is a script that checks permissions on all associated files, directories, etc. I'm not 100% sure what the permissions should be, except that what I have seems to be working. :-) Otherwise, I'd write the script myself. 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 Fri Jan 28 20:51:35 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA20064; Fri, 28 Jan 94 20:51:35 GMT Received: from nda.nda.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA20057; Fri, 28 Jan 94 12:51:26 PST Received: from localhost (kovar@localhost) by nda.nda.com (8.6.4/8.6.4) id PAA20810; Fri, 28 Jan 1994 15:53:09 -0500 From: David Kovar Message-Id: <199401282053.PAA20810@nda.nda.com> Subject: Re: Slowness of Majordomo To: tom_limoncelli@Warren.MENTORG.COM (Tom Limoncelli) Date: Fri, 28 Jan 1994 15:53:08 -0500 (EST) Cc: spp@cis.ufl.edu, majordomo-users@GreatCircle.COM In-Reply-To: <199401282017.AA25840@Warren.MENTORG.COM> from "Tom Limoncelli" at Jan 28, 94 03:17:28 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: 652 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Without a doubt, the one thing that Majordomo needs is > a script that checks permissions on all associated > files, directories, etc. > > I'm not 100% sure what the permissions should be, except > that what I have seems to be working. :-) Otherwise, > I'd write the script myself. On a sort of related issue, I was hacking majordomo a few months ago and found that the locking mechanism attempted to create a lockfile in the directory that the target of the lock lived in. If you were trying to lock /etc/aliases, it would try to make a lock file in /etc, which made things difficult. I worked around that one, but it was a bit ugly. -David From Majordomo-Users-Owner@GreatCircle.COM Sat Jan 29 07:44:48 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01957; Sat, 29 Jan 94 07:44:48 GMT Received: from CUTL.City.UniSA.edu.au by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA01922; Fri, 28 Jan 94 23:44:11 PST Received: from localhost (deraad@localhost) by CUTL.City.UniSA.edu.au (8.3/8.3) id SAA02099; Sat, 29 Jan 1994 18:17:34 +1030 Message-Id: <199401290747.SAA02099@CUTL.City.UniSA.edu.au> Subject: Another archive request To: majordomo-users@greatcircle.com Date: Sat, 29 Jan 1994 18:17:33 +1030 (CST) From: Mark.deRaad@UniSA.edu.au (Mark W. de Raad) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 713 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I was wondering whether it is possible to archive articles on an idividual basis rather than appending them to a daily/monthly file? That way, wouldnt users have to retrieve the WHOLE file for that day rather than just articles on topics of their choice? Has anybody written such a script for archiving? How have people set up their archiving under majordomo? (thanks to Brent for his archive program. Its working fine, but I was wondering how to do the above). Any help appreciated, Thanks. -- Mark W. de Raad. CWIS Project Officer, Centre for University Teaching and Learning, University of South Australia, Adelaide, South Australia. Telephone: (08) 302 2071 'Life just wouldnt be any fun without BSD' From Majordomo-Users-Owner@GreatCircle.COM Sat Jan 29 19:59:55 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04195; Sat, 29 Jan 94 19:59:55 GMT Received: from ub-gate.UB.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04188; Sat, 29 Jan 94 11:59:48 PST Received: from bolis.UUCP by ub-gate.UB.com (4.1/SMI-4.1[UB-1.8]) id AA00804; Sat, 29 Jan 94 11:44:47 PST Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0pQKXY-0002YxC; Sat, 29 Jan 94 10:37 PST Message-Id: From: Alan Millar Subject: Re: Slowness of Majordomo To: dans@ans.net (Dan Simoes) Date: Sat, 29 Jan 1994 10:37:02 -0800 (PST) Cc: bill@biome.bio.dfo.ca, Majordomo-Users@GreatCircle.COM In-Reply-To: <199401271559.AA63494@foo.ans.net> from "Dan Simoes" at Jan 27, 94 10:59:33 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: 1048 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Dan Simoes spake of these matters: > > I don't know about SGI, but on my Linux box it was taking almost > an hour to process commands with only 4Mb on a 386DX25. Adding > another 8Mb cut times substantially, but I'm not relying on it > anymore, so I haven't run any real tests. Whoa! Something else is definitely wrong. My Linux box is 386SX25 which should make it slower in general IO processing, and also only has 4MB ram. All my Majordomo commands are completed in under a minute or two. I'm using SMail 3.1.28 > perl is a memory hog, no doubt about it. Probably true, but relatively unimportant. If it runs that fast on my machine, something *else* is drastically wrong for those installations taking 10 times as long. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ And Moses said, "Oh, Lord, please send someone else to do it!" -Exodus 4:13 From Majordomo-Users-Owner@GreatCircle.COM Sat Jan 29 23:01:48 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04626; Sat, 29 Jan 94 23:01:48 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA04619; Sat, 29 Jan 94 15:01:36 PST Received: from cs.umb.edu by cs.umb.edu with SMTP id AA02237 (5.65c/IDA-1.4.4 for ); Sat, 29 Jan 1994 18:03:18 -0500 Message-Id: <199401292303.AA02237@cs.umb.edu> To: Mark.deRaad@unisa.edu.au (Mark W. de Raad) Cc: majordomo-users@greatcircle.com Subject: Re: Another archive request In-Reply-To: Your message of "Sat, 29 Jan 1994 18:17:33 +1030." <199401290747.SAA02099@CUTL.City.UniSA.edu.au> Date: Sat, 29 Jan 1994 18:03:16 -0500 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199401290747.SAA02099@CUTL.City.UniSA.edu.au>, Mark W. de Raad writes: > I was wondering whether it is possible to archive articles > on an idividual basis rather than appending them to a daily/monthly > file? That way, wouldnt users have to retrieve the WHOLE file for > that day rather than just articles on topics of their choice? Yes, I use mh to do the article manipulation. I use mh's scan to produce my indicies. When I get the modules code for majordomo 2.0 written I will create an addin module that uses pick to handle all sorts of searching queries (date ranges, keywords in any given header, or in the body of the message, boolean operation on searches etc). If you want to see what indeicies created using this scheme look like, send an "index bblisa" to majordomo@cs.umb.edu. > Has anybody written such a script for archiving? Put the perl script below (after changing the location for rcvstore) into the home directory for majordomo and use the wrapper to run it. Note that you will need to have the home directory set by the wrapper writable so that a Mail directory and sequence files can be created. #!/usr/local/bin/perl # archive: A hack to use mh to handle the archives # # You may redistribute this file, or inlcude it into the offical majordomo # package # # $Source: /source/cvsrepos/majordomo/archive,v $ # $Revision: 1.1 $ # $Date: 1993/08/31 18:28:12 $ # $Author: rouilj $ # $State: Exp $ # # $Locker: $ # set our path explicitly $ENV{'PATH'} = "/bin:/usr/bin:/usr/ucb"; # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/tools/majordomo-1.56/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`) || die 'eval of majordomo.cf failed'; # Go to the home directory specified by the .cf file chdir("$homedir"); exec("/tools/mh-6.8/lib/mh/rcvstore +$filedir/$ARGV[0] -nocreate\n"); === end perl script Use the following .mh_profile for the user who runs the wrapper: Msg-Protect: 644 Folder-Protect: 775 and put it into the $HOME directory used by the wrapper. > How have people set up their archiving under majordomo? I found that individual article archiving was a necessity. Our email archives for the Back Bay LISA group are accessible via email, ftp, gopher, and www. The articles themselves are wais indexed, and the wais index is accessible via gopher or www. > (thanks to Brent for his archive program. Its working fine, but I > was wondering how to do the above). MH is the fastest hack to get what you want. It does all of the locking on the files, and by using scan you can get any type of printout you want for the indexes. As I said, I plan on implementing an interface to pick later that will allow arbitrary queries via email. -- 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 Sun Jan 30 02:22:58 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05599; Sun, 30 Jan 94 02:22:58 GMT Received: from enfm.utcc (enfm.utcc.utoronto.ca) by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05592; Sat, 29 Jan 94 18:22:46 PST Received: from localhost by enfm.utcc.utoronto.ca with SMTP id <39634>; Sat, 29 Jan 1994 21:24:32 -0500 To: majordomo-users@GreatCircle.COM Subject: location of distribute package Organization: UTCC Network & Operations Services, External Network Fac. Mgmt. Phone: +1 416 978 3328 Date: Sat, 29 Jan 1994 21:24:22 -0500 From: "Eric M. Carroll" Message-Id: <94Jan29.212432est.39634@enfm.utcc.utoronto.ca> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk A package for resending mail has been mentioned to me in conjunction with our efforts to deploy majordomo. I have been looking for the archive site for distribute without any luck. Could someone running distribute with majordomo let me know where I can find it? I am not on the list, so please reply directly to me. Thanks, Eric Carroll University of Toronto Computing & Communications Network & Operations Services, External Network Fac. Management From Majordomo-Users-Owner@GreatCircle.COM Sun Jan 30 02:29:20 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05622; Sun, 30 Jan 94 02:29:20 GMT Received: from leibniz.math.psu.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA05615; Sat, 29 Jan 94 18:29:08 PST Received: from augusta.math.psu.edu (jim@augusta.math.psu.edu [146.186.131.77]) by leibniz.math.psu.edu (8.6.4/8.5) with ESMTP id VAA11799; Sat, 29 Jan 1994 21:31:05 -0500 Received: from localhost by augusta.math.psu.edu id ; Sat, 29 Jan 1994 21:31:03 -0500 Message-Id: <199401300231.VAA26041@augusta.math.psu.edu> To: "Eric M. Carroll" Cc: majordomo-users@GreatCircle.COM Subject: Re: location of distribute package In-Reply-To: Your message of "Sat, 29 Jan 1994 21:24:22 EST." <94Jan29.212432est.39634@enfm.utcc.utoronto.ca> Date: Sat, 29 Jan 1994 21:31:02 -0500 From: Jim Duncan Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Eric M. Carroll" writes: > A package for resending mail has been mentioned to me in conjunction > with our efforts to deploy majordomo. I have been looking for the > archive site for distribute without any luck. Could someone running > distribute with majordomo let me know where I can find it? I am not on > the list, so please reply directly to me. > > Thanks, > > Eric Carroll University of Toronto Computing & Communications > Network & Operations Services, External Network Fac. Management Contact Steve Miller at UUNET; I think it's steve@uunet.uu.net. Jim From Majordomo-Users-Owner@GreatCircle.COM Sun Jan 30 00:49:49 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA06353; Sun, 30 Jan 94 08:15:33 GMT Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA06330; Sun, 30 Jan 94 00:14:55 PST Message-Id: <9401300814.AA06330@mycroft.GreatCircle.COM> To: "Eric M. Carroll" Cc: majordomo-users@GreatCircle.COM Subject: Re: location of distribute package In-Reply-To: Your message of Sat, 29 Jan 1994 21:24:22 -0500 Date: Sun, 30 Jan 1994 00:14:54 -0800 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Eric M. Carroll" writes: # A package for resending mail has been mentioned to me in conjunction # with our efforts to deploy majordomo. I have been looking for the # archive site for distribute without any luck. Could someone running # distribute with majordomo let me know where I can find it? I am not on # the list, so please reply directly to me. I think that the "resend" script included with Majordomo now does everything that "distribute" does, and then some. I originally used "distribute", so some of the Majordomo documentation and such may still mention it, but I wrote "resend" and switched to that some time ago. -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 Sun Jan 30 12:14:37 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07341; Sun, 30 Jan 94 12:14:37 GMT Received: from lizard.foretune.co.jp by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA07334; Sun, 30 Jan 94 04:14:18 PST Received: from dink.foretune.co.jp (dink.foretune.co.jp [133.123.16.111]) by lizard.foretune.co.jp (8.6.5+2.3W/3.1W-ft2.1h) with ESMTP id VAA21903; Sun, 30 Jan 1994 21:15:41 +0900 Received: from localhost.foretune.co.jp (localhost.foretune.co.jp [127.0.0.1]) by dink.foretune.co.jp (8.6.5+2.3W/3.1W-ftc-nomx1.1) with SMTP id VAA07051; Sun, 30 Jan 1994 21:15:40 +0900 Message-Id: <199401301215.VAA07051@dink.foretune.co.jp> To: "Eric M. Carroll" Cc: majordomo-users@GreatCircle.COM Subject: Re: location of distribute package In-Reply-To: Your message of Sun, 30 Jan 1994 00:14:54 -0800. <9401300814.AA06330@mycroft.GreatCircle.COM> From: Shigeya Suzuki References: <9401300814.AA06330@mycroft.GreatCircle.COM> Mime-Version: 1.0 Content-Type: text/plain;charset="ISO-2022-JP" Date: Sun, 30 Jan 1994 21:15:39 +0900 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >>>>> On Sun, 30 Jan 1994 00:14:54 PST, Brent Chapman said: Brent> I think that the "resend" script included with Majordomo now does Brent> everything that "distribute" does, and then some. I agree "resend" is powerful enoough for most of cases. But we already start modifiying distribute, we're using it. It's heavily modified now. I had plan to release it to public earlier, but had no enough time last few month to write English documentation. Also, I need to get approval from original author... It fixes several minor bugs and limitations in original distribute, and modified to include "article number" and "mailing list name" in Subject, etc. At first look, It's odd to see mailinglist name and article number in subject, but really great to have such in Subject. You can pick and read your favorite mailing list from "subject list." I'm using it in mailagent and dist kit's mailining list. The subject look something like: Subject: (agent-users 1) Welcome to agent-users maling list If there are anyone interested in this, please drop me an email. Written in C, tested on Sun, BSD/386 and several other similar platforms. shigeya From Majordomo-Users-Owner@GreatCircle.COM Mon Jan 31 20:14:49 1994 Return-Path: Received: by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA13339; Mon, 31 Jan 94 20:14:49 GMT Received: from dirac.scri.fsu.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-931103) id AA13332; Mon, 31 Jan 94 12:14:42 PST Received: by dirac.scri.fsu.edu id AA54706 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Mon, 31 Jan 1994 15:16:39 -0500 Date: Mon, 31 Jan 1994 15:16:39 -0500 From: Kingsley Kerce Message-Id: <199401312016.AA54706@dirac.scri.fsu.edu> To: majordomo-users@greatcircle.com Subject: keeping bounced mail from returning to subscriber/sender Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk If a subscriber sends a message to a mailing list containing addresses that cause bounces, then the subscriber/sender gets a copy of the bounced mail. They don't care to receive the bounce. Can this be prevented? (Without removing the offending addresses from the list -- I'm aware of the Majordomo `bounce' utility.) Thanks much, Kingsley F. Kerce (kerce@scri.fsu.edu) WWW: http://dirac.scri.fsu.edu/~kerce Supercomputer Computations Research Institute Florida State University Tallahassee, FL, USA 32306 DEEP THOUGHT: I'd rather be rich than stupid.