From majordomo-users-owner Mon Aug 1 16:20:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA22616; Mon, 1 Aug 1994 16:20:14 GMT Received: from ketch.cis.ufl.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA22583; Mon, 1 Aug 1994 09:19:38 -0700 Received: from localhost by ketch.cis.ufl.edu (8.6.7/8.6.7-cis.ufl.edu) id MAA24461; Mon, 1 Aug 1994 12:21:59 -0400 Message-Id: <199408011621.MAA24461@ketch.cis.ufl.edu> To: Jim Reisert -- MLO5-2/36A -- DTN 223-5747 30-Jul-1994 1106 cc: majordomo-workers@greatcircle.com, majordomo-users@greatcircle.com Subject: Re: Dec Alpha and Core Dumps In-reply-to: Some random ramblings on Sat, 30 Jul 1994 11:11:24 -0400. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Mon, 01 Aug 1994 12:21:58 EDT From: Stephen P Potter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused Jim Reisert -- MLO5-2/36A -- DTN 223-5747 30-Ju l-1994 1106 to write: | Steve (tamm@mit.edu) asked: | | >Has anyone solved the problems of core dumps with majordomo and perl | >4.036 on Dec Alpha's? The problem is with perl and the majordomo script | >itself, not with the wrapper (as I had once thought). | | Well, I haven't had a single problem since upgrading to Perl 5, now in | either alpha or beta test. I found the sources at: | | ftp.funet.fi/pub/languages/perl/ports/perl5 Sorry this isn't really the forum for this, but: You might find it easier and quicker to get perl5 from my site: ftp.cis.ufl.edu:/pub/perl/src/5.0 Steve From majordomo-users-owner Mon Aug 1 19:01:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA24345; Mon, 1 Aug 1994 19:01:45 GMT Received: from infoexp.express.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA24339; Mon, 1 Aug 1994 12:01:36 -0700 Received: from alto.express.com (alto.express.com [199.74.248.4]) by infoexp.express.com (8.6.8/8.6.6) with ESMTP id MAA14566 for ; Mon, 1 Aug 1994 12:05:32 -0700 Received: from [199.74.248.5] (snoopy.express.com [199.74.248.5]) by alto.express.com (8.6.8/8.6.6) with SMTP id MAA15414 for ; Mon, 1 Aug 1994 12:05:13 -0700 Message-Id: <199408011905.MAA15414@alto.express.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 1 Aug 1994 12:07:51 -0800 To: majordomo-users@GreatCircle.COM From: pzee@express.com (Philip J. Zee) Subject: unknown mailer error 5 again Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have asked for help on this one before. It was suggested that my perl was installed incorrectly. But now, I have fixed the problem and am still getting this message: % echo help | /usr/lib/sendmail -v majordomo majordomo... aliased to "|/home/sigweb/majordomo/wrapper majordomo" majordomo: No such file or directory "|/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 Saving message in /home/sigweb/pzee/dead.letter /home/sigweb/pzee/dead.letter... Sent When I did: % ls -lg /home/sigweb/majordomo/wrapper -rwsr-sr-x 1 daemon majordom 24576 Jul 20 09:39 /home/sigweb/majordomo/wra pper* % ls -lg /home/sigweb/majordomo/majordomo -rwxr-xr-x 1 majordom majordom 42428 Aug 1 11:54 /home/sigweb/majordomo/maj ordomo* What's wrong? I want to get this installed today or tomorrow. Please, I really mean please, could someone help me? Philip ______________________________________________________________________ Philip J. Zee / / / Information Express / / / 3250 Ash St. o o o / / / Palo Alto, CA 94306 o o / o / / Main: (415) 494-8787 DID: (415) 812-3530 o /o /o / Internet: pzee@express.com / / / ______________________________________________________________________ From majordomo-users-owner Mon Aug 1 19:05:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA24374; Mon, 1 Aug 1994 19:05:33 GMT Received: from infoexp.express.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA24368; Mon, 1 Aug 1994 12:05:24 -0700 Received: from alto.express.com (alto.express.com [199.74.248.4]) by infoexp.express.com (8.6.8/8.6.6) with ESMTP id MAA14574 for ; Mon, 1 Aug 1994 12:09:20 -0700 Received: from [199.74.248.5] (snoopy.express.com [199.74.248.5]) by alto.express.com (8.6.8/8.6.6) with SMTP id MAA15429 for ; Mon, 1 Aug 1994 12:09:02 -0700 Message-Id: <199408011909.MAA15429@alto.express.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 1 Aug 1994 12:11:39 -0800 To: majordomo-users@GreatCircle.COM From: pzee@express.com (Philip J. Zee) Subject: unknown mailer error 5 again Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Oh, I may want to add that during the installation of wrapper, this is in the Makefile: # This is where "wrapper" looks for the programs it's supposed to run. W_BIN=/home/sigweb/majordomo # This is the environment that (along with LOGNAME and USER inherited from the # parent process, and without the leading "W_" in the variable names) gets # passed to processes run by "wrapper" W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf Thanks for any help, Philip ______________________________________________________________________ Philip J. Zee / / / Information Express / / / 3250 Ash St. o o o / / / Palo Alto, CA 94306 o o / o / / Main: (415) 494-8787 DID: (415) 812-3530 o /o /o / Internet: pzee@express.com / / / ______________________________________________________________________ From majordomo-users-owner Mon Aug 1 21:56:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA25505; Mon, 1 Aug 1994 21:56:39 GMT Received: from midway.uchicago.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA25499; Mon, 1 Aug 1994 14:56:29 -0700 From: ckoenig@midway.uchicago.edu Received: from kimbark.uchicago.edu by midway.uchicago.edu for majordomo-users@greatcircle.com Mon, 1 Aug 94 17:00:19 CDT Received: from localhost.uchicago.edu by kimbark.uchicago.edu (4.1/UCCO-1.0A) id AA05740; Mon, 1 Aug 94 16:59:12 CDT Message-Id: <9408012159.AA05740@kimbark.uchicago.edu> Reply-To: ckk@uchicago.edu To: majordomo-users@greatcircle.com Subject: more self-documenting list config file? Date: Mon, 01 Aug 94 16:59:12 -0500 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Has anyone out there written their own version of the default per-list config file, which might be less intimidating to a less sophisticated computer user who will be administering a mailing list? (i.e. what the individual list owner gets in the mail from Majordomo, after a "writeconfig" followed by a "config") It looks like we'll be writing one here, but if you've already done one that you would like to share, please do! (and I'll post ours to the majordomo-users list when our documentation person is through tangling with it). It would even be nice to consider, someday, maybe splitting the per-list config options into two files, and make the one file of generally "harmless" options available to everyone including more novice list owners, but saving the options which change working directories etc. and envelope senders etc. for more knowledgeable list owners only. Chris Koenigsberg: ckk@uchicago.edu, ckoenig@midway.uchicago.edu U. of Chicago Academic Information Technologies From majordomo-users-owner Mon Aug 1 22:05:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id WAA25578; Mon, 1 Aug 1994 22:05:00 GMT Received: from sparc by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA25572; Mon, 1 Aug 1994 15:04:43 -0700 Received: by sparc (5.0/SMI-SVR4) id AA01924; Mon, 1 Aug 1994 19:01:42 +0400 Date: Mon, 1 Aug 1994 19:01:42 -0300 (ADT) From: Steve MacLeod Subject: Re: unknown mailer error 5 again To: "Philip J. Zee" Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199408011905.MAA15414@alto.express.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 2574 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In my case, when I encountered this same error, the problem was with ownerships ... I fixed it like this ... 1) Created user majordomo and group majordom ... 2) entered the appropriate userid and groupid data in the Makefile section ... I used the POSIX section, I run Solaris 2.3 ... 3) did a make, and made sure that the wrapper went into the right area and had owner majordomo and group ownership to majordom 4) set up majordomo as a trusted user in my sendmail.cf ... restarted sendmail .. Works for me ... so far anyway ... plus my nerves are better now that wrapper is not setuid to root ... another thing I was able to do is set up all directories as 640 ... simply because enquiring minds want to know and this machine is in a university ! Hope this helps! sm -------------------------------------------------------------------- Steve MacLeod Microcomputer Specialist (902)539-5300x625 Computer Centre University College of Cape Breton Sydney, N.S. Fax (902)562-0119 Canada B1P 5S2 On Mon, 1 Aug 1994, Philip J. Zee wrote: > I have asked for help on this one before. It was suggested that my perl > was installed incorrectly. But now, I have fixed the problem and am still > getting this message: > > % echo help | /usr/lib/sendmail -v majordomo > majordomo... aliased to "|/home/sigweb/majordomo/wrapper majordomo" > majordomo: No such file or directory > "|/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 > Saving message in /home/sigweb/pzee/dead.letter > /home/sigweb/pzee/dead.letter... Sent > > When I did: > % ls -lg /home/sigweb/majordomo/wrapper > -rwsr-sr-x 1 daemon majordom 24576 Jul 20 09:39 /home/sigweb/majordomo/wra > pper* > > % ls -lg /home/sigweb/majordomo/majordomo > -rwxr-xr-x 1 majordom majordom 42428 Aug 1 11:54 /home/sigweb/majordomo/maj > ordomo* > > What's wrong? I want to get this installed today or tomorrow. Please, I > really mean please, could someone help me? > > Philip > > > ______________________________________________________________________ > Philip J. Zee / / / > Information Express / / / > 3250 Ash St. o o o / / / > Palo Alto, CA 94306 o o / o / / > Main: (415) 494-8787 DID: (415) 812-3530 o /o /o / > Internet: pzee@express.com / / / > ______________________________________________________________________ > > > From majordomo-users-owner Tue Aug 2 04:23:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id EAA27758; Tue, 2 Aug 1994 04:23:40 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA27752; Mon, 1 Aug 1994 21:23:31 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id XAA15754; Mon, 1 Aug 1994 23:33:53 -0500 Date: Mon, 1 Aug 1994 23:33:52 +0100 From: "Robert A. Hayden" Subject: File Server and Case Sensitivity To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Is there any way to turn off case sensitivty on the get command? (hmm, can't elaborate much more than that :-) ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else, dammit -=-=-=-=-=-=-=- (GEEK CODE 2.1) GJ/CM d- H-- s-:++>s-:+ g+ p? au+ a- w++ v* C++(++++) UL++++$ P+>++ L++$ 3- E---- N+++ K+++ W M+ V-- -po+(---)>$ Y++ t+ 5+++ j R+++$ G- tv+ b+ D+ B--- e+>++(*) u** h* f r-->+++ !n y++** From majordomo-users-owner Tue Aug 2 12:46:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA01567; Tue, 2 Aug 1994 12:46:28 GMT Received: from garm.adm.ku.dk by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id FAA01548; Tue, 2 Aug 1994 05:46:07 -0700 Received: from odont.ku.dk (server1.odont.ku.dk [130.225.107.2]) by garm.adm.ku.dk (8.6.8.1/8.6) with SMTP id OAA17059 for ; Tue, 2 Aug 1994 14:49:13 +0200 Received: from TS/MERCURY by odont.ku.dk (Mercury 1.12); Tue, 2 Aug 94 14:49:30 +100 Received: from MERCURY by TS (Mercury 1.12); Tue, 2 Aug 94 14:49:22 +100 From: "Anders Nattestad" Organization: Dental School, Univ. of Copenhagen To: Majordomo-Users@GreatCircle.com Date: Tue, 2 Aug 1994 14:49:19 GMT+100 Subject: Howto use Mime with Majordomo Priority: normal X-mailer: Pegasus Mail v3.1 (R1a) Message-ID: <2B5612D2D50@odont.ku.dk> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi All, Does anyone have experience with different mailers, Mime and Majordomo. I use a Sendmail/IDA package for Linux with Deliver as the local mailer-agent. Mime does not pass through this setup and I am uncertain which element is the cause of this. Any hints. Maybe I should upgrade to Sendmail 8.6.9 ??? Thanks in advance Anders ------------------------------------------------------------------- Anders Nattestad, DDS, Ph.D, Dep. of Oral and Maxillofacial Surgery and Chairman of Computer Network and Multimedia Division. Dental School, Faculty of Health Science, University of Copenhagen Norre Alle 20, Copenhagen, Denmark, Ph.+4535326618, Fax +4535326625 From majordomo-users-owner Tue Aug 2 19:12:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA04573; Tue, 2 Aug 1994 19:12:29 GMT Received: from vacuum.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA04565; Tue, 2 Aug 1994 12:12:20 -0700 Received: from auger by vacuum.org (5.0/SOLARIS-V1.0-American Vacuum Society) id AA08916; Tue, 2 Aug 94 15:16:14 EDT Message-Id: <9408021916.AA08916@vacuum.org> X-Sender: carlos@torr Date: Tue, 02 Aug 1994 15:14:35 -0400 To: majordomo-users@greatcircle.com From: carlos@vacuum.org (Carlos Toro) Subject: Naming Service--Solaris 2.2 Cc: m-slade@vacuum.org X-Mailer: content-length: 280 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk A new majordomo service is to be set up on a Sun running Solaris 2.2 which uses NIS+ for accounts to users on the local net. Should the majordomo account and group also be NIS+ or just on the local host's /etc/passwd and /etc/group files? Thanks for your attention. Carlos From majordomo-users-owner Tue Aug 2 19:27:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA04680; Tue, 2 Aug 1994 19:27:23 GMT Received: from thunder.cis.ufl.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA04674; Tue, 2 Aug 1994 12:27:12 -0700 Received: from localhost by thunder.cis.ufl.edu (8.6.7/8.6.7-cis.ufl.edu) id PAA05225; Tue, 2 Aug 1994 15:30:43 -0400 Message-Id: <199408021930.PAA05225@thunder.cis.ufl.edu> To: carlos@vacuum.org (Carlos Toro) cc: majordomo-users@greatcircle.com Subject: Re: Naming Service--Solaris 2.2 In-reply-to: Some random ramblings on Tue, 02 Aug 1994 15:14:35 -0400. Organization: Department of Impossible Probably Facts Reply-To: Stephen P Potter Date: Tue, 02 Aug 1994 15:30:43 EDT From: Stephen P Potter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Strange sunspot activity caused carlos@vacuum.org (Carlos Toro) to write: | A new majordomo service is to be set up on a Sun running Solaris 2.2 which | uses NIS+ for accounts to users on the local net. Should the majordomo | account and group also be NIS+ or just on the local host's /etc/passwd and | /etc/group files? | | Thanks for your attention. Carlos: We're running a large 4.1.3 network and have ours set up through NIS+. There's no reason not to set it up that way. Steve From majordomo-users-owner Wed Aug 3 08:45:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA11786; Wed, 3 Aug 1994 13:47:55 GMT Received: from watson.ibm.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA11755; Wed, 3 Aug 1994 06:47:10 -0700 Received: from WATSON by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 0869; Wed, 03 Aug 94 09:50:45 EDT Received: from YKTVMV by watson.vnet.ibm.com with "VAGENT.V1.0" id 4067; Wed, 3 Aug 1994 09:50:45 EDT Received: from hawpub1.watson.ibm.com by yktvmv.watson.ibm.com (IBM VM SMTP V2R3) with TCP; Wed, 03 Aug 94 09:50:45 EDT Received: by hawpub1.watson.ibm.com (AIX 3.2/UCB 5.64/930311) id AA43224; Wed, 3 Aug 1994 09:50:40 -0400 From: perk@watson.ibm.com (Charlie Perkins) Message-Id: <9408031350.AA43224@hawpub1.watson.ibm.com> To: majordomo-users@GreatCircle.COM Subject: Majordomo ideas Date: Wed, 03 Aug 94 09:50:39 -0500 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have spent the appropriate number of days setting up majordomo here. I have some ideas/complaints about the trials and tribulations of doing so. However, I have one big request, and wonder whether other people would share my concern. I think that requiring subscription requests ONLY in the body of the message is an unnecessary restriction. This invites user frustration, as many people will just get it wrong and not necessarily have a clue about how to go about getting it right. I'm sure we will all agree that there are many levels of user sophistication discernible within most normal populations of potential mailing list recipients. And, I don't see what is wrong, a priori, with allowing requests to be send on the 'Subject:' line of mail to majordomo. Comments? Is there any likelihood that this (probably major) change would ever happen? Thanks, Charlie P. PS. If there is interest, I will try to beat my notes into shape, regarding my frustrations as a new customer and wannabe mailing list administrator, and post them to this list. From majordomo-users-owner Wed Aug 3 17:10:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA18949; Wed, 3 Aug 1994 23:22:45 GMT Received: from megalon.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id DAA00798; Tue, 2 Aug 1994 03:10:40 -0700 From: ùmax@megalon.com Received: by megalon.com (8.6.8/SMI-5.3) id DAA10917; Tue, 2 Aug 1994 03:10:12 -0700 Message-Id: <199408021010.DAA10917@megalon.com> Subject: Problem using majordomo under Solaris 2.3 To: majordomo-users@GreatCircle.COM Date: Tue, 2 Aug 1994 03:10:11 -0700 (PDT) Cc: max@megalon.com (Max Hozven - Network Support) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 12097 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I am having some trouble getting Majordomo 1.92 to work under Solaris 2.3 (using Berkeley sendmail version 8.6.8). Below is the the error I'm stuck on (the line 46 part and unknown mailer errors below): megalon# Mail -v majordomo Subject: test subscribe test1 max # Set the umask for the process. Used to set default file status for # config file. umask(007); # the safe locations for archive directories # None of the parameters that use safedirs are actually used, so # @safedirs is a placeholder for future functionality. # Just ignore it for version 1.90 through 1.92. @safedirs = ( ); 1; # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1 1994/06/09 19:45:18 rouilj Exp $ eval of majordomo.cf failed at /files1/admin/majordomo/majordomo-1.92/bin/majordomo line 46. "|/files1/admin/majordomo/majordomo-1.92/bin/wrapper majordomo"... unknown mailer error 2 Saving message in /home/max/dead.letter /home/max/dead.letter... Sent Here's line 46 in majordomo: eval(`cat $cf`) || die "eval of majordomo.cf failed $@"; If I comment out this line 46, things begin to work with some errors: Mail -v majordomo Subject: test subscribe test1 max EOT megalon# majordomo... aliased to "|/files1/admin/majordomo/majordomo-1.92/bin/wrapper majordomo" megalon /tmp/majordomo.10682.* "|/files1/admin/majordomo/majordomo-1.92/bin/wrapper majordomo"... Sent The maillist has a succeeded line in it: megalon# pwd /files1/local/mail/lists megalon# cat test1 Succeeded. max I'll include some additional info below. If anyone can spot any errors or give me some pointers, I'd appreciate it. ------------------------------------------------------- -Max Hozven Megalon Network Support max@megalon.com ------------------------------------------------------- megalon# pwd /files1/admin/majordomo/majordomo-1.92/bin megalon# ls -l total 332 -rwxrwxr-x 1 majordom majordom 675 Aug 2 02:22 Log drwxrwxr-x 2 majordom majordom 512 Aug 2 00:14 Tools -rwxrwxr-x 1 majordom majordom 6195 Aug 2 00:39 approve drwxrwxr-x 2 majordom majordom 512 Aug 2 00:14 bin -rwxrwxr-x 1 majordom majordom 2874 Aug 2 00:39 bounce -rwxrwxr-x 1 majordom majordom 2610 Aug 2 01:09 bounce-remind -rwxrwxr-x 1 majordom majordom 43710 Aug 2 01:09 config_parse.pl -rwxrwxr-x 1 majordom majordom 9720 Aug 2 01:09 digest -rwxrwxr-x 1 majordom majordom 42269 Aug 2 02:13 majordomo -rwxrwxr-x 1 majordom majordom 3005 Aug 2 01:48 majordomo.cf -rwxrwxr-x 1 majordom majordom 10889 Aug 2 01:09 majordomo.pl -rwxrwxr-x 1 majordom majordom 137 Aug 2 01:09 majordomo_version.pl drwxrwxr-x 4 majordom majordom 512 Aug 2 00:14 man -rwxrwxr-x 1 majordom majordom 1412 Aug 2 00:39 medit -rwxrwxr-x 1 majordom majordom 2238 Aug 2 01:09 new-list -rwxrwxr-x 1 majordom majordom 3017 Aug 2 01:09 request-answer -rwxrwxr-x 1 majordom majordom 12135 Aug 2 01:09 resend -rwxrwxr-x 1 majordom majordom 3742 Aug 2 01:09 resend.README -rwxrwxr-x 1 majordom majordom 6051 Aug 2 01:09 shlock.pl -rwxrwxr-x 1 majordom majordom 8284 Aug 2 01:10 wrapper majordomo.cf: ================================================================= # $whereami -- What machine am I running on? $whereami = "megalon.megalon.com"; # $whoami -- Who do users send requests to me as? $whoami = "Majordomo@$whereami"; # $whoami_owner -- Who is the owner of the above, in case of problems? #$whoami_owner = "Majordomo-Owner@$whereami"; $whoami_owner = "postmaster@$whereami"; # $homedir -- Where can I find my extra .pl files, like majordomo.pl? # the environment variable HOME is set by the wrapper if ( defined $ENV{"HOME"}) { $homedir = $ENV{"HOME"}; } else { #$homedir = "/usr/local/majordomo-1.92"; $homedir = "/files1/admin/majordomo/majordomo-1.92/bin"; } # $listdir -- Where are the mailing lists? $listdir = "/usr/local/mail/lists"; # $digest_work_dir -- the parent directory for digest's queue area # Each list must have a subdirectory under this directory in order for # digest to work. E.G. The bblisa list would use: # /usr/local/mail/digest/bblisa # as its directory. $digest_work_dir = '/usr/local/mail/digest'; # $log -- Where do I write my log? $log = "$homedir/Log"; # $mailer -- What program and args do I use to send mail? # The variable $to can be interpolated into this command line, # however the $to variable is provided by the person sending mail, # and much mischief can be had by playing with this variable. # Use $to with care. $mailer = "/usr/lib/sendmail -f\$sender -t"; # Majordomo will look for "get" and "index" files related to $list in # directory "$filedir/$list$filedir_suffix", so set $filedir and # $filedir_suffix appropriately. For instance, to look in # /usr/local/mail/files/$list, use: # $filedir = "/usr/local/mail/files"; # $filedir_suffix = ""; # empty string # or to look in $listdir/$list.archive, use: # $filedir = "$listdir"; # $filedir_suffix = ".archive"; $filedir = "$listdir"; $filedir_suffix = ".archive"; # What command should I use to process an "index" request? $index_command = "/bin/ls -lRL"; # If you want to use FTPMAIL, rather than local access, for file transfer # and access, define the following: # $ftpmail_address = "ftpmail@decwrl.dec.com"; # $ftpmail_location = "FTP.$whereami"; # if you want the subject of the request to be included as part of the # subject of the reply (useful when automatically testing, or submitting # multiple command sets), set $return_subject to 1. $return_subject = 1; # If you are using majordomo at the -request address, set the # following variable to 1. This affects the welcome message that is # sent to a new subscriber as well as the help text that is generated. $majordomo_request = 0; # Set the umask for the process. Used to set default file status for # config file. umask(007); # the safe locations for archive directories # None of the parameters that use safedirs are actually used, so # @safedirs is a placeholder for future functionality. # Just ignore it for version 1.90 through 1.92. @safedirs = ( ); 1; # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1 1994/06/09 19:45:18 rouilj Exp $ ======================================================================== /etc/aliases section: # # Majordomo # #majordomo: "|/files1/admin/majordomo/majordomo_files/wrapper majordomo" majordomo: "|/files1/admin/majordomo/majordomo-1.92/bin/wrapper majordomo" majordomo-owner: max owner-majordomo: max # # Sample mailing list # owner-test1: test1-owner test1-outgoing: :include:/usr/local/mail/lists/test1, test1-archive owner-test1-outgoing: test1-owner test1-archive: /usr/local/mail/archive/test1 owner-test1-archive: test1-owner test1-request: "|/files1/admin/majordomo/majordomo-1.92/bin/wrapper test1-answer test1" owner-test1-request: test1-owner test1-approval: max test1-owner: max owner-test1-owner: max ======================================================================== Makefile: # $Source: /sources/cvsrepos/majordomo/Makefile,v $ # $Revision: 1.21.2.2 $ # $Date: 1994/06/09 19:48:07 $ # $Author: rouilj $ # $State: Exp $ # # $Header: /sources/cvsrepos/majordomo/Makefile,v 1.21.2.2 1994/06/09 19:48:07 rouilj Exp $ # # $Locker: $ # # this makefile installs the following structure for the bsd universe: # (root is W_BIN below) # root -+-- -- actual majordomo scripts, libraries etc # +-- Tools -- tools like archive # +-- bin -- user level tools, approve, bounce etc # +-- man -- man pages # # This is where "wrapper" looks for the programs it's supposed to run. #W_BIN=/tools/majordomo-1.92 W_BIN=/files1/admin/majordomo/majordomo-1.92/bin # This is the environment that (along with LOGNAME and USER inherited from the # parent process, and without the leading "W_" in the variable names) gets # passed to processes run by "wrapper" W_PATH=/bin:/usr/bin:/usr/ucb:/files1/admin/majordomo/majordomo-1.92/bin W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # Use these settings for BSD-based systems, including SunOS 4.x. If you're # using a POSIX-compliant system (including SysV and BSDI), comment these # settings out, and uncomment the POSIX settings below. #W_USER=daemon #W_GROUP=bblisa #W_CHOWN=${W_USER}.${W_GROUP} #W_CHMOD=6755 #WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ # -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ # -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" # If you're using a POSIX-compliant system, uncomment this set of parameters # and comment out the BSD settings above. W_UID = 1001 W_GID = 50 W_CHOWN=majordomo W_CHMOD=4755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" \ -DPOSIX_UID=${W_UID} -DPOSIX_GID=${W_GID} # YOU SHOULDN'T HAVE TO CHANGE ANYTHING BELOW THIS LINE. # For those stupid machines that try to use csh SHELL = /bin/sh default: wrapper install: install-scripts install-man @echo "Run 'make install-wrapper' as root" install-wrapper: wrapper cp wrapper $(W_BIN)/wrapper chown ${W_CHOWN} $(W_BIN)/wrapper chmod ${W_CHMOD} $(W_BIN)/wrapper install-scripts: install-cf @-test -d $(W_BIN)/Tools || mkdir $(W_BIN)/Tools cp contrib/archive2.pl $(W_BIN)/Tools @-test -d $(W_BIN)/bin || mkdir $(W_BIN)/bin cp approve bounce medit $(W_BIN)/bin cp bounce-remind config_parse.pl majordomo \ majordomo.pl majordomo_version.pl\ new-list request-answer resend resend.README shlock.pl \ digest/digest \ $(W_BIN) # the install.cf target will install the sample config file in the # proper place unless a majordomo.cf file exists in whcih case the # majordomo.cf file will be used. install-cf: (test ! -f majordomo.cf && echo "using sample.cf" && \ cp sample.cf $(W_BIN)/majordomo.cf; exit 0) (test -f majordomo.cf && echo "using majordomo.cf" && \ cp majordomo.cf $(W_BIN)/majordomo.cf; exit 0) install-man: @-test -d $(W_BIN)/man || mkdir $(W_BIN)/man @-test -d $(W_BIN)/man/man1 || mkdir $(W_BIN)/man/man1 @-test -d $(W_BIN)/man/man8 || mkdir $(W_BIN)/man/man8 cp Doc/man/approve.1 $(W_BIN)/man/man1 cp Doc/man/majordomo.8 $(W_BIN)/man/man8 install-shared: install-wrapper-shared install-scripts install-wrapper-shared: wrapper @test -d $(W_BIN)/wrappers || mkdir $(W_BIN)/wrappers @test -d $(W_BIN)/wrappers/$(W_GROUP) || mkdir $(W_BIN)/wrappers/$(W_GROUP) strip wrapper cp wrapper $(W_BIN)/wrappers/$(W_GROUP)/wrapper.`arch` cp wrapper.sh $(W_BIN)/wrappers/$(W_GROUP)/wrapper @echo 'run make permissions-shared' as root to set permissions install-archive: cp contrib/archive.pl $(W_BIN)/archive install-archive2: cp contrib/archive2.pl $(W_BIN)/archive install-archive_mh: cp contrib/archive_mh.pl $(W_BIN)/archive permissions-shared: chown ${W_CHOWN} $(W_BIN)/wrappers/$(W_GROUP)/wrapper.`arch` chown ${W_CHOWN} $(W_BIN)/. chmod ${W_CHMOD} $(W_BIN)/wrappers/$(W_GROUP)/wrapper.`arch` wrapper: wrapper.c cc ${WRAPPER_FLAGS} -o wrapper wrapper.c clean: rm -f wrapper *~ dist-clean: clean rm -f majordomo.cf .cvsignore todo.local .dcl archive rm -rf regress Doc/samples Tools distribution: dist-clean mkdir majordomo-1.92 mv * .??* majordomo-1.92 || exit 0 rm -rf majordomo-1.92/CVS majordomo-1.92/*/CVS majordomo-1.92/*/*/CVS tar -cZvf /home/ftp/pub/rouilj/majordomo-1.92.tar.Z majordomo-1.92 ========================================================================== Passwd entry: majordomo:x:1001:50:MajorD:/files1/admin/majordomo/majordomo-1.92/bin:/bin/csh From majordomo-users-owner Thu Aug 4 00:21:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id AAA19675; Thu, 4 Aug 1994 00:21:28 GMT Received: from sparc by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA19669; Wed, 3 Aug 1994 17:21:15 -0700 Received: by sparc (5.0/SMI-SVR4) id AA15665; Wed, 3 Aug 1994 21:22:58 +0400 Date: Wed, 3 Aug 1994 21:22:58 -0300 (ADT) From: Steve MacLeod Subject: Returned mail: unknown mailer error 4 (fwd) To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 1384 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I grabbed majordomo-1.92 and reads the docs, when I tried to generate the wrapper for my system (Solaris 2.3) I used the POSIX flags section. However unless I let the wrapper run with setuid to root I get errors from my mailer... I told sendmail.cf to allow majordomo as a trusted user, no difference, edited the Makefile and used user bin .. no difference ... I would rather not run as user root ... any ideas? Thanks sm -------------------------------------------------------------------- Steve MacLeod Microcomputer Specialist (902)539-5300x625 Computer Centre University College of Cape Breton Sydney, N.S. Fax (902)562-0119 Canada B1P 5S2 ---------- Forwarded message ---------- Date: Wed, 3 Aug 1994 21:08:45 +0400 From: Mail Delivery Subsystem To: Postmaster@sparc Subject: Returned mail: unknown mailer error 4 ----- Transcript of session follows ----- 554 "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l sample -f Sample-Owner -h sparc.uccb.ns.ca -s sample-outgoing"... unknown mailer error 4 ----- Message header follows ----- Return-Path: Received: by sparc (5.0/SMI-SVR4) id AA15517; Wed, 3 Aug 1994 21:08:45 +0400 Date: Wed, 3 Aug 1994 21:08:45 +0400 From: root (0000-Admin(0000)) Message-Id: <9408040008.AA15517@sparc> Errors-To: smacleod Apparently-To: sample content-length: 8 From majordomo-users-owner Thu Aug 4 11:34:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA24271; Thu, 4 Aug 1994 11:34:14 GMT Received: from letterbox.rl.ac.uk by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id EAA24265; Thu, 4 Aug 1994 04:34:05 -0700 Message-Id: <199408041134.EAA24265@mycroft.GreatCircle.COM> Received: from dudley.te.rl.ac.uk by letterbox.rl.ac.uk with SMTP (PP) id ; Thu, 4 Aug 1994 12:35:35 +0100 X-Sender: dhl@rcru1.te.rl.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 04 Aug 1994 11:38:25 +0100 To: majordomo-users@GREATCIRCLE.COM, Steve MacLeod From: dhl@sa.rl.ac.uk (Dudley Long) X-Mailer: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk From majordomo-users-owner Thu Aug 4 13:27:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA25286; Thu, 4 Aug 1994 13:27:22 GMT Received: from polo.iquest.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA25280; Thu, 4 Aug 1994 06:27:04 -0700 Received: by polo.iquest.com (Linux Smail3.1.28.1 #1) id m0qW2po-002EhPC; Thu, 4 Aug 94 08:27 CDT Received: from cc:Mail by multi.iquest.com id AA776014178 Thu, 04 Aug 94 08:29:38 Date: Thu, 04 Aug 94 08:29:38 From: "Dougal Campbell" Encoding: 721 Text Message-Id: <9407047760.AA776014178@multi.iquest.com> To: majordomo-users@GreatCircle.COM Subject: Majordomo, MTAs, and headers.... Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk When resend (or digest) adds headers to a message, it only uses newlines to signal EOL, yes? Shouldn't it use a CRLF combo as specified in RFC822 (did I get the right RFC num? I forget sometimes....) The reason I ask is that when I receive mail at my day job (in cc:Mail for Windows, through a UUCP link), it often shows up with a mutated From: line which has the next few headers appended to it. The CRLF speculation is the only thing I've been able to come up with as a reason for it. Even if I don't hear anything on this subject, I'll probably hack on the code a bit this afternoon to test my theory. Dougal Campbell dougal@multi.iquest.com owner-majordomo@magellan.iquest.com From majordomo-users-owner Thu Aug 4 13:29:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA25304; Thu, 4 Aug 1994 13:29:49 GMT Received: from ssi.edc.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA25298; Thu, 4 Aug 1994 06:29:38 -0700 Received: from ssi.edc.org by ssi.edc.org id aa07152; 4 Aug 94 9:33 EDT Date: Thu, 4 Aug 1994 09:33:12 -400 (EDT) From: Gunther Anderson Subject: Resend adds empty parameter to sendmail 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 Sorry for the impudence of sending a question message only seconds after subscribing, but I found no mention of this in the documentation or mailing list archives on GreatCircle. I am trying to get Majordomo running on a SCO Unix SYSV r3.2 v 4.2 system, with the full standard Development System. The new Perl built properly, and things like wrapper and the majordomo program itself work just fine. I have a problem with a strange interaction between resend and /usr/lib/sendmail. sendmail, on SCO systems equipped with MMDF, is not a true sendmail, but a lobotomized stub, used as a front-end for /usr/mmdf/bin/submit. For most simple operations, it suffices. In fact, it would suffice here, as well, if only the parameters were at issue. The problem is that, if you hand sendmail an empty parameter on the command line, it treats it as an address to send to. Rather than immediately rejecting that address as illegal, it hangs, trying to resolve it. I've checked sendmail on other systems, and it just ignores the extra parameter. resend adds an extra, empty parameter on the end of its sendmail invocation, so whenever I invoke resend, the Majordomo processing hangs. Eventually the job times out, and the message is stuck into the delay queue, to come up and haunt me ten minutes later. Has anyone else with SCO and/or MMDF run into and solved this problem? If not, how would I go about arbitrarily stripping off the last parameter from the sendmail invocation? Thanks in advance, Gunther Anderson From majordomo-users-owner Thu Aug 4 15:54:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA26317; Thu, 4 Aug 1994 15:54:28 GMT Received: from ssi.edc.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA26311; Thu, 4 Aug 1994 08:53:58 -0700 Received: from ssi.edc.org by ssi.edc.org id aa12139; 4 Aug 94 11:57 EDT Date: Thu, 4 Aug 1994 11:57:26 -400 (EDT) From: Gunther Anderson Subject: MMDF, sendmail, From: problems 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 OK, I solved my last problem, and it's left me with a question. My last problem involved MMDF's sendmail, and an empty parameter on the end of the command which was being interpreted as a "to" address, and hanging. I fixed that, but I don't understand where the problem came from. At the very end of resend, is the subroutine sub do_exec_sendmail { exec(@_, ""); die("Failed to exec mailer \"@_\": $!"); } Note the exec() line, which calls the program "@_" (which is a list generated from the sendmail invocation command defined previously), and "". It's the extra "" which is killing my sendmail. I removed it, and my system seems to be working properly now. Why was it there in the first place? It doesn't change the behavior of exec(), since @_ has more than one value in the array. Removing it seemed to have no ill effects, but I wonder nonetheless. But now I've hit the wall. I've got all the pieces working in Majordomo, but MMDF keeps rewriting my "From:" addresses to be the "From " (envelope header) addresses, making every entry to a mailing list which goes through resend show up as "From: owner-listname". This is not good, as all reference to the actual author of the message is lost. Does anyone have diffs to resend, or knowledge of MMDF, to make this work? I can't abandon Majordomo at this stage. Gunther Anderson From majordomo-users-owner Thu Aug 4 17:49:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA27302; Thu, 4 Aug 1994 17:49:01 GMT Received: from snyflcc.fingerlakes.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id KAA27296; Thu, 4 Aug 1994 10:47:33 -0700 Received: from localhost (krampwd@localhost) by snyflcc.fingerlakes.edu (8.6.5/8.6.5) id NAA18104; Thu, 4 Aug 1994 13:40:56 -0400 Date: Thu, 4 Aug 1994 13:40:55 -0400 (EDT) From: "William D. Kramp" Subject: configuration problem To: majordomo-users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have just loaded majordomo on a BSDI v1.1 system, but there is a little problem. When I try the "echo" test given in the manual, I get an error message when it runs the aliases file for [majordomo: "|/usr/local/majordomo/bin/wrapper majordomo"]. I get the message file not found. I have also tried adding the full path for majordomo, but I then get a violation error (wrapper complaining). I know the solution is staring me in the face, but I don't know what it is. thanks. +===============================================================+ | Bill Kramp - System Admin. Finger Lakes Community College | | krampwd@snyflcc.fingerlakes.edu | +===============================================================+ From majordomo-users-owner Thu Aug 4 14:18:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA28914; Thu, 4 Aug 1994 20:49:19 GMT Received: from sashimi.wwa.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA28900; Thu, 4 Aug 1994 13:48:58 -0700 Received: from hp1 by sashimi.wwa.com with uucp (Smail3.1.28.1 #8) id m0qW9nN-000bmmC; Thu, 4 Aug 94 15:53 CDT Received: by hp1.holl.com (/\==/\ Smail3.1.25.1 #25.2) id ; Thu, 4 Aug 94 15:46 CDT Message-Id: From: dave@holl.com (David Vrona) Subject: something very strange To: majordomo-users@greatcircle.com Date: Thu, 4 Aug 1994 15:46:48 -0600 (CDT) X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 998 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, I was reading some email today when suddenly all (and I mean all) of the August postings from a mailing list I maintain starting showing up in my in box. This was about 35 messages when it finished. I have never seen such a thing. The postings looked normal but they were exact duplicates of what had been already sent from 8/1 to 8/4. Is it possible to get majordomo to spit out each and every message in an archive? This is the only way I can explain such an event. Or, is it possible that this was a malicious act from someone on the list in question? I'm thankful it was near the beginning of the month!!!! dave -- David Vrona N9QNZ +1 708 680 2829 (voice) Hollister Incorporated +1 708 918 3860 (fax) 2000 Hollister Drive Internet: dave@hp1.holl.com Libertyville, IL 60048-3781 UUCP: {well connected}!gagme!hp1!dave Opinions expressed are my own and not those of Hollister Incorporated. From majordomo-users-owner Thu Aug 4 21:50:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA29487; Thu, 4 Aug 1994 21:50:54 GMT Received: from keeper.nmr.varian.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA29481; Thu, 4 Aug 1994 14:50:47 -0700 Received: from [132.190.40.12] (pizza.nmr.varian.com) by keeper.nmr.varian.com (4.1/SMI-4.1) id AA28591; Thu, 4 Aug 94 14:51:45 PDT Message-Id: <9408042151.AA28591@keeper.nmr.varian.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 4 Aug 1994 14:56:52 -0700 To: majordomo-users@GreatCircle.COM From: saeedi@netcom.com (Steve Saeedi) Subject: Re: something very strange Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk At 3:46 PM 8/4/94 -0600, David Vrona wrote: >Hi all, > >I was reading some email today when suddenly all (and I mean all) of the >August postings from a mailing list I maintain starting showing up in my in >box. This was about 35 messages when it finished. > >I have never seen such a thing. The postings looked normal but they were >exact duplicates of what had been already sent from 8/1 to 8/4. > >Is it possible to get majordomo to spit out each and every message in an >archive? This is the only way I can explain such an event. I would like to know about this one as well. - Steve From majordomo-users-owner Thu Aug 4 22:20:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id WAA29732; Thu, 4 Aug 1994 22:20:05 GMT Received: from pacificu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA29718; Thu, 4 Aug 1994 15:19:34 -0700 Received: by pacificu.edu (4.1/SMI-SVR4) id AA04202; Thu, 4 Aug 94 15:21:50 PDT Date: Thu, 4 Aug 1994 15:21:49 -0700 (PDT) From: Jeb Weisman Subject: mailing list security 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 Though we are majordomo users here, we run only one, closed, list available to users outside the University. That said we have recently experienced a security problem that though not limited to majordomo, may be of interest to administrators. Apparently a site running a significant list for managers of a specific brand of UNIX system has had it's subscription list subverted. It appears that many of the sites on the list are being systematically probed for a recently reported problem with ftp. The sites are quite specific to those subscribed to the mailing list. We are in contact with the site's administrator about this. The relevant detail here is that many new users have noted that the only way they could get majordomo to work was by using perms 777 or something similar, allowing world reads. If indeed the list subversion we are talking about here has taken place, it may well have been made easier by world readable lists. Granted, there are many other legitimate and non-legitimate ways to get such info. Nonetheless, if you are maintaining a subscriber list with some level of sensitivity, be aware that this may be a problem. -Jeb Weisman +---------------------------------------------------------------+ | Jeb Weisman weisman@pacificu.edu | | Systems Administrator/ (503)359-2927 (vox) | | Internet User Services (503)359-2242 (fax) | | Academic Computing | | Pacific University Forest Grove, OR 97116 | +---------------------------------------------------------------+ From majordomo-users-owner Fri Aug 5 01:25:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA02339; Fri, 5 Aug 1994 01:25:04 GMT Received: from sparc by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA02331; Thu, 4 Aug 1994 18:24:55 -0700 Received: by sparc (5.0/SMI-SVR4) id AA23553; Thu, 4 Aug 1994 22:26:32 +0400 Date: Thu, 4 Aug 1994 22:26:31 -0300 (ADT) From: Steve MacLeod Subject: ftpmail services ?? To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 712 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi All ... I am interested in some of the more indexing, archiving, and digest features of majordomo. Should a first step be to install ftpmail on my system or can I just point to the ftpmail@decwrl site? If I can point do I just have a DNS entry for my anon ftp site and toss the appropriate files in there ??? I didn't see much documentation on these features, is there anything on this in the docs that come with the 1.92 distribution? Thanks -------------------------------------------------------------------- Steve MacLeod Microcomputer Specialist (902)539-5300x625 Computer Centre University College of Cape Breton Sydney, N.S. Fax (902)562-0119 Canada B1P 5S2 From majordomo-users-owner Fri Aug 5 03:34:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id DAA03466; Fri, 5 Aug 1994 03:34:37 GMT Received: from gateway.sandelman.ocunix.on.ca by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA03457; Thu, 4 Aug 1994 20:34:23 -0700 Received: from latour.sandelman.ocunix.on.ca (latour.sandelman.ocunix.on.ca [192.139.46.129]) by gateway.sandelman.ocunix.on.ca (8.6.9/8.6.9) with SMTP id XAA11275 for ; Thu, 4 Aug 1994 23:32:53 -0400 Received: from localhost by latour.sandelman.ocunix.on.ca with SMTP id AA28336 sender mcr@latour.sandelman.ocunix.on.ca (5.65a/IDA-1.4.2); Thu, 4 Aug 94 19:46:15 -0400 Message-Id: <9408042346.AA28336@latour.sandelman.ocunix.on.ca> To: majordomo-users@greatcircle.com Subject: Re: Welcome to bounces In-Reply-To: Your message of "Thu, 04 Aug 1994 23:57:56 GMT." <199408042357.XAA01272@mycroft.GreatCircle.COM> Date: Thu, 04 Aug 1994 19:46:12 -0400 From: Michael Richardson Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >>>>> "Majordomo" == Majordomo writes: Majordomo> -- Majordomo> Welcome to the bounces mailing list! Majordomo> If you ever want to remove yourself from this mailing Majordomo> list, send the following command in email to Majordomo> "Majordomo@GreatCircle.COM": Majordomo> unsubscribe bounces mcr@sandelman.ocunix.on.ca Majordomo> (940804 majordomo-users) While I'm not sure why my address started bouncing (unless it was a power storm over the weekend that put my router into a weirdo state while *I* was camping in the rain), I really like this way of being notified about bounces. COOL! :!mcr!: | "Elegant and extremely rapid for calculation are the Michael Richardson | techniques of Young tableaux. They also have the merit NCF: aa714 || xx714 /of being fun to play with." - p.47 Intro to Quarks&Partons Home: mcr@sandelman.ocunix.on.ca From majordomo-users-owner Fri Aug 5 14:21:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA07672; Fri, 5 Aug 1994 14:21:58 GMT Received: from ssi.edc.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA07666; Fri, 5 Aug 1994 07:21:46 -0700 Received: from ssi.edc.org by ssi.edc.org id aa28748; 5 Aug 94 10:25 EDT Date: Fri, 5 Aug 1994 10:25:23 -400 (EDT) From: Gunther Anderson Subject: Getting MMDF and Majordomo to work 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 spent the last week getting Majordomo to work fully and properly with MMDF, and following are the lessons I've learned. Since I've found a dearth of information about MMDF and Majordomo in the list archives and documentation available, I thought I'd post this in its entirety, in hopes it helps someone else in similar straits. Gunther Anderson Unix System Administrator Education Development Center --------My Lessons-------- Majordomo can be fully utilized in a MMDF II 43b environment, it's just not easy. There are a number of features in both pieces which need to be overcome. First and foremost, you must repair two problems with the interaction between Majordomo's resend and MMDF's sendmail stub. At the end of resend, you will find the line exec(@_, ""); in the do_exec_sendmail routine. The extra "" as a passed parameter does no good, as a quick perusal through the Perl man pages will tell you. It's not at all clear why it's there. But it is clear that passing a null parameter to sendmail in MMDF causes it to hang. Change the line to read instead exec(@_); The next problem is a little more severe, and a lot harder to fix. If you have the source to your MMDF, you're in luck. If you don't, just grit your teeth and bull it through. Because MMDF's sendmail has one honest-to-goodness bug, specifically in the way it handles the -f{sender} parameter. Normal sendmail uses the -f parameter to specify the envelope "From " header (the SMTP 'Mail From:' command) only. MMDF's sendmail deliberately uses the -f parameter not only for the "From " header, but also to rewrite the message-level "From:" header. In mailing lists, this means that the record of the original author of any message passing through resend is totally lost. This is bad. What you have to do is modify uip/other/sendmail.c, and then somehow manage to get it compiled. So, one thing at a time. First, get and unpack the MMDF II 43b source. If you already have it, and have used it to build your system, wonderful. You can ignore all sorts of things in the next few paragraphs. If not, we have some work to do. cd to uip/other, and apply the following diff to the file sendmail.c. ------------CUT HERE------------ *** sendmail.old.c Fri Oct 10 15:16:57 1986 --- sendmail.c Fri Aug 5 06:46:28 1994 *************** *** 28,33 **** --- 28,34 ---- int extract; int badaddrs; int rewritefrom; + int gotafrom; int die(); *************** *** 93,104 **** continue; } } ! if (rewritefrom) { syserr("More than one \"from\" person"); continue; } from = p; ! rewritefrom++; continue; case 'F': /* set full name */ --- 94,105 ---- continue; } } ! if (gotafrom) { syserr("More than one \"from\" person"); continue; } from = p; ! gotafrom++; continue; case 'F': /* set full name */ *************** *** 151,157 **** syserr("Verify mode not supported on header components"); strcpy(subflags, "ml"); ! if (rewritefrom) strcat(subflags, "t"); if (watch) strcat(subflags, "w"); --- 152,158 ---- syserr("Verify mode not supported on header components"); strcpy(subflags, "ml"); ! if (rewritefrom || gotafrom) strcat(subflags, "t"); if (watch) strcat(subflags, "w"); ----------CUT HERE--------- This little patch prevents sendmail from actively rewriting the "From:" header, so that the original authors are preserved. Now, you get to rebuild sendmail. Ignore this if you already know how. cd to the .../mmdf2/conf directory. There you will find a bunch of configuration directories. Find one that matches you. I couldn't. Actually, I wound up modifying the files in the bbn directory. sendmail.c only uses the Makefile.com file, and in that you need only deal with the C preprocessor directives, the host name, and the library files. Anyway, use your intelligence, read the other Makefile.com's, and get something that works. When you've got a Makefile.com that you think works, execute the command: $ sh sitesetup bbn from within the conf directory. Instead of bbn, of course, type whatever directory you were working with. This will copy the revised configuration files where they need to go. Then cd back to .../mmdf2/uip/other, and execute the command $ ./gen xsendmail Yes, the 'x' is important. Anyway, you have a new sendmail, named xsendmail, in that directory. If your compile didn't work, make the appropriate changes in the ../../Makefile.com (like missing libraries), and rerun ./gen. Since I don't trust anything I compiled, I left the original sendmail in /usr/lib, and copied the new xsendmail simply as xsendmail to /usr/lib, and changed the ownership and permissions to match the real sendmail. Finally, edit Majordomo's resend script, and change all references to sendmail to xsendmail, with all the same parameters. Voila, now you have a working Majordomo. There is one more issue, though, that you'll want to consider. If you have, as you might very well want to, Majordomo pointing to an alias which specifies the list channel, the list channel will rewrite your envelope header again. Thankfully, it doesn't change the message From: header. Let me show you what I mean. If you have an series of entries in your aliases.list which look like this: testlist: "majordom|/usr/local/majordomo/bin/wrapper resend ... testlist-tem" testlist-tem: testlist-out@list-processor testlist-out: :include:/usr/local/majordomo/bin/wrapper,testlist-archive ...and so forth... thus explicitly using the list channel, the list channel will change the envelope "From " header from "owner-testlist" as Majordomo would have it, to "testlist-request". This affects things like bounce messages. If you want to use the list channel (check the man pages for its advantages), you'll need to be careful about using the -request address. If, on the other hand, you have entries which look like this: testlist: "majordom|/usr/local/majordomo/bin/wrapper resend ... testlist-out" testlist-out: :include:/usr/local/majordomo/bin/wrapper,testlist-archive ...and so forth... thereby going straight into the appropriate delivery channel, and bypassing the list channel, your envelope header will remain unchanged. Huge lists, though, will really want to think about the list channel, or about finding another way of deferring delivery. There aren't many options. Read the list man page if you haven't already. Finally, make sure "aliases.list" is "trusted" in your mmdftailor file. From majordomo-users-owner Fri Aug 5 14:38:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA07771; Fri, 5 Aug 1994 14:38:49 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA07754; Fri, 5 Aug 1994 07:38:13 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HFJRU7CQQO004AVK@SYSWRK.UCIS.DAL.CA>; Fri, 5 Aug 1994 11:41:55 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HFJRTUXGV400XLEZ@AC.DAL.CA>; Fri, 5 Aug 1994 11:41:40 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA26586; Fri, 5 Aug 94 11:34:35 -0300 Date: Fri, 05 Aug 1994 11:34:35 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Re: something very strange In-reply-to: from "David Vrona" at Aug 4, 94 03:46:48 pm To: dave@holl.com (David Vrona) Cc: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9408051434.AA26586@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: 1208 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >I was reading some email today when suddenly all (and I mean all) of the >August postings from a mailing list I maintain starting showing up in my in >box. This was about 35 messages when it finished. > >I have never seen such a thing. The postings looked normal but they were >exact duplicates of what had been already sent from 8/1 to 8/4. > >Is it possible to get majordomo to spit out each and every message in an >archive? This is the only way I can explain such an event. I've run into this when setting up digests. Although I obviously did something wrong, I've given up on digests because sometimes the mkdigest command causes all of the messages in the digest to be regurgitated to the entire list. So although I don't know exactly what the problem is, it can be a side effect of making digests. I repeat, I'm sure I did something wrong, but I don't know enough perl to debug the process without risking overloading the mailing lists, so I just passed on the digests option. -- 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 Fri Aug 5 17:50:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA09178; Fri, 5 Aug 1994 17:50:06 GMT Received: from atc.boeing.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id KAA09169; Fri, 5 Aug 1994 10:49:52 -0700 Received: by atc.boeing.com (5.57) id AA18385; Fri, 5 Aug 94 10:56:12 -0700 Received: from aw102.iasl.ca.boeing.com.iasl.ca.boeing.com (aw102.iasl.ca.boeing.com) by aw101.iasl.ca.boeing.com with SMTP id AA06153 (5.67a/IDA-1.4.4 for ); Fri, 5 Aug 1994 10:53:12 -0700 From: "Vincent D. Skahan" Received: by aw102.iasl.ca.boeing.com.majordomo-users@greatcircle.com (5.65c/client-1.3) id AA05300; Fri, 5 Aug 1994 10:53:11 -0700 Message-Id: <199408051753.AA05300@aw102.iasl.ca.boeing.com.majordomo-users@greatcircle.com> Subject: mailer error 2 (majordomo1.92 under Linux) To: majordomo-users@greatcircle.com Date: Fri, 5 Aug 1994 10:53:10 -0700 (PDT) X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 1250 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm trying to get v1.92 to work under Linux (using sendmail5.67b+IDA1.5) and any mail to majordomo gets the following bounce...any ideas ? -- ----------- Vince Skahan ------ vds7789@aw101.iasl.ca.boeing.com ----------- will perl for junk food... Forwarded message: >From MAILER-DAEMON Fri Aug 5 02:41:30 1994 Date: Thu, 4 Aug 1994 19:41:38 -0700 From: Mail Delivery Subsystem Message-Id: <199408050241.AB01094@victrola.wa.com> To: Postmaster Subject: Returned mail: unknown mailer error 2 ----- Transcript of session follows ----- 554 "|/site/sw/majordomo/wrapper majordomo"... unknown mailer error 2 ----- Recipients of this delivery ----- Bounced, cannot deliver: "|/site/sw/majordomo/wrapper majordomo" Sent successfully: majordomo mailing-lists ----- Message header follows ----- Received: by victrola.wa.com id AA01094 (5.67b/IDA-1.4.4 for majordomo); Thu, 4 Aug 1994 19:41:38 -0700 From: majordom Message-Id: <199408050241.AA01094@victrola.wa.com> Subject: test To: majordomo Date: Thu, 4 Aug 1994 19:41:30 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 9 From majordomo-users-owner Fri Aug 5 18:12:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA09343; Fri, 5 Aug 1994 18:12:00 GMT Received: from atc.boeing.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA09336; Fri, 5 Aug 1994 11:11:52 -0700 Received: by atc.boeing.com (5.57) id AA21382; Fri, 5 Aug 94 11:18:16 -0700 Received: from aw102.iasl.ca.boeing.com.iasl.ca.boeing.com (aw102.iasl.ca.boeing.com) by aw101.iasl.ca.boeing.com with SMTP id AA06382 (5.67a/IDA-1.4.4); Fri, 5 Aug 1994 11:15:24 -0700 From: "Vincent D. Skahan" Received: by aw102.iasl.ca.boeing.com. (5.65c/client-1.3) id AA05363; Fri, 5 Aug 1994 11:15:22 -0700 Message-Id: <199408051815.AA05363@aw102.iasl.ca.boeing.com.> Subject: Re: mailing list security To: weisman@pacificu.edu (Jeb Weisman) Date: Fri, 5 Aug 1994 11:15:21 -0700 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Jeb Weisman" at Aug 4, 94 03:21:49 pm X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 1347 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk (Jeb Weisman writes:) > Apparently a site running a significant list for managers of a specific > brand of UNIX system has had it's subscription list subverted. It > appears that many of the sites on the list are being systematically > probed for a recently reported problem with ftp. The sites are quite > specific to those subscribed to the mailing list. > > The relevant detail here is that many new users have > noted that the only way they could get majordomo to work was by using > perms 777 or something similar, allowing world reads. If indeed the list > subversion we are talking about here has taken place, it may well have > been made easier by world readable lists. Can John give us all the definitive word on how the ownership and permissions need to be set up for v1.92 under both the Posix and 'not Posix' case ? - the majordomo stuff - the mailing lists - mailing list archives - mailing list digests In particular, I was concerned (maybe needlessly) about the line in the v1.92 readme file that says that wrapper needs to be setuid to a user who is 'trusted' in sendmail.cf. I wasn't certain what the owner.group for wrapper and mode should be for Posix vs. non-Posix o/s's. -- ----------- Vince Skahan ------ vds7789@aw101.iasl.ca.boeing.com ----------- will perl for junk food... From majordomo-users-owner Fri Aug 5 23:26:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA12008; Fri, 5 Aug 1994 23:26:25 GMT Received: from sparc by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA11999; Fri, 5 Aug 1994 16:26:14 -0700 Received: by sparc (5.0/SMI-SVR4) id AA28710; Fri, 5 Aug 1994 20:27:53 +0400 Date: Fri, 5 Aug 1994 20:27:52 -0300 (ADT) From: Steve MacLeod Subject: Re: mailing list security ... great idea! To: "Vincent D. Skahan" Cc: majordomo-users@greatcircle.com In-Reply-To: <199408051815.AA05363@aw102.iasl.ca.boeing.com.> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 1876 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I think such a review would be of great benefit ... I am running Solaris 2.3 ... I am using the POSIX options ... how can one tell when this is necessary? Thanks -------------------------------------------------------------------- Steve MacLeod Microcomputer Specialist (902)539-5300x625 Computer Centre University College of Cape Breton Sydney, N.S. Fax (902)562-0119 Canada B1P 5S2 On Fri, 5 Aug 1994, Vincent D. Skahan wrote: > (Jeb Weisman writes:) > > Apparently a site running a significant list for managers of a specific > > brand of UNIX system has had it's subscription list subverted. It > > appears that many of the sites on the list are being systematically > > probed for a recently reported problem with ftp. The sites are quite > > specific to those subscribed to the mailing list. > > > > The relevant detail here is that many new users have > > noted that the only way they could get majordomo to work was by using > > perms 777 or something similar, allowing world reads. If indeed the list > > subversion we are talking about here has taken place, it may well have > > been made easier by world readable lists. > > Can John give us all the definitive word on how the ownership and permissions > need to be set up for v1.92 under both the Posix and 'not Posix' case ? > - the majordomo stuff > - the mailing lists > - mailing list archives > - mailing list digests > > In particular, I was concerned (maybe needlessly) about the line in the > v1.92 readme file that says that wrapper needs to be setuid to a user who > is 'trusted' in sendmail.cf. I wasn't certain what the owner.group for > wrapper and mode should be for Posix vs. non-Posix o/s's. > > -- > ----------- Vince Skahan ------ vds7789@aw101.iasl.ca.boeing.com ----------- > will perl for junk food... > From majordomo-users-owner Sat Aug 6 02:33:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA14517; Sat, 6 Aug 1994 02:33:47 GMT Received: from sigma.itu.ch by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA05040; Fri, 5 Aug 1994 01:04:41 -0700 Received: from MR.ITU.CH by ITU.CH (PMDF V4.3-7 #4298) id <01HFJO9I19C096WEAO@ITU.CH>; Fri, 5 Aug 1994 10:11:06 CET Received: with PMDF-MR; Fri, 5 Aug 1994 09:05:45 CET MR-Received: by mta TIES.MUAS; Relayed; Fri, 05 Aug 1994 09:05:45 +0100 MR-Received: by mta TAU; Relayed; Fri, 05 Aug 1994 09:06:02 +0100 Disclose-recipients: prohibited Date: Fri, 05 Aug 1994 09:05:45 +0100 (CET) From: JARLE MARTINSEN +41 22 730 5949 Subject: Can't create output To: Majordomo-users@GreatCircle.COM Message-id: <6245051005081994/A31638/TAU/11882A852B00*@MHS> X-Envelope-to: Majordomo-users@GreatCircle.COM Autoforwarded: false MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Importance: normal Priority: normal UA-content-id: 11882A852B00 X400-MTS-identifier: [;6245051005081994/A31638/TAU] Hop-count: 1 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I got Majordomo-1.92 'almost' up and running on a DEC Alpha 3000/600 And it mostly works OK. One problem though - when sending a mail to a test list (sample) I get the "Can't create output message. The message gets forwarded to all persons on the list + an error message to the list-owner. This occures when a message is sent from both the local or any remote system (to this test list). No entry is logged in the Log file....? help, lists, subscribe and unsubscribe works OK. No error, and an entry is created in Log. % echo asdfsdf|/usr/lib/sendmail -v sample sample... aliased to "|/majordomo-1.92/wrapper resend -l sample -h rhone.itu.ch sample-outgoing" "|/majordomo-1.92/wrapper resend -l sample -h rhone.itu.ch sample-outgoing"... C onnecting to (prog)... about to exec /majordomo-1.92/archive/sample... Can't create output "|/majordomo-1.92/wrapper resend -l sample -h rhone.itu.ch sample-outgoing"... S ent I know this error message has been discussed on this list before, but I cannot seem to find 'the' answer to the problem. All references I've found mention protection.... I've set mod 777 on all files - full access for everything, and still I get this message. (this is a test machine - I'll clean up later) Any information on where to look, and what to look for, would be appriciated. Thanks in advance. Best Regards, /jarle Jarle Martinsen System Analyst International Telecommunication Union (ITU) Geneva - Switzerlane Internet: martinsen@itu.ch X.400: s=martinsen,p=itu,a=arcom,c=ch Voice: +41 22 730 5949 >>> aliases sample: "|/majordomo-1.92/wrapper resend -l sample -h rhone.itu.ch sample-outgoing" owner-sample: sample-owner sample-outgoing: :include:/majordomo-1.92/lists/sample, sample-archive owner-sample-outgoing: sample-owner sample-archive: /majordomo-1.92/archive/sample owner-sample-archive: sample-owner sample-request: "|/majordomo-1.92/wrapper request-answer sample" owner-sample-request: sample-owner sample-approval: jarle sample-owner: jarle owner-sample-owner: jarle >>> ls -lFR /majordomo-1.92 total 318 -rw-r--r-- 1 majordom listserv 498 Aug 2 10:16 .env_file -rw-r--r-- 1 majordom listserv 1524 Aug 2 10:16 .ksh_keypad_aliases -rwxr-xr-x 1 majordom listserv 1639 Aug 2 10:15 .login* -rw-r--r-- 1 majordom listserv 3989 Aug 5 08:55 .pine-debug1 -rw-r--r-- 1 majordom listserv 4011 Aug 5 08:50 .pine-debug2 -rw-r--r-- 1 majordom listserv 3845 Aug 5 08:02 .pine-debug3 -rw-r--r-- 1 majordom listserv 7781 Aug 5 08:55 .pinerc -rwxr-xr-x 1 majordom listserv 1689 Aug 2 10:16 .profile* -rw------- 1 majordom listserv 5450 Aug 5 09:41 .sh_history -rw-r--r-- 1 majordom listserv 31757 Aug 2 11:51 Changelog -rw-r--r-- 1 majordom listserv 12785 Aug 2 11:51 Changes -rw-r--r-- 1 majordom listserv 4601 Aug 2 11:51 Description drwxrwxr-x 3 majordom listserv 512 Aug 2 11:51 Doc/ -rwxrwxrwx 1 majordom listserv 1 Aug 5 09:38 Log* -rw-r--r-- 1 majordom listserv 4375 Aug 4 08:28 Makefile -rw-r--r-- 1 majordom listserv 531 Aug 2 11:51 Manifest -rw-r--r-- 1 majordom listserv 51062 Aug 2 11:51 README drwxrwxrwx 2 majordom listserv 512 Aug 5 09:06 Tools/ -rwxr-xr-x 1 majordom listserv 6195 Aug 2 11:51 approve* drwxrwxrwx 3 majordom listserv 512 Aug 5 09:36 archive/ drwxrwxrwx 2 majordom listserv 512 Aug 4 11:50 bin/ -rwxr-xr-x 1 majordom listserv 2874 Aug 2 11:51 bounce* -rwxr-xr-x 1 majordom listserv 2610 Aug 2 11:51 bounce-remind* -rw-r--r-- 1 majordom listserv 43712 Aug 2 12:02 config_parse.pl drwxrwxrwx 2 majordom listserv 512 Aug 2 11:51 contrib/ drwxrwxrwx 2 majordom listserv 512 Aug 2 11:51 digest/ drwxrwxrwx 4 majordom listserv 512 Aug 5 09:46 lists/ drwxrwxrwx 2 majordom listserv 512 Aug 2 11:51 mail/ -rwxrwxrwx 1 majordom listserv 42445 Aug 3 16:38 majordomo* -rwxrwxrwx 1 majordom listserv 2879 Aug 4 16:00 majordomo.cf* -rw-r--r-- 1 majordom listserv 10889 Aug 2 11:51 majordomo.pl -rw-r--r-- 1 majordom listserv 137 Aug 2 11:51 majordomo_version.pl -rwxr-xr-x 1 majordom listserv 1412 Aug 2 11:51 medit* -rwxr-xr-x 1 majordom listserv 2238 Aug 2 11:51 new-list* -rwxr-xr-x 1 majordom listserv 3017 Aug 2 11:51 request-answer* -rwxr-xr-x 1 majordom listserv 12135 Aug 2 11:51 resend* -rw-r--r-- 1 majordom listserv 3742 Aug 2 11:51 resend.README -rw-r--r-- 1 majordom listserv 2087 Aug 2 11:51 sample.aliases -rw-r--r-- 1 majordom listserv 2901 Aug 2 11:51 sample.cf -rw-r--r-- 1 majordom listserv 6051 Aug 2 11:51 shlock.pl -rwxr-xr-x 1 majordom listserv 16384 Aug 3 17:25 wrapper* -rwxr-xr-x 1 majordom listserv 2331 Aug 3 10:17 wrapper.c* -rwxr-xr-x 1 majordom listserv 223 Aug 2 11:51 wrapper.sh* drwxrwxrwx 2 majordom listserv 512 Aug 3 17:25 wrappers/ majordomo-1.92/Doc: total 232 -rw-r--r-- 1 majordom listserv 14609 May 7 00:04 FAQ -rw-r--r-- 1 majordom listserv 1388 May 6 23:30 README -rw-r--r-- 1 majordom listserv 13475 Mar 14 19:10 list-owner-info -rw-r--r-- 1 majordom listserv 115561 Oct 27 1993 majordomo.lisa6.ps -rw-r--r-- 1 majordom listserv 73565 Apr 9 00:13 majordomo.ora drwxr-xr-x 2 majordom listserv 512 Jun 9 21:57 man/ majordomo-1.92/Doc/man: total 25 -rw-r--r-- 1 majordom listserv 3512 Oct 27 1993 approve.1 -rw-r--r-- 1 majordom listserv 4133 Oct 27 1993 approve.man -rw-r--r-- 1 majordom listserv 6922 May 2 19:33 majordomo.8 -rw-r--r-- 1 majordom listserv 8836 May 2 19:39 majordomo.man majordomo-1.92/Tools: total 0 majordomo-1.92/archive: total 1 drwxrwxrwx 2 majordom listserv 512 Aug 5 09:36 sample/ majordomo-1.92/archive/sample: total 0 majordomo-1.92/bin: total 0 majordomo-1.92/contrib: total 32 -rwxr-xr-x 1 majordom listserv 3185 Sep 1 1993 archive.pl* -rwxr-xr-x 1 majordom listserv 4289 Mar 6 23:44 archive2.pl* -rwxr-xr-x 1 majordom listserv 839 Sep 1 1993 archive_mh.pl* -rw-r--r-- 1 majordom listserv 10021 Apr 22 21:20 digest.diff -rwxr-xr-x 1 majordom listserv 674 Apr 3 00:36 digest.send* -rwxr-xr-x 1 majordom listserv 3201 Apr 22 20:22 logsummary.pl* -rwxr-xr-x 1 majordom listserv 2742 Apr 22 20:57 makeindex.pl* -rw-r--r-- 1 majordom listserv 3251 May 3 00:02 mod_addr.diff majordomo-1.92/digest: total 31 -rwxrwxrwx 1 majordom listserv 1697 Jan 19 1994 Makefile* -rwxrwxrwx 1 majordom listserv 1351 Jan 19 1994 README* -rwxrwxrwx 1 majordom listserv 1528 Jan 19 1994 aliases.slice* -rwxrwxrwx 1 majordom listserv 9720 May 9 02:00 digest* -rwxrwxrwx 1 majordom listserv 1231 Jan 19 1994 firewalls-digest.cf* -rwxrwxrwx 1 majordom listserv 174 Jan 19 1994 firewalls-digest.header* -rwxrwxrwx 1 majordom listserv 3 Jan 19 1994 firewalls-digest.num* -rwxrwxrwx 1 majordom listserv 777 Jan 19 1994 firewalls-digest.trailer* -rwxrwxrwx 1 majordom listserv 2 Jan 19 1994 firewalls-digest.vol* -rwxrwxrwx 1 majordom listserv 6058 Jan 19 1994 shlock.pl* -rwxrwxrwx 1 majordom listserv 2349 Jan 19 1994 wrapper.c* majordomo-1.92/lists: total 22 -rwxrwxrwx 1 majordom listserv 35 Aug 2 10:04 hello* drwxrwxrwx 2 majordom listserv 512 Aug 2 10:04 hello.archive/ -rwxrwxrwx 1 majordom listserv 7815 Aug 2 10:04 hello.config* -rwxrwxrwx 1 majordom listserv 47 Aug 2 10:04 hello.info* -rw-rw-r-- 1 majordom listserv 6 Aug 5 08:54 sample drwxrwxrwx 2 majordom listserv 512 Aug 2 10:04 sample.archive/ -rwxrwxrwx 1 majordom listserv 7812 Aug 4 11:43 sample.config* -rwxrwxrwx 1 majordom listserv 47 Aug 2 10:04 sample.info* majordomo-1.92/lists/hello.archive: total 0 majordomo-1.92/lists/sample.archive: total 1 -rwxrwxrwx 1 majordom listserv 9 Aug 2 10:04 testsample* majordomo-1.92/mail: total 0 -rw-rw-rw- 1 majordom listserv 0 Aug 2 11:26 saved-messages -rw-rw-rw- 1 majordom listserv 0 Aug 2 11:26 sent-mail majordomo-1.92/wrappers: total 0 >>> cat majordomo.cf # $whereami -- What machine am I running on? $whereami = "rhone.itu.ch"; # $whoami -- Who do users send requests to me as? $whoami = "Majordomo@$whereami"; # $whoami_owner -- Who is the owner of the above, in case of problems? $whoami_owner = "Majordomo-Owner@$whereami"; # $homedir -- Where can I find my extra .pl files, like majordomo.pl? # the environment variable HOME is set by the wrapper if ( defined $ENV{"HOME"}) { $homedir = $ENV{"HOME"}; } else { $homedir = "/majordomo-1.92"; } # $listdir -- Where are the mailing lists? $listdir = "/majordomo-1.92/lists"; # $digest_work_dir -- the parent directory for digest's queue area # Each list must have a subdirectory under this directory in order for # digest to work. E.G. The bblisa list would use: # /usr/local/mail/digest/bblisa # as its directory. $digest_work_dir = '/majordomo-1.92/digest'; # $log -- Where do I write my log? $log = "$homedir/Log"; # $mailer -- What program and args do I use to send mail? # The variable $to can be interpolated into this command line, # however the $to variable is provided by the person sending mail, # and much mischief can be had by playing with this variable. # Use $to with care. $mailer = "/usr/lib/sendmail -f\$sender -t"; # Majordomo will look for "get" and "index" files related to $list in # directory "$filedir/$list$filedir_suffix", so set $filedir and # $filedir_suffix appropriately. For instance, to look in # /usr/local/mail/files/$list, use: # $filedir = "/usr/local/mail/files"; # $filedir_suffix = ""; # empty string # or to look in $listdir/$list.archive, use: # $filedir = "$listdir"; # $filedir_suffix = ".archive"; $filedir = "$listdir"; $filedir_suffix = ".archive"; # What command should I use to process an "index" request? $index_command = "/bin/ls -lRL"; # If you want to use FTPMAIL, rather than local access, for file transfer # and access, define the following: # $ftpmail_address = "ftpmail@decwrl.dec.com"; # $ftpmail_location = "FTP.$whereami"; # if you want the subject of the request to be included as part of the # subject of the reply (useful when automatically testing, or submitting # multiple command sets), set $return_subject to 1. $return_subject = 1; # If you are using majordomo at the -request address, set the # following variable to 1. This affects the welcome message that is # sent to a new subscriber as well as the help text that is generated. $majordomo_request = 0; # Set the umask for the process. Used to set default file status for # config file. umask(007); # the safe locations for archive directories # None of the parameters that use safedirs are actually used, so # @safedirs is a placeholder for future functionality. # Just ignore it for version 1.90 through 1.92. @safedirs = ( ); 1; # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1 1994/06/09 19:45:18 r ouilj Exp $ 42:rhone:/majordomo-1.92# From majordomo-users-owner Fri Aug 5 20:17:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA14057; Sat, 6 Aug 1994 02:07:50 GMT Received: from math.mps.ohio-state.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id FAA24646; Thu, 4 Aug 1994 05:09:13 -0700 Received: (from alden@localhost) by math.mps.ohio-state.edu (8.6.8/8.6.9) id IAA09958; Thu, 4 Aug 1994 08:13:05 -0400 From: Dave Alden Message-Id: <199408041213.IAA09958@math.mps.ohio-state.edu> Subject: Re: Problem using majordomo under Solaris 2.3 To: max@megalon.com Date: Thu, 4 Aug 1994 08:13:04 -0400 (EDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199408021010.DAA10917@megalon.com> from "ùmax@megalon.com" at Aug 2, 94 03:10:11 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 737 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, > megalon# Mail -v majordomo > Subject: test > subscribe test1 max [...] > # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1 1994/06/09 19:45:18 rouilj Exp $ > eval of majordomo.cf failed at /files1/admin/majordomo/majordomo-1.92/bin/majordomo line 46. > "|/files1/admin/majordomo/majordomo-1.92/bin/wrapper majordomo"... unknown mailer error 2 > Saving message in /home/max/dead.letter > /home/max/dead.letter... Sent > > Here's line 46 in majordomo: > > eval(`cat $cf`) || die "eval of majordomo.cf failed $@"; Did you recompile your Perl binary for Solaris? I had the same problem with several of my Perl scripts (including Majordomo) -- I had to recompile Perl under Solaris to get it to work correctly. ...dave From majordomo-users-owner Sat Aug 6 12:22:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA17791; Sat, 6 Aug 1994 12:22:57 GMT Received: from home.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id FAA17785; Sat, 6 Aug 1994 05:22:51 -0700 Received: from .interaccess.com (dyna2-25.interaccess.com [198.80.0.214]) by home.interaccess.com (8.6.9/8.6.9) with SMTP id HAA07471 for ; Sat, 6 Aug 1994 07:24:10 -0500 Date: Sat, 6 Aug 1994 07:24:10 -0500 Message-Id: <199408061224.HAA07471@home.interaccess.com> X-Sender: ulysses@interaccess.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@GreatCircle.com From: ulysses@interaccess.com (Dennis Fey) Subject: v. 1.92 digest function X-Mailer: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Users: Our access vendor is upgrading to v 1.92 for our lists. I've been reviewing the readme files and I'm not clear on whether the new digest/functions actually give the SUBSCRIBER the option to set his/her mail to "digest," as with Listserv on many lists. Also, does anyone see anywhere a temporary-stop mail option for subscribers to lists managed by v 1.92? Thanks! Dennis Fey From majordomo-users-owner Sat Aug 6 15:48:16 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA18440; Sat, 6 Aug 1994 15:48:16 GMT Received: from atc.boeing.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA18434; Sat, 6 Aug 1994 08:48:09 -0700 Received: by atc.boeing.com (5.57) id AA27142; Sat, 6 Aug 94 08:54:39 -0700 Received: from aw102.iasl.ca.boeing.com.iasl.ca.boeing.com (aw102.iasl.ca.boeing.com) by aw101.iasl.ca.boeing.com with SMTP id AA11696 (5.67a/IDA-1.4.4 for ); Sat, 6 Aug 1994 08:51:56 -0700 From: "Vincent D. Skahan" Received: by aw102.iasl.ca.boeing.com. (5.65c/client-1.3) id AA07449; Sat, 6 Aug 1994 08:51:57 -0700 Message-Id: <199408061551.AA07449@aw102.iasl.ca.boeing.com.> Subject: Re: mailer error 2 (majordomo1.92 under Linux) To: vds7789@aw101.iasl.ca.boeing.com (Vincent D. Skahan) Date: Sat, 6 Aug 1994 08:51:56 -0700 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199408051753.AA05300@aw102.iasl.ca.boeing.com.majordomo-users@greatcircle.com> from "Vincent D. Skahan" at Aug 5, 94 10:53:10 am X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 288 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk (Vincent D. Skahan writes:) > > I'm trying to get v1.92 to work under Linux (using sendmail5.67b+IDA1.5) > and any mail to majordomo gets the following bounce...any ideas ? > solved. I had perl5a11 installed as /usr/bin/perl. When I switched back to v4.036 it all works just dandy. From majordomo-users-owner Sat Aug 6 18:21:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA18869; Sat, 6 Aug 1994 18:21:29 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA18856; Sat, 6 Aug 1994 11:21:20 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA02855 (5.65c/IDA-1.4.4 for ); Sat, 6 Aug 1994 13:42:02 -0400 Message-Id: <199408061742.AA02855@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: The schedule for rolling out version 1.93 of majordomo Date: Sat, 06 Aug 1994 13:42:01 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all: I have been receiving a lot of requests for the release date for the next majordomo iteration. I am afraid I have some bad news. while I was intending to get it out by the middle of August, something has come up that trashed those plans. For those of you who know me, this may come as a surprise, but I have a permanent full-time sysadmin job now. since I am no longer contracting, the amount of free time I have to work on majordomo had been diminshed. I am now shooting for a release date near the beginning of October. This should provide me with enough time to make use of the info I get at the LISA BOF. If you have been delaying the upgrade to majordomo 1.9x until 1.93 is released, I would say "don't" upgrade now to 1.92. If you get the concepts straight with 1.92, then the transition to 1.93 should be easy. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@cs.umb.edu Waltham, MA (617) 890-7227 x225 Senior Systems Consultant (SERL Project) 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 Sun Aug 7 01:20:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA21567; Sun, 7 Aug 1994 01:20:55 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA21557; Sat, 6 Aug 1994 18:20:45 -0700 Received: from lunch.asd.sgi.com by sgi.sgi.com via SMTP (940627.SGI.8.6.9/910110.SGI) id SAA18118; Sat, 6 Aug 1994 18:24:33 -0700 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:majordomo-users@GreatCircle.COM id AA08607; Sat, 6 Aug 94 18:24:20 -0700 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9408070124.AA08607@lunch.asd.sgi.com> Subject: Re: v. 1.92 digest function To: ulysses@interaccess.com (Dennis Fey) Date: Sat, 6 Aug 1994 18:24:20 -0700 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199408061224.HAA07471@home.interaccess.com> from "Dennis Fey" at Aug 6, 94 07:24:10 am X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 750 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Our access vendor is upgrading to v 1.92 for our lists. I've been reviewing > the readme files and I'm not clear on whether the new digest/functions > actually give the SUBSCRIBER the option to set his/her mail to "digest," as > with Listserv on many lists. Not like listserv. If you make a digest version available, you do so as a separate list. If people want the digest version, they unsubscribe from and subscribe to . > Also, does anyone see anywhere a temporary-stop mail option for subscribers > to lists managed by v 1.92? No. You unsubscribe and resubscribe later, then check the archives for mail you missed. -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Mon Aug 8 13:47:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA04454; Mon, 8 Aug 1994 13:47:01 GMT Received: from ciesin.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA04447; Mon, 8 Aug 1994 06:46:54 -0700 Received: from mail.ciesin.org by ciesin.org with SMTP id AA05415 (5.65c/IDA-1.4.4 for ); Mon, 8 Aug 1994 09:51:02 -0400 Message-Id: <199408081351.AA05415@ciesin.org> To: majordomo-users@greatcircle.com Subject: Approval being asked for now and then Date: Mon, 08 Aug 1994 09:51:01 -0400 From: Jeff Blaine Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Out of the blue, once every month or so with no regularity, I get mail (because I am owner-listname) asking for subscription approval from an open-subscription list. It appears what is happening when this kind of thing happens is that the person's (the one who is subscribing) email address is being broken up into the wrong elements. Today, the unexpected approval message was: Michael Foobar requests that you approve the following: subscribe TheList If you approve, etc etc etc... The ``subscribe TheList '' part makes no sense to me whatsoever, as it should be ``subscribe TheList mfoobar@foobar.EDU'' I wish I had more specifics, but I don't. ------- Jeff Blaine CIESIN Operations From majordomo-users-owner Mon Aug 8 16:41:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA06144; Mon, 8 Aug 1994 16:41:47 GMT Received: from amalthea.tenon.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA06137; Mon, 8 Aug 1994 09:41:17 -0700 Received: by amalthea.tenon.com (5.64/Tenon-1.35.01) id AA00140; Mon, 8 Aug 94 09:23:49 -0700 (PDT) From: grantham@amalthea.tenon.com (Brad Grantham) Message-Id: <9408081623.AA00140@amalthea.tenon.com> Subject: Approval being asked for now and then (fwd) To: majordomo-users@greatcircle.com Date: Mon, 8 Aug 1994 09:23:45 -36507155 (PDT) X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1379 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Jeff Blaine wrote: > > Out of the blue, once every month or so with no regularity, I get mail > (because I am owner-listname) asking for subscription approval from > an open-subscription list. > > It appears what is happening when this kind of thing happens is that > the person's (the one who is subscribing) email address is being > broken up into the wrong elements. Today, the unexpected approval > message was: > > Michael Foobar requests that you approve the > following: > > subscribe TheList > > If you approve, etc etc etc... > > The ``subscribe TheList '' part makes no sense to me > whatsoever, as it should be ``subscribe TheList mfoobar@foobar.EDU'' I think the reason it's sending to you is that the address he is trying to subscribe to the list is different than his return address, which looks as if it was put in the request explicitly. I'm not sure why he would put "", unless he doesn't understand his own email address. It's also reminiscent of BITNET listserv, where you specify your full name to the subscribe command instead of your email address. I would send return mail stating that "" isn't a valid address, and did he just mean to subscribe himself, in which case he doesn't have to specify the mail address in the message. -Brad From majordomo-users-owner Mon Aug 8 18:11:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA07109; Mon, 8 Aug 1994 18:11:56 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA07097; Mon, 8 Aug 1994 11:11:00 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HFO6594AZK004FQW@SYSWRK.UCIS.DAL.CA>; Mon, 8 Aug 1994 15:14:04 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HFO651JNR400R8YY@AC.DAL.CA>; Mon, 8 Aug 1994 15:13:55 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA18167; Mon, 8 Aug 94 15:06:52 -0300 Date: Mon, 08 Aug 1994 15:06:51 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Re: Approval being asked for now and then In-reply-to: <9408081623.AA00140@amalthea.tenon.com> from "Brad Grantham" at Aug 8, 94 09:23:45 am To: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9408081806.AA18167@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: 1410 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >Jeff Blaine wrote: >> >> Today, the unexpected approval message was: >> >> Michael Foobar requests that you approve the >> following: >> >> subscribe TheList >> >> The ``subscribe TheList '' part makes no sense to me >> whatsoever, as it should be ``subscribe TheList mfoobar@foobar.EDU'' > >I think the reason it's sending to you is that the address he is >trying to subscribe to the list is different than his return address, >which looks as if it was put in the request explicitly. >I'm not sure why he would put "", unless he doesn't >understand his own email address. It's also reminiscent of BITNET >listserv, where you specify your full name to the subscribe command >instead of your email address. > >I would send return mail stating that "" isn't a valid >address, and did he just mean to subscribe himself, in which >case he doesn't have to specify the mail address in the message. On the lists I run this is very common, and sure it indicates that the subscriber doesn't know what he is doing. I usually correct the address and enter the subscription, but of course that means that you have a subscriber who may screw up in other ways. It can be tricky telling a subscriber who uses incorrect syntax from one who really needs to subscribe at a different address, so be careful here. From majordomo-users-owner Mon Aug 8 20:06:36 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA08272; Mon, 8 Aug 1994 20:06:36 GMT Received: from ssi.edc.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA08266; Mon, 8 Aug 1994 13:05:49 -0700 Received: from ssi.edc.org by ssi.edc.org id aa07697; 8 Aug 94 16:08 EDT Date: Mon, 8 Aug 1994 16:08:43 -400 (EDT) From: Gunther Anderson Reply-To: Gunther Anderson Subject: unlink in resend script 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 In hacking up Majordomo to work with SCO and MMDF, I noticed one thing which comfused me. There are a few places in resend where unlink is called with a wildcarded filename. For instance, unlink(); Now, on SCO, this failed to delete any of these files. I had to break the line out into specific files, in this case, unlink("/tmp/resend.$$.in"); unlink("/tmp/resend.$$.out"); Is this a problem with SCO's unlink, my Perl build, or the resend script? That is, is it SCO's fault, my fault, or simply par for the course in the wide varieties of Unix out there? Do let me know. I'm very curious. Oh, for those of you who got my last message about making Majordomo work with SCO and MMDF, you will definitely need to check out your unlink behavior, because there's this tiny chance that Majordomo is leaving two copies of _every_message_it_processes_ in your tmp directory. Thanks, Gunther Anderson From majordomo-users-owner Mon Aug 8 23:08:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA10060; Mon, 8 Aug 1994 23:08:40 GMT Received: from infoexp.express.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA10054; Mon, 8 Aug 1994 16:08:31 -0700 Received: from alto.express.com (alto.express.com [199.74.248.4]) by infoexp.express.com (8.6.8/8.6.6) with ESMTP id QAA19767 for ; Mon, 8 Aug 1994 16:12:38 -0700 Received: from [199.74.248.5] (snoopy.express.com [199.74.248.5]) by alto.express.com (8.6.8/8.6.6) with SMTP id QAA23355 for ; Mon, 8 Aug 1994 16:12:15 -0700 Message-Id: <199408082312.QAA23355@alto.express.com> X-Sender: pzee@alto.express.com (Unverified) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 8 Aug 1994 16:14:50 -0800 To: majordomo-users@GreatCircle.COM From: pzee@express.com (Philip J. Zee) Subject: unknown mailer error 5 again Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Sorry to bother you all again. I am very frustrated from installation of majordomo 1.92. Please help me, someone! I am still having unknow mailer error 5. I installed majordomo 1.92 on three machines in different domains, two worked. The third I am trying to setup for sigweb organization keeps failing. I did the installing exactly the same. I re-installed it several times on for sigweb, made sure the path in the makefile is correct. I also made sure the ownship is right too, and compared with a running version on a different machine. But I am clueless as why it works on my machine but not on sigweb machine. Right now, I just run majordomo at command line, and got no response for over 10 minutes. The only differenct on these three machines are: the sigweb machine is running perl 4.35 while the other two are running perl 4.36. Does this make any difference? Also, someone posted a method to do a test at command line sometime back. Could you repost it or mail to me so that I can do some testing? Thank you all for your time and patience. Philip ______________________________________________________________________ Philip J. Zee / / / Information Express / / / 3250 Ash St. o o o / / / Palo Alto, CA 94306 o o / o / / Main: (415) 494-8787 DID: (415) 812-3530 o /o /o / Internet: pzee@express.com / / / ______________________________________________________________________ From majordomo-users-owner Tue Aug 9 03:55:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id DAA11945; Tue, 9 Aug 1994 03:55:14 GMT Received: from Sun.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA10814; Mon, 8 Aug 1994 17:45:58 -0700 Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA08783; Mon, 8 Aug 94 17:50:03 PDT Received: from damrak.Eng.Sun.COM by Eng.Sun.COM (4.1/SMI-4.1) id AA03842; Mon, 8 Aug 94 10:15:38 PDT Received: from damrak (localhost) by damrak.Eng.Sun.COM (5.x/SMI-SVR4) id AA15453; Mon, 8 Aug 1994 10:15:05 -0700 Message-Id: <9408081715.AA15453@damrak.Eng.Sun.COM> To: majordomo-users@GreatCircle.COM Subject: Re: Approval being asked for now and then -- Really listserv behavior Date: Mon, 08 Aug 1994 10:15:04 -0700 From: Steve Parker Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk - I'm not sure why he would put "", unless he doesn't - understand his own email address. It's also reminiscent of BITNET - listserv, where you specify your full name to the subscribe command - instead of your email address. I run several lists where the users are IETF types, all pretty well conditioned to listserv (and human emulations of same). I'ld especially like a replacement for request-answer which accepts listserv style requests and turns them into correct majordomo subscription requests. Has anyone done this? Cheers, ~sparker From majordomo-users-owner Tue Aug 9 02:28:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA13655; Tue, 9 Aug 1994 07:41:51 GMT Received: from ciup1.ncc.up.pt by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id AAA13646; Tue, 9 Aug 1994 00:41:32 -0700 Received: from rosa.esb.ucp.pt by ciup1.ncc.up.pt with SMTP id AA09295 (5.65c/IDA-1.4.4 for ); Tue, 9 Aug 1994 08:45:36 +0100 Received: by rosa.esb.ucp.pt id AA18333 (5.65c/IDA-1.4.4); Tue, 9 Aug 1994 09:44:05 +0200 Date: Tue, 9 Aug 1994 09:44:05 +0100 From: John Cullen Reply-To: John Cullen Subject: Re: unlink in resend script To: Gunther Anderson Cc: majordomo-users@greatcircle.com In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Mon, 8 Aug 1994, Gunther Anderson wrote: > your unlink behavior, because there's this tiny chance that Majordomo is > leaving two copies of _every_message_it_processes_ in your tmp directory. I just recently installed v1.92 of majordomo on a Linux box running (kernel 1.1.36, perl 4.036) and discovered exactly that behaviour. The odd thing is, when I run the unlink command from the command line, everything works fine. Regards, John Cullen --------------------------------------------------------------------------- Escola Superior de Biotecnologia | Email: J.Cullen@esb.ucp.pt Universidade Catolica Portuguesa | Phone: +351 2 558 0073 Rua Dr. Antonio Bernadino de Almeida | Fax: +351 2 590 351 4200 PORTO | Portugal | #include From majordomo-users-owner Tue Aug 9 09:59:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA15878; Tue, 9 Aug 1994 09:59:45 GMT Received: from ciup1.ncc.up.pt by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA15872; Tue, 9 Aug 1994 02:59:23 -0700 Received: from rosa.esb.ucp.pt by ciup1.ncc.up.pt with SMTP id AA12305 (5.65c/IDA-1.4.4 for ); Tue, 9 Aug 1994 11:02:54 +0100 Received: by rosa.esb.ucp.pt id AA18931 (5.65c/IDA-1.4.4); Tue, 9 Aug 1994 12:01:24 +0200 Date: Tue, 9 Aug 1994 12:01:24 +0100 From: John Cullen Subject: Re: unlink in resend script To: Gunther Anderson , majordomo-users@greatcircle.com In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Further to my last post, I just realised that I can _only_ remove the odd "resend.nnnn.{in,out}" files as root (or daemon -- su to daemon, or make a symlink from /bin/sh to the current dir and type 'wrapper sh'!). The "resend" files on my system are owned by daemon, group majordomo, with permissions 660, but user majordomo can't remove them. An odd thing I notice is that when I try and remove the files, I get "operation not permitted", rather than the usual "permission denied". Can anyone suggest a reason for this? For info, my wrapper program was compiled with POSIX flags, is owned by root, group majordomo and has perms 4755 (suid root: -rwsr-xr-x). Thanks, John Cullen --------------------------------------------------------------------------- Escola Superior de Biotecnologia | Email: J.Cullen@esb.ucp.pt Universidade Catolica Portuguesa | Phone: +351 2 558 0073 Rua Dr. Antonio Bernadino de Almeida | Fax: +351 2 590 351 4200 PORTO | Portugal | #include From majordomo-users-owner Tue Aug 9 14:03:51 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA17658; Tue, 9 Aug 1994 14:03:51 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA17651; Tue, 9 Aug 1994 07:03:36 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id KAA29151; Tue, 9 Aug 1994 10:05:45 -0400 Message-Id: <199408091405.KAA29151@bosnia.pop.psu.edu> To: pzee@express.com (Philip J. Zee) Cc: majordomo-users@greatcircle.com Subject: Re: unknown mailer error 5 again In-reply-to: Your message of "Mon, 08 Aug 1994 16:14:50 -0800." <199408082312.QAA23355@alto.express.com> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Tue, 09 Aug 1994 10:05:43 -0400 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199408082312.QAA23355@alto.express.com>, Philip J. Zee writes: >I am still having unknow mailer error 5. I installed majordomo 1.92 on >three machines in different domains, two worked. The third I am trying to >setup for sigweb organization keeps failing. I did the installing exactly >the same. What error messages do you get when it fails? (sorry I don't have your original message) error 5 is generated if the wrapper can't start majordomo. From Doc/FAQ: Subject: I get "majordomo: No such file or directory" from the wrapper ---------------------------------------------------------------------- Make sure that the #! statement at the beginning of all the Majordomo executables contain the correct path to the perl program. (the default is /usr/local/bin/perl) Make sure also that majordomo and all the related scripts are in the W_BIN directory as defined in the Makefile. >I re-installed it several times on for sigweb, made sure the path in the >makefile is correct. I also made sure the ownship is right too, and >compared with a running version on a different machine. But I am clueless >as why it works on my machine but not on sigweb machine. > >Right now, I just run majordomo at command line, and got no response for >over 10 minutes. This is a permission problem. Check the permissions on the directory where the Log file is, as well as the lists directory. The FAQ goes into further detail under "Subject: Majordomo seems to be taking many minutes to process commands" --Dave From majordomo-users-owner Tue Aug 9 15:32:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA18507; Tue, 9 Aug 1994 15:32:49 GMT Received: from ssi.edc.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA18501; Tue, 9 Aug 1994 08:32:42 -0700 Received: from ssi.edc.org by ssi.edc.org id aa15547; 9 Aug 94 11:36 EDT Date: Tue, 9 Aug 1994 11:36:26 -400 (EDT) From: Gunther Anderson To: majordomo-users@greatcircle.com Subject: Copying/reselling policy? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I didn't see this anywhere in the formal documentation. Someone I am aware of is considering taking my patches for Majordomo on MMDF and Majordomo 1.92 itself, and putting it on a CD-ROM along with many other packages, and selling it. What is the formal position of [whoever it is who's supposed to have these positions] about this? Is there someone I should have them get in touch with? I am making them aware of the impending release of 1.93, but their concern is for their own timetables, so they know they'll be .01 short on their distribution. Again, is there a prohibition on this? How is Majordomo copyrighted? Gunther Anderson From majordomo-users-owner Tue Aug 9 17:40:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA19903; Tue, 9 Aug 1994 17:40:09 GMT Received: from snyflcc.fingerlakes.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id KAA19889; Tue, 9 Aug 1994 10:39:23 -0700 Received: from localhost (krampwd@localhost) by snyflcc.fingerlakes.edu (8.6.5/8.6.5) id NAA23136; Tue, 9 Aug 1994 13:36:10 -0400 Date: Tue, 9 Aug 1994 13:36:10 -0400 (EDT) From: "William D. Kramp" Subject: Permission error To: majordomo-users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I thought I had the permission set properly, but I am getting an error message from shlock: shlock:open(">/local/majordomo/bin/shlock.6247"): Permission denied at /local/majordomo/bin/shlock.pl line 131, <> 1. My permissions for the directories /local/majordomo & /local/majordomo/bin are: majordom.majordom 775 My permissions for the perl files under /local/majordomo/bin are: majordom.majordom 555 My permissions for the *.pl files under /local/majordomo/bin are: majordom.majordom 444 I would appreciate any thoughts on the matter. Thanks. +===============================================================+ | Bill Kramp - System Admin. Finger Lakes Community College | | krampwd@snyflcc.fingerlakes.edu | +===============================================================+ From majordomo-users-owner Tue Aug 9 22:24:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id WAA23174; Tue, 9 Aug 1994 22:24:46 GMT Received: from e-Commerce.Com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA23168; Tue, 9 Aug 1994 15:24:38 -0700 Received: by e-Commerce.Com (4.1/SMI-4.1) id AA11310; Tue, 9 Aug 94 18:17:02 EDT Date: Tue, 9 Aug 94 18:17:02 EDT From: jimc@e-Commerce.Com (Jim Carroll) Message-Id: <9408092217.AA11310@e-Commerce.Com> To: majordomo-users@greatcircle.com Subject: error message Reply-To: jimc@e-Commerce.Com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Just tried installing Majordomo today. I've managed to be stumped by the following error: ----- Transcript of session follows ----- 550 "/usr/local/majordomo-1.92/wrapper resend -l shift -h Shift.Com -f Shift shift-outgoing"... Can't create output I'm able to subscribe and unsubscribe, but when I actually send to "shift", this gets thrown back at me. I've been rooting around, trying to find something permission related, but no cigar. Everything is owned by majordom, group majordom, mode 755. What am I overlooking? -- Jim Carroll -- jimc@e-Commerce.Com e-Commerce, Inc., 1030 Kamato Road, Suite 201 Mississauga, Ontario, Canada L4W 4B6 Tel: +1 905 602 0863 Fax: +1 905 603 8402 From majordomo-users-owner Tue Aug 9 23:33:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA23895; Tue, 9 Aug 1994 23:33:56 GMT Received: from e-Commerce.Com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA23889; Tue, 9 Aug 1994 16:33:48 -0700 Received: by e-Commerce.Com (4.1/SMI-4.1) id AA11722; Tue, 9 Aug 94 19:39:11 EDT Date: Tue, 9 Aug 94 19:39:11 EDT From: jimc@e-Commerce.Com (Jim Carroll) Message-Id: <9408092339.AA11722@e-Commerce.Com> To: majordomo-users@greatcircle.com Subject: found my 'error' - never mind Reply-To: jimc@e-Commerce.Com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Missing the "|" symbol in my aliases file. Yikes. Sorry to have wasted your bandwidth. -- Jim Carroll -- jimc@e-Commerce.Com e-Commerce, Inc., 1030 Kamato Road, Suite 201 Mississauga, Ontario, Canada L4W 4B6 Tel: +1 905 602 0863 Fax: +1 905 603 8402 From majordomo-users-owner Tue Aug 9 23:34:41 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA23913; Tue, 9 Aug 1994 23:34:41 GMT Received: from psych.psy.uq.oz.au by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA23897; Tue, 9 Aug 1994 16:34:18 -0700 Received: from localhost.psy.uq.oz.au by psych.psy.uq.oz.au id ; Wed, 10 Aug 1994 09:38:25 +1000 Message-Id: <199408092338.JAA01915@psych.psy.uq.oz.au> To: majordomo-users@GreatCircle.COM Subject: Core dump problem.... X-Mailer: exmh version 1.4.1 7/21/94 Date: Wed, 10 Aug 1994 09:38:24 +1000 From: Robert Dal Santo Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am beginning to see more and more errors like those below. I am running majordomo 1.92 (unpatched) on a Sparcstation 20 SunOS 4.1.3 using perl version 4.036. Can anyone help me?? Thanks, Robert Dal Santo Phone +61 7 365 6687 System Administrator Fax +61 7 365 4466 Department of Psychology, University of Queensland 4072, AUSTRALIA. ---------------------------------------------- The original message was received at Wed, 10 Aug 1994 05:42:50 +1000 from arl-img-1.compuserve.com [198.4.7.1] ----- The following addresses had delivery problems ----- "|/var/spool/majord/wrapper majordomo -l arlist" (unrecoverable error) (expanded from: ) ----- Transcript of session follows ----- sh: 27395 Memory fault - core dumped 554 "|/var/spool/majord/wrapper majordomo -l arlist"... unknown mailer error 139 ----- Message header follows ----- From majordomo-users-owner Tue Aug 9 23:44:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA24003; Tue, 9 Aug 1994 23:44:42 GMT Received: from e-Commerce.Com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA23997; Tue, 9 Aug 1994 16:44:34 -0700 Received: by e-Commerce.Com (4.1/SMI-4.1) id AA11735; Tue, 9 Aug 94 19:49:57 EDT Date: Tue, 9 Aug 94 19:49:57 EDT From: jimc@e-Commerce.Com (Jim Carroll) Message-Id: <9408092349.AA11735@e-Commerce.Com> To: majordomo-users@greatcircle.com Subject: modifying return address Reply-To: jimc@e-Commerce.Com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I understand how 'resend' works, as far as modifying the name of the host where Majordomo is working (-h host.domain.name), but is there a way to manage listname-request the same way? We'd like to be able to have Majordomo appear to be a completely different host, depending on which -request you send to. -- Jim Carroll -- jimc@e-Commerce.Com e-Commerce, Inc., 1030 Kamato Road, Suite 201 Mississauga, Ontario, Canada L4W 4B6 Tel: +1 905 602 0863 Fax: +1 905 603 8402 From majordomo-users-owner Wed Aug 10 00:07:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id AAA24190; Wed, 10 Aug 1994 00:07:55 GMT Received: from sgigate.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA24184; Tue, 9 Aug 1994 17:07:47 -0700 Received: from relay.sgi.com (relay.sgi.com [192.26.51.36]) by sgigate.sgi.com (940519.SGI.8.6.9/8.6.4) with SMTP id RAA20042; Tue, 9 Aug 1994 17:11:56 -0700 Received: from fogno.corp.sgi.com by relay.sgi.com via SMTP (920330.SGI/920502.SGI) for @sgigate.sgi.com:majordomo-users@GreatCircle.COM id AA09053; Tue, 9 Aug 94 17:11:55 -0700 Received: by fogno.corp.sgi.com (931110.SGI/911001.SGI) for @sgi.com:majordomo-users@GreatCircle.COM id AA01205; Tue, 9 Aug 94 17:11:53 -0700 From: terryd@fogno.corp.sgi.com (Terry Diemer, Datacomette) Message-Id: <9408091711.ZM1203@fogno.corp.sgi.com> Date: Tue, 9 Aug 1994 17:11:52 -0700 Reply-To: terryd@fogno.corp.sgi.com X-Face: '\qr5_l:k~*/u{d=\,i~)y)0[>m]Nph(W/cT9s.7&LWs}k3Ob#KHBo8ofBzI7Em578G|to( w%>+&BHJjtj^;a2c&7HY?:$Ku/|DifegFiyG=1Fiyjr4rXZ84#z1MAv$CCekyy#3/XX4T"}tP&+pNw a|&5P,;7Yeav3/opf"n'&>70}%(gvu"jxhbZffBcS}jbNCtuqrBvYXfI283whQv'&#m0^N@b%]b[-~ V};\X~-8uco=)J9cmpb1_R$l]QIINh=oxUb)0]+ X-Mailer: Z-Mail-SGI (3.0S.1026 26oct93 MediaMail) To: majordomo-users@GreatCircle.COM Subject: Question: what controls the timestamp in the Log? Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk help! what controls the timestamp in the Log? my timestamps are 8 hours ahead in the log generated by majordomo. It works so well I hate changing things... :?) -t -- Ms. Terry Diemer|terryd@sgi.com|Network Administration|Mountain View, CA, USA *** *** That money talks, I'll not deny. I heard it once. It said "good-bye". *** *** (The Gilroy Garlic Festival July 28,29 and 30,1995) From majordomo-users-owner Wed Aug 10 04:35:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id EAA26134; Wed, 10 Aug 1994 04:35:56 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA26128; Tue, 9 Aug 1994 21:35:49 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id XAA02661; Tue, 9 Aug 1994 23:49:06 -0500 Date: Tue, 9 Aug 1994 23:49:05 +0100 From: "Robert A. Hayden" Subject: Bounce program To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The documentation, I guess, isn't very clear on this, but how does one implement the bounce list/bounce-remind program so that people that go 'boing' can be dealt with in a somewhat more automated manner? Uh . . . how exactly is this accomplished? *ducks* ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else, dammit -=-=-=-=-=-=-=- (GEEK CODE 2.1) GJ/CM d- H-- s-:++>s-:+ g+ p? au+ a- w++ v* C++(++++) UL++++$ P+>++ L++$ 3- E---- N+++ K+++ W M+ V-- -po+(---)>$ Y++ t+ 5+++ j R+++$ G- tv+ b+ D+ B--- e+>++(*) u** h* f r-->+++ !n y++** From majordomo-users-owner Wed Aug 10 05:59:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id FAA26487; Wed, 10 Aug 1994 05:59:09 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id WAA26481; Tue, 9 Aug 1994 22:59:01 -0700 Received: from freke by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA17245; Tue, 9 Aug 94 22:50:19 -0700 Received: by freke.lerctr.org (/\==/\ Smail3.1.28.1 #28.9) id ; Tue, 9 Aug 94 22:36 PDT To: majordomo-users@greatcircle.com Newsgroups: mail.majordomo.users Path: mikepb From: mikepb@freke.lerctr.org (Michael P. Brininstool) Subject: Re: Question: what controls the timestamp in the Log? Message-Id: <1994Aug10.053634.7451@freke.lerctr.org> Organization: Valhalla MIS Department. References: <1994Aug10.051304.5716@freke.lerctr.org> Distribution: local Date: Wed, 10 Aug 1994 05:36:34 GMT Lines: 13 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In article <1994Aug10.051304.5716@freke.lerctr.org>, Terry Diemer, Datacomette wrote: >help! what controls the timestamp in the Log? >my timestamps are 8 hours ahead in the log generated by majordomo. >It works so well I hate changing things... :?) Happy Birthday, Terry! Is it 8 hours or 7 hours? Maybe the timestamp is GMT rather than PST??? But that is 7 hours. ---------------------------------------------------------| | #include "std/disclaimer.h" Michael P. Brininstool | | mikepb@freke.lerctr.org OR mikepb@netcom.com | |--------------------------------------------------------- From majordomo-users-owner Wed Aug 10 15:42:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA00295; Wed, 10 Aug 1994 15:42:55 GMT Received: from home.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA00288; Wed, 10 Aug 1994 08:42:16 -0700 Received: (from mzeier@localhost) by home.interaccess.com (8.6.9/8.6.9) id KAA18878 for majordomo-users@greatcircle.com; Wed, 10 Aug 1994 10:43:18 -0500 From: "Matthew R. Zeier" Message-Id: <199408101543.KAA18878@home.interaccess.com> Subject: How to set up digest? To: majordomo-users@greatcircle.com Date: Wed, 10 Aug 1994 10:43:17 -0500 (CDT) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 724 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm not sure how to set up the digest feature of majordomo 1.92 to send digests out. Currently, it is digesting incoming mail, but that's all it's doing. Any help? - Matthew ---- Matthew R. Zeier "Do what you can with what you have mzeier@interaccess.com where you are." -Teddy Roosevelt http://www.interaccess.com/mzeier.html ...................................................................... InterAccess Company Technical Support: 708/498-3842 3345 Commercial Avenue Modem Line: 708/498-3960 Northbrook, IL 60062 Fax Line: 708/498-3289 "Oh and where will you be in 10 years? I'll be on Mars myself." From majordomo-users-owner Wed Aug 10 15:53:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA00384; Wed, 10 Aug 1994 15:53:45 GMT Received: from vacuum.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA00378; Wed, 10 Aug 1994 08:53:37 -0700 Received: by vacuum.org (5.0/SOLARIS-V1.0-American Vacuum Society) id AA21181; Wed, 10 Aug 94 11:57:48 EDT Date: Wed, 10 Aug 94 11:57:48 EDT From: carlos@vacuum.org (Carlos Toro) Message-Id: <9408101557.AA21181@vacuum.org> To: majordomo-users@greatcircle.com Subject: "make wrapper" problems (Newbie) X-Sun-Charset: US-ASCII content-length: 674 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I just ran "make wrapper" and got: wrapper.c: In function `main': wrapper.c:65: warning: comparison between pointer and integer Line 65 of wrapper.c says /* if the command contains a /, then don't allow it */ if (STRCHR(argv[1], '/') != NULL) { /* this error message is intentionally cryptic */ fprintf(stderr, "%s: error: insecure usage\n", argv[0]); exit(2) Also, I edited the BIN and HOME variables in wrapper.c to point to the home dir of majordomo, where I want wrapper to reside. This was not documented anywhere in the .README or .manual docs, but I assume it's the right thing to do ... yes? Thanks for your attention, Carlos From majordomo-users-owner Thu Aug 11 05:08:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id FAA04864; Thu, 11 Aug 1994 05:08:12 GMT Received: from mailgate.ericsson.se by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id WAA04858; Wed, 10 Aug 1994 22:08:03 -0700 Received: from eua.ericsson.se by mailgate.ericsson.se (4.1/SMI-4.1-MAILGATE1.14) id AA09096; Thu, 11 Aug 94 07:12:19 +0200 Received: from ms.eua.ericsson.se by eua.ericsson.se (4.1/EUA-2.1) id AA20693; Thu, 11 Aug 94 07:12:17 +0200 Received: from etxbs3.eua.ericsson.se (etxbs3.etxb.eua.ericsson.se) by ms.eua.ericsson.se (4.1/MS-2.1) id AA06143; Thu, 11 Aug 94 07:12:17 +0200 Received: from etxus2c25.eua.ericsson.se by etxbs3.eua.ericsson.se (4.1/SMI-4.1-MS1.99) id AA04141; Thu, 11 Aug 94 07:12:16 +0200 From: etxpihl@etxb.eua.ericsson.se (Tomas Pihl ETX/B/DG) Received: by etxus2c25.eua.ericsson.se (4.1/client-1.3) id AA01107; Thu, 11 Aug 94 07:12:15 +0200 Date: Thu, 11 Aug 94 07:12:15 +0200 Message-Id: <9408110512.AA01107@etxus2c25.eua.ericsson.se> To: majordomo-users@GreatCircle.COM Subject: Re: "make wrapper" problems (Newbie) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk [compile error deleted] > Also, I edited the BIN and HOME variables in wrapper.c to point to the home > dir of majordomo, where I want wrapper to reside. This was not documented > anywhere in the .README or .manual docs, but I assume it's the right thing > to do ... yes? You shouldn't do this. Look in the top-Makefile at the `W_*' macros defined. Edit the W_BIN and W_HOME here instead because they get passed to wrapper at compilationtime. WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --- Tomas Pihl Ericsson Telecom AB, EO5/ETX/B/DE etxpihl@etxb.eua.ericsson.se From majordomo-users-owner Thu Aug 11 12:01:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA08852; Thu, 11 Aug 1994 12:01:46 GMT Received: from home.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id FAA08846; Thu, 11 Aug 1994 05:01:40 -0700 Received: from .interaccess.com (dyna2-25.interaccess.com [198.80.0.214]) by home.interaccess.com (8.6.9/8.6.9) with SMTP id HAA10484 for ; Thu, 11 Aug 1994 07:02:13 -0500 Date: Thu, 11 Aug 1994 07:02:13 -0500 Message-Id: <199408111202.HAA10484@home.interaccess.com> X-Sender: ulysses@interaccess.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@GreatCircle.COM From: ulysses@interaccess.com (Dennis Fey) Subject: How get v 1.92 to send digests? X-Mailer: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Users: I'm not sure how to set up the digest feature of majordomo 1.92 to send digests out. Currently, it is digesting incoming mail, but that's all it's doing. Ideas? Thanks! Dennis From majordomo-users-owner Thu Aug 11 18:46:35 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA11604; Thu, 11 Aug 1994 18:46:35 GMT Received: from snyflcc.fingerlakes.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA11598; Thu, 11 Aug 1994 11:46:27 -0700 Received: from localhost (krampwd@localhost) by snyflcc.fingerlakes.edu (8.6.5/8.6.5) id OAA26285; Thu, 11 Aug 1994 14:44:20 -0400 Date: Thu, 11 Aug 1994 14:44:20 -0400 (EDT) From: "William D. Kramp" Subject: permissions and wrapper To: majordomo-users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have wrapper/majordomo working, but I had to play games with the owner of all directories and files. If I set the owner to root, everything works okay, but it doesn't if it is majordom. I think the problem is in my lack of understanding how the wrapper is functioning. Here are some of the details. Makefile for "wrapper": 1) POSIX complient system 2) W_UID=1 3) W_GID=19 /etc/passwd: 1) majordom:*:19:19:MAjordomo account:/local/majordomo:/bin/csh /etc/group: 1) majordom:*:19:majordom Do I need to change the W_UID in the Makefile to 19, or what am I doing wrong? +===============================================================+ | Bill Kramp - System Admin. Finger Lakes Community College | | krampwd@snyflcc.fingerlakes.edu | +===============================================================+ From majordomo-users-owner Thu Aug 11 23:38:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA14872; Thu, 11 Aug 1994 23:38:53 GMT Received: from psycfrnd.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA14866; Thu, 11 Aug 1994 16:38:34 -0700 Received: from localhost (mzeier@localhost) by psycfrnd.interaccess.com (8.6.5/8.6.5) id SAA14466 for majordomo-users@greatcircle.com; Thu, 11 Aug 1994 18:40:55 -0500 From: "Matthew R. Zeier" Message-Id: <199408112340.SAA14466@psycfrnd.interaccess.com> Subject: Problems with shlock.pl To: majordomo-users@greatcircle.com Date: Thu, 11 Aug 1994 18:40:55 -0500 (CDT) Reply-To: mzeier@interaccess.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1531 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here's the message I get, and I can't deciper what needs to be fixed. I have things set up correctly, or so I think. Any hints? > ----- The following addresses had delivery problems ----- > "|/usr/home/majordomo1.92/wrapper digest -r -C -l ihp-net-digest ihp-net-digest-outgoing" (unrecoverable error) > (expanded from: ihp-net-outgoing) > gallagherk@sluvca.slu.edu (unrecoverable error) > (expanded from: :include:/usr/home/MAJORDOMO/lists/ihp-net) > coenen@vms.csd.mu.edu (unrecoverable error) > (expanded from: :include:/usr/home/MAJORDOMO/lists/ihp-net) > > ----- Transcript of session follows ----- > Message delivered to mailing list ihp-net-outgoing > shlock: open(">/usr/home/MAJORDOMO/digest/ihp-net-digest/shlock.11156"): No such file or directory at shlock.pl line 131. > shlock: open(">/usr/home/MAJORDOMO/digest/ihp-net-digest/shlock.11156"): No such file or directory at shlock.pl line 131. *NOTE: this goes on for another 700 lines. - Matthew ---- Matthew R. Zeier "Do what you can with what you have mzeier@interaccess.com where you are." -Teddy Roosevelt http://www.interaccess.com/mzeier.html ...................................................................... InterAccess Company Technical Support: 708/498-3842 3345 Commercial Avenue Modem Line: 708/498-3960 Northbrook, IL 60062 Fax Line: 708/498-3289 "Oh and where will you be in 10 years? I'll be on Mars myself." From majordomo-users-owner Fri Aug 12 03:31:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id DAA16150; Fri, 12 Aug 1994 03:31:49 GMT Received: from megalon.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA16144; Thu, 11 Aug 1994 20:31:42 -0700 Received: by megalon.com (8.6.9/8.6.9) id UAA01224; Thu, 11 Aug 1994 20:30:59 -0700 From: Max Hozven - Network Support Message-Id: <199408120330.UAA01224@megalon.com> Subject: Re: Problem using majordomo under Solaris 2.3 To: alden@math.ohio-state.edu (Dave Alden) Date: Thu, 11 Aug 1994 20:30:58 -0700 (PDT) Cc: max@megalon.com, majordomo-users@GreatCircle.COM In-Reply-To: <199408041213.IAA09958@math.mps.ohio-state.edu> from "Dave Alden" at Aug 4, 94 08:13:04 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 895 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Yes! That was it! It works now. Dave- Thank you very much for the fix, I really appreciate it. -Max > > Hi, > > > megalon# Mail -v majordomo > > Subject: test > > subscribe test1 max > [...] > > # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1 1994/06/09 19:45:18 rouilj Exp $ > > eval of majordomo.cf failed at /files1/admin/majordomo/majordomo-1.92/bin/majordomo line 46. > > "|/files1/admin/majordomo/majordomo-1.92/bin/wrapper majordomo"... unknown mailer error 2 > > Saving message in /home/max/dead.letter > > /home/max/dead.letter... Sent > > > > Here's line 46 in majordomo: > > > > eval(`cat $cf`) || die "eval of majordomo.cf failed $@"; > > Did you recompile your Perl binary for Solaris? I had the same problem with > several of my Perl scripts (including Majordomo) -- I had to recompile Perl > under Solaris to get it to work correctly. > > ...dave > > From majordomo-users-owner Fri Aug 12 10:56:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id KAA18508; Fri, 12 Aug 1994 10:56:31 GMT Received: from sparc by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id DAA18502; Fri, 12 Aug 1994 03:56:19 -0700 Received: by sparc (5.0/SMI-SVR4) id AA07927; Fri, 12 Aug 1994 07:58:18 +0400 Date: Fri, 12 Aug 1994 07:58:18 -0300 (ADT) From: Steve MacLeod Subject: Re: Problem using majordomo under Solaris 2.3 To: Max Hozven - Network Support Cc: Dave Alden , max@megalon.com, majordomo-users@GreatCircle.COM In-Reply-To: <199408120330.UAA01224@megalon.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 1399 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, what permissions are you able to get away with on your Solaris install? Did wrapper need to setuid to root? Thanks -------------------------------------------------------------------- Steve MacLeod Microcomputer Specialist (902)539-5300x625 Computer Centre University College of Cape Breton Sydney, N.S. Fax (902)562-0119 Canada B1P 5S2 On Thu, 11 Aug 1994, Max Hozven - Network Support wrote: > > Yes! That was it! It works now. > > Dave- Thank you very much for the fix, I really appreciate it. > > -Max > > > > > Hi, > > > > > megalon# Mail -v majordomo > > > Subject: test > > > subscribe test1 max > > [...] > > > # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1 1994/06/09 19:45:18 rouilj Exp $ > > > eval of majordomo.cf failed at /files1/admin/majordomo/majordomo-1.92/bin/majordomo line 46. > > > "|/files1/admin/majordomo/majordomo-1.92/bin/wrapper majordomo"... unknown mailer error 2 > > > Saving message in /home/max/dead.letter > > > /home/max/dead.letter... Sent > > > > > > Here's line 46 in majordomo: > > > > > > eval(`cat $cf`) || die "eval of majordomo.cf failed $@"; > > > > Did you recompile your Perl binary for Solaris? I had the same problem with > > several of my Perl scripts (including Majordomo) -- I had to recompile Perl > > under Solaris to get it to work correctly. > > > > ...dave > > > > > > From majordomo-users-owner Fri Aug 12 13:39:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA19689; Fri, 12 Aug 1994 13:39:22 GMT Received: from colossus.cse.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA19683; Fri, 12 Aug 1994 06:39:14 -0700 Received: from localhost by colossus.cse.psu.edu with SMTP id <45756>; Fri, 12 Aug 1994 09:43:19 -0400 To: mzeier@interaccess.com cc: majordomo-users@greatcircle.com Subject: Re: Problems with shlock.pl X-Work-Address: Department of Computer Science, 121A Pond Laboratory The Pennsylvania State University, University Park, PA 16802 X-Work-Phone: +1 814 863 1142 (Voice) +1 814 865 3176 (FAX) In-reply-to: Your message of Thu, 11 Aug 1994 19:40:55 EDT. <199408112340.SAA14466@psycfrnd.interaccess.com> Date: Fri, 12 Aug 1994 09:43:01 -0400 From: Daniel R Ehrlich Message-Id: <94Aug12.094319edt.45756@colossus.cse.psu.edu> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > >Here's the message I get, and I can't deciper what needs to be fixed. I >have things set up correctly, or so I think. Any hints? > >> ----- The following addresses had delivery problems ----- >> "|/usr/home/majordomo1.92/wrapper digest -r -C -l ihp-net-digest ihp-net-dig est-outgoing" (unrecoverable error) >> (expanded from: ihp-net-outgoing) >> gallagherk@sluvca.slu.edu (unrecoverable error) >> (expanded from: :include:/usr/home/MAJORDOMO/lists/ihp-net) >> coenen@vms.csd.mu.edu (unrecoverable error) >> (expanded from: :include:/usr/home/MAJORDOMO/lists/ihp-net) >> >> ----- Transcript of session follows ----- >> Message delivered to mailing list ihp-net-outgoing >> shlock: open(">/usr/home/MAJORDOMO/digest/ihp-net-digest/shlock.11156"): No such file or directory at shlock.pl line 131. >> shlock: open(">/usr/home/MAJORDOMO/digest/ihp-net-digest/shlock.11156"): No such file or directory at shlock.pl line 131. > Make sure that the permissions allow what ever user you are running majordomo under to write in the directory ihp-net-digest. Might also check that wrapper is installed correctly. Dan Ehrlich - Systems Analyst - PSU Computer Science and Engineering "Universities should be safe havens where ruthless examination of realities will not be distorted by the aim to please or inhibited by the risk of displeasure." - Kingman Brewster 2.6 fingerprint = 5C 01 7F 57 B0 AB 68 72 04 23 B9 BD 27 AD 85 60 echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc From majordomo-users-owner Fri Aug 12 18:07:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA21895; Fri, 12 Aug 1994 18:07:56 GMT Received: from balltown.cma.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA21884; Fri, 12 Aug 1994 11:07:30 -0700 Received: from homer.balltown.cma.com (homer.balltown.cma.com [149.19.1.16]) by balltown.cma.com (8.6.8/CMA01) with ESMTP id OAA12827 for ; Fri, 12 Aug 1994 14:11:40 -0400 From: richard welty Received: (welty@localhost) by homer.balltown.cma.com (8.6.8/CLI) id OAA23738; Fri, 12 Aug 1994 14:13:22 -0400 Date: Fri, 12 Aug 1994 14:13:22 -0400 Message-Id: <199408121813.OAA23738@homer.balltown.cma.com> To: majordomo-users@greatcircle.com Subject: "hostile users" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk the hostile user code is appreciated, of course, but in those cases where i approve of an address containing a "/" character, how am i supposed to put it in a list? mailing an "approve " type command clearly doesn't override the hostile user check. we just started running majordomo here, version 1.92 if that makes any difference. cheers, richard (welty@balltown.cma.com) From majordomo-users-owner Fri Aug 12 19:47:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA22555; Fri, 12 Aug 1994 19:47:26 GMT Received: from midway.uchicago.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA22549; Fri, 12 Aug 1994 12:47:13 -0700 From: ckoenig@midway.uchicago.edu Received: from kimbark.uchicago.edu by midway.uchicago.edu for majordomo-users@greatcircle.com Fri, 12 Aug 94 14:51:24 CDT Received: from localhost.uchicago.edu by kimbark.uchicago.edu (4.1/UCCO-1.0A) id AA22672; Fri, 12 Aug 94 14:50:56 CDT Message-Id: <9408121950.AA22672@kimbark.uchicago.edu> To: majordomo-users@greatcircle.com Subject: "digest work dir" also needs ARCHIVE dir! Date: Fri, 12 Aug 94 14:50:55 -0500 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk An observation stumbled across accidentally (by trying to set up a digest with no corresponding archive dir): The README and Majordomo.cf file comments about $digest_work_dir being where digest "does its work" are perhaps a bit misleading because it doesn't do ALL its work there.... i.e. it's not sufficient just to create a $digest_work_dir, you also need an archive dir for the digest, i.e. $filedir/listname-digest$filedir_suffix must be created too before the "digest" script can actually send out its first issue! The "make_digest()" subroutine of the "digest" Perl script actually writes the final copy (with overall digest fronter etc. prepended) of the new issue of the named digest NOT in the $digest_work_dir, but rather in the archive directory, as defined in the .cf file for "get" and "index" commands, i.e. "$filedir/listname-digest$filedir_suffix". Perhaps documentation should point out that you need to create an archive dir for a digest, even if you were NOT planning to explicitly archive digest issues.... Chris Koenigsberg: ckk@uchicago.edu, ckoenig@midway.uchicago.edu U. of Chicago Academic Information Technologies From majordomo-users-owner Fri Aug 12 20:18:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA22717; Fri, 12 Aug 1994 20:18:33 GMT Received: from pentagon.io.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA22711; Fri, 12 Aug 1994 13:18:25 -0700 Received: from localhost by pentagon.io.com (8.6.5/PERFORMIX-0.9/08-16-92) id PAA28193; Fri, 12 Aug 1994 15:22:42 -0500 From: mccoy@io.com (Jim McCoy) Message-Id: <199408122022.PAA28193@pentagon.io.com> Subject: Re: "digest work dir" also needs ARCHIVE dir! To: ckoenig@midway.uchicago.edu Date: Fri, 12 Aug 1994 15:22:41 -0500 (CDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <9408121950.AA22672@kimbark.uchicago.edu> from "ckoenig@midway.uchicago.edu" at Aug 12, 94 02:50:55 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 451 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk [...] > Perhaps documentation should point out that you need to create an > archive dir for a digest, even if you were NOT planning to explicitly > archive digest issues.... It does. From section 2.5 of the README: To use digest you must create the archive dir and the incoming directory. The archive directory is created using $filedir/.$filedir_suffix. $filedir and $filedir_suffix are defined in the majordomo.cf file. [...] jim From majordomo-users-owner Fri Aug 12 20:29:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA22762; Fri, 12 Aug 1994 20:29:05 GMT Received: from zoom.bga.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA22756; Fri, 12 Aug 1994 13:28:56 -0700 Received: (from sprater@localhost) by zoom.bga.com (8.6.9/8.6.9) id PAA14747; Fri, 12 Aug 1994 15:33:13 -0500 Date: Fri, 12 Aug 1994 15:33:11 -0500 (CDT) From: Scott Prater Subject: "reply_to" header in config file? 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'm maintaining a list for a specialized group, and I'm trying to get a "Reply-to:" header included in all postings sent to the list. I'm using Majordomo 1.92, and I've tried setting a "Reply-to:" header by remotely editing and uploading the individual list configuration file, using the "config" and "newconfig" commands. I switched the "reply_to" parameter to read "reply_to = ", and reloaded the configuration file; I got messages back from majordomo indicating that my new configuration file had been accepted, but when I post, then read a message, no "Reply-to:" header appears. Is there something else I should be doing, or changing, in the configuration file? I'm a humble user with only rudimentary programming and installation experience - I don't have any superuser or any other kind of administrative privileges on my host machine, so all the majordomo working files are (fortunately) off limits to me. If anyone has any suggestions, I'd appreciate them. Thanks, Scott Prater sprater@bga.com From majordomo-users-owner Sat Aug 13 11:22:03 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA26368; Sat, 13 Aug 1994 11:22:03 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id EAA26362; Sat, 13 Aug 1994 04:21:55 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HFURCACDEO001B5L@SYSWRK.UCIS.DAL.CA>; Sat, 13 Aug 1994 08:26:11 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HFURC5FCHS00XUNK@AC.DAL.CA>; Sat, 13 Aug 1994 08:26:06 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA28494; Sat, 13 Aug 94 08:18:49 -0300 Date: Sat, 13 Aug 1994 08:18:48 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Distribution vs. mailing list query To: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9408131118.AA28494@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: 996 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I was just asked to help set up a distribution list for a weekly report. I set it up under Majordomo (which is why I'm posting this to the Majordomo-Users list, no flames please) but wonder whether there is an easier way to run a mailing list as a distribution list. We're using Majordomo because it lets people subscribe and unsubscribe on their own, but only one person should be submitting material to the list. There are at least two ways to do this: 1. Make the list moderated, so the submitter has to include the approval header to every posting 2. Change the ListName alias to somthing obscure so that mail sent to the list name will bounce, and only the list manager will know the correct alias Any other suggestions that might be more straightforward? Thanks, 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 Sat Aug 13 15:08:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA26973; Sat, 13 Aug 1994 15:08:07 GMT Received: from netcom14.netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA26967; Sat, 13 Aug 1994 08:08:01 -0700 Received: by netcom14.netcom.com (8.6.8.1/Netcom) id IAA15282; Sat, 13 Aug 1994 08:12:43 -0700 Date: Sat, 13 Aug 1994 08:12:43 -0700 (PDT) From: James Cook Subject: Re: Distribution vs. mailing list query To: Bill Silvert cc: Majordomo Users In-Reply-To: <9408131118.AA28494@biome.bio.ns.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Sat, 13 Aug 1994, Bill Silvert wrote: > 2. Change the ListName alias to somthing obscure so that mail sent to > the list name will bounce, and only the list manager will know the > correct alias I would like to know how to change the alias for the listName on Majordomo. How is that done? Thanks! James Cook From majordomo-users-owner Sat Aug 13 16:35:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA27258; Sat, 13 Aug 1994 16:35:37 GMT Received: from hp.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA27252; Sat, 13 Aug 1994 09:35:30 -0700 Received: from hpkel02.cup.hp.com by hp.com with SMTP (1.36.108.7/15.5+IOS 3.13) id AA09778; Sat, 13 Aug 1994 09:39:54 -0700 Received: by hpkel02.cup.hp.com (1.38.193.5/15.5+IOS 3.20+cup+OMrelay) id AA14972; Sat, 13 Aug 1994 09:37:38 -0700 From: Ray Terry Message-Id: <9408131637.AA14972@hpkel02.cup.hp.com> Subject: bounces and bounce-remind ?? To: majordomo-users@greatcircle.com Date: Sat, 13 Aug 94 9:37:38 PDT Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In using a bounces dist list I notice that what is mentioned via bounce-remind doesn't actually happen: "Here are the addresses currently on Bounces@$whereami so that you can see which of your addresses is among them. The comment for each address shows the date it was moved, and the first list it was removed from. If you were on multiple lists here, you may have been removed from them as well, but only the first list you were removed from will show up in the comment below." The "comment for each address" mentioned above is written to the Log file, but it is not written to the actual bounces list. Just wondering if anyone has already figured this one out? Ray Terry raymail@hpkel02.cup.hp.com PGP public key available from public key servers or upon request. From majordomo-users-owner Sat Aug 13 20:37:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA28550; Sat, 13 Aug 1994 20:37:11 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA28544; Sat, 13 Aug 1994 13:36:58 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qZPqM-00014wC; Sat, 13 Aug 94 13:38 PDT Message-Id: To: majordomo-users@greatcircle.com Subject: "digest" question -- lazy user ;-) Date: Sat, 13 Aug 1994 13:38:12 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm on "digest" version 1.8. One of my digests just rolled from number 199 to number 0 -- does anyone have any ideas as to why? --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Sat Aug 13 20:43:16 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA28569; Sat, 13 Aug 1994 20:43:16 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA28563; Sat, 13 Aug 1994 13:43:09 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id PAA18671; Sat, 13 Aug 1994 15:57:24 -0500 Date: Sat, 13 Aug 1994 15:57:23 +0100 From: "Robert A. Hayden" Subject: Re: "digest" question -- lazy user ;-) To: "Roger B.A. Klorese" cc: majordomo-users@GreatCircle.COM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Sat, 13 Aug 1994, Roger B.A. Klorese wrote: > I'm on "digest" version 1.8. One of my digests just rolled from number 199 > to number 0 -- does anyone have any ideas as to why? Not sure why it rolled at 200 instead of some other number, but you can increment your volume number to make sure that old digests don't get nuked or whatever. This is in listname.config I think. ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else, dammit -=-=-=-=-=-=-=- (GEEK CODE 2.1) GJ/CM d- H-- s-:++>s-:+ g+ p? au+ a- w++ v* C++(++++) UL++++$ P+>++ L++$ 3- E---- N+++ K+++ W M+ V-- -po+(---)>$ Y++ t+ 5+++ j R+++$ G- tv+ b+ D+ B--- e+>++(*) u** h* f r-->+++ !n y++** From majordomo-users-owner Sat Aug 13 21:44:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA28780; Sat, 13 Aug 1994 21:44:49 GMT Received: from sparc by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA28773; Sat, 13 Aug 1994 14:44:39 -0700 Received: from dialup1.uccb.ns.ca by sparc (5.0/SMI-SVR4) id AA17464; Sat, 13 Aug 1994 18:46:26 +0400 Date: Sat, 13 Aug 1994 18:46:25 +0400 Message-Id: <9408132146.AA17464@sparc> X-Sender: smacleod@sparc.uccb.ns.ca Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: smacleod@sparc.uccb.ns.ca (Steve MacLeod) Subject: Linux version of majordomo 1.92? Exist??? X-Mailer: content-length: 525 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi All, I am looking at the possibility of setting up a linux host for department usage, the docs say it does not support setuid? If this is the case can the wrapper be run on it? Thanks ---------------------------------------------------------------------------- ------------------------------------------------------------ Steve MacLeod Microcomputer Specialist Computer Centre University College of Cape Breton Sydney, N.S. Canada 902-539-5300 x625 From majordomo-users-owner Sat Aug 13 23:17:15 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA29073; Sat, 13 Aug 1994 23:17:15 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA29067; Sat, 13 Aug 1994 16:17:08 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id SAA19122; Sat, 13 Aug 1994 18:31:46 -0500 Date: Sat, 13 Aug 1994 18:31:45 +0100 From: "Robert A. Hayden" Subject: Re: Linux version of majordomo 1.92? Exist??? To: Steve MacLeod cc: majordomo-users@GreatCircle.COM In-Reply-To: <9408132146.AA17464@sparc> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Sat, 13 Aug 1994, Steve MacLeod wrote: > Hi All, I am looking at the possibility of setting up a linux host for > department usage, the docs say it does not support setuid? If this is the > case can the wrapper be run on it? I'm using 1.92 on linux right now without any problems. I installed using the POSIX installation instructions. ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else, dammit -=-=-=-=-=-=-=- (GEEK CODE 2.1) GJ/CM d- H-- s-:++>s-:+ g+ p? au+ a- w++ v* C++(++++) UL++++$ P+>++ L++$ 3- E---- N+++ K+++ W M+ V-- -po+(---)>$ Y++ t+ 5+++ j R+++$ G- tv+ b+ D+ B--- e+>++(*) u** h* f r-->+++ !n y++** From majordomo-users-owner Sun Aug 14 01:40:51 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA29531; Sun, 14 Aug 1994 01:40:51 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA29525; Sat, 13 Aug 1994 18:40:42 -0700 Received: from bolis by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA23054; Sat, 13 Aug 94 18:45:13 -0700 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0qZThT-0002XaC; Sat, 13 Aug 94 17:45 PDT Message-Id: From: Alan Millar Subject: Re: bounces and bounce-remind ?? To: raymail@hpkel02.cup.hp.com (Ray Terry) Date: Sat, 13 Aug 1994 17:45:21 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <9408131637.AA14972@hpkel02.cup.hp.com> from "Ray Terry" at Aug 13, 94 09:37:38 am Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 727 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Ray Terry spake of these matters: > The comment for each address shows the date it was moved, > and the first list it was removed from. If you were on > The "comment for each address" mentioned above is written to the Log file, > but it is not written to the actual bounces list. The comment for each address is added by the bounce shell script. It is just a comment, added in parentheses after the actual address. If it shows up in the Log but not in the list, I would guess that you have the "strip" option turned on. - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: ftp://ftp.netcom.com/pub/amillar/welcome.html What part of "NO" don't you understand? From majordomo-users-owner Sun Aug 14 01:55:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA29584; Sun, 14 Aug 1994 01:55:56 GMT Received: from megalon.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA29578; Sat, 13 Aug 1994 18:55:48 -0700 Received: by megalon.com (8.6.9/8.6.9) id SAA00710; Sat, 13 Aug 1994 18:54:06 -0700 From: Max Hozven - Network Support Message-Id: <199408140154.SAA00710@megalon.com> Subject: Re: Problem using majordomo under Solaris 2.3 To: smacleod@sparc.uccb.ns.ca (Steve MacLeod) Date: Sat, 13 Aug 1994 18:54:04 -0700 (PDT) Cc: max@megalon.com, alden@math.ohio-state.edu, majordomo-users@GreatCircle.COM In-Reply-To: from "Steve MacLeod" at Aug 12, 94 07:58:18 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1655 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, This works for me: -rwxrwxr-x 1 majordom majordom 42269 Aug 2 02:13 majordomo -rwxrwxr-x 1 majordom majordom 8284 Aug 2 01:10 wrapper -Max > > > Hi, what permissions are you able to get away with on your Solaris > install? Did wrapper need to setuid to root? > > Thanks > -------------------------------------------------------------------- > Steve MacLeod Microcomputer Specialist (902)539-5300x625 > Computer Centre University College of Cape Breton > Sydney, N.S. Fax (902)562-0119 Canada B1P 5S2 > > On Thu, 11 Aug 1994, Max Hozven - Network Support wrote: > > > > > Yes! That was it! It works now. > > > > Dave- Thank you very much for the fix, I really appreciate it. > > > > -Max > > > > > > > > Hi, > > > > > > > megalon# Mail -v majordomo > > > > Subject: test > > > > subscribe test1 max > > > [...] > > > > # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1 1994/06/09 19:45:18 rouilj Exp $ > > > > eval of majordomo.cf failed at /files1/admin/majordomo/majordomo-1.92/bin/majordomo line 46. > > > > "|/files1/admin/majordomo/majordomo-1.92/bin/wrapper majordomo"... unknown mailer error 2 > > > > Saving message in /home/max/dead.letter > > > > /home/max/dead.letter... Sent > > > > > > > > Here's line 46 in majordomo: > > > > > > > > eval(`cat $cf`) || die "eval of majordomo.cf failed $@"; > > > > > > Did you recompile your Perl binary for Solaris? I had the same problem with > > > several of my Perl scripts (including Majordomo) -- I had to recompile Perl > > > under Solaris to get it to work correctly. > > > > > > ...dave > > > > > > > > > > > From majordomo-users-owner Sun Aug 14 03:43:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id DAA29897; Sun, 14 Aug 1994 03:43:21 GMT Received: from andy.bgsu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA29891; Sat, 13 Aug 1994 20:43:13 -0700 Received: by andy.bgsu.edu (5.65/4.0) id AA13096 ; Sat, 13 Aug 94 23:47:39 -0400 Date: Sat, 13 Aug 1994 23:44:16 -0400 (EDT) From: aka bookish Subject: RCPT messages 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 forgive me if this is a FAQ... the lists that i'm working with occasionally receive errant messages marked RCPT, apparently from Pegasus mail users. i saw a tantalizing suggestion in a gophered file that these could be screened out, but, alas, the method was not stored there with it. can anyone fill me in on how to screen out these obnoxious messages? thanks in advance, shawn wilbur +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Shawn P. Wilbur aka bookish | American Culture Studies swilbur@andy.bgsu.edu | Bowling Green State University +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ "Can you imagine what The Futurists would have done with an Information Superhighway?" --Avant-Pop Manifesto +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From majordomo-users-owner Sun Aug 14 14:40:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA03600; Sun, 14 Aug 1994 14:40:47 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA03587; Sun, 14 Aug 1994 07:40:33 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA24767 (5.65c/IDA-1.4.4 for ); Sun, 14 Aug 1994 10:44:24 -0400 Message-Id: <199408141444.AA24767@cs.umb.edu> To: aka bookish Cc: majordomo-users@greatcircle.com Subject: Re: RCPT messages In-Reply-To: Your message of "Sat, 13 Aug 1994 23:44:16 EDT." Date: Sun, 14 Aug 1994 10:44:18 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , aka bookish writes: >the lists that i'm working with occasionally receive errant messages >marked RCPT, apparently from Pegasus mail users. i saw a tantalizing >suggestion in a gophered file that these could be screened out, but, alas, >the method was not stored there with it. can anyone fill me in on how to >screen out these obnoxious messages? Add: /^subject:\s*RCPT:\b/ || to the list of admin requests. The comment just above the section is: # check for administrivia requests This test will be standard in 1.93. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-7227 x225 Senior Systems Consultant (SERL Project) 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 Sun Aug 14 14:54:51 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA03640; Sun, 14 Aug 1994 14:54:51 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA03634; Sun, 14 Aug 1994 07:54:44 -0700 Message-Id: <199408141454.HAA03634@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.37.109.11/16.2) id AA063666330; Sun, 14 Aug 1994 09:58:50 -0500 From: Larry Sheldon Date: Sun, 14 Aug 94 9:58:47 CDT To: swilbur@andy.bgsu.edu (aka bookish) Subject: Re: RCPT messages In-Reply-To: ; from "aka bookish" at Aug 13, 94 11:44 pm Status: RO Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Shawn Wilber said: > > forgive me if this is a FAQ... Just often enough that it ought tp be a BOC, methinks. > > the lists that i'm working with occasionally receive errant messages > marked RCPT, apparently from Pegasus mail users. i saw a tantalizing > suggestion in a gophered file that these could be screened out, but, alas, > the method was not stored there with it. can anyone fill me in on how to > screen out these obnoxious messages? Seems like there are two classes of the d*mn things, and we get tons of them every hour. I don't remember the hacks, but I'll go look for them in a few minutes. -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . . - L. F. (Larry) Sheldon, Jr. - . Unix Systems Administration . - Creighton University Computer Center-Old Gym We are all faced with - . 2500 California Plaza great opportunities . - Omaha, Nebraska, U.S.A. 68178 brillantly disquised as- . lsheldon@creighton.edu impossible situations.. - 402 280-2254 (work) - . 402 977-2946 (pager) "Bits & Pieces" . - 402 332-4622 (residence) - . . .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Sun Aug 14 14:55:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA03659; Sun, 14 Aug 1994 14:55:30 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA03653; Sun, 14 Aug 1994 07:55:22 -0700 Message-Id: <199408141455.HAA03653@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.37.109.11/16.2) id AA066196367; Sun, 14 Aug 1994 09:59:27 -0500 From: Larry Sheldon Date: Sun, 14 Aug 94 9:59:20 CDT To: swilbur@andy.bgsu.edu (aka bookish) Subject: Re: RCPT messages In-Reply-To: ; from "aka bookish" at Aug 13, 94 11:44 pm Status: RO Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk OK, here it is: (Note--we are still on an older version of majordomo--and the way this works is that it eats the _request_ for a return receipt or acknowledgement.) #!/usr/local/bin/perl -U # Copyright 1992, D. Brent Chapman. All Rights Reserved. For use by # permission only. # # $Source: /mycroft/brent/majordomo/RCS/resend,v $ # $Revision: 1.20 $ # $Date: 1993/11/13 21:49:16 $ # $Author: brent $ # $State: Exp $ 128a129,130 > || /^Return-Receipt-To:/i > || /^X-Pmrqc:/i -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . . - L. F. (Larry) Sheldon, Jr. - . Unix Systems Administration . - Creighton University Computer Center-Old Gym We are all faced with - . 2500 California Plaza great opportunities . - Omaha, Nebraska, U.S.A. 68178 brillantly disquised as- . lsheldon@creighton.edu impossible situations.. - 402 280-2254 (work) - . 402 977-2946 (pager) "Bits & Pieces" . - 402 332-4622 (residence) - . . .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Sun Aug 14 15:04:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA03703; Sun, 14 Aug 1994 15:04:58 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA03697; Sun, 14 Aug 1994 08:04:51 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA26049 (5.65c/IDA-1.4.4 for ); Sun, 14 Aug 1994 11:09:13 -0400 Message-Id: <199408141509.AA26049@cs.umb.edu> To: ulysses@interaccess.com (Dennis Fey) Cc: majordomo-users@greatcircle.com, dbarr@pop.psu.edu Subject: Re: How get v 1.92 to send digests? In-Reply-To: Your message of "Thu, 11 Aug 1994 07:02:13 CDT." <199408111202.HAA10484@home.interaccess.com> Date: Sun, 14 Aug 1994 11:09:12 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199408111202.HAA10484@home.interaccess.com>, Dennis Fey writes: >I'm not sure how to set up the digest feature of majordomo 1.92 to send >digests out. Currently, it is digesting incoming mail, but that's all it's >doing. Dave, could you add this one to the FAQ: "echo mkdigest | mail majordomo@..." This will force a digest to be created. Or you can set the max size in the digest list config file down low, and force automatic generation. There are some patches for 1.92 that will allow other ways of specifying automatic digest sending. The patch is in the contrib directory. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-7227 x225 Senior Systems Consultant (SERL Project) 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 Sun Aug 14 15:17:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA03760; Sun, 14 Aug 1994 15:17:29 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA03754; Sun, 14 Aug 1994 08:17:21 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA26716 (5.65c/IDA-1.4.4 for ); Sun, 14 Aug 1994 11:21:44 -0400 Message-Id: <199408141521.AA26716@cs.umb.edu> To: "Robert A. Hayden" Cc: majordomo-users@greatcircle.com Subject: Re: Bounce program In-Reply-To: Your message of "Tue, 09 Aug 1994 23:49:05 BST." Date: Sun, 14 Aug 1994 11:21:43 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , "Robert A. Hayden" writes: >The documentation, I guess, isn't very clear on this, but how does one >implement the bounce list/bounce-remind program so that people that go >'boing' can be dealt with in a somewhat more automated manner? > >Uh . . . how exactly is this accomplished? There is nothing special about this. Just create a mailing list called bounces. I usually set mine up as an auto list just to make life easier. All that bounce does is create an email message to that says: approve unsubscribe
approve subscribe bounces
The
and , are given on the command line to bounce. The address of the , and the passwords are retrieved from the .majordomo file in your home directory. A sample .majordomo file might look like (shamelessly stolen from the comments at the top of the bounce script): this-list passwd1 Majordomo@This.COM other-list passwd2 Majordomo@Other.GOV bounces passwd3 Majordomo@This.COM bounces passwd4 Majordomo@Other.GOV A command of "bounce this-list user@fubar.com" will mail the following message to Majordomo@This.COM: approve passwd1 unsubscribe this-list user@fubar.com approve passwd3 subscribe bounces user@fubar.com (930401 this-list) while a command of "bounce other-list user@fubar.com" will mail the following message to Majordomo@Other.COM: approve passwd2 unsubscribe other-list user@fubar.com approve passwd4 subscribe bounces user@fubar.com (930401 this-list) Note that the date and the list the user was bounced from are included as a comment in the address used for the "subscribe bounces" command. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-7227 x225 Senior Systems Consultant (SERL Project) 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 Sun Aug 14 19:18:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA04906; Sun, 14 Aug 1994 19:18:47 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA04899; Sun, 14 Aug 1994 12:18:40 -0700 Message-Id: <199408141918.MAA04899@mycroft.GreatCircle.COM> To: "Roger B.A. Klorese" cc: majordomo-users@greatcircle.com Subject: Re: "digest" question -- lazy user ;-) In-reply-to: Your message of Sat, 13 Aug 1994 13:38:12 -0700 Date: Sun, 14 Aug 1994 12:18:38 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Roger B.A. Klorese" writes: # I'm on "digest" version 1.8. One of my digests just rolled from number 199 # to number 0 -- does anyone have any ideas as to why? Disk full caused .number file to get zapped. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Sun Aug 14 19:27:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA05004; Sun, 14 Aug 1994 19:27:06 GMT Received: from gw1.att.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA04995; Sun, 14 Aug 1994 12:26:58 -0700 Received: from qsun.UUCP by ig1.att.att.com id AA23427; Sun, 14 Aug 94 15:30:36 EDT Message-Id: <9408141930.AA23427@ig1.att.att.com> From: debbie@qsun.att.com (Deborah A Hamilton +1 908 949 9459) Date: 14 Aug 94 19:31:00 GMT To: Majordomo-Users@GreatCircle.COM (Majordomo Users), GreatCircle.COM!majordomo-users-owner@research.att.com (Bill Silvert) Original-From: qsun!debbie (Deborah A Hamilton +1 908 949 9459) Original-To: Majordomo-Users@GreatCircle.COM (Majordomo Users), hoccson!research!GreatCircle.COM!majordomo-users-owner (Bill Silvert) Subject: Re: Distribution vs. mailing list query Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Bill writes: > I was just asked to help set up a distribution list for a weekly report. > I set it up under Majordomo (which is why I'm posting this to the > Majordomo-Users list, no flames please) but wonder whether there is an > easier way to run a mailing list as a distribution list. > > We're using Majordomo because it lets people subscribe and unsubscribe > on their own, but only one person should be submitting material to the > list. There are at least two ways to do this: > > 1. Make the list moderated, so the submitter has to include the approval > header to every posting > 2. Change the ListName alias to somthing obscure so that mail sent to > the list name will bounce, and only the list manager will know the > correct alias > > Any other suggestions that might be more straightforward? If you are running Majordomo V1.92, the restricted post feature works pretty well. With the support provided in 1.92, you can easily restrict the ability to post to the list to one or two ids. The documentation in the config file indicates that you can have a colon or space-separated list of file names that each contain one id that you want to restrict. Actually, the list of file names must be colon-separated. I've also implemented a small hack to resend to allow the files listed in the restricted_post config parm to contain multiple ids, in case you're interested. - Debbie ============================================================== Debbie Hamilton InterNIC Directory and Database Services Support AT&T Bell Laboratories debbie@qsun.att.com From majordomo-users-owner Sun Aug 14 13:15:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA05066; Sun, 14 Aug 1994 19:30:45 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA05054; Sun, 14 Aug 1994 12:30:28 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qZlHU-00014wC; Sun, 14 Aug 94 12:31 PDT Message-Id: To: Brent Chapman cc: majordomo-users@greatcircle.com Subject: Re: "digest" question -- lazy user ;-) In-reply-to: Your message of Sun, 14 Aug 1994 12:18:38 -0700. <199408141918.MAA04899@mycroft.GreatCircle.COM> Date: Sun, 14 Aug 1994 12:31:41 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > "Roger B.A. Klorese" writes: > > # I'm on "digest" version 1.8. One of my digests just rolled from number 199 > # to number 0 -- does anyone have any ideas as to why? > > Disk full caused .number file to get zapped. Cool! --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Mon Aug 15 23:02:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA08849; Mon, 15 Aug 1994 23:02:46 GMT Received: from qks.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA08843; Mon, 15 Aug 1994 16:02:38 -0700 Received: from [192.55.204.23] by qks.com (8.6.4/3.1.012693-Quasar Knowledge Systems) via SMTP; id TAA28031 for ; Mon, 15 Aug 1994 19:06:54 -0400 Message-Id: <199408152306.TAA28031@qks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 15 Aug 1994 19:07:29 -0400 To: majordomo-users@greatcircle.com From: faisal@qks.com (Faisal Nameer Jawdat) Subject: disabling who Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Our company runs some public mailing lists with a low poster/lurker ratio, and we'd like to disable the 'who' command so that people can't join to see who is on the list. What is the best way to go about doing this? Thanks, Faisal Jawdat -- Faisal Jawdat e-mail: faisal@qks.com System Administrator fax: 301-530-5712 Quasar Knowledge Systems, Inc. phone: 301-530-4853 9818 Parkwood Drive, Bethesda, MD 20814 From majordomo-users-owner Wed Aug 17 15:06:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA24123; Wed, 17 Aug 1994 15:06:37 GMT Received: from home.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA24117; Wed, 17 Aug 1994 08:06:30 -0700 Received: (from mzeier@localhost) by home.interaccess.com (8.6.9/8.6.9) id KAA14559 for majordomo-users@greatcircle.com; Wed, 17 Aug 1994 10:08:04 -0500 From: "Matthew R. Zeier" Message-Id: <199408171508.KAA14559@home.interaccess.com> Subject: Help with digest feature To: majordomo-users@greatcircle.com (Majordomo Users list) Date: Wed, 17 Aug 1994 10:08:04 -0500 (CDT) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1097 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have several lists that I maintain set up to digest and have learned how to force Majordomo to digest the lists. One of my list owners would like to set up his list in this fashion: o Have a weekly digest o Have a daily digest So I know I can have a cron for majordomo do those, but can I do both? Or would the weekly digest be the daily digest's archives? Once I have the digest made, and people subscribed to list-digest, how does majordomo know to send the digest out? I'm overall a tad confused on this - thanks for any help. - Matthew ---- Matthew R. Zeier "Do what you can with what you have matthew@interaccess.com where you are." -Teddy Roosevelt http://www.interaccess.com/mzeier.html ...................................................................... InterAccess Company Technical Support: 708/498-3842 3345 Commercial Avenue Modem Line: 708/498-3960 Northbrook, IL 60062 Fax Line: 708/498-3289 "Oh and where will you be in 10 years? I'll be on Mars myself." From majordomo-users-owner Wed Aug 17 20:01:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA26810; Wed, 17 Aug 1994 20:01:19 GMT Received: from central.darpa.mil by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA26804; Wed, 17 Aug 1994 13:01:06 -0700 Received: from mail.darpa.mil by central.darpa.mil (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0) id AA04901; Wed, 17 Aug 94 16:03:40 EDT Message-Id: Date: 17 Aug 1994 16:03:32 U From: "jsullivan" Subject: Archived Files over 32K To: "Majordomo List" X-Mailer: Mail*Link SMTP/MS 3.0.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have an archive of documents, many of which are over 32K in size, which I would like to make available for retrieval via e-mail with Majordomo. When I get a document greater than 32K from the Majordomo archive, it is delivered to my MS Mail in-box as a message attachment, which is fine. However, I am worried that for people using other mail applications, the delivery might not be as tidy - ie, they will only get the first 32K or they won't be able to decipher the attachment. What has been the experience of others who have large documents to distribute? TIA, -j o n- Jonathan P. Sullivan, "Webmaster" | jsullivan@arpa.mil [e] Technology Reinvestment Project | 703/696-8947 [v] 3701 N. Fairfax Drive, Arlington, VA 22203-1714 | 703/696-8956 [f] From majordomo-users-owner Thu Aug 18 11:29:03 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA02585; Thu, 18 Aug 1994 11:29:03 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id EAA02577; Thu, 18 Aug 1994 04:28:38 -0700 Received: from bolis by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA16027; Thu, 18 Aug 94 04:33:08 -0700 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0qb4mB-0002XaC; Thu, 18 Aug 94 03:32 PDT Message-Id: From: Alan Millar Subject: Re: Archived Files over 32K To: jsullivan@arpa.mil (jsullivan) Date: Thu, 18 Aug 1994 03:32:49 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "jsullivan" at Aug 17, 94 04:03:32 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: 1295 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst jsullivan spake of these matters: > > I have an archive of documents, many of which are over 32K in size, which I > would like to make available for retrieval via e-mail with Majordomo. When I > get a document greater than 32K from the Majordomo archive, it is delivered > to my MS Mail in-box as a message attachment, which is fine. However, I am > worried that for people using other mail applications, the delivery might not > be as tidy - ie, they will only get the first 32K or they won't be able to > decipher the attachment. What has been the experience of others who have > large documents to distribute? It will depend completely on what mail system/software the various subscribers are using. They are essentially guaranteed to all have different limits and quirks. What's commonly accepted as a reasonable limit varies from one expert's opinion to the next. Generally you hear numbers in the range of 50k to 80k bytes as generally being considered safe. Anything bigger than that you *definitely* want to break up into smaller pieces. - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: ftp://ftp.netcom.com/pub/amillar/welcome.html I believe the word you're looking for is "AAAAAAGHHHHHH!!!!" -Batman Returns From majordomo-users-owner Thu Aug 18 13:33:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA03260; Thu, 18 Aug 1994 13:33:39 GMT Received: from qks.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA03254; Thu, 18 Aug 1994 06:33:30 -0700 Received: from [192.55.204.23] by qks.com (8.6.4/3.1.012693-Quasar Knowledge Systems) via SMTP; id JAA08182 for ; Thu, 18 Aug 1994 09:37:54 -0400 Message-Id: <199408181337.JAA08182@qks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 18 Aug 1994 09:38:32 -0400 To: majordomo-users@greatcircle.com From: faisal@qks.com (Faisal Nameer Jawdat) Subject: admin bounces Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I keep having this problem where people will send a letter to a list, and the letter will bounce with an admin request because somewhere in the body of text it contains the word "help" or "who". How do I fix it so it lets those through and only deals with admin stuff at the majordomo address? Is there some way that it will only deal with it as an admin request if it matches the proper form (command at beginning of line, no impropper or unrecognized commands, command syntax must be correct, etc)? -fiz From majordomo-users-owner Thu Aug 18 22:48:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id WAA06408; Thu, 18 Aug 1994 22:48:53 GMT Received: from red3.cac.washington.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA06402; Thu, 18 Aug 1994 15:48:46 -0700 Received: by red3.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA13565; Thu, 18 Aug 94 15:53:20 -0700 From: Dave Dittrich Message-Id: <9408182253.AA13565@red3.cac.washington.edu> Subject: Mysterious infinite loops during "subscribe" (v1.92) To: majordomo-users@GreatCircle.COM Date: Thu, 18 Aug 1994 15:53:18 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 742 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I don't recall seeing anything about this on the list (but then my short term memory is pretty fried from putting out fires lately ;-) but I have been experieincing a problem with majordomo 1.92 going into an infinite loop of some sort when processing subscription requests sent to "list-request@site" (as opposed to "majordomo@site", which may or may not be significant). This is on an Ultrix 4.2a system running perl 4.0 (Revision: 4.0.1.7, Patch level: 35). Is this a known problem? Will turning off the "list-request@site" style processing work any better? -- Dave Dittrich Client Services dittrich@cac.washington.edu Computing & Communications dittrich@u.washington.edu University of Washington From majordomo-users-owner Fri Aug 19 02:06:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA07330; Fri, 19 Aug 1994 02:06:08 GMT Received: from wolfe.wimsey.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA07321; Thu, 18 Aug 1994 19:05:57 -0700 Received: from hustad by wolfe.wimsey.com with uucp (Smail3.1.28.1 #9) id m0qbJPZ-000CLeC; Thu, 18 Aug 94 19:10 PDT Received: by hustad.com (1.65/waf) via UUCP; Thu, 18 Aug 94 19:01:12 PDT for majordomo-users@GreatCircle.COM To: majordomo-users@GreatCircle.COM Subject: who, which , why? From: raymond@hustad.com (Raymond Hustad) Reply-To: Raymond@Hustad.com Message-ID: <6c80qc2w165w@hustad.com> Date: Thu, 18 Aug 94 18:30:16 PDT Organization: Hustad Associates Consulting Ltd. Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am the owner of a new list which is located on the host of my service provider. Some of my subscribers seem to be getting messages, but others are not. (including myself) A `who' command shows all subscribers as being listed. >>>> who chanter-liste Members of list 'chanter-liste': ...more names... ...etc... raymond@hustad.com (Raymond Hustad) ...more names... ...etc. But a `which' command shows the identical address as not being matched to the list. >>>> which The string 'raymond@hustad.com' appears in the following entries in lists served by Majordomo@wimsey.com: **** No matches found Is this due to the strip parameter = no ? Would this be the reason I am not receiving any messages sent to the list? And why? (Note: I do receive all administrivia messages re-directed from the list but thats all- I don't receive any of the messages). Also, one other naive question dealing with digest mode. In the readme file it states that the config file has both digest and resend parameters. > The config file is meant to be self-documenting. A representative file > is included below. Note that it has both digest and resend parameters > in it, so the person configuring the file needs to know whether the > list is being handled by digest (e.g. test-digest), or resend > (e.g. test), or neither. If the list is NOT meant to be a digest version - should the sections containing digest parameters be commented out? Which line in the config file effectively states whether the list is in in digest mode? I know mkdigest is used for generating digests, but which line says the list is set up for digest mode or not? ( I don't want digest mode on ). Thanks, Ray --- Raymond@Hustad.com owner - chanter-liste@wimsey.com (for fans of french musique) From majordomo-users-owner Fri Aug 19 04:10:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA09281; Fri, 19 Aug 1994 09:18:00 GMT Received: from baram.kaist.ac.kr by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA09275; Fri, 19 Aug 1994 02:17:39 -0700 Received: from localhost (mimi@localhost) by baram.kaist.ac.kr (8.6.4/8.6.4) id SAA09398 for majordomo-users@GreatCircle.COM; Fri, 19 Aug 1994 18:20:20 +0900 From: Seo Hongwon Message-Id: <199408190920.SAA09398@baram.kaist.ac.kr> To: majordomo-users@GreatCircle.COM Date: Fri, 19 Aug 1994 18:20:20 +0900 (KST) X-Mailer: ELM [version 2.4 PL21-h3] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 394 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk who majordomo-users --- ______________ ______________ / __ \_________) Seo Hongwon (_________/ __ \ / | |___) mimi@kaist.ac.kr (___| | \ / (\_|__) Applied Fluid Mechanics Lab., KAIST (__|_/) \ / (_____) +82-42-869-5014 (_____) \ From majordomo-users-owner Fri Aug 19 06:01:03 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA10174; Fri, 19 Aug 1994 12:00:51 GMT Received: from jess.ccc.nottingham.ac.uk by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id FAA10168; Fri, 19 Aug 1994 05:00:39 -0700 Received: from unicorn.ccc.nottingham.ac.uk by jess.ccc.nottingham.ac.uk with SMTP (PP) id <26907-0@jess.ccc.nottingham.ac.uk>; Fri, 19 Aug 1994 13:04:53 +0100 Received: from unicorn.ccc.nottingham.ac.uk (ccsun15) by unicorn.nott.ac.uk (4.1/940615) id AA05807; Fri, 19 Aug 94 13:04:47 BST To: Alan Millar Cc: jsullivan@arpa.mil (jsullivan), majordomo-users@GreatCircle.COM Subject: Re: Archived Files over 32K In-Reply-To: Message from amillar@bolis.sf-bay.org of 18 Aug 1994 3:32:49 -0800 X-Organization: Cripps Computing Centre, University of Nottingham Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Id: <2279.777297883.1@unicorn.ccc.nottingham.ac.uk> Date: Fri, 19 Aug 1994 13:04:44 +0100 Message-Id: <2280.777297884@unicorn.ccc.nottingham.ac.uk> From: David Osborne Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Alan Millar writes [18 Aug 1994 3:32:49 -0800]: > It will depend completely on what mail system/software the various > subscribers are using. They are essentially guaranteed to all have > different limits and quirks. > > What's commonly accepted as a reasonable limit varies from one expert's > opinion to the next. Generally you hear numbers in the range of > 50k to 80k bytes as generally being considered safe. Anything bigger > than that you *definitely* want to break up into smaller pieces. Internet hosts are required to handle messages at least 64K bytes in size, as specified in RFC1123 (host requirements), page 68: Mailer software MUST be able to send and receive messages of at least 64K bytes in length (including header), and a much larger maximum size is highly desirable. ~~David Osborne Cripps Computing Centre, University of Nottingham From majordomo-users-owner Fri Aug 19 13:26:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA10718; Fri, 19 Aug 1994 13:26:27 GMT Received: from qks.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA10712; Fri, 19 Aug 1994 06:26:10 -0700 Received: from [192.55.204.23] by qks.com (8.6.4/3.1.012693-Quasar Knowledge Systems) via SMTP; id JAA12072 for ; Fri, 19 Aug 1994 09:30:32 -0400 Message-Id: <199408191330.JAA12072@qks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 19 Aug 1994 09:31:10 -0400 To: majordomo-users@greatcircle.com From: faisal@qks.com (Faisal Nameer Jawdat) Subject: Re: Archived Files over 32K Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >Internet hosts are required to handle messages at least 64K bytes in >size, as specified in RFC1123 (host requirements), page 68: > > Mailer software MUST be able to send and receive messages of at > least 64K bytes in length (including header), and a much larger > maximum size is highly desirable. However, always remember rule number one of the Internet: "some bozo thinks he's got a better way". Lots of mail systems ignore that part of the RFC (the one I'm using, for instance, has problems with mail larger than 28k)(oh, and it also won't let you add a Reply-To header)(and it won't let you reply wide, and the authors said they wouldn't support IMAP because IMAP doesn't let you have .sig files) so you have systems which will bail as low as 10k (note that these are typically online providers, so you might as well just chalk this up to online-provider stupidity and ignore them, these are the sorts of internet sites we need less of) and some which will willingly let you mail a several meg file to someone with no problem. -fiz From majordomo-users-owner Fri Aug 19 13:30:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA10744; Fri, 19 Aug 1994 13:30:27 GMT Received: from zoom.bga.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA10738; Fri, 19 Aug 1994 06:30:20 -0700 Received: (from sprater@localhost) by zoom.bga.com (8.6.9/8.6.9) id IAA15278; Fri, 19 Aug 1994 08:34:51 -0500 Date: Fri, 19 Aug 1994 08:34:50 -0500 (CDT) From: Scott Prater Subject: reply-to header: Thanks 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 Thanks to everyone who offered their suggestions on how to include a "Reply to:" header in postings to the list. I contacted my host administrator, and he was able to get the header configurations up and working in no time. --Scott Prater sprater@bga.com From majordomo-users-owner Fri Aug 19 13:52:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA10914; Fri, 19 Aug 1994 13:52:12 GMT Received: from gatekeeper.roche.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA10907; Fri, 19 Aug 1994 06:51:52 -0700 Received: by gatekeeper.roche.com (5.65/fma-120691); id AA11486; Fri, 19 Aug 94 09:55:59 -0400 Received: by mailgate.roche.com (5.65/fma-120691); id AA27355; Fri, 19 Aug 94 09:55:57 -0400 Received: from conversion.RBAC01 by RBAC01.BAS.ROCHE.COM (PMDF V4.3-7 #5197) id <01HG3KGGMS1S985O3L@RBAC01.BAS.ROCHE.COM>; Fri, 19 Aug 1994 15:45:53 MET Received: from mr.bas.roche.com by RBAC01.BAS.ROCHE.COM (PMDF V4.3-7 #5197) id <01HG3K3XYG1S96WOPF@RBAC01.BAS.ROCHE.COM>; Fri, 19 Aug 1994 15:36:22 MET Received: with PMDF-MR; Fri, 19 Aug 1994 15:34:02 MET Mr-Received: by mta ROCBI.MUAS; Relayed; Fri, 19 Aug 1994 15:34:02 +0100 Mr-Received: by mta RBIZ06; Relayed; Fri, 19 Aug 1994 15:34:04 +0100 Mr-Received: by mta RBAC01; Relayed; Fri, 19 Aug 1994 15:34:05 +0100 Disclose-Recipients: prohibited Date: Fri, 19 Aug 1994 15:34:02 +0100 (MET) From: BAUMANNM +61 68 73 52 0 Subject: Question and Assistance To: Majord User Message-Id: <2102341519081994/A68574/RBIZ06/11889BE13700*@MHS> Autoforwarded: false Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary (ID q4gYDALi0SrfOJvjyEUkrQ)" Content-Transfer-Encoding: 7BIT Conversion: prohibited Importance: low Priority: non-urgent Ua-Content-Id: 11889BE13700 X400-Mts-Identifier: [;2102341519081994/A68574/RBIZ06] Hop-Count: 2 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk --Boundary (ID q4gYDALi0SrfOJvjyEUkrQ) Content-type: TEXT/PLAIN; CHARSET=US-ASCII Hi I am new to the list but after reading the archives and the README file and testing the Majordomo server I have one question: I am running majordomo on a HP (V 9.0.1) and I installed it as described. I know that this question was asked several times but I do not understand the answer or the solution described is not working on the HP. Everything works fine but I have to open the permission world wide on the wrapper, W_BIN, listdir, homedir and the Log. I tested it with the POSIX version and now difference. Right now I am using the POSIX version drwxrwxrwx majodom majodom mail.lists (listdir) drwxrwxrwx majodom majodom bin (homedir) -rwsr-xr-x root majodom wrapper chmod 775 for dir and 664 for files produces access errors! Any help is appreciated. Information: The reason why I installed majordomo was to distribute forms and these forms should be replyable to the list. If I sent a mail to majordomo with the get command in the body get form-list form11 The e-mail result has in the From field Majordomo@a.b.c but I want form-list@a.b.c in this field. Is this possible? I do not want that all majordomo mail have the form-list@a.b.c in the FROM or Reply-to field. I thought it is maybe possible to have an alias form-list-request: "|/usr/local/majodom/wrapper request-answer form11" Any ideas? Maybe their is a different way to solve the problem. -r Michael --Boundary (ID q4gYDALi0SrfOJvjyEUkrQ) Content-type: TEXT/PLAIN; CHARSET=US-ASCII ________________________________________________________________ Michael Baumann \ Department: PRIT \ There are three roads to ruin: F.Hoffmann - La Roche Ltd \ Gambling is the most expensive Build. 74 / 1 West CH 4002 Basel \ Sex the most fun Phone: +41 / 6873520 Fax: +41 / 6872897 \ Running a MIS shop the most shure E-Mail: michael.baumann@Roche.com \ _________________________________________________________________ --Boundary (ID q4gYDALi0SrfOJvjyEUkrQ)-- From majordomo-users-owner Fri Aug 19 15:58:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA11741; Fri, 19 Aug 1994 15:58:23 GMT Received: from who.net.uokhsc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA11735; Fri, 19 Aug 1994 08:58:06 -0700 Received: from MSSMTP.NET.UOKHSC.EDU by who.net.uokhsc.edu (5.64/A/UX-3.00) id AA08532; Fri, 19 Aug 94 11:03:53 PDT Received: by MSSMTP.NET.uokhsc.edu with Microsoft Mail id <2E54F1D2@MSSMTP.NET.uokhsc.edu>; Fri, 19 Aug 94 10:54:26 PDT From: Brian Fairless To: "'Major domo users'" Subject: Listing problem Date: Fri, 19 Aug 94 11:04:00 PDT Message-Id: <2E54F1D2@MSSMTP.NET.uokhsc.edu> Encoding: 37 TEXT X-Mailer: Microsoft Mail V3.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I know that this is probably a FAQ, but I will risk being flamed. I have set up Majordomo at my site and for the most part everything seems to work correctly except for the lists, and which commands. they both come back with nothing to report for example. -- >>>> lists lists@who.uokhsc.edu serves the following lists: Use the 'info ' command to get more information about a specific list. I don't know what to do every other command seems to work. I have looked at the config scripts for each individual list and I have even put in regular expressions in the advertise section, but nothing seems to work. HELP !!!!! please. by the way I am running majordomo 1.92 ------------------------------------------------------------------ Brian Fairless Senior Network Analyst University Of Oklahoma Health Sciences Center 1100 North Lindsay rm 102 Oklahoma City, OK. 73190 Voice (405)271-1905 Fax (405)271-3627 brian-fairless@uokhsc.edu ------------------------------------------------------------------ From majordomo-users-owner Fri Aug 19 16:59:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA12051; Fri, 19 Aug 1994 16:59:17 GMT Received: from who.net.uokhsc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA12045; Fri, 19 Aug 1994 09:59:10 -0700 Received: from MSSMTP.NET.UOKHSC.EDU by who.net.uokhsc.edu (5.64/A/UX-3.00) id AA08783; Fri, 19 Aug 94 12:05:08 PDT Received: by MSSMTP.NET.uokhsc.edu with Microsoft Mail id <2E55002C@MSSMTP.NET.uokhsc.edu>; Fri, 19 Aug 94 11:55:40 PDT From: Brian Fairless To: "'Major domo users'" Date: Fri, 19 Aug 94 12:05:00 PDT Message-Id: <2E55002C@MSSMTP.NET.uokhsc.edu> Encoding: 2 TEXT X-Mailer: Microsoft Mail V3.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk get majordomo-users.9407 From majordomo-users-owner Fri Aug 19 17:01:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA12105; Fri, 19 Aug 1994 17:01:22 GMT Received: from who.net.uokhsc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id KAA12099; Fri, 19 Aug 1994 10:01:14 -0700 Received: from MSSMTP.NET.UOKHSC.EDU by who.net.uokhsc.edu (5.64/A/UX-3.00) id AA08796; Fri, 19 Aug 94 12:07:11 PDT Received: by MSSMTP.NET.uokhsc.edu with Microsoft Mail id <2E5500A7@MSSMTP.NET.uokhsc.edu>; Fri, 19 Aug 94 11:57:43 PDT From: Brian Fairless To: "'Major domo users'" Date: Fri, 19 Aug 94 12:08:00 PDT Message-Id: <2E5500A7@MSSMTP.NET.uokhsc.edu> Encoding: 2 TEXT X-Mailer: Microsoft Mail V3.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk get FAQ From majordomo-users-owner Fri Aug 19 17:43:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA12310; Fri, 19 Aug 1994 17:43:20 GMT Received: from global by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id KAA12304; Fri, 19 Aug 1994 10:43:01 -0700 Received: from tsquare by global with uucp (Smail3.1.28.1 #1) id m0qbUZ2-0006VhC; Fri, 19 Aug 94 14:05 GMT Received: by tsquare.com (Smail3.1.28.1 #52) id m0qbTlu-000AUIC; Fri, 19 Aug 94 13:14 Date: Fri, 19 Aug 1994 13:14:13 +0000 From: "John M. Trindle" Subject: Re: Question and Assistance To: majordomo-users@greatcircle.com In-Reply-To: <2102341519081994/A68574/RBIZ06/11889BE13700*@MHS> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary (ID q4gYDALi0SrfOJvjyEUkrQ)" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --Boundary (ID q4gYDALi0SrfOJvjyEUkrQ) Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 19 Aug 1994, BAUMANNM +61 68 73 52 0 wrote: > drwxrwxrwx majodom majodom mail.lists (listdir) > drwxrwxrwx majodom majodom bin (homedir) > -rwsr-xr-x root majodom wrapper > > chmod 775 for dir and 664 for files produces access errors! Wrapper needs to be set to user "majodom" if I read this correctly. Then the list directory can be set to -rw-r--r-- I don't understand the other question (but hey, I just got this majordomo stuff working a few days ago). BTW, whoever supervises this list... >it< needs a Reply-To: line. John M. Trindle | Williamsburg Town Square | jtrindle@tsquare.com T-Square Company | 804-220-0533 login: bbs | jtrindle@world.std.com ISS/FSPlan for FS5 | Free Internet Mail | 70303.3506@compuserve.com Flight Deck IFT-PRO | Usenet Newsgroups | TeamRX@aol.com --Boundary (ID q4gYDALi0SrfOJvjyEUkrQ)-- From majordomo-users-owner Fri Aug 19 18:09:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA12491; Fri, 19 Aug 1994 18:09:43 GMT Received: from who.net.uokhsc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA12478; Fri, 19 Aug 1994 11:09:30 -0700 Received: from MSSMTP.NET.UOKHSC.EDU by who.net.uokhsc.edu (5.64/A/UX-3.00) id AA09049; Fri, 19 Aug 94 13:15:30 PDT Received: by MSSMTP.NET.uokhsc.edu with Microsoft Mail id <2E5510A8@MSSMTP.NET.uokhsc.edu>; Fri, 19 Aug 94 13:06:00 PDT From: Brian Fairless To: "'Majordomo users'" Subject: Sorry Date: Fri, 19 Aug 94 13:13:00 PDT Message-Id: <2E5510A8@MSSMTP.NET.uokhsc.edu> Encoding: 4 TEXT X-Mailer: Microsoft Mail V3.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Sorry for the two previous goof ups. I hope you guys will forgive me. Brian From majordomo-users-owner Fri Aug 19 18:14:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA12571; Fri, 19 Aug 1994 18:14:58 GMT Received: from duke.cs.duke.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA12565; Fri, 19 Aug 1994 11:14:48 -0700 Received: from london.chem.duke.edu by duke.cs.duke.edu (5.65/3.9G/4.1.3) id AA27117; Fri, 19 Aug 94 14:18:28 -0400 Received: from affymax.chem.duke.edu by london.chem.duke.edu (5.64/1.19LP/4.1.1) id AA03611; Fri, 19 Aug 94 14:18:26 -0400 Received: by affymax.chem.duke.edu (5.64/2.12L/4.1) id AA00554; Fri, 19 Aug 94 14:18:26 -0400 Date: Fri, 19 Aug 94 14:18:26 -0400 From: yuji@chem.duke.edu (Yuji Shinozaki) Message-Id: <9408191818.AA00554@affymax.chem.duke.edu> To: jtrindle@tsquare.com Subject: Re: Question and Assistance Cc: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > From jtrindle@tsquare.com Fri Aug 19 14:05:07 1994 > Subject: Re: Question and Assistance > To: majordomo-users@GreatCircle.COM > Sender: Majordomo-Users-Owner@GreatCircle.COM > > > On Fri, 19 Aug 1994, BAUMANNM +61 68 73 52 0 wrote: > > > drwxrwxrwx majodom majodom mail.lists (listdir) > > drwxrwxrwx majodom majodom bin (homedir) > > -rwsr-xr-x root majodom wrapper > > > > chmod 775 for dir and 664 for files produces access errors! > > Wrapper needs to be set to user "majodom" if I read this correctly. Then > the list directory can be set to -rw-r--r-- > Alternatively, you can set wrapper to set gid majordom (chmod g+s). I would also set wrapper to owner daemon or something other than root. It does not need to be (and probably shouldn't be) suid root. > I don't understand the other question (but hey, I just got this majordomo > stuff working a few days ago). > > BTW, whoever supervises this list... >it< needs a Reply-To: line. There are a few reason NOT to put in a Reply-To: line. On some mailers it is difficult to respond to just the sender if the Reply-To: field is the mailing-list. Without it, you can always "Reply to Group" or "Reply to All" or some such to get it to reply to the list. yuji ---- Yuji Shinozaki Computer Systems Manager (919)660-1514 Box 90347 / Dept of Chemistry yuji@chem.duke.edu Duke University http://www.chem.duke.edu Durham, NC 27708-0347 From majordomo-users-owner Fri Aug 19 18:28:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA12717; Fri, 19 Aug 1994 18:28:57 GMT Received: from who.net.uokhsc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA12710; Fri, 19 Aug 1994 11:28:40 -0700 Received: from MSSMTP.NET.UOKHSC.EDU by who.net.uokhsc.edu (5.64/A/UX-3.00) id AA09101; Fri, 19 Aug 94 13:34:33 PDT Received: by MSSMTP.NET.uokhsc.edu with Microsoft Mail id <2E55151F@MSSMTP.NET.uokhsc.edu>; Fri, 19 Aug 94 13:25:03 PDT From: Brian Fairless To: "'Majordomo users'" Subject: Listing problem Date: Fri, 19 Aug 94 13:35:00 PDT Message-Id: <2E55151F@MSSMTP.NET.uokhsc.edu> Encoding: 36 TEXT X-Mailer: Microsoft Mail V3.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I know that this is probably a FAQ, but I will risk being flamed. I have set up Majordomo at my site and for the most part everything seems to work correctly except for the lists, and which commands. they both come back with nothing to report for example. -- >>>> lists lists@who.uokhsc.edu serves the following lists: Use the 'info ' command to get more information about a specific list. I don't know what to do every other command seems to work. I have looked at the config scripts for each individual list and I have even put in regular expressions in the advertise section, but nothing seems to work. HELP !!!!! please. by the way I am running majordomo 1.92 ------------------------------------------------------------------ Brian Fairless Senior Network Analyst University Of Oklahoma Health Sciences Center 1100 North Lindsay rm 102 Oklahoma City, OK. 73190 Voice (405)271-1905 Fax (405)271-3627 brian-fairless@uokhsc.edu ------------------------------------------------------------------ From majordomo-users-owner Fri Aug 19 21:29:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA13913; Fri, 19 Aug 1994 21:29:27 GMT Received: from who.net.uokhsc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA13907; Fri, 19 Aug 1994 14:29:17 -0700 Received: from MSSMTP.NET.UOKHSC.EDU by who.net.uokhsc.edu (5.64/A/UX-3.00) id AA09974; Fri, 19 Aug 94 16:35:16 PDT Received: by MSSMTP.NET.uokhsc.edu with Microsoft Mail id <2E55420B@MSSMTP.NET.uokhsc.edu>; Fri, 19 Aug 94 16:36:43 PDT From: Brian Fairless To: "'Majordomo users'" Subject: Listing problem Date: Fri, 19 Aug 94 16:35:00 PDT Message-Id: <2E55420B@MSSMTP.NET.uokhsc.edu> Encoding: 41 TEXT X-Mailer: Microsoft Mail V3.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk at the risk of really getting flamed I will send this again, because my mailer got hosed today and I couldn't receive any mail. ----------------- I know that this is probably a FAQ, but I will risk being flamed. I have set up Majordomo at my site and for the most part everything seems to work correctly except for the lists, and which commands. they both come back with nothing to report for example. -- >>>> lists lists@who.uokhsc.edu serves the following lists: Use the 'info ' command to get more information about a specific list. I don't know what to do every other command seems to work. I have looked at the config scripts for each individual list and I have even put in regular expressions in the advertise section, but nothing seems to work. HELP !!!!! please. by the way I am running majordomo 1.92 ------------------------------------------------------------------ Brian Fairless Senior Network Analyst University Of Oklahoma Health Sciences Center 1100 North Lindsay rm 102 Oklahoma City, OK. 73190 Voice (405)271-1905 Fax (405)271-3627 brian-fairless@uokhsc.edu ------------------------------------------------------------------ From majordomo-users-owner Sat Aug 20 02:06:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA15139; Sat, 20 Aug 1994 02:06:55 GMT Received: from global by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA15133; Fri, 19 Aug 1994 19:06:45 -0700 Received: from tsquare by global with uucp (Smail3.1.28.1 #1) id m0qbcQu-0006b6C; Fri, 19 Aug 94 22:29 GMT Received: by tsquare.com (Smail3.1.28.1 #52) id m0qbbnw-000AUIC; Fri, 19 Aug 94 21:48 Date: Fri, 19 Aug 1994 21:48:51 +0000 From: "John M. Trindle" Subject: Re: Question and Assistance To: majordomo-users@greatcircle.com In-Reply-To: <9408191818.AA00554@affymax.chem.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Fri, 19 Aug 1994, Yuji Shinozaki wrote: > > From jtrindle@tsquare.com Fri Aug 19 14:05:07 1994 > > Subject: Re: Question and Assistance > > To: majordomo-users@GreatCircle.COM > > Sender: Majordomo-Users-Owner@GreatCircle.COM > > > > > > On Fri, 19 Aug 1994, BAUMANNM +61 68 73 52 0 wrote: > > > > > drwxrwxrwx majodom majodom mail.lists (listdir) > > > drwxrwxrwx majodom majodom bin (homedir) > > > -rwsr-xr-x root majodom wrapper > > > > > > chmod 775 for dir and 664 for files produces access errors! > > > > Wrapper needs to be set to user "majodom" if I read this correctly. Then > > the list directory can be set to -rw-r--r-- > > > > Alternatively, you can set wrapper to set gid majordom (chmod g+s). I would > also set wrapper to owner daemon or something other than root. It does not > need to be (and probably shouldn't be) suid root. > In case I am not using the terminology correctly, I mean "you need to chown majodom.majodom wrapper." > > I don't understand the other question (but hey, I just got this majordomo > > stuff working a few days ago). > > > > BTW, whoever supervises this list... >it< needs a Reply-To: line. > > There are a few reason NOT to put in a Reply-To: line. On some mailers > it is difficult to respond to just the sender if the Reply-To: field > is the mailing-list. Without it, you can always "Reply to Group" or > "Reply to All" or some such to get it to reply to the list From majordomo-users-owner Sat Aug 20 02:13:35 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA15193; Sat, 20 Aug 1994 02:13:35 GMT Received: from pluto by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA15187; Fri, 19 Aug 1994 19:13:28 -0700 Received: by pluto (Smail3.1.28.1 #6) id m0qbfzN-0002ebC; Fri, 19 Aug 94 22:16 EDT Date: Fri, 19 Aug 1994 22:16:57 +0100 From: Brian Kramer Subject: Majordomo/Linux & Smail To: Majordomo Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Does anyone have majordomo setup with linux and smail? Is this possible? Brian Kramer - Owner/Systems Administrator - bjkramer@pluto.njcc.com New Jersey Computer Connection - Public Access Unix Site - pluto.njcc.com Voice: 609-896-2799 - Fax: 609-896-2994 - Dialups: 609-896-3191 Dialup or Telnet to pluto.njcc.com and log in as guest for more information. From majordomo-users-owner Sat Aug 20 04:37:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id EAA15849; Sat, 20 Aug 1994 04:37:37 GMT Received: from ilium.troy.msen.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA15841; Fri, 19 Aug 1994 21:37:25 -0700 Received: from angus by ilium.troy.msen.com with uucp (Smail3.1.28.1 #1) id m0qbiEs-0002nTC; Sat, 20 Aug 94 00:41 EDT Received: from glynis by angus.mystery.com with uucp (Smail3.1.28.1 #6) id m0qbiEE-000BfwC; Sat, 20 Aug 94 00:40 EDT Received: by glynis (Smail3.1.28.1 #1) id m0qbhGe-000063C; Fri, 19 Aug 94 23:38 EDT Message-Id: From: gabe@glynis.mystery.com (Gabe Helou) Subject: Re: Majordomo/Linux & Smail To: bjkramer@pluto.njcc.com (Brian Kramer) Date: Fri, 19 Aug 1994 23:38:50 -0400 (EDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Brian Kramer" at Aug 19, 94 10:16:57 pm Reply-To: gabe@mystery.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 472 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk ... and then Brian Kramer says: ] Does anyone have majordomo setup with linux and smail? Is this possible? I'm current running Majordomo 1.62 under Linux with smail. It is possible, but it's been so long since I installed it that I don't recall what the installation was like. If you cite some specific problems, I may be able to recognize them and remember what I did to handle it. -- --- -- - - - - - - - - From majordomo-users-owner Sat Aug 20 06:58:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA16216; Sat, 20 Aug 1994 06:58:05 GMT Received: from mailgate.ericsson.se by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA16210; Fri, 19 Aug 1994 23:57:56 -0700 Received: from eua.ericsson.se by mailgate.ericsson.se (4.1/SMI-4.1-MAILGATE1.14) id AA00670; Sat, 20 Aug 94 09:02:37 +0200 Received: from ms.eua.ericsson.se by eua.ericsson.se (4.1/EUA-2.1) id AA11832; Sat, 20 Aug 94 09:02:35 +0200 Received: from etxbs3.eua.ericsson.se (etxbs3.etxb.eua.ericsson.se) by ms.eua.ericsson.se (4.1/MS-2.1) id AA09430; Sat, 20 Aug 94 09:02:34 +0200 Received: from etxus2c25.eua.ericsson.se by etxbs3.eua.ericsson.se (4.1/SMI-4.1-MS1.99) id AA19230; Sat, 20 Aug 94 09:02:34 +0200 From: etxpihl@etxb.eua.ericsson.se (Tomas Pihl ETX/B/DG) Received: by etxus2c25.eua.ericsson.se (4.1/client-1.3) id AA13871; Sat, 20 Aug 94 09:02:32 +0200 Date: Sat, 20 Aug 94 09:02:32 +0200 Message-Id: <9408200702.AA13871@etxus2c25.eua.ericsson.se> To: Majordomo-Users@GreatCircle.COM Subject: List problems Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've just created a new mailinglist but for some reason majordomo doesn't find it. A `lists' results in: >>>> lists majordomo@etxb.eua.ericsson.se serves the following lists: SDS-trouble sas-dev test When I try to subscribe, I get: >>>> subscribe SDS-trouble **** subscribe: unknown list 'SDS-trouble'. **** Help for majordomo@etxb.eua.ericsson.se: From majordomo-users-owner Sat Aug 20 08:04:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA16406; Sat, 20 Aug 1994 08:04:04 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA16400; Sat, 20 Aug 1994 01:03:51 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qblPz-00014wC; Sat, 20 Aug 94 01:04 PDT Message-Id: To: etxpihl@etxb.eua.ericsson.se (Tomas Pihl ETX/B/DG) cc: Majordomo-Users@greatcircle.com Subject: Re: List problems In-reply-to: Your message of Sat, 20 Aug 1994 09:02:32 +0200. <9408200702.AA13871@etxus2c25.eua.ericsson.se> Date: Sat, 20 Aug 1994 01:04:15 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > From: etxpihl@etxb.eua.ericsson.se (Tomas Pihl ETX/B/DG) > I've just created a new mailinglist but for some reason majordomo > doesn't find it. > > A `lists' results in: > > >>>> lists > majordomo@etxb.eua.ericsson.se serves the following lists: > > SDS-trouble > sas-dev > test > > When I try to subscribe, I get: > > >>>> subscribe SDS-trouble > **** subscribe: unknown list 'SDS-trouble'. > **** Help for majordomo@etxb.eua.ericsson.se: Don't use mixed case in list names. Majordomo converts names to lower case on input before comparison, but does not lower-case the filenames. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Sat Aug 20 15:08:34 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA18099; Sat, 20 Aug 1994 15:08:34 GMT Received: from pluto by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA18093; Sat, 20 Aug 1994 08:08:28 -0700 Received: by pluto (Smail3.1.28.1 #6) id m0qbs59-0002ebC; Sat, 20 Aug 94 11:11 EDT Date: Sat, 20 Aug 1994 11:11:43 +0100 From: Brian Kramer Subject: Help - Setting Up Majordomo To: Majordomo Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have set everything up and am trying to get a test list to run. I am using smail and linux and have used the posix options in the makefile. I have setup a list called test. Whenever I send something to majordomo (I do have the aliases setup) the message vanishes. In the smail log I see child returned status EX_2. Just to try to figure out what was going on I tried to run wrapper majordomo by hand and get {W_MAJORDOMO_CF} not readable; stopped at /home/home1/majordomo/majordomo line 44 When I send something to test it says no valid recipients and bounces. Brian Kramer - Owner/Systems Administrator - bjkramer@pluto.njcc.com New Jersey Computer Connection - Public Access Unix Site - pluto.njcc.com Voice: 609-896-2799 - Fax: 609-896-2994 - Dialups: 609-896-3191 Dialup or Telnet to pluto.njcc.com and log in as guest for more information. From majordomo-users-owner Sun Aug 21 00:39:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id AAA20662; Sun, 21 Aug 1994 00:39:54 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA03505; Thu, 18 Aug 1994 07:44:09 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HG1XUV5VKW0055PT@SYSWRK.UCIS.DAL.CA>; Thu, 18 Aug 1994 11:48:30 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HG1XUM7SU80125B3@AC.DAL.CA>; Thu, 18 Aug 1994 11:48:19 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA12616; Thu, 18 Aug 94 11:40:43 -0300 Date: Thu, 18 Aug 1994 11:40:42 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Problems with the subscription process To: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9408181440.AA12616@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: 798 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In processing some Majorddomo subscriptions I ran into two problems: 1. I sent the follow message to Majordomo approve password unsubscribe list bill approve password subscribe list bill@biome.bio.ns.ca and got back the message that bill was not subscribed. The name bill was in the file, I deleted it by hand, but why did this happen? 2. The welcome message I got when the subscription for the full name got processed told me that to unsubscribe I should send the message unsubscribe list bill@biome.bio.ns.ca to Majordomo. I thought that `unsubscribe list' would suffice? -- 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 Sun Aug 21 01:20:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA20930; Sun, 21 Aug 1994 01:20:13 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA20702; Sat, 20 Aug 1994 17:53:05 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qc1Do-00014xC; Sat, 20 Aug 94 17:57 PDT Message-Id: To: bill@biome.bio.ns.ca (Bill Silvert) cc: Majordomo-Users@greatcircle.com (Majordomo Users) Subject: Re: Problems with the subscription process In-reply-to: Your message of Thu, 18 Aug 1994 11:40:42 -0300. <9408181440.AA12616@biome.bio.ns.ca> Date: Sat, 20 Aug 1994 17:57:08 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > 2. The welcome message I got when the subscription for the full name > got processed told me that to unsubscribe I should send the message > > unsubscribe list bill@biome.bio.ns.ca > > to Majordomo. I thought that `unsubscribe list' would suffice? It would. however, since users often don't know what address they-re listed as, it's a good idea to notify them of their full addresses. Reasons these might not match incluse: - change of header addresses on their server - use of a different gateway - conversion from BITNET to domain addressing ...etc. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Sun Aug 21 02:39:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA21558; Sun, 21 Aug 1994 02:39:01 GMT Received: from global by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA21547; Sat, 20 Aug 1994 19:38:51 -0700 Received: from tsquare by global with uucp (Smail3.1.28.1 #1) id m0qbzQ3-0006ftC; Sat, 20 Aug 94 23:01 GMT Received: by tsquare.com (Smail3.1.28.1 #52) id m0qbyvj-000AW3C; Sat, 20 Aug 94 22:30 Date: Sat, 20 Aug 1994 22:30:26 +0000 From: "John M. Trindle" Subject: Re: Problems with the subscription process To: majordomo-users@greatcircle.com In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On my lists, sometimes the address comes in as or just as jtrindle@tsquare.com. I have to add the angle brackets to make the resend command work! So, before you unsubscribe you may have to send majordomo a message to who listname so that you can see what your address >as now used in the system< is. John M. Trindle | Williamsburg Town Square | jtrindle@tsquare.com T-Square Company | 804-220-0533 login: bbs | jtrindle@world.std.com ISS/FSPlan for FS5 | Free Internet Mail | 70303.3506@compuserve.com Flight Deck IFT-PRO | Usenet Newsgroups | TeamRX@aol.com From majordomo-users-owner Sun Aug 21 03:08:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id DAA21726; Sun, 21 Aug 1994 03:08:24 GMT Received: from pluto by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA21720; Sat, 20 Aug 1994 20:08:16 -0700 Received: by pluto (Smail3.1.28.1 #6) id m0qc3KK-0002emC; Sat, 20 Aug 94 23:12 EDT Date: Sat, 20 Aug 1994 23:12:07 +0100 From: Brian Kramer Subject: Help with archive To: Majordomo Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have everything working except the archive. What should the permissions be on the archive directory and file? I have it rw rw r and majordom.majordom for user/group. I get the following From MAILER-DAEMON Sat Aug 20 23:10:49 1994 Return-Path: Received: from pluto by pluto with bsmtp (Smail3.1.28.1 #6) id m0qc3J3-0002enC; Sat, 20 Aug 94 23:10 EDT Message-Id: Date: Sat, 20 Aug 94 23:10 EDT From: To: postmaster Subject: mail failed, sending to postmaster Reference: Status: R |------------------------- Message log follows: -------------------------| Xfail: parent: reason: (ERR_133) transport file: failed to open output file: Permission denied |------------------------- Failed addresses follow: ---------------------| /home/home1/majordomo/lists/njcc-uucp.archive/njcc-uucp ... transport file: failed to open output file: Permission denied |------------------------- Message text follows: ------------------------| Received: by pluto (Smail3.1.28.1 #6) id m0qc3J0-0002emC; Sat, 20 Aug 94 23:10 EDT Message-Id: Date: Sat, 20 Aug 94 23:10 EDT From: bjkramer (Brian Kramer) To: njcc-uucp-archive test Brian Kramer - Owner/Systems Administrator - bjkramer@pluto.njcc.com New Jersey Computer Connection - Public Access Unix Site - pluto.njcc.com Voice: 609-896-2799 - Fax: 609-896-2994 - Dialups: 609-896-3191 Dialup or Telnet to pluto.njcc.com and log in as guest for more information. From majordomo-users-owner Sun Aug 21 03:55:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id DAA22000; Sun, 21 Aug 1994 03:55:55 GMT Received: from pluto by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA21994; Sat, 20 Aug 1994 20:55:46 -0700 Received: by pluto (Smail3.1.28.1 #6) id m0qc44L-0002j6C; Sat, 20 Aug 94 23:59 EDT Date: Sat, 20 Aug 1994 23:59:40 +0100 From: Brian Kramer Subject: Digests To: Majordomo Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Is there any docs on digests? What I could find was very minimal. Brian Kramer - Owner/Systems Administrator - bjkramer@pluto.njcc.com New Jersey Computer Connection - Public Access Unix Site - pluto.njcc.com Voice: 609-896-2799 - Fax: 609-896-2994 - Dialups: 609-896-3191 Dialup or Telnet to pluto.njcc.com and log in as guest for more information. From majordomo-users-owner Sun Aug 21 13:50:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA24202; Sun, 21 Aug 1994 13:50:10 GMT Received: from pluto by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA24195; Sun, 21 Aug 1994 06:50:02 -0700 Received: by pluto (Smail3.1.28.1 #6) id m0qcDKx-0002erC; Sun, 21 Aug 94 09:53 EDT Date: Sun, 21 Aug 1994 09:53:27 +0100 From: Brian Kramer Subject: Re: Digests To: "Matthew R. Zeier" cc: Majordomo Mailing List In-Reply-To: <199408210418.XAA11235@psycfrnd.interaccess.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Sat, 20 Aug 1994, Matthew R. Zeier wrote: > > > > > > Is there any docs on digests? What I could find was very minimal. > > > > > > > > I know what you mean - all I know is that I have my lists digesting, but I > am clueless as to when MD decides to mail those digests out. Any ideas? > I can't even figure out how to set them up, or what exactly they are. I believe they pacakage up a bunch of messages instead of sending individual ones. Brian Kramer - Owner/Systems Administrator - bjkramer@pluto.njcc.com New Jersey Computer Connection - Public Access Unix Site - pluto.njcc.com Voice: 609-896-2799 - Fax: 609-896-2994 - Dialups: 609-896-3191 Dialup or Telnet to pluto.njcc.com and log in as guest for more information. From majordomo-users-owner Mon Aug 22 12:58:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA17782; Mon, 22 Aug 1994 12:58:07 GMT Received: from zoom.bga.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id FAA17776; Mon, 22 Aug 1994 05:57:55 -0700 Received: (from sprater@localhost) by zoom.bga.com (8.6.9/8.6.9) id IAA28295; Mon, 22 Aug 1994 08:02:29 -0500 Date: Mon, 22 Aug 1994 08:02:27 -0500 (CDT) From: Scott Prater Subject: Re: Help with archive To: Brian Kramer cc: Majordomo Mailing List In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Sat, 20 Aug 1994, Brian Kramer wrote: > > I have everything working except the archive. What should the permissions > be on the archive directory and file? I have it rw rw r and > majordom.majordom for user/group. I'm not certain, but I believe the directory/files need to have at least "rw-rw----" permissions (which you have), and the owner/group needs to be "daemon.majordom", at least on the current file being archived. Again, I'm not an expert - wiser heads than mine should confirm or deny this. --Scott Prater From majordomo-users-owner Mon Aug 22 13:14:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA17979; Mon, 22 Aug 1994 13:14:52 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA17973; Mon, 22 Aug 1994 06:14:44 -0700 Received: by interlock.ans.net id AA15730 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Mon, 22 Aug 1994 09:19:15 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Mon, 22 Aug 1994 09:19:15 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 22 Aug 1994 09:19:15 -0400 From: Dan Simoes Message-Id: <199408221319.AA54499@foo.ans.net> Subject: Re: Help with archive To: sprater@bga.com (Scott Prater) Date: Mon, 22 Aug 1994 09:19:13 -0400 (EDT) Cc: bjkramer@pluto.njcc.com, majordomo-users@greatcircle.com In-Reply-To: from "Scott Prater" at Aug 22, 94 08:02:27 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 842 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > I have everything working except the archive. What should the permissions > > be on the archive directory and file? I have it rw rw r and > > majordom.majordom for user/group. > > I'm not certain, but I believe the directory/files need to have at least > "rw-rw----" permissions (which you have), and the owner/group needs to be > "daemon.majordom", at least on the current file being archived. > > Again, I'm not an expert - wiser heads than mine should confirm or deny this. The archive dir nees to be majordom.majordom, 775 (under SunOS). In my experience, if it's a plain file it needs to be 664, if it's a subdir, it needs to be 775. The only exception to this is wrapper. | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From majordomo-users-owner Mon Aug 22 13:56:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA18253; Mon, 22 Aug 1994 13:56:43 GMT Received: from polo.iquest.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA18242; Mon, 22 Aug 1994 06:56:33 -0700 Received: by polo.iquest.com (Linux Smail3.1.28.1 #1) id m0qcZpv-002ENAC; Mon, 22 Aug 94 08:54 CDT Received: from cc:Mail by multi.iquest.com id AA777570404 Mon, 22 Aug 94 08:46:44 Date: Mon, 22 Aug 94 08:46:44 From: "Dougal Campbell" Encoding: 749 Text Message-Id: <9407227775.AA777570404@multi.iquest.com> To: majordomo-users@GreatCircle.COM, Brian Kramer Subject: Re: Help with archive Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >I have everything working except the archive. What should the permissions >be on the archive directory and file? I have it rw rw r and >majordom.majordom for user/group. > > >I get the following > [...message deleted...] > >Brian Kramer - Owner/Systems Administrator - bjkramer@pluto.njcc.com >New Jersey Computer Connection - Public Access Unix Site - pluto.njcc.com >Voice: 609-896-2799 - Fax: 609-896-2994 - Dialups: 609-896-3191 >Dialup or Telnet to pluto.njcc.com and log in as guest for more information. Don't forget that the process needs permissions on the *parent* directories, too. Double check that the majordomo user/group has read and execute permissions on all the parent directories. Dougal Campbell From majordomo-users-owner Mon Aug 22 13:56:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA18255; Mon, 22 Aug 1994 13:56:44 GMT Received: from polo.iquest.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA18243; Mon, 22 Aug 1994 06:56:33 -0700 Received: by polo.iquest.com (Linux Smail3.1.28.1 #1) id m0qcZpu-002ELhC; Mon, 22 Aug 94 08:54 CDT Received: from cc:Mail by multi.iquest.com id AA777570074 Mon, 22 Aug 94 08:41:14 Date: Mon, 22 Aug 94 08:41:14 From: "Dougal Campbell" Encoding: 846 Text Message-Id: <9407227775.AA777570074@multi.iquest.com> To: majordomo-users@GreatCircle.COM, Brian Kramer Subject: Re: Majordomo/Linux & Smail Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >Does anyone have majordomo setup with linux and smail? Is this possible? > > >Brian Kramer - Owner/Systems Administrator - bjkramer@pluto.njcc.com >New Jersey Computer Connection - Public Access Unix Site - pluto.njcc.com >Voice: 609-896-2799 - Fax: 609-896-2994 - Dialups: 609-896-3191 >Dialup or Telnet to pluto.njcc.com and log in as guest for more information. I'm running Majordomo v1.91 (1.90 with patches) under Linux kernel 1.1.39 with smail. Works just fine for the EarthDawn mailing list, with about 160 subscribers, approx. 50 of which are digest subscribers. Also, one of our other administrators has just started a mailing list for discussions of Linux BBS programs. Dougal Campbell System Administrator, interQuest dougal@iquest.com owner-majordomo@magellan.iquest.com From majordomo-users-owner Mon Aug 22 21:09:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA21533; Mon, 22 Aug 1994 21:09:44 GMT Received: from relay.iunet.it by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA21527; Mon, 22 Aug 1994 14:09:32 -0700 Received: from byrrhena.UUCP by relay.iunet.it with UUCP id AA16438 (5.65c8/IDA-1.4.4 for greatcircle.com!majordomo-users); Mon, 22 Aug 1994 23:20:54 +0200 Message-Id: From: floco@colletta.it (Valerio Saggini) Subject: Problems with advertising To: majordomo-users@greatcircle.com Date: Mon, 22 Aug 1994 15:50:43 +0200 (GMT+0200) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 882 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello all, I've sent to majordomo the newconfig command with a new configuration file including the following lines: advertise << END /valerio@psyche.colletta.it/ /stefania@psyche.colletta.it/ /gabriele@photide.colletta/ /guala@photide.colletta.it/ /gdc@psyche.colletta.it/ and I've received the following reply: > > >>>> newconfig mate password > The new config file for mate was NOT accepted because: > regexp |/valerio@psyche.colletta.it/| does not match pattern at line 76 > regexp |/stefania@psyche.colletta.it/| does not match pattern at line 77 > regexp |/gabriele@photide.colletta/| does not match pattern at line 78 > regexp |/guala@photide.colletta.it/| does not match pattern at line 79 > regexp |/gdc@psyche.colletta.it/| does not match pattern at line 80 can you explain to me what is the correct syntax for these regexps? Thanks in advance Valerio From majordomo-users-owner Mon Aug 22 21:18:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA21570; Mon, 22 Aug 1994 21:18:27 GMT Received: from osiris.ac.hmc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA21563; Mon, 22 Aug 1994 14:18:16 -0700 Received: (from jared@localhost) by osiris.ac.hmc.edu (8.6.8.1/8.6.7) id OAA14279; Mon, 22 Aug 1994 14:22:47 -0700 Date: Mon, 22 Aug 1994 14:22:47 -0700 Message-Id: <199408222122.OAA14279@osiris.ac.hmc.edu> From: Jared_Rhine@hmc.edu To: floco@colletta.it (Valerio Saggini) Cc: majordomo-users@GreatCircle.COM Subject: Problems with advertising References: X-Attribution: JRhine Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Valerio> advertise << END Valerio> /valerio@psyche.colletta.it/ Valerio> /stefania@psyche.colletta.it/ Valerio> /gabriele@photide.colletta/ Valerio> /guala@photide.colletta.it/ Valerio> /gdc@psyche.colletta.it/ Valerio> I've received the following reply: >> >>>> newconfig mate password >> The new config file for mate was NOT accepted because: >> regexp |/valerio@psyche.colletta.it/| does not match pattern at line 76 >> regexp |/stefania@psyche.colletta.it/| does not match pattern at line 77 >> regexp |/gabriele@photide.colletta/| does not match pattern at line 78 >> regexp |/guala@photide.colletta.it/| does not match pattern at line 79 >> regexp |/gdc@psyche.colletta.it/| does not match pattern at line 80 Valerio> can you explain to me what is the correct syntax for these regexps? By default, it doesn't accept the @ character. In 'grab_regexp_array', change a line to read: if "$re" =~ /^\......\^\+@]+........ -- Jared_Rhine@hmc.edu | Harvey Mudd College | http://www.hmc.edu/~jared/home.html "To live is to war with trolls." -- Ibsen From majordomo-users-owner Mon Aug 22 21:57:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA21750; Mon, 22 Aug 1994 21:57:55 GMT Received: from who.net.uokhsc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA21744; Mon, 22 Aug 1994 14:57:42 -0700 Received: from [157.142.8.22] by who.net.uokhsc.edu (5.64/A/UX-3.00) id AA13916; Mon, 22 Aug 94 17:02:49 PDT Received: from ccMail by cclink.uokhsc.edu id AA777600373 Mon, 22 Aug 94 17:06:13 CST Date: Mon, 22 Aug 94 17:06:13 CST From: "Scott Smith" Message-Id: <9407227776.AA777600373@cclink.uokhsc.edu> To: majordomo-users@greatcircle.com Subject: Need help with Bounce messages Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am a list moderator and need assistance. Majordomo doesn't seem to accept the approvals of postings. I have tried three different ways to get the approvals to go through to no avail. Our office use CC:mail (lotus product) to send/receive e-mail. Could this be part of the problem. What I get back is a bounced message the body of which includes a ten or twelve line header (showing who sent, etc) followed by their original message. The instructions state to put "Approved: " on the first line and send it back to the list. I have done this three different ways, resulting in the message being re-bounced to me. Please advise. Please feel free to e-mail me directly. Thanks. ************************************************************************* * Scott R. Smith * Office of Research Administration * * Sponsored Programs Administrator * University of Oklahoma * * Phone: 405/271-2090 * Health Sciences Center * * Fax: 405/271-8651 * P. O. Box 26901 * * E-mail: ssmith@uokhsc.edu * Oklahoma City, OK 73190 * ************************************************************************* From majordomo-users-owner Tue Aug 23 06:20:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA24500; Tue, 23 Aug 1994 06:20:54 GMT Received: from gatekeeper.roche.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA24494; Mon, 22 Aug 1994 23:20:42 -0700 Received: by gatekeeper.roche.com (5.65/fma-120691); id AA04151; Tue, 23 Aug 94 02:25:30 -0400 Received: by mailgate.roche.com (5.65/fma-120691); id AA19419; Tue, 23 Aug 94 02:25:28 -0400 Received: from conversion.RBAC01 by RBAC01.BAS.ROCHE.COM (PMDF V4.3-7 #5197) id <01HG8PV51TGW96X1AJ@RBAC01.BAS.ROCHE.COM>; Tue, 23 Aug 1994 08:15:13 MET Received: from mr.bas.roche.com by RBAC01.BAS.ROCHE.COM (PMDF V4.3-7 #5197) id <01HG8PILNRJK96WVJZ@RBAC01.BAS.ROCHE.COM>; Tue, 23 Aug 1994 08:05:17 MET Received: with PMDF-MR; Tue, 23 Aug 1994 07:58:31 MET Mr-Received: by mta ROCBI.MUAS; Relayed; Tue, 23 Aug 1994 07:58:31 +0100 Mr-Received: by mta RBIZ06; Relayed; Tue, 23 Aug 1994 07:58:33 +0100 Mr-Received: by mta RBAC01; Relayed; Tue, 23 Aug 1994 07:58:36 +0100 Disclose-Recipients: prohibited Date: Tue, 23 Aug 1994 07:58:31 +0100 (MET) From: BAUMANNM +61 68 73 52 0 Subject: RE: Question and Assistance To: Majord User Message-Id: <7631580723081994/A77338/RBIZ06/1188B9FA1900*@MHS> Autoforwarded: false Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Conversion: prohibited Importance: low Priority: non-urgent Ua-Content-Id: 1188B9FA1900 X400-Mts-Identifier: [;7631580723081994/A77338/RBIZ06] Hop-Count: 2 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I copied wrapper to /usr/local. Did a chmod 7777 and the result was majordomo: permission denied. This is because the majordomo homedir has 750 mode. /usr/local is not a NFS file system. I assume that I have a problem with setuid/setgid. Everytime wrapper is executed it is done with the callers uid/gid. If I open the majordomo homedir (777) everything works fine. Who installed majordomo succesfully on a HP with UX 9.0.1? Thx for the help -r Michael ..>Hi ..> ..>I am new to the list but after reading the archives and the README file and testing ..>the Majordomo server I have one question: ..> ..>I am running majordomo on a HP (V 9.0.1) and I installed it as described. ..>I know that this question was asked several times but I do not understand the ..>answer or the solution described is not working on the HP. ..> ..>Everything works fine but I have to open the permission world wide on ..>the wrapper, W_BIN, listdir, homedir and the Log. I tested it with the POSIX ..>version and now difference. Right now I am using the POSIX version ..> ..>drwxrwxrwx majodom majodom mail.lists (listdir) ..>drwxrwxrwx majodom majodom bin (homedir) ..>-rwsr-xr-x root majodom wrapper ..> ..>chmod 775 for dir and 664 for files produces access errors! ..> ..>Any help is appreciated. ..> ..>Any ideas? Maybe their is a different way to solve the problem. ..> ..>-r ..>Michael From majordomo-users-owner Tue Aug 23 07:27:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA25330; Tue, 23 Aug 1994 07:27:49 GMT Received: from duke.cs.duke.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA11571; Fri, 19 Aug 1994 08:17:43 -0700 Received: from london.chem.duke.edu by duke.cs.duke.edu (5.65/3.9G/4.1.3) id AA08620; Fri, 19 Aug 94 11:22:10 -0400 Received: from affymax.chem.duke.edu by london.chem.duke.edu (5.64/1.19LP/4.1.1) id AA00548; Fri, 19 Aug 94 11:22:07 -0400 Received: by affymax.chem.duke.edu (5.64/2.12L/4.1) id AA00423; Fri, 19 Aug 94 11:22:07 -0400 Date: Fri, 19 Aug 94 11:22:07 -0400 From: yuji@chem.duke.edu (Yuji Shinozaki) Message-Id: <9408191522.AA00423@affymax.chem.duke.edu> To: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Subject: limit by domain? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Is there a way to limit majordomo to automatically handle subscribe/unsubscribe requests only from specified domains? I am trying to construct a mailling list for specific subnets; I want people within the subnet domains to be able to freely subscribe and unsubscribe themselves, but I do not want anyone outside the domains to be able to subscribe. Can this be done in v.1.92? If not, it would be a nice feature... I'm not sure if I am ready to start hacking. yuji ---- Yuji Shinozaki Computer Systems Manager (919)660-1514 Box 90347 / Dept of Chemistry yuji@chem.duke.edu Duke University http://www.chem.duke.edu Durham, NC 27708-0347 From majordomo-users-owner Tue Aug 23 13:28:51 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA27690; Tue, 23 Aug 1994 13:28:51 GMT Received: from budman.lanl.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA27684; Tue, 23 Aug 1994 06:28:35 -0700 Received: by budman.lanl.gov (1.38.193.4/16.2) id AA18829; Tue, 23 Aug 1994 07:30:56 -0600 From: "Douglas Gatchell" Message-Id: <9408230730.ZM18827@budman.lanl.gov> Date: Tue, 23 Aug 1994 07:30:55 -0600 X-Mailer: Z-Mail (3.0.0 15dec93) To: majordomo-users@GreatCircle.COM Subject: Is there a way to not report successful subscribes Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Under Majordomo-1.92 a list owner would like to not get messages of successful subscribes/unsubscribes to his open list. Is there a way/technique to do this for an individual list? He can live with it but would rather not be annoyed by these messages. Thanks, Doug -- __ ---------------------------------------------------- __/ /_______/ Doug Gatchell/dgg@lanl.gov/(505)667-5119 / / / / / / Los Alamos National Labs/CIC-5 Network Engineering/ /___/_/ /_/ / MS B-255/Los Alamos, NM 87545/FAX(505)665-7793 / /__//__/___________________________________________________/ From majordomo-users-owner Tue Aug 23 13:52:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA27819; Tue, 23 Aug 1994 13:52:28 GMT Received: from ibp.ibp.fr by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA27813; Tue, 23 Aug 1994 06:52:19 -0700 Received: from masi.ibp.fr by ibp.ibp.fr (8.6.8/jtpda-5.0) with ESMTP id QAA12564 for ; Tue, 23 Aug 1994 16:03:47 +0200 Received: from cao-vlsi.ibp.fr by masi.ibp.fr (8.6.9/jtpda-5.0) with ESMTP id PAA09171 for ; Tue, 23 Aug 1994 15:57:59 +0200 Received: from rock.ibp.fr by cao-vlsi.ibp.fr (8.6.9/jtpda-5.0) with ESMTP id PAA25219 for ; Tue, 23 Aug 1994 15:55:35 +0100 From: Gilles-Eric.Descamps@masi.ibp.fr (Gilles-Eric DESCAMPS) Received: by rock.ibp.fr (8.6.9/jtpda-5.0) id PAA19525 for majordomo-users@greatcircle.com; Tue, 23 Aug 1994 15:55:34 +0100 Message-Id: <199408231455.PAA19525@rock.ibp.fr> Subject: Preventing Majordomo from answering to Mailer-Daemon To: majordomo-users@greatcircle.com Date: Tue, 23 Aug 1994 15:55:33 +0100 (BST) Organization: France UPMC-CNRS, IBP, MASI, cao-vlsi MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1677 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk ----------------------------------------------------------------------- (G)illes-(E)ric (D)ESCAMPS Paris, le Tue 23 Aug 1994 a 15:40 -------------------------- Hi all, I have just setup (hardly) Majordomo-1.92. I have the following problem : When an address bounces, Mailer-Daemon sends a mail to Majordomo saying that that address is unreachable. How can I prevent Majordomo from answering to Mailer-Daemon ?? > Forwarded message: > > From PostMaster@cao-vlsi.ibp.fr Tue Aug 23 07:05:00 1994 > > Date: Tue, 23 Aug 1994 07:03:24 +0100 > > Message-Id: <199408230603.HAA22168@cao-vlsi.ibp.fr> > > To: Mailer-Daemon@ibp.fr > > From: Majordomo@cao-vlsi.ibp.fr > > Subject: Majordomo results: Returned mail: User unknown > > Reply-To: Majordomo@cao-vlsi.ibp.fr > > > > -- > > > > >>>> This is a MIME-encapsulated message > > **** Command 'this' not recognized. > > >>>> > > >>>> --HAA09999.777618691/ibp.ibp.fr > > END OF COMMANDS > > **** Help for Majordomo@cao-vlsi.ibp.fr: > > > > This is Brent Chapman's "Majordomo" mailing list manager, version 1.92. > > > > [ . . . ] ----------------------------------------------------------------------- | (G)illes-(E)ric (D)ESCAMPS | Couloir 55-65, 2eme etage, Bureau 228 | | Administrateur des Systemes | Universite Pierre et Marie Curie (P6) | | de l'Equipe CAO-VLSI | 4 place Jussieu, 75252 Paris Cedex 05 | | du Laboratoire MASI | Tel: (33-1) 44.27.53.99 | | de l'Institut Blaise Pascal | Fax: (33-1) 44.27.62.86 | | EMERGENCY phone 43.31.83.17 | Mail Gilles-Eric.DESCAMPS@masi.ibp.fr | ----------------------------------------------------------------------- From majordomo-users-owner Tue Aug 23 13:56:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA27843; Tue, 23 Aug 1994 13:56:00 GMT Received: from hmco.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA27837; Tue, 23 Aug 1994 06:55:53 -0700 Received: by hmco.com (5.65/DEC-Ultrix/4.3/jcurran+a1+umc+dnet) id AA07377; Tue, 23 Aug 1994 10:00:07 -0400 Received: by willy.hmco.com (5.0/SMI-SVR4) id AA19534; Tue, 23 Aug 1994 09:57:56 +0500 Date: Tue, 23 Aug 1994 09:57:56 +0500 From: alaka@hmco.com (Ghassan J. Alaka) Message-Id: <9408231357.AA19534@willy.hmco.com> To: majordomo-users@greatcircle.com Subject: archive error message X-Sun-Charset: US-ASCII Content-Length: 389 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've just finished setting up Majordomo. Everything is working fine but, when a message is sent to the list an error message is mailed back to the list owner with the following: /usr/local/mail/archive/it... Can't create output I've opened-up the permissions on the whole file structure, and still get that error message. Can any one help me. THANKS, PS: "it" is the name of the list From majordomo-users-owner Tue Aug 23 14:19:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA28066; Tue, 23 Aug 1994 14:19:49 GMT Received: from alcor.concordia.ca by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA28060; Tue, 23 Aug 1994 07:19:39 -0700 Received: from localhost (anne@localhost [127.0.0.1]) by alcor.concordia.ca (8.6.7/8.6.6) with SMTP id KAA24648; Tue, 23 Aug 1994 10:24:21 -0400 Message-Id: <199408231424.KAA24648@alcor.concordia.ca> X-Authentication-Warning: alcor.concordia.ca: Host localhost didn't use HELO protocol To: "Scott Smith" cc: majordomo-users@GreatCircle.COM Subject: Re: Need help with Bounce messages In-reply-to: Your message of Mon, 22 Aug 94 17:06:13 CST Date: Tue, 23 Aug 94 10:24:20 EDT From: Anne Bennett Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Majordomo doesn't seem to > accept the approvals of postings. I have tried three different ways > to get the approvals to go through to no avail. [...] > The instructions state to put "Approved: " on the first > line and send it back to the list. I have done this three different > ways, resulting in the message being re-bounced to me. I had similar problems at this site from Vax/VMS users, who cannot add a header to their mail. Indeed, the "Approved:" line must not only be the first line of the message (below the headers), but also there must be exactly *one* blank line between the headers and the "Approved:" line; having more than one blank line there caused bounces for us. Anne. (Administrator for Concordia mail relay, news transfer, and DNS) Ms. Anne Bennett, Computing Services, Concordia University, Montreal H3G 1M8 anne@alcor.concordia.ca (514) 848-7606 From majordomo-users-owner Wed Aug 24 00:28:49 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id AAA03045; Wed, 24 Aug 1994 00:28:49 GMT Received: from home.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA03039; Tue, 23 Aug 1994 17:28:39 -0700 Received: (from matthew@localhost) by home.interaccess.com (8.6.9/8.6.9) id TAA18155 for majordomo-users@greatcircle.com; Tue, 23 Aug 1994 19:30:20 -0500 From: "Matthew R. Zeier" Message-Id: <199408240030.TAA18155@home.interaccess.com> Subject: sending a digest out To: majordomo-users@greatcircle.com (Majordomo Users list) Date: Tue, 23 Aug 1994 19:30:19 -0500 (CDT) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 847 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have Majordomo set up to digest several incoming lists, but I am amiss to how and when Majordomo decides to email those digests out to who ever is on the -digest list. I'm subscribed too all my lists that I maintain and the digests of them and have yet to receive any digests. Any help? - Matthew ---- Matthew R. Zeier "Do what you can with what you have matthew@interaccess.com where you are." -Teddy Roosevelt http://www.interaccess.com/mzeier.html ...................................................................... InterAccess Company Technical Support: 708/498-3842 3345 Commercial Avenue Modem Line: 708/498-3960 Northbrook, IL 60062 Fax Line: 708/498-3289 "Oh and where will you be in 10 years? I'll be on Mars myself." From majordomo-users-owner Wed Aug 24 00:30:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id AAA03071; Wed, 24 Aug 1994 00:30:09 GMT Received: from home.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA03057; Tue, 23 Aug 1994 17:29:59 -0700 Received: (from matthew@localhost) by home.interaccess.com (8.6.9/8.6.9) id TAA18226 for majordomo-users@greatcircle.com; Tue, 23 Aug 1994 19:31:41 -0500 From: "Matthew R. Zeier" Message-Id: <199408240031.TAA18226@home.interaccess.com> Subject: Appware-info headers (fwd) To: majordomo-users@greatcircle.com (Majordomo Users list) Date: Tue, 23 Aug 1994 19:31:40 -0500 (CDT) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1001 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Guys, I have a list which all of a sudden has changed the Sender field to something else. The only thing that's changed is an upgrade from 1.62 to 1.92. The list owner forwarded the following to me -> > Have you been able to diagnose the problem with the Sender: field of > outgoing appware-info messages? The 'owner-owner-appware-info@parallel.com' > is getting pretty annoying. If we could just get rid of the first 'owner-' Any ideas? - Matthew ---- Matthew R. Zeier "Do what you can with what you have matthew@interaccess.com where you are." -Teddy Roosevelt http://www.interaccess.com/mzeier.html ...................................................................... InterAccess Company Technical Support: 708/498-3842 3345 Commercial Avenue Modem Line: 708/498-3960 Northbrook, IL 60062 Fax Line: 708/498-3289 "Oh and where will you be in 10 years? I'll be on Mars myself." From majordomo-users-owner Wed Aug 24 01:59:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA03697; Wed, 24 Aug 1994 01:59:11 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA03691; Tue, 23 Aug 1994 18:59:01 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id WAA17744; Tue, 23 Aug 1994 22:03:28 -0400 Message-Id: <199408240203.WAA17744@bosnia.pop.psu.edu> To: "Matthew R. Zeier" cc: majordomo-users@GreatCircle.COM (Majordomo Users list) Subject: Re: sending a digest out In-reply-to: Your message of "Tue, 23 Aug 1994 19:30:19 CDT." <199408240030.TAA18155@home.interaccess.com> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Tue, 23 Aug 1994 22:03:27 -0400 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199408240030.TAA18155@home.interaccess.com>, "Matthew R. Zeier" wri tes: >I have Majordomo set up to digest several incoming lists, but I am amiss >to how and when Majordomo decides to email those digests out to who ever is >on the -digest list. This section was recently added to the FAQ. (which is due to be posted shortly) Subject: Why aren't my digests going out? ----------------------------------------- [from John Rouillard] >I'm not sure how to set up the digest feature of majordomo 1.92 to send >digests out. Currently, it is digesting incoming mail, but that's all it's >doing. "echo mkdigest | mail majordomo@..." This will force a digest to be created. Or you can set the max size in the digest list config file down low, and force automatic generation. There are some patches for 1.92 that will allow other ways of specifying automatic digest sending. The patch is in the contrib directory. From majordomo-users-owner Thu Aug 25 12:54:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA17624; Thu, 25 Aug 1994 12:54:01 GMT Received: from mwunix.mitre.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id FAA17618; Thu, 25 Aug 1994 05:53:49 -0700 Received: from mental (mental.mitre.org [128.29.135.14]) by mwunix.mitre.org (8.6.4/8.6.4) with SMTP id IAA23706 for ; Thu, 25 Aug 1994 08:58:37 -0400 Received: by mental (5.65/MITRE-SS2) id AA10857; Thu, 25 Aug 1994 08:58:37 -0400 Date: Thu, 25 Aug 1994 08:58:37 -0400 From: jwagner@mental.mitre.org (John G. Wagner) Message-Id: <9408251258.AA10857@mental> To: Majordomo-Users@greatcircle.com Subject: Forw: Returned mail: unknown mailer error 5 Forwarded-By: Mailer-Daemon --> jwagner X-Status: N X-Mailer: Applixware 3.1(124) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk does anybody else get these errors? If I send mail to the list, it gets resent ok, but when I send mail to majordomo it fails EVERY time. This is my first install, and I followed the instructions, but I guess I missed something. HELP :) John ---- Forwarded message follows----- > From Mailer-Daemon Wed Aug 24 15:48:01 1994 > Return-Path: > Received: by mental (5.65/MITRE-SS2) > id AA06366; Wed, 24 Aug 1994 15:47:59 -0400 > Date: Wed, 24 Aug 1994 15:47:59 -0400 > From: Mailer-Daemon@mental (Mail Delivery Subsystem) > Subject: Returned mail: unknown mailer error 5 > Message-Id: <9408241947.AA06366@mental> > To: owner-majordomo > Cc: Postmaster > ----- Transcript of session follows ----- > majordomo: No such file or directory > 554 "|/export/home/mental1/majordomo/wrapper majordomo"... unknown mailer error 5 > ----- Unsent message follows ----- > Received: from mwunix.mitre.org by mental (5.65/MITRE-SS2) > id AA06364; Wed, 24 Aug 1994 15:47:59 -0400 > Return-Path: A_H_McClure%MW_CORP2@MWMGATE1.mitre.org > Received: from mwmgate2.mitre.org (mwmgate2.mitre.org [128.29.155.13]) by mwunix.mitre.org (8.6.4/8.6.4) with SMTP id PAA05795 for <@mwunix.mitre.org:majordomo@mental.mitre.org>; Wed, 24 Aug 1994 15:47:58 -0400 > Message-Id: <199408241947.PAA05795@mwunix.mitre.org> > Date: Wed, 24 Aug 94 15:48:02 EDT > From: A_H_McClure%mwcorp2@MWMGATE1.mitre.org > To: majordomo@mental > Subject: Junk3 > unsubscribe amcclure@mitre.org intelink_developers_test From majordomo-users-owner Thu Aug 25 14:38:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA18379; Thu, 25 Aug 1994 14:38:46 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA18373; Thu, 25 Aug 1994 07:38:31 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id KAA05186; Thu, 25 Aug 1994 10:42:43 -0400 Message-Id: <199408251442.KAA05186@bosnia.pop.psu.edu> To: jwagner@mental.mitre.org (John G. Wagner) cc: Majordomo-Users@GreatCircle.COM Subject: Re: Forw: Returned mail: unknown mailer error 5 In-reply-to: Your message of "Thu, 25 Aug 1994 08:58:37 EDT." <9408251258.AA10857@mental> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Thu, 25 Aug 1994 10:42:43 -0400 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9408251258.AA10857@mental>, John G. Wagner writes: >does anybody else get these errors? If I send mail to the list, it gets >> ----- Transcript of session follows ----- >> majordomo: No such file or directory >> 554 "|/export/home/mental1/majordomo/wrapper majordomo"... unknown mailer er >ror 5 >From doc/FAQ Subject: I get "majordomo: No such file or directory" from the wrapper ---------------------------------------------------------------------- Make sure that the #! statement at the beginning of all the Majordomo executables contain the correct path to the perl program. (the default is /usr/local/bin/perl) Make sure also that majordomo and all the related scripts are in the W_BIN directory as defined in the Makefile when you compiled the wrapper. You can get the current FAQ by sending an e-mail message to "majordomo@pop.psu.edu" with "get file majordomo-faq" in the BODY of the message. --Dave From majordomo-users-owner Thu Aug 25 10:01:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA19173; Thu, 25 Aug 1994 16:21:17 GMT Received: from mwunix.mitre.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA19161; Thu, 25 Aug 1994 09:21:02 -0700 Received: from mental (mental.mitre.org [128.29.135.14]) by mwunix.mitre.org (8.6.4/8.6.4) with SMTP id MAA20383 for ; Thu, 25 Aug 1994 12:25:50 -0400 Received: by mental (5.65/MITRE-SS2) id AA07190; Thu, 25 Aug 1994 12:25:49 -0400 Date: Thu, 25 Aug 1994 12:25:49 -0400 From: jwagner@mental.mitre.org (John G. Wagner) Message-Id: <9408251625.AA07190@mental> To: Majordomo-Users@greatcircle.com Subject: RE: can't find file error 5 X-Status: N X-Mailer: Applixware 3.1(124) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Ok I found it, it was a typo in the "Makefile" hard to spot even when your looking right at it {;p. Thanks for all the replies, I hope everything else is working well now. I only have 12 lists to put up in 2 days :( and all will need approval before anyone can enter.. so I guess I'll be getting ALOT of mail from them, or someone will :) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Heck even I don't know what I do, so the company can't. + + empire isn't a game, it's a world ruled by elves! :) + + Bowling IS a sport, and if you don't believe me, I'll beat'ya + + and YES I mean with a BIG stick!! }:@ + + jwagner@mitre.org | John Wagner | PH# (703)883-3740 + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From majordomo-users-owner Thu Aug 25 21:58:48 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA22009; Thu, 25 Aug 1994 21:58:48 GMT Received: from nevis.cim.cdc.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA21998; Thu, 25 Aug 1994 14:58:29 -0700 Received: (from greg@localhost) by nevis.cim.cdc.com (8.6.8/8.6.6) id RAA28608 for Majordomo-Users@GreatCircle.COM; Thu, 25 Aug 1994 17:02:40 -0500 From: Greg Rowe Message-Id: <199408252202.RAA28608@nevis.cim.cdc.com> Subject: Moderated List Problems To: Majordomo-Users@GreatCircle.COM Date: Thu, 25 Aug 1994 17:02:39 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 786 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm running Majordomo 1.92 on a FreeBSD 1.1.5 system. I have been asked to turn one of the existing lists into a moderated list. This works fine except for two problems. After resending the mail with the "Approved:" line in, the "Subject" line gets tosssed away. Then the following lines get tossed in after the second blank line appears in the message body: Sender: owner-testlist@foo.bar.com Precedence: bulk Does anyone else have this problem or is it the level of sendmail on FreeBSD ? Thanks. -- Greg Rowe | Metaphase Technology Inc., ARH202 | INTERNET greg@nevis.cim.cdc.com 4201 Lexington Ave. North | Arden Hills, MN USA 55126 | Voice: (612) 482-2699 To err is human, to really foul up requires the root password. From majordomo-users-owner Thu Aug 25 22:02:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id WAA22109; Thu, 25 Aug 1994 22:02:33 GMT Received: from who.net.uokhsc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA22084; Thu, 25 Aug 1994 15:01:39 -0700 Received: from [157.142.8.22] by who.net.uokhsc.edu (5.64/A/UX-3.00) id AA23297; Thu, 25 Aug 94 17:06:57 PDT Received: from ccMail by cclink.uokhsc.edu id AA777860193 Thu, 25 Aug 94 17:16:33 CST Date: Thu, 25 Aug 94 17:16:33 CST From: "Scott Smith" Message-Id: <9407257778.AA777860193@cclink.uokhsc.edu> To: majordomo-users@greatcircle.com Subject: Still having trouble with bounce messages Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We use cc:mail which links through something called CCLINK to get messages to majordomo. I am trying to approve a message to be posted (which, incidentally, I sent myself), and here's what I get back (body of message) From ssmith@cclink.uokhsc.edu Thu Aug 25 15:08:55 1994 Received: from [157.142.8.22] by who.net.uokhsc.edu (5.64/A/UX-3.00) id AA22696; Thu, 25 Aug 94 15:08:55 PDT Received: from ccMail by cclink.uokhsc.edu id AA777853111 Thu, 25 Aug 94 15:18:31 CST Date: Thu, 25 Aug 94 15:18:31 CST From: "Scott Smith" Message-Id: <9407257778.AA777853111@cclink.uokhsc.edu> To: oranet@uokhsc.edu Subject: ORANET Fastrack Funding, August 26 Edition Text of message to be sent . . . . . Where do I put the approved line? I have tried before the From ssmith line, after the Subject line (two ways each, directly above/below and leaving one blank line above/below). I even tried sending the message the first time with my "Approved: " line before the message i.e.: Approved: Message text to be posted . . . . But that doesn't work either. I am slowly pulling out the hair on top of my head as this is driving me insane (short trip!). I do apprecaite the responses I have received, but still am confused (Dear Abby . . .). Thanks in advance for any further help. ************************************************************************* * Scott R. Smith * Office of Research Administration * * Sponsored Programs Administrator * University of Oklahoma * * Phone: 405/271-2090 * Health Sciences Center * * Fax: 405/271-8651 * P. O. Box 26901 * * E-mail: ssmith@uokhsc.edu * Oklahoma City, OK 73190 * ************************************************************************* From majordomo-users-owner Fri Aug 26 00:19:51 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id AAA23719; Fri, 26 Aug 1994 00:19:51 GMT Received: from ssi.edc.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA23710; Thu, 25 Aug 1994 17:19:33 -0700 Received: from ssi.edc.org by ssi.edc.org id aa21460; 25 Aug 94 20:23 EDT Date: Thu, 25 Aug 1994 20:23:38 -400 (EDT) From: Gunther Anderson To: Scott Smith cc: majordomo-users@greatcircle.com Subject: Re: Still having trouble with bounce messages In-Reply-To: <9407257778.AA777860193@cclink.uokhsc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Thu, 25 Aug 1994, Scott Smith wrote: > > We use cc:mail which links through something called CCLINK to get > messages to majordomo. I am trying to approve a message to be posted > (which, incidentally, I sent myself), and here's what I get back > (body of message) [Much deleted.] In theory, you put the Approved: header as the first line in the message, followed by a blank line, followed by the entirety, including all headers, of the message you wush to approve. I have found that cc:Mail's SMTPLink, at least, puts an extra blank line between the headers and the body, making approval of submitted messages impossible to do through cc:Mail at my site (all the moderators get Unix accounts, too). You might have the same trouble. Try mailing the approval not to Majordomo (or the list), but to another account on the Unix system, and see what sort of result you get there. It might tell you at least how cc:Mail is rendering your operations impossible. Of course, if this isn't what the trouble was, my apologies, I parsed your message wrong. Gunther Anderson From majordomo-users-owner Fri Aug 26 05:10:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA28174; Fri, 26 Aug 1994 09:46:27 GMT Received: from mwunix.mitre.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA28168; Fri, 26 Aug 1994 02:46:08 -0700 Received: from mental (mental.mitre.org [128.29.135.14]) by mwunix.mitre.org (8.6.4/8.6.4) with SMTP id FAA28445 for ; Fri, 26 Aug 1994 05:51:00 -0400 Received: by mental (5.65/MITRE-SS2) id AA21286; Fri, 26 Aug 1994 05:50:59 -0400 Date: Fri, 26 Aug 1994 05:50:59 -0400 From: jwagner@mental.mitre.org (John G. Wagner) Message-Id: <9408260950.AA21286@mental> To: majordomo-users@greatcircle.com Subject: unknown mailer error 255 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I keep getting this error from majordomo: eval of majordomo.cf failed at /export/home/mental1/majordomo/majordomo line 46. 554 "|/export/home/mental1/majordomo/wrapper majordomo"... unknown mailer error 255 the line in my majordomo.cf file that is line 46 is: eval(`cat /etc/majordomo.cf`) || die "eval of majordomo.cf failed $@"; Opps that is majordomo file itself, I've also replaced the $cf with the file name just to be sure that wasn't a problem, but the same error happens. Any ideas?? Yes /usr/lib/sendmail is there: mental: ~, 33 > which sendmail /usr/lib/sendmail mental: ~, 34 > perl version 4.036 majordomo version 1.92 John From majordomo-users-owner Fri Aug 26 18:27:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA02327; Fri, 26 Aug 1994 18:27:46 GMT Received: from vacuum.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA02317; Fri, 26 Aug 1994 11:27:05 -0700 Received: from auger by vacuum.org (5.0/SOLARIS-V1.0-American Vacuum Society) id AA20590; Fri, 26 Aug 94 14:30:16 EDT Message-Id: <9408261830.AA20590@vacuum.org> X-Sender: carlos@torr Date: Fri, 26 Aug 1994 14:30:54 -0400 To: majordomo-users@greatcircle.com From: carlos@vacuum.org (Carlos Toro) Subject: Error at shlock.pl line 131 Cc: rouilj@cs.umb.edu, jpater@cetis.hut.nl, carlos@vacuum.org X-Mailer: X-Attachments: C:\CARLOS\TEMP.ANS; content-length: 1111 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've installed Majordomo 1.92 on a Sun running Solaris 2.2 (a POSIX-compliant system). When someone outside of my LAN sends a "lists" command to majordomo I get the following error message: shlock: open(">/local1/apps/majordomo/mail/lists/shlock.18274"): Permission denied at /local1/apps/majordomo/majordomo- 1.92/shlock.pl line 131, <_GEN_1> line 1. In July Johan Pater had a similar problem and John Rouillard responded: >The permissions for the directory: > > /home/majordomo/lists > >must be 775. the directory must be owned by the user that the wrapper >runs as, and the group must be the same as the group that the wrapper >runs as. Also the wrapper must be setuid and setgid. I am confused by this response. The majordomo-1.92.README and majordomo.ora docs say that everything must be owned by user majordom, group majordom. They also say that under POSIX wrapper must be setuid "root" (they don't say anything about setgid). So what is wrong with the following setup? drwxrwxr-x 2 majordom majordom 512 Aug 25 18:09 lists and -rwxr-xr-x 1 root other 10072 Aug 10 15:21 wrapper From majordomo-users-owner Fri Aug 26 19:21:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA02753; Fri, 26 Aug 1994 19:21:29 GMT Received: from eos03a.eos.ncsu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA02746; Fri, 26 Aug 1994 12:21:16 -0700 From: mspitt@eos.ncsu.edu Received: from pamsdialup by eos03a.eos.ncsu.edu (8.6.9/ES17aug94) id PAA03670; Fri, 26 Aug 1994 15:26:11 -0400 Received: by pamsdialup (AIX 3.2/UCB 5.64/eos-client.920924i) id AA20902; Fri, 26 Aug 1994 15:26:07 -0400 Message-Id: <9408261926.AA20902@pamsdialup> Subject: altered headers To: majordomo-users@greatcircle.com Date: Fri, 26 Aug 1994 15:26:07 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23/POP] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 299 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi! We are attempting an installation of majordomo where we need majordomo to put out altered headers. We are hoping someone could tell us how to create customized reply-to and from headers in majordomo? Thank you, Mike -- Michael Pitt North Carolina State University mspitt@eos.ncsu.edu From majordomo-users-owner Fri Aug 26 21:43:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA04283; Fri, 26 Aug 1994 21:43:57 GMT Received: from polo.iquest.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA04277; Fri, 26 Aug 1994 14:43:39 -0700 Received: by polo.iquest.com (Linux Smail3.1.28.1 #1) id m0qe91T-002EKeC; Fri, 26 Aug 94 16:41 CDT Received: from cc:Mail by multi.iquest.com id AA777944753 Fri, 26 Aug 94 16:45:53 Date: Fri, 26 Aug 94 16:45:53 From: "Dougal Campbell" Encoding: 869 Text Message-Id: <9407267779.AA777944753@multi.iquest.com> To: majordomo-users@GreatCircle.COM Subject: Re: Error at shlock.pl line 131 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk [......] >I am confused by this response. The majordomo-1.92.README and majordomo.ora >docs say that everything must be owned by user majordom, group majordom. They >also say that under POSIX wrapper must be setuid "root" (they don't say >anything about setgid). So what is wrong with the following setup? > >drwxrwxr-x 2 majordom majordom 512 Aug 25 18:09 lists > >and > >-rwxr-xr-x 1 root other 10072 Aug 10 15:21 wrapper Well, you *don't* have wrapper setuid root, for one thing. Just being owned by root isn't the same. And it wouldn't hurt for it to belong to the majordom group, either. Try these commands: chown root.majordom wrapper chmod u+s wrapper This should give you -rwsr-xr-x 1 root majordom 10072 Aug 10 15:21 wrapper ^ ^^^^^^^^ Dougal Campbell dougal@iquest.com From majordomo-users-owner Fri Aug 26 22:06:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id WAA04486; Fri, 26 Aug 1994 22:06:12 GMT Received: from mwunix.mitre.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA04479; Fri, 26 Aug 1994 15:05:57 -0700 Received: from mental (mental.mitre.org [128.29.135.14]) by mwunix.mitre.org (8.6.4/8.6.4) with SMTP id SAA20072 for ; Fri, 26 Aug 1994 18:10:42 -0400 Received: by mental (5.65/MITRE-SS2) id AA28003; Fri, 26 Aug 1994 18:10:42 -0400 Date: Fri, 26 Aug 1994 18:10:42 -0400 From: jwagner@mental.mitre.org (John G. Wagner) Message-Id: <9408262210.AA28003@mental> To: Majordomo-Users@greatcircle.com Subject: Returned mail: unknown mailer error 255 X-Status: NA X-Mailer: Applixware 3.1(124) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've attached a copy of my majordomo.cf file that it seems that the majordomo program can not deal with. (I have not changed the majordomo program itself, from the release) I tried to look thru the code, but I don't know perl, so I might be looking right at it but wouldn't know it. I'm now starting to get frustrated at my lack of success with this program. anybody have ANY ideas? ERROR: eval of majordomo.cf failed at /export/home/mental1/majordomo/majordomo line 46. 554 "|/export/home/mental1/majordomo/wrapper majordomo"... unknown mailer error 255 system DEC 5000 running ultrix 4.3 perl version 4.036 majordomo version 1.92 begin 644 majordomo.cf M)'=H97)E86UI(#T@(FUE;G1A;"YM:71R92YOR)(3TU%(GT["GT@96QS92!["B @ M(" @)&AO;65D:7(@/2 B+V5X<&]R="]H;VUE+VUE;G1A;#$O;6%J;W)D;VUO M(CL*?0HD;&ES=&1I Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA06820; Sat, 27 Aug 1994 02:55:55 GMT Received: from gateway.Stoner.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA06814; Fri, 26 Aug 1994 19:55:43 -0700 Received: from uhura1.Stoner.COM (uhura1.Stoner.COM [198.64.192.11]) by gateway.Stoner.COM (8.6.9/8.6.4) with ESMTP id TAA07360; Fri, 26 Aug 1994 19:19:56 -0700 Received: (from curnutt@localhost) by uhura1.Stoner.COM (8.6.9/8.6.9) id VAA22758; Fri, 26 Aug 1994 21:58:18 -0500 From: "A. Bryan Curnutt" Message-Id: <199408270258.VAA22758@uhura1.Stoner.COM> Subject: Re: Error at shlock.pl line 131 To: carlos@vacuum.org (Carlos Toro) Date: Fri, 26 Aug 1994 21:58:18 -0500 (CDT) Cc: majordomo-users@GreatCircle.COM, rouilj@cs.umb.edu, jpater@cetis.hut.nl In-Reply-To: <9408261830.AA20590@vacuum.org> from "Carlos Toro" at Aug 26, 94 02:30:54 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2097 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Carlos Toro writes: > > The majordomo-1.92.README > and majordomo.ora docs say that everything must be owned by > user majordom, group majordom. They also say that under > POSIX wrapper must be setuid "root" (they don't say anything > about setgid). I'm puzzled that people keep missing this -- this has definitely become a Frequently Asked Question on the majordomo-users list. >From the top-level README in majordomo 1.92: : : 1.0 INSTALLATION : : The system should have its own uid and gid to run under ("majordom" is : used on GreatCircle.COM). You need to edit the Makefile to set up the : environment and directories used by the "wrapper" program. The : "wrapper" program needs to be installed setuid to daemon and setgid to ^^^^^^^^^^^ : the special group. If you're in that group and the directories used : by majordomo are writable by that group (they must be), [...] : : If you're running something POSIX-compliant (including System V and : BSDI, but not SunOS 4.x), you'll need to change the Makefile as : documented in it, to make "wrapper" program work. Under POSIX, : wrapper must be setuid "root", even if the programs will be running as : something other than "root" (i.e., "daemon"), or it won't work. The : [...] : To install majordomo: : [...] : edit the "Makefile" to set W_BIN and the environment for "wrapper"; : don't forget to make the changes for POSIX, if necessary : : compile and install the perl code and man pages. : ("make", then "make install") : : As root install the wrapper ("make install-wrapper") In the Makefile, it sure looks like the "install-wrapper" target takes care of setting the set[ug]id bits for you as appropriate, based on whether you modify the Makefile to work on a POSIX-compliant system as described in the comments. In other words, just follow the install instructions in the README file, and all will be well. -- Bryan Curnutt Stoner Associates, Inc. bryan.curnutt@stoner.com (713)626-9568 voice (713)622-7832 fax From majordomo-users-owner Mon Aug 29 07:13:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id HAA21593; Mon, 29 Aug 1994 07:13:23 GMT Received: from gatekeeper.roche.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id AAA21586; Mon, 29 Aug 1994 00:13:14 -0700 Received: by gatekeeper.roche.com (5.65/fma-120691); id AA20589; Mon, 29 Aug 94 03:18:09 -0400 Received: by mailgate.roche.com (5.65/fma-120691); id AA07592; Mon, 29 Aug 94 03:18:07 -0400 Received: from conversion.RBAC01 by RBAC01.BAS.ROCHE.COM (PMDF V4.3-7 #5197) id <01HGH5GRN8RK96XOR7@RBAC01.BAS.ROCHE.COM>; Mon, 29 Aug 1994 09:08:06 MET Received: from mr.bas.roche.com by RBAC01.BAS.ROCHE.COM (PMDF V4.3-7 #5197) id <01HGH55S7O2896WSLJ@RBAC01.BAS.ROCHE.COM>; Mon, 29 Aug 1994 08:59:40 MET Received: with PMDF-MR; Mon, 29 Aug 1994 08:56:54 MET Mr-Received: by mta ROCBI.MUAS; Relayed; Mon, 29 Aug 1994 08:56:54 +0100 Mr-Received: by mta RBIZ06; Relayed; Mon, 29 Aug 1994 08:56:55 +0100 Mr-Received: by mta RBAC01; Relayed; Mon, 29 Aug 1994 08:56:57 +0100 Disclose-Recipients: prohibited Date: Mon, 29 Aug 1994 08:56:54 +0100 (MET) From: BAUMANNM +61 68 73 52 0 Subject: RE: altered headers In-Reply-To: <80530072804991/456332@RBAC01> To: Majord User Message-Id: <6454560829081994/A93568/RBIZ06/1188EA382800*@MHS> Autoforwarded: false Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Conversion: prohibited Importance: low Priority: non-urgent Ua-Content-Id: 1188EA382800 X400-Mts-Identifier: [;6454560829081994/A93568/RBIZ06] Hop-Count: 2 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Read the installation guide careful and you will find the part "set up list distribution". Use the flag -f and -r to do the things you want. -r Michael ..> Hi! ..> ..> We are attempting an installation of majordomo where we need majordomo to ..> put out altered headers. ..> ..> We are hoping someone could tell us how to create customized reply-to and ..> from headers in majordomo? ..> ..> Thank you, ..> ..> Mike ..> -- ..> Michael Pitt ..> North Carolina State University ..> mspitt@eos.ncsu.edu From majordomo-users-owner Mon Aug 29 04:03:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA22059; Mon, 29 Aug 1994 08:33:52 GMT Received: from hp.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA22053; Mon, 29 Aug 1994 01:33:42 -0700 Received: from hpgntol1.grenoble.hp.com by hp.com with SMTP (1.36.108.7/15.5+IOS 3.13) id AA25214; Mon, 29 Aug 1994 01:38:43 -0700 Received: from cumulus.grenoble.hp.com by hpgntol1.grenoble.hp.com with SMTP (1.38.193.4/15.5+ECS 3.3) id AA05391; Mon, 29 Aug 1994 10:38:40 +0200 Message-Id: <9408290838.AA05391@hpgntol1.grenoble.hp.com> To: majordomo-users@GreatCircle.COM Cc: mathieu@hpgntol1.grenoble.hp.com Subject: HOSTILE ADDRESS - Please Help ! Date: Mon, 29 Aug 94 10:38:39 +0200 From: Mathieu Antoine Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, I've set up majordomo 1.62 a few months ago and it works fine for people who are using Unix mail. But for people who are using HPDesk mail on HP 3000 MPE/iX commercial systems, majordomo sends me the following error: MAJORDOMO ABORT HOSTILE ADDRESS LASTNAME_FIRSTNAME/HP0000_YY@hostname.hp.com I've found in majordomo.pl, at line 331: local($_) = @addrs; # if there's a "|" or a "/" in it, it's hostile if (tr/|\//|\// != 0) { &main'abort("HOSTILE ADDRESS $addr"); return undef; } I assume this test is there for security reasons. What are the risks if I allow "/" (or something like the regular expression "/HP[0-9][0-9][0-9][0-9]_[A-Z][A-Z]") in user addresses ? What else can I do to allow those persons to use my majordomo server ? I've been registered in majordomo-users but I'm not any more (sorry, too much traffic there). Could you also reply to me directly ? Many thanks, Mathieu. _________________________________________________________________________ Mathieu Antoine Hewlett Packard Grenoble Networks Division Lab 5, Av. Raymond Chanas - Eybens Software Engineering Group 38053 Grenoble Cedex 9 Phone: (+33) 76 62 50 14 FRANCE Fax: (+33) 76 62 12 86 Email: Mathieu_Antoine@grenoble.hp.com From majordomo-users-owner Mon Aug 29 16:35:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA25935; Mon, 29 Aug 1994 16:35:31 GMT Received: from mwunix.mitre.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA25929; Mon, 29 Aug 1994 09:35:21 -0700 Received: from mental (mental.mitre.org [128.29.135.14]) by mwunix.mitre.org (8.6.4/8.6.4) with SMTP id MAA20732 for ; Mon, 29 Aug 1994 12:39:58 -0400 Received: by mental (5.65/MITRE-SS2) id AA09230; Mon, 29 Aug 1994 12:39:57 -0400 Date: Mon, 29 Aug 1994 12:39:57 -0400 From: jwagner@mental.mitre.org (John G. Wagner) Message-Id: <9408291639.AA09230@mental> To: barr@pop.psu.edu Cc: Majordomo-Users@greatcircle.com Subject: Re: Returned mail: unknown mailer error 255 In-Reply-To: <199408262231.SAA27106@bosnia.pop.psu.edu> X-Status: N X-Mailer: Applixware 3.1(124) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Ok I've tried perl majordomo.cf, but no errors. I tried "perl majordomo" but it just hangs ( did give me an error to start with, but I removed the line about safedir, and now it doesn't bark about that, but still I get this F'ing error, unknown mailer 255. I tried sending mail to majordomo with subscribe/unsubscribe/info and list but nothing! all gave me the same results. Could it be the way majordomo is talking to sendmail? and I had version 1.62? running for 1 day or 2 just before I upgraded to 1.92, and now nothing works!! Any more ideas? From majordomo-users-owner Mon Aug 29 16:54:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA26067; Mon, 29 Aug 1994 16:54:22 GMT Received: from fievel.DaytonOH.NCR.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id JAA26061; Mon, 29 Aug 1994 09:54:12 -0700 Message-Id: <199408291654.JAA26061@mycroft.GreatCircle.COM> Subject: Changing a domain name To: majordomo-users@GreatCircle.COM (Majordomo Users) Date: Mon, 29 Aug 1994 12:58:59 -0400 (EDT) From: "Tom Moore" X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1769 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk As mailing list maintainers, I would like to solicit your input on the most painless way to change a domain name. In the future, we will be changing the NCR.COM domain name. There will be an extended interim period where both the old and new domain names will be supported and at some time the old name will be discontinued. The problem I see is for users to communicate this name change to mailing list maintainers such as ourselves. With automatic subscription/removal trying to subscribe/remove one address using another does not seem to be supported. Trying to coordinate switching from the old name to the new name while coordinating with every user to let them unsubscribe/resubscribe seems to be impossible to manage. I would really rather the user not have to do this at all. Is there some way that the administrators here could request a bulk update of all ncr.com addresses at the proper time? This is assuming that we could glean the appropriate information as to who is receiving what list. Is there a better way. As list maintainers, how would you like to see it done? (Try to keep this one in the realm of practicality please :-) Any assistance would be appreciated here to keep this as easy as possible for both subscribers and maintainers. Thanks. -- * "If we couldn't laugh at things that don't make sense, we couldn't react * * to a lot of life" --- Hobbes * * * * Tom Moore AT&T Global Information Solutions (513) 445-1373 * * Technology Consultant 1700 S. Patterson Blvd. VOICEplus 622-1373 * * Network System Solutions Dayton, OH 45479 Tom.Moore@DaytonOH.NCR.COM * From majordomo-users-owner Mon Aug 29 19:49:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA28462; Mon, 29 Aug 1994 19:49:29 GMT Received: from netcom3.netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id MAA28456; Mon, 29 Aug 1994 12:49:19 -0700 Received: by netcom3.netcom.com (8.6.8.1/Netcom) id MAA23034; Mon, 29 Aug 1994 12:44:55 -0700 From: sylviac@netcom.com (Sylvia Caras) Message-Id: <199408291944.MAA23034@netcom3.netcom.com> Subject: Bounce List To: majordomo-users@greatcircle.com Date: Mon, 29 Aug 1994 12:44:52 -0700 (PDT) Organization: Mood Matters X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 406 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Brent referenced a "bounce" list. How can I find out more about what that is? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SylviaC@netcom.com v/f:408 426 5335 Sylvia Caras, 146-5 Chrystal Ter, Santa Cruz CA 95060 It is not up to you to finish the work, but neither are you free not to take it up. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From majordomo-users-owner Mon Aug 29 14:03:48 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA28694; Mon, 29 Aug 1994 20:12:49 GMT Received: from mwunix.mitre.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA28688; Mon, 29 Aug 1994 13:12:20 -0700 Received: from mental (mental.mitre.org [128.29.135.14]) by mwunix.mitre.org (8.6.4/8.6.4) with SMTP id QAA21661 for ; Mon, 29 Aug 1994 16:17:15 -0400 Received: by mental (5.65/MITRE-SS2) id AA13621; Mon, 29 Aug 1994 16:17:14 -0400 Date: Mon, 29 Aug 1994 16:17:14 -0400 From: jwagner@mental.mitre.org (John G. Wagner) Message-Id: <9408292017.AA13621@mental> To: Majordomo-Users@greatcircle.com Subject: Time it takes do something X-Status: N X-Mailer: Applixware 3.1(124) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Ok I got Majordomo up and running! but now the "other" problems come in. First it takes about 10 minutes for majordomo to do anything. I send out a request to register myself on my list, and sent out a request to 3 other lists outside of my company, and all 3 came back before mine was finished working on my first request. Any ideas on the slow nature of this beast?? John P.S. Yes, I thought of admin error already :) +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Heck even I don't know what I do, so the company can't. + + empire isn't a game, it's a world ruled by elves! :) + + Bowling IS a sport, and if you don't believe me, I'll beat'ya + + and YES I mean with a BIG stick!! }:@ + + jwagner@mitre.org | John Wagner | PH# (703)883-3740 + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From majordomo-users-owner Mon Aug 29 22:06:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id WAA00282; Mon, 29 Aug 1994 22:06:04 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id PAA00270; Mon, 29 Aug 1994 15:05:53 -0700 Message-Id: <199408292205.PAA00270@mycroft.GreatCircle.COM> To: jwagner@mental.mitre.org (John G. Wagner) cc: Majordomo-Users@greatcircle.com Subject: Re: Time it takes do something In-reply-to: Your message of Mon, 29 Aug 1994 16:17:14 -0400 Date: Mon, 29 Aug 1994 15:05:50 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk jwagner@mental.mitre.org (John G. Wagner) writes: # Ok I got Majordomo up and running! but now the "other" problems # come in. First it takes about 10 minutes for majordomo to do anything. I send # out # a request to register myself on my list, and sent out a request to 3 other lists # # outside of my company, and all 3 came back before mine was finished working # on my first request. Any ideas on the slow nature of this beast?? # # John # # P.S. Yes, I thought of admin error already :) Check the permissions on the log file _and_ the directory containing the log file to make sure both are writable by Majordomo. "n*10 minute delays" associated with Majordomo are usually the result of file lock timeouts (since the timeout is 10 minutes), and the most common problem (particularly if the actual requests eventually succeed) is the log file. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Mon Aug 29 22:10:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id WAA00341; Mon, 29 Aug 1994 22:10:10 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id PAA00329; Mon, 29 Aug 1994 15:09:57 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id SAA24502; Mon, 29 Aug 1994 18:14:44 -0400 Message-Id: <199408292214.SAA24502@bosnia.pop.psu.edu> To: jwagner@mental.mitre.org (John G. Wagner) Cc: Majordomo-Users@GreatCircle.COM Subject: Re: Time it takes do something In-reply-to: Your message of "Mon, 29 Aug 1994 16:17:14 EDT." <9408292017.AA13621@mental> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Mon, 29 Aug 1994 18:14:43 -0400 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9408292017.AA13621@mental>, John G. Wagner writes: >Ok I got Majordomo up and running! but now the "other" problems >come in. First it takes about 10 minutes for majordomo to do anything. I send > out Here's what's in the FAQ: Subject: Majordomo seems to be taking many minutes to process commands ---------------------------------------------------------------------- | Commands are being processed at the rate of about two per | hour. It should take about three days for all 160 users to be | unsubscribed! Majordomo tries 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. If the directory containing the file is not writable by the Majordomo user/group, then majordomo won't be able to lock the file and thus will take a very long time to process commands. I just added this paragraph: Check the permissions on the log file and all the directories where majordomo files are located. Double-check the permission on the wrapper. It must be both setuid _and_ setgid on a non-POSIX environment (mode 6755), or setuid root if you compiled the wrapper using the POSIX rules in the Makefile. --Dave From majordomo-users-owner Tue Aug 30 00:06:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id AAA01977; Tue, 30 Aug 1994 00:06:54 GMT Received: from relay3.UU.NET by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id RAA01970; Mon, 29 Aug 1994 17:06:43 -0700 Received: from uucp6.UU.NET by relay3.UU.NET with SMTP id QQxfcq29016; Mon, 29 Aug 1994 20:11:45 -0400 Received: from csfb1.UUCP by uucp6.UU.NET with UUCP/RMAIL ; Mon, 29 Aug 1994 20:11:45 -0400 Received: from csfb.co.jp (japan) by csfb1 (4.1/SMI-4.1.v1) id AA29307; Mon, 29 Aug 94 20:03:27 EDT Received: from toro by csfb.co.jp (4.1/SMI-4.1.v1) id AA21092; Tue, 30 Aug 94 09:03:42 JST From: csfb1!japan!ahokas@uunet.uu.net (Jim Ahokas) Received: by toro (NeXT-1.0 (From Sendmail 5.52)/Jimbo-2.0) id AA12205; Tue, 30 Aug 94 09:03:41 JST Date: Tue, 30 Aug 94 09:03:41 JST Message-Id: <9408300003.AA12205@toro> Received: by NeXT Mailer (1.63) To: majordomo-users@greatcircle.com Subject: resend's files in /tmp Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I have recently upgraded to 1.92 and all is 100%. however, I have noticed that resend putS a .in and .out file in /tmp for each mail handled by resend. -rw-rw---- 1 daemon 2287 Aug 30 08:29 resend.20860.in -rw-rw---- 1 daemon 2197 Aug 30 08:29 resend.20860.out Can this be cleaned up with a modification to majordomo or should I just put in a cron to clean things up. /tmp will eventually fill up if left un-checked. Thanks Jim --- Jim Ahokas DOMAIN: ahokas@csfb1.fir.fbc.com CS First Boston (Japan) UUCP: ..uunet!csfb1!japan!ahokas 4-3-1 Toranomon, Minato-ku VOICE: (03)-5404-9562 Tokyo 105, Japan FAX: (03)-5404-9844 From majordomo-users-owner Tue Aug 30 06:28:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id GAA06446; Tue, 30 Aug 1994 06:28:01 GMT Received: from mwunix.mitre.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA27232; Mon, 29 Aug 1994 11:32:15 -0700 Received: from mental (mental.mitre.org [128.29.135.14]) by mwunix.mitre.org (8.6.4/8.6.4) with SMTP id OAA06453 for ; Mon, 29 Aug 1994 14:37:18 -0400 Received: by mental (5.65/MITRE-SS2) id AA12703; Mon, 29 Aug 1994 14:37:17 -0400 Date: Mon, 29 Aug 1994 14:37:17 -0400 From: jwagner@mental.mitre.org (John G. Wagner) Message-Id: <9408291837.AA12703@mental> To: Majordomo-Users@greatcircle.com Subject: error found in majordomo.cf X-Status: N X-Mailer: Applixware 3.1(124) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I think I've worked out the problem! I F'ed up!! I removed the last line of the majordomo.cf file, you know, the one with only "1"; Well when I added it back in things started to work ok. Mind you that all is not perfect yet, but majordomo doesn't throw large heavy objects in my general direction anymore. I've tested the subscribe/unsubscribe features from my own machine, and will be testing the remote stuff right after I finish this note. I'll also try to subscribe/unsubscribe from a different user to see how the approve works. Thanks again John +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Heck even I don't know what I do, so the company can't. + + empire isn't a game, it's a world ruled by elves! :) + + Bowling IS a sport, and if you don't believe me, I'll beat'ya + + and YES I mean with a BIG stick!! }:@ + + jwagner@mitre.org | John Wagner | PH# (703)883-3740 + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From majordomo-users-owner Tue Aug 30 01:21:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id GAA06905; Tue, 30 Aug 1994 06:49:42 GMT Received: from gatekeeper.roche.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id XAA06893; Mon, 29 Aug 1994 23:49:26 -0700 Received: by gatekeeper.roche.com (5.65/fma-120691); id AA28683; Tue, 30 Aug 94 02:54:28 -0400 Received: by mailgate.roche.com (5.65/fma-120691); id AA09651; Tue, 30 Aug 94 02:54:27 -0400 Received: from conversion.RBAC01 by RBAC01.BAS.ROCHE.COM (PMDF V4.3-7 #5197) id <01HGIIXKQ2TC98706I@RBAC01.BAS.ROCHE.COM>; Tue, 30 Aug 1994 08:44:20 MET Received: from mr.bas.roche.com by RBAC01.BAS.ROCHE.COM (PMDF V4.3-7 #5197) id <01HGIIL0WHGW96VY2K@RBAC01.BAS.ROCHE.COM>; Tue, 30 Aug 1994 08:34:15 MET Received: with PMDF-MR; Tue, 30 Aug 1994 08:25:04 MET Mr-Received: by mta ROCBI.MUAS; Relayed; Tue, 30 Aug 1994 08:25:04 +0100 Mr-Received: by mta RBIZ06; Relayed; Tue, 30 Aug 1994 08:25:05 +0100 Mr-Received: by mta RBAC01; Relayed; Tue, 30 Aug 1994 08:25:07 +0100 Disclose-Recipients: prohibited Date: Tue, 30 Aug 1994 08:25:04 +0100 (MET) From: BAUMANNM +61 68 73 52 0 Subject: Re: Returned mail: unknown mailer error 255 In-Reply-To: <23109192804991/458256@RBAC01> To: Majordomo-Users Message-Id: <9804250830081994/A96406/RBIZ06/1188F2190100*@MHS> Autoforwarded: false Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Conversion: prohibited Importance: low Priority: non-urgent Ua-Content-Id: 1188F2190100 X400-Mts-Identifier: [;9804250830081994/A96406/RBIZ06] Hop-Count: 2 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Could it be that you sendmail aliases file has a wrong alias? That was what I had. -r Michael ..> Ok I've tried perl majordomo.cf, but no errors. ..> I tried "perl majordomo" but it just hangs ( did give me an error to ..> start with, but I removed the line about safedir, and now it doesn't ..> bark about that, but still I get this F'ing error, unknown mailer 255. ..> ..> I tried sending mail to majordomo with subscribe/unsubscribe/info ..> and list but nothing! all gave me the same results. ..> ..> Could it be the way majordomo is talking to sendmail? and I had ..> version 1.62? running for 1 day or 2 just before I upgraded to ..> 1.92, and now nothing works!! ..> ..> Any more ideas? From majordomo-users-owner Tue Aug 30 13:13:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id NAA10714; Tue, 30 Aug 1994 13:13:42 GMT Received: from mv.mv.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id GAA10708; Tue, 30 Aug 1994 06:13:30 -0700 Received: by mv.mv.com (8.6.9/mv(b)/mem-940616) id JAA02690; Tue, 30 Aug 1994 09:18:25 -0400 Received: from magpie.mv.com by summa4.mv.COM (4.1/SMI-4.1) id AA02257; Tue, 30 Aug 94 08:51:08 EDT Date: Tue, 30 Aug 94 08:51:08 EDT From: lrc@summa4.MV.COM (Lawrence R. Cook) Message-Id: <9408301251.AA02257@summa4.mv.COM> To: csfb1!japan!ahokas@uunet.uu.net Subject: Re: resend's files in /tmp Cc: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > From majordom Mon Aug 29 20:44:01 1994 > From: csfb1!japan!ahokas@uunet.uu.net (Jim Ahokas) > I have recently upgraded to 1.92 and all is 100%. however, I have > noticed that resend putS a .in and .out file in /tmp for each mail > handled by resend. > > -rw-rw---- 1 daemon 2287 Aug 30 08:29 resend.20860.in > -rw-rw---- 1 daemon 2197 Aug 30 08:29 resend.20860.out > > Can this be cleaned up with a modification to majordomo or should I > just put in a cron to clean things up. /tmp will eventually fill up > if left un-checked. Jim, I just found this same problem recently. In resend, change line 347 to be the same as line 335: 347c347 < unlink("/tmp/resend.$$.*"); --- > unlink(); --------------------------------------------------------------------- Larry Cook, Senior Software Engineer Email: lrc@summa4.mv.com Summa Four, Inc. Phone: (603) 625-4050 x2566 25 Sundial Ave, Manchester, NH 03103-7251 Fax : (603) 668-4491 From majordomo-users-owner Tue Aug 30 14:59:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id OAA11548; Tue, 30 Aug 1994 14:59:44 GMT Received: from mwunix.mitre.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id HAA11541; Tue, 30 Aug 1994 07:59:34 -0700 Received: from mental (mental.mitre.org [128.29.135.14]) by mwunix.mitre.org (8.6.4/8.6.4) with SMTP id LAA28617 for ; Tue, 30 Aug 1994 11:04:26 -0400 Received: by mental (5.65/MITRE-SS2) id AA18148; Tue, 30 Aug 1994 11:04:26 -0400 Date: Tue, 30 Aug 1994 11:04:26 -0400 From: jwagner@mental.mitre.org (John G. Wagner) Message-Id: <9408301504.AA18148@mental> To: Majordomo-Users@greatcircle.com Subject: Slow times on returns X-Status: N X-Mailer: Applixware 3.1(124) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Ok I looked at the Log file, it's there, and the entire directory and subs are set to 775, owner majordomo, group majordomo. this is true in all cases except wrapper which has a owner of daemon. I checked the files that are created during a event, and all of them are owned by "majordomo-owner" and after the file is updated then and only then is it changed back to majordomo as owner, is this a problem? did I do something wrong? and YES everybody I did read the FAQ and checked the permissions first, I've even tried setting everything to 777 and then it works fine. But I don't want the world to be able to write in those directories, or even allow that person to be able to edit ANY file in it, so what do I need to change and where? John +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Heck even I don't know what I do, so the company can't. + + empire isn't a game, it's a world ruled by elves! :) + + Bowling IS a sport, and if you don't believe me, I'll beat'ya + + and YES I mean with a BIG stick!! }:@ + + jwagner@mitre.org | John Wagner | PH# (703)883-3740 + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From majordomo-users-owner Tue Aug 30 19:34:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id TAA13798; Tue, 30 Aug 1994 19:34:45 GMT Received: from csn.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id MAA13791; Tue, 30 Aug 1994 12:33:06 -0700 Received: from gateway.meu.edu (meu.edu) by csn.org with SMTP id AA27362 (5.65c/IDA-1.4.4 for ); Tue, 30 Aug 1994 13:37:19 -0600 Subject: Help with configuring Majordomo To: majordomo-users@greatcircle.com Date: Tue, 30 Aug 1994 13:35:41 -0600 (MDT) From: Dan Torbet X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 807 Message-Id: <9408301335.aa15716@gateway.meu.edu> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have been trying to get Majordomo to work with SCO and mmdf ver 43IIb and am running into a stubborn problem. When a user sends mail to the list, a message is sent to the entire list saying sender is not authenticated. The message is stamped with the from field as owner-list@meu.edu. What does this mean, and how do I fix it? Do I need to set auth variables in mmdftailor? Anyone have any ideas? Thanks, Dan Torbet torbet@meu.edu Here is the actual message:  From sample-request Tue Aug 30 15:13:22 1994 Received: from meu.edu by gateway.meu.edu id aa13762; 30 Aug 94 15:13 GMT Date: Tue, 30 Aug 94 15:13:19 GMT From: owner-sample@meu.edu Sender: owner-sample@meu.edu Message-ID: <9408301513.aa13758@gateway.meu.edu> Source-Info: From (or Sender) name not authenticated. Status: RO  From majordomo-users-owner Wed Aug 31 18:52:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id SAA24172; Wed, 31 Aug 1994 18:52:05 GMT Received: from pollux.cs.uga.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id LAA24166; Wed, 31 Aug 1994 11:51:47 -0700 Received: from jupiter (jupiter.cs.uga.edu) by pollux.cs.uga.edu (4.1/25-eef) id AA03599; Wed, 31 Aug 94 14:56:23 EDT Received: from ajax by jupiter (4.1/SMI-4.1) id AA19680; Wed, 31 Aug 94 14:56:43 EDT Received: by ajax (4.1/SMI-4.1) id AA11084; Wed, 31 Aug 94 14:54:28 EDT From: greg@pollux.cs.uga.edu (Greg Whitlock) Message-Id: <9408311854.AA11084@ajax> Subject: archive and digest questions To: majordomo-users@greatcircle.com Date: Wed, 31 Aug 1994 14:54:27 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 337 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've recently installed Majordomo v.1-92 and everything works real well except archiving and digesting. The initial config file that the list-owner gets says that these two features do not work. Is this still the case? If it's not, then I'm overlooking something. Any help would be appreciated. Thanks! -greg (greg@cs.uga.edu) From majordomo-users-owner Wed Aug 31 19:12:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id TAA24340; Wed, 31 Aug 1994 19:12:00 GMT Received: from hmco.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id MAA24334; Wed, 31 Aug 1994 12:11:49 -0700 Received: by hmco.com (5.65/DEC-Ultrix/4.3/jcurran+a1+umc+dnet) id AA09171; Wed, 31 Aug 1994 15:15:50 -0400 Received: by willy.hmco.com (5.0/SMI-SVR4) id AA10467; Wed, 31 Aug 1994 15:13:47 +0500 Date: Wed, 31 Aug 1994 15:13:47 +0500 From: alaka@hmco.com (Ghassan J. Alaka) Message-Id: <9408311913.AA10467@willy.hmco.com> To: majordomo-users@greatcircle.com Subject: archive error message X-Sun-Charset: US-ASCII Content-Length: 410 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've just finished setting up Majordomo v.1-92. Everything is working fine but, when a message is sent to the list an error message is mailed back to the list owner with the following: /usr/local/mail/archive/it... Can't create output I've opened-up the permissions on the whole file structure, and still get that error message. Any help would be appreciated. THANKS, PS: "it" is the name of the list From majordomo-users-owner Wed Aug 31 19:14:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id TAA24357; Wed, 31 Aug 1994 19:14:58 GMT Received: from ciesin.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id MAA24351; Wed, 31 Aug 1994 12:14:38 -0700 Received: from mail.ciesin.org (mail.ciesin.org [160.39.8.11]) by ciesin.org (8.6.9/8.6.9) with SMTP id PAA05003 for ; Wed, 31 Aug 1994 15:19:41 -0400 Message-Id: <199408311919.PAA05003@ciesin.org> X-Authentication-Warning: mail.ciesin.org: Host mail.ciesin.org didn't use HELO protocol To: majordomo-users@greatcircle.com Subject: Majordomo permissions Date: Wed, 31 Aug 1994 15:19:40 -0400 From: Jeff Blaine Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've added the user `daemon' to group `majordom' at our site and taken all `other' permissions off of all files under $MAJORDOMO_ROOT so no one can poke around in our majordomo stuff, but sendmail and the majordomo `wrapper' can still work. Everything appears to work just fine. Can anyone think of a reason not to do what I've done? We're running sendmail 8.6.9 and Majordomo 1.92. ------- Jeff Blaine CIESIN Operations From majordomo-users-owner Wed Aug 31 19:25:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id TAA24470; Wed, 31 Aug 1994 19:25:13 GMT Received: from alpha.xerox.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id MAA24462; Wed, 31 Aug 1994 12:24:49 -0700 Received: from samoyed.wrc.xerox.com ([13.0.32.6]) by alpha.xerox.com with SMTP id <14409(2)>; Wed, 31 Aug 1994 12:29:06 PDT Received: by samoyed.wrc.xerox.com (4.1/SMI-4.1) id AA12950; Wed, 31 Aug 94 15:29:05 EDT Date: Wed, 31 Aug 1994 12:29:05 PDT From: slade@wrc.xerox.com (Mike Slade) Message-Id: <9408311929.AA12950@samoyed.wrc.xerox.com> To: majordomo-users@greatcircle.com Subject: Solaris 2.x permissions Cc: slade@wrc.xerox.com, carlos@vacuum.org Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am helping getting majordomo 1.92 on a Sun running Solaris 2.2. Of course, I have permissions problems! I think I understand that I need to use the POSIX defaults rather than the BSD options in the Makefile but I have questions about W_UID and W_GID. In the Makefile: W_UID = 1 W_GID = 15 Should W_UID be the uid of root (0 on my system) and W_GID be the gid for majordom (or what special group you have called it) which is not 15 on my system? thanks -- Michael Slade Xerox Webster Research Center Phone: (716) 422-5346 FAX: x2126 800 Phillips Road, 0128-27E Internet: slade@wrc.xerox.com Webster, New York 14580 XNS: slade:wbst128:xerox:com From majordomo-users-owner Wed Aug 31 20:28:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id UAA25007; Wed, 31 Aug 1994 20:28:01 GMT Received: from ftp.std.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id NAA24999; Wed, 31 Aug 1994 13:27:47 -0700 Received: from world.std.com by ftp.std.com (8.6.8.1/Spike-8-1.0) id QAA24029; Wed, 31 Aug 1994 16:32:45 -0400 Received: by world.std.com (5.65c/Spike-2.0) id AA27878; Wed, 31 Aug 1994 16:32:44 -0400 Date: Wed, 31 Aug 1994 16:32:43 -0400 (EDT) From: Miles R Fidelman Subject: approved header question 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 Hi Folks, I've had varying luck using the Approved: password header to approve bounced messages. Majordomo seems to have no problem recognizing the approval and posting the message to a list, but it sometimes doesn't strip off the header, leaving the password exposed to everyone on the list. Can anybody suggest a reliable way to use the header? Thanks much, Miles Fidelman ************************************************************************** Miles R. Fidelman mfidelman@civicnet.org President 91 Baldwin St. Charlestown MA 02129 Director of Civic Networking Systems 617-241-9205 fax: 617-241-5064 The Center for Civic Networking Check out our Civic Network gopher and web servers: at a unix prompt: gopher gopher.civic.net 2400 gopher URL: gopher://gopher.civic.net:2400/ web URL: http://www.civic.net:2401/ Information Infrastructure: Public Spaces for the 21st Century Let's Start With: Internet Wall-Plugs Everywhere Say It Now, Say It Often: "I Want My Internet!" ************************************************************************** From majordomo-users-owner Wed Aug 31 20:36:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id UAA25119; Wed, 31 Aug 1994 20:36:47 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id NAA25097; Wed, 31 Aug 1994 13:36:26 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id QAA21796; Wed, 31 Aug 1994 16:40:52 -0400 Message-Id: <199408312040.QAA21796@bosnia.pop.psu.edu> To: slade@wrc.xerox.com (Mike Slade) cc: majordomo-users@GreatCircle.COM, carlos@vacuum.org Subject: Re: Solaris 2.x permissions In-reply-to: Your message of "Wed, 31 Aug 1994 12:29:05 PDT." <9408311929.AA12950@samoyed.wrc.xerox.com> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Wed, 31 Aug 1994 16:40:51 -0400 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9408311929.AA12950@samoyed.wrc.xerox.com>, Mike Slade writes: >I am helping getting majordomo 1.92 on a Sun running Solaris 2.2. > >Of course, I have permissions problems! > >I think I understand that I need to use the POSIX defaults rather than the BSD > options in the Makefile but I have questions about W_UID and W_GID. yeah, the Makefile and README could be a little clearer here. W_UID should be the uid of your majordomo user, and W_GID should be the gid of the majordomo group. They are analogous to the W_USER and W_GROUP of the non-POSIX configuration. --Dave From majordomo-users-owner Wed Aug 31 21:24:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id VAA25509; Wed, 31 Aug 1994 21:24:53 GMT Received: from gateway.Stoner.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id OAA25503; Wed, 31 Aug 1994 14:24:41 -0700 Received: from uhura1.Stoner.COM (uhura1.Stoner.COM [198.64.192.11]) by gateway.Stoner.COM (8.6.9/8.6.4) with ESMTP id NAA00291; Wed, 31 Aug 1994 13:48:59 -0700 Received: from crusher.Stoner.COM (crusher.Stoner.COM [198.64.192.28]) by uhura1.Stoner.COM (8.6.9/8.6.9) with ESMTP id QAA04315; Wed, 31 Aug 1994 16:27:55 -0500 From: "A. Bryan Curnutt" Received: from localhost (curnutt@localhost) by crusher.Stoner.COM (8.6.5/8.6.5) id QAA09228; Wed, 31 Aug 1994 16:27:55 -0500 Message-Id: <199408312127.QAA09228@crusher.Stoner.COM> Subject: Re: Solaris 2.x permissions To: barr@pop.psu.edu (David Barr) Date: Wed, 31 Aug 1994 16:27:53 -0500 (CDT) Cc: slade@wrc.xerox.com, majordomo-users@GreatCircle.COM, carlos@vacuum.org In-Reply-To: <199408312040.QAA21796@bosnia.pop.psu.edu> from "David Barr" at Aug 31, 94 04:40:51 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 403 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk David Barr writes: > > W_UID should be the uid of your majordomo user, and W_GID should be > the gid of the majordomo group. For some versions of sendmail (_not_ 8.6.9), doesn't the W_UID need to be "daemon" or another user that's on the "trusted" list? -- Bryan Curnutt Stoner Associates, Inc. bryan.curnutt@stoner.com (713)626-9568 voice (713)622-7832 fax From majordomo-users-owner Wed Aug 31 21:50:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id VAA25754; Wed, 31 Aug 1994 21:50:27 GMT Received: from qks.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id OAA25740; Wed, 31 Aug 1994 14:50:15 -0700 Received: from [192.55.204.23] by qks.com (8.6.4/3.1.012693-Quasar Knowledge Systems) via SMTP; id RAA06772 for ; Wed, 31 Aug 1994 17:55:29 -0400 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 31 Aug 1994 17:55:50 -0400 To: majordomo-users@greatcircle.com From: faisal@qks.com (Faisal Nameer Jawdat) Subject: lame digesting solution Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I tried digesting as listed in the README, but it said -l was not a good argument. Any suggestions? In the meantime, I wrote a shell script which throws the latest archive of the list foo out to foo-digprep, which goes through the resend (like foo goes to foo-outgoing) to foo-digest-outgoing. However, "To:" is foo-digprep, and I can't figure out how to have it say to is foo-digest instead. Is there an easier way to do this? Does anyone know how to make archive work instead? -fiz From majordomo-users-owner Wed Aug 31 22:15:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id WAA25986; Wed, 31 Aug 1994 22:15:26 GMT Received: from gateway.Stoner.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id PAA25970; Wed, 31 Aug 1994 15:15:07 -0700 Received: from uhura1.Stoner.COM (uhura1.Stoner.COM [198.64.192.11]) by gateway.Stoner.COM (8.6.9/8.6.4) with ESMTP id OAA00756; Wed, 31 Aug 1994 14:39:19 -0700 Received: from crusher.Stoner.COM (crusher.Stoner.COM [198.64.192.28]) by uhura1.Stoner.COM (8.6.9/8.6.9) with ESMTP id RAA05273; Wed, 31 Aug 1994 17:18:17 -0500 From: "A. Bryan Curnutt" Received: from localhost (curnutt@localhost) by crusher.Stoner.COM (8.6.5/8.6.5) id RAA09379; Wed, 31 Aug 1994 17:18:16 -0500 Message-Id: <199408312218.RAA09379@crusher.Stoner.COM> Subject: Re: lame digesting solution To: faisal@qks.com (Faisal Nameer Jawdat) Date: Wed, 31 Aug 1994 17:18:15 -0500 (CDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Faisal Nameer Jawdat" at Aug 31, 94 05:55:50 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3174 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Faisal Nameer Jawdat writes: > > I tried digesting as listed in the README, but [...] There seems to be a lot of this going around -- trouble getting digests and archiving to work... Here's an example configuration that I use for my lists that seems to work. (Mine are currently very low volume, though, so this hasn't been tested extensively.) For a mailing list named foo that has both digesting and archiving, I have the following configured: In my aliases file: ---------------------------------------------------------------------- # begin majordomo-handled list foo owner-foo: curnutt owner-foo-outgoing: owner-foo foo-request: "|/usr/local/lib/majordomo/wrapper majordomo -l foo" foo-approval: curnutt foo-digest-request: "|/usr/local/lib/majordomo/wrapper majordomo -l foo" foo-digest-approval: curnutt foo: "|/usr/local/lib/majordomo/wrapper resend -l foo -h Stoner.COM foo-outgoing" foo-digest: foo foo-outgoing: :include:/usr/local/mail/lists/foo, "| /usr/local/lib/majordomo/wrapper digest -r -C -l foo foo-digest-outgoing", "| /usr/local/lib/majordomo/wrapper archive2.pl -a -m -f /usr/local/mail/archive/foo/foo.archive" foo-digest-outgoing: :include:/usr/local/mail/lists/foo-digest owner-foo-digest: owner-foo owner-foo-digest-outgoing: owner-foo # end of majordomo-handled list foo ---------------------------------------------------------------------- My majordomo.cf file, sans comments and blank lines: ---------------------------------------------------------------------- $whereami = "Stoner.COM"; $whoami = "Majordomo@$whereami"; $whoami_owner = "Majordomo-Owner@$whereami"; if ( defined $ENV{"HOME"}) { $homedir = $ENV{"HOME"}; } else { $homedir = "/usr/local/lib/majordomo"; } $listdir = "/usr/local/mail/lists"; $digest_work_dir = '/usr/local/mail/digest'; $log = "$homedir/Log"; $mailer = "/usr/lib/sendmail -f\$sender -t"; $filedir = "/usr/local/mail/archive"; $filedir_suffix = ""; $index_command = "/bin/ls -lRL"; $return_subject = 1; $majordomo_request = 1; umask(007); @safedirs = ( ); 1; ---------------------------------------------------------------------- Root's crontab includes the line: ---------------------------------------------------------------------- 45 2 * * * /bin/sh /usr/local/lib/majordomo/digest.send ---------------------------------------------------------------------- /usr/local/mail/lists includes the files foo (addresses for the "foo" mailing list), foo-digest (addresses for the "foo-digest" mailing list), foo-digest.config, foo.config, foo.info, and foo.passwd. /usr/local/mail/digest has a directory named "foo", which is used to temporarily accumulate messages for digesting. /usr/local/mail/archive has a directory named "foo", which is where archives for the "foo" list are stored. I've copied "archive2.pl" from the "Tools" subdirectory into the /usr/local/lib/majordomo directory, so it's accessible to wrapper. I've also copied "digest.send" from the "contrib" subdirectory into the /usr/local/lib/majordomo directory. -- Bryan Curnutt Stoner Associates, Inc. bryan.curnutt@stoner.com (713)626-9568 voice (713)622-7832 fax From majordomo-users-owner Wed Aug 31 22:55:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id WAA26306; Wed, 31 Aug 1994 22:55:56 GMT Received: from midway.uchicago.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id PAA26300; Wed, 31 Aug 1994 15:55:44 -0700 From: ckoenig@midway.uchicago.edu Received: from kimbark.uchicago.edu by midway.uchicago.edu for majordomo-users@greatcircle.com Wed, 31 Aug 94 18:00:45 CDT Received: from localhost.uchicago.edu by kimbark.uchicago.edu (4.1/UCCO-1.0A) id AA07949; Wed, 31 Aug 94 17:57:47 CDT Message-Id: <9408312257.AA07949@kimbark.uchicago.edu> Reply-To: ckk@uchicago.edu To: faisal@qks.com (Faisal Nameer Jawdat) Cc: majordomo-users@greatcircle.com Subject: Re: lame digesting solution In-Reply-To: Your message of "Wed, 31 Aug 94 17:55:50 EDT." Date: Wed, 31 Aug 94 17:57:46 -0500 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here is a working example from /etc/aliases, for a list, with archiving through "archive2.pl", also digestification through "digest", plus the aliases for the associated digest list. This system is running Majordomo v1.92, Sendmail 8.6.9, on SunOS 4.1.3 U1.1.1. I actually generate this set of aliases from a Perl script, which uses a template and fills in values. As input, it takes a "lists.attributes" file (each entry specifies a listname, archive freq., digest enabled?, and listowner address). If a list's archive frequency attribute is "none", the script will leave out all archive-related aliases and commands; similarly for digestification. Note that I've chosen to make a separate "listname-mkdigest" alias, for the command to run a new message through the digest script to add it to the digest's working directory. This cleans up the appearance of the "listname-outgoing" alias. Once this script is more polished, and joined by several others in our Majordomo Administrator's Toolkit, I will share it with Majordomo-Users and Workers. In addition to generating the aliases for a new list, there will be a module to create the necessary files (listname, listname.passwd) and directories (archive/listname, digest/listname-digest), also a module to verify the correctness of the setup for an existing list.... In addition to these /etc/aliases entries and the listname files and directories, the other parts of the system are a set of cron jobs. Most of the jobs came from the "contrib" stuff in the Majordomo 1.92 release. One job, several times a day, runs an "archive-index" shellscript which runs "makeindex.pl" on each non-empty per-list archive subdir. Another job runs nightly, invoking "digest.send" to push out digest issues for all activated digest lists. Without this digest.send, you'd never see a digest issue, unless you have manually sent "mkdigest listname-digest " commands to Majordomo, or if the maximum digest size is reached by the total of the files in the digest's work directory (I've applied Paul Close's patch to our "digest"). A third job runs the "rotate_log" Perl script, to rotate various logfiles (Log -> Log.0 -> Log.1 -> Log.2), including tcp_wrapper logs, Majordomo's main Log file (which I hope to convert to using syslog one of these days soon) and the log file of the archive-index script. ("rotate_log" came off the net somewhere, written by Steve Simmons, scs@lokkur.dexter.mi.us, in 1991) I hope this helps at least a tiny bit. -- Chris Koenigsberg ------------------------------------------------------------------------ ######################################################################## # Begin aliases for christest mailing list # Archiving: monthly, Digestification: yes, ListOwner:ckk@uchicago.edu. # Note that long lines have been broken up to send this through email; # the backslash+newlines should be deleted in a real # /etc/aliases file! christest: "| /var/majordomo/v1.92/wrapper resend -h \ listhost.uchicago.edu -l christest christest-outgoing" owner-christest: christest-owner christest-owner: ckk@uchicago.edu christest-request: "| /var/majordomo/v1.92/wrapper majordomo -l \ christest" christest-approval: owner-christest christest-outgoing: :include:/var/majordomo/lists/christest, \ christest-archive, christest-mkdigest owner-christest-outgoing: owner-christest christest-archive: | "/var/majordomo/v1.92/wrapper archive2.pl -f \ /var/majordomo/archive/christest.archive/christest -m -a" christest-mkdigest: "| /var/majordomo/v1.92/wrapper digest -r -C -l \ christest-digest christest-digest-outgoing" christest-digest: christest christest-digest-request: "| /var/majordomo/v1.92/wrapper majordomo \ -l christest-digest" owner-christest-digest-request: owner-christest christest-digest-approval: owner-christest owner-christest-digest-approval: owner-christest christest-digest-outgoing: :include:/var/majordomo/lists/christest-digest owner-christest-digest-outgoing: owner-christest # End of christest list aliases From majordomo-users-owner Wed Aug 31 23:50:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id XAA26820; Wed, 31 Aug 1994 23:50:13 GMT Received: from ftp.std.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940829) id QAA26814; Wed, 31 Aug 1994 16:50:01 -0700 Received: from world.std.com by ftp.std.com (8.6.8.1/Spike-8-1.0) id TAA08889; Wed, 31 Aug 1994 19:54:54 -0400 Received: by world.std.com (5.65c/Spike-2.0) id AA21022; Wed, 31 Aug 1994 19:54:52 -0400 Message-Id: <199408312354.AA21022@world.std.com> To: Miles R Fidelman Cc: majordomo-users@GreatCircle.COM Subject: Re: approved header question Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Date: Wed, 31 Aug 1994 19:54:52 -0400 From: Joe Ilacqua Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I suggest using the "approve", see "man approve". ->Spike