From majordomo-users-owner Fri Sep 1 10:30:18 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA05236 for majordomo-users-outgoing; Fri, 1 Sep 1995 10:15:21 -0700 Received: from ruok ([204.32.101.202]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA05229 for ; Fri, 1 Sep 1995 10:15:15 -0700 Received: from walts by ruok (SMI-8.6/SMI-SVR4) id KAA18321; Fri, 1 Sep 1995 10:13:16 -0700 Message-Id: <199509011713.KAA18321@ruok> Comments: Authenticated sender is From: "Walter Reed" Organization: caligari.com To: majordomo-users@greatcircle.com Date: Fri, 1 Sep 1995 10:10:16 +0000 Subject: Hiding a list Reply-to: walt@caligari.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have just about tried everything to hide a list yet it still shows up on the lists command. I have tried: noadvertise << END /.*/ END noadvertise << END .* END noadvertise = /.*/ #END noadvertise = .* #END What value or method does work to hide a list? Thanks... --- Walter Reed (walt@caligari.com) From majordomo-users-owner Fri Sep 1 11:30:35 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA07464 for majordomo-users-outgoing; Fri, 1 Sep 1995 11:03:23 -0700 Received: from welby.ahc.ameritech.com (welby.ahc.ameritech.com [165.252.0.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA07452 for ; Fri, 1 Sep 1995 11:03:16 -0700 Received: by welby.ahc.ameritech.com (/\==/\ Smail3.1.28.1 #28.8) id ; Fri, 1 Sep 95 13:01 CDT Received: by Koop.Chi.AHC.Ameritech.COM (/\==/\ Smail3.1.28.1 #28.10) id ; Fri, 1 Sep 95 12:59 BST Message-Id: From: mandrews@Chi.AHC.Ameritech.COM (Mike Andrews) Subject: Re: Hiding a list To: walt@caligari.com Date: Fri, 1 Sep 1995 12:59:27 -0500 (CDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <199509011713.KAA18321@ruok> from "Walter Reed" at Sep 1, 95 10:10:16 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: 878 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Walter Reed > > I have just about tried everything to hide a list yet it still shows > up on the lists command. I have tried: > > noadvertise << END > /.*/ > END > > noadvertise << END > .* > END > > noadvertise = /.*/ > #END > > noadvertise = .* > #END > > What value or method does work to hide a list? > This works here: # noadvertise << END /.*/ END # You need to preserve the blank line before the END line. --Mike =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Mike Andrews mandrews@AHC.Ameritech.COM Technology Consultant mike@CHIN.NET Network Services - National Operations (312) 460-2753 Ameritech Health Connections Chicago, IL USA =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From majordomo-users-owner Fri Sep 1 11:32:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA07904 for majordomo-users-outgoing; Fri, 1 Sep 1995 11:08:54 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA07873 for ; Fri, 1 Sep 1995 11:08:47 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA26370 for majordomo-users@greatcircle.com; Fri, 1 Sep 95 11:07:18 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA08879; Fri, 1 Sep 95 11:06:24 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA08260 for majordomo-users@greatcircle.com; Fri, 1 Sep 95 11:06:23 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA20895; Fri, 1 Sep 95 13:06:21 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA10578; Fri, 1 Sep 1995 13:06:19 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509011806.AA10578@miaow.sps.mot.com> Subject: Re: Hiding a list To: uunet!caligari.com!walt Date: Fri, 1 Sep 1995 13:06:19 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509011713.KAA18321@ruok> from "Walter Reed" at Sep 1, 95 10:10:16 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 575 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Walter Reed writes: ] > > I have just about tried everything to hide a list yet it still shows > up on the lists command. I have tried: > > noadvertise << END > /.*/ > END That's the correct form, forget the rest. There's one caveat not mentioned: even if your address is not matched by advertise or is matched by noadvertise, lists always works for list members. You're apparently subscribed to the list you're trying to hide. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Fri Sep 1 12:01:29 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA09445 for majordomo-users-outgoing; Fri, 1 Sep 1995 11:38:11 -0700 Received: from gatekeeper.ray.com (gatekeeper.ray.com [138.125.162.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA09416 for ; Fri, 1 Sep 1995 11:38:04 -0700 Received: from localhost (mailer@localhost) by gatekeeper.ray.com (8.6.4/8.6.5) id OAA23661; Fri, 1 Sep 1995 14:31:32 -0400 Received: from rayssd.ssd.ray.com by gatekeeper.ray.com; Fri Sep 1 14:35:43 1995 Received: from fluke.ssd.ray.com (fluke.ssd.ray.com [138.125.192.34]) by rayssd.ssd.ray.com (8.6.12/8.6.12) with ESMTP id OAA20901; Fri, 1 Sep 1995 14:35:18 -0400 Received: (dhb@localhost) by fluke.ssd.ray.com (8.6.12/8.6.12) id OAA26991; Fri, 1 Sep 1995 14:35:17 -0400 Date: Fri, 1 Sep 1995 14:35:15 -0400 (EDT) From: "David H. Brierley" To: Walter Reed cc: majordomo-users@GreatCircle.COM Subject: Re: Hiding a list In-Reply-To: <199509011713.KAA18321@ruok> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 1 Sep 1995, Walter Reed wrote: > I have just about tried everything to hide a list yet it still shows > up on the lists command. I have tried: I use the following on several of my internal lists and it works quite nicely. noadvertise << END /./ END I use this to prevent idiot users from attempting to subscribe to some of my closed lists. I got tired of users that would send a "lists" command and then edit the output to attempt to subscribe to every list. -- David H. Brierley Raytheon Company; Electronic Systems Division - Portsmouth RI Facility Work: dhb@ssd.ray.com Home: dave@galaxia.network23.com From majordomo-users-owner Fri Sep 1 13:32:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA18762 for majordomo-users-outgoing; Fri, 1 Sep 1995 13:32:17 -0700 Received: from holodeck.cc.vt.edu (holodeck.cc.vt.edu [128.173.16.28]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA18748 for ; Fri, 1 Sep 1995 13:32:11 -0700 Received: from ebbs.english.vt.edu by holodeck.cc.vt.edu with SMTP (8.6.12/16.2) id QAA20425; Fri, 1 Sep 1995 16:29:29 -0400 Received: by ebbs.english.vt.edu id AA06821 (5.67b/IDA-1.5 for majordomo-users@greatcircle.com); Fri, 1 Sep 1995 16:28:30 -0400 From: Len Hatfield Message-Id: <199509012028.AA06821@ebbs.english.vt.edu> Subject: Problem:"wrapper not available to sendmail programs"? To: majordomo-users@greatcircle.com Date: Fri, 1 Sep 1995 16:28:29 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 925 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi. No doubt this is an oft asked question, but here goes: I've installed Majordomo 1.93, in a Linux (1.2.13-Posix) system, running Sendmail and Perl 4.036. I've put an alias in my system alias file (in /usr/local/lib/mail/xaliases) that looks like this: majordomo: "|/usr/listware/moe/bin/wrapper majordomo" (which includes the path to wrapper and majordomo), and I've run 'make' which installs new aliases. I've set wrapper to the majordomo GID and its permissions to 777 (just to be blunt). But when I send a mail message ('help') to uid majordomo, it bounces back with the following error message: sh: wrapper not available for sendmail programs 554 "|/usr/listware/moe/bin/wrapper majordomo"... Service unavailable I'll be grateful for advice and correction... Thanks! --- ...Len Hatfield From majordomo-users-owner Fri Sep 1 17:00:20 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA26465 for majordomo-users-outgoing; Fri, 1 Sep 1995 16:43:40 -0700 Received: from halcyon.com (coho.halcyon.com [198.137.231.21]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA02633 for ; Thu, 31 Aug 1995 14:18:03 -0700 Received: by halcyon.com id AA11879 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Thu, 31 Aug 1995 14:16:38 -0700 Date: Thu, 31 Aug 1995 14:16:37 -0700 (PDT) From: "Seattle Internet Sig Mailing List Mgr." To: majordomo-users@greatcircle.com Subject: Why does this bounce? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We have the list set up to bounce posts to the list-owner for having "subscribe" or "unsubscribe" in the first 5 lines or being over 40k in length, but this bounce doesn't meet any of these criteria. Any ideas why this bounces? Actually, it's *my* post, and I've tried several times with different subjects and different beginnings. I've even tried posting from another account at a different ISP. In the message forwarded below I mention posting to mac-eudora-forum@qualcomm.com to no avail. Actually, I don't remember seeing my own post being sent to me from the list, which is a Majordomo list. Maybe it also bounced to the list-owner. But why? Thanks, Dick Moores (rdm@netcom.com) ---------- Forwarded message ---------- Date: Wed, 30 Aug 1995 21:15:38 -0700 From: owner-seasigi@halcyon.com To: owner-seasigi@halcyon.com Subject: BOUNCE seasigi@halcyon.com: Admin request >From rdm@netcom.com Wed Aug 30 14:12:45 1995 Received: from netcom16.netcom.com by halcyon.com with SMTP id AA25167 (5.65c/IDA-1.4.4 for ); Wed, 30 Aug 1995 21:15:29 -0700 Received: by netcom16.netcom.com (8.6.12/Netcom) id VAA28389; Wed, 30 Aug 1995 21:12:47 -0700 Date: Wed, 30 Aug 1995 21:12:45 -0700 (PDT) From: Dick Moores X-Sender: rdm@netcom16 To: SEASIGI Subject: Help with Japanese version of Eudora for Mac (fwd) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Friends of mine in Japan have just got on the net and are eager to figure things out. They have a Mac, and Eudora-J1.3.8.3 (Japanese version). I'm guessing that except for the Japanese capability, this version corresponds closely to some English freeware version. Can anyone on this list help me answer their questions? I have a PC, and though I have used Eudora 1.4? some months ago, I'm not using it now. One specific question: As a test I sent them an ASCII file as an attachment using pine. I seem to recall that this should be no problem for Eudora, but they don't know what to do to read the file. How to do this? To no avail, I've already posted to mac-eudora-forum@qualcomm.com (a majordomo list) and checked a Eudora manual at http://cutl.city.unisa.edu.au/eudora/contents.html Thanks, Dick Moores From majordomo-users-owner Fri Sep 1 18:00:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id RAA28947 for majordomo-users-outgoing; Fri, 1 Sep 1995 17:47:48 -0700 Received: from basis.basis.com (basis.basis.com [204.52.207.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id RAA28934 for ; Fri, 1 Sep 1995 17:47:42 -0700 Received: (from mail@localhost) by basis.basis.com (8.6.9/8.6.9) id SAA15501 for ; Fri, 1 Sep 1995 18:43:35 -0600 Received: from bbx.basis.com(204.134.1.133) by basis.basis.com via smap (V1.3) id sma015497; Fri Sep 1 18:42:44 1995 Received: from dino.basis.com (dino.basis.com [204.134.1.140]) by bbx.basis.com (8.6.9/8.6.9) with SMTP id AAA29414 for ; Sat, 2 Sep 1995 00:46:19 GMT Received: by dino.basis.com (5.65/1.2-eef) id AA17750; Fri, 1 Sep 95 18:44:03 -0600 From: David Lewis Message-Id: <9509020044.AA17750@dino.basis.com> Subject: Re: Why does this bounce? To: majordomo-users@greatcircle.com Date: Fri, 1 Sep 1995 18:44:02 -0600 (MDT) X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 471 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > list-owner. But why? > ... > Subject: Help with Japanese version of Eudora for Mac (fwd) The subject line is the cause. It is getting bounced as an administrivia because one of the patterns in the administrivia checks in resend (around line 208, my resend has been modified) is for the following pattern: /^subject:\s*help\b/i which basically says, if the subject text begins with the word help, bounce it as administrivia. dl -- David Lewis dlewis@basis.com From majordomo-users-owner Fri Sep 1 21:00:04 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id UAA02906 for majordomo-users-outgoing; Fri, 1 Sep 1995 20:43:36 -0700 Received: from aisling.stanford.edu (aisling.Stanford.EDU [171.65.20.8]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id UAA02897 for ; Fri, 1 Sep 1995 20:43:33 -0700 Received: by aisling.stanford.edu (920330.SGI/920502.SGI) for majordomo-users@greatcircle.com id AA27127; Fri, 1 Sep 95 20:42:29 -0700 Date: Fri, 1 Sep 95 20:42:29 -0700 From: ceolas@aisling.stanford.edu (Gerard Manning) Message-Id: <9509020342.AA27127@aisling.stanford.edu> To: majordomo-users@greatcircle.com Subject: SGI sendmail update kills majordomo Cc: ceolas@aisling.stanford.edu Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In response to a recently discovered security flaw in many version of sendmail, Silicon Graphics released patches to update sendmail for Irix versions 4.x and 5.x (see CERT Advisory CA-95:08, Aug 18). I installed their update to my SGI Indigo running Irix 4.05F. All mail functions worked fine, except for majordomo. Almost any mail to majordomo caused the infamous shlock error - error mail messages with hundreds of lines repeating that a shlock file could not be opened. I tried changing the ownership of wrapper from root to majordomo (since the documentation is contradictory on that point) and was then told that majordomo should be recompiled. When I did that I ran into further problems....... so in the end I just went back to the old version of sendmail, and everything has been fine since then. I have notified SGI of the problem, but not yet got an answer, so if you are planning to upgrade sendmail on an SGI machine - keep the old version around! Gerard Manning. From majordomo-users-owner Fri Sep 1 22:00:13 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id VAA03858 for majordomo-users-outgoing; Fri, 1 Sep 1995 21:38:31 -0700 Received: from gw2.att.com (gw2.att.com [192.20.239.134]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id VAA03851 for ; Fri, 1 Sep 1995 21:38:28 -0700 Received: from ctc.ih.att.com by ig1.att.att.com id AA01355; Fri, 1 Sep 95 17:29:56 EDT Received: by ctc.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA15473; Fri, 1 Sep 95 16:30:56 CDT Received: from ihspa.ih.att.com by ctc.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA15469; Fri, 1 Sep 95 16:30:55 CDT Received: by ihspa.ih.att.com (4.1/EMS-1.1 SunOS) id AA18942; Fri, 1 Sep 95 16:30:34 CDT Date: Fri, 1 Sep 95 16:30:34 CDT Message-Id: <9509012130.AA18942@ihspa.ih.att.com> From: dkk@ctc.ih.att.com (Donna K Kroeschel) To: Majordomo-Users@GreatCircle.COM Subject: Re:email headers Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have majordomo install and things are working fine but my customers who are using the mailing list need to have the From and the From: in the mail header be the same and be the id of the person sending the mail. Does anyone know how I can configure this? Thanks Donna Kroeschel ctc!dkk 708-979-6192 IH 1C-209 From majordomo-users-owner Sat Sep 2 15:31:32 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA19772 for majordomo-users-outgoing; Sat, 2 Sep 1995 15:22:23 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA25497 for ; Fri, 1 Sep 1995 06:38:58 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA21249 for majordomo-users@greatcircle.com; Fri, 1 Sep 95 06:37:28 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA01889; Fri, 1 Sep 95 06:37:27 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA15986 for majordomo-users@greatcircle.com; Fri, 1 Sep 95 06:37:24 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA18451; Fri, 1 Sep 95 08:37:22 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA19225; Fri, 1 Sep 1995 08:37:19 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509011337.AA19225@miaow.sps.mot.com> Subject: Re: Why does this bounce? (fwd) To: csigimgr@halcyon.com (Seattle Internet Sig Mailing List Mgr.) Date: Fri, 1 Sep 1995 08:37:19 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Seattle Internet Sig Mailing List Mgr." at Aug 31, 95 08:10:52 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 654 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Seattle Internet Sig Mailing List Mgr. writes: ] > > We have the list set up to bounce posts to the list-owner for having > "subscribe" or "unsubscribe" in the first 5 lines or being over 40k in > length, but this bounce doesn't meet any of these criteria. Any ideas > why this bounces? Are you saying you've modified resend? If not, there are many more criteria that cause admin request bounces, like the word "help" in the subject of your message. > Subject: Help with Japanese version of Eudora for Mac (fwd) -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Sat Sep 2 15:32:44 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA19855 for majordomo-users-outgoing; Sat, 2 Sep 1995 15:23:18 -0700 Received: from [198.102.244.40] (pm-ppp-2.greatcircle.com [198.102.244.40]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id RAA29093; Fri, 1 Sep 1995 17:51:19 -0700 X-Sender: brent@miles.greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 1 Sep 1995 20:50:37 -0400 To: "Seattle Internet Sig Mailing List Mgr." , majordomo-users@greatcircle.com From: Brent@GreatCircle.COM (Brent Chapman) Subject: Re: Why does this bounce? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 2:16 PM 8/31/95, Seattle Internet Sig Mailing List Mgr. wrote: >We have the list set up to bounce posts to the list-owner for having >"subscribe" or "unsubscribe" in the first 5 lines or being over 40k in >length, but this bounce doesn't meet any of these criteria. Any ideas >why this bounces? Actually, it's *my* post, and I've tried several >times with different subjects and different beginnings. I've even >tried posting from another account at a different ISP. In the message >forwarded below I mention posting to mac-eudora-forum@qualcomm.com to no >avail. Actually, I don't remember seeing my own post being sent to me >from the list, which is a Majordomo list. Maybe it also bounced to the >list-owner. But why? Because the "Subject:" line starts with the word "help", which is another of the administrivia checks. -Brent >Thanks, > >Dick Moores (rdm@netcom.com) > >---------- Forwarded message ---------- >Date: Wed, 30 Aug 1995 21:15:38 -0700 >From: owner-seasigi@halcyon.com >To: owner-seasigi@halcyon.com >Subject: BOUNCE seasigi@halcyon.com: Admin request > >>From rdm@netcom.com Wed Aug 30 14:12:45 1995 >Received: from netcom16.netcom.com by halcyon.com with SMTP id AA25167 > (5.65c/IDA-1.4.4 for ); Wed, 30 Aug 1995 21:15:29 -0700 >Received: by netcom16.netcom.com (8.6.12/Netcom) > id VAA28389; Wed, 30 Aug 1995 21:12:47 -0700 >Date: Wed, 30 Aug 1995 21:12:45 -0700 (PDT) >From: Dick Moores >X-Sender: rdm@netcom16 >To: SEASIGI >Subject: Help with Japanese version of Eudora for Mac (fwd) >Message-Id: >Mime-Version: 1.0 >Content-Type: TEXT/PLAIN; charset=US-ASCII -- Brent Chapman | Great Circle Associates | For Firewalls Tutorial info: Brent@GreatCircle.COM | 1057 West Dana Street | Tutorial-Info@GreatCircle.COM +1 415 962 0841 | Mountain View, CA 94041 | http://www.greatcircle.com From majordomo-users-owner Sun Sep 3 20:31:08 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id UAA17557 for majordomo-users-outgoing; Sun, 3 Sep 1995 20:16:49 -0700 Received: from ix4.ix.netcom.com (ix4.ix.netcom.com [199.182.120.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA05665 for ; Sun, 3 Sep 1995 11:22:57 -0700 Received: from LOCALNAME by ix4.ix.netcom.com (8.6.12/SMI-4.1/Netcom) id LAA21933; Sun, 3 Sep 1995 11:18:50 -0700 Date: Sun, 3 Sep 1995 11:18:50 -0700 Message-Id: <199509031818.LAA21933@ix4.ix.netcom.com> X-Sender: mcobgyn@popd.ix.netcom.com (Unverified) X-Mailer: Windows Eudora Version 1.4.5 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: mcobgyn@ix.netcom.com (Michael J. Chmielewski) Subject: Help with Sendmail and Majordomo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I was wondering if anyone has had a problem with Majordomo communicating with sendmail on AIX? Our problem is that we are not sending to all of our subscribers, some foreign, some domestic, and all of America Online. Any assistance would be appreciated. Michael Chmielewski \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ Michael J. Chmielewski, M.D. List-Owner, GYN-DOCS{an e-mail discussion list for Gynecologists} 6150 Gibbon Building 111 South 11th Street Philadelphia, PA 19107 215- 955- 6060 ///////////////////////////////////////////////////////////////// From majordomo-users-owner Sun Sep 3 20:32:51 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id UAA17571 for majordomo-users-outgoing; Sun, 3 Sep 1995 20:17:06 -0700 Received: from bnr.ca (x400gate.bnr.ca [192.58.194.73]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id QAA12598 for ; Sun, 3 Sep 1995 16:48:01 -0700 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Sun, 3 Sep 1995 19:46:30 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Sun, 3 Sep 1995 19:46:24 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Sun, 3 Sep 1995 19:46:00 -0400 Date: Sun, 3 Sep 1995 19:46:00 -0400 X400-Originator: /dd.id=1579393/g=marc/i=pm/s=jourdeuil/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.229:03.08.95.23.46.24] X400-Content-Type: P2-1984 (2) Content-Identifier: installing ma... From: "marc (p.m.) jourdeuil" Message-ID: <"231 Sun Sep 3 19:46:26 1995"@bnr.ca> To: Majordomo-Users@greatcircle.com Subject: installing majordomo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm trying to get majordomo installed. One of the tests to run is echo help | /usr/lib/sendmail -v majordomo which should execute the majordomo wrapper via the majordomo alias defined in /etc/alias. There seems to be a sendmail problem, because it doesn't seem to recognize the alias. It says user unknown, and passes the message to root. This unix userid is local to the workstation Majordomo is installed on, not a NIS account. Also, we access the internet via proxy servers. I'm not sure how majordomo would know to execute itself on the correct workstation. Our internet email addresses are in the following format: unixuserid@bnr.ca eg marcj@bnr.ca I've included configuration files at the bottom. Any help you can provide would be greatly appreciated. TIA, Marc marcj@bnr.ca Machine : HP 712/60 OS : HP-UX 9.05 perl : 4.036 majordomo : 1.93 sendmail : 5.65? Note: Upgrading sendmail is not an option, as we are a large company, and another group repackages the vendor os for everyone. =================================================================== bcarheea-88> echo help | /usr/lib/sendmail -v majordomo majordomo... User unknown Bus error (core dumped) bcarheea-89> echo help | /usr/lib/sendmail -v majordom majordom... Connecting to local host (local)... majordom... Executing "/bin/rmail -d majordom" majordom... Sent bcarheea-76> mail >From root@bcarheea Sun Sep 3 17:59 EDT 1995 Received: by bcarheea (1.37.109.11/16.2) id AA087555567; Sun, 3 Sep 1995 17:59:27 -0400 Date: Sun, 3 Sep 1995 17:59:27 -0400 From: root@bcarheea Return-Path: Message-Id: <199509032159.AA087555567@bcarheea> Apparently-To: majordom@bcarheea help ? I then copied /etc/aliases to /usr/lib/aliases bcarheea-101> newaliases /usr/lib/aliases: 15 aliases, longest 114 bytes, 664 bytes total Cannot open /usr/lib/rev-aliases: No such file or directory bcarheea-104> echo help | /usr/lib/sendmail -v majordomo majordomo... User unknown owner-majordomo... User unknown root... Connecting to local host (local)... root... Executing "/bin/rmail -d root" root... Sent MAILER-DAEMON... User unknown Postmaster... User unknown MAILER-DAEMON... User unknown =================================================================== /usr/local/majordomo/majordomo.cf =================================================================== # $whereami -- What machine am I running on? $whereami = "bcarheea.bnr.ca"; # $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 = "/usr/local/majordomo"; } # $listdir -- Where are the mailing lists? $listdir = "/usr/local/majordomo/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/majordomo/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. This should be defined as # a series of root anchored directory paths as will be used as prefixes # to the file names specified to the archive2.pl script. @archive_dirs = ( "/spool/archive/bblisa", "/usr/spool/archive/firewalls" ); # Set this to 1 if you want to use the experimental mechanism for allowing # / in user names. People with lots of X.400 addresses on their lists or # HP mail whatever may want to set this. However use it at your own risk. $analyze_slash_in_address = 0; # # these tune the experimental matching that is done for addresses with / in # them. If you haven't turned on the experimental analyze_slash_in_address # they are ignored. See the source for full explanation of these variables. # # if set to 1 ignore the requirement that addresses have an @ sign in the # address component after the last /. $no_x400at=0; # if set to 1 do not look for "/c=" and "/ad=" or "/am=" in the address. # X.400 seems to require these components. $no_true_x400=0; 1; # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1.2.2 1995/01/07 17:35:03 rouilj Exp $ =================================================================== /etc/aliases =================================================================== # # Majordomo # majordomo: "|/usr/local/majordomo/wrapper majordomo" majordom:owner-majordomo majordomo-owner: marcj owner-majordomo: marcj # # Sample mailing list # sedtest: "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l sedtest -f Sample-Owner -h bnr.ca -s sedtest-outgoing" owner-sedtest: sedtest-owner sedtest-outgoing: :include:/usr/local/majordomo/lists/sedtest, sedtest-archive owner-sedtest-outgoing: sedtest-owner sedtest-archive: /usr/local/majordomo/archive/sedtest owner-sedtest-archive: sedtest-owner sedtest-request: "|/usr/local/majordomo/wrapper request-answer sedtest" owner-sedtest-request: sedtest-owner sedtest-approval: marcj sedtest-owner: marcj owner-sedtest-owner: marcj =================================================================== /bnr/tools/3rdparty/majordomo-1.93/Makefile =================================================================== # $Source: /sources/cvsrepos/majordomo/Makefile,v $ # $Revision: 1.21.2.2.2.8 $ # $Date: 1995/01/07 18:06:48 $ # $Author: rouilj $ # $State: Exp $ # # $Header: /sources/cvsrepos/majordomo/Makefile,v 1.21.2.2.2.8 1995/01/07 18:06:48 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=/bnr/3rdparty/majordomo-1.93 W_BIN=/usr/local/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 # Use these settings for BSD-based systems, including SunOS 4.x. If you're # using a POSIX-compliant system (including SysV and BSDI), comment these # settings out, and uncomment the POSIX settings below. #W_USER=daemon #W_GROUP=majordom #W_CHOWN=${W_USER}.${W_GROUP} #W_CHMOD=6755 #WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ # -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ # -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" # If you're using a POSIX-compliant system, uncomment this set of parameters # and comment out the BSD settings above. # # W_UID = 100 W_GID = 21 W_CHOWN=root W_CHMOD=4755 WRAPPER_FLAGS = -Aa -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} -DSETGROUP # 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 test \ $(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 Makefile $(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 VERSION=1.93 distribution: dist-clean mkdir majordomo-$(VERSION) mv * .??* majordomo-$(VERSION) || exit 0 rm -rf majordomo-$(VERSION)/CVS majordomo-$(VERSION)/*/CVS majordomo-$(VERSION)/*/*/CVS tar -cZvf majordomo-$(VERSION).tar.Z majordomo-$(VERSION) =================================================================== /usr/lib/sendmail.cf =================================================================== ############################################################ ############################################################ ##### ##### ##### SENDMAIL CONFIGURATION FILE ##### ##### ##### ############################################################ ############################################################ ##### @(#)$Revision: SRP 4.2 BNR $ # ############################################################ ############################################################ # This SENDMAIL CONFIGURATION FILE has been altered to # specifically work in the BNR CORWAN for the Ottawa site. # However, it can be easily modified such that it will work # at other BNR/NT sites. To modify this configuration file # for another site, pay specific attention to the current # configuration settings below: # - the local domain to which you connect directly for # SMTP mail ===> DLbnr.ca # - the SMTP relays for unresolved @ addresses # ===> DSsmtpgate BNR Ottawa SMTP gateway # ===> CSbnr bnr.ca BNR domain # ===> DTnt400 NT N.A. SMTP gateway # ===> CTnt nt.com NT domain # ===> DQsmtpgate # ===> CQinternet internet domain # ===> DRsmtpgate # ===> CRenvoy mci envoy400 mci400 elex at netas pde npotest # other supported mail domains # ===> DNsmtpgate # ===> CNnt.com bnr.co.uk domains found in FQHN # ===> DPfax used in X.400 translation of fax address # - Ruleset 0 (S0) contains rules to rewrite outgoing delivery # envelopes such that the correct SMTP gate for Ottawa is used. # Pay specific attention to the fact that rules presently # exist to flatten out FQHN in the domains bnr, bnr.ca, nt.com, # and bnr.co.uk. If your site supports FQHN (DNS), then the # specific FQHN rules will need to be commented out. # - note that all BNR modifications will start with a 'BNR mod begins' # comment, and end with a "BNR mod ends' comment. # ############################################################ ############################################################ ############################################################ ############################################################ ##### ##### ##### CAVEAT EMPTOR ##### ##### ##### ##### This configuration file is suitable for use on ##### ##### most HP-UX systems and can be installed, ##### ##### unmodified, as sendmail's configuration file, ##### ##### /usr/lib/sendmail.cf ##### ##### ##### ##### Modifications that reflect this host's mail ##### ##### environment may be needed. HP recommends that ##### ##### these be limited to the "Localizations" and ##### ##### "Routing Options" described below. ##### ##### ##### ##### ##### ##### HP will provide support for this configuration ##### ##### file if: ##### ##### ##### ##### * it is left unmodified; or ##### ##### ##### ##### * the only changes made are those described ##### ##### below under "Localizations" and "Routing ##### ##### Options". ##### ##### ##### ##### If other changes are made to this file, you ##### ##### are on your own. ##### ##### ##### ############################################################ ############################################################ ################################################################################ # Localizations: # ################################################################################ # # # While this configuration file can be used unmodified, it may be # # appropriate to make some or all of the following changes to this # # configuration file to incorporate local information or preferences. # # # # Detailed descriptions of sendmail.cf syntax and complete list of # # the configuration options can be found in the documentation. # # # # Use the Nameserver (option I): # # # # If this host is using the domain nameserver, the I option should # # be set. In most cases, sendmail will be able to detect whether # # the nameserver is in use and will automatically do the right # # thing. However, in some cases it will incorrectly appear to # # sendmail as though the nameserver is not being used, for example # # if the nameserver has not finished loading its data and is not yet # # responding to queries. If this host normally uses the nameserver, # # messages should be deferred when the nameserver is not running. # # # # If the I option is set, if an MX record lookup or gethostbyname() # # call fails because the nameserver is not running, sendmail will # # defer the message. # # # # If the I option is not set, if an MX record lookup fails, sendmail # # will assume that the nameserver is not being used, and that there # # are no MX records, and try to connect directly to the host. If a # # host name lookup fails, sendmail will assume that there is no # # entry for the host and return an error. # # # # By default, the I option is not set. To set it, uncomment the # # line: # # # # # OI # # # # Site Hiding (macro Y): # # # # It may be desirable to "hide" the name of a host generating SMTP # # mail, so that replies need not be directed to the particular host # # on which the message originated. This simplifies moving a user's # # mail home from one host to another, and gives the appearance of # # mail being generated by a unified organization rather than a # # collection of hosts. # # # # By default the sender of a message routed via SMTP is identified # # with the header line: # # # # From: Full Name # # # # where "host" is the canonical name of the local host (macro w). # # # # If the macro Y is defined, the value of macro Y will be appended # # instead of the local host name. The macro Y would typically be # # defined either as the name of a local mail hub, or as the local # # domain name. Although the name need not be the name of an actual # # host, this scheme requires that some host recognize the name and # # be able to route mail to the originating user. # # # # For example, to identify SMTP mail from the local host as # # originating from the domain poo.bah.edu, Y should be defined by # # replacing the line: # # # # # DY # # # # with: # # # # DYpoo.bah.edu # # # # An outgoing SMTP message from user "fred" at the host "burb" # # would have the From: header line: # # # # From: Fred User # # # # Assume that the host "porpoise.poo.bah.edu" is to accept and # # forward mail for the domain poo.bah.edu. In order for users at # # other hosts to reply to such messages, there are two things that # # must be done: # # # # 1) Replying hosts must be able to map the name poo.bah.edu to an # # internet address or MX record. # # # # 2) Some host must be prepared to recognize mail addressed to # # "user@poo.bah.edu" as local, and be able to route such mail # # appropriately. # # # # To satisfy 1), the nameserver for the domain bah.edu must have # # either an MX record for the name "poo" directing its mail to the # # host porpoise.poo.bah.edu, or an address record mapping the name # # "poo" to an internet address belonging to porpoise.poo.bah.edu. # # Do not make "poo.bah.edu" a CNAME for porpoise.poo.bah.edu, # # because in that case a recipient may canonicalize the sender # # address "user@poo.bah.edu" to "user@porpoise.poo.bah.edu", which # # defeats the purpose of site hiding. For the same reason, if a # # replying host uses /etc/hosts or NIS (formerly known as Yellow # # Pages) to do host name to address mapping, the entry for # # poo.bah.edu should be a separate line, not a host name alias. # # # # To satisfy 2), on porpoise, the name "poo.bah.edu" must be added # # to class w (see below), and there must be mail aliases for all # # users on systems with macro Y defined as above. For example: # # # # fred: fred@burb.poo.bah.edu # # # # Aliases for Local Host (class w): # # # # This configuration will automatically recognize that mail to users # # at the local host or any of its host name aliases or CNAMEs should # # be delivered locally. Other host names that you wish to recognize # # as local can be added to class w as either a simple class # # definition (Cw) or a file class (Fw). Any names added to class w # # must be canonical names. # # # # For example, by default, only the server cnode of an HP-UX cluster # # runs the sendmail daemon, and mail from the clients is sent out # # with headers indicating that it originated on the server. # # # # However, you might want the server also to accept mail addressed # # to users at the clients. You could have nameserver MX records # # directing mail for the clients to the server, and make the server # # recognize the clients' host names as local. If the clients' names # # are ick, ack, and ock in the domain urk.com, the class w could be # # augmented as follows: # # # # Cw ick.urk.com ack.urk.com ock.urk.com # # # # Message-ID Header Field # # # # Associating a unique Message-ID header line with every message can # # be useful for tracing messages through the mail system. This is # # not the default because it makes the syslog file grow 50% faster. # # If the configuration file line: # # # # # H?M?Message-Id: <$t.$i@$w> # # # # is uncommented, sendmail will generate a Message-ID header line # # for each message it routes that does not already have one. The id # # contains the date (GMT), in the form YYMMDDhhmm, the queue ID # # associated with the message on the local host, and the local host # # name. # # # # In any case, if an incoming message already has a Message-ID # # header line, sendmail will preserve this line. # # # # Postmaster Copy (option P): # # # # If this option is set to a valid address, when an undeliverable # # message is mailed back, a copy of the message header (but not the # # message body) is delivered to the PostMasterCopy address. It is # # suggested that this address be "Postmaster" since RFC 822 requires # # that there be a valid Postmaster address on all mail systems, and # # since sendmail also attempts to deliver undeliverable error return # # messages to Postmaster. # # # # Postmaster should be aliased locally to the (local or remote) # # address of the person responsible for mail system administration. # # # # To enable this feature, uncomment the line: # # # # # OPPostmaster # # # # If desired, replace "Postmaster" with the appropriate address. # # # # Dumb UUCP Hosts (class G): # # # # If your host has UUCP connections to hosts running "dumb", # # i.e. non-RFC 822 compatible, UUCP mailers, you should define the # # class G as a list of these hosts. This will cause UUCP mail to # # these hosts to be sent via the dumbuucp mailer rather than the # # normal uucp mailer. Since "dumb" mailers will not add their host # # names to the return path in the From: header field, the dumbuucp # # delivery agent deletes From: header fields from mail for such # # hosts. In most cases the mail system on the host where final # # delivery is done will be able to generate a correct return path # # from other information in the message header. # # # # For example, if your host has UUCP connections to dumb UUCP # # mailers on hosts rrgh and feh, the class G should be defined, # # on the line beginning with CG, as follows: # # # # CGrrgh feh # # # # Trusted Users (T): # # # # If other hosts login to your host to perform UUCP mail transfers, # # the login ids used by these systems must be defined as trusted # # users. The login id "uucp" is already defined as a trusted user. # # If necessary, add lines of the form: # # # # Tusername # # # # to the Trusted Users section of this file (lines beginning with T). # # # # Logging Level (option L): # # # # Logging level determines the classes of events which will be # # logged by sendmail in /usr/spool/mqueue/syslog. By default the # # log level is 10, which reports successful deliveries (and the # # mailer and host used for delivery), queue daemon startup, alias # # database rebuilds, and various errors. More detailed information # # is reported with higher log levels. In particular, log level 11 # # reports the MX host (if any) and internet address to which mail # # was delivered. Refer to the documentation for details. # # # # Note that log level also affects the information reported by # # sendmail -bv. At log level 10 and higher, sendmail also reports # # the mailer and host that would be used for addresses that are # # "deliverable." # # # # The option L is defined on the line beginning with OL. # # # # Delivery Mode (option d): # # # # The default delivery mode is "background": the user agent # # invoking sendmail will return immediately, and sendmail will route # # the mail in the background. Other options are "interactive": # # sendmail will not return control to the program invoking it until # # the mail has been routed; and "queue": sendmail will put the # # message in the mail queue and a sendmail queue process will route # # the message later. Delivery mode is defined on the line beginning # # with Od. # # # # Error Reporting Mode (option e): # # # # The default error reporting mode is "p": if sendmail detects an # # error before it finishes sending a message, error messages are # # output to stdout; if errors occur later they are mailed back. # # Other options are: "w": if the sender is logged in, any error # # messages are written to the sender's terminal, otherwise they are # # mailed back; "m": error messages are always mailed; and "q": no # # error messages. Error reporting mode is defined on the line # # beginning with Oe. # # # # Read Timeout (option r): # # # # If the program transmitting a message to sendmail hangs, or if an # # SMTP peer goes down, sendmail's read will time out after this # # interval. RFC 1123 section 5.3.2 discusses appropriate values for # # this timeout. Refer to the sendmail documentation for the syntax # # for specifying time intervals. The read timeout is defined on the # # line beginning with Or. # # # # Queue Timeout (option T): # # # # Messages in the mail queue which sendmail has been unable to # # deliver for this amount of time will be returned to the sender as # # undeliverable. Refer to the documentation for the syntax for # # specifying time intervals. Queue timeout is defined on the line # # beginning OT. # # # # Queue-Only Load Average (option x): # # # # In order to limit load on a very busy system, sendmail can be # # configured to queue up low priority messages rather than attempt # # delivery immediately if the five-minute load average is greater # # than some integer value, by default 8. This value is defined on # # the line beginning Ox. # # # # Refuse-Connections Load Average (option X): # # # # In order to limit load on a very busy system, the sendmail daemon # # can be configured not to accept SMTP connections if the five- # # minute load average is greater than some integer value, by # # default 12. This value is defined on the line beginning Ox. # # # ################################################################################ ################################################################################ # Routing Options: # ################################################################################ # # # The supported routing options are described below. Options for # # routing SMTP mail, UUCP mail, X.400 mail, and OpenMail mail are # # described. # # # # To implement any of these options, edit a copy of this file # # according to the instructions for that option. With minor # # exceptions, noted where appropriate, the options are independent # # of each other; you can implement any of them or none of them. # # # # Some of these options require that you have installed and # # configured other software not part of the ARPA/9000 product. # # # # # # Operator precedence: # # # # It is generally agreed that mixed addresses, being ambiguous, are # # abhorrent. This configuration file interprets address operators # # in the order '@', '!', '%'. # # # # Changes to this precedence are not supported! # # # # Mixed addresses are resolved as follows: # # # # Address Mailer Host User Destination # # ------- ------ ---- ---- ----------- # # user%hostA@hostB tcp hostB user%hostA@hostB user@hostA # # hostA!user@hostB tcp hostB hostA!user@hostB hostA!user # # hostA!user%hostB uucp hostA user@hostB user@hostB # # # ################################################################################ # SMTP Mail Routing: # ################################################################################ # # # By default, all mail to addresses of the form "user@host" will be # # routed to "host" using the SMTP protocol over TCP/IP. If the # # nameserver is in use, an MX record may direct sendmail to route # # mail for that host to some other host acting as a "mail exchanger" # # for the host in the recipient address. If there is no MX record # # for the host name, gethostbyname(3n) must be able to return an # # internet address for the host or else the delivery will fail. # # # # You can arrange to mail directly only to certain hosts. Mail to # # other hosts can either be rejected as an error, or be passed to a # # "relay" host for delivery. # # # # Direct SMTP connection within local domain only: # # # # This option makes sense only if your site uses internet domain # # style host names. You can define macro L as the name of the # # "local domain" and mail directly only to hosts whose canonical # # names end with that name. For example, if your local domain is # # "envy.sins.com", you might define macro L as "envy.sins.com" and # # define an SMTP relay, in which case sendmail would send directly # # to "user@porch.envy.sins.com" but relay "user@foyer.pride.sins.com". # # Alternatively, if your host is on a closed subnet, you might # # define macro L as "sins.com" and only relay mail (through a host # # with an interface on an open subnet as well as on your closed # # subnet) to domains outside sins.com . # # # # To route only to the local domain, first define macro L. For # # example, to route directly to hosts in the domain sins.com, define # # macro L, on the line beginning DL, as follows: # # # # DLsins.com # # # # Then uncomment the line in ruleset 0 following the comment: # # # # # connect to hosts in local domain # # # # Finally, comment out the line in ruleset 0 following the comment: # # # # # try to connect to any host for user@domain # # # # Direct SMTP connection to hosts in class S only: # # # # You can define a file class S of hosts to connect to directly. # # This option does not make much sense if your host runs the # # nameserver or NIS (formerly called Yellow Pages), since it # # requires that you keep a static table up to date. An internal # # hash table is generated from the file when the configuration file # # is frozen or, if no frozen configuration file is in use, when # # sendmail starts up. Therefore, if the file from which the class # # is generated changes, the configuration file should be re-frozen # # and the sendmail daemon killed and restarted. # # # # The file from which this class is defined (by default # # /etc/hosts.smtp) should contain only host names to which your host # # can connect via TCP, as the first word on each line. It would be # # appropriate for the file to include host name aliases as well as # # official host names, and to exclude hosts that do not run an SMTP # # server. # # # # The file can contain internet domain style names. The current # # HP-UX version of sendmail can match multi-token names to class # # members. # # # # To define file class S, first uncomment the line defining class S # # from /etc/hosts.smtp, following the comment: # # # # # class S defines hosts to which you connect directly for SMTP mail # # # # Then uncomment the line in ruleset 0 following the comment: # # # # # connect to hosts in class S # # # # Finally, comment out the line in ruleset 0 following the comment: # # # # # try to connect to any host for user@domain # # # # Direct SMTP connection to nobody: # # # # This option makes sense only if an SMTP relay is also defined. A # # host (for example a single user workstation) may wish to send all # # SMTP mail through a relay. To arrange this, comment out the line # # in ruleset 0 following the comment: # # # # # try to connect to any host for user@domain # # # # Note that this option is not compatible with options 1 or 2 above. # # # # SMTP relay: # # # # If you are limiting direct SMTP connections as described above, # # by default mail to hosts outside the limits will be returned with # # an error. If you can connect to another host with wider network # # connectivity than your host has, you can use that host as an SMTP # # relay. Courtesy suggests that you get permission from the # # administrator of that host before relaying mail through it. # # # # Any host name defined as a relay to be reached via SMTP must be an # # official host name; in a domain naming environment this must be a # # fully qualified domain name. The canonicalization operator $[ $] # # is not applied to relay names. # # # # To set up an SMTP relay, define the macro S, on the line beginning # # DS, as the host name (not path) of the relay host. For example, # # if you wish to relay through the host blab.bub.edu, define S as # # follows: # # # # DSblab.bub.edu # # # # Then uncomment the line in Ruleset 0 following the comment: # # # # # pass unresolved SMTP addresses to the SMTP relay # # (don't relay source routes) # # # # Note that if you are not limiting direct SMTP connections in some # # way, SMTP mail cannot be relayed. # # # ################################################################################ # UUCP Mail Routing: # ################################################################################ # # # By default, mail to addresses of the form "host!user" is routed to # # the uucp (or dumbuucp) mailer only if "host" is in the class U, # # generated from the output of uuname(1). Addresses of this form # # referring to other host names are treated as errors. # # # # The following UUCP routing options are supported: # # # # pathalias external nameserver for UUCP: # # # # You can maintain a pathalias database to provide sendmail with # # information on how to route UUCP mail to hosts to which your host # # does not have a direct UUCP connection. This routing information # # is generated by pathalias(1m). Mkuupath(1m) creates a hashed # # database from the routing information, and uupath(1m) is used to # # access the database. # # # # To make sendmail use uupath, first set up the database as # # described above. Then uncomment the three lines in Ruleset 0 # # following the comment: # # # # # try to get a path to an unresolved UUCP address # # from pathalias nameserver # # # # UUCP relay (via UUCP): # # # # If your host has a UUCP path to another host with wider UUCP # # connectivity than your host has, it may be appropriate to route # # UUCP mail to hosts to which your host cannot connect through # # this other host, which will attempt to relay messages to their # # final destination. Courtesy suggests that you get permission from # # the administrator of that host before relaying mail through it. # # # # To implement UUCP relaying via UUCP, first define the macro U, on # # the line beginning DU, as either the relay host name or the path # # to the relay host. # # # # For example, if you wish to relay through the host pzzz, via the # # path rrgh!frr!feh!pzzz , define U: # # # # DUrrgh!frr!feh!pzzz # # # # If you have a direct UUCP connection to pzzz, define U: # # # # DUpzzz # # # # After defining the UUCP relay, uncomment the three lines in # # Ruleset 0 following the comment: # # # # # pass unresolved UUCP addresses to the UUCP relay (via UUCP) # # # # UUCP relay (via SMTP): # # # # If you can mail via SMTP to the host you wish to use as a UUCP # # relay, define the macro W, on the line beginning DW, as the name # # of the UUCP relay host. # # # # Note that in this case, the macro W must be a single host name, # # not a path. Note also that the name of any host defined as a # # relay to be reached via SMTP must be an official host name; in a # # domain naming environment this must be a fully qualified domain # # name. The canonicalization operator $[ $] is not applied to relay # # names. # # # # For example, if domain names are not in use at your site, and # # if the relay host's official name is pzzz, define W: # # # # DWpzzz # # # # Then uncomment the line in Ruleset 0 following the comment: # # # # # pass unresolved UUCP addresses to the UUCP relay (via SMTP) # # # # Note that there is some risk of generating ambiguous (mixed) # # addresses in message headers using this type of relaying, if you # # are passing mail to hosts whose mail configuration is not under # # your control. This may cause some messages to be unreplyable. # # # # UUCP to X.400 gateway # # # # By default, mail from an X.400 user or gateway via UUCP may not be # # replyable. This is due to uucp interpreting the '/' in the name as # # implying a file transfer. # # # # If you are using X.400 or OpenMail on this machine, and have UUCP # # links from this machine, then apply the following changes: # # # # Uncomment the line in Ruleset 6 following the comment: # # # # # Recognize mail from uucp for x400 user on this system # # # # Uncomment the line in Ruleset 13 following the comment: # # # # # enable uucp recipient to reply to remote x400 sender # # # # and uncomment the line in Ruleset 13 following the comment: # # # # # enable uucp recipient to reply to local x400 sender # # # # This works by adding an extra host name 'hpx400' to the route back # # to this system; this name is stripped by the line in Ruleset 6. # # # # Note that this will mean that a machine called 'hpx400' will not be # # reachable from this machine via a direct UUCP connection. # # # # # ################################################################################ # X.400 Mail Routing: # ################################################################################ # # # By default, mail to X.400 style addresses will be rejected as an # # error. The following options permit routing X.400 mail to the # # X.400/9000 product running on this host or a remote host. # # # # X.400 mail via X.400/9000 delivery agent on this host: # # # # If you have installed the X.400/9000 X.400 delivery agent # # (/usr/lib/x400/x4mailer) on this host, you must enable sendmail to # # route X.400 mail to this mailer. Uncomment the line in Ruleset 0 # # following the comment: # # # # # resolve X.400 mail: local host is X.400 gateway # # # # For example, if the name of the local host is "buh", and sendmail # # is configured as described above, it would route mail to the # # address User_Joe//SomeOrg/US/TELEMAIL////HP@buh to the X.400 # # delivery agent for further routing through the X.400 network. # # # # See the X.400/9000 documentation for a complete explanation of # # X.400 style addresses. # # # # The X.400 receiving agent, also implemented by /usr/lib/x400/x4mailer, # # will be able to hand incoming messages to sendmail for further # # routing without any changes to the sendmail configuration. # # # # X.400 Relay (X.400/9000 delivery agent on a remote host): # # # # If the X.400/9000 X.400 delivery agent runs on a different host, # # for example, "farfel", sendmail on farfel must be configured to # # route X.400 mail to the X.400 delivery agent as described above. # # Sendmail on the local host would route mail addressed, for # # example, to User_Joe//SomeOrg/US/TELEMAIL////HP@farfel to farfel # # via SMTP, and sendmail on farfel would hand the mail to the X.400 # # delivery agent for routing through the X.400 network. This would # # require no change in the local host's sendmail configuration. # # # # So that users need not know which remote host is the X.400 # # gateway, sendmail can be configured to route mail to X.400 # # addresses via a designated X.400 gateway automatically. Define # # the macro X, on the line beginning DX, as the name of (not a path # # to) the X.400 gateway host. The X.400 relay must be accessible to # # this host via SMTP and must be defined as an official host name. # # # # In a domain naming environment this must be a fully qualified # # domain name. The canonicalization operator $[ $] is not applied # # to relay names. # # # # For example, if official name of the X.400 gateway is farfel, # # define the macro X as follows: # # # # DXfarfel # # # # Then uncomment the line following the comment: # # # # # resolve X.400 mail: remote host is X.400 gateway # # # # If the local host is named "buh", mail addressed to: # # # # User_Joe//SomeOrg/US/TELEMAIL////HP@buh # # # # will automatically be relayed to the X.400 delivery agent on # # farfel. # # # # See the X.400/9000 documentation for a complete explanation of # # X.400 style addresses. # # # ################################################################################ # OpenMail Routing: # ################################################################################ # # # By default, mail to OpenMail style addresses will be rejected as an # # error. The following options permit routing OpenMail and X.400 mail # # to the OpenMail product running on this host or a remote host. # # # # OpenMail to OpenMail delivery agent: # # # # If you have installed the OpenMail internal delivery agent # # /usr/openmail/bin/xport.in on this host, you must enable sendmail # # to route mail from other OpenMail systems to local OpenMail users # # via this mailer. Uncomment the line in Ruleset 0 following the # # comment: # # # # # resolve mail to OpenMail from remote OpenMail system # # # # OpenMail to X.400 delivery agent: # # # # If you have installed the OpenMail X.400 interface option # # (/usr/openmail/bin/x400.out) on this host, you must enable # # sendmail to route mail from OpenMail users to the X.400 network # # via this mailer. Uncomment the line in Ruleset 0 following the # # comment: # # # # # resolve mail to X.400 from OpenMail # # # # OpenMail delivery agent on this host: # # # # If you have installed the OpenMail delivery agent, # # /usr/openmail/bin/unix.in, on this host, you must enable sendmail # # to route mail to OpenMail users via this mailer. Uncomment the # # line in Ruleset 0 following the comment: # # # # # resolve mail to OpenMail: local host is OpenMail gateway # # # # For example, if the name of the local host is "warsh", and # # sendmail is configured as described above, it would route mail to # # the address User_Joe/SomeOrgUnit@warsh to the OpenMail delivery # # agent for routing through the OpenMail network. # # # # See the OpenMail documentation for a complete explanation of # # OpenMail style addresses. # # # # If the sendmail configuration has not been changed to pass X.400 # # messages to X.400/9000, then the above change will also cause X.400 # # messages to be passed to OpenMail. For example, the address # # User_Joe//SomeOrg/US/TELEMAIL////HP@warsh would be passed to the # # OpenMail delivery agent for further routing through the X.400 # # network. # # # # The OpenMail receiving agent will be able to hand incoming messages # # to sendmail for further routing without any changes to the # # sendmail configuration. # # # # OpenMail Relay (OpenMail delivery agent on a remote host): # # # # If the OpenMail delivery agent runs on a different host, for # # example, "tortue.ordinary.com", sendmail on tortue must be # # configured to route OpenMail mail to the OpenMail delivery agent # # as described above. Sendmail on the local host would route mail # # addressed, for example, to User_Joe/SomeOrgUnit@tortue to tortue # # via SMTP, and sendmail on tortue would hand the mail to the # # OpenMail delivery agent for further routing through the OpenMail # # or X.400 networks. This would require no change to the local # # host's sendmail configuration. # # # # So that users need not know which remote host is the OpenMail # # gateway, sendmail can be configured to route mail to OpenMail # # addresses via a designated OpenMail gateway automatically. Define # # the macro Z, on the line beginning DZ, as the name (not path) of # # the OpenMail gateway host. The OpenMail relay must be accessible # # to this host via SMTP. # # # # In a domain naming environment this must be a fully qualified # # domain name. The canonicalization operator $[ $] is not applied # # to relay names. # # # # For example, if the official host name of the OpenMail gateway is # # tortue.ordinary.com, define the macro Z as follows: # # # # DZtortue.ordinary.com # # # # Then uncomment the line following the comment: # # # # # resolve mail to OpenMail: remote host is OpenMail gateway # # # # If the local host is named "warsh", mail addressed to: # # # # User_Joe//SomeOrg/US/TELEMAIL////HP@warsh # # # # will automatically be relayed to the OpenMail delivery agent on # # tortue.ordinary.com . # # # # See the OpenMail documentation for a complete explanation of # # OpenMail style addresses. # # # ################################################################################ ############################################################ ### Localizable Options ### ############################################################ # logging level OL10 # what to do when an 8-bit message was received and the next MTA (mail # transfer agent) down the line will only allow 7-bit messages: # e => encode the message (using MIME) into a 7-bit message # r => reject the message, i.e., bounce it back to the sender # s => send the message anyway and risk data corruption OEe # defer messages to [IPC] mailers if the nameserver is not running # OI # delivery mode Odbackground # error reporting mode Oep # read timeout Or5m # queue timeout interval OT3d # load average at which low priority messages are queued rather than delivered Ox8 # load average at which daemon refuses to accept connections OX12 # checkpoint queue runs after every N successful deliveries OC10 # postmaster address which will receive headers of undeliverable messages # OPPostmaster ############################################################ ### Other Options ### ############################################################ ### ### ### HP recommends that these options not be changed. ### ### ### ############################################################ # queue directory OQ/usr/spool/mqueue # Save those UN*X From_ lines Of # location of alias files OA/usr/lib/aliases OV/usr/lib/rev-aliases # temporary file mode OF0600 # default UID Ou1 # default GID Og1 # location of help file OH/usr/lib/sendmail.hf # recognize old style as well as new style lists in headers Oo # statistics file OS/usr/lib/sendmail.st # wait up to 5 minutes for completion of alias db initialization Oa5 # queue up everything before starting transmission Os # send to me, too if in alias expansion Om # if the load average exceeds the x option limit, divide the q option # value by the difference (plus one) between the current load average and # the x option limit to find the maximum priority value (i.e. minimum # priority) of messages to send immediately. Oq10000 # value added to message priority per recipient Oy1000 # message precedence factor Oz1800 # value added to message priority per queue run OZ9000 ############################################################ ### Configuration-Specific Macro and Class Definitions ### ############################################################ # site hiding: local sender identified as user@my_site instead of user@my_host # DY # class w defines aliases for the local host # Cw # macro L defines the "local domain" to which you connect directly for SMTP mail # BNR mod begins DLbnr.ca # BNR mod ends # class S defines hosts to which you connect directly for SMTP mail # FS/etc/hosts.smtp %s # BNR mod begins # remove uuname call to avoid sendmail crashing if UUCP fileset isn't installed # class U defines known direct UUCP connections #FU|/usr/bin/uuname %s # BNR mod ends # UUCP relay for unresolved ! addresses (via UUCP) DU # UUCP relay for unresolved ! addresses (via SMTP) DW # BNR mod begins # SMTP relay for unresolved @ addresses # $S = smtpgate (an alias to one of the X.400 gateways) # CS = BNR domain # CT = NT domain # CQ = internet # CR = other mail domains # CN = domains found in fully qualified DNS hostnames DSsmtpgate CSbnr bnr.ca DTnt400 CTnt nt.com DQsmtpgate CQinternet DRsmtpgate CRenvoy mci envoy400 mci400 elex at netas pde npotest DNsmtpgate CNnt.com bnr.co.uk DPfax # BNR mod ends # X.400 relay if X.400 delivery agent is not local DX # OpenMail relay if OpenMail delivery agent is not local DZ # dumb (not RFC 822 compatible) UUCP hosts CG # BNR mod begins # pathalias external nameserver program #DP/usr/bin/uupath # BNR mod ends ############################################################ ### Configuration Version ### ############################################################ DV16.2 ############################################################ ### Required Macro Definitions ### ############################################################ # official domain name of this host for SMTP Dj$w # my name DnMAILER-DAEMON # UNIX header format DlFrom $g $d # delimiter (operator) characters Do.:%@!^=/[]| # format of a total name Dq$?x$x <$g>$|$g$. # SMTP banner De$j HP Sendmail ($v/$V) ready at $b ############################################################ ### Message Precedences ### ############################################################ Pfirst-class=0 Pspecial-delivery=100 Pjunk=-100 ############################################################ ### Trusted Users ### ############################################################ Troot Tdaemon Tuucp Tx400 ############################################################ ### Header Field Formats ### ############################################################ HReceived: $?sfrom $s $.by $w$?r with $r$. ($v/$V) id $i; $b HResent-Date: $a HDate: $a HResent-From: $q H?F?From: $q H?x?Full-Name: $x H?P?Return-Path: <$g> HSubject: # HPosted-Date: $a # HReceived-Date: $b # BNR mod begins HResent-Message-Id: <$t.$i@$w> H?M?Message-Id: <$t.$i@$w> # BNR mod ends ############################################################ ############################################################ ##### ##### ##### Address Rewriting Rulesets ##### ##### ##### ############################################################ ############################################################ ############################################################ ### Ruleset 1 - Sender Field Pre-rewriting ### ############################################################ S1 R$+ $:$>6$1 strip my_host and canonicalize R$*<@$+>$* $@$1<@$2>$3 already has (remote) domain R$+/$*/$*/$*/$* $:$1/$2/$3/$4/$5<@$w> @my_domain on local X.400 sender ############################################################ ### Ruleset 2 - Recipient Field Pre-rewriting ### ############################################################ S2 R$+ $:$>6$1 strip my_host and canonicalize R$*<@$+>$* $@$1<@$2>$3 already has (remote) domain R$+/$*/$*/$*/$* $:$1/$2/$3/$4/$5<@$w> @my_domain on local X.400 recpt ############################################################ ### Ruleset 3 - Address Internalization ### ############################################################ S3 # handle "From:<>" special case R<> $@$n null address => MAILER-DAEMON # basic textual canonicalization R$*<$*>$*<$*>$* $2$3<$4>$5 strip multiple <> <> R$*<$*<$+>$*>$* $1<$2$3$4>$5 strip <> from inside R$*<$+>$* $2 strip phrase and <> # BNR mod begins # this rule interferes with COCOS AT (Austria Telecom) domain #R$+ at $+ $1@$2 RFC 733 at => RFC 822 @ # BNR mod ends # source route <@a,@b,@c:user@d> syntax to internal form <@a>:@b:@c:user@d R@$+,$+ @$1:$2 change all , to : R@$+.UUCP:$+ $@<@$1.UUX>:$2 .UUCP pseudo-domain in route R@$+:$+ $@<@$1>:$2 focus on next hop # The @ delimiter takes precedence. Leave this alone. R$+@$+ $:$1<@$2> focus on domain R$+<$+@$+> $1$2<@$3> move gaze right R$+<@$+.UUCP> $@$1<@$2.UUX> .UUCP pseudo-domain R$+<@$+> $@$1<@$2> already in internal form # The ! delimiter. R$+^$+ $1!$2 convert obsolete ^ to ! R$+!$+ $@$2<@$1.UUX> host!user => user<@host.UUX> # % is a low precedence @. R$+%$+ $:$1<%$2> focus on domain R$+<$+%$+> $1$2<%$3> move gaze right R$+<%$+> $1<@$2> user%host => user@host R$+<@$+.UUCP> $@$1<@$2.UUX> .UUCP pseudo-domain # miscellaneous cleanup R$+@ $@$1 user@ => user R$+% $@$1 user% => user ############################################################ ### Ruleset 4 - Final Output Post-rewriting ### ############################################################ S4 # special cases R$+<@> $1 null domain # UUCP must always be presented as host!user R$+<@$+.UUX> $@$2!$1 user<@host.UUX> => host!user # UUCP hop in source route R<@$+.UUX>:$+ <@$1.UUCP>:$2 .UUX in source route => .UUCP R<@$+>:$+.UUX$+ <@$1>:$2.UUCP$3 .UUX in source route => .UUCP # defocus R$*<$+>$* $1$2$3 remove internal form <> # don't change %s or @s in mixed addresses R$+!$+@$+ $@$1!$2@$3 don't interpret it any further R$+!$+%$+ $@$1!$2%$3 don't interpret it any further # restore source route to external form R@$+:$+:$+ @$1,$2:$3 all but last : => , R@$+ $@<@$1> add <> to protect the ,s # should be exactly one @ in user@domain style address R$+%$+ $1@$2 all % => @ R$+@$+@$+ $1%$2@$3 all but last @ => % ############################################################# ### Ruleset 0 - {Delivery_Agent, Host, User} Resolution ### ############################################################# S0 # BNR mod begins # re-write outgoing delivery envelope recipients (RCPT TO:) # # uncomment the following line if you want ALL UUCP-style addresses to be # delivered to the first hop via SMTP R$+<@$+.UUX> $:$>3$1@$2 use SMTP for UUCP delivery R$+%$+<@$=Q> $:$>3$1@$2@$Q remove Internet domains R$+<@$=Q> $:$>3$1@$Q remove Internet domains R$+<@$=R> $:$>3$1@$2@$R replace SMTP relay alias with alias@SMTP relay R$+<@$=R.$L> $:$>3$1@$2@$R replace SMTP relay alias with alias@SMTP relay R$+.$+%$+<@$P> $:$>3/fax=$3/g=$1/s=$2/%$P@$S R$+.$+@$+<@$P> $:$>3/fax=$3/g=$1/s=$2/%$P@$S R$+<@$=S> $:$>3$1@$S username@domain => username@SMTP relay R$+<@$=T> $:$>3$1@$T username@domain => username@SMTP relay # Keep the following, such that a redefining of the local domain won't cause problems R$+<@$L> $:$>3$1@$L@$S username@domain => username%domain@SMTP relay # Remove known subdomains and domains from fully qualified DNS hostnames R$+<@$+.$+.$L> $:$1<@$2> hostname.subdomain. => hostname R$+<@$+.$L> $:$1<@$2> hostname. => hostname R$+<@$+.$+.$=N> $:$1<@$2> remove local subdomain R$+<@$+.$=N> $:$1<@$2> remove domain #BNR mod ends # recognize local host or canonicalize R$+ $:$>6$1 anything to ruleset 6 once # resolve domain-literals (numeric internet addresses) not canonicalized above R$*<@[$+]> $#tcp$@[$2]$:$1@[$2] user@internet address R<@[$+]>:$* $#tcp$@[$1]$:@[$1]:$2 internet address in source route # resolve mail to dumb UUCP hosts R$+<@$=G.UUX> $#dumbuucp$@$2$:$1 user@dumb_host.UUX # resolve mail to other known UUCP hosts R$+<@$=U.UUX> $#uucp$@$2$:$1 user@host.UUX R<@$=U.UUX>:$+ $#uucp$@$1$:$2 @host.UUX in source route # try to get a path to an unresolved UUCP address from pathalias nameserver # R$+<@$-.UUX> $:$>5$2!$1 uupath pathalias routing # R$+<@$=G.UUX> $#dumbuucp$@$2$:$1 to dumb UUCP host # R$+<@$=U.UUX> $#uucp$@$2$:$1 to other known UUCP host # pass unresolved UUCP addresses to the UUCP relay (via SMTP) # R$+<@$+.UUX> $#tcp$@$W$:$1<@$2.UUX> to UUCP relay via SMTP # pass unresolved UUCP addresses to the UUCP relay (via UUCP) # R$+<@$+.UUX> $:$>3 $U!$2!$1 re-internalize with $U # R$+<@$=G.UUX> $#dumbuucp$@$2$:$1 to dumb UUCP relay # R$+<@$+.UUX> $#uucp$@$2$:$1 to UUCP relay # other UUCP addresses are in error R$*<@$+.UUX>$* $#error$:unable to route to UUCP host name $2 # select hosts to connect with directly for SMTP mail: # connect to hosts in class S # R$+<@$=S> $#tcp$@$2$:$1<@$2> user@domain # BNR mod begins # connect to hosts in local domain R$+<@$+.$L> $#tcp$@$2.$L$:$1<@$2.$L> user@host.localdomain # BNR mod ends # BNR mod begins # try to connect to any host for user@domain #R$+<@$+> $#tcp$@$2$:$1<@$2> user@domain # BNR mod ends # try to connect to any host for source route R<@$+>:$+ $#tcp$@$1$:<@$1>:$2 source route # BNR mod begins # pass unresolved SMTP addresses to the SMTP relay (don't relay source routes) #R$+<@$+> $#tcp$@$S$:$1<@$2> user@domain to SMTP relay R$+<@$-.$+> $#tcp$@$S$:$1<@$2.$3> user@internet_domain to SMTP relay # try to connect to any host for user@domain R$+<@$+> $#tcp$@$2$:$1<@$2> user@domain # BNR mod ends # other SMTP addresses are in error R$*<@$+>$* $#error$:unable to route to domain $2 # resolve X.400 mail: local host is X.400 gateway # X.400 keyword addressing: # R/$+=$+/ $#x400$@$w$:/$1=$2/ # X.400 ordered addressing: # R$+/$*/$*/$*/$* $#x400$@$w$:$1/$2/$3/$4/$5 # resolve X.400 mail: remote host is X.400 gateway # X.400 keyword addressing: # R/$+=$+/ $#tcp$@$X$:/$1=$2/<@$X> # X.400 ordered addressing: # R$+/$*/$*/$*/$* $#tcp$@$X$:$1/$2/$3/$4/$5<@$X> # resolve keyword addressing mail to OpenMail: local host is OpenMail gateway # R/$+=$* $#openmail$@$w$:/$1=$2 # resolve keyword addressing mail to OpenMail: remote host is OpenMail gateway # R/$+=$* $#tcp$@$Z$:/$1=$2<@$Z> # file names, programs, and :include: must resolve to local mailer; # explicitly distinguish these from X.400 and OpenMail syntax R/$* $#local$:/$1 to absolute file path name R|$* $#local$:|$1 to a program R:include:$* $#local$::include:$1 to :include: list # resolve mail to OpenMail: local host is OpenMail gateway # R$+/$* $#openmail$@$w$:$1/$2 # R$+;$* $#openmail$@$w$:$1/$2 # resolve mail to OpenMail: remote host is OpenMail gateway # R$+/$* $#tcp$@$Z$:$1/$2<@$Z> # R$+;$* $#tcp$@$Z$:$1/$2<@$Z> # by default, reject X.400 address as error R$+/$*/$*/$*/$* $#error$:X\.400 delivery agent not configured # by default, reject OpenMail address as error R$+/$* $#error$:OpenMail delivery agent not configured # resolve mail to OpenMail from remote OpenMail system # Ropenmail $#omxport$@$w$:openmail # resolve mail to X.400 from OpenMail # Ropenmailx4 $#omx400$@$w$:openmailx4 # other addresses must resolve to local mailer in order for mail to Full.Name, # command line aliases, and quoted user names (\user) to be delivered. # remaining names must be local R$+ $#local$:$1 name ############################################################ ############################################################ ##### ##### ##### Special Rulesets ##### ##### ##### ############################################################ ############################################################ ############################################################ ### Ruleset 5 - Pathalias Nameserver ### ############################################################ S5 R$+ $:$3$1 re-internalize ############################################################ ### Ruleset 6 - Local Host Recognition ### ############################################################ S6 # RFC 822 does not permit hostnames to end in . R$*<@$*.>$* $1<@$2>$3 strip trailing . # strip local host R$+<@$w> $>3$1 strip my_host and re-internalize R<@$w>:$+ $>3$1 strip my_host and re-internalize # recognize local host in UUCP syntax R$+<@$k.UUX> $:$1<@$w> my_host in UUCP syntax # Recognize mail from uucp for x400 user on this system # R$+<@hpx400.UUX> $:$1<@$w> X.400 in UUCP syntax R<@$k.UUX>:$+ $:<@$w>:$1 my_host.UUCP in source route R$*<@$+.UUX>$* $@$1<@$2.UUX>$3 don't canonicalize host.UUX # canonicalize host and possibly recurse R$*<@$+>$* $:$1<@$[$2$]>$3 user@host or source route R$*<@$=w>$* $:$>6$1<@$w>$3 recurse if still to my_host ############################################################ ############################################################ ##### ##### ##### Mailer (Delivery Agent) Definitions ##### ##### ##### ############################################################ ############################################################ ############################################################ ### local and program mailers ### ############################################################ Mlocal, P=/bin/rmail, F=DFMPlms, S=10, R=20, A=rmail -d $u Mprog, P=/bin/sh, F=DFMPlshu, S=10, R=20, A=sh -c $u S10 R$*<@$+.UUX> $@$1<@$2.UUX> don't modify UUCP address R$*<@$+>$* $@$1<@$2>$3 already has domain R$+ $:$1<@$w> add local domain to user S20 R$*<@$+.UUX> $@$1<@$2.UUX> don't modify UUCP address R$*<@$+>$* $@$1<@$2>$3 already has domain R$+ $:$1<@$w> add local domain to user ############################################################ ### SMTP TCP/IP mailer ### ############################################################ Mtcp, P=[IPC], F=CDFMXmu, S=11, R=21, E=\r\n, A=IPC $h S11 R$*<@$+.UUX> $@$2!$1<@$w> add local domain to UUCP address R<@$+>:$* $@<@$w>:@$1:$2 add local domain to source route R$+<@$+> $@$1<@$2> already has domain R$+ $:$1<@$?Y$Y$|$w$.> add local domain S21 R$*<@$+>$* $@$1<@$2>$3 already has domain R$+ $:$1<@$w> add local domain ############################################################ ### UUCP mailer ### ############################################################ Muucp, P=/usr/bin/uux, F=DFMUshu, S=13, R=23, A=uux - $h!rmail ($u) S13 R$+<@$+.UUX> $@$2!$1<@$k.UUX> host!user => my_host!host!user R$+@$+<@$+> $1%$2<@$3> all but last @ => % # enable uucp recipient to reply to remote x400 sender # R$*/$*<@$+> $@hpx400!$1/$2%$3<@$k.UUX> user@host => my_host!hpx400!user%host R$+<@$+> $@$1%$2<@$k.UUX> user@host => my_host!user%host R<@$+>:$+ $@<@$k.UUCP>:@$1:$2 prepend @my_host.UUCP to route # enable uucp recipient to reply to local x400 sender # R$*/$* $@hpx400!$1/$2<@$k.UUX> user => my_host!hpx400!user R$+ $@$1<@$k.UUX> user => my_host!user S23 ############################################################ ### Dumb UUCP mailer ### ############################################################ ### UUCP for hosts running non-RFC 822 mailers ### ############################################################ Mdumbuucp, P=/usr/bin/uux, F=DMUshux, R=23, A=uux - $h!rmail ($u) ############################################################ ### X.400 mailer ### ############################################################ Mx400, P=/usr/lib/x400/x4mailer, F=CDMFmn, S=14, R=24, A=x4mailer -f $g $u S14 S24 ############################################################ ### OpenMail mailers ### ############################################################ Mopenmail, P=/usr/openmail/bin/unix.in, F=DFLMXmnu, S=15, R=25, A=unix.in S15 S25 Momxport, P=/usr/openmail/bin/xport.in, F=LMn, A=xport.in $u Momx400, P=/usr/openmail/bin/x400.out, F=LMn, A=x400.out $u From majordomo-users-owner Mon Sep 4 19:02:24 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA14130 for majordomo-users-outgoing; Mon, 4 Sep 1995 18:59:48 -0700 Received: from bnr.ca (x400gate.bnr.ca [192.58.194.73]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id SAA14123 for ; Mon, 4 Sep 1995 18:59:44 -0700 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Mon, 4 Sep 1995 21:57:58 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Mon, 4 Sep 1995 21:57:52 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Sat, 2 Sep 1995 21:57:00 -0400 Date: Mon, 4 Sep 1995 21:57:00 -0400 X400-Originator: /dd.id=1579393/g=marc/i=pm/s=jourdeuil/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.044:05.08.95.01.57.52] X400-Content-Type: P2-1984 (2) Content-Identifier: installing ma... From: "marc (p.m.) jourdeuil" Message-ID: <"16045 Mon Sep 4 21:57:53 1995"@bnr.ca> To: Majordomo-Users@greatcircle.com, zot@crl.com Subject: installing majordomo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Trying to test majordomo produces the following results. Anyone seen this? No mail gets sent anywhere. I have checked all the FAQs. Machine : HP 712/60 OS : HP-UX 9.05 perl : 4.036 majordomo : 1.93 sendmail : 5.65? Thanks, Marc marcj@bnr.ca bcarheea-162> echo help | /usr/lib/sendmail -v majordomo majordomo... aliased to "|/usr/local/majordomo/wrapper majordomo" "|/usr/local/majordomo/wrapper majordomo"... Connecting to local host (prog)... "|/usr/local/majordomo/wrapper majordomo"... Executing "/bin/sh -c /usr/local/majordomo/wrapper majordomo" shlock: open("/usr/local/majordomo/L.Log"): No such file or directory at /usr/local/majordomo/shlock.pl line 90. do_exec_sendmail, number of args <= 1 unsafe to exec do_exec_sendmail, number of args <= 1 unsafe to exec do_exec_sendmail, number of args <= 1 unsafe to exec ... Can't fork at /usr/local/majordomo/majordomo.pl line 288, line 1. ABORT do_exec_sendmail, number of args <= 1 unsafe to exec at /usr/local/majordomo/majordomo.pl line 209, line 1. ABORT do_exec_sendmail, number of args <= 1 unsafe to exec at /usr/local/majordomo/majordomo.pl line 209, line 1. ABORT do_exec_sendmail, number of args <= 1 unsafe to exec at /usr/local/majordomo/majordomo.pl line 209, line 1. ... "|/usr/local/majordomo/wrapper majordomo"... Sent From majordomo-users-owner Tue Sep 5 06:31:06 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA22871 for majordomo-users-outgoing; Tue, 5 Sep 1995 06:22:03 -0700 Received: from Nzambi.qub.ac.uk (nzambi.qub.ac.uk [143.117.14.23]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id GAA22864 for ; Tue, 5 Sep 1995 06:21:59 -0700 Received: from fujin.qub.ac.uk by Nzambi.qub.ac.uk with SMTP (PP); Tue, 5 Sep 1995 13:19:16 +0000 Received: from majella.cc.qub.ac.uk by fujin.qub.ac.uk (5.0/SMI-SVR4) id AA25373; Tue, 5 Sep 1995 14:20:49 +0100 Date: Tue, 5 Sep 1995 14:22:54 PDT From: Majella McCarron Subject: Bounced message : header too long To: majordomo-users@greatcircle.com Cc: m.mccarron@qub.ac.uk Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII content-length: 398 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk As a list owner I received a bounced message with the following subject line : Subject: BOUNCE isg@boris.qub.ac.uk: Header field too long (>1024) and later on : X-Comment: To: header was truncated; missing 46 entries. Can I modify the majordomo configuration to cope with longer header fields? If not what can I tell the senders of such messages? Majella McCarron Queen's University,Belfast From majordomo-users-owner Tue Sep 5 07:00:25 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA23226 for majordomo-users-outgoing; Tue, 5 Sep 1995 06:36:24 -0700 Received: from btmplq.god.bel.alcatel.be (gatekeeper.alcatel.be [138.203.244.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id GAA23219 for ; Tue, 5 Sep 1995 06:36:09 -0700 Received: from localhost (uucp@localhost) by btmplq.god.bel.alcatel.be (8.6.5/8.6.5) id PAA20147 for ; Tue, 5 Sep 1995 15:33:58 +0200 Received: from btep01.bec.bel.alcatel.be(138.203.48.2) by btmplq via smap (V1.3) id sma020136; Tue Sep 5 15:33:36 1995 Received: from btep11.bec (btep11 [138.203.48.77]) by btep01 (8.6.5/8.6.5) with SMTP id PAA24237; Tue, 5 Sep 1995 15:31:13 +0200 Date: Tue, 5 Sep 1995 15:31:13 +0200 From: Stefaan Onderbeke Message-Id: <199509051331.PAA24237@btep01> To: majordomo-users@GreatCircle.COM Subject: installing majordomo Cc: onderbes@btep01 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have following problem during the installation of majordomo on our network : +-------+ +-------+ | | | | | | | | +-------+ +-------+ - my WS with majordomo installed - our server (& mail server) On my WS I installed majordom in the /etc/local/majordomo directory. I updated the /etc/aliases file on my WS : majordomo: "|/usr/local/majordomo/wrapper majordomo" ... So this will start the wrapper program when a mail msg is received for user majordomo. And here I have a problem, when I send mail to : majordomo or majordomo@our-domain then the mail is received by the mail server (on which majordomo is not installed, so the wrapper program is never executed). So I suppose, the mail server must be configured in such a way that if a mail is received for user majordomo, that mail is sent to the WS on which majordomo is installed. Is there anybody out there who knows how to do this, thanks in advance, Stef From majordomo-users-owner Tue Sep 5 08:00:05 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA24798 for majordomo-users-outgoing; Tue, 5 Sep 1995 07:47:30 -0700 Received: from atlantis.eng.umd.edu (atlantis.eng.umd.edu [129.2.90.28]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id HAA24791 for ; Tue, 5 Sep 1995 07:47:24 -0700 Received: (from rsw@localhost) by atlantis.eng.umd.edu (8.7.Beta.13/8.7.Beta.13) id KAA09353; Tue, 5 Sep 1995 10:38:39 -0400 (EDT) Date: Tue, 5 Sep 1995 10:38:38 -0400 (EDT) From: "Randall S. Winchester" To: Stefaan Onderbeke cc: majordomo-users@GreatCircle.COM, btep01!onderbes@uunet.uu.net Subject: Re: installing majordomo In-Reply-To: <199509051331.PAA24237@btep01> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I maintain two aliases file for majordomo. One I call majordomo.aliases and the other minordomo.aliases. The majordomo.aliases file gets used on the actual majordomo server, while minordomo.aliases is what all the other mailservers see. A minordomo.aliases file would contain something like this; joetest-outgoing:joetest-outgoing@majordomo.glue.umd.edu joetest:joetest@majordomo.glue.umd.edu owner-joetest:owner-joetest@majordomo.glue.umd.edu joetest-owner:owner-joetest@majordomo.glue.umd.edu joetest-request:joetest-request@majordomo.glue.umd.edu joetest-approval:joetest-approval@majordomo.glue.umd.edu A majordomo.aliases file would look similar to this; joetest-outgoing: :include:/var/spool/majordomo/lists/joetest joetest: "|/var/spool/majordomo/bin/wrapper resend -p Bulk -l joetest -f owner-joetest -h Majordomo.Glue.umd.edu -s joetest-outgoing" owner-joetest: sanjour joetest-owner: owner-joetest joetest-request: "|/var/spool/majordomo/bin/wrapper request-answer joetest" joetest-approval: sanjour Randall On Tue, 5 Sep 1995, Stefaan Onderbeke wrote: > I have following problem during the installation of majordomo on our network : > > > +-------+ +-------+ > | | | | > | | | | > +-------+ +-------+ > > - my WS with majordomo installed - our server (& mail server) > > > On my WS I installed majordom in the /etc/local/majordomo directory. > I updated the /etc/aliases file on my WS : > > majordomo: "|/usr/local/majordomo/wrapper majordomo" > ... > > So this will start the wrapper program when a mail msg is received for user > majordomo. > > And here I have a problem, when I send mail to : > > majordomo or > majordomo@our-domain > > then the mail is received by the mail server (on which majordomo is not > installed, so the wrapper program is never executed). > > So I suppose, the mail server must be configured in such a way that if a mail is > received for user majordomo, that mail is sent to the WS on which majordomo is installed. > > Is there anybody out there who knows how to do this, thanks in advance, > > Stef > > From majordomo-users-owner Tue Sep 5 09:30:12 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA28527 for majordomo-users-outgoing; Tue, 5 Sep 1995 09:19:20 -0700 Received: from rs232.bb-elec.com (rs232.bb-elec.com [206.1.0.34]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA28520 for ; Tue, 5 Sep 1995 09:19:16 -0700 Received: from bill-iii.bb-elec (bill-iii.bb-elec.com [206.1.0.98]) by rs232.bb-elec.com (8.6.9/8.6.9) with SMTP id LAA15861; Tue, 5 Sep 1995 11:22:07 -0500 Message-Id: <199509051622.LAA15861@rs232.bb-elec.com> Comments: Authenticated sender is From: "Bill Franklin III" Organization: B&B Electronics Mfg Co To: majordomo-users@GreatCircle.COM Date: Tue, 5 Sep 1995 11:17:38 +0000 Subject: Re: installing majordomo Reply-to: bfrankln@bb-elec.com CC: btep01!onderbes@uunet.uu.net Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Date: Tue, 5 Sep 1995 15:31:13 +0200 > So I suppose, the mail server must be configured in such a way that if a mail is > received for user majordomo, that mail is sent to the WS on which majordomo is installed. > > Is there anybody out there who knows how to do this, thanks in advance, using the aliases file on the mail server.. majordomo: majordomo@workstation.domain.com plus any mailing lists you have.. basically all things you put in the workstation aliases file.. you but in the mail server pointing to the workstation.. or you could move majordomo to the mail server bill Bill Franklin III - bfrankln@bb-elec.com B&B Electronics Mfg Co PO Box 1040 Ottawa IL 61350 Phone 815-433-5100 x213 - Fax 815-434-7094 From majordomo-users-owner Tue Sep 5 09:32:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA29021 for majordomo-users-outgoing; Tue, 5 Sep 1995 09:28:16 -0700 Received: from Nzambi.qub.ac.uk (nzambi.qub.ac.uk [143.117.14.23]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA29013 for ; Tue, 5 Sep 1995 09:28:09 -0700 Received: from fujin.qub.ac.uk by Nzambi.qub.ac.uk with SMTP (PP); Tue, 5 Sep 1995 16:25:19 +0000 Received: from majella.cc.qub.ac.uk by fujin.qub.ac.uk (5.0/SMI-SVR4) id AA26902; Tue, 5 Sep 1995 17:26:52 +0100 Date: Tue, 5 Sep 1995 17:28:57 PDT From: Majella McCarron Subject: Bounces to majordomo not listowner - helllllllllp!!!!!! To: majordomo-users@greatcircle.com Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII content-length: 2813 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Please help. I'm desperate. I'm having a problem getting bounces to go to the list-owner. For some reason they go to majordomo instead. Here's the alias for one of my typical lists. This is straight out of "Managing Internet Information Services" (0'Reilly) owner-test: majella test: "|/usr/local/etc/majordomo/wrapper resend -l test -h boris.qub.ac.uk test-outgoing" test-approval: owner-test test-outgoing: :include:/usr/spool/ftp/pub/lists/test, test-archive owner-test-outgoing: owner-test test-archive: "|/usr/local/etc/majordomo/wrapper archive -f /usr/spool/ftp/pub/lists/cdnet.archive/test -m -a" owner-test-archive: owner-test test-request: :"|/usr/local/etc/majordomo/wrapper request-answer test" owner-test-request: owner-test This is straight out of "Managing Internet Information Services" (0'Reilly) Here's a typical failed message. ------------------------------------------------------------------------------------------------------------------------- >From Tue Sep 5 17:12 BST 1995 Received: from ubvmsb.cc.buffalo.edu by boris.qub.ac.uk (5.64/A/UX-3.00) id AA04562; Tue, 5 Sep 95 17:12:57 BST Received: from ubvms.cc.buffalo.edu by ubvms.cc.buffalo.edu (PMDF V4.3-9 #5889) id <01HUX04VV4HC8YAMHJ@ubvms.cc.buffalo.edu>; Tue, 05 Sep 1995 12:06:54 -0400 (EDT) Date: Tue, 05 Sep 1995 12:06:53 -0400 (EDT) From: PMDF Mail Server Subject: Undeliverable mail: local delivery failure To: majordom@boris.qub.ac.uk Message-Id: <01HUX04WWWG28YAMHJ@ubvms.cc.buffalo.edu> Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary (ID Jgo53CkoI6ED4KLDPLzJfQ)" Status: R --Boundary (ID Jgo53CkoI6ED4KLDPLzJfQ) Content-type: TEXT/PLAIN; CHARSET=US-ASCII The message could not be delivered to: Addressee: V077HNGW Reason: %MAIL-W-WRITEERR, error writing DISK$USERDISK3:[GST0.V077HNGW]MAIL.MAI;1 -RMS-E-EXT, ACP file extend failed -SYSTEM-F-EXDISKQUOTA, disk quota exceeded --Boundary (ID Jgo53CkoI6ED4KLDPLzJfQ) MIME-version: 1.0 Content-type: MESSAGE/RFC822 Received: from boris.qub.ac.uk by ubvms.cc.buffalo.edu (PMDF V4.3-9 #5889) id <01HUX04N3PK08XI1GD@ubvms.cc.buffalo.edu>; Tue, 05 Sep 1995 12:06:47 -0400 (EDT) Received: by boris.qub.ac.uk (5.64/A/UX-3.00) id AA04395; Tue, 5 Sep 95 16:56:44 BST Received: by boris.qub.ac.uk (5.64/A/UX-3.00) id AA04387; Tue, 5 Sep 95 16:56:40 BST Date: Tue, 05 Sep 1995 16:56:40 -0300 (BST) From: majella@boris.qub.ac.uk (Majella McCarron) Subject: another test - late Sender: owner-test@boris.qub.ac.uk To: test@boris.qub.ac.uk Message-id: <9509051556.AA04387@boris.qub.ac.uk> Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Precedence: bulk late test --Boundary (ID Jgo53CkoI6ED4KLDPLzJfQ)-- Please, please what is wrong ????? Majella From majordomo-users-owner Tue Sep 5 10:31:31 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA00479 for majordomo-users-outgoing; Tue, 5 Sep 1995 10:13:22 -0700 Received: from [198.102.244.42] (pb520.greatcircle.com [198.102.244.42]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA00470; Tue, 5 Sep 1995 10:13:17 -0700 X-Sender: brent@miles.greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 5 Sep 1995 10:12:26 -0800 To: Majella McCarron , majordomo-users@greatcircle.com From: Brent@GreatCircle.COM (Brent Chapman) Subject: Re: Bounced message : header too long Cc: m.mccarron@qub.ac.uk Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 2:22 PM 9/5/95, Majella McCarron wrote: >As a list owner I received a bounced message with the following subject line : > >Subject: BOUNCE isg@boris.qub.ac.uk: Header field too long (>1024) This is indeed a message from Majordomo. >and later on : > >X-Comment: To: header was truncated; missing 46 entries. But this isn't; this must have been done by somebody's mailer. >Can I modify the majordomo configuration to cope with longer header fields? Majordomo doesn't have any hard limitations on length of headers; the >1024 check is just there to catch "questionable" headers. You can "approve" such a bounced message for posting anyway (overriding the length check), or you could modify the "resend" script to change/delete the header length check. >If not >what can I tell the senders of such messages? "Don't"; lots of mailers can't handle it. That's why the check is there in Majordomo's "resend" script; Majordomo itself doesn't have any problem with long headers, but if you let such messages through, it screws up lots of other peoples mailers downstream. -Brent -- Brent Chapman | Great Circle Associates | For Firewalls Tutorial info: Brent@GreatCircle.COM | 1057 West Dana Street | Tutorial-Info@GreatCircle.COM +1 415 962 0841 | Mountain View, CA 94041 | http://www.greatcircle.com From majordomo-users-owner Tue Sep 5 11:00:02 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA01490 for majordomo-users-outgoing; Tue, 5 Sep 1995 10:54:16 -0700 Received: from relay2.cospo.osis.gov (relay2.cospo.osis.gov [198.81.186.194]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA01483 for ; Tue, 5 Sep 1995 10:54:12 -0700 From: sfn@washington.cospo.osis.gov Received: by relay2.cospo.osis.gov (4.1/SMI-4.1) id AA01829; Tue, 5 Sep 95 13:46:36 EDT Received: from washington.cospo.osis.gov(198.81.161.68) by relay2.cospo.osis.gov via smap (V1.3) id sma001827; Tue Sep 5 13:46:22 1995 Received: from UPC20.cospo.osis.gov by washington.cospo.osis.gov with SMTP (1.38.193.4/16.2) id AA15727; Tue, 5 Sep 1995 13:59:45 -0400 Date: Tue, 5 Sep 95 13:46:37 PDT Subject: Problem setting up Majordomo To: majordomo-users@GreatCircle.COM X-Mailer: Chameleon ARM_55, TCP/IP for Windows, NetManage Inc. Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am trying to set up majordomo on the following platform. HP-UX A.09.05 A 9000/750 when I send mail to majordomo, I get the following error message. Does anynone know why this would be??? Received: by washington.cospo.osis.gov (1.38.193.4/16.2) id AB15719; Tue, 5 Sep 1995 13:58:24 -0400 Date: Tue, 5 Sep 1995 13:58:22 -0400 (EDT) From: Mail Delivery Subsystem . Return-Path: Subject: Returned mail: unknown mailer error 5 To: root@washington.cospo.osis.gov ----- Transcript of session follows ----- majordomo: Exec format error 554 "|/usr/local/lib/mail/majordomo/sbin/wrapper majordomo"... unknown mailer error 5 ----- Message header follows ----- Received: by washington.cospo.osis.gov (1.38.193.4/16.2) id AA15717; Tue, 5 Sep 1995 13:58:24 -0400 Return-Path: Date: Tue, 5 Sep 1995 13:58:22 -0400 (EDT) From: Scott or Al To: majordomo@washington.cospo.osis.gov Subject: testing Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII *** Does anyone want to take a shot at this??? _____________________________________________________ |Company: Q U A L I T Y S Y S T E M S I N C. | | __ __ _____ | |Real Name: Scott Nichols / \ / \ | | |Office Phone: (703) 281-8908 | | \__ | | |Office Fax : (703) 242-0013 | | \ | | |Compuserve 71620.1434 \ __ / \__/ __|__ | |Internet sfn@qsi.com \ | |_____________________________________________________| From majordomo-users-owner Tue Sep 5 16:00:08 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA11410 for majordomo-users-outgoing; Tue, 5 Sep 1995 15:34:43 -0700 Received: from bnr.ca (x400gate.bnr.ca [192.58.194.73]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA11400 for ; Tue, 5 Sep 1995 15:34:24 -0700 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 5 Sep 1995 18:17:59 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 5 Sep 1995 16:35:24 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 5 Sep 1995 16:35:00 -0400 Date: Tue, 5 Sep 1995 16:35:00 -0400 X400-Originator: /dd.id=1579393/g=marc/i=pm/s=jourdeuil/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.256:05.08.95.20.35.24] X400-Content-Type: P2-1984 (2) Content-Identifier: Re: installin... From: "marc (p.m.) jourdeuil" Message-ID: <"22269 Tue Sep 5 16:35:39 1995"@bnr.ca> To: majordomo-users@greatcircle.com, onderbes@bec.bel.alcatel.be, rsw@eng.umd.edu, bfrankln@bb-elec.com Cc: btep01!onderbes@uunet.uu.net Subject: Re: installing majordomo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thanks to all who responded to this issue: ----------------------------------------- This unix userid is local to the workstation Majordomo is installed on, not a NIS account. Also, we access the internet via proxy servers. I'm not sure how majordomo would know to execute itself on the correct workstation. Our internet email addresses are in the following format: unixuserid@bnr.ca eg marcj@bnr.ca We have 10,000+ unix workstations at our site. We don't have a mail server - we use NIS. Also, we use our own in-house developed mail system, not unix mail. The nodename majordomo is installed on is bcarheea. Our solution may be to make the local majordom unix account a NIS account. I will specify that the userid DOES use unix mail. The MTA will be the nodename majordomo is installed on. I will also setup DNS on this node. So, when someone internally or externally sends mail to majordomo (majordomo@bnr.ca), the MTA will know to send it to bcarheea. The alias should then be used on that node. The whereami var in majordomo.cf will be set to the DNS addressing (bcarheea.bnr.ca). I haven't implemented this yet. --------------------------------------------------------------------------- Does anyone have a solution to my earlier problem: Trying to test majordomo produces the following results. Anyone seen this? No mail gets sent anywhere. I have checked all the FAQs. Machine : HP 712/60 OS : HP-UX 9.05 perl : 4.036 majordomo : 1.93 sendmail : 5.65? bcarheea-162> echo help | /usr/lib/sendmail -v majordomo majordomo... aliased to "|/usr/local/majordomo/wrapper majordomo" "|/usr/local/majordomo/wrapper majordomo"... Connecting to local host (prog)... "|/usr/local/majordomo/wrapper majordomo"... Executing "/bin/sh -c /usr/local/m\ ajordomo/wrapper majordomo" do_exec_sendmail, number of args <= 1 unsafe to exec do_exec_sendmail, number of args <= 1 unsafe to exec do_exec_sendmail, number of args <= 1 unsafe to exec ... Can't fork at /usr/local/majordomo/majordomo.pl line 288, line 1. ABORT do_exec_sendmail, number of args <= 1 unsafe to exec at /usr/local/majord omo/majordomo.pl line 209, line 1. ABORT do_exec_sendmail, number of args <= 1 unsafe to exec at /usr/local/majord\ omo/majordomo.pl line 209, line 1. ABORT do_exec_sendmail, number of args <= 1 unsafe to exec at /usr/local/majord\ omo/majordomo.pl line 209, line 1. ... "|/usr/local/majordomo/wrapper majordomo"... Sent Regards, Marc -- +----------------------------------------------------------------------+ / ''' /| / (o o) / | +---------------------------o00--(_)--00o------------------------------+ | | Marc Jourdeuil Voice: (613) 763-3332 | | | Technical Staff | | | Information Systems Analyst | | | Bell-Northern Research Fax: (613) 763-2880 | + | P.O. Box 3511, Station C | / | Ottawa, Canada K1Y 4H7 Internet: marcj@bnr.ca |/ +----------------------------------------------------------------------+ From majordomo-users-owner Tue Sep 5 23:30:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id XAA19193 for majordomo-users-outgoing; Tue, 5 Sep 1995 23:28:06 -0700 Received: from minuteman.com (minuteman.com [204.97.64.183]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id XAA19186 for ; Tue, 5 Sep 1995 23:28:03 -0700 Received: (from andy@localhost) by minuteman.com (8.6.11/8.6.9) id CAA15046; Wed, 6 Sep 1995 02:28:01 -0400 Date: Wed, 6 Sep 1995 02:27:59 -0400 (EDT) From: Andy Banks To: majordomo-users@greatcircle.com Subject: Upgraded to perl 5.001 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Well, I had a few other programs that required the use of perl 5.001 so I upgraded from 4.036. Now it seems that whenever majordomo is called upon, I get an error saying: eval of majordomo.cf failed Literal @minuteman now requires backslash at (eval 1) line 5, within string 554 "|/home/majordomo/wrapper majordomo"...unknown mailer error 29 I've played with a few things, but before I restore perl 4.036, does anyone have any other suggestions as to what I can do to fix this? TIA, __ __________________________________________________________________ Andy Banks Minuteman Press of Tysons andy@minuteman.com printing@minuteman.com http://minuteman.com/xman http://minuteman.com/mmp __________________________________________________________________ From majordomo-users-owner Wed Sep 6 01:30:01 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id BAA21063 for majordomo-users-outgoing; Wed, 6 Sep 1995 01:29:03 -0700 Received: from Nzambi.qub.ac.uk (nzambi.qub.ac.uk [143.117.14.23]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id BAA21056 for ; Wed, 6 Sep 1995 01:28:57 -0700 Received: from fujin.qub.ac.uk by Nzambi.qub.ac.uk with SMTP (PP); Wed, 6 Sep 1995 08:26:20 +0000 Received: from majella.cc.qub.ac.uk by fujin.qub.ac.uk (5.0/SMI-SVR4) id AA29860; Wed, 6 Sep 1995 09:27:48 +0100 Date: Wed, 6 Sep 1995 09:29:47 PDT From: Majella McCarron Subject: Re: Problem setting up Majordomo To: sfn@washington.cospo.osis.gov Cc: majordomo-users@GreatCircle.COM Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII content-length: 2561 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Tue, 5 Sep 95 13:46:37 PDT sfn@washington.cospo.osis.gov wrote: > From: sfn@washington.cospo.osis.gov> Date: Tue, 5 Sep 95 13:46:37 PDT > Subject: Problem setting up Majordomo > To: majordomo-users@GreatCircle.COM > > I am trying to set up majordomo on the following platform. > > HP-UX A.09.05 A 9000/750 > when I send mail to majordomo, I get the following error message. Does anynone know why > this would be??? > > Received: by washington.cospo.osis.gov > (1.38.193.4/16.2) id AB15719; Tue, 5 Sep 1995 13:58:24 -0400 > Date: Tue, 5 Sep 1995 13:58:22 -0400 (EDT) > From: Mail Delivery Subsystem . > Return-Path: > Subject: Returned mail: unknown mailer error 5 > To: root@washington.cospo.osis.gov > > ----- Transcript of session follows ----- > majordomo: Exec format error > 554 "|/usr/local/lib/mail/majordomo/sbin/wrapper majordomo"... unknown mailer error 5 > > ----- Message header follows ----- > Received: by washington.cospo.osis.gov > (1.38.193.4/16.2) id AA15717; Tue, 5 Sep 1995 13:58:24 -0400 > Return-Path: > Date: Tue, 5 Sep 1995 13:58:22 -0400 (EDT) > From: Scott or Al > To: majordomo@washington.cospo.osis.gov > Subject: testing > Message-Id: > Mime-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII > > *** Does anyone want to take a shot at this??? > > > _____________________________________________________ > |Company: Q U A L I T Y S Y S T E M S I N C. | > | __ __ _____ | > |Real Name: Scott Nichols / \ / \ | | > |Office Phone: (703) 281-8908 | | \__ | | > |Office Fax : (703) 242-0013 | | \ | | > |Compuserve 71620.1434 \ __ / \__/ __|__ | > |Internet sfn@qsi.com \ | > |_____________________________________________________| > Have you had a look at Section 2.3 in README. The last error message in that section is "unknown mailer error 5" . Three different reasons are suggested for the message. 1. The perl script is not executable (in this case majordomo] 2. The location of the perl program specified with the #! line is incorrect. (Find out where perl is held on your system) 3. The location where the wrapper looks for the perl scripts is not the location where the scripts are located. Regards Majella McCarron From majordomo-users-owner Wed Sep 6 01:32:23 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id BAA21112 for majordomo-users-outgoing; Wed, 6 Sep 1995 01:31:09 -0700 Received: from hp9000.ensi.rnrt.tn ([193.95.17.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id BAA21097 for ; Wed, 6 Sep 1995 01:30:54 -0700 From: hamida@ensi.rnrt.tn Message-Id: <199509060830.BAA21097@miles.greatcircle.com> Received: by hp9000.ensi.rnrt.tn (16.6/16.2) id AA07257; Wed, 6 Sep 95 09:30:13 +0100 Date: Wed, 6 Sep 95 09:30:13 +0100 Apparently-To: majordomo-users@greatcircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk i have installed majordomo with perl 5.001+, to solve the proleme of @ you must add an \ before any @ a+ From majordomo-users-owner Wed Sep 6 02:30:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id CAA22015 for majordomo-users-outgoing; Wed, 6 Sep 1995 02:24:41 -0700 Received: from hp9000.ensi.rnrt.tn ([193.95.17.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id CAA22007 for ; Wed, 6 Sep 1995 02:24:18 -0700 From: hamida@ensi.rnrt.tn Message-Id: <199509060924.CAA22007@miles.greatcircle.com> Received: by hp9000.ensi.rnrt.tn (16.6/16.2) id AA07421; Wed, 6 Sep 95 10:23:36 +0100 Subject: what is digest To: majordomo-users@greatcircle.com Date: Wed, 6 Sep 95 10:23:36 WAT Mailer: Elm [revision: 66.25] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk are there any one who knows what digest is shabou malek. From majordomo-users-owner Wed Sep 6 03:00:01 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id CAA22112 for majordomo-users-outgoing; Wed, 6 Sep 1995 02:35:26 -0700 Received: from mserv1.dl.ac.uk (mserv1.dl.ac.uk [148.79.160.65]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id CAA22105 for ; Wed, 6 Sep 1995 02:35:18 -0700 Received: from xserv1.dl_sun_server by mserv1.dl.ac.uk with SMTP id KAA23752 (8.6.12/5.3[ref postmaster@dl.ac.uk] for dl.ac.uk from J.F.L.Hopkinson@dl.ac.uk); Wed, 6 Sep 1995 10:33:21 +0100 Date: Wed, 6 Sep 1995 10:33:21 +0100 Message-Id: <199509060933.KAA23752@mserv1.dl.ac.uk> Received: by xserv1.dl_sun_server (4.1/SMI-4.1) id AA11293; Wed, 6 Sep 95 10:33:20 BST From: "J. Hopkinson" To: majordomo-users@GreatCircle.COM Reply-To: J.F.L.Hopkinson@dl.ac.uk Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk What do I have to do to get the @filename mechanism to work ? --Jerry >From the majordomo FAQ: ---------------------- You can use the "@filename" directive in resend to move the command-line options of resend into a file readable only by the majordomo user/group. This will make it such that you can't find out the -outgoing address by connecting to your mailer and doing an EXPN or VRFY. The "@filename" directive seems to have fallen into undocumentation for some reason. This should be fixed in future releases. ---------------------- So I tried an experimental list (jflh-1): /etc/aliases ---------------------- .. jflh-1: "|/home/majord/majordomo/wrapper resend @/home/majord/lists/jflh-1.parms" .. (etc) ---------------------- -rw-rw---- 1 majord majord 39 Sep 4 18:30 /home/majord/lists/jflh-1.parms which contains the single line: ---------------------- -l jflh-1 -h dl.ac.uk jflh-1-outgoing,nobody ---------------------- and got the error message: ---------------------- ----- The following addresses had delivery problems ----- "|/home/majord/majordomo/wrapper resend @/home/majord/lists/jflh-1.parms" (unrecoverable error) (expanded from: jflh-1@dl) ----- Transcript of session follows ----- Message delivered to mailing list jflh-1@dl resend: must specify both '-l list' and '-h host' arguments at /home/majord/majordomo-1.93/resend line 69, <_GEN_7> line 34. 554 "|/home/majord/majordomo/wrapper resend @/home/majord/lists/jflh-1.parms"... unknown mailer error 2 ----- Original message follows ----- Received: by mserv1.dl.ac.uk id SAA10737 (8.6.12/5.3[ref postmaster@dl.ac.uk] for dl.ac.uk from majord@dl.ac.uk); Tue, 5 Sep 1995 18:37:56 +0100 Date: Tue, 5 Sep 1995 18:37:56 +0100 From: Majordomo list server Precedence: first-class Message-Id: <199509051737.SAA10737@mserv1.dl.ac.uk> To: jflh-1@dl.ac.uk (etc) ---------------------- Configuration: ---------------------- majordomo: 1.93 perl: 4.036 Sun, SunOS Note: home directory /home/majord contains: lrwxrwxrwx 1 majord majord 14 Jun 5 11:27 majordomo -> majordomo-1.93 drwxrwx--x 8 majord majord 1024 May 5 18:32 majordomo-1.92 drwxr-xr-x 6 majord majord 1024 Jul 17 14:28 majordomo-1.93 (etc) ---------------------- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Jerry Hopkinson e-mail: j.hopkinson@dl.ac.uk Daresbury Laboratory Voice: (+44) 1925 603355 Warrington WA4 4AD Fax: (+44) 1925 603100 UK May 95 --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- From majordomo-users-owner Wed Sep 6 05:00:21 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id EAA23498 for majordomo-users-outgoing; Wed, 6 Sep 1995 04:43:50 -0700 Received: from j51.com (j51.com [199.224.7.51]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id EAA23491 for ; Wed, 6 Sep 1995 04:43:46 -0700 Received: from pm4.j51.com (pm4.j51.com [199.224.7.228]) by j51.com (8.6.12/8.6.9) with SMTP id LAA09494 for ; Wed, 6 Sep 1995 11:42:33 GMT Message-Id: <199509061142.LAA09494@j51.com> X-Sender: genesis@j51.com X-Mailer: Windows Eudora Version 2.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 06 Sep 1995 07:36:13 -0400 To: majordomo-users@GreatCircle.COM From: Project Genesis Subject: what is digest Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >are there any one who knows what digest is >shabou malek. A digest in majordomo is actually a separate list (called listname-digest), which collects the messages going out on listname until it has a block large enough to exceed the "maxlength" you've specified in the digest config file, which it then sends out as one message. Alternately, you can force a new digest with the mkdigest command. That's the basics. Unfortunately, I haven't found solid docs on how to set them up or what other tricks you can play. Anyone out there running one? Ken Menken From majordomo-users-owner Wed Sep 6 07:02:24 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA25001 for majordomo-users-outgoing; Wed, 6 Sep 1995 06:53:15 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA24994 for ; Wed, 6 Sep 1995 06:53:12 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA02038 for majordomo-users@greatcircle.com; Wed, 6 Sep 95 06:51:44 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA15312; Wed, 6 Sep 95 06:51:42 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA18549 for majordomo-users@greatcircle.com; Wed, 6 Sep 95 06:51:41 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA06357; Wed, 6 Sep 95 08:51:38 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA14607; Wed, 6 Sep 1995 08:51:35 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509061351.AA14607@miaow.sps.mot.com> Subject: Re: your mail To: J.F.L.Hopkinson@dl.ac.uk Date: Wed, 6 Sep 1995 08:51:35 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509060933.KAA23752@mserv1.dl.ac.uk> from "J. Hopkinson" at Sep 6, 95 10:33:21 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 807 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ J. Hopkinson writes: ] > > What do I have to do to get the @filename mechanism to work ? Works for me. > which contains the single line: > ---------------------- > -l jflh-1 -h dl.ac.uk jflh-1-outgoing,nobody > ---------------------- > > and got the error message: [...] > resend: must specify both '-l list' and '-h host' arguments at /home/majord/majordomo-1.93/resend line 69, <_GEN_7> line 34. Any chance you have a leading space in your parms file? I haven't tried it, but I know Perl's split function will create null array elements when it encounters leading delimiters and Getopts stops processing when it fails to find an element that starts with '-'. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 6 08:00:42 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA25561 for majordomo-users-outgoing; Wed, 6 Sep 1995 07:45:21 -0700 Received: from vichosp.london.on.ca (vicwc01.is.vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA25554 for ; Wed, 6 Sep 1995 07:45:15 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Wed, 06 Sep 1995 10:51:34 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 06 Sep 1995 10:47:13 -0400 From: MICHAEL KERR To: majordomo-users@greatcircle.com Subject: List Config Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The listname.config files don't seem to be working for me. I've tried actually putting a config file into the list directory, but for some reason mj deletes it. I've tried setting the config through an email to the list, and still no success. I'm obviously missing something, but what? Mike. From majordomo-users-owner Wed Sep 6 08:02:24 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA25592 for majordomo-users-outgoing; Wed, 6 Sep 1995 07:47:16 -0700 Received: from netboss1.trg.saic.com (netboss1.trg.SAIC.COM [139.121.21.13]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA25585 for ; Wed, 6 Sep 1995 07:47:14 -0700 Received: from [139.121.21.12] (macshep) by netboss1.trg.saic.com (5.x/SMI-SVR4) id AA02695; Wed, 6 Sep 1995 07:48:30 -0700 X-Sender: jeff@mail.trg.saic.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 6 Sep 1995 07:48:30 -0800 To: majordomo-users@greatcircle.com From: jeff@trg.saic.com (Jeff Shepherd) Subject: Majordomo 2.0 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is it naughty to ask when Majordomo v2.0 might be coming out? In a couple of weeks, in a couple of months, in a couple of years...? - Jeff - _______ jeff@trg.saic.com (Jeff Shepherd) Dance to Live! Cool: http://www.trg2.saic.com/~jeff/sw/ShepWeb.html From majordomo-users-owner Wed Sep 6 08:06:10 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA25648 for majordomo-users-outgoing; Wed, 6 Sep 1995 07:50:06 -0700 Received: from netboss1.trg.saic.com (netboss1.trg.SAIC.COM [139.121.21.13]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA25641 for ; Wed, 6 Sep 1995 07:50:01 -0700 Received: from [139.121.21.12] (macshep) by netboss1.trg.saic.com (5.x/SMI-SVR4) id AA02712; Wed, 6 Sep 1995 07:51:11 -0700 X-Sender: jeff@mail.trg.saic.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 6 Sep 1995 07:51:17 -0800 To: majordomo-users@greatcircle.com From: jeff@trg.saic.com (Jeff Shepherd) Subject: Receiving mail errs from Bounces list Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am finally getting enough schmutz from my mailing list to motivate me to get the Bounces list up and running. I'm not sure exactly what I expected, but I'm not sure I expected what I got. Most of the error messages I have are from people that have weird mail addresses or used the LWGate software and typed their e-mail address incorrectly. I'm getting all the bad messages still, but rather than them coming from sending out its message, I'm getting it from Bounces sending out its message. In my aliases file I currently have owner-bounces: jeff@trg.saic.com, nobody and I'm wondering if I should remove my own address and just let those all pipe into the bit bucket. Is this what I *should* have done, and just didn't catch it in the FAQ, README, and O'Reilly? Would it be bad to have owner-bounces just point to nobody? Also, I subscribed myself to bounces just so I could see the kind of messages people were receiving. At the bottom of the bounces message it says >If you need to contact a human being regarding this, send a message >to majordomo-owner@trg2.saic.com. which I find curious because all the other 'owner' e-mail addresses have owner in front (i.e. owner-majordomo@trg2.saic.com). I was good and followed the directions when establishing the list and therefore have a proper majordomo-owner alias (it points to owner-majordomo) but I thought it was an outdated format. - Jeff - .............................................................. Jeff | 619/546-6878 Tel | Science Applications Int'l Corp Shepherd | 619/546-6587 FAX | 10260 Campus Point Drive, MS/C4 | jeff@trg.saic.com | San Diego, CA 92121-1522 From majordomo-users-owner Wed Sep 6 08:30:14 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA26347 for majordomo-users-outgoing; Wed, 6 Sep 1995 08:23:23 -0700 Received: from bock.ucs.ualberta.ca (bock.ucs.ualberta.ca [129.128.5.214]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id IAA26340 for ; Wed, 6 Sep 1995 08:23:20 -0700 Received: from qm-gw.ucs.ualberta.ca by bock.ucs.ualberta.ca with SMTP (8.6.5/UA3.0.0June95) id JAA07700 for ; Wed, 6 Sep 1995 09:21:40 -0600 Message-ID: Date: 6 Sep 1995 09:22:01 U From: "Dennis Black" Subject: Re: List Config To: "majordomo users" Cc: "MICHAEL KERR" X-Mailer: Mail*Link SMTP-QM 3.0.1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Reply to: RE>List Config Michael, when you state 'setting the config through an email to the list' there lies your problem. You are posting a config command to the list, with the password. Send e-mail as follows: TO: majordomo@ config Don't forget when you e-mail up the newconfig, to put 'EOF' as the last line. -------------------------------------- Date: 9/6/95 9:10 AM To: Dennis Black From: MICHAEL KERR The listname.config files don't seem to be working for me. I've tried actually putting a config file into the list directory, but for some reason mj deletes it. I've tried setting the config through an email to the list, and still no success. I'm obviously missing something, but what? Mike. ------------------ RFC822 Header Follows ------------------ Received: by qm-gw.ucs.ualberta.ca with SMTP;6 Sep 1995 09:08:43 U Received: from relay4.UU.NET by bock.ucs.ualberta.ca with SMTP (8.6.5/UA3.0.0June95) id JAA06335 for ; Wed, 6 Sep 1995 09:03:49 -0600 Received: from miles.greatcircle.com by relay4.UU.NET with ESMTP id QQzgam00103; Wed, 6 Sep 1995 11:03:35 -0400 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA25561 for majordomo-users-outgoing; Wed, 6 Sep 1995 07:45:21 -0700 Received: from vichosp.london.on.ca (vicwc01.is.vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA25554 for ; Wed, 6 Sep 1995 07:45:15 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Wed, 06 Sep 1995 10:51:34 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 06 Sep 1995 10:47:13 -0400 From: MICHAEL KERR To: majordomo-users@greatcircle.com Subject: List Config Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk From majordomo-users-owner Wed Sep 6 09:02:24 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA26815 for majordomo-users-outgoing; Wed, 6 Sep 1995 08:50:22 -0700 Received: from vichosp.london.on.ca (vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA26808 for ; Wed, 6 Sep 1995 08:50:12 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Wed, 06 Sep 1995 11:56:26 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 06 Sep 1995 11:52:17 -0400 From: MICHAEL KERR To: majordomo-users@greatcircle.com, Dennis.Black@UAlberta.CA Subject: Re: List Config -Reply Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I worded that poorly, sorry. I did send it to majordomo@mysite before, not to the list. However, I tried it again and it still won't work. This is the error I'm getting: >>>> newconfig londonweb londonweb.admin The new config file for londonweb was NOT accepted because: Both listname.auto and listname.closed exist. Choosing closed unknown key |3968| in file londonweb.new.config at line 1 Any ideas? From majordomo-users-owner Wed Sep 6 09:30:39 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA27506 for majordomo-users-outgoing; Wed, 6 Sep 1995 09:26:21 -0700 Received: from vichosp.london.on.ca (vicwc01.is.vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA27499 for ; Wed, 6 Sep 1995 09:26:16 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Wed, 06 Sep 1995 12:32:34 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 06 Sep 1995 12:28:10 -0400 From: MICHAEL KERR To: bh@digital.net Cc: majordomo-users@GreatCircle.COM, Dennis.Black@UAlberta.CA Subject: Re: List Config -Reply -Reply Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>> Brian Hartsfield 09/05/95 11:22am >>> > > >>>> newconfig londonweb londonweb.admin > The new config file for londonweb was NOT accepted because: > Both listname.auto and listname.closed exist. Choosing closed > unknown key |3968| in file londonweb.new.config at line 1 >The error message sums it up. You have both listname.closed and l>istname.auto. Delete one of them. But that's just it...I don't have either. Mike. From majordomo-users-owner Wed Sep 6 09:32:36 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA27390 for majordomo-users-outgoing; Wed, 6 Sep 1995 09:20:16 -0700 Received: from dylan.mindspring.com (dylan.mindspring.com [204.180.128.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA27383 for ; Wed, 6 Sep 1995 09:20:11 -0700 Received: from bh.mindspring.com [168.121.33.204] by dylan.mindspring.com with ESMTP id MAA09711; Wed, 6 Sep 1995 12:18:24 -0400 Received: (from bh@localhost) by hq.stargame.org (8.6.12/8.6.9) id LAA03973; Tue, 5 Sep 1995 11:22:58 -0400 Date: Tue, 5 Sep 1995 11:22:58 -0400 (EDT) From: Brian Hartsfield Reply-To: bh@digital.net To: MICHAEL KERR cc: majordomo-users@GreatCircle.COM, Dennis.Black@UAlberta.CA Subject: Re: List Config -Reply 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 Wed, 6 Sep 1995, MICHAEL KERR wrote: > I worded that poorly, sorry. I did send it to majordomo@mysite before, > not to the list. > > However, I tried it again and it still won't work. This is the error I'm > getting: > > >>>> newconfig londonweb londonweb.admin > The new config file for londonweb was NOT accepted because: > Both listname.auto and listname.closed exist. Choosing closed > unknown key |3968| in file londonweb.new.config at line 1 The error message sums it up. You have both listname.closed and listname.auto. Delete one of them. Brian From majordomo-users-owner Wed Sep 6 09:40:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA27457 for majordomo-users-outgoing; Wed, 6 Sep 1995 09:24:44 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA27450 for ; Wed, 6 Sep 1995 09:24:39 -0700 Received: from se.cs.umb.edu by cs.umb.edu with SMTP id AA10110 (5.65c/IDA-1.4.4 for ); Wed, 6 Sep 1995 12:23:16 -0400 Message-Id: <199509061623.AA10110@cs.umb.edu> To: MICHAEL KERR Cc: majordomo-users@greatcircle.com, Dennis.Black@ualberta.ca Subject: Re: List Config -Reply In-Reply-To: Your message of "Wed, 06 Sep 1995 11:52:17 EDT." Date: Wed, 06 Sep 1995 12:23:55 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Yup. First of all remove either the listname.closed or listname.auto file. That will get rid of the warning. As to the error, you probably have a mailer being friendly and wrapping the lines for you. somewhere shomehow you have a line starting with 3968 that isn't commented or encosed in a string type of structure. The 3968 may be followed by an = sign, I don't remember if I requred a key=value syntax before designating something as a key or not. In message , MICHAEL KERR writes: >I worded that poorly, sorry. I did send it to majordomo@mysite before, >not to the list. > >However, I tried it again and it still won't work. This is the error I'm >getting: > >>>>> newconfig londonweb londonweb.admin >The new config file for londonweb was NOT accepted because: >Both listname.auto and listname.closed exist. Choosing closed >unknown key |3968| in file londonweb.new.config at line 1 > > >Any ideas? From majordomo-users-owner Wed Sep 6 10:01:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA28475 for majordomo-users-outgoing; Wed, 6 Sep 1995 09:53:30 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA28468 for ; Wed, 6 Sep 1995 09:53:26 -0700 Received: from se.cs.umb.edu by cs.umb.edu with SMTP id AA10437 (5.65c/IDA-1.4.4 for ); Wed, 6 Sep 1995 12:51:53 -0400 Message-Id: <199509061651.AA10437@cs.umb.edu> To: MICHAEL KERR Cc: bh@digital.net, majordomo-users@greatcircle.com, Dennis.Black@ualberta.ca Subject: Re: List Config -Reply -Reply In-Reply-To: Your message of "Wed, 06 Sep 1995 12:28:10 EDT." Date: Wed, 06 Sep 1995 12:52:36 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , MICHAEL KERR writes: >>>> Brian Hartsfield 09/05/95 11:22am >>> >> > >>>> newconfig londonweb londonweb.admin >> The new config file for londonweb was NOT accepted because: >> Both listname.auto and listname.closed exist. Choosing closed >> unknown key |3968| in file londonweb.new.config at line 1 > >>The error message sums it up. You have both listname.closed and >l>istname.auto. Delete one of them. > >But that's just it...I don't have either. You don't have the files: londonweb.auto or londonweb.closed ? In this case listname is a metaword not a literal word. From majordomo-users-owner Wed Sep 6 11:00:27 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA29580 for majordomo-users-outgoing; Wed, 6 Sep 1995 10:40:08 -0700 Received: from vichosp.london.on.ca (vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA29565 for ; Wed, 6 Sep 1995 10:39:51 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Wed, 06 Sep 1995 13:45:07 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 06 Sep 1995 13:40:50 -0400 From: MICHAEL KERR To: rouilj@cs.umb.edu Cc: bh@digital.net, majordomo-users@greatcircle.com, Dennis.Black@ualberta.ca Subject: Re: List Config -Reply -Reply -Reply Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Right. I don't have either londonweb.auto or londonweb.closed. Anywhere that I can tell. Mike. >>> John P. Rouillard 09/06/95 12:52pm >>> In message , MICHAEL KERR writes: >>>> Brian Hartsfield 09/05/95 11:22am >>> >> > >>>> newconfig londonweb londonweb.admin >> The new config file for londonweb was NOT accepted because: >> Both listname.auto and listname.closed exist. Choosing closed >> unknown key |3968| in file londonweb.new.config at line 1 > >>The error message sums it up. You have both listname.closed and >l>istname.auto. Delete one of them. > >But that's just it...I don't have either. You don't have the files: londonweb.auto or londonweb.closed ? In this case listname is a metaword not a literal word. From majordomo-users-owner Wed Sep 6 11:30:15 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA00539 for majordomo-users-outgoing; Wed, 6 Sep 1995 11:25:37 -0700 Received: from vichosp.london.on.ca (vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA00532 for ; Wed, 6 Sep 1995 11:25:34 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Wed, 06 Sep 1995 14:31:58 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 06 Sep 1995 14:27:33 -0400 From: MICHAEL KERR To: majordomo-users@greatcircle.com Subject: Archive problems Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Can anybody explain this one? 550 "/usr/local/etc/mail/wrapper archive2.pl -a -m -f /usr/local/etc/mail/archive/londonweb.archive"... Can't create output Receiving 9 My @archive_dirs = {"/usr/local/etc/mail/archive"} From majordomo-users-owner Wed Sep 6 12:00:05 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA01123 for majordomo-users-outgoing; Wed, 6 Sep 1995 11:58:45 -0700 Received: from vichosp.london.on.ca (vicwc01.is.vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA01116 for ; Wed, 6 Sep 1995 11:58:42 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Wed, 06 Sep 1995 15:05:05 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 06 Sep 1995 15:00:38 -0400 From: MICHAEL KERR To: david_wolfe@risc.sps.mot.com Cc: majordomo-users@greatcircle.com Subject: Re: List Config Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I just came across something interesting... When I send a request to the mailer like config, and I watch what happens on the server itself, I get two or three files popping up (depending on my timing) into my lists directory: shlock.4469 (or whatever number it uses at the time) londonweb.conf L.londonweb?????? I can't remember the filename except it started with L. Could it be a permissions problem I'm having that won't write the config? I can't imagine it being that since I can get the list to run otherwise, but stranger things have happened. Mike. From majordomo-users-owner Wed Sep 6 13:02:43 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA02226 for majordomo-users-outgoing; Wed, 6 Sep 1995 13:01:36 -0700 Received: from skinner.cs.uoregon.edu (skinner.cs.uoregon.edu [128.223.4.13]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA02217 for ; Wed, 6 Sep 1995 13:01:29 -0700 Received: from ix.cs.uoregon.edu by skinner.cs.uoregon.edu with SMTP id AA21189 (5.65/IDA-1.4.2 for majordomo-users@greatcircle.com); Wed, 6 Sep 95 12:59:56 -0700 Date: Wed, 6 Sep 1995 12:59:55 -0700 (PDT) From: chandra sekhar chitneni To: majordomo-users@greatcircle.com Subject: Hiding lists Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk 1. What I want is that "people other than in the list should not be able to view the list-name with the lists command. I went to the xxx.config file and next to the line "noadvertise" and added /.*/. It didn't work. So I added my name(loginname) /myname.*/. I kept the "advertise" as is(blank). Still the list is visible. Can somebody tell me what I am doing wrong or what is the right procedure. 2. Here is part of the reply that is comming back when there is a unknown command send to the majordomo. At the end this message, my name is listed for any problems. I am running 8.6.12. I was wondering how come my name showed up. help Retrieve this message. end Stop processing commands (useful if your mailer adds a signature). Commands should be sent in the body of an email message to "Majordomo". Commands in the "Subject:" line NOT processed. If you have any questions or problems, please contact "chandra". ----------- Thanks for any information you can give. -chandra chandra@law.uoregon.edu. From majordomo-users-owner Wed Sep 6 13:32:24 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA02384 for majordomo-users-outgoing; Wed, 6 Sep 1995 13:07:49 -0700 Received: from vichosp.london.on.ca (vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA02377 for ; Wed, 6 Sep 1995 13:07:37 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Wed, 06 Sep 1995 16:13:51 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 06 Sep 1995 16:09:24 -0400 From: MICHAEL KERR To: majordomo-users@greatcircle.com Subject: Archive fixed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Ok, my archive is now fixed! Good lord, what a day. I have a question though...I'm running 1.93 off an HP-UX box, and it only allows 14 character filenames. Will this affect any of the archives or anything because of the limited filename length? It hasn't so far, but I want to be prepared just in case. Mike. From majordomo-users-owner Wed Sep 6 14:30:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA04328 for majordomo-users-outgoing; Wed, 6 Sep 1995 14:17:14 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA04314 for ; Wed, 6 Sep 1995 14:17:10 -0700 From: wiseb@cs.rpi.edu Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA18059; Wed, 6 Sep 1995 17:15:40 -0400 (root from colossus.cs.rpi.edu) Date: Wed, 6 Sep 95 17:04:58 EDT Received: by colossus.cs.rpi.edu (4.1/2.3-RPI-CS-client) id AA16015; Wed, 6 Sep 95 17:04:58 EDT Message-Id: <9509062104.AA16015@colossus.cs.rpi.edu> Apparently-To: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk From majordomo-users-owner Wed Sep 6 14:32:24 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA04174 for majordomo-users-outgoing; Wed, 6 Sep 1995 14:10:19 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA04167 for ; Wed, 6 Sep 1995 14:10:14 -0700 From: wiseb@cs.rpi.edu Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA17669; Wed, 6 Sep 1995 17:08:43 -0400 (wiseb from colossus.cs.rpi.edu) Date: Wed, 6 Sep 95 17:08:17 EDT Received: by colossus.cs.rpi.edu (4.1/2.3-RPI-CS-client) id AA17114; Wed, 6 Sep 95 17:08:17 EDT Message-Id: <9509062108.AA17114@colossus.cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: What should HOME be for the wrapper? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I was chaning the directory structure for my archive dirs to: /home/majordom/archives by definining, in majordomo.cf, filedir="$homedir/archives"; filedir_suffix=""; However, what I discovered, is that the wrapper appears to be setting the env variable HOME=/home/majordom/bin instead of HOME=/home/majordom I can change everything in majordom since I have group access, but I cant recompile the warpper since that requires root. Should I tell my sysadmin to change it so that it is HOME=/home/majordom ?? What should the correct setting for HOME be? It doesnt need to be anchored on the bin directory does it? Bowden -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Wed Sep 6 14:33:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA04241 for majordomo-users-outgoing; Wed, 6 Sep 1995 14:13:41 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA04234 for ; Wed, 6 Sep 1995 14:13:38 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA16173 for majordomo-users@greatcircle.com; Wed, 6 Sep 95 14:12:09 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA27484; Wed, 6 Sep 95 14:12:03 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA01665 for majordomo-users@greatcircle.com; Wed, 6 Sep 95 14:11:59 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA10622; Wed, 6 Sep 95 16:11:57 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA16200; Wed, 6 Sep 1995 16:11:53 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509062111.AA16200@miaow.sps.mot.com> Subject: Re: Hiding lists To: chitneni@cs.uoregon.edu (chandra sekhar chitneni) Date: Wed, 6 Sep 1995 16:11:53 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "chandra sekhar chitneni" at Sep 6, 95 12:59:55 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 961 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ chandra sekhar chitneni writes: ] > > 1. What I want is that "people other than in the list should not be able > to view the list-name with the lists command. > > I went to the xxx.config file and next to the line "noadvertise" and > added /.*/. It didn't work. Are you subscribed to the list? List members can *always* see the list with a "lists" request. > 2. Here is part of the reply that is comming back when there is a unknown > command send to the majordomo. At the end this message, my name is > listed for any problems. I am running 8.6.12. I was wondering how come > my name showed up. [...] > Commands in the "Subject:" line NOT processed. > > If you have any questions or problems, please contact > "chandra". > ----------- Probably because you've set $whoami_owner = "chandra" in majordomo.cf. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 6 15:02:41 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA04847 for majordomo-users-outgoing; Wed, 6 Sep 1995 14:37:08 -0700 Received: from skinner.cs.uoregon.edu (skinner.cs.uoregon.edu [128.223.4.13]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA04825 for ; Wed, 6 Sep 1995 14:37:03 -0700 Received: from ix.cs.uoregon.edu by skinner.cs.uoregon.edu with SMTP id AA22498 (5.65/IDA-1.4.2 for majordomo-users@greatcircle.com); Wed, 6 Sep 95 14:35:30 -0700 Date: Wed, 6 Sep 1995 14:35:29 -0700 (PDT) From: chandra sekhar chitneni To: David Wolfe Cc: "Majordomo user's mailing list" Subject: Re: Hiding lists In-Reply-To: <9509062111.AA16200@miaow.sps.mot.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk (Help) What I want to do is that I don't want the people other than the members of the list to know about this list(Ex. If you try the lists command, it should not be listed). > > I went to the xxx.config file and next to the line "noadvertise" and > > added /.*/. It didn't work. > > Are you subscribed to the list? List members can *always* see the list > with a "lists" request. > You are right about the second question. It helped. -chandra > > If you have any questions or problems, please contact > > "chandra". > > ----------- > > Probably because you've set $whoami_owner = "chandra" in majordomo.cf. > > -- > Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 > Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 > From majordomo-users-owner Wed Sep 6 15:30:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA05474 for majordomo-users-outgoing; Wed, 6 Sep 1995 15:05:00 -0700 Received: from bnr.ca (x400gate.bnr.ca [192.58.194.73]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA05467 for ; Wed, 6 Sep 1995 15:04:55 -0700 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 6 Sep 1995 18:00:54 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 6 Sep 1995 12:39:50 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 6 Sep 1995 12:34:00 -0400 Date: Wed, 6 Sep 1995 12:34:00 -0400 X400-Originator: /dd.id=1579393/g=marc/i=pm/s=jourdeuil/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.829:06.08.95.16.39.50] X400-Content-Type: P2-1984 (2) Content-Identifier: installing ma... From: "marc (p.m.) jourdeuil" Message-ID: <"14862 Wed Sep 6 12:40:05 1995"@bnr.ca> To: Majordomo-Users@greatcircle.com Subject: installing majordomo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have archiving working, but index & get returns: >>>> index sedtest #### No files available for sedtest. >>>> get sedtest archive **** List 'sedtest' is a private list. **** Only members of the list can do a 'get'. **** You aren't a member of list 'sedtest'. >>>> I am a member of the list! majordomo.cf: $filedir = "$listdir"; $filedir_suffix = ".archive"; aliases: sedtest-archive: "|/usr/local/majordomo/wrapper archive2.pl -f /usr/local/majordomo/archive/sedtest -m -a" I'm still looking around for this one. Anyone know what the fix for this one is? Regards, Marc marcj@bnr.ca From majordomo-users-owner Wed Sep 6 15:32:24 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA05464 for majordomo-users-outgoing; Wed, 6 Sep 1995 15:03:56 -0700 Received: from bnr.ca (x400gate.bnr.ca [192.58.194.73]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA05457 for ; Wed, 6 Sep 1995 15:03:49 -0700 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 6 Sep 1995 18:00:18 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 6 Sep 1995 12:39:37 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 6 Sep 1995 12:33:00 -0400 Date: Wed, 6 Sep 1995 12:33:00 -0400 X400-Originator: /dd.id=1579393/g=marc/i=pm/s=jourdeuil/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.776:06.08.95.16.39.37] X400-Content-Type: P2-1984 (2) Content-Identifier: re:installing... From: "marc (p.m.) jourdeuil" Message-ID: <"14781 Wed Sep 6 12:39:47 1995"@bnr.ca> To: Majordomo-Users@greatcircle.com, david_wolfe@risc.sps.mot.com Subject: re:installing majordomo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have fixed this problem: bcarheea-162> echo help | /usr/lib/sendmail -v majordomo majordomo... aliased to "|/usr/local/majordomo/wrapper majordomo" "|/usr/local/majordomo/wrapper majordomo"... Connecting to local host (prog)... "|/usr/local/majordomo/wrapper majordomo"... Executing "/bin/sh -c /usr/local/majordomo/wrapper majordomo" 90. do_exec_sendmail, number of args <= 1 unsafe to exec ... Can't fork at /usr/local/majordomo/majordomo.pl line 288, line 1. ABORT do_exec_sendmail, number of args <= 1 unsafe to exec at /usr/local/majordomo/majordomo.pl line 209, line 1. ... "|/usr/local/majordomo/wrapper majordomo"... Sent WITH: The Solution to this is in majordomo.cf Change $mailer back to sendmail from /bin/mail $mailer = "/usr/lib/sendmail -f\$sender -t"; #$mailer = "/bin/mail"; Marc marcj@bnr.ca From majordomo-users-owner Wed Sep 6 17:00:29 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA06820 for majordomo-users-outgoing; Wed, 6 Sep 1995 16:36:48 -0700 Received: from mail. (mail.CDI.ORG [206.64.114.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id QAA06813 for ; Wed, 6 Sep 1995 16:36:44 -0700 Received: from novix (cdi02.CDI.ORG [206.64.114.11]) by mail. (8.6.11/8.6.9) with SMTP id TAA07091 for ; Wed, 6 Sep 1995 19:36:32 -0400 Date: Wed, 6 Sep 1995 19:36:32 -0400 Message-Id: <199509062336.TAA07091@mail.> X-Sender: aluther@mail.cdi.org X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: Adam Luther Subject: Error 127 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Help!???, I'm trying to run majordomo 1.93 on a linux system, and whenever I try to "make install" I get an Error 127 and things die. Any Ideas. TIA _ _ _ _ _ | \ | ___ ___ ___ ___ _| | _| | ___ ___ _| | ___ ___ ___ ___ | |/ . \ / . |/ . \/ . \/ . | / . |/ ._>/ ._>/ . | / . |/ . \/ ._><_-< |_\_|\___/ \_. |\___/\___/\___| \___|\___.\___.\___| \_. |\___/\___./__/ <___' <___' _ _ _ _ _ ._ _ ___ _ _ ._ _ <_> ___| |_ ___ _| | | | || ' || . \| | || ' || |<_-<| . |/ ._>/ . | `___||_|_|| _/`___||_|_||_|/__/|_|_|\___.\___| |_| From majordomo-users-owner Wed Sep 6 20:00:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id TAA09185 for majordomo-users-outgoing; Wed, 6 Sep 1995 19:36:28 -0700 Received: from byzantium.cs.berkeley.edu (byzantium.cs.Berkeley.EDU [128.32.211.129]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id TAA09178 for ; Wed, 6 Sep 1995 19:36:25 -0700 Received: (from sev@localhost) by byzantium.cs.berkeley.edu (8.6.12/8.6.9) id TAA15158; Wed, 6 Sep 1995 19:33:32 -0700 Date: Wed, 6 Sep 1995 19:33:32 -0700 (PDT) From: Silas Tomkyn Comberbache To: Majordomo-Users@GreatCircle.COM Subject: Re: installing majordomo In-Reply-To: <"14862 Wed Sep 6 12:40:05 1995"@bnr.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > **** You aren't a member of list 'sedtest'. > >>>> > > I am a member of the list! One thing to take into consideration... Some mailers (like Berkeley mail), when you are sending mail to a local machine, do not append your hostname. Other mailers (like Pine) do. So, when I subscribed to my mailing list using pine, I was subscribed as sev@byzantium.cs.berkeley.edu, but when I tried to unsubscribe using the 'mail' command, majordomo tried to unsubscribe 'sev' without the hostname, and informed me that I was not a member of the list. This may not be your problem, but it is something to be aware of (and, is there a fix?). sev sev, studly femme & amiable kook | http://byzantium.mckusick.com/~sev/ "The `loner' may be respected, but he is always resented by his colleagues, for he seems to be passing a critical judgment on them, when he may be simply making a limiting statement about himself." -- Sidney Harris From majordomo-users-owner Wed Sep 6 21:30:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id VAA10091 for majordomo-users-outgoing; Wed, 6 Sep 1995 21:16:44 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id VAA10084 for ; Wed, 6 Sep 1995 21:16:40 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA29858; Thu, 7 Sep 1995 00:15:12 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509070415.AA29858@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Where should _SUBJECTS_ go? X-Mailer: MH 6.7.1 (exmh 1.5.1) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 07 Sep 1995 00:14:46 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am trying to get my digest to work correctly. I am a little confused about how to set up the text at the beginning of the digest that goes out. I want to have it display: **Note: See the end of this digest message for how to obtain help with this mailing list. **In this issue: _SUBJECTS_ (and _SUBJECTS is filled in accordlingly) My list is called owl-list-test and the digest list is called owl-list-test-digest. Now, the majordomo config file for owl-list-test-digest has a variable called 'message_frontier'; I tried setting this to: message_fronter << END "**Note: See the end of this digest message for information on how to obtain help on using this mailing list.\n\n**In this issue:\n\n\t_SUBJECTS_\n\n" END but this clearly did not work since the \n and \t sequences didnt get translated. In addition, that entire message is inserted for each subject in the digest, which is not what I want. I want the note about getting help to appear just once, and then the subjects filled in for each message in the digest. Now here is the confusing part. The digest perl script also has a config file for each list being digestified. And there is a header file, as well, that is supposed to be prepended to the digest. But, this mechanism does not appear to work. The message was not prepended when I tried it. But, the digest was constructed, with the missing prepended message. So, which of these settings do i need? - the message_frontier in owl-list-test-digest.cf (majordomo) - HEADER=owl-list-test-diges.header (digest) - both? Bowden -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Wed Sep 6 22:00:31 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id VAA10481 for majordomo-users-outgoing; Wed, 6 Sep 1995 21:54:31 -0700 Received: from bnr.ca (x400gate.bnr.ca [192.58.194.73]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id VAA10474 for ; Wed, 6 Sep 1995 21:54:26 -0700 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Thu, 7 Sep 1995 00:51:48 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 6 Sep 1995 18:06:16 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Wed, 6 Sep 1995 18:05:00 -0400 Date: Wed, 6 Sep 1995 18:05:00 -0400 X400-Originator: /dd.id=1579393/g=marc/i=pm/s=jourdeuil/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.432:06.08.95.22.06.16] X400-Content-Type: P2-1984 (2) Content-Identifier: majordomo fix... From: "marc (p.m.) jourdeuil" Message-ID: <"8445 Wed Sep 6 18:06:18 1995"@bnr.ca> To: Majordomo-Users@greatcircle.com Subject: majordomo fixes! Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Yes! index & get work now. Get should have worked once index was fixed, but... Here are my solutions, If anyone cares (or for people who have some problems like me!) To get index to work: majordomo.cf #$filedir = "$listdir"; $filedir = "/usr/local/majordomo/archive"; #$filedir_suffix = ".archive"; $filedir_suffix = ""; @archive_dirs = ( "/usr/local/majordomo/archive", "/usr/local/majordomo/archive/sedtest" ); /usr/lib/aliases: sedtest-archive: "|/usr/local/majordomo/wrapper archive2.pl -f /usr/local/majordomo/archive/sedtest/sedtest -m -a" Archive dir for sedtest: /usr/local/majordomo/archive/sedtest bcarheea-238> ll total 10 -rw-rw-rw- 1 majordom majordom 1520 Sep 5 22:29 sedtest -rw-rw-rw- 1 majordom majordom 2470 Sep 6 16:32 sedtest.9509 To get "get" to work lists/sedtest.config # private_get [bool] (yes) # If set to yes, then the requestor must be on the mailing list in # order to get files. #private_get = yes private_get = no Marc From majordomo-users-owner Thu Sep 7 02:30:06 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id CAA13544 for majordomo-users-outgoing; Thu, 7 Sep 1995 02:21:12 -0700 Received: from mserv1.dl.ac.uk (mserv1.dl.ac.uk [148.79.160.65]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id CAA13536 for ; Thu, 7 Sep 1995 02:21:00 -0700 Received: from xserv1.dl_sun_server by mserv1.dl.ac.uk with SMTP id KAA02557 (8.6.12/5.3[ref postmaster@dl.ac.uk] for dl.ac.uk from J.F.L.Hopkinson@dl.ac.uk); Thu, 7 Sep 1995 10:19:08 +0100 Date: Thu, 7 Sep 1995 10:19:08 +0100 Message-Id: <199509070919.KAA02557@mserv1.dl.ac.uk> Received: by xserv1.dl_sun_server (4.1/SMI-4.1) id AA25555; Thu, 7 Sep 95 10:19:02 BST From: "J. Hopkinson" To: david_wolfe@risc.sps.mot.com Cc: majordomo-users@greatcircle.com In-Reply-To: <9509061351.AA14607@miaow.sps.mot.com> (dwolfe@risc.sps.mot.com) Subject: Re: your mail Reply-To: J.F.L.Hopkinson@dl.ac.uk Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ David Wolfe writes ] > [ J. Hopkinson writes: ] > > > What do I have to do to get the @filename mechanism to work ? > > Works for me. > > > which contains the single line: > > ---------------------- > > -l jflh-1 -h dl.ac.uk jflh-1-outgoing,nobody > > ---------------------- > > > > and got the error message: > [...] > > resend: must specify both '-l list' and '-h host' arguments at /home/majord/majordomo-1.93/resend line 69, <_GEN_7> line 34. > > Any chance you have a leading space in your parms file? I haven't tried > it, but I know Perl's split function will create null array elements > when it encounters leading delimiters and Getopts stops processing when > it fails to find an element that starts with '-'. > Ahhhhhh! Works for me now. Thanks --Jerry --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Jerry Hopkinson e-mail: j.hopkinson@dl.ac.uk Daresbury Laboratory Voice: (+44) 1925 603355 Warrington WA4 4AD Fax: (+44) 1925 603100 UK [May 95] --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- From majordomo-users-owner Thu Sep 7 03:00:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id CAA13819 for majordomo-users-outgoing; Thu, 7 Sep 1995 02:52:11 -0700 Received: from Nzambi.qub.ac.uk (nzambi.qub.ac.uk [143.117.14.23]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id CAA13812 for ; Thu, 7 Sep 1995 02:52:07 -0700 Received: from fujin.qub.ac.uk by Nzambi.qub.ac.uk with SMTP (PP); Thu, 7 Sep 1995 09:49:37 +0000 Received: from majella.cc.qub.ac.uk by fujin.qub.ac.uk (5.0/SMI-SVR4) id AA06871; Thu, 7 Sep 1995 10:51:07 +0100 Date: Thu, 7 Sep 1995 10:53:09 PDT From: Majella McCarron Subject: unknown mailer error 138 To: majordomo-users@greatcircle.com Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII content-length: 542 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm setting up majordomo 1.93 on a Solaris system. Has anyone seen mailer error 138 ----- The following addresses had delivery problems ----- "|/usr/local/majordomo/wrapper resend -l sample -h solution.unite.net sample-out going" (unrecoverable error) (expanded from: sample) ----- Transcript of session follows ----- Bus Error - core dumped 554 "|/usr/local/majordomo/wrapper resend -l sample -h solution.unite.net sample -outgoing"... unknown mailer error 138 Any ideas - a wrapper problem perhaps ??? Majella McCarron From majordomo-users-owner Thu Sep 7 11:10:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA20704 for majordomo-users-outgoing; Thu, 7 Sep 1995 10:42:36 -0700 Received: from newlink.atlanta.com (newlink.atlanta.com [155.229.17.50]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA20697 for ; Thu, 7 Sep 1995 10:42:31 -0700 Received: from apollo (admin.southlink.com [168.27.193.17]) by newlink.atlanta.com (8.6.9/8.6.9) with SMTP id NAA05798 for ; Thu, 7 Sep 1995 13:39:06 -0400 Message-Id: <199509071739.NAA05798@newlink.atlanta.com> X-Sender: larry@southlink.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 07 Sep 1995 13:41:34 -0500 To: majordomo-users@GreatCircle.COM From: Larry Morrow Subject: Re: What should HOME be for the wrapper? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Bowden At 05:08 PM 9/6/95 EDT, you wrote: >I was chaning the directory structure for my archive dirs to: > /home/majordom/archives >by definining, in majordomo.cf, > filedir="$homedir/archives"; > filedir_suffix=""; > >However, what I discovered, is that the wrapper appears to be setting >the env variable HOME=/home/majordom/bin instead of HOME=/home/majordom > >I can change everything in majordom since I have group access, but I >cant recompile the warpper since that requires root. Should I tell my >sysadmin to change it so that it is HOME=/home/majordom ?? You do not have to do that. Look below. >What should the correct setting for HOME be? It doesnt need to be >anchored on the bin directory does it? > This is a UNIX answer. If you have permissions in /home/majordom then you can create a softlink to change the directory location. execute the following command, (check for errors on my part first) ln -s /home/majordom /home/majordom/bin That will make /home/majordom/bin a link to /home/majordom. That should fix everything. Larry :-) Larry J. Morrow Director, Georgia Operations NewLink Global Engineering Corporation voice: (404) 502-8144 fax: (404) 502-9010 page: (404) 689-6029 newlink@mindspring.com From majordomo-users-owner Thu Sep 7 11:10:37 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA21089 for majordomo-users-outgoing; Thu, 7 Sep 1995 11:01:44 -0700 Received: from vichosp.london.on.ca (vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA21082 for ; Thu, 7 Sep 1995 11:01:28 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Thu, 07 Sep 1995 14:08:10 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Thu, 07 Sep 1995 14:03:44 -0400 From: MICHAEL KERR To: majordomo-users@greatcircle.com Subject: 14-char Filenames = BAD THING Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Ok guys, this may be one for the FAQ or something... If you're trying to install and run Majordomo 1.93 on a UNIX system using 14-character filenames (my particular example is on an HP-UX 9.04 system), your mailing list names may be NO LONGER than 3 characters. THREE! Can I PLEASE cry??!! Everything in the list will work (or so I can tell) except for the per-list config files. The config won't hold because of some sort of conflict in filenames due to truncation, so if you rename your lists to three characters, the configs will hold and everything will be peachy. I haven't gone into list-digest.config yet, but if there is such a file, it won't work at all. Just a public service announcement. Mike. From majordomo-users-owner Thu Sep 7 11:32:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA21988 for majordomo-users-outgoing; Thu, 7 Sep 1995 11:27:25 -0700 Received: from smuggler.bbn.com (SMUGGLER.BBN.COM [128.89.7.132]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA21980 for ; Thu, 7 Sep 1995 11:27:23 -0700 Received: from smuggler.bbn.com (LOCALHOST.BBN.COM [127.0.0.1]) by smuggler.bbn.com (8.6.9/8.6.6) with ESMTP id OAA03568 for ; Thu, 7 Sep 1995 14:25:56 -0400 Message-Id: <199509071825.OAA03568@smuggler.bbn.com> To: majordomo-users@greatcircle.com Subject: Re: 14-char Filenames = BAD THING In-reply-to: Your message of "Thu, 07 Sep 1995 14:03:44 EDT." Date: Thu, 07 Sep 1995 14:25:55 -0400 From: "John C. Orthoefer" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk You can make hp-ux filesystems with 256 character names. That is not a problem. Infact you can take a filesystem off line and convert it to long file names. There is NO REASON for a modern OS to have file names with lengths less than 128. johno - From majordomo-users-owner Thu Sep 7 11:32:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA22004 for majordomo-users-outgoing; Thu, 7 Sep 1995 11:27:32 -0700 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA21989 for ; Thu, 7 Sep 1995 11:27:27 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id OAA01489; Thu, 7 Sep 1995 14:15:35 -0400 Date: Thu, 7 Sep 1995 14:15:34 -0400 (EDT) From: "Jonathan M. Bresler" Subject: Re: 14-char Filenames = BAD THING To: MICHAEL KERR 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 Thu, 7 Sep 1995, MICHAEL KERR wrote: > If you're trying to install and run Majordomo 1.93 on a UNIX system using > 14-character filenames (my particular example is on an HP-UX 9.04 > system), your mailing list names may be NO LONGER than 3 characters. > THREE! > > Can I PLEASE cry??!! yes you may. and afterward you have free fire authorization. 14 character filenames reminds me of a broken program loader that is very popular in the pc world. save yourself a lot of grief and grab an old pc (386dx40 with 8mb is fine) and load FreeBSD. the network support is wonderful as are the mailing lists. i run about a half dozen lists on a 386dx40 as well as a few users doing mail, news, etc... save the hp for other work. and yes i have a VERY STRONG vested interest in FreeBSD. i run their majordomo mailing lists ;) using FreeBSD Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From majordomo-users-owner Thu Sep 7 12:02:33 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA22069 for majordomo-users-outgoing; Thu, 7 Sep 1995 11:31:05 -0700 Received: from gw2.att.com (gw2.att.com [192.20.239.134]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA22062 for ; Thu, 7 Sep 1995 11:31:02 -0700 Received: from ctc.ih.att.com by ig2.att.att.com id AA26767; Thu, 7 Sep 95 13:22:58 EDT Received: by ctc.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA08956; Thu, 7 Sep 95 11:58:04 CDT Received: from ihspa.ih.att.com by ctc.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA08948; Thu, 7 Sep 95 11:58:02 CDT Received: by ihspa.ih.att.com (4.1/EMS-1.1 SunOS) id AA24552; Thu, 7 Sep 95 11:57:41 CDT Date: Thu, 7 Sep 95 11:57:41 CDT Message-Id: <9509071657.AA24552@ihspa.ih.att.com> From: dkk@ctc.ih.att.com (Donna K Kroeschel) To: Majordomo-Users@GreatCircle.COM Subject: Re:email headers Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have majordomo install and things are working fine but my customers who are using the mailing list need to have the From and the From: in the email header be the same and be the id of the person sending the mail. Does anyone know how I can configure this? I can't use Majordomo in production until I can find out how to configure the headers. The From header is fine but I need the From: to be the same as the From header. Thanks Donna Kroeschel ctc!dkk 708-979-6192 IH 1C-209 From majordomo-users-owner Thu Sep 7 12:04:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA22156 for majordomo-users-outgoing; Thu, 7 Sep 1995 11:33:04 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA22149 for ; Thu, 7 Sep 1995 11:33:00 -0700 Received: from se.cs.umb.edu by cs.umb.edu with SMTP id AA04525 (5.65c/IDA-1.4.4 for ); Thu, 7 Sep 1995 14:31:40 -0400 Message-Id: <199509071831.AA04525@cs.umb.edu> To: MICHAEL KERR Cc: majordomo-users@greatcircle.com Subject: Re: 14-char Filenames = BAD THING In-Reply-To: Your message of "Thu, 07 Sep 1995 14:03:44 EDT." Date: Thu, 07 Sep 1995 14:32:23 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >If you're trying to install and run Majordomo 1.93 on a UNIX system using >14-character filenames (my particular example is on an HP-UX 9.04 >system), your mailing list names may be NO LONGER than 3 characters. >THREE! >[...] >Everything in the list will work (or so I can tell) except for the per-list >config files. The config won't hold because of some sort of conflict in >filenames due to truncation, so if you rename your lists to three >characters, the configs will hold and everything will be peachy. New config files are placed under the name of ".config.new". ".config.new" takes up 11 characters. With 3 for the list name that makes 14. Yup. The fix can be to shorten the ".config" to ".c" and the ".new" to ".n" that should get you some additional characters in the list name. From majordomo-users-owner Thu Sep 7 12:31:49 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA24017 for majordomo-users-outgoing; Thu, 7 Sep 1995 12:26:15 -0700 Received: from trotter.usma.edu (trotter.usma.edu [129.29.64.245]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA24003 for ; Thu, 7 Sep 1995 12:26:09 -0700 Received: from euler.math.usma.edu by trotter.usma.edu (4.1/SMI-4.1-eef) id AA02245; Thu, 7 Sep 95 15:24:40 EDT Received: by euler.math.usma.edu (4.1/SMI-4.1) id AA12030; Thu, 7 Sep 95 15:24:40 EDT From: ae6244@euler.math.USMA.EDU (Markert Erich Mr.) Message-Id: <9509071924.AA12030@euler.math.usma.edu> Subject: return receipts to a list To: majordomo-users@greatcircle.com (Majordomo Users List) Date: Thu, 7 Sep 1995 15:24:39 -0400 (EDT) Reply-To: ae6244@euler.math.USMA.EDU X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 886 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I operate several lists and have come across more than several situations where someone has sent a message to one of my lists with the return receipt option turned on. What happens is when anyone reads this message using the same mail package as what was used by the originator a return rcpt message is sent back to the list. My question is, is there anyway to filter these types of messages from getting back to the list? -- _______________________________________________________________________ Mr. Erich L. Markert markert@euler.math.usma.edu Systems Administrator TEL (914)938-6463 Directorate of Information Management FAX (914)938-7075 United States Military Academy West Point, NY 10996 Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer From majordomo-users-owner Thu Sep 7 13:01:57 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA24562 for majordomo-users-outgoing; Thu, 7 Sep 1995 12:46:38 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA24554 for ; Thu, 7 Sep 1995 12:46:32 -0700 Received: from ro.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA23109; Thu, 7 Sep 1995 15:45:01 -0400 (wiseb from ro.cs.rpi.edu) Message-Id: <199509071945.AA23109@cs.rpi.edu> X-Mailer: exmh version 1.6.1 5/23/95 To: majordomo-users@greatcircle.com Subject: Digest headers? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 1995 15:45:00 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Can someone please tell me how to set the header that appears at the beginning of a digest so that it correctly lists the Subjects of the messages that are digested? I tried: message_fronter << END In this Issue: _SUBJECTS_ END But that inserts the In this Issue before every subject! Argh! How can I get: In this issue: _SUBJECTS_ -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Thu Sep 7 13:02:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA24404 for majordomo-users-outgoing; Thu, 7 Sep 1995 12:37:46 -0700 Received: from msu.edu (ibm.cl.msu.edu [35.8.2.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA24391 for ; Thu, 7 Sep 1995 12:37:39 -0700 Received: from msuces.canr.msu.edu by msu.edu (IBM VM SMTP V2R2) with TCP; Thu, 07 Sep 95 15:36:23 EDT Date: Thu, 7 Sep 1995 15:36:11 -0400 (EDT) From: Gina Fogelsonger To: majordomo-users@GreatCircle.COM Subject: get list file In-Reply-To: <199509071929.MAA24069@miles.greatcircle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have currently installed Majordomo on our system. The mailing lists seem to be working properly. What I seem to be having trouble with is the "get " command. I believe I have everything set up properly because I do receive a reply back from Majordomo that the request was accepted and I do not receive any errors. I guess what I don't understand is, where did my file go? I thought that Majordomo was supposed to email the file contents back to the sender of the request yet I have received nothing except the reply that the request was accepted. Any ideas? Thanx. Signed, Dazed and Confused ============================================================================ Gina E. Fogelsonger Systems Programmer MICHIGAN STATE College of Agriculture and Natural Resources ---------------- Computer Services U N I V E R S I T Y Phone: (517) 355-3776 Fax: (517) 353-5341 Internet: fogelson@msuces.canr.msu.edu ============================================================================ From majordomo-users-owner Thu Sep 7 13:32:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA24177 for majordomo-users-outgoing; Thu, 7 Sep 1995 12:32:48 -0700 Received: from leibniz.math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id MAA24168 for ; Thu, 7 Sep 1995 12:32:41 -0700 Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by leibniz.math.psu.edu (8.6.12/8.6.9) with ESMTP id PAA15370; Thu, 7 Sep 1995 15:31:10 -0400 Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.6.12/8.6.9) with ESMTP id PAA20226; Thu, 7 Sep 1995 15:31:09 -0400 Message-Id: <199509071931.PAA20226@augusta.math.psu.edu> X-Mailer: exmh version 1.6.2 7/18/95 To: dkk@ctc.ih.att.com (Donna K Kroeschel) cc: Majordomo-Users@GreatCircle.COM Subject: Re: email headers In-reply-to: Your message of "Thu, 07 Sep 1995 11:57:41 CDT." <9509071657.AA24552@ihspa.ih.att.com> References: <9509071657.AA24552@ihspa.ih.att.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 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 1995 15:31:08 -0400 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <9509071657.AA24552@ihspa.ih.att.com>, Donna K Kroeschel writes: >I have majordomo install and things are working fine but > my customers who are using the mailing list need to have > the From and the From: in the email header be the same and > be the id of the person sending the mail. Does anyone know > how I can configure this? I can't use Majordomo in production > until I can find out how to configure the headers. The From > header is fine but I need the From: to be the same as the From > header. Majordomo doesn't touch headers. If the From: header is incorrect before it gets to Majordomo then there's nothing it can do about it. This sounds like a mailer agent problem. --Dave From majordomo-users-owner Thu Sep 7 13:48:13 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA25540 for majordomo-users-outgoing; Thu, 7 Sep 1995 13:27:11 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA25533 for ; Thu, 7 Sep 1995 13:27:07 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA20663 for majordomo-users@greatcircle.com; Thu, 7 Sep 95 13:25:39 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA21490; Thu, 7 Sep 95 13:25:37 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA02866 for majordomo-users@greatcircle.com; Thu, 7 Sep 95 13:25:35 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA17759; Thu, 7 Sep 95 15:25:28 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA20034; Thu, 7 Sep 1995 15:25:22 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509072025.AA20034@miaow.sps.mot.com> Subject: Re: return receipts to a list To: ae6244@euler.math.USMA.EDU Date: Thu, 7 Sep 1995 15:25:22 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <9509071924.AA12030@euler.math.usma.edu> from "Markert Erich Mr." at Sep 7, 95 03:24:39 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 722 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Markert Erich Mr. writes: ] > > I operate several lists and have come across more than several > situations where someone has sent a message to one of my > lists with the return receipt option turned on. > > What happens is when anyone reads this message using the same mail > package as what was used by the originator a return rcpt message > is sent back to the list. > > My question is, is there anyway to filter these types of messages from > getting back to the list? Yes, in resend find the section that drops certain headers and add the regexps for the offending headers. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Thu Sep 7 14:01:16 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA25730 for majordomo-users-outgoing; Thu, 7 Sep 1995 13:35:11 -0700 Received: from lynx.dac.neu.edu (lynx.dac.neu.edu [129.10.1.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA25723 for ; Thu, 7 Sep 1995 13:35:06 -0700 Received: (from johnson@localhost) by lynx.dac.neu.edu (8.6.12/8.6.12) id QAA22014; Thu, 7 Sep 1995 16:33:29 -0400 From: Chris Johnson Message-Id: <199509072033.QAA22014@lynx.dac.neu.edu> Subject: MAJORDOMO ABORT shlock problem. To: majordomo-users@greatcircle.com Date: Thu, 7 Sep 1995 16:33:28 -0400 (EDT) Cc: johnson@lynx.dac.neu.edu (Chris Johnson) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1208 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi. Trying to set up digests and archives here. Finally got 1.93 up on Digital UNIX 3.2a with perl5.001m. Wouldn't work with 4.36. Thanks to all who helped. I scanned my majordomo-users list archive and saw a few things with shlock in them but nothing exactly like this. I have digest running as per the README and as far as I know the FAQ. When I send to test-digest I get the following: > MAJORDOMO ABORT > > open of temp file /majordomo/Digest/test-digest/shlock.32669 failed > No such file or directory > > The FAQ talks about permissions but this isn't that or does seem to be. And the directory mentioned in the error exists, is owned by majordom.majordom, and is mode 750. What's wrong? ---------------------------------------------------------------------------- Chris Johnson Internet: johnson@chaos.dac.neu.edu Assistant Director, Systems BITNET: johnson@nuhub Division of Academic Computing Voice: 617.373.3300 Northeastern University, 39 RI FAX: 617.373.8600 360 Huntington Ave. Boston, MA., U.S.A. 02115 ---------------------------------------------------------------------------- From majordomo-users-owner Thu Sep 7 14:31:42 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA27089 for majordomo-users-outgoing; Thu, 7 Sep 1995 14:14:40 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA27082 for ; Thu, 7 Sep 1995 14:14:36 -0700 Received: from ro.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA26506; Thu, 7 Sep 1995 17:13:00 -0400 (wiseb from ro.cs.rpi.edu) Message-Id: <199509072113.AA26506@cs.rpi.edu> X-Mailer: exmh version 1.6.1 5/23/95 To: majordomo-users@greatcircle.com Subject: More on Digests Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Sep 1995 17:12:59 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thanks to those of you who told me I needed a hyphen or something around the _SUBJECTS_ .. I will test that out soon. My next question is how to deal with messages sent to the digest. I run a mailing list called the owl-list, and owl-list-digest is simply the digest version of that list. What happens when send mail to the -digest address? It goes to the digest users. What should I do to make sure that digest users send their posts/replies related to the posts they see in the digest back to the owl-list instead of the owl-list-digest? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Thu Sep 7 14:32:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA27212 for majordomo-users-outgoing; Thu, 7 Sep 1995 14:20:02 -0700 Received: from gateway.iscla.sei-it.com ([205.231.128.33]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id OAA27205 for ; Thu, 7 Sep 1995 14:19:59 -0700 Received: from pop.iscla.sei-it.com (pop.iscla.sei-it.com [205.231.128.72]) by gateway.iscla.sei-it.com (8.6.12/8.6.12) with ESMTP id OAA10635; Thu, 7 Sep 1995 14:03:41 -0700 Received: from ISC_LA/SpoolDir by pop.iscla.sei-it.com (Mercury 1.21); 7 Sep 95 13:54:41 -0800 Received: from SpoolDir by ISC_LA (Mercury 1.21); 7 Sep 95 13:54:30 -0800 Received: from atlantis.idsoc.sei-it.com by pop.iscla.sei-it.com (Mercury 1.21) with ESMTP; 7 Sep 95 13:54:26 -0800 Received: (from dwig@localhost) by atlantis.idsoc.sei-it.com (8.6.12/8.6.12) id NAA56430; Thu, 7 Sep 1995 13:31:37 -0700 Date: Thu, 7 Sep 1995 13:31:37 -0700 From: dwig@sei-it.com Message-Id: <199509072031.NAA56430@atlantis.idsoc.sei-it.com> To: rouilj@cs.umb.edu CC: MKERR@vichosp.london.on.ca, majordomo-users@GreatCircle.COM In-reply-to: <199509071831.AA04525@cs.umb.edu> (rouilj@cs.umb.edu) Subject: Re: 14-char Filenames = BAD THING Reply-to: Don Dwiggins Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk John P Rouillard writes: > New config files are placed under the name of > ".config.new". ".config.new" takes up 11 characters. With 3 > for the list name that makes 14. Yup. > The fix can be to shorten the ".config" to ".c" and the ".new" to ".n" > that should get you some additional characters in the list name. Another fix, that takes more work but allows more characters, would be to make "config.new" a directory, with files inside it, so the filenames become config.new/. Of course, this is still less desirable than changing the filesystem to allow for long filenames, as a previous poster mentioned. Don Dwiggins "Solvitur Ambulando" SEI Information Technology ddwiggins@sei-it.com From majordomo-users-owner Thu Sep 7 14:39:17 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA27511 for majordomo-users-outgoing; Thu, 7 Sep 1995 14:31:51 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA27504 for ; Thu, 7 Sep 1995 14:31:46 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA06493 for majordomo-users@greatcircle.com; Thu, 7 Sep 95 14:30:20 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA23047; Thu, 7 Sep 95 14:30:19 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA09127 for majordomo-users@greatcircle.com; Thu, 7 Sep 95 14:30:17 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA18380; Thu, 7 Sep 95 16:30:14 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA14301; Thu, 7 Sep 1995 16:30:12 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509072130.AA14301@miaow.sps.mot.com> Subject: Re: MAJORDOMO ABORT shlock problem. To: johnson@lynx.dac.neu.edu (Chris Johnson) Date: Thu, 7 Sep 1995 16:30:12 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509072033.QAA22014@lynx.dac.neu.edu> from "Chris Johnson" at Sep 7, 95 04:33:28 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 708 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Chris Johnson writes: ] > > When I send to test-digest I get the following: > > > MAJORDOMO ABORT > > > > open of temp file /majordomo/Digest/test-digest/shlock.32669 failed > > No such file or directory > > The FAQ talks about permissions but this isn't that or does seem to > be. And the directory mentioned in the error exists, is owned by > majordom.majordom, and is mode 750. > > What's wrong? I'm guessing, but it looks to me like the digest directory is misspelled (in the config file?). Pathname case gets smashed to lower-case. See the FAQ. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Thu Sep 7 16:32:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA00432 for majordomo-users-outgoing; Thu, 7 Sep 1995 16:26:16 -0700 Received: from vichosp.london.on.ca (vichosp.london.on.ca [142.158.100.181]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA07714 for ; Tue, 5 Sep 1995 13:23:28 -0700 Received: from VHC-Message_Server by vichosp.london.on.ca with Novell_GroupWise; Tue, 05 Sep 1995 16:29:30 -0400 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Tue, 05 Sep 1995 16:25:41 -0400 From: MICHAEL KERR To: majordomo-users@greatcircle.com Subject: Digests and Archives Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've gone through the FAQ and the README file, but can't seem to find a solution to my (new) problems... 1) I've set up a list for digest, and it's keeping a digest fine. However, I can't subscribe to the digest list because it doesn't recognize it. I think the problem is that I don't have a londonweb-digest-request alias, but can someone verify this? 2) I've also set the same list up for archiving. I checked that the @archive_dir or whatever the variable is in the majordomo.cf file points to the "ok" archive dir, which right now is /usr/local/mail/archive. Inside that directory I have londonweb. Nothing is going into it. How come? Mike. From majordomo-users-owner Thu Sep 7 17:02:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA00866 for majordomo-users-outgoing; Thu, 7 Sep 1995 16:39:48 -0700 Received: from noah.smumn.edu (NOAH.smumn.edu [140.190.128.63]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id QAA00849 for ; Thu, 7 Sep 1995 16:39:43 -0700 Received: by noah.smumn.edu (5.64/A/UX-3.00) id AA03612; Thu, 7 Sep 95 18:44:25 CDT Date: Thu, 7 Sep 95 18:44:25 CDT From: kevinh@noah.smumn.edu (Kevin A. Hoogheem) Message-Id: <9509072344.AA03612@noah.smumn.edu> To: majordomo-users@greatcircle.com Subject: Config Files Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a question concerning the config file for majordomo. the problem is how can I make a fresh one for each new list I make Ie the full config file. Also I am having problems not geting any reply when I send to the user &&&&-request that I have set up in my aliases file the section looks like this: prpolice: "|/usr/local/majordom/wrapper resend -l prpolice -h noah.smumn.edu -s prpolice-outgoing" owner-prpolice: prpolice-owner prpolice-owner: kevinh prpolice-approval: prpolice-owner prpolice-outgoing: :|include:/usr/local/majordom/list/prpolice prpolice-request: "|/usr/local/majordom/wrapper request-answer prpolice" When i send to prpolice-request I get nothing back from majordomo and it doesnt do any thing. is there a problem in my aliease that you see...also do I need the -l -h -s if I use the full config file thanks for any help sorry if this is a FAQ Kevinh From majordomo-users-owner Thu Sep 7 17:07:32 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA00739 for majordomo-users-outgoing; Thu, 7 Sep 1995 16:36:26 -0700 Received: from skinner.cs.uoregon.edu (skinner.cs.uoregon.edu [128.223.4.13]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA05693 for ; Wed, 6 Sep 1995 15:21:59 -0700 Received: from ix.cs.uoregon.edu by skinner.cs.uoregon.edu with SMTP id AA23020 (5.65/IDA-1.4.2 for majordomo-users@greatcircle.com); Wed, 6 Sep 95 15:20:31 -0700 Date: Wed, 6 Sep 1995 15:20:30 -0700 (PDT) From: chandra sekhar chitneni To: majordomo-users@greatcircle.com Subject: E-mail name resolution Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk For a moderated list, this is what the output is generated. -------------------------------------------------------------------------- chandra sekhar chitneni requests that you approve the following: subscribe lawnet chandra sekhar chitneni If you approve, please send a message such as the following back to Majordomo (with the appropriate PASSWORD filled in, of course): -------------------------------------------------------------------------- When I gave the password, it is trying to save 'chandra sekhar chitneni' rather than in the lawnet file. I tried to play with the strip option(set to yes) and I have 2 files lawnet and lawnet.strib. Nothing is gettng added to "lawnet.strip". Can somebody tell me what is happening. Thanks, -chandra From majordomo-users-owner Thu Sep 7 19:30:02 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id TAA04324 for majordomo-users-outgoing; Thu, 7 Sep 1995 19:21:07 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id TAA04317 for ; Thu, 7 Sep 1995 19:21:04 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA28526 for majordomo-users@greatcircle.com; Thu, 7 Sep 95 19:19:38 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA28084; Thu, 7 Sep 95 19:19:37 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA28448 for majordomo-users@greatcircle.com; Thu, 7 Sep 95 19:19:35 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA19607; Thu, 7 Sep 95 21:19:33 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA21686; Thu, 7 Sep 1995 21:19:31 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509080219.AA21686@miaow.sps.mot.com> Subject: Re: Config Files To: kevinh@noah.smumn.edu (Kevin A. Hoogheem) Date: Thu, 7 Sep 1995 21:19:31 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <9509072344.AA03612@noah.smumn.edu> from "Kevin A. Hoogheem" at Sep 7, 95 06:44:25 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1472 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Kevin A. Hoogheem writes: ] > > I have a question concerning the config file for majordomo. > the problem is how can I make a fresh one for each new list I make > Ie the full config file. Just create the list file (an empty one via touch will do, but be sure it has the correct ownerships and permissions), set up the aliases for it, and send a "config listname listname.admin" request to Mj. It will create a default config file and return it to you for editing. > Also I am having problems not geting any reply when I send to > the user &&&&-request that I have set up in my aliases file > the section looks like this: > prpolice: "|/usr/local/majordom/wrapper resend -l prpolice -h noah.smumn.edu -s prpolice-outgoing" > owner-prpolice: prpolice-owner > prpolice-owner: kevinh > prpolice-approval: prpolice-owner > prpolice-outgoing: :|include:/usr/local/majordom/list/prpolice ^ Typo in your alias file or just here? > prpolice-request: "|/usr/local/majordom/wrapper request-answer prpolice" > > When i send to prpolice-request I get nothing back > from majordomo and it doesnt do any thing. Did you fix request-answer as per the latest FAQ? > is there a problem in my aliease that you see...also do I need the > -l -h -s if I use the full config file -l, -h, and outgoing alias -- yes. -s -- no. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Fri Sep 8 00:30:08 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id AAA09796 for majordomo-users-outgoing; Fri, 8 Sep 1995 00:05:42 -0700 Received: from qtts-nfs-2308.telkom.co.za (qtts-nfs-2308.telkom.co.za [165.143.31.76]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id AAA09789 for ; Fri, 8 Sep 1995 00:05:21 -0700 From: MASIESC@telkom09.telkom.co.za X-Nvlenv-01Date-Transferred: 08-Sep-1995 09:02:44 +0000; at Telkom00.Telkom X-Nvlenv-01Date-Transferred: 8-Sep-1995 9:03:02 +0000; at qtts2308.Telkom X-Nvlenv-01Date-Posted: 08-Sep-1995 09:00:33 +0000; at QTTS2303.Telkom Priority: Urgent To: majordomo-users@greatcircle.com Message-Id: <962D5030014C620C@-SMF-> Subject: Date: 08 Sep 95 11:00:13 GMT References: <962D5030024C620C@-SMF-> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all, I'm a newcomer to this list and to the list-server environment - please understand my ignorance : I need help with the following - I have set up a unixware 2.02 box here in my office, I have added a wrapper package to it and configured it to suite our environment. Before installing the majordomo software I read in the manual that one needed the Perl interpreter, well, this is where my trouble starts - firstly I don't have any manuals for the perl software and this is causing a problem with the installation - does anyone have manuals I can read through to get things going? I'd also appreciate some advice on how to approach this majordomo installation.........any help would be great - Thanks. P.S. This is rather urgent so will one of you guys please contact me via enail asap... Regards Stafford MASIESC@Telkom09.Telkom.Co.Za From majordomo-users-owner Fri Sep 8 06:31:05 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA18438 for majordomo-users-outgoing; Fri, 8 Sep 1995 06:17:30 -0700 Received: from trotter.usma.edu (trotter.usma.edu [129.29.64.245]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA18431 for ; Fri, 8 Sep 1995 06:17:26 -0700 Received: from euler.math.usma.edu by trotter.usma.edu (4.1/SMI-4.1-eef) id AA12444; Fri, 8 Sep 95 09:15:50 EDT Received: by euler.math.usma.edu (4.1/SMI-4.1) id AA14721; Fri, 8 Sep 95 09:15:51 EDT From: ae6244@euler.math.USMA.EDU (Markert Erich Mr.) Message-Id: <9509081315.AA14721@euler.math.usma.edu> Subject: Re: return receipts to a list To: majordomo-users@greatcircle.com (Majordomo Users List) Date: Fri, 8 Sep 1995 09:15:51 -0400 (EDT) Reply-To: ae6244@euler.math.USMA.EDU X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1673 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thanks for Dave Wolfe's help in pointing me in the correct direction. I found a nasty little bug in the resend code that prevents RCPT subjects from being properly handled. In the check for administrivia requests portion of resend the code is: /^subject:\s*RCPT:\b/ || I could not, for the life of me, figure out why this wasn't working. Well, after banging my head against the wall and cursing regular expressions I removed the colon after RCPT and made another small change so that the regular expression looks like: /^subject:\s*RCPT\b/i || Viola! It now works. This keeps all those pesky return receipts from getting back onto the list, but it doesn't prevent registered mail from being sent to the list. Add the following regexp to this else block: /^registered:/i This will cause registered messages to bounce due to an admin request if it's sent as registered mail. Of course, my knowledge of the RFCs for registered mail is limited so I'm not sure that this will handle ALL registered mail. But, it's a start. BTW, I noticed that the Failed mail regexp doesn't work unless the i switch is added to the regexp. I have a feeling that this is the case for the rest of the regexps as well. -- _______________________________________________________________________ Mr. Erich L. Markert markert@euler.math.usma.edu Systems Administrator TEL (914)938-6463 Directorate of Information Management FAX (914)938-7075 United States Military Academy West Point, NY 10996 Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer From majordomo-users-owner Fri Sep 8 06:32:27 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA18555 for majordomo-users-outgoing; Fri, 8 Sep 1995 06:28:58 -0700 Received: from msu.edu (ibm.cl.msu.edu [35.8.2.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA18548 for ; Fri, 8 Sep 1995 06:28:55 -0700 Received: from msuces.canr.msu.edu by msu.edu (IBM VM SMTP V2R2) with TCP; Fri, 08 Sep 95 09:27:41 EDT Date: Fri, 8 Sep 1995 09:27:28 -0400 (EDT) From: Gina Fogelsonger To: David Wolfe cc: majordomo-users@greatcircle.com Subject: Re: get list file In-Reply-To: <9509072053.AA17748@miaow.sps.mot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 7 Sep 1995, Dave Wolfe wrote: > [ Gina Fogelsonger writes: ] > > > > What I seem to be having trouble with is the "get " command. > > I believe I have everything set up properly because I do receive a reply > > back from Majordomo that the request was accepted and I do not receive > > any errors. > > > > I guess what I don't understand is, where did my file go? I thought that > > Majordomo was supposed to email the file contents back to the sender of > > the request yet I have received nothing except the reply that the request > > was accepted. > > Did it say that the file was being sent in a separate message? Maybe if > you forwarded a sample of exactly what Mj did say it would help. Does > index show that the file you're trying to get is there? > I changed the group and owner to majordom and the get is now working. I'm not exactly sure why this is the case since the read permissions were set for all. Now that the get command is working like a charm, I am confused as to why my index command is NOT working. Following is the reply from majordomo to the index request of the same list the I DO receive the file in the get command: >From Majordomo@msuces.canr.msu.eduFri Sep 8 09:20:47 1995 Date: Fri, 8 Sep 1995 12:53:15 GMT From: Majordomo@msuces.canr.msu.edu To: fogelson@msuces.canr.msu.edu Subject: Majordomo results: index -- >>>> index dairy_ext_team **** index: index command failed >>>> There are actually two files in the directory /usr/local/mail/files/dairy_ext_team to list. Any thoughts ? Thanx. Gina > -- > Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 > Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 > ============================================================================ Gina E. Fogelsonger Systems Programmer MICHIGAN STATE College of Agriculture and Natural Resources ---------------- Computer Services U N I V E R S I T Y Phone: (517) 355-3776 Fax: (517) 353-5341 Internet: fogelson@msuces.canr.msu.edu ============================================================================ From majordomo-users-owner Fri Sep 8 07:01:18 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA19062 for majordomo-users-outgoing; Fri, 8 Sep 1995 06:53:12 -0700 Received: from oulu.fi (ousrvr.oulu.fi [130.231.240.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA19048; Fri, 8 Sep 1995 06:53:04 -0700 Received: from paju.oulu.fi by oulu.fi (4.1/SMI-4.1) id AA11570; Fri, 8 Sep 95 16:51:32 +0300 Received: from raita.oulu.fi by paju.oulu.fi via ESMTP (950215.SGI.8.6.10/930416.SGI.AUTO) id QAA20256; Fri, 8 Sep 1995 16:51:31 +0300 Received: (mhotti@localhost) by raita.oulu.fi (950215.SGI.8.6.10/8.6.9) id QAA21336; Fri, 8 Sep 1995 16:51:31 +0300 Date: Fri, 8 Sep 1995 16:51:28 +0300 (EDT) From: Marko Hotti To: majordomo-workers@greatcircle.com Cc: majordomo-users@greatcircle.com Subject: A suggestion: Logging of resent messages Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'd like to see a new feature in resend: If the incoming message passes the administrivia check and resend prepares the message for listname-outgoing, it would optionally append a log message to a file in a majordomo subdirectory, stating who sent the message and when. Each mailing list could have a logfile of its own. I guess this is very easy to implement in the resend code. The reason for this is obvious. We would like to keep log on activity on the mailing lists. It would be very easy to calculate the lines in the logfiles e.g. once a month, make statistics on most active submitting subscribers etc. There are numerous benefits and no file locking is needed - I guess. With regards, Mako Hotti - Majordomo-Owner at lists.oulu.fi University of Oulu, FINLAND __Marko_Hotti____________________________________mhotti@paju.oulu.fi_____ University of Oulu * Finland URL: http://phoenix.oulu.fi/~mhotti/ Smail: Tervontie 4 C 11, 90230 OULU Tel: available on request IRC: Mikael From majordomo-users-owner Fri Sep 8 07:03:05 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA18939 for majordomo-users-outgoing; Fri, 8 Sep 1995 06:45:48 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA18931 for ; Fri, 8 Sep 1995 06:45:45 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA03677 for majordomo-users@greatcircle.com; Fri, 8 Sep 95 06:44:20 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA04633; Fri, 8 Sep 95 06:44:19 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA01914 for majordomo-users@greatcircle.com; Fri, 8 Sep 95 06:44:17 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA20986; Fri, 8 Sep 95 08:44:14 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA16078; Fri, 8 Sep 1995 08:44:12 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509081344.AA16078@miaow.sps.mot.com> Subject: Re: get list file To: fogelson@msuces.canr.msu.edu (Gina Fogelsonger) Date: Fri, 8 Sep 1995 08:44:11 -0500 (CDT) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Gina Fogelsonger" at Sep 8, 95 09:27:28 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1082 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Gina Fogelsonger writes: ] > > I changed the group and owner to majordom and the get is now working. > I'm not exactly sure why this is the case since the read permissions were > set for all. Mj locks the files before mailing them (it expects them to be archive files, which might be extended by mail received while it's reading them for the get), so the directory has to be writable by Mj. > Now that the get command is working like a charm, I am confused as to why > my index command is NOT working. [...] > >>>> index dairy_ext_team > **** index: index command failed > >>>> Mj prints this message when the $index_command (in majordomo.cf) fails: what do you have $index_command set to? Does that program exist on the path set by wrapper? Is it executable by Mj? Is the (index) directory searchable by Mj so that $index_command can search and read its contents? Obviously the answer to at least one of the last 3 questions is "no". -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Fri Sep 8 07:41:32 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA19717 for majordomo-users-outgoing; Fri, 8 Sep 1995 07:28:45 -0700 Received: from trotter.usma.edu (trotter.usma.edu [129.29.64.245]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA19710 for ; Fri, 8 Sep 1995 07:28:22 -0700 Received: from euler.math.usma.edu by trotter.usma.edu (4.1/SMI-4.1-eef) id AA13090; Fri, 8 Sep 95 10:26:42 EDT Received: by euler.math.usma.edu (4.1/SMI-4.1) id AA15857; Fri, 8 Sep 95 10:26:43 EDT From: ae6244@euler.math.USMA.EDU (Markert Erich Mr.) Message-Id: <9509081426.AA15857@euler.math.usma.edu> Subject: Re: return receipts to a list To: majordomo-users@greatcircle.com (Majordomo Users List) Date: Fri, 8 Sep 1995 10:26:42 -0400 (EDT) Reply-To: ae6244@euler.math.USMA.EDU X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1331 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have to agree with Dave. This fix will work, but the reason I suggested the removal of the colon is because I've seen several situations where the RCPT is of the following forms: RCPT: original subject RCPT OF: original subject > --- 206,218 ---- > && (/^subject:\s*subscribe\b/i || > /^subject:\s*unsubscribe\b/i || > /^subject:\s*help\b/i || > ! /^subject:\s*RCPT:/i || > ! /^subject:\s*Delivery Confirmation\b/i || > ! /^subject:\s*NON-DELIVERY of:/i || > ! /^subject:\s*Undeliverable Message\b/i || > ! /^subject:\s*Receipt Confirmation\b/i || > ! /^subject:\s*Failed mail\b/i || > ! /^subject:\s.*\bchange\b.*\baddress\b/i || > /^subject:\s*request\b.*\baddition\b/i)) { > &bounce("Admin request"); We may also want to add a regexp that handles the latter case as well. -- _______________________________________________________________________ Mr. Erich L. Markert markert@euler.math.usma.edu Systems Administrator TEL (914)938-6463 Directorate of Information Management FAX (914)938-7075 United States Military Academy West Point, NY 10996 Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer From majordomo-users-owner Fri Sep 8 07:47:16 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA19597 for majordomo-users-outgoing; Fri, 8 Sep 1995 07:23:58 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA19590; Fri, 8 Sep 1995 07:23:54 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA12926 for majordomo-workers@greatcircle.com; Fri, 8 Sep 95 07:22:29 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA06350; Fri, 8 Sep 95 07:22:28 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA05215 for majordomo-workers@greatcircle.com; Fri, 8 Sep 95 07:22:26 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA21417; Fri, 8 Sep 95 09:22:23 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA15961; Fri, 8 Sep 1995 09:22:20 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509081422.AA15961@miaow.sps.mot.com> Subject: Re: A suggestion: Logging of resent messages To: mhotti@paju.oulu.fi (Marko Hotti) Date: Fri, 8 Sep 1995 09:22:20 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list), majordomo-workers@greatcircle.com (Majordomo developer's mailing list) In-Reply-To: from "Marko Hotti" at Sep 8, 95 04:51:28 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1261 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Marko Hotti writes: ] > > I'd like to see a new feature in resend: If the incoming message passes > the administrivia check and resend prepares the message for > listname-outgoing, it would optionally append a log message to a file in a > majordomo subdirectory, stating who sent the message and when. Each > mailing list could have a logfile of its own. I guess this is very easy > to implement in the resend code. But apparently not easy enough that any code was included. ;-) > There are numerous benefits and no file locking is needed - I guess. Bad guess. Queuing by sendmail elevates the probability to near 1 that multiple messages will arrive at nearly the same time, resulting in multiple resend processes running at the same time, some of which will be trying to write to the same list log file at the same time. Every file that can be modified must be locked for every access. Seems to me this could be implemented without bothering resend and slowing down delivery to the list. Just hook in a tabulator script, similar to the way archives are done. Code is left as an exercise for those who care. :-) -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Fri Sep 8 08:02:13 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA19394 for majordomo-users-outgoing; Fri, 8 Sep 1995 07:10:38 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA19387; Fri, 8 Sep 1995 07:10:35 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA09490 for majordomo-workers@greatcircle.com; Fri, 8 Sep 95 07:09:08 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA05447; Fri, 8 Sep 95 07:09:06 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA03889 for majordomo-workers@greatcircle.com; Fri, 8 Sep 95 07:09:04 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA21262; Fri, 8 Sep 95 09:09:01 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA21046; Fri, 8 Sep 1995 09:08:56 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509081408.AA21046@miaow.sps.mot.com> Subject: Re: return receipts to a list To: uunet!euler.math.USMA.EDU!ae6244 Date: Fri, 8 Sep 1995 09:08:56 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list), majordomo-workers@greatcircle.com (Majordomo developer's mailing list), cwilson@snarf.engr.sgi.com (Chan Wilson) In-Reply-To: <9509081315.AA14721@euler.math.usma.edu> from "Markert Erich Mr." at Sep 8, 95 09:15:51 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2755 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Markert Erich Mr. writes: ] > > I found a nasty little bug in the resend code that prevents > RCPT subjects from being properly handled. In the check > for administrivia requests portion of resend the code is: > > /^subject:\s*RCPT:\b/ || > > [...] I removed the colon after RCPT and made another small change so > that the regular expression looks like: > > /^subject:\s*RCPT\b/i || > > Viola! It now works. Erich posted his observation before I could reply to his previous message, but let me add my $.02 worth... He was right about the 'i' modifier, the match needs to be case insensitive since the subject header is usually spelled "Subject", but the other bug is that ':' is already a "non-word" character (non-alphanumeric), so unless it's immediately followed by an alphanumeric character, the '\b' fails to match, i.e. if the colon is followed by a space (another non-word character), there is no word boundary between them and the '\b' (word boundary meta-(non)character) fails to match. Removing either the ':' or the '\b' from the regexp works, but I think it's safer to match the ':' explicitly and forget about what follows it. Therefore I'm submitting the following patch to resend to correct such problems (if some of the match strings *must* match in upper-case, i.e. RCPT, then the fix is going to have to take a different approach because the "subject:" part of the match is case insensitive): *** resend.orig Wed Mar 1 08:43:24 1995 --- resend Fri Sep 8 08:58:30 1995 *************** *** 206,218 **** && (/^subject:\s*subscribe\b/i || /^subject:\s*unsubscribe\b/i || /^subject:\s*help\b/i || ! /^subject:\s*RCPT:\b/ || ! /^subject:\s*Delivery Confirmation\b/ || ! /^subject:\s*NON-DELIVERY of:/ || ! /^subject:\s*Undeliverable Message\b/ || ! /^subject:\s*Receipt Confirmation\b/ || ! /^subject:\s*Failed mail\b/ || ! /^subject:\s.*\bchange\b.*\baddress\b/ || /^subject:\s*request\b.*\baddition\b/i)) { &bounce("Admin request"); } --- 206,218 ---- && (/^subject:\s*subscribe\b/i || /^subject:\s*unsubscribe\b/i || /^subject:\s*help\b/i || ! /^subject:\s*RCPT:/i || ! /^subject:\s*Delivery Confirmation\b/i || ! /^subject:\s*NON-DELIVERY of:/i || ! /^subject:\s*Undeliverable Message\b/i || ! /^subject:\s*Receipt Confirmation\b/i || ! /^subject:\s*Failed mail\b/i || ! /^subject:\s.*\bchange\b.*\baddress\b/i || /^subject:\s*request\b.*\baddition\b/i)) { &bounce("Admin request"); } -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Fri Sep 8 08:35:21 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA21030 for majordomo-users-outgoing; Fri, 8 Sep 1995 08:25:08 -0700 Received: from msu.edu (ibm.cl.msu.edu [35.8.2.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA21017 for ; Fri, 8 Sep 1995 08:25:01 -0700 Received: from msuces.canr.msu.edu by msu.edu (IBM VM SMTP V2R2) with TCP; Fri, 08 Sep 95 11:23:45 EDT Date: Fri, 8 Sep 1995 11:23:33 -0400 (EDT) From: Gina Fogelsonger To: David Wolfe cc: majordomo-users@greatcircle.com Subject: Re: get list file In-Reply-To: <9509081344.AA16078@miaow.sps.mot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 8 Sep 1995, Dave Wolfe wrote: > > Now that the get command is working like a charm, I am confused as to why > > my index command is NOT working. > [...] > > >>>> index dairy_ext_team > > **** index: index command failed > > >>>> > > Mj prints this message when the $index_command (in majordomo.cf) > fails: what do you have $index_command set to? Does that program exist > on the path set by wrapper? Is it executable by Mj? Is the (index) > directory searchable by Mj so that $index_command can search and read > its contents? Obviously the answer to at least one of the last 3 > questions is "no". > > -- > Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 > Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 > Dave, The $index_command setting in the cf file was incorrect and the index command is now working. :-) Thank you so much for all of your help. Maybe sometime I will be able to answer someone elses questions after I haved worked with this longer. Gina ============================================================================ Gina E. Fogelsonger Systems Programmer MICHIGAN STATE College of Agriculture and Natural Resources ---------------- Computer Services U N I V E R S I T Y Phone: (517) 355-3776 Fax: (517) 353-5341 Internet: fogelson@msuces.canr.msu.edu ============================================================================ From majordomo-users-owner Fri Sep 8 09:32:28 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA23178 for majordomo-users-outgoing; Fri, 8 Sep 1995 09:31:36 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA23171 for ; Fri, 8 Sep 1995 09:31:32 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA25664; Fri, 8 Sep 1995 12:30:05 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509081630.AA25664@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: MESSAGE_FOOTERS ? X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Fri, 08 Sep 1995 12:29:37 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Do people actually put something in the message_footers for their lists? I was thinking of putting something like how to get help from majordomo in the footer. But do I really need to do this? Given that I use the administrivia checks, and I have installed the request_answer stuff, wont people get a reply back from majordomo if they do it incorrectly? When the list is digested, it looks silly to see those footers at the end of every message you read. Also, they probably take up just that much more space ... over a lot of messages that is a lot of bytes! So should I include a footer or no? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Fri Sep 8 10:00:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA23933 for majordomo-users-outgoing; Fri, 8 Sep 1995 09:53:56 -0700 Received: from europe.std.com (europe.std.com [192.74.137.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA23926 for ; Fri, 8 Sep 1995 09:53:53 -0700 Received: from world.std.com by europe.std.com (8.6.12/Spike-8-1.0) id MAA12432; Fri, 8 Sep 1995 12:52:28 -0400 Received: by world.std.com (5.65c/Spike-2.0) id AA10060; Fri, 8 Sep 1995 12:52:27 -0400 Message-Id: <199509081652.AA10060@world.std.com> To: Bowden Wise Cc: majordomo-users@greatcircle.com Subject: Re: MESSAGE_FOOTERS ? In-Reply-To: Your message of "Fri, 08 Sep 1995 12:29:37 EDT." <199509081630.AA25664@cs.rpi.edu> Date: Fri, 08 Sep 1995 12:52:27 -0400 From: Elizabeth Lear Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I use them, even though the list is digested. I put in: - _________________________________________________________________ - To leave this mailing list, send mail to majordomo@world.std.com - with the message UNSUBSCRIBE MUSICALS END Saves me from people who don't save the 'how to get off this list' message. ..eliz From majordomo-users-owner Fri Sep 8 10:30:18 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA25120 for majordomo-users-outgoing; Fri, 8 Sep 1995 10:24:41 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA25111 for ; Fri, 8 Sep 1995 10:24:36 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA27775; Fri, 8 Sep 1995 13:23:07 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509081723.AA27775@cs.rpi.edu> To: Project Genesis Cc: majordomo-users@greatcircle.com Subject: Re: MESSAGE_FOOTERS ? In-Reply-To: Project Genesis's message of "Fri, 08 Sep 1995 13:10:53 EDT." <199509081717.RAA08176@j51.com> X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Fri, 08 Sep 1995 13:22:39 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I could have a message in the digest footer, but the problem I am having is that my digest list is a digest of a normal list, and the normal list has the footer, so all of the messages that end up in the digest end up with that same footer.... Is there a way to remove footers when the digest is created? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Fri Sep 8 13:11:15 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA01040 for majordomo-users-outgoing; Fri, 8 Sep 1995 12:45:59 -0700 Received: from lynx.dac.neu.edu (lynx.dac.neu.edu [129.10.1.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id MAA01029 for ; Fri, 8 Sep 1995 12:45:49 -0700 Received: (from johnson@localhost) by lynx.dac.neu.edu (8.6.12/8.6.12) id PAA19865 for majordomo-users@greatcircle.com; Fri, 8 Sep 1995 15:44:14 -0400 From: Chris Johnson Message-Id: <199509081944.PAA19865@lynx.dac.neu.edu> Subject: digest error, no files? To: majordomo-users@greatcircle.com Date: Fri, 8 Sep 1995 15:44:13 -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: 1795 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > I'm guessing, but it looks to me like the digest directory is misspelled > (in the config file?). Pathname case gets smashed to lower-case. See the > FAQ. > > -- > Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 > Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 > Right as usual. Thanks Dave. Type-o's. SHEESH! I must be getting old. Digest files are now showing up in test-digest. That's good. So I sent majordomo an mkdigest command. Sending mkdigest test-digest returns and error claiming no list. Ok. So I think the -digest is assumed. I certainly found them as strings in the code. Sending mkdigest test returns with an error claiming there are no files to digest. Huh? There are files there, four in point of fact. And now there's this test directory in my Digests area along with the test-digest directory. I saw a .LOCK file show up there momentarily so it is trying to do something. I'm guessing that the test directory is the work area to build the digest. Ok fine. Why does mkdigest not find the four digest files in test-digest? Looked in the README. Looked in the FAQ. Maybe I missed it but I didn't see anything that looked like this particular problem. What am I doing wrong now? Thanks. ---------------------------------------------------------------------------- Chris Johnson Internet: johnson@chaos.dac.neu.edu Assistant Director, Systems BITNET: johnson@nuhub Division of Academic Computing Voice: 617.373.3300 Northeastern University, 39 RI FAX: 617.373.8600 360 Huntington Ave. Boston, MA., U.S.A. 02115 ---------------------------------------------------------------------------- From majordomo-users-owner Fri Sep 8 14:02:34 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA03526 for majordomo-users-outgoing; Fri, 8 Sep 1995 13:37:22 -0700 Received: from j51.com (j51.com [199.224.7.51]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA03506 for ; Fri, 8 Sep 1995 13:37:08 -0700 Received: from pm2.j51.com (pm2.j51.com [199.224.7.226]) by j51.com (8.6.12/8.6.9) with SMTP id UAA14530; Fri, 8 Sep 1995 20:35:58 GMT Message-Id: <199509082035.UAA14530@j51.com> X-Sender: genesis@j51.com X-Mailer: Windows Eudora Version 2.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 08 Sep 1995 16:29:15 -0400 To: Bowden Wise From: Project Genesis Subject: Re: MESSAGE_FOOTERS ? Cc: majordomo-users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 01:22 PM 9/8/95 -0400, Bowden Wise wrote: >I could have a message in the digest footer, but the problem I am >having is that my digest list is a digest of a normal list, and the >normal list has the footer, so all of the messages that end up in the >digest end up with that same footer.... > >Is there a way to remove footers when the digest is created? > According to the config file, that's a feature which needs to be activated in the future. Ken From majordomo-users-owner Fri Sep 8 17:30:04 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id RAA10899 for majordomo-users-outgoing; Fri, 8 Sep 1995 17:25:23 -0700 Received: from noah.smumn.edu (NOAH.smumn.edu [140.190.128.63]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id RAA10892 for ; Fri, 8 Sep 1995 17:25:20 -0700 Received: by noah.smumn.edu (5.64/A/UX-3.00) id AA05693; Fri, 8 Sep 95 19:29:57 CDT Date: Fri, 8 Sep 95 19:29:57 CDT From: kevinh@noah.smumn.edu (Kevin A. Hoogheem) Message-Id: <9509090029.AA05693@noah.smumn.edu> To: majordomo-users@greatcircle.com Subject: Problmes Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Well I have tracked some problems down but here is one I have not seen b4 MAJORDOMO ABORT do_exec_sendmail, number of args <= 1 unsafe to exec This is when i try to send to a list-request any ideas here? From majordomo-users-owner Fri Sep 8 20:30:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id UAA14733 for majordomo-users-outgoing; Fri, 8 Sep 1995 20:05:03 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id UAA14726 for ; Fri, 8 Sep 1995 20:04:57 -0700 From: wiseb@cs.rpi.edu Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA14933; Fri, 8 Sep 1995 23:03:31 -0400 (wiseb from colossus.cs.rpi.edu) Date: Fri, 8 Sep 95 23:03:03 EDT Received: by colossus.cs.rpi.edu (4.1/2.3-RPI-CS-client) id AA20226; Fri, 8 Sep 95 23:03:03 EDT Message-Id: <9509090303.AA20226@colossus.cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Digest numbers? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Does mkdgiest update the numbers of the digest? I thought it was updating correctly, but I just noticed that the last 4 digests generated have all been: V1 #4 DO i have to manually update it?? From majordomo-users-owner Fri Sep 8 20:32:34 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id UAA15194 for majordomo-users-outgoing; Fri, 8 Sep 1995 20:25:40 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id UAA15187 for ; Fri, 8 Sep 1995 20:25:37 -0700 From: wiseb@cs.rpi.edu Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA15209; Fri, 8 Sep 1995 23:24:13 -0400 (wiseb from colossus.cs.rpi.edu) Date: Fri, 8 Sep 95 23:23:44 EDT Received: by colossus.cs.rpi.edu (4.1/2.3-RPI-CS-client) id AA20323; Fri, 8 Sep 95 23:23:44 EDT Message-Id: <9509090323.AA20323@colossus.cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Digest Config Confusion Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am confused about some things about digest in the README. What are the config file modifications? That the -C swithc turns on? Currently that is what I am using. What are the extra digest config files that I found in the contrib directory along with the digest script? I set up one fo those for my digest list, but the settings in there apparently do not seem to be used. All the settings apear to come from the list specific config file majordomo uses. From majordomo-users-owner Sun Sep 10 04:30:00 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id EAA04801 for majordomo-users-outgoing; Sun, 10 Sep 1995 04:28:24 -0700 Received: from earth.sparco.com (Earth.SPARCO.Com [130.18.192.110]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id EAA04794 for ; Sun, 10 Sep 1995 04:28:20 -0700 Received: (from salman@localhost) by earth.sparco.com (8.6.9/8.6.9) id GAA05746 for majordomo-users@greatcircle.com; Sun, 10 Sep 1995 06:26:50 -0500 From: Muhammad Salman Mughal Message-Id: <199509101126.GAA05746@earth.sparco.com> Subject: archive2.pl error To: majordomo-users@greatcircle.com Date: Sun, 10 Sep 1995 06:26:50 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2128 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all, I'm trying to setup an archive using archive2.pl. My aliases go something like: --------------------------------------------------------------------------- test: "|/usr/local/majordomo/wrapper resend -h machname -l test test-outgoing" test-digest:test test-outgoing: :include:/usr/local/majordomo/lists/test, "| /usr/local/majordomo/wrapper digest -r -C -l test-digest test-digest-outgoing", "| /usr/local/majordomo/wrapper archive2.pl -f /usr/local/majordomo/archive/test.archive/test -a -m" test-digest-outgoing: :include:/usr/local/majordomo/lists/test test-request: "|/usr/local/majordomo/wrapper request-answer test" test-approval: salman owner-test: salman owner-test-outgoing:owner-test owner-test-digest:owner-test owner-test-digest-outgoing:owner-test --------------------------------------------------------------------------- I created /usr/local/majordomo/archive/test.archive/ directory and even created a file with the name "test" (size 0) in this directory. Everytime I send mail to test@machname, I get the following error: --------------------------------------------------------------------------- ----- The following addresses had delivery problems ----- "| /usr/local/majordomo/wrapper archive2.pl -f /usr/local/majordomo/archive/test.archive/test -a -m" (unrecoverable error) (expanded from: test-outgoing) ----- Transcript of session follows ----- Invalid archive directory. Aborting. ABORT Invalid archive directory. Aborting. 554 "| /usr/local/majordomo/wrapper archive2.pl -f /usr/local/majordomo/archive/test.archive/test -a -m"... unknown mailer error 29 Receiving 3 --------------------------------------------------------------------------- I know that /usr/local/majordomo/archive/test.archive/ directory exists and test is a file sitting in there, but still it keeps aborting like this. I'll appreciate if anyone could tell me what I'm doing wrong here. Thanks. Regards -- Salman Mughal Computer Science Mississippi State University Email: msm6@Ra.MsState.Edu WWW: http://www2.msstate.edu/~msm6 From majordomo-users-owner Sun Sep 10 13:00:05 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA09731 for majordomo-users-outgoing; Sun, 10 Sep 1995 12:33:50 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA09724 for ; Sun, 10 Sep 1995 12:33:46 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA21239; Sun, 10 Sep 1995 15:32:24 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509101932.AA21239@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Archiving vs. Digesting X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Sun, 10 Sep 1995 15:31:46 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The list I am setting up will also have a digestified version of the list; so there are two lists: owl-list, and owl-list-digest. Since the digest will be creted using the mail to owl-list, could I not use the digests as archives of owl-list? Or should I set up the archival script as well? The other thing I am not sure how to do is how to handle replies to the -digest list. Don't I want replies to go back to owl-list? What do people use for their reply-to headers? Currently, I havent changed the default setting ... (i.e., blank). What would be the best thing to do here? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Sun Sep 10 15:30:05 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA13093 for majordomo-users-outgoing; Sun, 10 Sep 1995 15:25:34 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA25697 for ; Fri, 8 Sep 1995 10:41:00 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA28307; Fri, 8 Sep 1995 13:39:33 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509081739.AA28307@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: One line administrative footer message? X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Fri, 08 Sep 1995 13:38:52 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Anyone have a a small, concise, one line administrative message that tells how to get help/unsubscribe/ from majordomo? I want to put something like that in my footer. -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Sun Sep 10 15:32:49 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA13077 for majordomo-users-outgoing; Sun, 10 Sep 1995 15:25:22 -0700 Received: from blue.NL.net (blue1.NL.net [193.79.241.51]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id EAA15669 for ; Fri, 8 Sep 1995 04:39:11 -0700 Received: (from jv@localhost) by blue.NL.net (8.6.12/8.6.9) id NAA00220; Fri, 8 Sep 1995 13:43:35 +0200 Date: Fri, 8 Sep 1995 13:43:35 +0200 Message-Id: <199509081143.NAA00220@blue.NL.net> From: Johan Vromans To: majordomo-users@greatcircle.com Subject: Automatic membership maintenance Reply-To: Johan.Vromans@NL.net X-Organization: NLnet - the Internet in the Netherlands X-Address: Kruislaan 419, 1098 VA Amsterdam, The Netherlands X-Phone: +31 20 6639366 Fax: +31 20 6655311 X-Mailer: GNU Emacs 19.29.2 with VM 5.95 (beta) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk One of the nice features of majordome is its ability to have users subscribe and unsubscribe on mailing lists w/o intervention of a human. I'd say that would definitely apply to the majordomo-users list itself. For more than a week now I have been trying to get off this list, without success. It seems that majordomo-users-request@greatcircle.com is dead. I get no response on list and help commands either. Sorry to bother you all, but I'd like to be removed from the list. -- Johan From majordomo-users-owner Sun Sep 10 19:30:16 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id TAA18446 for majordomo-users-outgoing; Sun, 10 Sep 1995 19:21:18 -0700 Received: from earth.sparco.com (Earth.SPARCO.Com [130.18.192.110]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id TAA18439 for ; Sun, 10 Sep 1995 19:21:14 -0700 Received: (from salman@localhost) by earth.sparco.com (8.6.9/8.6.9) id VAA08247 for majordomo-users@greatcircle.com; Sun, 10 Sep 1995 21:19:29 -0500 From: Muhammad Salman Mughal Message-Id: <199509110219.VAA08247@earth.sparco.com> Subject: moderated lists To: majordomo-users@greatcircle.com Date: Sun, 10 Sep 1995 21:19:29 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2074 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all, I am trying to do the following things: * I want the list to be moderated, and only want someone@somehere to be allowed to post articles to the mailing list. I changed "moderated = no" to "moderate = yes" in listname.config. It does sends the orignal mail back to the sender with a subject saying "Approval Required". Where do I specify who can post to the mailing list? * I have this experimental list, I defined myself as the listowner. Now, I want another person to be the listowner too. So, I defined the following aliases in /etc/aliases, but they never worked. I keep getting "approval" requests for subscription and unsubscription; and errors related to the mailing list to my address only. There is a section in the README file and I tried to follow it, but I guess I didn't set it up correctly. I'll appreciate any help. Thanks! -------------------------------------------------------------------------- test: "| /usr/local/majordomo/wrapper resend -h machname -l test test-outgoing" test-outgoing: :include:/usr/local/majordomo/lists/test, "| /usr/local/majordomo/wrapper digest -r -C -l test-digest test-digest-outgoing" , "| /usr/local/majordomo/wrapper archive2.pl -f /usr/local/majordomo/archive/test.archive/test -a -m" test-digest:test test-digest-outgoing: :include:/usr/local/majordomo/lists/test test-request: "|/usr/local/majordomo/wrapper request-answer test" test-approval: salman owner-test: :include:/usr/local/majordomo/lists/test-owners test-owner:owner-test owner-owner-test: owner-majordomo owner-test-outgoing:owner-test owner-test-digest:owner-test owner-test-digest-outgoing:owner-test "test-owners" is the name of the file where I stored 2 email address, and it's lying in /usr/local/majordomo/lists/ directory. -------------------------------------------------------------------------- -- Salman Mughal Computer Science Mississippi State University Email: msm6@Ra.MsState.Edu WWW: http://www2.msstate.edu/~msm6 From majordomo-users-owner Sun Sep 10 23:30:05 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id XAA21183 for majordomo-users-outgoing; Sun, 10 Sep 1995 23:04:02 -0700 Received: from isp1.isp.net (isp1.isp.net [204.139.9.12]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id XAA21176 for ; Sun, 10 Sep 1995 23:03:58 -0700 Received: from outsider.bolis.sf-bay.org ([204.153.195.10]) by mail.isp.net (8.6.9/8.6.9) with SMTP id XAA13401; Sun, 10 Sep 1995 23:01:03 -0700 Received: from hock.bolis.sf-bay.org by outsider.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0ss1si-0006vSC; Sun, 10 Sep 95 22:58 PDT Received: from amillar by hock.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0ss1tR-000UpuC; Sun, 10 Sep 95 22:58 PDT Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: Bowden Wise , majordomo-users@greatcircle.com Date: Sun, 10 Sep 1995 21:50:41 -800 Subject: Re: More on Digests Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On 7 Sep 95 at 17:12, Bowden Wise wrote: > What happens when send mail to the -digest address? It goes > to the digest users. What should I do to make sure that digest > users send their posts/replies related to the posts they > see in the digest back to the owl-list instead of the owl-list-digest? Good question. This isn't obvious at first. You want the digest members to receive the same messages as the main list. You want the digest submissions to go to everyone also. Because of this, you DON'T want to feed the digest submissions to the digest outgoing list. Any submissions to the digest address should just be more input into the main list. Here are some sample alias file entries: Mayberry: "|/usr/local/mail/mj193/wrapper resend \ -l Mayberry -f Mayberry-sender -h Bolis.SF-Bay.org \ Mayberry-outgo1" This is your typical list main input mayberry-digest: mayberry This is your digest input. It just goes into the list like everything else. Mayberry-outgo1: :include:/usr/local/mail/lists/mayberry, \ Mayberry-archive , \ "|/usr/local/mail/mj193/wrapper digest \ -r -C -l mayberry-digest mayberry-digest-outgoing" Here is a sample outgoing alias. Explode the main list file, archive if necessary, and add it to the digest queue. mayberry-digest-outgoing: :include:/usr/local/mail/lists/mayberry-digest And at the end, the digest outgoing has the digest list exploder. Note that it is best to have the digest input on the main list outgoing alias, AFTER the messages have been through "resend". That way you have the moderation restrictions, administrivia filters, etc., in effect for all messages. - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: http://metro.turnpike.net/metro/amillar From majordomo-users-owner Mon Sep 11 03:30:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id DAA25218 for majordomo-users-outgoing; Mon, 11 Sep 1995 03:03:44 -0700 Received: from cougar.multiline.com.au (cougar.multiline.com.au [203.5.127.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id DAA25211 for ; Mon, 11 Sep 1995 03:03:40 -0700 Received: (from yug@localhost) by cougar.multiline.com.au (8.6.9/8.6.9) id SAA30168; Mon, 11 Sep 1995 18:02:09 +0800 Date: Mon, 11 Sep 1995 18:02:08 +0000 From: Craig Guy Subject: ctime.pl 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, I'd be grateful if someone could forward me a copy of their ctime.pl file. It's a required library file for the majordomo scripts that doesn't appear to be on our system. We are running Linux and Perl V 4.035 It _may_ be in your /usr/local/majordomo directory. Craig From majordomo-users-owner Mon Sep 11 04:30:02 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id EAA26185 for majordomo-users-outgoing; Mon, 11 Sep 1995 04:19:39 -0700 Received: from trotter.usma.edu (trotter.usma.edu [129.29.64.245]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id EAA26178 for ; Mon, 11 Sep 1995 04:19:36 -0700 Received: from euler.math.usma.edu by trotter.usma.edu (4.1/SMI-4.1-eef) id AA27660; Mon, 11 Sep 95 07:18:12 EDT Received: by euler.math.usma.edu (4.1/SMI-4.1) id AA23325; Mon, 11 Sep 95 07:18:11 EDT From: ae6244@euler.math.USMA.EDU (Markert Erich Mr.) Message-Id: <9509111118.AA23325@euler.math.usma.edu> Subject: Re: ctime.pl To: yug@cougar.multiline.com.au (Craig Guy) Date: Mon, 11 Sep 1995 07:18:11 -0400 (EDT) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Craig Guy" at Sep 11, 95 06:02:08 pm Reply-To: ae6244@euler.math.USMA.EDU X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 717 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Craig, Get at least v4.036 of Perl. Once installed this will take care of the problem. Also, alot of what seems to be mdomo problems may be attributed to using pre 4.036 versions of perl. > > It _may_ be in your /usr/local/majordomo directory. > > -- _______________________________________________________________________ Mr. Erich L. Markert markert@euler.math.usma.edu Systems Administrator TEL (914)938-6463 Directorate of Information Management FAX (914)938-7075 United States Military Academy West Point, NY 10996 Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer From majordomo-users-owner Mon Sep 11 05:00:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id EAA26299 for majordomo-users-outgoing; Mon, 11 Sep 1995 04:35:08 -0700 Received: from sba31004.comune.torino.it (sba31004.comune.torino.it [158.102.52.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id EAA26290 for ; Mon, 11 Sep 1995 04:34:57 -0700 Received: from gandalf.comune.torino.it by sba31004.comune.torino.it (AIX 4.1/UCB 5.64/4.03) id AA10122; Mon, 11 Sep 1995 13:29:35 +0200 Message-Id: <9509111129.AA10122@sba31004.comune.torino.it> Comments: Authenticated sender is From: "Gianni Savoia" Organization: Comune di Torino To: majordomo-users@greatcircle.com Date: Mon, 11 Sep 1995 13:36:47 +0000 Subject: Re: ctime.pl Priority: normal X-Mailer: Pegasus Mail for Windows (v2.01) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Hi, I'd be grateful if someone could forward me a copy of their ctime.pl > file. It's a required library file for the majordomo scripts that > doesn't appear to be on our system. We are running Linux and Perl V 4.035 > > It _may_ be in your /usr/local/majordomo directory. > > Craig > Take a look at "README" file. ctime.pl is a library file that comes with perl. *---------------------------------------------------------------* * Gianni Savoia * Comune di Torino Tel : +39 11 442.4021 * Corso Unione Sovietica 218 Fax : +39 11 442.4030 * I - 10134 Torino * mailto:savoia@comune.torino.it *---------------------------------------------------------------* From majordomo-users-owner Mon Sep 11 05:02:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id EAA26258 for majordomo-users-outgoing; Mon, 11 Sep 1995 04:33:21 -0700 Received: from trotter.usma.edu (trotter.usma.edu [129.29.64.245]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id EAA26251 for ; Mon, 11 Sep 1995 04:33:17 -0700 Received: from euler.math.usma.edu by trotter.usma.edu (4.1/SMI-4.1-eef) id AA28814; Mon, 11 Sep 95 07:31:56 EDT Received: by euler.math.usma.edu (4.1/SMI-4.1) id AA23375; Mon, 11 Sep 95 07:31:55 EDT From: ae6244@euler.math.USMA.EDU (Markert Erich Mr.) Message-Id: <9509111131.AA23375@euler.math.usma.edu> Subject: Re: Archiving vs. Digesting To: wiseb@cs.rpi.edu (Bowden Wise) Date: Mon, 11 Sep 1995 07:31:55 -0400 (EDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <199509101932.AA21239@cs.rpi.edu> from "Bowden Wise" at Sep 10, 95 03:31:46 pm Reply-To: ae6244@euler.math.USMA.EDU X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1160 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > The list I am setting up will also have a digestified version of the > list; so there are two lists: owl-list, and owl-list-digest. Since > the digest will be creted using the mail to owl-list, could I not use > the digests as archives of owl-list? In theory, anything is possible. Why people setup and use archives is because daily messages are compiled into one file for each month. For example, all September traffic to a list would be in a file listname.archive.9509. Digests differ from this because they are spread out over MANY files, and unless I'm mistaken digest files are not retained, they are wiped out each time a mkdigest is execd. Archives are kept for as long as you want. -- _______________________________________________________________________ Mr. Erich L. Markert markert@euler.math.usma.edu Systems Administrator TEL (914)938-6463 Directorate of Information Management FAX (914)938-7075 United States Military Academy West Point, NY 10996 Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer From majordomo-users-owner Mon Sep 11 06:00:15 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id FAA27091 for majordomo-users-outgoing; Mon, 11 Sep 1995 05:39:45 -0700 Received: from lynx.dac.neu.edu (lynx.dac.neu.edu [129.10.1.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id FAA27084 for ; Mon, 11 Sep 1995 05:39:41 -0700 Received: (from johnson@localhost) by lynx.dac.neu.edu (8.6.12/8.6.12) id IAA29229; Mon, 11 Sep 1995 08:38:11 -0400 From: Chris Johnson Message-Id: <199509111238.IAA29229@lynx.dac.neu.edu> Subject: Re:digests error To: majordomo-users@greatcircle.com Date: Mon, 11 Sep 1995 08:38:11 -0400 (EDT) Cc: johnson@lynx.dac.neu.edu (Chris Johnson) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1755 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Here's how my digests are set up: > > Suppose a list foobar and it's digest foobar-digest. > The subscriber lists for these files are in ~majordomo/lists > as defined in majordomo.cf. Got that and it works. > The working directory for the digest is ~majordomo/digest as > defined in majordomo.cf. Check. > In the directory ~majordomo/digest there will be a subdirectory > called foobar-digest. This is where the messages are collected > throughout the day. Check again. > When I use the mkdigest command and I give it > the list name foobar-digest it looks in the digest_work_dir for > the messages to create and then sends it out to the foobar-digest > list. Hold it. When I send mkdigest test-digest I get a no list error returned. The digest never gets created. > Finally the resulting digests are kept in ~majordomo/lists/ > foobar-digest.archive (a directory). These digests are subsequently > moved to an ANON FTP server for retrieval by people wanting old > list traffic. > > Hope that helps. > > Mike > I'm golden up until the mkdigest command. Then things crash and burn. Maybe I'm missing a symptom in that mkdigest test-digest fails and the problem is really earlier that where I think? ---------------------------------------------------------------------------- Chris Johnson Internet: johnson@chaos.dac.neu.edu Assistant Director, Systems BITNET: johnson@nuhub Division of Academic Computing Voice: 617.373.3300 Northeastern University, 39 RI FAX: 617.373.8600 360 Huntington Ave. Boston, MA., U.S.A. 02115 ---------------------------------------------------------------------------- From majordomo-users-owner Mon Sep 11 07:30:13 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA29004 for majordomo-users-outgoing; Mon, 11 Sep 1995 07:14:41 -0700 Received: from www.CyberMarket.com (cybermarket.cybermarket.com [199.86.32.160]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id HAA28997 for ; Mon, 11 Sep 1995 07:14:36 -0700 Received: from pm1-20.skypoint.net (pm1-20.skypoint.net [199.86.33.20]) by www.CyberMarket.com (8.6.12/8.6.12) with SMTP id JAA11039 for ; Mon, 11 Sep 1995 09:13:12 -0500 Date: Mon, 11 Sep 1995 09:13:12 -0500 Message-Id: <199509111413.JAA11039@www.CyberMarket.com> X-Sender: gmiller@cybermarket.com X-Mailer: Windows Eudora Version 2.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@GreatCircle.COM From: George Miller - The CyberMarketing Group Subject: Digest Problems Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When I use the mkdigest command, I get an error: *** digest: failed errors follow No messages to process. The digest working directory in the majordom.cf is using both upper and lower case: $digest_work_dir = "/usr/local/bin/majordomo/Lists/Digests"; given that Majordomo doesn't like upper case, will this alone cause the digest to fail? If this is in fact the problem, will changing the case in the majordom.cf file to lowercase alone fix the problem, or do we need to change the actual path to all lower? Is there a 'digest faq' available somewhere for totally 'digest-challenged' people like myself? Thanks! George ________________________________________________ The CyberMarketing Group Full Service Internet Advertising and Consulting gmiller@cybermarket.com http://www.cybermarket.com/ ________________________________________________ From majordomo-users-owner Mon Sep 11 08:30:58 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA00767 for majordomo-users-outgoing; Mon, 11 Sep 1995 08:18:23 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA00760 for ; Mon, 11 Sep 1995 08:18:18 -0700 Received: from avs.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA12652; Mon, 11 Sep 1995 11:16:57 -0400 (wiseb from avs.cs.rpi.edu) Message-Id: <199509111516.AA12652@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Bounces; how does Sender get set? X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Mon, 11 Sep 1995 11:16:52 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am trying to get the bounces to work correctly. What does the list owner get when there is a bounce? Doesn't a message with BOUNCE in the subject get generated? I have one invalid address in my mailing list for testing purposes. I sent a message, but I got the mailer daemon mesages sent right back, so it sounds like the Sender is not getting reset to owner-listname for all messages. I am using resend: owl-list: "|/home/majordom/bin/wrapper resend -l owl-list -h netlab.cs.rpi.edu -s -p bulk owl-list-outgoing" The FAQ says "Make sure the "sender" keyword in the config file points to owner-listname and that you have defined owner-listname alias to point to the onwer of the list. I have the correct aliases, but what config file are they talking about? I dont see a Sender keyword anywhere? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Mon Sep 11 10:00:04 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA04963 for majordomo-users-outgoing; Mon, 11 Sep 1995 09:59:10 -0700 Received: from gov.ab.ca (is-news.gov.ab.ca [198.161.6.11]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA04954 for ; Mon, 11 Sep 1995 09:59:07 -0700 Received: from itdfs14.pwss.gov.ab.ca by gov.ab.ca (5.x/SMI-SVR4) id AA09231; Mon, 11 Sep 1995 10:58:42 -0600 Date: Mon, 11 Sep 1995 10:58:41 -0600 Message-Id: <9509111658.AA09231@gov.ab.ca> X-Sender: achatha@gov.ab.ca X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: achatha@gov.ab.ca (Avtar Chatha) Subject: Put Command? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello: I have recently set up Majordomo 1.93 on SunOS 5.4. My users are asking me if they can store files under a list using e-mail? I know we can retrieve files associated with lists using the "Get" command. Does anyone know/have a "Put" command which will allow us to store files under a list using e-mail? I will really appreciate your replies. ----------------------------------------------------------------------- Avtar Chatha Software Services Branch, Alberta PWSS Decision & Office Support Team SoftSwitch Nickname: CHATHA Phone 403/427-7622 Internet: chatha@censsw.gov.ab.ca Fax 403/427-3876 From majordomo-users-owner Mon Sep 11 10:02:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA04116 for majordomo-users-outgoing; Mon, 11 Sep 1995 09:42:50 -0700 Received: from lynx.dac.neu.edu (lynx.dac.neu.edu [129.10.1.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA04100 for ; Mon, 11 Sep 1995 09:42:42 -0700 Received: (from johnson@localhost) by lynx.dac.neu.edu (8.6.12/8.6.12) id MAA23133; Mon, 11 Sep 1995 12:41:11 -0400 From: Chris Johnson Message-Id: <199509111641.MAA23133@lynx.dac.neu.edu> Subject: re: digests error To: majordomo-users@greatcircle.com Date: Mon, 11 Sep 1995 12:41:11 -0400 (EDT) Cc: johnson@lynx.dac.neu.edu (Chris Johnson) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 774 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Me again. Thank you all who responded. My digests now work. Eeven index and get work. Maybe its age but my memory seems subject to ECC errors and my servo systems are prone to type-o's. Majordomo/UNIX are very unforgiving about such things. The next hurtle is archiving ... onward. ---------------------------------------------------------------------------- Chris Johnson Internet: johnson@chaos.dac.neu.edu Assistant Director, Systems BITNET: johnson@nuhub Division of Academic Computing Voice: 617.373.3300 Northeastern University, 39 RI FAX: 617.373.8600 360 Huntington Ave. Boston, MA., U.S.A. 02115 ---------------------------------------------------------------------------- From majordomo-users-owner Mon Sep 11 10:35:02 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA05839 for majordomo-users-outgoing; Mon, 11 Sep 1995 10:24:39 -0700 Received: from lynx.dac.neu.edu (lynx.dac.neu.edu [129.10.1.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA05832 for ; Mon, 11 Sep 1995 10:24:35 -0700 Received: (from johnson@localhost) by lynx.dac.neu.edu (8.6.12/8.6.12) id NAA00933; Mon, 11 Sep 1995 13:22:49 -0400 From: Chris Johnson Message-Id: <199509111722.NAA00933@lynx.dac.neu.edu> Subject: Re: ctime.pl To: yug@cougar.multiline.com.au (Craig Guy), majordomo-users@greatcircle.com Date: Mon, 11 Sep 1995 13:22:48 -0400 (EDT) Cc: johnson@lynx.dac.neu.edu (Chris Johnson) In-Reply-To: from "Craig Guy" at Sep 11, 95 06:02:08 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: 1107 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > Hi, I'd be grateful if someone could forward me a copy of their ctime.pl > file. It's a required library file for the majordomo scripts that > doesn't appear to be on our system. We are running Linux and Perl V 4.035 > > It _may_ be in your /usr/local/majordomo directory. > > Craig > It's in /usr/local/lib/perl for 4.36 & /usr/local/lib/perl5 for 5.001m. From the README; "If you get complaints about being unable to find "ctime.pl", then either your version of perl is too old, or is not installed properly. "ctime.pl" is a library file that comes with all versions of perl recent enough to use with Majordomo." ---------------------------------------------------------------------------- Chris Johnson Internet: johnson@chaos.dac.neu.edu Assistant Director, Systems BITNET: johnson@nuhub Division of Academic Computing Voice: 617.373.3300 Northeastern University, 39 RI FAX: 617.373.8600 360 Huntington Ave. Boston, MA., U.S.A. 02115 ---------------------------------------------------------------------------- From majordomo-users-owner Mon Sep 11 11:01:23 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA07097 for majordomo-users-outgoing; Mon, 11 Sep 1995 10:54:57 -0700 Received: from lynx.dac.neu.edu (lynx.dac.neu.edu [129.10.1.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA07090 for ; Mon, 11 Sep 1995 10:54:53 -0700 Received: (from johnson@localhost) by lynx.dac.neu.edu (8.6.12/8.6.12) id NAA01105 for majordomo-users@greatcircle.com; Mon, 11 Sep 1995 13:53:23 -0400 From: Chris Johnson Message-Id: <199509111753.NAA01105@lynx.dac.neu.edu> Subject: Re: Archiving vs. Digesting To: majordomo-users@greatcircle.com Date: Mon, 11 Sep 1995 13:53:22 -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: 1370 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > In theory, anything is possible. Why people setup and use > archives is because daily messages are compiled into > one file for each month. For example, all September traffic to > a list would be in a file listname.archive.9509. Digests differ > from this because they are spread out over MANY files, and unless > I'm mistaken digest files are not retained, they are wiped > out each time a mkdigest is execd. Archives are kept > for as long as you want. > -- > _______________________________________________________________________ > Mr. Erich L. Markert markert@euler.math.usma.edu Digests don't seem to goway with mkdigest, at least mine haven't. I just got digesting running and I've run mkdigest a few times. I just get another digest. I was looking at archiving but I don't see the difference at the moment. Is there one? If not then why even bother? ---------------------------------------------------------------------------- Chris Johnson Internet: johnson@chaos.dac.neu.edu Assistant Director, Systems BITNET: johnson@nuhub Division of Academic Computing Voice: 617.373.3300 Northeastern University, 39 RI FAX: 617.373.8600 360 Huntington Ave. Boston, MA., U.S.A. 02115 ---------------------------------------------------------------------------- From majordomo-users-owner Mon Sep 11 13:32:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA11234 for majordomo-users-outgoing; Mon, 11 Sep 1995 13:31:16 -0700 Received: from gw2.att.com (gw2.att.com [192.20.239.134]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA11226 for ; Mon, 11 Sep 1995 13:31:12 -0700 Received: from ctc.ih.att.com by ig1.att.att.com id AA13563; Mon, 11 Sep 95 16:28:51 EDT Received: by ctc.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA20897; Mon, 11 Sep 95 15:29:14 CDT Received: from ihspa.ih.att.com by ctc.ih.att.com (4.1/EMS-1.1.1 SunOS) id AA20893; Mon, 11 Sep 95 15:29:12 CDT Received: by ihspa.ih.att.com (4.1/EMS-1.1 SunOS) id AA01358; Mon, 11 Sep 95 15:28:51 CDT Date: Mon, 11 Sep 95 15:28:51 CDT Message-Id: <9509112028.AA01358@ihspa.ih.att.com> From: dkk@ctc.ih.att.com (Donna K Kroeschel) To: Dave Barr Cc: Majordomo-Users@GreatCircle.COM Subject: Re: email headers Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Dave Thanks for answering my email. It is not the From: that is wrong. It is the From which is the first line on the email header that is wrong. Is there a script in majordomo that work with the email headers? Thanks Donna Kroeschel ctc!dkk 708-979-6192 IH 1C-209 _____________________- From math.psu.edu!barr@ig1.att.att.com Thu Sep 7 14:34:02 1995 Return-Path: Cc: Majordomo-Users@GreatCircle.COM To: dkk@ctc.ih.att.com (Donna K Kroeschel) Subject: Re: email headers References: <9509071657.AA24552@ihspa.ih.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Dave Barr In message <9509071657.AA24552@ihspa.ih.att.com>, Donna K Kroeschel writes: >I have majordomo install and things are working fine but > my customers who are using the mailing list need to have > the From and the From: in the email header be the same and > be the id of the person sending the mail. Does anyone know > how I can configure this? I can't use Majordomo in production > until I can find out how to configure the headers. The From > header is fine but I need the From: to be the same as the From > header. Majordomo doesn't touch headers. If the From: header is incorrect before it gets to Majordomo then there's nothing it can do about it. This sounds like a mailer agent problem. --Dave From majordomo-users-owner Mon Sep 11 13:57:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA11242 for majordomo-users-outgoing; Mon, 11 Sep 1995 13:31:21 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA11235 for ; Mon, 11 Sep 1995 13:31:16 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA09567 for majordomo-users@greatcircle.com; Mon, 11 Sep 95 13:29:53 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA26206; Mon, 11 Sep 95 13:28:42 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA07969 for majordomo-users@greatcircle.com; Mon, 11 Sep 95 13:28:29 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA05712; Mon, 11 Sep 95 15:28:24 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA12540; Mon, 11 Sep 1995 15:28:22 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509112028.AA12540@miaow.sps.mot.com> Subject: Re: Problmes To: uunet!noah.smumn.edu!kevinh (Kevin A. Hoogheem) Date: Mon, 11 Sep 1995 15:28:22 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <9509090029.AA05693@noah.smumn.edu> from "Kevin A. Hoogheem" at Sep 8, 95 07:29:57 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1065 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Kevin A. Hoogheem writes: ] > > Well I have tracked some problems down but here is one I have not seen > b4 > > > MAJORDOMO ABORT > > do_exec_sendmail, number of args <= 1 unsafe to exec > > This is when i try to send to a list-request > any ideas here? Yes, *READ* the Fine FAQ: PROBLEMS WITH 1.93'S REQUEST-ANSWER [ Summary by Yusef Pisan ] There are a some known bugs in request-answer. If you get the error 'Undefined subroutine "main'lopen"' (or "main::lopen" for Perl 5), you need to insert the line 'require "shlock.pl";' near the beginning of request-answer. The syntax of the 'do_exec_sendmail' function is different in majordomo than in majordomo.pl, so you need to change all occurences of 'do_exec_sendmail' in request-answer to something like 'do_exec_sendmail_in_request_answer'. On line 41 where it exec()'s sendmail, change the "-f$list-request" to "-f$list-approval". -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Mon Sep 11 14:00:36 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA11976 for majordomo-users-outgoing; Mon, 11 Sep 1995 13:56:11 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA11969 for ; Mon, 11 Sep 1995 13:56:08 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA16403 for majordomo-users@greatcircle.com; Mon, 11 Sep 95 13:54:43 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA26732; Mon, 11 Sep 95 13:45:26 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA09527 for majordomo-users@greatcircle.com; Mon, 11 Sep 95 13:44:45 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA05856; Mon, 11 Sep 95 15:44:42 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA12360; Mon, 11 Sep 1995 15:44:41 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509112044.AA12360@miaow.sps.mot.com> Subject: Re: archive2.pl error To: salman@earth.sparco.com (Muhammad Salman Mughal) Date: Mon, 11 Sep 1995 15:44:40 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509101126.GAA05746@earth.sparco.com> from "Muhammad Salman Mughal" at Sep 10, 95 06:26:50 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 970 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Muhammad Salman Mughal writes: ] > > I created /usr/local/majordomo/archive/test.archive/ directory and even > created a file with the name "test" (size 0) in this directory. Worthless. Archive2.pl will create files named "test.YYMM", e.g. test.9509 this month. > Everytime I send mail to test@machname, I get the following error: > > --------------------------------------------------------------------------- > ----- The following addresses had delivery problems ----- > "| /usr/local/majordomo/wrapper archive2.pl -f > /usr/local/majordomo/archive/test.archive/test -a -m" (unrecoverable > error) > > (expanded from: test-outgoing) > > ----- Transcript of session follows ----- > Invalid archive directory. Aborting. Check how you have $filedir, $filedir_suffix, and @archive_dirs set in your majordomo.cf. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Mon Sep 11 14:32:49 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA12719 for majordomo-users-outgoing; Mon, 11 Sep 1995 14:15:48 -0700 Received: from snmpmgr.state.tn.us (snmpmgr.state.tn.us [170.142.1.74]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA12710 for ; Mon, 11 Sep 1995 14:15:43 -0700 Received: from langate.tnet.state.tn.us (langate.state.tn.us) by snmpmgr.state.tn.us with SMTP id AA14872 (5.67b/IDA-1.5 for ); Mon, 11 Sep 1995 16:14:22 -0500 Received: from tn01-Message_Server by langate.tnet.state.tn.us with Novell_GroupWise; Mon, 11 Sep 1995 16:19:18 -0500 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Mon, 11 Sep 1995 16:13:29 -0500 From: Wade Williams To: Majordomo-Users@greatcircle.com Subject: No Approvals? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've got majordomo working just like I want it, except one small problem: it won't do approvals. With the moderate keyword set to yes in the per-list config file, Majordomo sends any mail sent to the list address (net-status in this case) to all the members of the list without any approval. In fact, an approval message does not get sent to the approval address. Here are the aliases: wadewilliams: ag03302@langate.tnet.state.tn.us net-status: :include:/usr/spool/major/lists/net-status owner-net-status: wadewilliams net-status-request:"|/usr/spool/major/wrapper request-answer net-status" net-status-approval: wadewilliams All of the files and directories are owned by the majordomo user and group. The majordomo user is a trusted sendmail user. The Log file is no help. Can anyone suggest some methods for tracking down this problem? Thanks, Wade Williams wwilliams@mail.state.tn.us From majordomo-users-owner Mon Sep 11 15:02:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA13984 for majordomo-users-outgoing; Mon, 11 Sep 1995 14:54:41 -0700 Received: from haydn.metsci.com (metsci.com [149.94.0.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id OAA13977 for ; Mon, 11 Sep 1995 14:54:38 -0700 Message-Id: <199509112146.RAA13513@haydn.metsci.com> Date: Mon, 11 Sep 1995 17:40:18 -0400 From: trinh@metsci.com (Stephanie Trinh) To: Majordomo-Users@greatcircle.com, wwilliams@mail.state.tn.us Subject: Re: No Approvals? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Make sure you set subscribe_policy = closed in your $list.config file That will work. trinh@metsci.com From majordomo-users-owner Mon Sep 11 15:04:15 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA13774 for majordomo-users-outgoing; Mon, 11 Sep 1995 14:49:35 -0700 Received: from presence.lglobal.com (presence.lglobal.com [204.50.121.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA05080 for ; Mon, 11 Sep 1995 10:00:20 -0700 Received: from presence.lglobal.com (jesse@presence.lglobal.com [204.50.121.2]) by presence.lglobal.com (8.6.12/8.6.12) with SMTP id NAA17929 for ; Mon, 11 Sep 1995 13:06:17 -0400 Date: Mon, 11 Sep 1995 13:06:17 -0400 (EDT) From: Jesse Hirsh To: majordomo-users@greatcircle.com Subject: HELP!!!!!! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Well I've posted many times to this mail list and still my problems persist. So I will post again: I'm running 1.93 on BSDI 2.0 with Perl 5.001m Permissions are all correct, i've read the faq, docs, you name it... Here's the problems: Log is not working (probably source of it all) (and yes i've checked the directory permissions) Approve is not working Welcome messages are not sent out Perpetually runs out of memory, and on occasion dumps the core. I'll post any of my alias files, or directory/file permissions, or config files on request. I've done a wrapper test and the euid, egid, ruid, rgid are all majordom (POSIX system) HELP ME PLEASE @-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@ Jesse Dillan Hirsh Local GlobalAccess Inc. (416)515-7400 @-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@ From majordomo-users-owner Mon Sep 11 15:30:01 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA14497 for majordomo-users-outgoing; Mon, 11 Sep 1995 15:09:01 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA14480 for ; Mon, 11 Sep 1995 15:08:56 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA08706 for majordomo-users@greatcircle.com; Mon, 11 Sep 95 15:07:26 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA29493; Mon, 11 Sep 95 15:07:01 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA18812 for majordomo-users@greatcircle.com; Mon, 11 Sep 95 15:06:38 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA06875; Mon, 11 Sep 95 17:06:36 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA15142; Mon, 11 Sep 1995 17:06:35 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509112206.AA15142@miaow.sps.mot.com> Subject: Re: No Approvals? To: wwilliams@mail.state.tn.us (Wade Williams) Date: Mon, 11 Sep 1995 17:06:35 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Wade Williams" at Sep 11, 95 04:13:29 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 734 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Wade Williams writes: ] > > I've got majordomo working just like I want it, except one small > problem: it won't do approvals. With the moderate keyword set to > yes in the per-list config file, Majordomo sends any mail sent to the > list address (net-status in this case) to all the members of the list > without any approval. In fact, an approval message does not get sent > to the approval address. > > Here are the aliases: > wadewilliams: ag03302@langate.tnet.state.tn.us > > net-status: :include:/usr/spool/major/lists/net-status You *MUST* use resend to enable resend's features. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Mon Sep 11 16:32:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA16187 for majordomo-users-outgoing; Mon, 11 Sep 1995 16:31:15 -0700 Received: from mail2.pilot.net (mail2.pilot.net [198.232.147.11]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id QAA16178 for ; Mon, 11 Sep 1995 16:31:12 -0700 Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail2.pilot.net (8.7.Beta.11/) with SMTP id QAA07963 for ; Mon, 11 Sep 1995 16:30:55 -0700 (PDT) Received: from awacs.pilot.net by corsair.pilot.net (4.1/SMI-4.1) id AA17907; Mon, 11 Sep 95 16:29:46 PDT Received: by awacs.pilot.net (5.x/SMI-SVR4) id AA00926; Mon, 11 Sep 1995 16:29:21 -0700 Date: Mon, 11 Sep 1995 16:29:21 -0700 From: mikes@pilot.net (Mike St. Vincent) Message-Id: <9509112329.AA00926@awacs.pilot.net> To: majordomo-users@greatcircle.com Subject: Out of Memory X-Sun-Charset: US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When sending basic commands to majordomo, the system sends back an answer but also goes into some type of spin until it runs out of memory. I am running on SunOS 4.1.3, Perl 5.001 (1m), and MajorDomo 1.93 on a SPARC 5 with 32Mb RAM... ----- Transcript of session follows ----- Out of memory! 554 "|/usr/local/MajorDomo/wrapper majordomo"... unknown mailer error 1 Before I go ahead to configure lists, etc., any advice? --Michael St. Vincent --Pilot Network Services From majordomo-users-owner Mon Sep 11 21:30:09 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id VAA23564 for majordomo-users-outgoing; Mon, 11 Sep 1995 21:29:07 -0700 Received: from uu4.psi.com (uu4.psi.com [38.146.21.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id VAA23555 for ; Mon, 11 Sep 1995 21:29:03 -0700 Received: by uu4.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP; id AA20332 for ; Tue, 12 Sep 95 00:22:55 -0400 Date: Mon, 11 Sep 1995 23:01:53 -0500 From: dan@kypris.com (Daniel A. Nichols) Received: by kypris.com (5.65c#3#/3.2.083191-Kypris Software Systems) id AA01526; Mon, 11 Sep 1995 23:01:53 -0500 Message-Id: <199509120401.AA01526@kypris.com> Received: by NeXT.Mailer (1.100) Received: by NeXT Mailer (1.100) To: majordomo-users@greatcircle.com Subject: list config questions (header/footer) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've finally got archiving AND digesting working, but I'm having fits trying to set the digest header and footer. I tried calling digest with "-c /somepath/test-digest.cf" but it crashes, so I'm using the "-C -l /somepath/test-digest" option. That's fine, but in the list config file I can't quite get message_footer and message_fronter to work. If I define them like this: --------------- message_footer << END To subscribe to Test-Digest, send the command: subscribe test-digest in the body of a message to "majordomo@kypris.com". If you want to subscribe something other than the account the mail is coming from, such as a local redistribution list, then append that address to the "subscribe" command; for example, to subscribe "local-alicia": subscribe alicia-fans-digest local-alicia@your.domain.net END message_fronter << END In this issue: _SUBJECTS_ See the end of the digest for information on subscribing to the Test or Test-Digest mailing lists and on how to retrieve back issues. END --------------- it inserts it just fine, but what I really want is the following: --------------- message_footer << END To subscribe to Test-Digest, send the command: subscribe test-digest in the body of a message to "majordomo@kypris.com". If you want to subscribe something other than the account the mail is coming from, such as a local redistribution list, then append that address to the "subscribe" command; for example, to subscribe "local-alicia": subscribe alicia-fans-digest local-alicia@your.domain.net END message_fronter << END In this issue: _SUBJECTS_ See the end of the digest for information on subscribing to the Test or Test-Digest mailing lists and on how to retrieve back issues. END --------------- With the blank lines in there, it throws away everything from the first blank line on and rewrites the config file to look like this: --------------- message_footer << END To subscribe to Test-Digest, send the command: END message_fronter << END In this issue: END --------------- Can anyone explain this and/or tell me how to keep the blank lines in there? thanks, Dan --- Daniel A. Nichols Voice: (214) 790-7255 2905 Lawrence St. Fax: (214) 790-2950 Irving TX 75061-6645 E-Mail: dan_nichols@kypris.com LP 40,45,64 NeXTMail Welcome! From majordomo-users-owner Mon Sep 11 22:30:04 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA24880 for majordomo-users-outgoing; Mon, 11 Sep 1995 22:27:00 -0700 Received: from uu4.psi.com (uu4.psi.com [38.146.21.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id WAA24873 for ; Mon, 11 Sep 1995 22:26:56 -0700 Received: by uu4.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP; id AA25174 for ; Tue, 12 Sep 95 01:16:16 -0400 Date: Mon, 11 Sep 1995 23:17:54 -0500 From: dan@kypris.com (Daniel A. Nichols) Received: by kypris.com (5.65c#3#/3.2.083191-Kypris Software Systems) id AA01713; Mon, 11 Sep 1995 23:17:54 -0500 Message-Id: <199509120417.AA01713@kypris.com> Received: by NeXT.Mailer (1.100) Received: by NeXT Mailer (1.100) To: majordomo-users@greatcircle.com Subject: another config (header/footer) question Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I should have included this in my previous message, sorry. I have one more thing I can't figure out. I have two lists, test and test-digest. If I include a footer for the test list like: message_footer << END ----- + DO NOT INCLUDE THIS TRAILER IN REPLIES TO THE LIST! + The preceding message is from the test mailing list + To submit an article, send it to test@kypris.com + To sub, unsub, etc., send mail to Majordomo@kypris.com END How to I get that stripped when the digest for test-digest is created? It seems to leave it in on EVERY message. Dan From majordomo-users-owner Tue Sep 12 00:00:18 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id XAA26514 for majordomo-users-outgoing; Mon, 11 Sep 1995 23:37:25 -0700 Received: from waffle.ditc.npl.co.uk (waffle.ditc.npl.co.uk [139.143.21.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id XAA26499 for ; Mon, 11 Sep 1995 23:37:19 -0700 Received: from hooke.npl.co.uk by waffle.ditc.npl.co.uk; Tue, 12 Sep 1995 07:36:13 +0100 From: Martin G Kiff Message-Id: <853.9509120635@hooke.npl.co.uk> Subject: Re: Problmes To: majordomo-users@GreatCircle.COM Date: Tue, 12 Sep 1995 07:35:46 +0100 (BST) X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 863 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I watch the same questions cycle round and round on the list, and, I have to say, greatly admire Dave Wolfe's dedication in fielding them, but a nagging doubt surfaces.... _Why_ do the a set of similar questions always come up? Doesn't this suggest a weakness in the Majordomo package? Is it not wary enough of it's environment? Shouldn't it check the permissions of the files and directories when it cannot access a file etc etc? A lot of the work that David seems to do would be solved it there was a patch set for Majordomo which fixed the largest pitfalls - and a lot more of his work could be avoided if Majordomo was a little more defensive ... Just a thought - not meant as any form of criticism - but I'd be interested to know (having only followed this list for a few months) the history behind this.... Regards, Martin Kiff mgk@csu.npl.co.uk From majordomo-users-owner Tue Sep 12 07:30:13 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA04314 for majordomo-users-outgoing; Tue, 12 Sep 1995 07:08:46 -0700 Received: from unilab.dfci.harvard.edu (unilab.dfci.harvard.edu [155.52.46.57]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id HAA04305 for ; Tue, 12 Sep 1995 07:08:43 -0700 Received: (from ratinox@localhost) by unilab.dfci.harvard.edu (8.6.12/8.6.9) id KAA10841; Tue, 12 Sep 1995 10:07:20 -0400 Date: Tue, 12 Sep 1995 10:07:20 -0400 Message-Id: <199509121407.KAA10841@unilab.dfci.harvard.edu> From: Richard Pieri To: Majordomo-users@GreatCircle.COM In-reply-to: Martin G Kiff's message of Tue, 12 Sep 1995 07:35:46 +0100 (BST) Subject: Re: Problmes References: <853.9509120635@hooke.npl.co.uk> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- >>>>> "MGK" == Martin G Kiff writes: MGK> _Why_ do the a set of similar questions always come up? Doesn't MGK> this suggest a weakness in the Majordomo package? Is it not wary MGK> enough of it's environment? Shouldn't it check the permissions of MGK> the files and directories when it cannot access a file etc etc? Because Majordomo isn't a simple package, no, no, and no. A person installing Majordomo should read *all* of the documentation, including the FAQ; this would eliminate about 90% of all the repeated questions seen on the list. Of the remainder, many are OS-related issues which Majordomo cannot even begin to deal with internally and correcting them should not be it's domain. MGK> A lot of the work that David seems to do would be solved it there MGK> was a patch set for Majordomo which fixed the largest pitfalls - MGK> and a lot more of his work could be avoided if Majordomo was a MGK> little more defensive ... No, but life in general for him and everyone else would be much nicer if people actually read the documentation *before* attempting to install Majordomo. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Processed by Mailcrypt 3.3, an Emacs/PGP interface iQCVAwUBMFWUD56VRH7BJMxHAQGqzAP+KMb0PFEUNeFiLoKF50KlBqF0IQBzrUeU EFEjdR+LRhqaAgc7ACSaFpBV1DZkCYhscjQzGD5OzKC22SUYcxbXefHf+S4qinK8 l13nuks57AXSXKKKpYkx7vJoc1DWpPFrM9n8R6+acXJ2b4MpBmDT2Wbgew3BNVm/ pxffIzEfgUk= =JQjb -----END PGP SIGNATURE----- -- Richard Pieri/Information Services \ Make your mark in the world, or at least \ spray in each corner. -A cat's guide to http://www.dfci.harvard.edu/~ratinox \ life From majordomo-users-owner Tue Sep 12 08:02:49 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA05186 for majordomo-users-outgoing; Tue, 12 Sep 1995 08:00:48 -0700 Received: from triton.rdc.puc-rio.br (triton.rdc.puc-rio.br [139.82.34.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA05174 for ; Tue, 12 Sep 1995 08:00:40 -0700 Received: by triton.rdc.puc-rio.br (AIX 3.2/UCB 5.64/4.03) id AA40856; Tue, 12 Sep 1995 11:42:00 -0300 From: poyart@triton.rdc.puc-rio.br (Eduardo Poyart) Message-Id: <9509121442.AA40856@triton.rdc.puc-rio.br> Subject: Test script To: majordomo-users@greatcircle.com Date: Tue, 12 Sep 1995 11:41:59 -0300 (BSC) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 313 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello, How do I use the Test script? The information on the Readme is not complete. Do I run "/usr/local/majordomo/wrapper test" as root or as majordom? What should it return when it is working, and when it is not working? I'm under the Posix conditions. Thanks a lot Eduardo Poyart poyart@rdc.puc-rio.br From majordomo-users-owner Tue Sep 12 08:30:43 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA05582 for majordomo-users-outgoing; Tue, 12 Sep 1995 08:19:20 -0700 Received: from lynx.dac.neu.edu (lynx.dac.neu.edu [129.10.1.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id IAA05573 for ; Tue, 12 Sep 1995 08:19:15 -0700 Received: (from johnson@localhost) by lynx.dac.neu.edu (8.6.12/8.6.12) id LAA18420; Tue, 12 Sep 1995 11:17:23 -0400 From: Chris Johnson Message-Id: <199509121517.LAA18420@lynx.dac.neu.edu> Subject: Re: Test script To: poyart@triton.rdc.puc-rio.br (Eduardo Poyart), majordomo-users@greatcircle.com Date: Tue, 12 Sep 1995 11:17:22 -0400 (EDT) In-Reply-To: <9509121442.AA40856@triton.rdc.puc-rio.br> from "Eduardo Poyart" at Sep 12, 95 11:41:59 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: 1237 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > Hello, > > How do I use the Test script? The information on the Readme is not > complete. Do I run "/usr/local/majordomo/wrapper test" as root or as > majordom? > > What should it return when it is working, and when it is not working? > > I'm under the Posix conditions. > > Thanks a lot > Eduardo Poyart > poyart@rdc.puc-rio.br > > The README might be a bit more clear about this. I had to fiddle a bit myself. You need to compile wrapper with the uid and gid parameters defined as majordom.majordom. You run wrapper as suid and it then does a setuid/setgid to the majordomo uid and gid and then runs whatever you told it to run. Wrapper, at least in my case, is owned by root.majordom and had to be worl executable for sendmail to run it. ---------------------------------------------------------------------------- Chris Johnson Internet: johnson@chaos.dac.neu.edu Assistant Director, Systems BITNET: johnson@nuhub Division of Academic Computing Voice: 617.373.3300 Northeastern University, 39 RI FAX: 617.373.8600 360 Huntington Ave. Boston, MA., U.S.A. 02115 ---------------------------------------------------------------------------- From majordomo-users-owner Tue Sep 12 09:00:41 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA05973 for majordomo-users-outgoing; Tue, 12 Sep 1995 08:34:35 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA05966 for ; Tue, 12 Sep 1995 08:34:31 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA25548; Tue, 12 Sep 1995 11:32:12 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509121532.AA25548@cs.rpi.edu> To: Martin G Kiff Cc: majordomo-users@greatcircle.com Subject: Re: Problmes In-Reply-To: Martin G Kiff's message of "Tue, 12 Sep 1995 07:35:46 BST." <853.9509120635@hooke.npl.co.uk> X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Tue, 12 Sep 1995 11:31:36 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Or, better a simply script (probably perl) that would check your installatin for these common pitfalls, and provide solutions for how to rememdy the problem. -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Tue Sep 12 09:30:34 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA07006 for majordomo-users-outgoing; Tue, 12 Sep 1995 09:16:15 -0700 Received: from topdog.geneva.edu (topdog.geneva.edu [199.234.16.132]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA06999 for ; Tue, 12 Sep 1995 09:16:12 -0700 Received: by topdog.geneva.edu (4.1/SMI-4.1) id AA20747; Tue, 12 Sep 95 12:17:18 EDT Date: Tue, 12 Sep 1995 12:17:17 -0400 (EDT) From: Joe Hines To: majordomo-users@greatcircle.com Subject: Re: Out of Memory In-Reply-To: <9509112329.AA00926@awacs.pilot.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I received the unknown mailer error 1 when the UID and GID in majordomo.cf did not match the owner (majordom) in the passwd file. The default in majordomo.cf was 54, and when checking processes user 54 was running perl, instead of majordom. On Mon, 11 Sep 1995, Mike St. Vincent wrote: > When sending basic commands to majordomo, the system sends back an answer but > also goes into some type of spin until it runs out of memory. I am running > on SunOS 4.1.3, Perl 5.001 (1m), and MajorDomo 1.93 on a SPARC 5 with 32Mb > RAM... > > ----- Transcript of session follows ----- > Out of memory! > 554 "|/usr/local/MajorDomo/wrapper majordomo"... unknown mailer error 1 > > > Before I go ahead to configure lists, etc., any advice? > > --Michael St. Vincent > --Pilot Network Services > From majordomo-users-owner Tue Sep 12 09:32:41 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA06865 for majordomo-users-outgoing; Tue, 12 Sep 1995 09:09:09 -0700 Received: from lynx.dac.neu.edu (lynx.dac.neu.edu [129.10.1.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA06858 for ; Tue, 12 Sep 1995 09:09:05 -0700 Received: (from johnson@localhost) by lynx.dac.neu.edu (8.6.12/8.6.12) id MAA12499 for majordomo-users@greatcircle.com; Tue, 12 Sep 1995 12:07:36 -0400 From: Chris Johnson Message-Id: <199509121607.MAA12499@lynx.dac.neu.edu> Subject: Re: Problmes To: majordomo-users@greatcircle.com Date: Tue, 12 Sep 1995 12:07:36 -0400 (EDT) In-Reply-To: <199509121407.KAA10841@unilab.dfci.harvard.edu> from "Richard Pieri" at Sep 12, 95 10:07:20 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: 2825 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > MGK> _Why_ do the a set of similar questions always come up? Doesn't > MGK> this suggest a weakness in the Majordomo package? Is it not wary > MGK> enough of it's environment? Shouldn't it check the permissions of > MGK> the files and directories when it cannot access a file etc etc? > > Because Majordomo isn't a simple package, no, no, and no. A person > installing Majordomo should read *all* of the documentation, including > the FAQ; this would eliminate about 90% of all the repeated questions > seen on the list. Of the remainder, many are OS-related issues which > Majordomo cannot even begin to deal with internally and correcting them > should not be it's domain. Agreed. But maybe reporting them better might be done. > > MGK> A lot of the work that David seems to do would be solved it there > MGK> was a patch set for Majordomo which fixed the largest pitfalls - > MGK> and a lot more of his work could be avoided if Majordomo was a > MGK> little more defensive ... > > No, but life in general for him and everyone else would be much nicer if > people actually read the documentation *before* attempting to install > Majordomo. > > Richard Pieri/Information Services \ Make your mark in the world, or at least > \ spray in each corner. -A cat's guide to > http://www.dfci.harvard.edu/~ratinox \ life > Again agreed. However I read the README and the FAQ and this list for a while first. It wasn't so much the lack of available information as the, um, concise brevity of it that I found difficult to deal with. I still needed help. And many of the problems I had in getting Majordoo running actually had little to do with Majordomo itself. Examples are a) 1.93 doesn't work with perl4.36 on Digital UNIX 3.2a, b) sendmail barffed on me well before I even got to wrapper never mind any Majordomo code, c) a sometimes reality challenged keyboard/chair interface. That last happens to all of use from time to time. But hey, what do you want for free? I didn't see an 800 number for tech support in the README. So it has the odd bug. It has fewer than most of the products I buy and often has a much better technical assistance facility; this list. True, the same questions get answered all the time. Are you volunteering to rewrite the README or add to the FAQ? ---------------------------------------------------------------------------- Chris Johnson Internet: johnson@chaos.dac.neu.edu Assistant Director, Systems BITNET: johnson@nuhub Division of Academic Computing Voice: 617.373.3300 Northeastern University, 39 RI FAX: 617.373.8600 360 Huntington Ave. Boston, MA., U.S.A. 02115 ---------------------------------------------------------------------------- From majordomo-users-owner Tue Sep 12 10:02:12 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA08021 for majordomo-users-outgoing; Tue, 12 Sep 1995 09:57:13 -0700 Received: from lynx.dac.neu.edu (lynx.dac.neu.edu [129.10.1.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA08014 for ; Tue, 12 Sep 1995 09:57:09 -0700 Received: (from johnson@localhost) by lynx.dac.neu.edu (8.6.12/8.6.12) id MAA30100; Tue, 12 Sep 1995 12:55:21 -0400 From: Chris Johnson Message-Id: <199509121655.MAA30100@lynx.dac.neu.edu> Subject: Re: Problmes To: wiseb@cs.rpi.edu (Bowden Wise), majordomo-users@greatcircle.com Date: Tue, 12 Sep 1995 12:55:19 -0400 (EDT) In-Reply-To: <199509121532.AA25548@cs.rpi.edu> from "Bowden Wise" at Sep 12, 95 11:31:36 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: 979 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > Or, better a simply script (probably perl) that would check your > installatin for these common pitfalls, and provide solutions for how > to rememdy the problem. > -------------------------------------------------------------------- > G. Bowden Wise > Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 > Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ > Ah, gee, if my ECC failure prone memory is acurate today I seem to remember MMDF having one of these. ---------------------------------------------------------------------------- Chris Johnson Internet: johnson@chaos.dac.neu.edu Assistant Director, Systems BITNET: johnson@nuhub Division of Academic Computing Voice: 617.373.3300 Northeastern University, 39 RI FAX: 617.373.8600 360 Huntington Ave. Boston, MA., U.S.A. 02115 ---------------------------------------------------------------------------- From majordomo-users-owner Tue Sep 12 11:30:23 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA10968 for majordomo-users-outgoing; Tue, 12 Sep 1995 11:07:49 -0700 Received: from leibniz.math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA10955 for ; Tue, 12 Sep 1995 11:07:40 -0700 Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by leibniz.math.psu.edu (8.6.12/8.6.9) with ESMTP id OAA26823 for ; Tue, 12 Sep 1995 14:05:37 -0400 Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.6.12/8.6.9) with ESMTP id OAA17437 for ; Tue, 12 Sep 1995 14:05:36 -0400 Message-Id: <199509121805.OAA17437@augusta.math.psu.edu> X-Mailer: exmh version 1.6.2 7/18/95 To: majordomo-users@GreatCircle.COM Subject: Re: Problmes In-reply-to: Your message of "Tue, 12 Sep 1995 12:07:36 EDT." <199509121607.MAA12499@lynx.dac.neu.edu> References: <199509121607.MAA12499@lynx.dac.neu.edu> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Sep 1995 14:05:35 -0400 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <199509121607.MAA12499@lynx.dac.neu.edu>, Chris Johnson writes: > True, the same questions get answered all the time. Are you >volunteering to rewrite the README or add to the FAQ? The FAQ probably could use a rewrite, but I have lost some enthusiasm for it. I don't necessarily want to give up being the maintainer, but if someone could take a good look at it and do a full rewrite (from the HTML source, please) I'd be very happy. The README does really need to be rewritten (again), with a division between "how to get Majordomo working" and a tutorial on how to set up different kinds of lists. Those sorts of things are really beyond the scope of a FAQ, which is why I have been so reluctant to put them in there. The other thing is that there really really needs to be a 1.94 release now. At least 75%-85% of the problems here on this list have already been solved, yet everyone is forced to trudge through an ever-growing bug/incompatibility/caveat list and implement the same solutions over and over. (the major reason for my loss of enthusiasm for Majordomo. One can say RTFM only so many times.) Supposedly 1.94 is coming soon to the gracious help of a new maintainer. (don't ask me when, I don't know) --Dave From majordomo-users-owner Tue Sep 12 11:32:41 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA11345 for majordomo-users-outgoing; Tue, 12 Sep 1995 11:18:23 -0700 Received: from uswat.advtech.uswest.com (uswat.advtech.uswest.com [130.13.16.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA11338 for ; Tue, 12 Sep 1995 11:18:19 -0700 Received: from centhub ([151.116.23.137]) by uswat.advtech.uswest.com (8.6.12/8.6.12) with SMTP id MAA19253 for ; Tue, 12 Sep 1995 12:17:00 -0600 Received: by centhub.mnet.uswest.com (M-Net Hub.950111) Received: from lws489.salttn by lms1 (5.x/SMI-SVR4) id AA26230; Tue, 12 Sep 1995 12:16:55 -0600 Received: from lws489 (localhost) by lws489.salttn (5.x/SMI-SVR4) id AA05505; Tue, 12 Sep 1995 12:17:48 -0600 Message-Id: <9509121817.AA05505@lws489.salttn> To: majordomo-users@greatcircle.com Cc: frjones@sa Subject: problem with header length w/resend. Date: Tue, 12 Sep 1995 12:17:48 -0600 From: "Franklin R. Jones" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello all, apologies if this has been discussed up recently, I've been off the list for a while. I recently received the error: =>Subject: BOUNCE : Header field too long (>1024) Which was indeed the case, as the header contained over 100 individual addresses in addition to one of them being a list address. I traced the error output to Brent's resend program lines 421... => # is this field too long? => if ((($field_len += length($_)) > 1024) && ! defined($approved)) { => &bounce("Header field too long (>1024)"); => return(undef); => } This seems abritrary, and well below limits imposed by sendmail: IDA has 4096, V8 doesn't impose one. Perl doesn't really have a functional line limit that I can find. If it did there wouldn't be much sense in testing for something bigger, as it would already be garbage. FAQ dated dec 94 makes no mention of this, problem etc. Questions: Why the limit? and Is there a good reason it can't be bumped higher? I reviewing the code I can't see a reason for the limit? Is this legacy code that is no longer apropos? Brent, are you out there? Thanks for any input, I'm going to bump it on a test system and see, but wanted to know if anyone had been down this road before. fj.. From majordomo-users-owner Tue Sep 12 12:00:04 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA12655 for majordomo-users-outgoing; Tue, 12 Sep 1995 11:40:32 -0700 Received: from mail2.pilot.net (mail2.pilot.net [198.232.147.11]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA12646 for ; Tue, 12 Sep 1995 11:40:29 -0700 Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail2.pilot.net (8.7.Beta.11/) with SMTP id LAA17271 for ; Tue, 12 Sep 1995 11:40:16 -0700 (PDT) Received: from awacs.pilot.net by corsair.pilot.net (4.1/SMI-4.1) id AA01826; Tue, 12 Sep 95 11:39:08 PDT Received: by awacs.pilot.net (5.x/SMI-SVR4) id AA01230; Tue, 12 Sep 1995 11:38:42 -0700 Date: Tue, 12 Sep 1995 11:38:42 -0700 From: mikes@pilot.net (Mike St. Vincent) Message-Id: <9509121838.AA01230@awacs.pilot.net> To: majordomo-users@greatcircle.com Subject: Re: Out of Memory X-Sun-Charset: US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Interesting... I have the wrapper running by setting its owner to root. There is no reference in my majordomo.cf file to seting UID or GID... BUT, in my majordomo.cf file (copied from the sample from the tar 1.93) it appears that the file is missing data / corrupted at the end. Perhaps the distribution is goofed on the sample.cf??? My sample.cf ends with: [...] # address component after the last /. $no_x400at=0; # if set to 1 do not look for "/c=" and "/ad=" or "/am=" in the address. # X.400 seems to require these components. $no_true_x400=0; 1; # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1.2.2 1995/01/07 17:35:03 rouilj Exp $ [EOF] --Michael St. Vincent --Pilot Network Services > Date: Tue, 12 Sep 1995 12:17:17 -0400 (EDT) > From: Joe Hines > > I received the unknown mailer error 1 when the UID and GID in > majordomo.cf did not match the owner (majordom) in the passwd file. The > default in majordomo.cf was 54, and when checking processes user 54 was > running perl, instead of majordom. From majordomo-users-owner Tue Sep 12 12:02:41 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA12298 for majordomo-users-outgoing; Tue, 12 Sep 1995 11:35:13 -0700 Received: from eipipeline.ei.org (eipipeline.ei.org [192.55.120.104]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA12290 for ; Tue, 12 Sep 1995 11:35:09 -0700 Received: (from shevett@localhost) by eipipeline.ei.org (8.6.12/8.6.12) id OAA04602; Tue, 12 Sep 1995 14:29:02 -0400 Date: Tue, 12 Sep 1995 14:29:02 -0400 (EDT) From: Dave Shevett To: majordomo-users@greatcircle.com Subject: Problems with 1.93. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hey folks... I'm trying to get 1.93 running on a Solaris 2.4 system - first time install, using both gcc and cc. The problem is the wrapper program keeps giving segmentation faults when running. It seems to _run_ properly, but generates an error, so you get a Mailer error when it sends. Compiling the wrapper was tricky due to 2 errors in the code... One was documented in the FAQ, the other had to do with the 'insecure usage' clause, which was just coded poorly. :) I took out the 'insecure usage' check, just to get it to compile cleanly, and i have my alias set up properly in /etc/aliases (a 'help' command to majordomo does return the help script, but also generates an error). here's the error: ----- The following addresses had delivery problems ----- "|/usr/local/majordomo/wrapper majordomo" (unrecoverable error) (expanded from: MajorDomo List Administration ) ----- Transcript of session follows ----- Segmentation Fault 554 "|/usr/local/majordomo/wrapper majordomo"... unknown mailer error 139 ANY help would be appreciated. Time is of the essence. :) ---------------------------------------------------------------------------- Dave Shevett On Contract on the Pipeline Project at shevett@ei.org Engineering Information Hoboken, NJ (h) 908-940-2689 -- (w) 201-216-8500 x694 From majordomo-users-owner Tue Sep 12 12:08:09 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA13050 for majordomo-users-outgoing; Tue, 12 Sep 1995 11:50:02 -0700 Received: from bnr.ca (x400gate.bnr.ca [192.58.194.73]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA13043 for ; Tue, 12 Sep 1995 11:49:57 -0700 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 12 Sep 1995 14:47:06 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 12 Sep 1995 14:46:41 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 12 Sep 1995 14:46:00 -0400 Date: Tue, 12 Sep 1995 14:46:00 -0400 X400-Originator: /dd.id=1579393/g=marc/i=pm/s=jourdeuil/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars735.b.473:12.08.95.18.46.41] X400-Content-Type: P2-1984 (2) Content-Identifier: Re: Test script From: "marc (p.m.) jourdeuil" Message-ID: <"29533 Tue Sep 12 14:46:57 1995"@bnr.ca> To: johnson@lynx.dac.neu.edu, poyart@triton.rdc.puc-rio.br, majordomo-users@greatcircle.com Subject: Re: Test script Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > Hello, > > How do I use the Test script? The information on the Readme is not > complete. Do I run "/usr/local/majordomo/wrapper test" as root or as > majordom? > > What should it return when it is working, and when it is not working? > > I'm under the Posix conditions. > > Thanks a lot > Eduardo Poyart > poyart@rdc.puc-rio.br > > The README might be a bit more clear about this. I had to fiddle a bit myself. You need to compile wrapper with the uid and gid parameters defined as majordom.majordom. You run wrapper as suid and it then does a setuid/setgid to the majordomo uid and gid and then runs whatever you told it to run. Wrapper, at least in my case, is owned by root.majordom and had to be worl executable for sendmail to run it. -------------------------------------------------------------------------- Yes, the info could be clearer. For POSIX, you config the Makefile with the UID.GID of majordom.majordom. You set the wrapper to setuid, ie -rwsr-xr-x 1 root root 20480 Sep 3 15:31 wrapper You run the wrapper as a non-root user (not majordom), ie ./wrapper test It should return the UID, GID of majordom. If it is not correct, you will have other problems! Marc -- +----------------------------------------------------------------------+ / ''' /| / (o o) / | +---------------------------o00--(_)--00o------------------------------+ | | Marc Jourdeuil Voice: (613) 763-3332 | | | Technical Staff | | | Information Systems Analyst | | | Bell-Northern Research Fax: (613) 763-2880 | + | P.O. Box 3511, Station C | / | Ottawa, Canada K1Y 4H7 Internet: marcj@bnr.ca |/ +----------------------------------------------------------------------+ From majordomo-users-owner Tue Sep 12 12:12:02 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA13241 for majordomo-users-outgoing; Tue, 12 Sep 1995 11:54:10 -0700 Received: from hustle.rahul.net (hustle.rahul.net [192.160.13.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA13228 for ; Tue, 12 Sep 1995 11:54:06 -0700 Received: from chage.com by hustle.rahul.net with UUCP id AA20443 (5.67b8/IDA-1.5 for greatcircle.com!majordomo-users); Tue, 12 Sep 1995 11:52:46 -0700 Received: by slick.chage.com (4.1/SMI-4.1) id AA01927; Tue, 12 Sep 95 10:37:12 PDT Date: Tue, 12 Sep 95 10:37:12 PDT From: carl@chage.com (Carl Hage) Message-Id: <9509121737.AA01927@slick.chage.com> To: majordomo-users@greatcircle.com Subject: Infinite loop of bounced mail Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've had a problem recently with an infinite loop of returned mail. The problem happens when a gateway to a proprietary PC email system loses the "Errors-To:" header and bounces mail (in a full mailbox) back to the list. Majordomo fails to detect the message has the "Subject: Undeliverable Message", and sends the bounce to the list including the bouncer for an infinite loop. I read the source code to Majordomo, and I believe I have found a bug in the bounced mail filters, plus noticed some obvious limitations from cases not covered. I believe the matches for bounced messages should all be case insensitive. I added a test for the Subject: Returned mail, a typical bounce and ".*\baway from my mail", which is the default from SunOS vacation. It would be nice to also block messages originating from "mailer-daemon@*", but I haven't figured out where to add a patch for that. Is this the correct place to report this problem? Do developers read this group? Here is the patch (on Version 1.93) to fix the problem (I think): diff -c resend.orig resend *** resend.orig Fri Sep 8 17:03:56 1995 --- resend Fri Sep 8 17:07:25 1995 *************** *** 206,218 **** && (/^subject:\s*subscribe\b/i || /^subject:\s*unsubscribe\b/i || /^subject:\s*help\b/i || ! /^subject:\s*RCPT:\b/ || ! /^subject:\s*Delivery Confirmation\b/ || ! /^subject:\s*NON-DELIVERY of:/ || ! /^subject:\s*Undeliverable Message\b/ || ! /^subject:\s*Receipt Confirmation\b/ || ! /^subject:\s*Failed mail\b/ || ! /^subject:\s.*\bchange\b.*\baddress\b/ || /^subject:\s*request\b.*\baddition\b/i)) { &bounce("Admin request"); } --- 206,221 ---- && (/^subject:\s*subscribe\b/i || /^subject:\s*unsubscribe\b/i || /^subject:\s*help\b/i || ! /^subject:\s*RCPT:\b/i || ! /^subject:\s*Delivery Confirmation\b/i || ! /^subject:\s*NON-DELIVERY of:/i || ! /^subject:\s*Undeliverable Message\b/i || ! /^subject:\s*Receipt Confirmation\b/i || ! /^subject:\s*Failed mail\b/i || ! /^subject:\s*Returned mail\b/i || ! /^subject:\s*unable to deliver mail\b/i || ! /^subject:\s.*\baway from my mail\b/i || ! /^subject:\s.*\bchange\b.*\baddress\b/i || /^subject:\s*request\b.*\baddition\b/i)) { &bounce("Admin request"); } -------------------------------------------------------------------------- Carl Hage C. Hage Associates 1180 Reed Ave #51 Sunnyvale, CA 94086 From majordomo-users-owner Tue Sep 12 12:30:33 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA14258 for majordomo-users-outgoing; Tue, 12 Sep 1995 12:12:29 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA14244 for ; Tue, 12 Sep 1995 12:12:24 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA26249 for majordomo-users@greatcircle.com; Tue, 12 Sep 95 12:11:03 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA21968; Tue, 12 Sep 95 12:10:32 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA11048 for majordomo-users@greatcircle.com; Tue, 12 Sep 95 12:10:30 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA13370; Tue, 12 Sep 95 14:10:28 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA14152; Tue, 12 Sep 1995 14:10:26 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509121910.AA14152@miaow.sps.mot.com> Subject: Re: Test script To: poyart@triton.rdc.puc-rio.br (Eduardo Poyart) Date: Tue, 12 Sep 1995 14:10:26 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <9509121442.AA40856@triton.rdc.puc-rio.br> from "Eduardo Poyart" at Sep 12, 95 11:41:59 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2303 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Eduardo Poyart writes: ] > > How do I use the Test script? The information on the Readme is not > complete. Do I run "/usr/local/majordomo/wrapper test" as root or as > majordom? Neither. To verify that wrapper is installed and working correctly, you must NOT run it from a root logon, nor from the logon it's expected to change to, i.e. W_UID and W_GID (same applies to the logon group, but that's somewhat less critical). Run it from a logon that's completely distinct and disjoint from both root and majordom. The reason you must not be root when running the test script is because the setuid and setgid calls in wrapper work, on most modern systems, only when wrapper runs as root, so the test appears to work even if wrapper is not installed correctly, i.e. setuid root. You must not be majordom (or whatever you set W_UID to) because that's the uid wrapper is trying to change to, so again the test appears to work even if it totally failed. > What should it return when it is working, and when it is not working? When you run the test script, it displays the effective user ID and effective group ID, as well as the real user ID and real group ID (see the man pages for chown(1 & 2) for explanations). To be successful, the euid and ruid must match, as well as the egid and rgid. Additionally, the uid and gid must be what you specified in the Makefile prior to building wrapper and must *not* be the uid and gid (if different) of the current logon. No additional messages from wrapper should be displayed. You can determine the current logon uid and gid by running test both with and without using wrapper. For the reasons mentioned above, only the test run by wrapper should indicate W_UID and W_GID and the test not run by wrapper must not indicate a uid of zero. For example: [majordomo] ./test euid is: 500 egid is: 500 501 200 500 ruid is: 500 rgid is: 500 501 200 500 majordomo] ./wrapper test euid is: 200 egid is: 200 200 ruid is: 200 rgid is: 200 200 Note that running 'test' instead of './test' or 'perl test' will probably just run the shell's internal 'test' command or even /bin/test, neither of which will produce any useful output. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Tue Sep 12 12:33:23 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA15274 for majordomo-users-outgoing; Tue, 12 Sep 1995 12:32:08 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA15255 for ; Tue, 12 Sep 1995 12:32:03 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA06012; Tue, 12 Sep 1995 15:30:43 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509121930.AA06012@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Invalid E-Mails and Mailer Daemon X-Mailer: MH 6.7.1 (exmh 1.5.1) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 12 Sep 1995 15:30:10 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have an invalid e-mail address on one of my lists for testing purposes. When I send to the list, the mailer daemon messages are getting sent back to me. Arent these messages not supposed to reach the sender since resend uses owner- address for the Sender? And, the messages only make it back to the list owner? Obviously I have something not quite set up right? What am I missing? I am also not getting the BOUNCE messages for the invalid address that can be used with the bounce script. What am I missing here? Perhaps both problems can be fixed with same fix? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Tue Sep 12 13:00:46 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA16377 for majordomo-users-outgoing; Tue, 12 Sep 1995 12:58:09 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA16361 for ; Tue, 12 Sep 1995 12:58:05 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA09888 for majordomo-users@greatcircle.com; Tue, 12 Sep 95 12:56:39 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA23486; Tue, 12 Sep 95 12:56:34 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA14935 for majordomo-users@greatcircle.com; Tue, 12 Sep 95 12:56:33 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA13868; Tue, 12 Sep 95 14:56:30 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA20736; Tue, 12 Sep 1995 14:56:29 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509121956.AA20736@miaow.sps.mot.com> Subject: Re: another config (header/footer) question To: uunet!kypris.com!dan (Daniel A. Nichols) Date: Tue, 12 Sep 1995 14:56:29 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509120417.AA01713@kypris.com> from "Daniel A. Nichols" at Sep 11, 95 11:17:54 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 868 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Daniel A. Nichols writes: ] > > I have two lists, test and test-digest. > If I include a footer for the test list like: > > message_footer << END > ----- > + DO NOT INCLUDE THIS TRAILER IN REPLIES TO THE LIST! > + The preceding message is from the test mailing list > + To submit an article, send it to test@kypris.com > + To sub, unsub, etc., send mail to Majordomo@kypris.com > END > > How to I get that stripped when the digest for test-digest is > created? It seems to leave it in on EVERY message. Then you have to get it in the digest *before* it goes through resend (which adds the message_footer), i.e. the alias that redirects messages through resend should also redirect the message to the digest accumulator. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Tue Sep 12 13:02:41 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA16224 for majordomo-users-outgoing; Tue, 12 Sep 1995 12:54:24 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA16211 for ; Tue, 12 Sep 1995 12:54:18 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA08794 for majordomo-users@greatcircle.com; Tue, 12 Sep 95 12:53:00 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA23408; Tue, 12 Sep 95 12:52:58 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA14766 for majordomo-users@greatcircle.com; Tue, 12 Sep 95 12:52:57 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA13830; Tue, 12 Sep 95 14:52:55 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA20979; Tue, 12 Sep 1995 14:52:54 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509121952.AA20979@miaow.sps.mot.com> Subject: Re: list config questions (header/footer) To: dan@kypris.com (Daniel A. Nichols) Date: Tue, 12 Sep 1995 14:52:54 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509120401.AA01526@kypris.com> from "Daniel A. Nichols" at Sep 11, 95 11:01:53 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2697 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Daniel A. Nichols writes: ] > > [...] in the list config file I can't quite get > message_footer and message_fronter to work. > > If I define them like this: > --------------- > message_footer << END > To subscribe to Test-Digest, send the command: > subscribe test-digest > in the body of a message to "majordomo@kypris.com". If you want > to subscribe something other than the account the mail is coming > from, such as a local redistribution list, then append that address > to the "subscribe" command; for example, to subscribe "local-alicia": > subscribe alicia-fans-digest local-alicia@your.domain.net > END [...] > it inserts it just fine, but what I really want is the following: > > --------------- > message_footer << END > To subscribe to Test-Digest, send the command: > > subscribe test-digest > > in the body of a message to "majordomo@kypris.com". If you want > to subscribe something other than the account the mail is coming > from, such as a local redistribution list, then append that address > to the "subscribe" command; for example, to subscribe "local-alicia": > > subscribe alicia-fans-digest local-alicia@your.domain.net > END [...] > With the blank lines in there, it throws away everything from the > first blank line on and rewrites the config file to look like this: > > --------------- > message_footer << END > To subscribe to Test-Digest, send the command: > > END [...] > Can anyone explain this and/or tell me how to keep the blank lines in > there? The docs for this are sort of hidden; you have to read the comments in the list config file: # Within a here document for a string_array, the '-' sign takes on a special # significance. # # To embed a blank line in the here document, put a '-' as the first # and ONLY character on the line. # # To preserve whitespace at the beginning of a line, put a - on the # line before the whitespace to be preserved # # To put a literal '-' at the beginning of a line, double it. So, to get the whitespace in your footers and fronters, make them look like this in the config file: message_footer << END To subscribe to Test-Digest, send the command: - - subscribe test-digest - in the body of a message to "majordomo@kypris.com". If you want to subscribe something other than the account the mail is coming from, such as a local redistribution list, then append that address to the "subscribe" command; for example, to subscribe "local-alicia": - - subscribe alicia-fans-digest local-alicia@your.domain.net END -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Tue Sep 12 13:30:12 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA17738 for majordomo-users-outgoing; Tue, 12 Sep 1995 13:25:09 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA17725 for ; Tue, 12 Sep 1995 13:25:03 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA17448 for majordomo-users@greatcircle.com; Tue, 12 Sep 95 13:23:44 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA24282; Tue, 12 Sep 95 13:23:43 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA17261 for majordomo-users@greatcircle.com; Tue, 12 Sep 95 13:23:41 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA14190; Tue, 12 Sep 95 15:23:40 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA15991; Tue, 12 Sep 1995 15:23:38 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509122023.AA15991@miaow.sps.mot.com> Subject: Re: Infinite loop of bounced mail To: carl@chage.com (Carl Hage) Date: Tue, 12 Sep 1995 15:23:38 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <9509121737.AA01927@slick.chage.com> from "Carl Hage" at Sep 12, 95 10:37:12 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 644 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Carl Hage writes: ] > > I read the source code to Majordomo, and I believe I have found a bug in the > bounced mail filters, plus noticed some obvious limitations from cases not > covered. This was covered just last Friday (except for your additions, of course); check the archive for 9/8 "Re: return receipts to a list". Note that there's another bug you missed (look at RCPT:\b). > Is this the correct place to report this problem? Do developers read > this group? Majordomo-workers@greatcircle.com. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Tue Sep 12 14:01:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA18854 for majordomo-users-outgoing; Tue, 12 Sep 1995 13:51:16 -0700 Received: from mail2.pilot.net (mail2.pilot.net [198.232.147.11]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA18831 for ; Tue, 12 Sep 1995 13:51:10 -0700 Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail2.pilot.net (8.7.Beta.11/) with SMTP id NAA24606 for ; Tue, 12 Sep 1995 13:51:00 -0700 (PDT) Received: from awacs.pilot.net by corsair.pilot.net (4.1/SMI-4.1) id AA13997; Tue, 12 Sep 95 13:49:52 PDT Received: by awacs.pilot.net (5.x/SMI-SVR4) id AA01297; Tue, 12 Sep 1995 13:49:26 -0700 Date: Tue, 12 Sep 1995 13:49:26 -0700 From: mikes@pilot.net (Mike St. Vincent) Message-Id: <9509122049.AA01297@awacs.pilot.net> To: majordomo-users@greatcircle.com Subject: Re: Out of Memory X-Sun-Charset: US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is the better solution... it worked, too. Thanks! (And thanks to all the other helpers on this.) --Michael St. Vincent ----- Begin Included Message ----- From wwilliams@mail.state.tn.us Tue Sep 12 13:38:09 1995 >>> Mike St. Vincent - 9/12/95 1:38 PM >>> Interesting... I have the wrapper running by setting its owner to root. There is no reference in my majordomo.cf file to seting UID or GID... BUT, in my majordomo.cf file (copied from the sample from the tar 1.93) it appears that the file is missing data / corrupted at the end. Perhaps the distribution is goofed on the sample.cf??? My sample.cf ends with: <<<<<<< I don't think that's your problem. Wrapper should be owned by the majordomo user, not by root. However, it should have a mode of 4755. Wade ----- End Included Message ----- From majordomo-users-owner Tue Sep 12 14:04:02 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA19444 for majordomo-users-outgoing; Tue, 12 Sep 1995 14:01:34 -0700 Received: from bnr.ca (x400gate.bnr.ca [192.58.194.73]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA19342; Tue, 12 Sep 1995 14:00:42 -0700 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 12 Sep 1995 16:55:21 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 12 Sep 1995 16:55:02 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 12 Sep 1995 16:54:59 -0400 X400-Received: by /PRMD=bnr/ADMD=telecom.canada/C=ca/; Relayed; Tue, 12 Sep 1995 17:00:29 -0400 Date: Tue, 12 Sep 1995 16:54:59 -0400 X400-Originator: /dd.id=1306203/g=glenn/i=g/s=henshaw/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Message-ID: To: david_wolfe%risc.sps.mot.com@bnr.ca, carl%chage.com@bnr.ca, majordomo-users%greatcircle.com@bnr.ca, majordomo-workers%greatcircle.com@bnr.ca Subject: Re: Infinite loop of bounced mail X-Sender: thraxisp@bcars743.bnr.ca Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 3:23 PM 9/12/95, dwolfe%risc.sps.mot.com@bnr400 wrote: > [ Carl Hage writes: ] > > > > I read the source code to Majordomo, and I believe I have found a bug in the > > bounced mail filters, plus noticed some obvious limitations from cases not > > covered. > > This was covered just last Friday (except for your additions, of > course); check the archive for 9/8 "Re: return receipts to a list". Note > that there's another bug you missed (look at RCPT:\b). > In my previous reply, I noted that there may be a need to filter these responses in "majordomo", as well as "resend". Is this fix in the cards? Common filters would be nice. ... Glenn -- Glenn Henshaw | Advanced System Design, BNR/Nortel Phone: ESN 393-3963, (613)763-3963| Fax: ESN 395-2469, (613)765-2469 From majordomo-users-owner Tue Sep 12 14:09:49 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA18768 for majordomo-users-outgoing; Tue, 12 Sep 1995 13:48:53 -0700 Received: from bnr.ca (x400gate.bnr.ca [192.58.194.73]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA18707 for ; Tue, 12 Sep 1995 13:48:06 -0700 X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 12 Sep 1995 16:42:34 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 12 Sep 1995 16:42:11 -0400 X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 12 Sep 1995 16:42:10 -0400 X400-Received: by /PRMD=bnr/ADMD=telecom.canada/C=ca/; Relayed; Tue, 12 Sep 1995 16:47:37 -0400 Date: Tue, 12 Sep 1995 16:42:10 -0400 X400-Originator: /dd.id=1306203/g=glenn/i=g/s=henshaw/@bnr.ca X400-MTS-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Message-ID: To: carl%chage.com@bnr.ca, majordomo-users%greatcircle.com@bnr.ca Subject: Re: Infinite loop of bounced mail X-Sender: thraxisp@bcars743.bnr.ca Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 10:37 AM 9/12/95, carl%chage.com@bnr400 wrote: > I've had a problem recently with an infinite loop of returned mail. The > problem happens when a gateway to a proprietary PC email system loses > the "Errors-To:" header and bounces mail (in a full mailbox) back to the > list. Majordomo fails to detect the message has the "Subject: Undeliverable > Message", and sends the bounce to the list including the bouncer for an > infinite loop. > > I read the source code to Majordomo, and I believe I have found a bug in the > bounced mail filters, plus noticed some obvious limitations from cases not > covered. I believe the matches for bounced messages should all be case > insensitive. I added a test for the Subject: Returned mail, a typical bounce > and ".*\baway from my mail", which is the default from SunOS vacation. > > It would be nice to also block messages originating from "mailer-daemon@*", > but I haven't figured out where to add a patch for that. > I found a similar situation with our mail gateways. In the case of a bad address, the message was being bounced back to the MD command handler ("majordomo"). Since it was not a well formed message, it was bounced back to the sys-admin with help appended. I added the following (BNR specific) code to the majordomo PERL code to abort the processing of messages apparently from our gateway. diff follows: *** 108,113 **** --- 108,119 ---- if (&addr_match($reply_to, $whoami)) { print STDERR "$whoami punting to avoid mail loop.\n"; exit 0; + } + + # bounce mail from the BNR Postmaster + if ($reply_to =~ /.*[Pp]ostmaster.*@bnr.ca/) { + print STDERR "$whoami punting to avoid mail to administration.\n"; + exit 99; } if (! &valid_addr($reply_to)) { ... Glenn -- Glenn Henshaw | Advanced System Design, BNR/Nortel Phone: ESN 393-3963, (613)763-3963| Fax: ESN 395-2469, (613)765-2469 From majordomo-users-owner Tue Sep 12 16:03:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA24790 for majordomo-users-outgoing; Tue, 12 Sep 1995 15:54:29 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA14801 for ; Tue, 12 Sep 1995 12:22:29 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA05613; Tue, 12 Sep 1995 15:21:02 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509121921.AA05613@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Admin Bounces X-Mailer: MH 6.7.1 (exmh 1.5.1) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 12 Sep 1995 15:20:29 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When someone sends a subscribe request to a list, I get the BOUNCE mail informing me of the admin request. But, does the original user get any kind of help message sent back to them, telling them to send requests to majordomo ?? I thought it did, but when I test it I am not getting such a help message back... -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Tue Sep 12 16:30:31 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA26712 for majordomo-users-outgoing; Tue, 12 Sep 1995 16:23:39 -0700 Received: from mail.eecs.uic.edu (mail.eecs.uic.edu [128.248.174.29]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id QAA26693 for ; Tue, 12 Sep 1995 16:23:34 -0700 Received: from ernie.eecs.uic.edu (ernie.eecs.uic.edu [128.248.176.24]) by mail.eecs.uic.edu (8.6.11/8.6.10) with ESMTP id SAA20707 for ; Tue, 12 Sep 1995 18:23:19 -0500 From: Aaron Newman Received: (anewman1@localhost) by ernie.eecs.uic.edu (8.6.10/8.6.10) id SAA10204 for majordomo-users@GreatCircle.COM; Tue, 12 Sep 1995 18:23:49 -0500 Message-Id: <199509122323.SAA10204@ernie.eecs.uic.edu> Subject: compiling wrapper as other than root To: majordomo-users@GreatCircle.COM Date: Tue, 12 Sep 1995 18:23:49 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 574 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am on SunOS 4.1.3. Because of the way I have my file system set up, I cannot compile in the majordomo directory as root (the file system is mounted and root can't write to it). I figured the same thing would be to make sure that the permissions for group and owner are correct for wrapper (ie set for majordomo). But when I log onto the system as another user and run the test program, I do not get the permissions of this user as I am expecting, I get the permissions of the user I logged in as. I have read the FAQ a zillion times. What am I missing? Thanks, Aaron From majordomo-users-owner Tue Sep 12 17:02:41 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA27663 for majordomo-users-outgoing; Tue, 12 Sep 1995 16:48:19 -0700 Received: from boiled.egg.com (boiled.egg.com [199.2.107.33]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id QAA27649 for ; Tue, 12 Sep 1995 16:48:14 -0700 Received: from localhost by boiled.egg.com (8.6.5/25-eef) id QAA26211; Tue, 12 Sep 1995 16:44:55 -0700 Date: Tue, 12 Sep 1995 16:44:55 -0700 (PDT) From: Tom Glover To: "Mike St. Vincent" cc: majordomo-users@greatcircle.com Subject: Re: Out of Memory In-Reply-To: <9509122049.AA01297@awacs.pilot.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > There is no reference in my majordomo.cf file to seting UID or GID... > BUT, in my majordomo.cf file (copied from the sample from the tar > 1.93) it appears that the file is missing data / corrupted at the > end. Perhaps the distribution is goofed on the sample.cf??? My > sample.cf ends with: > <<<<<<< > > > I don't think that's your problem. > > Wrapper should be owned by the majordomo user, not by root. However, > it should have a mode of 4755. > Absolutely not true. In POSIX based systems (like BSD/OS) wrapper must be owned by root. -- Tom __________________________________________________________________________ | "The Egg Domain" | There are lots of shades of grey | | tomg@boiled.egg.com | between black and white. | | http://www.egg.com/ | | From majordomo-users-owner Tue Sep 12 18:02:41 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA29873 for majordomo-users-outgoing; Tue, 12 Sep 1995 18:02:22 -0700 Received: from uu11.psi.com (uu11.psi.com [38.8.24.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id SAA29864 for ; Tue, 12 Sep 1995 18:02:13 -0700 Received: from andor.com by uu11.psi.com (5.65b/4.0.940727-PSI/PSINet) via UUCP; id AA27626 for ; Tue, 12 Sep 95 20:58:09 -0400 From: Pamela_Stayden@andor.com (Pamela Stayden) Reply-To: Pamela_Stayden@andor.com To: majordomo-users@greatcircle.com Subject: Fwd: Majordomo Date: 12 Sep 1995 17:41:53 GMT Message-Id: <231473118.391335250@andor.com> Organization: AND Interactive Communications Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Brent: I am the Engineering Administrator with And Interactive Communications. Maybe you can help me or direct me in the right direction: I need the following as soon as possible: The compiled version of Wrapper for Major Domo. We are operating on a Sun Netra Operating system is Solaris 2.4 Need it because the Netra doesn't come w/ the proper files to build from C Code. Thank you for your assistance. Pamela Stayden (213)871-8181 (213)871-8282 fax pamela_stayden@andor.com From majordomo-users-owner Wed Sep 13 03:30:12 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id DAA13385 for majordomo-users-outgoing; Wed, 13 Sep 1995 03:13:50 -0700 Received: from isp1.isp.net (isp1.isp.net [204.139.9.12]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id DAA13378 for ; Wed, 13 Sep 1995 03:13:46 -0700 Received: from outsider.bolis.sf-bay.org (bolis.isp.net [204.153.195.10]) by mail.isp.net (8.6.9/8.6.9) with SMTP id DAA20277 for ; Wed, 13 Sep 1995 03:11:16 -0700 Received: from hock.bolis.sf-bay.org by outsider.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0ssoko-0006vUC; Wed, 13 Sep 95 03:09 PDT Received: from amillar by hock.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0ssokV-000UpwC; Wed, 13 Sep 95 03:08 PDT Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: majordomo-users@greatcircle.com (Majordomo user's mailing list) Date: Wed, 13 Sep 1995 02:00:19 -800 Subject: Re: another config (header/footer) question Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On 12 Sep 95 at 14:56, Dave Wolfe wrote: > [ Daniel A. Nichols writes: ] > > > > I have two lists, test and test-digest. > > If I include a footer for the test list like: > > > > message_footer << END > > How to I get that stripped when the digest for test-digest is > > created? It seems to leave it in on EVERY message. > > Then you have to get it in the digest *before* it goes through resend > (which adds the message_footer), i.e. the alias that redirects > messages through resend should also redirect the message to the digest > accumulator. Yuck. The problem with this is that the digest will receive the junk that resend weeds out, such as administrivia checks and posting restrictions. This is, generally speaking, bad. Unfortunately, that leaves no good answer to the original question. A better design would be to have resend invoke digest, based on a list config variable, after the checks but before message mangling. Too many good ideas, never enough time :-) - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: http://metro.turnpike.net/metro/amillar From majordomo-users-owner Wed Sep 13 05:30:51 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id FAA15552 for majordomo-users-outgoing; Wed, 13 Sep 1995 05:24:47 -0700 Received: from cclsun01.let.uva.nl (cclsun01.let.uva.nl [145.18.228.21]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id FAA15545 for ; Wed, 13 Sep 1995 05:24:43 -0700 Received: from cclsun01 (cclsun01.let.uva.nl) by cclsun01.let.uva.nl with SMTP id AA05315 (5.67a/IDA-1.5 for ); Wed, 13 Sep 1995 14:22:31 +0200 Date: Wed, 13 Sep 1995 14:22:31 +0200 (MET DST) From: Yuri Engelhardt X-Sender: yuri@cclsun01 To: majordomo-users@greatcircle.com Subject: creating a sub-list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk How can I restrict subscription to a sub-list to addresses already subscribed to the main list ? I am running a majordomo-list (version 1.93, 525 subscribers), and I would like to start a second list that is intended to be an 'optional supplement' or 'sub-forum' of the first one. Is there any way to prevent people who are NOT on the first list from subscribing to this second list ? I mean: Is there a way to let majordomo restrict open subscription to the second list to addresses that appear in the subscriber-file of the first list ? Any help is very much appreciated. Thanks, Yuri Engelhardt From majordomo-users-owner Wed Sep 13 06:30:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA16639 for majordomo-users-outgoing; Wed, 13 Sep 1995 06:06:40 -0700 Received: from presence.lglobal.com (presence.lglobal.com [204.50.121.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id GAA16632 for ; Wed, 13 Sep 1995 06:06:37 -0700 Received: from presence.lglobal.com (jesse@presence.lglobal.com [204.50.121.2]) by presence.lglobal.com (8.6.12/8.6.12) with SMTP id JAA11785; Wed, 13 Sep 1995 09:13:27 -0400 Date: Wed, 13 Sep 1995 09:13:27 -0400 (EDT) From: Jesse Hirsh To: Tom Glover cc: "Mike St. Vincent" , majordomo-users@GreatCircle.COM Subject: Re: Out of Memory In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk So what am i supposed to do when i'm running bsdi2.0 and wrapper is root with mode 4755 and all, but i'm still getting out of memory error1? @-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@ Jesse Dillan Hirsh Local GlobalAccess Inc. (416)515-7400 @-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@ On Tue, 12 Sep 1995, Tom Glover wrote: > > There is no reference in my majordomo.cf file to seting UID or GID... > > BUT, in my majordomo.cf file (copied from the sample from the tar > > 1.93) it appears that the file is missing data / corrupted at the > > end. Perhaps the distribution is goofed on the sample.cf??? My > > sample.cf ends with: > > <<<<<<< > > > > > > I don't think that's your problem. > > > > Wrapper should be owned by the majordomo user, not by root. However, > > it should have a mode of 4755. > > > > Absolutely not true. In POSIX based systems (like BSD/OS) wrapper must be > owned by root. > > -- > Tom > __________________________________________________________________________ > | "The Egg Domain" | There are lots of shades of grey | > | tomg@boiled.egg.com | between black and white. | > | http://www.egg.com/ | | > > From majordomo-users-owner Wed Sep 13 06:32:42 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA17387 for majordomo-users-outgoing; Wed, 13 Sep 1995 06:27:27 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA17380 for ; Wed, 13 Sep 1995 06:27:23 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA26071 for majordomo-users@greatcircle.com; Wed, 13 Sep 95 06:26:03 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA06751; Wed, 13 Sep 95 06:25:58 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA15490 for majordomo-users@greatcircle.com; Wed, 13 Sep 95 06:25:53 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA17208; Wed, 13 Sep 95 08:25:50 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA17537; Wed, 13 Sep 1995 08:25:48 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509131325.AA17537@miaow.sps.mot.com> Subject: Re: compiling wrapper as other than root To: anewman1@eecs.uic.edu (Aaron Newman) Date: Wed, 13 Sep 1995 08:25:48 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509122323.SAA10204@ernie.eecs.uic.edu> from "Aaron Newman" at Sep 12, 95 06:23:49 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 790 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Aaron Newman writes: ] > > I am on SunOS 4.1.3. Because of the way I have my file system set up, > I cannot compile in the majordomo directory as root (the file system > is mounted and root can't write to it). > > I figured the same thing would be to make sure that the permissions > for group and owner are correct for wrapper (ie set for majordomo). > But when I log onto the system as another > user and run the test program, I do not get the permissions of this > user as I am expecting, I get the permissions of the user I logged in > as. I have read the FAQ a zillion times. What am I missing? Compile as an ordinary user. Install as root. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 13 07:00:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA17948 for majordomo-users-outgoing; Wed, 13 Sep 1995 06:49:26 -0700 Received: from sigma.itu.ch (sigma.itu.ch [156.106.128.30]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id GAA17939 for ; Wed, 13 Sep 1995 06:49:14 -0700 Received: from MR.ITU.CH by ITU.CH (PMDF V4.3-7 #4298) id <01HV8E6LNXY89KOD59@ITU.CH>; Wed, 13 Sep 1995 15:48:25 CET Received: with PMDF-MR; Wed, 13 Sep 1995 14:43:28 CET MR-Received: by mta TIES.MUAS; Relayed; Wed, 13 Sep 1995 14:43:28 +0100 MR-Received: by mta TAU; Relayed; Wed, 13 Sep 1995 14:43:30 +0100 Disclose-recipients: prohibited Date: Wed, 13 Sep 1995 14:43:28 +0100 (CET) From: Jarle Martinsen +41 22 730 5949 Subject: long lines in approve... To: majordomo-users@GreatCircle.COM Message-id: <7828431513091995/A34298/TAU/11996BEB1B00*@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 Sensitivity: Company-Confidential UA-content-id: 11996BEB1B00 X400-MTS-identifier: [;7828431513091995/A34298/TAU] Hop-count: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, When I send an approve back to my majordomo mailserver, sometimes my editor wraps the approve line. And this goes, of course, unnoticed by me. Is there any way I can avoid this in future. Can I escape long lines by the shell backslash? i.e. approve password subscribe list name@mlab.nttdocomo.co.jp \(Yasuo Maruyama) ...or something like that. Any help/information is appreciated. Regards, /jarle Jarle Martinsen International Telecommunication Union (ITU) Place des nations CH-1211 Geneva 20 Switzerland Internet: martinsen@itu.ch X.400: S=martinsen; P=itu; A=arcom; C=ch Voice: +41 22 730 5949 Fax: +41 22 730 5337 From majordomo-users-owner Wed Sep 13 07:02:42 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA18014 for majordomo-users-outgoing; Wed, 13 Sep 1995 06:52:43 -0700 Received: from triton.rdc.puc-rio.br (triton.rdc.puc-rio.br [139.82.34.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA17999 for ; Wed, 13 Sep 1995 06:52:34 -0700 Received: by triton.rdc.puc-rio.br (AIX 3.2/UCB 5.64/4.03) id AA19882; Wed, 13 Sep 1995 10:40:04 -0300 From: poyart@triton.rdc.puc-rio.br (Eduardo Poyart) Message-Id: <9509131340.AA19882@triton.rdc.puc-rio.br> Subject: Re: Test script To: majordomo-users@greatcircle.com Date: Wed, 13 Sep 1995 10:40:04 -0300 (BSC) In-Reply-To: <9509121910.AA14152@miaow.sps.mot.com> from "Dave Wolfe" at Sep 12, 95 02:10:26 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1058 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > When you run the test script, it displays the effective user ID and > effective group ID, as well as the real user ID and real group ID (see > the man pages for chown(1 & 2) for explanations). To be successful, the > euid and ruid must match, as well as the egid and rgid. Additionally, > the uid and gid must be what you specified in the Makefile prior to > building wrapper and must *not* be the uid and gid (if different) of the > current logon. No additional messages from wrapper should be displayed. Ok, what about this error? (Obs: Before you ask, I COMPILED WRAPPER WITH POSIX FLAGS!!!!!) $ ./wrapper test ./wrapper: error setgroups failed errno 1./wrapper: error: recompile with POSIX flags. $ This happens only in the condition that it shouldn't, that is, when I run it other than root or majordom. I'm using AIX/ESA operating system, which is OSF compatible. However, I receive no error when I use Majordomo (when I send mail to majordomo it subscribes and unsubscribes me normally). Thanks again Eduardo Poyart poyart@rdc.puc-rio.br From majordomo-users-owner Wed Sep 13 07:07:23 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA17955 for majordomo-users-outgoing; Wed, 13 Sep 1995 06:49:30 -0700 Received: from snmpmgr.state.tn.us (snmpmgr.state.tn.us [170.142.1.74]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA17941 for ; Wed, 13 Sep 1995 06:49:19 -0700 Received: from langate.tnet.state.tn.us (langate.state.tn.us) by snmpmgr.state.tn.us with SMTP id AA29966 (5.67b/IDA-1.5 for ); Wed, 13 Sep 1995 08:47:58 -0500 Received: from tn01-Message_Server by langate.tnet.state.tn.us with Novell_GroupWise; Wed, 13 Sep 1995 08:52:48 -0500 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 13 Sep 1995 08:47:02 -0500 From: Wade Williams To: hpux-admin@cv.ruu.nl, majordomo-users@greatcircle.com Subject: Majordomo on HP-UX Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've successfully installed Majordomo 1.93 on HP-UX 9.03 on an HP 9000/715. To do so, I had to make some source changes and I wanted to be sure that others using HP-UX had found the same thing. If so, I'll distribute the necessary changes to the Majordomo-workers mailing list so they may be included in the next release. What I found was: A) HP-UX is POSIX compliant and Majordomo should be compiled with the POSIX options. B) HP-UX does not support the setuid() and setgid() calls to allow wrapper to setuid unless the group in which Majordomo is in has been granted the SETRUGID privilege (via the setprivgrp command). C) If users on your UNIX system are trying to use Majordomo, wrapper will try to setuid to their user ID. This would mean that setuid() will fail unless your generic users group also has the SETRUGID privilege set. That's probably unacceptable to most. D) To avoid the necessity of both B and C, one can use the setresuid() and setresgid() calls instead of setuid and setgid. Has anyone else found the same situation? If you didn't figure out D, did you at least find parts B&C to be true? Again, if the experience of others agrees with my own, I'll submit the changes to the Majordomo authors for inclusion into the next version. Thanks, Wade Williams wwilliams@mail.state.tn.us From majordomo-users-owner Wed Sep 13 07:30:32 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA19255 for majordomo-users-outgoing; Wed, 13 Sep 1995 07:28:30 -0700 Received: from eipipeline.ei.org (eipipeline.ei.org [192.55.120.104]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id HAA19247 for ; Wed, 13 Sep 1995 07:28:26 -0700 Received: (from shevett@localhost) by eipipeline.ei.org (8.6.12/8.6.12) id KAA28237; Wed, 13 Sep 1995 10:22:14 -0400 Date: Wed, 13 Sep 1995 10:22:13 -0400 (EDT) From: Dave Shevett To: majordomo-users@greatcircle.com Subject: MARS NEEDS WRAPPER. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk (well that and women...) Well, really, mars doesn't need wrapper. Hood does. And hood can compile wrapper (hood being a Solaris 2.4 Sparc 20), both with gcc, and with the sun C compiler, but when it runs, I get 'Segmentation fault'. It doesn't core, and it does do what its supposed to do (at least as far as responding to a 'ghelp' message). So... methinks ah ain't compilin it right. Someone got a Solaris binary of wrapper they cann uuencode or mime-up and send to me? Muchos appreciative. THis is MD 1.93, btw. ---------------------------------------------------------------------------- Dave Shevett On Contract on the Pipeline Project at shevett@ei.org Engineering Information Hoboken, NJ (h) 908-940-2689 -- (w) 201-216-8500 x694 From majordomo-users-owner Wed Sep 13 07:32:42 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA19303 for majordomo-users-outgoing; Wed, 13 Sep 1995 07:29:03 -0700 Received: from list.cdc.gov (list.cdc.gov [158.111.3.20]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id HAA19293 for ; Wed, 13 Sep 1995 07:28:59 -0700 Received: (from gln1@localhost) by list.cdc.gov (8.6.12/8.6.12) id KAA00380; Wed, 13 Sep 1995 10:24:36 -0400 Date: Wed, 13 Sep 1995 10:24:35 -0400 (EDT) From: Lee Nelson To: Muhammad Salman Mughal cc: majordomo-users@GreatCircle.COM Subject: Re: moderated lists In-Reply-To: <199509110219.VAA08247@earth.sparco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Sun, 10 Sep 1995, Muhammad Salman Mughal wrote: > Hi all, > > I am trying to do the following things: > > * I want the list to be moderated, and only want someone@somehere > to be allowed to post articles to the mailing list. I changed > "moderated = no" to "moderate = yes" in listname.config. It does > sends the orignal mail back to the sender with a subject saying > "Approval Required". Where do I specify who can post to the mailing > list? You don't. Even if the list is moderated anyone who knows the password to post to the list can do so. In theory no one but the list moderator would know the password so only the moderator could post to it. BTW, the moderator can put the approved header on any posted article when it is first sent to Majordomo in order to avoid the bounce/approval process. > > * I have this experimental list, I defined myself as the listowner. > Now, I want another person to be the listowner too. So, I defined > the following aliases in /etc/aliases, but they never worked. I keep > getting "approval" requests for subscription and unsubscription; and > errors related to the mailing list to my address only. There is a > section in the README file and I tried to follow it, but I guess I > didn't set it up correctly. > > "test-owners" is the name of the file where I stored 2 email address, and > it's lying in /usr/local/majordomo/lists/ directory. > -------------------------------------------------------------------------- Very easy. To have several owners of a list just specify the alias for the owner as follows (seperating each owners address with a comma) list-owner: person1@company.com, person2@company.com ------------------------------------------------------------------------------ Lee Nelson, Network Technology Branch, Information Resources Management Office U.S. Centers for Disease Control and Prevention (CDC) 1600 Clifton Road, N.E., MS-C06 Atlanta, GA 30333 USA Phone: (404) 639-2494 E-Mail: gln1@ntb9.cdc.gov or Compuserve: 76507,2240 ------------------------------------------------------------------------------ From majordomo-users-owner Wed Sep 13 08:02:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA20544 for majordomo-users-outgoing; Wed, 13 Sep 1995 07:55:42 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA20537 for ; Wed, 13 Sep 1995 07:55:38 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA04633 for majordomo-users@greatcircle.com; Wed, 13 Sep 95 07:54:21 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA09479; Wed, 13 Sep 95 07:54:20 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA22909 for majordomo-users@greatcircle.com; Wed, 13 Sep 95 07:54:18 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA18921; Wed, 13 Sep 95 09:54:15 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA15419; Wed, 13 Sep 1995 09:54:13 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509131454.AA15419@miaow.sps.mot.com> Subject: Re: Test script To: poyart@triton.rdc.puc-rio.br (Eduardo Poyart) Date: Wed, 13 Sep 1995 09:54:13 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <9509131340.AA19882@triton.rdc.puc-rio.br> from "Eduardo Poyart" at Sep 13, 95 10:40:04 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1324 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Eduardo Poyart writes: ] > [ I (Dave Wolfe) wrote: ] > > No additional messages from wrapper should be displayed. > > Ok, what about this error? > > (Obs: Before you ask, I COMPILED WRAPPER WITH POSIX FLAGS!!!!!) > > $ ./wrapper test > ./wrapper: error setgroups failed errno 1./wrapper: error: recompile with > POSIX flags. > $ > > This happens only in the condition that it shouldn't, that is, when I run > it other than root or majordom. Extracted from /usr/include/sys/errno.h: #define EPERM 1 /* Operation not permitted */ Extracted from the setgroups(2) man page: EPERM A group ID in the GroupIDSet parameter is not presently in the supplementary group ID, and the invoker does not have root user authority. So either you have wrapper installed incorrectly (not setuid root) or (if I understand what the EPERM description is talking about), root doesn't have W_GID listed as a supplementary gid in /etc/group. Since wrapper works when run from a root logon, I suspect the supplementary gid stuff is just noise. Be very sure that wrapper has mode 04755 and is owned by root, e.g.: -r-sr-xr-x ... root majordom ... wrapper ^ -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 13 08:04:15 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA19418 for majordomo-users-outgoing; Wed, 13 Sep 1995 07:32:59 -0700 Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id HAA19409 for ; Wed, 13 Sep 1995 07:32:55 -0700 Received: by night.primate.wisc.edu; id JAA10235; 8.6.10/41.8; Wed, 13 Sep 1995 09:31:35 -0500 From: Software Development Message-Id: <199509131431.JAA10235@night.primate.wisc.edu> Subject: Re: Majordomo on HP-UX To: wwilliams@mail.state.tn.us (Wade Williams) Date: Wed, 13 Sep 1995 09:31:35 -0500 (CDT) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Wade Williams" at Sep 13, 95 08:47:02 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1911 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > I've successfully installed Majordomo 1.93 on HP-UX 9.03 on an HP > 9000/715. My comments below pertain to 9.05. > To do so, I had to make some source changes and I wanted to be sure > that others using HP-UX had found the same thing. If so, I'll > distribute the necessary changes to the Majordomo-workers mailing > list so they may be included in the next release. > > What I found was: > > A) HP-UX is POSIX compliant and Majordomo should be compiled with > the POSIX options. That's what I did. > > B) HP-UX does not support the setuid() and setgid() calls to allow > wrapper to setuid unless the group in which Majordomo is in has been > granted the SETRUGID privilege (via the setprivgrp command). My wrapper has user/group ownerships of root/majordom and setuid root. I have W_UID and W_GID in the Makefile set to 1 (daemon) and 5 (daemon). I didn't have to do anything special to wrapper with setprivgrp. My getprivgrp output is: % getprivgrp global privileges: CHOWN > C) If users on your UNIX system are trying to use Majordomo, wrapper > will try to setuid to their user ID. This would mean that setuid() Why will it do that? In wrapper.c, it looks to me like it will try to set to POSIX_UID and POSIX_GID if you compile with POSIX flags. > will fail unless your generic users group also has the SETRUGID > privilege set. That's probably unacceptable to most. > > D) To avoid the necessity of both B and C, one can use the > setresuid() and setresgid() calls instead of setuid and setgid. I didn't do this. > Has anyone else found the same situation? If you didn't figure out > D, did you at least find parts B&C to be true? Nope. If I remember correctly, though, I did have to do some messing around with directory ownerships before things worked correctly. I have the directories in /usr/spool/majordom set to daemon/majordom. Paul DuBois dubois@primate.wisc.edu From majordomo-users-owner Wed Sep 13 08:20:54 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA19397 for majordomo-users-outgoing; Wed, 13 Sep 1995 07:32:34 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA19390 for ; Wed, 13 Sep 1995 07:32:31 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA02395 for majordomo-users@greatcircle.com; Wed, 13 Sep 95 07:31:12 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA08801; Wed, 13 Sep 95 07:31:11 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA20826 for majordomo-users@greatcircle.com; Wed, 13 Sep 95 07:31:09 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA18663; Wed, 13 Sep 95 09:31:08 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA14094; Wed, 13 Sep 1995 09:31:04 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509131431.AA14094@miaow.sps.mot.com> Subject: Re: Out of Memory To: uunet!lglobal.com!jesse (Jesse Hirsh) Date: Wed, 13 Sep 1995 09:31:04 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Jesse Hirsh" at Sep 13, 95 09:13:27 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1350 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Jesse Hirsh writes: ] > > So what am i supposed to do when i'm running bsdi2.0 and wrapper is root > with mode 4755 and all, but i'm still getting out of memory error1? > > On Tue, 12 Sep 1995, Tom Glover wrote: > > > > There is no reference in my majordomo.cf file to seting UID or GID... > > > BUT, in my majordomo.cf file (copied from the sample from the tar > > > 1.93) it appears that the file is missing data / corrupted at the > > > end. Perhaps the distribution is goofed on the sample.cf??? My > > > sample.cf ends with: > > > <<<<<<< > > > > > > > > > I don't think that's your problem. > > > > > > Wrapper should be owned by the majordomo user, not by root. However, > > > it should have a mode of 4755. > > > > > > > Absolutely not true. In POSIX based systems (like BSD/OS) wrapper must be > > owned by root. I don't think all the attributions have been included and I don't remember who asked the original message or the first response above, but I don't think many (anyone?) understood what was being asked. However, for BSD systems, wrapper should be owned by W_USER and W_GROUP, as defined in Makefile, and installed mode 06755. Root ownership and mode 04755 is for POSIX systems. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 13 08:31:20 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA21938 for majordomo-users-outgoing; Wed, 13 Sep 1995 08:27:24 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA21930 for ; Wed, 13 Sep 1995 08:27:21 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA07966 for majordomo-users@greatcircle.com; Wed, 13 Sep 95 08:25:56 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA10357; Wed, 13 Sep 95 08:25:51 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA25640 for majordomo-users@greatcircle.com; Wed, 13 Sep 95 08:25:49 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA19151; Wed, 13 Sep 95 10:25:46 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA16024; Wed, 13 Sep 1995 10:25:44 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509131525.AA16024@miaow.sps.mot.com> Subject: Re: MARS NEEDS WRAPPER. To: shevett@ei.org (Dave Shevett) Date: Wed, 13 Sep 1995 10:25:43 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Dave Shevett" at Sep 13, 95 10:22:13 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1182 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Dave Shevett writes: ] > > Well, really, mars doesn't need wrapper. Hood does. And hood can > compile wrapper (hood being a Solaris 2.4 Sparc 20), both with gcc, and > with the sun C compiler, but when it runs, I get 'Segmentation fault'. > It doesn't core, and it does do what its supposed to do (at least as far > as responding to a 'ghelp' message). > > So... methinks ah ain't compilin it right. Someone got a Solaris binary > of wrapper they cann uuencode or mime-up and send to me? If it responds to a help request, then wrapper isn't getting the segmentation fault, Perl is. You have permission problems somewhere, probably Mj doesn't have write permission in the lists or log file directory (or maybe you didn't create a log file, or maybe Mj doesn't have write permission for the log file, or maybe you don't have at least patch 1e of Perl 5 (if you have Perl 5), or maybe you didn't install wrapper correctly, or maybe ...). If the patch level of Perl 5 is the problem, get all the patches through 1m while you're at it. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 13 09:01:30 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA23629 for majordomo-users-outgoing; Wed, 13 Sep 1995 08:59:36 -0700 Received: from ix4.ix.netcom.com (ix4.ix.netcom.com [199.182.120.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id IAA23614 for ; Wed, 13 Sep 1995 08:59:32 -0700 Received: from LOCALNAME by ix4.ix.netcom.com (8.6.12/SMI-4.1/Netcom) id IAA23495; Wed, 13 Sep 1995 08:58:14 -0700 Date: Wed, 13 Sep 1995 08:58:14 -0700 Message-Id: <199509131558.IAA23495@ix4.ix.netcom.com> X-Sender: mcobgyn@popd.ix.netcom.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: "Michael J. Chmielewski" Subject: Re: long lines in approve... Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have had the same problem using Pine. You must type right up to last character and hit the return manually to start on the next line and continue your approve command. If I allow the whole final character string to be wrapped, it is not recognized on the second line and I get an error message. This is a function of the Pine interface I use and imagine that the problem is editor specific. At 02:43 PM 9/13/95 +0100, you wrote: >Hi, > >When I send an approve back to my majordomo mailserver, >sometimes my editor wraps the approve line. And this >goes, of course, unnoticed by me. > >Is there any way I can avoid this in future. Can I >escape long lines by the shell backslash? i.e. > >approve password subscribe list name@mlab.nttdocomo.co.jp >\(Yasuo Maruyama) > >...or something like that. > >Any help/information is appreciated. > >Regards, >/jarle > >Jarle Martinsen >International Telecommunication Union (ITU) >Place des nations >CH-1211 Geneva 20 >Switzerland > >Internet: martinsen@itu.ch >X.400: S=martinsen; P=itu; A=arcom; C=ch >Voice: +41 22 730 5949 >Fax: +41 22 730 5337 > > > > From majordomo-users-owner Wed Sep 13 09:02:46 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA23452 for majordomo-users-outgoing; Wed, 13 Sep 1995 08:52:25 -0700 Received: from triton.rdc.puc-rio.br (triton.rdc.puc-rio.br [139.82.34.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA23445 for ; Wed, 13 Sep 1995 08:52:15 -0700 Received: by triton.rdc.puc-rio.br (AIX 3.2/UCB 5.64/4.03) id AA35841; Wed, 13 Sep 1995 12:39:47 -0300 From: poyart@triton.rdc.puc-rio.br (Eduardo Poyart) Message-Id: <9509131539.AA35841@triton.rdc.puc-rio.br> Subject: Re: Test script - setluid To: majordomo-users@greatcircle.com Date: Wed, 13 Sep 1995 12:39:45 -0300 (BSC) Cc: poyart@triton.rdc.puc-rio.br (Eduardo Poyart) In-Reply-To: <9509131520.AA27637@triton.rdc.puc-rio.br> from "Eduardo Poyart" at Sep 13, 95 12:20:30 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1408 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > [ME] > What the hell is setluid? Let's see.. > > NAME > setluid - Sets login user ID > > DESCRIPTION > The setluid() function sets the Login User ID (LUID) of the > calling process. The LUID should be set at login, batch > job, daemon, or initialization script start. Only a process > with the setprocident effective privilege can set the LUID. > Once set, it cannot be reset under any circumstances. > > Until the LUID is set, the following functions fail: > setuid(), setreuid(), setgid(), setregid(), and setgroups(). > This ensures that the LUID is set before any identity > changes in the other IDs. > > Wow! Good! This would never be possible without your help pointing my way > through the setgroups man page, thanks a lot. I'll try to write some code > in wrapper.c to call setluid. Perhaps it should be implemented in the next > version... I guess it is something required by OSF systems. [ME AGAIN] Well, I checked and setluid didn't work in wrapper.c. It returned EPERM, which is: [EPERM] The LUID has already been set for this process or any ancestors of this process. The process did not have the requisite privileges. I'm stuck again... Have anyone used this function? Regards, Eduardo Poyart poyart@rdc.puc-rio.br From majordomo-users-owner Wed Sep 13 09:10:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA22449 for majordomo-users-outgoing; Wed, 13 Sep 1995 08:33:45 -0700 Received: from triton.rdc.puc-rio.br (triton.rdc.puc-rio.br [139.82.34.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA22433 for ; Wed, 13 Sep 1995 08:33:33 -0700 Received: by triton.rdc.puc-rio.br (AIX 3.2/UCB 5.64/4.03) id AA27637; Wed, 13 Sep 1995 12:20:31 -0300 From: poyart@triton.rdc.puc-rio.br (Eduardo Poyart) Message-Id: <9509131520.AA27637@triton.rdc.puc-rio.br> Subject: Re: Test script To: david_wolfe@risc.sps.mot.com Date: Wed, 13 Sep 1995 12:20:30 -0300 (BSC) Cc: majordomo-users@greatcircle.com, poyart@triton.rdc.puc-rio.br (Eduardo Poyart) In-Reply-To: <9509131454.AA15419@miaow.sps.mot.com> from "Dave Wolfe" at Sep 13, 95 09:54:13 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2785 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > [ME] > > (Obs: Before you ask, I COMPILED WRAPPER WITH POSIX FLAGS!!!!!) > > > > $ ./wrapper test > > ./wrapper: error setgroups failed errno 1./wrapper: error: recompile with > > POSIX flags. > [YOU (david_wolfe@risc.sps.mot.com)] > Extracted from /usr/include/sys/errno.h: > > #define EPERM 1 /* Operation not permitted */ Mine: #define EPERM 1 /* Not owner */ > Extracted from the setgroups(2) man page: > > EPERM A group ID in the GroupIDSet parameter is not presently in > the supplementary group ID, and the invoker does not have root > user authority. > > So either you have wrapper installed incorrectly (not setuid root) or > (if I understand what the EPERM description is talking about), root > doesn't have W_GID listed as a supplementary gid in /etc/group. As you suggested, I put the supplementary group majordom in root in /etc/group: majordom:*:54:majordom,root It still doesn't work. > Since wrapper works when run from a root logon, I suspect the supplementary > gid stuff is just noise. Be very sure that wrapper has mode 04755 and is > owned by root, e.g.: > > -r-sr-xr-x ... root majordom ... wrapper > ^ It's already that way. I tried too: -rwsr-sr-x ... root system ... wrapper and -rwsr-sr-x ... root majordom ... wrapper Doesn't work... But look what I found at the setgroups man page: DESCRIPTION (...) The process's login user ID must be set with setluid() before this call will succeed. This function fails unless the invoking process has the setprocident effective privilege. ERRORS [EPERM] The caller does not have the appropriate system privilege. What the hell is setluid? Let's see.. NAME setluid - Sets login user ID DESCRIPTION The setluid() function sets the Login User ID (LUID) of the calling process. The LUID should be set at login, batch job, daemon, or initialization script start. Only a process with the setprocident effective privilege can set the LUID. Once set, it cannot be reset under any circumstances. Until the LUID is set, the following functions fail: setuid(), setreuid(), setgid(), setregid(), and setgroups(). This ensures that the LUID is set before any identity changes in the other IDs. Wow! Good! This would never be possible without your help pointing my way through the setgroups man page, thanks a lot. I'll try to write some code in wrapper.c to call setluid. Perhaps it should be implemented in the next version... I guess it is something required by OSF systems. Best regards Eduardo Poyart poyart@rdc.puc-rio.br From majordomo-users-owner Wed Sep 13 13:30:17 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA05434 for majordomo-users-outgoing; Wed, 13 Sep 1995 13:28:13 -0700 Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA05427 for ; Wed, 13 Sep 1995 13:28:11 -0700 Received: from cs.rpi.edu by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-950602) id NAA19723; Wed, 13 Sep 1995 13:20:34 -0700 Received: from ro.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA13812; Wed, 13 Sep 1995 16:25:05 -0400 (wiseb from ro.cs.rpi.edu) Message-Id: <199509132025.AA13812@cs.rpi.edu> X-Mailer: exmh version 1.6.1 5/23/95 To: majordomo-users@greatcircle.com Subject: Bounced Mails Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Sep 1995 16:25:02 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Okay, I think I have the bounces set up right now. I use resend so that all messages have the Sender as owner-listname So, whenever a bounce occurs I get the MAILER DAEMON messages. Is this all I get? I thought a BOUNCE message was generated for the offending address? Do I still have to analyze the mailer daemon messages for the offending addresses and then use bounce to move that address to the bounces list? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Wed Sep 13 19:32:16 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id TAA17536 for majordomo-users-outgoing; Wed, 13 Sep 1995 19:17:56 -0700 Received: from ncrhub1.ATTGIS.COM (h192-127-251-3.ATTGIS.COM [192.127.251.3]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id TAA17529 for ; Wed, 13 Sep 1995 19:17:53 -0700 Received: from ncrhub4 by ncrhub1.ATTGIS.COM id aa14694; 13 Sep 95 22:16 EDT Received: by ncrhub4.ATTGIS.COM; 13 Sep 95 22:15:38 EDT Received: by ncr-sd.SanDiegoCA.ATTGIS.COM; 13 Sep 95 19:16:07 PDT X-Sender: bhoule@www.sandiegoca.attgis.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: Bill Houle Subject: moderated+nonmoderated=? Date: Wed, 13 Sep 95 22:15:00 EDT Message-ID: <9509132216.aa14694@ncrhub1.ATTGIS.COM> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk OK, I admit it. I've been too lazy to actually test this myself: If I send to 2 addresses, one of them a moderated list, one message will go to the unmoderated recipient and the other will be BOUNCEd to the list-owner. The owner then approves the message. What happens? Does recip#1 get a 2nd copy of the same message when resend posts the approved mail? -- Bill Houle Bill.Houle@SanDiegoCA.ATTGIS.COM AT&T Global Information Solutions (619) 485-4027 From majordomo-users-owner Wed Sep 13 23:00:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA23284 for majordomo-users-outgoing; Wed, 13 Sep 1995 22:39:27 -0700 Received: from sigma.itu.ch (sigma.itu.ch [156.106.128.30]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id WAA23277 for ; Wed, 13 Sep 1995 22:39:23 -0700 Received: from MR.ITU.CH by ITU.CH (PMDF V4.3-7 #4298) id <01HV9BDG8YFK9KOQ7P@ITU.CH>; Thu, 14 Sep 1995 07:38:40 CET Received: with PMDF-MR; Thu, 14 Sep 1995 06:32:50 CET MR-Received: by mta TIES.MUAS; Relayed; Thu, 14 Sep 1995 06:32:50 +0100 MR-Received: by mta TAU; Relayed; Thu, 14 Sep 1995 06:32:52 +0100 Disclose-recipients: prohibited Date: Thu, 14 Sep 1995 06:32:50 +0100 (CET) From: Jarle Martinsen +41 22 730 5949 Subject: Re: long lines in approve... In-reply-to: <199509131558.IAA23495@ix4.ix.netcom.com> To: majordomo-users Message-id: <7050320714091995/A38508/TAU/119971E03100*@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 Sensitivity: Company-Confidential UA-content-id: 119971E03100 X400-MTS-identifier: [;7050320714091995/A38508/TAU] Hop-count: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >> This is a function of the Pine interface I use and imagine that the problem is >> editor specific. Yes, I agree - that's why I was looking for.... >Is there any way I can avoid this in future. Can I >escape long lines by the shell backslash? i.e. > >approve password subscribe list name@mlab.nttdocomo.co.jp >\(Yasuo Maruyama) > >...or something like that. > If this is not possible, is there any other workaround...? Regards, /jarle From majordomo-users-owner Thu Sep 14 00:00:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id XAA24994 for majordomo-users-outgoing; Wed, 13 Sep 1995 23:53:58 -0700 Received: from minerva.ibernet.es (minerva.ibernet.es [194.179.1.100]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id XAA24987 for ; Wed, 13 Sep 1995 23:53:53 -0700 Received: from encomix.es (root@encomix.es [194.30.5.1]) by minerva.ibernet.es (8.6.12/8.6.9) with ESMTP id IAA27432 for ; Thu, 14 Sep 1995 08:53:48 +0200 Received: (from uucp@localhost) by encomix.es (8.6.11/8.6.12) with UUCP id IAA27364 for majordomo-users@greatcircle.com; Thu, 14 Sep 1995 08:50:46 +0200 Received: (from adriano@localhost) by tp.encomix.es (8.6.12/8.6.12) id IAA12503 for majordomo-users@greatcircle.com; Thu, 14 Sep 1995 08:18:22 +0100 From: Adriano Garcia Message-Id: <199509140718.IAA12503@tp.encomix.es> Subject: Mailer prog died To: majordomo-users@greatcircle.com Date: Thu, 14 Sep 1995 08:18:22 +0100 (GMT+0100) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 257 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I just installed majordomo and when i send a message to it, i get the correct answer but allways get a message "Mailer prog died with signal 13" and sendmail sends messages until i delete the mqueue files. Why my mailer prog dies? adriano@tp.encomix.es From majordomo-users-owner Thu Sep 14 04:00:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id DAA01152 for majordomo-users-outgoing; Thu, 14 Sep 1995 03:51:54 -0700 Received: from newlink.atlanta.com (newlink.atlanta.com [155.229.17.50]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id DAA01133 for ; Thu, 14 Sep 1995 03:51:43 -0700 Received: from apollo (admin.southlink.com [168.27.193.17]) by newlink.atlanta.com (8.6.9/8.6.9) with SMTP id GAA18186 for ; Thu, 14 Sep 1995 06:47:33 -0400 Message-Id: <199509141047.GAA18186@newlink.atlanta.com> X-Sender: larry@southlink.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 14 Sep 1995 06:50:55 -0500 To: majordomo-users@GreatCircle.COM From: Larry Morrow Subject: Re: long lines in approve... Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 06:32 AM 9/14/95 +0100, Jarle wrote: > >>> This is a function of the Pine interface I use and imagine that the problem >is >>> editor specific. > >Yes, I agree - that's why I was looking for.... > >>Is there any way I can avoid this in future. Can I >>escape long lines by the shell backslash? i.e. >> >>approve password subscribe list name@mlab.nttdocomo.co.jp >>\(Yasuo Maruyama) >> >>...or something like that. >> > >If this is not possible, is there any other workaround...? > >Regards, >/jarle > Can you provide more information. Which editor is pine setup to use? If it happens to be joe, then you can use "CTRL-T W" to turn off line wrapping. Or you can change the editor based on what's available on your system. You can always use "vi", but it is not as easy to use. Larry :-) Larry J. Morrow Director, Georgia Operations NewLink Global Engineering Corporation voice: (404) 502-8144 fax: (404) 502-9010 page: (404) 689-6029 newlink@mindspring.com From majordomo-users-owner Thu Sep 14 06:00:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id FAA03314 for majordomo-users-outgoing; Thu, 14 Sep 1995 05:42:23 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id FAA03306 for ; Thu, 14 Sep 1995 05:42:20 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA17084 for majordomo-users@greatcircle.com; Thu, 14 Sep 95 05:41:03 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA29525; Thu, 14 Sep 95 05:40:59 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA16284 for majordomo-users@greatcircle.com; Thu, 14 Sep 95 05:40:58 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA24193; Thu, 14 Sep 95 07:40:56 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA12151; Thu, 14 Sep 1995 07:40:54 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509141240.AA12151@miaow.sps.mot.com> Subject: Re: Mailer prog died To: adriano@tp.encomix.es (Adriano Garcia) Date: Thu, 14 Sep 1995 07:40:54 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509140718.IAA12503@tp.encomix.es> from "Adriano Garcia" at Sep 14, 95 08:18:22 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1203 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Adriano Garcia writes: ] > > I just installed majordomo and when i send a message to it, i get the > correct answer but allways get a message "Mailer prog died with signal 13" > and sendmail sends messages until i delete the mqueue files. > > Why my mailer prog dies? Excerpt from /usr/include/sys/signal.h: #define SIGPIPE 13 /* write on a pipe with no one to read it */ Apparently majordomo is dying without reading the stdin pipe from sendmail. If you (or root or postmaster) aren't getting any mail about the failure that indicates more specific reasons for Mj dying, you could probably get more information by doing the following: echo help | /usr/lib/sendmail -v majordomo (Your actual path to sendmail may vary.) If I had to guess, I'd say wrapper isn't executable by sendmail or that Perl isn't where the #! path tries to execute it from, i.e. check the first line of the majordomo (and other) scripts. Don't forget search (x) permissions on wrapper's directory (and all directories leading to it) for sendmail when examining permissions. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Thu Sep 14 07:02:44 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA06158 for majordomo-users-outgoing; Thu, 14 Sep 1995 07:00:20 -0700 Received: from leibniz.math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id HAA06103 for ; Thu, 14 Sep 1995 07:00:04 -0700 Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by leibniz.math.psu.edu (8.6.12/8.6.9) with ESMTP id JAA05939; Thu, 14 Sep 1995 09:58:21 -0400 Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.6.12/8.6.9) with ESMTP id JAA01521; Thu, 14 Sep 1995 09:58:20 -0400 Message-Id: <199509141358.JAA01521@augusta.math.psu.edu> X-Mailer: exmh version 1.6.2 7/18/95 To: Bowden Wise cc: majordomo-users@GreatCircle.COM Subject: Re: Bounced Mails In-reply-to: Your message of "Wed, 13 Sep 1995 16:25:02 EDT." <199509132025.AA13812@cs.rpi.edu> References: <199509132025.AA13812@cs.rpi.edu> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Sep 1995 09:58:20 -0400 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <199509132025.AA13812@cs.rpi.edu>, Bowden Wise writes: >Okay, I think I have the bounces set up right now. I use resend so >that all messages have the Sender as owner-listname So, whenever a >bounce occurs I get the MAILER DAEMON messages. > >Is this all I get? Yep > I thought a BOUNCE message was generated for the >offending address? How can it? the bounce message isn't generated by majordomo -- it doesn't even pass through majordomo. Bounce messages are generated by other sites' mailers. > Do I still have to analyze the mailer daemon >messages for the offending addresses and then use bounce to move >that address to the bounces list? Yes. --Dave From majordomo-users-owner Thu Sep 14 10:01:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA14576 for majordomo-users-outgoing; Thu, 14 Sep 1995 09:51:39 -0700 Received: from campbell-emh4.army.mil (CAMPBELL-EMH4.ARMY.MIL [150.152.31.3]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA14548 for ; Thu, 14 Sep 1995 09:51:28 -0700 Date: Thu, 14 Sep 1995 11:50:02 -0500 (CDT) From: CW2 Rob Miletich To: majordomo-users@GreatCircle.COM Subject: Re: long lines in approve... In-Reply-To: <199509141047.GAA18186@newlink.atlanta.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 14 Sep 1995, Larry Morrow wrote: > At 06:32 AM 9/14/95 +0100, Jarle wrote: > > > >>> This is a function of the Pine interface I use and imagine that the problem > >is > >>> editor specific. I use pine for approves too... and yes, there is an allow long lines option in pine, but even if it wraps, so what? Use the "\" character to escape the line break. example: approve PASSWD subscribe \ joe-bob@greatbig.site.edu \ (Briggs JB) who listname +-------------------------------------------------------------------+ | CW2 Rob Miletich CSSAMO - 101st Support Group (Corps), FTCKY | | mileticr@campbell-emh4.army.mil handle=rm401 DSN 635-7293/4679 | +-------------------------------------------------------------------+ AAAAAA - American Association Against Acronym Abuse Anonymous From majordomo-users-owner Thu Sep 14 11:32:44 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA20103 for majordomo-users-outgoing; Thu, 14 Sep 1995 11:31:57 -0700 Received: from tango.rahul.net (tango.rahul.net [192.160.13.5]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA20096 for ; Thu, 14 Sep 1995 11:31:53 -0700 Received: from bolero.rahul.net by tango.rahul.net with SMTP id AA28259 (5.67b8/IDA-1.5 for ); Thu, 14 Sep 1995 11:30:33 -0700 Received: by bolero.rahul.net id AA09809 (5.67b8/IDA-1.5 for majordomo-users@greatcircle.com); Thu, 14 Sep 1995 11:30:32 -0700 Date: Thu, 14 Sep 1995 11:30:32 -0700 (PDT) From: Jeff Schneiter Subject: creating a simple list 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 am looking to create a very simple mailing list, one that only has two functions - give the user back a list of files, allow the user to get one of those files. Say the user sent a first message to the mailing list "info" and my list automatically responds with the list of archive files. Then the user sends a message to "info" requesting one of those files, or more (?). I want the user to avoid sending a message to "majordomo" like this: index info What can be done to achieve this? info:"|/usr/local/majordomo/wrapper majordomo -l info" sends an intro type message; can I change that to send an index with a different intro? How then can the user send "info" the command: get info I am assuming that I could always write another perl script to pass to wrapper, but I don't have the time for that. Thanks for any pointers, jeff From majordomo-users-owner Thu Sep 14 14:00:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA28085 for majordomo-users-outgoing; Thu, 14 Sep 1995 13:38:10 -0700 Received: from cclsun01.let.uva.nl (cclsun01.let.uva.nl [145.18.228.21]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA28043 for ; Thu, 14 Sep 1995 13:37:59 -0700 Received: from cclsun01 (cclsun01.let.uva.nl) by cclsun01.let.uva.nl with SMTP id AA06496 (5.67a/IDA-1.5 for ); Thu, 14 Sep 1995 22:35:57 +0200 Date: Thu, 14 Sep 1995 22:35:57 +0200 (MET DST) From: Yuri Engelhardt X-Sender: yuri@cclsun01 To: majordomo-users@greatcircle.com Subject: subscribers-file, opening a 'cafe' Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello everybody, I have received no reaction to my first posting, so please forgive me for trying it once more: I am running and moderating a majordomo-1.93-list (525 subscribers) called 'InfoDesign', and I have the following, not yet implemented fantasy (this is what I WOULD then post on my InfoDesign list): > ANNOUNCEMENT: Opening of the InfoDesign-Cafe > > > As an addition to InfoDesign, I am happy to now announce the > opening of the 'InfoDesign-Cafe' ! > > While: - 'InfoDesign' itself remains a moderated forum > for general issues of information design > (graphic design aspects, cognitive aspects, > theoretical aspects, plus announcements), > > the new: - 'InfoDesign-Cafe' is a space within InfoDesign > for unmoderated informal exchange. Just to give > one example: specific technological aspects of > information design work fall outside the defined > scope of the moderated InfoDesign forum, but may > freely be discussed in the InfoDesign-Cafe. > > Technically, the InfoDesign-Cafe is a mailing list that is > a sub-list of the InfoDesign list. In other words, the > InfoDesign-Cafe is an optional supplement (sub-forum) of > InfoDesign. In order to subscribe to ... So far my fantasy. I know that not all of my 525 subscribers would subscribe to the 'Cafe'. My problem now is that after a while, new people might be attracted to the 'Cafe'-list without having subscribed to the 'main'-list, while it is important to me that all messages and announcements posted on the main-list will also reach ALL people on the Cafe-list. Simply chosing to post the main-list messages also to the 'Cafe'-list is not an option, because most (preferably all) 'Cafe'-subscribers ARE also on the main-list, and would then receive all 'main'-messages TWICE. The remaining option is: prevent new people from subscribing to the 'Cafe' without first subscribing to the main-list. So the question becomes: Is there a way to restrict open subscription to the 'Cafe'-list to addresses that appear in the subscriber-file of the main-list ? I would be grateful for any help ! Thanks a lot, Yuri Engelhardt From majordomo-users-owner Thu Sep 14 15:30:33 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA05154 for majordomo-users-outgoing; Thu, 14 Sep 1995 15:27:11 -0700 Received: from homer.louisville.edu (homer.louisville.edu [136.165.1.20]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA05140 for ; Thu, 14 Sep 1995 15:27:00 -0700 Received: by homer.louisville.edu; (5.65v3.0/1.1.8.2/03Jun94-0854PM) id AA30956; Thu, 14 Sep 1995 18:25:43 -0400 From: "Jason A. Dour" Message-Id: <9509142225.AA30956@homer.louisville.edu> Subject: Munged subscriber files... To: majordomo-users@greatcircle.com Date: Thu, 14 Sep 1995 18:25:42 -0500 (EDT) X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 756 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Recently, I was notified that one of the mailing lists I run had not been working. I found out later that the subscriber file had been completely erased by the system. I am the only person with priveldges to those files (other than user majordom, of course)...and I did not delete them. This happened roughly around the first of September. Has anyone had anything similar happen? Ever? Any advice on how to keep this from happening again? Jason +- Jason A. Dour ----------------------------------- Dark Father Amadeus -+ |----------- jadour01@[homer|ftp|ulkyvx|ulkyvm].louisville.edu -----------| |--------- Home Page : http://www.louisville.edu/~jadour01/ ----------| +--------- PJ Harvey : http://www.louisville.edu/~jadour01/pjh/ ----------+ From majordomo-users-owner Thu Sep 14 16:30:15 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA08640 for majordomo-users-outgoing; Thu, 14 Sep 1995 16:18:02 -0700 Received: from GRACE.WAIKATO.AC.NZ (grace.waikato.ac.nz [130.217.64.32]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id QAA08603 for ; Thu, 14 Sep 1995 16:17:54 -0700 Received: from cs.waikato.ac.nz (lucy.cs.waikato.ac.nz) by waikato.ac.nz (PMDF V5.0-3 #11755) id <01HVAX9JPKKWAHNDKM@waikato.ac.nz> for majordomo-users@GreatCircle.COM; Fri, 15 Sep 1995 11:16:12 +1200 Received: from borg.cs.waikato.ac.nz by cs.waikato.ac.nz (5.x/SMI-SVR4) id AA21468; Fri, 15 Sep 1995 11:16:07 +1200 Received: from borg (localhost) by borg.cs.waikato.ac.nz (5.x/SMI-SVR4) id AA22833; Fri, 15 Sep 1995 11:16:06 +1200 Date: Fri, 15 Sep 1995 11:16:06 +1200 From: Andrew Donkin Subject: Re: Munged subscriber files... In-reply-to: "Your message of Thu, 14 Sep 1995 18:25:42 EST." <9509142225.AA30956@homer.louisville.edu> To: majordomo-users@GreatCircle.COM Message-id: <9509142316.AA22833@borg.cs.waikato.ac.nz> Content-transfer-encoding: 7BIT Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi; Jason said: |Recently, I was notified that one of the mailing lists I run had not been |working. I found out later that the subscriber file had been completely |erased by the system. Yup. One of the local disks had run out of space, so Majordomo had had a problem writing to a temporary file. I can't remember if it was "/var" or "/tmp" or Majordomo's home which filled up but my subscription lists were scrapped. Fortunately I keep a copy for WWW use on another system and so I only lost a few hours' worth of subscriptions. |Any advice on how to keep this from happening again? Ideally whichever Majordomo script truncated the file could be fitted with more error checking. I just fixed the (unrelated) problem which caused the disk to become full and it's been fine ever since. =========================================================================== Andrew Donkin, UNIX admin, Sch. of CompSci&Math, Waikato Univ, New Zealand Email: ard@cs.waikato.ac.nz HTTP://www.cs.waikato.ac.nz/~ard/ PGP keyprint:AA-47-E3-D8-AA-BD-02-AC--48-93-BF-EE-FE-38-8C-09 Key 0B0F9FE5 From majordomo-users-owner Thu Sep 14 16:32:44 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA10185 for majordomo-users-outgoing; Thu, 14 Sep 1995 16:31:07 -0700 Received: from GRACE.WAIKATO.AC.NZ (grace.waikato.ac.nz [130.217.64.32]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id QAA10176 for ; Thu, 14 Sep 1995 16:31:02 -0700 Received: from cs.waikato.ac.nz (lucy.cs.waikato.ac.nz) by waikato.ac.nz (PMDF V5.0-3 #11755) id <01HVAXPZ1ALSAHO0J9@waikato.ac.nz> for majordomo-users@GreatCircle.COM; Fri, 15 Sep 1995 11:29:27 +1200 Received: from borg.cs.waikato.ac.nz by cs.waikato.ac.nz (5.x/SMI-SVR4) id AA23025; Fri, 15 Sep 1995 11:29:22 +1200 Received: from borg (localhost) by borg.cs.waikato.ac.nz (5.x/SMI-SVR4) id AA23256; Fri, 15 Sep 1995 11:29:21 +1200 Date: Fri, 15 Sep 1995 11:29:21 +1200 From: Andrew Donkin Subject: List usage statistics; archive searching? To: majordomo-users@GreatCircle.COM Reply-to: ard@lucy.cs.waikato.ac.nz Message-id: <9509142329.AA23256@borg.cs.waikato.ac.nz> Content-transfer-encoding: 7BIT Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Two questions: Does anyone provide a list archive searching facility via the WWW? Sam Leffler (?) has set up an awesome one for the HylaFax list "based on Version 0.9beta of the Mailing List Archive (MLA) tools" (to quote the page). Sam says these tools are no longer available, so I'm wondering if there's anything else. Is there a package out there in use by other Majordomo admins that provides a search facility, or did you roll your own? Secondly, has anyone set up an accounting system, providing traffic or subscription details? I have thrown together some simple subscription and daily postings graphs that people can browse on the web (see my home page), but if there's a package in use elsewhere I'll take it on, in order to be consistent with other Majordomo sites. =========================================================================== Andrew Donkin, UNIX admin, Sch. of CompSci&Math, Waikato Univ, New Zealand Email: ard@cs.waikato.ac.nz HTTP://www.cs.waikato.ac.nz/~ard/ PGP keyprint:AA-47-E3-D8-AA-BD-02-AC--48-93-BF-EE-FE-38-8C-09 Key 0B0F9FE5 From majordomo-users-owner Thu Sep 14 17:02:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id RAA11715 for majordomo-users-outgoing; Thu, 14 Sep 1995 17:00:20 -0700 Received: from foo.garply.com (foo.garply.com [165.113.188.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id RAA11708 for ; Thu, 14 Sep 1995 17:00:15 -0700 Received: by foo.garply.com; (5.65/1.1.8.2/22Nov94-0235PM) id AA31298; Thu, 14 Sep 1995 19:02:00 -0500 From: Hugh Messenger Message-Id: <9509150002.AA31298@foo.garply.com> Subject: Re: List usage statistics; archive searching? To: ard@lucy.cs.waikato.ac.nz Date: Thu, 14 Sep 1995 19:02:00 -0500 (CDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <9509142329.AA23256@borg.cs.waikato.ac.nz> from "Andrew Donkin" at Sep 15, 95 11:29:21 am Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 798 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Does anyone provide a list archive searching facility via the WWW? Sam > Leffler (?) has set up an awesome one for the HylaFax list "based on > Version 0.9beta of the Mailing List Archive (MLA) tools" (to quote the > page). Sam says these tools are no longer available, so I'm wondering if > there's anything else. > > Is there a package out there in use by other Majordomo admins that provides > a search facility, or did you roll your own? I'm in the process of playing with hypermail, swish and wwwwais from ... http://www.eit.com ... which provide a very nice interface onto mail archives, and should also provide a cut-down WAIS style indexing/searching mechanism. I'm having some problems getting the WWW based search interface working, More News When There Is News ... -- hugh From majordomo-users-owner Thu Sep 14 17:30:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id RAA13744 for majordomo-users-outgoing; Thu, 14 Sep 1995 17:26:40 -0700 Received: from futureinfo.com (futureinfo.com [192.246.172.20]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id RAA13720 for ; Thu, 14 Sep 1995 17:26:31 -0700 Received: by futureinfo.com (4.1/3.1.012693-Future InfoSystems); id AA06648 for majordomo-users@GreatCircle.COM; Thu, 14 Sep 95 17:27:30 PDT Date: Thu, 14 Sep 1995 17:27:30 -0700 (PDT) From: Willem Scholten To: ard@lucy.cs.waikato.ac.nz Cc: majordomo-users@GreatCircle.COM Subject: Re: List usage statistics; archive searching? In-Reply-To: <9509142329.AA23256@borg.cs.waikato.ac.nz> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Take a look at HyperMail at EIT. You can take look at www.spl.org page under mailinglists, and you'll find pointers to the software. Also add WAIS search to it is pretty straight forward if using for example freewais and their http-wais gateway.. -Willem. On Fri, 15 Sep 1995, Andrew Donkin wrote: > > Two questions: > > Does anyone provide a list archive searching facility via the WWW? Sam > Leffler (?) has set up an awesome one for the HylaFax list "based on > Version 0.9beta of the Mailing List Archive (MLA) tools" (to quote the > page). Sam says these tools are no longer available, so I'm wondering if > there's anything else. > > Is there a package out there in use by other Majordomo admins that provides > a search facility, or did you roll your own? > > Secondly, has anyone set up an accounting system, providing traffic or > subscription details? I have thrown together some simple subscription and > daily postings graphs that people can browse on the web (see my home page), > but if there's a package in use elsewhere I'll take it on, in order to be > consistent with other Majordomo sites. > > > =========================================================================== > Andrew Donkin, UNIX admin, Sch. of CompSci&Math, Waikato Univ, New Zealand > Email: ard@cs.waikato.ac.nz HTTP://www.cs.waikato.ac.nz/~ard/ > PGP keyprint:AA-47-E3-D8-AA-BD-02-AC--48-93-BF-EE-FE-38-8C-09 Key 0B0F9FE5 > From majordomo-users-owner Thu Sep 14 18:30:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA16167 for majordomo-users-outgoing; Thu, 14 Sep 1995 18:29:38 -0700 Received: from relay.ubss.com (relay.ubss.com [199.222.66.11]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id SAA16157 for ; Thu, 14 Sep 1995 18:29:33 -0700 Received: from ny.ubs.com (ns1.ny.ubs.com) by relay.ubss.com with SMTP id AA05303 (InterLock SMTP Gateway 3.0 for ); Thu, 14 Sep 1995 21:27:41 -0400 Received: from ikura.ny.ubs.com by ny.ubs.com (4.1/SMI-4.1) id AA03510; Thu, 14 Sep 95 21:25:50 EDT Received: by ikura.ny.ubs.com (4.1/SMI-4.1) id AA13512; Thu, 14 Sep 95 21:27:38 EDT Message-Id: <9509150127.AA13512@ikura.ny.ubs.com> From: rct@ubss.com (Robert C. Terzi) Date: Thu, 14 Sep 1995 21:27:38 -0400 In-Reply-To: Andrew Donkin "Re: Munged subscriber files..." (Sep 15, 11:16am) Reply-To: rct@ubss.com X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Andrew Donkin , majordomo-users@GreatCircle.COM Subject: Re: Munged subscriber files... Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >> In "Re: Munged subscriber files...", Sep 15, Andrew Donkin writes << > > |Any advice on how to keep this from happening again? > > Ideally whichever Majordomo script truncated the file could be fitted with > more error checking. I just fixed the (unrelated) problem which caused the > disk to become full and it's been fine ever since. It would be nice if it could be taught to use RCS, so you'd also be able to get a history over time as well as some protection. --Robert From majordomo-users-owner Thu Sep 14 19:00:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA16616 for majordomo-users-outgoing; Thu, 14 Sep 1995 18:45:28 -0700 Received: from caipfs.rutgers.edu (caipfs.rutgers.edu [128.6.37.100]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id SAA16609 for ; Thu, 14 Sep 1995 18:45:25 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id VAA01388; Thu, 14 Sep 1995 21:44:02 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id VAA01204; Thu, 14 Sep 1995 21:44:01 -0400 Date: Thu, 14 Sep 1995 21:44:01 -0400 Message-Id: <199509150144.VAA01204@huahaga.rutgers.edu> From: "David S. Miller" To: rct@ubss.com CC: ard@borg.cs.waikato.ac.nz, majordomo-users@GreatCircle.COM In-reply-to: <9509150127.AA13512@ikura.ny.ubs.com> (rct@ubss.com) Subject: Re: Munged subscriber files... Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk From: rct@ubss.com (Robert C. Terzi) Date: Thu, 14 Sep 1995 21:27:38 -0400 > Ideally whichever Majordomo script truncated the file could be fitted with > more error checking. I just fixed the (unrelated) problem which caused the > disk to become full and it's been fine ever since. It would be nice if it could be taught to use RCS, so you'd also be able to get a history over time as well as some protection. This is the best idea I have seen yet for this problem. As a quick hack, you could write a script that briefly understood the locking semantics of Majordomo for the subscription lists and would be run as a cron job every so often to check in all the subscription lists (but locking them properly first) then check them all out. Then majordomo would proceed as normal. For people running a lot of lists (like me) and see this spammage often enough, this would be a *HUGE* win... Later, David S. Miller davem@caip.rutgers.edu From majordomo-users-owner Thu Sep 14 19:02:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA16414 for majordomo-users-outgoing; Thu, 14 Sep 1995 18:38:35 -0700 Received: from sparc (Sparc.uccb.ns.ca [142.12.4.50]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id SAA16378 for ; Thu, 14 Sep 1995 18:38:07 -0700 Received: by sparc (5.0/SMI-SVR4) id AA24125; Thu, 14 Sep 1995 22:37:37 +0400 Date: Thu, 14 Sep 1995 22:37:36 -0300 (ADT) From: Steve MacLeod Subject: Re: List usage statistics; archive searching? To: Hugh Messenger Cc: majordomo-users@GreatCircle.COM In-Reply-To: <9509150002.AA31298@foo.garply.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 1199 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 14 Sep 1995, Hugh Messenger wrote: > I'm in the process of playing with hypermail, swish and wwwwais from ... > > http://www.eit.com > > ... which provide a very nice interface onto mail archives, and should also > provide a cut-down WAIS style indexing/searching mechanism. I'm having some > problems getting the WWW based search interface working, More News When There > Is News ... > > -- hugh Hi Hugh As you have mentioned wwwwais I have a question that some on the list might be able to help with. I run WAIS and index the mail folder/archive for two lists ... one I run on that machine, this I can search with waissearch or wwwwais no problem. The other is an archive of messages from another list. This give me much grief with wais complaining about Dangling Files ... is there a difference between the way the majordomo archive stores it's messages and the regular unix mail folder? 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 From majordomo-users-owner Thu Sep 14 22:00:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id VAA21518 for majordomo-users-outgoing; Thu, 14 Sep 1995 21:51:06 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id VAA21511 for ; Thu, 14 Sep 1995 21:51:02 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA11832; Fri, 15 Sep 1995 00:49:22 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509150449.AA11832@cs.rpi.edu> To: ard@lucy.cs.waikato.ac.nz Cc: majordomo-users@GreatCircle.COM Subject: Re: List usage statistics; archive searching? In-Reply-To: Andrew Donkin's message of "Fri, 15 Sep 1995 11:29:21 +1200." <9509142329.AA23256@borg.cs.waikato.ac.nz> X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Fri, 15 Sep 1995 00:48:47 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk A very good package for online Web searching is glimpse and glimpseHTTP. I haven't integrated it with majordomo yet, but someone else has been able to set it up so that it will search my archive of zip files which contain about 100 articles each of messages posted to my mailing list. Glimpse can be made to do full-text searching, which is very good, since subject lines do not have much in them. The indices are built ahead of time (something like an inverted index) so searching is very fast. The search results are displayed in a Web page with links pointint to the actual files. To try glimpse on the owl-list go to this page: http://www.ioc.ee/owl/search.html For more on glimpse go to: http://glimpse.cs.arizona.edu:1994/index.html an for info on glimpseHTTP go to: http://glimpse.cs.arizona.edu:1994/glimpsehttp.html -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Fri Sep 15 00:30:09 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id AAA25111 for majordomo-users-outgoing; Fri, 15 Sep 1995 00:23:22 -0700 Received: from outsider.bolis.sf-bay.org (bolis.isp.net [204.153.195.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id AAA25104 for ; Fri, 15 Sep 1995 00:23:16 -0700 Received: from hock.bolis.sf-bay.org by outsider.bolis.sf-bay.org with smtp (Smail3.1.29.1 #3) id m0stV3i-0006vlC; Fri, 15 Sep 95 00:19 PDT Received: from amillar by hock.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0stV3G-000UpwC; Fri, 15 Sep 95 00:19 PDT Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: Bowden Wise , majordomo-users@greatcircle.com Date: Thu, 14 Sep 1995 23:09:52 -800 Subject: Re: Bounced Mails Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Okay, I think I have the bounces set up right now. I use resend so > that all messages have the Sender as owner-listname So, whenever a > bounce occurs I get the MAILER DAEMON messages. > > Is this all I get? I thought a BOUNCE message was generated for the > offending address? Do I still have to analyze the mailer daemon > messages for the offending addresses and then use bounce to move > that address to the bounces list? Yes, it is all you get. A MAILER-DAEMON message is sent to you when another site doesn't accept a message. You have to analyze it for the bouncing address. It is caused by the end delivery of list messages going out to the recipients. A message with BOUNCE in the subject line is different. It comes from "resend" on your system. It is caused by "resend" rejecting incoming messages before they are sent out to the list. They are not related to delivery problems on a particular address. - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: http://metro.turnpike.net/metro/amillar From majordomo-users-owner Fri Sep 15 00:32:44 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id AAA24782 for majordomo-users-outgoing; Fri, 15 Sep 1995 00:03:22 -0700 Received: from outsider.bolis.sf-bay.org (bolis.isp.net [204.153.195.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id AAA24775 for ; Fri, 15 Sep 1995 00:03:15 -0700 Received: from hock.bolis.sf-bay.org by outsider.bolis.sf-bay.org with smtp (Smail3.1.29.1 #3) id m0stUkN-0006uvC; Thu, 14 Sep 95 23:59 PDT Received: from amillar by hock.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0stUgw-000UpuC; Thu, 14 Sep 95 23:56 PDT Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: Yuri Engelhardt , majordomo-users@greatcircle.com Date: Thu, 14 Sep 1995 22:46:45 -800 Subject: Re: subscribers-file, opening a 'cafe' Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On 14 Sep 95 at 22:35, Yuri Engelhardt wrote: > > Technically, the InfoDesign-Cafe is a mailing list that is > > a sub-list of the InfoDesign list. In other words, the > > InfoDesign-Cafe is an optional supplement (sub-forum) of > > InfoDesign. In order to subscribe to ... > Simply chosing to post the main-list messages also to the 'Cafe'-list > is not an option, because most (preferably all) 'Cafe'-subscribers ARE > also on the main-list, and would then receive all 'main'-messages TWICE. The problem of duplicate mailings can be fixed, and therefore this method *IS* the easiest way to solve your problem. If sendmail explodes both files as one expansion, it will remove the duplicates automatically. Set up your aliases along these lines: Infodesign-Cafe: |wrapper resend infodesign-cafe-outgoing Infodesign-cafe-outgoing: :include:/lists/infodesign-cafe Infodesign: |wrapper resend infodesign-outgoing Infodesign-outgoing: infodesign-cafe-outgoing, :include:/lists/infodesign The key here is to have cafe-outgoing AFTER resend. Remember, *you* don't send messages to both lists; let the aliases expand both files and eliminate duplicates in a single mailing. Give that a try and see how it works. It is definitely going to be easier than trying to limit subscriptions on the other end. - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: http://metro.turnpike.net/metro/amillar From majordomo-users-owner Fri Sep 15 02:30:01 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id CAA27065 for majordomo-users-outgoing; Fri, 15 Sep 1995 02:09:12 -0700 Received: from uni-paderborn.de (uni-paderborn.de [131.234.10.3]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id CAA27035 for ; Fri, 15 Sep 1995 02:08:52 -0700 Received: from diana (diana.uni-paderborn.de [131.234.2.33]) by uni-paderborn.de (8.6.12/8.6.12) with SMTP id LAA15916 for ; Fri, 15 Sep 1995 11:07:27 +0200 Date: Fri, 15 Sep 1995 11:07:24 +0200 (MET DST) From: Matthias Hovestadt X-Sender: maho@diana To: majordomo-users@greatcircle.com Subject: lower-case problem with Majordomo 1.93 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi! I'm using Majordomo 1.93 and everythink works really fine, except of one _BIG_ problem: Majordomo seems to have problems with capital-letters in the listnames. He can find the list "test-list", but not "Test-List". First I had the lower-case version in my listdir and could get informations about this list. Then I tried it with the capital-letter version and got a fault (could not find list...). :-( Can anybody help me solving this problem? Btw: How can I become a member of this mailing-list? Ciao, Matthias From majordomo-users-owner Fri Sep 15 06:00:30 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id FAA00317 for majordomo-users-outgoing; Fri, 15 Sep 1995 05:53:47 -0700 Received: from homer.louisville.edu (homer.louisville.edu [136.165.1.20]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id FAA00304 for ; Fri, 15 Sep 1995 05:53:42 -0700 Received: by homer.louisville.edu; (5.65v3.0/1.1.8.2/03Jun94-0854PM) id AA19642; Fri, 15 Sep 1995 08:52:27 -0400 From: "Jason A. Dour" Message-Id: <9509151252.AA19642@homer.louisville.edu> Subject: Re: Munged subscriber files... To: majordomo-users@GreatCircle.COM Date: Fri, 15 Sep 1995 08:52:27 -0500 (EDT) X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1029 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk First off... Thanks for all the replies both public and private, everyone. They were much help. I have found the instigator of my problem... If what Andrew said is true (about disk space), then yes, we did have that problem recently, and it was right about the same time that I believe the files got munged. I never connected the two. (Duh!) A quick hack I put in place as a precaution (and as a secondary fallback from backup tapes), was to schedule a CRON job to tar and gzip the entire list directory. It's cheap, and not very strong, but it works in some (most?) cases. I was informed privately of a patch to fix this problem. I'm going to look for it, and see if I can get it installed. Again. Thanks! Jason +- Jason A. Dour ----------------------------------- Dark Father Amadeus -+ |----------- jadour01@[homer|ftp|ulkyvx|ulkyvm].louisville.edu -----------| |--------- Home Page : http://www.louisville.edu/~jadour01/ ----------| +--------- PJ Harvey : http://www.louisville.edu/~jadour01/pjh/ ----------+ From majordomo-users-owner Fri Sep 15 06:30:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA01391 for majordomo-users-outgoing; Fri, 15 Sep 1995 06:17:56 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA01383 for ; Fri, 15 Sep 1995 06:17:52 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA22304 for majordomo-users@greatcircle.com; Fri, 15 Sep 95 06:16:36 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA24277; Fri, 15 Sep 95 06:16:35 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA02455 for majordomo-users@greatcircle.com; Fri, 15 Sep 95 06:16:34 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA02232; Fri, 15 Sep 95 08:16:32 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA19825; Fri, 15 Sep 1995 08:16:26 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509151316.AA19825@miaow.sps.mot.com> Subject: Re: lower-case problem with Majordomo 1.93 To: uunet!uni-paderborn.de!maho (Matthias Hovestadt) Date: Fri, 15 Sep 1995 08:16:26 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Matthias Hovestadt" at Sep 15, 95 11:07:24 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2188 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Matthias Hovestadt writes: ] > > I'm using Majordomo 1.93 and everythink works really fine, except of one > _BIG_ problem: > Majordomo seems to have problems with capital-letters in the listnames. > He can find the list "test-list", but not "Test-List". First I had the > lower-case version in my listdir and could get informations about this > list. Then I tried it with the capital-letter version and got a fault > (could not find list...). :-( Excerpted from the FAQ, available at ftp.greatcircle.com in /pub/majordomo/majordomo-faq.txt: A LIST IS VISIBLE VIA LISTS, BUT CAN'T SUBSCRIBE OR 'GET' FILES [From Brent Chapman] I'll bet your list name has capital letters in it... Majordomo smashes all list names to all-lower-case before attempting to use the list name as part of a filename. So, while it's OK to advertise (for instance) "Majordomo-Users" and have the headers say "Majordomo-Users", the file names and archive directory names themselves all need to be in lower case. If you want to use mixed case, simply configure the list using the lower-case names everywhere, except put the mixed-case version in the "-l" and "-h" flags to resend. > Btw: How can I become a member of this mailing-list? You've installed Majordomo and can post to majordomo-users, but don't know how to subscribe??? I hope you can find someone to read this response to you... ;-) Excerpted from the README file in the Majordomo 1.93 distribution: 4.0 Mailing Lists/Support There are four mailing lists at GreatCircle.COM, Majordomo-Users - for discussions on using Majordomo Majordomo-Announce - for announcements of new releases Majordomo-Workers - for people interested in development of Majordomo. Majordomo-Docs - for people interested in development of documentation for Majordomo. To subscribe to any of the lists above, send an appropriate "subscribe" command to "Majordomo@GreatCircle.COM". -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Fri Sep 15 09:00:06 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA07571 for majordomo-users-outgoing; Fri, 15 Sep 1995 08:52:30 -0700 Received: from triples.math.mcgill.ca (Triples.Math.McGill.CA [132.206.150.30]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id IAA07547 for ; Fri, 15 Sep 1995 08:52:07 -0700 Received: (from phaedrus@localhost) by triples.math.mcgill.ca (8.6.8/8.6.6) id LAA06578 for majordomo-users@greatcircle.com; Fri, 15 Sep 1995 11:50:22 -0400 Message-Id: <199509151550.LAA06578@triples.math.mcgill.ca> From: phaedrus@Math.McGill.CA (Phong Co) Date: Fri, 15 Sep 1995 11:50:22 +1000 In-Reply-To: "Jason A. Dour" "Re: Munged subscriber files..." (Sep 15, 8:52am) X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: majordomo-users@greatcircle.com Subject: Re: Munged subscriber files... Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In reply to your message of Sep 15 ( 8:52am), } > If what Andrew said is true (about disk space), then yes, we did have that > problem recently, and it was right about the same time that I believe the > files got munged. I never connected the two. (Duh!) > > A quick hack I put in place as a precaution (and as a secondary fallback > from backup tapes), was to schedule a CRON job to tar and gzip the entire > list directory. It's cheap, and not very strong, but it works in some > (most?) cases. > }-- End of excerpt from "Jason A. Dour" I fell prey to the "disk full" gremlins a couple of times myself, and had to resort to the backup tapes. At one point one of my config files even reverted to the default state. I now tar and gzip the list directory as Jason describes above, keeping the last 10 copies. It's cheap, simple, and entirely adequate if you keep an eye on your subscribers list now and then. -- ========================================================================= Phong T. Co phaedrus@Math.McGill.CA McGill University Computer Coordinator Montreal, CANADA Department of Mathematics (514) 398-8448 When does summertime come to Minnesota, you ask? Well, last year, I think it was a Tuesday. From majordomo-users-owner Fri Sep 15 12:04:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA18724 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:00:20 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id TAA02903 for ; Tue, 12 Sep 1995 19:32:40 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA17754; Tue, 12 Sep 1995 22:31:22 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509130231.AA17754@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Admin Bounces X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Tue, 12 Sep 1995 22:30:48 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When someone sends a subscribe message to a list, I am using resend with administrative checking, and the BOUNCE admin message is getting sent to me, the list owner. But....does the person who sent the message get anything back?? I think it would be good if they got the request-answer message returned to them so that they would know to send their request to the majordomo address. But it looks like the message is just sent to me and then I must resolve it? is this the way it is supposed to work? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Fri Sep 15 12:32:44 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA19752 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:14:42 -0700 Received: from law.uoregon.edu (law.uoregon.edu [128.223.106.198]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA16126 for ; Thu, 14 Sep 1995 10:17:47 -0700 Received: from [128.223.106.195] (meetingmaker1.uoregon.edu [128.223.106.195]) by law.uoregon.edu (8.6.12/8.6.12) with SMTP id KAA01807 for ; Thu, 14 Sep 1995 10:16:26 -0700 Date: Thu, 14 Sep 1995 10:16:26 -0700 Message-Id: <199509141716.KAA01807@law.uoregon.edu> Subject: HELP( BOUNCE faculty: Admin request) From: "Chandra S. Chitneni" To: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a list called faculty. It is not a moderated list. When one of the faculty member posted a message, I(ownet-faculty) got the message forwarded with the subject BOUNCD faculty: Admin request. Can somebody tell me when I would usually get this kind of message. This list was working OK so far until today when I saw this message. Thanks, -chandra chandra@law.uoregon.edu From majordomo-users-owner Fri Sep 15 12:34:21 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA19142 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:05:46 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA17098 for ; Wed, 13 Sep 1995 06:21:06 -0700 Received: from ro.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA28502; Wed, 13 Sep 1995 09:19:47 -0400 (wiseb from ro.cs.rpi.edu) Message-Id: <199509131319.AA28502@cs.rpi.edu> X-Mailer: exmh version 1.6.1 5/23/95 To: majordomo-users@greatcircle.com Subject: Re: Admin Bounces In-Reply-To: "Alan Millar"'s message of "Wed, 13 Sep 1995 02:11:59." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Sep 1995 09:19:45 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > When someone sends a subscribe request to a list, I get the BOUNCE > > mail informing me of the admin request. But, does the original user > > get any kind of help message sent back to them, telling them to send > > requests to majordomo ?? > > No, Majordomo does not send any notice back to the user. I think > some people have patched their copies of Majordomo to do that, but it > is not part of the distribution currently. Has anyone patched majordomo to do that? I would be interested in seeing the diff for it. --Bowden -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Fri Sep 15 12:52:13 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA19169 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:06:09 -0700 Received: from unilab.dfci.harvard.edu (unilab.dfci.harvard.edu [155.52.46.57]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id HAA19191 for ; Wed, 13 Sep 1995 07:26:18 -0700 Received: (from ratinox@localhost) by unilab.dfci.harvard.edu (8.6.12/8.6.9) id KAA00156; Wed, 13 Sep 1995 10:25:00 -0400 Date: Wed, 13 Sep 1995 10:25:00 -0400 Message-Id: <199509131425.KAA00156@unilab.dfci.harvard.edu> From: Richard Pieri To: Majordomo-users@GreatCircle.COM In-reply-to: Jarle Martinsen +41 22 730 5949's message of Wed, 13 Sep 1995 14:43:28 +0100 (CET) Subject: Re: long lines in approve... References: <7828431513091995/A34298/TAU/11996BEB1B00*@MHS> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- >>>>> "4275" == 41 22 730 5949 writes: 4275> approve password subscribe list name@mlab.nttdocomo.co.jp 4275> \(Yasuo Maruyama) Almost. You want to have the escaping backslash on the first line, like this: approve PASSWD subscribe LIST \ name@mlab.nttdocomo.co.jp -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Processed by Mailcrypt 3.3, an Emacs/PGP interface iQCVAwUBMFbptZ6VRH7BJMxHAQFIoAQAyMEabImXYSJzUOvyLmVQnuYqZ98TN3o/ Mi9p9mgG1GJNjjbpE2yFhMCPEgTUoBAllfe28QsenvlOslWqzGJUwdEF0Z2iMCz3 uQcYO6mRTBwFPnujyzVvNIdSuAU/IwVa8t89LaA7dHtkVuUglY80AKiDVq1hCmLA BTMozhqkoQs= =OxgV -----END PGP SIGNATURE----- -- Richard Pieri/Information Services \ When eating out, think nothing of sending \ back your meal twenty or thirty times. -A http://www.dfci.harvard.edu/~ratinox \ cat's guide to life From majordomo-users-owner Fri Sep 15 13:01:21 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA22835 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:55:13 -0700 Received: from hq.stargame.org (bh.mindspring.com [168.121.33.204]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id MAA22818 for ; Fri, 15 Sep 1995 12:55:08 -0700 Received: (from bh@localhost) by hq.stargame.org (8.6.12/8.6.9) id OAA03609; Thu, 14 Sep 1995 14:58:29 -0400 Date: Thu, 14 Sep 1995 14:58:29 -0400 (EDT) From: Brian Hartsfield To: "Chandra S. Chitneni" cc: majordomo-users@GreatCircle.COM Subject: Re: HELP( BOUNCE faculty: Admin request) In-Reply-To: <199509141716.KAA01807@law.uoregon.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 14 Sep 1995, Chandra S. Chitneni wrote: > > I have a list called faculty. It is not a moderated list. When one of > the faculty member posted a message, I(ownet-faculty) got the message > forwarded with the subject > > BOUNCD faculty: Admin request. > > Can somebody tell me when I would usually get this kind of message. This > list was working OK so far until today when I saw this message. Majordomo tries to identify admin requests that should go to majordomo that are sent to the list address by mistake. It is at times overly paranoid. That is why the message got bounced to you. It identified it as a possible messages that should have goine to majordomo. It is was not, just approve the message like you would for a moderated list and it will be sent to the list. Brian From majordomo-users-owner Fri Sep 15 13:02:44 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA19098 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:05:26 -0700 Received: from isp1.isp.net (isp1.isp.net [204.139.9.12]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id DAA13483 for ; Wed, 13 Sep 1995 03:23:33 -0700 Received: from outsider.bolis.sf-bay.org (bolis.isp.net [204.153.195.10]) by mail.isp.net (8.6.9/8.6.9) with SMTP id DAA20324 for ; Wed, 13 Sep 1995 03:21:04 -0700 Received: from hock.bolis.sf-bay.org by outsider.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0ssouE-0006wvC; Wed, 13 Sep 95 03:19 PDT Received: from amillar by hock.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0ssovm-000Uq6C; Wed, 13 Sep 95 03:20 PDT Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: Bowden Wise , majordomo-users@GreatCircle.COM Date: Wed, 13 Sep 1995 02:11:59 -800 Subject: Re: Admin Bounces Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On 12 Sep 95 at 15:20, Bowden Wise wrote: > When someone sends a subscribe request to a list, I get the BOUNCE > mail informing me of the admin request. But, does the original user > get any kind of help message sent back to them, telling them to send > requests to majordomo ?? No, Majordomo does not send any notice back to the user. I think some people have patched their copies of Majordomo to do that, but it is not part of the distribution currently. - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: http://metro.turnpike.net/metro/amillar From majordomo-users-owner Fri Sep 15 13:14:52 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA19237 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:07:06 -0700 Received: from VNET.IBM.COM (vnet.ibm.com [199.171.26.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA29369 for ; Wed, 13 Sep 1995 11:09:12 -0700 Received: from TOROLAB by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 3267; Wed, 13 Sep 95 14:07:35 EDT Received: by TOROLAB (XAGENTA 4.0) id 1878; Wed, 13 Sep 1995 13:32:45 -0400 Received: by tormail1.torolab.ibm.com (IBM OS/2 SENDMAIL VERSION 1.2.12/4.04um) id AA0116; Wed, 13 Sep 95 13:19:12 -0400 Message-Id: <9509131719.AA0116@tormail1.torolab.ibm.com> Mime-Version: 1.0 Date: Wed, 13 Sep 95 13:25:40 From: "Leip, D" (0) To: "majordomo-users" (0) Reply-To: "Leip, D" (0) Subject: Subscribing a ML to an ML X-Mailer: IBM WorkGroup Mail Version 1.0 X-Mailer: IBM WorkGroup Mail Version 1.0 Content-Id: <185_171_4_811013140> Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've got two questions that I hope someone can answer for me. 1) Is it possible to subscribe one majordomo list to another (on the same server)? I can't see why not, but I thought I'd ask before have my sys-admin create a list only to find out that it doesn't work. 2) Is it possible to completely restrict the use of the list command to just the owner or disable it altogether? I know you can restrict it to those on the list, I'm just curious if it can be restricted further. Thanks. David Leip IBM Toronto Lab work: 416-448-3027 internal:Leip@torolab external:Leip@vnet.ibm.com home: 519-766-1834 David@Leip.com IWW (IBM Wide Web) http://w3.torolab.ibm.com/~leip From majordomo-users-owner Fri Sep 15 13:16:48 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA19272 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:07:32 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA05907 for ; Wed, 13 Sep 1995 13:35:04 -0700 Received: from ro.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA14134; Wed, 13 Sep 1995 16:33:46 -0400 (wiseb from ro.cs.rpi.edu) Message-Id: <199509132033.AA14134@cs.rpi.edu> X-Mailer: exmh version 1.6.1 5/23/95 To: majordomo-users@greatcircle.com Subject: Re: Admin Bounces In-Reply-To: "Alan Millar"'s message of "Wed, 13 Sep 1995 02:11:59." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Sep 1995 16:33:42 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > On 12 Sep 95 at 15:20, Bowden Wise wrote: > > > When someone sends a subscribe request to a list, I get the BOUNCE > > mail informing me of the admin request. But, does the original user > > get any kind of help message sent back to them, telling them to send > > requests to majordomo ?? > > No, Majordomo does not send any notice back to the user. I think > some people have patched their copies of Majordomo to do that, but it > is not part of the distribution currently. Okay, what I would like to happen is for the user to get the same reply that is generated when request-answer is run for that particular list. Two questions: - how can i manually cause request answer to be invoked for a particular user and list - how do I patch resend to do this for me? Bowden -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Fri Sep 15 13:19:31 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA20040 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:17:41 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id WAA21819 for ; Thu, 14 Sep 1995 22:01:44 -0700 From: wiseb@cs.rpi.edu Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA12032; Fri, 15 Sep 1995 01:00:29 -0400 (wiseb from colossus.cs.rpi.edu) Date: Fri, 15 Sep 95 00:59:47 EDT Received: by colossus.cs.rpi.edu (4.1/2.3-RPI-CS-client) id AA11783; Fri, 15 Sep 95 00:59:47 EDT Message-Id: <9509150459.AA11783@colossus.cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Admin Bounces Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Whenever I get an admin bounce (someone sends a subscribe to the list), I get TWO messags; the first is the BOUNCE message with an empty body, and the second is the original message. This seems odd, should I just get one message with the original message in the body of the BOUNCE message? is this the way it is supposed to work or is something fishy happening here? Bowden -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Fri Sep 15 13:23:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA20081 for majordomo-users-outgoing; Fri, 15 Sep 1995 12:17:59 -0700 Received: from leibniz.math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id WAA22007 for ; Thu, 14 Sep 1995 22:06:18 -0700 Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by leibniz.math.psu.edu (8.6.12/8.6.9) with ESMTP id BAA19425 for ; Fri, 15 Sep 1995 01:05:03 -0400 From: Dave Barr Received: (barr@localhost) by augusta.math.psu.edu (8.6.12/8.6.9) id BAA06672 for Majordomo-Users@GreatCircle.COM; Fri, 15 Sep 1995 01:05:01 -0400 Date: Fri, 15 Sep 1995 01:05:01 -0400 Message-Id: <199509150505.BAA06672@augusta.math.psu.edu> To: Majordomo-Users@GreatCircle.COM Reply-To: barr@math.psu.edu Subject: Majordomo Frequently Asked Questions Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Version: $Id: majordomo-faq.html,v 1.83 1995/09/07 15:34:52 barr Exp barr $ Archive-Name: mail/list-admin/majordomo-faq Posting-Frequency: monthly Table of Contents: 1. What is Majordomo and how can I get it? + What is Majordomo? + Where do I get it? + How do I install it? + How do I upgrade from an earlier release? + Where do I report bugs or get help with Majordomo? + Which is better, Majordomo or LISTSERV? 2. Problems setting up Majordomo + What are the proper permissions and ownership of all Majordomo files and directories? + I get "Unknown mailer error" when majordomo runs + I get "Permission denied at ..." when majordomo runs + I get "shlock: open(">/some/path/...") when majordomo runs + A file is visible via index, but can't 'get' it + Majordomo seems to be taking many minutes to process commands + I get an error "insecure usage" from the wrapper + I get "majordomo: No such file or directory" from the wrapper + I get an error "Can't locate majordomo.pl" + I told my majordomo.cf where to archive the list, why isn't it working? + I'm accumulating lots of files called /tmp/resend.*.in and .out, + A list is visible via lists, but can't subscribe or 'get' files + I get "Out of Memory" when upgrading to 1.93 + I get warnings or errors when trying to compile 1.93's wrapper + Problems with 1.93's request-answer + I get "Invalid archive directory. Aborting." 3. Setting up mailing lists and aliases + How do I direct bounces to the right address? + Semi-automated handling of bounced mail + What's this Owner-List and List-Owner stuff? Why both? + How should I configure resend for Reply-To headers? + How can I hide lists so they can't be viewed by 'lists'? + How can I restrict a list such that only subscribers can send mail to the list? + Can I have the list owner or approval person be changeable without intervention from the Majordomo owner? + What about all of these passwords starting in version 1.90? + How do I tell majordomo to handle "get"-ing of binary files? + How do I set up a moderated list? + How do I set up a digested version of a list? 4. Miscellaneous mailer and other problems + Address with blanks are being treated separately + Why aren't my digests going out? + Why do I get duplicate mail sent to the list? + How do I gate my list to and/or from a newsgroup? + How can I improve Majordomo's performance? + How can I handle X.400 addresses? This FAQ is Copyright 1995 by David Barr and The Pennsylvania State University. This document may be reproduced, so long as it is kept in its entirety and in its original format. Credits: This FAQ originally written by Vincent D. Skahan. Many thanks to the members of the majordomo-workers and majordomo-users mailing lists for many of the questions and answers found in this FAQ. Thanks to fen@comedia.com (Fen Labalme) for getting an HTML version started. You can get an HTML version of this FAQ on the World Wide Web at http://www.math.psu.edu/barr/majordomo-faq.html. You can request a copy by email by sending a message to mail-server@rtfm.mit.edu, with the following text in the body: send usenet/comp.mail.list-admin.software/Majordomo_Frequently_Asked_Questions If you have any questions or submissions regarding this FAQ, send them to barr@math.psu.edu (David Barr). _________________________________________________________________ Section 1: What is Majordomo and how can I get it? WHAT IS MAJORDOMO? Majordomo is a program which automates the management of Internet mailing lists. Commands are sent to Majordomo via electronic mail to handle all aspects of list maintainance. Once a list is set up, virtually all operations can be performed remotely, requiring no intervention upon the postmaster of the list site. majordomo - n: a person who speaks, makes arrangements, or takes charge for another. From latin "major domus" - "master of the house". Majordomo is written in Perl (at least 4.036). It should also work under at least Perl 5.001a. It will not work with Perl 5.001!!! It has reportedly worked with Perl 5.000 on some but not all platforms. ftp://ftp.netlabs.com/pub/outgoing/perl5.0/perl5.001m.tar.gz is the latest release from the author. However, with Perl 5 you must edit majordomo and resend to look for instances of the "@" character inside text strings "something@something". Change the "@" to "\@". The same fix is also required if you want to run Majordomo under OSF/1 on the DEC AXP systems with Perl 4 or 5. [from Jim Reisert] Many people have been having problems with DEC OSF/1 AXP systems with Majordomo. Apparently Perl on the Alphas is not as stable as compared to other platforms, and Majordomo tickles bugs in that port of Perl. If you are having problems, please make sure you are running the very latest version of Perl. If anyone has successfully gotten a recent Majordomo to work on OSF/1 on the Alpha, please let the FAQ maintainer know how. There have also been reported problems with the native compiler for AIX 3.2.5. Perl compiled with that compiler will crash when running Majordomo (even though it passes all the regression tests), however if you compile Perl with gcc it will work. Majordomo was developed under UNIX based systems, but will probably work on others. If you can get Perl to compile and run cleanly on your system, and can send Internet mail by piping or calling an external program (and that external program reads its list of recipients from a plain text file), you can probably get Majordomo to work on a wide variety of UNIX-based and non-UNIX based systems. Majordomo controls a list of addresses for some mail transport system (like sendmail or smail) to handle. Majordomo itself performs no mail delivery (though it has scripts to format and archive messages). Here's a short list of some of the features of Majordomo. * supports various types of lists, including moderated ones. * List options can be set easily through a configuration file, editable remotely. * Supports archival and remote retrieval of messages. * Supports digests. * Written in Perl, - easily customizable and expandable. * Modular in design. * Includes support for FTPMAIL. There is a World Wide Web interface for Majordomo and other mail servers, called "Mailserv". Check it out at WHERE DO I GET IT? Via anonymous FTP at: ftp://ftp.greatcircle.com/pub/majordomo/ If you don't have Perl, you can get it from: ftp://ftp.netlabs.com/pub/outgoing/perl5.0/perl5.001m.tar.gz Information about Perl can be found from: http://www.metronet.com/perlinfo/perl5.html The FTPMAIL package can be found in ftp://src.doc.ic.ac.uk/packages/ftpmail or any comp.sources.misc archive (volume 37). HOW DO I INSTALL IT? Majordomo comes with a rather extensive README. Read this file completely. This FAQ is meant to be a supplement to Majordomo's documentation, not a replacement for it. If you have any questions that this FAQ doesn't cover, chances are that it is covered in the README or other documentation in the Majordomo distribution. For anyone who is going to run a list, you must read Doc/list-owner-info before trying to do anything. If you don't have access to the system where your list is being run, the Majordomo maintainer who set up your list should have sent it to you. Bug him if he didn't. If you have permission problems unpacking the distribution, try using the 'o' flag to ignore user/group information. HOW DO I UPGRADE FROM AN EARLIER RELEASE? Be sure to browse the "Changes" and "Changelog" files to get an idea what has changed. There currently is no canned set of instructions for upgrading from an earlier release. The most straightforward method is to simply install the current release in a different directory, (with the same list/archive/digest directories) and change the mail aliases for each list to use the new Majordomo scripts as soon as you feel comfortable with the new setup. WHERE DO I REPORT BUGS OR GET HELP WITH MAJORDOMO? If you need help, there is a mailing list majordomo-users@greatcircle.com, which is frequented by lots of users of Majordomo. Report bugs to majordomo-workers@greatcircle.com. Be sure always to include which version of Majordomo you are using. You should also include what operating system you are using, what version of Perl, and what mailer (sendmail, smail, etc) and version you are using, especially if you can't get Majordomo to work at all. But first, you must have thoroughly read the ALL documentation in the Majordomo distribution and this FAQ. If you got this FAQ from the Majordomo distribution, or anywhere except from the WWW site at the top of this document don't expect it to be up-to-date. It's probably not. Please don't ask the FAQ maintainer for help on Majordomo. I will probably accidently delete your message. Let me say that about 90% of the answers I give are from the documentation or this FAQ. Most of the rest are answered by reading the source. It's really not that hard to figure out. Do NOT ask questions about Majordomo on the list-managers@greatcircle.com list. That list is for general discussions about running mailing lists, not for help on specific packages. The same goes for the Usenet group comp.mail.list-admin.policy. There is a good guide for people running majordomo lists at http://www.uchicago.edu/a.docs/Mail/majordomo.admin.html. WHICH IS BETTER, MAJORDOMO OR LISTSERV? For a good comparison of various mailing list managers (MLM's) there's a good FAQ by Norm Aleks. It is posted monthly to news.answers and comp.mail.list-admin.software. It's also mirrored at the following URL. ftp://ftp.uu.net/usenet/news.answers/mail/list-admin/software-faq You can also request a copy via email, by sending the text "get mlm-software faq" in the body of a mail message to LISTSERV@listserv.net. Contact naleks@library.ummed.edu (Norm Aleks) for more information. Section 2: Problems setting up Majordomo WHAT ARE THE PROPER PERMISSIONS AND OWNERSHIP OF ALL MAJORDOMO FILES AND DIRECTORIES? By far the biggest problem in setting up Majordomo is getting all the permissions and ownerships right. In part this is due to the security model that Majordomo uses, and it's also due to the fact that it's hard to automate this process. That's due to improve in future releases. Majordomo works by using a small C "wrapper" which works by allowing Majordomo to always run as the "majordom" user and group that you create. (note that the wrapper may disappear in a future release, since its function could safely be replaced by features found in Perl 5) You can use a different name than "majordom" for your user and group, but that is what is assumed for the explanations found in this document. Because Majordomo does not run with any "special" (root) priviliges, and because of the fact that Majordomo does a lot of .lock-style locking (with shlock.pl), permissions on all files and directories are critical to the correct operation of Majordomo. The wrapper The wrapper is compiled in one of two ways, by uncommenting the correct section in the Makefile for your type of system. If you are unsure if your system is POSIX or not, I would suggest you assume that your system is not. (The default in 1.93 is POSIX) If things don't work right (for example you get symptoms of permission problems or you get an error from the wrapper saying to recompile using POSIX flags), then try POSIX. Some systems which are BSD: SunOS 4.x, Ultrix, most BSD 4.2 and 4.3-based systems. POSIX systems include Solaris 2.x, BSDI (and presumably other 4.4 BSD-based systems), Linux. If you are on a non-POSIX system, the wrapper must be both suid and sgid (mode 6755) to "majordom". It must not be setuid root! OR On a POSIX system the wrapper must be setuid root, and double-check that W_UID and W_GID are the uid and gid of the "majordom" user and group. Don't set W_UID to be 0! Then compile the wrapper and install it. Do not install the wrapper on an NFS filesystem with the "nosuid" option set. This will prevent the wrapper from working. Majordomo files All files that majordomo creates will be mode 660, user "majordom", group "majordom" if it is running correctly. The Log file that Majordomo writes logging information to must have this same permission and ownership. Make sure any files you create by hand (.config, subscription lists) have this same permission and ownership. (the can also be mode 664 if you don't need the contents to be private to others) The permissions/ownership of the Majordomo programs and related files themselves aren't as critical, but the must all be readable to the "majordom" user/group. All Majordomo programs (majordomo, resend, etc.) must have the execute bit set. Majordomo directories All directories under Majordomo's control ($homedir, $listdir, $digest_work_dir, $filedir, as defined in your majordomo.cf) must be mode 770 (or 775). They should be user and group owned by "majordom". If want to allow a local user to be able to directly modify files or for example copy files into a list's archive directory, you may make the directory or file owned by that user. However directories and files must be group-"majordom" writeable. I GET "UNKNOWN MAILER ERROR" WHEN MAJORDOMO RUNS If something is wrong with your setup, the wrapper will often exit with various return codes depending on what the problem is. In order to really understand what is going on, look at the session transcript further down in the bounce message to see the error which is returned from the wrapper or from Majordomo. You should always see some sort of error message. For information purposes, here are the current return codes from the wrapper: * 1: Usage error * 2: Insecure usage (argument to wrapper can't contain a '/') * 3: malloc() failed (out of memory) * 4: set[ug]id() failed, compile with POSIX instead of BSD flags * 5: execve() failed * >5: return code from perl [reported by Russell Street] You may also get problems when messages to majordomo are queued (for example if you change sendmail's behavior to always queue messages rather than perform immediate delivery). The problem was that if sendmail queues a message it smashes the case in command lines and addresses when the queue gets processed. This is inspite of the lines shown by mailq. This is sendmail 5.x on Solaris 2.3, but it might apply to other versions of sendmail. I GET "PERMISSION DENIED AT ..." WHEN MAJORDOMO RUNS I GET "SHLOCK: OPEN(">/SOME/PATH/..." WHEN MAJORDOMO RUNS A FILE IS VISIBLE VIA INDEX, BUT CAN'T 'GET' IT MAJORDOMO SEEMS TO BE TAKING MANY MINUTES TO PROCESS COMMANDS These are all symptoms of a permission or ownership problem. See the previous question. The directory specified of any "shlock" errors indicates a problem with that directory. A "get" problem means the ownership or permission of archive directory for that list is wrong. I GET AN ERROR "INSECURE USAGE" FROM THE WRAPPER The argument to "wrapper" should be simply be the command, not the full path to the command. "wrapper" has where to look compiled in to it (the "W_BIN" setting in the Makefile) and for security reasons will not let you specify another directory. Your alias should say for example: |"/path/to/majordomo/wrapper majordomo" I GET "MAJORDOMO: NO SUCH FILE OR DIRECTORY" FROM THE WRAPPER Make sure that the #! statement at the beginning of all the Majordomo Perl executables contain the correct path to the perl program (the default is /usr/local/bin/perl). Note many UNIXes have a 32 character limit on that path -- make sure it doesn't exceed this limit. 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. I GET AN ERROR "CAN'T LOCATE MAJORDOMO.PL" [from Brent Chapman] Majordomo adds "$homedir" from the majordomo.cf file to the @INC array before it goes looking for "majordomo.pl". Since it's not finding it, I'd guess you have one of two problems: 1) $homedir is set improperly (or not set at all; there is no default) in your majordomo.cf file. 2) majordomo.pl is not in $homedir, or is not readable. [from John P. Rouillard] 3) Note that the new majordomo.cf file checks to see if the environment variable $HOME is set first, and uses that for $homedir. Since the wrapper always sets HOME to the correct directory, you get a nice default, unless you are running a previously built wrapper, in which case you may get the wrong directory. [from Andreas Fenner] 4) I had the same problem when I installed majordomo (1.62). My Problem was a missing ";" in the majordomo.cf file - just in the line before setting homedir .... My hint for you: Check your perl-files carefully. I TOLD MY MAJORDOMO.CF WHERE TO ARCHIVE THE LIST, WHY ISN'T IT WORKING? [From John Rouillard] The archive variables in majordomo.cf aren't used to archive anything. You have to use a separate archive program, or a sendmail alias to do the archiving. The info is used to generate a directory where the archive files are being placed by some other mechanism. You are telling majordomo to look in the directory: /usr/local/mail/majordomo/archive/listname for files that it should allow to be gotten using the get command. Majordomo comes with three different archive programs that run under wrapper, that do various types of archiving. Look in the contrib directory. I'M ACCUMULATING LOTS OF FILES CALLED /TMP/RESEND.*.IN AND .OUT WHAT ARE THESE AND HOW CAN I GET RID OF THEM? This is a known bug in Majordomo 1.92. There was a typo in resend on line 347. Change the double-quotes to angle-brackets. (just like the other calls to unlink()) A LIST IS VISIBLE VIA LISTS, BUT CAN'T SUBSCRIBE OR 'GET' FILES [From Brent Chapman] I'll bet your list name has capital letters in it... Majordomo smashes all list names to all-lower-case before attempting to use the list name as part of a filename. So, while it's OK to advertise (for instance) "Majordomo-Users" and have the headers say "Majordomo-Users", the file names and archive directory names themselves all need to be in lower case. If you want to use mixed case, simply configure the list using the lower-case names everwhere, except put the mixed-case version in the "-l" and "-h" flags to resend. I GET "OUT OF MEMORY" WHEN UPGRADING TO 1.93 [summary of report from Matthew A. Braithwaite] There appears to be a bug in error reporting in Majordomo 1.93. Under certain circumstances, if the directory containing your Log file is not writable by majordomo then it will get caught in an infinite recursion, eventually allocating all the memory in the system. The fix is to make sure that the directory containing your Log file is user and group writeable, and user and group owned by your majordomo user and group. This doesn't work in all cases. There have been reports that some O/S have bugs in Perl's eval() routine causing this error. This condition will also arise if the wrapper is configured or installed improperly. Refer above for how to configure and install the wrapper on your system. I GET WARNINGS OR ERRORS WHEN TRYING TO COMPILE 1.93'S WRAPPER You're probably trying to compile the wrapper using the default Makefile on a non-POSIX system (like SunOS 4.x). As it says in the Makefile, SunOS isn't POSIX -- you need to use the BSD rules. If you're having trouble compiling the wrapper under AIX, change the line that says: char setgroups_used = "setgroups_was_included"; /* give strings a hint */ to char *setgroups_used = "setgroups_was_included"; /* give strings a hint */ The wrapper compilation may generate warnings under Linux and SunOS, which you can safely ignore. PROBLEMS WITH 1.93'S REQUEST-ANSWER [ Summary by Yusef Pisan ] There are a some known bugs in request-answer. If you get the error 'Undefined subroutine "main'lopen"' (or "main::lopen" for Perl 5), you need to insert the line 'require "shlock.pl";' near the beginning of request-answer. The syntax of the 'do_exec_sendmail' function is different in majordomo than in majordomo.pl, so you need to change all occurences of 'do_exec_sendmail' in request-answer to something like 'do_exec_sendmail_in_request_answer'. On line 41 where it exec()'s sendmail, change the "-f$list-request" to "-f$list-approval". I GET "INVALID ARCHIVE DIRECTORY. ABORTING." archive2.pl, as a security feature, refuses to write to directories other than ones "approved" for archiving. You need to edit the variable "@archive_dirs" in your majordomo.cf to list all the directories that you have set up for list archives. _________________________________________________________________ Section 3: Setting up mailing lists and aliases HOW DO I DIRECT BOUNCES TO THE RIGHT ADDRESS? You should use 'resend' to filter all messages. Make sure the "sender" keyword in the config file points to "owner-listname" and that you have defined the "owner-listname" alias to point to the owner of the list. What this does is force outgoing mail to have the out-of-band envelope FROM be "owner-listname", and thus all bounces will be redirected to that address. (Users often see this mirrored in the message body as the "From " or "Return-Path:" header). 'resend' also inserts a "Sender:" line with the same address to help people identify where it came from, but that header is not used for the bounce address. If you are using sendmail v8.x, you don't have to use 'resend' to do the same thing. You simply have to define an alias like this: owner-sample: joe, Note the trailing comma is necessary to prevent sendmail from resolving the alias first before putting it in the header. Without the comma, it will put "joe" in the envelope from instead of "owner-sample". Either address will work, of course, but the generic address is preferred should the owner ever change. However if you choose not to use 'resend', you will have to do without much of majordomo's other features like moderating, administravia checks, and others. SEMI-AUTOMATED HANDLING OF BOUNCED MAIL [From John Rouillard] Just create a mailing list called "bounces". I usually set mine up as an auto list just to make life easier. All that "bounce" script does is create an email message to majordomo that says: approve [passwd] unsubscribe [listname] [address] approve [passwd] subscribe bounces [address] The [address] and [listname], are given on the command line to bounce. The address of the majordomo, 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.COM bounces passwd3 Majordomo@This.COM bounces passwd4 Majordomo@Other.COM 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. WHAT'S THIS OWNER-LIST AND LIST-OWNER STUFF? WHY BOTH? [From David Barr] The "standard" is spelled out in RFC 1211 - "Problems with the Maintenance of Large Mailing Lists". It's here where the "owner-listname" and "listname-request" concepts got their start. (well it was before this, but this is where it was first spelled out) Personally, I don't use "listname-owner" anywhere. You don't really have to put both, since the "owner" alias is usually only for bounces, which you add automatically anyway with resend's "-f" flag, or having Sendmail v8.x's "owner-listname" alias. (while I'm on the subject) The "-approval" is a Majordomo-ism, and is only necessary if you want bounces and approval notices to go to different mailboxes. (though you'll have to edit some code in majordomo and request-answer if you want to get rid of the -approval alias, since it's currently hardwired in) So, to answer your question, I'd say "no". You don't have to have both. You should just have "owner-list". HOW SHOULD I CONFIGURE RESEND FOR REPLY-TO HEADERS? Whether you should have a "Reply-To:" or not depends on the charter of your list and the nature of its users. If the list is a discussion list and you generally want replies to go back to the list, you can include one. Some people don't like being told what to do, and prefer to be able to choose whether to send a private reply or a reply to the list just by using the right function on their mail agent. Take note that if you do use a "Reply-To:", then some mail agents make it much harder for a person on the list to send a private reply. If you are using resend, use the '-r ' flag to set the Reply-To field to the list, or use the 'reply_to' config keyword for 1.9x or greater. HOW CAN I HIDE LISTS SO THEY CAN'T BE VIEWED BY 'LISTS'? That is what advertise and noadvertise are for. The two keywords take regular expressions that are matched against the from address of the sender. A list display follows the rules: 1. If the from address is on the list, it is shown. 2. If the from address matches a regexp in noadvertise (e.g. /.*/) the list is not shown. 3. If the advertise list is empty, the list is shown unless 2 applies. 4. If the advertise list is non-empty, the from address must match an address in advertise. Otherwise the list is not shown. Rule 2 applies, so you could allow all hosts in umb.edu except hosts in cs.umb.edu. HOW CAN I RESTRICT A LIST SUCH THAT ONLY SUBSCRIBERS CAN SEND MAIL TO THE LIST? For pre-1.9x versions of majordomo, see the -I option to resend. For 1.9x this is the restrict_post keyword in the config file. Just set it to the filename that holds the list of subscribers. Unfortunately this means you probably will need help from the Majordomo maintainer in setting it if you don't have access to the host machine. This is due to be improved in a future release of Majordomo. However, there is a problem with either of these methods. Majordomo works by filtering the messages coming in through the "listname" alias, doing its dirty work, then passing the resulting message out to another alias you define like "listname-outgoing". If you trust people to not send mail directly to the "listname-outgoing" alias, then you'll be fine. If however you're not trusting, there are several steps to make sure people don't bypass the restrictions of the list. There are several methods. First you need to change your "listname-outgoing" alias such that it is not obvious. Next, you need to make it such that people can't find out what your -outgoing alias is. You can use the "@filename" directive in resend to move the command-line options of resend into a file readable only by the majordomo user/group. This will make it such that you can't find out the -outgoing address by connecting to your mailer and doing an EXPN or VRFY. The "@filename" directive seems to have fallen into undocumentation for some reason. This should be fixed in future releases. Another more direct approach is to simply disable EXPN or VRFY altogether. See the documentation for your mailer on how to do this. However this doesn't prevent local reading if the aliases file. Sendmail 8.x will unfortunately log your -outgoing alias in the "Received:" lines. To get around this you need to specify more than one address for the list name argument to resend. The easiest way is to simply put a comma after your -outgoing address. (for example "mylist: :include:/var/lists/mylist,") For Sendmail 8.x you must not define an alias 'owner-mylist-seekrit' to be something like 'owner-mylist,' (with the commma). Otherwise sendmail will set the envelope address of outgoing mail to contain your secret outgoing alias. Finally it should be noted that it is impossible with any method to prevent people from forging mail as someone on the list, and sending to the list that way. CAN I HAVE THE LIST OWNER OR APPROVAL PERSON BE CHANGEABLE WITHOUT INTERVENTION FROM THE MAJORDOMO OWNER? Sure! Just make owner-listname and/or listname-approval be another majordomo list. (probably hidden, for simplicity's sake) WHAT ABOUT ALL OF THESE PASSWORDS STARTING IN VERSION 1.90? Think of three separate passwords: 1. A master password that can be used by both resend and majordomo contained in [listname].passwd. To be used by the master list manager when using writeconfig commands etc. This allows someone who handles a number of mailing lists all using the same password. 2. A password for the manager of this one list. The admin_passwd can be used by subsidiary majordomo list maintainers. 3. A password for those concerned with the list content (approve_passwd) This way the administration and moderation functions can be split. The original reason for maintaining [listname].passwd was to allow a new config file to be put in if the config file was trashed and the admin_password was obliterated, and may still be useful to allow a single password to be used for admin functions by the majordomo admin or some other "superadmin". Note that the admin passwd in the config file is not a file name, but the password itself. This is the only way that the list-maintainer could change the password since they wouldn't have access to the file. HOW DO I TELL MAJORDOMO TO HANDLE "GET"-ING OF BINARY FILES? Majordomo is not designed to be a general-purpose file-by-mail system. If you want to do anything more than trivial "get"-ing of text files (archives, etc) than you should get and install ftpmail. Majordomo has hooks to allow transparent access to files via ftpmail (see majordomo.cf). See the beginning of this FAQ for where to get ftpmail. HOW DO I SET UP A MODERATED LIST? First, you need to tell Majordomo that the list is moderated. In the configuration file for the list, you set "moderated = yes". If you're using Majordomo 1.9x or greater, do not try to use the now-deprecated "-A" option to resend. In fact if you're using 1.9x or greater, you shouldn't be using ANY options to resend except "-h" and "-l". Any mail which is not "approved", gets bounced with "Approval required". If the moderator wishes to approve the message for the list, then you need to tag the message as "approved" and send it to the list. The "approve" script which comes with Majordomo does this for you. If you don't have access to "approve" (e.g. you're not on a UNIX system with Perl), you have to do it by hand. The easiest way is to forward the original message to the list, add the line "Approved: approval-password" to the very first line of the body, leave a blank line, and then the contents of the original message. (meaning there should be a blank line before and after the "Approved:" line.) HOW DO I SET UP A DIGESTED VERSION OF A LIST? [ Modified from explanation given by jmb@kryten.atinc.com (Jonathan M. Bresler)] * Create aliases for the mailing list and the digest. See section 2.2 of the README for an example. * create an alias for the majordom(o) user, so that his cron generated mail comes to me, rather than just piling up in /usr/local/mail/majordom. * create the list's and the digest's files, (widget, widget-digest, widget.config, widget-digest.config, etc.). Edit the widget-digest.config file and make sure all the digest options are set to your tastes. * create the digest directory and archive directory. See FAQ section 2 on how to set permissions on all majordomo files and directories. You must have archives if you have digests so the digester can make the digest. You can purge the archive after the digest is generated. * Add yourself to both the mailing list and its digest so you can monitor what happens...at least for a while (not a bad idea to create a dummy user, and subscribe him to both the mailing list and its digest. This preserves a record of messages for debugging. Don't forget to remove this account and unsubscribe it after debugging.) * Optionally you may add a crontab for majrodom, to push out a digest at set intervals regardless of the number of queued messages. Of course you can do this from any account not just majordom, as long as the password is correct. See the question Why aren't my digests going out?". _________________________________________________________________ Section 4: Miscellaneous mailer problems ADDRESS WITH BLANKS ARE BEING TREATED SEPARATELY If a subscriber to the list is John Doe it gets treated these as the three addresses: John Doe [From Alan Millar] Majordomo does not treat these as three addresses. Apparently your mailer does. Remember that all Majordomo does is add and remove addresses from a list. Majordomo does not interpret the contents of the list for message distribution; the system mailer (such as sendmail) does. I'm using SMail3 instead of sendmail, and it has an alternative (read "stupid") view of how mixed angle-bracketed and non-angle-bracketed addresses should be interpreted. I found that putting a comma at the end of each line was effective to fix the problem, and I got to keep my comments. So I patched Majordomo to add the comma at the end of each address it writes to the list file. You can also add the $listname.strip option so that none of the addresses are angle-bracketed. (the "strip" config option for 1.90) WHY AREN'T MY DIGESTS GOING OUT? >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. [from John Rouillard] echo mkdigest [digest-name] [digest-password] | 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. WHY DO I GET DUPLICATE MAIL SENT TO THE LIST? I've you're running MMDF, read on: [From Gunther Anderson] Well, I can tell you what happened to me recently. We use MMDF here, which certainly colors the picture a little. What was happening here was that MMDF was verifying the validity of the whole mailing list before returning from the Submit call. The thing calling the Submit would time out and close, but the Submit itself would still be running somewhere. The calling routine would believe that the message had failed in its delivery, but the Submit would eventually succeed. The calling process would try again some time later. This, of course, is bad. The larger the list got, the more addresses there were to verify (verification was really just a DNS search on the target machine name), the more likely, under load, that the message would duplicate. We finally got so large, with so many international addresses (which seem to timeout on DNS queries much more ofen than US addresses) that we were always duplicating. Infinitely (until I killed the original submitter). The solution for us was MMDF-specific. We used a different channel for submission and delivery, one which deliberately doesn't verify the addresses before accepting a job. We used the list-processor channel, and only had to check that the listname-request name was set properly, because list-processor insists on making listname-request the envelope "From " header name. If you're running Sendmail, this is more rare. There have been unconfirmed reports that on some systems having the queue process interval set too short can cause problems, even though sendmail is supposed to handle this. Workarounds are to increase your queue process interval (-q flag), or decrease the interval between queue checkpoints (OC flag in sendmail.cf). There have been many reports from Linux users complaining about duplicate mail. The problem seems to be that flock() under Linux is broken. This may be fixed in a future release, but for now in sendmail's conf.h in the #ifdef __linux__ section add a line #define HASFLOCK 0. There are also reports that some versions of the libc have problems, and that linking with the libresolv.a from a recent BIND version will work around the problem. [ Please let me know if you have any more information --ed ] HOW DO I GATE MY LIST TO AND/OR FROM A NEWSGROUP? The easiest method is to use a program called newsgate. Send mail to rsalz@uunet.uu.net (Rich Salz) for a copy. Unless he tells you otherwise, do not redistribute what he sends you. Installation instructions are straightforward, it provides sample entires for your newsfeeds/sys file and aliases entries. The newsgate package includes news2mail and mail2news. HOW CAN I IMPROVE MAJORDOMO'S PERFORMANCE? Mail to list throughput Majordomo does very little except pass each message to the list through 'resend', and then pass it on to your mailer for distribution. Improving your mailer is the first step to improving speed of delivery of mail to the list. Upgrading your sendmail to version 8.6.x or greater will improve things greatly, as this version has a lot of enhancements which use connections more efficiently. For most lists, this is enough. Majordomo itself doesn't use very much resources except perhaps memory. Adding more memory will help if your machine does a lot of paging during mail delivery. Using other mailers instead of sendmail like ZMailer has met with varying success. If your lists are very large you may try installing bulk_mailer, by Keith Moore. It pre-sorts the list into chunks grouped by site, and passes the resulting chunks off to individual sendmail processes for delivery (see note next paragraph). Get it from ftp://cs.utk.edu/pub/moore/bulk_mailer/. It installs simply by replacing your usual -outgoing alias with (line wrapped for clarity): sample-outgoing: |"/path/to/bulk_mailer owner-sample@your.site /path/to/lists/sample" This has reportedly resulted in dramatic speedups in delivery times, on the order of several times faster. Note this works just as well on digested lists as well as normal lists. bulk_mailer does have one problem. It doesn't understand parenthesized comments in addresses, resulting in incorrect sorting and reduced performance. Either your list must be configured with strip=yes in the configuration file, or a patch has recently been submitted to the author for a -m option to strip these comments before sorting. Look for it to be incorporated soon. The restrict_post list option with large lists can cause a significant slowdown in mail delivery, since resend has to do a sequential search through the subscription list for each mail sent to the list (to verify that the sender is subscribed to the list). Think twice about using this option with very large lists. Majordomo command processing Most of the improvements in this are are experimental and not widely available or not yet completed but scheduled for future releases. Some areas include: improvements in shlock.pl to use exponential backoffs to reduce contention and starvation of locks, using some sort of dbz-style database for subscription lists to speed up subscribe and unsubscribe commands, and changes in the configuration file system to allow faster parsing and faster execution of certain commands such as "lists". If you are interested in working on improvements in this area, join the majordomo-workers list mentioned above. If you make any specific patches or additions available, please let me know so I can add references to it here. HOW CAN I HANDLE X.400 ADDRESSES? Majordomo by default treats addresses starting with "/" as "hostile", and won't let people subscribe. This is to prevent someone from subscribing a majordomo-owned filename to the list, and being able to write by sending mail to the list. Unfortunately, all X.400 addresses begin with a "/". Starting in Majordomo 1.93, there are three variables in the majordomo.cf which control how majordomo treats these sorts of addresses. See the end of the sample.cf in the Majordomo 1.93 distribution for a complete explanation. From majordomo-users-owner Fri Sep 15 14:00:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA25657 for majordomo-users-outgoing; Fri, 15 Sep 1995 13:48:29 -0700 Received: from hops.wharton.upenn.edu (HOPS.WHARTON.UPENN.EDU [130.91.160.179]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA25648 for ; Fri, 15 Sep 1995 13:48:25 -0700 Received: (from loren@localhost) by hops.wharton.upenn.edu (8.6.10/8.6.9) id QAA04016 for majordomo-users@greatcircle.com; Fri, 15 Sep 1995 16:47:10 -0400 From: Loren Miller Message-Id: <199509152047.QAA04016@hops.wharton.upenn.edu> Subject: blasted aliases file into smithereens To: majordomo-users@greatcircle.com Date: Fri, 15 Sep 1995 16:47:10 -0400 (EDT) Reply-To: loren@hops.wharton.upenn.edu X-Eyes: corrected X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1510 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have apparently blasted my aliases file into smithereens while performing an upgrade so that my tape reader would work better, and as the tape reader isn't working right yet I haven't been able to retrieve current backups of it. I have several mailing lists which are digested using the digest script and when they were sent out majordomo somehow would pop the complete digest into a file called v001n123 where 001 is the volume and 123 is the number. Assuming the name of the list is fubar and fubar-digest is the digested version, the digest script would keep individual messages in /usr/local/mail/Digests/fubar-digest/001 and so on until the digest passes the size limit and then it would be sent out and a copy of the digest put in /usr/local/mail/Lists/fubar-digest.archive/v01n123. Unfortunately, though I have been able to get the direct reflecting version of fubar and other mailing lists working, and digest pops them into the correct directory for compilation, it doesn't actually send out the digests or put them into the appropriate archive directory. None of the settings in any of the config files or the directory permissions have changed. I know the problem is in the aliases file. If you have an aliases file that does something like this for your copy of majordomo (1.92) please send it my way. I'd greatly appreciate it. Thanks. -- +++++++++++++++++++++++23 Loren Miller Working my butt off and wishing I had the time and the equipment to sit down. From majordomo-users-owner Fri Sep 15 15:30:55 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA01340 for majordomo-users-outgoing; Fri, 15 Sep 1995 15:11:08 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id PAA01333 for ; Fri, 15 Sep 1995 15:11:05 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by tetsuo.communique.net (8.6.12/8.6.12) with SMTP id RAA46521 for ; Fri, 15 Sep 1995 17:09:51 -0500 Date: Fri, 15 Sep 1995 17:09:51 -0500 (CDT) From: Raul Zighelboim To: majordomo-users@GreatCircle.COM Subject: Re: bounces In-Reply-To: <199508212030.PAA03307@rs232.bb-elec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Help! When sending requests to Majordomo, I get an error message back; It seems that majordomo (or resend) cannot send mail to test-approval nor (any list)-approval. If I try to send mail to test approval via pine, everything seems to work ok. ----- Transcript of session follows ----- 550 test-approval... User unknown: No such file or directory ----- Unsent message follows ----- Received: by tetsuo.communique.net (AIX 3.2/UCB 5.64/4.03) id AA46786; Fri, 15 Sep 1995 21:52:27 GMT Date: Fri, 15 Sep 1995 21:52:27 GMT Message-Id: <9509152152.AA46786@tetsuo.communique.net> To: test-approval From: Majordomo Subject: APPROVE test Reply-To: Majordomo -- ----------------------------------------------------------------------------- Raul Zighelboim e-mail: mango@communique.net Communique Inc. Tel: 504.527.6200 Technical Specialist Fax: 504.527.6030 From majordomo-users-owner Fri Sep 15 15:32:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA01517 for majordomo-users-outgoing; Fri, 15 Sep 1995 15:15:14 -0700 Received: from cmcl2.NYU.EDU (NYU.EDU [192.76.177.18]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA01508 for ; Fri, 15 Sep 1995 15:15:07 -0700 Received: from WOTAN.CNS.NYU.EDU by cmcl2.NYU.EDU (5.61/1.34) id AA13378; Fri, 15 Sep 95 18:09:46 -0400 Received: by wotan.cns.nyu.edu (4.1/SMI-4.0) id AA01096; Fri, 15 Sep 95 18:12:21 EDT Date: Fri, 15 Sep 1995 18:06:39 -0400 (EDT) From: Ariel Spivakovsky Subject: Re: Upgraded to perl 5.001 To: Andy Banks 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 I have perl 5.01 as /usr/bin/perl I also have perl 5.00 as /usr/bin/perl500 and MD 1.93. I just changed all all the entries in the MD code to be #!/usr/bin/perl500. It works fine. Cheers Ari oooooooooooooooooooooooooooooooooooooooooooooo O Ariel Spivakovsky O O spiv@wotan.cns.nyu.edu O O ------------------------- O oooooooooooooooooooooooooooooooooooooooooooooo On Wed, 6 Sep 1995, Andy Banks wrote: > > Well, I had a few other programs that required the use of perl 5.001 so I > upgraded from 4.036. Now it seems that whenever majordomo is called > upon, I get an error saying: > > eval of majordomo.cf failed Literal @minuteman now requires backslash at > (eval 1) line 5, within string > 554 "|/home/majordomo/wrapper majordomo"...unknown mailer error 29 > > I've played with a few things, but before I restore perl 4.036, does > anyone have any other suggestions as to what I can do to fix this? > > TIA, > > > __ > > __________________________________________________________________ > Andy Banks Minuteman Press of Tysons > andy@minuteman.com printing@minuteman.com > http://minuteman.com/xman http://minuteman.com/mmp > __________________________________________________________________ > From majordomo-users-owner Fri Sep 15 16:30:25 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA05949 for majordomo-users-outgoing; Fri, 15 Sep 1995 16:21:32 -0700 Received: from triumph.cs.utah.edu (triumph.cs.utah.edu [155.99.208.4]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id XAA23834 for ; Thu, 14 Sep 1995 23:24:12 -0700 Received: (from mjb@localhost) by triumph.cs.utah.edu (8.6.10/8.6.6) id AAA20248; Fri, 15 Sep 1995 00:22:50 -0600 Date: Fri, 15 Sep 1995 00:22:50 -0600 From: Mark J Bradakis Message-Id: <199509150622.AAA20248@triumph.cs.utah.edu> To: majordomo-users@GreatCircle.COM Subject: String matching? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We're running version 1.92 here, and it seems that when checking lists for users, majordomo claims that "user" is not in the list, for unsubscribes and private functions, though the list would have ... user otheruser luser@host ... It does match if there is an at sign in the address, user@host, but a lone user name fails. Perusal of the FAQ and various docs turned up no clue, any quick suggestions on how to fix this? mjb. From majordomo-users-owner Fri Sep 15 16:32:44 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA04575 for majordomo-users-outgoing; Fri, 15 Sep 1995 16:04:59 -0700 Received: from hq.stargame.org (bh.mindspring.com [168.121.33.204]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id QAA04557 for ; Fri, 15 Sep 1995 16:04:54 -0700 Received: (from bh@localhost) by hq.stargame.org (8.6.12/8.6.9) id SAA04522; Thu, 14 Sep 1995 18:08:22 -0400 Date: Thu, 14 Sep 1995 18:08:22 -0400 (EDT) From: Brian Hartsfield To: "Leip, D" cc: majordomo-users Subject: Re: Subscribing a ML to an ML In-Reply-To: <9509131719.AA0116@tormail1.torolab.ibm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Wed, 13 Sep 1995, Leip, D wrote: > > I've got two questions that I hope someone can answer for me. > > 1) Is it possible to subscribe one majordomo list to another (on > the same server)? I can't see why not, but I thought I'd ask > before have my sys-admin create a list only to find out that it > doesn't work. Yes, but be VERY CAREFUL if you do so. You can very easily create a mail loop if you are not careful. Double and triple check everything. Brian From majordomo-users-owner Fri Sep 15 17:00:13 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA04662 for majordomo-users-outgoing; Fri, 15 Sep 1995 16:06:22 -0700 Received: from hq.stargame.org (bh.mindspring.com [168.121.33.204]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id QAA04655 for ; Fri, 15 Sep 1995 16:06:16 -0700 Received: (from bh@localhost) by hq.stargame.org (8.6.12/8.6.9) id SAA04529; Thu, 14 Sep 1995 18:09:41 -0400 Date: Thu, 14 Sep 1995 18:09:41 -0400 (EDT) From: Brian Hartsfield To: "Leip, D" cc: majordomo-users Subject: Re: Subscribing a ML to an ML In-Reply-To: <9509131719.AA0116@tormail1.torolab.ibm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Wed, 13 Sep 1995, Leip, D wrote: > > I've got two questions that I hope someone can answer for me. > > 1) Is it possible to subscribe one majordomo list to another (on > the same server)? I can't see why not, but I thought I'd ask > before have my sys-admin create a list only to find out that it > doesn't work. And if you are subscribing a majordomo list that you do not own to a list that you own, NOTIFY THE LIST-OWNER of the list you are subscribing BEFORE you do it. I had to put that in. I've been fighting some idiot that keeps subbing my lists to one of his even after being told several times not to do so. Brian From majordomo-users-owner Fri Sep 15 17:02:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA05969 for majordomo-users-outgoing; Fri, 15 Sep 1995 16:21:45 -0700 Received: from hq.stargame.org (bh.mindspring.com [168.121.33.204]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id MAA21291 for ; Fri, 15 Sep 1995 12:34:10 -0700 Received: (from bh@localhost) by hq.stargame.org (8.6.12/8.6.9) id OAA03469; Thu, 14 Sep 1995 14:36:51 -0400 Date: Thu, 14 Sep 1995 14:36:51 -0400 (EDT) From: Brian Hartsfield To: Bowden Wise cc: majordomo-users@GreatCircle.COM Subject: Re: Admin Bounces In-Reply-To: <199509130231.AA17754@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Tue, 12 Sep 1995, Bowden Wise wrote: > When someone sends a subscribe message to a list, I am using resend > with administrative checking, and the BOUNCE admin message is getting > sent to me, the list owner. But....does the person who sent the > message get anything back?? I think it would be good if they got the > request-answer message returned to them so that they would know to > send their request to the majordomo address. But it looks like the > message is just sent to me and then I must resolve it? is this the > way it is supposed to work? Yes. You have to decide if this is a legitimate message or somebody eas stupid and sent a subscribe to the list address. You are to look at it and if it is a valid message approve it. It was an admin request then you can do what you want to with it. Brian From majordomo-users-owner Fri Sep 15 17:04:55 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA05983 for majordomo-users-outgoing; Fri, 15 Sep 1995 16:21:53 -0700 Received: from unilab.dfci.harvard.edu (unilab.dfci.harvard.edu [155.52.46.57]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA24164 for ; Fri, 15 Sep 1995 13:24:37 -0700 Received: (from ratinox@localhost) by unilab.dfci.harvard.edu (8.6.12/8.6.9) id QAA14431; Fri, 15 Sep 1995 16:23:18 -0400 Date: Fri, 15 Sep 1995 16:23:18 -0400 Message-Id: <199509152023.QAA14431@unilab.dfci.harvard.edu> From: Richard Pieri To: Majordomo-users@GreatCircle.COM CC: leip@vnet.ibm.com In-reply-to: "Leip, D"'s message of Wed, 13 Sep 95 13:25:40 Subject: Re: Subscribing a ML to an ML References: <9509131719.AA0116@tormail1.torolab.ibm.com> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- 0> 1) Is it possible to subscribe one majordomo list to another (on 0> the same server)? Sure; just make sure that when you subscribe list B to list A you don't accidentally subscribe list A to list B. 0> 2) Is it possible to completely restrict the use of the list 0> command to just the owner or disable it altogether? Not without modifying Mj code and that would disable the commands for all lists. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Processed by Mailcrypt 3.3, an Emacs/PGP interface iQCVAwUBMFngrJ6VRH7BJMxHAQGUcwP/erNQjNpNiQGAvF0sfsJ9xo8BGefE46Gr yCvesUk2SE+EUQhOSE1bK6XI8vGP1ZGjB7ERv/05Sxb5tTR5U4Qvvq+6uKYAIj1m 2R46S9mQ2CwpBzBHYqSUU9Oxz1u86Xy8wGTKap9AEeWNXUgEo/nE7ik9cao5BI3w E++7yk3esaY= =hiO9 -----END PGP SIGNATURE----- -- Richard Pieri/Information Services \ When eating out, think nothing of sending \ back your meal twenty or thirty times. -A http://www.dfci.harvard.edu/~ratinox \ cat's guide to life From majordomo-users-owner Fri Sep 15 17:09:47 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA06034 for majordomo-users-outgoing; Fri, 15 Sep 1995 16:22:21 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA26209 for ; Fri, 15 Sep 1995 13:59:42 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA25398 for majordomo-users@greatcircle.com; Fri, 15 Sep 95 13:58:27 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA07763; Fri, 15 Sep 95 13:58:25 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA16334 for majordomo-users@greatcircle.com; Fri, 15 Sep 95 13:58:23 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA05597; Fri, 15 Sep 95 15:58:19 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA19705; Fri, 15 Sep 1995 15:58:18 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509152058.AA19705@miaow.sps.mot.com> Subject: Re: Subscribing a ML to an ML To: leip@VNET.IBM.COM Date: Fri, 15 Sep 1995 15:58:17 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <9509131719.AA0116@tormail1.torolab.ibm.com> from "0" at Sep 13, 95 01:25:40 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 788 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ 0 writes: ] One can't help but wonder what the 0 signifies. :-) > 1) Is it possible to subscribe one majordomo list to another (on > the same server)? Yes, any address can be subscribed (some just make more sense than others :-). You probably want to subscribe the :include: version of the list alias so that you don't run messages through resend twice. Of course, that exposes the alias to anyone allowed to do a 'who', but maybe you don't care. > 2) Is it possible to completely restrict the use of the list > command to just the owner or disable it altogether? Anything's possible, but in this case, not without modifying the majordomo code. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Fri Sep 15 17:11:44 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA06044 for majordomo-users-outgoing; Fri, 15 Sep 1995 16:22:30 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA26538 for ; Fri, 15 Sep 1995 14:05:39 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA27054 for majordomo-users@greatcircle.com; Fri, 15 Sep 95 14:04:24 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA07960; Fri, 15 Sep 95 14:04:22 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA17102 for majordomo-users@greatcircle.com; Fri, 15 Sep 95 14:04:20 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA05672; Fri, 15 Sep 95 16:04:19 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA11393; Fri, 15 Sep 1995 16:04:17 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509152104.AA11393@miaow.sps.mot.com> Subject: Re: Admin Bounces To: wiseb@cs.rpi.edu Date: Fri, 15 Sep 1995 16:04:17 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <9509150459.AA11783@colossus.cs.rpi.edu> from "cs.rpi.edu!wiseb" at Sep 15, 95 00:59:47 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1063 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ uunet!cs.rpi.edu!wiseb writes: ] > > Whenever I get an admin bounce (someone sends a subscribe to the list), > I get TWO messags; the first is the BOUNCE message with an empty body, > and the second is the original message. This seems odd, should I just get > one message with the original message in the body of the BOUNCE message? > > is this the way it is supposed to work or is something fishy happening > here? Do the headers on the original message indicate it was re-addressed to you (as owner-listname) or is it still addressed to the list? If the latter, then it probably *is* being delivered to you as one message with the original in the body, but your mail reader is splitting it into 2 messages. If the bounce message has a correct Content-Length header, then you need to get a smarter mail reader (or reconfigure it correctly). Otherwise, you need to reconfigure sendmail to escape enclosed From headers. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Sat Sep 16 11:32:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA00226 for majordomo-users-outgoing; Sat, 16 Sep 1995 11:31:06 -0700 Received: from presence.lglobal.com (presence.lglobal.com [204.50.121.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA00219 for ; Sat, 16 Sep 1995 11:31:00 -0700 Received: from presence.lglobal.com (jesse@presence.lglobal.com [204.50.121.2]) by presence.lglobal.com (8.6.12/8.6.12) with SMTP id QAA06686 for ; Fri, 25 Aug 1995 16:33:38 -0400 Date: Fri, 25 Aug 1995 16:33:37 -0400 (EDT) From: Jesse Hirsh To: majordomo-users@greatcircle.com Subject: Returned mail: unknown mailer error 1 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="QAA06516.809382461/presence.lglobal.com" Content-ID: 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. Send mail to mime@docserver.cac.washington.edu for more info. --QAA06516.809382461/presence.lglobal.com Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Help me, I'm still getting these errors. What could it be? /~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\ Jesse Dillan Hirsh jesse@lglobal.com Information Revolutionary Local GlobalAccess Toronto Ontario Canada (416) 515-7400 Disseminating Information & Power Onto The Community Level "It's all just a dream babe, a vacuum, a scheme babe, that sucks you into feeling like this." ---------- Forwarded message ---------- Date: Fri, 25 Aug 1995 16:27:41 -0400 From: Mail Delivery Subsystem To: owner-majordomo@lglobal.com Subject: Returned mail: unknown mailer error 1 The original message was received at Fri, 25 Aug 1995 16:27:19 -0400 from root@newsgate.dircon.co.uk [194.129.52.15] ----- The following addresses had delivery problems ----- "|/usr/local/majordom/wrapper majordomo" (unrecoverable error) (expanded from: ) ----- Transcript of session follows ----- Message delivered to mailing list Out of memory! 554 "|/usr/local/majordom/wrapper majordomo"... unknown mailer error 1 Message delivered to mailing list owner-majordomo ----- Original message follows ----- --QAA06516.809382461/presence.lglobal.com-- From majordomo-users-owner Sat Sep 16 12:00:04 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA01665 for majordomo-users-outgoing; Sat, 16 Sep 1995 11:54:26 -0700 Received: from hq.stargame.org (bh.mindspring.com [168.121.33.204]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA01651 for ; Sat, 16 Sep 1995 11:54:22 -0700 Received: (from bh@localhost) by hq.stargame.org (8.6.12/8.6.9) id NAA08828; Fri, 15 Sep 1995 13:57:52 -0400 Date: Fri, 15 Sep 1995 13:57:52 -0400 (EDT) From: Brian Hartsfield To: "Chandra S. Chitneni" cc: majordomo-users@GreatCircle.COM Subject: Re: HELP( BOUNCE faculty: Admin request) 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, 16 Sep 1995, Chandra S. Chitneni wrote: > > Thanks for your help. I found that -s switch is set to the resend. And > that is what caused the BOUNCE. > > * By the way for some reason even if I set the noadvertise to have /.*/ > still the list is getting displayed. Under advertise I have nothing set. If you are subscribed to a list you will ALWAYS see it in a lists command even if it is not set advertised. So you need to make sure you are testing advertise/unadvertise settings from an account not subscribed to the list you are testing. Brian From majordomo-users-owner Sat Sep 16 12:02:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA00545 for majordomo-users-outgoing; Sat, 16 Sep 1995 11:39:48 -0700 Received: from law.uoregon.edu (law.uoregon.edu [128.223.106.198]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA00538 for ; Sat, 16 Sep 1995 11:39:44 -0700 Received: (from chandra@localhost) by law.uoregon.edu (8.6.12/8.6.12) id LAA07691; Sat, 16 Sep 1995 11:38:20 -0700 Date: Sat, 16 Sep 1995 11:38:20 -0700 (PDT) From: "Chandra S. Chitneni" To: Brian Hartsfield cc: majordomo-users@GreatCircle.COM Subject: Re: HELP( BOUNCE faculty: Admin request) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thanks for your help. I found that -s switch is set to the resend. And that is what caused the BOUNCE. * By the way for some reason even if I set the noadvertise to have /.*/ still the list is getting displayed. Under advertise I have nothing set. Does anybody have similar problem. Thanks, -chandra On Thu, 14 Sep 1995, Brian Hartsfield wrote: > > > On Thu, 14 Sep 1995, Chandra S. Chitneni wrote: > > > > > I have a list called faculty. It is not a moderated list. When one of > > the faculty member posted a message, I(ownet-faculty) got the message > > forwarded with the subject > > > > BOUNCD faculty: Admin request. > > > > Can somebody tell me when I would usually get this kind of message. This > > list was working OK so far until today when I saw this message. > > Majordomo tries to identify admin requests that should go to majordomo > that are sent to the list address by mistake. It is at times overly > paranoid. That is why the message got bounced to you. It identified it > as a possible messages that should have goine to majordomo. It is was > not, just approve the message like you would for a moderated list and it > will be sent to the list. > > Brian > > From majordomo-users-owner Sat Sep 16 15:00:17 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA06148 for majordomo-users-outgoing; Sat, 16 Sep 1995 14:46:57 -0700 Received: from smuggler.bbn.com (SMUGGLER.BBN.COM [128.89.7.132]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id SAA13961 for ; Fri, 15 Sep 1995 18:29:41 -0700 Received: from smuggler.bbn.com (LOCALHOST.BBN.COM [127.0.0.1]) by smuggler.bbn.com (8.6.9/8.6.6) with ESMTP id VAA05120; Fri, 15 Sep 1995 21:28:11 -0400 Message-Id: <199509160128.VAA05120@smuggler.bbn.com> To: "Chandra S. Chitneni" Cc: majordomo-users@greatcircle.com Subject: Re: HELP( BOUNCE faculty: Admin request) In-reply-to: Your message of "Thu, 14 Sep 1995 10:16:26 PDT." <199509141716.KAA01807@law.uoregon.edu> Date: Fri, 15 Sep 1995 21:28:10 -0400 From: "John C. Orthoefer" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Humm, here is a list of things which cause the Admin request mail. Something I've been meaning to look up in the code. Subject line with subscribe, unsubscribe, help, RCPT, change...address, request...addition. First 5 lines of the body contain: add me delete me remove me help change...address subscribe sub unsubscribe unsub ... stands for the regex .* ie any characters, any number. Johno - From majordomo-users-owner Mon Sep 18 12:32:53 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA02907 for majordomo-users-outgoing; Mon, 18 Sep 1995 12:08:55 -0700 Received: from optical.fiber.net (optical.fiber.net [204.250.13.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA02900 for ; Mon, 18 Sep 1995 12:08:50 -0700 Received: by optical.fiber.net (NX5.67e/NX3.0M) id AA20977; Mon, 18 Sep 95 13:04:40 -0600 Message-Id: <9509181904.AA20977@optical.fiber.net> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Carl Payne Date: Mon, 18 Sep 95 13:04:37 -0600 To: majordomo-users@greatcircle.com Subject: New install: nothing outgoing Reply-To: cpayne@optical.fiber.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've read the FAQ, the MIIS book, and still can't find a way to test that the list is sending content to its subscribers. Basically, a subscription request goes through and seems just fine, but doesn't sent the list.info file. Also, any other requests made to the server just throw back the "this pre-recorded message" note. Sending to the list, and the log is blank, nothing in the list file, nothing but "Sent" in the syslog. All permissions are correct. I'm sure it's something trite and basic and I've overlooked something, but here it is: day 4 for trying to get this going, so I'm calling for reinforements. Thanks for your time. BTW, the system is a Pentium-90 running NeXTSTEP 3.3 Carl From majordomo-users-owner Mon Sep 18 15:03:20 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA12583 for majordomo-users-outgoing; Mon, 18 Sep 1995 14:32:00 -0700 Received: from presence.lglobal.com (presence.lglobal.com [204.50.121.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id OAA12576 for ; Mon, 18 Sep 1995 14:31:55 -0700 Received: from presence.lglobal.com (jesse@presence.lglobal.com [204.50.121.2]) by presence.lglobal.com (8.6.12/8.6.12) with SMTP id QAA06686 for ; Fri, 25 Aug 1995 16:33:38 -0400 Date: Fri, 25 Aug 1995 16:33:37 -0400 (EDT) From: Jesse Hirsh To: majordomo-users@greatcircle.com Subject: Returned mail: unknown mailer error 1 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="QAA06516.809382461/presence.lglobal.com" Content-ID: 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. Send mail to mime@docserver.cac.washington.edu for more info. --QAA06516.809382461/presence.lglobal.com Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Help me, I'm still getting these errors. What could it be? /~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\ Jesse Dillan Hirsh jesse@lglobal.com Information Revolutionary Local GlobalAccess Toronto Ontario Canada (416) 515-7400 Disseminating Information & Power Onto The Community Level "It's all just a dream babe, a vacuum, a scheme babe, that sucks you into feeling like this." ---------- Forwarded message ---------- Date: Fri, 25 Aug 1995 16:27:41 -0400 From: Mail Delivery Subsystem To: owner-majordomo@lglobal.com Subject: Returned mail: unknown mailer error 1 The original message was received at Fri, 25 Aug 1995 16:27:19 -0400 from root@newsgate.dircon.co.uk [194.129.52.15] ----- The following addresses had delivery problems ----- "|/usr/local/majordom/wrapper majordomo" (unrecoverable error) (expanded from: ) ----- Transcript of session follows ----- Message delivered to mailing list Out of memory! 554 "|/usr/local/majordom/wrapper majordomo"... unknown mailer error 1 Message delivered to mailing list owner-majordomo ----- Original message follows ----- --QAA06516.809382461/presence.lglobal.com-- From majordomo-users-owner Mon Sep 18 15:32:50 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA16287 for majordomo-users-outgoing; Mon, 18 Sep 1995 15:14:43 -0700 Received: from mailhub.hcl.com (mailhub.hcl.com [204.101.87.120]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id PAA07391 for ; Sat, 16 Sep 1995 15:28:31 -0700 Received: (rudy@localhost) by mailhub.hcl.com (8.6.12/8.6.5) id SAA10425 for majordomo-users@GreatCircle.COM; Sat, 16 Sep 1995 18:38:19 -0400 From: Rudy Amid Message-Id: <199509162238.SAA10425@mailhub.hcl.com> Subject: Re: HELP( BOUNCE faculty: Admin request) To: majordomo-users@GreatCircle.COM Date: Sat, 16 Sep 1995 18:38:18 -0400 (EDT) In-Reply-To: <199509160128.VAA05120@smuggler.bbn.com> from "John C. Orthoefer" at Sep 15, 95 09:28:10 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 869 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk An excerpt from John C. Orthoefer message: > Humm, here is a list of things which cause the Admin request mail. > Something I've been meaning to look up in the code. > > Subject line with subscribe, unsubscribe, help, RCPT, > change...address, request...addition. > > First 5 lines of the body contain: > add me > delete me > remove me > help > change...address > subscribe > sub > unsubscribe > unsub > > ... stands for the regex .* ie any characters, any number. I had someone sent a message with the first line: "OK..." and it bounced. -- Rudy Amid (rudy@hcl.com) // alt: ramid@nyx.cs.du.edu Systems Administrator \X/ URL: http://nyx10.cs.du.edu:8001/~ramid Hummingbird Communications, Ltd. #include 1 Sparks Ave. Toronto, Canada. M2H 2W1 /* This message is only my opinion */ From majordomo-users-owner Mon Sep 18 15:34:04 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA16901 for majordomo-users-outgoing; Mon, 18 Sep 1995 15:22:51 -0700 Received: from presence.lglobal.com (presence.lglobal.com [204.50.121.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id PAA16894 for ; Mon, 18 Sep 1995 15:22:47 -0700 Received: from presence.lglobal.com (jesse@presence.lglobal.com [204.50.121.2]) by presence.lglobal.com (8.6.12/8.6.12) with SMTP id QAA06686 for ; Fri, 25 Aug 1995 16:33:38 -0400 Date: Fri, 25 Aug 1995 16:33:37 -0400 (EDT) From: Jesse Hirsh To: majordomo-users@greatcircle.com Subject: Returned mail: unknown mailer error 1 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="QAA06516.809382461/presence.lglobal.com" Content-ID: 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. Send mail to mime@docserver.cac.washington.edu for more info. --QAA06516.809382461/presence.lglobal.com Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Help me, I'm still getting these errors. What could it be? /~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\_/~\ Jesse Dillan Hirsh jesse@lglobal.com Information Revolutionary Local GlobalAccess Toronto Ontario Canada (416) 515-7400 Disseminating Information & Power Onto The Community Level "It's all just a dream babe, a vacuum, a scheme babe, that sucks you into feeling like this." ---------- Forwarded message ---------- Date: Fri, 25 Aug 1995 16:27:41 -0400 From: Mail Delivery Subsystem To: owner-majordomo@lglobal.com Subject: Returned mail: unknown mailer error 1 The original message was received at Fri, 25 Aug 1995 16:27:19 -0400 from root@newsgate.dircon.co.uk [194.129.52.15] ----- The following addresses had delivery problems ----- "|/usr/local/majordom/wrapper majordomo" (unrecoverable error) (expanded from: ) ----- Transcript of session follows ----- Message delivered to mailing list Out of memory! 554 "|/usr/local/majordom/wrapper majordomo"... unknown mailer error 1 Message delivered to mailing list owner-majordomo ----- Original message follows ----- --QAA06516.809382461/presence.lglobal.com-- From majordomo-users-owner Mon Sep 18 15:48:15 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA17492 for majordomo-users-outgoing; Mon, 18 Sep 1995 15:32:01 -0700 Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id FAA14168 for ; Mon, 18 Sep 1995 05:59:03 -0700 Received: from i3.informatik.rwth-aachen.de (bach.Informatik.RWTH-Aachen.DE [137.226.168.13]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-4/8.6.12) with SMTP id OAA14805; Mon, 18 Sep 1995 14:53:26 +0200 Received: from grieg.informatik.rwth-aachen.de.informatik.rwth-aachen.de by i3.informatik.rwth-aachen.de (4.1/4.1-i3) id AA28164; Mon, 18 Sep 95 14:53:35 +0200 From: peter@i3.informatik.rwth-aachen.de (Peter Heimann) Received: by grieg.informatik.rwth-aachen.de.informatik.rwth-aachen.de (4.1/client-1.5) id AA11923; Mon, 18 Sep 95 14:53:29 +0200 Date: Mon, 18 Sep 95 14:53:29 +0200 Message-Id: <9509181253.AA11923@grieg.informatik.rwth-aachen.de.informatik.rwth-aachen.de> To: majordomo-users@GreatCircle.com Subject: Re: String matching? Cc: mjb@triumph.cs.utah.edu Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Mark J Bradakis writes > We're running version 1.92 here, and it seems that when checking lists > for users, majordomo claims that "user" is not in the list, for unsubscribes > and private functions [...] > It does match if there is an at sign in the address, user@host, but a > lone user name fails. I once had a similar problem with majordomo 1.93 when I set "mungedomain = yes" in a list's config file. I could subscribe addresses that didn't contain "@", but was unable to unsubscribe them. The problem might be in the "main'addr_match" subroutine in "majordomo.pl": if @addr1 does not contain a "@", $addr1 equals 0, and the test in line 171 fails: if ( $#addr1 == $#addr2 && $#addr1 == 1 && ^^^^^^^^^^^^ $addr1[0] eq $addr2[0] && (index($addr1[1], $addr2[1]) >= $[)) Possible fix (WARNING: untested): Delete lines 175-176 } else { return(undef); Thus, the "return($a1[0] eq $a2[0]);" comes into effect for the else case as well. I don't know whether the 1.92 "main'addr_match" subroutine is any different. -- Peter Heimann Lehrstuhl fuer Informatik III peter@i3.informatik.rwth-aachen.de RWTH Aachen From majordomo-users-owner Mon Sep 18 16:01:27 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA18159 for majordomo-users-outgoing; Mon, 18 Sep 1995 15:41:28 -0700 Received: from topdog.geneva.edu (topdog.geneva.edu [199.234.16.132]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id OAA14745 for ; Mon, 18 Sep 1995 14:54:46 -0700 Received: by topdog.geneva.edu (4.1/SMI-4.1) id AA08969; Mon, 18 Sep 95 17:56:02 EDT Date: Mon, 18 Sep 1995 17:56:00 -0400 (EDT) From: Joe Hines To: majordomo-users@GreatCircle.Com Subject: help with options, PLEASE Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am trying to configure Majordomo 1.93 with the -I and the -r options. I continually get errors when trying to implement these options. Could someone please provide some insight into how to configure these? Joe Hines From majordomo-users-owner Mon Sep 18 16:02:50 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA18142 for majordomo-users-outgoing; Mon, 18 Sep 1995 15:41:20 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA08223 for ; Mon, 18 Sep 1995 13:32:24 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by tetsuo.communique.net (8.6.12/8.6.12) with SMTP id PAA44815 for ; Mon, 18 Sep 1995 15:31:16 -0500 Date: Mon, 18 Sep 1995 15:09:16 -0500 (CDT) From: Raul Zighelboim To: majordomo@greatcircle.com Subject: Help! majordomo: Unknown user $list-approve Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII ReSent-Date: Mon, 18 Sep 1995 15:30:52 -0500 (CDT) ReSent-From: Raul Zighelboim ReSent-To: majordomo-users@greatcircle.com ReSent-Message-ID: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am getting this from running majordomo: $> echo 'subscribe test gregh' | sendmail -v majordomo majordomo... aliased to "|/usr/local/lib/majordomo/wrapper majordomo" test-approval... User unknown: No such file or directory majordomo[9773] {Raul Zighelboim } request subscribe test gregh "|/usr/local/lib/majordomo/wrapper majordomo"... Sent $> I can send mail directly to test-approval, defined as an alias to me. If I replace the $list-approval argument on line 1145 of $home/majordomo with 'mango' (me), everything works file. Any sugestions ? Oh majordomo 1.93 and perl 5.001 ----------------------------------------------------------------------------- Raul Zighelboim e-mail: mango@communique.net Communique Inc. Tel: 504.527.6200 Technical Specialist Fax: 504.527.6030 From majordomo-users-owner Mon Sep 18 16:05:58 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA17913 for majordomo-users-outgoing; Mon, 18 Sep 1995 15:37:28 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA19122 for ; Mon, 18 Sep 1995 07:50:19 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA17722 for majordomo-users@greatcircle.com; Mon, 18 Sep 95 07:49:09 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA08302; Mon, 18 Sep 95 07:49:07 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA04626 for majordomo-users@greatcircle.com; Mon, 18 Sep 95 07:49:04 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA11168; Mon, 18 Sep 95 09:49:02 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA19514; Mon, 18 Sep 1995 09:49:00 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509181449.AA19514@miaow.sps.mot.com> Subject: Re: String matching? To: mjb@triumph.cs.utah.edu (Mark J Bradakis) Date: Mon, 18 Sep 1995 09:49:00 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509150622.AAA20248@triumph.cs.utah.edu> from "Mark J Bradakis" at Sep 15, 95 00:22:50 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 894 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Mark J Bradakis writes: ] > > We're running version 1.92 here, and it seems that when checking lists > for users, majordomo claims that "user" is not in the list, for unsubscribes > and private functions, though the list would have > > > ... > user > otheruser > luser@host > ... > > > It does match if there is an at sign in the address, user@host, but a > lone user name fails. Perusal of the FAQ and various docs turned up no > clue, any quick suggestions on how to fix this? Yes, quit subscribing people by what you *think* their e-mail address is and let Mj use what their mail to Mj shows their e-mail address *really* is. "user" and "user@host" really are 2 different addresses, even if they ultimately deliver to the same mailbox. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Mon Sep 18 17:00:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA23212 for majordomo-users-outgoing; Mon, 18 Sep 1995 16:54:28 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id QAA23204 for ; Mon, 18 Sep 1995 16:54:23 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA23351 for majordomo-users@greatcircle.com; Mon, 18 Sep 95 16:53:14 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA23300; Mon, 18 Sep 95 16:53:13 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA25944 for majordomo-users@greatcircle.com; Mon, 18 Sep 95 16:53:12 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA17122; Mon, 18 Sep 95 18:53:10 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA21408; Mon, 18 Sep 1995 18:53:08 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509182353.AA21408@miaow.sps.mot.com> Subject: Re: race condition? (was: Re: Majordomo subscription problem) To: rj@rainbow.in-berlin.de (Robert Joop) Date: Mon, 18 Sep 1995 18:53:08 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <43i7kb$pfi@rainbow.in-berlin.de> from "Robert Joop" at Sep 18, 95 00:31:39 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 915 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Robert Joop writes: ] > > nb3367@u.cc.utah.edu (Nathan Beddes) writes: > > >When I send mail to majordomo like so: > > subscribe list-l > > >I get this back over and over: > > Subject: Majordomo results > > > -- > > > >>>> subscribe sltribune-l > > >and /usr/local/mail/lists/list-l stays empty. > > i've got exactly the same problem. [...] > i began to track this problem down by inserting code that writes to a > debug log file. > > at some point the subscription request suddenly works! If this were C code, I'd say you had an uninitialized variable or bad pointer, but I don't think that applies to Perl unless you have a bad Perl installation. Just for the record, what version of Majordomo are you using? Have you tried rebuilding/ reinstalling Perl? Majordomo? -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Mon Sep 18 18:00:16 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id RAA25166 for majordomo-users-outgoing; Mon, 18 Sep 1995 17:40:49 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id RAA25159 for ; Mon, 18 Sep 1995 17:40:45 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA08177 for majordomo-users@greatcircle.com; Mon, 18 Sep 95 17:39:37 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA23963; Mon, 18 Sep 95 17:39:36 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA28535 for majordomo-users@greatcircle.com; Mon, 18 Sep 95 17:39:34 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA17302; Mon, 18 Sep 95 19:39:33 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA19701; Mon, 18 Sep 1995 19:39:31 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509190039.AA19701@miaow.sps.mot.com> Subject: Re: help with options, PLEASE To: jdh@topdog.geneva.edu (Joe Hines) Date: Mon, 18 Sep 1995 19:39:31 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Joe Hines" at Sep 18, 95 05:56:00 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 483 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Joe Hines writes: ] > > I am trying to configure Majordomo 1.93 with the -I and the -r options. > I continually get errors when trying to implement these options. Could > someone please provide some insight into how to configure these? You mean resend? Just use the restrict_post (-I) and reply_to (-r) parameters in the list.config file. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Tue Sep 19 07:00:46 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA21669 for majordomo-users-outgoing; Tue, 19 Sep 1995 06:58:11 -0700 Received: from hub.concord.org (hub.concord.org [204.180.89.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id GAA21660 for ; Tue, 19 Sep 1995 06:58:02 -0700 Received: from [204.180.89.38] (noapb.concord.org [204.180.89.38]) by hub.concord.org (8.6.10/8.6.9) with SMTP id KAA27486 for ; Tue, 19 Sep 1995 10:14:51 -0400 X-Sender: noah@hub.concord.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 19 Sep 1995 09:58:19 -0500 To: majordomo-users@GreatCircle.COM From: noah@concord.org (Noah Fields) Subject: permissions, shlock, unknown error (2) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am using majordomo 1.93 I really did have majordomo running beautifully on our system here for quite some time. Last night, in a rush, while adding a new mailing list, I noticed that the majordomo.cf file had the wrong permissions set (it still worked, so I definately should *not* have tried to fix it, but I did any how) The owner was root and group was root, so I changed it back to uid guid majordom. Now all of a sudden, I am getting lots of the following error messages: >> MAJORDOMO ABORT open of temp file /usr/local/majordomo/lists/shlock.25946 failed Permission denied << I even made my /usr/loccal/majordomo/archives and /usr/local/majordomo/lists directories 777 majordom majordom, but still I could not create a temp file. I read section 2 of the FAQ over and over again. I recently upgraded my perl to version 5.001m, but that was three weeks ago, and the problem happened last night when I was changing file perms. I ahve checked many times, but I think that I am so paniced that I am not thinking clearly... here are the file perms for majordomos directory here: (I am *sure* the problem is here, and I dont know why I cant see it) -rw-r--r-- 1 majordom majordom 0 Aug 17 11:07 Log drwxr-xr-x 2 majordom majordom 1024 Jun 16 14:36 Tools -rwxrwxr-x 1 majordom majordom 7192 Jul 5 14:18 archive -rwxr-xr-x 1 majordom majordom 7192 Jul 5 14:17 archive.old -rwxr-xr-x 1 majordom majordom 7192 Jun 30 15:13 archive2.pl drwxrwxr-x 15 majordom majordom 1024 Sep 18 16:23 archives drwxr-xr-x 2 majordom majordom 1024 Jun 16 14:36 bin -rwxr-xr-x 1 majordom majordom 2615 Jun 16 14:36 bounce-remind -rw-r--r-- 1 majordom majordom 43737 Jun 16 14:36 config_parse.pl -rwxr-xr-x 1 majordom majordom 11320 Jun 16 14:36 digest drwxrwxr-x 2 majordom majordom 1024 Jun 16 15:04 digests drwxrwxr-x 2 majordom majordom 2048 Sep 19 09:59 lists drwx------ 2 majordom majordom 1024 Jul 6 13:55 mail -rwxr-xr-x 1 majordom majordom 42524 Jun 16 14:36 majordomo drwxrwxr-x 5 majordom majordom 1024 Jun 16 18:23 majordomo-1.93 -rwxrwxr-- 1 majordom majordom 4428 Sep 18 16:37 majordomo.cf -rwxrwxr-- 1 majordom majordom 4426 Sep 18 16:29 majordomo.cf~ -rw-r--r-- 1 majordom majordom 14327 Jun 16 14:36 majordomo.pl -rw-r--r-- 1 majordom majordom 634880 Jun 16 14:30 majordomo.tar -rw-r--r-- 1 majordom majordom 141 Jun 16 14:36 majordomo_version.pl drwxr-xr-x 4 majordom majordom 1024 Jun 16 14:36 man -rwxr-xr-x 1 majordom majordom 2153 Jun 16 14:36 new-list -rwxr-xr-x 1 majordom majordom 3025 Jun 16 15:13 request-answer -rwxr-xr-x 1 majordom majordom 12872 Jun 16 14:36 resend -rw-r--r-- 1 majordom majordom 3742 Jun 16 14:36 resend.README -rw-r--r-- 1 majordom majordom 6183 Jun 16 14:36 shlock.pl -rwxr-xr-x 1 majordom majordom 131 Jun 16 14:36 test -rwxr-xr-x 1 majordom majordom 17125 Jul 5 15:57 wrapper -Thanks *GAZILLIONS* for any suggestions at all !!! -Noah From majordomo-users-owner Tue Sep 19 08:30:13 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA24787 for majordomo-users-outgoing; Tue, 19 Sep 1995 08:18:57 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA24779 for ; Tue, 19 Sep 1995 08:18:54 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA19037 for majordomo-users@greatcircle.com; Tue, 19 Sep 95 08:17:37 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA04616; Tue, 19 Sep 95 08:17:13 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA10836 for majordomo-users@greatcircle.com; Tue, 19 Sep 95 08:17:10 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA20118; Tue, 19 Sep 95 10:17:08 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA19673; Tue, 19 Sep 1995 10:17:06 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509191517.AA19673@miaow.sps.mot.com> Subject: Re: permissions, shlock, unknown error (2) To: noah@concord.org (Noah Fields) Date: Tue, 19 Sep 1995 10:17:05 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Noah Fields" at Sep 19, 95 09:58:19 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1145 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Noah Fields writes: ] > > I really did have majordomo running beautifully on our system here for > quite some time. Last night, in a rush, while adding a new mailing list, I > noticed that the majordomo.cf file had the wrong permissions set (it still > worked, so I definately should *not* have tried to fix it, but I did any > how) The owner was root and group was root, so I changed it back to uid > guid majordom. Now all of a sudden, I am getting lots of the following > error messages: > > >> > MAJORDOMO ABORT > > open of temp file /usr/local/majordomo/lists/shlock.25946 failed > Permission denied [...] > -rwxr-xr-x 1 majordom majordom 17125 Jul 5 15:57 wrapper ^ ^ ^^^^^^^^ There's your problem. If you have a POSIX installation, wrapper should be installed setuid root; if BSD, then it should be setuid and setgid majordom, i.e.: POSIX: -rwsr-xr-x 1 root majordom 17125 Jul 5 15:57 wrapper BSD: -rwsr-sr-x 1 majordom majordom 17125 Jul 5 15:57 wrapper -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Tue Sep 19 09:04:08 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA27017 for majordomo-users-outgoing; Tue, 19 Sep 1995 08:56:52 -0700 Received: from msu.edu (ibm.cl.msu.edu [35.8.2.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA27009 for ; Tue, 19 Sep 1995 08:56:48 -0700 Received: from msuces.canr.msu.edu by msu.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Sep 95 11:55:52 EDT Date: Tue, 19 Sep 1995 11:55:36 -0400 (EDT) From: Gina Fogelsonger To: majordomo-users@greatcircle.com Subject: approve line length Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Some of my listowners are having trouble with approving subscription requests. The problem is that the lines are longer than 80 characters and it is wrapping the rest of the address onto a new line. Is there a special character that can be used to continue the request on the next line? Thanks in advance for any suggestions. Gina ============================================================================ Gina E. Fogelsonger Systems Programmer MICHIGAN STATE College of Agriculture and Natural Resources ---------------- Computer Services U N I V E R S I T Y Phone: (517) 355-3776 Fax: (517) 353-5341 Internet: fogelson@msuces.canr.msu.edu ============================================================================ From majordomo-users-owner Tue Sep 19 09:04:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA26740 for majordomo-users-outgoing; Tue, 19 Sep 1995 08:48:43 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id IAA26730 for ; Tue, 19 Sep 1995 08:48:39 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by tetsuo.communique.net (8.6.12/8.6.12) with SMTP id KAA13616; Tue, 19 Sep 1995 10:47:27 -0500 Date: Tue, 19 Sep 1995 10:47:26 -0500 (CDT) From: Raul Zighelboim To: David Wolfe cc: "Majordomo user's mailing list" Subject: Re: Help! majordomo: Unknown user $list-approve In-Reply-To: <9509182358.AA21384@miaow.sps.mot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > Oh majordomo 1.93 and perl 5.001 > > Not perl 5.001e, or even 5.001m? Update your perl. Beyond that, get > sendmail on the machine Mj runs on to verify the alias via: > > $> telnet mjmachine 25 > vrfy test-approval > quit Sorry: perl 5.001 pathc 1m And I can mail directly to test-approval. Majordomo cannot. Or: vrfy test-approval 250 On Mon, 18 Sep 1995, Dave Wolfe wrote: > [ Raul Zighelboim writes: ] > > > > I am getting this from running majordomo: > > > > $> echo 'subscribe test gregh' | sendmail -v majordomo > > majordomo... aliased to "|/usr/local/lib/majordomo/wrapper majordomo" > > test-approval... User unknown: No such file or directory > > majordomo[9773] {Raul Zighelboim } request subscribe test gregh > > "|/usr/local/lib/majordomo/wrapper majordomo"... Sent > > $> > > > > I can send mail directly to test-approval, defined as an alias to me. > > > > If I replace the $list-approval argument on line 1145 of $home/majordomo > > with 'mango' (me), everything works file. > > > > Any sugestions ? > > Oh majordomo 1.93 and perl 5.001 > > Not perl 5.001e, or even 5.001m? Update your perl. Beyond that, get > sendmail on the machine Mj runs on to verify the alias via: > > $> telnet mjmachine 25 > vrfy test-approval > quit > > -- > Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 > Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 > ----------------------------------------------------------------------------- Raul Zighelboim e-mail: mango@communique.net Communique Inc. Tel: 504.527.6200 Technical Specialist Fax: 504.527.6030 From majordomo-users-owner Tue Sep 19 09:31:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA28345 for majordomo-users-outgoing; Tue, 19 Sep 1995 09:21:35 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA28338 for ; Tue, 19 Sep 1995 09:21:32 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA05812 for majordomo-users@greatcircle.com; Tue, 19 Sep 95 09:20:19 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA06621; Tue, 19 Sep 95 09:20:16 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA16148 for majordomo-users@greatcircle.com; Tue, 19 Sep 95 09:20:12 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA21092; Tue, 19 Sep 95 11:20:07 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA18483; Tue, 19 Sep 1995 11:20:05 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509191620.AA18483@miaow.sps.mot.com> Subject: Re: Help! majordomo: Unknown user $list-approve To: mango@communique.net (Raul Zighelboim) Date: Tue, 19 Sep 1995 11:20:05 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Raul Zighelboim" at Sep 19, 95 10:47:26 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 736 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Raul Zighelboim writes: ] > > > > Oh majordomo 1.93 and perl 5.001 > > > > Not perl 5.001e, or even 5.001m? Update your perl. Beyond that, get > > sendmail on the machine Mj runs on to verify the alias via: > > > > $> telnet mjmachine 25 > > vrfy test-approval > > quit > > Sorry: perl 5.001 pathc 1m > And I can mail directly to test-approval. Majordomo cannot. > Or: vrfy test-approval > 250 Is it possible that the sendmail daemon gets started with a different (additional?) alias file that the sendmail invoked by Mj doesn't have? -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Tue Sep 19 10:30:53 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA01485 for majordomo-users-outgoing; Tue, 19 Sep 1995 10:09:45 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA01442 for ; Tue, 19 Sep 1995 10:09:36 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by tetsuo.communique.net (8.6.12/8.6.12) with SMTP id MAA27819; Tue, 19 Sep 1995 12:08:23 -0500 Date: Tue, 19 Sep 1995 12:08:21 -0500 (CDT) From: Raul Zighelboim To: David Wolfe cc: "Majordomo user's mailing list" Subject: Re: Help! majordomo: Unknown user $list-approve In-Reply-To: <9509191620.AA18483@miaow.sps.mot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk A temporary fix: but I do not know yet why, or what else is broken: On the majordomo script, I changed the line: # open a sendmail process for the approval request &sendmail(APPROVE, "$list-approval", "APPROVE $list") to read: &sendmail(APPROVE, "$list-approval\@communique.net", "APPROVE $list") and that seems to work. Do I have to change this every time invoke sendmail ? On Tue, 19 Sep 1995, Dave Wolfe wrote: > [ Raul Zighelboim writes: ] > > > > > > Oh majordomo 1.93 and perl 5.001 > > > > > > Not perl 5.001e, or even 5.001m? Update your perl. Beyond that, get > > > sendmail on the machine Mj runs on to verify the alias via: > > > > > > $> telnet mjmachine 25 > > > vrfy test-approval > > > quit > > > > Sorry: perl 5.001 pathc 1m > > And I can mail directly to test-approval. Majordomo cannot. > > Or: vrfy test-approval > > 250 > > Is it possible that the sendmail daemon gets started with a different > (additional?) alias file that the sendmail invoked by Mj doesn't have? > > -- > Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 > Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 > ----------------------------------------------------------------------------- Raul Zighelboim e-mail: mango@communique.net Communique Inc. Tel: 504.527.6200 Technical Specialist Fax: 504.527.6030 From majordomo-users-owner Tue Sep 19 13:02:50 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA13188 for majordomo-users-outgoing; Tue, 19 Sep 1995 13:02:02 -0700 Received: from ebbs.english.vt.edu (ebbs.english.vt.edu [128.173.168.253]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA13180 for ; Tue, 19 Sep 1995 13:01:59 -0700 Received: by ebbs.english.vt.edu id AA20532 (5.67b/IDA-1.5 for majordomo-users@greatcircle.com); Tue, 19 Sep 1995 16:00:39 -0400 From: Len Hatfield Message-Id: <199509192000.AA20532@ebbs.english.vt.edu> Subject: Index/Archive2.pl not working.... To: majordomo-users@greatcircle.com Date: Tue, 19 Sep 1995 16:00:38 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 409 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Folks: I've got a list working away under Majordomo 1.93; sendmail aliases are in place; and an archive file is accumulating. But an 'index' command sent to majordomo reports that there aren't any files for that list. Plus, when I run archive2.pl like so: archive2.pl -f /path/to/list -d -u /path/to/archive/file it tells me that the archive directory is invalid. Pointers? -- ...Len Hatfield From majordomo-users-owner Tue Sep 19 13:05:32 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA12679 for majordomo-users-outgoing; Tue, 19 Sep 1995 12:54:07 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA12672 for ; Tue, 19 Sep 1995 12:54:03 -0700 Received: from ro.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA19851; Tue, 19 Sep 1995 15:52:51 -0400 (wiseb from ro.cs.rpi.edu) Message-Id: <199509191952.AA19851@cs.rpi.edu> X-Mailer: exmh version 1.6.1 5/23/95 To: majordomo-users@greatcircle.com Subject: Separate list and digest owners In-Reply-To: Bowden Wise's message of "Tue, 19 Sep 1995 11:33:18 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Sep 1995 15:52:48 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a list that has an associated -digest list; the lists are owl-list and owl-list-digest. Now, messages to owl-list are sent to resend in the usual way. Any mail sent to owl-list goes to users of the owl-list and is digestified by digest. To ensure that discussions from digest participants get routed back to the owl-list, I added the following to aliases: owl-list-digest: owl-list This means, however, that any administrative mail sent to owl-list-digest is always caught by the resend for owl-list and is therefore sent to owner-owl-list and not owner-owl-list-digest. So, I changed owl-list-digest alias to this: owl-list-digest: "|/home/majordom/bin/wrapper resend -l owl-list-digest -h netlab.cs.rpi.edu -s -p bulk owl-list-outgoing" Well, now the different owner aliases work, but since the headers/footers found in the config file work for both digest and resend, whenever a message is sent to the -digest address the mail - appears on the owl-list-digest correctly (the digest headers and footers are NOT expanded); but, on both the owl-list and the message stored by digest, the header and footer is included, which is not what we want. So, how can I have two different owners (one for owl-list and another for owl-list-digest) and ensure that messages are processed the way they were before when I simply had: owl-list-digest: owl-list for the alias? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Tue Sep 19 16:32:50 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA01196 for majordomo-users-outgoing; Tue, 19 Sep 1995 16:32:15 -0700 Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id QAA01144 for ; Tue, 19 Sep 1995 16:32:01 -0700 Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from uriela.in-berlin.de (192.109.42.147) with smtp id ; Wed, 20 Sep 95 01:30 MEST Received: by uriela.in-berlin.de (/\oo/\ Smail3.1.29.1 #29.8) id ; Wed, 20 Sep 95 01:30 MET DST Received: from rainbow.in-berlin.de by moonbow.in-berlin.de with smtp (Smail3.1.29.1 #8) id m0svAxt-000Tj4C; Wed, 20 Sep 95 00:16 MET DST Received: by rainbow.in-berlin.de (Smail3.1.28.1 #1) id m0svAxs-000fuIC; Wed, 20 Sep 95 00:16 MET DST Message-Id: From: rj@rainbow.in-berlin.de (Robert Joop) Subject: Re: race condition? (was: Re: Majordomo subscription problem) To: david_wolfe@risc.sps.mot.com Date: Wed, 20 Sep 1995 00:16:32 +0200 (MET DST) Cc: majordomo-users@greatcircle.com In-Reply-To: <9509182353.AA21408@miaow.sps.mot.com> from "Dave Wolfe" at Sep 18, 95 06:53:08 pm X-Mailer: ELM [version 2.4 PL24++ PGP2] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1056 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk `Dave Wolfe' wrote: > > [ Robert Joop writes: ] > > > > nb3367@u.cc.utah.edu (Nathan Beddes) writes: > > > > >When I send mail to majordomo like so: > > > subscribe list-l > > > > >I get this back over and over: > > > Subject: Majordomo results > > > > > -- > > > > > >>>> subscribe sltribune-l > > > > >and /usr/local/mail/lists/list-l stays empty. > > > > i've got exactly the same problem. > [...] > > i began to track this problem down by inserting code that writes to a > > debug log file. > > > > at some point the subscription request suddenly works! > > If this were C code, I'd say you had an uninitialized variable or bad > pointer, but I don't think that applies to Perl unless you have a bad > Perl installation. Just for the record, what version of Majordomo are > you using? Have you tried rebuilding/ reinstalling Perl? Majordomo? 1.93, no, no. i'm using perl4.036 which executes dozens of other scripts just fine. besides the wrapper majordomo consists of perl scripts only; reinstalling them could hardly change anything. rj From majordomo-users-owner Tue Sep 19 23:02:51 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA23917 for majordomo-users-outgoing; Tue, 19 Sep 1995 22:37:40 -0700 Received: from optical.fiber.net (optical.fiber.net [204.250.13.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id XAA08273 for ; Mon, 18 Sep 1995 23:11:30 -0700 Received: by optical.fiber.net (NX5.67e/NX3.0M) id AA27225; Tue, 19 Sep 95 00:07:26 -0600 Message-Id: <9509190607.AA27225@optical.fiber.net> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Carl Payne Date: Tue, 19 Sep 95 00:07:23 -0600 To: majordomo-users@greatcircle.com Subject: Not in FAQ: no log, same reply no matter what Reply-To: cpayne@optical.fiber.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Nothing in the log and, no matter what the command is, whether it's subscribe list or help or whatever, I get the majordomo-supplied response, not the one I wrote. All permissions are correct, I realize I'm being vague but I'm hoping it's some basic little thing I blew up. 1.93 and 5.0 on NeXTSTEP 3.3 Thanks Carl From majordomo-users-owner Tue Sep 19 23:03:30 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA23915 for majordomo-users-outgoing; Tue, 19 Sep 1995 22:37:36 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id QAA23552 for ; Mon, 18 Sep 1995 16:59:49 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA25392 for majordomo-users@greatcircle.com; Mon, 18 Sep 95 16:58:41 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA23431; Mon, 18 Sep 95 16:58:39 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA26214 for majordomo-users@greatcircle.com; Mon, 18 Sep 95 16:58:37 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA17139; Mon, 18 Sep 95 18:58:35 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA21384; Mon, 18 Sep 1995 18:58:33 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509182358.AA21384@miaow.sps.mot.com> Subject: Re: Help! majordomo: Unknown user $list-approve To: mango@communique.net (Raul Zighelboim) Date: Mon, 18 Sep 1995 18:58:33 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Raul Zighelboim" at Sep 18, 95 03:09:16 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 979 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Raul Zighelboim writes: ] > > I am getting this from running majordomo: > > $> echo 'subscribe test gregh' | sendmail -v majordomo > majordomo... aliased to "|/usr/local/lib/majordomo/wrapper majordomo" > test-approval... User unknown: No such file or directory > majordomo[9773] {Raul Zighelboim } request subscribe test gregh > "|/usr/local/lib/majordomo/wrapper majordomo"... Sent > $> > > I can send mail directly to test-approval, defined as an alias to me. > > If I replace the $list-approval argument on line 1145 of $home/majordomo > with 'mango' (me), everything works file. > > Any sugestions ? > Oh majordomo 1.93 and perl 5.001 Not perl 5.001e, or even 5.001m? Update your perl. Beyond that, get sendmail on the machine Mj runs on to verify the alias via: $> telnet mjmachine 25 vrfy test-approval quit -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 20 06:30:38 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA07711 for majordomo-users-outgoing; Wed, 20 Sep 1995 06:20:54 -0700 Received: from unilab.dfci.harvard.edu (unilab.dfci.harvard.edu [155.52.46.57]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id GAA07704 for ; Wed, 20 Sep 1995 06:20:51 -0700 Received: (from ratinox@localhost) by unilab.dfci.harvard.edu (8.6.12/8.6.9) id JAA07519; Wed, 20 Sep 1995 09:19:45 -0400 Date: Wed, 20 Sep 1995 09:19:45 -0400 Message-Id: <199509201319.JAA07519@unilab.dfci.harvard.edu> From: Richard Pieri To: Majordomo-users@GreatCircle.COM CC: fogelson@msuces.canr.msu.edu In-reply-to: Gina Fogelsonger's message of Tue, 19 Sep 1995 11:55:36 -0400 (EDT) Subject: Re: approve line length References: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- >>>>> "GF" == Gina Fogelsonger writes: GF> Is there a special character that can be used to continue the GF> request on the next line? A backslash: approve subscribe \ Richard=L.=Pieri%IS@eye.dfci.harvard.edu -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Processed by Mailcrypt 3.4beta, an Emacs/PGP interface iQCVAwUBMGAU6J6VRH7BJMxHAQEQuQQAs0tq15/sWU2cK2RSs9sftg7kzYqV5E5V TDEczEYoY1YpDaaaiB1xPzlLwbqQ1rawRmh53ZkbgcO0ZMyVKgyFq7NfgHhq1F3t /JfiW/UcVpkUzUQDaAoHRb1+WZjCGhbHM01EzAzHRC1Czhj3W4sLhVPHfo2Mqiuf YJ8OvZQjsTg= =zR7f -----END PGP SIGNATURE----- -- Richard Pieri/Information Services \ When you go out in the world, remember: \ being placed on a pedestal is a right, http://www.dfci.harvard.edu/~ratinox \ not a priviledge! -A cat's guide to life From majordomo-users-owner Wed Sep 20 06:32:51 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA07830 for majordomo-users-outgoing; Wed, 20 Sep 1995 06:24:32 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA07823 for ; Wed, 20 Sep 1995 06:24:29 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA16782 for majordomo-users@greatcircle.com; Wed, 20 Sep 95 06:23:20 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA26142; Wed, 20 Sep 95 06:23:17 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA11938 for majordomo-users@greatcircle.com; Wed, 20 Sep 95 06:23:13 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA04939; Wed, 20 Sep 95 08:23:11 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA17662; Wed, 20 Sep 1995 08:23:09 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509201323.AA17662@miaow.sps.mot.com> Subject: Re: race condition? (was: Re: Majordomo subscription problem) To: rj@rainbow.in-berlin.de (Robert Joop) Date: Wed, 20 Sep 1995 08:23:09 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Robert Joop" at Sep 20, 95 00:16:32 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1364 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Robert Joop writes: ] > > `Dave Wolfe' wrote: > > > > [ Robert Joop writes: ] > > > > > > nb3367@u.cc.utah.edu (Nathan Beddes) writes: > > > > > > >When I send mail to majordomo like so: > > > > subscribe list-l > > > > > > >I get this back over and over: > > > > Subject: Majordomo results > > > > > > > -- > > > > > > > >>>> subscribe sltribune-l > > > > > > >and /usr/local/mail/lists/list-l stays empty. > > > > > > i've got exactly the same problem. > > [...] > > > i began to track this problem down by inserting code that writes to a > > > debug log file. > > > > > > at some point the subscription request suddenly works! > > > > If this were C code, I'd say you had an uninitialized variable or bad > > pointer, but I don't think that applies to Perl unless you have a bad > > Perl installation. Just for the record, what version of Majordomo are > > you using? Have you tried rebuilding/ reinstalling Perl? Majordomo? > > 1.93, no, no. > > i'm using perl4.036 which executes dozens of other scripts just fine. > > besides the wrapper majordomo consists of perl scripts only; > reinstalling them could hardly change anything. Only if none of the scripts were totally unmodified, including the #! line. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 20 10:31:29 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA15355 for majordomo-users-outgoing; Wed, 20 Sep 1995 10:19:52 -0700 Received: from hub.concord.org (hub.concord.org [204.180.89.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA15342 for ; Wed, 20 Sep 1995 10:19:46 -0700 Received: from [204.180.89.38] (noapb.concord.org [204.180.89.38]) by hub.concord.org (8.6.10/8.6.9) with SMTP id NAA06197; Wed, 20 Sep 1995 13:36:54 -0400 X-Sender: noah@hub.concord.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 20 Sep 1995 13:20:09 -0500 To: majordomo-users@GreatCircle.COM From: noah@concord.org (Noah Fields) Subject: Adding mime-extraction feature...LONG! Cc: kevinh@eit.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk ----( Warning this is a bit long, and may not be of interest to many )---- Hello, Here is a small project I am working on, followed by some problems I am having. This might be better suited for a sendmail mailing list, and I am sorry if that is the case. -- DESCRIPTION: -- The basic goal of this project is to configure majordomo, (and the sendmail alias file) so that certain subscribes to lists have any enclosed mime files automagically sucked out of them, and placed in the servers /ftp/pub/incoming directory. The message then has the URL of the enclosed document branded on its footer. All Mailing list messages will then be archived, and placed on a website using EIC's HyperMail. Any messages going to HyperMail, will also have the mime files sucked out and replaced with the file-pointing-URL. The reason for this is because often times some people with slower connections do not appreciate receiving large enclosed documents, while other on the list really enjoy that. Additionally EIC's HyperMail will otherwise archive the mime file as part of the message body (yuck). -- WHERE I AM: -- I have a hacked perl script which can *usually* notice attached mime files inside mail, extract information about the files name and type, place that file in an FTP directory, and append the correct URL to the mail. This hack is henceforth called "mimesuck". Mimesuck is a regular text filter, and is run from /bin/sh by sendmail. (Im sure that none of this is secure in the least, I imagine that as phase 2 or so). So for now what I do is make two mailing lists for every single conceptual mailing list. People who want to have their files extracted for them subscribe to "themailinglist-nofiles" instead of "themailinglist". "themailinglist" is aliased out to a regular majordomo list, *and* to "the-mailinglist-nofiles", which has an alias that looks like this: thelist-nofiles: "| .. mimesuck | .../wrapper resend -l thelist-nofiles -h host thelist-nofiles-outgoing" -- THE PROBLEM / QUESTION: -- This *does* mail out the messages without the files to thelist-nofiles, but the FROM and SUBJECT do not show any sort of useful information. For some reason this info gets lost. (it appears in the message body as a faux-header but is *not* interpreted by mail handlers) This is obviously less than one would like. I am trying to *actually* learn a bit about sendmail and /bin/mail and things like this, but I figured this was a reasonable place to look for clues too. Thanks very much, I am sorry if I have wasted any ones time. -Noah From majordomo-users-owner Wed Sep 20 12:33:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA21472 for majordomo-users-outgoing; Wed, 20 Sep 1995 12:16:12 -0700 Received: from sun4nl.NL.net (sun4nl.NL.net [193.78.240.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id MAA21463 for ; Wed, 20 Sep 1995 12:16:02 -0700 Received: from hsb.nest.nl by sun4nl.NL.net with SMTP id AA18741 (5.65b/CWI-3.3); Wed, 20 Sep 1995 21:14:52 +0200 Received: from hsb.nest.nl (hsb.nest.nl [193.78.79.21]) by hsb.nest.nl (8.6.11/8.6.11) with SMTP id VAA23639 for ; Wed, 20 Sep 1995 21:25:44 +0100 Date: Wed, 20 Sep 1995 21:25:43 +0100 (WET DST) From: johan Henselmans To: majordomo-users@greatcircle.com Subject: problems with unknown mailer error Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi I am trying to set up majordom with perl5.0001m, Linux1.2.13 ELF and patched majordomo, majordome.pl and /etc/majordomo.cf (in consecutive failling runs) to make all the user@addresses to user\@adresses. I have set wrapper to 4755, user root, start sendmail with the flags /usr/sbin/sendmail -bd -q 15m and I am getting the following error. Has anyone any idea what a solution to this error is? I have followed all the suggestions in the README and the faq, but cannot seem to resolve the problem... Regards, Johan Johan Henselmans work: johan@netsense.nl tel: (+31)-(0)20-6261180 http://www.netsense.nl Netsense vof, Nieuwe Herengracht 149 1011 SG Amsterdam home: johan@hsb.nest.nl tel: (+31)-(0)20-6267538 Nieuwe Herengracht 147d 1011 SG Amsterdam ----- The following addresses had delivery problems ----- "|/usr/local/effe/majordomo/wrapper majordomo" (unrecoverable error) (expanded from: ) ----- Transcript of session follows ----- Message delivered to mailing list sh: /usr/local/effe/majordomo/wrapper: Permission denied 554 "|/usr/local/effe/majordomo/wrapper majordomo"... unknown mailer error 126 ----- 0riginal message follows ----- [ Part 2: "Included Message" ] Date: Wed, 20 Sep 1995 21:16:58 +0100 (WET DST) From: johan Henselmans To: majordomo@hsb.nest.nl Subject: test From majordomo-users-owner Wed Sep 20 13:32:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA24609 for majordomo-users-outgoing; Wed, 20 Sep 1995 13:13:29 -0700 Received: from optical.fiber.net (optical.fiber.net [204.250.13.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA24600 for ; Wed, 20 Sep 1995 13:13:25 -0700 Received: by optical.fiber.net (NX5.67e/NX3.0M) id AA17288; Wed, 20 Sep 95 14:09:40 -0600 Message-Id: <9509202009.AA17288@optical.fiber.net> Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Received: by NeXT.Mailer (1.118.2) From: Carl Payne Date: Wed, 20 Sep 95 14:09:37 -0600 To: majordomo-users@greatcircle.com Subject: Re: problems with unknown mailer error Reply-To: cpayne@optical.fiber.net References: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >and I am getting the following error.=20 > >sh: /usr/local/effe/majordomo/wrapper: Permission denied Sorry, I don't know what it is, but I can add to the fire. I get the exact same error on my NeXT. I went into my sendmail.cf and = changed the P=3D to /bin/csh and I got a different error, but majordomo = worked LOCALLY. I changed the shell to tcsh or zsh and it gave me = "mismatched "."" and "can't determine current directory," respecively. Are you running 1.93? I'm thinking of trying 1.92 just for fun. 1.93 will = NOT work on my system. Good luck, and keep us posted Carl= From majordomo-users-owner Wed Sep 20 13:32:52 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA25030 for majordomo-users-outgoing; Wed, 20 Sep 1995 13:20:51 -0700 Received: from www.CyberMarket.com (cybermarket.cybermarket.com [199.86.32.160]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA25020 for ; Wed, 20 Sep 1995 13:20:45 -0700 Received: from pm4-109.skypoint.net (pm4-109.skypoint.net [199.86.33.109]) by www.CyberMarket.com (8.6.12/8.6.12) with SMTP id PAA25787 for ; Wed, 20 Sep 1995 15:19:31 -0500 Date: Wed, 20 Sep 1995 15:19:31 -0500 Message-Id: <199509202019.PAA25787@www.CyberMarket.com> X-Sender: gmiller@cybermarket.com X-Mailer: Windows Eudora Version 2.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@GreatCircle.COM From: George Miller - The CyberMarketing Group Subject: Digest Problem Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We've got majordomo working like a charm, and are working on setting up a digest now. We're close, but get the following error returned when issue the 'mkdigest' command. Does anybody have any thoughts on what might be wrong? Thanks! George >>>> mkdigest herky-digest $$$$$$ *** digest: failed errors follow producing herky-digest V1 #1 processing /usr/local/bin/majordomo/lists/digests/herky-digest/001 processing /usr/local/bin/majordomo/lists/digests/herky-digest/002 processing /usr/local/bin/majordomo/lists/digests/herky-digest/003 processing /usr/local/bin/majordomo/lists/digests/herky-digest/004 processing /usr/local/bin/majordomo/lists/digests/herky-digest/005 processing /usr/local/bin/majordomo/lists/digests/herky-digest/006 processing /usr/local/bin/majordomo/lists/digests/herky-digest/007 open(DIGEST, ">/usr/local/bin/majordomo/lists/files/herky-digest/v01.n001"): No such file or directory ABORT open(DIGEST, ">/usr/local/bin/majordomo/lists/files/herky-digest/v01.n001"): No such file or directory at majordomo.pl line 209. ________________________________________________ The CyberMarketing Group Full Service Internet Advertising and Consulting gmiller@cybermarket.com http://www.cybermarket.com/ ________________________________________________ From majordomo-users-owner Wed Sep 20 14:01:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA26660 for majordomo-users-outgoing; Wed, 20 Sep 1995 13:34:23 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA26652 for ; Wed, 20 Sep 1995 13:34:20 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA06631 for majordomo-users@greatcircle.com; Wed, 20 Sep 95 13:33:12 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA08430; Wed, 20 Sep 95 13:33:11 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA20228 for majordomo-users@greatcircle.com; Wed, 20 Sep 95 13:33:09 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA09575; Wed, 20 Sep 95 15:33:07 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA13736; Wed, 20 Sep 1995 15:33:06 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509202033.AA13736@miaow.sps.mot.com> Subject: Re: problems with unknown mailer error To: johan@hsb.nest.nl (johan Henselmans) Date: Wed, 20 Sep 1995 15:33:05 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "johan Henselmans" at Sep 20, 95 09:25:43 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1277 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ johan Henselmans writes: ] > > I have set wrapper to 4755, user root, start sendmail with the flags > /usr/sbin/sendmail -bd -q 15m > > and I am getting the following error. Has anyone any idea what a solution > to this error is? [...] > ----- The following addresses had delivery problems ----- > "|/usr/local/effe/majordomo/wrapper majordomo" (unrecoverable error) > (expanded from: ) > > ----- Transcript of session follows ----- > Message delivered to mailing list > sh: /usr/local/effe/majordomo/wrapper: Permission denied > 554 "|/usr/local/effe/majordomo/wrapper majordomo"... unknown mailer > error 126 Your sendmail probably runs as some user/group other than root and majordom (or whatever you call your majordomo gid), so in order for it to run wrapper, it must have execute permission on the entire path leading to wrapper as well as wrapper itself. If that all checks out, then you need to be sure that perl is where the #! line in the scripts (majordomo, resend, request-answer, etc.) say it is and that your majordomo uid or gid has permission to execute it. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Thu Sep 21 03:30:27 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id DAA19487 for majordomo-users-outgoing; Thu, 21 Sep 1995 03:05:45 -0700 Received: from nebula.mpn.com (nebula.mpn.com [194.72.64.30]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id DAA19480 for ; Thu, 21 Sep 1995 03:05:37 -0700 Received: from helios.mpn.com by nebula.mpn.com (5.x/SMI-SVR4) id AA22509; Thu, 21 Sep 1995 11:04:23 +0100 From: nikos@mpn.com (Nikos Drakos) Received: by helios.mpn.com (5.x/Spike-2.0/sweh-1.0) id AA07853; Thu, 21 Sep 1995 11:04:18 +0100 Date: Thu, 21 Sep 1995 11:04:18 +0100 Message-Id: <9509211004.AA07853@helios.mpn.com> To: majordomo-users@greatcircle.com Subject: sendmail dies after a retry on large mailing lists X-Sun-Charset: US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all, I'm running Solaris 2.4, sendmail, and majordomo 1.93. Everything has been ticking along nicely for several months until one of the mailing lists we support grew to over 1000 members. This seems to cause sendmail to coredump after a retry. Perhaps I should add that many of those members are on dialup accounts and their ISP does not always accept delivery of their mail (demon.net :-( and it ends up back on our machines. These messages get queued in one huge bundle and when sendmail tries to send them again it dies. I understand that this is partly a sendmail question but perhaps an interim solution might be to split the large mailing list into smaller parts which perhaps go out at different times. Is there a way to do that with majordomo? Any other suggestions? Thanks in advance, Nikos. -- Nikos Drakos MatriX Publishing Network nikos@mpn.net 32/34 Broadwick Street Tel: +44-171 316 9291 London Fax: +44-171 437 9951 W1A 2HG http://www.mpn.net/ From majordomo-users-owner Thu Sep 21 09:35:14 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA01627 for majordomo-users-outgoing; Thu, 21 Sep 1995 09:07:46 -0700 Received: from mailhost.lanl.gov (mailhost.lanl.gov [128.165.3.12]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA01608 for ; Thu, 21 Sep 1995 09:07:40 -0700 Received: from xdiv.lanl.gov by mailhost.lanl.gov (8.6.12/1.2) id KAA29192; Thu, 21 Sep 1995 10:06:30 -0600 Received: from [128.165.116.127] (dangelo.lanl.gov [128.165.116.127]) by xdiv.lanl.gov (8.6.12/8.6.12) with SMTP id KAA15902 for ; Thu, 21 Sep 1995 10:06:30 -0600 X-Sender: scalia@hayworth.lanl.gov Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 21 Sep 1995 10:09:16 -0600 To: majordomo-users@greatcircle.com From: scalia@lanl.gov (Stephen Paulo Calia) Subject: -request Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk How do you configure majordomo so it will respond to listname-request address? ********************** Stephen Paulo Calia * X Division * scalia@lanl.gov * 667-4159 * * ********************** From majordomo-users-owner Thu Sep 21 09:47:12 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA02348 for majordomo-users-outgoing; Thu, 21 Sep 1995 09:29:16 -0700 Received: from cs.oswego.edu (cs-gw.oswego.edu [129.3.17.9]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA02332 for ; Thu, 21 Sep 1995 09:29:07 -0700 Received: from moxie.cs.oswego.edu by cs.oswego.edu (SMI-8.6/SMI-SVR4) id MAA06851; Thu, 21 Sep 1995 12:27:55 -0400 Received: by moxie.cs.oswego.edu (5.x/SMI-SVR4) id AA01101; Thu, 21 Sep 1995 12:27:36 -0400 Date: Thu, 21 Sep 1995 12:27:31 -0400 (EDT) From: David Bozak To: Majordomo-users@greatcircle.com Subject: from vs. reply-to question not in faq... Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk hi, ok, i read the faq. my mailer (pine) doesn't (as far as i can determine as a user) allow me the option of reply-to INSTEAD of from, only in addition to. i've gotten mail from list members who want the from line to be the list name...can this be done? help is always appreciated... -dab ============================================================================= David Alan Bozak Computer Science Department ________|________ dab@cs.oswego.edu SUNY Oswego, Oswego, NY 13126 ___\__(*)__/___ (315) 341-2347 http://www.cs.oswego.edu/~dab o/ \o From majordomo-users-owner Thu Sep 21 10:00:36 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA02440 for majordomo-users-outgoing; Thu, 21 Sep 1995 09:33:44 -0700 Received: from www.CyberMarket.com (cybermarket.cybermarket.com [199.86.32.160]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA02430 for ; Thu, 21 Sep 1995 09:33:36 -0700 Received: from pm1-22.skypoint.net (pm1-22.skypoint.net [199.86.33.22]) by www.CyberMarket.com (8.6.12/8.6.12) with SMTP id LAA04322 for ; Thu, 21 Sep 1995 11:32:08 -0500 Date: Thu, 21 Sep 1995 11:32:08 -0500 Message-Id: <199509211632.LAA04322@www.CyberMarket.com> X-Sender: gmiller@cybermarket.com X-Mailer: Windows Eudora Version 2.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@GreatCircle.COM From: George Miller - The CyberMarketing Group Subject: deleting message footers in digests Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We currently use a message footer in the regular version of our list, but I would like this stripped in the digest version. Since the digest_rm_footer is 'non-operative', does anybody know of another way to accomplish this? Thanks! George ________________________________________________ The CyberMarketing Group Full Service Internet Advertising and Consulting gmiller@cybermarket.com http://www.cybermarket.com/ ________________________________________________ From majordomo-users-owner Thu Sep 21 11:00:20 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA04365 for majordomo-users-outgoing; Thu, 21 Sep 1995 10:33:10 -0700 Received: from seal.css.edu (seal.css.edu [143.110.75.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA04356 for ; Thu, 21 Sep 1995 10:33:04 -0700 Received: by seal.css.edu (5.x/SMI-SVR4) id AA26243; Thu, 21 Sep 1995 12:29:06 -0500 Received: from lava.css.edu(143.110.80.1) by seal via smap (V1.3) id sma026239; Thu Sep 21 12:28:57 1995 Received: by lava.css.edu (5.x/SMI-SVR4) id AA28677; Thu, 21 Sep 1995 12:30:51 -0500 Received: from mailgate.css.edu(143.110.2.175) by lava via smap (V1.3) id sma028668; Thu Sep 21 12:30:25 1995 Received: by mailgate.css.edu with Microsoft Mail id <3061BE28@mailgate.css.edu>; Thu, 21 Sep 95 12:34:00 PDT From: CROW To: "Majordomo-Users@" Subject: FW: listserv msmail question Date: Thu, 21 Sep 95 12:29:00 PDT Message-Id: <3061BE28@mailgate.css.edu> Encoding: 50 TEXT X-Mailer: Microsoft Mail V3.0 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We are trying to setup a listserv on one of our unix boxes on campus running majordomo, but are running into problems using the microsoft mail client (see the examples below). Is there a trick to getting the mail header in microsoft mail to show the true sender of the message? Is this a configuration issue with majordomo or msmail? Is anyone out there who uses msmail also running a listserv and if so what listserv software do you use? Thanks in advance. EXAMPLE #1 Below is a mail message received using a eudora mail client: From: CROW To: test serv Subject: Rotorouter Test Date: Wed, 20 Sep 95 15:48:00 PDT Encoding: 4 TEXT Sender: owner-test Precedence: bulk I follow instructions pretty well, even when I don't know what I'm doing. Crow ----------------------------- EXAMPLE #2 Below is the same mail message received using a microsoft mail client: From: majordom To: test serv Subject: Rotorouter Test Date: Wednesday, September 20, 1995 3:48PM I follow instructions pretty well, even when I don't know what I'm doing. Crow --------------------------- From majordomo-users-owner Thu Sep 21 11:31:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA05372 for majordomo-users-outgoing; Thu, 21 Sep 1995 11:08:24 -0700 Received: from ECE.ORST.EDU (ECE.ORST.EDU [128.193.48.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id LAA05365 for ; Thu, 21 Sep 1995 11:08:20 -0700 Received: from darkwing.ECE.ORST.EDU by ECE.ORST.EDU with SMTP (1.38.193.4/16.2) id AA27681; Thu, 21 Sep 1995 11:07:13 -0700 Received: by darkwing.ECE.ORST.EDU (NX5.67e/NX3.0S) id AA08051; Thu, 21 Sep 95 11:05:44 -0700 Message-Id: <9509211805.AA08051@darkwing.ECE.ORST.EDU> Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Received: by NeXT.Mailer (1.118.2) From: Mike Miller Date: Thu, 21 Sep 95 11:05:37 -0700 To: staff@ECE.ORST.EDU Subject: Majordomo woes over Cc: ringwas@darkwing.ece.orst.edu, toml@engr.ORST.EDU, log@ECE.ORST.EDU, majordomo-users@greatcircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is an interesting problem that as far as I know only exists on HP-UX (I know it doesn't on NextStep) and I thought I would share it with you so you don't have to experience it for yourself. After wasting many hours trying to hack the wrapper and other stupid solutions I finally figure out that my problem is that it can't create this lock file, so I give global permissions and do a `while 1` with a `ls -la | grep shlock` to find out who is trying to create it and failing. It turns out it is my account, despite the fact that I had su2ed to majordomo, and su2ed to root to install the wrapper. The reason is that like the mail program, it looked at my real uid/gid instead of my effective uid/gid when compiling the wrapper. The obvious solution was to log in as root (no su2) and compile/install the wrapper. The happy ending to the story is that majordomo compiles with posix options (using gcc, HP's cc barfs) without code modification and appears to run fine as long as you avoid su2. I hope this saves somebody some time :-) From majordomo-users-owner Thu Sep 21 12:01:36 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA07365 for majordomo-users-outgoing; Thu, 21 Sep 1995 11:56:24 -0700 Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA07358 for ; Thu, 21 Sep 1995 11:56:18 -0700 Received: from plvns1.edc.ge.com ([3.46.4.200]) by ns.ge.com (8.6.12/8.6.11) with ESMTP id OAA04122 for ; Thu, 21 Sep 1995 14:55:09 -0400 Received: from mssmtp1.edc.ge.com (mssmtp1.edc.ge.com [3.46.20.215]) by plvns1.edc.ge.com (8.6.11/8.6.11) with SMTP id OAA09824 for ; Thu, 21 Sep 1995 14:52:56 -0400 Received: by mssmtp1.edc.ge.com with Microsoft Mail id <3061B571@mssmtp1.edc.ge.com>; Thu, 21 Sep 95 14:56:49 EDT From: "Flynn, Bill" To: "Majordomo-Users (listserv)" Subject: RE: listserv msmail question Date: Thu, 21 Sep 95 14:55:00 EDT Message-ID: <3061B571@mssmtp1.edc.ge.com> Encoding: 120 TEXT X-Mailer: Microsoft Mail V3.0 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Crow, It sounds like a MS Mail problem. Make sure you're running the latest version of the SMTP gateway software (3.0.9). You can pull it down from the MS ftp server. Next, on your SMTPGATE startup command line, make sure you have the "-f" option included. This causes MS Mail to use the RFC-822 From field. It seems to work for us. Before the "-f", all my messages from listservs used to show list-owner as the sender. Now, with the "-f" switch, all my messages show the true sender of the message. Bill Flynn GE Electrical Distribution and Control bill.flynn@edc.ge.com ---------- >From: CROW >To: Majordomo-Users@ >Subject: FW: listserv msmail question >Date: Thursday, September 21, 1995 12:29pm > >Return-Path: >Received: from plvns1.edc.ge.com by mssmtp1.edc.ge.com id > <3061AAC3@mssmtp1.edc.ge.com>; Thu, 21 Sep 95 14:11:15 EDT >Received: from thomas.ge.com (thomas.ge.com [3.47.28.21]) by plvns1.edc.ge.com > (8.6.11/8.6.11) with ESMTP id OAA09177 for ; Thu, 21 > Sep 1995 14:07:17 -0400 >Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by thomas.ge.com > (8.6.12/8.6.12) with ESMTP id OAA15451 for ; Thu, 21 > Sep 1995 14:05:10 -0400 >Received: from relay4.UU.NET (relay4.UU.NET [192.48.96.14]) by ns.ge.com > (8.6.12/8.6.11) with ESMTP id OAA28187 for ; Thu, 21 > Sep 1995 14:09:23 -0400 >Received: from miles.greatcircle.com by relay4.UU.NET with ESMTP id > QQziei13999; Thu, 21 Sep 1995 14:03:31 -0400 >Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) > id KAA04365 for majordomo-users-outgoing; Thu, 21 Sep 1995 10:33:10 -0700 >Received: from seal.css.edu (seal.css.edu [143.110.75.1]) by > miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA04356 for > ; Thu, 21 Sep 1995 10:33:04 -0700 >Received: by seal.css.edu (5.x/SMI-SVR4) id AA26243; Thu, 21 Sep 1995 12:29:06 > -0500 >Received: from lava.css.edu(143.110.80.1) by seal via smap (V1.3) id > sma026239; Thu Sep 21 12:28:57 1995 >Received: by lava.css.edu (5.x/SMI-SVR4) id AA28677; Thu, 21 Sep 1995 12:30:51 > -0500 >Received: from mailgate.css.edu(143.110.2.175) by lava via smap (V1.3) id > sma028668; Thu Sep 21 12:30:25 1995 >Received: by mailgate.css.edu with Microsoft Mail id > <3061BE28@mailgate.css.edu>; Thu, 21 Sep 95 12:34:00 PDT >From: CROW >To: "Majordomo-Users@" >Subject: FW: listserv msmail question >Date: Thu, 21 Sep 95 12:29:00 PDT >Message-Id: <3061BE28@mailgate.css.edu> >Encoding: 50 TEXT >X-Mailer: Microsoft Mail V3.0 >Sender: majordomo-users-owner@GreatCircle.COM >Precedence: bulk >--------------------------------------------------------------------------- --- > > >We are trying to setup a listserv on one of our unix boxes on campus running > >majordomo, but are running into problems using the microsoft mail client >(see >the examples below). Is there a trick to getting the mail header in >microsoft mail to show the true sender of the message? Is this a >configuration issue with majordomo or msmail? Is anyone out there who uses >msmail also running a listserv and if so what listserv software do you use? > >Thanks in advance. > > > >EXAMPLE #1 > >Below is a mail message received using a eudora mail client: > > >From: CROW >To: test serv >Subject: Rotorouter Test >Date: Wed, 20 Sep 95 15:48:00 PDT >Encoding: 4 TEXT >Sender: owner-test >Precedence: bulk > > >I follow instructions pretty well, even when I don't know what I'm doing. > >Crow > ----------------------------- > > >EXAMPLE #2 > >Below is the same mail message received using a microsoft mail client: > > >From: majordom >To: test serv >Subject: Rotorouter Test >Date: Wednesday, September 20, 1995 3:48PM > > >I follow instructions pretty well, even when I don't know what I'm doing. > >Crow > --------------------------- > From majordomo-users-owner Thu Sep 21 14:00:54 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA12327 for majordomo-users-outgoing; Thu, 21 Sep 1995 13:50:42 -0700 Received: from ncrhub1.ATTGIS.COM (h192-127-251-3.ATTGIS.COM [192.127.251.3]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA12320 for ; Thu, 21 Sep 1995 13:50:39 -0700 Received: from ncrhub4 by ncrhub1.ATTGIS.COM id ae07162; 21 Sep 95 16:47 EDT Received: by ncrhub4.ATTGIS.COM; 21 Sep 95 16:45:33 EDT Received: by ncr-sd.SanDiegoCA.ATTGIS.COM; 21 Sep 95 13:46:11 PDT X-Sender: bhoule@www.sandiegoca.attgis.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: CROW , Majordomo-Users@greatcircle.com From: Bill Houle Subject: Re: FW: listserv msmail question Date: Thu, 21 Sep 95 16:45:00 EDT Message-ID: <9509211647.ae07162@ncrhub1.ATTGIS.COM> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 12:29 PM 9/21/95 PDT, CROW wrote: > >We are trying to setup a listserv on one of our unix boxes on campus running > >majordomo, but are running into problems using the microsoft mail client >(see >the examples below). Is there a trick to getting the mail header in >microsoft mail to show the true sender of the message? Is this a >configuration issue with majordomo or msmail? Is anyone out there who uses >msmail also running a listserv and if so what listserv software do you use? Earlier versions of the MSMail SMTP software used rfc821 addresses (the envelope) for the From:. If you get the latest version from the MS FTP site, and run it with "-f", it will support rfc822 addresses. -- Bill Houle Bill.Houle@SanDiegoCA.ATTGIS.COM AT&T Global Information Solutions (619) 485-4027 From majordomo-users-owner Thu Sep 21 16:02:15 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA15991 for majordomo-users-outgoing; Thu, 21 Sep 1995 15:33:57 -0700 Received: from mailhost.lanl.gov (mailhost.lanl.gov [128.165.3.12]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id PAA15984 for ; Thu, 21 Sep 1995 15:33:53 -0700 Received: from xdiv.lanl.gov by mailhost.lanl.gov (8.6.12/1.2) id QAA26922; Thu, 21 Sep 1995 16:32:49 -0600 Received: from [128.165.116.127] (dangelo.lanl.gov [128.165.116.127]) by xdiv.lanl.gov (8.6.12/8.6.12) with SMTP id QAA20671; Thu, 21 Sep 1995 16:32:48 -0600 X-Sender: scalia@hayworth.lanl.gov Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 21 Sep 1995 16:35:35 -0600 To: staff@ECE.ORST.EDU From: scalia@lanl.gov (Stephen Paulo Calia) Subject: Majordomo woes over Cc: ringwas@darkwing.ece.orst.edu, toml@engr.ORST.EDU, log@ECE.ORST.EDU, majordomo-users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk You might find this interesting. This is an interesting problem that as far as I know only exists on HP-UX (I know it doesn't on NextStep) and I thought I would share it with you so you don't have to experience it for yourself. After wasting many hours trying to hack the wrapper and other stupid solutions I finally figure out that my problem is that it can't create this lock file, so I give global permissions and do a `while 1` with a `ls -la | grep shlock` to find out who is trying to create it and failing. It turns out it is my account, despite the fact that I had su2ed to majordomo, and su2ed to root to install the wrapper. The reason is that like the mail program, it looked at my real uid/gid instead of my effective uid/gid when compiling the wrapper. The obvious solution was to log in as root (no su2) and compile/install the wrapper. The happy ending to the story is that majordomo compiles with posix options (using gcc, HP's cc barfs) without code modification and appears to run fine as long as you avoid su2. I hope this saves somebody some time :-) ********************** Stephen Paulo Calia * X Division * scalia@lanl.gov * 667-4159 * * ********************** From majordomo-users-owner Thu Sep 21 16:34:38 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA18988 for majordomo-users-outgoing; Thu, 21 Sep 1995 16:32:12 -0700 Received: from hq.stargame.org (bh.mindspring.com [168.121.33.204]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA19875 for ; Wed, 20 Sep 1995 11:52:08 -0700 Received: (from bh@localhost) by hq.stargame.org (8.6.12/8.6.9) id NAA09759; Tue, 19 Sep 1995 13:55:53 -0400 Date: Tue, 19 Sep 1995 13:55:51 -0400 (EDT) From: Brian Hartsfield To: Carl Payne cc: majordomo-users@GreatCircle.COM Subject: Re: Not in FAQ: no log, same reply no matter what In-Reply-To: <9509190607.AA27225@optical.fiber.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Tue, 19 Sep 1995, Carl Payne wrote: > Nothing in the log and, no matter what the command is, whether it's subscribe > list or help or whatever, I get the majordomo-supplied response, not the one > I wrote. What did you do to try to change the responces? You would have to hack the perl code to change the messages that majordomo replies with. (except for the list info message). Brian From majordomo-users-owner Thu Sep 21 16:34:39 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA18971 for majordomo-users-outgoing; Thu, 21 Sep 1995 16:32:06 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA13919 for ; Wed, 20 Sep 1995 09:37:47 -0700 Received: from ro.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA17621; Wed, 20 Sep 1995 12:36:39 -0400 (wiseb from ro.cs.rpi.edu) Message-Id: <199509201636.AA17621@cs.rpi.edu> X-Mailer: exmh version 1.6.1 5/23/95 To: majordomo-users@greatcircle.com Subject: Repyling to Bounced Admin Messages Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 1995 12:36:37 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Does anyone have any scripts that make it easy to deal with the bounced admin messagse that you get when someone sends a subscribe request to a list? I would like to send the request-answer script; is there a way to generate this script from the shell for a particular users? What do other people do with their bounced admin emails? Has anyone patched resend to send off an automatic message to users that send admin requests to the list? To me that seems the best way... -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Thu Sep 21 17:01:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id QAA20573 for majordomo-users-outgoing; Thu, 21 Sep 1995 16:56:35 -0700 Received: from pathfinder.com (relay.pathfinder.com [204.71.242.18]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id QAA20565 for ; Thu, 21 Sep 1995 16:56:32 -0700 Received: from bigmouth.pathfinder.com by pathfinder.com (8.6.12/SMI-SVR4) id TAA23110; Thu, 21 Sep 1995 19:55:02 -0400 From: ahanes@pathfinder.com (Amanda Hanes (Pathfinder)) Received: from chutney.dev.pathfinder.com by bigmouth.pathfinder.com (5.x) id AA27405; Thu, 21 Sep 1995 19:55:26 -0400 Received: by chutney.dev.pathfinder.com (5.x) id AA11321; Thu, 21 Sep 1995 19:55:26 -0400 Message-Id: <9509212355.AA11321@chutney.dev.pathfinder.com> Date: Thu, 21 Sep 1995 19:55:24 -0400 (EDT) Subject: How to handle LARGE majordomo lists. . . To: ahanes@pathfinder.com Cc: majordomo-users@greatcircle.com X-Mailer: Ishmail 1.1-950814-sol24 Mime-Version: 1.0 Content-Type: text/plain Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We have a list which currently has several thousand email addresses on it. Its rapidly getting bigger and there seems to be no end in sight. What would you suggest for this list? Should we stay with majordomo? Should we go to another list-serve type package? What about bulk-mailer? I can't seem to find any information on bulk-mailer but I've seen mentions on this mailing list. Any suggestions or help would be greatly appreciated!! Amanda ************************************************************ Amanda S. Hanes System Engineer, Pathfinder Time Inc., New Media 212-522-3585 From majordomo-users-owner Thu Sep 21 21:02:53 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id VAA00512 for majordomo-users-outgoing; Thu, 21 Sep 1995 21:00:30 -0700 Received: from ASARian.org (ASARian.org [152.52.36.201]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id VAA00503 for ; Thu, 21 Sep 1995 21:00:26 -0700 Received: from ASARian.org (fuzzy@ASARian.org [152.52.36.201]) by ASARian.org (8.6.10/8.6.12) with SMTP id XAA00358 for ; Thu, 21 Sep 1995 23:59:19 -0400 Date: Thu, 21 Sep 1995 23:59:18 -0400 (EDT) From: Fuzzy To: Majordomo-users List Subject: nobody sendmail alias Message-ID: Organization: *fuzzies* and *e-hugs* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk sorry to be so dumb... but how do I define the nobody alias to route it to /dev/null? nobody: "/dev/null" and nobody: "|/dev/null" fail with errors saying it could not run. *sigh* fuzzy From majordomo-users-owner Fri Sep 22 02:31:33 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id CAA07631 for majordomo-users-outgoing; Fri, 22 Sep 1995 02:05:32 -0700 Received: from ita.tip.net (peroni.ita.tip.net [194.20.0.111]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id CAA07624 for ; Fri, 22 Sep 1995 02:05:22 -0700 Received: from [194.20.0.55] ([194.20.0.55]) by ita.tip.net (8.7.Beta.2/8.7.Beta.2) with SMTP id LAA20612 for ; Fri, 22 Sep 1995 11:03:37 +0200 (MET DST) Date: Fri, 22 Sep 1995 11:03:37 +0200 (MET DST) Message-Id: <199509220903.LAA20612@ita.tip.net> X-Authentication-Warning: peroni: Host [194.20.0.55] didn't use HELO protocol X-Sender: varoli@ita.tip.net X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: varoli@ita.tip.net (Varoli Marco) Subject: mailer error Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I received the follow error from my majordomo: ----- The following addresses have delivery notifications ----- "|/opt/local/bin/majordomo/sbin/wrapper majordomo" (unrecoverable error) (expanded from: majordom) ----- Transcript of session follows ----- Segmentation Fault 554 "|/opt/local/bin/majordomo/sbin/wrapper majordomo"... unknown mailer error 139 Thanks, Marco _____________________________________________________________________________ /\ /\ / Marco Varoli / \ / \ / e-mail: varoli@ita.tip.net / \/ \ / s-mail: UniSource Italy / \/ Via Caldera, 21 \ /\ I-20153 Milano (Italy) \ / \ phone: +39 2 482421 \/ fax : +39 2 48242424 _____________________________________________________________________________ From majordomo-users-owner Fri Sep 22 03:00:19 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id CAA08447 for majordomo-users-outgoing; Fri, 22 Sep 1995 02:56:05 -0700 Received: from gamma.dou.dk (gamma.dou.dk [130.225.156.14]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id CAA08438 for ; Fri, 22 Sep 1995 02:55:38 -0700 Received: from dou-pc1 (peter.dou.dk [130.225.156.244]) by gamma.dou.dk (8.6.10/8.6.10) with SMTP id LAA23346; Fri, 22 Sep 1995 11:52:57 +0200 Date: Fri, 22 Sep 1995 11:52:57 +0200 Message-Id: <199509220952.LAA23346@gamma.dou.dk> X-Sender: maspsr@mail.dou.dk Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Len Hatfield , majordomo-users@GreatCircle.COM From: maspsr@gamma.dou.dk (Peter Sorensen) Subject: Re: Index/Archive2.pl not working.... X-Mailer: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 04:00 PM 19/9/95, Len Hatfield wrote: >Folks: > >I've got a list working away under Majordomo 1.93; >sendmail aliases are in place; and an archive file is >accumulating. > >But an 'index' command sent to majordomo reports that there >aren't any files for that list. > >Plus, when I run archive2.pl like so: > > archive2.pl -f /path/to/list -d -u /path/to/archive/file > >it tells me that the archive directory is invalid. > >Pointers? You have to append the name of your archive directory to the @archive_dirs array in majordomo.cf. regards Peter Sorensen/University of Odense,dk/e-mail:maspsr@dou.ou.dk From majordomo-users-owner Fri Sep 22 08:05:27 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA18777 for majordomo-users-outgoing; Fri, 22 Sep 1995 08:00:33 -0700 Received: from tiger.coe.missouri.edu (tiger.coe.missouri.edu [128.206.59.185]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id IAA18770 for ; Fri, 22 Sep 1995 08:00:26 -0700 Received: from tiger.coe.missouri.edu by tiger.coe.missouri.edu via SMTP (950215.SGI.8.6.10/940406.SGI) for id JAA06978; Fri, 22 Sep 1995 09:59:14 -0500 Date: Fri, 22 Sep 1995 09:59:14 -0500 (CDT) From: Humphrey Loe To: majordomo-users@GreatCircle.COM Subject: Digest config file Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have majordomo1.93 on IRIX5.3 running and trying to use the digest. However, the digest.cf file was not in the archive when I downloaded. Could someone post a sample digest.cf file? From majordomo-users-owner Sat Sep 23 12:00:10 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id LAA06914 for majordomo-users-outgoing; Sat, 23 Sep 1995 11:48:12 -0700 Received: from ASARian.org (ASARian.org [152.52.36.201]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA06907 for ; Sat, 23 Sep 1995 11:48:07 -0700 Received: from ASARian.org (fuzzy@ASARian.org [152.52.36.201]) by ASARian.org (8.6.10/8.6.12) with SMTP id OAA01169 for ; Sat, 23 Sep 1995 14:47:02 -0400 Date: Sat, 23 Sep 1995 14:47:01 -0400 (EDT) From: Fuzzy To: Majordomo-users List Subject: re: BOUNCE courage@asarian.org: Imbalanced parentheses or angle brackets Message-ID: Organization: *fuzzies* and *e-hugs* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk anyone know why a quoted name would cause this email to have been bounced??? and a fix to not bounce it ?? seems a bit "overkill" to us. Your Friend, _____ __ __ ____ ____ __ __ / ___// // //__ )/__ )\ \/ / / __/ / // / / /__ / /__\ / (_/ (____/ <____/<____//_/ SysAdmin, ASARian.org Email: fuzzy@asarian.org (non-anon) an72289@anon.penet.fi (true anon) anon-2986@anon.twwells.com (true anon) Send email to fuzzykey@asarian.org with a subject of send key for my current PGP public key. ---------- Forwarded message ---------- Date: Sat, 23 Sep 1995 12:42:19 -0400 From: owner-courage@asarian.org To: owner-courage@asarian.org Subject: BOUNCE courage@asarian.org: Imbalanced parentheses or angle brackets >From fuzzy Sat Sep 23 12:42:05 1995 From: "Ellen M. Jensen ;-)" From majordomo-users-owner Sat Sep 23 12:30:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA07649 for majordomo-users-outgoing; Sat, 23 Sep 1995 12:22:04 -0700 Received: from MediaCity.com (easy1.mediacity.com [205.216.172.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id MAA07641 for ; Sat, 23 Sep 1995 12:22:01 -0700 Received: (from josef@localhost) by MediaCity.com (8.6.11/8.6.9) id MAA23410 for majordomo-users@greatcircle.com; Sat, 23 Sep 1995 12:22:01 -0700 Date: Sat, 23 Sep 1995 12:22:01 -0700 From: Josef Rokicki Message-Id: <199509231922.MAA23410@MediaCity.com> To: majordomo-users@greatcircle.com Subject: Memory fault Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Whenever I send a command to the majordomo on my system majordomo runs the "|/usr/local/majordomo/bin/wrapper majordomo" (unrecoverable error) (expanded from: majordomo) Message delivered to mailing list majordomo Memory fault 554 "|/usr/local/majordomo/bin/wrapper majordomo"... unknown mailer error 139 Also, when I run the command: echo "" | /usr/local/majordomo/bin/wrapper majordomo I get the this error message: majordomo@MediaCity.com: is not a valid return address. I tried to change the $whoami variable to josef@mediacity.com but it gave me this error: josef@mediacity.com: is not a valid return address. I have tried changing the whoami to various other things, but nothing seems to fix the error. Any suggestions? -Josef Rokicki MediaCity From majordomo-users-owner Sat Sep 23 18:23:42 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA08936 for majordomo-users-outgoing; Sat, 23 Sep 1995 18:21:16 -0700 Received: from j51.com (j51.com [199.224.7.51]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id SAA08929 for ; Sat, 23 Sep 1995 18:21:13 -0700 Received: from pm4.j51.com (pm4.j51.com [199.224.7.228]) by j51.com (8.6.12/8.6.9) with SMTP id BAA12455 for ; Sun, 24 Sep 1995 01:19:50 GMT Message-Id: <199509240119.BAA12455@j51.com> X-Sender: genesis@j51.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 23 Sep 1995 21:11:17 -0400 To: majordomo-users@greatcircle.com From: Project Genesis Subject: Digest Error Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We have a list 'forum', appropriately accompanied by a digest. Mail comes through on forum just fine, but the digest returns... ----- The following addresses had delivery problems ----- "|/usr/local/lib/majordomo-1.93/wrapper digest -r -C -l forum-digest forum-digest-outgoing" (unrecoverable error) (expanded from: forum-outgoing) ----- Transcript of session follows ----- open of temp file $listdir/digest/forum-digest/shlock.22780 failed No such file or directory ABORT open of temp file $listdir/digest/forum-digest/shlock.22780 failed No such file or directory at majordomo.pl line 209. 554 "|/usr/local/lib/majordomo-1.93/wrapper digest -r -C -l forum-digest forum-digest-outgoing"... unknown mailer error 2 Any ideas? Ken Menken From majordomo-users-owner Sat Sep 23 20:22:20 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id UAA10189 for majordomo-users-outgoing; Sat, 23 Sep 1995 20:14:40 -0700 Received: from sparc (Sparc.uccb.ns.ca [142.12.4.50]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id UAA10182 for ; Sat, 23 Sep 1995 20:14:36 -0700 Received: by sparc (5.0/SMI-SVR4) id AA28549; Sun, 24 Sep 1995 00:13:58 +0400 Date: Sun, 24 Sep 1995 00:13:58 -0300 (ADT) From: Steve MacLeod Subject: ANNOUNCE: WAIS Searching on Majordomo Archives To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 902 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi All It's not often that I get to contribute something to this forum but, I think you might be interested to check out a WAIS search ability I implemented on one of our servers. The URL is http://w3.uccb.ns.ca/majordomo I have yet to put some pretty graphics and such on the page but, there is a help file for all the options with WAIS searching. A big benefit is that the word you specify can be anywhere in the document ... When you select the WAIS search page you will see a number of databases to search ... I use the Clarion Programming language, you will see those archives there too. Check It Out! Best Regards 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 From majordomo-users-owner Mon Sep 25 08:24:16 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA14467 for majordomo-users-outgoing; Mon, 25 Sep 1995 08:18:23 -0700 Received: from remora.ssp.nmfs.gov (remora.ssp.nmfs.gov [155.206.15.40]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id IAA14455 for ; Mon, 25 Sep 1995 08:18:19 -0700 Received: by remora.ssp.nmfs.gov (940816.SGI.8.6.9/940406.SGI) for majordomo-users@greatcircle.com id LAA00465; Mon, 25 Sep 1995 11:16:22 -0400 From: kbfoster@remora.ssp.nmfs.gov (Karen Brown Foster) Message-Id: <9509251116.ZM463@remora.ssp.nmfs.gov> Date: Mon, 25 Sep 1995 11:16:22 -0400 X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: majordomo-users@greatcircle.com Subject: Majordomo Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello users: I am new to the mailing list and hope that someone can be of assistance. I have successfully installed majordomo on an SGI workstation running IRIX 5.3. I am running Majordomo version 1.93 and Perl version 4.036. I have enclosed a copy of my alias file. What I have done is to create a test listname called admins. I have been running tests with this list to see if everything is working correctly. I am able to send help requests to the list, subscribe users to the list, etc. The problem I am having is that when someone sends mail to the list, the mail goes to everyone in the list, but if anyone in the list replies to the mail, the reply goes back to the sender of the mail instead of to everyone that is a member of the list. I would like the reply to be seen by everyone in the list. Can anyone see or tell me what I'm doing wrong? Thanks in advance. Karen Brown Foster ###### aliases file ###### owner-owner: postmaster # # Majordomo # majordomo: "|/usr1/apps/majordomo/wrapper majordomo" owner-majordomo: kbfoster, nobody majordom: owner-majordomo #Needed "just in case" for Majordomo version 1.9x: Majordomo-Owner: owner-majordomo # admins mailing list owner-admins: kbfoster, nobody admins: "|/usr1/apps/majordomo/wrapper resend -l admins -h remora.ssp.nmfs.gov admins-outgoing" admins-approval: owner-admins admins-outgoing: :include:/usr1/apps/majordomo/lists/admins, admins-archive owner-admins-outgoing: owner-admins admins-archive: "|/usr1/apps/majordomo/wrapper archive -f /usr1/apps/majordomo/archives/admins/admins -m -a" owner-admins-archive: owner-admins admins-request: "|/usr1/apps/majordomo/wrapper request-answer admins" owner-admins-request: owner-admins -- Karen Brown Foster Unix System Administrator Fisheries Statitics Division National Marine Fisheries Service (301) 713-2316 VOICE (301) 713-4137 FAX kbfoster@oyster.ssp.nmfs.gov From majordomo-users-owner Mon Sep 25 08:30:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA14966 for majordomo-users-outgoing; Mon, 25 Sep 1995 08:28:33 -0700 Received: from remora.ssp.nmfs.gov (remora.ssp.nmfs.gov [155.206.15.40]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id IAA14959 for ; Mon, 25 Sep 1995 08:28:31 -0700 Received: by remora.ssp.nmfs.gov (940816.SGI.8.6.9/940406.SGI) for majordomo-users@greatcircle.com id LAA00474; Mon, 25 Sep 1995 11:26:34 -0400 From: kbfoster@remora.ssp.nmfs.gov (Karen Brown Foster) Message-Id: <9509251126.ZM472@remora.ssp.nmfs.gov> Date: Mon, 25 Sep 1995 11:26:34 -0400 X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: majordomo-users@greatcircle.com Subject: Testing Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Could someone please answer this so that I can see if I'm still a member of this group. Thanks in advance. Karen -- Karen Brown Foster Unix System Administrator Fisheries Statitics Division National Marine Fisheries Service (301) 713-2316 VOICE (301) 713-4137 FAX kbfoster@oyster.ssp.nmfs.gov From majordomo-users-owner Mon Sep 25 09:24:09 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA17301 for majordomo-users-outgoing; Mon, 25 Sep 1995 09:04:38 -0700 Received: from pigeon.cf.ac.uk (pigeon.cf.ac.uk [131.251.0.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id JAA17266 for ; Mon, 25 Sep 1995 09:04:24 -0700 Received: from thor.cf.ac.uk by pigeon.cf.ac.uk with SMTP (PP) id <18810-0@pigeon.cf.ac.uk>; Mon, 25 Sep 1995 17:00:02 +0100 Date: Mon, 25 Sep 1995 16:59:08 +0100 (BST) From: Andrew Cormack Reply-To: Andrew Cormack To: majordomo-users@greatcircle.com Subject: Majordomo and OSF/1 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've heard a lot of reports about problems with MD on OSF systems, but nothing specific about what actions cause what problems. Since our current MD server (an ultrix box) is being pensioned off in favour of a new DECAlpha, I'd be interested in any detailed reports of what problems have been found in what areas of the system's operation. This should help me to decide whether my own system is working or not. I'll post a summry of any replies to the list, so please feel free to e-mail me direct as . Thanks, Andrew -- +-----------------------------------------------------------------+ | Andrew Cormack | email: cormack@cardiff.ac.uk | | Information Systems Support, | snail: 40/41 Park Place, Cardiff | | postmaster and webmaster | CF1 3BB | | University of Wales, Cardiff | | +-----------------------------------------------------------------+ From majordomo-users-owner Mon Sep 25 10:24:16 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA19727 for majordomo-users-outgoing; Mon, 25 Sep 1995 10:05:55 -0700 Received: from jrv.qc.ca (jrv.interax.net [199.84.226.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA19720 for ; Mon, 25 Sep 1995 10:05:44 -0700 Received: from denis (meigs.orion.jrv.qc.ca [204.19.247.2]) by jrv.qc.ca (8.6.12/8.6.9) with SMTP id MAA17141 for ; Mon, 25 Sep 1995 12:27:11 GMT Message-Id: <199509251227.MAA17141@jrv.qc.ca> Comments: Authenticated sender is From: "Denis Dumouchel" To: Majordomo-users@GreatCircle.COM Date: Mon, 25 Sep 1995 13:02:10 +0000 Subject: Double messages Reply-to: denis@jrv.qc.ca Priority: normal X-mailer: Pegasus Mail for Windows (v2.0-WB1) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello, I administer a mailing list , that my Internet provider runs with Majordomo, but we have the following bug: Everyone who is subscribe to the list receives the messages in double, except the messages that come from my provisers server. He uses "Linux" and "send mail". He tried to set the software properly using the FAQ, but the problem remains. He work arround the queue process interval (-q flag), and the interval between queue checkpoints (OC flag in sendmail.cf) . Does anyone know of the good settings he could use to solve the problem, or does someone knows another solution to the problem? thanks, Denis =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Denis Dumouchel Dunham, Quebec,Ca. denis@jrv.qc.ca http://www.ornitho.com/ "Les oiseaux de l'autoroute electronique" =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- From majordomo-users-owner Mon Sep 25 14:25:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA27967 for majordomo-users-outgoing; Mon, 25 Sep 1995 14:06:51 -0700 Received: from remora.ssp.nmfs.gov (remora.ssp.nmfs.gov [155.206.15.40]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id OAA27960 for ; Mon, 25 Sep 1995 14:06:46 -0700 Received: by remora.ssp.nmfs.gov (940816.SGI.8.6.9/940406.SGI) for majordomo-users@greatcircle.com id RAA01080; Mon, 25 Sep 1995 17:04:48 -0400 From: kbfoster@remora.ssp.nmfs.gov (Karen Brown Foster) Message-Id: <9509251704.ZM1078@remora.ssp.nmfs.gov> Date: Mon, 25 Sep 1995 17:04:48 -0400 X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: majordomo-users@greatcircle.com Subject: Reply to listname Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello: I sent this message out earlier and didn't receive a reply, so I'm sending it again. I am running majordomo 1.93 on an SGI workstation running IRIX 5.3. I am running Perl version 4.036. I have majordomo set up and running but I have one problem. When I send mail to my listname (admins), it gets sent to everyone in the list. However, when someone replies to the message, the reply gets sent to the send of the mail and not to everyone in the list which is how I would like it to work. Is this even possible with majordomo? I am including a copy of my /etc/aliases file, but perhaps the problem may be one of the parameters in the majordomo.cf file. I will also include it. Any help that anyone can provide would very much be appreciated. Thanks in advance. Karen Brown Foster ############### ## /etc/aliases ############### owner-owner: postmaster # # Majordomo # majordomo: "|/usr1/apps/majordomo/wrapper majordomo" owner-majordomo: kbfoster, nobody majordom: owner-majordomo #Needed "just in case" for Majordomo version 1.9x: Majordomo-Owner: owner-majordomo # admins mailing list owner-admins: kbfoster, nobody admins: "|/usr1/apps/majordomo/wrapper resend -l admins -h remora.ssp.nmfs.gov admins-outgoing" admins-approval: owner-admins admins-outgoing: :include:/usr1/apps/majordomo/lists/admins, admins-archive owner-admins-outgoing: owner-admins admins-archive: "|/usr1/apps/majordomo/wrapper archive -f /usr1/apps/majordomo/archives/admins/admins -m -a" owner-admins-archive: owner-admins admins-request: "|/usr1/apps/majordomo/wrapper request-answer admins" owner-admins-request: owner-admins ##################### ### /etc/majordomo.cf ##################### # $whereami -- What machine am I running on? $whereami = "remora.ssp.nmfs.gov"; # $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 = "/usr1/apps/majordomo"; } # $listdir -- Where are the mailing lists? $listdir = "/usr1/apps/majordomo/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 = "/usr1/apps/majordomo/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 = "/usr1/apps/majordomo/archives"; $filedir_suffix = ""; # 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. This should be defined as # a series of root anchored directory paths as will be used as prefixes # to the file names specified to the archive2.pl script. @archive_dirs = ( "/usr1/apps/majordomo/archives/admins" ); # Set this to 1 if you want to use the experimental mechanism for allowing # / in user names. People with lots of X.400 addresses on their lists or # HP mail whatever may want to set this. However use it at your own risk. $analyze_slash_in_address = 0; # # these tune the experimental matching that is done for addresses with / in # them. If you haven't turned on the experimental analyze_slash_in_address # they are ignored. See the source for full explanation of these variables. # # if set to 1 ignore the requirement that addresses have an @ sign in the # address component after the last /. $no_x400at=0; # if set to 1 do not look for "/c=" and "/ad=" or "/am=" in the address. # X.400 seems to require these components. $no_true_x400=0; 1; # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1.2.2 1995/01/07 17:35:03 rouilj Exp $ -- Karen Brown Foster Unix System Administrator Fisheries Statitics Division National Marine Fisheries Service (301) 713-2316 VOICE (301) 713-4137 FAX kbfoster@oyster.ssp.nmfs.gov From majordomo-users-owner Mon Sep 25 15:55:42 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA01539 for majordomo-users-outgoing; Mon, 25 Sep 1995 15:35:32 -0700 Received: from haydn.metsci.com (metsci.com [149.94.0.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id PAA01524 for ; Mon, 25 Sep 1995 15:35:25 -0700 Message-Id: <199509252236.SAA00581@haydn.metsci.com> Date: Mon, 25 Sep 1995 18:34:51 -0400 From: trinh@metsci.com (Stephanie Trinh) To: majordomo-users@greatcircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is this true that a closed and unmodified list would allow anyone including those who are NOT members of the list to post to a list and distribute the message to everyone on the list and archive it ??? I don't think this is acceptable, can anyone verify this ?? or have I done something wrong during setup ? Is there a way to allow members only to post to a closed list ? Thanks, Stephanie Trinh - trinh@metsci.com From majordomo-users-owner Mon Sep 25 19:23:48 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id TAA10830 for majordomo-users-outgoing; Mon, 25 Sep 1995 19:21:23 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id TAA10823 for ; Mon, 25 Sep 1995 19:21:20 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA09696; Mon, 25 Sep 1995 22:19:40 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509260219.AA09696@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: From headers lost by some mailers? X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Mon, 25 Sep 1995 22:19:27 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I finally went on-line with majordomo today for the owl-list, which has close to 500 subscribers. One thing I have notices is that some people do not get all the headers. In my mail from the list (since I am subscribed also) I get headers like this: Reply-To: wiseb@cs.rpi.edu From: someone-on-the-list@somwhere Sender: owl-list-owner@netlab.cs.rpi.edu Subject: ..some topic... Since owl-list-owner points to me wiseb@cs.rpi.edu, apparently sendmail? or resend? inserts the reply-to header? Just curious... The other thing I noticed is that some people don't get the oringal >From header so they do not know who the original poster was -- all they can tell is that it came from me, they get wiseb@cs.rpi.edu, instead. Is there anything to do about this? Anyone else notice that? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Mon Sep 25 21:52:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id VAA13749 for majordomo-users-outgoing; Mon, 25 Sep 1995 21:48:15 -0700 Received: from haydn.metsci.com (metsci.com [149.94.0.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id PAA10593 for ; Fri, 22 Sep 1995 15:42:38 -0700 Message-Id: <199509222244.SAA27112@haydn.metsci.com> Date: Fri, 22 Sep 1995 18:42:53 -0400 From: trinh@metsci.com (Stephanie Trinh) To: majordomo-users@greatcircle.com Subject: automatically subscribe List_B members to List_A ?? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Does anyone know how to automatically subscribe members from one list to another ? For instance, I have a big list, let's call it List_A and a smaller list (or a subset of List_A) called List_B. Is there a way, either automatically or as an option presented to the List_B subscribers, to subscribe List_B members to List_A but NOT vice versa ? Thanks, Stephanie From majordomo-users-owner Mon Sep 25 22:22:23 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA14447 for majordomo-users-outgoing; Mon, 25 Sep 1995 22:11:40 -0700 Received: (mcb@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA14227; Mon, 25 Sep 1995 22:06:18 -0700 Message-Id: <199509260506.WAA14227@miles.greatcircle.com> From: mcb@greatcircle.com (Michael C. Berch) Date: Mon, 25 Sep 1995 22:06:17 +0000 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: majordomo-users Subject: ADMIN: list restored from crash Cc: brent Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The majordomo-users list has been restored from a backup made at approximately 1300 PST on 21 September. The list was truncated to zero by a system problem (probably a full file system). New subscribers to the list since then (about 19 addresses) have been merged in, but some unsubscribes undoubtedly went astray; if you tried to unsubscribe but get this message, please unsubscribe again. The messages from that period (8 of them) that you missed will be posted in a separate message following this one. We apologize for the inconvenience. -- Michael C. Berch Postmaster and List Manager, Great Circle Associates mcb@greatcircle.com From majordomo-users-owner Mon Sep 25 22:30:04 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA14799 for majordomo-users-outgoing; Mon, 25 Sep 1995 22:22:43 -0700 Received: (mcb@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA14680 for majordomo-users; Mon, 25 Sep 1995 22:19:46 -0700 Message-Id: <199509260519.WAA14680@miles.greatcircle.com> From: mcb@greatcircle.com (Michael C. Berch) Date: Mon, 25 Sep 1995 22:19:46 +0000 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: majordomo-users Subject: ADMIN: "missing" messages while list was truncated Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk From: kbfoster@remora.ssp.nmfs.gov (Karen Brown Foster) Date: Mon, 25 Sep 1995 11:16:22 -0400 To: majordomo-users@greatcircle.com Subject: Majordomo Hello users: I am new to the mailing list and hope that someone can be of assistance. I have successfully installed majordomo on an SGI workstation running IRIX 5.3. I am running Majordomo version 1.93 and Perl version 4.036. I have enclosed a copy of my alias file. What I have done is to create a test listname called admins. I have been running tests with this list to see if everything is working correctly. I am able to send help requests to the list, subscribe users to the list, etc. The problem I am having is that when someone sends mail to the list, the mail goes to everyone in the list, but if anyone in the list replies to the mail, the reply goes back to the sender of the mail instead of to everyone that is a member of the list. I would like the reply to be seen by everyone in the list. Can anyone see or tell me what I'm doing wrong? Thanks in advance. Karen Brown Foster ###### aliases file ###### owner-owner: postmaster # # Majordomo # majordomo: "|/usr1/apps/majordomo/wrapper majordomo" owner-majordomo: kbfoster, nobody majordom: owner-majordomo #Needed "just in case" for Majordomo version 1.9x: Majordomo-Owner: owner-majordomo # admins mailing list owner-admins: kbfoster, nobody admins: "|/usr1/apps/majordomo/wrapper resend -l admins -h remora.ssp.nmfs.gov admins-outgoing" admins-approval: owner-admins admins-outgoing: :include:/usr1/apps/majordomo/lists/admins, admins-archive owner-admins-outgoing: owner-admins admins-archive: "|/usr1/apps/majordomo/wrapper archive -f /usr1/apps/majordomo/archives/admins/admins -m -a" owner-admins-archive: owner-admins admins-request: "|/usr1/apps/majordomo/wrapper request-answer admins" owner-admins-request: owner-admins -- Karen Brown Foster Unix System Administrator Fisheries Statitics Division National Marine Fisheries Service (301) 713-2316 VOICE (301) 713-4137 FAX kbfoster@oyster.ssp.nmfs.gov ----- From: Andrew Cormack Reply-To: Andrew Cormack To: majordomo-users@greatcircle.com Subject: Majordomo and OSF/1 I've heard a lot of reports about problems with MD on OSF systems, but nothing specific about what actions cause what problems. Since our current MD server (an ultrix box) is being pensioned off in favour of a new DECAlpha, I'd be interested in any detailed reports of what problems have been found in what areas of the system's operation. This should help me to decide whether my own system is working or not. I'll post a summry of any replies to the list, so please feel free to e-mail me direct as . Thanks, Andrew -- +-----------------------------------------------------------------+ | Andrew Cormack | email: cormack@cardiff.ac.uk | | Information Systems Support, | snail: 40/41 Park Place, Cardiff | | postmaster and webmaster | CF1 3BB | | University of Wales, Cardiff | | +-----------------------------------------------------------------+ ----- From: "Denis Dumouchel" To: Majordomo-users@GreatCircle.COM Date: Mon, 25 Sep 1995 13:02:10 +0000 Subject: Double messages Reply-to: denis@jrv.qc.ca Hello, I administer a mailing list , that my Internet provider runs with Majordomo, but we have the following bug: Everyone who is subscribe to the list receives the messages in double, except the messages that come from my provisers server. He uses "Linux" and "send mail". He tried to set the software properly using the FAQ, but the problem remains. He work arround the queue process interval (-q flag), and the interval between queue checkpoints (OC flag in sendmail.cf) . Does anyone know of the good settings he could use to solve the problem, or does someone knows another solution to the problem? thanks, Denis =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Denis Dumouchel Dunham, Quebec,Ca. denis@jrv.qc.ca http://www.ornitho.com/ "Les oiseaux de l'autoroute electronique" =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ----- From: kbfoster@remora.ssp.nmfs.gov (Karen Brown Foster) Message-Id: <9509251704.ZM1078@remora.ssp.nmfs.gov> Date: Mon, 25 Sep 1995 17:04:48 -0400 To: majordomo-users@greatcircle.com Subject: Reply to listname Hello: I sent this message out earlier and didn't receive a reply, so I'm sending it again. I am running majordomo 1.93 on an SGI workstation running IRIX 5.3. I am running Perl version 4.036. I have majordomo set up and running but I have one problem. When I send mail to my listname (admins), it gets sent to everyone in the list. However, when someone replies to the message, the reply gets sent to the send of the mail and not to everyone in the list which is how I would like it to work. Is this even possible with majordomo? I am including a copy of my /etc/aliases file, but perhaps the problem may be one of the parameters in the majordomo.cf file. I will also include it. Any help that anyone can provide would very much be appreciated. Thanks in advance. Karen Brown Foster ############### ## /etc/aliases ############### owner-owner: postmaster # # Majordomo # majordomo: "|/usr1/apps/majordomo/wrapper majordomo" owner-majordomo: kbfoster, nobody majordom: owner-majordomo #Needed "just in case" for Majordomo version 1.9x: Majordomo-Owner: owner-majordomo # admins mailing list owner-admins: kbfoster, nobody admins: "|/usr1/apps/majordomo/wrapper resend -l admins -h remora.ssp.nmfs.gov admins-outgoing" admins-approval: owner-admins admins-outgoing: :include:/usr1/apps/majordomo/lists/admins, admins-archive owner-admins-outgoing: owner-admins admins-archive: "|/usr1/apps/majordomo/wrapper archive -f /usr1/apps/majordomo/archives/admins/admins -m -a" owner-admins-archive: owner-admins admins-request: "|/usr1/apps/majordomo/wrapper request-answer admins" owner-admins-request: owner-admins ##################### ### /etc/majordomo.cf ##################### # $whereami -- What machine am I running on? $whereami = "remora.ssp.nmfs.gov"; # $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 = "/usr1/apps/majordomo"; } # $listdir -- Where are the mailing lists? $listdir = "/usr1/apps/majordomo/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 = "/usr1/apps/majordomo/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 = "/usr1/apps/majordomo/archives"; $filedir_suffix = ""; # 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. This should be defined as # a series of root anchored directory paths as will be used as prefixes # to the file names specified to the archive2.pl script. @archive_dirs = ( "/usr1/apps/majordomo/archives/admins" ); # Set this to 1 if you want to use the experimental mechanism for allowing # / in user names. People with lots of X.400 addresses on their lists or # HP mail whatever may want to set this. However use it at your own risk. $analyze_slash_in_address = 0; # # these tune the experimental matching that is done for addresses with / in # them. If you haven't turned on the experimental analyze_slash_in_address # they are ignored. See the source for full explanation of these variables. # # if set to 1 ignore the requirement that addresses have an @ sign in the # address component after the last /. $no_x400at=0; # if set to 1 do not look for "/c=" and "/ad=" or "/am=" in the address. # X.400 seems to require these components. $no_true_x400=0; 1; # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1.2.2 1995/01/07 17:35:03 rouilj Exp $ -- Karen Brown Foster Unix System Administrator Fisheries Statitics Division National Marine Fisheries Service (301) 713-2316 VOICE (301) 713-4137 FAX kbfoster@oyster.ssp.nmfs.gov ----- From: trinh@metsci.com (Stephanie Trinh) Date: Mon, 25 Sep 1995 18:34:51 -0400 To: majordomo-users@greatcircle.com Is this true that a closed and unmodified list would allow anyone including those who are NOT members of the list to post to a list and distribute the message to everyone on the list and archive it ??? I don't think this is acceptable, can anyone verify this ?? or have I done something wrong during setup ? Is there a way to allow members only to post to a closed list ? Thanks, Stephanie Trinh - trinh@metsci.com ----- From: Bowden Wise To: majordomo-users@greatcircle.com Subject: From headers lost by some mailers? Date: Mon, 25 Sep 1995 22:19:27 -0400 I finally went on-line with majordomo today for the owl-list, which has close to 500 subscribers. One thing I have notices is that some people do not get all the headers. In my mail from the list (since I am subscribed also) I get headers like this: Reply-To: wiseb@cs.rpi.edu From: someone-on-the-list@somwhere Sender: owl-list-owner@netlab.cs.rpi.edu Subject: ..some topic... Since owl-list-owner points to me wiseb@cs.rpi.edu, apparently sendmail? or resend? inserts the reply-to header? Just curious... The other thing I noticed is that some people don't get the oringal >From header so they do not know who the original poster was -- all they can tell is that it came from me, they get wiseb@cs.rpi.edu, instead. Is there anything to do about this? Anyone else notice that? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ ----- From: trinh@metsci.com (Stephanie Trinh) To: majordomo-users@greatcircle.com Subject: automatically subscribe List_B members to List_A ?? Does anyone know how to automatically subscribe members from one list to another ? For instance, I have a big list, let's call it List_A and a smaller list (or a subset of List_A) called List_B. Is there a way, either automatically or as an option presented to the List_B subscribers, to subscribe List_B members to List_A but NOT vice versa ? Thanks, Stephanie ----- END ----- From majordomo-users-owner Tue Sep 26 01:01:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id AAA16712 for majordomo-users-outgoing; Tue, 26 Sep 1995 00:59:39 -0700 Received: from ncb.gov.sg (ncb.gov.sg [160.96.4.100]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id AAA16705 for ; Tue, 26 Sep 1995 00:59:28 -0700 Received: by ncb.gov.sg (4.1/SMI-4.1) id AA25361; Tue, 26 Sep 95 15:53:59 SST Date: Tue, 26 Sep 1995 15:53:59 +0800 (SST) From: Lam Lai San Reply-To: Lam Lai San Subject: Another victim! To: majordomo-users@greatcircle.com Cc: laisan@ncb.gov.sg In-Reply-To: <199509260608.GAA10636@regent.ncb.gov.sg> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I must say I never have such a hard time getting other programs to work than majordomo. Ooops I'm not trying to be offensive but to let the rest knows that I need all the help I can get to solve the errors here. They've been haunting me for weeks. All I ask for is to implement digest and archive and I've been gnashing my teeth to get these up. I'm running majordomo 1.93 on irix 5.3. Please see the error message returned by sendmail below, followed by my aliases file. And now here's my explanation for not being able to figure out what has gone wrong. 1. The @archive_dirs is clearly defined in majordomo.cf but majordomo insists it's not and aborted the execution. Do I have to "makefile" after ammendments are done to the majordomo.cf? But majordomo is written in perl and will read in majordomo.cf during execution. I'm helpless 2. I've no idea why the digest program fails. I need your advice. Any slightest idea to the cause of the error would be much appreciated. Many thanks. --Lai San LAM ---------------------------- On Tue, 26 Sep 1995, Mail Delivery Subsystem wrote: > The original message was received at Tue, 26 Sep 1995 06:08:36 GMT > from majordomo@localhost > > ----- The following addresses had delivery problems ----- > "|/usr/users/majordomo/maj/wrapper archive2.pl -a -m -f /usr/users/majordomo/maj/lists/sg-nic.archive" (unrecoverable error) > (expanded from: sg-nic-outgoing) > "|/usr/users/majordomo/maj/wrapper digest -r -C -l sg-nic-digest sg-nic-digest" (unrecoverable error) > (expanded from: sg-nic-outgoing) > > ----- Transcript of session follows ----- > @archive_dirs not defined in majordomo.cf! Aborting. > > ABORT @archive_dirs not defined in majordomo.cf! Aborting. > 554 "|/usr/users/majordomo/maj/wrapper archive2.pl -a -m -f /usr/users/majordomo/maj/lists/sg-nic.archive"... unknown mailer error 2 > Undefined subroutine "main'abort" called at /usr/users/majordomo/maj/digest line 300. > 554 "|/usr/users/majordomo/maj/wrapper digest -r -C -l sg-nic-digest sg-nic-digest"... unknown mailer error 2 > > ----- Message header follows ----- > Received: by www.ncb.gov.sg (940816.SGI.8.6.9/940406.SGI.AUTO) > for sg-nic-outgoing id GAA10463; Tue, 26 Sep 1995 06:08:36 GMT > Return-Path: > Received: from ncb.gov.sg by www.ncb.gov.sg via SMTP (940816.SGI.8.6.9/940406.SGI.AUTO) > for id PAA10458; Tue, 26 Sep 1995 15:08:26 +0900 > Received: by ncb.gov.sg (4.1/SMI-4.1) > id AA22030; Tue, 26 Sep 95 15:08:17 SST > Date: Tue, 26 Sep 1995 15:08:16 +0800 (SST) > From: Lam Lai San > To: sg-nic@www.ncb.gov.sg > Message-Id: > Mime-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII > Sender: owner-sg-nic@www.ncb.gov.sg > Precedence: bulk > > ----- Message body suppressed ----- --------------------------- THE ALIASES FILE majordomo: "|/usr/users/majordomo/maj/wrapper majordomo" owner-majordomo:laisan@ncb.gov.sg majordomo-owner:laisan@ncb.gov.sg owner-sg-nic: laisan@ncb.gov.sg sg-nic-approval: laisan@ncb.gov.sg owner-sg-nic-digest: owner-sg-nic sg-nic-digest-approval: sg-nic-approval sg-nic: "|/usr/users/majordomo/maj/wrapper resend -l sg-nic -h www.ncb.gov.sg sg-nic-outgoing" sg-nic-digest: sg-nic owner-sg-nic-outgoing: owner-sg-nic sg-nic-outgoing: :include:/usr/users/majordomo/maj/lists/sg-nic,"|/usr/users/majordomo/maj/wrapper digest -r -C -l sg-nic-digest sg-nic-digest","|/usr/users/majordomo/maj/wrapper archive2.pl -a -m -f /usr/users/majordomo/maj/lists/sg-nic.archive" owner-sg-nic-request: owner-sg-nic sg-nic-request: "|/usr/users/majordomo/maj/wrapper majordomo -l sg-nic" owner-sg-nic-digest-request: owner-sg-nic-digest sg-nic-digest-request: "|/usr/users/majordomo/maj/wrapper majordomo -l sg-nic-digest" From majordomo-users-owner Tue Sep 26 03:22:53 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id DAA20271 for majordomo-users-outgoing; Tue, 26 Sep 1995 03:12:31 -0700 Received: from faxe (ns.tip.net [192.36.73.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id DAA20264 for ; Tue, 26 Sep 1995 03:12:28 -0700 From: tom@hbl.se Received: from bahnhof.se (root@sunny.bahnhof.se [193.44.91.1]) by faxe (8.7.Beta.2/8.7.Beta.2) with SMTP id LAA18540 for ; Tue, 26 Sep 1995 11:08:30 +0100 (MET) Received: from [193.44.91.12] (dude) by bahnhof.se (5.0/SMI-SVR4) id AA09852; Tue, 26 Sep 1995 11:10:22 GMT Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 26 Sep 1995 11:10:39 +0100 To: majordomo-users@greatcircle.com Subject: Hidden who? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, It is possible to hide the results of the command even for subscribers of a list? I Want to set up a list for price list updates. Subscribers should not be able to figure out who else got the price info. Not with a simple command anyway. I run majordomo 1.92 Perl 4 Solaris 2.3 /tom From majordomo-users-owner Tue Sep 26 04:52:23 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id EAA22062 for majordomo-users-outgoing; Tue, 26 Sep 1995 04:40:21 -0700 Received: from kingcrab (kingcrab.nrl.navy.mil [132.250.32.72]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id EAA22055 for ; Tue, 26 Sep 1995 04:40:18 -0700 Received: from [132.250.32.90] (c4i-ether-mac11.nrl.navy.mil) by kingcrab (5.x/SMI-SVR4) id AA04602; Tue, 26 Sep 1995 07:38:25 -0400 X-Sender: will@kingcrab.nrl.navy.mil Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 26 Sep 1995 07:38:40 -0400 To: majordomo-users@greatcircle.com From: Michael_Will@kingcrab.nrl.navy.mil (Michael Will) Subject: aliases ??? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have set up two list where I have set the following aliases up: owner-ListA : myname@site ListA-approval: sysadm@site The sysadm@site is an alias that contains the addresses of the three other administrators who can approve the subscriptions. One of the three is also my E-mail. The problem is that all subscriptions notices and requests go to the other two administrators (their names are included on the sysadm alias) but not to me?? Really weird. Anyone have any ideas? Michael -- Michael Will | Voice: (202) 767-0955 Naval Research Lab Code 8140 | Fax: (202) 404-8520 4555 Overlook Ave. SW | E-mail: will@kingcrab.nrl.navy.mil Washington, DC 20375 Key fingerprint = F03F 87F2 4264 8540 AA19 92E9 6F03 D219 From majordomo-users-owner Tue Sep 26 05:00:03 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id EAA21980 for majordomo-users-outgoing; Tue, 26 Sep 1995 04:34:25 -0700 Received: from sparc (Sparc.uccb.ns.ca [142.12.4.50]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id EAA21973 for ; Tue, 26 Sep 1995 04:34:19 -0700 Received: by sparc (5.0/SMI-SVR4) id AA06202; Tue, 26 Sep 1995 08:33:43 +0400 Date: Tue, 26 Sep 1995 08:33:43 -0300 (ADT) From: Steve MacLeod Subject: ANNOUNCE: WAIS Searching on Majordomo Archives To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 903 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi All It's not often that I get to contribute something to this forum but, I think you might be interested to check out a WAIS search ability I implemented on one of our servers. The URL is http://w3.uccb.ns.ca/majordomo I have yet to put some pretty graphics and such on the page but, there is a help file for all the options with WAIS searching. A big benefit is that the word you specify can be anywhere in the document ... When you select the WAIS search page you will see a number of databases to search ... I use the Clarion Programming language, you will see those archives there too. Check It Out! Best Regards 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 From majordomo-users-owner Tue Sep 26 06:00:07 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id FAA24211 for majordomo-users-outgoing; Tue, 26 Sep 1995 05:55:03 -0700 Received: from europe.std.com (europe.std.com [192.74.137.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id FAA24198 for ; Tue, 26 Sep 1995 05:54:57 -0700 Received: from world.std.com by europe.std.com (8.6.12/Spike-8-1.0) id IAA16355; Tue, 26 Sep 1995 08:53:19 -0400 Received: by world.std.com (5.65c/Spike-2.0) id AA05937; Tue, 26 Sep 1995 08:53:18 -0400 Date: Tue, 26 Sep 1995 08:53:18 -0400 From: eliz@world.std.com (Elizabeth Lear) Message-Id: <199509261253.AA05937@world.std.com> To: majordomo-users@greatcircle.com Subject: Re: Hidden who? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk command even for command anyway. Sure, you need the 'anonymous' patch. Here's a copy of the original. I've been using this without a problem in 1.93 since Feb. ...eliz *Date: Wed, 16 Nov 1994 23:48:37 -0500 *From: Spider Boardman I've seen a number of such requests come and go on this list, so here's what I did. I added two new config options, "anon_who" and "anon_which". Their purpose is to implement per-list privacy options. Even list members can't do a "who list" if "anon_who" is set, and "which other-address" commands skip lists with "anon_which" set. In order that the list owner can still see who's subscribed, I also made it possible to approve a who request. This part is not clean, since the existing "approve" code wants more arguments than a "who" command normally needs. Thus, you wind up needing to do "approve PASSWORD who LIST ." or somesuch to get the desired result. It's that wart on this that has kept me from posting this earlier. Anyway, appended are the relevant sections of diffs for my setup. Your line numbers will almost certainly vary, since I have other changes besides. --spider -- Spider Boardman spider@orb.nashua.nh.us speaking only for myself ...!decvax!orb!spider ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <350.785047715.2@orb.nashua.nh.us> Content-Description: diffs for anon_which and anon_who *** /local/src/majordomo-1.92/config_parse.pl.ORIG Mon May 9 14:34:06 1994 --- /local/src/majordomo-1.92/config_parse.pl Fri Oct 14 02:25:37 1994 *************** *** 77,82 **** --- 78,85 ---- # otherwise the value is the default value for the keyword. # if the value starts with #!, the rest of the value is eval'ed %known_keys = ( + 'anon_who', 'no', # anonymous list disallowing who + 'anon_which', 'no', # anonymous list disallowing which other 'private_get', 'yes', # must be on list to use get 'private_index', 'no', # must be on list to use index 'private_who', 'no', # must be on list to use who *************** *** 157,162 **** --- 162,173 ---- "If set to yes, then the requestor must be on the mailing list to use the info command.", + 'anon_who', + "If set to yes, then 'who ' commands will not be allowed.", + + 'anon_which', + "If set to yes, then 'which ' commands will skip this list.", + 'advertise', "If the requestor email address matches one of these regexps, then the list will be listed *************** *** 340,345 **** --- 359,366 ---- 'private_info', 'majordomo', 'private_who', 'majordomo', 'private_which', 'majordomo', + 'anon_which', 'majordomo', + 'anon_who', 'majordomo', 'advertise', 'majordomo', 'noadvertise', 'majordomo', 'description', 'majordomo', *************** *** 386,391 **** --- 409,416 ---- 'private_info', 'grab_bool', 'private_who', 'grab_bool', 'private_which', 'grab_bool', + 'anon_which', 'grab_bool', + 'anon_who', 'grab_bool', 'advertise', 'grab_regexp_array', 'noadvertise', 'grab_regexp_array', 'description', 'grab_string', *************** *** 609,614 **** --- 636,645 ---- sub handle_flag_files { local($listdir, $list) = @_; + if ( -e "$listdir/$list.anon") { + $main'config_opts{$list,"anon_which"} = 1; + $main'config_opts{$list,"anon_who"} = 1; } + if ( -e "$listdir/$list.private") { $main'config_opts{$list,"private_get"} = 1; $main'config_opts{$list,"private_index"} = 1; *************** *** 928,934 **** sub grab_float { local($num)=@_; ! return($num) if $num =~ /^[0-9][0-9]*\.[0-9]+$/; return($num) if $num =~ /^$/; push(@errors, "$num is not a floating point number at line $.\n"); return ""; --- 959,965 ---- sub grab_float { local($num)=@_; ! return($num) if $num =~ /^\d+(\.\d+)?$|^\.\d+$/; return($num) if $num =~ /^$/; push(@errors, "$num is not a floating point number at line $.\n"); return ""; *************** *** 944,950 **** "integer |$num| contains a ^A at line $.\n"), next if $re =~ /\001/; ! push(@return_array, $num) if $num =~ /^[1-9][0-9]*\.[0-9]+$/; push(@return_array, $num) if $num =~ /^$/; push(@local_errors, "$num is not an floating point number at line $.\n"); --- 975,981 ---- "integer |$num| contains a ^A at line $.\n"), next if $re =~ /\001/; ! push(@return_array, $num) if $num =~ /^\d+(\.\d+)?$|^\.\d+$/; push(@return_array, $num) if $num =~ /^$/; push(@local_errors, "$num is not an floating point number at line $.\n"); *** /local/src/majordomo-1.92/majordomo.ORIG Sun May 8 17:07:37 1994 --- /local/src/majordomo-1.92/majordomo Sun Sep 25 02:34:32 1994 *************** *** 379,384 **** --- 379,387 ---- } elsif ($cmd eq "unsubscribe") { &log("approve PASSWORD unsubscribe $clean_list $subscriber"); &do_unsubscribe($clean_list, $subscriber); + } elsif ($cmd eq "who") { + &log("approve PASSWORD who $clean_list"); + &do_who($clean_list); } else { # you can only approve "subscribe" and "unsubscribe" &squawk("approve: invalid command '$cmd'"); *************** *** 454,460 **** --- 457,473 ---- # get configuration info &get_config($listdir, $_) if !&cf_ck_bool($_, '', 1); + if ( &cf_ck_bool($list,"anon_which") + && ! $approved + && (! &is_list_member($reply_to, $listdir, $list)) + && (! &addr_match($reply_to, $subscriber, + (&cf_ck_bool($clean_list,"mungedomain") + ? 2 : undef)))) { + # skip anonymous lists if requestor isn't a member or is snooping + # on someone else + next; + } if ( &cf_ck_bool($list,"private_which") && (! &is_list_member($reply_to, $listdir, $list))) { # skip private lists that the requestor isn't a member of next; *************** *** 503,509 **** --- 517,529 ---- &get_config($listdir, $clean_list) if !&cf_ck_bool($clean_list, '', 1); + if ( &cf_ck_bool($clean_list,"anon_who") && ! $approved) { + print REPLY "**** List '$clean_list' is an anonymous list.\n"; + print REPLY "**** The 'who' command is not allowed for this list.\n" ; + return 0; + } if ( &cf_ck_bool($clean_list,"private_who") + && ! $approved && ! &is_list_member($reply_to, $listdir, $clean_list)) { print REPLY "**** List '$clean_list' is a private list.\n"; print REPLY "**** Only members of the list can do a 'who'.\n"; (end) From majordomo-users-owner Tue Sep 26 08:52:45 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA00414 for majordomo-users-outgoing; Tue, 26 Sep 1995 08:42:02 -0700 Received: from cs.rpi.edu (cs.rpi.edu [128.213.1.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA00407 for ; Tue, 26 Sep 1995 08:41:59 -0700 Received: from colossus.cs.rpi.edu by cs.rpi.edu (5.67a/1.4-RPI-CS-Dept) id AA25263; Tue, 26 Sep 1995 11:40:20 -0400 (wiseb from colossus.cs.rpi.edu) Message-Id: <199509261540.AA25263@cs.rpi.edu> To: majordomo-users@greatcircle.com Subject: Digest and Sender field X-Mailer: MH 6.7.1 (exmh 1.5.1) Date: Tue, 26 Sep 1995 11:40:04 -0400 From: Bowden Wise Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have noticed that digests have a From header specifying the owner as the address. My normal list has a Sender header. Is there a way to get the digest to also use have a Sender field also? -------------------------------------------------------------------- G. Bowden Wise Computer Science Dept, Rensselaer Polytechnic Inst, Troy, NY 12180 Email: wiseb@cs.rpi.edu WWW: http://www.cs.rpi.edu/~wiseb/ From majordomo-users-owner Tue Sep 26 09:00:08 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA29956 for majordomo-users-outgoing; Tue, 26 Sep 1995 08:31:50 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA29949 for ; Tue, 26 Sep 1995 08:31:45 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA18643 for majordomo-users@greatcircle.com; Tue, 26 Sep 95 08:30:04 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA12012; Tue, 26 Sep 95 08:30:02 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA11131 for majordomo-users@greatcircle.com; Tue, 26 Sep 95 08:30:00 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA11476; Tue, 26 Sep 95 10:29:58 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA18178; Tue, 26 Sep 1995 10:29:56 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509261529.AA18178@miaow.sps.mot.com> Subject: Re: Another victim! To: laisan@ncb.gov.sg Date: Tue, 26 Sep 1995 10:29:56 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Lam Lai San" at Sep 26, 95 03:53:59 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2426 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Lam Lai San writes: ] > > 1. The @archive_dirs is clearly defined in majordomo.cf but majordomo > insists it's not and aborted the execution. Do I have to "makefile" > after ammendments are done to the majordomo.cf? But majordomo is written > in perl and will read in majordomo.cf during execution. I'm helpless [...] [ alias reformatted for readability: it doesn't have to all be on 1 line ] > sg-nic-outgoing: :include:/usr/users/majordomo/maj/lists/sg-nic, > "|/usr/users/majordomo/maj/wrapper digest -r -C -l sg-nic-digest > sg-nic-digest", > "|/usr/users/majordomo/maj/wrapper archive2.pl -a -m > -f /usr/users/majordomo/maj/lists/sg-nic.archive" No, you don't have to rebuild after changing majordomo.cf. Other than the path for the archive -f parameter is probably wrong, all I can tell you is that we'll need to see your settings for $filedir, $fieldir_suffix, and @archive_dirs to see how they match up with your alias. Another Mj user recently had this same problem and when he fixed his alias -f parameter, it started working. The -f parameter should be a base file name for archive2.pl to append the various archive designators onto, not a directory where the files are kept, e.g.: -f /usr/users/majordomo/maj/lists/sg-nic.archive/sg-nic from which it will create, e.g.: /usr/users/majordomo/maj/lists/sg-nic.archive/sg-nic.9509 /usr/users/majordomo/maj/lists/sg-nic.archive/sg-nic.9510 /usr/users/majordomo/maj/lists/sg-nic.archive/sg-nic.9511 Note that /usr/users/majordomo/maj/lists/sg-nic.archive must exist and be writable by Mj. > 2. I've no idea why the digest program fails. I need your advice. [...] > > Undefined subroutine "main'abort" called at /usr/users/majordomo/maj/digest line 300. Digest is totally confused about Perl packages (or I am :-) and is beyond hope. Assuming we're talking about unmodified Mj 1.93, it shouldn't reach line 300 unless it didn't find your -C option. It calls abort because it didn't find a -c option to initialize the file handle variable. It can't find main'abort because it never executed the code to "require" the file that defines it (only done if -C is present; require is done at run time, not compile time). I have no idea why it didn't find the -C. What version of Perl are you using? -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Tue Sep 26 10:53:24 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA07173 for majordomo-users-outgoing; Tue, 26 Sep 1995 10:43:43 -0700 Received: from nd.edu (nd.edu [129.74.250.101]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA07166 for ; Tue, 26 Sep 1995 10:43:40 -0700 Received: from bach.helios.nd.edu by nd.edu with SMTP (PP); Tue, 26 Sep 1995 12:41:41 -0500 Date: Tue, 26 Sep 1995 12:41:40 -0500 (EST) From: Mike Buening To: David Wolfe cc: laisan@ncb.gov.sg, "Majordomo user's mailing list" Subject: Re: Another victim! In-Reply-To: <9509261529.AA18178@miaow.sps.mot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Tue, 26 Sep 1995, Dave Wolfe wrote: > [ Lam Lai San writes: ] > > 2. I've no idea why the digest program fails. I need your advice. > [...] > > > Undefined subroutine "main'abort" called at /usr/users/majordomo/maj/digest line 300. > > Digest is totally confused about Perl packages (or I am :-) and is > beyond hope. Assuming we're talking about unmodified Mj 1.93, it > shouldn't reach line 300 unless it didn't find your -C option. It calls > abort because it didn't find a -c option to initialize the file handle > variable. It can't find main'abort because it never executed the code to > "require" the file that defines it (only done if -C is present; require > is done at run time, not compile time). I have no idea why it didn't > find the -C. What version of Perl are you using? > > -- > Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 > Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 > In my case it was as simply as not having sendmail send capital letters through. Therefore my digest always failed. It wasn't until some kind soul pointed out to me that you need to include the flag for passing upper case letters in the MProg portion of your sendmail.cf. Just a thought. Mike From majordomo-users-owner Tue Sep 26 11:00:01 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id KAA07643 for majordomo-users-outgoing; Tue, 26 Sep 1995 10:56:09 -0700 Received: from post3.inre.asu.edu (post3.INRE.ASU.EDU [129.219.10.148]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id KAA07635 for ; Tue, 26 Sep 1995 10:56:06 -0700 Received: from x1.asu.edu by asu.edu (PMDF V4.3-10 #7723) id <01HVQ9P3H88W8X3P14@asu.edu>; Tue, 26 Sep 1995 10:54:13 -0700 (MST) Received: from earthvision (earthvision.ASU.EDU [129.219.14.15]) by x1.asu.edu (8.6.12/8.6.12) with ESMTP id KAA06972 for <@x1.asu.edu:majordomo-users@greatcircle.com>; Tue, 26 Sep 1995 10:53:55 -0700 Received: by earthvision (940816.SGI.8.6.9/940406.SGI) for majordomo-users@greatcircle.com id KAA03290; Tue, 26 Sep 1995 10:57:09 -0700 Date: Tue, 26 Sep 1995 10:57:09 -0700 From: Jason Vagner Subject: Compiling wrapper problem on Irix 5.3 To: majordomo-users@greatcircle.com Message-id: <9509261057.ZM3288@earthvision> MIME-version: 1.0 X-Mailer: Z-Mail (3.2.2 10apr95 MediaMail) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've been having problems getting the wrapper to compile on an SGI. What exactly is necessary to get the wrapper simply to compile? Allow me to step through the installation steps from the README and please tell me if I'm not understanding this (I'm trying to understand what depends on what): >choose and/or create a uid and gid for this to run under I have chosen these. >create appropriate directories ($homedir and $listdir), with >appropriate user, group, and permissions (775) Are these necessary for the wrapper to compile? >edit the "Makefile" to set W_BIN and the environment for "wrapper"; >don't forget to make the changes for POSIX, if necessary Is the W_BIN the only one necessary? I'm compiling this on an IRIX 5.3, and I'll include the error message I get at the end of this post. Does the compile rely on majordomo.cf? >compile and install the perl code and man pages. >("make", then "make install") This is where I get this error message: ---- cc -DBIN=\"/usr/people/aidsauth/tools/majordomo-1.93\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/usr/people/aidsauth/tools/majordomo-1.93\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF=\"MAJORDOMO_CF=/usr/people/aidsauth/tools/majordomo-1.93/majordomo.cf\" -DPOSIX_UID=1115 -DPOSIX_GID=40 -DSETGROUP -o wrapper wrapper.c cfe: Error: wrapper.c, line 65: Unacceptable operand of == or != if (strchr(argv[1], '/') != (char *) 0 ) { ------------------------------^ cfe: Warning 712: wrapper.c, line 99: illegal combination of pointer and integer char setgroups_used = "setgroups_was_included"; ---------^ *** Error code 1 (bu21) ---- And I admit I can't make much of this. I noticed in the last few days that a few people are running theirs on Irix 5.3 (which is what I have), but I thought perhaps a public post might be the best way to elicit feedback. Thanks in advance!! Jason -- Email jason@asu.edu Finger jason@earthvision.asu.edu Key BF 6B EE 1C 03 E8 06 31 48 02 75 87 07 46 66 6D WWW http://earthvision.asu.edu/aidsauthority From majordomo-users-owner Tue Sep 26 15:24:54 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA18957 for majordomo-users-outgoing; Tue, 26 Sep 1995 15:05:54 -0700 Received: from pht.com (exodus.pht.com [198.60.59.99]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA18950 for ; Tue, 26 Sep 1995 15:05:51 -0700 Received: by pht.com id AA11915 (5.67b/IDA-1.5 for majordomo-users@greatcircle.com); Tue, 26 Sep 1995 14:18:22 -0600 Date: Tue, 26 Sep 1995 14:18:13 -0600 (MDT) From: Brad Midgley To: majordomo-users@greatcircle.com Cc: Brad Midgley Subject: security... Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I would like to fix a couple things which look like security problems. For one, I don't want users to get the lists of those subscribed to our lists. call me crazy. tha other isn't necessarily a majordomo thing, more a sendmail thing, but I'd like to force senders to our lists to be restricted to local users at our site. majordomo-1.93, latest sendmail, linux. thanks. oddly, I didn't see anything in the faq about the former problem... brad@pht.com From majordomo-users-owner Tue Sep 26 15:25:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA18800 for majordomo-users-outgoing; Tue, 26 Sep 1995 15:02:27 -0700 Received: from pht.com (exodus.pht.com [198.60.59.99]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id PAA18785 for ; Tue, 26 Sep 1995 15:02:21 -0700 Received: by pht.com id AA11850 (5.67b/IDA-1.5 for majordomo-users@greatcircle.com); Tue, 26 Sep 1995 14:14:54 -0600 Date: Tue, 26 Sep 1995 14:14:49 -0600 (MDT) From: Brad Midgley To: majordomo-users@greatcircle.com Cc: Brad Midgley Subject: majordomo on redhat commercial 2.0 linux? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk hi majordomo nuts, I tried to "upgrade" our linux server from an old old linux distribution to the new redhat 2.0 elf linux. Everything else (except popmail, but that's another story) works, but majordomo, whether it's invoked to process a simple "lists" or to subscribe someone, forks off once and then the two processes slurp up ram and exercise the cpu like mad until they're finally killed. I tried it with perl5 as well as perl4.036 with exactly the same results. I'm using majordomo-1.93. The reason this all seems odd is because the exact same setup worked on the old linux system (save the fact that the wrapper is now an ELF binary). Any ideas anyone? thanks, brad@pht.com From majordomo-users-owner Tue Sep 26 17:54:01 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id RAA25270 for majordomo-users-outgoing; Tue, 26 Sep 1995 17:33:38 -0700 Received: from sparc (Sparc.uccb.ns.ca [142.12.4.50]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id RAA25262 for ; Tue, 26 Sep 1995 17:33:25 -0700 Received: by sparc (5.0/SMI-SVR4) id AA19901; Tue, 26 Sep 1995 21:31:26 +0400 Date: Tue, 26 Sep 1995 21:31:26 -0300 (ADT) From: Steve MacLeod Subject: Re: majordomo on redhat commercial 2.0 linux? To: Brad Midgley Cc: majordomo-users@greatcircle.com, Brad Midgley In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 1419 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Tue, 26 Sep 1995, Brad Midgley wrote: > hi majordomo nuts, > > I tried to "upgrade" our linux server from an old old linux distribution > to the new redhat 2.0 elf linux. Everything else (except popmail, but > that's another story) works, but majordomo, whether it's invoked to > process a simple "lists" or to subscribe someone, forks off once and then > the two processes slurp up ram and exercise the cpu like mad until they're > finally killed. > > I tried it with perl5 as well as perl4.036 with exactly the same results. > I'm using majordomo-1.93. Hi Brad This was discussed a short while ago, I think the permissions on the lockfile were the culprit. If you have a web browser you can look up that discussion on the new handy dandy WAIS search engine I just setup on the majordomo archives. Whew, after that shameless plug the darn thing better work http://w3.uccb.ns.ca/majordomo Check It Out! Best Regards 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 > > The reason this all seems odd is because the exact same setup worked on > the old linux system (save the fact that the wrapper is now an ELF binary). > > Any ideas anyone? > > thanks, > brad@pht.com > From majordomo-users-owner Tue Sep 26 18:30:06 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id SAA28017 for majordomo-users-outgoing; Tue, 26 Sep 1995 18:23:40 -0700 Received: from j51.com (j51.com [199.224.7.51]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id SAA28007 for ; Tue, 26 Sep 1995 18:23:37 -0700 Received: from pm4.j51.com (pm4.j51.com [199.224.7.228]) by j51.com (8.6.12/8.6.9) with SMTP id BAA27967 for ; Wed, 27 Sep 1995 01:22:24 GMT Message-Id: <199509270122.BAA27967@j51.com> X-Sender: genesis@j51.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 26 Sep 1995 21:13:25 -0400 To: majordomo-users@greatcircle.com From: Project Genesis Subject: Yet ANOTHER victim... Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm having a problem with Digesting pretty similar (but not identical) to that posted by Lam Lai San. The following is returned by the primary list... ----- The following addresses had delivery problems ----- "|/usr/local/lib/majordomo-1.93/wrapper digest -r -C -l forum-digest forum-digest-outgoing" (unrecoverable error) (expanded from: forum-outgoing) ----- Transcript of session follows ----- open of temp file $listdir/digest/forum-digest/shlock.18947 failed No such file or directory ABORT open of temp file $listdir/digest/forum-digest/shlock.18947 failed No such file or directory at majordomo.pl line 209. 554 "|/usr/local/lib/majordomo-1.93/wrapper digest -r -C -l forum-digest forum-digest-outgoing"... unknown mailer error 2 ----- Message header follows ----- etc.... What more info do you need to figure this out? Messages to the list or personal email would be MUCH appreciated! Ken Menken From majordomo-users-owner Tue Sep 26 19:23:58 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id TAA00962 for majordomo-users-outgoing; Tue, 26 Sep 1995 19:13:29 -0700 Received: from orange.metron.com (metron.com [204.182.31.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id TAA00953 for ; Tue, 26 Sep 1995 19:13:25 -0700 Received: (from lou@localhost) by orange.metron.com (8.6.10/8.6.10) id TAA29134 for majordomo-users@GreatCircle.COM; Tue, 26 Sep 1995 19:11:46 -0700 From: Lou Katz Message-Id: <199509270211.TAA29134@orange.metron.com> Subject: Re: Yet ANOTHER victim... To: majordomo-users@GreatCircle.COM Date: Tue, 26 Sep 1995 19:11:46 -0700 (PDT) In-Reply-To: <199509270122.BAA27967@j51.com> from "Project Genesis" at Sep 26, 95 09:13:25 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 141 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have gotten approximately the same messages, and cannot get digests to work, also. -- -=[Lou Katz]=- +[1] (510) 530 8870 From majordomo-users-owner Wed Sep 27 06:22:51 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA27593 for majordomo-users-outgoing; Wed, 27 Sep 1995 06:11:57 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA27578 for ; Wed, 27 Sep 1995 06:11:52 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA20219 for majordomo-users@greatcircle.com; Wed, 27 Sep 95 06:10:04 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA05570; Wed, 27 Sep 95 06:10:02 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA01120 for majordomo-users@greatcircle.com; Wed, 27 Sep 95 06:10:01 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA16791; Wed, 27 Sep 95 08:09:59 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA17111; Wed, 27 Sep 1995 08:09:58 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509271309.AA17111@miaow.sps.mot.com> Subject: Re: Compiling wrapper problem on Irix 5.3 To: jason@asu.edu (Jason Vagner) Date: Wed, 27 Sep 1995 08:09:57 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <9509261057.ZM3288@earthvision> from "Jason Vagner" at Sep 26, 95 10:57:09 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2443 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Jason Vagner writes: ] > > I've been having problems getting the wrapper to compile on an SGI. What > exactly is necessary to get the wrapper simply to compile? Allow me to step > through the installation steps from the README and please tell me if I'm not > understanding this (I'm trying to understand what depends on what): [...] > >create appropriate directories ($homedir and $listdir), with > >appropriate user, group, and permissions (775) > > Are these necessary for the wrapper to compile? No, but since $homedir is W_BIN and you have to set W_BIN before running make, why not create them so you don't forget. > >edit the "Makefile" to set W_BIN and the environment for "wrapper"; > >don't forget to make the changes for POSIX, if necessary > > Is the W_BIN the only one necessary? I'm compiling this on an IRIX 5.3, and > I'll include the error message I get at the end of this post. Does the compile > rely on majordomo.cf? W_BIN and either W_USER and W_GROUP (for BSD) or W_UID and W_GID (for POSIX). Be sure that the other option (BSD or POSIX) settings are commented out so that only one is defined. If you're asking if the compile relies on majordomo.cf existing, then no, only the definition in the makefile of *where* it will exist counts. > >compile and install the perl code and man pages. > >("make", then "make install") > > This is where I get this error message: > ---- > cc -DBIN=\"/usr/people/aidsauth/tools/majordomo-1.93\" > -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" > -DHOME=\"HOME=/usr/people/aidsauth/tools/majordomo-1.93\" > -DSHELL=\"SHELL=/bin/csh\" > -DMAJORDOMO_CF=\"MAJORDOMO_CF=/usr/people/aidsauth/tools/majordomo-1.93/majordomo.cf\" > -DPOSIX_UID=1115 -DPOSIX_GID=40 -DSETGROUP -o wrapper wrapper.c > cfe: Error: wrapper.c, line 65: Unacceptable operand of == or != > if (strchr(argv[1], '/') != (char *) 0 ) { > ------------------------------^ > cfe: Warning 712: wrapper.c, line 99: illegal combination of pointer and > integer > char setgroups_used = "setgroups_was_included"; > ---------^ > *** Error code 1 (bu21) Get the latest FAQ from ftp.Greatcircle.com and read it. There are some fixes that must be applied to wrapper.c. In your case, add #include and declare setgroups_used as char* instead of just char. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 27 08:26:38 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id IAA01757 for majordomo-users-outgoing; Wed, 27 Sep 1995 08:00:30 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id IAA01750 for ; Wed, 27 Sep 1995 08:00:26 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AB10868 for majordomo-users@greatcircle.com; Wed, 27 Sep 95 07:58:47 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA09061; Wed, 27 Sep 95 07:58:46 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA09818 for majordomo-users@greatcircle.com; Wed, 27 Sep 95 07:58:44 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA17959; Wed, 27 Sep 95 09:58:43 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA19816; Wed, 27 Sep 1995 09:58:41 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509271458.AA19816@miaow.sps.mot.com> Subject: Re: Yet ANOTHER victim... To: genesis@j51.com (Project Genesis) Date: Wed, 27 Sep 1995 09:58:41 -0500 (CDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <199509270122.BAA27967@j51.com> from "Project Genesis" at Sep 26, 95 09:13:25 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1254 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Project Genesis writes: ] > > I'm having a problem with Digesting pretty similar (but not identical) to > that posted by Lam Lai San. The following is returned by the primary list... > > ----- The following addresses had delivery problems ----- > "|/usr/local/lib/majordomo-1.93/wrapper digest -r -C -l forum-digest > forum-digest-outgoing" (unrecoverable error) > (expanded from: forum-outgoing) > > ----- Transcript of session follows ----- > open of temp file $listdir/digest/forum-digest/shlock.18947 failed > No such file or directory > ABORT open of temp file $listdir/digest/forum-digest/shlock.18947 failed > No such file or directory at majordomo.pl line 209. > 554 "|/usr/local/lib/majordomo-1.93/wrapper digest -r -C -l forum-digest > forum-digest-outgoing"... unknown mailer error 2 Why isn't $listdir expanded? You've used a Perl variable in a parameter that doesn't get eval'ed by perl. Note that only majordomo.cf is interpreted as Perl code. The list config file (and digest config file?) are just parsed by Mj and allow very limited substitution, none of which is to be Perl code. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Wed Sep 27 09:30:26 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA03588 for majordomo-users-outgoing; Wed, 27 Sep 1995 09:01:07 -0700 Received: from krypton.netropolis.net (krypton.netropolis.net [204.176.47.5]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA03581 for ; Wed, 27 Sep 1995 09:01:04 -0700 Received: from krypton.netropolis.net (krypton.netropolis.net [204.176.47.5]) by krypton.netropolis.net (8.6.5/8.6.5) with SMTP id KAA23271 for ; Wed, 27 Sep 1995 10:59:04 GMT Date: Wed, 27 Sep 1995 10:59:03 +0000 (GMT) From: Robert Hill To: majordomo-users@greatcircle.com Subject: Returned mail: unknown mailer error 139 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="KAA22865.812198445/krypton.netropolis.net" Content-ID: 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. Send mail to mime@docserver.cac.washington.edu for more info. --KAA22865.812198445/krypton.netropolis.net Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: I am trying to set up a mailling list and when I send a subscribe message, I get the following message: ---------- Forwarded message ---------- Date: Wed, 27 Sep 1995 10:40:45 GMT From: Mail Delivery Subsystem To: rob@krypton.netropolis.net Subject: Returned mail: unknown mailer error 139 The original message was received at Wed, 27 Sep 1995 10:40:43 GMT from pig@localhost ----- The following addresses had delivery problems ----- "|/usr/local/majordomo/majordomo" (unrecoverable error) (expanded from: majordomo@netropolis.net) ----- Transcript of session follows ----- Memory fault 554 "|/usr/local/majordomo/majordomo"... unknown mailer error 139 ----- Original message follows ----- I've tried numerous things to fix this but it laughs at me. Any help will be appreciated. rob@netropolis.net --KAA22865.812198445/krypton.netropolis.net Content-Type: MESSAGE/RFC822 Content-ID: Return-Path: pig Received: from localhost (pig@localhost) by krypton.netropolis.net (8.6.5/8.6.5) id KAA22863 for majordomo@netropolis.net; Wed, 27 Sep 1995 10:40:43 GMT Date: Wed, 27 Sep 1995 10:40:43 GMT From: Piggy Pig Message-Id: <199509271040.KAA22863@krypton.netropolis.net> To: majordomo@netropolis.net subscribe hswhtcoop --KAA22865.812198445/krypton.netropolis.net-- From majordomo-users-owner Wed Sep 27 09:39:37 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA04532 for majordomo-users-outgoing; Wed, 27 Sep 1995 09:27:27 -0700 Received: from apollo.COSC.GOV (apollo.COSC.GOV [198.94.103.34]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA04516; Wed, 27 Sep 1995 09:27:15 -0700 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.11/8.6.9) id JAA06453; Wed, 27 Sep 1995 09:24:24 -0700 Date: Wed, 27 Sep 1995 09:24:22 -0700 (PDT) From: -Vince- To: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Subject: majordomo Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi everyone, I'm trying to setup majordomo so any posts to the list will go to the digest which goes out once a day and I am using Crontab to do it. Any ideas what I am doing wrong? Here is my Crontab entry: 6 0 * * * /usr/home/majordomo/digest -m -c /usr/home/majordomo/lists/gus-general-digest.config 6 0 * * * /usr/home/majordomo/digest -m -c /usr/home/majordomo/lists/gus-music-digest.config 6 0 * * * /usr/home/majordomo/digest -m -c /usr/home/majordomo/lists/gus-sdk-digest.config and here's my alias file: # # gus-general mailing list # gus-general-owner: vince gus-general-approval: vince gus-general: "|/usr/home/majordomo/wrapper resend -l gus-general -h apollo.COSC.GOV gus-general-outgoing,nobody" gus-general-outgoing: "|/usr/local/bin/bulk_mailer -m owner-gus-general@apollo.COSC.GOV /usr/home/majordomo/lists/gus-general","|/usr/home/majordomo/wrapper digest -r -C -l gus-general-digest gus-general-digest-outgoing,nobody" #gus-general-outgoing: :include:/usr/home/majordomo/lists/gus-general,"|/usr/home/majordomo/wrapper digest -r -C -l gus-general-digest gus-general-digest-outgoing,nobody" gus-general-archive: /usr/home/majordomo/archive/gus-general gus-general-request: "|/usr/home/majordomo/wrapper majordomo -l gus-general" owner-gus-general: gus-general-owner owner-gus-general-archive: gus-general-owner owner-gus-general-outgoing: gus-general-owner owner-gus-general-owner: gus-general-owner owner-gus-general-request: gus-general-owner # # and gus-general digest # gus-general-digest-owner: vince gus-general-digest-approval: vince gus-general-digest: gus-general #gus-general-digest-outgoing: :include:/usr/home/majordomo/lists/gus-general-digest gus-general-digest-outgoing: "|/usr/local/bin/bulk_mailer -m owner-gus-general-digest@apollo.COSC.GOV /usr/home/majordomo/lists/gus-general-digest" gus-general-digest-request: "|/usr/home/majordomo/wrapper majordomo -l gus-general-digest" owner-gus-general-digest: gus-general-digest-owner owner-gus-general-digest-outgoing: gus-general-digest-owner owner-gus-general-digest-owner: gus-general-digest-owner owner-gus-general-digest-request: gus-general-digest-owner Thanks for your help! Cheers, -Vince- vince@apollo.COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! From majordomo-users-owner Wed Sep 27 12:26:13 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA10934 for majordomo-users-outgoing; Wed, 27 Sep 1995 12:00:38 -0700 Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id MAA10919; Wed, 27 Sep 1995 12:00:21 -0700 Received: from cthulhu.engr.sgi.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id LAA03930; Wed, 27 Sep 1995 11:54:28 -0700 Received: from lunch.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id LAA28868; Wed, 27 Sep 1995 11:25:29 -0700 Received: by lunch.engr.sgi.com (950511.SGI.8.6.12.PATCH526/940406.SGI.AUTO) id LAA08511; Wed, 27 Sep 1995 11:25:28 -0700 From: pdc@lunch.engr.sgi.com (Paul Close) Message-Id: <199509271825.LAA08511@lunch.engr.sgi.com> Subject: Re: majordomo To: vince@apollo.COSC.GOV (-Vince-) Date: Wed, 27 Sep 1995 11:25:25 -0700 (PDT) Cc: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com In-Reply-To: from "-Vince-" at Sep 27, 95 09:24:22 am X-Mailer: ELM [version 2.5 PL0a7] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1929 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > I'm trying to setup majordomo so any posts to the list will go to the > digest which goes out once a day and I am using Crontab to do it. Any > ideas what I am doing wrong? You didn't say what wasn't working. I assume messages are queuing up all right, it's just that a digest isn't sent out daily? > Here is my Crontab entry: > > 6 0 * * * /usr/home/majordomo/digest -m -c /usr/home/majordomo/lists/gus-general-digest.config > gus-general-outgoing: "|/usr/local/bin/bulk_mailer -m owner-gus-general@apollo.COSC.GOV /usr/home/majordomo/lists/gus-general","|/usr/home/majordomo/wrapper digest -r -C -l gus-general-digest gus-general-digest-outgoing,nobody" The config files are different formats. The digest program either takes a -C, in which case it reads the new config file format that all lists use, or for backwards compatibility you can feed it an old-style config file (specific to digest) using -c. For example, a -C config file looks like: # admin_passwd [word] (list.admin) # (Default is specified in the file .passwd) The password # for handling administrative tasks on the list. admin_passwd = list.admin # administrivia [bool] (yes) # Look for administrative requests (e.g. subscribe/unsubscribe) and # forward them to the list maintainer instead of the list. administrivia = yes ... while a -c config file looks like: #name that appears in subject line and digest banner NAME=Firewalls Digest #address reader send to to reply to the entire list REPLY-TO=Firewalls@GreatCircle.COM ... Not the same at all! I'd suggest changing your cron entry to: 6 0 * * * /usr/home/majordomo/wrapper digest -m -C -l gus-general-digest gus-general-digest-outgoing,nobody That should solve your problem. -- Paul Close pdc@sgi.com http://reality.sgi.com/employees/pdc/ No fate but what we make From majordomo-users-owner Wed Sep 27 13:23:00 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA13883 for majordomo-users-outgoing; Wed, 27 Sep 1995 13:18:55 -0700 Received: from krypton.netropolis.net (krypton.netropolis.net [204.176.47.5]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id NAA13876 for ; Wed, 27 Sep 1995 13:18:52 -0700 Received: from krypton.netropolis.net (krypton.netropolis.net [204.176.47.5]) by krypton.netropolis.net (8.6.5/8.6.5) with SMTP id PAA02573 for ; Wed, 27 Sep 1995 15:16:29 GMT Date: Wed, 27 Sep 1995 15:16:29 +0000 (GMT) From: Robert Hill To: majordomo-users@greatcircle.com Subject: Returned mail: unknown mailer error 139 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="PAA02214.812214251/krypton.netropolis.net" Content-ID: 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. Send mail to mime@docserver.cac.washington.edu for more info. --PAA02214.812214251/krypton.netropolis.net Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: I've set up the wrapper and everything and I am still getting this error. I changed the path of $mailer in my majordomo.cf file but no luck. I've downloaded the faq and I'm going through it but I see nothing concerning my problem just yet. rob@netropolis.net ---------- Forwarded message ---------- Date: Wed, 27 Sep 1995 15:04:11 GMT From: Mail Delivery Subsystem To: rob@krypton.netropolis.net Subject: Returned mail: unknown mailer error 139 The original message was received at Wed, 27 Sep 1995 15:04:06 GMT from pig@localhost ----- The following addresses had delivery problems ----- "|/usr/users/listserv/wrapper majordomo" (unrecoverable error) (expanded from: majordomo@netropolis.net) ----- Transcript of session follows ----- Memory fault - core dumped 554 "|/usr/users/listserv/wrapper majordomo"... unknown mailer error 139 ----- Original message follows ----- --PAA02214.812214251/krypton.netropolis.net Content-Type: MESSAGE/RFC822 Content-ID: Return-Path: pig Received: from localhost (pig@localhost) by krypton.netropolis.net (8.6.5/8.6.5) id PAA02212 for majordomo@netropolis.net; Wed, 27 Sep 1995 15:04:06 GMT Date: Wed, 27 Sep 1995 15:04:06 GMT From: Piggy Pig Message-Id: <199509271504.PAA02212@krypton.netropolis.net> To: majordomo@netropolis.net subscribe hswhtcoop --PAA02214.812214251/krypton.netropolis.net-- From majordomo-users-owner Wed Sep 27 15:08:54 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id OAA16783 for majordomo-users-outgoing; Wed, 27 Sep 1995 14:38:37 -0700 Received: from apollo.COSC.GOV (apollo.COSC.GOV [198.94.103.34]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id OAA16751; Wed, 27 Sep 1995 14:38:17 -0700 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.11/8.6.9) id OAA08971; Wed, 27 Sep 1995 14:35:38 -0700 Date: Wed, 27 Sep 1995 14:35:38 -0700 (PDT) From: -Vince- To: Paul Close cc: majordomo-users@GreatCircle.COM, majordomo-workers@GreatCircle.COM Subject: Re: majordomo In-Reply-To: <199509271825.LAA08511@lunch.engr.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Wed, 27 Sep 1995, Paul Close wrote: > > I'm trying to setup majordomo so any posts to the list will go to the > > digest which goes out once a day and I am using Crontab to do it. Any > > ideas what I am doing wrong? > > You didn't say what wasn't working. I assume messages are queuing up all > right, it's just that a digest isn't sent out daily? I'm not sure if the messages are queuing up all right since nothing is in the directories in both listname.archive and /usr/home/digests/listname-digest > > Here is my Crontab entry: > > > > 6 0 * * * /usr/home/majordomo/digest -m -c /usr/home/majordomo/lists/gus-general-digest.config > > > gus-general-outgoing: "|/usr/local/bin/bulk_mailer -m owner-gus-general@apollo.COSC.GOV /usr/home/majordomo/lists/gus-general","|/usr/home/majordomo/wrapper digest -r -C -l gus-general-digest gus-general-digest-outgoing,nobody" > > The config files are different formats. The digest program either takes > a -C, in which case it reads the new config file format that all lists > use, or for backwards compatibility you can feed it an old-style config > file (specific to digest) using -c. I'm using the 1.93 config files so it's supposed to be a -C > For example, a -C config file looks like: > > # admin_passwd [word] (list.admin) > # (Default is specified in the file .passwd) The password > # for handling administrative tasks on the list. > admin_passwd = list.admin > > # administrivia [bool] (yes) > # Look for administrative requests (e.g. subscribe/unsubscribe) and > # forward them to the list maintainer instead of the list. > administrivia = yes > > ... > > while a -c config file looks like: > > #name that appears in subject line and digest banner > NAME=Firewalls Digest > > #address reader send to to reply to the entire list > REPLY-TO=Firewalls@GreatCircle.COM > > ... > > Not the same at all! Yep, I have to agree with that.... The new one is alot better. > I'd suggest changing your cron entry to: > > 6 0 * * * /usr/home/majordomo/wrapper digest -m -C -l gus-general-digest gus-general-digest-outgoing,nobody > > That should solve your problem. Hopefully it does but does my /etc/aliases look correct if people mailing to gus-general which is the mailing list version will queue and have cron actually sending out the daily digest with the above cron entry for gus-general-digest? Here is my /etc/aliases: # # gus-general mailing list # gus-general-owner: vince gus-general-approval: vince gus-general: "|/usr/home/majordomo/wrapper resend -l gus-general -h apollo.COSC.GOV gus-general-outgoing,nobody" gus-general-outgoing: "|/usr/local/bin/bulk_mailer -m owner-gus-general@apollo.COSC.GOV /usr/home/majordomo/lists/gus-general","|/usr/home/majordomo/wrapper digest -r -C -l gus-general-digest gus-general-digest-outgoing,nobody" #gus-general-outgoing: :include:/usr/home/majordomo/lists/gus-general,"|/usr/home/majordomo/wrapper digest -r -C -l gus-general-digest gus-general-digest-outgoing,nobody" gus-general-archive: /usr/home/majordomo/archive/gus-general gus-general-request: "|/usr/home/majordomo/wrapper majordomo -l gus-general" owner-gus-general: gus-general-owner owner-gus-general-archive: gus-general-owner owner-gus-general-outgoing: gus-general-owner owner-gus-general-owner: gus-general-owner owner-gus-general-request: gus-general-owner # # and gus-general digest # gus-general-digest-owner: vince gus-general-digest-approval: vince gus-general-digest: gus-general #gus-general-digest-outgoing: :include:/usr/home/majordomo/lists/gus-general-digest gus-general-digest-outgoing: "|/usr/local/bin/bulk_mailer -m owner-gus-general-digest@apollo.COSC.GOV /usr/home/majordomo/lists/gus-general-digest" gus-general-digest-request: "|/usr/home/majordomo/wrapper majordomo -l gus-general-digest" owner-gus-general-digest: gus-general-digest-owner owner-gus-general-digest-outgoing: gus-general-digest-owner owner-gus-general-digest-owner: gus-general-digest-owner owner-gus-general-digest-request: gus-general-digest-owner Cheers, -Vince- vince@apollo.COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From majordomo-users-owner Wed Sep 27 15:52:37 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id PAA18417 for majordomo-users-outgoing; Wed, 27 Sep 1995 15:39:44 -0700 Received: from isis.cu.soltec.com (isis.cu.soltec.com [204.248.64.21]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id PAA18410 for ; Wed, 27 Sep 1995 15:39:40 -0700 Received: from wolf.cu.soltec.com (wolf.cu.soltec.com [204.248.64.35]) by isis.cu.soltec.com (8.6.9/8.6.9) with SMTP id RAA10228 for ; Wed, 27 Sep 1995 17:38:18 -0500 Message-Id: <199509272238.RAA10228@isis.cu.soltec.com> X-Sender: erikw@mail.cu.soltec.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 27 Sep 1995 17:47:17 -0400 To: majordomo-users@greatcircle.com From: erikw@soltec.com (Erik Wolf) Subject: Unknown Mailer Error 139 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello, I am installing Majordomo 1.93 on a Sun SparcStation SLC running SunOS 4.1.3. When I am testing majordomo by sending requests to it (usually subscribing to a sample list), any mail I send gets returned with Unknown mailer error 139 and it tells me that the core dumped. I ran adb on the core file and the only thing it told me was the was a segmentation violation. Anybody ever seen this before? Thanks in advance. Erik Wolf (erikw@soltec.com) Systems Admin and Tech Support Sol Tec, Inc http://www.cu.soltec.com/ From majordomo-users-owner Thu Sep 28 00:27:15 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id AAA04150 for majordomo-users-outgoing; Thu, 28 Sep 1995 00:19:58 -0700 Received: from kingcrab (kingcrab.nrl.navy.mil [132.250.32.72]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id FAA24044 for ; Wed, 27 Sep 1995 05:09:21 -0700 Received: from [132.250.32.90] (c4i-ether-mac11.nrl.navy.mil) by kingcrab (5.x/SMI-SVR4) id AA13358; Wed, 27 Sep 1995 08:07:23 -0400 X-Sender: will@kingcrab.nrl.navy.mil Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 27 Sep 1995 08:07:40 -0400 To: majordomo-users@greatcircle.com From: Michael_Will@kingcrab.nrl.navy.mil (Michael Will) Subject: HELP! Aliases Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'll try this again. I have no idea why I am being filtered out via the aliases. I have set up two list where I have set the following aliases up: owner-ListA : myname@site ListA-approval: sysadm@site The sysadm@site is an alias that contains the addresses of the three other administrators who can approve the subscriptions. One of the three is also my E-mail. The problem is that all subscriptions notices and requests go to the other two administrators (their names are included on the sysadm alias) but not to me?? Really weird. Anyone have any ideas? Michael -- Michael Will | Voice: (202) 767-0955 Naval Research Lab Code 8140 | Fax: (202) 404-8520 4555 Overlook Ave. SW | E-mail: will@kingcrab.nrl.navy.mil Washington, DC 20375 Key fingerprint = F03F 87F2 4264 8540 AA19 92E9 6F03 D219 From majordomo-users-owner Thu Sep 28 00:30:00 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id AAA04185 for majordomo-users-outgoing; Thu, 28 Sep 1995 00:20:43 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id KAA06412 for ; Wed, 27 Sep 1995 10:09:41 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA13642 for majordomo-users@greatcircle.com; Wed, 27 Sep 95 10:08:00 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA12879; Wed, 27 Sep 95 10:07:57 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA22542 for majordomo-users@greatcircle.com; Wed, 27 Sep 95 10:07:55 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA19294; Wed, 27 Sep 95 12:07:53 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA19530; Wed, 27 Sep 1995 12:07:51 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509271707.AA19530@miaow.sps.mot.com> Subject: Re: Returned mail: unknown mailer error 139 (fwd) To: rob@krypton.netropolis.net (Robert Hill) Date: Wed, 27 Sep 1995 12:07:51 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "Robert Hill" at Sep 27, 95 10:59:03 am Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 874 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Robert Hill writes: ] > > I am trying to set up a mailling list and when I send a subscribe > message, I get the following message: > > ----- The following addresses had delivery problems ----- > "|/usr/local/majordomo/majordomo" (unrecoverable error) > (expanded from: majordomo@netropolis.net) > > ----- Transcript of session follows ----- > Memory fault > 554 "|/usr/local/majordomo/majordomo"... unknown mailer error 139 > > ----- Original message follows ----- > > I've tried numerous things to fix this but it laughs at me. And it should! :-) Set up your majordomo alias to invoke majordomo with wrapper (you did build and install wrapper, right?), e.g.: majordomo: "|/usr/local/majordomo/wrapper majordomo" -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Thu Sep 28 00:30:22 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id AAA04200 for majordomo-users-outgoing; Thu, 28 Sep 1995 00:20:54 -0700 Received: from ita.tip.net (peroni.ita.tip.net [194.20.0.111]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id LAA09366 for ; Wed, 27 Sep 1995 11:18:19 -0700 Received: from [194.20.0.55] ([194.20.0.55]) by ita.tip.net (8.7.Beta.2/8.7.Beta.2) with SMTP id TAA07490; Wed, 27 Sep 1995 19:15:41 +0100 (MET) Date: Wed, 27 Sep 1995 19:15:41 +0100 (MET) Message-Id: <199509271815.TAA07490@ita.tip.net> X-Authentication-Warning: peroni: Host [194.20.0.55] didn't use HELO protocol X-Sender: varoli@ita.tip.net X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Robert Hill , majordomo-users@GreatCircle.COM From: varoli@ita.tip.net (Varoli Marco) Subject: Re: Returned mail: unknown mailer error 139 (fwd) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 10:59 AM 9/27/95 +0000, Robert Hill wrote: >I am trying to set up a mailling list and when I send a subscribe >message, I get the following message: > > >---------- Forwarded message ---------- >Date: Wed, 27 Sep 1995 10:40:45 GMT >From: Mail Delivery Subsystem >To: rob@krypton.netropolis.net >Subject: Returned mail: unknown mailer error 139 > >The original message was received at Wed, 27 Sep 1995 10:40:43 GMT >from pig@localhost > > ----- The following addresses had delivery problems ----- >"|/usr/local/majordomo/majordomo" (unrecoverable error) > (expanded from: majordomo@netropolis.net) > > ----- Transcript of session follows ----- >Memory fault >554 "|/usr/local/majordomo/majordomo"... unknown mailer error 139 > > ----- Original message follows ----- > >I've tried numerous things to fix this but it laughs at me. >Any help will be appreciated. > >rob@netropolis.net >Return-Path: pig >Received: from localhost (pig@localhost) by krypton.netropolis.net (8.6.5/8.6.5) id KAA22863 for majordomo@netropolis.net; Wed, 27 Sep 1995 10:40:43 GMT >Date: Wed, 27 Sep 1995 10:40:43 GMT >From: Piggy Pig >Message-Id: <199509271040.KAA22863@krypton.netropolis.net> >To: majordomo@netropolis.net > >subscribe hswhtcoop > I had this error too! It occurs when Majordomo can't create lock files (to see this put the '-w' option in the #! perl statament in the file "majordomo") To fix this I changed the owner of directories of lists, digest, log etc... to "daemon" ( I compiled wrapper with the POSIX flag W_USER = daemon)and the group to "majordom" (the Majordomo user goup) Good lucky Marco Varoli _____________________________________________________________________________ /\ /\ / Marco Varoli / \ / \ / e-mail: varoli@ita.tip.net / \/ \ / s-mail: UniSource Italy / \/ Via Caldera, 21 \ /\ I-20153 Milano (Italy) \ / \ phone: +39 2 482421 \/ fax : +39 2 48242424 _____________________________________________________________________________ From majordomo-users-owner Thu Sep 28 00:38:39 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id AAA04164 for majordomo-users-outgoing; Thu, 28 Sep 1995 00:20:14 -0700 Received: from remora.ssp.nmfs.gov (remora.ssp.nmfs.gov [155.206.15.40]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id FAA24290 for ; Wed, 27 Sep 1995 05:17:20 -0700 Received: by remora.ssp.nmfs.gov (940816.SGI.8.6.9/940406.SGI) id IAA03580; Wed, 27 Sep 1995 08:15:19 -0400 From: kbfoster@remora.ssp.nmfs.gov (Karen Brown Foster) Message-Id: <9509270815.ZM3578@remora.ssp.nmfs.gov> Date: Wed, 27 Sep 1995 08:15:19 -0400 In-Reply-To: Jason Vagner "Compiling wrapper problem on Irix 5.3" (Sep 26, 10:57am) References: <9509261057.ZM3288@earthvision> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: Jason Vagner , majordomo-users@greatcircle.com Subject: Re: Compiling wrapper problem on Irix 5.3 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The following is a list of things that I had to do to get wrapper to compile on our Indigo 2 running IRIX 5.3. First of all I have majordomo 1.93 and Perl version 4.036. Here goes: (1) I created user majordom and group majordom (2) The home directory of majordom is /usr1/apps/majordomo Changes to Makefile (1) W_BIN is set to /usr1/apps/majordomo (2) I had to add /usr/bsd to the W_PATH statement to find the hostname command. (3) Make sure that W_UID and W_GID is equal to the uid and gid of your majordom user account. (4) In the wrapper section of the Makefile, add the -cckr flag to the $(CC) line, i.e., $(CC) $(WRAPPER_FLAGS) -cckr -o wrapper wrapper.c Changes to the wrapper.c file (1) Add the following line #include right after the line #include Changes to other Perl scripts (1) After compiling the programs, i.e. make wrapper as user majordom make install as majordom make install-archive2 as majordom (if you will be archiving) make install-wrapper as root Make change to request-answer script per instructions in the majordomo FAQ Set up a symbolic link between $HOME/majordomo.cf and /etc/majordomo.cf, i.e. ln -s /usr1/apps/majordomo/majordomo.cf /etc/majordomo.cf I found corrections to many of the problems that I was having in the majordomo FAQ. This is an excellent document!!!!! I will include copies of all of the important files and this should get you set up. ************************** ** /etc/aliases ************************** ######################################################################### # # Aliases in this file will NOT be expanded in the header from # Mail, but WILL be visible over networks or from /bin/mail. # # >>>>>>>>>> The program "newaliases" must be run after # >> NOTE >> this file is updated for any changes to # >>>>>>>>>> show through to sendmail. # ######################################################################### # start of common aliases--do not remove this line # Add the following alias to enable NIS aliases. If enabled, the # NIS database defines anything not defined in this file. #+:+ # Alias for mailer daemon MAILER-DAEMON:postmaster # send mail likely to be lost to the mail server rootcsh:postmaster rootsh:postmaster setup:postmaster powerdown:postmaster sysadm:postmaster daemon:postmaster bin:postmaster sys:postmaster adm:postmaster lp:postmaster uucpws:postmaster uucp:postmaster uucpadm:postmaster nuucp:postmaster rje:postmaster man:postmaster diag:postmaster tutor:postmaster demos:postmaster mexdemos:postmaster guest:postmaster games:postmaster auditor:postmaster dbadmin:postmaster rfindd:postmaster tour:postmaster 4Dgifts:postmaster # Following alias is required by RFC 822 # You should change 'root' in the first line below to the administrator # of this machine, and un-comment the following line. postmaster:root #root:postmaster # Aliases to handle mail to msgs and news nobody: /dev/null # end of common aliases--do not remove this line owner-owner: postmaster # # Majordomo # majordomo: "|/usr1/apps/majordomo/wrapper majordomo" owner-majordomo: kbfoster, nobody majordom: owner-majordomo #Needed "just in case" for Majordomo version 1.9x: #Majordomo-Owner: owner-majordomo ############################ # Test mailing list (admins) ############################ owner-admins: kbfoster, nobody admins: "|/usr1/apps/majordomo/wrapper resend -l admins -h remora.ssp.nmfs.gov admins-outgoing" admins-approval: owner-admins admins-outgoing: :include:/usr1/apps/majordomo/lists/admins, admins-archive owner-admins-outgoing: owner-admins admins-archive: "|/usr1/apps/majordomo/wrapper archive -f /usr1/apps/majordomo/archives/admins/admins -d -a" owner-admins-archive: owner-admins admins-request: "|/usr1/apps/majordomo/wrapper request-answer admins" owner-admins-request: owner-admins #################### # econ mailing list #################### owner-econ: Amy_Buss_Gautam@ssp.nmfs.gov, nobody econ: "|/usr1/apps/majordomo/wrapper resend -l econ -h remora.ssp.nmfs.gov econ-outgoing" econ-approval: owner-econ econ-outgoing: :include:/usr1/apps/majordomo/lists/econ, econ-archive owner-econ-outgoing: owner-econ econ-archive: "|/usr1/apps/majordomo/wrapper archive -f /usr1/apps/majordomo/archives/econ/econ -d -a" owner-econ-archive: owner-econ econ-request: "|/usr1/apps/majordomo/wrapper request-answer econ" owner-econ-request: owner-econ ********************* ** /etc/majordomo.cf ********************* # $whereami -- What machine am I running on? $whereami = "remora.ssp.nmfs.gov"; # $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 = "/usr1/apps/majordomo"; } # $listdir -- Where are the mailing lists? $listdir = "/usr1/apps/majordomo/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 = "/usr1/apps/majordomo/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 = "/usr1/apps/majordomo/archives"; $filedir_suffix = ""; # 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. This should be defined as # a series of root anchored directory paths as will be used as prefixes # to the file names specified to the archive2.pl script. @archive_dirs = ( "/usr1/apps/majordomo/archives/admins", "/usr1/apps/majordomo/archives/econ"); # Set this to 1 if you want to use the experimental mechanism for allowing # / in user names. People with lots of X.400 addresses on their lists or # HP mail whatever may want to set this. However use it at your own risk. $analyze_slash_in_address = 0; # # these tune the experimental matching that is done for addresses with / in # them. If you haven't turned on the experimental analyze_slash_in_address # they are ignored. See the source for full explanation of these variables. # # if set to 1 ignore the requirement that addresses have an @ sign in the # address component after the last /. $no_x400at=0; # if set to 1 do not look for "/c=" and "/ad=" or "/am=" in the address. # X.400 seems to require these components. $no_true_x400=0; 1; # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4.2.1.2.2 1995/01/07 17:35:03 rouilj Exp $ ************************************* ** ~majordom/majordomo-1.93/Makefile ************************************* # $Source: /sources/cvsrepos/majordomo/Makefile,v $ # $Revision: 1.21.2.2.2.8 $ # $Date: 1995/01/07 18:06:48 $ # $Author: rouilj $ # $State: Exp $ # # $Header: /sources/cvsrepos/majordomo/Makefile,v 1.21.2.2.2.8 1995/01/07 18:06:48 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=/usr1/apps/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:/usr/bsd W_HOME=${W_BIN} W_SHELL=/bin/ksh 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=majordom #W_CHOWN=${W_USER}.${W_GROUP} #W_CHMOD=6755 #WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ # -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ # -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" # If you're using a POSIX-compliant system, uncomment this set of parameters # and comment out the BSD settings above. # # W_UID = 1112 W_GID = 200 W_CHOWN=root W_CHMOD=4755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" \ -DPOSIX_UID=${W_UID} -DPOSIX_GID=${W_GID} -DSETGROUP # 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 test \ $(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 Makefile $(CC) ${WRAPPER_FLAGS} -cckr -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 VERSION=1.93 distribution: dist-clean mkdir majordomo-$(VERSION) mv * .??* majordomo-$(VERSION) || exit 0 rm -rf majordomo-$(VERSION)/CVS majordomo-$(VERSION)/*/CVS majordomo-$(VERSION)/*/*/CVS tar -cZvf majordomo-$(VERSION).tar.Z majordomo-$(VERSION) ********************************** ~majordom/majordomo-1.93/wrapper.c ********************************** /* * $Source: /sources/cvsrepos/majordomo/wrapper.c,v $ * $Revision: 1.1.1.1.8.2 $ * $Date: 1995/01/07 17:28:00 $ * $Author: rouilj $ * $State: Exp $ * * $Locker: $ * */ #ifndef lint static char rcs_header[] = "$Header: /sources/cvsrepos/majordomo/wrapper.c,v 1.1.1.1.8.2 1995/01/07 17:28:00 rouilj Exp $"; #endif #include #include #ifndef STRCHR # define STRCHR(s,c) strchr(s,c) #endif #ifndef BIN # define BIN "/usr/local/mail/majordomo" #endif #ifndef PATH # define PATH "PATH=/bin:/usr/bin:/usr/ucb" #endif #ifndef HOME # define HOME "HOME=/usr/local/mail/majordomo" #endif #ifndef SHELL # define SHELL "SHELL=/bin/csh" #endif char * new_env[] = { HOME, /* 0 */ PATH, /* 1 */ SHELL, /* 2 */ #ifdef MAJORDOMO_CF MAJORDOMO_CF, /* 3 */ #endif 0, /* possibly for USER or LOGNAME */ 0, /* possible for LOGNAME */ 0 }; main(argc, argv, env) int argc; char * argv[]; char * env[]; { char * prog; int e, i; if (argc < 2) { fprintf(stderr, "USAGE: %s program [ ...]\n", argv[0]); exit(1); } /* if the command contains a /, then don't allow it */ if (STRCHR(argv[1], '/') != (char *) NULL) { /* this error message is intentionally cryptic */ fprintf(stderr, "%s: error: insecure usage\n", argv[0]); exit(2); } if ((prog = (char *) malloc(strlen(BIN) + strlen(argv[1]) + 2)) == NULL) { fprintf(stderr, "%s: error: malloc failed\n", argv[0]); exit(3); } sprintf(prog, "%s/%s", BIN, argv[1]); /* copy the "USER=" and "LOGNAME=" envariables into the new environment, * if they exist. */ #ifdef MAJORDOMO_CF e = 4; /* the first unused slot in new_env[] */ #else e = 3; /* the first unused slot in new_env[] */ #endif for (i = 0 ; env[i] != NULL ; i++) { if ((strncmp(env[i], "USER=", 5) == 0) || (strncmp(env[i], "LOGNAME=", 8) == 0)) { new_env[e++] = env[i]; } } #if defined(SETGROUP) /* renounce any previous group memberships if we are running as root */ if (geteuid() == 0) { /* Should I exit if this test fails? */ char setgroups_used = "setgroups_was_included"; /* give strings a hint */ int groups[] = { POSIX_GID, 0 }; if (setgroups(1, groups) != 0) { extern int errno; fprintf(stderr, "%s: error setgroups failed errno %d", argv[0], errno); } } #endif #ifdef POSIX_GID setgid(POSIX_GID); #else setgid(getegid()); #endif #ifdef POSIX_UID setuid(POSIX_UID); #else setuid(geteuid()); #endif if ((getuid() != geteuid()) || (getgid() != getegid())) { fprintf(stderr, "%s: error: recompile with POSIX flags.\n", argv[0]); exit(4); } execve(prog, argv+1, new_env); /* the exec should never return */ perror(argv[1]); exit(5); } *********************************************************************** *** The following is a listing of the directory structure of majordomo *********************************************************************** total 1600 -rw-rw---- 1 majordom majordom 7377 Sep 26 17:40 Log drwxr-xr-x 2 majordom majordom 512 Sep 22 09:49 Tools -rwxr-xr-x 1 majordom majordom 7192 Sep 22 10:29 archive drwxrwxr-x 4 majordom majordom 512 Sep 26 11:00 archives drwxr-xr-x 2 majordom majordom 512 Sep 22 09:49 bin -rwxr-xr-x 1 majordom majordom 2615 Sep 22 09:49 bounce-remind -rw-rw-r-- 1 majordom majordom 43737 Sep 22 09:49 config_parse.pl -rwxr-xr-x 1 majordom majordom 11320 Sep 22 09:49 digest drwxr-xr-x 2 majordom majordom 512 Sep 26 17:40 lists -rwxr-xr-x 1 majordom majordom 42524 Sep 22 09:49 majordomo drwxr-xr-x 5 majordom majordom 512 Sep 22 09:48 majordomo-1.93 -rw-rw-r-- 1 majordom majordom 634880 Sep 22 09:31 majordomo-1.93.tar -rw-rw-r-- 1 majordom majordom 3743 Sep 26 11:03 majordomo.cf -rw-rw-r-- 1 majordom majordom 14327 Sep 22 09:49 majordomo.pl -rw-rw-r-- 1 majordom majordom 141 Sep 22 09:49 majordomo_version.pl drwxrwxr-x 4 majordom majordom 512 Sep 22 09:49 man -rwxr-xr-x 1 majordom majordom 2153 Sep 22 09:49 new-list -rw-r--r-- 1 majordom majordom 0 Sep 27 08:09 permits -rwxr-xr-x 1 majordom majordom 3205 Sep 22 13:16 request-answer -rwxr-xr-x 1 majordom majordom 12872 Sep 22 09:49 resend -rw-rw-r-- 1 majordom majordom 6183 Sep 22 09:49 shlock.pl -rwxr-xr-x 1 majordom majordom 131 Sep 22 09:49 test -rwsr-xr-x 1 root sys 18252 Sep 22 10:28 wrapper ./Tools: total 15 -rwxr-xr-x 1 majordom majordom 7192 Sep 22 09:49 archive2.pl ./archives: total 2 drwxrwxr-x 2 majordom majordom 512 Sep 26 17:32 admins drwxrwxr-x 2 majordom majordom 512 Sep 26 15:40 econ ./archives/admins: total 14 -rw-rw---- 1 majordom majordom 5860 Sep 26 15:00 admins.9509 -rw-rw---- 1 majordom majordom 944 Sep 26 17:32 admins.950926 ./archives/econ: total 7 -rw-rw---- 1 majordom majordom 3508 Sep 26 15:40 econ.9509 ./bin: total 22 -rwxr-xr-x 1 majordom majordom 6219 Sep 22 09:49 approve -rwxr-xr-x 1 majordom majordom 2887 Sep 22 09:49 bounce -rwxr-xr-x 1 majordom majordom 1424 Sep 22 09:49 medit ./lists: total 102 -rw-rw-r-- 1 majordom majordom 67 Sep 26 17:38 admins -rw-rw---- 1 majordom majordom 12060 Sep 26 17:19 admins.config -rw-rw-r-- 1 majordom majordom 36 Sep 25 14:00 admins.info -rw-rw---- 1 majordom majordom 12059 Sep 26 14:57 admins.old.config -rw-rw---- 1 majordom majordom 6 Sep 22 12:15 admins.passwd -rw-rw-r-- 1 majordom majordom 57 Sep 26 17:40 econ -rw-rw---- 1 majordom majordom 12049 Sep 26 15:06 econ.config -rw-rw-r-- 1 majordom majordom 60 Sep 26 09:38 econ.info -rw-rw---- 1 majordom majordom 12027 Sep 26 09:46 econ.old.config -rw-rw---- 1 majordom majordom 6 Sep 26 09:37 econ.passwd ./majordomo-1.93: total 584 -rw-r--r-- 1 majordom majordom 39173 Jan 10 1995 Changelog -rw-r--r-- 1 majordom majordom 12785 Apr 2 1994 Changes -rw-r--r-- 1 majordom majordom 4601 May 5 1994 Description drwxr-xr-x 3 majordom majordom 512 Sep 22 09:32 Doc -rw-r--r-- 1 majordom majordom 4631 Dec 26 1994 LICENSE -rw-r--r-- 1 majordom majordom 4460 Sep 22 09:48 Makefile -rw-r--r-- 1 majordom majordom 531 May 9 1994 Manifest -rw-r--r-- 1 majordom majordom 54569 Jan 7 1995 README -rwxr-xr-x 1 majordom majordom 6219 Jan 1 1995 approve -rwxr-xr-x 1 majordom majordom 2887 Dec 27 1994 bounce -rwxr-xr-x 1 majordom majordom 2615 Dec 26 1994 bounce-remind -rw-r--r-- 1 majordom majordom 43737 Jan 7 1995 config_parse.pl drwxr-xr-x 2 majordom majordom 512 Sep 22 09:32 contrib drwxr-xr-x 2 majordom majordom 512 Sep 22 09:32 digest -rwxr-xr-x 1 majordom majordom 42524 Jan 4 1995 majordomo -rw-r--r-- 1 majordom majordom 14327 Jan 7 1995 majordomo.pl -rw-r--r-- 1 majordom majordom 141 Dec 26 1994 majordomo_version.pl -rwxr-xr-x 1 majordom majordom 1424 Dec 26 1994 medit -rwxr-xr-x 1 majordom majordom 2153 Jan 7 1995 new-list -rwxr-xr-x 1 majordom majordom 3024 Dec 26 1994 request-answer -rwxr-xr-x 1 majordom majordom 12872 Jan 7 1995 resend -rw-r--r-- 1 majordom majordom 3742 Sep 3 1993 resend.README -rw-r--r-- 1 majordom majordom 2087 May 8 1994 sample.aliases -rw-r--r-- 1 majordom majordom 3697 Jan 7 1995 sample.cf -rw-r--r-- 1 majordom majordom 6183 Dec 31 1994 shlock.pl -rwxr-xr-x 1 majordom majordom 131 Dec 26 1994 test -rwxr-xr-x 1 majordom majordom 18252 Sep 22 09:48 wrapper -rw-r--r-- 1 majordom majordom 2803 Sep 22 09:48 wrapper.c -rwxr-xr-x 1 majordom majordom 223 May 9 1994 wrapper.sh ./majordomo-1.93/Doc: total 451 -rw-r--r-- 1 majordom majordom 25429 Jan 7 1995 FAQ -rw-r--r-- 1 majordom majordom 1388 May 6 1994 README -rw-r--r-- 1 majordom majordom 13475 Mar 14 1994 list-owner-info -rw-r--r-- 1 majordom majordom 115561 Oct 27 1993 majordomo.lisa6.ps -rw-r--r-- 1 majordom majordom 73565 Apr 8 1994 majordomo.ora drwxr-xr-x 2 majordom majordom 512 Sep 22 09:32 man ./majordomo-1.93/Doc/man: total 48 -rw-r--r-- 1 majordom majordom 3512 Oct 27 1993 approve.1 -rw-r--r-- 1 majordom majordom 4133 Oct 27 1993 approve.man -rw-r--r-- 1 majordom majordom 6922 May 2 1994 majordomo.8 -rw-r--r-- 1 majordom majordom 8836 May 2 1994 majordomo.man ./majordomo-1.93/contrib: total 66 -rwxr-xr-x 1 majordom majordom 3185 Sep 1 1993 archive.pl -rwxr-xr-x 1 majordom majordom 7192 Jan 2 1995 archive2.pl -rwxr-xr-x 1 majordom majordom 839 Sep 1 1993 archive_mh.pl -rw-r--r-- 1 majordom majordom 10021 Apr 22 1994 digest.diff -rwxr-xr-x 1 majordom majordom 674 Apr 2 1994 digest.send -rwxr-xr-x 1 majordom majordom 3201 Apr 22 1994 logsummary.pl -rwxr-xr-x 1 majordom majordom 2742 Apr 22 1994 makeindex.pl -rw-r--r-- 1 majordom majordom 3251 May 2 1994 mod_addr.diff ./majordomo-1.93/digest: total 58 -rw-r--r-- 1 majordom majordom 1697 Jan 18 1994 Makefile -rw-r--r-- 1 majordom majordom 1351 Jan 18 1994 README -rw-r--r-- 1 majordom majordom 1528 Jan 18 1994 aliases.slice -rwxr-xr-x 1 majordom majordom 11320 Jan 4 1995 digest -rw-r--r-- 1 majordom majordom 1231 Jan 18 1994 firewalls-digest.cf -rw-r--r-- 1 majordom majordom 174 Jan 18 1994 firewalls-digest.header -rw-r--r-- 1 majordom majordom 3 Jan 18 1994 firewalls-digest.num -rw-r--r-- 1 majordom majordom 777 Jan 18 1994 firewalls-digest.trailer -rw-r--r-- 1 majordom majordom 2 Jan 18 1994 firewalls-digest.vol -rw-r--r-- 1 majordom majordom 6058 Jan 18 1994 shlock.pl -rw-r--r-- 1 majordom majordom 2349 Jan 18 1994 wrapper.c ./man: total 2 drwxr-xr-x 2 majordom majordom 512 Sep 22 09:49 man1 drwxr-xr-x 2 majordom majordom 512 Sep 22 09:49 man8 ./man/man1: total 7 -rw-r--r-- 1 majordom majordom 3512 Sep 22 09:49 approve.1 ./man/man8: total 14 -rw-r--r-- 1 majordom majordom 6922 Sep 22 09:49 majordomo.8 Good luck, Karen Brown Foster Unix System Administrator National Marine Fisheries Service On Sep 26, 10:57am, Jason Vagner wrote: > Subject: Compiling wrapper problem on Irix 5.3 > I've been having problems getting the wrapper to compile on an SGI. What > exactly is necessary to get the wrapper simply to compile? Allow me to step > through the installation steps from the README and please tell me if I'm not > understanding this (I'm trying to understand what depends on what): > > >choose and/or create a uid and gid for this to run under > > I have chosen these. > > >create appropriate directories ($homedir and $listdir), with > >appropriate user, group, and permissions (775) > > Are these necessary for the wrapper to compile? > > >edit the "Makefile" to set W_BIN and the environment for "wrapper"; > >don't forget to make the changes for POSIX, if necessary > > Is the W_BIN the only one necessary? I'm compiling this on an IRIX 5.3, and > I'll include the error message I get at the end of this post. Does the compile > rely on majordomo.cf? > > >compile and install the perl code and man pages. > >("make", then "make install") > > This is where I get this error message: > ---- > cc -DBIN=\"/usr/people/aidsauth/tools/majordomo-1.93\" > -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" > -DHOME=\"HOME=/usr/people/aidsauth/tools/majordomo-1.93\" > -DSHELL=\"SHELL=/bin/csh\" > -DMAJORDOMO_CF=\"MAJORDOMO_CF=/usr/people/aidsauth/tools/majordomo-1.93/majordomo.cf\" > -DPOSIX_UID=1115 -DPOSIX_GID=40 -DSETGROUP -o wrapper wrapper.c > cfe: Error: wrapper.c, line 65: Unacceptable operand of == or != > if (strchr(argv[1], '/') != (char *) 0 ) { > ------------------------------^ > cfe: Warning 712: wrapper.c, line 99: illegal combination of pointer and > integer > char setgroups_used = "setgroups_was_included"; > ---------^ > *** Error code 1 (bu21) > ---- > > And I admit I can't make much of this. > > I noticed in the last few days that a few people are running theirs on Irix 5.3 > (which is what I have), but I thought perhaps a public post might be the best > way to elicit feedback. > > Thanks in advance!! > > Jason > > -- > Email jason@asu.edu > Finger jason@earthvision.asu.edu > Key BF 6B EE 1C 03 E8 06 31 48 02 75 87 07 46 66 6D > WWW http://earthvision.asu.edu/aidsauthority >-- End of excerpt from Jason Vagner -- Karen Brown Foster Unix System Administrator Fisheries Statitics Division National Marine Fisheries Service (301) 713-2316 VOICE (301) 713-4137 FAX kbfoster@oyster.ssp.nmfs.gov From majordomo-users-owner Thu Sep 28 06:00:01 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id FAA14659 for majordomo-users-outgoing; Thu, 28 Sep 1995 05:39:43 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id FAA14652 for ; Thu, 28 Sep 1995 05:39:40 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA18302 for majordomo-users@greatcircle.com; Thu, 28 Sep 95 05:38:03 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA06969; Thu, 28 Sep 95 05:38:01 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA26710 for majordomo-users@greatcircle.com; Thu, 28 Sep 95 05:37:59 MST Received: from miaow.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA25845; Thu, 28 Sep 95 07:37:58 CDT Received: by miaow.sps.mot.com (AIX 3.2/UCB 5.64/4.03) id AA13386; Thu, 28 Sep 1995 07:37:48 -0500 From: dwolfe@risc.sps.mot.com (Dave Wolfe) Message-Id: <9509281237.AA13386@miaow.sps.mot.com> Subject: Re: Unknown Mailer Error 139 To: uunet!soltec.com!erikw (Erik Wolf) Date: Thu, 28 Sep 1995 07:37:47 -0500 (CDT) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: <199509272238.RAA10228@isis.cu.soltec.com> from "Erik Wolf" at Sep 27, 95 05:47:17 pm Reply-To: David Wolfe X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 703 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Erik Wolf writes: ] > > I am installing Majordomo 1.93 on a Sun SparcStation SLC running SunOS > 4.1.3. When I am testing majordomo by sending requests to it (usually > subscribing to a sample list), any mail I send gets returned with Unknown > mailer error 139 and it tells me that the core dumped. I ran adb on the > core file and the only thing it told me was the was a segmentation > violation. Anybody ever seen this before? About every hour on this list. It's the same as the "out of memory" problem described in the FAQ. You have a permissions problem. -- Dave Wolfe *Not a spokesman for Motorola* (512) 891-3246 Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598 From majordomo-users-owner Thu Sep 28 07:04:55 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA16131 for majordomo-users-outgoing; Thu, 28 Sep 1995 06:31:36 -0700 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id GAA16116; Thu, 28 Sep 1995 06:31:20 -0700 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id JAA05158; Thu, 28 Sep 1995 09:15:53 -0400 Date: Thu, 28 Sep 1995 09:15:52 -0400 (EDT) From: "Jonathan M. Bresler" Subject: Re: majordomo To: -Vince- cc: majordomo-users@GreatCircle.COM, majordomo-workers@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 Wed, 27 Sep 1995, -Vince- wrote: > Hi everyone, > > I'm trying to setup majordomo so any posts to the list will go to the > digest which goes out once a day and I am using Crontab to do it. Any > ideas what I am doing wrong? > > Here is my Crontab entry: > > 6 0 * * * /usr/home/majordomo/digest -m -c /usr/home/majordomo/lists/gus-general-digest.config ^^^ i use '-C' with majordomo-1.92. as in: 9 22 * * * /usr/local/majordomo/wrapper digest -m -C -l test-digest test-digest-outgoing Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From majordomo-users-owner Thu Sep 28 07:14:46 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id GAA16112 for majordomo-users-outgoing; Thu, 28 Sep 1995 06:30:50 -0700 Received: from mail2.digital.com (mail2.digital.com [204.123.2.56]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id GAA16097 for ; Thu, 28 Sep 1995 06:30:45 -0700 Received: from us1rmc.bb.dec.com by mail2.digital.com; (5.65 EXP 4/12/95 for V3.2/1.0/WV) id AA01578; Thu, 28 Sep 1995 06:23:03 -0700 Received: from human.enet by us1rmc.bb.dec.com (5.65/rmc-22feb94) id AA19370; Thu, 28 Sep 95 09:13:05 -0400 Message-Id: <9509281313.AA19370@us1rmc.bb.dec.com> Received: from human.enet; by us1rmc.enet; Thu, 28 Sep 95 09:24:23 EDT Date: Thu, 28 Sep 95 09:24:23 EDT From: "Al Avery, Digital Equipment, Maynard, MA, 508.493.6607 (223-6607)" To: majordomo-users@greatcircle.com Cc: avery@human.ENET.dec.com Apparently-To: majordomo-users@greatcircle.com Subject: "info" and "subscribe" reply messages Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, Background I'm setting up a closed list and I'd like the response to "info" command to be different than the one for the "subscribe" command. In particular, I want "info" to describe what the list is used for. Since the list is closed (or restricted membership), I want the "subscribe" command to display a message that tells the requestor the criteria for membership, includes the membership request form and tells her/him where to send the completed request. Question May I specify different reply messages for the "info" and the "subscribe" commands for a closed list? If yes, how do I do this? Many thanks, - Al Avery From majordomo-users-owner Thu Sep 28 22:58:06 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA14037 for majordomo-users-outgoing; Thu, 28 Sep 1995 22:30:50 -0700 Received: from viper.gao.gov (viper.gao.gov [161.203.16.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id IAA19341 for ; Thu, 28 Sep 1995 08:02:02 -0700 From: troy2.atc@gao.gov Received: from viper.gao.gov (daemon@localhost) by viper.gao.gov (8.6.12/8.6.12) with ESMTP id LAA26864 for ; Thu, 28 Sep 1995 11:04:57 -0400 Received: from mailgateway.gao.gov (mailgateway.gao.gov [161.203.15.2]) by viper.gao.gov (8.6.12/8.6.12) with SMTP id LAA26842 for ; Thu, 28 Sep 1995 11:04:55 -0400 Received: from ccMail by mailgateway.gao.gov (SMTPLINK V2.10.04o) id AA812311279; Thu, 28 Sep 95 10:41:07 EST Date: Thu, 28 Sep 95 10:41:07 EST Message-Id: <9508288123.AA812311279@mailgateway.gao.gov> To: majordomo-users@GreatCircle.com Subject: HELP!!!! Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I've been running a majordomo mailing list called daybook for the General Accounting Office for about 2 months without any major problems. The list has grown to over 1500 users with several people coming and going each day. Just recently, Majordomo got held up a couple of times processing requests. Previously, when a new daybook request was sent to daybook the resend program ran quickly and when I checked the mail queue I could see the one job with the whole list of users as recipients. Now, twice when I've kicked in a new request, the process has hung on the resend program. Last night, it hung for over two hours (until I accidentally blew it away from the queue while I was tinkering with it). I'm not sure if it would have hung forever our not. This morning I tried to recreate the problem, but the process only hung at the resend for about 10-40 minutes (no big deal) and then started working. Our information server lies outside our domain so any problems communicating with the Internet would be isolated to our machine. (I was able to send other messages without a problem while it was hung). Our router, DNS, sendmail, etc. are working properly. We have plenty of disk space in all partitions and no memory problems. We are running SUNOS 5.4 on an Internet Netra Server. Here is part of the /etc/aliases file: daybook: "|/usr/local/majordomo/wrapper resend -l daybook -h www.gao.gov daybook-outgoing" daybook-outgoing: :include:/usr/local/majordomo/lists/daybook, daybook-archive daybook-archive: "/usr/local/majordomo/wrapper archive -f /usr/local/majordomo/archives/daybook/daybook -d -a" HAS ANYBODY ENCOUNTERED THIS PROBLEM BEFORE OR IS IT TO BE EXPECTED WITH SUCH A LARGE LIST??? Thanks a Bunch, Paul Gordon - TROY SYSTEMS (202) 512-3342 (U.S.) troy2.atc@gao.gov From majordomo-users-owner Fri Sep 29 01:31:11 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id BAA19432 for majordomo-users-outgoing; Fri, 29 Sep 1995 01:28:09 -0700 Received: from wwwserver.law.wits.ac.za (wwwserver.law.wits.ac.za [146.141.59.72]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id BAA19379 for ; Fri, 29 Sep 1995 01:26:25 -0700 Received: (from majordom@localhost) by wwwserver.law.wits.ac.za (8.6.12/8.6.9) id KAA27454; Fri, 29 Sep 1995 10:31:58 +0200 Date: Fri, 29 Sep 1995 10:31:58 +0200 (GMT+0200) From: Majordomo list server To: Majordomo-Users@greatcircle.com Subject: Problem with RCPT In-Reply-To: <9509281313.AA19370@us1rmc.bb.dec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all I am very new to this group. I set up a majordomo list server and am now finding out what it is like to be on the admin end of list serving. The problem I currently face is that resend is allowing RCPT: notices through, despite the fact that there is a catch for this in the resend script. It catches returned mail and redirects these to the list owner but not RCPT confirmation messages. Can someone please tell me why this is and how I might go about rectifying it? Also is there any way of stripping messages that go through resend of their receipt notification flags to nip the problem in the bud before the RCPT: problem starts? Many thanks Regards Mark From majordomo-users-owner Fri Sep 29 07:23:46 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id HAA02472 for majordomo-users-outgoing; Fri, 29 Sep 1995 07:17:25 -0700 Received: from pigeon.cf.ac.uk (pigeon.cf.ac.uk [131.251.0.2]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id HAA02465 for ; Fri, 29 Sep 1995 07:17:19 -0700 Received: from thor.cf.ac.uk by pigeon.cf.ac.uk with SMTP (PP) id <29183-0@pigeon.cf.ac.uk>; Fri, 29 Sep 1995 15:10:52 +0100 Date: Fri, 29 Sep 1995 15:12:30 +0100 (BST) From: Andrew Cormack Reply-To: Andrew Cormack To: majordomo-users@greatcircle.com Subject: Making list files secure Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The FAQ mentions making the majordomo directory and files only readable by their owner and group (ie 770 for dirs. and 660 for files), but this prevents the mailer from reading my list membership file when I send a mail to the list. Majordomo, resend and co. are ok as they are run via the wrapper. I'd like to keep all the files as restricted as possible, since my system has real users on it who might start trying to find out list membership by reading any world-readable files, but the best I can think of is either: make the permissions 771 (dir) and 664 (list file), which allows any local user who knows the list name to display the membership file or add the user daemon to the majordomo group Are there any security implications to the latter idea ? Thanks, Andrew -- +-----------------------------------------------------------------+ | Andrew Cormack | email: cormack@cardiff.ac.uk | | Information Systems Support, | snail: 40/41 Park Place, Cardiff | | postmaster and webmaster | CF1 3BB | | University of Wales, Cardiff | | +-----------------------------------------------------------------+ From majordomo-users-owner Fri Sep 29 09:53:46 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id JAA07058 for majordomo-users-outgoing; Fri, 29 Sep 1995 09:35:36 -0700 Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id JAA07049; Fri, 29 Sep 1995 09:35:30 -0700 Received: from cthulhu.engr.sgi.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id JAA03904; Fri, 29 Sep 1995 09:33:36 -0700 Received: from lunch.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id JAA00201; Fri, 29 Sep 1995 09:25:38 -0700 Received: by lunch.engr.sgi.com (950511.SGI.8.6.12.PATCH526/940406.SGI.AUTO) id JAA04757; Fri, 29 Sep 1995 09:25:36 -0700 From: pdc@lunch.engr.sgi.com (Paul Close) Message-Id: <199509291625.JAA04757@lunch.engr.sgi.com> Subject: Re: majordomo To: vince@apollo.COSC.GOV (-Vince-) Date: Fri, 29 Sep 1995 09:25:33 -0700 (PDT) Cc: majordomo-users@GreatCircle.COM, majordomo-workers@GreatCircle.COM In-Reply-To: from "-Vince-" at Sep 27, 95 02:35:38 pm X-Mailer: ELM [version 2.5 PL0a7] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1432 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > > I'm trying to setup majordomo so any posts to the list will go to the > > > digest which goes out once a day and I am using Crontab to do it. Any > > > ideas what I am doing wrong? > > > > You didn't say what wasn't working. I assume messages are queuing up all > > right, it's just that a digest isn't sent out daily? > > I'm not sure if the messages are queuing up all right since nothing > is in the directories in both listname.archive and > /usr/home/digests/listname-digest Messages posted to the main list should show up in your digest work directory ($digest_work_dir in majordomo.cf). If they don't, you have something mis-configured. > Hopefully it does but does my /etc/aliases look correct if people > mailing to gus-general which is the mailing list version will queue and > have cron actually sending out the daily digest with the above cron > entry for gus-general-digest? > > Here is my /etc/aliases: > > gus-general: "|/usr/home/majordomo/wrapper resend -l gus-general -h apollo.COSC.GOV gus-general-outgoing,nobody" > gus-general-outgoing: "|/usr/local/bin/bulk_mailer -m owner-gus-general@apollo.COSC.GOV /usr/home/majordomo/lists/gus-general","|/usr/home/majordomo/wrapper digest -r -C -l gus-general-digest gus-general-digest-outgoing,nobody" Yes, these entries look fine. -- Paul Close pdc@sgi.com http://reality.sgi.com/employees/pdc/ No fate but what we make From majordomo-users-owner Fri Sep 29 12:23:40 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id MAA14339 for majordomo-users-outgoing; Fri, 29 Sep 1995 12:04:34 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with ESMTP id MAA14332 for ; Fri, 29 Sep 1995 12:04:30 -0700 Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by tetsuo.communique.net (8.6.12/8.6.12) with SMTP id OAA14104 for ; Fri, 29 Sep 1995 14:02:56 -0500 Date: Fri, 29 Sep 1995 14:02:56 -0500 (CDT) From: Raul Zighelboim To: majordomo-users@greatcircle.com Subject: Moderated lists Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I know this can be done, as I did it once by accident. But now, I cannot figure out how to do it: I would like to create a moderated list were: -The moderator(s) can post without a BOUNCE nor having to use an Approve: password, ie if mail is From:moderator then post. -If any one else tries to post to the list, then the message will be bounced to the moderator. Thanks ----------------------------------------------------------------------------- Raul Zighelboim e-mail: mango@communique.net Communique Inc. Tel: 504.527.6200 Technical Specialist Fax: 504.527.6030 From majordomo-users-owner Fri Sep 29 13:33:24 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id NAA17108 for majordomo-users-outgoing; Fri, 29 Sep 1995 13:25:33 -0700 Received: from inforamp.net (InfoRamp.Net [198.53.144.31]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id NAA17101 for ; Fri, 29 Sep 1995 13:25:28 -0700 Received: from ts16-12.inforamp.net by inforamp.net (5.0/SMI-SVR4) id AA27325; Fri, 29 Sep 1995 16:23:29 -0400 Message-Id: <9509292023.AA27325@inforamp.net> X-Sender: nhersco@inforamp.net X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 29 Sep 1995 04:24:51 -0400 To: majordomo-users@greatcircle.com From: Hersco@NetDirectories.com (Neil A. Hersco) Subject: Majordomo/Out of Memory/Linux content-length: 1672 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk It's a beautiful day outside, but unfortunately I'm on the inside looking out. Could someone please help me enjoy my weekend ! Here's my problem I just installed Majordomo 1.93 under Linux with Perl 4.036 I have set it up as instructed and (I think) got all the permissions proper. Directories are set to mode 775 and user and group owned majordom. When I test using "sendmail -v majordomo", I get the following errors: WARNING: cannot open alias database /etc/aliases /etc/aliases: 9 aliases, longest 47 bytes, 267 bytes total (at this point I enter:) help . (at which point in about 1 minute I get:) Out of memory! "|/tools/majordomo/wrapper majordomo"...unknown mailer error 1 The funny thing is the majordomo help script is delivered to root (from where I am testing) and to majordomo-owner ... aliased to neil (as an error). Therefore I know the aliases file is being used to send majordomo-owner: neil a message. I have a "Log" file set in /tools/majordomo but nothing has been written to it. (and yes the permissions are set properly). My majordomo.cf file is properly set (in the /etc directory - actually linked to /tools/majordomo) ... My wrapper program has proper permissions ... I have read both the FAQ and README and Majordomo Distribution (majordomo.ora). I am at a loss? Please help !! Thanks very much. +-------------------------------------------------------------+ | Neil A. Hersco Tel: (905) 886-7638 | | Hersco@NetDirectories.com Fax: (905) 709-0780 | | Thornhill, Ontario CANADA | +-------------------------------------------------------------+ From majordomo-users-owner Sat Sep 30 22:30:00 1995 Received: (majordom@localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1) id WAA05124 for majordomo-users-outgoing; Sat, 30 Sep 1995 22:24:37 -0700 Received: from sowebo.charm.net (sowebo.charm.net [199.0.70.21]) by miles.greatcircle.com (8.6.9/Miles-950430-1) with SMTP id WAA05117 for ; Sat, 30 Sep 1995 22:24:34 -0700 From: petej@clickvision.com Received: from clickvision.com by sowebo.charm.net; Sun, 1 Oct 95 01:21 EDT X-Sender: petej@sowebo.charm.net Message-Id: Mime-Version: 1.0 Content-Length: 730 Content-Type: text/plain; charset="us-ascii" Date: Sun, 1 Oct 1995 01:05:33 -0500 To: majordomo-users@greatcircle.com >From: petej@clickvision.com (Peter M. Jansson) Subject: Compilation problems with OSF/1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk OSF/1 sometimes behaves as if it were a BSD system, so I went ahead and tried to use the BSD flags in the Makefile. When compiling, I got an error on line 65 complaining that the "(char *) NULL" was invalid; I repaired this one by eliminating the (char *) cast. When running the wrapper for the first time, I got the message "Recompile with POSIX flags" (anyone else get this? It surprised me, but maybe it shouldn't have). So I switched the Makefile to the POSIX flags, and now got a compilation error on line 99, because the variable "setgroups_used" should have been a char * instead of a char -- at least that's how it looked to me. Is this, indeed, an error? Did I fix it properly by adding a "*"? Thanks, Pete.