From majordomo-users-owner Fri Nov 1 10:44:08 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA09443 for majordomo-users-outgoing; Fri, 1 Nov 1996 10:31:50 -0800 (PST) Received: from westnet.com (westnet.com [206.24.6.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA09382 for ; Fri, 1 Nov 1996 10:31:33 -0800 (PST) Received: from playfully.icsn.com ([207.122.96.111]) by westnet.com (8.7.6/8.7.3) with SMTP id NAA21163 for ; Fri, 1 Nov 1996 13:31:39 -0500 (EST) Message-ID: <327A32DC.15DF@webspan.net> Date: Fri, 01 Nov 1996 12:26:52 -0500 From: Jim Anderson Reply-To: playfull@webspan.net Organization: Playfully Inc. X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk -who From majordomo-users-owner Fri Nov 1 13:16:37 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA06763 for majordomo-users-outgoing; Fri, 1 Nov 1996 13:03:13 -0800 (PST) Received: from uclink4.berkeley.edu (uclink4.Berkeley.EDU [128.32.155.12]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA06725 for ; Fri, 1 Nov 1996 13:03:03 -0800 (PST) Received: from [128.32.188.35] ([128.32.188.35]) by uclink4.berkeley.edu (8.7.6/8.6.12) with SMTP id NAA10809 for ; Fri, 1 Nov 1996 13:02:34 -0800 (PST) Date: Fri, 1 Nov 1996 13:02:34 -0800 (PST) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-mailer: Eudora Pro 2.1.3 To: majordomo-users@greatcircle.com From: tliving@uclink4.berkeley.edu (Tom Livingston) Subject: Blcoking Access to the WHO list Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Does anyone know if it is possible to prevent even subscribers from accessing the WHO list information? Thanks. Tom Livingston ****************************************************************************** Please notice that I have a new email address: tliving@uclink4.berkeley.edu From majordomo-users-owner Fri Nov 1 13:50:47 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA08750 for majordomo-users-outgoing; Fri, 1 Nov 1996 13:38:53 -0800 (PST) Received: from eclectic.kluge.net (eclectic.kluge.net [130.215.248.68]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA08743 for ; Fri, 1 Nov 1996 13:38:45 -0800 (PST) Received: from dilbert.kluge.net (root@dilbert.kluge.net [130.215.248.72]) by eclectic.kluge.net (8.8.2/8.8.2) with ESMTP id QAA31931; Fri, 1 Nov 1996 16:40:48 -0500 Received: from localhost (felicity@localhost) by dilbert.kluge.net (8.8.2/8.8.2) with SMTP id QAA28490; Fri, 1 Nov 1996 16:29:06 -0500 X-Authentication-Warning: dilbert.kluge.net: felicity owned process doing -bs Date: Fri, 1 Nov 1996 16:29:06 -0500 (EST) From: Theo Van Dinter To: Tom Livingston cc: majordomo-users@GreatCircle.COM Subject: Re: Blcoking Access to the WHO list In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 1 Nov 1996, Tom Livingston wrote: > Does anyone know if it is possible to prevent even subscribers from > accessing the WHO list information? under MD 1.94, there's a who_access option (it's at the bottom) ... you can set it to 'open', 'list', or 'closed' ... You want closed. 8) -- ----------------------------------------------------------------------------- Theo Van Dinter www: http://www.kluge.net/~felicity/ Vice-President WPI Lens and Lights Active Member in SocComm and ACM Color is only a pigment of your imagination. ----------------------------------------------------------------------------- From majordomo-users-owner Fri Nov 1 14:01:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA09101 for majordomo-users-outgoing; Fri, 1 Nov 1996 13:48:33 -0800 (PST) Received: from queernet.queernet.org (queernet.queernet.org [140.174.78.69]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA09092 for ; Fri, 1 Nov 1996 13:48:27 -0800 (PST) Received: from localhost (rogerk@localhost) by queernet.queernet.org (8.7.4/8.7.3) with SMTP id NAA20016 Date: Fri, 1 Nov 1996 13:46:53 -0800 (PST) From: "Roger B.A. Klorese" To: Tom Livingston cc: majordomo-users@GreatCircle.COM Subject: Re: Blcoking Access to the WHO list In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk You can't block "who" access with unmodified pre-1.94 software. In 1.94, set who_access to "closed"; in pre-1.94, you must get the "anon" patch and set "anon_who" for the list. -- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy -- the refusal of joy!" -- Paul Rudnick From majordomo-users-owner Fri Nov 1 16:30:54 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA19275 for majordomo-users-outgoing; Fri, 1 Nov 1996 16:24:40 -0800 (PST) Received: from reduno.reduno.com.mx (reduno.reduno.com.mx [192.100.183.178]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id QAA19264 for ; Fri, 1 Nov 1996 16:24:31 -0800 (PST) Received: by reduno.reduno.com.mx (4.1/4.7) id AA18315; Fri, 1 Nov 96 18:25:07 CST Date: Fri, 1 Nov 1996 18:25:06 -0600 (CST) From: SANDRA CEJUDO FUNES To: Majordomo-Users@GreatCircle.COM Subject: archive files Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi !! When I post to majordomo the index command to my list prueba1, it said that there's no files available, but there are two files in the archive directory. What'is wrong? Sandra From majordomo-users-owner Fri Nov 1 16:45:43 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA20044 for majordomo-users-outgoing; Fri, 1 Nov 1996 16:39:05 -0800 (PST) Received: from srv1-bsb.GNS.com.br (srv1-bsb.GNS.com.br [200.239.56.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id QAA20024 for ; Fri, 1 Nov 1996 16:38:55 -0800 (PST) Received: (from lioux@localhost) by srv1-bsb.GNS.com.br (8.8.2/8.8.2) id WAA28795 for majordomo-users@greatcircle.com; Fri, 1 Nov 1996 22:38:43 -0200 (EDT) From: Mario Sergio Fujikawa Ferreira Message-Id: <199611020038.WAA28795@srv1-bsb.GNS.com.br> Subject: Off topic - Qmail + Majordomo + Sendmail To: majordomo-users@greatcircle.com Date: Fri, 1 Nov 1996 22:38:42 -0200 (EDT) X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Dear guys, Here is a setup. I am running sendmail 8.8.2. I have majordomo 1.94 working. Somebody told me that qmail is faster than sendmail for mail delivery. Being a dumb try-it-out idiot: I just installed qmail. However, I don't want to put down my beloved sendmail. It's dealing well with my mail. Besides, I don't want to have the pain of converting all my setup to a totally new different one, being it easy or not. :) So, what's the point? I want to setup qmail with majordomo only. I can run qmail-start just like this (written in the INSTALL file): 'qmail-start logger -p mail.info -t qmail' So that it can handle deliveries sent to it through its sendmail wrapper and qmail-inject programs. I just installed qmsmac so that qmail knows how to handle sendmail aliases style files (the ones Majordomo uses). Problems: - qmail wanting to be different does not deliver local mail the way sendmail does in its standard configuration. - the sendmail standard is delivering to /var/mail/$user file - the qmail standard is delivering to $home/Mailbox file - besides that, it bypasses the ~/.forward style files, for it has its own implementation of them, ~/.qmail, with different syntax, of course Possibles Solutions: 1) (Ugly) - let qmail handle all non-local mail directly and correctly - disable local mail delivery - tell qmail to send all local mail to sendmail (at some host, maybe localhost) via smtp, so that sendmail handles it correctly Possible modifications: - dealing with control/locals, control/rcpthosts and smtproutes. 2) (a little better) - tell qmail to direct all local mail to sendmail through piping You may be asking why don't I just tell qmail to handle email to /var/mail/$user the way sendmail does. The problem is that it would bypass ~/.forward files, ignoring filters and else. So, I need qmail to handle local delivery through some mean, sendmail or not, that both doesn't bypass ~/.forward files and does deliver all mail to /var/mail/$user if not worked through ~/.forward files. Maybe procmail could do this. How I would tell qmail to use it (procmail) this way would be a good question. Another question: is there any way to mimic 'sendmail -q' behavior, so that I don't need to be running qmail. I would just need to call it from crontab from time to time. Working it solely as a mail delivery agent to majordomo? Please redirect this mail to other forums if you find applicable. Sorry if I am too off-topic. Look towards your answering soon, Mario Sergio. (lioux@gns.com.br) ps: please direct answers in private if you prefer. From majordomo-users-owner Fri Nov 1 21:15:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA04464 for majordomo-users-outgoing; Fri, 1 Nov 1996 21:05:57 -0800 (PST) Received: from senie.com (senie.com [204.69.207.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id VAA04450 for ; Fri, 1 Nov 1996 21:05:50 -0800 (PST) Received: (qmail-queue invoked from smtpd); 2 Nov 1996 05:05:45 -0000 Received: from localhost (dts@127.0.0.1) by localhost with SMTP; 2 Nov 1996 05:05:45 -0000 Date: Sat, 2 Nov 1996 00:05:45 -0500 (EST) From: Daniel Senie To: majordomo-users@greatcircle.com Subject: trouble getting approve command working Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've got a list working well, but now find that the approve command doesn't work. I get responses from majordomo that the list name is unknown or that the password is incorrect, but am having trouble tracking down which it is. The log file shows me making "help" requests instead of showing anything useful for debugging the problem. Could someone offer a clue as to where to start debugging this problem? Thanks. Dan --------------------------------------------------------------- Daniel Senie Internet: dan@senie.com, Daniel Senie Consulting n1jeb@senie.com http://www.senie.com Packet Radio: N1JEB@KA1SRD.MA If we suffer tamely a lawless attack upon our liberty, we encourage it, and involve others in our doom. -- Samuel Adams From majordomo-users-owner Fri Nov 1 21:45:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA05443 for majordomo-users-outgoing; Fri, 1 Nov 1996 21:43:30 -0800 (PST) Received: from senie.com (senie.com [204.69.207.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id VAA05436 for ; Fri, 1 Nov 1996 21:43:24 -0800 (PST) Received: (qmail-queue invoked from smtpd); 2 Nov 1996 05:43:21 -0000 Received: from localhost (dts@127.0.0.1) by localhost with SMTP; 2 Nov 1996 05:43:21 -0000 Date: Sat, 2 Nov 1996 00:43:21 -0500 (EST) From: Daniel Senie To: majordomo-users@greatcircle.com Subject: approve troubles... never mind! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I figured out how to get the approve stuff to work. I read too much into the instructions again... Dan --------------------------------------------------------------- Daniel Senie Internet: dan@senie.com, Daniel Senie Consulting n1jeb@senie.com http://www.senie.com Packet Radio: N1JEB@KA1SRD.MA If we suffer tamely a lawless attack upon our liberty, we encourage it, and involve others in our doom. -- Samuel Adams From majordomo-users-owner Sat Nov 2 04:16:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id EAA29951 for majordomo-users-outgoing; Sat, 2 Nov 1996 04:12:57 -0800 (PST) Received: from pop (pop.mcs.dundee.ac.uk [134.36.32.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id EAA29876 for ; Sat, 2 Nov 1996 04:11:45 -0800 (PST) Received: from dialin3.dundee.ac.uk by pop (4.1/SMI-4.1-CGM.2) id AA11940; Sat, 2 Nov 96 12:11:56 GMT Received: by dialin3.dundee.ac.uk with Microsoft Mail id <01BBC8B6.CA3080C0@dialin3.dundee.ac.uk>; Sat, 2 Nov 1996 12:10:08 -0000 Message-Id: <01BBC8B6.CA3080C0@dialin3.dundee.ac.uk> From: Andy C To: "'MJ-Users'" Subject: Restricting users post Date: Sat, 2 Nov 1996 12:09:32 -0000 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is probably a really dumb question so excuse me I'm a total newbie at majordomo admin. Is it possible to restrict users so they can receive mail but not post. I want to do this for one or two list members only ! Thanks in advance Andy C (Who hopes this is the correct list and apologizes if it should have gone to the listowners list) From majordomo-users-owner Sat Nov 2 06:32:21 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA02606 for majordomo-users-outgoing; Sat, 2 Nov 1996 06:26:28 -0800 (PST) Received: from cosmos.imag.fr (cosmos.imag.fr [147.171.130.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA02599 for ; Sat, 2 Nov 1996 06:26:22 -0800 (PST) Received: (from phs@localhost) by cosmos.imag.fr (8.6.13-durand/8.6.9) id PAA03466; Sat, 2 Nov 1996 15:26:14 +0100 Date: Sat, 2 Nov 1996 15:26:14 +0100 Message-Id: <199611021426.PAA03466@cosmos.imag.fr> From: Philippe Schnoebelen To: majordomo-users@GreatCircle.COM Subject: sender does not receive own copy Reply-to: Philippe.Schnoebelen@imag.fr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am not a sysadmin but I own a mailing-list, retros@imag.fr, with 200+ subscribers. The list has been created by the local sysadmin, who used majordomo@imag.fr. 2-3 months ago a weird behaviour began to occur. A few members of the list do not receive a copy of their own messages when they post one. It seems they get the other messages OK and some subscribers (e.g. me) do seem to receive a copy of all messages, including their own. Has anybody else experienced this ? Understand that this did not occur before recently, while the list has been quite active for more than 1 year. Perhaps there is something simple that can explain this apparently weird behaviour ? Many thanks for any hint, help, suggestion, ... -- Philippe SCHNOEBELEN, Leibniz-IMAG, 46 Av F. VIALLET, 38000 Grenoble, FRANCE Tel: (+33)0476 57 46 68 email: phs@imag.fr "Algebraic symbols are used when you do not know what you are talking about" From majordomo-users-owner Sat Nov 2 09:47:52 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA20205 for majordomo-users-outgoing; Sat, 2 Nov 1996 09:46:07 -0800 (PST) Received: from www.hsc.wvu.edu (www.hsc.wvu.edu [157.182.105.122]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA20150 for ; Sat, 2 Nov 1996 09:45:55 -0800 (PST) Received: (from rjivan@localhost) by www.hsc.wvu.edu (8.7.5/8.7.3) id MAA09912; Sat, 2 Nov 1996 12:47:32 -0500 (EST) Date: Sat, 2 Nov 1996 12:47:32 -0500 (EST) From: Rajiv Jivan To: majordomo-users@greatcircle.com Subject: sender receives copy Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, Is there anyway to prevent the sender from receiving a copy of his mail. Rajiv From majordomo-users-owner Sat Nov 2 10:17:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA26391 for majordomo-users-outgoing; Sat, 2 Nov 1996 10:01:57 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA26035 for ; Sat, 2 Nov 1996 10:01:15 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id NAA25250; Sat, 2 Nov 1996 13:01:10 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id NAA07262; Sat, 2 Nov 1996 13:01:05 -0500 (EST) Message-Id: <199611021801.NAA07262@augusta.math.psu.edu> To: Rajiv Jivan cc: majordomo-users@GreatCircle.COM Subject: Re: sender receives copy In-reply-to: Your message of "Sat, 02 Nov 1996 12:47:32 EST." References: 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: Sat, 02 Nov 1996 13:01:04 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , Rajiv Jiv an writes: >Is there anyway to prevent the sender from receiving a copy of his mail. No. --Dave From majordomo-users-owner Sat Nov 2 10:38:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA28532 for majordomo-users-outgoing; Sat, 2 Nov 1996 10:25:27 -0800 (PST) Received: from eclectic.kluge.net (eclectic.kluge.net [130.215.248.68]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA28516 for ; Sat, 2 Nov 1996 10:25:17 -0800 (PST) Received: from localhost (felicity@localhost) by eclectic.kluge.net (8.8.2/8.8.2) with SMTP id NAA07705; Sat, 2 Nov 1996 13:27:31 -0500 Date: Sat, 2 Nov 1996 13:27:30 -0500 (EST) From: Theo Van Dinter To: Andy C cc: "'MJ-Users'" Subject: Re: Restricting users post In-Reply-To: <01BBC8B6.CA3080C0@dialin3.dundee.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Sat, 2 Nov 1996, Andy C wrote: > > Is it possible to restrict users so they can receive mail but not > post. I want to do this for one or two list members only ! > There's an option in list.config called 'restrict_post' which you can set to be a filename. In the file you entered, you can then put the list of email addresses who are allowed to post to the list. good luck! -- ----------------------------------------------------------------------------- Theo Van Dinter www: http://www.kluge.net/~felicity/ Vice-President WPI Lens and Lights Active Member in SocComm and ACM "Life," said Marvin. "Don't talk to me about life." ----------------------------------------------------------------------------- From majordomo-users-owner Sat Nov 2 11:32:36 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA07603 for majordomo-users-outgoing; Sat, 2 Nov 1996 11:27:10 -0800 (PST) Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA07596 for ; Sat, 2 Nov 1996 11:27:04 -0800 (PST) Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-960123) id LAA03525; Sat, 2 Nov 1996 11:26:56 -0800 Received: from taz.hyperreal.com(204.152.144.36) by mycroft via smap (V1.3mjr) id sma003523; Sat Nov 2 11:26:20 1996 Received: from localhost by taz.hyperreal.com (8.7.6/V2.0) with SMTP id LAA20804; Sat, 2 Nov 1996 11:23:37 -0800 (PST) Date: Sat, 2 Nov 1996 11:23:37 -0800 (PST) From: Brian Behlendorf To: Mario Sergio Fujikawa Ferreira cc: majordomo-users@GreatCircle.COM Subject: Re: Off topic - Qmail + Majordomo + Sendmail In-Reply-To: <199611020038.WAA28795@srv1-bsb.GNS.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 1 Nov 1996, Mario Sergio Fujikawa Ferreira wrote: > So, I need qmail to handle local delivery through some mean, > sendmail or not, that both doesn't bypass ~/.forward files and does > deliver all mail to /var/mail/$user if not worked through ~/.forward > files. Maybe procmail could do this. How I would tell qmail to use it > (procmail) this way would be a good question. I'm very interested in getting this to work too. One ugly hack: before the list of subscribers is passed off to qmail, run a filter converting all "user@gns.com.br" subscribers to "user%gns.com.br@gns.com.br". If qmail acts as sendmail does, it would reconnect to port 25 and deliver the mail to port 25 as "user@gns.com.br", and since sendmail is still your mail daemon it would handle it from that point forward. If Qmail's "smart" and tries to do its own reduction of "user%gns.com.br@gns.com.br" to "user@gns.com.br", then another alternative is to send it to "user%gns.com.br@someotherhost.com.br", where ideally that other host would have high connectivity to gns.com.br. These are all ugly hacks, though. If qmail doesn't have the direct capability to have another MTA handle local mail, it's more limited than I thought. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- brian@hyperreal.com http://www.apache.org http://www.organic.com/jobs From majordomo-users-owner Sat Nov 2 12:03:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA13591 for majordomo-users-outgoing; Sat, 2 Nov 1996 11:56:29 -0800 (PST) Received: from antares.pegasus.com.br ([200.251.120.50]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA13131 for ; Sat, 2 Nov 1996 11:55:35 -0800 (PST) Received: from Mizar.INTERMAIL ([200.251.120.35]) by antares.pegasus.com.br (8.6.12/8.6.9) with SMTP id QAA05954 for ; Sat, 2 Nov 1996 16:48:16 -0300 Message-ID: <327BA767.5A97@pegasus.com.br> Date: Sat, 02 Nov 1996 17:56:23 -0200 From: Frederico Ferreira da Silva Reply-To: fred@pegasus.com.br Organization: InterMail Ltda X-Mailer: Mozilla 3.01b1 (Win95; I) MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: ctime.pl References: <199611021801.NAA07262@augusta.math.psu.edu> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk If someone now, I'd like a help, When I'm installing my majordomo, it not find the file ctime.pl. I tried find but nothing. What's have? Is The ctime.pl file a file of majordomo or not? When i get tar in the file, it wasn't there. Thank's for any help. -- +-----------------------------------------------------+ | Frederico F. da Silva e-mail: fred@pegasus.com.br | | InterMail Ltda. Rua Sta Rita Durão, 321,209 | | 30140-110 - Belo Horizonte, MG Brazil | | http://www.pegasus.com.br +55-31-281-1508 | +-----------------------------------------------------+ From majordomo-users-owner Sat Nov 2 12:32:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA17510 for majordomo-users-outgoing; Sat, 2 Nov 1996 12:24:16 -0800 (PST) Received: from antequera (antequera.antequera.com [167.114.36.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA17494 for ; Sat, 2 Nov 1996 12:24:08 -0800 (PST) Received: from tule.noc.antequera.com by antequera (SMI-8.6/SMI-SVR4) id OAA10704; Sat, 2 Nov 1996 14:28:30 -0600 Message-Id: <1.5.4.32.19961102212518.006d49e4@antequera.com> X-Sender: javiers@antequera.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 02 Nov 1996 14:25:18 -0700 To: fred@pegasus.com.br From: Javier Santiago Arenas Subject: Re: ctime.pl Cc: majordomo-users@greatcircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Nop. Ctime.pl is perl distribution archive. I'm not sure about this but I never had seen this file in the majordomo distributiion file. javier Javier Santiago Arenas Network Manager Antequera Red S.A de C.V. INFOSURESTE 96... H. Col. Militar 1009-4 Col Reforma http://antequera.com/info96/ C.P. 68050 Oaxaca. Oaxaca. Mx. http://antequera.com Visite Oaxaca: http://antequera.com/OaxacaTour/ Visit Oaxaca: From majordomo-users-owner Sat Nov 2 15:02:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA26504 for majordomo-users-outgoing; Sat, 2 Nov 1996 14:48:23 -0800 (PST) Received: from Post-Office.UH.EDU (Post-Office.UH.EDU [129.7.1.20]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA26497 for ; Sat, 2 Nov 1996 14:48:16 -0800 (PST) Received: from UUCP-GW.CC.UH.EDU by Post-Office.UH.EDU (PMDF V5.0-7 #18580) id <01IBDLI42I9A000K77@Post-Office.UH.EDU> for Majordomo-users@GreatCircle.COM; Sat, 02 Nov 1996 16:48:12 -0600 (CST) Received: from Siswat.Houston.TX.US by UUCP-GW.CC.UH.EDU with UUCP id AA05668 (5.67a/IDA-1.5 for Majordomo-users@GreatCircle.COM); Sat, 02 Nov 1996 16:27:05 -0600 Received: from localhost (localhost [127.0.0.1]) by siswat.compact.com (8.7.4/8.7.3) with ESMTP id KAA12905 for ; Sat, 02 Nov 1996 10:45:06 -0600 Date: Sat, 02 Nov 1996 10:45:06 -0600 From: "A. Lester Buck III" Subject: digestifying old archives To: Majordomo-users@GreatCircle.COM Reply-to: "A. Lester Buck III" Message-id: <199611021645.KAA12905@siswat.compact.com> Content-transfer-encoding: 7BIT Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I started a list with an existing member base and it was very popular right from the start. After people complained about too many messages and no digest for several weeks, I finally got that configured. Now I want to go back and convert the single archive file, with every posting every made, into 40KB digests, so that all the good information at the beginning is available to new members I have looked at archive2.pl and digest, and it seems I need some kind of cross between these. I don't want to make the early digests by day, week, or month, but rather by size, just like a digest. Is there some way to use the distribution tools directly, or are there other tools out there to digestify from an archive file? I am new to perl, but I will start hacking if necessary. One more question, maybe a sendmail nit. In the one big archive file, every posting starts " From list-owner ....". I don't understand where the extra space at the the beginning of the line comes from. Is that a sign I have misconfigured sendmail? Linux 1.2.13 sendmail 8.7.4/8.7.3 Majordomo 1.93 Thanks, Lester -- A. Lester Buck buck@compact.com From majordomo-users-owner Sat Nov 2 15:17:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA27523 for majordomo-users-outgoing; Sat, 2 Nov 1996 15:15:54 -0800 (PST) Received: from spook-le0.cia.com.au ([203.63.116.90]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA27516 for ; Sat, 2 Nov 1996 15:15:47 -0800 (PST) Received: from [203.28.48.4] (d4.cia.com.au [203.28.48.4]) by spook-le0.cia.com.au (8.7.5/8.7.3) with ESMTP id KAA22441 for ; Sun, 3 Nov 1996 10:15:39 +1100 (EST) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 3 Nov 1996 10:20:55 +1100 To: majordomo-users@greatcircle.com From: Katrina Ritchie Subject: URGENT ADVICE NEEDED! Majordomo sending old posts *again* Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all :-) I logged on today to find MD had started sending old list posts (from three to four days ago) again!!! I'm getting lots of annoying "whats happening???" and "me too" posts and really need to try to sort this out. Any ideas on what could be causing this???? This is not what I need fours days before I'm due to go overseas for two months :-( Your help would be so appreciated! Kindest Regards Katrina (Ritchie) WELLPET List Administrator/Owner Sydney, Australia email: katrina@cia.com.au Kindest Regards & Yours in Wellness, Katrina (Ritchie) WELLPET List Administrator/Owner Sydney, Australia email: katrina@cia.com.au From majordomo-users-owner Sat Nov 2 15:47:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA27876 for majordomo-users-outgoing; Sat, 2 Nov 1996 15:31:31 -0800 (PST) Received: from home.samurai.com (home.samurai.com [205.207.28.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA27869 for ; Sat, 2 Nov 1996 15:31:23 -0800 (PST) Received: (from bryanf@localhost) by home.samurai.com (8.8.2/8.8.2) id SAA14411 for majordomo-users@GreatCircle.COM; Sat, 2 Nov 1996 18:31:18 -0500 (EST) From: Bryan Fullerton Message-Id: <199611022331.SAA14411@home.samurai.com> Subject: Re: URGENT ADVICE NEEDED! Majordomo sending old posts *again* To: katrina@cia.com.au (Katrina Ritchie) Date: Sat, 2 Nov 1996 18:28:41 -0500 (EST) In-Reply-To: from "Katrina Ritchie" at Nov 3, 96 10:20:55 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This happened to me today too - several posts from Wednesday of this week suddenly were re-sent this morning. No idea why or where they came from. Quite annoying. I'll be attempting to track it down later today (ie when the people I have coming over in 1/2 hour leave... ;) Bryan > > Hi all :-) > > I logged on today to find MD had started sending old list posts (from three > to four days ago) again!!! > > I'm getting lots of annoying "whats happening???" and "me too" posts and > really need to try to sort this out. > > Any ideas on what could be causing this???? > > This is not what I need fours days before I'm due to go overseas for two > months :-( > > Your help would be so appreciated! > > Kindest Regards > Katrina (Ritchie) > WELLPET List Administrator/Owner > Sydney, Australia > email: katrina@cia.com.au > > Kindest Regards & Yours in Wellness, > Katrina (Ritchie) > WELLPET List Administrator/Owner > Sydney, Australia > email: katrina@cia.com.au > > > From majordomo-users-owner Sat Nov 2 15:50:46 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA28012 for majordomo-users-outgoing; Sat, 2 Nov 1996 15:40:50 -0800 (PST) Received: from [198.102.244.42] (pb520.greatcircle.com [198.102.244.42]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA28005; Sat, 2 Nov 1996 15:40:43 -0800 (PST) X-Sender: brent@miles.greatcircle.com Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 2 Nov 1996 15:40:46 -0800 To: Katrina Ritchie , majordomo-users@greatcircle.com From: Brent Chapman Subject: Re: URGENT ADVICE NEEDED! Majordomo sending old posts *again* Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 10:20 AM +1100 11/3/96, Katrina Ritchie wrote: >Hi all :-) > >I logged on today to find MD had started sending old list posts (from three >to four days ago) again!!! > >I'm getting lots of annoying "whats happening???" and "me too" posts and >really need to try to sort this out. > >Any ideas on what could be causing this???? > >This is not what I need fours days before I'm due to go overseas for two >months :-( > >Your help would be so appreciated! Majordomo doesn't keep old messages around or anything like that, so this is almost certainly a problem with the underlying mail system, not with Majordomo itself. What's usually happening in a situation like this is that somebody tried to "fix" a mail problem at their site by resending all the messages in their queue to the addresses in the "To:" and "Cc:". Well, the "To:" and/or "Cc:" headers of mailing list messages are going to show the mailing list address, not the address of the subscriber(s) that particular copy of the message was destined to; those would be in the "envelope" that the mail system maintains for the message, which isn't visible as part of the headers on most mail systems. To figure out what site did this, take a very close look at the "Received:" headers of both the original and duplicate copy of one of the repeated messages; the differences (the duplicate should have more "Received:" headers) should give you a good idea of who's responsible. Alternatively, compare the "Received:" headers of several of the duplicates to each other, to see what they have in common. Note that "Received:" headers are generally added bottom-to-top; that is, those nearest the top of the headers are the newest ones, and those near the bottom of the headers are the oldest ones. Majordomo version 1.94 has the ability to specify (on both a site-wide and per-list basis) "taboo" header and body lines that will cause a message to be handed to the list owner for approval if they are present. One of the patterns that we have in the site-wide taboo header list ($global_taboo_headers in the /etc/majordomo.cf file) here at GreatCircle.COM is this: /^received: .*from miles\.greatcircle\.com/i Because of the way our mailing lists are handled, all outgoing list mail will have a line that matches that pattern; all our outgoing list mail is passed from host miles.greatcircle.com to one of the mail machines at UUNET, which adds the "Received: " header that matches the pattern above. If we ever get such a message back, we can be pretty certain that it's been looped by somebody. -Brent ----------------------+----------------------------+------------------------ Brent Chapman | Great Circle Associates | 1057 West Dana Street Brent@GreatCircle.COM | http://www.greatcircle.com | Mountain View, CA 94041 ----------------------+----------------------------+------------------------ Internet Tutorials from the Experts! From majordomo-users-owner Sat Nov 2 16:02:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA28346 for majordomo-users-outgoing; Sat, 2 Nov 1996 15:54:26 -0800 (PST) Received: from ds.rnet.com (ds.rnet.com [205.216.192.93]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA28330 for ; Sat, 2 Nov 1996 15:54:19 -0800 (PST) Received: (from opie@localhost) by ds.rnet.com (8.7.1/8.7.1) id RAA02858; Sat, 2 Nov 1996 17:53:21 -0600 Date: Sat, 2 Nov 1996 17:53:20 -0600 (CST) From: Paul Opie To: Dave Barr cc: Rajiv Jivan , majordomo-users@GreatCircle.COM Subject: Re: sender receives copy In-Reply-To: <199611021801.NAA07262@augusta.math.psu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Sat, 2 Nov 1996, Dave Barr wrote: > In message , Rajiv Jiv > an writes: > >Is there anyway to prevent the sender from receiving a copy of his mail. > > No. > > --Dave > well... actually it's a function of 'my' sendmail. throw a switch and the sender doesn't get a copy. consult the sendmail docs. Paul _______________________________________________________________________ Digitally Speaking (c) 1989 - opie@DigitallySpeaking.com - 217.224.9153 Powered By Linux: http://www.DigitallySpeaking.com From majordomo-users-owner Sat Nov 2 16:47:37 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA29871 for majordomo-users-outgoing; Sat, 2 Nov 1996 16:32:47 -0800 (PST) Received: from [198.102.244.42] (pb520.greatcircle.com [198.102.244.42]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id QAA29864; Sat, 2 Nov 1996 16:32:39 -0800 (PST) X-Sender: brent@miles.greatcircle.com Message-Id: In-Reply-To: References: <199611021801.NAA07262@augusta.math.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 2 Nov 1996 16:32:43 -0800 To: Paul Opie , Dave Barr From: Brent Chapman Subject: Re: sender receives copy Cc: Rajiv Jivan , majordomo-users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 5:53 PM -0600 11/2/96, Paul Opie wrote: >On Sat, 2 Nov 1996, Dave Barr wrote: > >> In message , >>Rajiv Jiv >> an writes: >> >Is there anyway to prevent the sender from receiving a copy of his mail. >> >> No. >> >> --Dave >> > >well... actually it's a function of 'my' sendmail. throw a switch and the >sender doesn't get a copy. consult the sendmail docs. It only works for messages Sendmail thinks are sent by one of the recipients. Messages to Majordomo-managed lists (i.e., if you're using the "resend" program) aren't "sent" by the originator (the "From:" line) from Sendmail's point of view; they're "sent" by the mailing list owner. -Brent ----------------------+----------------------------+------------------------ Brent Chapman | Great Circle Associates | 1057 West Dana Street Brent@GreatCircle.COM | http://www.greatcircle.com | Mountain View, CA 94041 ----------------------+----------------------------+------------------------ Internet Tutorials from the Experts! From majordomo-users-owner Sat Nov 2 19:33:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA07209 for majordomo-users-outgoing; Sat, 2 Nov 1996 19:17:31 -0800 (PST) Received: from zeus (zeus.worldramp.net [199.233.67.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id TAA07185 for ; Sat, 2 Nov 1996 19:17:15 -0800 (PST) Received: from starfury by zeus with smtp (Smail3.1.29.1 #7) id m0vJt1M-000IHfC; Sat, 2 Nov 96 22:14 EST Message-Id: <2.2.32.19961103031600.006ad4e8@worldramp.net> X-Home-Page: http://www.aiscom.com/~dstrauss/ Organization: Advanced Internet Services X-Sender: dstrauss@worldramp.net X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 02 Nov 1996 22:16:00 -0500 To: majordomo-users@GreatCircle.COM From: David Strauss Subject: Re: URGENT ADVICE NEEDED! Majordomo sending old posts *again* Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 06:28 PM 11/2/96 -0500, Bryan Fullerton wrote: >This happened to me today too - several posts from Wednesday of this week >suddenly were re-sent this morning. No idea why or where they came >from. Quite annoying. I'll be attempting to track it down later today Are you using smail? I've had this problem three times now, where the list started sending out dozens, even hundreds of old posts going back several weeks. It seems to be a smail bug, which can be stopped by rebooting the mail server. I've asked the sys admin to upgrade to 1.94, so I can use the taboo headers trick that Brent posted earlier today. Simple and elegant. (Actually, he's trying to convince the ISP owner to switch to sendmail, which I hope will solve the problem once and for all.) Dave -- David Strauss <*> O- Administrator, New York Islanders Mailing List http://www.aiscom.com/~dstrauss/ CAFFIDGET (ka fij' it) v. The act of breaking up a Styrofoam coffee cup into several hundred pieces after consuming it's contents. - Rich Hall, Sniglets From majordomo-users-owner Sun Nov 3 00:32:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id AAA26037 for majordomo-users-outgoing; Sun, 3 Nov 1996 00:24:47 -0800 (PST) Received: from home.samurai.com (home.samurai.com [205.207.28.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id AAA25714 for ; Sun, 3 Nov 1996 00:24:12 -0800 (PST) Received: (from bryanf@localhost) by home.samurai.com (8.8.2/8.8.2) id DAA00251; Sun, 3 Nov 1996 03:24:01 -0500 (EST) From: Bryan Fullerton Message-Id: <199611030824.DAA00251@home.samurai.com> Subject: Re: URGENT ADVICE NEEDED! Majordomo sending old posts *again* To: dstrauss@aiscom.com (David Strauss) Date: Sun, 3 Nov 1996 03:24:01 -0500 (EST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <2.2.32.19961103031600.006ad4e8@worldramp.net> from "David Strauss" at Nov 2, 96 10:16:00 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > At 06:28 PM 11/2/96 -0500, Bryan Fullerton wrote: > >This happened to me today too - several posts from Wednesday of this week > >suddenly were re-sent this morning. No idea why or where they came > >from. Quite annoying. I'll be attempting to track it down later today > > Are you using smail? I've had this problem three times now, where the list > started sending out dozens, even hundreds of old posts going back several > weeks. It seems to be a smail bug, which can be stopped by rebooting the > mail server. Nope. sendmail 8.8.2. I'll be looking thru logs now - it's entirely possible that someone bounced/redirected a copy back to the list. My main server is still running majordomo 1.93 - my test server is running 1.94, and I plan to upgrade the main server in a couple of days, which may eliminate a whole bunch of problems. Bryan From majordomo-users-owner Sun Nov 3 09:02:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA10479 for majordomo-users-outgoing; Sun, 3 Nov 1996 08:59:19 -0800 (PST) Received: from sufsys.sufsys.com (mail.sufsys.com [205.183.39.93]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA10472 for ; Sun, 3 Nov 1996 08:59:13 -0800 (PST) Received: by sufsys.sufsys.com with Microsoft Exchange (IMC 4.0.837.3) id <01BBC975.C1B805C0@sufsys.sufsys.com>; Sun, 3 Nov 1996 10:57:08 -0600 Message-ID: From: "Scott C. Villinski" To: "'Majordomo-Users@greatcircle.com'" Subject: Majordomo 1.94, setuid and permissions Date: Sun, 3 Nov 1996 10:57:06 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I just installed 1.94 on a Linux 1.2.13 machine. Worked great, but is really, until I realized my permissions were a little off. Anyway, now it is much quicker, but I don't think that it is configured correctly. When I first ran a test, I got the following error back: MAJORDOMO ABORT While running with an effective uid of 1 and an effective gid of 1, Majordomo ran into the following problems: Unable to write to log file, check permissions on /usr/src/majordomo-1.94/Log Unable to write to list directory $listdir, check permissions on /usr/src/majordomo-1.94/lists Anyway, I fixed the permissions, but one thing that concerns me is that majordomo is running as uid=1 and gid=1 when it should be: uid=443 and gid=2. Furthermore, to make it work, I had to chmod everything to 777, since all the files were owned by majordomo:daemon and it was running as bin:bin. Any thoughts? Thanks, Scott Scott C. Villinski, CNE Consulting Engineer Sufficient Systems, Inc. Email: svillins@sufsys.com USCOMM - Internet Division Email: svillins@uscomm.net 2860 Patton Road Phone: 612.638.9190 Roseville, MN 55113 Fax: 612.638.9290 Web: http://www.sufsys.com http://www.uscomm.net From majordomo-users-owner Sun Nov 3 09:32:35 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA11076 for majordomo-users-outgoing; Sun, 3 Nov 1996 09:18:52 -0800 (PST) Received: from storm.certix.fr (world-net.sct.fr [194.2.128.4]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA11064 for ; Sun, 3 Nov 1996 09:18:43 -0800 (PST) From: ptaylor@worldnet.net Received: from tg8-28.netculture.net (tg8-28.netculture.net [194.250.139.2]) by storm.certix.fr (8.6.12/8.6.12) with SMTP id SAA05854 for ; Sun, 3 Nov 1996 18:10:29 +0100 Message-Id: <199611031710.SAA05854@storm.certix.fr> Comments: Authenticated sender is To: Majordomo-users@GreatCircle.COM Date: Sun, 3 Nov 1996 18:18:44 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: List statistics X-mailer: Pegasus Mail for Win32 (v2.42) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi There Are there any programs available which can give a summary of the amount of Kb used by a list per day ? Many thanks Peter From majordomo-users-owner Sun Nov 3 11:47:36 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA14870 for majordomo-users-outgoing; Sun, 3 Nov 1996 11:44:50 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id LAA14861 for ; Sun, 3 Nov 1996 11:44:42 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id NAA25732; Sun, 3 Nov 1996 13:44:22 -0600 (CST) To: fred@pegasus.com.br Cc: majordomo-users@GreatCircle.COM Subject: Re: ctime.pl References: <199611021801.NAA07262@augusta.math.psu.edu> <327BA767.5A97@pegasus.com.br> From: Jason L Tibbitts III Date: 03 Nov 1996 13:44:21 -0600 In-Reply-To: Frederico Ferreira da Silva's message of Sat, 02 Nov 1996 17:56:23 -0200 Message-ID: Lines: 9 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "FFdS" == Frederico Ferreira da Silva writes: FFdS> If someone now, I'd like a help, When I'm installing my majordomo, it FFdS> not find the file ctime.pl. I tried find but nothing. It's part of Perl. If you don't have ctime.pl, you need to properly install Perl. - J< From majordomo-users-owner Sun Nov 3 12:02:43 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA15515 for majordomo-users-outgoing; Sun, 3 Nov 1996 11:54:31 -0800 (PST) Received: from taz.hyperreal.com (taz.hyperreal.com [204.152.144.36]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id LAA15240 for ; Sun, 3 Nov 1996 11:53:45 -0800 (PST) Received: from localhost by taz.hyperreal.com (8.7.6/V2.0) with SMTP id LAA22425; Sun, 3 Nov 1996 11:53:37 -0800 (PST) Date: Sun, 3 Nov 1996 11:53:37 -0800 (PST) From: Brian Behlendorf To: Bryan Fullerton cc: David Strauss , majordomo-users@GreatCircle.COM Subject: Re: URGENT ADVICE NEEDED! Majordomo sending old posts *again* In-Reply-To: <199611030824.DAA00251@home.samurai.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Sun, 3 Nov 1996, Bryan Fullerton wrote: > > At 06:28 PM 11/2/96 -0500, Bryan Fullerton wrote: > > >This happened to me today too - several posts from Wednesday of this week > > >suddenly were re-sent this morning. No idea why or where they came > > >from. Quite annoying. I'll be attempting to track it down later today > > > > Are you using smail? I've had this problem three times now, where the list > > started sending out dozens, even hundreds of old posts going back several > > weeks. It seems to be a smail bug, which can be stopped by rebooting the > > mail server. > > Nope. sendmail 8.8.2. I'll be looking thru logs now - it's entirely > possible that someone bounced/redirected a copy back to the list. My > main server is still running majordomo 1.93 - my test server is running > 1.94, and I plan to upgrade the main server in a couple of days, which > may eliminate a whole bunch of problems. axionet.com has been doing this to me over the last couple of days. Is a message-ID check going into mj 1.95? Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- brian@hyperreal.com http://www.apache.org http://www.organic.com/jobs From majordomo-users-owner Sun Nov 3 15:40:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21795 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:59:09 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21719 for ; Sun, 3 Nov 1996 14:58:36 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06440 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:58:19 -0800 (PST) Received: from haus.efn.org (haus.efn.org [198.68.17.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id VAA29359 for ; Fri, 25 Oct 1996 21:17:56 -0700 (PDT) Received: from r_morris.efn.org (dynip40.efn.org [204.214.97.40]) by haus.efn.org (8.7.5/8.7.3) with SMTP id VAA29325 for ; Fri, 25 Oct 1996 21:21:04 -0700 (PDT) Message-Id: <199610260421.VAA29325@haus.efn.org> Comments: Authenticated sender is From: "Roger Morris" To: majordomo-users@greatcircle.com Date: Fri, 25 Oct 1996 21:16:16 +0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Digests Reply-to: roger@efn.org X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I have a problem with the digest that I set up. The digests are being created, I can see them in the list.archive directory. The digest is not being mailed out. If I send majordomo the command mkdigest the digest goes out. Is there something in the alias file that I have configured wrong? Roger From majordomo-users-owner Sun Nov 3 15:41:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21640 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:55:32 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21633 for ; Sun, 3 Nov 1996 14:55:28 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06424 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:55:12 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id WAA04080 for ; Thu, 24 Oct 1996 22:57:09 -0700 (PDT) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id AAA03670; Fri, 25 Oct 1996 00:56:03 -0500 (CDT) To: richard welty Cc: majordomo-users@GreatCircle.COM Subject: Re: argh -- 1.94 upgrade problem References: <326E6485.15FB7483@balltown.cma.com> From: Jason L Tibbitts III Date: 25 Oct 1996 00:56:03 -0500 In-Reply-To: richard welty's message of Wed, 23 Oct 1996 14:31:33 -0400 Message-ID: Lines: 11 X-Mailer: Red Gnus v0.51/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "rw" == richard welty writes: rw> when moving to 1.94, we need to update our config files so they contain rw> the new variables, right? what is the recommended way to bring rw> existing config files up to 1.94 standards? Which config file? For majordomo.cf, it's best to use sample.cf as a model and do it all by hand. For the per-list config files, just use the writeconfig command. - J< From majordomo-users-owner Sun Nov 3 15:45:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22131 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:02:58 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22113 for ; Sun, 3 Nov 1996 15:02:53 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06555 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:02:36 -0800 (PST) Received: from sisko.cc.rochester.edu (sisko.cc.rochester.edu [128.151.219.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id LAA02752 for ; Mon, 28 Oct 1996 11:50:17 -0800 (PST) Received: (from kenr@localhost) by sisko.cc.rochester.edu (8.7.6/8.7.3) id OAA19060; Mon, 28 Oct 1996 14:52:41 -0500 (EST) Date: Mon, 28 Oct 1996 14:52:41 -0500 (EST) From: Kenneth C Rich Message-Id: <199610281952.OAA19060@sisko.cc.rochester.edu> To: barr@math.psu.edu, majordomo-users@GreatCircle.COM Subject: Re: utility: help upgrade list to 1.94 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Why not just use the 'writeconfig' command? It's already there. ah, i have rushed in where giants have already trod. i see the writeconfig code takes care of some good things that don't apply at my site. i just figured it couldn't upgrade a large installation with decent speed. well i will wait for more comments before digging myself even deeper. ;-) -- -ken rich This environmentally sound posting was manufactured in the USA from recycled and recyclable electrons. kenr@cc.rochester.edu From majordomo-users-owner Sun Nov 3 15:46:09 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21797 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:59:11 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21734 for ; Sun, 3 Nov 1996 14:58:37 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06455 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:58:20 -0800 (PST) Received: from java.aboard.co.uk (mailhost.aboard.co.uk [194.73.51.130]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id QAA14394 for ; Sun, 27 Oct 1996 16:19:16 -0800 (PST) Received: (from nick@localhost) by java.aboard.co.uk (8.6.12/8.6.9) id AAA09549 for majordomo-users@greatcircle.com; Mon, 28 Oct 1996 00:19:16 GMT From: Nick Perry Message-Id: <199610280019.AAA09549@java.aboard.co.uk> Subject: Can't Unsubscribe with 1.94 To: majordomo-users@greatcircle.com Date: Mon, 28 Oct 1996 00:19:16 +0000 (GMT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I get ABORTs with majordomo 1.94 ona ny attempts to unsubscribe from any list: MAJORDOMO ABORT chown(508, 102, "/usr/local/majordomo/lists/martin-guerre-l.new"): Operation not permitted looking at the file in question reveals that the file in question has uid:gid bin:bin. Any clues appreciated. Linux 2.0.23 / Sendmail 8 / Perl 5.002 -- Nick Perry | AboarD Boats & Yachts Market Ltd Webmaster Manager | 7a Fernshaw Road, LONDON, SW10 0TB. UK Mobile: +44 (0)973 566204 | Tel: +44 (0)171 460 0030 Fax: 0040 | http://www.aboard.co.uk From majordomo-users-owner Sun Nov 3 15:47:43 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21816 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:59:17 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21721 for ; Sun, 3 Nov 1996 14:58:36 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06443 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:58:19 -0800 (PST) Received: from giasbm01.vsnl.net.in (giasbm01.vsnl.net.in [202.54.1.18]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id XAA02439 for ; Fri, 25 Oct 1996 23:00:07 -0700 (PDT) From: aurotech@giasbm01.vsnl.net.in Received: from [205.138.164.2] ([202.54.4.91]) by giasbm01.vsnl.net.in (8.7.4/8.7.3) with SMTP id LAA27806 for ; Sat, 26 Oct 1996 11:28:38 +0530 (IST) Message-Id: <199610260558.LAA27806@giasbm01.vsnl.net.in> Comments: Authenticated sender is To: majordomo-users@GreatCircle.COM Date: Sat, 26 Oct 1996 11:28:55 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: help Reply-to: aurotech@giasbm01.vsnl.net.in X-mailer: Pegasus Mail for Win32 (v2.42) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello Majordomo users, I would like to use majordomo software for my mailing list, Could any one help me how to go ahead, I mean What are the things I have to do to setup the majordomo on my server. I shall appreciate, If you could tell me what are majordomo files should be used and sources of procurement. Please Guide me in this regard. I am also subscriber of majordomo user list I looking forward to reply Thank You in advance S.Ramadoss aurotech@giasbm01.vsnl.net.in From majordomo-users-owner Sun Nov 3 15:48:38 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA21928 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:01:04 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA21921 for ; Sun, 3 Nov 1996 15:01:00 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06502 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:00:44 -0800 (PST) Received: from zax.leftbank.com (zax.leftbank.com [139.167.32.33]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA03537 for ; Mon, 28 Oct 1996 06:51:20 -0800 (PST) Received: (from nmehl@localhost) by zax.leftbank.com (8.7.5/8.7.3/LeftBank-1.1/http://www.leftbank.com/) id JAA11613 for majordomo-users@greatcircle.com; Mon, 28 Oct 1996 09:53:15 -0500 (EST) From: "Nathan J. Mehl" Message-Id: <199610281453.JAA11613@zax.leftbank.com> Subject: Re: $340.00 in FREE Groceries To: majordomo-users@greatcircle.com Date: Mon, 28 Oct 1996 09:53:15 -0500 (EST) In-Reply-To: <21472066536457@hia.net> from "Sheila K. Maxwell" at Oct 27, 96 03:13:49 pm Reply-to: nmehl@leftbank.com X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Don't tell me that majordomo-users _isn't_ set to restrict_post? [ No, but I _did_ add "free groceries" to the "taboo" list after that first post came though, which is why your followup was delayed for a few days until I checked the queue of messages awaiting approval. -Brent ] For shame... :) -- "When the going gets weird, the weird turn pro." Nathan J. Mehl -- The Left Bank Operation (work) nmehl@leftbank.com -- http://www.leftbank.com (play) nmehl@blank.org -- http://ccat.sas.upenn.edu/nmehl/ From majordomo-users-owner Sun Nov 3 15:49:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA23028 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:24:02 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA23018 for ; Sun, 3 Nov 1996 15:23:53 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA07144 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:23:36 -0800 (PST) Received: from nusunix2.nus.sg (nusunix2.nus.sg [137.132.9.12]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id QAA19277 for ; Fri, 1 Nov 1996 16:24:41 -0800 (PST) Received: from leonis.nus.sg (mcblohkc@leonis.nus.sg [137.132.1.18]) by nusunix2.nus.sg (8.7.5/8.7.3) with ESMTP id IAA25311 for ; Sat, 2 Nov 1996 08:24:32 +0800 Received: from localhost (mcblohkc@localhost) by leonis.nus.sg (8.6.10/8.6.9/CNS-3.5) with SMTP id IAA09460 for ; Sat, 2 Nov 1996 08:24:31 +0800 Date: Sat, 2 Nov 1996 08:24:31 +0800 (SST) From: Loh Kir Chern 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, Suppose someone's account was deleted (because he had resigned) and he once subscribed to a Majordomo list, but he did not issue an unsubscribe before he left. Will Majordomo automatically detect such "missing" account and do an automatic unsubscribe for that account ? Or does that need the intervention of the owner or postmaster to do some manual "cleaning up" work. Thanks so much. Rgds Kir Chern Inst of Molecular And Cell Biology National University of Singapore From majordomo-users-owner Sun Nov 3 15:52:54 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22065 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:02:19 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22058 for ; Sun, 3 Nov 1996 15:02:15 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06536 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:01:58 -0800 (PST) Received: from mrknox.lanl.gov (mrknox.lanl.gov [128.165.115.90]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA18157 for ; Mon, 28 Oct 1996 09:39:21 -0800 (PST) Received: by mrknox.lanl.gov (1.37.109.16/16.2) id AA094684352; Mon, 28 Oct 1996 10:39:12 -0700 X-Sender: jmcdermo@mrknox.lanl.gov Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 28 Oct 1996 10:39:07 -0700 To: majordomo-users@GreatCircle.COM From: John McDermon Subject: help with config_parse.pl Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In v1.94, I'm trying to set my default subscription policy for all new lists as "closed". I've edited the following line in the config_parse.pl file to read: 'subscribe_policy', "open\001closed\001auto\001open+confirm\001close d+confirm\001auto+confirm\001#!\$default_subscribe_policy ? \$default_subscribe_ policy : 'closed'", I even recompiled and reinstalled, after these edits, since the #! symbol mentioned that it was eval'd. BUT every new list I set up comes back with a default subscribe_policy od open+confirm. What am I doing wrong? TIA, --John +-------------------------------------------------+ | John McDermon, voice mail 7-7315 Fax 5-1002 | | CIC-2, MS B215 cell 699-4910, page 104-8665 | +-------------------------------------------------+ From majordomo-users-owner Sun Nov 3 15:53:52 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22962 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:21:45 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22955 for ; Sun, 3 Nov 1996 15:21:42 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA07091 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:21:25 -0800 (PST) Received: from okjunc.junction.net (okjunc.junction.net [199.166.227.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA02535 for ; Fri, 1 Nov 1996 09:13:30 -0800 (PST) Received: from mauro.junction.net (ian.junction.net [204.239.30.6]) by okjunc.junction.net (8.6.11/8.6.11) with SMTP id JAA25336 for ; Fri, 1 Nov 1996 09:15:44 -0800 Date: Fri, 1 Nov 1996 09:15:44 -0800 Message-Id: <199611011715.JAA25336@okjunc.junction.net> X-Sender: mauro@junction.net (Unverified) 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: Mauro Incrocci Subject: can't unsubscribe from test list Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm using Majordomo 1.94 on an IBM running 1.2.13 Caldera as my OS. My sendmail version is 8. I have created a test list and can 'subscribe', 'who list', 'lists' but cannot 'unsubscribe' from it. The message I get back as the issuer of unsubscribe is: >>>> unsubscribe test mauro@junction.net The message I get back as the owner of the mailing list is: MAJORDOMO ABORT Can't open /majordomo/lists/test.new: Permission denied The permission of the test.new file is majordom.majordom and 660. Any help is appreciated. Mauro =-=-= From majordomo-users-owner Sun Nov 3 15:55:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22843 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:18:52 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22834 for ; Sun, 3 Nov 1996 15:18:48 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA07008 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:18:31 -0800 (PST) Received: from mrknox.lanl.gov (mrknox.lanl.gov [128.165.115.90]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id TAA27230 for ; Thu, 31 Oct 1996 19:59:43 -0800 (PST) Received: by mrknox.lanl.gov (1.37.109.16/16.2) id AA026060778; Thu, 31 Oct 1996 20:59:38 -0700 X-Sender: jmcdermo@mrknox.lanl.gov Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 31 Oct 1996 20:59:33 -0700 To: majordomo-users@GreatCircle.COM From: John McDermon Subject: changing default s*bscribe policy Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have tried editing the config_parse.pl file to change some of the default behavior for newly created lists. Everthing has been accepted, but one. I changed the default subscribe policy line to read (yes it's all on one line): 'subscribe_policy', "open\001closed\001auto\001open+confirm\001closed+confirm\001auto+confirm\001#!\ $default_subscribe_policy ? \$default_subscribe_policy : 'closed'", But new lists still are created open+confirm. I also tried changing the line and then recompiling and installing, but that didn't work either. What am I missing? TIA, --John +-------------------------------------------------+ | John McDermon, voice mail 7-7315 Fax 5-1002 | | CIC-2, MS B215 cell 699-4910, page 104-8665 | +-------------------------------------------------+ From majordomo-users-owner Sun Nov 3 15:57:14 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22237 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:04:55 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22230 for ; Sun, 3 Nov 1996 15:04:52 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06607 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:04:35 -0800 (PST) Received: from mrknox.lanl.gov (mrknox.lanl.gov [128.165.115.90]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id DAA04075 for ; Tue, 29 Oct 1996 03:20:51 -0800 (PST) Received: by mrknox.lanl.gov (1.37.109.16/16.2) id AA103358052; Tue, 29 Oct 1996 04:20:52 -0700 X-Sender: jmcdermo@mrknox.lanl.gov Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 29 Oct 1996 04:20:46 -0700 To: majordomo-users@GreatCircle.COM From: John McDermon Subject: changing default subscribe policy Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have tried editing the config_parse.pl file to change some of the default behavior for newly created lists. Everthing has been accepted, but one. I changed the default subscribe policy line to read (yes it's all on one line): 'subscribe_policy', "open\001closed\001auto\001open+confirm\001closed+confirm\001auto+confirm\001#!\ $default_subscribe_policy ? \$default_subscribe_policy : 'closed'", But new lists still are created open+confirm. I also tried changing the line and then recompiling and installing, but that didn't work either. What am I missing? TIA, --John +-------------------------------------------------+ | John McDermon, voice mail 7-7315 Fax 5-1002 | | CIC-2, MS B215 cell 699-4910, page 104-8665 | +-------------------------------------------------+ From majordomo-users-owner Sun Nov 3 15:58:44 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22319 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:07:50 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22310 for ; Sun, 3 Nov 1996 15:07:45 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06688 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:07:29 -0800 (PST) Received: from mrknox.lanl.gov (mrknox.lanl.gov [128.165.115.90]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA07177 for ; Tue, 29 Oct 1996 10:39:15 -0800 (PST) Received: by mrknox.lanl.gov (1.37.109.16/16.2) id AA106654355; Tue, 29 Oct 1996 11:39:15 -0700 X-Sender: jmcdermo@mrknox.lanl.gov Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 29 Oct 1996 11:39:13 -0700 To: majordomo-users@GreatCircle.COM From: John McDermon Subject: changing default subscribe policy Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have tried editing the config_parse.pl file to change some of the default behavior for newly created lists. Everthing has been accepted, but one. I changed the default subscribe policy line to read (yes it's all on one line): 'subscribe_policy', "open\001closed\001auto\001open+confirm\001closed+confirm\001auto+confirm\001#!\ $default_subscribe_policy ? \$default_subscribe_policy : 'closed'", But new lists still are created open+confirm. I also tried changing the line and then recompiling and installing, but that didn't work either. What am I missing? TIA, --John +-------------------------------------------------+ | John McDermon, voice mail 7-7315 Fax 5-1002 | | CIC-2, MS B215 cell 699-4910, page 104-8665 | +-------------------------------------------------+ From majordomo-users-owner Sun Nov 3 15:59:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22308 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:07:40 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22300 for ; Sun, 3 Nov 1996 15:07:36 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06682 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:07:19 -0800 (PST) Received: from mail.his.com (mail.his.com [205.177.25.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA05373 for ; Tue, 29 Oct 1996 10:18:44 -0800 (PST) Received: from localhost (kendall@localhost) by mail.his.com (8.6.9/8.6.12) with SMTP id NAA09022; Tue, 29 Oct 1996 13:09:07 -0500 Date: Tue, 29 Oct 1996 13:09:07 -0500 (EST) From: "Kendall P. Bullen" Reply-To: "Kendall P. Bullen" To: "Kent S. Larsen II" cc: Majordomo-Users@GreatCircle.COM Subject: Re: S*bscribing the list to itself 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 Tue, 29 Oct 1996, Kent S. Larsen II wrote: *I would rather keep the list in Auto and somehow exclude the list *from addresses that can be s*bscribed. I wonder if auto+confirm [requires MJ 1.94] would work? That way, people could subscribe anyone, but the subscribee would have to confirm it. WARNING: I haven't tried this, so I do NOT know if it would work. Try this with a test list, not a real, live list! :) It would be great if majordomo bounced to the list owner (simply ignoring any user command is not great, methinks) anything resembling /$LIST@$whoami/ /majordomo@.*/ And anything in majordomo.aliases. (1.94 might do this; I haven't checked -- this is just a closing comment.) Kendall From majordomo-users-owner Sun Nov 3 16:01:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22195 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:04:11 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22188 for ; Sun, 3 Nov 1996 15:04:07 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06588 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:03:51 -0800 (PST) Received: from mrknox.lanl.gov (mrknox.lanl.gov [128.165.115.90]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id QAA27515 for ; Mon, 28 Oct 1996 16:07:51 -0800 (PST) Received: by mrknox.lanl.gov (1.37.109.16/16.2) id AA099697664; Mon, 28 Oct 1996 17:07:44 -0700 X-Sender: jmcdermo@mrknox.lanl.gov Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 28 Oct 1996 17:07:39 -0700 To: majordomo-users@GreatCircle.COM From: John McDermon Subject: Comments in list file Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I would like to have a pernthetical comment in the list file so when someone gets back the response from a who command they get a line like this: jmcdermo@lanl.gov (John McDermon, CIC-2) On one majordomo server I'm on the following subscription command does the trick: approve password subscribe listname (John McDermon, CIC-2) jmcdermo@lanl.gov On my server running 1.94 it doesn't complain, it just ignores the stuff in the parenthesis. I've checked the readme and FAQ, but I didn't see anything about this. BUT I'm not sure what to acll this, so it's possible I overlooked it. TIA, --John +--------------------------+--------------------------+ | John McDermon | UNIX Team Leader | | MS B215, CIC-2 | * Macintosh bigot * | | Los Alamos National Lab | voice: (505)667-7315 | | Los Alamos, NM 87545 | cell: (505)699-4910 | | "my opinions are my own" | fax: (505)665-1002 | | http://www.lanl.gov/home/jmcdermo | +--------------------------+--------------------------+ From majordomo-users-owner Sun Nov 3 16:03:37 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21796 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:59:11 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21731 for ; Sun, 3 Nov 1996 14:58:37 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06452 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:58:20 -0800 (PST) Received: from panix.com (panix.com [198.7.0.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA20252 for ; Sun, 27 Oct 1996 07:35:35 -0800 (PST) Received: from [166.84.194.182] (nsbooks.dialup.access.net [166.84.194.182]) by panix.com (8.7.6/8.7/PanixU1.3) with ESMTP id KAA04672 for ; Sun, 27 Oct 1996 10:34:43 -0500 (EST) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 27 Oct 1996 10:02:29 -0500 To: Majordomo-Users@GreatCircle.COM From: "Kent S. Larsen II" Subject: Subscribing the list to itself Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've looked through the majordomo FAQ and other information I've been able to find on-line, but I haven't found the answer to this question. Is it possible to prevent someone from subscribing the list to itself? This comes up because on one of my lists, someone trying to subscribe put the list name in the message they sent in place of their address. Naturally, this resulted in a nasty loop (one that my service provider fortunately caught in just two hours -- on a Sunday night no less!). I have my subscription policy set to Auto. If I understand this correctly (It doesn't say what "open" is in any of the documentation), setting the policy to open will allow users to subscribe themselves, and not another address, correct? While this may solve the problem, I'm not sure its the solution I would prefer. I would rather keep the list in Auto and somehow exclude the list from addresses that can be subscribed. Any ideas? Workarounds? Corrections to my impressions? Kent S. "Kip" Larsen II; KLarsen@panix.com or KLarsen@NorthSouth.com (work). From majordomo-users-owner Sun Nov 3 16:05:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA21997 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:01:29 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA21930 for ; Sun, 3 Nov 1996 15:01:13 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06507 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:00:57 -0800 (PST) Received: from mail2.panix.com (mail2.panix.com [198.7.0.33]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA10994 for ; Mon, 28 Oct 1996 08:04:38 -0800 (PST) Received: from [166.84.194.182] (nsbooks.dialup.access.net [166.84.194.182]) by mail2.panix.com (8.7.5/8.7.1/PanixM1.0) with ESMTP id LAA27997 for ; Mon, 28 Oct 1996 11:03:36 -0500 (EST) Message-Id: Disposition-Notification-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 28 Oct 1996 10:45:51 -0500 To: Majordomo-Users@GreatCircle.COM From: "Kent S. Larsen II" Subject: Subscribing the list to itself Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've looked through the majordomo FAQ and other information I've been able to find on-line, but I haven't found the answer to this question. Is it possible to prevent someone from subscribing the list to itself? This comes up because on one of my lists, someone trying to subscribe put the list name in the message they sent in place of their address. Naturally, this resulted in a nasty loop (one that my service provider fortunately caught in just two hours -- on a Sunday night no less!). I have my subscription policy set to Auto. If I understand this correctly (It doesn't say what "open" is in any of the documentation), setting the policy to open will allow users to subscribe themselves, and not another address, correct? While this may solve the problem, I'm not sure its the solution I would prefer. I would rather keep the list in Auto and somehow exclude the list from addresses that can be subscribed. Any ideas? Workarounds? Corrections to my impressions? Kent S. "Kip" Larsen II; KLarsen@panix.com or KLarsen@NorthSouth.com (work). From majordomo-users-owner Sun Nov 3 16:06:07 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21629 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:55:16 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21622 for ; Sun, 3 Nov 1996 14:55:12 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06419 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:54:55 -0800 (PST) Received: from netop3.harvard.edu (netop3.harvard.edu [128.103.205.103]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA16557 for ; Thu, 24 Oct 1996 17:28:23 -0700 (PDT) Received: from hsph.harvard.edu (hsph.harvard.edu [128.103.75.21]) by netop3.harvard.edu (8.6.12/8.6.12) with ESMTP id UAA15607 for ; Thu, 24 Oct 1996 20:27:30 -0400 Received: by hsph.harvard.edu (SMI-8.6/SMI-SVR4) id UAA08464; Thu, 24 Oct 1996 20:28:18 -0400 Date: Thu, 24 Oct 1996 20:28:17 -0400 (EDT) From: Robert Byers To: majordomo-users@greatcircle.com Subject: The amazing shrinking subscriber list! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Over the last several weeks my MJ list included ~570 subscribers. Yesterday I happened to look at the list and it was down to only 18 subscribers. I quick scan of the Log file (which hasn't been flushed) reveals only 54 UN-subscribe requests. Folks, unless my math skills fail me, 570 - 54 does NOT equal 18 !!! That's when that all-too-common sinking feeling hit my gut :( Now, after many hours of restoring the original list, I have a few moments to think about what happened. I have to admit, I don't have much of a clue. The most likely culprit, I would say, is a panic crash our server sufferred on three occasions over the last month. Perhaps the subscriber list was open for writing at an inopportune moment. However, I would appreciate any input from list members. Has anyone experienced this problem with MJ? Or, has anyone seen MJ cause panic crashes on SunOS 4.1.3? [we never did identify what caused those crashes] My vital stats are: MJ 1.93 SunOS 4.1.3 perl 4.0.1.8 pl36 Thanks in advance, -Bob Byers HSPH Boston, MA From majordomo-users-owner Sun Nov 3 16:06:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA24591 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:56:48 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA24584 for ; Sun, 3 Nov 1996 15:56:42 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id RAA05476; Sun, 3 Nov 1996 17:56:34 -0600 (CST) To: Brian Behlendorf Cc: majordomo-users@GreatCircle.COM Subject: Re: URGENT ADVICE NEEDED! Majordomo sending old posts *again* References: From: Jason L Tibbitts III Date: 03 Nov 1996 17:56:34 -0600 In-Reply-To: Brian Behlendorf's message of Sun, 3 Nov 1996 11:53:37 -0800 (PST) Message-ID: Lines: 15 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "BB" == Brian Behlendorf writes: BB> Is a message-ID check going into mj 1.95? Someone said they had patches to do this, but I haven't actually seen them. There might be a perl4 issue, though, this patch kept the state data stored in a DBM file, and that might not be portable. As with any feature request, it stands a much larger chance of ever being done if someone contributes the code. -- Jason L. Tibbitts III - tibbs@uh.edu - 713/743-8684 - 221SR1 System Manager: University of Houston High Performance Computing Center 1994 PC800 "Kuroneko" DoD# 1723 From majordomo-users-owner Sun Nov 3 16:07:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21806 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:59:14 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21726 for ; Sun, 3 Nov 1996 14:58:36 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06446 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:58:20 -0800 (PST) Received: from sodium.Mlink.NET (sodium.Mlink.NET [205.236.182.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA19239 for ; Sat, 26 Oct 1996 17:43:20 -0700 (PDT) From: pascal@Mlink.NET Received: by sodium.Mlink.NET id UAA10795 (8.6.11/8.6.12 for majordomo-users@greatcircle.com); Sat, 26 Oct 1996 20:41:36 -0400 Message-ID: <199610270041.UAA10795@sodium.Mlink.NET> Subject: unsubscribe problem ! To: majordomo-users@greatcircle.com Date: Sat, 26 Oct 1996 20:41:34 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We are experiencing a bizarre problem with Majordomo. This problem is only occuring with a single Majorodomo list that we manage. What has happened 3-4 times in the past few months is that a subscriber to the list will unsubscribe him/herself in a legal fashion from the list, but Majordomo somehow unsubscribes EVERYONE from the list! He is an example of such a case: Oct 25 12:33:52 zinc.Mlink.NET majordomo[147] {Francois Gravel } unsubscribe blacklist Francois Gravel This last command completely nuked the subscription list. (we figured this out by copying the file every 5 minutes through a cron job to figure out when it would "disappear". Has anyone else ever encountered this problem ? If so, please drop me an email. As for the version we are running, it looks possibly old: # General subroutines for Majordomo # $Source: /sources/cvsrepos/majordomo/majordomo.pl,v $ # $Revision: 1.12.2.2.2.4 $ # $Date: 1995/01/07 17:34:27 $ # $Author: rouilj $ # $State: Exp $ # # $Header: /sources/cvsrepos/majordomo/majordomo.pl,v 1.12.2.2.2.4 1995/01/07 17 :34:27 rouilj Exp -Pascal -- +----------------------------------------------+---------------------------+ Pascal Gosselin http://www.Mlink.NET/~pascal | Mlink Internet Inc. pascal@Mlink.NET (514) 231-1923 | Montréal & Québec, Canada From majordomo-users-owner Sun Nov 3 16:10:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA24215 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:52:30 -0800 (PST) Received: from spook-le0.cia.com.au ([203.63.116.90]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA24201 for ; Sun, 3 Nov 1996 15:52:23 -0800 (PST) Received: from [203.28.48.26] (d26.cia.com.au [203.28.48.26]) by spook-le0.cia.com.au (8.7.5/8.7.3) with ESMTP id KAA17794 for ; Mon, 4 Nov 1996 10:52:15 +1100 (EST) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 4 Nov 1996 10:57:32 +1100 To: majordomo-users@greatcircle.com From: Katrina Ritchie Subject: Re: URGENT ADVICE NEEDED! Majordomo sending old posts *again* Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >On Sun, 3 Nov 1996, Bryan Fullerton wrote: >> > At 06:28 PM 11/2/96 -0500, Bryan Fullerton wrote: >> > >This happened to me today too - several posts from Wednesday of this >>week >> > >suddenly were re-sent this morning. No idea why or where they came >> > >from. Quite annoying. I'll be attempting to track it down later today >> > >> > Are you using smail? I've had this problem three times now, where the >>list >> > started sending out dozens, even hundreds of old posts going back several >> > weeks. It seems to be a smail bug, which can be stopped by rebooting the >> > mail server. >> >> Nope. sendmail 8.8.2. I'll be looking thru logs now - it's entirely >> possible that someone bounced/redirected a copy back to the list. My >> main server is still running majordomo 1.93 - my test server is running >> 1.94, and I plan to upgrade the main server in a couple of days, which >> may eliminate a whole bunch of problems. > >axionet.com has been doing this to me over the last couple of days. > Arrgghhh the bastards having been doing it to you as well! :-( With a little help from Brett (thanks again Brett :-)) we tracked downded axionet to be the source of my problems as well!!!! What to do? I will write to the postmaster, not that I'll probably hear from them. I have tried writing to postmasters at various sites, many times over different issues and have yet to receive a reply from one of them :-( Thanks for your message, great to know others have had the same prob with them. Kindest regards, Kindest Regards, Katrina (Ritchie) WELLPET List Administrator/Owner Sydney, Australia email: katrina@cia.com.au From majordomo-users-owner Sun Nov 3 16:10:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22605 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:16:05 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22598 for ; Sun, 3 Nov 1996 15:16:01 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06913 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:15:44 -0800 (PST) Received: from camco2.celestial.com (camco2.celestial.com [192.136.111.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA27702 for ; Thu, 31 Oct 1996 08:19:58 -0800 (PST) Received: by camco2.celestial.com (Smail3.1.29.1 #8) id m0vIzpb-000RXjC; Thu, 31 Oct 96 08:18 PST Message-Id: From: bill@celestial.com (Bill Campbell) Subject: Re: word "help" in the body of a message for a ML To: kendall@his.com (Kendall P. Bullen) Date: Thu, 31 Oct 1996 08:18:59 -0800 (PST) Cc: osul@mail.dotcom.fr, majordomo-users@GreatCircle.COM In-Reply-To: from "Kendall P. Bullen" at Oct 31, 96 09:22:00 am Reply-To: bill@Celestial.COM Organization: Celestial Software, Mercer Island, WA 98040 X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > >It's a feature; you have administrativa (or whatever it's called -- >the thing that checks for list commands in the first 5 lines or so) >turned on in your config file for that list. Change it from 'yes' to >'no' and that should solve your problem. Solve that problem -- and let all the subscribe/unsubscribe messages go out to the list that people send there rather than to the correct address. In our experience, probably one out of fifty of these bounces should really go to the list while the rest really are administrative requests. All you have to do is approve the message and it will go out to the list (the same way you can approve overlong messages or ones with humongous headers). Bill -- INTERNET: bill@Celestial.COM Bill Campbell; Celestial Systems, Inc. UUCP: camco!bill PO Box 820; 2835 82nd Avenue S.E. S-100 FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ Government spending? I don't know what it's all about. I don't know any more about this thing than an economist does, and, God knows, he doesn't know much. -- Will Rogers From majordomo-users-owner Sun Nov 3 16:11:08 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22508 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:13:35 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22494 for ; Sun, 3 Nov 1996 15:13:31 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06843 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:13:15 -0800 (PST) Received: from gamma.dou.dk (gamma.dou.dk [130.225.156.14]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id BAA06122 for ; Thu, 31 Oct 1996 01:02:43 -0800 (PST) Received: from dou-pc1 (peter.dou.dk [130.225.156.244]) by gamma.dou.dk (8.6.10/8.6.10) with SMTP id KAA14130 for ; Thu, 31 Oct 1996 10:02:35 +0100 Date: Thu, 31 Oct 1996 10:02:35 +0100 Message-Id: <2.2.16.19961031105259.2bdf2066@mail.dou.dk> X-Sender: maspsr@mail.dou.dk X-Mailer: Windows Eudora Pro Version 2.2 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: Peter Sorensen Subject: Returned mail: Can't create output: Error 0 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a problem with release 1.93, which I got after a reinstall of my whole system. The problem has do to with the archive facility. Somehow sendmail can't write to the archive file when the permission is 660 but require 666. I'm not sure if this is a sendmail problem, but I hope someone could give me a hint. Below the message i receive back. regards Peter Sorensen/University of Odense,dk/e-mail:maspsr@dou.ou.dk The original message was received at Thu, 31 Oct 1996 09:44:04 +0100 from majordom@localhost ----- Transcript of session follows ----- 554 /usr/local/lib/mail/majordomo/archive/test-dou/test-dou: line 0: /usr/local/lib/mail/majordomo/archive/test-dou/test-dou... cannot open: Permission denied 550 /usr/local/lib/mail/majordomo/archive/test-dou/test-dou... Can't create output: Error 0 ----- Message header follows ----- Return-Path: owner-test-dou Received: (from majordom@localhost) by gamma.dou.dk (8.6.10/8.6.10) id JAA13201 for test-dou-outgoing; Thu, 31 Oct 1996 09:44:04 +0100 Date: Thu, 31 Oct 1996 09:44:00 +0100 Message-Id: <2.2.16.19961031103423.2bdf1c44@mail.dou.dk> X-Sender: maspsr@mail.dou.dk X-Mailer: Windows Eudora Pro Version 2.2 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: test-dou@dou.dk From: Peter Sorensen Sender: owner-test-dou Errors-To: owner-test-dou Precedence: bulk Reply-To: test-dou ----- Message body suppressed ----- From majordomo-users-owner Sun Nov 3 16:12:17 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21651 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:55:42 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21642 for ; Sun, 3 Nov 1996 14:55:37 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06429 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:55:20 -0800 (PST) Received: from eclectic.kluge.net (eclectic.kluge.net [130.215.248.68]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id CAA04477 for ; Fri, 25 Oct 1996 02:25:54 -0700 (PDT) Received: from localhost (felicity@localhost) by eclectic.kluge.net (8.8.2/kluge0.5) with SMTP id FAA23948 for ; Fri, 25 Oct 1996 05:27:39 -0400 Date: Fri, 25 Oct 1996 05:27:39 -0400 (EDT) From: Theo Van Dinter To: Majordomo-Users@GreatCircle.COM Subject: Re: problems with 1.94 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, 23 Oct 1996, Theo Van Dinter wrote: > I just upgraded my MD 1.93 installation to 1.94. Unfortunately, certain > commands (currently, I've only tested unsubscribe) doesn't work. If I > send an unsubscribe command, I get the following message back: [snip] > Everything is owned by majordom, group majordomo, owner and group have > full perms on the files/directories. My question is: > > Do I want everything gid majordomo or gid daemon? Under the Makefile for > the installation, it says the GID for daemon, but under all relavent doc > files and such it says gid majordomo. > > This is obviously some simple little perm problem, but I'm not sure > exactly where/what it is. Any ideas? I believe I saw someone mention that this was in the FAQ, but ... I sort of answered my own question anyway... As mentioned on the list before, I believe, I just simply added daemon and mail (the only possible users that would run majordomo ...) to the majordomo group. Fixed the problem right up. (The only problem is that when new files are created by majordomo (new configs, etc.) the group is set to daemon, not majordomo ... Not a biggie, just takes an extra second to su and change the group, but ... 8|) -- ----------------------------------------------------------------------------- Theo Van Dinter www: http://www.kluge.net/~felicity/ Vice-President WPI Lens and Lights Active Member in SocComm and ACM Any bug not fixed in one year becomes a feature. ----------------------------------------------------------------------------- From majordomo-users-owner Sun Nov 3 16:14:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22031 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:01:48 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22024 for ; Sun, 3 Nov 1996 15:01:43 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06526 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:01:27 -0800 (PST) Received: from sparkie.osl.state.or.us (sparkie.osl.state.or.us [192.84.215.34]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA14977 for ; Mon, 28 Oct 1996 09:05:43 -0800 (PST) Received: from [192.84.215.117] (mac117.osl.state.or.us [192.84.215.117]) by sparkie.osl.state.or.us (8.6.9/8.6.9) with SMTP id JAA25344 for ; Mon, 28 Oct 1996 09:05:07 -0800 Message-Id: <199610281705.JAA25344@sparkie.osl.state.or.us> Subject: Re: how to access majordomo Date: Mon, 28 Oct 96 09:06:26 +1200 From: chris To: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk No need to apologize. You really were left with alot to figure out. You use the password to subscribe or unsubscribe individuals. The format is: approve password subscribe listname first.last@somewhere.com Send the message to majordomo@yourserver.com You need to be the listowner to submit the following commands. ** To submit new information about the list, the information that new subscribers will receive, send the following command to majordomo@yourserver.com: newinfo listname password Then add the new information that you want to submit. After the message, on a line by itself, put EOT (end of text). Send it and the information about the list will be updated. **To change the configuration file for a list, issue the command: config listname password Send it to majordomo@yourserver.com You will receive an e-mail back, containing the configuration file for the particular list. Then edit it to your liking, and send it back to majordomo@yourserver.com, with the format: newconfig list password. Your list will now have a new configuration file. Good luck! Christopher Adams >Subject: how to access majordomo >Sent: 10/29/96 3:58 AM >Received: 10/28/96 8:42 AM >From: Susan Flewelling, kmm@mis.ca >To: majordomo-users@GreatCircle.COM > >This is a very basic question and I apologize. I'm new to this list and >basically to the internet, having been on only a few months. I have a list >which was set up through Maritime Internet Services on their majordomo >system. The person who set it up is no longer there - I have the password >but no one can tell me how to access it to make changes to my mailing list. >Can anyone help or tell me how to find the info? I tried searching www (and >found this list!) but didn't really find what I needed to know. > >Thanks > >Susan Flewelling >Fredericton, N.B., Canada > From majordomo-users-owner Sun Nov 3 16:15:09 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21793 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:59:06 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21716 for ; Sun, 3 Nov 1996 14:58:36 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06437 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:58:18 -0800 (PST) Received: from camco2.celestial.com (camco2.celestial.com [192.136.111.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA16561 for ; Fri, 25 Oct 1996 09:57:26 -0700 (PDT) Received: by camco2.celestial.com (Smail3.1.29.1 #8) id m0vGpXu-000Q5SC; Fri, 25 Oct 96 09:55 PDT Message-Id: From: bill@celestial.com (Bill Campbell) Subject: Re: denying unsubscribe... To: lazlo@swcp.com (Lazlo Nibble) Date: Fri, 25 Oct 1996 09:55:46 -0700 (PDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <199610231535.JAA24452@llama.swcp.com> from "Lazlo Nibble" at Oct 23, 96 09:35:02 am Reply-To: bill@Celestial.COM Organization: Celestial Software, Mercer Island, WA 98040 X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > >> So, the "correct answer" might be: Majordomo is intended for voluntary, >> public mailing lists, and should thus allow anyone to unsubscribe, and allow >> any list member to 'who'. Other programs should be used for "broadcast" and >> private lists... Opinions on this statement? - Sarang > >Majordomo works fine for broadcast and private lists, unless your definition >of "broadcast" includes "users must not be allowed to unsubscribe themselves". >(I tend to agree with the other folks who think that if you're trying to >enforce subscriptions, the admin notification is probably a good enough tool >to let you do that.) And 1.94 supports per-list control over the "who" >command, so keeping lists completely private is a simple config option now. I don't see why this has been such a Big Deal. In our business of setting up our InterRack(rg) ISP systems around the U.S. and Canada, we always set up majordomo lists to mail to all customers based on the Unix group they belong to as well as a full list of all users (non-administrative accounts) on the system. These lists are all set up as moderated with a closed subscription policy. We set them up as moderated to prevent people spamming the ISP's customers, and to control what goes out to these lists. The lists themselves are maintained automatically in the same perl scripts that we use to keep the password databases up-to-date for the communications server's authentication databases (Xylogics Annex acp_passwd or radius users files). These are updated every fifteen minutes from cron, and any unsubscribe requests are simply ignored. Bill -- INTERNET: bill@Celestial.COM Bill Campbell; Celestial Systems, Inc. UUCP: camco!bill PO Box 820; 2835 82nd Avenue S.E. S-100 FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ Government spending? I don't know what it's all about. I don't know any more about this thing than an economist does, and, God knows, he doesn't know much. -- Will Rogers From majordomo-users-owner Sun Nov 3 16:17:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA23016 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:23:43 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA23002 for ; Sun, 3 Nov 1996 15:23:36 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA07139 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:23:19 -0800 (PST) Received: from gaia.swip.net (gaia.swip.net [193.12.122.17]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA15895 for ; Fri, 1 Nov 1996 15:35:44 -0800 (PST) Received: from s-45103.swip.net (dialup112-5-13.swipnet.se [130.244.112.113]) by gaia.swip.net (8.7.6swip/8.7.3) with SMTP id AAA07764 for ; Sat, 2 Nov 1996 00:35:36 +0100 (MET) Message-Id: <1.5.4.32.19961101233542.00675a1c@gaia.swip.net> X-Sender: mg15827@gaia.swip.net X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 02 Nov 1996 00:35:42 +0100 To: majordomo-users@greatcircle.com From: Magnus Borg Subject: help! Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello everyone! And sorry for dumping a problem in your laps... I just set up Majordomo 1.94 on a Linux system (latest Slackware distribution). Everything seems to work fine except for two things: I had to set the reply-to in the test.config file to test in order for the replies to work the way I want them (this might be normal). and I get the following warning message when sending test messages >From owner-test@www.home.kulturhuset.stockholm.se Sat Nov 2 00:21:16 1996 Received: from mn6.swip.net (mn6.swip.net [192.71.180.34]) by gaia.swip.net (8.7.6swip/8.7.3) with ESMTP id AAA06001 for ; Sat, 2 Nov 1996 00:21:15 +0100 (MET) Received: from www.home.kulturhuset.stockholm.se ([194.22.231.13]) by mn6.swip.net (8.8.2/8.8.2) with ESMTP id AAA17801 for ; Sat, 2 Nov 1996 00:21:14 +0100 (MET) Received: (from majordom@localhost) by www.home.kulturhuset.stockholm.se (8.7.5/8.7.3) id BAA02944 for test-list; Sat, 2 Nov 1996 01:05:12 +0100 X-Authentication-Warning: www.home.kulturhuset.stockholm.se: majordom set sender to owner-test@www.home.kulturhuset.stockholm.se using -f Received: from localhost (root@localhost) by www.home.kulturhuset.stockholm.se (8.7.5/8.7.3) with SMTP id BAA02939 for ; Sat, 2 Nov 1996 01:04:56 +0100 Date: Sat, 2 Nov 1996 01:04:55 +0100 (MET) From: root To: test@www.home.kulturhuset.stockholm.se Subject: fdkdlk Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-test@www.home.kulturhuset.stockholm.se Precedence: bulk Reply-To: test@www.home.kulturhuset.stockholm.se I have specified sender as owner-test in the config file, as well as in the aliases... Can anybody please help? Thanks! Magnus Borg System Administrator Kulturhuset Stockholm From majordomo-users-owner Sun Nov 3 16:17:34 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21792 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:59:03 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21711 for ; Sun, 3 Nov 1996 14:58:35 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06434 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:58:18 -0800 (PST) Received: from mailbox.neosoft.com (mailbox.neosoft.com [206.109.1.16]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA06560 for ; Fri, 25 Oct 1996 08:44:05 -0700 (PDT) Received: from nacht.neosoft.com (annabelle-ppp-15.hou.NeoWorld.net [206.109.18.31]) by mailbox.neosoft.com (8.7.5/8.7.3) with ESMTP id KAA24288 for ; Fri, 25 Oct 1996 10:43:06 -0500 (CDT) Message-Id: <199610251543.KAA24288@mailbox.neosoft.com> From: "David Reed" To: "Majordomo Users" Subject: Re: denying unsubscribe... Date: Fri, 25 Oct 1996 10:44:08 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk ---------- > From: Whitlock, Brad > To: Majordomo Users > Subject: Re: denying unsubscribe... > Date: Wednesday, October 23, 1996 4:08 AM > > Completely. It's the spam artists that want this type of feature. Some > > people also enjoy the power trip ... the knowledge that they can bombard > you > > with mail and your only out is a kill file. > Spam artists are doing just fine without this feature, unfortunately; I > threw away probably 100 unsolicited job and product offers from my > CompuServe account last night and have never subscribed to ANY mailing lists > from there. The converse of the solution above is equally true: the "needs > of the spammer" are adequately served just by being notified of > "subscribes". Save those away into another mailing list and you effectively > have the non-unsubscribe-able spamming list. Not having the feature in > majordomo doesn't stop the bad, it only gets in the way of the of good. > Leave it in, and forget trying to legislate netiquette through missing > features. Glad you brought up legislation, Brad. I just thought I'd toss out that there are already some users of majordomo who've disabled the unsub command. Democrats.org runs several mailing lists, and some joker spoofed my addy and subscribed me to the news list, but their majordomo WILL NOT respond to my unsubscribe requests... For that matter, it doesn't respond to "which" or "who" either... ;-\ Any suggestions for reporting this abuse (and stopping them from spamming me) before I resort to shipping every email address at democrats.org the entire NY phone book 10 times? Thanx. ______________________________________________________________________ David Reed $$ | webmaster@techrefuge.com $$ What do you mean by "it's all politics"? | $$ Are you trying to suggest that there has | All material and ideas $$ EVER been anything else? | are (c) David Reed, 1996 $$ | From majordomo-users-owner Sun Nov 3 16:17:55 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22469 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:11:45 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22452 for ; Sun, 3 Nov 1996 15:11:39 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06777 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:11:22 -0800 (PST) Received: from sisko.cc.rochester.edu (sisko.cc.rochester.edu [128.151.219.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id LAA11184 for ; Wed, 30 Oct 1996 11:58:53 -0800 (PST) Received: (from kenr@localhost) by sisko.cc.rochester.edu (8.7.6/8.7.3) id PAA22212 for majordomo-users@GreatCircle.COM; Wed, 30 Oct 1996 15:01:43 -0500 (EST) Date: Wed, 30 Oct 1996 15:01:43 -0500 (EST) From: Kenneth C Rich Message-Id: <199610302001.PAA22212@sisko.cc.rochester.edu> To: majordomo-users@GreatCircle.COM Subject: Re: utility: help upgrade list to 1.94 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk tested my transition config idea and it works. at least for my situation of upgrading an installation of version 1.Ancient&Unknown to version 1.94. while i think that not using it would result in few or no problems, i feel a little more secure about making the transition this way. a test list under both versions worked happily with a transition config consisting of concatenating the old version config and the version 1.94 config in that order. as for why not use writeconfig, 1.94 has to be up to use it, plus it leaves no natural backout path. i want to generate the new config before the transition. writeconfig is fine for generating a template config during the test phase off in a corner. i really like how the makefile deposits the new installation in majordomo-1.94 by the way. my utility/upgrade-hack on further investigation does not deal properly with config vars that take multi-line values. not sure if i will hack it to do so since that is a non-issue for me. maybe i can rip off the writeconfig code. a suggestion on the Makefile: if the vars whose values get compiled into the innards of wrapper were different vars than are used in the rest of the Makefile, it would be a heck of a lot easier to hack the Makefile to install into a source library. sample of the reworked Makefile available on request. thanks for the comments, and of course, i remain open to further comment. ---------------------------------------------------------------------- > i had a thought (uh-oh!) that maybe one can make a transition > configuration file by concatenating the Old and the New versions of the > list config together for each list! the old version of majordomo would > only see the variables compatible with it, & the same for the new > version. the only exception would be if you did a subscription policy > of "open+confirm" or something like that. is that the only config > variable whose range of values has changed? so the configs could > be converted ahead of time, then after upgrading majordomo, the > first half of the config file could be deleted or something, leaving the new > one only. am i making any sense? > ## preparing transition config: > upgradelist list-name ## creates listname.config.NEW > echo '#### VERSION BOUNDARY ####' >> listname.config ## just a reminder > cat listname.config.NEW >> listname.config > ## after transition (cp preserves permissions mv might trash): > cp listname.config.NEW listname.config > well, now i will go off and test my vapor...i mean idea. -- -ken rich "How many people can look at a painting for even long enough to peel an orange and eat it?" -Sir Kenneth Clark kenr@cc.rochester.edu From majordomo-users-owner Sun Nov 3 16:20:01 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22448 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:11:36 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22434 for ; Sun, 3 Nov 1996 15:11:32 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA06772 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:11:15 -0800 (PST) Received: from okjunc.junction.net (okjunc.junction.net [199.166.227.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA04066 for ; Wed, 30 Oct 1996 11:01:51 -0800 (PST) Received: from mauro.junction.net (ian.junction.net [204.239.30.6]) by okjunc.junction.net (8.6.11/8.6.11) with SMTP id LAA09011 for ; Wed, 30 Oct 1996 11:04:01 -0800 Date: Wed, 30 Oct 1996 11:04:01 -0800 Message-Id: <199610301904.LAA09011@okjunc.junction.net> X-Sender: mauro@junction.net 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: Mauro Incrocci Subject: Large Process, doesn't stop Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When I send a subscribe request to majordomo, it creates a process that does not end but grows to the point it takes up all the virtual memory on the server. I have to kill sendmail and then majordomo to stop the process. Killing majordomo results in majordomo re-spawing itself. Below is information about my setup in case someone can assist me. We are running Caldera 1.2.13 on an IBM clone with 1.94 majordomo. [request message] To:majordomo@mail.sd22.bc.ca From:mauro@junction.net Subject:Sub _________________________________ subscribe test mauro@junction.net --- [e-mail from majordomo when it is killed] X-POP3-Rcpt: mauro@okjunc Return-Path: mauro@mail.sd22.bc.ca Date: Wed, 30 Oct 1996 09:43:22 -0800 To: mauro@junction.net From: Majordomo@sd22.bc.ca Subject: Majordomo results: Sub Reply-To: Majordomo@sd22.bc.ca --- >>>> subscribe test mauro@junction.net Succeeded. ---- [sendmail.cf] # location of alias file OA/etc/aliases OA/majordomo/majordomo.aliases --- [aliases] no majordomo entries --- [majordomo.aliases] majordomo: "|/majordomo/wrapper majordomo" majordomo-owner: mauro owner-majordomo: mauro test: "|/majordomo/wrapper resend -l test test-list" test-list: :include:/majordomo/lists/test owner-test: mauro, test-owner: mauro test-request: "|/majordomo/wrapper majordomo -l test" --- [/majordomo/lists/] drwxrwxr-x 2 majordom majordom 1024 Oct 30 10:07 . drwxr-x--- 11 majordom daemon 1024 Oct 29 10:24 .. -rw-rw-r-- 1 bin bin 5 Oct 30 10:07 L.test -rw-rw-r-- 1 majordom majordom 0 Oct 28 15:30 test -rw-rw-r-- 1 bin bin 14537 Oct 29 10:53 test.config -rw-rw-r-- 1 majordom majordom 82 Oct 28 15:33 test.info --- [wrapper] [root@mail /majordomo]# ls -al wrapper -rwxrwxr-x 1 root root 17035 Oct 29 10:24 wrapper --- [perl] [root@mail /majordomo]# whereis perl perl: /usr/bin/perl /usr/bin/perl4.036 /usr/bin/perl5.003 /usr/man/man1/perl.1 --- This is perl, version 5.003 with EMBED built under linux at Sep 24 1996 09:44:00 + suidperl security patch --- [perl config-test] [root@mail /majordomo]# perl config-test --------------------- Obvious things: --------------------- ------------------ environment variables ------------------ BASH=/bin/bash DISPLAY=mail.sd22.bc.ca:0 ENV=/home/admin/.bashrc HISTFILESIZE=1000 HISTSIZE=1000 HOME=/root HOSTNAME=mail.sd22.bc.ca HOSTTYPE=i386 LOGNAME=admin MAIL=/var/spool/mail/admin PATH=/usr/local/bin:/bin:/usr/bin:/usr/bin/X11:/usr/bin/mm:/home/admin/bin PS1=[\u@\h \W]\$ SHELL=/bin/bash SHLVL=2 TERM=vt100 USERNAME= WWW_HOME=file:/etc/caldera.html _=/usr/bin/perl --------------------- euid/egid checks --------------------- effective user = root (uid 0) effective group = root wheel disk adm sys daemon bin root (gid 0 10 6 4 3 2 1 0 ) ---------------------- uid/gid checks ---------------------- real user = root (uid 0) real group = root wheel disk adm sys daemon bin root (gid 0 10 6 4 3 2 1 0 ) ----------------------------- ----------------------------- Non obvious things that cause headaches: ----------------------------- ----------------------------- Null filename used at config-test line 54. From majordomo-users-owner Sun Nov 3 16:20:20 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21805 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:59:15 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21729 for ; Sun, 3 Nov 1996 14:58:37 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06449 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:58:20 -0800 (PST) Received: from cloud.ccsf.cc.ca.us (cloud.ccsf.cc.ca.us [147.144.2.46]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id RAA18763 for ; Sat, 26 Oct 1996 17:39:49 -0700 (PDT) Received: from localhost (jjah@localhost) by cloud.ccsf.cc.ca.us (8.7.3/8.6.9) with SMTP id RAA15398 for ; Sat, 26 Oct 1996 17:37:49 -0700 (PDT) Date: Sat, 26 Oct 1996 17:37:49 -0700 (PDT) From: "Joe R. Jah" To: majordomo-users@GreatCircle.COM Subject: sendmail again Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Folks, This is not directly related to MJ, but... _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ -\<, _/ _/ _/_/_/ _/ _/ ........O/ O _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us ---------- Forwarded message ---------- Date: Mon, 21 Oct 1996 11:17:04 +1000 From: ian mcwilliam To: bsdi-users@bsdi.com Subject: sendmail again Howdy all, Just to keep you all on your toes, sendmail 8.8.1 has some problems as well, Just thought you all should know. >---------- Forwarded message ---------- >Date: Sun, 20 Oct 1996 10:35:31 +1000 (EST) >From: auscert@auscert.org.au >To: auscert-public@auscert.org.au >Subject: (Updated AUSCERT Advisory) AA-96.06a sendmail 8.8.0-8.8.1 >Vulnerability > >-----BEGIN PGP SIGNED MESSAGE----- > >=========================================================================== >AA-96.06a AUSCERT Advisory > sendmail 8.8.0-8.8.1 Vulnerability > 18 October 1996 > >Last Revised: >20-Oct-1996 Updated to include Version 8.8.1 Vulnerability > >- --------------------------------------------------------------------------- > >** This Advisory contains updated information. The new version of >** sendmail released to fix the vulnerability in sendmail Version 8.8.0 >** did not address the problem. A new version of sendmail, Version 8.8.2, >** has now been released. > >AUSCERT has received information that sendmail Versions 8.8.0 and 8.8.1 >contain a serious security vulnerability. This vulnerability allows remote >users to execute arbitrary commands on systems running the vulnerable >sendmail by sending a carefully crafted electronic mail message. Note >that this vulnerability may be exploited on systems despite the presence >of firewalls or other boundary protective measures. > >- --------------------------------------------------------------------------- > >1. Description > > A serious security vulnerability in sendmail Versions 8.8.0 and 8.8.1 > has been discovered that allows remote users to execute arbitrary > commands with root privileges. Versions prior to Version 8.8.0 do > not contain this vulnerability. Versions prior to 8.7.6 contain other > unrelated vulnerabilities. The vulnerability described in this > Advisory is exploited by sending a carefully crafted electronic mail > message to the system running the vulnerable version of sendmail. > This vulnerability may be exploited on systems despite the presence > of firewalls and other boundary protective measures. > > System are vulnerable to this attack if both of the following > conditions are true: > > 1. The version of sendmail is 8.8.0 or 8.8.1. To determine the > version of sendmail, use the following command: > > % sendmail -d0 -bt | grep Version > > If the string returned is "Version 8.8.0" or "Version 8.8.1", then > this version of sendmail contains the vulnerability. Note you > can type ^D to exit this command. > > 2. Examine the sendmail configuration file (usually, /etc/sendmail.cf). > If the '9' flag is set in the "F=" (Flags) section for any Mailer > specifications (Sections starting with 'M' in the first column, > such as "Mprog" or "Mlocal"), then this configuration is > vulnerable. Use of the '9' flag can usually be determined using > the following command (depending on your sendmail configuration): > > % grep '^M' /etc/sendmail.cf | grep '9' > > If any lines are output from this command, then the sendmail > configuration may be vulnerable. > > The use of the '9' flag in the sendmail configuration is documented > only in the Release Notes. This flag is set by default if the > sendmail.cf file was generated from the sendmail Version 8.8.x > distribution files using m4(1). Previous versions of sendmail did > not set this flag by default when the sendmail.cf file was generated. > The '9' flag is also set by default in the precompiled example > configuration files found in the cf/cf/obj/ subdirectory of the > sendmail Version 8.8.x distribution. > >2. Impact > > Remote users may execute arbitrary commands as root on systems using > the vulnerable sendmail. This may be leveraged to gain root access. > >3. Workarounds/Solution > > AUSCERT recommends that sendmail Version 8.8.2 be installed immediately > (see Section 3.1). For sites that can not install sendmail Version > 8.8.2 immediately, apply the workaround described in Section 3.2. > >3.1 Upgrade to sendmail version 8.8.2. > > Eric Allman has released a new version of sendmail which fixes this > vulnerability. This can be obtained from the following locations: > > ftp://ftp.sendmail.org/ucb/src/sendmail/ > ftp://ftp.auscert.org.au/pub/mirrors/ftp.cs.berkeley.edu/ucb/sendmail/ > ftp://ftp.cert.dfn.de/pub/tools/net/sendmail/ > ftp://ftp.cert.org/pub/tools/sendmail/ > > The MD5 checksum for this distribution is: > > MD5 (sendmail.8.8.2.patch) = a3fdf7ea9967064e2b00f7796a87dfd9 > MD5 (sendmail.8.8.2.tar.gz) = 7ba82d2008a40337bc5828a77694f66e > MD5 (sendmail.8.8.2.tar.sig) = 3b1765110818cf1ab3cec33e825479cb > MD5 (sendmail.8.8.2.tar.Z) = 183b7d3461af7735bf2f9b2c17526476 > >3.2 Workaround for existing sendmail Version 8.8.0 and 8.8.1 installations > > AUSCERT has been advised that the following workaround removes the > vulnerability described in this Advisory. > > The /etc/sendmail.cf file should be modified to remove the use of the > '9' flag for all Mailer specifications (lines starting with 'M'). > > For example, the sendmail.cf file should look similar to (depending > on your system and configuration): > >Mlocal, P=/usr/libexec/mail.local, F=lsDFMAw5:/|@qrmn, S=10/30, >R=20/40, > T=DNS/RFC822/X-Unix, > A=mail -d $u >Mprog, P=/bin/sh, F=lsDFMoqeu, S=10/30, R=20/40, > D=$z:/, > T=X-Unix, > A=sh -c $u > > This can be achieved for the "Mlocal" and "Mprog" Mailers by modifying > the ".mc" file to include the following lines: > > define(`LOCAL_MAILER_FLAGS', > ifdef(`LOCAL_MAILER_FLAGS', > `translit(LOCAL_MAILER_FLAGS, `9')', > `rmn')) > define(`LOCAL_SHELL_FLAGS', > ifdef(`LOCAL_SHELL_FLAGS', > `translit(LOCAL_SHELL_FLAGS, `9')', > `eu')) > > and then rebuilding the sendmail.cf file using m4(1). > > It is possible to directly edit the sendmail.cf file to resolve this > vulnerability. However, caution must be taken to ensure that the > sendmail.cf file is not replaced in the future with a new version > rebuilt from configuration files that include the '9' flag. > > Once the configuration file has been modified, all running versions > of sendmail should be killed and the sendmail daemon restarted, or > the system rebooted, for these changes to take effect. > >4. Additional Measures > > This section describes some additional measures for increasing the > security of sendmail in general. It is unrelated to the vulnerability > described in this Advisory. Sites must apply the Workarounds/Solution > described in Section 3 first, and then optionally apply additional > measures described in this Section. > >4.1 Restrict Ability to Mail to Programs > > If the ability to send electronic mail to programs (for example, > vacation programs) is not required, this feature should be disabled. > This is achieved by modifying the "Mprog" line in the configuration > file to mail to "/bin/false" rather than "/bin/sh". The following > line in the ".mc" file will achieve this: > > define(`LOCAL_SHELL_PATH', `/bin/false')dnl > > If mailing to programs is required, it is recommended that the sendmail > restricted shell, smrsh, be used at all times. This applies to all > versions of sendmail, including vendor versions. smrsh is supplied > with the sendmail 8.8.2 distribution and includes documentation and > installation instructions. > >- --------------------------------------------------------------------------- >AUSCERT thanks Eric Allman for his rapid response to this vulnerability, >and Wolfgang Ley from the DFN-CERT team for technical input to this >Advisory. >- --------------------------------------------------------------------------- > >The AUSCERT team have made every effort to ensure that the information >contained in this document is accurate. However, the decision to use the >information described is the responsibility of each user or organisation. >The appropriateness of this document for an organisation or individual >system should be considered before application in conjunction with local >policies and procedures. AUSCERT takes no responsibility for the >consequences of applying the contents of this document. > >If you believe that your system has been compromised, contact AUSCERT or >your representative in FIRST (Forum of Incident Response and Security >Teams). > >AUSCERT is located at The University of Queensland within the Prentice >Centre. AUSCERT is a full member of the Forum of Incident Response and >Security Teams (FIRST). > >AUSCERT maintains an anonymous FTP service which is found on: >ftp://ftp.auscert.org.au/pub/. This archive contains past SERT and AUSCERT >Advisories, and other computer security information. > >AUSCERT also maintains a World Wide Web service which is found on: >http://www.auscert.org.au/. > >Internet Email: auscert@auscert.org.au >Facsimile: (07) 3365 4477 >Telephone: (07) 3365 4417 (International: +61 7 3365 4417) > AUSCERT personnel answer during Queensland business hours > which are GMT+10:00 (AEST). > On call after hours for emergencies. > >Postal: >Australian Computer Emergency Response Team >c/- Prentice Centre >The University of Queensland >Brisbane >Qld. 4072. >AUSTRALIA > > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >Revision History > >20-Oct-1996. Revision a. Sendmail Version 8.8.1 did not adequately > address the problem. A new version (8.8.2) has now been released. > Advisory updated to reflect these changes. Added ftp.cert.org to > mirror site as Version 8.8.2 is now there. > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >-----BEGIN PGP SIGNATURE----- >Version: 2.6.3i >Charset: noconv >Comment: ftp://ftp.auscert.org.au/pub/auscert/AUSCERT_PGP.key > >iQCVAwUBMmoAYyh9+71yA2DNAQEomAP/dmfNJFhF5mG8WgVjVEVfNzqN94IF5lfX >WL1haADOd9Tp+4d5Zf2gwJUOrHTfMBGqUxf2r4EUQqMLVMTmuMQp7Ob8XNbRBNZc >i/jGA19DRfNWnbhEbGXqC9oY5Ev5Phx+OYI2ItBn4ppt2ljsluTZCeQdycjfJig+ >Et25ix0c378= >=WgTX >-----END PGP SIGNATURE----- Catch ya, ____________________________________________________________________________ Ian McWilliam. Technical Officer, Faculty of Science & Technology, Dept. of Computing. University of Western Sydney, NEPEAN. P.O.Box 10 Kingswood, N.S.W, Australia. 2560. (047) 360 757 ____________________________________________________________________________ People Get Lost in Thought 'cause it's Unknown Territory. CHIP - Found on the shoulders of Systems Support Personnel. It becomes Most evident when some fool claims that the computer has made a mistake!!!! ____________________________________________________________________________ E-Mail: ianm@st.nepean.uws.edu.au i.mcwilliam@st.nepean.uws.edu.au From majordomo-users-owner Sun Nov 3 16:47:46 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA26968 for majordomo-users-outgoing; Sun, 3 Nov 1996 16:31:43 -0800 (PST) Received: from iquest.net (iquest4.iquest.net [206.53.230.100]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id QAA26931 for ; Sun, 3 Nov 1996 16:31:21 -0800 (PST) Received: by iquest.net (Smail3.1.29.1 #5) id m0vKCwQ-003iLsC; Sun, 3 Nov 96 19:31 EST Received: (from alt@localhost) by aen.aen.org (8.6.12/8.6.12) id SAA00850; Sun, 3 Nov 1996 18:59:39 -0500 Date: Sun, 3 Nov 1996 18:59:39 -0500 (EST) From: Al Thompson To: majordomo-users@greatcircle.com Subject: Weird configuration problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I recently put Majordomo 1.93 up, and it works fine, except for one small, mostly cosmetic thing. When I address a h*lp message to 'majordomo@aen.org,' I receive a response from: Date: Sun, 3 Nov 1996 18:51:42 -0500 From: Majordomo.org@aen.org To: alt@aen.org Subject: Majordomo results And in the body of the h*lp message, there are these two lines: ------ Commands should be sent in the body of an email message to "Majordomo.org". If you have any questions or problems, please contact "list-owner.org". ---------- Can anyone give me a clue where to look? I've studied majordomo.cf, and there's nothing in it that looks like it could be causing this. Any assistance would be appreciated. Thanks From majordomo-users-owner Sun Nov 3 17:47:35 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA06889 for majordomo-users-outgoing; Sun, 3 Nov 1996 17:40:55 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id RAA06865 for ; Sun, 3 Nov 1996 17:40:45 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id TAA07221; Sun, 3 Nov 1996 19:40:35 -0600 (CST) To: "Kendall P. Bullen" Cc: "Kent S. Larsen II" , Majordomo-Users@GreatCircle.COM Subject: Re: S*bscribing the list to itself References: From: Jason L Tibbitts III Date: 03 Nov 1996 19:40:35 -0600 In-Reply-To: "Kendall P. Bullen"'s message of Tue, 29 Oct 1996 13:09:07 -0500 (EST) Message-ID: Lines: 12 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "KPB" == Kendall P Bullen writes: KPB> I wonder if auto+confirm [requires MJ 1.94] would work? Yes it would, but his server was unfortunately still at 1.93. KPB> It would be great if majordomo bounced to the list owner (simply KPB> ignoring any user command is not great, methinks) anything resembling Soon (i.e. next couple of versions). Not in 1.94, though. - J< From majordomo-users-owner Sun Nov 3 17:51:41 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA07064 for majordomo-users-outgoing; Sun, 3 Nov 1996 17:45:31 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id RAA07050 for ; Sun, 3 Nov 1996 17:45:23 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id TAA07257; Sun, 3 Nov 1996 19:45:24 -0600 (CST) To: John McDermon Cc: majordomo-users@GreatCircle.COM Subject: Re: changing default s*bscribe policy References: From: Jason L Tibbitts III Date: 03 Nov 1996 19:45:24 -0600 In-Reply-To: John McDermon's message of Thu, 31 Oct 1996 20:59:33 -0700 Message-ID: Lines: 14 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "JM" == John McDermon writes: JM> I have tried editing the config_parse.pl file to change some of the JM> default behavior for newly created lists. Everthing has been accepted, JM> but one. Why? Just set $config'default_subscribe_policy = "open+confirm"; in majordomo.cfg. (1.94 only.) That's why the weird trinary conditional is there: to let it pick up the default from the config file. This unfortunately only applies to subscribe_policy, but there will be provisions setting all defaults in future versions. - J< From majordomo-users-owner Sun Nov 3 18:32:43 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA08418 for majordomo-users-outgoing; Sun, 3 Nov 1996 18:18:58 -0800 (PST) Received: from clarknet.clark.net (clarknet.clark.net [168.143.0.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id SAA08364 for ; Sun, 3 Nov 1996 18:18:38 -0800 (PST) Received: by clarknet.clark.net (5.0/SMI-SVR4) id AA15546; Sun, 3 Nov 1996 21:18:05 +0500 >Received: from shaknet.clark.net (alan_s@localhost [127.0.0.1]) by shaknet.clark.net (8.6.12/8.6.9) with SMTP id TAA00360; Sun, 3 Nov 1996 19:43:13 -0500 Date: Sun, 3 Nov 1996 19:43:12 -0500 (EST) From: "Alan V. Shackelford" To: Roger Morris Cc: majordomo-users@greatcircle.com Subject: Re: Digests In-Reply-To: <199610260421.VAA29325@haus.efn.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 25 Oct 1996, Roger Morris wrote: > Hi, I have a problem with the digest that I set up. > The digests are being created, I can see them in the list.archive > directory. The digest is not being mailed out. > If I send majordomo the command > mkdigest > the digest goes out. > Is there something in the alias file that I have configured wrong? That's probably where the trouble lies, but can't be sure without the alias file to examine. You want to make sure that it looks something like this: listname-digest: listname listname-digest-outgoing: :include:/home/majordomo/lists/listname-digest listname-digest-digestify: "| /home/majordomo/majordomo-1.93/wrapper\ digest -r -C -l listname-digest\ listname-digest-outgoing" owner-listname-digest-outgoing: somebody@some.domain The first line just ensures that if someone accidentally posts to the digest, it will go to the list instead. The rest is the get-it-done part. The \ indicates that the line is really continued all on one line (vi likes this, joe doesn't). Good luck. Alan One net to rule them all, one net to find them, one net to bring them all and using Unix bind them. alan_s@shaknet.clark.net From majordomo-users-owner Sun Nov 3 21:18:17 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA15784 for majordomo-users-outgoing; Sun, 3 Nov 1996 21:05:50 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id VAA15777 for ; Sun, 3 Nov 1996 21:05:45 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id XAA10285; Sun, 3 Nov 1996 23:05:46 -0600 (CST) To: Al Thompson Cc: majordomo-users@GreatCircle.COM Subject: Re: Weird configuration problem References: From: Jason L Tibbitts III Date: 03 Nov 1996 23:05:45 -0600 In-Reply-To: Al Thompson's message of Sun, 3 Nov 1996 18:59:39 -0500 (EST) Message-ID: Lines: 9 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "AT" == Al Thompson writes: AT> ------ Commands should be sent in the body of an email message to AT> "Majordomo.org". It looks to me like you might be using perl5 and you might have neglected to escape an `@' symbol with a backslash. - J< From majordomo-users-owner Sun Nov 3 21:23:08 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA15703 for majordomo-users-outgoing; Sun, 3 Nov 1996 21:02:22 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id VAA15696 for ; Sun, 3 Nov 1996 21:02:16 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id XAA10243; Sun, 3 Nov 1996 23:02:00 -0600 (CST) To: "Kent S. Larsen II" Cc: Majordomo-Users@GreatCircle.COM Subject: Re: Subscribing the list to itself References: From: Jason L Tibbitts III Date: 03 Nov 1996 23:01:59 -0600 In-Reply-To: "Kent S. Larsen II"'s message of Mon, 28 Oct 1996 10:45:51 -0500 Message-ID: Lines: 24 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "KSL" == Kent S Larsen writes: KSL> Is it possible to prevent someone from subscribing the list to itself? 1.94 will complain about zubscribe test-list test-list (I think this is new) but unfortunately it allows zubscribe test-list test-list@your.host.name The real solution (outside of hacking the source) is to either use zubscribe_policy = "open" or "auto+confirm". If you have an auto list, you are just asking to be zubscribe-bombed. This is not fun. The real answer is to allow a set of regular expressions that, if matched, will prevent the address from subscribing. The problem with that is that you can't just disallow, say, /^$listname\@/; I have plenty of addresses on my list that start with the listname. If you have a pile of domains that map to the same host you'll understand why this is a problem. So it has to be a config option. - J< From majordomo-users-owner Sun Nov 3 22:47:34 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id WAA18408 for majordomo-users-outgoing; Sun, 3 Nov 1996 22:43:22 -0800 (PST) Received: from rollercoaster.com (tmb.extern.ucsd.edu [137.110.120.81]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id WAA18401 for ; Sun, 3 Nov 1996 22:43:13 -0800 (PST) Received: from tmb2.extern.ucsd.edu (tmb2.extern.ucsd.edu [137.110.120.82]) by rollercoaster.com (8.7.6/8.7.3) with SMTP id WAA02459; Sun, 3 Nov 1996 22:42:19 -0800 Message-Id: <3.0.32.19961103224211.00698cf0@rollercoaster.com> X-Sender: jim@rollercoaster.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 03 Nov 1996 22:42:16 -0800 To: tibbs@hpc.uh.edu From: Jim Serio Subject: Majordomo 1.94 'make install' problem Cc: majordomo-users@greatcircle.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I just upgraded to Red Hat 4.0 and am now running the 2.0.18 kernel, so, even though I copied (backed-up) my old majordomo files I decided to just install 1.94. I modified the Makefile to reflect the newly created majordom user, UID=501 and GID=2 (daemon). After running make install, I get the following error: ----- [root@rollercoaster majordomo-1.94]# make install Testing for perl (/usr/bin/perl)... Configuring scripts... chown: :2: No such file or directory Hmmm, if /usr/local/sbin/majordomo doesn't have an owner and group of 501 2, do a chown 501 :2 /usr/local/sbin/majordomo (as root.) drwxr-x--- 3 501 0 1024 Nov 3 21:23 /usr/local/sbin/majordomo Copying tools to /usr/local/sbin/majordomo/bin chown: :2: No such file or directory chown: :2: No such file or directory mchown: :2: No such file or directory amake: *** [install-scripts] Error 1 ---- I then check the newly created dir and find it: drwxr-x--- 3 majordom root 1024 Nov 3 21:23 majordomo I do a chown 501:2 majordomo and get: drwxr-x--- 3 majordom daemon 1024 Nov 3 21:23 majordomo Still a make install gives me the same above error. What up with that? Jim -- Jim Serio jim@rollercoaster.com World of Coasters http://www.rollercoaster.com The Web's Premier Coaster Site! From majordomo-users-owner Mon Nov 4 05:47:48 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA11370 for majordomo-users-outgoing; Mon, 4 Nov 1996 05:42:59 -0800 (PST) Received: from wisdom.lakecumberland.com (lakecumberland.com [206.112.195.92]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id FAA11345 for ; Mon, 4 Nov 1996 05:42:50 -0800 (PST) Received: from AWNC2 (iware.belcan.com [192.131.246.9]) by wisdom.lakecumberland.com (8.7.6/8.7.3) with SMTP id IAA26236 for ; Mon, 4 Nov 1996 08:42:46 -0500 Message-Id: <2.2.16.19961104134249.2117af90@lakecumberland.com> X-Sender: mitch@lakecumberland.com X-Mailer: Windows Eudora Pro Version 2.2 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Nov 1996 08:42:49 -0500 To: majordomo-users@greatcircle.com From: "Mitchell B. Hamm" Subject: Upgrading to 1.94 Release Version Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello All, Please excuse the quick post; I've just joined your list, but I did read through the FAQ. I also tried to find a working search engine into your archives, but could not. So, I have a question... System: Caldera Linux on kernel 2.0.24 Majordomo Version: 1.94 Release I have been running an alpha version (3 I think) of 1.94 for a couple of months with very little problem, but figured that I should upgrade to the final version. I grabbed the new source, configured it to use the same user/group and directories as my other majordomo and installed it. The ./wrapper config-test gave me an all clear. I set up a test list with the same type of configuration as my current list, but gave the new majordomo an alias of "testdomo". I then rebuilt my sendmail aliases and issued an "echo 'lists' |mail testdomo" to the new version. Here's where the trouble starts. I have a performance monitor running on my X server and as soon as that mail gets sent, I can watch all my running processes get swapped to disk. When the swap fills, the memory fills and then the processor gets overwhelmed. Top shows the CPU usage at around 97% with all resources being used by majordomo. The only way out is to kill the process. I have triple-checked all my permissions and they are good. The old list continues to function just fine. What is causing this new version to swamp my system? Thanks! Mitch Hamm From majordomo-users-owner Mon Nov 4 06:18:12 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA13325 for majordomo-users-outgoing; Mon, 4 Nov 1996 06:07:29 -0800 (PST) Received: from splat.niehs.nih.gov (splat.niehs.nih.gov [157.98.9.238]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA13307 for ; Mon, 4 Nov 1996 06:07:19 -0800 (PST) Received: from splat.niehs.nih.gov (labrown@localhost [127.0.0.1]) by splat.niehs.nih.gov (8.8.2/8.8.2) with ESMTP id JAA13916; Mon, 4 Nov 1996 09:06:57 -0500 (EST) To: Jim Serio cc: tibbs@hpc.uh.edu, majordomo-users@greatcircle.com Subject: Re: Majordomo 1.94 'make install' problem In-reply-to: Your message of "Mon, 04 Nov 1996 01:42:16 EST." <3.0.32.19961103224211.00698cf0@rollercoaster.com> Date: Mon, 04 Nov 1996 09:06:56 -0500 Message-ID: <13913.847116416@splat.niehs.nih.gov> From: "Lance A. Brown" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Make sure you doon't have any extraneous spaces or tabs FOLLOWING the assignment of the UID number in your Makefile. This bit me too. :-) --[Lance] From majordomo-users-owner Mon Nov 4 06:53:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA15378 for majordomo-users-outgoing; Mon, 4 Nov 1996 06:34:48 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA15349 for ; Mon, 4 Nov 1996 06:34:33 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA24840 for majordomo-users@GreatCircle.COM; Mon, 4 Nov 96 07:34:32 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA24858 for majordomo-users@GreatCircle.COM; Mon, 4 Nov 96 07:34:31 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id IAA15666; Mon, 4 Nov 1996 08:34:31 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id IAA11481; Mon, 4 Nov 1996 08:34:29 -0600 From: Dave Wolfe Message-Id: <199611041434.IAA11481@miaow.risc.sps.mot.com> Subject: Re: help with config_parse.pl To: jmcdermo@lanl.gov (John McDermon) Date: Mon, 4 Nov 1996 08:34:28 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "John McDermon" at Oct 28, 96 10:39:07 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ John McDermon writes: ] > > In v1.94, I'm trying to set my default subscription policy for all new > lists as "closed". > > I've edited the following line in the config_parse.pl file to read: > 'subscribe_policy', > "open\001closed\001auto\001open+confirm\001close > d+confirm\001auto+confirm\001#!\$default_subscribe_policy ? > \$default_subscribe_ > policy : 'closed'", > > I even recompiled and reinstalled, after these edits, since the #! symbol > mentioned that it was eval'd. BUT every new list I set up comes back with a > default subscribe_policy od open+confirm. > > What am I doing wrong? No need to mess with config_parse.pl, just uncomment and edit the line in your majordomo.cf: # Set the default subscribe policy for new lists here. # If not defined, defaults to "open", but in today's increasingly # imbecile Internet, "open+confirm" or "auto+confirm" is a wiser # choice for publicly available Majordomo servers. # # $config'default_subscribe_policy = "open+confirm"; $config'default_subscribe_policy = "closed"; -- Dave Wolfe From majordomo-users-owner Mon Nov 4 07:03:10 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA16697 for majordomo-users-outgoing; Mon, 4 Nov 1996 06:53:18 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA16681 for ; Mon, 4 Nov 1996 06:53:09 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA27925 for majordomo-users@GreatCircle.COM; Mon, 4 Nov 96 07:53:08 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA25465 for majordomo-users@GreatCircle.COM; Mon, 4 Nov 96 07:53:04 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id IAA15868; Mon, 4 Nov 1996 08:53:03 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id IAA18686; Mon, 4 Nov 1996 08:53:01 -0600 From: Dave Wolfe Message-Id: <199611041453.IAA18686@miaow.risc.sps.mot.com> Subject: Re: Comments in list file To: jmcdermo@lanl.gov (John McDermon) Date: Mon, 4 Nov 1996 08:53:01 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "John McDermon" at Oct 28, 96 05:07:39 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ John McDermon writes: ] > > I would like to have a pernthetical comment in the list file so when > someone gets back the response from a who command they get a line like this: > > jmcdermo@lanl.gov (John McDermon, CIC-2) > > On one majordomo server I'm on the following subscription command does the > trick: > approve password subscribe listname (John McDermon, CIC-2) jmcdermo@lanl.gov > > On my server running 1.94 it doesn't complain, it just ignores the stuff in > the parenthesis. I've checked the readme and FAQ, but I didn't see anything > about this. BUT I'm not sure what to acll this, so it's possible I > overlooked it. See the 'strip' parameter in the list .config file. -- Dave Wolfe From majordomo-users-owner Mon Nov 4 07:09:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA16463 for majordomo-users-outgoing; Mon, 4 Nov 1996 06:51:32 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA16454 for ; Mon, 4 Nov 1996 06:51:24 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA27368 for majordomo-users@GreatCircle.COM; Mon, 4 Nov 96 07:51:24 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA25429 for majordomo-users@GreatCircle.COM; Mon, 4 Nov 96 07:51:20 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id IAA15855; Mon, 4 Nov 1996 08:51:19 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id IAA18674; Mon, 4 Nov 1996 08:51:17 -0600 From: Dave Wolfe Message-Id: <199611041451.IAA18674@miaow.risc.sps.mot.com> Subject: Re: utility: help upgrade list to 1.94 To: kenr@sisko.cc.rochester.edu (Kenneth C Rich) Date: Mon, 4 Nov 1996 08:51:17 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199610302001.PAA22212@sisko.cc.rochester.edu> from "Kenneth C Rich" at Oct 30, 96 03:01:43 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Kenneth C Rich writes: ] > > as for why not use writeconfig, 1.94 has to be up to use it, plus it > leaves no natural backout path. i want to generate the new config > before the transition. writeconfig is fine for generating a template > config during the test phase off in a corner. Just install 1.94 in a new place (I'd recommend this anyway) and temporarily use a different alias for 1.94 majordomo. Copy the old list files into the 1.94 list directory and send the writeconfigs to the temporary 1.94 alias. Once you're satisfied that the Mj commands work, save off the list aliases, edit the paths to point to the 1.94 installation (including the majordomo aliases), run newaliases, and verify that posting to the lists works. That leaves the old installation intact and you can switch back by just restoring the old aliases. The only hang out is Mj command activity during the 1.94 test if you decide to go back. > my utility/upgrade-hack on further investigation does not deal properly > with config vars that take multi-line values. not sure if i will > hack it to do so since that is a non-issue for me. maybe i can rip > off the writeconfig code. Just FYI, that's easy to do: [...] require 'config_parse.pl'; [...] &get_config($listdir, $list); # Creates a default file Simulating a 'writeconfig' should be just as easy. -- Dave Wolfe From majordomo-users-owner Mon Nov 4 07:22:20 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA19006 for majordomo-users-outgoing; Mon, 4 Nov 1996 07:15:37 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA18972 for ; Mon, 4 Nov 1996 07:15:10 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id KAA29177; Mon, 4 Nov 1996 10:15:03 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id KAA10413; Mon, 4 Nov 1996 10:15:00 -0500 (EST) Message-Id: <199611041515.KAA10413@augusta.math.psu.edu> To: "Scott C. Villinski" cc: "'Majordomo-Users@greatcircle.com'" Subject: Re: Majordomo 1.94, setuid and permissions In-reply-to: Your message of "Sun, 03 Nov 1996 10:57:06 CST." References: 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: Mon, 04 Nov 1996 10:14:59 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , "Scott C. Villinski" writes: >bin:bin. Any thoughts? Try reading the Majordomo FAQ section on setting up permissions. It should be able to help you debug what's going on. I suspect that there's some confusion going on with your wrapper, it may have been compiled incorrectly. (with the wrong uid/gid) --Dave From majordomo-users-owner Mon Nov 4 07:29:00 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA18851 for majordomo-users-outgoing; Mon, 4 Nov 1996 07:14:17 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA18826 for ; Mon, 4 Nov 1996 07:14:07 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA01440 for majordomo-users@greatcircle.com; Mon, 4 Nov 96 08:14:07 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA26228 for majordomo-users@greatcircle.com; Mon, 4 Nov 96 08:14:05 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA16311; Mon, 4 Nov 1996 09:14:04 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA13422; Mon, 4 Nov 1996 09:14:02 -0600 From: Dave Wolfe Message-Id: <199611041514.JAA13422@miaow.risc.sps.mot.com> Subject: Re: help! To: mborg@adm.kulturhuset.stockholm.se (Magnus Borg) Date: Mon, 4 Nov 1996 09:14:02 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <1.5.4.32.19961101233542.00675a1c@gaia.swip.net> from "Magnus Borg" at Nov 2, 96 00:35:42 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Magnus Borg writes: ] > > I just set up Majordomo 1.94 on a Linux system (latest Slackware > distribution). Everything seems to work fine except for two things: I > had to set the reply-to in the test.config file to test in order for > the replies to work the way I want them (this might be normal). and I > get the following warning message when sending test messages [...] > X-Authentication-Warning: www.home.kulturhuset.stockholm.se: majordom set > sender to owner-test@www.home.kulturhuset.stockholm.se using -f You need to make majordom a trusted user in your sendmail.cf. -- Dave Wolfe From majordomo-users-owner Mon Nov 4 07:33:57 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA17886 for majordomo-users-outgoing; Mon, 4 Nov 1996 07:02:47 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA17871 for ; Mon, 4 Nov 1996 07:02:32 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA29643 for majordomo-users@greatcircle.com; Mon, 4 Nov 96 08:02:31 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA25841 for majordomo-users@greatcircle.com; Mon, 4 Nov 96 08:02:27 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA16100; Mon, 4 Nov 1996 09:02:26 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA11572; Mon, 4 Nov 1996 09:02:24 -0600 From: Dave Wolfe Message-Id: <199611041502.JAA11572@miaow.risc.sps.mot.com> Subject: Re: Returned mail: Can't create output: Error 0 To: maspsr@dou.ou.dk (Peter Sorensen) Date: Mon, 4 Nov 1996 09:02:23 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <2.2.16.19961031105259.2bdf2066@mail.dou.dk> from "Peter Sorensen" at Oct 31, 96 10:02:35 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Peter Sorensen writes: ] > > I have a problem with release 1.93, which I got after a reinstall of > my whole system. The problem has do to with the archive facility. > Somehow sendmail can't write to the archive file when the permission > is 660 but require 666. I'm not sure if this is a sendmail problem, > but I hope someone could give me a hint. Below the message i receive > back. [...] > ----- Transcript of session follows ----- > 554 /usr/local/lib/mail/majordomo/archive/test-dou/test-dou: line 0: > /usr/local/lib/mail/majordomo/archive/test-dou/test-dou... cannot open: > Permission denied Sounds like you're trying to have sendmail just deliver to a file in your archive directory, but we'd have to see your aliases to know for sure. If that's the case, then of course sendmail has problems unless the archive directory owner or group matches sendmail's. -- Dave Wolfe From majordomo-users-owner Mon Nov 4 07:37:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA19842 for majordomo-users-outgoing; Mon, 4 Nov 1996 07:23:24 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA19828 for ; Mon, 4 Nov 1996 07:23:17 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA03066 for Majordomo-Users@GreatCircle.COM; Mon, 4 Nov 96 08:23:15 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA26617 for Majordomo-Users@GreatCircle.COM; Mon, 4 Nov 96 08:23:14 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA16436; Mon, 4 Nov 1996 09:23:13 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA13966; Mon, 4 Nov 1996 09:23:11 -0600 From: Dave Wolfe Message-Id: <199611041523.JAA13966@miaow.risc.sps.mot.com> Subject: Re: archive files To: sandrac@reduno.com.mx (SANDRA CEJUDO FUNES) Date: Mon, 4 Nov 1996 09:23:11 -0600 (CST) Cc: Majordomo-Users@GreatCircle.COM In-Reply-To: from "SANDRA CEJUDO FUNES" at Nov 1, 96 06:25:06 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ SANDRA CEJUDO FUNES writes: ] > > When I post to majordomo the index command to my list prueba1, it said > that there's no files available, but there are two files in the archive > directory. > > What'is wrong? What's wrong is that you give us almost *no* information to go on. But I'll propose some things for you to check. Does Mj have permission to read/search your archive directory path? Do you have 'private_index' set but are not a subscriber to the list? Do you have a .private file (that sets 'private_index')? Do your '$filedir', '$filedir_suffix', and '@archive_dirs' in majordomo.cf and what you think is the archive directory all match up? -- Dave Wolfe From majordomo-users-owner Mon Nov 4 07:54:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA21451 for majordomo-users-outgoing; Mon, 4 Nov 1996 07:37:27 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA21406 for ; Mon, 4 Nov 1996 07:37:12 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA06241 for majordomo-users@greatcircle.com; Mon, 4 Nov 96 08:36:42 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA27290 for majordomo-users@greatcircle.com; Mon, 4 Nov 96 08:36:25 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA16615; Mon, 4 Nov 1996 09:36:24 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA14275; Mon, 4 Nov 1996 09:36:23 -0600 From: Dave Wolfe Message-Id: <199611041536.JAA14275@miaow.risc.sps.mot.com> Subject: Re: trouble getting approve command working To: dts@senie.com (Daniel Senie) Date: Mon, 4 Nov 1996 09:36:22 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Daniel Senie" at Nov 2, 96 00:05:45 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Daniel Senie writes: ] > > I've got a list working well, but now find that the approve command > doesn't work. I get responses from majordomo that the list name is unknown > or that the password is incorrect, but am having trouble tracking down > which it is. > > The log file shows me making "help" requests instead of showing anything > useful for debugging the problem. > > Could someone offer a clue as to where to start debugging this problem? It'd help if you'd show us some samples of what you're doing and replies and what version of Mj you're running. Short of repeating the documentation there's nothing I can suggest because you don't give me enough to go on to even guess what you're doing wrong. -- Dave Wolfe From majordomo-users-owner Mon Nov 4 08:03:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA23662 for majordomo-users-outgoing; Mon, 4 Nov 1996 07:58:33 -0800 (PST) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA23645 for ; Mon, 4 Nov 1996 07:58:24 -0800 (PST) Received: from Mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by Kitten.mcs.com (8.8.2/8.8.Beta.3) with ESMTP id JAA19938 for ; Mon, 4 Nov 1996 09:58:20 -0600 (CST) Received: from Mercury.mcs.net (les@Mercury.mcs.com [192.160.127.80]) by Mailbox.mcs.com (8.8.2/8.8.2) with ESMTP id JAA09633 for ; Mon, 4 Nov 1996 09:58:19 -0600 (CST) Received: (from les@localhost) by Mercury.mcs.net (8.8.2/8.8.2) id JAA15929 for majordomo-users@greatcircle.com; Mon, 4 Nov 1996 09:58:17 -0600 (CST) From: Leslie Mikesell Message-Id: <199611041558.JAA15929@Mercury.mcs.net> Subject: Archiving for web browsing? To: majordomo-users@greatcircle.com Date: Mon, 4 Nov 1996 09:58:17 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is anyone running a list where the main point is to generate the archive copy so it can be accessed via web browsers instead of cluttering everyone's mailboxes? If so, do you have any advice about how to set it up? Les Mikesell les@mcs.com From majordomo-users-owner Mon Nov 4 08:33:28 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA25547 for majordomo-users-outgoing; Mon, 4 Nov 1996 08:19:33 -0800 (PST) Received: from boulder.earthnet.net (boulder.earthnet.net [199.45.146.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA25514 for ; Mon, 4 Nov 1996 08:19:13 -0800 (PST) Received: from jennifer (slip9.earthnet.net [199.45.146.109]) by boulder.earthnet.net (8.6.10/8.6.10) with ESMTP id JAA28999 for ; Mon, 4 Nov 1996 09:20:59 -0700 Message-Id: <199611041620.JAA28999@boulder.earthnet.net> From: "Gregory K. Remington" To: Subject: MD 1.93 DIFFs to suppress 'who' response Date: Mon, 4 Nov 1996 09:20:13 -0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk TWIMC; I modified majordomo 1.93 to suppress the 'who' response on a per-list basis, controlled by a new config option. For those who expressed interest, here are the diff files... The first modifies majordomo, the second modifies config_parse.pl... ---------majordomo.diff---------- 517a518,522 > #check for function suppression > if ( &cf_ck_bool($clean_list,"suppress_who") ) { > print REPLY "**** The 'who' function is suppressed.\n"; > return 0; > } ---------config_parse.diff---------- 82a83 > 'suppress_who', 'no', # nobody get who response 151a153,155 > 'suppress_who', > "If set to yes, then nobody gets the who list.", > 341a346 > 'suppress_who', 'majordomo', 387a393 > 'suppress_who', 'grab_bool', After making the modifications, any list manager can add suppress_who = yes to the list config file... Good luck, Greg P.S. Sorry I'm not into shell scripts or patch enough to provide automatic update material... anyway, MD 1.94 will do it differently. From majordomo-users-owner Mon Nov 4 09:19:10 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA00624 for majordomo-users-outgoing; Mon, 4 Nov 1996 09:16:03 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA00617 for ; Mon, 4 Nov 1996 09:15:56 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id LAA24873; Mon, 4 Nov 1996 11:15:54 -0600 (CST) To: Subject: Re: MD 1.93 DIFFs to suppress 'who' response References: <199611041620.JAA28999@boulder.earthnet.net> From: Jason L Tibbitts III Date: 04 Nov 1996 11:15:54 -0600 In-Reply-To: "Gregory K. Remington"'s message of Mon, 4 Nov 1996 09:20:13 -0700 Message-ID: Lines: 12 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "GKR" == Gregory K Remington writes: GKR> TWIMC; I modified majordomo 1.93 to suppress the 'who' response on a GKR> per-list basis, controlled by a new config option. Just so everyone knows, this is completely unnecessary with 1.94 as this feature is built in. (See who_access in the config file.) Also, this patch doesn't actually protect you at all, since unless you also turn off "which", someone can get all of your addresses by doing "which @" or things like "which a", "which b", etc. - J< From majordomo-users-owner Mon Nov 4 09:23:34 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA00123 for majordomo-users-outgoing; Mon, 4 Nov 1996 09:09:27 -0800 (PST) Received: from smtp.esosoft.com (gila.iserver.com [192.41.21.130]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA29994 for ; Mon, 4 Nov 1996 09:09:12 -0800 (PST) Received: from michael (msn-39.tue-1.msn.eunet.de [194.175.78.39]) by smtp.esosoft.com (8.6.10) id SAA07153; Mon, 4 Nov 1996 18:08:59 +0100 Message-Id: <199611041708.SAA07153@smtp.esosoft.com> From: "Michael Tratz" To: Subject: Confirmation problems for many subscribers Date: Mon, 4 Nov 1996 18:07:50 +0100 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello Majordomo-Users, I'm the Majordomo-Owner of the PCFlightSim.com site. Last week we have upgraded to Majordomo 1.94. One of the most exciting feature was the confirmation. But no I really hate this, because the people who are sending back the confirmation don't supply their email address, most of them are suppling only their name. And then I got a User unkown message. And I need to look at the Log files to get their email address. Now I told every listowner to turn off this, because I don't have the time to do this beside my busy work. Perhaps they have put on word wrap... I have updated the Majordomo confirmation that it will supply a message, that they need to supply their email address. But I'll thinking that they don't read the message they hit only reply... And know I'll think it will be the best way to develop a patch for Majordomo that it will strip out the Name as it is done if you have strip=yes in the configuration file. Can someone help me? I have programmed only little small programs in Perl. Do other Majordomo-Owners experience this, too? Regards Michael Tratz From majordomo-users-owner Mon Nov 4 09:32:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA00963 for majordomo-users-outgoing; Mon, 4 Nov 1996 09:20:09 -0800 (PST) Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA00955 for ; Mon, 4 Nov 1996 09:20:03 -0800 (PST) Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-960123) id JAA11387; Mon, 4 Nov 1996 09:19:56 -0800 Received: from sina.hpc.uh.edu(129.7.3.5) by mycroft via smap (V1.3mjr) id sma011384; Mon Nov 4 09:19:35 1996 Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id LAA24927; Mon, 4 Nov 1996 11:18:21 -0600 (CST) To: Leslie Mikesell Cc: majordomo-users@GreatCircle.COM Subject: Re: Archiving for web browsing? References: <199611041558.JAA15929@Mercury.mcs.net> From: Jason L Tibbitts III Date: 04 Nov 1996 11:18:20 -0600 In-Reply-To: Leslie Mikesell's message of Mon, 4 Nov 1996 09:58:17 -0600 (CST) Message-ID: Lines: 13 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "LM" == Leslie Mikesell writes: LM> Is anyone running a list where the main point is to generate the LM> archive copy so it can be accessed via web browsers instead of LM> cluttering everyone's mailboxes? I use MHonArc (do a web search for it) to archive my lists; others use HyperMail. Unfortunately none of these are really interactive; you can't easily respond to a message through the archive and you have to rely on your browsers coloring of followed links to find new messages. It works well for lurkers, though. - J< From majordomo-users-owner Mon Nov 4 09:49:40 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA02972 for majordomo-users-outgoing; Mon, 4 Nov 1996 09:42:45 -0800 (PST) Received: from free-me.marben.be (gatekeeper.marben.be [194.78.27.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA02379 for ; Mon, 4 Nov 1996 09:35:47 -0800 (PST) Received: (from smap@localhost) by free-me.marben.be (8.7.5/8.7.3) id SAA06106 for <@gatekeeper.marben.be:majordomo-users@GreatCircle.COM>; Mon, 4 Nov 1996 18:35:30 +0100 (MET) X-Authentication-Warning: free-me.marben.be: smap set sender to using -f Received: from tarifa.marben.be(172.20.0.254) by free-me.marben.be via smap (V1.3) id sma006104; Mon Nov 4 18:35:06 1996 Received: from tarifa.marben.be by tarifa via SMTP (940816.SGI.8.6.9/940406.SGI.AUTO) for id SAA22779; Mon, 4 Nov 1996 18:29:36 +0100 Message-ID: <327E27FF.C6D@marben.be> Date: Mon, 04 Nov 1996 18:29:35 +0100 From: Jean-Pierre Morant Organization: Marben SA-NV X-Mailer: Mozilla 3.0Gold (X11; I; IRIX 5.3 IP22) MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: List moderation, Netscape mailer together Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello ! I have a moderated list with a moderator on a MS-whatever machine using Netscape builtin movemail to approve messages. It works but I'm not satisfied as: 1 - (minor problem) he does not have a handy mechanism like the approve script 2 - (major) the net result is that the mailer is set to auto-quote the message and the moderator must erase the first few lines (do not forget any !), up to the white space before the original "Subject:" (too bad for the "from:" ...), and edit the "to " field for the forwarding/approval to succeeds. Needless to say this procedure is far too complex to have a 100% success rate. I would appreciate if someone could tell me how to simplify this procedure, taking into account that I want to stick with Netscape's mailer. Not to have the ">" in front of the quoted message would already be a giant leap forward ... -- Jean-Pierre Morant c/o MARBEN S.A./N.V. La vie serait tellement Boulevard du Souverain,400, Vorstlaan plus facile 1160 Bruxelles Si seulement Belgium nous avions les sources.... + 32 2 663 1130 (phone) + 32 2 663 1199 (fax) http://www.marben.be jpm@marben.be From majordomo-users-owner Mon Nov 4 10:03:19 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA04018 for majordomo-users-outgoing; Mon, 4 Nov 1996 09:54:35 -0800 (PST) Received: from boulder.earthnet.net (boulder.earthnet.net [199.45.146.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA03912 for ; Mon, 4 Nov 1996 09:54:08 -0800 (PST) Received: from jennifer (slip3.earthnet.net [199.45.146.103]) by boulder.earthnet.net (8.6.10/8.6.10) with ESMTP id KAA03616; Mon, 4 Nov 1996 10:55:52 -0700 Message-Id: <199611041755.KAA03616@boulder.earthnet.net> From: "Gregory K. Remington" To: , "Jason L Tibbitts III" Subject: Re: MD 1.93 DIFFs to suppress 'who' response Date: Mon, 4 Nov 1996 10:55:04 -0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Just so everyone knows, this is completely unnecessary with 1.94 as this > feature is built in. Noted in my PS, but considering the mail volume, 1.94 does not yet appear to be stable enough for me to risk installing it... G. From majordomo-users-owner Mon Nov 4 10:07:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA02063 for majordomo-users-outgoing; Mon, 4 Nov 1996 09:32:22 -0800 (PST) Received: from dnacom.com (dnacom.com [205.147.66.209]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA02029 for ; Mon, 4 Nov 1996 09:32:08 -0800 (PST) Received: from dnacom.com (jdawson@dnacom.com [205.147.66.209]) by dnacom.com (8.6.12/8.6.12) with SMTP id JAA01305 for ; Mon, 4 Nov 1996 09:32:04 -0800 Date: Mon, 4 Nov 1996 09:32:02 -0800 (PST) From: Jim Dawson X-Sender: jdawson@dnacom.com To: Majordomo Users List Subject: Aborted address Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Running MD 1.93 on BSDI 2.1. Got the following messages sent to majordomo-owner (the actual question is at the end): =======================message 1================ Subject: MAJORDOMO ABORT MAJORDOMO ABORT HOSTILE ADDRESS - lcarin@igg2.agric.za ========================message 2=============== Subject: Returned mail: unknown mailer error 2 The original message was received at Mon, 4 Nov 1996 01:11:28 -0800 (PST) from apollo.is.co.za [196.4.160.2] ----- The following addresses have delivery notifications ----- "|/usr/local/majordomo/wrapper majordomo" (unrecoverable error) (expanded from: ) ----- Transcript of session follows ----- Message delivered to mailing list HOSTILE ADDRESS - lcarin@igg2.agric.za ABORT HOSTILE ADDRESS - lcarin@igg2.agric.za at /usr/local/majordomo/majordomo.pl line 209, <> line 1. 554 "|/usr/local/majordomo/wrapper majordomo"... unknown mailer error 2 [ Part 2: "Included Message" ] Reporting-MTA: dns; navi.net Received-From-MTA: DNS; apollo.is.co.za Arrival-Date: Mon, 4 Nov 1996 01:11:28 -0800 (PST) Final-Recipient: RFC822; majordomo@navi.net Action: delivered (to mailing list) Status: 2.0.0 Last-Attempt-Date: Mon, 4 Nov 1996 01:11:42 -0800 (PST) Final-Recipient: RFC822; majordomo@navi.net X-Actual-Recipient: RFC822; |/usr/local/majordomo/wrapper majordomo@navi.net Action: failed Status: 5.0.0 Last-Attempt-Date: Mon, 4 Nov 1996 01:11:42 -0800 (PST) [ Part 3: "Included Message" ] Date: Mon, 4 Nov 1996 11:08:51 +0200 From: "Mej. C. van der Merwe" To: Majordomo@navi.net subscribe dsfict - lcarin@igg2.agric.za ===================End message 2================= The log shows this (wrapped for clarity): ==========/majordomo/Log========== Nov 04 01:11:39 pdx-s01.navi.net majordomo[11104] {"Mej. C. van der Merwe" } ABORT HOSTILE ADDRESS - lcarin@igg2.agric.za ==============End log============ That list.config has mungedomain = no and subscribe_policy = open. Here's the question: If either mungedomain or subscribe_policy is rejecting the subscribe request, why is majordomo aborting? As best I can tell, line 209 in majordomo.pl logs the error, which it did. This particular list has been up since May, and several others have been up longer, without anything like this happening. Any thoughts? Thanks, Jim __________________________________________________________________ Jim Dawson jdawson@navi.net GCN Communications, Inc. http://www.navi.net 2305 NW Kearney St. Ste. 239 voice: +1.503.531.1978 Portland, Or 97210 USA fax: +1.503.531.1979 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From majordomo-users-owner Mon Nov 4 11:40:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA09813 for majordomo-users-outgoing; Mon, 4 Nov 1996 10:48:14 -0800 (PST) Received: from queernet.queernet.org (queernet.queernet.org [140.174.78.69]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA09762 for ; Mon, 4 Nov 1996 10:48:01 -0800 (PST) Received: from localhost (rogerk@localhost) by queernet.queernet.org (8.7.4/8.7.3) with SMTP id KAA19455 Date: Mon, 4 Nov 1996 10:45:49 -0800 (PST) From: "Roger B.A. Klorese" To: "Gregory K. Remington" cc: majordomo-users@GreatCircle.COM, Jason L Tibbitts III Subject: Re: MD 1.93 DIFFs to suppress 'who' response In-Reply-To: <199611041755.KAA03616@boulder.earthnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Mon, 4 Nov 1996, Gregory K. Remington wrote: > > Just so everyone knows, this is completely unnecessary with 1.94 as this > > feature is built in. > > Noted in my PS, but considering the mail volume, 1.94 does not yet > appear to be stable enough for me to risk installing it... First: my experience is that 1.94 is more stable than 1.93 *ever* got to be. Second: the "anon" patch for 1.62 and later has been in the archive for, oh, at least a year now. -- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy -- the refusal of joy!" -- Paul Rudnick From majordomo-users-owner Mon Nov 4 11:44:23 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA10010 for majordomo-users-outgoing; Mon, 4 Nov 1996 10:50:36 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA09982 for ; Mon, 4 Nov 1996 10:50:26 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA11944 for Majordomo-Users@GreatCircle.COM; Mon, 4 Nov 96 11:50:21 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA06470 for Majordomo-Users@GreatCircle.COM; Mon, 4 Nov 96 11:50:20 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id MAA20822; Mon, 4 Nov 1996 12:50:19 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id MAA11756; Mon, 4 Nov 1996 12:48:48 -0600 From: Dave Wolfe Message-Id: <199611041848.MAA11756@miaow.risc.sps.mot.com> Subject: Re: archive files To: sandrac@reduno.com.mx (SANDRA CEJUDO FUNES) Date: Mon, 4 Nov 1996 12:48:47 -0600 (CST) Cc: Majordomo-Users@GreatCircle.COM In-Reply-To: from "SANDRA CEJUDO FUNES" at Nov 4, 96 12:39:10 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ SANDRA CEJUDO FUNES writes: ] > > > > When I post to majordomo the index command to my list prueba1, > > > it said that there's no files available, but there are two files > > > in the archive directory. > > I'm using Mj 1.94, on Solaris 2.5, sparc station. > > I don't have private_index, I'm a subscriber to the list, Mj have > permission. My @archive_dirs: > > @archive_dirs = ("/usr/local/mail/archives/prueba1", > "/usr/local/mail/archives/moderada", > "/usr/local/mail/archives/nueva_tecnologia" ); > > And the files are in /usr/local/mail/archives/prueba1 If the exact message you're getting is: #### No files available for prueba1 then the only way to get that is if "$filedir/prueba1$filedir_suffix" is *not* a directory. See lines 1373 and 1390 in majordomo. -- Dave Wolfe From majordomo-users-owner Mon Nov 4 11:44:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA12325 for majordomo-users-outgoing; Mon, 4 Nov 1996 11:10:17 -0800 (PST) Received: from reduno.reduno.com.mx (reduno.reduno.com.mx [192.100.183.178]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA12292 for ; Mon, 4 Nov 1996 11:10:06 -0800 (PST) Received: by reduno.reduno.com.mx (4.1/4.7) id AA11629; Mon, 4 Nov 96 12:39:10 CST Date: Mon, 4 Nov 1996 12:39:10 -0600 (CST) From: SANDRA CEJUDO FUNES To: Dave Wolfe Cc: Majordomo-Users@GreatCircle.COM Subject: Re: archive files In-Reply-To: <199611041523.JAA13966@miaow.risc.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 Mon, 4 Nov 1996, Dave Wolfe wrote: > [ SANDRA CEJUDO FUNES writes: ] > > > > When I post to majordomo the index command to my list prueba1, it said > > that there's no files available, but there are two files in the archive > > directory. > > > > What'is wrong? > > What's wrong is that you give us almost *no* information to go on. But > I'll propose some things for you to check. Does Mj have permission to > read/search your archive directory path? Do you have 'private_index' set > but are not a subscriber to the list? Do you have a .private > file (that sets 'private_index')? Do your '$filedir', '$filedir_suffix', > and '@archive_dirs' in majordomo.cf and what you think is the archive > directory all match up? > I'm using Mj 1.94, on Solaris 2.5, sparc station. I don't have private_index, I'm a subscriber to the list, Mj have permission. My @archive_dirs: @archive_dirs = ("/usr/local/mail/archives/prueba1", "/usr/local/mail/archives/moderada", "/usr/local/mail/archives/nueva_tecnologia" ); And the files are in /usr/local/mail/archives/prueba1 Any ideas? From majordomo-users-owner Mon Nov 4 11:45:36 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA10692 for majordomo-users-outgoing; Mon, 4 Nov 1996 10:56:54 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA10675 for ; Mon, 4 Nov 1996 10:56:45 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id NAA03903; Mon, 4 Nov 1996 13:56:32 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id NAA11561; Mon, 4 Nov 1996 13:56:29 -0500 (EST) Message-Id: <199611041856.NAA11561@augusta.math.psu.edu> To: "Gregory K. Remington" cc: majordomo-users@GreatCircle.COM Subject: Re: MD 1.93 DIFFs to suppress 'who' response In-reply-to: Your message of "Mon, 04 Nov 1996 10:55:04 MST." <199611041755.KAA03616@boulder.earthnet.net> References: <199611041755.KAA03616@boulder.earthnet.net> 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: Mon, 04 Nov 1996 13:56:27 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <199611041755.KAA03616@boulder.earthnet.net>, "Gregory K. Remington" writes: >> Just so everyone knows, this is completely unnecessary with 1.94 as this >> feature is built in. > >Noted in my PS, but considering the mail volume, 1.94 does not yet >appear to be stable enough for me to risk installing it... Really? IMHO it's just as stable as 1.93, and a lot more features to boot. There's only one real bug I can determine, and that's an installation bug and covered in the current FAQ. Put it this way -- the FAQ shrunk by a significant amount the day 1.94 was released. (and I think it can shrink a bit more, too) --Dave From majordomo-users-owner Mon Nov 4 11:51:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA15108 for majordomo-users-outgoing; Mon, 4 Nov 1996 11:44:02 -0800 (PST) Received: from gw.alsys.com (gw.alsys.com [136.175.17.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA15088 for ; Mon, 4 Nov 1996 11:43:52 -0800 (PST) Received: from east.alsys.com (wheel.east.alsys.com) by gw.alsys.com (4.1/SMI-4.1.1) id AA18905; Mon, 4 Nov 96 11:44:22 PST Received: from sparky.east.thomsoft.com by east.alsys.com (4.1/SMI-4.1) id AA07557; Mon, 4 Nov 96 14:43:01 EST Received: from fielding.east.aonix.com by sparky.east.thomsoft.com (5.0/SMI-SVR4) id AA13983; Mon, 4 Nov 1996 14:39:33 +0500 Received: by fielding.east.aonix.com with Microsoft Mail id <01BBCA5E.82F5BD20@fielding.east.aonix.com>; Mon, 4 Nov 1996 14:43:15 -0500 Message-Id: <01BBCA5E.82F5BD20@fielding.east.aonix.com> From: "Neil O'Brien" To: "'majordomo-users'" Subject: fun with digests and archives Date: Mon, 4 Nov 1996 14:43:14 -0500 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I think I have a conceptual problem with digests here, well actually I have a problem because they are not working as well!. Anyway, my digests didn't seem to be right with 1.93, I upgraded to 1.94 at the weekend, everything seems fine but my digests still do not work. I think this may be confusion on my part, but also the descriptions of how to set them up looks to be different in 1.94 than 1.93. I am running 1.94 on a solaris 2.5 machine. So, my system is similar to the following: /machine/disk/MajorDomo /machine/disk/MajorDomo/lists /test-list #subscriber names /test-list-digest #subscriber names /test-list-digest.archive #digest archive directory /machine/disk/MajorDomo/archives /archives/test-list #directories for archiving? /archives/test-list-digest /machine/disk/MajorDomo/digests /digests/test-list #directories for digests? /digests/test-list-digest The names (test-list and test-list-digest) are valid, or at least I can email them and get the messages forwarded to list members (me only in both cases). However, I don't see any information being stored in the directories. What happens when I email a mesage to a list?, my assumption is that it is sent to the list members, a copy is stored in the archives as /archives/list-name/listname.yymm and a copy is kept in /digests/list-name/listname and a in /lists/list-name-digest.archive. But the new description in Doc (Quick Digest Setup) says I should also have a directory called /lists/listname-digest.archive, even so I'm still not getting anything stored from my email. When I send a mkdigest command, I get an error that there is nothing to process. Not a surprise really. What is the relationship between archives and digests? I think if I can sort this out correctly then I can set up the files correctly. For example in 1.93 there was information about using a file called /digests/list-name-digest.cf, but there is also a file called /lists/list-name-digest.config, which do I use? one or both? In my majordomo.cf I use the following: $homedir="/machines/disk/MajorDomo"; $listdir ="$homedir/lists"; $digest_work_dir="$homedir/digests"; $filedir="$listdir"; $filedir_suffix=".archive"; is this correct? My permissions seem to be correct (certainly a "make test-config" doesn't have any complaints). How should these really be? ========================================================= Neil O'Brien obrien@east.thomsoft.com Customer Support (617) 221 7320 Thomson Software Products subscribe intel-objectada (or unix-objectada) send your email to majordomo@east.thomsoft.com with a blank subject line and the subscribe command in the body "I went back to my hotel and intended to watch Tottenham - but I fell asleep" - Arsene Wenger From majordomo-users-owner Mon Nov 4 12:36:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA18196 for majordomo-users-outgoing; Mon, 4 Nov 1996 12:20:23 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id MAA18183 for ; Mon, 4 Nov 1996 12:20:14 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id OAA03994; Mon, 4 Nov 1996 14:20:01 -0600 (CST) To: Michael Tratz Cc: majordomo-users@GreatCircle.COM Subject: Re: Confirmation problems for many subscribers References: <199611041708.SAA07153@smtp.esosoft.com> From: Jason L Tibbitts III Date: 04 Nov 1996 14:20:00 -0600 In-Reply-To: Michael Tratz's message of Mon, 04 Nov 1996 18:07:50 +0100 Message-ID: Lines: 21 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "MT" == Michael Tratz writes: MT> But no I really hate this, because the people who are sending back the MT> confirmation don't supply their email address, most of them are MT> suppling only their name. Yeah, people mess this up royally. It was just as bad before, though. Heck, with an auto list, you can add any string of garbage onto the list. I have this fixed in my sources, which will eventually become part of a later version. I do many more checks on the supplied address, and tell people they're doing it wrong if they give their name or make many other common mistakes. I have received nary a bounce, nor any complaints about not understanding the directions since I started running this. I don't intend to supply a patch for this as my sources are too far diverged from 1.94 to allow an easy fix. You may of course join the majordomo-workers list and participate in the testing (when we start it) if you desire to try out these fixes. - J< From majordomo-users-owner Mon Nov 4 13:37:54 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA23607 for majordomo-users-outgoing; Mon, 4 Nov 1996 13:09:47 -0800 (PST) Received: from mailhub.aros.net (mailhub.aros.net [205.164.111.17]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA23590 for ; Mon, 4 Nov 1996 13:09:38 -0800 (PST) From: Damian@aros.net Received: from aros.net.aros.net (pm3-1.slc.aros.net [207.173.24.66]) by mailhub.aros.net (8.7.6/Unknown) with SMTP id OAA29591 for ; Mon, 4 Nov 1996 14:09:05 -0700 (MST) Message-ID: <327E5B59.4FD8@aros.net> Date: Mon, 04 Nov 1996 14:08:41 -0700 Reply-To: Damian@aros.net Organization: Damian's Music Emporium X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: A beginner (oh no)... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello everyone, I am an absolute beginner when it comes to mailing lists and the like. Currently I am two weeks into running a mailing list for myself. My ISP did all of the leg work in setting me up and now I'm trying to take it all further by customizing and creating a digest version (which my ISP doesn't currently offer). My highest priority is to get a digest version of my mailing list going. I have been watching everyone's postings for the past week and have gone through all of Octobers archives. Nevertheless and sadly, I still am lost! ): I need help with the most basic of items and this list, so far, is too advanced for me. Where can I go for simple instructions in setting up a digest? I've noticed O'Reilly's Managing Internet Information Services mentioned a time or two. Is this a book or something available on the net? My ISP is using MD 1.93 They use Sendmail And I believe they run off of a Unix server. My ISP is eager to try anything. Any guidance, suggestions, or comments will be greatly appreciated. Thank You. -- Damian@aros.net ================================== http://www.aros.net/~damian/ Home to the Mobility Mailing List ================================== From majordomo-users-owner Mon Nov 4 13:42:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA23583 for majordomo-users-outgoing; Mon, 4 Nov 1996 13:09:16 -0800 (PST) Received: from smtp.esosoft.com (gila.iserver.com [192.41.21.130]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id NAA23576 for ; Mon, 4 Nov 1996 13:09:09 -0800 (PST) Received: from michael (msn-6.tue-1.msn.eunet.de [194.175.78.6]) by smtp.esosoft.com (8.6.10) id WAA10673; Mon, 4 Nov 1996 22:08:45 +0100 Message-Id: <199611042108.WAA10673@smtp.esosoft.com> From: "Michael Tratz" To: "Jason L Tibbitts III" Cc: Subject: Re: Confirmation problems for many subscribers Date: Mon, 4 Nov 1996 22:08:32 +0100 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Jason, I will try to get a patch for this (Stripping only the name out). If I will have luck, I will post it on the list. Regards Michael Tratz ---------- > From: Jason L Tibbitts III > To: Michael Tratz > Cc: majordomo-users@GreatCircle.COM > Subject: Re: Confirmation problems for many subscribers > Date: Montag, 4. November 1996 21:20 > > >>>>> "MT" == Michael Tratz writes: > > MT> But no I really hate this, because the people who are sending back the > MT> confirmation don't supply their email address, most of them are > MT> suppling only their name. > > Yeah, people mess this up royally. It was just as bad before, though. > Heck, with an auto list, you can add any string of garbage onto the list. > > I have this fixed in my sources, which will eventually become part of a > later version. I do many more checks on the supplied address, and tell > people they're doing it wrong if they give their name or make many other > common mistakes. I have received nary a bounce, nor any complaints about > not understanding the directions since I started running this. > > I don't intend to supply a patch for this as my sources are too far > diverged from 1.94 to allow an easy fix. You may of course join the > majordomo-workers list and participate in the testing (when we start it) if > you desire to try out these fixes. > > - J< From majordomo-users-owner Mon Nov 4 13:54:12 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA26149 for majordomo-users-outgoing; Mon, 4 Nov 1996 13:39:52 -0800 (PST) Received: from odin.cair.du.edu (odin.cair.du.edu [130.253.1.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id NAA26140 for ; Mon, 4 Nov 1996 13:39:46 -0800 (PST) Received: from [130.253.80.236] by odin.cair.du.edu; (5.65v3.2/1.1.8.2/19Apr96-0816AM) id AA00709; Mon, 4 Nov 1996 14:38:50 -0700 Message-Id: <327E62A1.178F@du.edu> Date: Mon, 04 Nov 1996 14:39:46 -0700 From: "Victor M. Vazquez Jr." Organization: University of Denver X-Mailer: Mozilla 3.0 (Win95; I) Mime-Version: 1.0 To: Dave Barr Cc: "Gregory K. Remington" , majordomo-users@GreatCircle.COM Subject: Re: MD 1.93 DIFFs to suppress 'who' response References: <199611041755.KAA03616@boulder.earthnet.net> <199611041856.NAA11561@augusta.math.psu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Dave Barr wrote: > > In message <199611041755.KAA03616@boulder.earthnet.net>, "Gregory K. Remington" > writes: > >> Just so everyone knows, this is completely unnecessary with 1.94 as this > >> feature is built in. > > > >Noted in my PS, but considering the mail volume, 1.94 does not yet > >appear to be stable enough for me to risk installing it... > > Really? IMHO it's just as stable as 1.93, and a lot more features to boot. > > There's only one real bug I can determine, and that's an installation bug > and covered in the current FAQ. > > Put it this way -- the FAQ shrunk by a significant amount the day 1.94 > was released. (and I think it can shrink a bit more, too) > > --Dave can someone send me the command to unsubscribe. thanks From majordomo-users-owner Mon Nov 4 14:01:06 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA24769 for majordomo-users-outgoing; Mon, 4 Nov 1996 13:23:43 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA24758 for ; Mon, 4 Nov 1996 13:23:32 -0800 (PST) Received: from sina.hpc.uh.edu (localhost [127.0.0.1]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id PAA06245; Mon, 4 Nov 1996 15:23:20 -0600 (CST) Message-Id: <199611042123.PAA06245@sina.hpc.uh.edu> To: michael@esosoft.com Cc: majordomo-users@GreatCircle.COM Subject: Re: Confirmation problems for many subscribers In-Reply-To: Your message of "Mon, 4 Nov 1996 22:08:32 +0100" References: <199611042108.WAA10673@smtp.esosoft.com> X-Mailer: Mew beta version 0.98 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 04 Nov 1996 15:23:19 -0600 From: Jason L Tibbitts III Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "MT" == Michael Tratz writes: MT> Jason, I will try to get a patch for this (Stripping only the name MT> out). If I will have luck, I will post it on the list. If you are not intimately familiar with RFC822 and the internals of Majordomo, I suggest that you either do a bunch of reading or leave it to the experts. You can seriously break recognition of perfectly legal but quite weird addresses without knowing it very easily. This is definitely not a simple matter. If you want to play, I suggest trying something like the following in place of the valid_addr routine in majordomo.pl. Be sure to strip out any perl5isms if perl4 compatability is important to you. Also, this routine may not work in the 1.94 framework because it may not have depended-upon side effects. Part of my recoding has been to reduce the dependence on bizarre side-effects and globals. Then again, this may just drop right in. Let me know if it works and I'll come up with a real patch. Note also that some of the messages are placeholders, and that more useful and helpful messages will go in before this gets into a release. # Check to see that this is a valid address. # A valid address is a single address with # no "|" in the address part. It may not start with a - either. # If it has a / in it, we use some heuristics to find out if the address # may be a file. Some other heuristics attempt to look for a valid X.400 # address. This is not infallible. sub main::valid_addr { local($addr, $list) = @_; local(@addrs, $temp); # Parse the address out into parts @addrs = &main::ParseAddrs($addr); # if there's not exactly 1 part, it's no good if ($#addrs != 0) { return undef; } local($_) = $addrs[0]; # Deal with unbalanced brackets or parenthesis in an address. $temp = $_; # Nuke anything within quotes. Placate Emacs -------v 1 while $temp =~ s/(^|([^\\\"]|\\.)+)\"([^\\\"]|\\.|$+)*\"?/$1/g; # Remove nested parentheses 1 while $temp =~ s/\([^\(\)]*\)//g; # Remove nested angle brackets 1 while $temp =~ s/\<[^\<\>]*\>//g; # remove nested square brackets 1 while $temp =~ s/\[[^\[\]]*\]//g; # If any parentheses of brackets remain, they are unbalanced and the # address is illegal. if ($temp =~ /[\(\)\<\>\[\]]/) { if (defined main::REPLY) { print main::REPLY <<"EOM" **** The address you supplied, $_ **** Does not seem to be a legal Internet address. It seems to have an **** uneven number of parenthesis or brackets. EOM } &main::log("WARNING", "Unbalanced address: $_"); return undef; } # Deal with legal spaces in a stripped address, then check and reject # any remaining space. Note that as I write this, the comment stripper # ParseAddrs does not handle things like a quoted local part but I've # included the correct routines just in case it ever does. $temp = $_; # We assume that the comment stripper will have eaten leading and # trailing space. # This mess turns "jason ti bb i tt s"@hpc.uh.edu into # "jasontibbitts"@hpc.uh.edu 1 while $temp =~ s/\"(.*)\s(.*)\"/\"$1$2\"/g; # This compresses space before dots or `@'s. 1 while $a =~ s/\s(\.|@)/$1/g; # This compresses space after dots or `@'s. 1 while $a =~ s/(\.|@)\s/$1/g; # We've taken out all legitimate space from the address (yes, RFC822 # permits that kind of bogosity), so if the address has spaces, we have # a problem. if ($temp =~ /\s/) { if (defined main::REPLY) { print main::REPLY <<"EOM"; **** The address you supplied, $_ **** does not seem to be a legal Internet address. You may have supplied **** your full name instead of your address, or you may have included your **** name along with your address in a manner that does not comply with **** Internet standards for addresses. **** It is also possible that you are using a mailer that wraps long lines **** and the end of your request ended up on the following line. If the **** latter is true, try using backslashes to split long lines. (Split the **** line between words, then put a backslash at the end of all but the **** last line.) EOM } &main::log("WARNING", "Illegal space in address: $_"); return undef; } # Look for addresses of the form rouilj@cs if (/\@/ && !/\./) { if (defined main::REPLY) { print main::REPLY <<"EOM"; **** The address you supplied, $_ **** is not a complete address. When providing an address, you must give **** the full name of the machine including the domain part (like **** host.corp.com), not just the short name of the machine (just host). EOM } &main::log("WARNING", "Non-domained address: $_"); return undef; } # o if there's a "|" in it, it's hostile # o if there is a - sign at the front of the address, it may be an attempt # to pass a flag to the MTA # o bail if they're attempting to subscribe the list to itself # print STDERR "$0: valid_addr: comparing '$addr' to '$list'\n" if $DEBUG; if ( /\|/ || /^-/ ) { &main'abort("HOSTILE ADDRESS (invalid first char or |) $addr"); #' return undef; } if ( $addr eq $list ) { &main'abort("HOSTILE ADDRESS (tried to subscribe list) $addr"); # ' return undef; } # if the is a / in it, it may be an attempt to write to a file. # or it may be an X.400, HP Openmail or some other dain bramaged # address 8-(. We check this by breaking the address on '/'s # and checking to see if the first component of the address # exists. If it does we bounce it as a hostile address. if ( m#/# ) { local(@components) = split( /\//, $_); &main'abort("HOSTILE ADDRESS (path exists to /file) $addr") if (-e "/$components[0]"); #' &main'abort("HOSTILE ADDRESS (path exists to file) $addr") if (-e "$components[0]"); #' # then as an extra check that can be turned off in the majordomo.cf # file we make sure that the last component of the address has an # @ sign on it for an X.400->smtp gateway translation. if (!$no_x400at) { &main'abort("HOSTILE ADDRESS (no x400 \@) $addr") if ( "$components[$#components]" !~ /\@/); #' } # check to see that the c= and a[dm]= parts exist if (!$no_true_x400) { &main'abort("HOSTILE ADDRESS (no x400 c=) $addr") if ($_ !~ m#/c=#); #' &main'abort("HOSTILE ADDRESS (no x400 a[dm]=) $addr") if ($_ !~ m#/a[dm]=#); #' } } print STDERR "$0: valid_addr: exit\n" if $DEBUG; return $_; } - J< From majordomo-users-owner Mon Nov 4 14:17:44 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA26669 for majordomo-users-outgoing; Mon, 4 Nov 1996 13:46:48 -0800 (PST) Received: from gamespot.com (ns1.gamespot.com [206.169.18.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA26659 for ; Mon, 4 Nov 1996 13:46:42 -0800 (PST) Received: from tech-a.gamespot.com (tech-a.gamespot.com [206.169.18.66]) by gamespot.com (8.7.5/8.6.12) with SMTP id OAA29738 for ; Mon, 4 Nov 1996 14:34:17 GMT Message-Id: <199611041434.OAA29738@gamespot.com> Comments: Authenticated sender is From: "Ian Kallen" To: majordomo-users@greatcircle.com Date: Mon, 4 Nov 1996 13:47:51 +0000 Subject: Re: Archiving for web browsing? Reply-to: ian@gamespot.com X-mailer: Pegasus Mail for Windows (v2.23) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Perhaps you want hypermail? http://www.eit.com:80/goodies/software/hypermail/ > From: Leslie Mikesell > Subject: Archiving for web browsing? > To: majordomo-users@GreatCircle.COM > Date: Mon, 4 Nov 1996 09:58:17 -0600 (CST) > Is anyone running a list where the main point is to generate the archive > copy so it can be accessed via web browsers instead of cluttering > everyone's mailboxes? If so, do you have any advice about how to > set it up? > > Les Mikesell > les@mcs.com > > -- Ian Kallen ian@gamespot.com Director of Technology & Web Administration http://www.gamespot.com From majordomo-users-owner Mon Nov 4 15:10:12 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA01875 for majordomo-users-outgoing; Mon, 4 Nov 1996 14:50:37 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id OAA01850 for ; Mon, 4 Nov 1996 14:50:25 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA23325 for majordomo-users@GreatCircle.COM; Mon, 4 Nov 96 15:50:23 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA14256 for majordomo-users@GreatCircle.COM; Mon, 4 Nov 96 15:50:21 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id QAA25096; Mon, 4 Nov 1996 16:50:20 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id QAA17347; Mon, 4 Nov 1996 16:08:34 -0600 From: Dave Wolfe Message-Id: <199611042208.QAA17347@miaow.risc.sps.mot.com> Subject: Re: A beginner (oh no)... To: Damian@aros.net Date: Mon, 4 Nov 1996 16:08:34 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <327E5B59.4FD8@aros.net> from "aros.net!Damian" at Nov 4, 96 02:08:41 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ uunet!aros.net!Damian writes: ] > > Where can I go for simple instructions in setting up a digest? A little further back in the archives... This is all for 1.93 so I don't know how much applies to 1.94, but I don't think it changed that much. >Date: Tue, 27 Aug 1996 17:05:19 -0400 (EDT) >From: Kevin Kelleher >Subject: how to set up a digest My recent exchange with Vince about digests showed me that I didn't know as much as I thought I did. At the same time, I don't think that many other people know much about them either. So I read the code a bit more carefully and prepared the following document. I'd appreciate feedback on it. I'll put it on my website, and let you know when it's there. I'm also going to work on a second part that deals with the infamous five files that can also be used for configuring digests. Anyway, here's what I have so far: ------------------------------------------------------------------- HOW DIGESTS WORK Digest work this way: Incoming messages are stored in a work directory. When the digest is built, these individual messages are put together into a single file. This file (the digest) is stored in an archive directory and mailed to the subscribers of the digest. Usually a digest is associated with an ordinary mj list, although this is not a necessary condition. The name of the digest is usually the ordinary listname with the addition of "-digest"; this too is a convention, albeit a useful one. A number of events can cause a digest to be built. When the sum of the sizes of the incoming messages passes the digest's byte limit (this is a configurable variable), the digest is automatically built and sent. A cron command to majordomo can also build a digest, and is the best way to ensure that digests are sent with regularity. HOW DO I SET UP A DIGEST? For the sake of example, let us say that we want to make a digest for an existing mj list called "banjo". The digest will be called "banjo-digest". 1. You must create a working directory and an archive directory for the digest. In majordomo.cf, there are three variables that are significant to all digests: $digest_work_dir and $filedir and $filedir_suffix. The first and second, $digest_work_dir and $filedir, are directories and must already exist. Majordomo will not create them. Some example definitions: $digest_work_dir = "/usr/local/mail/digest"; $filedir = "/usr/local/mail/files"; $filedir_suffix = ".archive"; "$digest_work_dir" is the working directory, where incoming messages are held for all digests. "$filedir" is the main archive directory for all lists. You must create a working directory and an archive directory for each list. In our case, these will be: /usr/local/mail/digest/banjo-digest /usr/local/mail/files/banjo-digest.archive In other words, they have the form "$digest_work_dir/$list" and "$filedir/$list.$filedir_suffix". 2. You must create a list for the digest. Create the files for the list banjo-digest: banjo-digest (to hold the subscribers' addresses), banjo-digest.info (information about the list and welcome message), and banjo-digest.config. You don't need to change anything in the ordinary list's configuration. Even though there are variables like "digest_name" in banjo.config, NONE of these variables are used. All the variables you need to set are in the file banjo-digest.config. These are the variables that affect the digest: digest_issue = 1 digest_name = Banjo Digest digest_volume = 1 maxlength = 40000 message_footer << END END message_fronter << END END Other digest variables (digest_archive, etc.) should NOT be touched! The "maxlength" variable is the size limit for digests. If the size of an incoming message causes the total size of undigested messages to go over the maxlength, a digest is automatically created and sent. The digest_volume and digest_issue usually begin at 1. Each issue of the digest begins with a line showing the digest_name, the date, the volume and number, for example: Banjo Digest Tuesday, 20 August 1996 Volume 01 : Number 011 Next, after a blank line, will appear whatever you have written in the message_fronter. If you want to have blank lines in your text, you need to insert a '-' as the first and only character on the line. To have whitespace at the beginning of a line, you need to begin the line with a '-' in front of the whitespace to be preserved. message_fronter << END In this issue: - - _SUBJECTS_ - See the end of the digest for information on subscribing to banjo or banjo-digest mailing lists and how to retrieve back issues. END The keyword "_SUBJECTS_" is expanded to all of the subject lines from the emails included in the digest. Likewise, any text inserted in message_footer will be placed at the end of the digest. Some other expansion tokens that can be used in both message_fronter and message_footer are: $LIST - the name of the current list, $SENDER - the sender (as seen on the >From line), and $VERSION - the current version of majordomo. 3. You must create some aliases. First, you must add to the banjo-outgoing alias: banjo-outgoing: :include:/path/to/lists/banjo,banjo-digestify and then you will need the banjo-digest aliases: banjo-digest: banjo banjo-digest-outgoing: :include:/path/to/lists/banjo-outgoing banjo-digest-digestify: "|/path/to/wrapper digest -r -C -l banjo-digest \ banjo-digest-outgoing" owner-banjo-digest-outgoing: harry Note that anyone who posts to "banjo-digest" will have their mail routed to the right place anyway. At this point your digest is ready. It will work, although digests will only be created when the size limit is hit. 4. Making the digests run more regularly. You can send a message to majordomo to cause a digest to be created and sent: mkdigest listname-digest [digest-password] In our case: mkdigest banjo-digest strums If there are any messages in the work directory, a digest will be created and sent. Probably you would like the digest to run more automatically. To do this, you need to insert this command into a cron table: echo mkdigest listname-digest [digest-password] | mail majordomo@server.com (Of course, you have to put the real listname and password (if any) and the correct address for majordomo.) DO I HAVE TO HAVE TWO LISTS? I HAVE A LIST THAT I WOULD LIKE TO MAKE AVAILABLE ONLY IN DIGEST FORMAT. The only thing that will be different from the setup described above is in the aliases file: banjo-digest: "|/path/to/wrapper digest -r -C -l banjo-digest \ banjo-digest-outgoing" banjo-digest-outgoing: :include:/path/to/lists/banjo-digest banjo-digest-approval: owner-banjo-digest owner-banjo-digest: harry owner-banjo-digest-outgoing: owner-banjo-digest You don't need a "digestify" alias in this case. I've converted my "how to make a digest" guide into html at: http://www.concorde.com/~kevink/digest.html Kevin Kelleher (feedback, suggestions, questions welcome) -- Dave Wolfe From majordomo-users-owner Mon Nov 4 15:31:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA03499 for majordomo-users-outgoing; Mon, 4 Nov 1996 15:21:21 -0800 (PST) Received: from pinky.kern.org (pinky.kern.org [206.13.105.62]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA03492 for ; Mon, 4 Nov 1996 15:21:16 -0800 (PST) Received: from localhost (dave@localhost) by pinky.kern.org (8.8.0/8.8.0) with SMTP id QAA02915 for ; Mon, 4 Nov 1996 16:14:33 -0800 Date: Mon, 4 Nov 1996 16:14:33 -0800 (PST) From: Dave hecht To: majordomo-users@greatcircle.com Subject: Abort error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Without raising the ABORTion issue so close to election day, I am getting the following error with every submisson to this (or any)list. The trial list is merely for testing purposes. I am running domo 1.94 on Linux 2.0.0. Ideas? MAJORDOMO ABORT Mailer /usr/sbin/sendmail -oi -fowner-trial@pinky.kern.org trial-outgoing exited unexpectedly with error 16384 Thanks Dave Hecht From majordomo-users-owner Mon Nov 4 15:49:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA04654 for majordomo-users-outgoing; Mon, 4 Nov 1996 15:44:57 -0800 (PST) Received: from quest.arc.nasa.gov (quest.arc.nasa.gov [198.123.15.250]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA04647 for ; Mon, 4 Nov 1996 15:44:52 -0800 (PST) Received: by quest.arc.nasa.gov (8.7.1/1.35) id XAA07092; Mon, 4 Nov 1996 23:43:02 GMT Date: Mon, 4 Nov 1996 23:43:02 GMT From: federman@quest.arc.nasa.gov (Alan Federman) Message-Id: <199611042343.XAA07092@quest.arc.nasa.gov> To: majordomo-users@greatcircle.com Subject: V 1.93, Solaris 2.5 - Moderated lists - sender/subject. Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Please excuse me if this topic has been discussed before, but I couldn't find it in the FAQ. We recently upgraded servers from Sun OS to Solaris 2.5 and from 1.92 to 1.93. There seems to be a difference in the way moderated lists send out headers. In our previous installation the Original sender and subject were preserved when a message was approved. Now, it appears that the sender becomes owner-'list' and the subject is stripped. I know it is possible to "preserve" the sender and subject in the body of the message via a 'message-fronter' or 'message-footer' but what I want is to have the original info appear in the sendmail header. We have many "pine" users who want to see the original sender before they open the message. Thanks Alan N. Federman From majordomo-users-owner Mon Nov 4 16:04:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA04950 for majordomo-users-outgoing; Mon, 4 Nov 1996 15:49:06 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA04941 for ; Mon, 4 Nov 1996 15:49:00 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id RAA12111; Mon, 4 Nov 1996 17:48:24 -0600 (CST) To: Damian@aros.net Cc: majordomo-users@GreatCircle.COM Subject: Re: A beginner (oh no)... References: <327E5B59.4FD8@aros.net> From: Jason L Tibbitts III Date: 04 Nov 1996 17:48:23 -0600 In-Reply-To: Damian@aros.net's message of Mon, 04 Nov 1996 14:08:41 -0700 Message-ID: Lines: 23 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "D" == Damian writes: D> [...] My ISP did all of the leg work in setting me up and now I'm trying D> to take it all further by customizing and creating a digest version D> (which my ISP doesn't currently offer). If your ISP won't do the legwork to set up the digest, then you're most likely out of luck. Setting up a digest requires setting up a separate list and fiddling with a few configuration things. The rest of the configuration can be done by the list owner, but you are definitely stuck without your ISP doing what's required on their end. D> My ISP is eager to try anything. Well, if they're willing, tell them go grab the 1.94 distribution and read the new documentation for setting up a digest. They probably won't have to upgrade the whole Majordomo system, they just need the good docs. If they can't figure it out from there, then have them ask specific questions here. - J< From majordomo-users-owner Mon Nov 4 16:31:34 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA06225 for majordomo-users-outgoing; Mon, 4 Nov 1996 16:16:45 -0800 (PST) Received: from janus.3com.com (janus.3com.com [129.213.128.99]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id QAA06209 for ; Mon, 4 Nov 1996 16:16:39 -0800 (PST) Received: from new-york.3com.com (new-york.3com.com [129.213.157.12]) by janus.3com.com (8.8.2/8.8.2) with ESMTP id QAA23785 for ; Mon, 4 Nov 1996 16:16:39 -0800 (PST) Received: from chicago.nsd.3com.com (chicago.nsd.3com.com [129.213.157.11]) by new-york.3com.com (8.8.2/8.8.2) with ESMTP id QAA11245 for ; Mon, 4 Nov 1996 16:13:36 -0800 (PST) Received: from bonnie.nsd.3com.com (bonnie.NSD.3Com.COM [129.213.24.10]) by chicago.nsd.3com.com (8.8.2/8.8.2) with SMTP id QAA20060 for ; Mon, 4 Nov 1996 16:11:25 -0800 (PST) Message-Id: <3.0.32.19961104161512.0068abe4@chicago.nsd.3com.com> X-Sender: mrz@chicago.nsd.3com.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 04 Nov 1996 16:16:43 -0800 To: majordomo-users@greatcircle.com From: matthew zeier Subject: unable to create output - where? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Tried installing majordomo and getting it running today. I keep getting the error below when doing just an "echo 'lists' | mail majordomo" and I'm stuck for a reason why. Checked all my permissions and everything looks okay. Browsed through the FAQ and checked everything I could. Ran through ./wrapper config-test and no errors were reported. If I knew where it was trying to create output I could check there. Can anyone help? > ----- The following addresses had permanent fatal errors ----- >"/homes/majordomo/wrapper majordomo" > (expanded from: majordomo) > > ----- Transcript of session follows ----- >550 "/homes/majordomo/wrapper majordomo"... Can't create output: Permission denied >Message delivered to mailing list majordomo >554 /homes/mrz/dead.letter... cannot open: Permission denied ---- matthew zeier -- mrz@3com.com -- 3Com NSD Engineering -- 408/764-8420 ...................................................................... "To live and die, it seems, is a waste without a dream." - BoDeans From majordomo-users-owner Mon Nov 4 18:16:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA11305 for majordomo-users-outgoing; Mon, 4 Nov 1996 18:14:10 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id SAA11298 for ; Mon, 4 Nov 1996 18:14:01 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id UAA16448; Mon, 4 Nov 1996 20:13:53 -0600 (CST) To: Dave hecht Cc: majordomo-users@GreatCircle.COM Subject: Re: Abort error References: From: Jason L Tibbitts III Date: 04 Nov 1996 20:13:53 -0600 In-Reply-To: Dave hecht's message of Mon, 4 Nov 1996 16:14:33 -0800 (PST) Message-ID: Lines: 11 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "Dh" == Dave hecht writes: Dh> MAJORDOMO ABORT Dh> Mailer /usr/sbin/sendmail -oi -fowner-trial@pinky.kern.org Dh> trial-outgoing exited unexpectedly with error 16384 What's in the debug logs? 16384 = 256 * 64, and on my system, sysexits.h says 64 is EX_USAGE, command line usage error. - J< From majordomo-users-owner Mon Nov 4 18:18:58 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA11381 for majordomo-users-outgoing; Mon, 4 Nov 1996 18:15:50 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id SAA11359 for ; Mon, 4 Nov 1996 18:15:40 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id UAA16547; Mon, 4 Nov 1996 20:15:37 -0600 (CST) To: federman@quest.arc.nasa.gov (Alan Federman) Cc: majordomo-users@GreatCircle.COM Subject: Re: V 1.93, Solaris 2.5 - Moderated lists - sender/subject. References: <199611042343.XAA07092@quest.arc.nasa.gov> From: Jason L Tibbitts III Date: 04 Nov 1996 20:15:37 -0600 In-Reply-To: federman@quest.arc.nasa.gov's message of Mon, 04 Nov 1996 23:43:02 +0000 (GMT) Message-ID: Lines: 15 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "AF" == Alan Federman writes: AF> We recently upgraded servers from Sun OS to Solaris 2.5 and from 1.92 AF> to 1.93. Why upgrade to a version that's out of date? Why not use 1.94? AF> There seems to be a difference in the way moderated lists send out AF> headers. 1.93 was a bit messy with regards to moderated lists. Get 1.94 and read the documentation, specifically list-owner-info, which describes in depth how you approve messages. - J< From majordomo-users-owner Mon Nov 4 18:31:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA11465 for majordomo-users-outgoing; Mon, 4 Nov 1996 18:17:31 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id SAA11458 for ; Mon, 4 Nov 1996 18:17:23 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id UAA16601; Mon, 4 Nov 1996 20:17:15 -0600 (CST) To: matthew zeier Cc: majordomo-users@GreatCircle.COM Subject: Re: unable to create output - where? References: <3.0.32.19961104161512.0068abe4@chicago.nsd.3com.com> From: Jason L Tibbitts III Date: 04 Nov 1996 20:17:14 -0600 In-Reply-To: matthew zeier's message of Mon, 04 Nov 1996 16:16:43 -0800 Message-ID: Lines: 13 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "mz" == matthew zeier writes: >> ----- The following addresses had permanent fatal errors ----- >> "/homes/majordomo/wrapper majordomo" (expanded from: majordomo) Looks to me like you forgot a pipe symbol here. That should be "|/homes/majordomo/wrapper majordomo" As you have it, sendmail is trying to store the message in a file called /homes/majordomo/wrapper, which it obviously can't. - J< From majordomo-users-owner Mon Nov 4 18:46:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA12509 for majordomo-users-outgoing; Mon, 4 Nov 1996 18:40:28 -0800 (PST) Received: from janus.3com.com (janus.3com.com [129.213.128.99]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id SAA12502 for ; Mon, 4 Nov 1996 18:40:22 -0800 (PST) Received: from new-york.3com.com (new-york.3com.com [129.213.157.12]) by janus.3com.com (8.8.2/8.8.2) with ESMTP id SAA28845; Mon, 4 Nov 1996 18:39:43 -0800 (PST) Received: from chicago.nsd.3com.com (chicago.nsd.3com.com [129.213.157.11]) by new-york.3com.com (8.8.2/8.8.2) with ESMTP id SAA16469; Mon, 4 Nov 1996 18:36:39 -0800 (PST) Received: from bonnie.nsd.3com.com (bonnie.NSD.3Com.COM [129.213.24.10]) by chicago.nsd.3com.com (8.8.2/8.8.2) with SMTP id SAA22211; Mon, 4 Nov 1996 18:34:30 -0800 (PST) Message-Id: <3.0.32.19961104183922.006c3f40@chicago.nsd.3com.com> X-Sender: mrz@chicago.nsd.3com.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 04 Nov 1996 18:39:47 -0800 To: Jason L Tibbitts III , matthew zeier From: matthew zeier Subject: Re: unable to create output - where? Cc: majordomo-users@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Grr... I'm almost embarrassed to thank you :) Would have to be something simple too, no? thanks. - mz At 08:17 PM 11/4/96 -0600, Jason L Tibbitts III wrote: >>>>>> "mz" == matthew zeier writes: > >>> ----- The following addresses had permanent fatal errors ----- >>> "/homes/majordomo/wrapper majordomo" (expanded from: majordomo) > >Looks to me like you forgot a pipe symbol here. That should be > >"|/homes/majordomo/wrapper majordomo" > >As you have it, sendmail is trying to store the message in a file called >/homes/majordomo/wrapper, which it obviously can't. > > - J< > > ---- matthew zeier -- mrz@3com.com -- 3Com NSD Engineering -- 408/764-8420 ...................................................................... "To live and die, it seems, is a waste without a dream." - BoDeans From majordomo-users-owner Mon Nov 4 19:01:28 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA12822 for majordomo-users-outgoing; Mon, 4 Nov 1996 18:49:38 -0800 (PST) Received: from hplms26.hpl.hp.com (hplms26.hpl.hp.com [15.255.168.31]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id SAA12815 for ; Mon, 4 Nov 1996 18:49:32 -0800 (PST) Received: from irit.hpl.hp.com (dhcpp34.hpl.hp.com) by hplms26.hpl.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3+HPL1.1S) id AA014662168; Mon, 4 Nov 1996 18:49:28 -0800 Message-Id: <3.0.32.19961104185055.006d92e4@hploms.hpl.hp.com> X-Sender: kevinwu@hploms.hpl.hp.com X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Mon, 04 Nov 1996 18:51:00 -0800 To: majordomo-users@greatcircle.com From: Kevin Wu Subject: Restricted postings Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have installed Majordomo 1.94. I would like to restrict postings to senders within my company. Setting the variable restrict_post in .config to is too restrictive. I have been experimenting with taboo_headers. If I add the following line for taboo_headers, it bounces mail from within my company as expected: /^from:.*[@\.]hp.com[>\s]/i What I want is the opposite: to bounce mail from outside while accepting mail from inside. My knowledge of Perl is limited. I thought that applying XOR to the result would invert it, but the following doesn't do what I want: /^from:.*[@\.]hp.com[>\s]/i ^ 1 This accepts mail from inside and outside without being bounced. Is there a simple solution to this problem? Kevin Wu From majordomo-users-owner Mon Nov 4 22:46:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id WAA24145 for majordomo-users-outgoing; Mon, 4 Nov 1996 22:36:20 -0800 (PST) Received: from email.archlab.tuwien.ac.at (archsgi1.archlab.tuwien.ac.at [128.130.118.15]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id WAA23902 for ; Mon, 4 Nov 1996 22:29:18 -0800 (PST) Received: by email.archlab.tuwien.ac.at (951211.SGI.8.6.12.PATCH1042/940406.SGI.AUTO) for majordomo-users@GreatCircle.COM id HAA10629; Tue, 5 Nov 1996 07:27:46 +0100 From: "Martin Baehr" Message-Id: <9611050727.ZM10627@email.archlab.tuwien.ac.at> Date: Tue, 5 Nov 1996 07:27:33 +0100 In-Reply-To: Jason L Tibbitts III "Re: strange errormessage: when sending mail to majordomo" (Oct 30, 1:30) References: <9610300021.ZM2309@email.archlab.tuwien.ac.at> X-Mailer: Z-Mail (3.2.2 10apr95 MediaMail) To: majordomo-users@GreatCircle.COM Subject: Re: strange errormessage: when sending mail to majordomo Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Oct 30, 1:30, Jason L Tibbitts III wrote: > > >>>>> "MB" == Martin Baehr writes: > > MB> "|/usr/local/servers/majordomo/wrapper majordomo"... User unknown > > Did you update your alias databases? You usually have to run newaliases to > do this, though some Sendmail installations rebuild the databases > automatically. This is documented in the NEWLIST file, though we should > probably put in in INSTALL, too. i did. the alias looks like this: majordomo: "|/usr/local/servers/majordomo/wrapper majordomo" had i not updated the aliasesdb i'd have gotten: "majordomo"... User unknown since majordomo is running under the account majordom, majordomo wouldn't have existed. the point is, that sendmail seems to think that "|/usr/local/servers/majordomo/wrapper majordomo" is a normal name, instead of a pipe. thanks for the comments though, greetings, martin. -- unix systemadministrator iaeste.org iaeste.or.at iaeste.tuwien.ac.at. email.archlab.tuwien.ac.at. yumyum communications. Martin B"ahr mbaehr@iaeste.or.at From majordomo-users-owner Tue Nov 5 00:16:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id AAA28988 for majordomo-users-outgoing; Tue, 5 Nov 1996 00:07:20 -0800 (PST) Received: from horse.saberspace.com ([205.197.223.239]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id AAA28981 for ; Tue, 5 Nov 1996 00:07:14 -0800 (PST) From: scott@saberspace.com Received: from localhost (scott@localhost) by horse.saberspace.com (8.7.6/8.7.3) with SMTP id EAA10211 for ; Tue, 5 Nov 1996 04:13:33 -0500 Date: Tue, 5 Nov 1996 04:13:32 -0500 (EST) To: majordomo-users@greatcircle.com Subject: Permissions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have just installed Majordomo on my server (running Linux) and I seem to have a permissions problem. I followed the instructions carefully... Hopefully this is just a dumb oversight on my part! Everything works fine as long as the permissions for all directories and files are 777 and 666, respectively. Otherwise, even though everything is majordom.majordom, Majordomo churns away in the background until all memory is exhausted and the server crashes. I used the POSIX settings in the Makefile, inserting the UID and GID that I created for Majordomo. Any Ideas? Thanks, Scott Rothgaber From majordomo-users-owner Tue Nov 5 00:31:35 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id AAA29701 for majordomo-users-outgoing; Tue, 5 Nov 1996 00:27:20 -0800 (PST) Received: from bolis.com (waltz.rahul.net [192.160.13.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id AAA29692 for ; Tue, 5 Nov 1996 00:27:12 -0800 (PST) Received: Received: from hock.bolis.com (root@hock.bolis.com [199.165.142.10]) by bolis.com (8.7.3/8.7.3) with SMTP id XAA10228; Mon, 4 Nov 1996 23:05:47 -0800 Received: from amillar.bolis.com by hock.bolis.com with smtp (Smail3.1.28.1 #6) id m0vKfWU-000G0KC; Mon, 4 Nov 96 23:02 PST Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: Jim Dawson Date: Mon, 4 Nov 1996 22:49:11 -800 Subject: Re: Aborted address CC: Majordomo Users List X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On 4 Nov 96 at 9:32, Jim Dawson wrote: > Running MD 1.93 on BSDI 2.1. Got the following messages sent to > majordomo-owner (the actual question is at the end): > > =======================message 1================ > > Subject: MAJORDOMO ABORT > > MAJORDOMO ABORT > > HOSTILE ADDRESS - lcarin@igg2.agric.za ^^^^^^^^^^^^^^^^^^^^^^ This one is misleading. The hyphen is the real problem. Majordomo is complaining that the hyphen is a hostile address. Somebody sent in a subscription request that looked like: subscribe listname - lcaring@igg2.agric.za Majordomo aborts on the hyphen and doesn't even notice the address after it. I get an abort several time a month with HOSTILE ADDRESS - digest because someone sent in a subscription request that said subscribe listname - digest when they should have said subscribe listname-digest Majordomo probably *should* halt the command at a hyphen like that, but I think a nasty message back to the sender would be good enough, I don't think a full-blown abort is needed. But I haven't fixed it myself yet.... I figure the user will catch on sooner or later :-) - Alan ---- Alan Millar amillar@bolis.com Owner, System Admin http://www.bolis.com Ask me about Internet mailing list services at Bolis.com Batteries not included. From majordomo-users-owner Tue Nov 5 00:46:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id AAA29987 for majordomo-users-outgoing; Tue, 5 Nov 1996 00:36:24 -0800 (PST) Received: from www.mckinneyavenue.com (www.mckinneyavenue.com [199.1.135.160]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id AAA29980 for ; Tue, 5 Nov 1996 00:36:19 -0800 (PST) Received: from scomac (r122p3.onramp.net [206.50.122.3]) by www.mckinneyavenue.com (8.7.6/8.7.3) with SMTP id CAA18544 for ; Tue, 5 Nov 1996 02:38:18 -0600 Message-Id: <3.0.32.19961105023412.00685114@www.mckinneyavenue.com> X-Sender: scott@www.mckinneyavenue.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 05 Nov 1996 02:34:14 -0600 To: majordomo-users@greatcircle.com From: Scott MacFarland Subject: creating a mailing list for virtual domains Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am running multiple virtual domains on my server I would like to create a memo@domain_x.com but each list will have different users in them...Can anyone advice me to the best way to do this??? --- Scott MacFarland Mckinney Avenue System Admin 0000,0000,ffffscott@mckinneyavenue.com From majordomo-users-owner Tue Nov 5 01:31:57 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id BAA02327 for majordomo-users-outgoing; Tue, 5 Nov 1996 01:22:30 -0800 (PST) Received: from gamma.dou.dk (gamma.dou.dk [130.225.156.14]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id BAA02295 for ; Tue, 5 Nov 1996 01:22:10 -0800 (PST) Received: from dou-pc1 (peter.dou.dk [130.225.156.244]) by gamma.dou.dk (8.6.10/8.6.10) with SMTP id KAA21004; Tue, 5 Nov 1996 10:21:31 +0100 Date: Tue, 5 Nov 1996 10:21:31 +0100 Message-Id: <2.2.16.19961105111127.2a3f98d8@mail.dou.dk> X-Sender: maspsr@mail.dou.dk X-Mailer: Windows Eudora Pro Version 2.2 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Dave Wolfe From: Peter Sorensen Subject: Re: Returned mail: Can't create output: Error 0 Cc: majordomo-users@greatcircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 09.02 04-11-1996 -0600, Dave Wolfe wrote: >[ Peter Sorensen writes: ] >> >> I have a problem with release 1.93, which I got after a reinstall of >> my whole system. The problem has do to with the archive facility. >> Somehow sendmail can't write to the archive file when the permission >> is 660 but require 666. I'm not sure if this is a sendmail problem, >> but I hope someone could give me a hint. Below the message i receive >> back. >[...] >> ----- Transcript of session follows ----- >> 554 /usr/local/lib/mail/majordomo/archive/test-dou/test-dou: line 0: >> /usr/local/lib/mail/majordomo/archive/test-dou/test-dou... cannot open: >> Permission denied > >Sounds like you're trying to have sendmail just deliver to a file in >your archive directory, but we'd have to see your aliases to know for >sure. If that's the case, then of course sendmail has problems unless >the archive directory owner or group matches sendmail's. I'm using sendmail to deliver. Here's the aliase for the list: # # test-dou Mailing list # owner-test-dou:test-dou-owner test-dou:|"/usr/local/lib/mail/majordomo/sbin/wrapper resend -p bulk -M 10000 -R -l test-dou -f test-dou-owner -h mail.dou.dk -r test-dou -s test-dou-outgoing" test-dou-owner:maspsr@dou.ou.dk test-dou-approval:test-dou-owner test-dou-outgoing: :include:/usr/local/lib/mail/majordomo/lists/test-dou,test-dou-archive, |"/usr/local/lib/mail/majordomo/sbin/wrapper archive2.pl -f /usr/local/lib/mail/ majordomo/archive/test-dou/test-dou.archive -a -m" owner-test-dou-outgoing:test-dou-owner test-dou-archive:/usr/local/lib/mail/majordomo/archive/test-dou/test-dou owner-test-dou-archive:test-dou-owner test-dou-request: |"/usr/local/lib/mail/majordomo/sbin/wrapper request-answer te st-dou" owner-test-dou-request:test-dou-owner What I don't understan is why the archive need to be world writeable, when sendmail has the s bit set? regards Peter From majordomo-users-owner Tue Nov 5 03:06:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id CAA07955 for majordomo-users-outgoing; Tue, 5 Nov 1996 02:53:43 -0800 (PST) Received: from telsis2.ts.es (telsis2.ts.es [192.101.1.13]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id CAA07938 for ; Tue, 5 Nov 1996 02:53:24 -0800 (PST) Received: from pc-mej.rae.ts.es ([194.179.30.164]) by telsis2.ts.es (Netscape Mail Server v1.1) with SMTP id AAA16317 for ; Tue, 5 Nov 1996 11:55:24 -0700 Message-ID: <327F1C82.1502@ts.es> Date: Tue, 05 Nov 1996 11:52:50 +0100 From: martinez@ts.es (Jose Luis Martinez) Reply-To: jlmartinez@ts.es Organization: Telefonica Sistemas, S.A. X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk suscribe end -- ......oooooo000000oooooo...... Jose Luis Martinez Estefania Dpto.: Redes de Area Extensa TELEFONICA SISTEMAS, S.A. e-mail: jlmartinez@ts.es Telef: 34-1-3375917 Fax: 34-1-3375707 ......oooooo000000oooooo...... From majordomo-users-owner Tue Nov 5 05:31:23 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA14059 for majordomo-users-outgoing; Tue, 5 Nov 1996 05:18:19 -0800 (PST) Received: from sisko.cc.rochester.edu (sisko.cc.rochester.edu [128.151.219.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id FAA14051 for ; Tue, 5 Nov 1996 05:18:12 -0800 (PST) Received: (from kenr@localhost) by sisko.cc.rochester.edu (8.7.6/8.7.3) id IAA26360 for majordomo-users@GreatCircle.COM; Tue, 5 Nov 1996 08:21:07 -0500 (EST) Date: Tue, 5 Nov 1996 08:21:07 -0500 (EST) From: Kenneth C Rich Message-Id: <199611051321.IAA26360@sisko.cc.rochester.edu> To: majordomo-users@GreatCircle.COM Subject: digests problem Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk digest problem: archiving, index, getting without digests works great. when i then add in the aliases stuff for digests, posts to test1 list still archives, but nothing visible happens in the digesting arena. not seeing in the docs a description of what is supposed to happen, i presume that digesting works off the archive. i issue a mkdigest command as described in the quick-digest-setup file: echo mkdigest test1-digest cluefulpw | mail majordomo@testhost.blahblah the test majordomo host goes into seizure with dozens of sendmail processes flooding our sysadmin mail drop with (last count on 2nd try 2700) messages like the "abort message" below. i have tried it twice and it takes a half hour or more to recover control of the machine and clean up each time. (totally weird: the 1st time, majord's crontab got wiped off the machine too) i am tempted to cobble together digesting scripts on my own so i know what is going on, lots of code sitting around to play with for sure. hope the honorable list gods will grant this supplicant a clue. thanks! ------- system info -------------------------------------------------------- majordomo 1.94 on solaris 2.5 (sparc) -------abort message-----------want one? i have buckets of them--------------- To: Postmaster@testhost.blahblah From: Majordomo@testhost.blahblah Subject: MAJORDOMO ABORT MAJORDOMO ABORT do_exec_sendmail, mailer -fMajordomo-Owner not executable ------- sendmail permissions etc ------------------------------------------- -r-s--x--x 1 root other 312432 Oct 10 15:07 /usr/lib/sendmail -rwxrwxr-x 1 majord majord 4415 Nov 4 15:10 archive (archive2.pl) -rwxrwxr-x 1 majord majord 12163 Oct 31 13:13 digest ------- aliases ------------------------------------------------------------ test1:"|/usr/ucc/lib/majordomo/wrapper resend -l test1 -h testhost.blahblah -p bulk -f test1-owner -s test1-outgoing" test1-outgoing: :include:/usr/ucc/lib/majordomo/lists/test1, test1-archive, test1-digestify test1-request: "|/usr/ucc/lib/majordomo/wrapper request-answer test1" owner-test1: test1-owner owner-test1-outgoing: test1-owner owner-test1-request: test1-owner test1-approval: test1-owner test1-owner: kenr@bridge.blahblah, test1-archive: "|/usr/ucc/lib/majordomo/wrapper archive -a -m -f /usr/ucc/lib/majordomo/archives/test1/today" owner-test1-archive: test1-owner test1-digestify: "|/usr/ucc/lib/majordomo/wrapper digest -r -C -l test1-digest test1-digest-outgoing" test1-digest: test1 test1-digest-outgoing: :include:/usr/ucc/lib/majordomo/lists/test1-digest test1-digest-request: "|/usr/ucc/lib/majordomo/wrapper majordomo -l test1-digest" owner-test1-digest: test1-owner test1-digest-approval: test1-owner ----- test1-digest.config -----------non-null config values only------- admin_passwd = cluefulpw approve_passwd = cluefulpw date_info = yes description = digest for test1 majordomo 1.94 testing list digest_issue = 1 digest_maxdays = 3 digest_maxlines = 400 digest_name = Test Digest digest_volume = 1 get_access = list index_access = list info_access = open intro_access = list maxlength = 3000 moderate = yes precedence = bulk reply_to = $SENDER sender = owner-test1-digest strip = yes subscribe_policy = closed unsubscribe_policy = open which_access = open who_access = open ----- some majordomo.cf stuff ------------------------------------------ $homedir = "/usr/ucc/lib/majordomo"; $listdir = "$homedir/lists"; $digest_work_dir = '$homedir/digests'; $sendmail_command = "/usr/lib/sendmail"; $mailer = "$sendmail_command -oi -f\$sender"; $filedir = "$homedir/archives"; $filedir_suffix = ""; ------- dir permissions ----------------------------------------------- drwxr-sr-x 6 majord majord 512 Sep 25 16:26 /var/ucc/lib/majordomo wherein lie: drwxrws--- 2 majord majord 512 Nov 5 06:40 archives/test1 drwxrws--- 2 majord majord 512 Nov 1 09:03 archives/test1-digest drwxrws--- 2 majord majord 512 Nov 4 14:41 digests/test1 drwxrws--- 2 majord majord 512 Oct 31 13:33 digests/test1-digest which are symlinked to $homedir -- -ken rich "How many people can look at a painting for even long enough to peel an orange and eat it?" -Sir Kenneth Clark kenr@cc.rochester.edu From majordomo-users-owner Tue Nov 5 06:20:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA18535 for majordomo-users-outgoing; Tue, 5 Nov 1996 06:11:18 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA18516 for ; Tue, 5 Nov 1996 06:11:08 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA18754 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 07:11:07 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA26330 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 07:11:06 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id IAA03371; Tue, 5 Nov 1996 08:11:05 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id IAA15554; Tue, 5 Nov 1996 08:11:04 -0600 From: Dave Wolfe Message-Id: <199611051411.IAA15554@miaow.risc.sps.mot.com> Subject: Re: Returned mail: Can't create output: Error 0 To: maspsr@dou.ou.dk (Peter Sorensen) Date: Tue, 5 Nov 1996 08:11:03 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <2.2.16.19961105111127.2a3f98d8@mail.dou.dk> from "Peter Sorensen" at Nov 5, 96 10:21:31 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Peter Sorensen writes: ] > > At 09.02 04-11-1996 -0600, Dave Wolfe wrote: > >[ Peter Sorensen writes: ] > >> > >> Somehow sendmail can't write to the archive file when the > >> permission is 660 but require 666. [...] Below the message i > >> receive back. > >[...] > >> ----- Transcript of session follows ----- > >> 554 /usr/local/lib/mail/majordomo/archive/test-dou/test-dou: line 0: > >> /usr/local/lib/mail/majordomo/archive/test-dou/test-dou... cannot open: > >> Permission denied > > > >Sounds like you're trying to have sendmail just deliver to a file in > >your archive directory, but we'd have to see your aliases to know for > >sure. If that's the case, then of course sendmail has problems unless > >the archive directory owner or group matches sendmail's. > > I'm using sendmail to deliver. Here's the aliase for the list: [...] > test-dou-archive:/usr/local/lib/mail/majordomo/archive/test-dou/test-dou [...] > What I don't understan is why the archive need to be world writeable, > when sendmail has the s bit set? Sendmail has no idea who the user is in this case to change its uid to, so it just delivers to the file as itself. It would have to have a local address to know to change the working uid before delivery. Deliver to an address, such as an alias to archive2.pl (via wrapper), then the message will be archived as your majordomo user. -- Dave Wolfe From majordomo-users-owner Tue Nov 5 07:02:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA22087 for majordomo-users-outgoing; Tue, 5 Nov 1996 06:50:56 -0800 (PST) Received: from netcomi.com (www.netcomi.com [204.58.152.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA22079 for ; Tue, 5 Nov 1996 06:50:47 -0800 (PST) Received: from [204.58.155.43] (inaras.netcomi.com [204.58.155.43]) by netcomi.com (8.7.5/8.7.3) with ESMTP id JAA26014 for ; Tue, 5 Nov 1996 09:53:41 -0600 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 5 Nov 1996 08:54:36 -0600 To: majordomo-users@greatcircle.com From: Chris Fogel Subject: Can't figure out the moderated lists Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Tried the Approve: password...but still bounces... Was wondering if anyone could help me with setting up a moderated list using the resend feature.. Chris ------------------------------------------------------------------------------- Chris Fogel Phone: 214/481-5741 System Administrator Pager: 972/209-0336 Netcom Interactive mailto:fogel@netcomi.com 1607 LBJ Freeway http://www.netcomi.com Dallas, TX 75234 "She lured the dragon out of his lair with wine." From majordomo-users-owner Tue Nov 5 07:23:36 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA23064 for majordomo-users-outgoing; Tue, 5 Nov 1996 07:08:22 -0800 (PST) Received: from srv1-bsb.GNS.com.br ([200.239.56.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA23027 for ; Tue, 5 Nov 1996 07:07:53 -0800 (PST) Received: (from lioux@localhost) by srv1-bsb.GNS.com.br (8.8.2/8.8.2) id NAA07895 for majordomo-users@greatcircle.com; Tue, 5 Nov 1996 13:07:19 -0200 (EDT) From: Mario Sergio Fujikawa Ferreira Message-Id: <199611051507.NAA07895@srv1-bsb.GNS.com.br> Subject: Bug on Digest (1.94) To: majordomo-users@greatcircle.com Date: Tue, 5 Nov 1996 13:07:19 -0200 (EDT) X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I was playing with digest fine-tuning, and I got an strange behavior: The To: field on my digests had missing @fdqns. There is a mistyping in line 356 of digest. It reads: $V{'TO'} = "$opt_l@$whereami"; It should read: $V{'TO'} = "$opt_l\@$whereami"; Regards, Mario Ferreira. (lioux@gns.com.br) (lioux@bsdnet.org) From majordomo-users-owner Tue Nov 5 07:31:53 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA24123 for majordomo-users-outgoing; Tue, 5 Nov 1996 07:29:35 -0800 (PST) Received: from srv1-bsb.GNS.com.br ([200.239.56.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA24081 for ; Tue, 5 Nov 1996 07:29:04 -0800 (PST) Received: (from lioux@localhost) by srv1-bsb.GNS.com.br (8.8.2/8.8.2) id NAA08591 for majordomo-users@greatcircle.com; Tue, 5 Nov 1996 13:28:40 -0200 (EDT) From: Mario Sergio Fujikawa Ferreira Message-Id: <199611051528.NAA08591@srv1-bsb.GNS.com.br> Subject: One more problem with $list.config To: majordomo-users@greatcircle.com Date: Tue, 5 Nov 1996 13:28:40 -0200 (EDT) X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Does anyone have the least idea why the token $SENDER in the option reply_to is not being replaced by the its value when parsed. I am getting digest 'reply to' fields '$SENDER' and not "$SENDER". Any ideas?, Mario Ferreira. (lioux@gns.com.br) ps: Is there any possibility of the field resend_host being parsed for token $WHEREAMI? From majordomo-users-owner Tue Nov 5 07:35:35 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA22758 for majordomo-users-outgoing; Tue, 5 Nov 1996 07:02:16 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA22744 for ; Tue, 5 Nov 1996 07:02:05 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA26263 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 08:02:03 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA28048 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 08:01:59 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA03989; Tue, 5 Nov 1996 09:01:58 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA18259; Tue, 5 Nov 1996 09:01:56 -0600 From: Dave Wolfe Message-Id: <199611051501.JAA18259@miaow.risc.sps.mot.com> Subject: Re: Restricted postings To: kevinwu@hploms.hpl.hp.com (Kevin Wu) Date: Tue, 5 Nov 1996 09:01:56 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <3.0.32.19961104185055.006d92e4@hploms.hpl.hp.com> from "Kevin Wu" at Nov 4, 96 06:51:00 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Kevin Wu writes: ] > > I have installed Majordomo 1.94. I would like to restrict postings > to senders within my company. Setting the variable restrict_post > in .config to is too restrictive. I have > been experimenting with taboo_headers. If I add the following line > for taboo_headers, it bounces mail from within my company as expected: > > /^from:.*[@\.]hp.com[>\s]/i > > What I want is the opposite: to bounce mail from outside while accepting > mail from inside. My knowledge of Perl is limited. I thought that > applying XOR to the result would invert it, but the following doesn't > do what I want: > > /^from:.*[@\.]hp.com[>\s]/i ^ 1 > > This accepts mail from inside and outside without being bounced. > > Is there a simple solution to this problem? Perl has a logical not operator ('!') that would be more appropriate, but it looks like the grab_regexp_array processing in config_parse.pl doesn't allow one to negate the taboo regexes. The regexes that check the taboo regexes are a little arcane to say the least, but I think this patch will allow you to specify a negated regex like so: !/^from:.*[\@.]hp.com[>\s]/i Note the leading '!'. Also note that '@' needs to be escaped but '.' doesn't when it's in a character class, i.e. '[.]'. Disclaimer: This patch has undergone almost *no* testing. Apply it totally at your own risk. --- config_parse.pl.orig Sun Sep 22 19:51:08 1996 +++ config_parse.pl Tue Nov 5 08:58:31 1996 @@ -1065,8 +1065,8 @@ # m:yyy: ; `/bin/mail evil_hacker < /etc/passwd` ; "bar" =~ m:yyy: # END # - elsif (($re !~ m:^((/)|m([^\w\s])): , $dlm=($2||$3)) && - $re !~ m:^m?$dlm[^\\$dlm]*(\\.[^\\$dlm]*)*$dlm[gimosx]*$: ){ + elsif (($re !~ m:^!?((/)|m([^\w\s])): , $dlm=($2||$3)) && + $re !~ m:^!?m?$dlm[^\\$dlm]*(\\.[^\\$dlm]*)*$dlm[gimosx]*$: ){ push(@re_errors, "|$re| not a valid pattern match expression at line $.\n"); } -- Dave Wolfe From majordomo-users-owner Tue Nov 5 07:47:04 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA23810 for majordomo-users-outgoing; Tue, 5 Nov 1996 07:23:40 -0800 (PST) Received: from berean.berean.net ([207.48.63.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA23803 for ; Tue, 5 Nov 1996 07:23:30 -0800 (PST) Received: from scott.berean.net (SLT [207.48.63.5]) by berean.berean.net (8.7.6/8.7.3) with SMTP id JAA07093 for ; Tue, 5 Nov 1996 09:20:32 -0600 (CST) Message-Id: <3.0b36.32.19961105092014.00687930@berean.net> X-Sender: scott@berean.net X-Mailer: Windows Eudora Pro Version 3.0b36 (32) Date: Tue, 05 Nov 1996 09:20:20 -0600 To: Majordomo-users@GreatCircle.COM From: Scott Thomas Subject: X-Authentication-Warning Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have MJ 1.94 running, and all seems well, as far as sending, subscribing, etc. However, each message has the following header: X-Authentication-Warning: berean.berean.net: majordom set sender to owner-afa-alert@afa.net using -f I assume this means I should change some setting, but I'm afraid I can't locate anything to tell me what that would be. Can you help? Thanks, Scott Scott Thomas Berean Solutions, Inc. (601) 840-2221 http://www.berean.net From majordomo-users-owner Tue Nov 5 07:49:12 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA23113 for majordomo-users-outgoing; Tue, 5 Nov 1996 07:09:28 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA23101 for ; Tue, 5 Nov 1996 07:09:12 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA27444 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 08:09:10 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA28371 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 08:09:08 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA04220; Tue, 5 Nov 1996 09:09:08 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA14720; Tue, 5 Nov 1996 09:09:06 -0600 From: Dave Wolfe Message-Id: <199611051509.JAA14720@miaow.risc.sps.mot.com> Subject: Re: Permissions To: scott@saberspace.com Date: Tue, 5 Nov 1996 09:09:06 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "saberspace.com!scott" at Nov 5, 96 04:13:32 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ uunet!saberspace.com!scott writes: ] > > I have just installed Majordomo on my server (running Linux) and I seem to > have a permissions problem. [...] > Everything works fine as long as the permissions for all directories and > files are 777 and 666, respectively. Otherwise, even though everything is > majordom.majordom, Majordomo churns away in the background until all > memory is exhausted and the server crashes. You don't tell us what version, but maybe this will help you check some things: [This is a canned message.] You have asked a question about a "Permission denied", "Out of memory", "Bus error", "Segmentation violation", or that Majordomo runs a long time and consumes nearly all the CPU. All except the "Permission denied" are usually the result of a bug in Mj 1.93 that is triggered when you don't have Majordomo configured or installed correctly. Ask yourself the following questions. They'll give you guidance as to what you need to do to correct your Mj installation. 1) Do the ownerships and permissions on the list files, log file, and the directories where they reside allow the majordomo user to write to the files and create files in the directories? 2) Is wrapper configured and installed correctly? It must be owned by root and setuid (BSD-based systems are different: see Makefile). You can test this by logging on as a user other than root or your majordomo user and running the following *exactly as shown*: ./test ./wrapper test The first should show the uid/gids of the logon user. The second should show the majordomo uid/gids. If not, you don't have wrapper installed and/or configured correctly. Note that wrapper must be installed by the superuser (root) in order to set the owner and setuid permissions. 3) Do your aliases use wrapper to invoke the Mj programs? 4) If you're running Perl 5, is your version of Perl at least 5.001e (perl -v will display the perl version). Perl 4.019 through 4.036 will work, but 5.000 through 5.001d will not. Version 5.003 is recommended (as of this writing) if you need to upgrade. Note that some changes are required in the Mj Perl files for Perl 5 (all '@' characters in quotish strings must be escaped, e.g. "user@host.net" must be changed to "user\@host.net"). -- Dave Wolfe From majordomo-users-owner Tue Nov 5 08:31:17 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA27600 for majordomo-users-outgoing; Tue, 5 Nov 1996 08:26:37 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA27559 for ; Tue, 5 Nov 1996 08:26:23 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA11475 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 09:26:22 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA02236 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 09:26:18 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id KAA05789; Tue, 5 Nov 1996 10:26:17 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id KAA13172; Tue, 5 Nov 1996 10:26:16 -0600 From: Dave Wolfe Message-Id: <199611051626.KAA13172@miaow.risc.sps.mot.com> Subject: Re: Restricted postings (again) To: kevinwu@hploms.hpl.hp.com (Kevin Wu) Date: Tue, 5 Nov 1996 10:26:15 -0600 (CST) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Sorry to followup my own post, but I missed something obvious: [ Dave Wolfe writes: ] > > [...] I think this patch will allow you to specify a negated regex > like so: > > !/^from:.*[\@.]hp.com[>\s]/i > > Note the leading '!'. Also note that '@' needs to be escaped but '.' > doesn't when it's in a character class, i.e. '[.]'. Of course the '.' outside the character class should be escaped. !/^from:.*[\@.]hp\.com[>\s]/i ^^ -- Dave Wolfe From majordomo-users-owner Tue Nov 5 08:47:04 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA27343 for majordomo-users-outgoing; Tue, 5 Nov 1996 08:23:10 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA27325 for ; Tue, 5 Nov 1996 08:22:54 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA10887 for Majordomo-users@GreatCircle.COM; Tue, 5 Nov 96 09:22:45 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA02091 for Majordomo-users@GreatCircle.COM; Tue, 5 Nov 96 09:22:44 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id KAA05689; Tue, 5 Nov 1996 10:22:43 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id KAA14693; Tue, 5 Nov 1996 10:22:41 -0600 From: Dave Wolfe Message-Id: <199611051622.KAA14693@miaow.risc.sps.mot.com> Subject: Re: X-Authentication-Warning To: scott@berean.net (Scott Thomas) Date: Tue, 5 Nov 1996 10:22:41 -0600 (CST) Cc: Majordomo-users@GreatCircle.COM In-Reply-To: <3.0b36.32.19961105092014.00687930@berean.net> from "Scott Thomas" at Nov 5, 96 09:20:20 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Scott Thomas writes: ] > > I have MJ 1.94 running, and all seems well, as far as sending, subscribing, > etc. > > However, each message has the following header: > > X-Authentication-Warning: berean.berean.net: majordom set sender to > owner-afa-alert@afa.net using -f > > I assume this means I should change some setting, but I'm afraid I can't > locate anything to tell me what that would be. It's the trusted users in your sendmail.cf. Make majordom a trusted user and sendmail will stop complaining. -- Dave Wolfe From majordomo-users-owner Tue Nov 5 08:54:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA27518 for majordomo-users-outgoing; Tue, 5 Nov 1996 08:25:46 -0800 (PST) Received: from ginger.vnet.net (ginger.vnet.net [166.82.1.69]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA27510 for ; Tue, 5 Nov 1996 08:25:32 -0800 (PST) Received: from vnet.net (elvis.vnet.net [166.82.1.5]) by ginger.vnet.net (8.7.6/8.6.12) with SMTP id LAA16010 for ; Tue, 5 Nov 1996 11:31:09 -0500 Received: from ns.ASARian.org by vnet.net with SMTP id AA25056 (5.67b/IDA-1.5 for ); Tue, 5 Nov 1996 11:25:10 -0500 Received: from localhost (fuzzy@localhost) by ns.ASARian.org (8.6.12/8.6.12) with SMTP id LAA00587 for ; Tue, 5 Nov 1996 11:21:55 -0500 Date: Tue, 5 Nov 1996 11:21:53 -0500 (EST) From: Fuzzy To: Majordomo-users List Subject: problem with new-list and 1.93 Message-Id: X-No-Archive: yes Organization: ASARian Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk environment: linux kernel 1.2.13 (ELF+EQU patches) Linux version 1.2.13 (root@ASARian) (gcc version 2.7.0) #3 Sun Jun 30 23:12:43 EDT 1996 slackware 3.0.0 sendmail 8.6.12 220-ns.ASARian.org Sendmail 8.6.12/8.6.12 ready at Tue, 5 Nov 1996 11:08:17 -0500 perl 5.003 This is perl, version 5.003 with EMBED built under linux at Oct 23 1996 15:44:58 + suidperl security patch [message sent to postmaster] ----- The following addresses had delivery problems ----- "|/usr/bin/nice -n 15 /majordomo/majordom/wrapper new-list dif" (unrecoverable error) (expanded from: dif) ----- Transcript of session follows ----- Modification of a read-only value attempted at /majordomo/majordom/new-list line 72, chunk 1. 554 "|/usr/bin/nice -n 15 /majordomo/majordom/wrapper new-list dif"... unknown mailer error 29 Message delivered to mailing list owner-dif ----- Message header follows ----- [ Part 2: "Included Message" ] Date: Tue, 5 Nov 1996 11:03:16 -0500 From: Fuzzy To: dif@ns.asarian.org ----- Message body suppressed ----- [/message] /etc/mailing.lists # # Majordomo # majordomo: "|/usr/bin/nice -n 10 /majordomo/majordom/wrapper majordomo" majordomo-owner: fuzzy@asarian.org owner-majordomo: majordomo-owner majordom: majordomo-owner # other mailing lists clipped for bandwidth # list lines broken with \ for readabiltiy, really on on 1 line # # dif mailing list # owner-dif: fuzzy, benson@nando.net dif-owner: owner-dif owner-dif-request: dif-owner owner-dif-outgoing: dif-owner owner-dif-approval: dif-owner dif-approval: dif-owner dif-request: dif-owner dif: "|/usr/bin/nice -n 15 /majordomo/majordom/wrapper new-list dif" #dif: |"/usr/bin/nice -n 15 /majordomo/majordom/wrapper resend -l dif \ -h ns.ASARian.org dif-outgoing" dif-archiver: |"/usr/bin/nice -n 15/majordomo/majordom/wrapper archive2.pl \ -f /majordomo/archive/dif/dif -da" dif-outgoing: :include:/majordomo/lists/dif, dif-digester, dif-archiver # # dif digest # owner-dif-digest-approval: dif-owner owner-dif-digest-request: dif-owner owner-dif-digest-outgoing: dif-owner owner-dif-digest: dif-owner dif-digest-approval: dif-owner dif-digest-request: dif-owner dif-digest-owner: dif-owner dif-digest: dif dif-digester: |"/usr/bin/nice-n 15 /majordomo/majordom/wrapper digest -r -C \ -l dif-digest dif-digest-outgoing" dif-digest-outgoing: :include:/majordomo/lists/dif-digest [/alias file] we see the test user gets the usual canned message, but the append of the original text, (the test senders attempted posting), fails. so the test user gets a truncated email from listname-approval, and postmaster gets a sendmail error 29. we are unsure if this is supposed to be working in 1.93 or not. when I use the real alias posted email is delivered correctly. this tells me its probably a problem in new-list rather than other parts of md or the actual list file as resend can get sendmail to deliver to it ok. what am I doing wrong? a rather confused, fuzzy From majordomo-users-owner Tue Nov 5 10:01:54 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA06520 for majordomo-users-outgoing; Tue, 5 Nov 1996 09:59:10 -0800 (PST) Received: from mis.ca (mrburns.mis.ca [198.164.250.7]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA06450 for ; Tue, 5 Nov 1996 09:58:03 -0800 (PST) Received: from ts1-fctn-02.mis.ca (ts1-fctn-02.mis.ca [198.164.253.12]) by mis.ca (8.6.9/8.6.12) with SMTP id NAA08743 for ; Tue, 5 Nov 1996 13:55:41 -0400 Date: Tue, 5 Nov 1996 13:55:41 -0400 Comments: MiNet - Maritime Internet Services - 506-652-3624 Message-Id: <199611051755.NAA08743@mis.ca> X-Sender: kmm@mis.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: kmm@mis.ca (Susan Flewelling) Subject: question: very basic - novice Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a very simple question but one I can't seem find an answer to in the postings or in the info on majordomo on web - those of you who are using majordomo systems - have you downloaded the system into your home computers or are you linked to an ISP computer and using theirs? I have a mailing list which is through a majordomo system at Maritime Internet Services. They will cease to exist the end of the year and if it is possible to dowload this into my personal computer I'd like to do so. And if this is possible, can you tell me how much space it will require - I am going to upgrade to 8 mgs but should I go to 16 or 32? thanks and I apologize for asking such a simple basic question. Susan Flewelling Fredericton, N.B., Canada From majordomo-users-owner Tue Nov 5 10:39:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA06848 for majordomo-users-outgoing; Tue, 5 Nov 1996 10:01:17 -0800 (PST) Received: from relay.bt.net (relay.bt.net [194.72.6.52]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA06803 for ; Tue, 5 Nov 1996 10:00:57 -0800 (PST) Received: from arachnid.btinternet.com by relay.bt.net with SMTP (PP); Tue, 5 Nov 1996 17:48:37 +0000 Received: from btinternet.com (host-73-37-36.btinternet.com [194.73.37.36]) by arachnid.btinternet.com (8.7.1/8.7.1) with SMTP id RAA23539 for ; Tue, 5 Nov 1996 17:46:14 GMT Message-ID: To: majordomo-users@greatcircle.com MIME-Version: 1.0 From: Full Name Subject: List sites Date: Tue, 05 Nov 96 17:46:34 GMT Content-Type: text/plain; charset=US-ASCII; X-MAPIextension=".TXT" Content-Transfer-Encoding: quoted-printable Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am looking for an organization that actually hosts Majordomo lists for = people who want to run lists without having to master the technicalities of installing softw= are etc. ( like L-Soft does with LISTSERV). Can you help? Jim Coleman Jim.Coleman@BTInternet.com From majordomo-users-owner Tue Nov 5 12:16:21 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA09938 for majordomo-users-outgoing; Tue, 5 Nov 1996 10:51:52 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA09924 for ; Tue, 5 Nov 1996 10:51:36 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA04668 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 11:50:23 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA07171 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 11:50:21 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id MAA10780; Tue, 5 Nov 1996 12:50:20 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id LAA20036; Tue, 5 Nov 1996 11:50:59 -0600 From: Dave Wolfe Message-Id: <199611051750.LAA20036@miaow.risc.sps.mot.com> Subject: Re: problem with new-list and 1.93 To: fuzzy@ns.asarian.org (Fuzzy) Date: Tue, 5 Nov 1996 11:50:59 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Fuzzy" at Nov 5, 96 11:21:53 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Fuzzy writes: ] > > This is perl, version 5.003 with EMBED > built under linux at Oct 23 1996 15:44:58 > + suidperl security patch [...] > ----- Transcript of session follows ----- > Modification of a read-only value attempted at > /majordomo/majordom/new-list line 72, chunk 1. [...] > we are unsure if this is supposed to be working in 1.93 or not. It's a silent change in Perl 5, but the problem is fixed in Mj 1.94. Upgrade. -- Dave Wolfe From majordomo-users-owner Tue Nov 5 12:45:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA18158 for majordomo-users-outgoing; Tue, 5 Nov 1996 12:09:09 -0800 (PST) Received: from hplms26.hpl.hp.com (hplms26.hpl.hp.com [15.255.168.31]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id MAA17988 for ; Tue, 5 Nov 1996 12:08:34 -0800 (PST) Received: from irit.hpl.hp.com (dhcpp34.hpl.hp.com) by hplms26.hpl.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3+HPL1.1S) id AA165524506; Tue, 5 Nov 1996 12:08:26 -0800 Message-Id: <3.0.32.19961105120956.006e5060@hploms.hpl.hp.com> X-Sender: kevinwu@hploms.hpl.hp.com X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Tue, 05 Nov 1996 12:09:57 -0800 To: Dave Wolfe From: Kevin Wu Subject: Re: Restricted postings Cc: majordomo-users@greatcircle.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 09:01 AM 11/5/96 -0600, Dave Wolfe wrote: >Perl has a logical not operator ('!') that would be more appropriate, >but it looks like the grab_regexp_array processing in config_parse.pl >doesn't allow one to negate the taboo regexes. The regexes that check >the taboo regexes are a little arcane to say the least, but I think this >patch will allow you to specify a negated regex like so: > > !/^from:.*[\@.]hp.com[>\s]/i > >Note the leading '!'. Also note that '@' needs to be escaped but '.' >doesn't when it's in a character class, i.e. '[.]'. > >Disclaimer: This patch has undergone almost *no* testing. Apply it >totally at your own risk. > I should have added to my original post that prefixing the pattern match with '!' or 'not' causes internal mail to bounce, which is the same result as not adding these prefixes. Applying XOR to the result of the pattern match does not bounce internal mail, but it does not bounce external mail either. Kevin From majordomo-users-owner Tue Nov 5 13:43:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA21597 for majordomo-users-outgoing; Tue, 5 Nov 1996 12:38:01 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA21538 for ; Tue, 5 Nov 1996 12:37:34 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA21709 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 13:37:28 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA10765 for majordomo-users@greatcircle.com; Tue, 5 Nov 96 13:37:26 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id OAA12416; Tue, 5 Nov 1996 14:37:25 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id OAA19569; Tue, 5 Nov 1996 14:37:24 -0600 From: Dave Wolfe Message-Id: <199611052037.OAA19569@miaow.risc.sps.mot.com> Subject: Re: Restricted postings To: kevinwu@hploms.hpl.hp.com (Kevin Wu) Date: Tue, 5 Nov 1996 14:37:24 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <3.0.32.19961105120956.006e5060@hploms.hpl.hp.com> from "Kevin Wu" at Nov 5, 96 12:09:57 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Kevin Wu writes: ] > > I should have added to my original post that prefixing the pattern > match with '!' or 'not' causes internal mail to bounce, which is the > same result as not adding these prefixes. Applying XOR to the > result of the pattern match does not bounce internal mail, but it > does not bounce external mail either. I'm confused. Anything outside the // delimiters (other than the allowed modifiers [gimosx]) should've caused your .config file to fail with "... not a valid pattern match expression at line...". If you're editing the .config file directly, then you're playing with fire. Make changes with 'newconfig' requests so you know that the changes are valid. Even if it was accepted, the problem with XOR is that you're assuming that the true value is 1 and that ain't necessarily so. False is (the value) zero, (the string) "0", (the string) "", or (the value) undef. True is anything else. Depending on your regex and the eval context, it could return most anything. -- Dave Wolfe From majordomo-users-owner Tue Nov 5 14:51:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA01712 for majordomo-users-outgoing; Tue, 5 Nov 1996 14:36:25 -0800 (PST) Received: from ginger.vnet.net (ginger.vnet.net [166.82.1.69]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA01664 for ; Tue, 5 Nov 1996 14:36:06 -0800 (PST) Received: from vnet.net (elvis.vnet.net [166.82.1.5]) by ginger.vnet.net (8.7.6/8.6.12) with SMTP id RAA30422 for ; Tue, 5 Nov 1996 17:42:00 -0500 Received: from ns.ASARian.org by vnet.net with SMTP id AA12907 (5.67b/IDA-1.5 for ); Tue, 5 Nov 1996 17:35:57 -0500 Received: from localhost (fuzzy@localhost) by ns.ASARian.org (8.6.12/8.6.12) with SMTP id RAA03554 for ; Tue, 5 Nov 1996 17:35:39 -0500 Date: Tue, 5 Nov 1996 17:35:38 -0500 (EST) From: Fuzzy Reply-To: Fuzzy To: Majordomo-users List Subject: geting a 126 error from digest and 1 error from archive2.pl??? Message-Id: X-No-Archive: yes Organization: ASARian Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk environment: linux kernel 1.2.13 (ELF+EQU patches) Linux version 1.2.13 (root@ASARian) (gcc version 2.7.0) #3 Sun Jun 30 23:12:43 EDT 1996 slackware 3.0.0 sendmail 8.6.12 220-ns.ASARian.org Sendmail 8.6.12/8.6.12 ready at Tue, 5 Nov 1996 11:08:17 -0500 perl 5.003 This is perl, version 5.003 with EMBED built under linux at Oct 23 1996 15:44:58 + suidperl security patch [console output] Nov 5 17:24:04 ASARian sendmail[3375]: RAA03373: to=|"/usr/bin/nice -n 15/majordomo/majordom/wrapper archive2.pl -f /majordomo/archive/dif/dif -da", delay=00:00:06, mailer=prog, stat=unknown mailer error 1 Nov 5 17:24:05 ASARian sendmail[3375]: RAA03373: to=|"/usr/bin/nice-n 15 /majordomo/majordom/wrapper digest -r -C -l dif-digest dif-digest-outgoing", delay=00:00:07, mailer=prog, stat=unknown mailer error 126 Nov 5 17:24:06 ASARian sendmail[3370]: RAA03369: to=|"/usr/bin/nice -n 15 /majordomo/majordom/wrapper resend -l dif -h ns.ASARian.org dif-outgoing", delay=00:00:22, mailer=prog, stat=Sent Nov 5 17:24:19 ASARian sendmail[3375]: RAA03373: to=benson@nando.net, delay=00:00:21, mailer=relay, relay=email.vnet.net. [166.82.1.5], stat=Sent (Ok) Nov 5 17:24:20 ASARian sendmail[3375]: RAA03373: to="|/usr/bin/filter -vo ~/.elm/filter-errors", ctladdr=fuzzy@ns.asarian.org (501/2), delay=00:00:22, mailer=prog, stat=Sent Nov 5 17:24:20 ASARian sendmail[3375]: RAA03373: alias dif-owner => owner-dif Nov 5 17:24:20 ASARian sendmail[3375]: RAA03373: alias owner-dif => fuzzy, benson@nando.net Nov 5 17:24:21 ASARian sendmail[3375]: RAA03373: forward [/console output] /etc/mailing.lists # # Majordomo # majordomo: "|/usr/bin/nice -n 10 /majordomo/majordom/wrapper majordomo" majordomo-owner: fuzzy@asarian.org owner-majordomo: majordomo-owner majordom: majordomo-owner # other mailing lists clipped for bandwidth # list lines broken with \ for readabiltiy, really on on 1 line # # dif mailing list # owner-dif: fuzzy, benson@nando.net dif-owner: owner-dif owner-dif-request: dif-owner owner-dif-outgoing: dif-owner owner-dif-approval: dif-owner dif-approval: dif-owner dif-request: dif-owner #dif: "|/usr/bin/nice -n 15 /majordomo/majordom/wrapper new-list dif" dif: |"/usr/bin/nice -n 15 /majordomo/majordom/wrapper resend -l dif \ -h ns.ASARian.org dif-outgoing" dif-archiver: |"/usr/bin/nice -n 15/majordomo/majordom/wrapper archive2.pl \ -f /majordomo/archive/dif/dif -da" dif-outgoing: :include:/majordomo/lists/dif, dif-digester, dif-archiver # # dif digest # owner-dif-digest-approval: dif-owner owner-dif-digest-request: dif-owner owner-dif-digest-outgoing: dif-owner owner-dif-digest: dif-owner dif-digest-approval: dif-owner dif-digest-request: dif-owner dif-digest-owner: dif-owner dif-digest: dif dif-digester: |"/usr/bin/nice-n 15 /majordomo/majordom/wrapper digest -r -C \ -l dif-digest dif-digest-outgoing" dif-digest-outgoing: :include:/majordomo/lists/dif-digest [/alias file] ASARian:/majordomo/lists# ls -l *dif* -rw-rw-r-- 1 majordom majordom 38 Nov 5 17:23 dif -rw-rw-r-- 1 majordom majordom 23 Nov 5 09:28 dif-digest -rw-rw---- 1 majordom majordom 12510 Nov 5 09:35 dif-digest.config -rw-rw-r-- 1 majordom majordom 64 Nov 5 10:59 dif-posters -rw-rw---- 1 majordom majordom 12454 Nov 5 09:32 dif.config -rw-rw-r-- 1 majordom majordom 7567 Nov 5 16:45 dif.info ASARian:/majordomo/majordom# ls -l majordomo* archive2* resend* digest* wrapper -rwxrwxr-x 1 majordom majordom 7192 Nov 4 1995 archive2.pl* -rwxrwxr-x 1 majordom majordom 13191 Nov 2 1995 digest* -rwxrwxr-x 1 majordom majordom 43020 Jul 14 12:31 majordomo* -rw-rw-r-- 1 majordom majordom 4093 Nov 5 09:53 majordomo.cf -rw-rw---- 1 majordom majordom 43840 Nov 30 1995 majordomo.orig -rw-rw-r-- 1 majordom majordom 14327 Nov 2 1995 majordomo.pl -rw-rw---- 1 majordom majordom 43020 Dec 6 1995 majordomo.save -rw-rw---- 1 majordom majordom 141 Nov 2 1995 majordomo_version.pl -rwxrwxr-x 1 majordom majordom 12892 Sep 3 11:31 resend* -rw-rw---- 1 majordom majordom 3742 Nov 2 1995 resend.README -rwsr-sr-x 1 root majordom 6324 Jul 15 09:50 wrapper* also tried wrapper as 4755 -rwsr-xr-x *sighs* the email does get sent out from resend, but its not putting in a subject line? archive2 dies as does digest. what are we doing wrong?? a rather confused, fuzzy From majordomo-users-owner Tue Nov 5 15:48:00 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA05968 for majordomo-users-outgoing; Tue, 5 Nov 1996 15:42:38 -0800 (PST) Received: from ginger.vnet.net (ginger.vnet.net [166.82.1.69]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA05950 for ; Tue, 5 Nov 1996 15:42:27 -0800 (PST) Received: from vnet.net (elvis.vnet.net [166.82.1.5]) by ginger.vnet.net (8.7.6/8.6.12) with SMTP id SAA01082 for ; Tue, 5 Nov 1996 18:48:25 -0500 Received: from ns.ASARian.org by vnet.net with SMTP id AA20915 (5.67b/IDA-1.5 for ); Tue, 5 Nov 1996 18:42:23 -0500 Received: from localhost (fuzzy@localhost) by ns.ASARian.org (8.6.12/8.6.12) with SMTP id SAA04202 for ; Tue, 5 Nov 1996 18:42:20 -0500 Date: Tue, 5 Nov 1996 18:42:18 -0500 (EST) From: Fuzzy To: Majordomo-users List Subject: Fixed: geting a 126 error from digest and 1 error from archive2.pl??? Message-Id: X-No-Archive: yes Organization: ASARian Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk *blush* sorry people....we should have looked harder :( both of these aliases have typos causing them to fail when sendmail tries to expand them. we didn't get any errors mail the last few times, I guess sendmail couldn't figure out where to sned it, so it only displayed on the console/syslog. dif-archiver: |"/usr/bin/nice -n 15/majordomo/majordom/wrapper archive2.pl \ -f /majordomo/archive/dif/dif -da" dif-digester: |"/usr/bin/nice-n 15 /majordomo/majordom/wrapper digest -r -C \ -l dif-digest dif-digest-outgoing" a red faced fuzzy From majordomo-users-owner Tue Nov 5 16:18:13 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA06499 for majordomo-users-outgoing; Tue, 5 Nov 1996 15:52:11 -0800 (PST) Received: from hplms26.hpl.hp.com (hplms26.hpl.hp.com [15.255.168.31]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA06491 for ; Tue, 5 Nov 1996 15:51:59 -0800 (PST) Received: from irit.hpl.hp.com (dhcpp34.hpl.hp.com) by hplms26.hpl.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3+HPL1.1S) id AA215497905; Tue, 5 Nov 1996 15:51:45 -0800 Message-Id: <3.0.32.19961105155314.006c7fd0@hploms.hpl.hp.com> X-Sender: kevinwu@hploms.hpl.hp.com X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Tue, 05 Nov 1996 15:53:15 -0800 To: Dave Wolfe From: Kevin Wu Subject: Re: Restricted postings Cc: majordomo-users@greatcircle.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 02:37 PM 11/5/96 -0600, Dave Wolfe wrote: >[ Kevin Wu writes: ] >> >> I should have added to my original post that prefixing the pattern >> match with '!' or 'not' causes internal mail to bounce, which is the >> same result as not adding these prefixes. Applying XOR to the >> result of the pattern match does not bounce internal mail, but it >> does not bounce external mail either. > >I'm confused. Anything outside the // delimiters (other than the allowed >modifiers [gimosx]) should've caused your .config file to fail with "... >not a valid pattern match expression at line...". If you're editing the >.config file directly, then you're playing with fire. Make changes with >'newconfig' requests so you know that the changes are valid. > >Even if it was accepted, the problem with XOR is that you're assuming >that the true value is 1 and that ain't necessarily so. False is (the >value) zero, (the string) "0", (the string) "", or (the value) undef. >True is anything else. Depending on your regex and the eval context, it >could return most anything. Dave, I was editing the config file directly. Thank you for letting me know that I should be using newconfig, and for explaining why XOR may not work. The main problem is still unsolved: Can Majordomo restrict postings to people inside of a domain? I have tried '!', 'not', and '^', and they all fail. I'm sure that that this problem is common enough that Majordomo should have a simple solution if it doesn't already. Kevin From majordomo-users-owner Tue Nov 5 19:18:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA20344 for majordomo-users-outgoing; Tue, 5 Nov 1996 19:06:37 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id TAA20337 for ; Tue, 5 Nov 1996 19:06:25 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id UAA22920; Tue, 5 Nov 1996 20:57:43 -0600 (CST) To: Kevin Wu Cc: Dave Wolfe , majordomo-users@GreatCircle.COM Subject: Re: Restricted postings References: <3.0.32.19961105155314.006c7fd0@hploms.hpl.hp.com> From: Jason L Tibbitts III Date: 05 Nov 1996 20:57:42 -0600 In-Reply-To: Kevin Wu's message of Tue, 05 Nov 1996 15:53:15 -0800 Message-ID: Lines: 19 X-Mailer: Red Gnus v0.53/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "KW" == Kevin Wu writes: KW> The main problem is still unsolved: Can Majordomo restrict postings to KW> people inside of a domain? Not, it seems, without source modification. I tried some tricks using the zero-width negative lookahead assertion in perl5 and wasn't successful. However, Dave (I think) sent a source code modification that should have allowed this. Did you try it? What was the result? KW> I'm sure that that this problem is common enough that Majordomo should KW> have a simple solution if it doesn't already. Well, if the mod you were given works, it will eventually make it into the main source. It would certainly be an easier method than the one I was considering implementing. - J< From majordomo-users-owner Tue Nov 5 19:48:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA21201 for majordomo-users-outgoing; Tue, 5 Nov 1996 19:40:53 -0800 (PST) Received: from hplms26.hpl.hp.com (hplms26.hpl.hp.com [15.255.168.31]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id TAA21193 for ; Tue, 5 Nov 1996 19:40:43 -0800 (PST) Received: from irit.hpl.hp.com (dhcpp34.hpl.hp.com) by hplms26.hpl.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3+HPL1.1S) id AA261471635; Tue, 5 Nov 1996 19:40:35 -0800 Message-Id: <3.0.32.19961105194204.006ebf90@hploms.hpl.hp.com> X-Sender: kevinwu@hploms.hpl.hp.com X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Tue, 05 Nov 1996 19:42:05 -0800 To: Jason L Tibbitts III From: Kevin Wu Subject: Re: Restricted postings Cc: Dave Wolfe , majordomo-users@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 08:57 PM 11/5/96 -0600, Jason L Tibbitts III wrote: >>>>>> "KW" == Kevin Wu writes: > >KW> The main problem is still unsolved: Can Majordomo restrict postings to >KW> people inside of a domain? > >Not, it seems, without source modification. I tried some tricks using the >zero-width negative lookahead assertion in perl5 and wasn't successful. > >However, Dave (I think) sent a source code modification that should have >allowed this. Did you try it? What was the result? Jason, I tried this. The result was the same as without the modification: mail within the domain bounced. I'm using Perl 5.002 if it matters. Kevin From majordomo-users-owner Tue Nov 5 21:17:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA24092 for majordomo-users-outgoing; Tue, 5 Nov 1996 21:14:21 -0800 (PST) Received: from catwoman.cs.moravian.edu (catwoman.cs.moravian.edu [192.31.90.71]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id VAA24081 for ; Tue, 5 Nov 1996 21:14:08 -0800 (PST) Received: by catwoman.cs.moravian.edu (5.0/SMI-SVR4) id AA29872; Wed, 6 Nov 1996 00:04:20 +0500 Date: Wed, 6 Nov 1996 00:04:17 -0500 (EST) From: Mason Taube 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've tried everything to GET OFF this list and I can not do it. Is there something wrong with this list?? From majordomo-users-owner Wed Nov 6 02:01:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id BAA18676 for majordomo-users-outgoing; Wed, 6 Nov 1996 01:56:01 -0800 (PST) Received: from telsis2.ts.es (telsis2.ts.es [192.101.1.13]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id BAA18667 for ; Wed, 6 Nov 1996 01:55:30 -0800 (PST) Received: from pc-mej.rae.ts.es ([194.179.30.164]) by telsis2.ts.es (Netscape Mail Server v1.1) with SMTP id AAA13515 for ; Wed, 6 Nov 1996 10:57:48 -0700 Message-ID: <309DDB78.7844@ts.es> Date: Mon, 06 Nov 1995 10:55:04 +0100 From: martinez@ts.es (Jose Luis Martinez) Reply-To: jlmartinez@ts.es Organization: Telefonica Sistemas, S.A. X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Majordomo & Netscape Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello: Can I use majordomo with Netscape Mail Server? Thanks, in advance. -- ......oooooo000000oooooo...... Jose Luis Martinez Estefania Dpto.: Redes de Area Extensa TELEFONICA SISTEMAS, S.A. e-mail: jlmartinez@ts.es Telef: 34-1-3375917 Fax: 34-1-3375707 ......oooooo000000oooooo...... From majordomo-users-owner Wed Nov 6 07:33:46 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA05447 for majordomo-users-outgoing; Wed, 6 Nov 1996 07:18:15 -0800 (PST) Received: from odin.cair.du.edu (odin.cair.du.edu [130.253.1.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA05440 for ; Wed, 6 Nov 1996 07:18:05 -0800 (PST) Received: from [130.253.80.27] by odin.cair.du.edu; (5.65v3.2/1.1.8.2/19Apr96-0816AM) id AA23882; Wed, 6 Nov 1996 08:13:10 -0700 Message-Id: <3280ABCC.160E@du.edu> Date: Wed, 06 Nov 1996 08:16:28 -0700 From: "Victor M. Vazquez Jr." Organization: University of Denver X-Mailer: Mozilla 3.0 (WinNT; I) Mime-Version: 1.0 To: Kevin Wu Cc: Jason L Tibbitts III , Dave Wolfe , majordomo-users@GreatCircle.COM Subject: Re: Restricted postings References: <3.0.32.19961105194204.006ebf90@hploms.hpl.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Kevin Wu wrote: > > At 08:57 PM 11/5/96 -0600, Jason L Tibbitts III wrote: > >>>>>> "KW" == Kevin Wu writes: > > > >KW> The main problem is still unsolved: Can Majordomo restrict postings to > >KW> people inside of a domain? > > > >Not, it seems, without source modification. I tried some tricks using the > >zero-width negative lookahead assertion in perl5 and wasn't successful. > > > >However, Dave (I think) sent a source code modification that should have > >allowed this. Did you try it? What was the result? > > Jason, > > I tried this. The result was the same as without the modification: > mail within the domain bounced. I'm using Perl 5.002 if it matters. > > Kevin Can someone please remove me from the list. I have tried but havenot been sucessfull. thanks ! my e-mail is vvazquez@du.edu From majordomo-users-owner Wed Nov 6 08:47:25 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA08935 for majordomo-users-outgoing; Wed, 6 Nov 1996 08:18:44 -0800 (PST) Received: from pancake.remcomp.fr (pancake.remcomp.fr [194.51.30.247]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA08887 for ; Wed, 6 Nov 1996 08:18:20 -0800 (PST) From: majordomo_inVivo@invivo.remcomp.fr (majordomo inVivo) Reply-To: majordomo_inVivo@invivo.remcomp.fr To: majordomo-users@greatcircle.com, PostMaster@invivo.remcomp.fr Subject: Fwd: Re: Restricted postings Date: 06 Nov 1996 17:05:03 GMT Message-Id: <3638099934.3366097@invivo.remcomp.fr> Organization: inVivo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Kevin Wu wrote: > > At 08:57 PM 11/5/96 -0600, Jason L Tibbitts III wrote: > >>>>>> "KW" == Kevin Wu writes: > > > >KW> The main problem is still unsolved: Can Majordomo restrict postings to > >KW> people inside of a domain? > > > >Not, it seems, without source modification. I tried some tricks using the > >zero-width negative lookahead assertion in perl5 and wasn't successful. > > > >However, Dave (I think) sent a source code modification that should have > >allowed this. Did you try it? What was the result? > > Jason, > > I tried this. The result was the same as without the modification: > mail within the domain bounced. I'm using Perl 5.002 if it matters. > > Kevin Can someone please remove me from the list. I have tried but havenot been sucessfull. thanks ! my e-mail is vvazquez@du.edu end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ From majordomo-users-owner Wed Nov 6 10:04:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA15693 for majordomo-users-outgoing; Wed, 6 Nov 1996 09:50:33 -0800 (PST) Received: from pancake.remcomp.fr (pancake.remcomp.fr [194.51.30.247]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA15663 for ; Wed, 6 Nov 1996 09:50:17 -0800 (PST) From: majordomo_inVivo@invivo.remcomp.fr (majordomo inVivo) Reply-To: majordomo_inVivo@invivo.remcomp.fr To: majordomo-users@greatcircle.com, PostMaster@invivo.remcomp.fr Subject: Fwd(2): Re: Restricted postings Date: 06 Nov 1996 18:35:04 GMT Message-Id: <908521438.3690900@invivo.remcomp.fr> Organization: inVivo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Kevin Wu wrote: > > At 08:57 PM 11/5/96 -0600, Jason L Tibbitts III wrote: > >>>>>> "KW" == Kevin Wu writes: > > > >KW> The main problem is still unsolved: Can Majordomo restrict postings to > >KW> people inside of a domain? > > > >Not, it seems, without source modification. I tried some tricks using the > >zero-width negative lookahead assertion in perl5 and wasn't successful. > > > >However, Dave (I think) sent a source code modification that should have > >allowed this. Did you try it? What was the result? > > Jason, > > I tried this. The result was the same as without the modification: > mail within the domain bounced. I'm using Perl 5.002 if it matters. > > Kevin Can someone please remove me from the list. I have tried but havenot been sucessfull. thanks ! my e-mail is vvazquez@du.edu end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ From majordomo-users-owner Wed Nov 6 11:07:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA18859 for majordomo-users-outgoing; Wed, 6 Nov 1996 10:46:32 -0800 (PST) Received: from sisko.cc.rochester.edu (sisko.cc.rochester.edu [128.151.219.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA18841 for ; Wed, 6 Nov 1996 10:46:21 -0800 (PST) Received: (from kenr@localhost) by sisko.cc.rochester.edu (8.7.6/8.7.3) id NAA27479 for Majordomo-Users@GreatCircle.COM; Wed, 6 Nov 1996 13:49:11 -0500 (EST) Date: Wed, 6 Nov 1996 13:49:11 -0500 (EST) From: Kenneth C Rich Message-Id: <199611061849.NAA27479@sisko.cc.rochester.edu> To: Majordomo-Users@GreatCircle.COM Subject: unsatisfied uns*bscribers Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Can someone please r*move me from the list. I have tried but havenot > been sucessfull. i feel for his pain. ;-) regardless of whether the user was doing it right or not, i vaguely recall someone (i _think_ it was on majordomo-users) explaining there is considerable latency in this list so you get a lot of messages after uns*bscribing or some such silliness. it might be nice if such a notice, if true, were included in the majordomo-users.intro. it might also be nice if the intro went out on the list weekly, biweekly, or monthly. i know, the folks who need it would never read it. eh what? ---------------------------------------------------------------------- Subject: Majordomo results Reply-To: Majordomo@GreatCircle.COM >>>> intro majordomo-users #### No intro available for majordomo-users. ---------------------------------------------------------------------- -- -ken rich "How many people can look at a painting for even long enough to peel an orange and eat it?" -Sir Kenneth Clark kenr@cc.rochester.edu From majordomo-users-owner Wed Nov 6 11:14:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA19565 for majordomo-users-outgoing; Wed, 6 Nov 1996 10:58:08 -0800 (PST) Received: from pancake.remcomp.fr (pancake.remcomp.fr [194.51.30.247]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA19547 for ; Wed, 6 Nov 1996 10:57:56 -0800 (PST) From: majordomo_inVivo@invivo.remcomp.fr (majordomo inVivo) Reply-To: majordomo_inVivo@invivo.remcomp.fr To: majordomo-users@greatcircle.com, PostMaster@invivo.remcomp.fr Subject: Fwd(3): Re: Restricted postings Date: 06 Nov 1996 19:35:05 GMT Message-Id: <908521438.3943332@invivo.remcomp.fr> Organization: inVivo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Kevin Wu wrote: > > At 08:57 PM 11/5/96 -0600, Jason L Tibbitts III wrote: > >>>>>> "KW" == Kevin Wu writes: > > > >KW> The main problem is still unsolved: Can Majordomo restrict postings to > >KW> people inside of a domain? > > > >Not, it seems, without source modification. I tried some tricks using the > >zero-width negative lookahead assertion in perl5 and wasn't successful. > > > >However, Dave (I think) sent a source code modification that should have > >allowed this. Did you try it? What was the result? > > Jason, > > I tried this. The result was the same as without the modification: > mail within the domain bounced. I'm using Perl 5.002 if it matters. > > Kevin Can someone please remove me from the list. I have tried but havenot been sucessfull. thanks ! my e-mail is vvazquez@du.edu end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ From majordomo-users-owner Wed Nov 6 12:01:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA23203 for majordomo-users-outgoing; Wed, 6 Nov 1996 11:58:26 -0800 (PST) Received: from pancake.remcomp.fr (pancake.remcomp.fr [194.51.30.247]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA23154 for ; Wed, 6 Nov 1996 11:57:59 -0800 (PST) From: majordomo_inVivo@invivo.remcomp.fr (majordomo inVivo) Reply-To: majordomo_inVivo@invivo.remcomp.fr To: majordomo-users@greatcircle.com, PostMaster@invivo.remcomp.fr Subject: Fwd: unsatisfied uns*bscribers Date: 06 Nov 1996 20:35:10 GMT Message-Id: <382857182.4159715@invivo.remcomp.fr> Organization: inVivo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Can someone please r*move me from the list. I have tried but havenot > been sucessfull. i feel for his pain. ;-) regardless of whether the user was doing it right or not, i vaguely recall someone (i _think_ it was on majordomo-users) explaining there is considerable latency in this list so you get a lot of messages after uns*bscribing or some such silliness. it might be nice if such a notice, if true, were included in the majordomo-users.intro. it might also be nice if the intro went out on the list weekly, biweekly, or monthly. i know, the folks who need it would never read it. eh what? ---------------------------------------------------------------------- Subject: Majordomo results Reply-To: Majordomo@GreatCircle.COM >>>> intro majordomo-users #### No intro available for majordomo-users. ---------------------------------------------------------------------- -- -ken rich "How many people can look at a painting for even long enough to peel an orange and eat it?" -Sir Kenneth Clark kenr@cc.rochester.edu end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ From majordomo-users-owner Wed Nov 6 12:36:41 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA25059 for majordomo-users-outgoing; Wed, 6 Nov 1996 12:28:08 -0800 (PST) Received: from pancake.remcomp.fr (pancake.remcomp.fr [194.51.30.247]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA25050 for ; Wed, 6 Nov 1996 12:27:58 -0800 (PST) From: majordomo_inVivo@invivo.remcomp.fr (majordomo inVivo) Reply-To: majordomo_inVivo@invivo.remcomp.fr To: majordomo-users@greatcircle.com, PostMaster@invivo.remcomp.fr Subject: Fwd(4): Re: Restricted postings Date: 06 Nov 1996 21:05:03 GMT Message-Id: <908521438.4268047@invivo.remcomp.fr> Organization: inVivo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Kevin Wu wrote: > > At 08:57 PM 11/5/96 -0600, Jason L Tibbitts III wrote: > >>>>>> "KW" == Kevin Wu writes: > > > >KW> The main problem is still unsolved: Can Majordomo restrict postings to > >KW> people inside of a domain? > > > >Not, it seems, without source modification. I tried some tricks using the > >zero-width negative lookahead assertion in perl5 and wasn't successful. > > > >However, Dave (I think) sent a source code modification that should have > >allowed this. Did you try it? What was the result? > > Jason, > > I tried this. The result was the same as without the modification: > mail within the domain bounced. I'm using Perl 5.002 if it matters. > > Kevin Can someone please remove me from the list. I have tried but havenot been sucessfull. thanks ! my e-mail is vvazquez@du.edu end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ end ******************************************************************** Sent by inVivo. The BBS of Life Sciences, Paris, France, info@invivo.edu http://www.invivo.net/ From majordomo-users-owner Wed Nov 6 12:43:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA25342 for majordomo-users-outgoing; Wed, 6 Nov 1996 12:30:43 -0800 (PST) Received: from free-me.marben.be (gatekeeper.marben.be [194.78.27.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id MAA25186 for ; Wed, 6 Nov 1996 12:29:17 -0800 (PST) Received: (from smap@localhost) by free-me.marben.be (8.7.5/8.7.3) id VAA12765 for <@gatekeeper.marben.be:majordomo-users@GreatCircle.COM>; Wed, 6 Nov 1996 21:29:09 +0100 (MET) X-Authentication-Warning: free-me.marben.be: smap set sender to using -f Received: from tarifa.marben.be(172.20.0.254) by free-me.marben.be via smap (V1.3) id sma012763; Wed Nov 6 21:28:53 1996 Received: from tarifa.marben.be by tarifa via SMTP (940816.SGI.8.6.9/940406.SGI.AUTO) for id VAA04312; Wed, 6 Nov 1996 21:23:19 +0100 Message-ID: <3280F3B6.1372@marben.be> Date: Wed, 06 Nov 1996 21:23:18 +0100 From: Jean-Pierre Morant Organization: Marben SA-NV X-Mailer: Mozilla 3.0Gold (X11; I; IRIX 5.3 IP22) MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Originator set to owner-listname Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi ! I'm having (yet another) small problem with my lists - but this should be no big deal. Using Maj. 1.93 together with sendmail, I've set up a moderated list. Everythings goes fine but the mails appears as coming from "owner-listname" where I would expect "listname" .... In my maillog file there is a message teling me that ... sendmail[4600]: VAA04600: Authentication-Warning: fresco.marben.be: majordom set sender to owner-marben using -f (marben is the name of the list). ????? Could someone tell me what I'm doing wrong ??? Here is a fragment of my aliases : owner-marben:test@tarifa owner-marben-outgoing:owner-marben marben-approval:test@tarifa owner-marben-info:marinf@fresco marben: "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -R -l marben -h tarifa -A -a /tmp/marben.passwd marben-outgoing" #marben: "|/usr/local/majordomo/wrapper resend -l marben -h tarifa marben-outgoing" #marben-outgoing::include:/usr/local/majordomo/lists/marben marben-outgoing::include:/usr/local/majordomo/lists/marben, "|/usr/local/bin/mhonarc -add -outdir /usr/local/majordomo/lists/marben.archive", "|/usr/local/majordomo/wrapper archive -a -d -f /usr/local/majordomo/lists/marben.archive/marben" marben-request: "|/usr/local/majordomo/wrapper majordomo -l marben" Thanks a 1000 times (very very long days behind a computer's screen tend to make me extremely grateful - actually I was even considering 10 000 ;-) JPM -- Jean-Pierre Morant c/o MARBEN S.A./N.V. La vie serait tellement Boulevard du Souverain,400, Vorstlaan plus facile 1160 Bruxelles Si seulement Belgium nous avions les sources.... + 32 2 663 1130 (phone) + 32 2 663 1199 (fax) http://www.marben.be jpm@marben.be From majordomo-users-owner Wed Nov 6 13:47:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA29970 for majordomo-users-outgoing; Wed, 6 Nov 1996 13:38:23 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id NAA29943 for ; Wed, 6 Nov 1996 13:38:10 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA16260 for majordomo-users@GreatCircle.COM; Wed, 6 Nov 96 14:38:12 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA14181 for majordomo-users@GreatCircle.COM; Wed, 6 Nov 96 14:38:10 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id PAA01936; Wed, 6 Nov 1996 15:38:09 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id PAA11657; Wed, 6 Nov 1996 15:38:08 -0600 From: Dave Wolfe Message-Id: <199611062138.PAA11657@miaow.risc.sps.mot.com> Subject: Re: Originator set to owner-listname To: jpm@marben.be (Jean-Pierre Morant) Date: Wed, 6 Nov 1996 15:38:08 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <3280F3B6.1372@marben.be> from "Jean-Pierre Morant" at Nov 6, 96 09:23:18 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Jean-Pierre Morant writes: ] > > Everythings goes fine but the mails appears as coming from > "owner-listname" where I would expect "listname" .... > > In my maillog file there is a message teling me that ... > sendmail[4600]: VAA04600: Authentication-Warning: fresco.marben.be: > majordom set sender to owner-marben using -f > > (marben is the name of the list). > > ????? > > Could someone tell me what I'm doing wrong ??? Doesn't look to me like you're doing anything wrong unless the messages should actually appear to be coming from the original sender, in which case you're not inserting the Approved header correctly and thus losing the original headers. You can get rid of the Authentication-Warning by making majordom (or whatever your majordomo user is) trusted by sendmail in the sendmail.cf file. -- Dave Wolfe From majordomo-users-owner Wed Nov 6 20:47:44 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA01276 for majordomo-users-outgoing; Wed, 6 Nov 1996 20:43:55 -0800 (PST) Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id UAA01267 for ; Wed, 6 Nov 1996 20:43:44 -0800 (PST) Received: (from smap@localhost) by mailgate.Cadence.COM (8.6.8/8.6.8) id VAA19948; Wed, 6 Nov 1996 21:43:46 -0700 Received: from jewels.cadence.com(158.140.32.165) by mailgate.cadence.com via smap (V1.0mjr) id sma847332244.022638; Wed Nov 6 19:04:04 1996 Received: (from julian@localhost) by jewels.Cadence.COM (8.6.8/8.6.8) id SAA15442; Wed, 6 Nov 1996 18:04:01 -0800 Date: Wed, 6 Nov 1996 18:04:01 -0800 From: Julian Gordon Message-Id: <199611070204.SAA15442@jewels.Cadence.COM> To: kevinwu@hploms.hpl.hp.com Subject: Re: Restricted postings Cc: majordomo-users@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: IS+KeMNVUz+L5lsRIk2fDQ== Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Kevin, I have a script that I wrote that automatically subscribes people (when the subscription list is closed) from a persons company (it uses yp to ascertain that the person is a member. But could use any mechanism for doing so, even a static address - like x.com). It uses -approval. Julian > From majordomo-users-owner@GreatCircle.COM Wed Nov 6 03:42:01 1996 > > I have installed Majordomo 1.94. I would like to restrict postings > to senders within my company. Setting the variable restrict_post > in .config to is too restrictive. I have > been experimenting with taboo_headers. If I add the following line > for taboo_headers, it bounces mail from within my company as expected: > > /^from:.*[@\.]hp.com[>\s]/i > > What I want is the opposite: to bounce mail from outside while accepting > mail from inside. My knowledge of Perl is limited. I thought that > applying XOR to the result would invert it, but the following doesn't > do what I want: > > /^from:.*[@\.]hp.com[>\s]/i ^ 1 > > This accepts mail from inside and outside without being bounced. > > Is there a simple solution to this problem? > > Kevin Wu From majordomo-users-owner Thu Nov 7 04:03:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id DAA19872 for majordomo-users-outgoing; Thu, 7 Nov 1996 03:46:34 -0800 (PST) Received: from sisko.cc.rochester.edu (sisko.cc.rochester.edu [128.151.219.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id DAA19821 for ; Thu, 7 Nov 1996 03:46:11 -0800 (PST) Received: (from kenr@localhost) by sisko.cc.rochester.edu (8.7.6/8.7.3) id GAA27983; Thu, 7 Nov 1996 06:45:24 -0500 (EST) Date: Thu, 7 Nov 1996 06:45:24 -0500 (EST) From: Kenneth C Rich Message-Id: <199611071145.GAA27983@sisko.cc.rochester.edu> To: kevinwu@hploms.hpl.hp.com Subject: Re: digests problem Cc: majordomo-users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk -kevin wrote-------------------------------------------------------- > At 08:21 AM 11/5/96 -0500, you wrote: > >digest problem: > > > >To: Postmaster@testhost.blahblah > >From: Majordomo@testhost.blahblah > >Subject: MAJORDOMO ABORT > > > >MAJORDOMO ABORT > > > >do_exec_sendmail, mailer -fMajordomo-Owner not executable > Kenneth, > Did anyone give you an answer? I got this abort too. This abort > happens at line 375 of majordomo.pl. This line is testing whether > '-fMajordomo-Owner' is an executable file, and of course it is not > since this parameter is not even a file. > Kevin ---------------------------------------------------------------------- no answers or clues from the list yet. that piece of code looked suspicious to me, but i wasnt willing to get too down and dirty. testing -fMajordomo-owner for executability looks symptomatic of bad error processing, but the actual error may be something quite unrelated. i was on the verge of announcing here that majordomo 1.94 does not do digesting and leaving it at that but i kept picking at a script to do a piece of the digesting thing, thinking it can't be that hard what with archiving working so sweetly. that script uncovered for me an error in my majordomo.cf and some time today i plan to see if fixing that error fixes digesting. i will tell you the results of my experiment when i have them. my error is in the line where the original sample.cf says: $digest_work_dir = '/usr/local/mail/digest'; i interpolated a variable in the assigned value without changing the single quotes to double quotes. one of the serious perils of using perl as the config language is that the stupid user (me) must then know perl syntax! i know i saw an error message somewhere with the '$homedir/digests' string in it. so i know that majordomo is getting at least far enough into digesting to trip over it. so i will change my: $digest_work_dir = '$homedir/digests'; to $digest_work_dir = "$homedir/digests"; and test. later. when i have reinforcements. -- -ken rich // kenr@cc.rochester.edu From majordomo-users-owner Thu Nov 7 05:18:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA21865 for majordomo-users-outgoing; Thu, 7 Nov 1996 05:09:23 -0800 (PST) Received: from antares.linf.unb.br ([164.41.12.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id FAA21858 for ; Thu, 7 Nov 1996 05:08:54 -0800 (PST) Received: (from luthor@localhost) by antares.linf.unb.br (8.8.2/8.7.3) id LAA12963; Thu, 7 Nov 1996 11:02:58 -0200 (EDT) Date: Thu, 7 Nov 1996 11:02:48 -0200 (EDT) From: Lex Luthor X-Sender: luthor@antares To: majordomo-users@greatcircle.com Subject: Problems Installing Majordomo - HELP ! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I'm trying to install majordomo on a FreeBSD Box. I compiled it with POSIX flags,. The version of majordomo is 1.94, and my version of perl is 5.002. I created a user called majordom, group majordom, modified Makefile to theese flags, installed and no error messages. Created /etc/aliases aliases for majordomo : majordomo: "|/usr/local/majordomo/wrapper majordomo" When I send a mail to majordomo like : echo 'lists'|mail majordomo (also tried with pine), the system returns the following message : ----- The following addresses have delivery notifications ----- "|/usr/local/majordomo/wrapper majordomo" (unrecoverable error) (expanded from: majordomo@juris.prdf.mpf.gov.br) ----- Transcript of session follows ----- Message delivered to mailing list majordomo@juris.prdf.mpf.gov.br /usr/local/majordomo/wrapper: permission denied 554 "|/usr/local/majordomo/wrapper majordomo"... unknown mailer error 2 It looks like permissions problems, and after read the FAQ, I put the permissions like this : drwxrwx--- 6 majordom majordom 512 Nov 7 10:17 . drwxr-xr-x 19 root wheel 512 Nov 7 09:30 .. -rw------- 1 majordom majordom 4 Nov 6 12:36 .majordomo_registration drwxrwx--- 3 root majordom 512 Nov 7 10:18 Doc -rwxrwx--- 1 majordom majordom 0 Nov 6 12:35 Log drwxrwx--- 2 majordom majordom 512 Nov 6 12:34 Tools drwxrwx--- 2 majordom majordom 512 Nov 6 12:34 bin -rw-rw---- 1 majordom majordom 2777 Nov 6 12:34 bounce-remind -rw-rw---- 1 majordom majordom 8833 Nov 6 12:34 config-test -rw-rw---- 1 majordom majordom 47928 Nov 6 12:34 config_parse.pl drwxrwx--- 2 majordom majordom 512 Nov 6 12:46 listas -rwxrwx--- 1 majordom majordom 55409 Nov 6 12:34 majordomo -rw-rw---- 1 majordom majordom 8665 Nov 7 09:56 majordomo.cf -rw-rw---- 1 majordom majordom 19828 Nov 7 10:05 majordomo.pl -rw-rw---- 1 majordom majordom 124 Nov 6 12:34 majordomo_version.pl -rw-rw---- 1 majordom majordom 3492 Nov 6 12:34 request-answer -rwxrwx--- 1 majordom majordom 29608 Nov 6 12:34 resend -rw-rw---- 1 majordom majordom 2803 Nov 6 12:37 results-config -rw-rw---- 1 majordom majordom 8627 Nov 6 12:34 sample.cf -rw-rw---- 1 majordom majordom 7547 Nov 6 12:34 shlock.pl -rwxrwx--- 1 majordom majordom 12967 Nov 7 09:52 wrapper Does anybodyy knows what's is going on ? Oh, yes the perl permissions are ok and are in /usr/local/bin; Abracos, --- _________________________________ _________________________ / Alex Carlos Braga Antao \ /_ __ \ | UnB - Universidade de Brasilia | // ...on IRC | | | // ____ | | e-mail : luthor@linf.unb.br | // / _/________ | | http://www.linf.unb.br/~luthor | /____ /_/ / /) (_) / | \_________________________________/ \_______It's me !_________/ From majordomo-users-owner Thu Nov 7 06:05:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA23010 for majordomo-users-outgoing; Thu, 7 Nov 1996 05:50:45 -0800 (PST) Received: from rs232.bb-elec.com ([206.1.0.34]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id FAA22976 for ; Thu, 7 Nov 1996 05:50:20 -0800 (PST) Received: from corncam ([206.1.0.98]) by rs232.bb-elec.com (8.7.3/8.7.3) with SMTP id IAA14584; Thu, 7 Nov 1996 08:15:40 -0600 (CST) Message-Id: <199611071415.IAA14584@rs232.bb-elec.com> Comments: Authenticated sender is From: "Bill Franklin III" Organization: B&B Electronics Mfg Co To: Kenneth C Rich Date: Thu, 7 Nov 1996 06:52:56 -0600 Subject: Re: digests problem Reply-to: bfranklin@bb-elec.com CC: majordomo-users@GreatCircle.COM X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > -kevin wrote-------------------------------------------------------- > > At 08:21 AM 11/5/96 -0500, you wrote: > > >digest problem: > > > > > >To: Postmaster@testhost.blahblah > > >From: Majordomo@testhost.blahblah > > >Subject: MAJORDOMO ABORT > > > > > >MAJORDOMO ABORT > > > > > >do_exec_sendmail, mailer -fMajordomo-Owner not executable I am having the same problem.. the digest that came with 1.93 seems to still work okay.. if you use perl 4 anyway.. it seems to depend on how you use digest.. I have one list that uses the mkdigest command to force a digest. the others all use size as the digest trigger.. they seem to be working fine with the old version but the mkdigest command will not work .. as for the new version.. while Majordomo does seem to give wrong error messages alot I messed around with the do_exec_sendmail routing in majordomo.pl.. I hardcoded the $mail_prog var with the correct sendmail command and made some headway.. got one digest to go out.. but there were several other things going wrong.. from the error it looks as though the vars are getting set wrong.. BTW when you get the do_exec_sendmail error.. does it repeat until you kill the proccess? thanks.. bill Bill Franklin III - bfrankln@bb-elec.com B&B Electronics Mfg Co http://www.bb-elec.com Phone 815-433-5100 x213 - Fax 815-434-7094 From majordomo-users-owner Thu Nov 7 06:19:41 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA23795 for majordomo-users-outgoing; Thu, 7 Nov 1996 06:04:27 -0800 (PST) Received: from i2bs.com (i2bs.com [205.242.194.21]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA23782 for ; Thu, 7 Nov 1996 06:04:15 -0800 (PST) Received: from skb.sbcomp.net (bernoulli-00.inpi.com [207.152.80.100]) by i2bs.com (8.7.5/8.7.3) with SMTP id IAA09333; Thu, 7 Nov 1996 08:03:38 -0600 (CST) Message-Id: <3.0.32.19961107080306.006bc10c@205.242.194.21> X-Sender: skb@205.242.194.21 X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Thu, 07 Nov 1996 08:04:04 -0600 To: Lex Luthor From: "Steven K. Buehler" Subject: Re: Problems Installing Majordomo - HELP ! Cc: majordomo-users@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 11:02 AM 11/7/96 -0200, you wrote: > ----- The following addresses have delivery notifications ----- >"|/usr/local/majordomo/wrapper majordomo" (unrecoverable error) > (expanded from: majordomo@juris.prdf.mpf.gov.br) > > ----- Transcript of session follows ----- >Message delivered to mailing list majordomo@juris.prdf.mpf.gov.br >/usr/local/majordomo/wrapper: permission denied >554 "|/usr/local/majordomo/wrapper majordomo"... unknown mailer error 2 >-rwxrwx--- 1 majordom majordom 12967 Nov 7 09:52 wrapper Unless your wrapper is part of the daemon group (or whatever group that your mailer runs under) you will get that error since you don't have world execute permissions on the file (which you don't want). Set your wrapper up as either owned by majordom and the group of daemon or put your majordom in the daemon group. ====================================================== Steven K. Buehler S & B Computers Rockford Illinois, USA Phone: 815-398-7169 Fax: 815-398-7266 ====================================================== From majordomo-users-owner Thu Nov 7 06:24:37 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA23796 for majordomo-users-outgoing; Thu, 7 Nov 1996 06:04:33 -0800 (PST) Received: from horse.saberspace.com ([205.197.223.239]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA23781 for ; Thu, 7 Nov 1996 06:04:14 -0800 (PST) From: scott@saberspace.com Received: from localhost (scott@localhost) by horse.saberspace.com (8.7.6/8.7.3) with SMTP id JAA05543; Thu, 7 Nov 1996 09:02:43 -0500 Date: Thu, 7 Nov 1996 09:02:43 -0500 (EST) To: Lex Luthor cc: majordomo-users@GreatCircle.COM Subject: Re: Problems Installing Majordomo - HELP ! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Sounds familiar! Try making EVERYTHING 777, and I bet it'll work. I just installed 1.94 on Linux 2.0.18 hoping that the permission thing would be cleared up. I followed the docs (which were GREATLY improved!) verbatim. I then ran the tests and everything is Kosher. However, unless everything is world writable, it won't run. If you or anyone else figure out what is causing this, I would really like to know. Thanks, Scott Rothgaber * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Break the stranglehold of the Evil Software Empire. * * Ask me about becoming Micro$oft-Free with Linux, * * a free implementation of UNIX, featuring X-Windows. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * On Thu, 7 Nov 1996, Lex Luthor wrote: > Hi, > > I'm trying to install majordomo on a FreeBSD Box. I compiled it with > POSIX flags,. The version of majordomo is 1.94, and my version of perl is > 5.002. > I created a user called majordom, group majordom, modified Makefile to > theese flags, installed and no error messages. > Created /etc/aliases aliases for majordomo : > majordomo: "|/usr/local/majordomo/wrapper majordomo" > > When I send a mail to majordomo like : > echo 'lists'|mail majordomo > (also tried with pine), the system returns the following message : > > ----- The following addresses have delivery notifications ----- > "|/usr/local/majordomo/wrapper majordomo" (unrecoverable error) > (expanded from: majordomo@juris.prdf.mpf.gov.br) > > ----- Transcript of session follows ----- > Message delivered to mailing list majordomo@juris.prdf.mpf.gov.br > /usr/local/majordomo/wrapper: permission denied > 554 "|/usr/local/majordomo/wrapper majordomo"... unknown mailer error 2 > > It looks like permissions problems, and after read the FAQ, I put the > permissions like this : > > drwxrwx--- 6 majordom majordom 512 Nov 7 10:17 . > drwxr-xr-x 19 root wheel 512 Nov 7 09:30 .. > -rw------- 1 majordom majordom 4 Nov 6 12:36 .majordomo_registration > drwxrwx--- 3 root majordom 512 Nov 7 10:18 Doc > -rwxrwx--- 1 majordom majordom 0 Nov 6 12:35 Log > drwxrwx--- 2 majordom majordom 512 Nov 6 12:34 Tools > drwxrwx--- 2 majordom majordom 512 Nov 6 12:34 bin > -rw-rw---- 1 majordom majordom 2777 Nov 6 12:34 bounce-remind > -rw-rw---- 1 majordom majordom 8833 Nov 6 12:34 config-test > -rw-rw---- 1 majordom majordom 47928 Nov 6 12:34 config_parse.pl > drwxrwx--- 2 majordom majordom 512 Nov 6 12:46 listas > -rwxrwx--- 1 majordom majordom 55409 Nov 6 12:34 majordomo > -rw-rw---- 1 majordom majordom 8665 Nov 7 09:56 majordomo.cf > -rw-rw---- 1 majordom majordom 19828 Nov 7 10:05 majordomo.pl > -rw-rw---- 1 majordom majordom 124 Nov 6 12:34 majordomo_version.pl > -rw-rw---- 1 majordom majordom 3492 Nov 6 12:34 request-answer > -rwxrwx--- 1 majordom majordom 29608 Nov 6 12:34 resend > -rw-rw---- 1 majordom majordom 2803 Nov 6 12:37 results-config > -rw-rw---- 1 majordom majordom 8627 Nov 6 12:34 sample.cf > -rw-rw---- 1 majordom majordom 7547 Nov 6 12:34 shlock.pl > -rwxrwx--- 1 majordom majordom 12967 Nov 7 09:52 wrapper > > Does anybodyy knows what's is going on ? > Oh, yes the perl permissions are ok and are in /usr/local/bin; > > Abracos, > --- > _________________________________ _________________________ > / Alex Carlos Braga Antao \ /_ __ \ > | UnB - Universidade de Brasilia | // ...on IRC | > | | // ____ | > | e-mail : luthor@linf.unb.br | // / _/________ | > | http://www.linf.unb.br/~luthor | /____ /_/ / /) (_) / | > \_________________________________/ \_______It's me !_________/ > > > From majordomo-users-owner Thu Nov 7 06:32:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA24510 for majordomo-users-outgoing; Thu, 7 Nov 1996 06:24:58 -0800 (PST) Received: from antares.linf.unb.br ([164.41.12.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA24481 for ; Thu, 7 Nov 1996 06:24:38 -0800 (PST) Received: (from luthor@localhost) by antares.linf.unb.br (8.8.2/8.7.3) id MAA13216; Thu, 7 Nov 1996 12:18:24 -0200 (EDT) Date: Thu, 7 Nov 1996 12:18:17 -0200 (EDT) From: Lex Luthor X-Sender: luthor@antares To: "Steven K. Buehler" cc: majordomo-users@GreatCircle.COM Subject: Re: Problems Installing Majordomo - HELP ! In-Reply-To: <3.0.32.19961107080306.006bc10c@205.242.194.21> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 7 Nov 1996, Steven K. Buehler wrote: It didn't work. I've already installed it with GID deamon, and the same message acurred. An Interesting test I did : From prompt I put : echo lists |wrapper majordomo When theowners was majordom.majordom for the wrapper, I got : su: echop: command not found wrapper: error: Not running with proper UID and GID. Make certain that wrapper is installed setuid, and if so, recompile with POSIX flags. and when the owners was root.majordom, I got : su: echop: command not found /usr/local/majordomo/majordomo: starting /usr/local/majordomo/majordomo: requires succeeded. Setting defaults. /usr/local/majordomo/majordomo: done with defaults, parsing mail header. /usr/local/majordomo/majordomo: setting log file. addr_match: enter addr_match: comparing against majordomo@juris.prdf.mpf.gov.br majordomo@juris.prdf.mpf.gov.br: is not a valid return address. The user majordom is on deamon group. > At 11:02 AM 11/7/96 -0200, you wrote: > > ----- The following addresses have delivery notifications ----- > >"|/usr/local/majordomo/wrapper majordomo" (unrecoverable error) > > (expanded from: majordomo@juris.prdf.mpf.gov.br) > > > > ----- Transcript of session follows ----- > >Message delivered to mailing list majordomo@juris.prdf.mpf.gov.br > >/usr/local/majordomo/wrapper: permission denied > >554 "|/usr/local/majordomo/wrapper majordomo"... unknown mailer error 2 > >-rwxrwx--- 1 majordom majordom 12967 Nov 7 09:52 wrapper > > Unless your wrapper is part of the daemon group (or whatever group that > your mailer runs under) you will get that error since you don't have world > execute permissions on the file (which you don't want). Set your wrapper > up as either owned by majordom and the group of daemon or put your majordom > in the daemon group. > > ====================================================== > Steven K. Buehler > S & B Computers > Rockford Illinois, USA > Phone: 815-398-7169 > Fax: 815-398-7266 > ====================================================== > Abracos, --- _________________________________ _________________________ / Alex Carlos Braga Antao \ /_ __ \ | UnB - Universidade de Brasilia | // ...on IRC | | | // ____ | | e-mail : luthor@linf.unb.br | // / _/________ | | http://www.linf.unb.br/~luthor | /____ /_/ / /) (_) / | \_________________________________/ \_______It's me !_________/ From majordomo-users-owner Thu Nov 7 07:03:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA25728 for majordomo-users-outgoing; Thu, 7 Nov 1996 07:00:21 -0800 (PST) Received: from webdreams.com (www.webdreams.com [192.80.84.132]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA25660 for ; Thu, 7 Nov 1996 07:00:02 -0800 (PST) Received: from localhost by webdreams.com (5.65v3.2/1.1.10.5/29Aug96-0251AM) id AA08791; Thu, 7 Nov 1996 09:55:52 -0500 Date: Thu, 7 Nov 1996 09:55:52 -0500 (EST) From: Brock Rozen To: Kenneth C Rich Cc: kevinwu@hploms.hpl.hp.com, majordomo-users@GreatCircle.COM Subject: Re: digests problem In-Reply-To: <199611071145.GAA27983@sisko.cc.rochester.edu> Message-Id: X-Url: http://www.webdreams.com/~brozen Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 7 Nov 1996, Kenneth C Rich wrote: > i was on the verge of announcing here that majordomo 1.94 does not do > digesting and leaving it at that but i kept picking at a script to do a > piece of the digesting thing, thinking it can't be that hard what with > archiving working so sweetly. that script uncovered for me an error in > my majordomo.cf and some time today i plan to see if fixing that error > fixes digesting. i will tell you the results of my experiment when i > have them. It works fine for me. I have a few thousand people on one of my digests lists and it works without a hitch. You need to make sure that all your directories are set properly and are actually there with the proper permissions. ------------------------------------------------------------------------- | Brock Rozen | brozen@webdreams.com | http://www.webdreams.com/~brozen | ------------------------------------------------------------------------- From majordomo-users-owner Thu Nov 7 07:18:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA25902 for majordomo-users-outgoing; Thu, 7 Nov 1996 07:01:57 -0800 (PST) Received: from webdreams.com (www.webdreams.com [192.80.84.132]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA25632 for ; Thu, 7 Nov 1996 06:59:26 -0800 (PST) Received: from localhost by webdreams.com (5.65v3.2/1.1.10.5/29Aug96-0251AM) id AA09218; Thu, 7 Nov 1996 09:58:07 -0500 Date: Thu, 7 Nov 1996 09:58:07 -0500 (EST) From: Brock Rozen To: Bill Franklin III Cc: Kenneth C Rich , majordomo-users@GreatCircle.COM Subject: Re: digests problem In-Reply-To: <199611071415.IAA14584@rs232.bb-elec.com> Message-Id: X-Url: http://www.webdreams.com/~brozen Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 7 Nov 1996, Bill Franklin III wrote: > the others all use size as the digest trigger.. they seem to be working fine > with the old version but the mkdigest command will not work .. Everything works fine if you set it up properly. I've used the mkdigest, size, whatever. I use digest is whatever format it CAN work, and with success. I've been using 1.94 digest (alpha and beta) all the way back starting with a3 or so. > as for the new version.. while Majordomo does seem to give wrong error messages > alot I messed around with the do_exec_sendmail routing in majordomo.pl.. I > hardcoded the $mail_prog var with the correct sendmail command and made some > headway.. got one digest to go out.. but there were several other things going > wrong.. from the error it looks as though the vars are getting set wrong.. > > BTW when you get the do_exec_sendmail error.. does it repeat until you kill the > proccess? Yes, it does. Make sure: 1) THe work directory exists , and a seperate one for each list at that within the work directory 2) THe archive directory exists Both of the above, if not setup right, will generate that error message. ------------------------------------------------------------------------- | Brock Rozen | brozen@webdreams.com | http://www.webdreams.com/~brozen | ------------------------------------------------------------------------- From majordomo-users-owner Thu Nov 7 08:19:52 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA29441 for majordomo-users-outgoing; Thu, 7 Nov 1996 08:13:47 -0800 (PST) Received: from hermes.etheron.net (HERMES.ETHERON.NET [200.30.8.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA29432 for ; Thu, 7 Nov 1996 08:13:31 -0800 (PST) Received: from [200.30.8.66] by hermes.etheron.net (NTMail 3.02.07) with ESMTP id la072317 for ; Wed, 6 Nov 1996 21:27:04 -0400 Message-ID: <327EE49B.487F@etheron.net> Date: Tue, 05 Nov 1996 02:54:19 -0400 From: "Juan J. Vieira" Organization: UCV X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: majordomo-users@GreatCircle.com Subject: Log File Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello, I have Majordomo 1.94 and Linux, When i Mail a message Majordomo Abort and give me an Error with the Log file. The Error is that majordomo can't write in the log file, because the permissions is wrong I Have to create the Log file? What Information have the Log file? Which are the permissions of the Log file? Please reply me Jvieira@etheron.net Thank you Juan J. Vieira From majordomo-users-owner Thu Nov 7 08:34:00 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA29158 for majordomo-users-outgoing; Thu, 7 Nov 1996 08:07:52 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA29138 for ; Thu, 7 Nov 1996 08:07:36 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id LAA24279; Thu, 7 Nov 1996 11:07:33 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id LAA24907; Thu, 7 Nov 1996 11:07:25 -0500 (EST) Message-Id: <199611071607.LAA24907@augusta.math.psu.edu> To: scott@saberspace.com cc: Lex Luthor , majordomo-users@GreatCircle.COM Subject: Re: Problems Installing Majordomo - HELP ! In-reply-to: Your message of "Thu, 07 Nov 1996 09:02:43 EST." References: 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 Nov 1996 11:07:23 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , scot t@saberspace.com writes: >Sounds familiar! Try making EVERYTHING 777, and I bet it'll work. Yeah, and I bet you don't worry about those silly things called passwords either. This problem is covered in question 2.2 of the current Majordomo FAQ. --Dave From majordomo-users-owner Thu Nov 7 08:43:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA28846 for majordomo-users-outgoing; Thu, 7 Nov 1996 08:02:29 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA28811 for ; Thu, 7 Nov 1996 08:02:11 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA09479 for majordomo-users@greatcircle.com; Thu, 7 Nov 96 09:02:13 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA01398 for majordomo-users@greatcircle.com; Thu, 7 Nov 96 09:02:12 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id KAA14239; Thu, 7 Nov 1996 10:02:11 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id KAA13449; Thu, 7 Nov 1996 10:02:10 -0600 From: Dave Wolfe Message-Id: <199611071602.KAA13449@miaow.risc.sps.mot.com> Subject: Re: Problems Installing Majordomo - HELP ! To: luthor@linf.unb.br (Lex Luthor) Date: Thu, 7 Nov 1996 10:02:09 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Lex Luthor" at Nov 7, 96 11:02:48 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Lex Luthor writes: ] > > When I send a mail to majordomo like : > echo 'lists'|mail majordomo > > ----- Transcript of session follows ----- > Message delivered to mailing list majordomo@juris.prdf.mpf.gov.br > /usr/local/majordomo/wrapper: permission denied [...] > drwxrwx--- 6 majordom majordom 512 Nov 7 10:17 . ^^^^^^^^ daemon (Assuming your sendmail runs as gid==daemon.) > -rwxrwx--- 1 majordom majordom 12967 Nov 7 09:52 wrapper ^ ^ ^^^^^^^^ ^^^^^^^^ s - root daemon You didn't run 'make install-wrapper' as root. -- Dave Wolfe From majordomo-users-owner Thu Nov 7 08:49:01 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA29433 for majordomo-users-outgoing; Thu, 7 Nov 1996 08:13:32 -0800 (PST) Received: from netcomi.com (netcomi.com [204.58.152.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA29413 for ; Thu, 7 Nov 1996 08:13:21 -0800 (PST) Received: from [204.58.155.43] (inaras.netcomi.com [204.58.155.43]) by netcomi.com (8.7.5/8.7.3) with ESMTP id LAA21129 for ; Thu, 7 Nov 1996 11:16:21 -0600 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 7 Nov 1996 10:17:13 -0600 To: majordomo-users@greatcircle.com From: Chris Fogel Subject: The secret list is visible!!! Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >Well, I finally got the moderated lists to work, just did a LOT more >reading and testing, but it works...there is *one* flaw though that I find >with Majordomo on the resending process...And thats that the listname for >the redirect is not truly invisible...Notice: > > ------- Transcript of Report follows ------ >01Report-Date: 6-Nov-1996 19:07:46 -0500; at X-WB-NGM-SMTP.XEROX >Re-Content-Subject: [INSPIRE] Resuming Service >Re-Content-Message-ID: <199611062222.AA28662@halcyon.com> >Report-Explanation: Address doesn't refer to a known recipient. >Rejected-For: Bill America@mc.xerox, origin NGM, event# 319, subevent# > 0, explanation Address doesn't refer to a known recipient. > > >--$----Novell--Attachment----$ > >X-NVL-Content-Type: BINARY/X-NVL-TRACE >X-NVL-Content-Typename: mms >X-NVL-Content-Transfer-Encoding: X-TRACEBINARY > >Received: from majordomo.netcomi.com ([204.58.152.13]) by alpha.xerox.com >with SMTP id <15207(5)>; Wed, 6 Nov 1996 16:07:22 PST >Received: (from majordom@localhost) by majordomo.netcomi.com >(8.7.5/8.7.3) id >RAA00912 for inspire-secret; Wed, 6 Nov 1996 17:23:10 -0600 > ^^^^^^^^^^^^^^^^^^^ > >INSPIRE-SECRET is the name of the secret list to which the redirection >goes to...how can I make majordomo scrap that piece of the header >totally.... > >Chris > > -------------------------------------------------------------------------- Chris Fogel / System Administrator Netcom Interactive mailto:fogel@netcomi.com 1607 LBJ Freeway http://www.netcomi.com Dallas, TX 75234 "She lured the dragon out of his lair with wine." From majordomo-users-owner Thu Nov 7 08:55:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA29240 for majordomo-users-outgoing; Thu, 7 Nov 1996 08:09:52 -0800 (PST) Received: from rs232.bb-elec.com ([206.1.0.34]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA29231 for ; Thu, 7 Nov 1996 08:09:38 -0800 (PST) Received: from corncam ([206.1.0.98]) by rs232.bb-elec.com (8.7.3/8.7.3) with SMTP id KAA21373; Thu, 7 Nov 1996 10:28:47 -0600 (CST) Message-Id: <199611071628.KAA21373@rs232.bb-elec.com> Comments: Authenticated sender is From: "Bill Franklin III" Organization: B&B Electronics Mfg Co To: Brock Rozen Date: Thu, 7 Nov 1996 09:05:59 -0600 Subject: Re: digests problem Reply-to: bfranklin@bb-elec.com CC: Kenneth C Rich , majordomo-users@GreatCircle.COM X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > On Thu, 7 Nov 1996, Bill Franklin III wrote: > > > the others all use size as the digest trigger.. they seem to be working fine > > with the old version but the mkdigest command will not work .. > > Everything works fine if you set it up properly. I've used the mkdigest, > size, whatever. I use digest is whatever format it CAN work, and with > success. I've been using 1.94 digest (alpha and beta) all the way back > starting with a3 or so. > > > as for the new version.. while Majordomo does seem to give wrong error messages > > alot I messed around with the do_exec_sendmail routing in majordomo.pl.. I > > hardcoded the $mail_prog var with the correct sendmail command and made some > > headway.. got one digest to go out.. but there were several other things going > > wrong.. from the error it looks as though the vars are getting set wrong.. > > > > BTW when you get the do_exec_sendmail error.. does it repeat until you kill the > > proccess? > > Yes, it does. > > Make sure: > > 1) THe work directory exists , and a seperate one for each list at that > within the work directory > > 2) THe archive directory exists > > Both of the above, if not setup right, will generate that error message. did you setup 1.94 from scratch or upgrade from 1.93..? if 1.93 works fine the directories are there and such? why would 1.94 puke? do you use a digest.cf file for the digest configuration info? with a NUM and VOL file or do you use the digest stuff that's in the intstant.config file? bill Bill Franklin III - bfrankln@bb-elec.com B&B Electronics Mfg Co http://www.bb-elec.com Phone 815-433-5100 x213 - Fax 815-434-7094 From majordomo-users-owner Thu Nov 7 08:55:43 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA29562 for majordomo-users-outgoing; Thu, 7 Nov 1996 08:15:27 -0800 (PST) Received: from netcomi.com (netcomi.com [204.58.152.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA29532 for ; Thu, 7 Nov 1996 08:15:02 -0800 (PST) Received: from [204.58.155.43] (inaras.netcomi.com [204.58.155.43]) by netcomi.com (8.7.5/8.7.3) with ESMTP id LAA21143 for ; Thu, 7 Nov 1996 11:18:07 -0600 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 7 Nov 1996 10:18:59 -0600 To: majordomo-users@greatcircle.com From: Chris Fogel Subject: MD1.94, gives me: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Below is the full Error message that Majordomo gives me sometimes...Quite a bit actually... I did not play with the Majordomo code at all...its a straight install... Chris ------------------ The original message was received at Thu, 7 Nov 1996 08:26:47 -0600 from root@blacklodge.c2.net [140.174.185.21] ----- The following addresses have delivery notifications ----- "|/usr/local/majordomo/wrapper majordomo" (unrecoverable error) (expanded from: ) ----- Transcript of session follows ----- Message delivered to mailing list Bare word found where operator expected at /usr/local/majordomo/majordomo line 994, near "(local($passwd) = shift) || &squawk("newconfig" (Might be a runaway multi-line "" string starting on line 990) (Missing operator before newconfig?) syntax error at /usr/local/majordomo/majordomo line 994, near "(local($passwd) = shift) || &squawk("newconfig" String found where operator expected at /usr/local/majordomo/majordomo line 1004, near "if (&lopen(NCONFIG, "" (Might be a runaway multi-line "" string starting on line 995) (Missing semicolon on previous line?) Scalar found where operator expected at /usr/local/majordomo/majordomo line 1004, near "", "$listdir" (Missing operator before $listdir?) String found where operator expected at /usr/local/majordomo/majordomo line 1007, near "if ($_ eq "" (Might be a runaway multi-line "" string starting on line 1004) (Missing semicolon on previous line?) Bare word found where operator expected at /usr/local/majordomo/majordomo line 1007, near "if ($_ eq "EOF" (Do you need to predeclare if?) String found where operator expected at /usr/local/majordomo/majordomo line 1010, near "print NCONFIG $_, "" (Might be a runaway multi-line "" string starting on line 1007) (Missing semicolon on previous line?) Backslash found where operator expected at /usr/local/majordomo/majordomo line 1010, near "print NCONFIG $_, "\" (Do you need to predeclare print?) String found where operator expected at /usr/local/majordomo/majordomo line 1015, near "if ( &get_config($listdir, "" (Might be a runaway multi-line "" string starting on line 1010) (Missing semicolon on previous line?) Scalar found where operator expected at /usr/local/majordomo/majordomo line 1015, near "if ( &get_config($listdir, "$clean_list" (Do you need to predeclare if?) String found where operator expected at /usr/local/majordomo/majordomo line 1016, near "print REPLY "" (Might be a runaway multi-line "" string starting on line 1015) (Missing semicolon on previous line?) Bare word found where operator expected at /usr/local/majordomo/majordomo line 1016, near "print REPLY "The" (Do you need to predeclare print?) Bare word found where operator expected at /usr/local/majordomo/majordomo line 1016, near "$clean_list was" (Missing operator before was?) String found where operator expected at /usr/local/majordomo/majordomo line 1018, near "&log("" (Might be a runaway multi-line "" string starting on line 1016) (Missing semicolon on previous line?) Literal @config::errors now requires backslash at /usr/local/majordomo/majordomo line 1016, within string Bare word found where operator expected at /usr/local/majordomo/majordomo line 1018, near "&log("FAILED" (Missing operator before FAILED?) Bare word found where operator expected at /usr/local/majordomo/majordomo line 1018, near ") newconfig" (Missing operator before newconfig?) Bare word found where operator expected at /usr/local/majordomo/majordomo line 1018, near "$clean_list PASSWORD" (Missing operator before PASSWORD?) String found where operator expected at /usr/local/majordomo/majordomo line 1019, near "unlink "" (Might be a runaway multi-line "" string starting on line 1018) (Missing semicolon on previous line?) Scalar found where operator expected at /usr/local/majordomo/majordomo line 1019, near "unlink "$listdir" (Do you need to predeclare unlink?) String found where operator expected at /usr/local/majordomo/majordomo line 1023, near "&shlock( "" (Might be a runaway multi-line "" string starting on line 1019) (Missing semicolon on previous line?) Scalar found where operator expected at /usr/local/majordomo/majordomo line 1023, near "&shlock( "$listdir" (Missing operator before $listdir?) String found where operator expected at /usr/local/majordomo/majordomo line 1025, near "do { print REPLY "" (Might be a runaway multi-line "" string starting on line 1023) (Missing semicolon on previous line?) Bare word found where operator expected at /usr/local/majordomo/majordomo line 1025, near "-> old failed" (Missing operator before failed?) String found where operator expected at /usr/local/majordomo/majordomo line 1027, near "if ( !rename("" (Might be a runaway multi-line "" string starting on line 1025) (Missing semicolon on previous line?) Scalar found where operator expected at /usr/local/majordomo/majordomo line 1027, near "if ( !rename("$listdir" (Do you need to predeclare if?) String found where operator expected at /usr/local/majordomo/majordomo line 1028, near """ (Might be a runaway multi-line "" string starting on line 1027) (Missing semicolon on previous line?) Scalar found where operator expected at /usr/local/majordomo/majordomo line 1028, near ""$listdir" (Missing operator before $listdir?) String found where operator expected at /usr/local/majordomo/majordomo line 1029, near "do { print REPLY "" (Might be a runaway multi-line "" string starting on line 1028) (Missing semicolon on previous line?) Bare word found where operator expected at /usr/local/majordomo/majordomo line 1029, near "-> current failed" (Missing operator before failed?) String found where operator expected at /usr/local/majordomo/majordomo line 1032, near "!rename("" (Might be a runaway multi-line "" string starting on line 1029) (Missing semicolon on previous line?) Scalar found where operator expected at /usr/local/majordomo/majordomo line 1032, near "!rename("$listdir" (Missing operator before $listdir?) String found where operator expected at /usr/local/majordomo/majordomo line 1033, near """ (Might be a runaway multi-line "" string starting on line 1032) (Missing semicolon on previous line?) Scalar found where operator expected at /usr/local/majordomo/majordomo line 1033, near ""$listdir" (Missing operator before $listdir?) String found where operator expected at /usr/local/majordomo/majordomo line 1035, near "unlink( "" (Might be a runaway multi-line "" string starting on line 1033) (Missing semicolon on previous line?) Scalar found where operator expected at /usr/local/majordomo/majordomo line 1035, near "unlink( "$listdir" String found where operator expected at /usr/local/majordomo/majordomo line 1037, near "print REPLY "" (Might be a runaway multi-line "" string starting on line 1035) (Missing semicolon on previous line?) Bare word found where operator expected at /usr/local/majordomo/majordomo line 1037, near "print REPLY "New" (Do you need to predeclare print?) Missing $ on loop variable at /usr/local/majordomo/majordomo line 1037. 554 "|/usr/local/majordomo/wrapper majordomo"... unknown mailer error 2 Reporting-MTA: dns; majordomo.netcomi.com Received-From-MTA: DNS; blacklodge.c2.net Arrival-Date: Thu, 7 Nov 1996 08:26:47 -0600 Final-Recipient: RFC822; majordomo@majordomo.netcomi.com Action: delivered (to mailing list) Status: 2.0.0 Last-Attempt-Date: Thu, 7 Nov 1996 08:26:48 -0600 Final-Recipient: RFC822; majordomo@majordomo.netcomi.com X-Actual-Recipient: RFC822; |/usr/local/majordomo/wrapper majordomo@majordomo.netcomi.com Action: failed Status: 5.0.0 Last-Attempt-Date: Thu, 7 Nov 1996 08:26:48 -0600 Return-Path: nobody@c2.net Received: from blacklodge.c2.net (root@blacklodge.c2.net [140.174.185.21]) by majordomo.netcomi.com (8.7.5/8.7.3) with ESMTP id IAA04177 for ; Thu, 7 Nov 1996 08:26:47 -0600 Received: from atropos.c2.org (atropos.c2.org [140.174.185.14]) by blacklodge.c2.net (8.7.6/8.7.3) with ESMTP id FAA20517 for ; Thu, 7 Nov 1996 05:29:00 -0800 (PST) Received: (from nobody@localhost) by atropos.c2.org (8.7.6/8.7.3) id FAA06075; Thu, 7 Nov 1996 05:26:23 -0800 (PST) Date: Thu, 7 Nov 1996 05:26:23 -0800 (PST) Message-Id: <199611071326.FAA06075@atropos.c2.org> To: majordomo@inspire.infoadvn.com From: noblebelfast@msn.com () subscribe inspire -------------------------------------------------------------------------- Chris Fogel / System Administrator Netcom Interactive mailto:fogel@netcomi.com 1607 LBJ Freeway http://www.netcomi.com Dallas, TX 75234 "She lured the dragon out of his lair with wine." From majordomo-users-owner Thu Nov 7 09:03:02 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA01762 for majordomo-users-outgoing; Thu, 7 Nov 1996 08:54:27 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA01745 for ; Thu, 7 Nov 1996 08:54:14 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id LAA25534; Thu, 7 Nov 1996 11:54:18 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id LAA25323; Thu, 7 Nov 1996 11:54:14 -0500 (EST) Message-Id: <199611071654.LAA25323@augusta.math.psu.edu> To: "Juan J. Vieira" cc: majordomo-users@GreatCircle.COM Subject: Re: Log File In-reply-to: Your message of "Tue, 05 Nov 1996 02:54:19 -0400." <327EE49B.487F@etheron.net> References: <327EE49B.487F@etheron.net> 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 Nov 1996 11:54:13 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <327EE49B.487F@etheron.net>, "Juan J. Vieira" writes: >Hello, I have Majordomo 1.94 and Linux, When i Mail a message >Majordomo Abort and give me an Error with the Log file. > > The Error is that majordomo can't write in the log file, because > the permissions is wrong > > I Have to create the Log file? > > What Information have the Log file? > > Which are the permissions of the Log file? This is answered in question 2.1 of the current Majordomo FAQ. http://www.math.psu.edu/barr/majordomo-faq.html --Dave From majordomo-users-owner Thu Nov 7 09:18:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA02102 for majordomo-users-outgoing; Thu, 7 Nov 1996 09:01:51 -0800 (PST) Received: from okjunc.junction.net (okjunc.junction.net [199.166.227.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA02095 for ; Thu, 7 Nov 1996 09:01:43 -0800 (PST) Received: (from mauro@localhost) by okjunc.junction.net (8.6.11/8.6.11) id JAA16048; Thu, 7 Nov 1996 09:04:29 -0800 Date: Thu, 7 Nov 1996 09:04:29 -0800 (PST) From: Mauro Incrocci To: majordomo-users@GreatCircle.COM Subject: restrict_post Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm trying to restrict posting to one of my lists using restrict_post but posting is available to everyone. I'm using 1.93 on a Redhat Linux system. I have restrict_post = .restrict .restrict contains e-mail addresses in the form of @.net. I have one entry on each line. Any ideas? On another note, it takes several days for a message I post to be echoed to the list. Mauro =-=-= From majordomo-users-owner Thu Nov 7 09:23:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA02751 for majordomo-users-outgoing; Thu, 7 Nov 1996 09:08:30 -0800 (PST) Received: from sisko.cc.rochester.edu (sisko.cc.rochester.edu [128.151.219.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA02726 for ; Thu, 7 Nov 1996 09:08:14 -0800 (PST) Received: (from kenr@localhost) by sisko.cc.rochester.edu (8.7.6/8.7.3) id MAA28409 for majordomo-users@GreatCircle.COM; Thu, 7 Nov 1996 12:11:09 -0500 (EST) Date: Thu, 7 Nov 1996 12:11:09 -0500 (EST) From: Kenneth C Rich Message-Id: <199611071711.MAA28409@sisko.cc.rochester.edu> To: majordomo-users@GreatCircle.COM Subject: Re: digests problem Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk well just FYAmusement, fixing my majordomo.cf cured the mogombo masses of majordomo abort messages. however it ain't creating any digest that i can see, and certainly is not delivering it anywhere. and majordomo is sending me confirmation on the mkdigest command. can anyone tell what i _should_ be seeing? is the digest indeed created from the archive? is it supposed to create its own archive? how does digest know which file to digestify? ------------------------------------------------------------------------ > least far enough into digesting to trip over it. so i will change my: > > $digest_work_dir = '$homedir/digests'; > to > $digest_work_dir = "$homedir/digests"; > > and test. later. when i have reinforcements. -- -ken rich "How many people can look at a painting for even long enough to peel an orange and eat it?" -Sir Kenneth Clark kenr@cc.rochester.edu From majordomo-users-owner Thu Nov 7 09:51:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA04452 for majordomo-users-outgoing; Thu, 7 Nov 1996 09:34:42 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA04423 for ; Thu, 7 Nov 1996 09:34:22 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA24344 for majordomo-users@GreatCircle.COM; Thu, 7 Nov 96 10:34:23 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA05292 for majordomo-users@GreatCircle.COM; Thu, 7 Nov 96 10:34:22 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id LAA16418; Thu, 7 Nov 1996 11:34:21 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id LAA12267; Thu, 7 Nov 1996 11:34:19 -0600 From: Dave Wolfe Message-Id: <199611071734.LAA12267@miaow.risc.sps.mot.com> Subject: Re: restrict_post To: mauro@okjunc.junction.net (Mauro Incrocci) Date: Thu, 7 Nov 1996 11:34:19 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Mauro Incrocci" at Nov 7, 96 09:04:29 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Mauro Incrocci writes: ] > > I'm trying to restrict posting to one of my lists using restrict_post but > posting is available to everyone. I'm using 1.93 on a Redhat Linux system. > > I have restrict_post = .restrict > > .restrict contains e-mail addresses in the form of > @.net. I have one entry on each line. Any ideas? You must use resend in your list alias for resend features to work. > On another note, it takes several days for a message I post to be echoed > to the list. You must have a very slow mail relay. -- Dave Wolfe From majordomo-users-owner Thu Nov 7 09:59:07 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA05105 for majordomo-users-outgoing; Thu, 7 Nov 1996 09:45:52 -0800 (PST) Received: from relay5.UU.NET (relay5.UU.NET [192.48.96.15]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA05026 for ; Thu, 7 Nov 1996 09:45:23 -0800 (PST) Received: from uucp6.UU.NET by relay5.UU.NET with SMTP (peer crosschecked as: uucp6.UU.NET [192.48.96.37]) id QQbovf04093; Thu, 7 Nov 1996 12:45:26 -0500 (EST) Received: from spsgate.UUCP by uucp6.UU.NET with UUCP/RMAIL ; Thu, 7 Nov 1996 12:45:27 -0500 Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA24742 for netcomi.com!fogel; Thu, 7 Nov 96 10:36:39 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA05421 for greatcircle.com!majordomo-users@uunet.uucp; Thu, 7 Nov 96 10:36:38 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id LAA16467; Thu, 7 Nov 1996 11:36:37 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id LAA12281; Thu, 7 Nov 1996 11:36:35 -0600 From: Dave Wolfe Message-Id: <199611071736.LAA12281@miaow.risc.sps.mot.com> Subject: Re: The secret list is visible!!! To: uunet!netcomi.com!fogel@uunet.uu.net (Chris Fogel) Date: Thu, 7 Nov 1996 11:36:35 -0600 (CST) Cc: uunet!greatcircle.com!majordomo-users@uunet.uu.net In-Reply-To: from "Chris Fogel" at Nov 7, 96 10:17:13 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Chris Fogel writes: ] >Well, I finally got the moderated lists to work, just did a LOT more >reading and testing, but it works...there is *one* flaw though that I find >with Majordomo on the resending process...And thats that the listname for >the redirect is not truly invisible...Notice: [...] >Received: (from majordom@localhost) by majordomo.netcomi.com >(8.7.5/8.7.3) id >RAA00912 for inspire-secret; Wed, 6 Nov 1996 17:23:10 -0600 > ^^^^^^^^^^^^^^^^^^^ Reconfigure sendmail on majordomo.netcomi.com to quit giving away your secrets. -- Dave Wolfe From majordomo-users-owner Thu Nov 7 10:37:02 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA05689 for majordomo-users-outgoing; Thu, 7 Nov 1996 09:54:13 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA05680 for ; Thu, 7 Nov 1996 09:54:01 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id MAA26502; Thu, 7 Nov 1996 12:54:02 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id MAA25646; Thu, 7 Nov 1996 12:53:57 -0500 (EST) Message-Id: <199611071753.MAA25646@augusta.math.psu.edu> To: Chris Fogel cc: majordomo-users@GreatCircle.COM Subject: Re: The secret list is visible!!! In-reply-to: Your message of "Thu, 07 Nov 1996 10:17:13 CST." References: 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 Nov 1996 12:53:55 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , Chris Fogel writes: >RAA00912 for inspire-secret; Wed, 6 Nov 1996 17:23:10 -0600 > ^^^^^^^^^^^^^^^^^^^ > >INSPIRE-SECRET is the name of the secret list to which the redirection >goes to...how can I make majordomo scrap that piece of the header >totally.... See the end of question 3.6 in the Majordomo FAQ. http://www.math.psu.edu/barr/majordomo-faq.html --Dave From majordomo-users-owner Thu Nov 7 10:43:34 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA08104 for majordomo-users-outgoing; Thu, 7 Nov 1996 10:22:52 -0800 (PST) Received: from horse.saberspace.com ([205.197.223.239]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA08067 for ; Thu, 7 Nov 1996 10:22:37 -0800 (PST) From: scott@saberspace.com Received: from localhost (scott@localhost) by horse.saberspace.com (8.7.6/8.7.3) with SMTP id NAA08252; Thu, 7 Nov 1996 13:22:33 -0500 Date: Thu, 7 Nov 1996 13:22:33 -0500 (EST) To: Dave Wolfe cc: majordomo-users@greatcircle.com Subject: Re: Ppermissions In-Reply-To: <199611071602.KAA13449@miaow.risc.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 Nov 1996, Dave Wolfe wrote: > [ Lex Luthor writes: ] > > drwxrwx--- 6 majordom majordom 512 Nov 7 10:17 . > ^^^^^^^^ > daemon > (Assuming your sendmail runs as gid==daemon.) > > > -rwxrwx--- 1 majordom majordom 12967 Nov 7 09:52 wrapper > ^ ^ ^^^^^^^^ ^^^^^^^^ > s - root daemon > > You didn't run 'make install-wrapper' as root. I *DID* run make install-wrapper as root. Your tip above gave me an idea, though. In /etc/group, I added user mail (sendmail is mail.mail) to group majordom, added the group mail to the makefile and made wrapper root.mail, mode 4770. I now have everything either 770 or 660 and all is well... THANKS!!! Seeya! Scott From majordomo-users-owner Thu Nov 7 10:47:47 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA05793 for majordomo-users-outgoing; Thu, 7 Nov 1996 09:56:00 -0800 (PST) Received: from relay5.UU.NET (relay5.UU.NET [192.48.96.15]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA05765 for ; Thu, 7 Nov 1996 09:55:44 -0800 (PST) Received: from uucp6.UU.NET by relay5.UU.NET with SMTP (peer crosschecked as: uucp6.UU.NET [192.48.96.37]) id QQbovf07556; Thu, 7 Nov 1996 12:55:26 -0500 (EST) Received: from spsgate.UUCP by uucp6.UU.NET with UUCP/RMAIL ; Thu, 7 Nov 1996 12:55:40 -0500 Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA26844 for netcomi.com!fogel; Thu, 7 Nov 96 10:50:25 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA05841 for greatcircle.com!majordomo-users@uunet.uucp; Thu, 7 Nov 96 10:50:22 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id LAA16820; Thu, 7 Nov 1996 11:50:21 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id LAA12281; Thu, 7 Nov 1996 11:36:35 -0600 From: Dave Wolfe Message-Id: <199611071736.LAA12281@miaow.risc.sps.mot.com> Subject: Re: The secret list is visible!!! To: uunet!netcomi.com!fogel@uunet.uu.net (Chris Fogel) Date: Thu, 7 Nov 1996 11:36:35 -0600 (CST) Cc: uunet!greatcircle.com!majordomo-users@uunet.uu.net In-Reply-To: from "Chris Fogel" at Nov 7, 96 10:17:13 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk <<< No Message Collected >>> From majordomo-users-owner Thu Nov 7 10:48:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA05580 for majordomo-users-outgoing; Thu, 7 Nov 1996 09:52:03 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA05542 for ; Thu, 7 Nov 1996 09:51:39 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA27057 for majordomo-users@greatcircle.com; Thu, 7 Nov 96 10:51:43 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA05886 for majordomo-users@greatcircle.com; Thu, 7 Nov 96 10:51:42 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id LAA16870; Thu, 7 Nov 1996 11:51:41 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id LAA16150; Thu, 7 Nov 1996 11:51:39 -0600 From: Dave Wolfe Message-Id: <199611071751.LAA16150@miaow.risc.sps.mot.com> Subject: Re: MD1.94, gives me: To: fogel@netcomi.com (Chris Fogel) Date: Thu, 7 Nov 1996 11:51:39 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Chris Fogel" at Nov 7, 96 10:18:59 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Chris Fogel writes: ] > > Below is the full Error message that Majordomo gives me sometimes...Quite a > bit actually... > I did not play with the Majordomo code at all...its a straight install... [...] > ----- Transcript of session follows ----- > Message delivered to mailing list > Bare word found where operator expected at /usr/local/majordomo/majordomo > line 994, near "(local($passwd) = shift) || &squawk("newconfig" > (Might be a runaway multi-line "" string starting on line 990) > (Missing operator before newconfig?) > syntax error at /usr/local/majordomo/majordomo line 994, near > "(local($passwd) = shift) || &squawk("newconfig" > String found where operator expected at /usr/local/majordomo/majordomo line > 1004, near "if (&lopen(NCONFIG, "" [ remainder deleted ] Just how old is your perl? Let's see 'perl -v'. -- Dave Wolfe From majordomo-users-owner Thu Nov 7 10:49:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA05837 for majordomo-users-outgoing; Thu, 7 Nov 1996 09:56:21 -0800 (PST) Received: from relay5.UU.NET (relay5.UU.NET [192.48.96.15]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA05786 for ; Thu, 7 Nov 1996 09:55:55 -0800 (PST) Received: from uucp6.UU.NET by relay5.UU.NET with SMTP (peer crosschecked as: uucp6.UU.NET [192.48.96.37]) id QQbovf07731; Thu, 7 Nov 1996 12:55:46 -0500 (EST) Received: from spsgate.UUCP by uucp6.UU.NET with UUCP/RMAIL ; Thu, 7 Nov 1996 12:55:55 -0500 Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA26845 for etheron.net!jvieira; Thu, 7 Nov 96 10:50:25 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA05843 for GreatCircle.com!majordomo-users@uunet.uucp; Thu, 7 Nov 96 10:50:23 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id LAA16830; Thu, 7 Nov 1996 11:50:21 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id KAA19748; Thu, 7 Nov 1996 10:55:03 -0600 From: Dave Wolfe Message-Id: <199611071655.KAA19748@miaow.risc.sps.mot.com> Subject: Re: Log File To: uunet!etheron.net!jvieira@uunet.uu.net (Juan J. Vieira) Date: Thu, 7 Nov 1996 10:55:03 -0600 (CST) Cc: uunet!GreatCircle.com!majordomo-users@uunet.uu.net In-Reply-To: <327EE49B.487F@etheron.net> from "Juan J. Vieira" at Nov 5, 96 02:54:19 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Juan J. Vieira writes: ] > > Hello, I have Majordomo 1.94 and Linux, When i Mail a message > Majordomo Abort and give me an Error with the Log file. > > The Error is that majordomo can't write in the log file, because > the permissions is wrong > > I Have to create the Log file? Yes. > What Information have the Log file? Majordomo requests (not maillist posts). > Which are the permissions of the Log file? That depends on how you have Mj configured. If you don't have a log file with the correct permissions, then you didn't install Mj per the directions, so you probably have other problems as well, so you should start over and reinstall it correctly. -- Dave Wolfe From majordomo-users-owner Thu Nov 7 11:08:20 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA10140 for majordomo-users-outgoing; Thu, 7 Nov 1996 10:52:27 -0800 (PST) Received: from okjunc.junction.net (okjunc.junction.net [199.166.227.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA10112 for ; Thu, 7 Nov 1996 10:52:13 -0800 (PST) Received: (from mauro@localhost) by okjunc.junction.net (8.6.11/8.6.11) id KAA18770; Thu, 7 Nov 1996 10:53:49 -0800 Date: Thu, 7 Nov 1996 10:53:49 -0800 (PST) From: Mauro Incrocci To: Dave Wolfe cc: majordomo-users@GreatCircle.COM Subject: Re: restrict_post In-Reply-To: <199611071734.LAA12267@miaow.risc.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 Nov 1996, Dave Wolfe wrote: > You must use resend in your list alias for resend features to work. That is what I was missing. Thank you. For those following this thread, here is the line needed to add to the alias file: : "|/wrapper resend -p bulk -M 10000 -l -f -owner -h -s -outgoing" The above is one line and not broken. > > On another note, it takes several days for a message I post to be echoed > > to the list. > You must have a very slow mail relay. Don't think that's it but that's another issue. Mauro =-=-= From majordomo-users-owner Thu Nov 7 11:22:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA11215 for majordomo-users-outgoing; Thu, 7 Nov 1996 11:09:45 -0800 (PST) Received: from vulture.creighton.edu (vulture.creighton.edu [147.134.5.137]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id LAA11100 for ; Thu, 7 Nov 1996 11:07:58 -0800 (PST) Received: from localhost (kevie@localhost) by vulture.creighton.edu (8.7.6/8.7.3) with SMTP id NAA29192 for ; Thu, 7 Nov 1996 13:07:32 -0600 X-Authentication-Warning: vulture.creighton.edu: kevie owned process doing -bs Date: Thu, 7 Nov 1996 13:07:31 -0600 (CST) From: Kevin Chu To: majordomo-users@greatcircle.com Subject: Taboo-headers... Message-ID: X-URL: http://acm-www.creighton.edu/~kevie/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm having a program getting Majordomo 1.94 to "block" a certain e-mail address. It's my understanding that the "taboo-headers" section of majordomo.cf is where you put the address in. Here is what mine looks like: # List of perl regular expressions that, if found in the headers of a message, # will cause the message to be bounced to the list approver. # Put each regular expression on a separate line before the "END" mark, with # no trailing ";" # For example: # $global_taboo_headers = <<'END'; # /^from:.*trouble@hassle.net/i # /^subject:.*non-delivery notice/i # END # NOTE! Using ' instead of " in the 'END' is VERY IMPORTANT!!! # $global_taboo_headers = <<'END'; /^from:.*kevie@creighton.edu/i END This should be able to block all messages that I send (just for testing), but it doesn't and I can still subscribe to any list that is open. Any suggestions??? --kevie From majordomo-users-owner Thu Nov 7 11:48:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA12840 for majordomo-users-outgoing; Thu, 7 Nov 1996 11:45:26 -0800 (PST) Received: from mail.his.com (mail.his.com [205.177.25.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA12833 for ; Thu, 7 Nov 1996 11:45:16 -0800 (PST) Received: from localhost (kendall@localhost) by mail.his.com (8.6.9/8.6.12) with SMTP id OAA05870 for ; Thu, 7 Nov 1996 14:42:28 -0500 Date: Thu, 7 Nov 1996 14:42:28 -0500 (EST) From: "Kendall P. Bullen" To: majordomo-users@greatcircle.com Subject: "who" for moderator only? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi All, Before I go hacking sources, I was wondering if anyone had already come up with a patch for Mj 1.94 to allow 'who' to only work for the moderator. Something like who_access allowing 'moderator' in addition to 'open'/'closed'/'list'. . . . I suspect this would be easy to do, but I'd rather stray from sources as little as possible. :) Thanks in advance, Kendall From majordomo-users-owner Thu Nov 7 11:54:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA12771 for majordomo-users-outgoing; Thu, 7 Nov 1996 11:43:35 -0800 (PST) Received: from netop3.harvard.edu (netop3.harvard.edu [128.103.205.103]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA12753 for ; Thu, 7 Nov 1996 11:43:20 -0800 (PST) Received: from hsph.harvard.edu (hsph.harvard.edu [128.103.75.21]) by netop3.harvard.edu (8.6.12/8.6.12) with ESMTP id OAA09360 for ; Thu, 7 Nov 1996 14:43:13 -0500 Received: from sph-optivity.harvard.edu by hsph.harvard.edu (SMI-8.6/SMI-SVR4) id OAA10111; Thu, 7 Nov 1996 14:44:07 -0500 Message-Id: <199611071944.OAA10111@hsph.harvard.edu> From: "Robert Byers" To: Subject: Dots '.' at start of line needed Date: Thu, 7 Nov 1996 14:43:05 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The users of my list have a need to send postings with a dot '.' at the start of various lines in their postings The list concerns a software package that uses a dot '.' as a command line prompt. When they send program listings, often a line will contain nothing but a prompt ('.') in the first column. Of course, mail interprets this as and end of data, and the rest of the message is ignored. While not strictly a MD issue, I thought some users might have an idea on how I could allow users to post their program listings without truncation. Thanks, -Bob Byers Harvard School of Public Health Boston, MA From majordomo-users-owner Thu Nov 7 12:32:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA15365 for majordomo-users-outgoing; Thu, 7 Nov 1996 12:26:51 -0800 (PST) Received: from eros.gcsnet.com.br (eros.gcsnet.com.br [200.238.233.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id MAA15358 for ; Thu, 7 Nov 1996 12:26:41 -0800 (PST) Received: from localhost (root@localhost) by eros.gcsnet.com.br (8.7.5/8.7.3) with SMTP id SAA00417 for ; Thu, 7 Nov 1996 18:26:38 -0200 Date: Thu, 7 Nov 1996 18:26:38 -0200 (EDT) From: root To: majordomo-users@GreatCircle.COM Subject: Big problems with Majordomo 1.94 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi All, I was wondering if anyone could help me, my problems occurs when someone sends a request that needs to be forwarded to the owner of the list. At this point somethings happens that instead the mail fowarded arrives to the owner of the list, many processes of sendmail are created and many mails are queued and this thing grews up to according that I must kill sendmail and delete the mails queued or my machine crashs. majordomo.aliases ______________________________ majordomo: "|/usr/local/majordomo/majordomo/wrapper majordomo" majordomo-owner: root owner-majordomo: root outerspace: "|/usr/local/majordomo/majordomo/wrapper resend -l outerspace outerspace-list" outerspace-list: :include:/usr/local/majordomo/majordomo/lists/outerspace owner-outerspace: root outerspace-owner: root outerspace-request: root ------------------------------------------------------------- Makefile -------------------------------------------------------------- # Where is Perl located? PERL = /usr/bin/perl # specify one that does here. CHOWN = chown # The location of Majordomo. Wrapper looks here for programs to run. W_HOME = /usr/local/majordomo/majordomo # $(W_HOME)/man/man[18] # W_MAN = $(W_HOME)/man MAN1 = $(W_HOME)/man/man1 MAN8 = $(W_HOME)/man/man8 # *** This gets reset below if this is a POSIX system *** W_CHMOD = 6755 # passed to processes run by "wrapper" W_PATH = /bin:/usr/bin:/usr/ucb W_BIN = $(W_HOME) W_SHELL = /bin/csh W_MAJORDOMO_CF = $(W_BIN)/majordomo.cf # majordomo on my system # W_USER = 502 # # daemon on my system # W_GROUP = 2 # # You might need to change : to . # W_CHOWN = $(W_USER).$(W_GROUP) # If installing wrapper 'shared', define what the suffix of wrapper is. # (I'd like to hear if anybody is using MJ this way) # ARCHCMD=`arch` # ARCHCMD=`uname -m` #------------- POSIX SECTION ----------------------------- # WRAPPER_CHOWN = root WRAPPER_CHMOD = 4755 POSIX = -DPOSIX_UID=$(W_USER) -DPOSIX_GID=$(W_GROUP) # Define this if the majordomo programs should *also* be run in the same # group as your MTA, usually sendmail. This is rarely needed, but some # MTAs require certain group memberships before allowing the message sender # to be set arbitrarily. # # MAIL_GID = numeric_gid_of_MTA ------------------------------------------------------------- thanks in advance, Fabricio From majordomo-users-owner Thu Nov 7 13:03:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA16889 for majordomo-users-outgoing; Thu, 7 Nov 1996 12:50:22 -0800 (PST) Received: from relay5.UU.NET (relay5.UU.NET [192.48.96.15]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id MAA16848 for ; Thu, 7 Nov 1996 12:49:48 -0800 (PST) Received: from uucp5.UU.NET by relay5.UU.NET with SMTP (peer crosschecked as: uucp5.UU.NET [192.48.96.36]) id QQbovr17031; Thu, 7 Nov 1996 15:49:50 -0500 (EST) Received: from organon.UUCP by uucp5.UU.NET with UUCP/RMAIL ; Thu, 7 Nov 1996 15:49:51 -0500 Received: by organon.com (4.1/SMI-4.1) id AA07747; Thu, 7 Nov 96 15:34:12 EST Date: Thu, 7 Nov 96 15:34:12 EST From: jfb@organon.com (Julie Burch) Message-Id: <9611072034.AA07747@organon.com> To: majordomo-users@greatcircle.com Subject: MJ Installation trouble--p.s. Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk (I sent that from root... my return address is jfb@organon.com :} --Julie Burch Organon Motives SysAdmin From majordomo-users-owner Thu Nov 7 13:11:46 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA16881 for majordomo-users-outgoing; Thu, 7 Nov 1996 12:50:18 -0800 (PST) Received: from relay5.UU.NET (relay5.UU.NET [192.48.96.15]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id MAA16842 for ; Thu, 7 Nov 1996 12:49:45 -0800 (PST) Received: from uucp5.UU.NET by relay5.UU.NET with SMTP (peer crosschecked as: uucp5.UU.NET [192.48.96.36]) id QQbovr17017; Thu, 7 Nov 1996 15:49:48 -0500 (EST) Received: from organon.UUCP by uucp5.UU.NET with UUCP/RMAIL ; Thu, 7 Nov 1996 15:49:48 -0500 Received: by organon.com (4.1/SMI-4.1) id AA07725; Thu, 7 Nov 96 15:31:33 EST Date: Thu, 7 Nov 96 15:31:33 EST From: jfb@organon.com (Julie Burch) Message-Id: <9611072031.AA07725@organon.com> To: majordomo-users@greatcircle.com Subject: Trouble Installing MJ 1.94 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm on a Sparc 2 running SunOS 4.1.4 and Perl 5.001 trying to install MJ 1.94. I've gone through all the installation steps twice (and read the FAQ and ORA files). the config-test tells me everything is ok, but when I try the echo 'lists' | mail majordomo command I get trouble. if i do it as majordomo--nothing happens if i do it as myself, i get an ABORT error--ostensibly 'cause it's running under my uid. Why isn't the echo line working? Or is their another simple way to test this before I start playing with lists? Also: Last time I tried this, somehow sendmail got hung--and stopped sending all outgoing mail. We've got a UUCP setup and it wasn't even in the spool. We restarted sendmail and it`s fine, and the seemingly lost mail went out Any idea why this would or could happen? TIA --Julie Burch Organon Motives SysAdmin From majordomo-users-owner Thu Nov 7 13:48:21 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA20911 for majordomo-users-outgoing; Thu, 7 Nov 1996 13:40:17 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA20892 for ; Thu, 7 Nov 1996 13:40:06 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id QAA01341; Thu, 7 Nov 1996 16:40:05 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id QAA27176; Thu, 7 Nov 1996 16:40:02 -0500 (EST) Message-Id: <199611072140.QAA27176@augusta.math.psu.edu> To: jfb@organon.com (Julie Burch) cc: majordomo-users@GreatCircle.COM Subject: Re: Trouble Installing MJ 1.94 In-reply-to: Your message of "Thu, 07 Nov 1996 15:31:33 EST." <9611072031.AA07725@organon.com> References: <9611072031.AA07725@organon.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 Nov 1996 16:40:00 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <9611072031.AA07725@organon.com>, Julie Burch writes: >I'm on a Sparc 2 running SunOS 4.1.4 and Perl 5.001 >trying to install MJ 1.94. > >I've gone through all the installation steps twice (and read the FAQ Except for the part in the FAQ about how Perl 5.001 will not work with Majordomo. Upgrade to 5.002 or 5.003. --Dave From majordomo-users-owner Thu Nov 7 14:38:40 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA24066 for majordomo-users-outgoing; Thu, 7 Nov 1996 14:22:17 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA24001 for ; Thu, 7 Nov 1996 14:21:36 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id QAA05275; Thu, 7 Nov 1996 16:21:29 -0600 (CST) To: "Kendall P. Bullen" Cc: majordomo-users@GreatCircle.COM Subject: Re: "who" for moderator only? References: From: Jason L Tibbitts III Date: 07 Nov 1996 16:21:29 -0600 In-Reply-To: "Kendall P. Bullen"'s message of Thu, 7 Nov 1996 14:42:28 -0500 (EST) Message-ID: Lines: 9 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "KPB" == Kendall P Bullen writes: KPB> Hi All, Before I go hacking sources, I was wondering if anyone had KPB> already come up with a patch for Mj 1.94 to allow 'who' to only work KPB> for the moderator. Why? Just use the approve command ("approve password who list"). - J< From majordomo-users-owner Thu Nov 7 14:45:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA23986 for majordomo-users-outgoing; Thu, 7 Nov 1996 14:21:20 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA23909 for ; Thu, 7 Nov 1996 14:20:43 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id QAA05161; Thu, 7 Nov 1996 16:19:03 -0600 (CST) To: Mauro Incrocci Cc: majordomo-users@GreatCircle.COM Subject: Re: restrict_post References: From: Jason L Tibbitts III Date: 07 Nov 1996 16:19:03 -0600 In-Reply-To: Mauro Incrocci's message of Thu, 7 Nov 1996 10:53:49 -0800 (PST) Message-ID: Lines: 17 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "MI" == Mauro Incrocci writes: MI> That is what I was missing. Thank you. For those following this MI> thread, here is the line needed to add to the alias file: MI> : "|/wrapper resend -p bulk -M 10000 -l MI> -f -owner -h -s -outgoing" Umm, no, don't use all of those arguments. Just use: : "|/wrapper resend -l -h -outgoing" The other stuff will definitely be going away in future versions, and is all supported by using the list config file. - J< From majordomo-users-owner Thu Nov 7 15:23:19 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA26827 for majordomo-users-outgoing; Thu, 7 Nov 1996 14:55:21 -0800 (PST) Received: from hplms26.hpl.hp.com (hplms26.hpl.hp.com [15.255.168.31]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA26820 for ; Thu, 7 Nov 1996 14:55:09 -0800 (PST) Received: from irit.hpl.hp.com (dhcpp34.hpl.hp.com) by hplms26.hpl.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3+HPL1.1S) id AA073667300; Thu, 7 Nov 1996 14:55:00 -0800 Message-Id: <3.0.32.19961107145632.00687318@hploms.hpl.hp.com> X-Sender: kevinwu@hploms.hpl.hp.com X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Thu, 07 Nov 1996 14:56:32 -0800 To: Kenneth C Rich From: Kevin Wu Subject: Re: digests problem Cc: majordomo-users@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 12:11 PM 11/7/96 -0500, Kenneth C Rich wrote: >------------------------------------------------------------------------ >> least far enough into digesting to trip over it. so i will change my: >> >> $digest_work_dir = '$homedir/digests'; >> to >> $digest_work_dir = "$homedir/digests"; >> >> and test. later. when i have reinforcements. > Ken, Thanks for the tip! I was using $homedir in the path and forgot to replace the single quotes with double quotes for variable interpolation. Digests now work at my site, and mkdigest generates and sends the digest. >well just FYAmusement, fixing my majordomo.cf cured the mogombo masses >of majordomo abort messages. however it ain't creating any digest that >i can see, and certainly is not delivering it anywhere. and majordomo >is sending me confirmation on the mkdigest command. can anyone tell >what i _should_ be seeing? is the digest indeed created from the >archive? is it supposed to create its own archive? how does digest >know which file to digestify? Make the working directory manually and make sure the permissions are correct. When an article is submitted to the list, it should be appended to a file named '001' for issue number 1. This file is removed when the digest is sent out. The digest is independent of the article archiving. The digests are also archived, and you need to create this directory manually. Kevin From majordomo-users-owner Thu Nov 7 15:23:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA28765 for majordomo-users-outgoing; Thu, 7 Nov 1996 15:12:16 -0800 (PST) Received: from hplms26.hpl.hp.com (hplms26.hpl.hp.com [15.255.168.31]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA28725 for ; Thu, 7 Nov 1996 15:12:04 -0800 (PST) Received: from irit.hpl.hp.com (dhcpp34.hpl.hp.com) by hplms26.hpl.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3+HPL1.1S) id AA077648328; Thu, 7 Nov 1996 15:12:08 -0800 Message-Id: <3.0.32.19961107151339.006d7100@hploms.hpl.hp.com> X-Sender: kevinwu@hploms.hpl.hp.com X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Thu, 07 Nov 1996 15:13:39 -0800 To: majordomo-users@greatcircle.com From: Kevin Wu Subject: Permission of archive/digest files Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In MJ 1.94, Majordomo creates the archive and digest files with a mode of -rw-rw-rw. What do I change to make this -rw-rw-r--? BTW, in majordomo.cf, $config_umask is set to 007. Kevin From majordomo-users-owner Thu Nov 7 16:33:46 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA04858 for majordomo-users-outgoing; Thu, 7 Nov 1996 16:27:51 -0800 (PST) Received: from tahi.tradesrv.com.au ([203.63.230.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id QAA04823 for ; Thu, 7 Nov 1996 16:27:32 -0800 (PST) Received: from neil.tradesrv.com.au ([203.63.230.20]) by tahi.tradesrv.com.au (8.6.12/8.6.9) with SMTP id LAA25785 for ; Fri, 8 Nov 1996 11:27:33 +1100 Message-ID: <32827B58.50E6@tradesrv.com.au> Date: Fri, 08 Nov 1996 11:14:16 +1100 From: Neil Cotty Reply-To: neilc@tradesrv.com.au Organization: Internet Trading Services Pty. Ltd. X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: NEW Digest/Mail Error Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I've been testing my MJ 1.94 install over the last couple of days concentrating on digesting. I finally got the digest to go off (reached the size limit :) ) however a couple of the people who are testing it with me were not sent their mail and MJ (or sendmail ?) popped this 'Remote Protocol Error' message. Could somebody explain this message to me. I'm afraid I don't have a clue about this one as it doesn't seem to be a MJ error message. My owner-vizsla-digest points to owner-vizsla which is me, neilc. Is this something strange to do with the mail server at the other end needing my full email address ??? Urggh brain strain.. TIA. The original message was received at Fri, 8 Nov 1996 10:47:14 +1100 from majordom@localhost ----- The following addresses had delivery problems ----- djb9895@tam2000.tamu.edu (unrecoverable error) (expanded from: :include:/usr/local/majordomo/lists/vizsla-digest) ddnelson@ix.netcom.com (unrecoverable error) (expanded from: :include:/usr/local/majordomo/lists/vizsla-digest) ----- Transcript of session follows ----- ... while talking to tam2000.tamu.edu.: >>> DATA <<< 550 owner-vizsla-digest... User unknown 554 djb9895@tam2000.tamu.edu... Remote protocol error ... while talking to ixmail5.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail2.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail3.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail6.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail4.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixsrs5.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixsrs4.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown 554 ddnelson@ix.netcom.com... Remote protocol error ----- Message header follows ----- Subject: vizsla-digest V1 #1 Date: Fri, 8 Nov 1996 10:47:14 +1100 From: owner-vizsla-digest (vizsla-digest) Reply-To: vizsla To: vizsla-digest ----- Message body suppressed ----- Kind Regards, Neil Cotty. -- Internet Trading Services Access Providers Level 1, Fayworth House Internet Database Systems 379-383 Pitt Street Client/Server Sydney, NSW 2000 Consulting Australia Phone : +61 2 264 8811 Fax: +61 2 264 8822 Modems: +61 2 264 8810 URL: http://www.tradesrv.com.au Email: neilc@tradesrv.com.au From majordomo-users-owner Thu Nov 7 17:35:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA08271 for majordomo-users-outgoing; Thu, 7 Nov 1996 17:24:10 -0800 (PST) Received: from webdreams.com (www.webdreams.com [192.80.84.132]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA08263 for ; Thu, 7 Nov 1996 17:23:56 -0800 (PST) Received: from localhost by webdreams.com (5.65v3.2/1.1.10.5/29Aug96-0251AM) id AA20507; Thu, 7 Nov 1996 20:23:32 -0500 Date: Thu, 7 Nov 1996 20:23:31 -0500 (EST) From: Brock Rozen To: Bill Franklin III Cc: Kenneth C Rich , majordomo-users@GreatCircle.COM Subject: Re: digests problem In-Reply-To: <199611071628.KAA21373@rs232.bb-elec.com> Message-Id: X-Url: http://www.webdreams.com/~brozen Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 7 Nov 1996, Bill Franklin III wrote: > did you setup 1.94 from scratch or upgrade from 1.93..? if 1.93 works fine the > directories are there and such? why would 1.94 puke? do you use a digest.cf I've done both and they both work fine. > file for the digest configuration info? with a NUM and VOL file or do you use > the digest stuff that's in the intstant.config file? I use listname-digest.config and listname.config Again, I stress that you have to double-check your directories, working, archive. Both to make sure they exist, permissions are set and that they are set properly in the config files (namely majordomo.cf) ------------------------------------------------------------------------- | Brock Rozen | brozen@webdreams.com | http://www.webdreams.com/~brozen | ------------------------------------------------------------------------- From majordomo-users-owner Thu Nov 7 17:40:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA08466 for majordomo-users-outgoing; Thu, 7 Nov 1996 17:30:35 -0800 (PST) Received: from webdreams.com (www.webdreams.com [192.80.84.132]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA08417 for ; Thu, 7 Nov 1996 17:27:55 -0800 (PST) Received: from localhost by webdreams.com (5.65v3.2/1.1.10.5/29Aug96-0251AM) id AA19488; Thu, 7 Nov 1996 20:27:33 -0500 Date: Thu, 7 Nov 1996 20:27:33 -0500 (EST) From: Brock Rozen To: Kenneth C Rich Cc: majordomo-users@GreatCircle.COM Subject: Re: digests problem In-Reply-To: <199611071711.MAA28409@sisko.cc.rochester.edu> Message-Id: X-Url: http://www.webdreams.com/~brozen Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 7 Nov 1996, Kenneth C Rich wrote: > well just FYAmusement, fixing my majordomo.cf cured the mogombo masses > of majordomo abort messages. however it ain't creating any digest that > i can see, and certainly is not delivering it anywhere. and majordomo > is sending me confirmation on the mkdigest command. can anyone tell > what i _should_ be seeing? is the digest indeed created from the > archive? is it supposed to create its own archive? how does digest > know which file to digestify? You send a message through to listname. If it goes through properly to that list, then it also gets placed in $homedir/digests/listname-digest The files get stored as 001, 002, 003 . . . when a mkdigest is run or the limit is reached the program (I'm not sure if it's mj or resend) takes all the files in $homedir/digests/listname-digest (I'm using your $digest_work_dir setup) and creates a digest using the variables in your config file. If that goes through fine, it also archives it in $homedir/lists/listname-digest.archive Thus, be sure all the directories I mentioned above exist, as well as config files for your regular as well as digest list and that the permissions are right ont he directories. > > ------------------------------------------------------------------------ > > least far enough into digesting to trip over it. so i will change my: > > > > $digest_work_dir = '$homedir/digests'; > > to > > $digest_work_dir = "$homedir/digests"; > > > > and test. later. when i have reinforcements. > > -- > -ken rich "How many people can look at > a painting for even long enough > to peel an orange and eat it?" > -Sir Kenneth Clark kenr@cc.rochester.edu > ------------------------------------------------------------------------- | Brock Rozen | brozen@webdreams.com | http://www.webdreams.com/~brozen | ------------------------------------------------------------------------- From majordomo-users-owner Thu Nov 7 17:48:10 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA08797 for majordomo-users-outgoing; Thu, 7 Nov 1996 17:43:00 -0800 (PST) Received: from ponder (ponder.csci.unt.edu [129.120.3.16]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA08767 for ; Thu, 7 Nov 1996 17:42:21 -0800 (PST) Received: by ponder (5.61/1.36) id AA14974; Thu, 7 Nov 96 19:42:42 -0600 From: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) Message-Id: <9611080142.AA14974@ponder> Subject: unknown mailer error 139? To: majordomo-users@greatcircle.com Date: Thu, 7 Nov 1996 19:42:41 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Guys is there any person out there who is running majordomo on FreeBSD machine successfully? :-) I did everything but now I am getting these weard unknown mail errors.. can anyone give me some tips on that please? -- Faraz E-mail: sshamim@cs.unt.edu ########## fwd mail attached below ################# IN REPLY TO Mail Delivery Subsystem MAIL > From Thu Nov 7 19:37:16 1996 > Date: Thu, 7 Nov 1996 19:35:27 -0600 (CST) > From: Mail Delivery Subsystem > Subject: Returned mail: unknown mailer error 139 > Message-Id: <199611080135.TAA09405@psycho.csci.unt.edu> > To: owner-majordomo@psycho.csci.unt.edu > Mime-Version: 1.0 > Content-Type: multipart/report; report-type=delivery-status; > boundary="TAA09405.847416927/psycho.csci.unt.edu" > Auto-Submitted: auto-generated (failure) > > This is a MIME-encapsulated message > > --TAA09405.847416927/psycho.csci.unt.edu > > The original message was received at Thu, 7 Nov 1996 19:35:07 -0600 (CST) > from ponder.csci.unt.edu [129.120.3.16] > > ----- The following addresses have delivery notifications ----- > "|/usr/users/sshamim/majordomo-1.93/wrapper majordomo" (unrecoverable error) > (expanded from: ) > > ----- Transcript of session follows ----- > Message delivered to mailing list > Memory fault > 554 "|/usr/users/sshamim/majordomo-1.93/wrapper majordomo"... unknown mailer error 139 > > --TAA09405.847416927/psycho.csci.unt.edu > Content-Type: message/delivery-status > > Reporting-MTA: dns; psycho.csci.unt.edu > Received-From-MTA: DNS; ponder.csci.unt.edu > Arrival-Date: Thu, 7 Nov 1996 19:35:07 -0600 (CST) > > Final-Recipient: RFC822; majordomo@psycho.csci.unt.edu > Action: delivered (to mailing list) > Status: 2.0.0 > Last-Attempt-Date: Thu, 7 Nov 1996 19:35:27 -0600 (CST) > > Final-Recipient: RFC822; majordomo@psycho.csci.unt.edu > X-Actual-Recipient: RFC822; |/usr/users/sshamim/majordomo-1.93/wrapper majordomo@psycho.csci.unt.edu > Action: failed > Status: 5.0.0 > Last-Attempt-Date: Thu, 7 Nov 1996 19:35:26 -0600 (CST) > > --TAA09405.847416927/psycho.csci.unt.edu > Content-Type: message/rfc822 > > Return-Path: sshamim@ponder.csci.unt.edu > Received: from ponder (ponder.csci.unt.edu [129.120.3.16]) by psycho.csci.unt.edu (8.7.5/8.7.3) with SMTP id TAA09404 for ; Thu, 7 Nov 1996 19:35:07 -0600 (CST) > Received: by ponder (5.61/1.36) > id AA14045; Thu, 7 Nov 96 19:36:51 -0600 > From: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) > Message-Id: <9611080136.AA14045@ponder> > To: majordomo@psycho.csci.unt.edu > Date: Thu, 7 Nov 1996 19:36:50 -0600 (CST) > X-Mailer: ELM [version 2.4 PL24] > Mime-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > > lists > who unix-class > end > -- Faraz > E-mail: sshamim@cs.unt.edu > > > > --TAA09405.847416927/psycho.csci.unt.edu-- > > From majordomo-users-owner Thu Nov 7 18:03:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA09009 for majordomo-users-outgoing; Thu, 7 Nov 1996 17:46:24 -0800 (PST) Received: from ponder (ponder.csci.unt.edu [129.120.3.16]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA08964 for ; Thu, 7 Nov 1996 17:46:01 -0800 (PST) Received: by ponder (5.61/1.36) id AA15486; Thu, 7 Nov 96 19:46:32 -0600 From: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) Message-Id: <9611080146.AA15486@ponder> Subject: another mailer error To: majordomo-users@greatcircle.com Date: Thu, 7 Nov 1996 19:46:32 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk here I tried to send a mail to an actual list that I created and this time it bounced back with mailer error 2.. anyone knows? to remind you again the system is FreeBSD. -- Faraz E-mail: sshamim@cs.unt.edu ### fwded mail from mailer daemon attached below ############### IN REPLY TO Mail Delivery Subsystem MAIL > From Thu Nov 7 19:37:22 1996 > Date: Thu, 7 Nov 1996 19:35:32 -0600 (CST) > From: Mail Delivery Subsystem > Subject: Returned mail: unknown mailer error 2 > Message-Id: <199611080135.TAA09415@psycho.csci.unt.edu> > To: sshamim@psycho.csci.unt.edu > Mime-Version: 1.0 > Content-Type: multipart/report; report-type=delivery-status; > boundary="TAA09415.847416932/psycho.csci.unt.edu" > Auto-Submitted: auto-generated (failure) > > This is a MIME-encapsulated message > > --TAA09415.847416932/psycho.csci.unt.edu > > The original message was received at Thu, 7 Nov 1996 19:35:31 -0600 (CST) > from ponder.csci.unt.edu [129.120.3.16] > > ----- The following addresses have delivery notifications ----- > "|/usr/users/sshamim/majordomo-1.93/wrapper resend -h psycho.csci.unt.edu -l unix-class unix-class-outgoing" (unrecoverable error) > (expanded from: ) > > ----- Transcript of session follows ----- > Message delivered to mailing list > open of temp file /usr/users/sshamim/majordomo-1.93/lists/shlock.9417 failed > Permission denied > Failed to exec mailer "/usr/lib/sendmail -fMajordomo-Owner -t": No such file or directory at /usr/users/sshamim/majordomo-1.93/majordomo.pl line 311. > ABORT open of temp file /usr/users/sshamim/majordomo-1.93/lists/shlock.9417 failed > Permission denied at /usr/users/sshamim/majordomo-1.93/majordomo.pl line 209. > 554 "|/usr/users/sshamim/majordomo-1.93/wrapper resend -h psycho.csci.unt.edu -l unix-class unix-class-outgoing"... unknown mailer error 2 > > --TAA09415.847416932/psycho.csci.unt.edu > Content-Type: message/delivery-status > > Reporting-MTA: dns; psycho.csci.unt.edu > Received-From-MTA: DNS; ponder.csci.unt.edu > Arrival-Date: Thu, 7 Nov 1996 19:35:31 -0600 (CST) > > Final-Recipient: RFC822; unix-class@psycho.csci.unt.edu > Action: delivered (to mailing list) > Status: 2.0.0 > Last-Attempt-Date: Thu, 7 Nov 1996 19:35:32 -0600 (CST) > > Final-Recipient: RFC822; unix-class@psycho.csci.unt.edu > X-Actual-Recipient: RFC822; |/usr/users/sshamim/majordomo-1.93/wrapper resend -h psycho.csci.unt.edu -l unix-class unix-class-outgoing@psycho.csci.unt.edu > Action: failed > Status: 5.0.0 > Last-Attempt-Date: Thu, 7 Nov 1996 19:35:32 -0600 (CST) > > --TAA09415.847416932/psycho.csci.unt.edu > Content-Type: message/rfc822 > > Return-Path: sshamim@ponder.csci.unt.edu > Received: from ponder (ponder.csci.unt.edu [129.120.3.16]) by psycho.csci.unt.edu (8.7.5/8.7.3) with SMTP id TAA09414 for ; Thu, 7 Nov 1996 19:35:31 -0600 (CST) > Received: by ponder (5.61/1.36) > id AA14113; Thu, 7 Nov 96 19:37:14 -0600 > From: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) > Message-Id: <9611080137.AA14113@ponder> > To: unix-class@psycho.csci.unt.edu > Date: Thu, 7 Nov 1996 19:37:13 -0600 (CST) > X-Mailer: ELM [version 2.4 PL24] > Mime-Version: 1.0 > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > > testing mail sys > -- > -- Faraz > E-mail: sshamim@cs.unt.edu > > > > --TAA09415.847416932/psycho.csci.unt.edu-- > > From majordomo-users-owner Thu Nov 7 18:18:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA09945 for majordomo-users-outgoing; Thu, 7 Nov 1996 18:02:14 -0800 (PST) Received: from mail.his.com (mail.his.com [205.177.25.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id SAA09937 for ; Thu, 7 Nov 1996 18:02:01 -0800 (PST) Received: from localhost (kendall@localhost) by mail.his.com (8.6.9/8.6.12) with SMTP id UAA14157; Thu, 7 Nov 1996 20:51:18 -0500 Date: Thu, 7 Nov 1996 20:51:18 -0500 (EST) From: "Kendall P. Bullen" Reply-To: "Kendall P. Bullen" To: Jason L Tibbitts III cc: majordomo-users@GreatCircle.COM Subject: Re: "who" for moderator only? 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 7 Nov 1996, Jason L Tibbitts III wrote: *>>>>> "KPB" == Kendall P Bullen writes: *KPB> Hi All, Before I go hacking sources, I was wondering if anyone had *KPB> already come up with a patch for Mj 1.94 to allow 'who' to only work *KPB> for the moderator. *Why? Just use the approve command ("approve password who list"). Whoops, I think "why?" is because I'm a dork. :) Thanks. . . . I knew it worked with sub/unsub, I don't know why my brain didn't make the mental leap that it might work with any command, such as who. Again, thanks for pointing out the easy answer. Kendall (whew! no changing Mj! ;) From majordomo-users-owner Thu Nov 7 23:41:15 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id XAA20993 for majordomo-users-outgoing; Thu, 7 Nov 1996 23:07:59 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id XAA20984 for majordomo-users@greatcircle.com; Thu, 7 Nov 1996 23:07:51 -0800 (PST) Received: from relay4.UU.NET by ascb.saturnm.rosmail.com with ESMTP id CAA07420; (8.8.2/vak/1.9) Mon, 4 Nov 1996 02:59:48 +0300 (MSK) Received: from miles.greatcircle.com by relay4.UU.NET with ESMTP (peer crosschecked as: miles.greatcircle.com [198.102.244.34]) id QQbohj28666; Sun, 3 Nov 1996 18:59:16 -0500 (EST) Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22962 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:21:45 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22955 for ; Sun, 3 Nov 1996 15:21:42 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA07091 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:21:25 -0800 (PST) Received: from okjunc.junction.net (okjunc.junction.net [199.166.227.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA02535 for ; Fri, 1 Nov 1996 09:13:30 -0800 (PST) Received: from mauro.junction.net (ian.junction.net [204.239.30.6]) by okjunc.junction.net (8.6.11/8.6.11) with SMTP id JAA25336 for ; Fri, 1 Nov 1996 09:15:44 -0800 Date: Fri, 1 Nov 1996 09:15:44 -0800 Message-Id: <199611011715.JAA25336@okjunc.junction.net> X-Sender: mauro@junction.net (Unverified) 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: Mauro Incrocci Subject: can't unsubscribe from test list Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm using Majordomo 1.94 on an IBM running 1.2.13 Caldera as my OS. My sendmail version is 8. I have created a test list and can 'subscribe', 'who list', 'lists' but cannot 'unsubscribe' from it. The message I get back as the issuer of unsubscribe is: >>>> unsubscribe test mauro@junction.net The message I get back as the owner of the mailing list is: MAJORDOMO ABORT Can't open /majordomo/lists/test.new: Permission denied The permission of the test.new file is majordom.majordom and 660. Any help is appreciated. Mauro =-=-= From majordomo-users-owner Thu Nov 7 23:45:25 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id XAA20992 for majordomo-users-outgoing; Thu, 7 Nov 1996 23:07:54 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id XAA20974 for majordomo-users@greatcircle.com; Thu, 7 Nov 1996 23:07:45 -0800 (PST) Received: from relay5.UU.NET by ascb.saturnm.rosmail.com with ESMTP id CAA07408; (8.8.2/vak/1.9) Mon, 4 Nov 1996 02:58:58 +0300 (MSK) Received: from miles.greatcircle.com by relay5.UU.NET with ESMTP (peer crosschecked as: miles.greatcircle.com [198.102.244.34]) id QQbohj20072; Sun, 3 Nov 1996 18:58:36 -0500 (EST) Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA22843 for majordomo-users-outgoing; Sun, 3 Nov 1996 15:18:52 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA22834 for ; Sun, 3 Nov 1996 15:18:48 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id PAA07008 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 15:18:31 -0800 (PST) Received: from mrknox.lanl.gov (mrknox.lanl.gov [128.165.115.90]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id TAA27230 for ; Thu, 31 Oct 1996 19:59:43 -0800 (PST) Received: by mrknox.lanl.gov (1.37.109.16/16.2) id AA026060778; Thu, 31 Oct 1996 20:59:38 -0700 X-Sender: jmcdermo@mrknox.lanl.gov Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 31 Oct 1996 20:59:33 -0700 To: majordomo-users@GreatCircle.COM From: John McDermon Subject: changing default s*bscribe policy Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have tried editing the config_parse.pl file to change some of the default behavior for newly created lists. Everthing has been accepted, but one. I changed the default subscribe policy line to read (yes it's all on one line): 'subscribe_policy', "open\001closed\001auto\001open+confirm\001closed+confirm\001auto+confirm\001#!\ $default_subscribe_policy ? \$default_subscribe_policy : 'closed'", But new lists still are created open+confirm. I also tried changing the line and then recompiling and installing, but that didn't work either. What am I missing? TIA, --John +-------------------------------------------------+ | John McDermon, voice mail 7-7315 Fax 5-1002 | | CIC-2, MS B215 cell 699-4910, page 104-8665 | +-------------------------------------------------+ From majordomo-users-owner Thu Nov 7 23:48:08 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id XAA21017 for majordomo-users-outgoing; Thu, 7 Nov 1996 23:08:35 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id XAA21007 for majordomo-users@greatcircle.com; Thu, 7 Nov 1996 23:08:24 -0800 (PST) Received: from relay6.UU.NET by ascb.saturnm.rosmail.com with ESMTP id DAA08458; (8.8.2/vak/1.9) Mon, 4 Nov 1996 03:11:30 +0300 (MSK) Received: from miles.greatcircle.com by relay6.UU.NET with ESMTP (peer crosschecked as: miles.greatcircle.com [198.102.244.34]) id QQbohk17039; Sun, 3 Nov 1996 19:10:15 -0500 (EST) Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21629 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:55:16 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21622 for ; Sun, 3 Nov 1996 14:55:12 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06419 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:54:55 -0800 (PST) Received: from netop3.harvard.edu (netop3.harvard.edu [128.103.205.103]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA16557 for ; Thu, 24 Oct 1996 17:28:23 -0700 (PDT) Received: from hsph.harvard.edu (hsph.harvard.edu [128.103.75.21]) by netop3.harvard.edu (8.6.12/8.6.12) with ESMTP id UAA15607 for ; Thu, 24 Oct 1996 20:27:30 -0400 Received: by hsph.harvard.edu (SMI-8.6/SMI-SVR4) id UAA08464; Thu, 24 Oct 1996 20:28:18 -0400 Date: Thu, 24 Oct 1996 20:28:17 -0400 (EDT) From: Robert Byers To: majordomo-users@greatcircle.com Subject: The amazing shrinking subscriber list! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Over the last several weeks my MJ list included ~570 subscribers. Yesterday I happened to look at the list and it was down to only 18 subscribers. I quick scan of the Log file (which hasn't been flushed) reveals only 54 UN-subscribe requests. Folks, unless my math skills fail me, 570 - 54 does NOT equal 18 !!! That's when that all-too-common sinking feeling hit my gut :( Now, after many hours of restoring the original list, I have a few moments to think about what happened. I have to admit, I don't have much of a clue. The most likely culprit, I would say, is a panic crash our server sufferred on three occasions over the last month. Perhaps the subscriber list was open for writing at an inopportune moment. However, I would appreciate any input from list members. Has anyone experienced this problem with MJ? Or, has anyone seen MJ cause panic crashes on SunOS 4.1.3? [we never did identify what caused those crashes] My vital stats are: MJ 1.93 SunOS 4.1.3 perl 4.0.1.8 pl36 Thanks in advance, -Bob Byers HSPH Boston, MA From majordomo-users-owner Thu Nov 7 23:49:01 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id XAA21032 for majordomo-users-outgoing; Thu, 7 Nov 1996 23:08:49 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id XAA21022 for majordomo-users@greatcircle.com; Thu, 7 Nov 1996 23:08:38 -0800 (PST) Received: from relay5.UU.NET by ascb.saturnm.rosmail.com with ESMTP id DAA09280; (8.8.2/vak/1.9) Mon, 4 Nov 1996 03:18:15 +0300 (MSK) Received: from miles.greatcircle.com by relay5.UU.NET with ESMTP (peer crosschecked as: miles.greatcircle.com [198.102.244.34]) id QQbohl22391; Sun, 3 Nov 1996 19:17:45 -0500 (EST) Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21651 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:55:42 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21642 for ; Sun, 3 Nov 1996 14:55:37 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06429 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:55:20 -0800 (PST) Received: from eclectic.kluge.net (eclectic.kluge.net [130.215.248.68]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id CAA04477 for ; Fri, 25 Oct 1996 02:25:54 -0700 (PDT) Received: from localhost (felicity@localhost) by eclectic.kluge.net (8.8.2/kluge0.5) with SMTP id FAA23948 for ; Fri, 25 Oct 1996 05:27:39 -0400 Date: Fri, 25 Oct 1996 05:27:39 -0400 (EDT) From: Theo Van Dinter To: Majordomo-Users@GreatCircle.COM Subject: Re: problems with 1.94 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, 23 Oct 1996, Theo Van Dinter wrote: > I just upgraded my MD 1.93 installation to 1.94. Unfortunately, certain > commands (currently, I've only tested unsubscribe) doesn't work. If I > send an unsubscribe command, I get the following message back: [snip] > Everything is owned by majordom, group majordomo, owner and group have > full perms on the files/directories. My question is: > > Do I want everything gid majordomo or gid daemon? Under the Makefile for > the installation, it says the GID for daemon, but under all relavent doc > files and such it says gid majordomo. > > This is obviously some simple little perm problem, but I'm not sure > exactly where/what it is. Any ideas? I believe I saw someone mention that this was in the FAQ, but ... I sort of answered my own question anyway... As mentioned on the list before, I believe, I just simply added daemon and mail (the only possible users that would run majordomo ...) to the majordomo group. Fixed the problem right up. (The only problem is that when new files are created by majordomo (new configs, etc.) the group is set to daemon, not majordomo ... Not a biggie, just takes an extra second to su and change the group, but ... 8|) -- ----------------------------------------------------------------------------- Theo Van Dinter www: http://www.kluge.net/~felicity/ Vice-President WPI Lens and Lights Active Member in SocComm and ACM Any bug not fixed in one year becomes a feature. ----------------------------------------------------------------------------- From majordomo-users-owner Thu Nov 7 23:52:52 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id XAA21046 for majordomo-users-outgoing; Thu, 7 Nov 1996 23:09:10 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id XAA21035 for majordomo-users@greatcircle.com; Thu, 7 Nov 1996 23:09:01 -0800 (PST) Received: from relay6.UU.NET by ascb.saturnm.rosmail.com with ESMTP id DAA09337; (8.8.2/vak/1.9) Mon, 4 Nov 1996 03:21:16 +0300 (MSK) Received: from miles.greatcircle.com by relay6.UU.NET with ESMTP (peer crosschecked as: miles.greatcircle.com [198.102.244.34]) id QQbohl18050; Sun, 3 Nov 1996 19:20:11 -0500 (EST) Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA21793 for majordomo-users-outgoing; Sun, 3 Nov 1996 14:59:06 -0800 (PST) Received: from honor.greatcircle.com (honor.greatcircle.com [198.102.244.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA21716 for ; Sun, 3 Nov 1996 14:58:36 -0800 (PST) Received: (brent@localhost) by honor.greatcircle.com (8.7.5/Honor-960830-1) id OAA06437 for majordomo-users@greatcircle.com; Sun, 3 Nov 1996 14:58:18 -0800 (PST) Received: from camco2.celestial.com (camco2.celestial.com [192.136.111.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA16561 for ; Fri, 25 Oct 1996 09:57:26 -0700 (PDT) Received: by camco2.celestial.com (Smail3.1.29.1 #8) id m0vGpXu-000Q5SC; Fri, 25 Oct 96 09:55 PDT Message-Id: From: bill@celestial.com (Bill Campbell) Subject: Re: denying unsubscribe... To: lazlo@swcp.com (Lazlo Nibble) Date: Fri, 25 Oct 1996 09:55:46 -0700 (PDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <199610231535.JAA24452@llama.swcp.com> from "Lazlo Nibble" at Oct 23, 96 09:35:02 am Reply-To: bill@Celestial.COM Organization: Celestial Software, Mercer Island, WA 98040 X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > >> So, the "correct answer" might be: Majordomo is intended for voluntary, >> public mailing lists, and should thus allow anyone to unsubscribe, and allow >> any list member to 'who'. Other programs should be used for "broadcast" and >> private lists... Opinions on this statement? - Sarang > >Majordomo works fine for broadcast and private lists, unless your definition >of "broadcast" includes "users must not be allowed to unsubscribe themselves". >(I tend to agree with the other folks who think that if you're trying to >enforce subscriptions, the admin notification is probably a good enough tool >to let you do that.) And 1.94 supports per-list control over the "who" >command, so keeping lists completely private is a simple config option now. I don't see why this has been such a Big Deal. In our business of setting up our InterRack(rg) ISP systems around the U.S. and Canada, we always set up majordomo lists to mail to all customers based on the Unix group they belong to as well as a full list of all users (non-administrative accounts) on the system. These lists are all set up as moderated with a closed subscription policy. We set them up as moderated to prevent people spamming the ISP's customers, and to control what goes out to these lists. The lists themselves are maintained automatically in the same perl scripts that we use to keep the password databases up-to-date for the communications server's authentication databases (Xylogics Annex acp_passwd or radius users files). These are updated every fifteen minutes from cron, and any unsubscribe requests are simply ignored. Bill -- INTERNET: bill@Celestial.COM Bill Campbell; Celestial Systems, Inc. UUCP: camco!bill PO Box 820; 2835 82nd Avenue S.E. S-100 FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ Government spending? I don't know what it's all about. I don't know any more about this thing than an economist does, and, God knows, he doesn't know much. -- Will Rogers From majordomo-users-owner Fri Nov 8 01:05:50 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id AAA24016 for majordomo-users-outgoing; Fri, 8 Nov 1996 00:54:27 -0800 (PST) Received: from caesar.wits.ac.za (caesar.wits.ac.za [146.141.15.210]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id AAA24009 for ; Fri, 8 Nov 1996 00:54:16 -0800 (PST) Received: from uwcc.cc.wits.ac.za by caesar.wits.ac.za (SMI-8.6/SMI-SVR4) id KAA10361; Fri, 8 Nov 1996 10:53:07 -0200 Received: from UWCC/SpoolDir by uwcc.cc.wits.ac.za (Mercury 1.21); 8 Nov 96 10:54:46 GMT +2:00 Received: from SpoolDir by UWCC (Mercury 1.21); 8 Nov 96 10:54:19 GMT +2:00 From: "Peony" <090PEONY@UWCC.CC.WITS.AC.ZA> Organization: University of the Witwatersrand To: majordomo-users@GreatCircle.com Date: Fri, 8 Nov 1996 10:54:12 GMT + 2:00 Subject: Privacy Mailing Lists X-mailer: Pegasus Mail v3.1 (R1a) Message-ID: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Dear all, Is there a way to keep a mailing list so private that not even the administrator of the list can get access to any mail on the list? I'm administering in an university and some users require this for their confidential information. Personally i don't think this is possible, but any help would be greatly appreciated. Thanks in advance. Peony Hwang From majordomo-users-owner Fri Nov 8 01:25:28 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id BAA24372 for majordomo-users-outgoing; Fri, 8 Nov 1996 01:02:34 -0800 (PST) Received: from webdreams.com (www.webdreams.com [192.80.84.132]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id BAA24365 for ; Fri, 8 Nov 1996 01:02:23 -0800 (PST) Received: from localhost by webdreams.com (5.65v3.2/1.1.10.5/29Aug96-0251AM) id AA24622; Fri, 8 Nov 1996 04:02:26 -0500 Date: Fri, 8 Nov 1996 04:02:26 -0500 (EST) From: Brock Rozen To: Robert Byers Cc: majordomo-users@greatcircle.com Subject: Re: The amazing shrinking subscriber list! In-Reply-To: Message-Id: X-Url: http://www.webdreams.com/~brozen Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 24 Oct 1996, Robert Byers wrote: > However, I would appreciate any input from list members. Has anyone > experienced this problem with MJ? Yes, and I have two suggestions: 1) Upgrade to 1.94 -- The lock mechanism has changed and that seemed to prevent most, if not all, of my list crashing. 2) Add the following few lines to your majordomo.cf -- They will prevent majordomo from processing any further commands if the system load gets too high. I have found that when I lost lists, it was because majordomo was being pressured. While this might not exactly mean that mj is being pressured, but it sure helps the overall status on my system. Of course, feel free to change the number to whatever might suit your particular system. # System load protection. Stop any new processing if load gets too high. $uptime = `/usr/bin/uptime`; $uptime =~ s/.*:\s*//; $uptime =~ s/,.*//; if ($uptime >= 2.55) { exit 75; # E_TEMPFAIL } What it does is simply send the message back to sendmail and defers it. IT will still get processe,d just later. The number is 2.55 and that refers to the system load. ------------------------------------------------------------------------- | Brock Rozen | brozen@webdreams.com | http://www.webdreams.com/~brozen | ------------------------------------------------------------------------- From majordomo-users-owner Fri Nov 8 04:03:12 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id DAA00258 for majordomo-users-outgoing; Fri, 8 Nov 1996 03:51:16 -0800 (PST) Received: from flint.sentex.net (flint.sentex.net [199.212.134.7]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id DAA00248 for ; Fri, 8 Nov 1996 03:51:02 -0800 (PST) Received: (from uucp@localhost) by flint.sentex.net (8.7.5/8.7.3) with UUCP id GAA19302; Fri, 8 Nov 1996 06:51:08 -0500 (EST) Received: from localhost (nick@localhost) by xwing.xwing.org (8.7.5/8.7.3) with SMTP id GAA08941; Fri, 8 Nov 1996 06:39:18 -0500 Date: Fri, 8 Nov 1996 06:39:17 -0500 (EST) From: Nick Busigin To: Peony <090PEONY@UWCC.CC.WITS.AC.ZA> cc: majordomo-users@GreatCircle.COM Subject: Re: Privacy Mailing Lists 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 Fri, 8 Nov 1996, Peony wrote: > Is there a way to keep a mailing list so private that not even the > administrator of the list can get access to any mail on the list? I'm > administering in an university and some users require this for their > confidential information. > > Personally i don't think this is possible, but any help would be > greatly appreciated. Consider having the list subscribers use pgp encryption. Nick -------------------------------------------------------------------------- Nick Busigin nick@xwing.org To obtain my pgp public key, email me with the subject: "get pgp-key" -------------------------------------------------------------------------- From majordomo-users-owner Fri Nov 8 06:48:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA05906 for majordomo-users-outgoing; Fri, 8 Nov 1996 06:38:08 -0800 (PST) Received: from renko.ucs.ed.ac.uk (renko.ucs.ed.ac.uk [129.215.13.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA05872 for ; Fri, 8 Nov 1996 06:37:50 -0800 (PST) Received: from adrenalin.ucs.ed.ac.uk (adrenalin.ucs.ed.ac.uk [129.215.200.40]) by renko.ucs.ed.ac.uk (8.6.13/8.6.12) with SMTP id OAA23653; Fri, 8 Nov 1996 14:37:38 GMT Date: Fri, 8 Nov 1996 14:37:34 +0000 (GMT) From: Scott Larnach Reply-To: Scott.Larnach@ed.ac.uk To: Robert Byers cc: majordomo-users@GreatCircle.COM Subject: Re: Dots '.' at start of line needed In-Reply-To: <199611071944.OAA10111@hsph.harvard.edu> Message-ID: Organisation: Edinburgh University Computing Service MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 7 Nov 1996, Robert Byers wrote: > The users of my list have a need to send postings with a dot '.' at the > start of various lines in their postings The list concerns a software > package that uses a dot '.' as a command line prompt. When they send > program listings, often a line will contain nothing but a prompt ('.') in > the first column. > > Of course, mail interprets this as and end of data, and the rest of the > message is ignored. If sendmail is not properly configured then it will truncate message bodies at a line that consists only of a single dot. Some old user agents (such as UCB Mail) will do this too. Assuming that it's sendmail that's at fault: if you generate your sendmail.cf with m4 from a .mc file, add define(`confIGNORE_DOTS', `True')dnl to the .mc file and regenerate and reinstall your .cf file. Otherwise, add OiTrue to your .cf file. And remember to restart your sendmail daemon. Hope this helps Scott Larnach, Edinburgh University, Scotland From majordomo-users-owner Fri Nov 8 07:04:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA06291 for majordomo-users-outgoing; Fri, 8 Nov 1996 06:50:59 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA06276 for ; Fri, 8 Nov 1996 06:50:48 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA10301 for majordomo-users@greatcircle.com; Fri, 8 Nov 96 07:50:54 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA27784 for majordomo-users@greatcircle.com; Fri, 8 Nov 96 07:50:50 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id IAA04378; Fri, 8 Nov 1996 08:50:49 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id IAA11282; Fri, 8 Nov 1996 08:50:48 -0600 From: Dave Wolfe Message-Id: <199611081450.IAA11282@miaow.risc.sps.mot.com> Subject: Re: The amazing shrinking subscriber list! To: brozen@webdreams.com (Brock Rozen) Date: Fri, 8 Nov 1996 08:50:48 -0600 (CST) Cc: bob@hsph.harvard.edu, majordomo-users@greatcircle.com In-Reply-To: from "Brock Rozen" at Nov 8, 96 04:02:26 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > On Thu, 24 Oct 1996, Robert Byers wrote: [ Somebody's echoing old messages back to the list again ] [ and Brock Rozen responds: ] > > # System load protection. Stop any new processing if load gets too high. > $uptime = `/usr/bin/uptime`; > $uptime =~ s/.*:\s*//; > $uptime =~ s/,.*//; > if ($uptime >= 2.55) { > exit 75; # E_TEMPFAIL > } Too much work! :-) # System load protection. Delay any new processing if load gets too high. @uptime = split ' ', `/usr/bin/uptime`; if ($uptime[$#uptime] >= 2.55) { # last field is 15 minute avg exit 75; # E_TEMPFAIL } -- Dave Wolfe From majordomo-users-owner Fri Nov 8 08:07:06 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA08254 for majordomo-users-outgoing; Fri, 8 Nov 1996 08:00:06 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA08196 for ; Fri, 8 Nov 1996 07:59:52 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA20049 for majordomo-users@greatcircle.com; Fri, 8 Nov 96 08:59:58 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA00878 for majordomo-users@greatcircle.com; Fri, 8 Nov 96 08:59:57 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA05707; Fri, 8 Nov 1996 09:59:56 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA13785; Fri, 8 Nov 1996 09:59:54 -0600 From: Dave Wolfe Message-Id: <199611081559.JAA13785@miaow.risc.sps.mot.com> Subject: Re: unknown mailer error 139? To: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) Date: Fri, 8 Nov 1996 09:59:54 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <9611080142.AA14974@ponder> from "Syed Faraz Shamim" at Nov 7, 96 07:42:41 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Syed Faraz Shamim writes: ] > > > ----- Transcript of session follows ----- > > Message delivered to mailing list > > Memory fault > > 554 "|/usr/users/sshamim/majordomo-1.93/wrapper majordomo"... unknown mailer error 139 [This is a canned message.] You have asked a question about a "Permission denied", "Out of memory", "Bus error", "Segmentation violation", or that Majordomo runs a long time and consumes nearly all the CPU. All except the "Permission denied" are usually the result of a bug in Mj 1.93 that is triggered when you don't have Majordomo configured or installed correctly. Ask yourself the following questions. They'll give you guidance as to what you need to do to correct your Mj installation. 1) Do the ownerships and permissions on the list files, log file, and the directories where they reside allow the majordomo user to write to the files and create files in the directories? 2) Is wrapper configured and installed correctly? It must be owned by root and setuid (BSD-based systems are different: see Makefile). You can test this by logging on as a user other than root or your majordomo user and running the following *exactly as shown*: ./test ./wrapper test The first should show the uid/gids of the logon user. The second should show the majordomo uid/gids. If not, you don't have wrapper installed and/or configured correctly. Note that wrapper must be installed by the superuser (root) in order to set the owner and setuid permissions. If the first uid is 0 (zero), then you logged on as root (which totally invalidates the tests). If both tests report the same uids, you either logged on as your majordomo user (which totally invalidates the tests) or your wrapper isn't installed correctly. 3) Do your aliases use wrapper to invoke the Mj programs? 4) If you're running Perl 5, is your version of Perl at least 5.001e (perl -v will display the perl version). Perl 4.019 through 4.036 will work, but 5.000 through 5.001d will not. Version 5.003 is recommended (as of this writing) if you need to upgrade. Note that some changes are required in the Mj Perl files for Perl 5 (all '@' characters in quotish strings must be escaped, e.g. "user@host.net" must be changed to "user\@host.net"). -- Dave Wolfe From majordomo-users-owner Fri Nov 8 10:41:47 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA12199 for majordomo-users-outgoing; Fri, 8 Nov 1996 09:59:02 -0800 (PST) Received: from nmjc.org (nobunaga.nmjc.org [205.187.221.6]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA12173 for ; Fri, 8 Nov 1996 09:58:45 -0800 (PST) Received: from draco.atip.org.atip.org (ped0.nmjc.org) by nmjc.org (5.0/3.3W8) id AA29863; Fri, 8 Nov 1996 10:52:55 -0700 Received: by draco.atip.org.atip.org (SMI-8.6/SMI-SVR4) id LAA07562; Fri, 8 Nov 1996 11:00:09 -0700 Date: Fri, 8 Nov 1996 11:00:07 -0700 (MST) From: "Mr. Sarang Gupta" To: Dave Wolfe Cc: Brock Rozen , bob@hsph.harvard.edu, majordomo-users@greatcircle.com Subject: Re: The amazing shrinking subscriber list! In-Reply-To: <199611081450.IAA11282@miaow.risc.sps.mot.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > # System load protection. Delay any new processing if load gets too high. > @uptime = split ' ', `/usr/bin/uptime`; > if ($uptime[$#uptime] >= 2.55) { # last field is 15 minute avg > exit 75; # E_TEMPFAIL > } or even: $_=`/usr/bin/uptime`;s/.*,//;exit 75 if $_>2.55 - Sarang (all code is one line.. if the line's long enough) From majordomo-users-owner Fri Nov 8 12:25:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA18662 for majordomo-users-outgoing; Fri, 8 Nov 1996 11:58:52 -0800 (PST) Received: from ponder (ponder.csci.unt.edu [129.120.3.16]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA18595 for ; Fri, 8 Nov 1996 11:57:56 -0800 (PST) Received: by ponder (5.61/1.36) id AA17680; Fri, 8 Nov 96 13:58:16 -0600 From: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) Message-Id: <9611081958.AA17680@ponder> Subject: MAJORDOMO ABORT To: majordomo-users@greatcircle.com Date: Fri, 8 Nov 1996 13:58:15 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have updated the version to 1.94 and now it seems like a little problem.. anyone know what i need to do? Log permission are -rwx rw r and lists permission are drwxr-xr-x > > MAJORDOMO ABORT > > While running with an effective uid of 1 and an effective gid of 1 1 1, Majordomo > ran into the following problems: > Unable to write to log file, check permissions on /usr/users/sshamim/majordomo-1.94/Log > Unable to write to list directory $listdir, check permissions on /usr/users/sshamim/majordomo-1.94/lists > > > -- Faraz E-mail: sshamim@cs.unt.edu From majordomo-users-owner Fri Nov 8 12:50:41 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA20798 for majordomo-users-outgoing; Fri, 8 Nov 1996 12:37:10 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA20745 for ; Fri, 8 Nov 1996 12:36:39 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA29386 for majordomo-users@greatcircle.com; Fri, 8 Nov 96 13:36:37 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA10674 for majordomo-users@greatcircle.com; Fri, 8 Nov 96 13:36:35 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id OAA09169; Fri, 8 Nov 1996 14:36:34 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id OAA17684; Fri, 8 Nov 1996 14:36:32 -0600 From: Dave Wolfe Message-Id: <199611082036.OAA17684@miaow.risc.sps.mot.com> Subject: Re: The amazing shrinking subscriber list! To: sgupta@nmjc.org (Mr. Sarang Gupta) Date: Fri, 8 Nov 1996 14:36:32 -0600 (CST) Cc: david_wolfe@risc.sps.mot.com, brozen@webdreams.com, bob@hsph.harvard.edu, majordomo-users@greatcircle.com In-Reply-To: from "Mr. Sarang Gupta" at Nov 8, 96 11:00:07 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Mr. Sarang Gupta writes: ] > > [ Dave Wolfe writes: ] > > > > # System load protection. Delay any new processing if load gets too high. > > @uptime = split ' ', `/usr/bin/uptime`; > > if ($uptime[$#uptime] >= 2.55) { # last field is 15 minute avg > > exit 75; # E_TEMPFAIL > > } > > or even: > > $_=`/usr/bin/uptime`;s/.*,//;exit 75 if $_>2.55 I didn't want to offend anyone's sensibilities by Randalizing it, :-) although I generally prefer the "exit 75 if ...;" form for 1-line conditionals. -- Dave Wolfe From majordomo-users-owner Fri Nov 8 13:19:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA21883 for majordomo-users-outgoing; Fri, 8 Nov 1996 13:00:42 -0800 (PST) Received: from mailhub.aros.net (mailhub.aros.net [205.164.111.17]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA21865 for ; Fri, 8 Nov 1996 13:00:12 -0800 (PST) From: Damian@aros.net Received: from aros.net.aros.net (pm1-22.slc.aros.net [207.173.24.23]) by mailhub.aros.net (8.7.6/Unknown) with SMTP id OAA26835 for ; Fri, 8 Nov 1996 14:00:17 -0700 (MST) Message-ID: <32839F48.52F1@aros.net> Date: Fri, 08 Nov 1996 13:59:52 -0700 Reply-To: Damian@aros.net Organization: Damian's Music Emporium X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: What does: 'Can't create output' mean? References: <327E5B59.4FD8@aros.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've been recieving quite a few of these messages. Being new at this stuff, I'm not understanding who or where the problem is coming from. Is it the sender? Or someone on the list who's mailbox is full? What is it trying to do? thanks... > From: > MAILER-DAEMON@evans.CUDenver.EDU (Mail Delivery Subsystem) > To: > > > > ----- Transcript of session follows ----- > mail: Cannot append to /var/mail/dcerman > 550 ... Can't create output > > ----- Unsent message follows ----- > Received: by evans.CUDenver.EDU (5.x/SUN-Solaris/2.3) > id AA14608; Fri, 8 Nov 1996 13:47:14 -0700 > Errors-To: > Received: from terra.aros.net (terra.aros.net [205.164.111.10]) by mailhub.aros.net (8.7.6/Unknown) with ESMTP id NAA26591; Fri, 8 Nov 1996 13:41:15 -0700 (MST) > Received: (from majordom@localhost) by terra.aros.net (8.7.6/8.6.12) id NAA15397 for mobility-list-safe-outgoing; Fri, 8 Nov 1996 13:41:01 -0700 > X-Authentication-Warning: terra.aros.net: majordom set sender to owner-mobility-list using -f > Received: from linden.fortnet.org (keen@linden.fortnet.org [199.45.144.10]) by terra.aros.net (8.7.6/8.6.12) with ESMTP id NAA15389 for ; Fri, 8 Nov 1996 13:40:54 -0700 > Received: (from keen@localhost) by linden.fortnet.org (8.8.0/8.7.2) id NAA01973; Fri, 8 Nov 1996 13:41:38 -0700 (MST) > Date: Fri, 8 Nov 1996 13:41:38 -0700 (MST) > From: Daniel Cerman > To: Come On Mobility > Subject: Mobility: Come On Baby lyrics > In-Reply-To: <199611070637.BAA00952@mail.third-wave.com> > Message-Id: > Mime-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII > Sender: owner-mobility-list@aros.net > Precedence: bulk > Reply-To: mobility-list@aros.net -- Damian@aros.net ================================== http://www.aros.net/~damian/ Home to the Mobility Mailing List ================================== From majordomo-users-owner Fri Nov 8 14:03:28 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA24613 for majordomo-users-outgoing; Fri, 8 Nov 1996 13:50:51 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id NAA24602 for ; Fri, 8 Nov 1996 13:50:34 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA10884 for majordomo-users@greatcircle.com; Fri, 8 Nov 96 14:50:32 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA12951 for majordomo-users@greatcircle.com; Fri, 8 Nov 96 14:50:20 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id PAA10514; Fri, 8 Nov 1996 15:50:19 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id PAA17785; Fri, 8 Nov 1996 15:05:03 -0600 From: Dave Wolfe Message-Id: <199611082105.PAA17785@miaow.risc.sps.mot.com> Subject: Re: MAJORDOMO ABORT To: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) Date: Fri, 8 Nov 1996 15:05:03 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <9611081958.AA17680@ponder> from "Syed Faraz Shamim" at Nov 8, 96 01:58:15 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Syed Faraz Shamim writes: ] > > I have updated the version to 1.94 and now it seems like a little > problem.. anyone know what i need to do? > > Log permission are -rwx rw r > and lists permission are drwxr-xr-x The file mode flags are meaningful *only* in the context of the user and group owner IDs, but you've failed to provide that critical piece of information. > > MAJORDOMO ABORT > > > > While running with an effective uid of 1 and an effective gid of 1 1 1, Majordomo > > ran into the following problems: > > Unable to write to log file, check permissions on /usr/users/sshamim/majordomo-1.94/Log > > Unable to write to list directory $listdir, check permissions on /usr/users/sshamim/majordomo-1.94/lists Since Mj is running as daemon/daemon (assuming daemon == 1 for both uid and gid), odds are that the file and directory in question aren't owned by daemon. I suspect you either didn't configure or install wrapper correctly. Check the owners and modes of wrapper. -- Dave Wolfe From majordomo-users-owner Fri Nov 8 15:18:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA27938 for majordomo-users-outgoing; Fri, 8 Nov 1996 14:37:33 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA27922 for ; Fri, 8 Nov 1996 14:37:17 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id QAA15112; Fri, 8 Nov 1996 16:37:25 -0600 (CST) To: Damian@aros.net Cc: majordomo-users@GreatCircle.COM Subject: Re: What does: 'Can't create output' mean? References: <327E5B59.4FD8@aros.net> <32839F48.52F1@aros.net> From: Jason L Tibbitts III Date: 08 Nov 1996 16:37:24 -0600 In-Reply-To: Damian@aros.net's message of Fri, 08 Nov 1996 13:59:52 -0700 Message-ID: Lines: 17 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "D" == Damian writes: D> I've been recieving quite a few of these messages. Being new at this D> stuff, I'm not understanding who or where the problem is coming from. [Bounce deleted] A remote site is telling you there was a delivery problem there. There is nothing you can do except wait or remove the address from your list. It isn't a problem at your site. You will get bounces of all different kinds from all different sites. In general the only thing you can do is look at them to figure out which address is bouncing and remove it. You can't fix problems at other peoples' sites. - J< From majordomo-users-owner Fri Nov 8 17:33:04 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA09423 for majordomo-users-outgoing; Fri, 8 Nov 1996 17:12:49 -0800 (PST) Received: from tahi.tradesrv.com.au ([203.63.230.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA09383 for ; Fri, 8 Nov 1996 17:12:21 -0800 (PST) Received: from neil.tradesrv.com.au ([203.63.230.20]) by tahi.tradesrv.com.au (8.6.12/8.6.9) with SMTP id MAA31719 for ; Sat, 9 Nov 1996 12:12:27 +1100 Message-ID: <3283D750.6D25@tradesrv.com.au> Date: Sat, 09 Nov 1996 11:58:56 +1100 From: Neil Cotty Reply-To: neilc@tradesrv.com.au Organization: Internet Trading Services Pty. Ltd. X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Remote Protocol Error - Digests Only Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I've been testing my MJ 1.94 install over the last couple of days concentrating on digesting. I finally got the digest to go off (reached the size limit :) ) however a couple of the people who are testing it with me were not sent their mail and MJ popped this 'Remote Protocol Error' message. I can send email to these addresses just fine. It only occurs when the digest goes off. Could somebody explain this message to me. I'm afraid I don't have a clue about this one. My owner-vizsla-digest points to owner-vizsla which is me, neilc (no trailing comma, do I need one ?). Heres a copy of the relevant section from the alias file. # Vizsla List owner-vizsla: neilc vizsla: "| /usr/local/majordomo/wrapper resend -l vizsla -h tradesrv.com.au vizsla-outgoing" vizsla-approval: owner-vizsla vizsla-outgoing: :include:/usr/local/majordomo/lists/vizsla, vizsla-archive, "| /usr/local/majordomo/wrapper digest -r -C -l vizsla-digest vizsla-digest-outgoing" owner-vizsla-outgoing: owner-vizsla vizsla-archive: "| /usr/local/majordomo/wrapper archive2.pl -a -d -f /usr/local/majordomo/archives/vizsla.archive/vizsla -d -a" owner-vizsla-archive: owner-vizsla vizsla-request: "| /usr/local/majordomo/wrapper majordomo -l vizsla" owner-vizsla-request: owner-vizsla vizsla-digest: vizsla vizsla-digest-outgoing: :include:/usr/local/majordomo/lists/vizsla-digest vizsla-digest-request: "| /usr/local/majordomo/wrapper majordomo -l vizsla-digest" owner-vizsla-digest: owner-vizsla owner-vizsla-digest-outgoing: owner-vizsla owner-vizsla-digest-request: owner-vizsla vizsla-digest-approval: vizsla-approval Is it anything to do with this ? I'm running 5.003 and I have not made this change as I don't remember seeing it in the docs or the FAQ. >4) If you're running Perl 5, is your version of Perl at least 5.001e > (perl -v will display the perl version). Perl 4.019 through 4.036 > will work, but 5.000 through 5.001d will not. Version 5.003 is > recommended (as of this writing) if you need to upgrade. Note that > some changes are required in the Mj Perl files for Perl 5 (all '@' > characters in quotish strings must be escaped, e.g. "user@host.net" > must be changed to "user\@host.net"). Heres the message that I receive. The original message was received at Fri, 8 Nov 1996 10:47:14 +1100 from majordom@localhost ----- The following addresses had delivery problems ----- djb9895@tam2000.tamu.edu (unrecoverable error) (expanded from: :include:/usr/local/majordomo/lists/vizsla-digest) ddnelson@ix.netcom.com (unrecoverable error) (expanded from: :include:/usr/local/majordomo/lists/vizsla-digest) ----- Transcript of session follows ----- ... while talking to tam2000.tamu.edu.: >>> DATA <<< 550 owner-vizsla-digest... User unknown 554 djb9895@tam2000.tamu.edu... Remote protocol error ... while talking to ixmail5.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail2.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail3.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail6.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail4.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixsrs5.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixsrs4.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown 554 ddnelson@ix.netcom.com... Remote protocol error ----- Message header follows ----- Subject: vizsla-digest V1 #1 Date: Fri, 8 Nov 1996 10:47:14 +1100 From: owner-vizsla-digest (vizsla-digest) Reply-To: vizsla To: vizsla-digest ----- Message body suppressed ----- Kind Regards, Neil Cotty. -- Internet Trading Services Access Providers Level 1, Fayworth House Internet Database Systems 379-383 Pitt Street Client/Server Sydney, NSW 2000 Consulting Australia Phone : +61 2 264 8811 Fax: +61 2 264 8822 Modems: +61 2 264 8810 URL: http://www.tradesrv.com.au Email: neilc@tradesrv.com.au From majordomo-users-owner Fri Nov 8 23:32:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id XAA26954 for majordomo-users-outgoing; Fri, 8 Nov 1996 23:26:40 -0800 (PST) Received: from cloud.ccsf.cc.ca.us (cloud.ccsf.cc.ca.us [147.144.2.46]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id XAA26945 for ; Fri, 8 Nov 1996 23:26:27 -0800 (PST) Received: from localhost (jjah@localhost) by cloud.ccsf.cc.ca.us (8.7.3/8.6.9) with SMTP id XAA26786 for ; Fri, 8 Nov 1996 23:24:20 -0800 (PST) Date: Fri, 8 Nov 1996 23:24:20 -0800 (PST) From: "Joe R. Jah" Reply-To: "Joe R. Jah" To: majordomo-users@GreatCircle.COM Subject: sequencer.pl In-Reply-To: <31CB7D36.1739@io.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Folks, How can one take advantage of sequencer.pl in Mj 1.94. I believe one has to hack resend to use sequencer.pl, but it seems to be more complicated than my elementary perl knowledge can fathom. A couple of weeks ago some one wrote here that five lines of code would do it. How many characters per line?-) I appreciate any hint or pointer or five lines of code.8-} Joe _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ -\<, _/ _/ _/_/_/ _/ _/ ........O/ O _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us From majordomo-users-owner Sat Nov 9 01:18:14 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id BAA29231 for majordomo-users-outgoing; Sat, 9 Nov 1996 01:08:19 -0800 (PST) Received: from sun.parallaxinc.com (sun.parallaxinc.com [165.113.203.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id BAA29224 for ; Sat, 9 Nov 1996 01:08:10 -0800 (PST) Received: (from tmornini@localhost) by sun.parallaxinc.com (8.7.5/8.7.3) id BAA00211 for majordomo-users@greatcircle.com; Sat, 9 Nov 1996 01:08:13 -0800 (PST) From: Tom Mornini Message-Id: <199611090908.BAA00211@sun.parallaxinc.com> Subject: 1.94 and Perl 5.003? To: majordomo-users@greatcircle.com Date: Sat, 9 Nov 1996 01:08:10 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I installed 1.94 and Perl 5.003 a couple of days ago. I compiled clean on Solaris 2.5, current patches, gcc 2.7.2, sendmail 8.7.5. wrapper config-test yields... -- snipped for brevity -- Good: "require"d /export/u1/majordomo/majordomo.cf okay. Good: found ctime.pl okay. Good: found majordomo_version.pl okay. Good: found majordomo.pl okay. Good: found shlock.pl okay. Good: found config_parse.pl okay. You're running Majordomo Version 1.94. /export/u1/majordomo /usr/local/lib/perl5/sun4-solaris/5.003 /usr/local/lib/perl5 /usr/local/lib/perl5/site_perl/sun4-solaris /usr/local/lib/perl5/site_perl . Good: changedir to /export/u1/majordomo succeeded. Good: Created a mock lock file. ---------------------- temp directory ---------------------- Good: Created a temp file in $TMPDIR (/usr/tmp). ---------------------- list directory ---------------------- Good: list directory /export/u1/majordomo/lists has good permissions. --------------------------- log --------------------------- Good: logfile /export/u1/majordomo/Log exists and is writeable. ------------------------- Mailers ------------------------- You have defined a mailer for delivery. Attempting to verify that this is a valid mailer...looks okay. You have defined a mailer for delivering administrative messages. Attempting to verify that this is a valid mailer...looks okay. ------------------ Checking majordomo.cf ------------------ Checking to see if there are new variables that should be in your majordomo.cf file...Nope, none that I see. ----------------------- end of tests ----------------------- Nothing bad found! Majordomo _should_ work correctly. If it doesn't, check your configuration file (/export/u1/majordomo/majordomo.cf) closely, and if it still looks okay, consider asking the majordomo-users mailing list at "majordomo-users@greatcircle.com" for assistance. Be sure and fully specify what your problems are, and what type of machine (and operating system) you are using. -- ended of snipped output -- Sharp eyed readers will note how I came up with this address. :-) Most (haven't tested everything, perhaps all) of the administrive functions appear to work OK, but when mail goes to the list, I get a giant shit-storm of abort messages that don't quit until I stop sendmail and kill off the processes. The abort messages report: MAJORDOMO ABORT do_exec_sendmail, mailer -fMajordomo-Owner not executable Which indicates to me that the expansion of $sendmail_command isn't happening at line 348 of majordomo.pl. $sendmail_command IS defined in majordomo.cf. Any ideas? I'd LOVE to get the list going again... I'm NOT a subscribed to your list. Please respond by e-mail. -- Tom Mornini ---------------------------------------------------------- -- Parallax, Inc. ------------------------------------------------------ -- Makers of really cool PIC development tools & the BASIC Stamps ------ -- http://www.parallaxinc.com ftp://ftp.parallaxinc.com/pub -- From majordomo-users-owner Sat Nov 9 05:02:54 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id EAA04486 for majordomo-users-outgoing; Sat, 9 Nov 1996 04:57:03 -0800 (PST) Received: from cedar.strohwig.com ([206.150.138.253]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id EAA04479 for ; Sat, 9 Nov 1996 04:56:53 -0800 (PST) Received: from cedar (cedar [206.150.138.253]) by cedar.strohwig.com (SMI-8.6/8.7) with SMTP id GAA02494; Sat, 9 Nov 1996 06:56:30 -0600 Date: Sat, 9 Nov 1996 06:56:29 -0600 (CST) From: Richard McKay X-Sender: rmckay1@cedar To: majordomo-users@greatcircle.com cc: mcarthey@execpc.com Subject: No Response from Majordomo user. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm am new to this group and Majordomo on general. On that note, HI! I have a concern and a question to pose. I have Majordomo 1.94 running on a Solaris 2.5 Sparc box. The lists were working just fine for several days after the initial installation of Majordomo. So far so good. Yesterday, I had to take this same sparc down for maintenance (normal procedure). No errors were found while the server was booting. Here is the problem, Majordomo no longer processes any incoming mail at all. Everything destined for Majordomo is stored in /usr/mail/majordomo. This shouldn't happen. Nothing changed in /etc/mail/aliases or majordomo.cf. The user settings were never altered one bit. I even removed the majordomo-1.94 directory (and contents) from the /usr/local/bin area, recompiled wrapper and re-installed everything. Majordomo still does not respond to incoming mail any more. All my mailing utilities work (sendmail, uux, uucp etc..) as this email can atest to that. I'm stumped, can anyone help? Has anyone ever seen this before? I appologize if this question has been asked before, but like I stated before, I am but a newbie. ;) Let me know if you need more info. Thanks, Richard W. McKay rmckay1@strohwig.com From majordomo-users-owner Sat Nov 9 13:50:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA18400 for majordomo-users-outgoing; Sat, 9 Nov 1996 13:36:21 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA18393 for ; Sat, 9 Nov 1996 13:36:11 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id QAA28982; Sat, 9 Nov 1996 16:36:18 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id QAA04153; Sat, 9 Nov 1996 16:36:15 -0500 (EST) Message-Id: <199611092136.QAA04153@augusta.math.psu.edu> To: John McDermon cc: majordomo-users@GreatCircle.COM Subject: Re: changing default s*bscribe policy In-reply-to: Your message of "Thu, 31 Oct 1996 20:59:33 MST." References: 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: Sat, 09 Nov 1996 16:36:14 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , John McDermon writes: >I have tried editing the config_parse.pl file to change some of the default >behavior for newly created lists. Everthing has been accepted, but one. Why are you editing config_parse.pl? See the following line in your majordomo.cf: # $config'default_subscribe_policy = "open+confirm"; Uncomment it and edit to taste. --Dave From majordomo-users-owner Sat Nov 9 15:50:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA21526 for majordomo-users-outgoing; Sat, 9 Nov 1996 15:46:31 -0800 (PST) Received: from sufsys.sufsys.com (mail.sufsys.com [205.183.39.93]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id PAA21519 for ; Sat, 9 Nov 1996 15:46:22 -0800 (PST) Received: by sufsys.sufsys.com with Microsoft Exchange (IMC 4.0.837.3) id <01BBCE65.C17D3E50@sufsys.sufsys.com>; Sat, 9 Nov 1996 17:45:11 -0600 Message-ID: From: "Scott C. Villinski" To: "'majordomo-users@greatcircle.com'" Subject: Compile problem - wrapper.c Date: Sat, 9 Nov 1996 17:45:10 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a Linux 1.2.13 machine that I have successfully compiled mj-1.94 on. Now I am trying to compile mj-1.94 on another 1.2.13 machine, this time our production mail server and I keep getting the following error: gcc -DBIN=\"/usr/src/majordomo-1.94\" -DPATH=\"PATH=/bin:/usr/bin\" -DHOME=\"HOME=/usr/src/majordomo-1.94\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF=\"MAJORDOMO_CF=/usr/src/majordomo-1.94/majordomo.cf\" -DPOSIX_UID=443 -DPOSIX_GID=2 -o wrapper wrapper.c In file included from wrapper.c:25: /usr/include/string.h:44: parse error before `memmove' /usr/include/string.h:44: parse error before `__dest' /usr/include/string.h:45: warning: data definition has no type or storage class /usr/include/string.h:50: parse error before `__memccpy' /usr/include/string.h:50: parse error before `__dest' /usr/include/string.h:51: warning: data definition has no type or storage class /usr/include/string.h:53: parse error before `memccpy' /usr/include/string.h:53: parse error before `__dest' /usr/include/string.h:54: warning: data definition has no type or storage class /usr/include/string.h:62: parse error before `memset' /usr/include/string.h:62: parse error before `__s' /usr/include/string.h:62: warning: data definition has no type or storage class /usr/include/string.h:72: parse error before `memchr' /usr/include/string.h:72: parse error before `__s' /usr/include/string.h:72: warning: data definition has no type or storage class /usr/include/string.h:122: parse error before `memmem' /usr/include/string.h:122: parse error before `__needle' /usr/include/string.h:123: warning: data definition has no type or storage class /usr/include/string.h:153: parse error before `__src' /usr/include/string.h:156: parse error before `__s' /usr/include/string.h:159: parse error before `__s1' /usr/include/string.h:195: parse error before `memfrob' /usr/include/string.h:195: parse error before `__s' /usr/include/string.h:195: warning: data definition has no type or storage class /usr/include/string.h:197: parse error before `__from' make: *** [wrapper] Error 1 Any thoughts? I am using the same configuration on both machine. I checke the /usr/include/string.h file on each machine and they are identical. Thanks, Scott Scott C. Villinski, CNE Consulting Engineer Sufficient Systems, Inc. Email: svillins@sufsys.com USCOMM - Internet Division Email: svillins@uscomm.net 2860 Patton Road Phone: 612.638.9190 Roseville, MN 55113 Fax: 612.638.9290 Web: http://www.sufsys.com http://www.uscomm.net From majordomo-users-owner Sat Nov 9 16:16:48 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA22585 for majordomo-users-outgoing; Sat, 9 Nov 1996 16:10:47 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id QAA22578 for ; Sat, 9 Nov 1996 16:10:37 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id SAA09916; Sat, 9 Nov 1996 18:10:47 -0600 (CST) To: "Scott C. Villinski" Cc: "'majordomo-users@greatcircle.com'" Subject: Re: Compile problem - wrapper.c References: From: Jason L Tibbitts III Date: 09 Nov 1996 18:10:47 -0600 In-Reply-To: "Scott C. Villinski"'s message of Sat, 9 Nov 1996 17:45:10 -0600 Message-ID: Lines: 17 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "SCV" == Scott C Villinski writes: SCV> Now I am trying to compile mj-1.94 on another 1.2.13 machine, this SCV> time our production mail server and I keep getting the following SCV> error: [Piles of errors having nothing to do with the code of wrapper.] I suspect something is seriously hosed with the Linux installation on that machine. Check things like compiler versions. Ask folks in the Linux newsgroups. Of course, if the configuration variables are the same you can just copy the binary. Or copy your makefile onto the machine that works, build a binary there, and copy it back. - J< From majordomo-users-owner Sat Nov 9 22:01:50 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA28379 for majordomo-users-outgoing; Sat, 9 Nov 1996 21:53:11 -0800 (PST) Received: from ns1.fni.com (ns1.fni.com [204.181.104.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id VAA28372 for ; Sat, 9 Nov 1996 21:53:03 -0800 (PST) Received: from ns1.fni.com (ns1.fni.com [204.181.104.1]) by ns1.fni.com (8.7.6/8.7.3) with SMTP id XAA09187 for ; Sat, 9 Nov 1996 23:53:22 -0600 Date: Sat, 9 Nov 1996 23:53:22 -0600 (CST) From: Michael Brennen Reply-To: Michael Brennen To: majordomo-users@greatcircle.com Subject: Digest List Name Privacy Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've run MJ for nearly two years; I'm currently on 1.94. Tonight I pulled up my first digest. It is running fine so far, but I am not yet able to remove the header information that gives the name of the outgoing list. I want to remove the "for list-digest-outgoing" part below. I've successfully done this for the normal lists. I could not find this in the FAQ. Received: (from majordom@localhost) by ns1.fni.com (8.7.6/8.7.3) id XAA09028 for list-digest-outgoing; Sat, 9 Nov 1996 23:36:38 -0600 ^^^^^^^^^^^^^^^^^^^^^^^^ The digest aliases are below. I've put ",nobody" on several of the aliases, as with the normal list, but so far it has not made any differnce. Experimentally, I also added a couple of "owner-" aliases where none were indicated in the examples, but that has done nothing either. If anyone has any experience with hiding the list name on digests I would appreciate it. TIA, -- Michael list-digestify: "|/usr/local/majordomo/wrapper digest -r -C -l list-digest list-digest-outgoing,nobody" list-digest: list owner-list-digest: owner-list,nobody list-digest-outgoing: :include:/usr/local/majordomo/lists/list-digest owner-list-digest-outgoing: owner-list,nobody list-digest-request: "|/usr/local/majordomo/wrapper majordomo -l list-digest" owner-list-digest-request: owner-list,nobody list-digest-approval: owner-list,nobody From majordomo-users-owner Sun Nov 10 16:48:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA15597 for majordomo-users-outgoing; Sun, 10 Nov 1996 16:34:55 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id QAA15575 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 16:34:47 -0800 (PST) Received: from antares.pegasus.com.br (antares.pegasus.com.br [200.251.120.50]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id EAA24584 for ; Wed, 6 Nov 1996 04:41:30 -0800 (PST) Received: from Mizar.INTERMAIL (algol.pegasus.com.br [200.251.120.35]) by antares.pegasus.com.br (8.6.12/8.6.9) with SMTP id JAA01902 for ; Wed, 6 Nov 1996 09:33:42 -0300 Message-ID: <3280878A.370E@pegasus.com.br> Date: Wed, 06 Nov 1996 10:41:46 -0200 From: Frederico Ferreira da Silva Reply-To: fred@pegasus.com.br Organization: InterMail Ltda X-Mailer: Mozilla 3.01b1 (Win95; I) MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Can't unsubscribe from test list Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm using Majordomo 1.94 on an Linux. I have created a test list and can 'subscribe', 'who list', 'lists' but cannot 'unsubscribe' from it. The message I get back as the issuer of unsubscribe is: >>>> unsubscribe test fred@antares.pegasus.com.br The message I get back as the owner of the mailing list is: MAJORDOMO ABORT Can't open /majordomo/lists/test.new: Permission denied The permission of the test.new file is majordom.majordom and 666. Any help is appreciated. Fred. -- +-----------------------------------------------------+ | Frederico F. da Silva e-mail: fred@pegasus.com.br | | InterMail Ltda. Rua Sta Rita Durão, 321,209 | | 30140-110 - Belo Horizonte, MG Brazil | | http://www.pegasus.com.br +55-31-281-1508 | +-----------------------------------------------------+ From majordomo-users-owner Sun Nov 10 17:02:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA15646 for majordomo-users-outgoing; Sun, 10 Nov 1996 16:35:39 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id QAA15629 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 16:35:28 -0800 (PST) Received: from sisko.cc.rochester.edu (sisko.cc.rochester.edu [128.151.219.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA09309; Wed, 6 Nov 1996 08:24:26 -0800 (PST) Received: (from kenr@localhost) by sisko.cc.rochester.edu (8.7.6/8.7.3) id LAA27324; Wed, 6 Nov 1996 11:27:11 -0500 (EST) Date: Wed, 6 Nov 1996 11:27:11 -0500 (EST) From: Kenneth C Rich Message-Id: <199611061627.LAA27324@sisko.cc.rochester.edu> To: majordomo-users@GreatCircle.COM Subject: Re: unsatisfied unsubscribers Cc: majordomo-users-request@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Can someone please remove me from the list. I have tried but havenot > been sucessfull. i feel for his pain. ;-) regardless of whether the user was doing it right or not, i vaguely recall someone (i _think_ it was on majordomo-users) explaining there is considerable latency in this list so you get a lot of messages after unsubscribing or some such silliness. it might be nice if such a notice, if true, were included in the majordomo-users.intro. it might also be nice if the intro went out on the list weekly, biweekly, or monthly. i know, the folks who need it never think to read it. eh what? ---------------------------------------------------------------------- Subject: Majordomo results Reply-To: Majordomo@GreatCircle.COM >>>> intro majordomo-users #### No intro available for majordomo-users. ---------------------------------------------------------------------- -- -ken rich "How many people can look at a painting for even long enough to peel an orange and eat it?" -Sir Kenneth Clark kenr@cc.rochester.edu From majordomo-users-owner Sun Nov 10 17:06:50 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA15780 for majordomo-users-outgoing; Sun, 10 Nov 1996 16:38:22 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id QAA15770 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 16:38:16 -0800 (PST) Received: from paloalto.access.hp.com (paloalto.access.hp.com [15.254.56.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA02381 for ; Wed, 6 Nov 1996 14:28:40 -0800 (PST) Received: from hp10sso1.nsr.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA140299314; Wed, 6 Nov 1996 14:28:36 -0800 Message-Id: <199611062228.AA140299314@paloalto.access.hp.com> Received: by hp10sso1.nsr.hp.com (1.39.111.2/16.2) id AA108879313; Wed, 6 Nov 1996 14:28:33 -0800 From: Jack Maynard Subject: Problem with resend To: majordomo-users@greatcircle.com Date: Wed, 06 Nov 1996 14:28:33 PST X-Mailer: Elm [revision: 110.32] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi everyone, I have just completed installing Majordomo ver. 1.94 on an hp-ux 755 running 10.01. I have a problem. Everything appears to work correctly except the resend. I have created a list, subscribed, unsubscribed, etc. all with success, but when I try to post a message to the list I get two errors: ------------- >From MAILER-DAEMON@hp10sso1.nsr.hp.com Wed Nov 6 13:55:05 PST 1996 Subject: Returned mail: aliasing/forwarding loop broken To: owner-security@hp10sso1.nsr.hp.com 501 include:/opt/majordomo/lists/security... X \. 400 delivery agent not configured 554 aliasing/forwarding loop broken ------------- here's my alias file: ------------- majordomo : "|/opt/majordomo/wrapper majordomo" owner-majordomo : jackm majordomo-owner : jackm security : "|/opt/majordomo/wrapper resend -l security security-list" security-list : include:/opt/majordomo/lists/security owner-security : jackm security-owner : jackm security-approval : jackm security-request : "|/opt/majordomo/wrapper request-answer security" ------------- Any ideas? Jack Maynard 206/643-8750 -- "Two of the most famous products of Berkeley are LSD and Unix. I don't think that this is a coincidence." -Anonymous From majordomo-users-owner Sun Nov 10 17:32:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA17996 for majordomo-users-outgoing; Sun, 10 Nov 1996 17:25:55 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id RAA17989 for ; Sun, 10 Nov 1996 17:25:46 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id TAA04082; Sun, 10 Nov 1996 19:18:42 -0600 (CST) To: Jack Maynard Cc: majordomo-users@GreatCircle.COM Subject: Re: Problem with resend References: <199611062228.AA140299314@paloalto.access.hp.com> From: Jason L Tibbitts III Date: 10 Nov 1996 19:18:41 -0600 In-Reply-To: Jack Maynard's message of Wed, 06 Nov 1996 14:28:33 PST Message-ID: Lines: 11 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "JM" == Jack Maynard writes: JM> here's my alias file: JM> security-list : include:/opt/majordomo/lists/security Looks to me like you left out a colon. Try: security-list : :include:/opt/majordomo/lists/security - J< From majordomo-users-owner Sun Nov 10 18:06:54 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA19537 for majordomo-users-outgoing; Sun, 10 Nov 1996 17:56:21 -0800 (PST) Received: from chaos.taylored.com (chaos.taylored.com [206.53.224.58]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA19491 for ; Sun, 10 Nov 1996 17:56:00 -0800 (PST) Received: (qmail 20976 invoked by uid 20); 11 Nov 1996 01:56:10 -0000 Date: Sun, 10 Nov 1996 20:56:10 -0500 (EST) From: Chael Hall To: majordomo-users@GreatCircle.COM cc: majordomo-workers@greatcircle.com, Chael Hall Subject: ANNOUNCE: patches for Majordomo 1.94 available Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm working on switching all of my mailing lists over from Majordomo 1.92 to version 1.94. In the process of making all of the changes to 1.94 that I had made to 1.92, I decided to go ahead and make each one a patch. Since these patches may be useful to others, I've put them together in a package. Here's the README information from the package: Chael's Majordomo Patches ========================= Version ======= This is version 1.00 of Chael Hall's Majordomo patches The release date is 11/10/96. The latest version can be retrieved via the world-wide web at http://www.chaos.taylored.com/pub/development/ or via anonymous ftp from Host: ftp.chaos.taylored.com Directory: /pub/development. Filename: mj-patches-current.tar.gz These locations will always allow you to access the current version. Earlier versions may be available as well. Table of Contents ================= [1] Abstract [2] Introduction [3] Applying the Patches [4] Copyright and Disclaimer [5] Files [1] Abstract ============ This is a set of patches to apply to Majordomo 1.94 that add functionality or fix specific problems with the software. See the very end of this document for copyright, distribution, and disclaimer. [2] Introduction ================ In the time that I have been running Majordomo, I have made several changes to the software to make my life easier. Some of the changes were requested by list members and others were just my idea of a way to accomplish a specific goal. Most of the patches in this package add non-standard features to Majordomo that allow me to run my mailing lists the way I want to (automatically!) without being constantly bombarded with questions from the list members. If you are running qmail and are interested in making Majordomo and qmail work well together, please go to the web or FTP site listed at the top of this document and retrieve the package named 'mj+qmail.' That package includes patches to Majordomo, suggestions for improving security, and scripts to help setup new lists. If you are running sendmail, smail or another mailer that makes you tear your hair out, you might consider retrieving qmail and trying it out. It's significantly faster than any other mailer I have used and is very flexible. You can install and play with it without affecting your other mailer's environment. So give it a shot! qmail can be retrieved via anonymous FTP from ftp://koobera.math.uic.edu/pub/software/. The filename of the latest release should be 'qmail.tar.gz' [3] Applying the Patches ======================== Backup the Majordomo files just to be safe. Then, assuming you have the program 'patch', you can simply execute it with the patches file included with this distribution on standard input: % patch < guidelines/patch I STRONGLY recommend that you read the accompanying README file for each patch before you apply it. [4] Copyright and Disclaimer ============================ I wrote these utilities for myself and thought that other people might want to use them too. If they help you, great. If they don't, write your own. Please send any patches to me at nowhere@chaos.taylored.com, but do NOT distribute these files individually or in modified form. Despite the standard disclaimer (which you all know and love, so I'm not going to repeat it here), I reserve all rights to this software and this is the way I want it. If you can't deal, delete it. mj-patches-1.00 Copyright 1996 Chael Hall (nowhere@chaos.taylored.com) All rights are reserved. You are granted a non-exclusive license to use and modify these files as long as you do not distribute modified versions or any copy that does not contain all of the files in this package. majordomo 1.94 Copyright 1992 D. Brent Chapman [5] Files ========= The files included with this distribution are: README - This file commands/ - Patch to allow shortened forms of some commands commands/README - Instructions for applying this patch commands/patch - Context diff patch for Majordomo guidelines/ - Patch to allow multiple files to be sent upon subscribing to a list guidelines/README - Instructions for applying this patch guidelines/patch - Context diff patch for Majordomo redirection/ - Patch to redirect botched requests of the form 'subscribe LIST DIGEST ...' to 'subscribe LIST-DIGEST ...' redirection/README - Instructions for applying this patch redirection/patch - Context diff patch for Majordomo refuse/ - Patch to implement a blocking mechanism in resend for addresses that should not be allowed to post (a blacklist.) refuse/README - Instructions for applying this patch refuse/patch - Context diff patch for Majordomo reply-to/ - Patch to make resend remove Reply-To: headers IFF it will be adding its own Reply-To: header to the message reply-to/README - Instructions for applying this patch reply-to/patch - Context diff patch for Majordomo resend-fix/ - Patch to fix miscellaneous bugs in resend resend-fix/README - Instructions for applying this patch resend-fix/patch - Context diff patch for Majordomo virtual-rewrite/ - Patch for resend to correctly rewrite list addresses when dealing with virtual domains virtual-rewrite/README - Instructions for applying this patch virtual-rewrite/patch - Context diff patch for Majordomo -- Chael Hall, nowhere@chaos.taylored.com http://www.chaos.taylored.com/home/nowhere/ From majordomo-users-owner Sun Nov 10 18:17:37 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA20700 for majordomo-users-outgoing; Sun, 10 Nov 1996 18:13:30 -0800 (PST) Received: from sun630mp.infomania.com (sun630mp.infomania.com [199.182.37.33]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id SAA20684 for ; Sun, 10 Nov 1996 18:13:21 -0800 (PST) Received: (from tmornini@localhost) by sun630mp.infomania.com (8.7.5/8.7.3) id SAA24611 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 18:13:09 -0800 (PST) From: Tom Mornini Message-Id: <199611110213.SAA24611@sun630mp.infomania.com> Subject: 5.003 & 1.94 fixed To: majordomo-users@greatcircle.com Date: Sun, 10 Nov 1996 18:13:09 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I fought for another 6 hours or so, and could not get 1.94 working with perl 5.003 on Solaris 2.5 (current patches). I decided to re-read everything carefully, which made me re-evaluate my archiving and digesting functions, which made me re-evaluate my directory tree. After moving almost everything to new locations, I grabbed a fresh 1.94, re-edited the majordomo.cf to reflect the new directory structure, re-installed, and everything now works wonderfully. It is clear from some investigation that majordomo.cf was not being eval'd since the substitutions on variables defined within were not being recognized. Anybody have any ideas? -- Tom Mornini -- Parallax From majordomo-users-owner Sun Nov 10 18:21:54 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA20869 for majordomo-users-outgoing; Sun, 10 Nov 1996 18:16:24 -0800 (PST) Received: from sun630mp.infomania.com (sun630mp.infomania.com [199.182.37.33]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id SAA20855 for ; Sun, 10 Nov 1996 18:16:13 -0800 (PST) Received: (from tmornini@localhost) by sun630mp.infomania.com (8.7.5/8.7.3) id SAA24827 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 18:16:15 -0800 (PST) From: Tom Mornini Message-Id: <199611110216.SAA24827@sun630mp.infomania.com> Subject: Want an automated list cleaner? To: majordomo-users@greatcircle.com Date: Sun, 10 Nov 1996 18:16:14 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I finally got around to writing some Perl scripts to automate the list cleaning procedure on my system. This software is brand-new, only been used once (not very well tested), has not been packaged for easy installation, and is probably typical for a first-attempt piece of code. It is totally unusable to anyone who doesn't 1) know perl, 2) know a lot about their system, 3) understand the value of backups, 4) understand how completely not responsible I am if something goes wrong and brings down their system :-) It is written for use with Majordomo, but could probably work with other packages as well. With that behind me, let me tell you how it works. I wrote three programs, boing-sender, boing-receiver, and boing-fixer. boing-sender sends a message, with an easily parsable subject line that contains list name and subscribed address, to each subscriber of each list. It pauses 10 seconds between messages to keep the # of processes to a low roar. The body of the message informs the recipient that to stay subscribed to the list, he/she should simply delete the message. It also tells them that if they want off, they should simply reply to it without substantially altering the subject line. boing-receiver parses incoming mail for that recognizable subject line. If it finds one, it writes the subscribed address to a file named list-name-results. This is what happens when people reply to the message sent by boing-sender, or a message is bounced in the process. boing-fixer stops sendmail (by /etc/init.d/sendmail stop), parses a dead.letter file for any matches, and adds them to the results file. It then cats the subscription list and the list-name-results file, pipes them to sort, pipes that to uniq -u and writes the results to list-name-new. Then it copies list-name-new over the original subscription list, removes the results and dead.letter files. Finally, it restarts sendmail. I created a new user on my system, boing. I gave boing a home directory and shell, and a .forward file that points to boing-receiver. I set cron to run boing-sender once a week, Fridays at 8:00 p.m. I set cron to run boing-fixer once a week, Monday sat 6:00 a.m. This radically thinned about 10% of the recipients off my list, who were generating about 2000 bounces per day! It also allowed users who didn't know how they were subscribed, to get off the list easily. Anyone else interested? -- Tom Mornini -- InfoMania From majordomo-users-owner Sun Nov 10 20:40:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA24609 for majordomo-users-outgoing; Sun, 10 Nov 1996 20:17:07 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id UAA23515 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 20:01:16 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA24214 for ; Thu, 7 Nov 1996 14:23:39 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id QAA05384; Thu, 7 Nov 1996 16:23:38 -0600 (CST) To: Kevin Chu Cc: majordomo-users@GreatCircle.COM Subject: Re: Taboo-headers... References: From: Jason L Tibbitts III Date: 07 Nov 1996 16:23:37 -0600 In-Reply-To: Kevin Chu's message of Thu, 07 Nov 1996 13:07:31 -0600 (CST) Message-ID: Lines: 13 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "KC" == Kevin Chu writes: KC> $global_taboo_headers = <<'END'; /^from:.*kevie@creighton.edu/i END KC> This should be able to block all messages that I send (just for KC> testing), but it doesn't and I can still subscribe to any list that is KC> open. Any suggestions??? You can't yet block anything coming in to Majordomo. This will be remedied in a future version. Of course this _will_ block messages sent to any of the lists, but only if you're using resend. - J< From majordomo-users-owner Sun Nov 10 20:45:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA24785 for majordomo-users-outgoing; Sun, 10 Nov 1996 20:18:12 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id TAA23393 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 19:59:42 -0800 (PST) Received: from antares.pegasus.com.br (antares.pegasus.com.br [200.251.120.50]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA09002 for ; Thu, 7 Nov 1996 10:33:27 -0800 (PST) Received: from Mizar.INTERMAIL (algol.pegasus.com.br [200.251.120.35]) by antares.pegasus.com.br (8.6.12/8.6.9) with SMTP id PAA04753 for ; Thu, 7 Nov 1996 15:25:55 -0300 Message-ID: <32822BB7.3C2A@pegasus.com.br> Date: Thu, 07 Nov 1996 16:34:31 -0200 From: Frederico Ferreira da Silva Reply-To: fred@pegasus.com.br Organization: InterMail Ltda X-Mailer: Mozilla 3.01b1 (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Can't unsubscribe Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm using Majordomo 1.94 on an Linux. I have created a test list and can 'subscribe', 'who list', 'lists' but cannot 'unsubscribe' from it. The message I get back as the issuer of unsubscribe is: >>>> unsubscribe test The message I get back as the owner of the mailing list is: MAJORDOMO ABORT chmod(33206, "/server/majordomo-1.94/lists/test.new"): Operation not permitted the arquives are in 666 mod majordomo own and daemon group. Any help is appreciated. Fred. -- +-----------------------------------------------------+ | Frederico F. da Silva e-mail: fred@pegasus.com.br | | InterMail Ltda. Rua Sta Rita Durão, 321,209 | | 30140-110 - Belo Horizonte, MG Brazil | | http://www.pegasus.com.br +55-31-281-1508 | +-----------------------------------------------------+ From majordomo-users-owner Sun Nov 10 20:47:02 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA25054 for majordomo-users-outgoing; Sun, 10 Nov 1996 20:19:39 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id UAA23497 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 20:00:35 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA16882 for ; Thu, 7 Nov 1996 12:50:18 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA22894 for majordomo-users@greatcircle.com; Thu, 7 Nov 96 13:50:21 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA11166 for majordomo-users@greatcircle.com; Thu, 7 Nov 96 13:50:20 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id OAA20724; Thu, 7 Nov 1996 14:50:19 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id NAA22355; Thu, 7 Nov 1996 13:58:50 -0600 From: Dave Wolfe Message-Id: <199611071958.NAA22355@miaow.risc.sps.mot.com> Subject: Re: Taboo-headers... To: kevie@creighton.edu (Kevin Chu) Date: Thu, 7 Nov 1996 13:58:50 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Kevin Chu" at Nov 7, 96 01:07:31 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Kevin Chu writes: ] > > $global_taboo_headers = <<'END'; > /^from:.*kevie@creighton.edu/i > END > > This should be able to block all messages that I send (just for testing), > but it doesn't and I can still subscribe to any list that is open. The taboo stuff applies only to list messages, not to Mj requests. Escape the '@' and you'll have better luck, e.g.: /^from:.*kevie\@creighton.edu/i -- Dave Wolfe From majordomo-users-owner Sun Nov 10 20:50:09 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA23850 for majordomo-users-outgoing; Sun, 10 Nov 1996 20:05:12 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id UAA23830 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 20:05:04 -0800 (PST) Received: from belize.ucs.indiana.edu (belize.ucs.indiana.edu [129.79.10.64]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA05557 for ; Fri, 8 Nov 1996 06:20:53 -0800 (PST) Received: from stone51.netlab.indiana.edu (stone51.netlab.indiana.edu [129.79.51.21]) by belize.ucs.indiana.edu (8.7.3/8.7.3/1.12IUPO) with ESMTP id JAA23046; Fri, 8 Nov 1996 09:20:58 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by stone51.netlab.indiana.edu (8.7.5/8.7.3) with ESMTP id JAA27823; Fri, 8 Nov 1996 09:20:58 -0500 (EST) Message-Id: <199611081420.JAA27823@stone51.netlab.indiana.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: Robert Byers cc: majordomo-users@GreatCircle.COM Subject: Re: The amazing shrinking subscriber list! In-reply-to: Your message of "Thu, 24 Oct 1996 20:28:17 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Nov 1996 09:20:58 -0500 From: Allen Hutchison Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've had a similar problem on a solaris 2.4 machine. In my case, /tmp fills up occasionally, and then MD clears the list of subscribers. This happens on the first time a subscribe/unsubscribe request hits the list, after /tmp fills up. I don't know if this is fixed in 1.94 or not. Allen Robert Byers is rumored to have said: >Over the last several weeks my MJ list included ~570 subscribers. >Yesterday I happened to look at the list and it was down to only 18 >subscribers. I quick scan of the Log file (which hasn't been flushed) >reveals only 54 UN-subscribe requests. > >Folks, unless my math skills fail me, 570 - 54 does NOT equal 18 !!! > >That's when that all-too-common sinking feeling hit my gut :( > >Now, after many hours of restoring the original list, I have a few >moments to think about what happened. > >I have to admit, I don't have much of a clue. > >The most likely culprit, I would say, is a panic crash our server >sufferred on three occasions over the last month. Perhaps the subscriber >list was open for writing at an inopportune moment. > >However, I would appreciate any input from list members. Has anyone >experienced this problem with MJ? > >Or, has anyone seen MJ cause panic crashes on SunOS 4.1.3? [we never did >identify what caused those crashes] > > >My vital stats are: > > MJ 1.93 > SunOS 4.1.3 > perl 4.0.1.8 pl36 > > >Thanks in advance, >-Bob Byers > HSPH > Boston, MA > -_=+\|`~[{]};:'",<.>/?-_=+\|`~[{]};:'",<.>/?-_=+\|`~[{]};:'",<.>/?-_=+\|`~[ Allen Dale Hutchison http://www.netlab.indiana.edu/~hutchiso UCS Network Lab Coordinator mailto:hutchiso@netlab.indiana.edu PGP Key Finger: hutchiso@stone51.netlab.indiana.edu 812-855-1878 -_=+\|`~[{]};:'",<.>/?-_=+\|`~[{]};:'",<.>/?-_=+\|`~[{]};:'",<.>/?-_=+\|`~[ From majordomo-users-owner Sun Nov 10 22:21:20 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id WAA02084 for majordomo-users-outgoing; Sun, 10 Nov 1996 22:08:31 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id WAA02076 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 22:08:27 -0800 (PST) Received: from mozart.quinncom.net (quinncom.net [205.136.86.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA12839 for ; Sun, 10 Nov 1996 15:21:58 -0800 (PST) Received: from tpupke.awod.com (chs0127.awod.com [198.81.225.46]) by mozart.quinncom.net (8.7.6/8.6.9) with SMTP id SAA15688 for ; Sun, 10 Nov 1996 18:20:54 -0500 Message-Id: <3.0.32.19961110182158.006a3e94@popserver.quinncom.net> X-Sender: tpupke@popserver.quinncom.net X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Sun, 10 Nov 1996 18:22:02 -0500 To: majordomo-users@GreatCircle.com From: Trace Pupke Subject: Majordomo ABORT - Can someone help? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm getting this error message when I try to unsubscribe. --- MAJORDOMO ABORT chown(54, 2, "/usr/local/majordomo/lists/test.new"): Operation not permitted --- I'm trying to set up majordomo on Linux 2.0.18 I have the user and group set as majordom:daemon (54:2) I added majordom to the group listing for daemon Does any have a little time and patience to help?? Thanks ~~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ Trace Pupke <>< HTML Coordinator Quinn Communications tpupke@quinncom.net http://www.quinncom.net/ ~~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ From majordomo-users-owner Sun Nov 10 22:27:12 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id WAA01924 for majordomo-users-outgoing; Sun, 10 Nov 1996 22:06:47 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id WAA01915 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 22:06:44 -0800 (PST) Received: from sparkie.osl.state.or.us (sparkie.osl.state.or.us [192.84.215.34]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id QAA22766 for ; Sat, 9 Nov 1996 16:22:44 -0800 (PST) Received: (from chris@localhost) by sparkie.osl.state.or.us (8.6.9/8.6.9) id QAA06007; Sat, 9 Nov 1996 16:21:46 -0800 Date: Sat, 9 Nov 1996 16:21:45 -0800 (PST) From: Christopher Adams To: majordomo-users@greatcircle.com Subject: turn off messages to listowner? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is there a way to turn off the messages that are sent to the listowner when an individual subscribes or unsubscribes? Christopher Adams Automated Systems Oregon State Library chris@sparkie.osl.state.or.us From majordomo-users-owner Mon Nov 11 00:47:37 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id AAA07706 for majordomo-users-outgoing; Mon, 11 Nov 1996 00:44:29 -0800 (PST) Received: from tahi.tradesrv.com.au ([203.63.230.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id AAA07699 for ; Mon, 11 Nov 1996 00:44:13 -0800 (PST) Received: from neil.tradesrv.com.au ([203.63.230.20]) by tahi.tradesrv.com.au (8.6.12/8.6.9) with SMTP id TAA11581 for ; Mon, 11 Nov 1996 19:44:32 +1100 Message-ID: <3286E40A.4F22@tradesrv.com.au> Date: Mon, 11 Nov 1996 19:30:02 +1100 From: Neil Cotty Reply-To: neilc@tradesrv.com.au Organization: Internet Trading Services Pty. Ltd. X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Remote Protocol # 3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Sorry to be a pain in the proverbial but this is the third time I've posted this message with no responses. Does anybody out there have any idea about what is going on. Even a one line hint will do. The mailing list is for a non-profit group of doggy lovers around the globe who are getting pretty nasty...! Hi, I've been testing my MJ 1.94 install over the last couple of days concentrating on digesting. I finally got the digest to go off (reached the size limit :) ) however a couple of the people who are testing it with me were not sent their mail and MJ popped this 'Remote Protocol Error' message. I can send email to these addresses just fine. It only occurs when the digest goes off. Could somebody explain this message to me. I'm afraid I don't have a clue about this one. My owner-vizsla-digest points to owner-vizsla which is me, neilc (no trailing comma, do I need one ?). Heres a copy of the relevant section from the alias file. # Vizsla List owner-vizsla: neilc vizsla: "| /usr/local/majordomo/wrapper resend -l vizsla -h tradesrv.com.au vizsla-outgoing" vizsla-approval: owner-vizsla vizsla-outgoing: :include:/usr/local/majordomo/lists/vizsla, vizsla-archive, "| /usr/local/majordomo/wrapper digest -r -C -l vizsla-digest vizsla-digest-outgoing" owner-vizsla-outgoing: owner-vizsla vizsla-archive: "| /usr/local/majordomo/wrapper archive2.pl -a -d -f /usr/local/majordomo/archives/vizsla.archive/vizsla -d -a" owner-vizsla-archive: owner-vizsla vizsla-request: "| /usr/local/majordomo/wrapper majordomo -l vizsla" owner-vizsla-request: owner-vizsla vizsla-digest: vizsla vizsla-digest-outgoing: :include:/usr/local/majordomo/lists/vizsla-digest vizsla-digest-request: "| /usr/local/majordomo/wrapper majordomo -l vizsla-digest" owner-vizsla-digest: owner-vizsla owner-vizsla-digest-outgoing: owner-vizsla owner-vizsla-digest-request: owner-vizsla vizsla-digest-approval: vizsla-approval Is it anything to do with this ? I'm running 5.003 and I have not made this change as I don't remember seeing it in the docs or the FAQ. >4) If you're running Perl 5, is your version of Perl at least 5.001e > (perl -v will display the perl version). Perl 4.019 through 4.036 > will work, but 5.000 through 5.001d will not. Version 5.003 is > recommended (as of this writing) if you need to upgrade. Note that > some changes are required in the Mj Perl files for Perl 5 (all '@' > characters in quotish strings must be escaped, e.g. "user@host.net" > must be changed to "user\@host.net"). Heres the message that I receive. The original message was received at Fri, 8 Nov 1996 10:47:14 +1100 from majordom@localhost ----- The following addresses had delivery problems ----- djb9895@tam2000.tamu.edu (unrecoverable error) (expanded from: :include:/usr/local/majordomo/lists/vizsla-digest) ddnelson@ix.netcom.com (unrecoverable error) (expanded from: :include:/usr/local/majordomo/lists/vizsla-digest) ----- Transcript of session follows ----- ... while talking to tam2000.tamu.edu.: >>> DATA <<< 550 owner-vizsla-digest... User unknown 554 djb9895@tam2000.tamu.edu... Remote protocol error ... while talking to ixmail5.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail2.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail3.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail6.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixmail4.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixsrs5.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown ... while talking to ixsrs4.ix.netcom.com.: >>> DATA <<< 550 owner-vizsla-digest... User unknown 554 ddnelson@ix.netcom.com... Remote protocol error ----- Message header follows ----- Subject: vizsla-digest V1 #1 Date: Fri, 8 Nov 1996 10:47:14 +1100 From: owner-vizsla-digest (vizsla-digest) Reply-To: vizsla To: vizsla-digest ----- Message body suppressed ----- Kind Regards, Neil Cotty. -- Internet Trading Services Access Providers Level 1, Fayworth House Internet Database Systems 379-383 Pitt Street Client/Server Sydney, NSW 2000 Consulting Australia Phone : +61 2 264 8811 Fax: +61 2 264 8822 Modems: +61 2 264 8810 URL: http://www.tradesrv.com.au Email: neilc@tradesrv.com.au From majordomo-users-owner Mon Nov 11 04:16:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id EAA15990 for majordomo-users-outgoing; Mon, 11 Nov 1996 04:11:22 -0800 (PST) Received: from beetroot.va.com.au (beetroot.va.com.au [203.15.106.100]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id EAA15971 for ; Mon, 11 Nov 1996 04:11:06 -0800 (PST) Received: from descent ([203.15.106.200]) by beetroot.va.com.au (post.office MTA v2.0 0813 ID# 0-0U10) with SMTP id AAA74 for ; Mon, 11 Nov 1996 22:44:42 +1030 Message-ID: <328717CC.255C@va.com.au> Date: Mon, 11 Nov 1996 22:40:52 +1030 From: "Florian Mueller" Reply-To: floyd@va.com.au Organization: Virtual Artists X-Mailer: Mozilla 3.0Gold (WinNT; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: solaris binary of majordomo Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk please! Can someone please send me the binary version of majordomo for solaris 2.5 (SunOS5.5), because I can't make Perl running! I am sure that it is somewhere out there, so please help! Please! Floyd -- Florian Mueller +61 8 8223 2288 Virtual Artists 187RundleStreet Adelaide SA5000 From majordomo-users-owner Mon Nov 11 05:47:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA18605 for majordomo-users-outgoing; Mon, 11 Nov 1996 05:39:54 -0800 (PST) Received: from i2bs.com (i2bs.com [205.242.194.21]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id FAA18597 for ; Mon, 11 Nov 1996 05:39:44 -0800 (PST) Received: from skb.sbcomp.net (bernoulli-05.inpi.com [207.152.80.105]) by i2bs.com (8.7.5/8.7.3) with SMTP id HAA02204 for ; Mon, 11 Nov 1996 07:39:43 -0600 (CST) Message-Id: <3.0.32.19961111074012.006bd7d4@205.242.194.21> X-Sender: skb@205.242.194.21 X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 11 Nov 1996 07:40:25 -0600 To: majordomo-users@GreatCircle.COM From: "Steven K. Buehler" Subject: digests Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a problem that I hope someone can help me with. For about 2 months of maybe a little more, I have been using the digest function and it has worked flawlessly from a cron job. Now, all of a sudden, last night I get two messages back that say the following (list names have been changed for privacy): 1st message________________________________________________________ Date: Mon, 11 Nov 1996 07:31:41 -0600 (CST) To: skb@sbcomp.net From: Majordomo Subject: Majordomo results Reply-To: Majordomo -- >>>> mkdigest my-list-digest 17November96 *** digest: failed errors follow producing my-digest V1 #54 Warning: cannot determine current directory /usr/home/majordom/digests/my-list-digest/001: No such file or directory ABORT Warning: cannot determine current directory /usr/home/majordom/digests/my-list-digest/001: No such file or directory >>>> end END OF COMMANDS End of first message_________________________________________________ 2nd message________________________________________________________ Date: Mon, 11 Nov 1996 07:31:42 -0600 (CST) To: Postmaster From: Majordomo Subject: MAJORDOMO ABORT Reply-To: Majordomo -- MAJORDOMO ABORT Warning: cannot determine current directory /usr/home/majordom/digests/my-list-digest/001: No such file or directory End of 2nd message___________________________________________________ Does anybody know what might cause this? Nothing has been changed on the system and it has been making the digests now for 2 months or so from the cron job every single night at the same time. I have checked and the directory and the file does exist and the write permissions are the same as always. drwxrwxr-x 2 majordom daemon 512 Nov 11 07:31 my-list-digest/ -rw-rw---- 1 majordom daemon 2144 Nov 10 08:10 001 The first is the directory (of course) and the second is the file in the directory (of course again). Any help would be appreciated. Oh...One other thing. When the mkdigest runs from the cron job or from a message from me to majordomo to do a mkdigest, I get these messages and also a .LOCK file is created in the my-list-digest directory that has to be manually deleted. Thanks Steve ====================================================== Steven K. Buehler S & B Computers Rockford Illinois, USA Phone: 815-398-7169 Fax: 815-398-7266 ====================================================== From majordomo-users-owner Mon Nov 11 06:47:04 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA20996 for majordomo-users-outgoing; Mon, 11 Nov 1996 06:36:44 -0800 (PST) Received: from antares.linf.unb.br ([164.41.12.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA20971 for ; Mon, 11 Nov 1996 06:36:21 -0800 (PST) Received: (from luthor@localhost) by antares.linf.unb.br (8.8.2/8.7.3) id MAA19636; Mon, 11 Nov 1996 12:29:30 -0200 (EDT) Date: Mon, 11 Nov 1996 12:29:11 -0200 (EDT) From: Lex Luthor X-Sender: luthor@antares To: majordomo-users@greatcircle.com Subject: How to make a "-l"list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, Are there any special care when making a list with it's name containing a - ? How are the aliases for such list, like majordomo-users ? Is it like this : majordomo-users-owner, majordomo-users-request ? Abracos, --- _________________________________ _________________________ / Alex Carlos Braga Antao \ /_ __ \ | UnB - Universidade de Brasilia | // ...on IRC | | | // ____ | | e-mail : luthor@linf.unb.br | // / _/________ | | http://www.linf.unb.br/~luthor | /____ /_/ / /) (_) / | \_________________________________/ \_______It's me !_________/ From majordomo-users-owner Mon Nov 11 07:17:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA21377 for majordomo-users-outgoing; Mon, 11 Nov 1996 06:48:31 -0800 (PST) Received: from cedar.strohwig.com ([206.150.138.253]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA21370 for ; Mon, 11 Nov 1996 06:48:21 -0800 (PST) Received: from cedar (cedar [206.150.138.253]) by cedar.strohwig.com (SMI-8.6/8.7) with SMTP id IAA05077 for ; Mon, 11 Nov 1996 08:47:46 -0600 Date: Mon, 11 Nov 1996 08:47:46 -0600 (CST) From: Richard McKay X-Sender: rmckay1@cedar To: majordomo-users@greatcircle.com Subject: No Response from Majordomo user. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm am new to this group and Majordomo in general. On that note, HI! I have a concern and a question to pose. I have Majordomo 1.94 running on a Solaris 2.5 Sparc box. The lists were working just fine for several days after the initial installation of Majordomo. So far so good. Yesterday, I had to take this same sparc down for maintenance (normal procedure). No errors were found while the server was booting. Here is the problem, Majordomo no longer processes any incoming mail at all. Everything destined for Majordomo is stored in /usr/mail/majordomo. This shouldn't happen. Nothing changed in /etc/mail/aliases or majordomo.cf. The user settings were never altered one bit. I even removed the majordomo-1.94 directory (and contents) from the /usr/local/bin area, recompiled wrapper and re-installed everything. Majordomo still does not respond to incoming mail any more. All my mailing utilities work (sendmail, uux, uucp etc..) as this email can atest to that. I'm stumped, can anyone help? Has anyone ever seen this before? I appologize if this question has been asked before, but like I stated before, I am but a newbie. ;) Let me know if you need more info. Thanks, Richard W. McKay rmckay1@strohwig.com From majordomo-users-owner Mon Nov 11 08:47:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA27093 for majordomo-users-outgoing; Mon, 11 Nov 1996 08:37:44 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA27005 for ; Mon, 11 Nov 1996 08:37:12 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id LAA17047; Mon, 11 Nov 1996 11:37:21 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id LAA07355; Mon, 11 Nov 1996 11:37:18 -0500 (EST) Message-Id: <199611111637.LAA07355@augusta.math.psu.edu> To: floyd@va.com.au cc: majordomo-users@GreatCircle.COM Subject: Re: solaris binary of majordomo In-reply-to: Your message of "Mon, 11 Nov 1996 22:40:52 +1030." <328717CC.255C@va.com.au> References: <328717CC.255C@va.com.au> 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: Mon, 11 Nov 1996 11:37:17 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <328717CC.255C@va.com.au>, "Florian Mueller" writes: >please! > >Can someone please send me the binary version of majordomo for solaris >2.5 (SunOS5.5), because I can't make Perl running! If you cant get perl working, then it's useless for you to get a binary of the wrapper. Majordomo isn't compiled, it's Perl. Only a teeny tiny portion is C. --Dave From majordomo-users-owner Mon Nov 11 09:01:53 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA26679 for majordomo-users-outgoing; Mon, 11 Nov 1996 08:32:13 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA26664 for ; Mon, 11 Nov 1996 08:31:59 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id LAA17006; Mon, 11 Nov 1996 11:32:09 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id LAA07315; Mon, 11 Nov 1996 11:32:04 -0500 (EST) Message-Id: <199611111632.LAA07315@augusta.math.psu.edu> To: Michael Brennen cc: majordomo-users@GreatCircle.COM Subject: Re: Digest List Name Privacy In-reply-to: Your message of "Sat, 09 Nov 1996 23:53:22 CST." References: 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: Mon, 11 Nov 1996 11:32:02 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , Michael Brenn en writes: > >I've run MJ for nearly two years; I'm currently on 1.94. Tonight I pulled >up my first digest. It is running fine so far, but I am not yet able to >remove the header information that gives the name of the outgoing list. I >want to remove the "for list-digest-outgoing" part below. I've >successfully done this for the normal lists. I could not find this in the >FAQ. It's there. See the Majordomo FAQ, question 3.6. http://www.math.psu.edu/barr/majordomo-faq.html --Dave From majordomo-users-owner Mon Nov 11 09:02:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA27228 for majordomo-users-outgoing; Mon, 11 Nov 1996 08:42:51 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA27221 for ; Mon, 11 Nov 1996 08:42:41 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA14060 for majordomo-users@greatcircle.com; Mon, 11 Nov 96 09:42:39 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA16105 for mcarthey@execpc.com; Mon, 11 Nov 96 09:42:38 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id KAA01739; Mon, 11 Nov 1996 10:42:37 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id KAA20697; Mon, 11 Nov 1996 10:42:36 -0600 From: Dave Wolfe Message-Id: <199611111642.KAA20697@miaow.risc.sps.mot.com> Subject: Re: No Response from Majordomo user. To: rmckay1@strohwig.com (Richard McKay) Date: Mon, 11 Nov 1996 10:42:35 -0600 (CST) Cc: majordomo-users@greatcircle.com, mcarthey@execpc.com In-Reply-To: from "Richard McKay" at Nov 9, 96 06:56:29 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Richard McKay writes: ] > > I have Majordomo 1.94 running on a Solaris 2.5 Sparc box. The > lists were working just fine for several days after the initial > installation of Majordomo. [...] Majordomo no longer processes any > incoming mail at all. Everything destined for Majordomo is stored > in /usr/mail/majordomo. This shouldn't happen. Nothing changed in > /etc/mail/aliases or majordomo.cf. Verify that your aliases are still intact and run newaliases to be sure that sendmail's alias database is in sync with the text file. -- Dave Wolfe From majordomo-users-owner Mon Nov 11 09:12:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA27620 for majordomo-users-outgoing; Mon, 11 Nov 1996 08:52:55 -0800 (PST) Received: from ns1.fni.com (ns1.fni.com [204.181.104.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA27584 for ; Mon, 11 Nov 1996 08:52:37 -0800 (PST) Received: from ns1.fni.com (ns1.fni.com [204.181.104.1]) by ns1.fni.com (8.7.6/8.7.3) with SMTP id KAA15899; Mon, 11 Nov 1996 10:52:49 -0600 Date: Mon, 11 Nov 1996 10:52:49 -0600 (CST) From: Michael Brennen To: Dave Barr cc: majordomo-users@GreatCircle.COM Subject: Re: Digest List Name Privacy In-Reply-To: <199611111632.LAA07315@augusta.math.psu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk It is there for normal lists that use resend; I know about this and use it. As I explained in my original post, it is not working for digests. >From what I've seen, digest does not use resend and does not work the same way when supplied with multiple mail addresses. I've not looked into the details of how digest works yet. I have long ago turned off EXPN/VRFY, so that is not an issue. The issue is the alias logging by sendmail v8 in the Received: headers. The digest aliases were listed in my original post, and they do have the multiple senders (trailing ,nobody) in place. I also made a copy of these aliases at the foot of this message. The list alias is still logged in the Received: headers on digests where it is not logged on normal lists run through resend. -- Michael On Mon, 11 Nov 1996, Dave Barr wrote: > >I've run MJ for nearly two years; I'm currently on 1.94. Tonight I pulled > >up my first digest. It is running fine so far, but I am not yet able to > >remove the header information that gives the name of the outgoing list. I > >want to remove the "for list-digest-outgoing" part below. I've > >successfully done this for the normal lists. I could not find this in the > >FAQ. > > It's there. See the Majordomo FAQ, question 3.6. > > http://www.math.psu.edu/barr/majordomo-faq.html DIGEST ALIASES: list-digestify: "|/usr/local/majordomo/wrapper digest -r -C -l list-digest list-digest-outgoing,nobody" list-digest: list owner-list-digest: owner-list,nobody list-digest-outgoing: :include:/usr/local/majordomo/lists/list-digest owner-list-digest-outgoing: owner-list,nobody list-digest-request: "|/usr/local/majordomo/wrapper majordomo -l list-digest" owner-list-digest-request: owner-list,nobody list-digest-approval: owner-list,nobody From majordomo-users-owner Mon Nov 11 09:17:20 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA28309 for majordomo-users-outgoing; Mon, 11 Nov 1996 09:08:34 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA28300 for ; Mon, 11 Nov 1996 09:08:23 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA17903 for majordomo-users@greatcircle.com; Mon, 11 Nov 96 10:08:33 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA17147 for majordomo-users@greatcircle.com; Mon, 11 Nov 96 10:08:28 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id LAA02131; Mon, 11 Nov 1996 11:08:27 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id LAA11090; Mon, 11 Nov 1996 11:08:25 -0600 From: Dave Wolfe Message-Id: <199611111708.LAA11090@miaow.risc.sps.mot.com> Subject: Re: Remote Protocol # 3 To: neilc@tradesrv.com.au Date: Mon, 11 Nov 1996 11:08:25 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <3286E40A.4F22@tradesrv.com.au> from "Neil Cotty" at Nov 11, 96 07:30:02 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Neil Cotty writes: ] > > I finally got the digest to go off (reached the size limit :) ) > however a couple of the people who are testing it with me were not > sent their mail and MJ popped this 'Remote Protocol Error' message. I > can send email to these addresses just fine. It only occurs when the > digest goes off. [...] > > ----- The following addresses had delivery problems ----- > djb9895@tam2000.tamu.edu (unrecoverable error) > (expanded from: :include:/usr/local/majordomo/lists/vizsla-digest) > ddnelson@ix.netcom.com (unrecoverable error) > (expanded from: :include:/usr/local/majordomo/lists/vizsla-digest) > > ----- Transcript of session follows ----- > ... while talking to tam2000.tamu.edu.: > >>> DATA > <<< 550 owner-vizsla-digest... User unknown > 554 djb9895@tam2000.tamu.edu... Remote protocol error > ... while talking to ixmail5.ix.netcom.com.: > >>> DATA > <<< 550 owner-vizsla-digest... User unknown > ... while talking to ixmail2.ix.netcom.com.: > >>> DATA > <<< 550 owner-vizsla-digest... User unknown > ... while talking to ixmail3.ix.netcom.com.: > >>> DATA > <<< 550 owner-vizsla-digest... User unknown > ... while talking to ixmail6.ix.netcom.com.: > >>> DATA > <<< 550 owner-vizsla-digest... User unknown > ... while talking to ixmail4.ix.netcom.com.: > >>> DATA > <<< 550 owner-vizsla-digest... User unknown > ... while talking to ixsrs5.ix.netcom.com.: > >>> DATA > <<< 550 owner-vizsla-digest... User unknown > ... while talking to ixsrs4.ix.netcom.com.: > >>> DATA > <<< 550 owner-vizsla-digest... User unknown > 554 ddnelson@ix.netcom.com... Remote protocol error > > ----- Message header follows ----- > > > Subject: > vizsla-digest V1 #1 > Date: > Fri, 8 Nov 1996 10:47:14 +1100 > From: > owner-vizsla-digest (vizsla-digest) > Reply-To: > vizsla It'd help to see the *actual* headers on an outgoing message that causes so much sendmail indigestion (rim shot :-), but if the Reply-To really is an unqualified name, that could be a problem. Perhaps you need to escape an '@' somewhere? -- Dave Wolfe From majordomo-users-owner Mon Nov 11 09:31:43 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA28820 for majordomo-users-outgoing; Mon, 11 Nov 1996 09:19:19 -0800 (PST) Received: from sun630mp.infomania.com (sun630mp.infomania.com [199.182.37.33]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA28813 for ; Mon, 11 Nov 1996 09:19:10 -0800 (PST) Received: (from tmornini@localhost) by sun630mp.infomania.com (8.7.5/8.7.3) id JAA28614; Mon, 11 Nov 1996 09:19:07 -0800 (PST) From: Tom Mornini Message-Id: <199611111719.JAA28614@sun630mp.infomania.com> Subject: Re: solaris binary of majordomo To: 328717CC.255C@va.com.au Date: Mon, 11 Nov 1996 09:19:07 -0800 (PST) Cc: majordomo-users@greatcircle.com In-Reply-To: <199611111637.LAA07355@augusta.math.psu.edu> from "Dave Barr" at Nov 11, 96 11:37:17 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > In message <328717CC.255C@va.com.au>, "Florian Mueller" writes: > >please! > > > >Can someone please send me the binary version of majordomo for solaris > >2.5 (SunOS5.5), because I can't make Perl running! I can send you the compiled binary tree for Perl, not majordomo. With that you should be able to get majordomo working... -- Tom Mornini -- InfoMania From majordomo-users-owner Mon Nov 11 09:47:35 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA29946 for majordomo-users-outgoing; Mon, 11 Nov 1996 09:42:45 -0800 (PST) Received: from antequera (antequera.antequera.com [167.114.36.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA29930 for ; Mon, 11 Nov 1996 09:42:31 -0800 (PST) From: javiers@antequera.antequera.com Received: by antequera (SMI-8.6/SMI-SVR4) id LAA09505; Mon, 11 Nov 1996 11:47:05 -0600 Date: Mon, 11 Nov 1996 11:47:05 -0600 Message-Id: <199611111747.LAA09505@antequera> To: majordomo-users@greatcircle.com Subject: Re: solaris binary of majordomo X-Sun-Charset: US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Florian! I have Solaris 2.4 for x86 and I don't have some problems with Perl 5.003 and Majordomo 1.93. If you have some problems with Perl maybe you have a wrong setup. Go to http://www.perl.com/perl/ for details. Javier NOTE: Majordomo is a script. You need Perl If you want to run Majordomo. From majordomo-users-owner Mon Nov 11 09:58:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA29421 for majordomo-users-outgoing; Mon, 11 Nov 1996 09:35:14 -0800 (PST) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA29398 for ; Mon, 11 Nov 1996 09:34:59 -0800 (PST) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Mon, 11 Nov 1996 10:35:00 -0700 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Mon, 11 Nov 1996 10:34:26 -0700 From: Brian Christensen To: majordomo-users@GreatCircle.com Subject: MAJORDOMO ABORT -Forwarded Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm new to Majordomo, and I've recently inherited the responsibility of maintaining a list server that our company has been using for a while. The person who previously maintained it didn't really know what they were doing when they set it up, so they have no clue what's causing the problem I'm experiencing. Whenever I send a 'which' command to the list server, it sends a reply with no lists shown, even though I'm subscribed to several lists. Also, since I'm the list owner, it sends me a MAJORDOMO ABORT message, which says: MAJORDOMO ABORT Failed to open temp file /export/home/majordomo/lists/9152986d.config.out, it exists I have tried renaming the file mentioned in the error message, but a new one gets created and the problem continues. Is anybody familiar with this problem? BTW, I'm on a Sun SPARCstation-20 running SunOS 5.5. Brian Christensen Novell Electronic Support Received: by mordor.npd.provo.novell.com (SMI-8.6/SMI-SVR4) id NAA27369; Sun, 10 Nov 1996 13:06:33 -0700 Message-Id: <199611102006.NAA27369@mordor.npd.provo.novell.com> Reply-To: Majordomo@mordor.npd.provo.novell.com Date: Sun, 10 Nov 1996 13:06:33 -0700 From: To: Majordomo-Owner@mordor.npd.provo.novell.com Subject: MAJORDOMO ABORT -- MAJORDOMO ABORT Failed to open temp file /export/home/majordomo/lists/9152986d.config.out, it exists From majordomo-users-owner Mon Nov 11 10:20:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA01637 for majordomo-users-outgoing; Mon, 11 Nov 1996 10:05:59 -0800 (PST) Received: from mozart.quinncom.net (quinncom.net [205.136.86.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA01627 for ; Mon, 11 Nov 1996 10:05:48 -0800 (PST) Received: from tpupke.awod.com (chs0129.awod.com [198.81.225.48]) by mozart.quinncom.net (8.7.6/8.6.9) with SMTP id NAA19674; Mon, 11 Nov 1996 13:04:24 -0500 Message-Id: <3.0.32.19961111130533.006a66b4@popserver.quinncom.net> X-Sender: tpupke@popserver.quinncom.net X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Mon, 11 Nov 1996 13:05:37 -0500 To: postmaster@cadence.com From: Trace Pupke Subject: Re: Majordomo ABORT - Can someone help? Cc: majordomo-users@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 09:41 AM 11/11/96 -0800, postmaster@cadence.com wrote: >chown is only allowed by the user or super-user. So what it means is that >majordomo is not running as the owner of the file, (or root) and so cannot >chown. > >Julian Thanks for replying, but what would be the way to correct this? The file, that can't be changed, is created automatically and is first owned by bin:bin when the problem below happens. Should I add majordom to the bin group? Change the ownership on the majordomo exec. or another file? Thanks for any help. >> Date: Sun, 10 Nov 1996 18:22:02 -0500 >> To: majordomo-users@GreatCircle.COM >> From: Trace Pupke >> Subject: Majordomo ABORT - Can someone help? >> >> I'm getting this error message when I try to unsubscribe. >> --- >> >> MAJORDOMO ABORT >> >> chown(54, 2, "/usr/local/majordomo/lists/test.new"): Operation not permitted >> >> --- >> I'm trying to set up majordomo on Linux 2.0.18 >> I have the user and group set as majordom:daemon (54:2) >> I added majordom to the group listing for daemon ~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ Trace Pupke <>< HTML Coordinator Quinn Communications tpupke@quinncom.net http://www.quinncom.net/ ~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ From majordomo-users-owner Mon Nov 11 11:36:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA05982 for majordomo-users-outgoing; Mon, 11 Nov 1996 11:19:05 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA05952 for ; Mon, 11 Nov 1996 11:18:47 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA06553 for majordomo-users@greatcircle.com; Mon, 11 Nov 96 12:18:57 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA21082 for majordomo-users@greatcircle.com; Mon, 11 Nov 96 12:18:56 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id NAA04347; Mon, 11 Nov 1996 13:18:55 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id NAA11257; Mon, 11 Nov 1996 13:18:54 -0600 From: Dave Wolfe Message-Id: <199611111918.NAA11257@miaow.risc.sps.mot.com> Subject: Re: How to make a "-l"list To: luthor@linf.unb.br (Lex Luthor) Date: Mon, 11 Nov 1996 13:18:53 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Lex Luthor" at Nov 11, 96 12:29:11 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Lex Luthor writes: ] > > Are there any special care when making a list with it's name containing > a - ? As long as your listname contains only (ASCII) alphanumerics, dash (-), and underscore (_), it's OK. -- Dave Wolfe From majordomo-users-owner Mon Nov 11 11:45:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA06255 for majordomo-users-outgoing; Mon, 11 Nov 1996 11:29:30 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA06236 for ; Mon, 11 Nov 1996 11:29:17 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA08135 for majordomo-users@GreatCircle.COM; Mon, 11 Nov 96 12:29:28 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA21487 for majordomo-users@GreatCircle.COM; Mon, 11 Nov 96 12:29:24 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id NAA04476; Mon, 11 Nov 1996 13:29:23 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id NAA12576; Mon, 11 Nov 1996 13:29:22 -0600 From: Dave Wolfe Message-Id: <199611111929.NAA12576@miaow.risc.sps.mot.com> Subject: Re: Majordomo ABORT - Can someone help? To: tpupke@quinncom.net (Trace Pupke) Date: Mon, 11 Nov 1996 13:29:22 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <3.0.32.19961111130533.006a66b4@popserver.quinncom.net> from "Trace Pupke" at Nov 11, 96 01:05:37 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Trace Pupke writes: ] > > At 09:41 AM 11/11/96 -0800, postmaster@cadence.com wrote: > >chown is only allowed by the user or super-user. So what it means is that > >majordomo is not running as the owner of the file, (or root) and so cannot > >chown. > > Thanks for replying, but what would be the way to correct this? Make sure wrapper is owned by root and has the setuid flag set, i.e.: -rwsr-xr-x 1 root daemon 24576 Feb 2 1995 wrapper ^ ^^^^ -- Dave Wolfe From majordomo-users-owner Mon Nov 11 12:36:50 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA09344 for majordomo-users-outgoing; Mon, 11 Nov 1996 12:30:39 -0800 (PST) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA09326 for ; Mon, 11 Nov 1996 12:30:28 -0800 (PST) Received: from gymir.ifi.uio.no (1368@gymir.ifi.uio.no [129.240.80.2]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Mon, 11 Nov 1996 21:30:37 +0100 Received: (from thomasg@localhost) by gymir.ifi.uio.no ; Mon, 11 Nov 1996 21:30:32 +0100 Date: Mon, 11 Nov 1996 21:30:25 +0100 From: Thomas Gramstad Reply-To: thomasg@ifi.uio.no To: majordomo-users@greatcircle.com Subject: Re: How to make a "-l"list In-Reply-To: Dave Wolfe 's message of Mon, 11 Nov 1996 13:18:53 -0600 (CST) References: <199611111918.NAA11257@miaow.risc.sps.mot.com> Message-ID: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >> Are there any special care when making a list with it's name >> containing a - ? > As long as your listname contains only (ASCII) alphanumerics, dash > (-), and underscore (_), it's OK. Note though, that you probably don't want - and _ in the same listname, as that is something that typically confuses people. -------------------------------------------------------------- Thomas Gramstad thomasg@ifi.uio.no From majordomo-users-owner Mon Nov 11 13:01:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA10829 for majordomo-users-outgoing; Mon, 11 Nov 1996 12:58:20 -0800 (PST) Received: from web.webcoach.com (web.webcoach.com [204.245.253.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id MAA10821 for ; Mon, 11 Nov 1996 12:58:11 -0800 (PST) Received: from mogens.mogens.com (mogens.webcoach.com [204.245.253.12]) by web.webcoach.com (8.8.2/8.7.3) with SMTP id NAA12439; Mon, 11 Nov 1996 13:00:36 -0800 (PST) Message-Id: <3.0.32.19961111125720.00c3ce14@mail.webcoach.com> X-Sender: mogens@mail.webcoach.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 11 Nov 1996 12:57:22 -0800 To: thomasg@ifi.uio.no, majordomo-users@GreatCircle.COM From: "Mogens L. Gilmour" Subject: Re: How to make a "-l"list Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I highly recommend you use "-list" not "-l". Because on a lot of screens the l (lowercase L) also looks exactly like 1 (numeric one) and subscribers get confused. Mogens Gilmour At 09:30 PM 11/11/96 +0100, Thomas Gramstad wrote: >>> Are there any special care when making a list with it's name >>> containing a - ? > >> As long as your listname contains only (ASCII) alphanumerics, dash >> (-), and underscore (_), it's OK. > >Note though, that you probably don't want - and _ in the same >listname, as that is something that typically confuses people. > >-------------------------------------------------------------- >Thomas Gramstad thomasg@ifi.uio.no > > _______________________________________________ WebCoach Internet Services Corporation Your Personal Internet Presence Provider Mogens L. Gilmour 503/655-6813 (talk) 503/655-6907 (fax) http://www.webcoach.com Info@WebCoach.com ========================================== From majordomo-users-owner Mon Nov 11 14:36:53 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA14913 for majordomo-users-outgoing; Mon, 11 Nov 1996 14:19:05 -0800 (PST) Received: from crl.dec.com (crl.dec.com [192.58.206.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id OAA14903 for ; Mon, 11 Nov 1996 14:18:53 -0800 (PST) Received: by crl.dec.com; id AA20808; Mon, 11 Nov 96 17:12:23 -0500 Received: (from uucp@localhost) by leggy.zk3.dec.com (8.6.9+sb+dnet/8.6.12+dnet) id RAA02173; Mon, 11 Nov 1996 17:12:03 -0500 Received: from localhost (localhost [127.0.0.1]) by Orb.Nashua.NH.US (8.6.12+sb+dnet/8.6.12+dnet) with SMTP id RAA18970; Mon, 11 Nov 1996 17:11:50 -0500 Message-Id: <199611112211.RAA18970@Orb.Nashua.NH.US> Subject: Re: Digest List Name Privacy In-Reply-To: Your message of "Mon, 11 Nov 1996 10:52:49 CST." References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Id: <18618.847750274.1@Orb.Nashua.NH.US> To: Michael Brennen Cc: majordomo-users@greatcircle.com Date: Mon, 11 Nov 1996 17:11:43 -0500 From: Spider Boardman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> On Mon, 11 Nov 1996 10:52:49 -0600 (CST), Michael Brennen said: Michael> The issue is the alias logging by sendmail v8 in the Michael> Received: headers. The digest aliases were listed in my Michael> original post, and they do have the multiple senders Michael> (trailing ,nobody) in place. No, you only think they do. See the following commentary on your aliases. Michael> I also made a copy of these aliases at the foot of this Michael> message. The list alias is still logged in the Michael> Received: headers on digests where it is not logged on Michael> normal lists run through resend. >From which I'd have to guess that the error I flagged below is one you're not making on your non-digest list. + DIGEST ALIASES: + list-digestify: "|/usr/local/majordomo/wrapper digest -r -C -l list-digest + list-digest-outgoing,nobody" + list-digest: list + owner-list-digest: owner-list,nobody + list-digest-outgoing: :include:/usr/local/majordomo/lists/list-digest So far, so good. + owner-list-digest-outgoing: owner-list,nobody WHOA THERE! Here, you've asked sendmail to do what it calls 'envelope splitting'. The previous envelope-from of 'owner-list-digest' isn't good enough any more. Now, the part of the outgoing message being delivered to 'nobody' stays the same, but the part being delivered to 'list-digest-outgoing' needs a new envelope-from, that of 'owner-list-digest-outgoing'. This, of course, is a single-recipient mailing (at this level), which causes the name of the list to appear in the 'Received:' header. In summary, once you've redirected bounces with an 'owner-list' alias, leave it alone. Don't add an alias for 'owner-list-outgoing' (or whatever corresponds to your real outgoing aliases)--it'll only cause you grief. -- Spider Boardman (at home) spider@Orb.Nashua.NH.US The management (my cats) made me say this. http://www.wp.com/spider/ PGP public key fingerprint = 96 72 D2 C6 E0 92 32 89 F6 B2 C2 A0 1C AB 1F DC From majordomo-users-owner Mon Nov 11 16:46:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA20124 for majordomo-users-outgoing; Mon, 11 Nov 1996 16:42:12 -0800 (PST) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id QAA20117 for ; Mon, 11 Nov 1996 16:42:04 -0800 (PST) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Mon, 11 Nov 1996 17:41:58 -0700 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Mon, 11 Nov 1996 17:38:09 -0700 From: Brian Christensen To: majordomo-users@GreatCircle.com Subject: Re: How to make a "-l"list -Reply Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is odd to me, because I set up several lists that all had problems, and I spent countless hours trying to get them to work, and finally I changed all the names to 8 characters or less and they all worked. Some of the names were cnenet-grpwise, cnenet-inet, cnenet-3x. I was quite disappointed that I had to use 8 characters or less to get them to work. >>> Dave Wolfe 11/11/96 12:18pm >>> [ Lex Luthor writes: ] > > Are there any special care when making a list with it's name containing > a - ? As long as your listname contains only (ASCII) alphanumerics, dash (-), and underscore (_), it's OK. -- Dave Wolfe From majordomo-users-owner Mon Nov 11 17:04:13 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA20547 for majordomo-users-outgoing; Mon, 11 Nov 1996 16:57:28 -0800 (PST) Received: from ns1.fni.com (ns1.fni.com [204.181.104.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id QAA20537 for ; Mon, 11 Nov 1996 16:57:20 -0800 (PST) Received: from ns1.fni.com (ns1.fni.com [204.181.104.1]) by ns1.fni.com (8.7.6/8.7.3) with SMTP id SAA20566 for ; Mon, 11 Nov 1996 18:57:39 -0600 Date: Mon, 11 Nov 1996 18:57:39 -0600 (CST) From: Michael Brennen To: majordomo-users@greatcircle.com Subject: Re: Digest List Name Privacy In-Reply-To: <199611112211.RAA18970@Orb.Nashua.NH.US> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Done. The digests are finally going out without the list name in the Received: header. I appreciate the responses, but none of them did the trick. What finally did fix it was to think a little more carefully about what I was doing (which usually helps :). Had I been generating the digests automatically it would have worked all along. I was generating the digests by the following (as if from cron): echo mkdigest list-digest passwd | mail majordomo@domain.com After poking around in the digest source, I starting using the following, which still did not work: echo mkdigest list-digest list-digest-alias passwd | mail majordomo@domain.com What fixed it was adding a ",nobody" after the list alias: echo mkdigest list-digest list-digest-alias,nobody passwd | mail majordomo@domain.com Bingo. -- Michael From majordomo-users-owner Mon Nov 11 17:17:09 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA20750 for majordomo-users-outgoing; Mon, 11 Nov 1996 17:02:38 -0800 (PST) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA20743 for ; Mon, 11 Nov 1996 17:02:31 -0800 (PST) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Mon, 11 Nov 1996 18:02:42 -0700 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Mon, 11 Nov 1996 18:02:08 -0700 From: Brian Christensen To: majordomo-users@GreatCircle.com Subject: Upgrade to PERL 5.003 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk ** Reply Requested When Convenient ** I've currently got PERL 5.0 installed on my system, which may explain why I'm having all the problems I am. I want to upgrade to version 5.003, but I have to be careful not to kill the whole service in the process. In the book Managing Internet Information Services it says that Majordomo can be temporarily disabled by using the command exit 75. Will I be okay if I execute this command, upgrade my version of PERL, then reenable Majordomo? Will it be able to process everything that gets queued up while I'm performing the upgrade? I would appreciate any advice or feedback that anybody has. Thanks, Brian Christensen Novell Electronic Support From majordomo-users-owner Mon Nov 11 17:23:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA20888 for majordomo-users-outgoing; Mon, 11 Nov 1996 17:07:40 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id RAA20881 for ; Mon, 11 Nov 1996 17:07:29 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id TAA11006; Mon, 11 Nov 1996 19:07:24 -0600 (CST) To: Brian Christensen Cc: majordomo-users@GreatCircle.COM Subject: Re: How to make a "-l"list -Reply References: From: Jason L Tibbitts III Date: 11 Nov 1996 19:07:23 -0600 In-Reply-To: Brian Christensen's message of Mon, 11 Nov 1996 17:38:09 -0700 Message-ID: Lines: 13 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "BC" == Brian Christensen writes: BC> [...] finally I changed all the names to 8 characters or less and they BC> all worked. Some of the names were cnenet-grpwise, cnenet-inet, BC> cnenet-3x. I was quite disappointed that I had to use 8 characters or BC> less to get them to work. Looking at the name of this mailing list, there is clear evidence that there is not generally an eight character limit to the name of the list. There may be limitations having to do with your particular mail software, but not in Majordomo itself. - J< From majordomo-users-owner Mon Nov 11 17:31:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA21413 for majordomo-users-outgoing; Mon, 11 Nov 1996 17:26:49 -0800 (PST) Received: from hermes.etheron.net (HERMES.ETHERON.NET [200.30.8.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA21387 for ; Mon, 11 Nov 1996 17:26:03 -0800 (PST) Received: from [200.30.8.67] by hermes.etheron.net (NTMail 3.02.07) with ESMTP id ua075394 for ; Mon, 11 Nov 1996 21:26:56 -0400 Message-ID: <32857C04.4D84@etheron.net> Date: Sun, 10 Nov 1996 02:53:56 -0400 From: "Juan J. Vieira" Organization: UCV X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Permision Denied Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I Have majordomo 1.94 and Linux when I Mail a message to majordomo I receive a message of error: "sh: /usr/local/majordomo/wrapper : Permision Denied "/usr/local/majordomo/wrapper" Unknow mailer error 126 I did configure the aliases file good but when I mail a message to a list, I get the message "User Unknow" Goodbye and Thank Jvieira@etheron.net From majordomo-users-owner Mon Nov 11 18:17:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA22596 for majordomo-users-outgoing; Mon, 11 Nov 1996 18:08:27 -0800 (PST) Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id SAA22581 for ; Mon, 11 Nov 1996 18:08:16 -0800 (PST) Received: (from smap@localhost) by mailgate.Cadence.COM (8.6.8/8.6.8) id SAA21230; Mon, 11 Nov 1996 18:08:04 -0800 Received: from jewels.cadence.com(158.140.32.165) by mailgate.cadence.com via smap (V1.0mjr) id sma847764384.021170; Mon Nov 11 18:06:24 1996 Received: (from julian@localhost) by jewels.Cadence.COM (8.6.8/8.6.8) id SAA27993; Mon, 11 Nov 1996 18:06:22 -0800 Date: Mon, 11 Nov 1996 18:06:22 -0800 From: Julian Gordon Message-Id: <199611120206.SAA27993@jewels.Cadence.COM> To: tpupke@quinncom.net Subject: Re: Majordomo ABORT - Can someone help? Cc: majordomo-users@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: /5QJXRQ3MbMq0vDhfzBN1A== Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Trace, Check your gid. I had the same problem. Julian > From majordomo-users-owner@GreatCircle.COM Sun Nov 10 22:34:36 1996 > Received-Date: Sun, 10 Nov 1996 22:34:35 -0800 > X-Sender: tpupke@popserver.quinncom.net > Date: Sun, 10 Nov 1996 18:22:02 -0500 > To: majordomo-users@GreatCircle.COM > From: Trace Pupke > Subject: Majordomo ABORT - Can someone help? > Mime-Version: 1.0 > > > I'm getting this error message when I try to unsubscribe. > > --- > > MAJORDOMO ABORT > > chown(54, 2, "/usr/local/majordomo/lists/test.new"): Operation not permitted > > --- > > I'm trying to set up majordomo on Linux 2.0.18 > I have the user and group set as majordom:daemon (54:2) > I added majordom to the group listing for daemon > > Does any have a little time and patience to help?? > > Thanks > > > ~~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ > Trace Pupke <>< HTML Coordinator Quinn Communications > tpupke@quinncom.net http://www.quinncom.net/ > ~~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ > > From majordomo-users-owner Mon Nov 11 21:03:36 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA29387 for majordomo-users-outgoing; Mon, 11 Nov 1996 20:52:59 -0800 (PST) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id UAA29378 for ; Mon, 11 Nov 1996 20:52:49 -0800 (PST) Received: from gymir.ifi.uio.no (1368@gymir.ifi.uio.no [129.240.80.2]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id ; Tue, 12 Nov 1996 05:52:59 +0100 Received: (from thomasg@localhost) by gymir.ifi.uio.no ; Tue, 12 Nov 1996 05:52:55 +0100 Date: Tue, 12 Nov 1996 05:52:48 +0100 From: Thomas Gramstad Reply-To: thomasg@ifi.uio.no To: majordomo-users@greatcircle.com Subject: Superlists (Re: Duplicate messages to a list) In-Reply-To: "Dennis Black" 's message of 21 Aug 1996 10:45:26 -0600 References: Message-ID: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Way back in august, Dennis Black wrote: > Name and create your > In the subscriber's file, enter the names of the three > or four other lists. > When you send out a message to , it gets distributed to > the subscribers - the other lists. And Majordomo will > do the duplicate-checking for you. Well, it doesn't work that way for me. I'm testing this now, with two listnames in the subscriber file. List 1 has A and B as subscribers, list 2 has A and C as subscribers. A got the message twice. I'm using Mj version 1.92. Each list has a subject_prefix in the .config-file, would that make any difference. So, can it work -- all subscribers getting the message only once, no matter how many lists they are subscribed to? > I've had this sort of thing set up for over a year. We have 5 > sections in our department. I created a list for each > section. Then I created a department-wide list. There are five > subscribers to the dept-wide list: the other 5. When someone sends > to the dept-wide, all five groups get it. With restrict_post = > group1: group2: group3: group4: group5, all subscribers can > cross-post to the other groups. -------------------------------------------------------------- Thomas Gramstad thomasg@ifi.uio.no From majordomo-users-owner Tue Nov 12 01:16:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id BAA07480 for majordomo-users-outgoing; Tue, 12 Nov 1996 01:12:35 -0800 (PST) Received: from ub4b.eunet.be (ub4b.eunet.be [192.92.130.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id BAA07473 for ; Tue, 12 Nov 1996 01:12:22 -0800 (PST) Received: from gate_e1.eurocontrol.be (gate.eurocontrol.be) by ub4b.eunet.be (ub4b_08) id AA04173; Tue, 12 Nov 1996 10:11:54 +0100 Received: (from uucp@localhost) by gate_e1.eurocontrol.be (8.7.1/8.7.1) id KAA25441 for ; Tue, 12 Nov 1996 10:13:19 +0100 (MET) Received: from biscuit.eurocontrol.be(193.221.170.179) by gate_e1.eurocontrol.be via smap (V1.3) id sma025431; Tue Nov 12 10:12:48 1996 Received: from ir6mws15.mas.eurocontrol.be by biscuit.eurocontrol.be with SMTP (1.37.109.18/16.2) id AA171559915; Tue, 12 Nov 1996 10:11:55 +0100 Received: from ir6mws38.mas.eurocontrol.be by ir6mws15.mas.eurocontrol.be (AIX 3.2/UCB 5.64/4.03) id AA26015; Tue, 12 Nov 1996 11:06:41 GMT Received: by masadm1.mas.eurocontrol.be (AIX 3.2/UCB 5.64/4.03) id AA15546; Tue, 12 Nov 1996 09:14:19 GMT From: "Alan Buck" Message-Id: <9611120914.ZM16056@ir6mws38.mas.eurocontrol.be> Date: Tue, 12 Nov 1996 09:14:18 +0000 X-Mailer: Z-Mail (3.2.1 10oct95) To: majordomo-users@GreatCircle.COM Subject: Upgrade of MD 1.93 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have recently installed MD1.93 against Perl 5.001m and it seems to be running OK, after some hiccups which were nearly all solved by subscribing to this list. Thanks for the support. May question is whether I should upgrade to 1.94 of Majordomo. I read that a version 2.0 is due out sometime, and if there is going to be disruption (or this sort of work to do), I'd rather have it once rather than twice. So when is v2.0 going to be available in a reliable form? Cheers, Alan -- ----------------------------------------------------------- Alan Buck: Eurocontrol, Maastricht UAC; Brussels HQ Telephone: work: +31 (0)43-3661461; +32 2 7293653 home: +31 (0)35 6024594 Fax: work +31 (0)43-3661300; +32 2 7299066 email: work Alan.Buck@eurocontrol.be home Alan.Buck@inter.nl.net ----------------------------------------------------------- From majordomo-users-owner Tue Nov 12 02:32:17 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id CAA11465 for majordomo-users-outgoing; Tue, 12 Nov 1996 02:20:51 -0800 (PST) Received: from java.aboard.co.uk (java.aboard.co.uk [194.73.51.130]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id CAA11434 for ; Tue, 12 Nov 1996 02:20:31 -0800 (PST) Received: (from nick@localhost) by java.aboard.co.uk (8.6.12/8.6.9) id KAA01639; Tue, 12 Nov 1996 10:20:42 GMT From: Nick Perry Message-Id: <199611121020.KAA01639@java.aboard.co.uk> Subject: Re: Superlists (Re: Duplicate messages to a list) To: thomasg@ifi.uio.no Date: Tue, 12 Nov 1996 10:20:42 +0000 (GMT) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Thomas Gramstad" at Nov 12, 96 05:52:48 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thomas Gramstad wrote: > > Name and create your > > In the subscriber's file, enter the names of the three > > or four other lists. > > When you send out a message to , it gets distributed to > > the subscribers - the other lists. And Majordomo will > > do the duplicate-checking for you. It is the mailer (eg sendmail) that removes duplicates - majordomo doesn't even 'send' the recipients to sendmail - sendmail picks them up from files :included: in the aliases file. After fully expanding aliases, sendmail will remove any *identical* recipients. > Well, it doesn't work that way for me. I'm testing this now, with > two listnames in the subscriber file. List 1 has A and B as > subscribers, list 2 has A and C as subscribers. A got the message > twice. If you sent the mail to (which has aliases 1 and 2 as its members), then providing the lines in each file corresponding to 'A' are IDENTICAL, then A shouldn't get the mail twice. NB, the following are *not* identical: Joe Bloggs Joe Bloggs > I'm using Mj version 1.92. > Each list has a subject_prefix in the .config-file, would that make > any difference. Ahah! Presumably the members of are the two aliases that each point to resend, eg: big-list: :include:/path/to/members/big-list list1: "|path/to/wrapper resend blah blah list1-outgoing" list1-outgoing: :include:/path/to/members/list1 list2: "|/path/to/wrapper resend blah blah list2-outgoing" list2-outgoing: :include:/path/to/members/list2 and /path/to/members/big-list contains: list1 list2 In this case, sending mail to big-list spawns two entirely unconnected majordomo processes each of which processed the mail in (probably) a diffeent way - there is no commmunication beween the majordomo processes or the resultant sendmail processes, so yes, A will get two messages. if, however, /path/to/members/big-list contains: list1-outgoing list2-outgoing then sendmail will remove duplicates after combining the files /path/to/members/list1 and /path/to/members/list2 - but majordomo was never involved, so you probably really want to do this: big-list: "|/path/to/wrapper resend blah blah big-list-outgoing" big-list-outgoing: :include:/path/to/members/big-list where /path/to/members/big-list contains the list?-outgoing aliases It means you have to set up a config file and aliases for a third list but should give you what you want. > So, can it work -- all subscribers getting the message only once, > no matter how many lists they are subscribed to? > Should do, Does my explaination make sense? Nick -- Nick Perry | AboarD Boats & Yachts Market Ltd Webmaster Manager | 7a Fernshaw Road, LONDON, SW10 0TB. UK Mobile: +44 (0)973 566204 | Tel: +44 (0)171 460 0030 Fax: 0040 | http://www.aboard.co.uk From majordomo-users-owner Tue Nov 12 03:01:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id CAA12750 for majordomo-users-outgoing; Tue, 12 Nov 1996 02:53:45 -0800 (PST) Received: from moss.verinet.com (moss.verinet.com [204.144.246.15]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id CAA12743 for ; Tue, 12 Nov 1996 02:53:35 -0800 (PST) Received: from bamboo.verinet.com (bamboo.verinet.com [204.144.246.3]) by moss.verinet.com (8.7.6/8.6.9) with ESMTP id DAA23448 for ; Tue, 12 Nov 1996 03:54:11 -0700 Received: from none (port16.verinet.com [204.144.246.65]) by bamboo.verinet.com (8.7.6/8.7.1) with SMTP id DAA31956 for ; Tue, 12 Nov 1996 03:52:14 -0700 Message-Id: <2.2.32.19961112105309.00735cc8@verinet.com> X-Sender: sjepsen@verinet.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 12 Nov 1996 03:53:09 -0700 To: majordomo-users@greatcircle.com From: Sandi-J Subject: Index Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have already added the following command in my digest config file: message_fronter << END - In this issue: - - _SUBJECTS_ END What I would like to know is if there is a way to add the name of the sender as well as the subject. I don't think my provider has upgraded to the 1.94 version yet so I still need work with the previous version of majordomo. Please answer me privately. Due to email overload I am no longer on this mailing list. Thanks in advance for any help Sandi From majordomo-users-owner Tue Nov 12 06:46:53 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA20596 for majordomo-users-outgoing; Tue, 12 Nov 1996 06:33:21 -0800 (PST) Received: from bigdog.fred.net (fred.net [204.215.84.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA20576 for ; Tue, 12 Nov 1996 06:33:06 -0800 (PST) Received: from localhost (mjj@localhost) by bigdog.fred.net (8.7.5/8.6.12) with SMTP id JAA20364 for ; Tue, 12 Nov 1996 09:32:35 -0500 (EST) Date: Tue, 12 Nov 1996 09:32:34 -0500 (EST) From: MJ Fan Club To: majordomo-users@greatcircle.com Subject: Problem with multiple mailings on moderated list In-Reply-To: <9611120914.ZM16056@ir6mws38.mas.eurocontrol.be> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have recently installed MD 1.93, and everything appeared smooth until a list was created with about 700 recipients. The list is moderated, and the listowner manually forwards each message back with the "Approved: " in the second line of the body. However, over the course of 48 hours, the listowner keeps receiving multiple copies of the messages (about 5) sent by listowner. The actual other members of the list have not reported this problem (yet). In addition, while testing out this same list and sending a message out, it came back to the listowner twice with "Precendence: bulk" embedded right in the middle of the body of the message. Any ideas on how to correct these problems (I have a feeling they may possibly be related?). Thanks, --Brian mjj@fred.net From majordomo-users-owner Tue Nov 12 07:17:02 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA22548 for majordomo-users-outgoing; Tue, 12 Nov 1996 07:12:44 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA22476 for ; Tue, 12 Nov 1996 07:12:16 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA14832 for majordomo-users@greatcircle.com; Tue, 12 Nov 96 08:12:24 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA12692 for majordomo-users@greatcircle.com; Tue, 12 Nov 96 08:12:23 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA16114; Tue, 12 Nov 1996 09:12:22 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA14833; Tue, 12 Nov 1996 09:12:20 -0600 From: Dave Wolfe Message-Id: <199611121512.JAA14833@miaow.risc.sps.mot.com> Subject: Re: Permision Denied To: jvieira@etheron.net (Juan J. Vieira) Date: Tue, 12 Nov 1996 09:12:20 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <32857C04.4D84@etheron.net> from "Juan J. Vieira" at Nov 10, 96 02:53:56 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Juan J. Vieira writes: ] > > I Have majordomo 1.94 and Linux when I Mail a message to majordomo > I receive a message of error: > > "sh: /usr/local/majordomo/wrapper : Permision Denied You probably need to open permissions on the Mj home directory. Try: chmod o+x /usr/local/majordomo Depending on the user/group ownership of wrapper and the uid/gid your MTA (e.g. sendmail) runs as, you might also need to: chmod o+x /usr/local/majordomo/wrapper > I did configure the aliases file good but when I mail a message > to a list, I get the message "User Unknow" Did you run newaliases (or sendmail -bi) to rebuild the database files? -- Dave Wolfe From majordomo-users-owner Tue Nov 12 08:02:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA24277 for majordomo-users-outgoing; Tue, 12 Nov 1996 07:41:43 -0800 (PST) Received: from senie.com (senie.com [204.69.207.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA24247 for ; Tue, 12 Nov 1996 07:41:16 -0800 (PST) Received: (qmail-queue invoked from smtpd); 12 Nov 1996 15:41:28 -0000 Received: from localhost (dts@127.0.0.1) by localhost with SMTP; 12 Nov 1996 15:41:28 -0000 Date: Tue, 12 Nov 1996 10:41:28 -0500 (EST) From: Daniel Senie To: majordomo-users@greatcircle.com Subject: editing qmail's queues Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is quasi-related to majordomo. I've had several users on my list that I've been stripping off due to problems at their sites. I think at present I have some 40 messages still queued and being retried for some of those sites. I'd like to remove these messages from qmail's queues, but am unsure if I can do this without getting qmail very upset. Is there a proper utility or procedure for convincing qmail to give up on a piece of mail? Dan --------------------------------------------------------------- Daniel Senie Internet: dan@senie.com, Daniel Senie Consulting n1jeb@senie.com http://www.senie.com Packet Radio: N1JEB@KA1SRD.MA If we suffer tamely a lawless attack upon our liberty, we encourage it, and involve others in our doom. -- Samuel Adams From majordomo-users-owner Tue Nov 12 08:08:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA24265 for majordomo-users-outgoing; Tue, 12 Nov 1996 07:41:30 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA24228 for ; Tue, 12 Nov 1996 07:41:03 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id KAA04610; Tue, 12 Nov 1996 10:41:15 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id KAA13271; Tue, 12 Nov 1996 10:41:11 -0500 (EST) Message-Id: <199611121541.KAA13271@augusta.math.psu.edu> To: "Alan Buck" cc: majordomo-users@GreatCircle.COM Subject: Re: Upgrade of MD 1.93 In-reply-to: Your message of "Tue, 12 Nov 1996 09:14:18 GMT." <9611120914.ZM16056@ir6mws38.mas.eurocontrol.be> References: <9611120914.ZM16056@ir6mws38.mas.eurocontrol.be> 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 Nov 1996 10:41:10 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <9611120914.ZM16056@ir6mws38.mas.eurocontrol.be>, "Alan Buck" writes : >May question is whether I should upgrade to 1.94 of Majordomo. I read that a >version 2.0 is due out sometime, and if there is going to be disruption (or >this sort of work to do), I'd rather have it once rather than twice. So when i >s >v2.0 going to be available in a reliable form? Upgrade to 1.94. 2.0 will probably be a long time. --Dave From majordomo-users-owner Tue Nov 12 08:13:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA23699 for majordomo-users-outgoing; Tue, 12 Nov 1996 07:32:41 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA23681 for ; Tue, 12 Nov 1996 07:32:24 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA17973 for majordomo-users@GreatCircle.com; Tue, 12 Nov 96 08:32:36 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA13609 for majordomo-users@GreatCircle.com; Tue, 12 Nov 96 08:32:35 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA16422; Tue, 12 Nov 1996 09:32:33 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA22321; Tue, 12 Nov 1996 09:32:32 -0600 From: Dave Wolfe Message-Id: <199611121532.JAA22321@miaow.risc.sps.mot.com> Subject: Re: How to make a "-l"list -Reply To: BCCHRISTENSEN@novell.com (Brian Christensen) Date: Tue, 12 Nov 1996 09:32:31 -0600 (CST) Cc: majordomo-users@GreatCircle.com In-Reply-To: from "Brian Christensen" at Nov 11, 96 05:38:09 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Brian Christensen writes: ] > > This is odd to me, because I set up several lists that all had problems, and > I spent countless hours trying to get them to work, and finally I changed all > the names to 8 characters or less and they all worked. Some of the > names were cnenet-grpwise, cnenet-inet, cnenet-3x. I was quite > disappointed that I had to use 8 characters or less to get them to work. > > >>> Dave Wolfe 11/11/96 12:18pm >>> > [ Lex Luthor writes: ] > > > > Are there any special care when making a list with it's name containing > > a - ? > > As long as your listname contains only (ASCII) alphanumerics, dash (-), > and underscore (_), it's OK. That doesn't make sense unless you also had to restrict things like owner-listname and listname-outgoing to 8 characters. In any case it would seem to be an MTA problem and not the fault of Mj. My answer to the original question applies only to Mj. -- Dave Wolfe From majordomo-users-owner Tue Nov 12 08:17:20 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA26444 for majordomo-users-outgoing; Tue, 12 Nov 1996 08:08:37 -0800 (PST) Received: from balltown.cma.com (balltown.cma.com [149.19.1.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA26435 for ; Tue, 12 Nov 1996 08:08:27 -0800 (PST) Received: from skipper (welty@skipper.balltown.cma.com [149.19.1.19]) by balltown.cma.com (8.7.1/CMA02) with SMTP id LAA24300; Tue, 12 Nov 1996 11:07:37 -0500 (EST) Message-ID: <3288A0C4.59E2B600@balltown.cma.com> Date: Tue, 12 Nov 1996 11:07:32 -0500 From: richard welty Organization: New York State Institute for Sebastian Cabot Studies X-Mailer: Mozilla 3.0 (X11; I; SunOS 4.1.3_U1 sun4m) MIME-Version: 1.0 To: Alan Buck CC: majordomo-users@GreatCircle.COM Subject: Re: Upgrade of MD 1.93 References: <9611120914.ZM16056@ir6mws38.mas.eurocontrol.be> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk *My question is whether I should upgrade to 1.94 of Majordomo. I read *that a version 2.0 is due out sometime, and if there is going to be *disruption (or this sort of work to do) upgrading from 1.92 to 1.94 went very easily here; i see no reason why you should skip the 1.93->1.94 upgrade while waiting for 2.0 richard -- Not Insane! in '96 George Leroy Tirebiter for President One Organism: One Vote From majordomo-users-owner Tue Nov 12 08:19:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA24417 for majordomo-users-outgoing; Tue, 12 Nov 1996 07:43:13 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA24359 for ; Tue, 12 Nov 1996 07:42:46 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AB19639 for majordomo-users@GreatCircle.com; Tue, 12 Nov 96 08:42:53 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA14015 for majordomo-users@GreatCircle.com; Tue, 12 Nov 96 08:42:46 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA16638; Tue, 12 Nov 1996 09:42:45 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA20560; Tue, 12 Nov 1996 09:42:44 -0600 From: Dave Wolfe Message-Id: <199611121542.JAA20560@miaow.risc.sps.mot.com> Subject: Re: Upgrade to PERL 5.003 To: BCCHRISTENSEN@novell.com (Brian Christensen) Date: Tue, 12 Nov 1996 09:42:44 -0600 (CST) Cc: majordomo-users@GreatCircle.com In-Reply-To: from "Brian Christensen" at Nov 11, 96 06:02:08 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Brian Christensen writes: ] > > I've currently got PERL 5.0 installed on my system, which may explain why > I'm having all the problems I am. I want to upgrade to version 5.003, but I > have to be careful not to kill the whole service in the process. In the book > Managing Internet Information Services it says that Majordomo can be > temporarily disabled by using the command exit 75. Will I be okay if I > execute this command, upgrade my version of PERL, then reenable > Majordomo? Will it be able to process everything that gets queued up > while I'm performing the upgrade? Does it mention *where* the "exit 75" is to be used? I suspect they mean as the first line of your majordomo.cf file (it returns a "temporary failure" exit code to sendmail, causing incoming mail to be queued for later processing), *not* from a shell command line. As long as you don't have Mj disabled for longer than sendmail's time limit (usually 5 days, but see your sendmail.cf), it should all get processed when sendmail is able to successfully deliver to Mj (i.e. the next queue scan after you remove the 'exit 75'). If you install Perl in a different place than where it currently is, remember to change the #! path on all the appropriate Mj program files. -- Dave Wolfe From majordomo-users-owner Tue Nov 12 08:37:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA28206 for majordomo-users-outgoing; Tue, 12 Nov 1996 08:29:08 -0800 (PST) Received: from sun630mp.infomania.com (sun630mp.infomania.com [199.182.37.33]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA28184; Tue, 12 Nov 1996 08:28:57 -0800 (PST) Received: (from tmornini@localhost) by sun630mp.infomania.com (8.7.5/8.7.3) id IAA09845; Tue, 12 Nov 1996 08:29:00 -0800 (PST) From: Tom Mornini Message-Id: <199611121629.IAA09845@sun630mp.infomania.com> Subject: How will 2.0 features be determined? To: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Date: Tue, 12 Nov 1996 08:29:00 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm just curious if there is a list of intended features, etc. In my experience, if you ask the customers you'll get far better ideas than you might ever imagine. -- Tom Mornini -- InfoMania From majordomo-users-owner Tue Nov 12 08:37:19 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA27457 for majordomo-users-outgoing; Tue, 12 Nov 1996 08:19:02 -0800 (PST) Received: from clarinet.synapse.net (clarinet.synapse.net [199.84.54.19]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA27420 for ; Tue, 12 Nov 1996 08:18:36 -0800 (PST) Received: from piano.synapse.net (piano.synapse.net [199.84.54.20]) by clarinet.synapse.net (8.8.2/8.8.2) with ESMTP id LAA21975; Tue, 12 Nov 1996 11:18:45 -0500 (EST) Received: from piano.synapse.net (localhost [127.0.0.1]) by piano.synapse.net (8.8.2/8.8.2) with SMTP id LAA19933; Tue, 12 Nov 1996 11:18:44 -0500 (EST) Date: Tue, 12 Nov 1996 11:18:44 -0500 (EST) From: Evan Champion To: Dave Wolfe cc: Brian Christensen , majordomo-users@GreatCircle.COM Subject: Re: How to make a "-l"list -Reply In-Reply-To: <199611121532.JAA22321@miaow.risc.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, 12 Nov 1996, Dave Wolfe wrote: > That doesn't make sense unless you also had to restrict things like > owner-listname and listname-outgoing to 8 characters. In any case it > would seem to be an MTA problem and not the fault of Mj. My answer to > the original question applies only to Mj. It is most certainly an MTA issue. I have lists whose names are 20+ characters long with all kinds of dashes etc. and they run just fine. I think he should upgrade to sendmail 8.8.2; I suspect that all his prolems will disappear with 8.8.2 installed. Evan -- Evan Champion * Director, Network Operations mailto:evanc@synapse.net * Directeur, Exploitation du reseau http://www.synapse.net/ * Synapse Internet From majordomo-users-owner Tue Nov 12 08:37:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA28018 for majordomo-users-outgoing; Tue, 12 Nov 1996 08:26:56 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA27995 for ; Tue, 12 Nov 1996 08:26:45 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA26564 for majordomo-users@GreatCircle.COM; Tue, 12 Nov 96 09:26:50 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA14685 for majordomo-users@GreatCircle.COM; Tue, 12 Nov 96 08:56:20 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA16756; Tue, 12 Nov 1996 09:56:19 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA20594; Tue, 12 Nov 1996 09:56:18 -0600 From: Dave Wolfe Message-Id: <199611121556.JAA20594@miaow.risc.sps.mot.com> Subject: Re: Upgrade of MD 1.93 To: alan.buck@eurocontrol.be (Alan Buck) Date: Tue, 12 Nov 1996 09:56:18 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <9611120914.ZM16056@ir6mws38.mas.eurocontrol.be> from "Alan Buck" at Nov 12, 96 09:14:18 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Alan Buck writes: ] > > May question is whether I should upgrade to 1.94 of Majordomo. I read > that a version 2.0 is due out sometime, and if there is going to be > disruption (or this sort of work to do), I'd rather have it once > rather than twice. So when is v2.0 going to be available in a reliable > form? "It'll happen when it happens." But it'll be awhile. There will certainly be at least a 1.94 patch release and a 1.95 release (or 1.95 and 1.96) before then. The patch release should happen Real Soon Now, so you might want to wait for that. The goal is that subsequent releases won't be nearly the pain that 1.93 was. Most all the problems in 1.94 are pretty minor, but Murphy always has the last word. -- Dave Wolfe From majordomo-users-owner Tue Nov 12 08:37:50 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA25594 for majordomo-users-outgoing; Tue, 12 Nov 1996 07:58:52 -0800 (PST) Received: from bolis.com ([204.153.195.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA25585 for ; Tue, 12 Nov 1996 07:58:36 -0800 (PST) Received: Received: from hock.bolis.com (root@hock.bolis.com [199.165.142.10]) by bolis.com (8.7.3/8.7.3) with SMTP id HAA26038 ; Tue, 12 Nov 1996 07:58:39 -0800 Received: from amillar.bolis.com by hock.bolis.com with smtp (Smail3.1.28.1 #6) id m0vNLEU-000G0KC; Tue, 12 Nov 96 07:58 PST Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: majordomo-users@GreatCircle.COM Date: Tue, 12 Nov 1996 08:00:41 -800 Subject: Re: How to make a "-l"list -Reply X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On 11 Nov 96 at 19:07, Jason L Tibbitts III wrote: > >>>>> "BC" == Brian Christensen writes: > BC> [...] finally I changed all the names to 8 characters or less and they > BC> all worked. Some of the names were cnenet-grpwise, cnenet-inet, > BC> cnenet-3x. I was quite disappointed that I had to use 8 characters or > BC> less to get them to work. > > Looking at the name of this mailing list, there is clear evidence that > there is not generally an eight character limit to the name of the list. > There may be limitations having to do with your particular mail software, > but not in Majordomo itself. Without knowing what specific problems he faced, it could have also been an old filesystem that limited the file name length. I know the Minix file system limited names to about 14 or 16 chars; presumably there are other systems still floating around like this too. When you tack on extensions like .config and .config.new, you've got a basic limit on list name length. - Alan ---- Alan Millar amillar@bolis.com Owner, System Admin http://www.bolis.com Ask me about Internet mailing list services at Bolis.com 'And did you live?' 'Did I? You should see me now!' From majordomo-users-owner Tue Nov 12 09:02:09 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA29627 for majordomo-users-outgoing; Tue, 12 Nov 1996 08:55:19 -0800 (PST) Received: from beta.loyno.edu (beta.loyno.edu [141.164.1.44]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA29584 for ; Tue, 12 Nov 1996 08:54:47 -0800 (PST) Received: by beta.loyno.edu; (5.65/1.1.8.2/31Oct96-0621AM) id AA23044; Tue, 12 Nov 1996 10:59:25 -0600 Date: Tue, 12 Nov 1996 10:59:23 -0600 (CST) From: Kevin Lewandowski To: majordomo-users@greatcircle.com Subject: more permissions Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I get this error when I try to post to my list. All files and directories are rwx for owner and group (majordom). Can anyone help? Thanks. -- open of temp file /usr/local/majordomo/lists/shlock.15842 failed Permission denied ABORT open of temp file /usr/local/majordomo/lists/shlock.15842 failed Permission denied at /usr/local/majordomo/majordomo-1.93/majordomo.pl line 209. From majordomo-users-owner Tue Nov 12 09:47:25 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA01888 for majordomo-users-outgoing; Tue, 12 Nov 1996 09:34:30 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA01820 for ; Tue, 12 Nov 1996 09:34:01 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id MAA06835; Tue, 12 Nov 1996 12:33:56 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id MAA14271; Tue, 12 Nov 1996 12:33:53 -0500 (EST) Message-Id: <199611121733.MAA14271@augusta.math.psu.edu> To: Kevin Lewandowski cc: majordomo-users@GreatCircle.COM Subject: Re: more permissions In-reply-to: Your message of "Tue, 12 Nov 1996 10:59:23 CST." References: 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 Nov 1996 12:33:51 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , Kevin Lew andowski writes: >I get this error when I try to post to my list. All files and >directories are rwx for owner and group (majordom). Can anyone help? >Thanks. 1) Consider upgrading to 1.94. 2) Read question 2.1 of the current Majordomo FAQ http://www.math.psu.edu/barr/majordomo-faq.html >-- >open of temp file /usr/local/majordomo/lists/shlock.15842 failed > Permission denied >ABORT open of temp file /usr/local/majordomo/lists/shlock.15842 failed > Permission denied at /usr/local/majordomo/majordomo-1.93/majordomo.pl line 20 >9. From majordomo-users-owner Tue Nov 12 10:17:04 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA04667 for majordomo-users-outgoing; Tue, 12 Nov 1996 10:04:04 -0800 (PST) Received: from bigdog.fred.net (fred.net [204.215.84.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA04590 for ; Tue, 12 Nov 1996 10:03:34 -0800 (PST) Received: from localhost (mjj@localhost) by bigdog.fred.net (8.7.5/8.6.12) with SMTP id NAA22154 for ; Tue, 12 Nov 1996 13:02:44 -0500 (EST) Date: Tue, 12 Nov 1996 13:02:44 -0500 (EST) From: MJ Fan Club To: majordomo-users@greatcircle.com Subject: Re: Problem with multiple mailings on moderated list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk From: Dave Wolfe Reply-To: Dave Wolfe To: MJ Fan Club [ MJ Fan Club writes: ] > > Thank you for your quick response--I can see that I didn't give enough > information. The moderator uses Pine to receive the mail that gets bounced > to him by majordomo. Majordomo bounces two pieces of mail for each message > sent to the mailing list--one with the bounce header, and the next > message is an exact replica of the message that was sent to the list. Aha! The moderator's mail system or Pine is broken. That's actually just one message, but someone is ignoring the Content-Length header and interpreting the embedded (original) headers in the body as the start of a new message. He needs to see if this is a Pine configuration problem (I believe it is) or if his mail system needs to be escaping embedded headers instead of inserting Content-Length headers. Or if Pine uses POP to retrieve messages, maybe it's a POP server configuration problem. In any case, the two pieces of mail should be just one which contains the original headers and original message as a single bounced message. Then he could pipe bounced messages to approve and eliminate a lot of hassles. Or at least edit the Approved header onto the front of the embedded headers. > The moderator then forwards the mail (F command within Pine) back to > the list, putting the 'Approved: ' at the top of the body of the > message. The message he sends back contains the Date, From, To, and > Subject header that the 'F'orward command automatically puts there. I.e. he loses all the original headers unless he copies them to the approved message. -- Dave Wolfe From majordomo-users-owner Tue Nov 12 10:47:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA07323 for majordomo-users-outgoing; Tue, 12 Nov 1996 10:38:21 -0800 (PST) Received: from hplms26.hpl.hp.com (hplms26.hpl.hp.com [15.255.168.31]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA07314 for ; Tue, 12 Nov 1996 10:38:04 -0800 (PST) Received: from hplms2.hpl.hp.com by hplms26.hpl.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3+HPL1.1S) id AA259173894; Tue, 12 Nov 1996 10:38:15 -0800 Received: from hplmds (hplmds.hpl.hp.com) by hplms2.hpl.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3+HPL1.1I) id AA232733900; Tue, 12 Nov 1996 10:38:20 -0800 Message-Id: <3288C420.3035@hpl.hp.com> Date: Tue, 12 Nov 1996 10:38:24 -0800 From: Michael Stokes Organization: Hewlett Packard Labs X-Mailer: Mozilla 3.0 (X11; I; HP-UX B.10.20 9000/735) Mime-Version: 1.0 To: majordomo-users@greatcircle.com Subject: HPUX 10.20 and MD1.94 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I just upgraded from HPUX 9.07 to HPUX 10.20 and MD1.93 stopped working. I decided to go ahead and upgread to MD1.94 and hope my problems went away. No such luck. When I try to echo 'lists' | mail majordomo I recieved the following error via email ---- The following addresses have delivery notifications ---- "|/usr/local/majordomo/wrapper majordomo" (unrecoverable error) (expanded from majordomo) ---- Transcript of sesssion follows ---- sh: /usr/local/majordomo/wrapper: not found, 554 "|/usr/local/majordomo/wrapper majordomo"...unknown mailer error 126 I have verified that /usr/local/majordomo/wrapper exists and has executable permissions for all users. PLEASE help...any ideas ? Lost in a new OS... -- Michael ________________________________________________________________________ Michael Stokes stokes@hpl.hp.com Hewlett-Packard Laboratories Phone : (415) 857-3908 1501 Page Mill Rd, MS: 4U5 Fax : (415) 857-5272 Palo Alto, CA 94304 Hewlett-Packard Company From majordomo-users-owner Tue Nov 12 11:17:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA10205 for majordomo-users-outgoing; Tue, 12 Nov 1996 11:04:22 -0800 (PST) Received: from i2bs.com (i2bs.com [205.242.194.21]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id LAA10167 for ; Tue, 12 Nov 1996 11:04:04 -0800 (PST) Received: from skb.sbcomp.net (bernoulli-01.inpi.com [207.152.80.101]) by i2bs.com (8.7.5/8.7.3) with SMTP id NAA20710; Tue, 12 Nov 1996 13:00:26 -0600 (CST) Message-Id: <3.0.32.19961112125941.006d6914@205.242.194.21> X-Sender: skb@205.242.194.21 X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 12 Nov 1996 13:01:25 -0600 To: Kevin Lewandowski From: "Steven K. Buehler" Subject: Re: more permissions Cc: majordomo-users@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 10:59 AM 11/12/96 -0600, you wrote: >I get this error when I try to post to my list. All files and >directories are rwx for owner and group (majordom). Can anyone help? >Thanks. >open of temp file /usr/local/majordomo/lists/shlock.15842 failed > Permission denied >ABORT open of temp file /usr/local/majordomo/lists/shlock.15842 failed > Permission denied at /usr/local/majordomo/majordomo-1.93/majordomo.pl line 209. Don't know if this will help or not in your case, but I just had some failures like that and what I found it to be was that another person that has superuser access was trying to make the server more secure and took read access away for "o" on root / and /usr and /home. I set them back to the way they were and off they flew. It was messing with my digests when he did that. ====================================================== Steven K. Buehler S & B Computers Rockford Illinois, USA Phone: 815-398-7169 Fax: 815-398-7266 ====================================================== From majordomo-users-owner Tue Nov 12 12:01:57 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA13871 for majordomo-users-outgoing; Tue, 12 Nov 1996 11:53:15 -0800 (PST) Received: from senie.com (senie.com [204.69.207.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA13845 for ; Tue, 12 Nov 1996 11:53:03 -0800 (PST) Received: (qmail-queue invoked from smtpd); 12 Nov 1996 19:46:28 -0000 Received: from localhost (dts@127.0.0.1) by localhost with SMTP; 12 Nov 1996 19:46:28 -0000 Date: Tue, 12 Nov 1996 14:46:27 -0500 (EST) From: Daniel Senie To: majordomo-users@greatcircle.com Subject: restricting 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 limit the ability to send messages to a list to those people already s*bscribed to the list. I thought there was an item in the config file to do this, but now do not seem to find it. Dan --------------------------------------------------------------- Daniel Senie Internet: dan@senie.com, Daniel Senie Consulting n1jeb@senie.com http://www.senie.com Packet Radio: N1JEB@KA1SRD.MA If we suffer tamely a lawless attack upon our liberty, we encourage it, and involve others in our doom. -- Samuel Adams From majordomo-users-owner Tue Nov 12 12:08:28 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA13694 for majordomo-users-outgoing; Tue, 12 Nov 1996 11:50:33 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA13678 for ; Tue, 12 Nov 1996 11:50:18 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA27655 for majordomo-users@greatcircle.com; Tue, 12 Nov 96 12:50:25 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA23523 for majordomo-users@greatcircle.com; Tue, 12 Nov 96 12:50:20 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id NAA19911; Tue, 12 Nov 1996 13:50:19 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id NAA14147; Tue, 12 Nov 1996 13:22:17 -0600 From: Dave Wolfe Message-Id: <199611121922.NAA14147@miaow.risc.sps.mot.com> Subject: Re: HPUX 10.20 and MD1.94 To: stokes@hplms2.hpl.hp.com (Michael Stokes) Date: Tue, 12 Nov 1996 13:22:17 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <3288C420.3035@hpl.hp.com> from "Michael Stokes" at Nov 12, 96 10:38:24 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Michael Stokes writes: ] > > ---- Transcript of sesssion follows ---- > sh: /usr/local/majordomo/wrapper: not found, [...] > I have verified that /usr/local/majordomo/wrapper exists and has > executable permissions for all users. Could it be that /usr/local/majordomo doesn't have search permissions for all users? -- Dave Wolfe From majordomo-users-owner Tue Nov 12 13:02:38 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA18797 for majordomo-users-outgoing; Tue, 12 Nov 1996 12:50:28 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA18767 for ; Tue, 12 Nov 1996 12:50:13 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA07077 for majordomo-users@greatcircle.com; Tue, 12 Nov 96 13:50:24 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA25794 for majordomo-users@greatcircle.com; Tue, 12 Nov 96 13:50:21 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id OAA20871; Tue, 12 Nov 1996 14:50:20 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id OAA13273; Tue, 12 Nov 1996 14:33:44 -0600 From: Dave Wolfe Message-Id: <199611122033.OAA13273@miaow.risc.sps.mot.com> Subject: Re: restricting messages To: dts@senie.com (Daniel Senie) Date: Tue, 12 Nov 1996 14:33:44 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Daniel Senie" at Nov 12, 96 02:46:27 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Daniel Senie writes: ] > > I'd like to limit the ability to send messages to a list to those people > already s*bscribed to the list. I thought there was an item in the config > file to do this, but now do not seem to find it. Look for restrict_post. -- Dave Wolfe From majordomo-users-owner Tue Nov 12 14:47:20 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA27765 for majordomo-users-outgoing; Tue, 12 Nov 1996 14:36:40 -0800 (PST) Received: from methan.chemie.fu-berlin.de (methan.chemie.fu-berlin.de [160.45.22.81]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id OAA27667 for ; Tue, 12 Nov 1996 14:35:47 -0800 (PST) Received: by methan.chemie.fu-berlin.de (Smail3.1.29.1) from calle.in-berlin.de (194.94.235.16) with smtp id ; Tue, 12 Nov 96 23:35 MET Received: by calle.in-berlin.de (Smail3.2) from moonbow.in-berlin.de with bsmtp id ; Tue, 12 Nov 1996 23:35:42 +0100 (MET) Received: from rainbow.in-berlin.de by moonbow.in-berlin.de with smtp (Smail3.1.29.1 #8) id m0vNRGK-000aGRC; Tue, 12 Nov 96 23:24 MET Received: by rainbow.in-berlin.de (Smail3.1.28.1 #1) id m0vNRGJ-000g6bC; Tue, 12 Nov 96 23:24 MET Received: from GATEWAY by rainbow with netnews for majordomo-users@GreatCircle.COM (majordomo-users@GreatCircle.COM) To: majordomo-users@GreatCircle.COM Date: Tue, 5 Nov 1996 18:44:01 GMT From: sbolting@nemonet.com (Stephen Boltinghouse) Message-ID: <679.051093963906@news.nemonet.com> Subject: Just try this, it will work Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Take five minutes to read this and it WILL change your life. The Internet has grown tremendously. It doubles in size every 4 months. think about it. You see those 'Make.Money.Fast' posts more and more. That's ... because it WORKS ! So I thought, all those new users might make it work. And I decided to try it out, a few months ago. Besides, whats $5.00, I spend more than that in the morning on my way to work on coffee and cigs for the day. So I sent in my money and posted. Everyone was calling it a scam, but there are SO many new users from AOL, Netcom, etc. they will join in and make it work for you. Well, two weeks later, I began recieving bucks in the mail! I couldn't believe it! Not just a little, I mean big bucks! At first only a few hundred dollars, then a week later, a couple of thousand, then BOOM. By the end of the fourth week, I had recieved nearly $47,000.00. It came from all over the world. And every bit of it perfectly legal and on the up and up. I've been able to pay off all my bills and still had enough left over for a nice vacation for me and my family. Not only does it work for me, it works for other folks as well. Markus Valppu says he made $57,883 in four weeks. Dave Manning claims he made $53,664 in the same amount of time. Dan Shepstone says it was only $17,000 for him. Do I know these folks? No, but when I read how they say they did it, it made sense to me. Enough sense that I'm taking a similar chance with $5 of my own bucks. Not a big chance, I admit--but one with incredible potential, because $5 is all anyone ever invests in this system. Period. That's all Markus, Dave, or Dan invested, yet their $5 netted them tens of thousands of dollars each, in a safe, legal, completely legitimate way. Here's how it works in 3 easy steps: STEP 1. Invest your $5 by writing your name and address on five seperate pieces of paper along with the words: "PLEASE ADD ME TO YOUR MAILING LIST." (In this way, you're not just sending a dollar to someone; you're paying for a legitimate service.) Fold a $1 bill, money order, or bank note inside each paper, and mail them by standard U. S. Mail to the following five addresses: 1- Fern Suarez Mallorca 112 Hato Rey, P.R., USA, 00917 2- Philippe 2104 De Mexico Chomedey, Laval Quebec, Canada H7M 3C6 3- Natalie Jansen Lancveldlaan 18 5671 CN Nuenen Holland 4- Chad Collier 2785 Cold Springs Rd. #49 Placerville, CA 95667 5- Steve Boltinghouse 1009 Bird St. Hannibal, MO 63401 STEP 2. Now remove the top name from the list, and move the other names up.This way, #5 becomes #4 and so on. Put your name in as the fifth one on the list. STEP 3. Post the article to at least 250 newsgroups. There are at least 19000 newsgroups at any given moment in time. Try posting to as many newsgroups as you can. Remember the more groups you post to, the more people will see your article and send you cash! STEP 4. You are now in business for yourself, and should start seeing returns within 7 to 14 days! Remember, the Internet is new and huge. There is no way you can lose. Now here is how and why this system works: Out of every block of 250 posts I made, I got back 5 responses. Yes, thats right,only 5. You make $5.00 in cash, not checks or money orders, but real cash with your name at #5. Each additional person who sent you $1.00 now also makes 250 additional postings with your name at #4, 1000 postings. On average then, 50 people will send you $1.00 with your name at #4,....$50.00 in your pocket! Now these 50 new people will make 250 postings each with your name at #3 or 10,000 postings. Average return, 500 people= $500. They make 250 postings each with your name at #2= 100,000 postings=5000 returns at $1.00 each=$5,000.00 in cash! Finally, 5,000 people make 250 postings each with your name at #1 and you get a return of $60,000 before your name drops off the list.And that's only if everyone down the line makes only 250 postings each! Your total income for this one cycle is $55,000. From time to time when you see your name is no longer on the list, you take the latest posting you can find and start all over again. The end result depends on you. You must follow through and repost this article everywhere you can think of. The more postings you make, the more cash ends up in your mailbox. It's too easy and too cheap to pass up!!! So thats it. Pretty simple sounding stuff, huh? But believe me, it works. There are millions of people surfing the net every day, all day, all over the world. And 100,000 new people get on the net every day. You know that, you've seen the stories in the paper. So, my friend, read and follow the simple instructions and play fair. Thats the key, and thats all there is to it. Print this out right now so you can refer back to this article easily. Try to keep an eye on all the postings you made to make sure everyone is playing fairly. You know where your name should be. If you're really not sure or still think this can't be for real, then don't do it. But please print this article and pass it along to someone you know who really needs the bucks, and see what happens. REMEMBER....HONESTY IS THE BEST POLICY.YOU DON'T NEED TO CHEAT THE BASIC IDEA TO MAKE THE BUCKS! GOOD LUCK TO ALL, AND PLEASE PLAY FAIR AND YOU WILL WIN AND MAKE SOME REAL INSTANT FREE CASH! *** By the way, if you try to deceive people by posting the messages with your name in the list and not sending the bucks to the people already included, you will not get much. I know someone who did this and only got about $150 (and that's after two months). Then he sent the 5 bills, people added him to their lists, and in 4-5 weeks he had over $10,000! TRY IT AND YOU'LL BE HAPPY!!! :o) !!!!!!!!!! From majordomo-users-owner Tue Nov 12 15:17:00 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA28957 for majordomo-users-outgoing; Tue, 12 Nov 1996 14:50:25 -0800 (PST) Received: from senie.com (senie.com [204.69.207.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id OAA28944 for ; Tue, 12 Nov 1996 14:50:14 -0800 (PST) Received: (qmail-queue invoked from smtpd); 12 Nov 1996 22:50:06 -0000 Received: from localhost (dts@127.0.0.1) by localhost with SMTP; 12 Nov 1996 22:50:06 -0000 Date: Tue, 12 Nov 1996 17:50:06 -0500 (EST) From: Daniel Senie To: Dave Wolfe cc: majordomo-users@greatcircle.com Subject: Re: restricting messages In-Reply-To: <199611122033.OAA13273@miaow.risc.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, 12 Nov 1996, Dave Wolfe wrote: > [ Daniel Senie writes: ] > > > > I'd like to limit the ability to send messages to a list to those people > > already s*bscribed to the list. I thought there was an item in the config > > file to do this, but now do not seem to find it. > > Look for restrict_post. Thanks to everyone who responded both to the list and privately. For anyone else watching, the proper incantation is to set restrict_post = listname If you're running digests, then additional stuff needs to be there for that. As with other text in the config file, it wasn't clear if the list file should be named with a full path, with no path, etc. Dan --------------------------------------------------------------- Daniel Senie Internet: dan@senie.com, Daniel Senie Consulting n1jeb@senie.com http://www.senie.com Packet Radio: N1JEB@KA1SRD.MA If we suffer tamely a lawless attack upon our liberty, we encourage it, and involve others in our doom. -- Samuel Adams From majordomo-users-owner Tue Nov 12 19:32:02 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA18846 for majordomo-users-outgoing; Tue, 12 Nov 1996 19:23:28 -0800 (PST) Received: from ponder (ponder.csci.unt.edu [129.120.3.16]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id TAA18783 for ; Tue, 12 Nov 1996 19:23:02 -0800 (PST) Received: by ponder (5.61/1.36) id AA20734; Tue, 12 Nov 96 21:23:47 -0600 From: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) Message-Id: <9611130323.AA20734@ponder> Subject: mail error 139 To: majordomo-users@greatcircle.com Date: Tue, 12 Nov 1996 21:23:45 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk ok th efunny part is that I am getting a mail from majordomo as well but I get this mail as well.. anybody know why am i getting this additional mail .. some asked me about the dir rights earlier so lemme show the dir rights.. majordomo is installed in my home dir.. drwxr-xr-x 10 sshamim daemon 1024 Nov 12 20:59 . drwxr-xr-x 4 sshamim sshamim 512 Nov 12 20:32 .. -rw-r--r-- 1 sshamim sshamim 19 May 7 1994 .cvsignore -rw-r--r-- 1 sshamim sshamim 45 May 7 1994 .dcl -rw-r--r-- 1 sshamim sshamim 58112 May 23 17:02 Changelog drwxr-xr-x 3 sshamim sshamim 512 Oct 20 08:26 Doc -rw-r--r-- 1 sshamim sshamim 8933 Oct 20 07:23 FUTURE -rw-r--r-- 1 sshamim sshamim 4116 Sep 24 18:49 INSTALL -rw-r--r-- 1 sshamim sshamim 6732 Sep 20 11:46 LICENSE -rw-rw-r-- 1 sshamim daemon 0 Nov 12 20:56 Log -rw-r--r-- 1 sshamim sshamim 8220 Nov 12 20:38 Makefile -rw-r--r-- 1 sshamim sshamim 5655 Sep 4 11:01 NEWLIST -rw-r--r-- 1 sshamim sshamim 21590 Oct 20 08:18 README drwxr-xr-x 2 sshamim daemon 512 Nov 12 20:57 Tools -rw-r--r-- 1 sshamim sshamim 6241 Jul 21 15:06 approve drwxr-xr-x 2 sshamim sshamim 512 Nov 12 20:57 bin -rw-r--r-- 1 sshamim sshamim 5122 Sep 17 12:38 bounce -rwxr-xr-x 1 sshamim daemon 2771 Nov 12 20:57 bounce-remind -rwxr-xr-x 1 sshamim daemon 8827 Nov 12 20:57 config-test -rwxr-xr-x 1 sshamim daemon 47928 Nov 12 20:57 config_parse.pl drwxr-xr-x 2 sshamim sshamim 512 Oct 20 08:26 contrib drwxr-xr-x 2 sshamim sshamim 512 Oct 20 08:26 include drwxrwxr-x 2 sshamim daemon 512 Nov 12 21:13 lists -rwxr-xr-x 1 sshamim daemon 55403 Nov 12 20:57 majordomo -rw-r--r-- 1 sshamim sshamim 856 Jan 28 1996 majordomo.aliases -rw-r--r-- 1 sshamim daemon 8639 Nov 12 20:57 majordomo.cf -rwxr-xr-x 1 sshamim daemon 19842 Nov 12 20:57 majordomo.pl -rwxr-xr-x 1 sshamim daemon 124 Nov 12 20:57 majordomo_version.pl drwxr-xr-x 4 sshamim daemon 512 Nov 12 20:47 man drwxr-xr-x 2 sshamim sshamim 512 Oct 20 08:26 md-sub -rw-r--r-- 1 sshamim sshamim 1297 Jan 17 1996 medit -rwxr-xr-x 1 sshamim daemon 3486 Nov 12 20:57 request-answer -rwxr-xr-x 1 sshamim daemon 29602 Nov 12 20:57 resend -rw-r--r-- 1 sshamim daemon 8639 Nov 12 20:58 sample.cf -rwxr-xr-x 1 sshamim daemon 7547 Nov 12 20:57 shlock.pl -rwxr-xr-x 1 sshamim sshamim 12967 Nov 12 20:42 wrapper -rw-r--r-- 1 sshamim sshamim 3544 Sep 22 17:08 wrapper.c -rw-r--r-- 1 sshamim sshamim 212 May 9 1994 wrapper.sh IN REPLY TO Mail Delivery Subsystem MAIL > From Tue Nov 12 21:16:10 1996 > Date: Tue, 12 Nov 1996 21:14:05 -0600 (CST) > From: Mail Delivery Subsystem > Subject: Returned mail: unknown mailer error 139 > Message-Id: <199611130314.VAA11439@psycho.csci.unt.edu> > To: owner-majordomo@psycho.csci.unt.edu > Mime-Version: 1.0 > Content-Type: multipart/report; report-type=delivery-status; > boundary="VAA11439.847854845/psycho.csci.unt.edu" > Auto-Submitted: auto-generated (failure) > > This is a MIME-encapsulated message > > --VAA11439.847854845/psycho.csci.unt.edu > > The original message was received at Tue, 12 Nov 1996 21:13:56 -0600 (CST) > from sshamim@localhost > > ----- The following addresses have delivery notifications ----- > "|/usr/users/sshamim/majordomo-1.94/wrapper majordomo" (unrecoverable error) > (expanded from: majordomo) > > ----- Transcript of session follows ----- > Message delivered to mailing list majordomo > Memory fault > 554 "|/usr/users/sshamim/majordomo-1.94/wrapper majordomo"... unknown mailer error 139 > > --VAA11439.847854845/psycho.csci.unt.edu > Content-Type: message/delivery-status > > Reporting-MTA: dns; psycho.csci.unt.edu > Arrival-Date: Tue, 12 Nov 1996 21:13:56 -0600 (CST) > > Final-Recipient: RFC822; majordomo@psycho.csci.unt.edu > Action: delivered (to mailing list) > Status: 2.0.0 > Last-Attempt-Date: Tue, 12 Nov 1996 21:14:05 -0600 (CST) > > Final-Recipient: RFC822; majordomo@psycho.csci.unt.edu > X-Actual-Recipient: RFC822; |/usr/users/sshamim/majordomo-1.94/wrapper majordomo@psycho.csci.unt.edu > Action: failed > Status: 5.0.0 > Last-Attempt-Date: Tue, 12 Nov 1996 21:14:04 -0600 (CST) > > --VAA11439.847854845/psycho.csci.unt.edu > Content-Type: message/rfc822 > > Return-Path: sshamim > Received: (from sshamim@localhost) by psycho.csci.unt.edu (8.7.5/8.7.3) id VAA11437 for majordomo; Tue, 12 Nov 1996 21:13:56 -0600 (CST) > Date: Tue, 12 Nov 1996 21:13:56 -0600 (CST) > From: Syed Faraz Shamim > Message-Id: <199611130313.VAA11437@psycho.csci.unt.edu> > To: majordomo > > lists > > --VAA11439.847854845/psycho.csci.unt.edu-- > > -- Assalam o Alaikum -- Faraz E-mail: sshamim@cs.unt.edu From majordomo-users-owner Wed Nov 13 00:32:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id AAA02376 for majordomo-users-outgoing; Wed, 13 Nov 1996 00:29:40 -0800 (PST) Received: from gamma.dou.dk ([130.225.156.14]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id AAA02369 for ; Wed, 13 Nov 1996 00:29:31 -0800 (PST) Received: from dou-pc1 (peter.dou.dk [130.225.156.244]) by gamma.dou.dk (8.6.10/8.6.10) with SMTP id JAA22036; Wed, 13 Nov 1996 09:26:48 +0100 Date: Wed, 13 Nov 1996 09:26:48 +0100 Message-Id: <2.2.16.19961113101552.2dbf01b2@mail.dou.dk> X-Sender: maspsr@mail.dou.dk X-Mailer: Windows Eudora Pro Version 2.2 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Michael Stokes , majordomo-users@GreatCircle.COM From: Peter Sorensen Subject: Re: HPUX 10.20 and MD1.94 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 10.38 12-11-1996 -0800, Michael Stokes wrote: >I just upgraded from HPUX 9.07 to HPUX 10.20 and MD1.93 stopped working. >I decided to go ahead and upgread to MD1.94 and hope my problems went >away. No such luck. > >When I try to > >echo 'lists' | mail majordomo > >I recieved the following error via email > > ---- The following addresses have delivery notifications ---- >"|/usr/local/majordomo/wrapper majordomo" (unrecoverable error) > (expanded from majordomo) > > ---- Transcript of sesssion follows ---- >sh: /usr/local/majordomo/wrapper: not found, >554 "|/usr/local/majordomo/wrapper majordomo"...unknown mailer error 126 > >I have verified that /usr/local/majordomo/wrapper exists and has >executable permissions for all users. > >PLEASE help...any ideas ? change alias to: |"/usr/local/majordomo/wrapper majordomo" regards Peter Sorensen/University of Odense,dk/e-mail:maspsr@dou.ou.dk From majordomo-users-owner Wed Nov 13 03:02:23 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id CAA07979 for majordomo-users-outgoing; Wed, 13 Nov 1996 02:55:17 -0800 (PST) Received: from i2bs.com (i2bs.com [205.242.194.21]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id CAA07949 for ; Wed, 13 Nov 1996 02:54:53 -0800 (PST) Received: from skb.sbcomp.net (bernoulli-07.inpi.com [207.152.80.107]) by i2bs.com (8.7.5/8.7.3) with SMTP id EAA05034 for ; Wed, 13 Nov 1996 04:54:54 -0600 (CST) Message-Id: <3.0.32.19961113044549.006ce258@205.242.194.21> X-Sender: skb@205.242.194.21 X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 13 Nov 1996 04:55:07 -0600 To: majordomo-users@GreatCircle.COM From: "Steven K. Buehler" Subject: Re: digests Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Ok...I solved my own problem here. The problem was that the other person that is an admin on the system decided to try and tighten up security on the system and did an "chmod o-r /" (without quotes of course), taking away read permissions for other on the root directory of the system and it was messing with more then just majordomo. At 07:40 AM 11/11/96 -0600, Steven K. Buehler wrote: > mkdigest my-list-digest 17November96 >*** digest: failed errors follow >producing my-digest V1 #54 >Warning: cannot determine current directory >/usr/home/majordom/digests/my-list-digest/001: No such file or directory > >ABORT Warning: cannot determine current directory >/usr/home/majordom/digests/my-list-digest/001: No such file or directory > >End of first message_________________________________________________ > >2nd message________________________________________________________ >MAJORDOMO ABORT > >Warning: cannot determine current directory >/usr/home/majordom/digests/my-list-digest/001: No such file or directory > >End of 2nd message___________________________________________________ ====================================================== Steven K. Buehler S & B Computers Rockford Illinois, USA Phone: 815-398-7169 Fax: 815-398-7266 ====================================================== From majordomo-users-owner Wed Nov 13 04:17:01 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id EAA09838 for majordomo-users-outgoing; Wed, 13 Nov 1996 04:00:59 -0800 (PST) Received: from ponder (ponder.csci.unt.edu [129.120.3.16]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id EAA09806 for ; Wed, 13 Nov 1996 04:00:25 -0800 (PST) Received: by ponder (5.61/1.36) id AA02199; Wed, 13 Nov 96 06:01:12 -0600 From: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) Message-Id: <9611131201.AA02199@ponder> Subject: Re: mail error 139 To: majordomo-users@greatcircle.com Date: Wed, 13 Nov 1996 06:01:11 -0600 (CST) In-Reply-To: from "Kendall P Bullen" at Nov 13, 96 02:41:27 am X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk IN REPLY TO Kendall P Bullen MAIL > > Hiya, > > root -- the permissions should be -rws--x--x (or maybe that's > -rwsr-xr-x?), and owner/group should both be root. I also wonder if > the permissions on your directory are correct. . . . (That one bit me > when I installed Mj.) > Yes, it was the permission of the Mj dir that bit me also because my system is FreeBSD and it uses daemon's uid and gid.. so the the Mj dir should be set to 1:1 as daemon:daemon.. I believe someone asked me earlier that if I ever find out about this mailer error 139 let him know.. since I lost his address I have to post it here :-) -- Faraz E-mail: sshamim@cs.unt.edu From majordomo-users-owner Wed Nov 13 05:02:38 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id EAA10667 for majordomo-users-outgoing; Wed, 13 Nov 1996 04:49:12 -0800 (PST) Received: from anjinho (anjinho.dsc.ufpb.br [150.165.2.21]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id EAA10622 for ; Wed, 13 Nov 1996 04:48:04 -0800 (PST) Received: from zevampir.dsc.ufpb.br (zevampir.dsc.ufpb.br [150.165.2.20]) by anjinho (8.7.5/8.7.3) with SMTP id JAA18304 for ; Wed, 13 Nov 1996 09:44:06 -0400 Received: by zevampir.dsc.ufpb.br (5.x/SMI-SVR4) id AA22336; Wed, 13 Nov 1996 09:55:18 -0200 Date: Wed, 13 Nov 1996 09:55:17 -0200 (EDT) From: Fellipe Araujo Aleixo X-Sender: fellipe@zevampir To: majordomo-users@GreatCircle.com Subject: Finishing installation of Majordomo Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Folks, Somebody could help me? I finished all steps to the installation of the Majordomo 1.94, i tested it with the "wrapper config-test", and it work ok. But when i was testing sending an e-mail to majordomo the following error happen to me: ******Begin of test [anjinho] root# sendmail -v majordomo majordomo... aliased to "| /usr/local/share/src/majordomo-1.94/wrapper majordom" lists From majordomo-users-owner Wed Nov 13 07:11:17 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA16471 for majordomo-users-outgoing; Wed, 13 Nov 1996 06:56:48 -0800 (PST) Received: from Central.KeyWest.MPGN.COM (Central.TanSoft.COM [206.175.4.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA16462 for ; Wed, 13 Nov 1996 06:56:37 -0800 (PST) Received: from devious.Tansoft.com (Devious.TanSoft.COM [206.175.4.10]) by Central.KeyWest.MPGN.COM (8.6.9/8.6.9) with SMTP id JAA09806 for ; Wed, 13 Nov 1996 09:56:45 -0500 Message-Id: <3.0b35.32.19961113095644.007c5860@central.TanSoft.COM> X-Sender: rwm@central.TanSoft.COM X-Mailer: Windows Eudora Pro Version 3.0b35 (32) Date: Wed, 13 Nov 1996 09:56:49 -0500 To: majordomo-users@greatcircle.com From: Rob Miracle Subject: Majordomo 1.94 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have recently installed 1.94 (I need the taboo_*** abilities) and I have had nothing but headaches with it. (Bascially it uses /tmp for a log file and the digests and like most sites, we didn't commit a lot of storage to the / partition). Any way, my question is this: Is 1.94 a release version or an alpha? I have gotten conflicting information about this. Thanks Rob -- Rob Miracle Tantalus Inc. Be patient or be a patient. -- Anton Devious From majordomo-users-owner Wed Nov 13 07:28:14 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA17328 for majordomo-users-outgoing; Wed, 13 Nov 1996 07:11:34 -0800 (PST) Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA17297 for ; Wed, 13 Nov 1996 07:11:14 -0800 (PST) Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-961106) id HAA23455; Wed, 13 Nov 1996 07:11:14 -0800 Received: from unknown(207.19.215.3) by mycroft via smap (V1.3mjr) id sma023434; Wed Nov 13 07:10:31 1996 Received: from localhost (bikesh@localhost) by ns2.t3tech.com (8.7.5/8.7.3) with SMTP id KAA24383; Wed, 13 Nov 1996 10:16:02 GMT Date: Wed, 13 Nov 1996 10:16:02 +0000 () From: The UNIX Mighty! X-Sender: bikesh@ns2.t3tech.com To: Stephen Boltinghouse cc: majordomo-users@GreatCircle.COM Subject: Re: Just try this, it will work In-Reply-To: <679.051093963906@news.nemonet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk someone spam this moran! bikesh On Tue, 5 Nov 1996, Stephen Boltinghouse wrote: > Date: Tue, 5 Nov 1996 18:44:01 GMT > From: Stephen Boltinghouse > To: majordomo-users@GreatCircle.COM > Subject: Just try this, it will work > > > Take five minutes to read this and it WILL change your life. > > The Internet has grown tremendously. It doubles in size every 4 months. > think about it. You see those 'Make.Money.Fast' posts more and more. > That's ... because it WORKS ! So I thought, all those new users might > make it work. And I decided to try it out, a few months ago. Besides, > whats $5.00, I spend more than that in the morning on my way to work on > coffee and cigs for the day. So I sent in my money and posted. > Everyone was calling it a scam, but there are SO many new users from > AOL, Netcom, etc. they will join in and make it work for you. > > Well, two weeks later, I began recieving bucks in the mail! I couldn't > believe it! Not just a little, I mean big bucks! At first only a few > hundred dollars, then a week later, a couple of thousand, then BOOM. By > the end of the fourth week, I had recieved nearly $47,000.00. It came > from all over the world. And every bit of it perfectly legal and on the > up and up. I've been able to pay off all my bills and still had enough > left over for a nice vacation for me and my family. > > Not only does it work for me, it works for other folks as well. Markus > Valppu says he made $57,883 in four weeks. Dave Manning claims he made > $53,664 in the same amount of time. Dan Shepstone says it was only > $17,000 for him. Do I know these folks? No, but when I read how they > say they did it, it made sense to me. Enough sense that I'm taking a > similar chance with $5 of my own bucks. Not a big chance, I admit--but > one with incredible potential, because $5 is all anyone ever invests in > this system. Period. That's all Markus, Dave, or Dan invested, yet > their $5 netted them tens of thousands of dollars each, in a safe, > legal, completely legitimate way. Here's how it works in 3 easy steps: > > STEP 1. > > Invest your $5 by writing your name and address on five seperate pieces > of paper along with the words: "PLEASE ADD ME TO YOUR MAILING LIST." (In > this way, you're not just sending a dollar to someone; you're paying for > a legitimate service.) Fold a $1 bill, money order, or bank note inside > each paper, and mail them by standard U. S. Mail to the following five > addresses: > > 1- Fern Suarez > Mallorca 112 > Hato Rey, P.R., USA, 00917 > > 2- Philippe > 2104 De Mexico > Chomedey, Laval > Quebec, Canada > H7M 3C6 > > 3- Natalie Jansen > Lancveldlaan 18 > 5671 CN Nuenen > Holland > > 4- Chad Collier > 2785 Cold Springs Rd. #49 > Placerville, CA 95667 > > 5- Steve Boltinghouse > 1009 Bird St. > Hannibal, MO 63401 > > STEP 2. > > Now remove the top name from the list, and move the > other names up.This way, #5 becomes #4 and so on. > Put your name in as the fifth one on the list. > > > STEP 3. > > Post the article to at least 250 newsgroups. There are at > least 19000 newsgroups at any given moment in time. > Try posting to as many newsgroups as you can. Remember > the more groups you post to, the more people will see your > article and send you cash! > > > STEP 4. > > You are now in business for yourself, and should start seeing > returns within 7 to 14 days! Remember, the Internet is new > and huge. There is no way you can lose. > > Now here is how and why this system works: > > Out of every block of 250 posts I made, I got back 5 responses. > Yes, thats right,only 5. You make $5.00 in cash, not checks or > money orders, but real cash with your name at #5. > > Each additional person who sent you $1.00 now also makes 250 > additional postings with your name at #4, 1000 postings. On > average then, 50 people will send you $1.00 with your name at > #4,....$50.00 in your pocket! > > Now these 50 new people will make 250 postings each with your > name at #3 or 10,000 postings. Average return, 500 people= $500. > They make 250 postings each with your name at #2= 100,000 > postings=5000 returns at $1.00 each=$5,000.00 in cash! > > Finally, 5,000 people make 250 postings each with your name at > #1 and you get a return of $60,000 before your name drops off > the list.And that's only if everyone down the line makes only 250 > postings each! Your total income for this one cycle is $55,000. > > From time to time when you see your name is no longer on the list, > you take the latest posting you can find and start all over again. > > The end result depends on you. You must follow through > and repost this article everywhere you can think of. > The more postings you make, the more cash ends up in > your mailbox. It's too easy and too cheap to pass up!!! > > So thats it. Pretty simple sounding stuff, huh? But believe me, it > works. There are millions of people surfing the net every day, all > day, all over the world. And 100,000 new people get on the net > every day. You know that, you've seen the stories in the paper. > So, my friend, read and follow the simple instructions and play > fair. Thats the key, and thats all there is to it. Print this out > right now so you can refer back to this article easily. Try to keep > an eye on all the postings you made to make sure everyone is > playing fairly. You know where your name should be. > > If you're really not sure or still think this can't be > for real, then don't do it. But please print this article and pass it > along to someone you know who really needs the bucks, and see > what happens. > > > REMEMBER....HONESTY IS THE BEST POLICY.YOU DON'T > NEED TO CHEAT THE BASIC IDEA TO MAKE THE BUCKS! > GOOD LUCK TO ALL, AND PLEASE PLAY FAIR AND YOU WILL > WIN AND MAKE SOME REAL INSTANT FREE CASH! > > *** By the way, if you try to deceive people by posting the messages > with your name in the list and not sending the bucks to the people > already included, you will not get much. I know someone who did this > and only got about $150 (and that's after two months). Then he sent > the 5 bills, people added him to their lists, and in 4-5 weeks he had > over $10,000! > > TRY IT AND YOU'LL BE HAPPY!!! :o) !!!!!!!!!! > From majordomo-users-owner Wed Nov 13 07:47:19 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA18670 for majordomo-users-outgoing; Wed, 13 Nov 1996 07:46:02 -0800 (PST) Received: from mail.his.com (mail.his.com [205.177.25.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA18663 for ; Wed, 13 Nov 1996 07:45:52 -0800 (PST) Received: from [205.177.25.164] (kendall.his.com [205.177.25.164]) by mail.his.com (8.6.9/8.6.12) with ESMTP id KAA05136; Wed, 13 Nov 1996 10:45:36 -0500 Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 13 Nov 1996 10:45:37 -0500 To: Fellipe Araujo Aleixo From: "Kendall P Bullen" Subject: Re:Finishing installation of Majordomo Cc: majordomo-users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 9:55 AM -0200 11/13/96, Fellipe Araujo Aleixo wrote: >But when i was testing sending an e-mail to majordomo the following >error happen to me: > > >******Begin of test > >[anjinho] root# sendmail -v majordomo >majordomo... aliased to "| >/usr/local/share/src/majordomo-1.94/wrapper majordom" >lists Um, you must've sent too soon, because I see no error here. But I tried what you did, out of curiosity, and got some weirdness that maybe someone can help *me* with (grin) -- what's up with the sendmail WARNING signs below? As you can see, /etc/alises is readable, and /usr/local/majordomo-1.94/majordomo.aliases is indeed read in, because the alias is expanded. Curious. . . . Kendall (clueless) lists:~# sendmail -v majordomo WARNING: cannot open alias database /etc/aliases /etc/aliases: 5 aliases, longest 46 bytes, 124 bytes total WARNING: cannot open alias database /usr/local/majordomo-1.94/majordomo.aliases /usr/local/majordomo-1.94/majordomo.aliases: 35 aliases, longest 88 bytes, 1943 bytes total majordomo... aliased to "|/usr/local/majordomo-1.94/wrapper majordomo" [1]+ Stopped sendmail -v majordomo lists:~# v /etc/aliases -rw-r--r-- 1 root root 141 Oct 26 00:41 /etc/aliases lists:~# fg sendmail -v majordomo lists "|/usr/local/majordomo-1.94/wrapper majordomo"... Sent lists:~# -- Kendall P. Bullen E-mail: kendall@his.com Web: http://www.his.com/~kendall/ From majordomo-users-owner Wed Nov 13 08:17:44 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA19230 for majordomo-users-outgoing; Wed, 13 Nov 1996 07:57:46 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA19210; Wed, 13 Nov 1996 07:57:12 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA03036 for majordomo-users@greatcircle.com; Wed, 13 Nov 96 08:56:52 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA19221 for majordomo-workers@greatcircle.com; Wed, 13 Nov 96 08:56:50 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA04119; Wed, 13 Nov 1996 09:56:50 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA15915; Wed, 13 Nov 1996 09:56:48 -0600 From: Dave Wolfe Message-Id: <199611131556.JAA15915@miaow.risc.sps.mot.com> Subject: Re: Majordomo 1.94 To: rwm@MPGN.COM (Rob Miracle) Date: Wed, 13 Nov 1996 09:56:48 -0600 (CST) Cc: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com (Majordomo developer's mailing list) In-Reply-To: <3.0b35.32.19961113095644.007c5860@central.TanSoft.COM> from "Rob Miracle" at Nov 13, 96 09:56:49 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Rob Miracle writes: ] > > I have recently installed 1.94 (I need the taboo_*** abilities) and I have > had nothing but headaches with it. (Bascially it uses /tmp for a log file > and the digests and like most sites, we didn't commit a lot of storage to > the / partition). I'd agree, digest really needs to be using $TMPDIR from the majordomo.cf file. > Any way, my question is this: Is 1.94 a release version or an alpha? I > have gotten conflicting information about this. It's released, but did you pick up an alpha or final release? -- Dave Wolfe From majordomo-users-owner Wed Nov 13 08:17:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA20011 for majordomo-users-outgoing; Wed, 13 Nov 1996 08:15:10 -0800 (PST) Received: from bock.ucs.ualberta.ca (bock.ucs.ualberta.ca [129.128.5.214]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA20003 for ; Wed, 13 Nov 1996 08:15:01 -0800 (PST) Received: from qm-gw.ucs.ualberta.ca by bock.ucs.ualberta.ca with SMTP (8.6.5/UA) id JAA24312 for ; Wed, 13 Nov 1996 09:15:28 -0700 Message-ID: Date: 13 Nov 1996 09:16:29 -0600 From: "Dennis Black" Subject: Re: Superlists (Re- Duplicat To: "Majordomo Users" X-Mailer: Mail*Link SMTP-QM 3.0.1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Reply to: RE>Superlists (Re: Duplicate messages to a list) On 11/11/96 thomasg@ifi.uio.no wrote: >Well, it doesn't work that way for me. I'm testing this now, with >two listnames in the subscriber file. List 1 has A and B as >subscribers, list 2 has A and C as subscribers. A got the message >twice. >So, can it work -- all subscribers getting the message only once, >no matter how many lists they are subscribed to? Thomas, In the following example, "lista" is the . All lists have a restrict_post = lista:listab:listc:listd:liste:listf lista subscribers are: listb@mysite.ca listc@mysite.ca listd@mysite.ca liste@mysite.ca listf@mysite.ca Lists b through f have actual subscribers' addresses. Nothing fancy with each of the alias entries: lista:"|/home/majordomo/wrapper resend -l lista -h majordomo.srv.ualberta.ca lista-outgoing" lista-outgoing::include:/usr/local/mail/lists/lista Lists b through f are defined the same way. If I understand your examples correctly, List1 contains subscribers A@yoursite and B@yoursite List2 contains subscribers A@yoursite and C@yoursite What you need is a third list. Let's call it List0. List1 and List2 subscribers can stay put, but for List0, enter two subscribers: List1@yoursite List2@yoursite And set restrict_post for all three to be all three: restrict_post = List0:List1:List2 When someone posts to List0, Majordomo expands its two subscribers, List1 and List2, to the actual recipients in each of those. Just don't set any reply_to's in any of the three - you'll set yourself up for loops. If I interpret your examples another way, you may be saying that you want people to be able to post to 'lista&b' and 'lista&c' separately, but also be able to post to both lists with a single message. Again, you need a third list, hypothetically called Listabc. 'Lista&b' contains people's email addresses, as does 'Lista&c'. 'Listabc' contains, as subscribers: lista&b@yoursite lista&c@yoursite A post goes to 'listabc@yoursite', and gets expanded to the two smaller lists. Majordomo (so I've read somewhere) checks for duplicates. Again, don't do reply_to's. Clear as mud? For your other concern, I don't think 1.92 is that much different - I'm still on 1.93. From majordomo-users-owner Wed Nov 13 08:48:19 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA20760 for majordomo-users-outgoing; Wed, 13 Nov 1996 08:32:04 -0800 (PST) Received: from apollo.it.hq.nasa.gov (apollo.it.hq.nasa.gov [131.182.119.87]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA20693 for ; Wed, 13 Nov 1996 08:31:41 -0800 (PST) Received: from wirehead.it.hq.nasa.gov (WireHead.it.hq.nasa.gov [131.182.119.88]) by apollo.it.hq.nasa.gov (8.6.12/8.6.12) with ESMTP id QAA20253 for ; Wed, 13 Nov 1996 16:32:08 GMT Received: from localhost (cshenton@localhost) by wirehead.it.hq.nasa.gov (8.6.12/8.6.12) with SMTP id QAA18215 for ; Wed, 13 Nov 1996 16:31:20 GMT Message-Id: <199611131631.QAA18215@wirehead.it.hq.nasa.gov> X-Authentication-Warning: wirehead.it.hq.nasa.gov: cshenton owned process doing -bs X-Authentication-Warning: wirehead.it.hq.nasa.gov: Host localhost didn't use HELO protocol To: majordomo-users@greatcircle.com Subject: Preventing spam via *-outgoing alias? X-Mailer: Mew version 1.03 on Emacs 19.31.8 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 13 Nov 1996 11:31:20 -0500 From: Chris Shenton Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk One of NASA HQ's public affairs lists (total about 20K subscribers) just got spammed by some jerk sending mail to one of the *-outgoing aliases. We just changed these names to be something non-obvious, hid the headers with the "nobody" alias hack, and disabled EXPN and VRFY on sendmail. This is in line with the FAQ's suggestions. I'm not a believer in "security through obscurity". I also think using something like: listname-outgoing: :include:/usr/local/majordomo/lists/listname is naively dangerous and will be exploited eventually. Seems silly for majordomo to check for valid sender, headers, special keywords, etc on one alias, then do nothing about the alias that does the sending. Why isn't there a wrapper function which checks the sender, Received-by: headers, etc, to ensure that the originator is not some off-site toad, and if legitimate, then does the ":include:" thing itself? Has anyone done something like this? Do alternative list manager programs also suffer from this same design flaw? Thanks. From majordomo-users-owner Wed Nov 13 09:02:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA22107 for majordomo-users-outgoing; Wed, 13 Nov 1996 08:52:57 -0800 (PST) Received: from ns2.t3tech.com (ns2.t3tech.com [207.19.215.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA22080 for ; Wed, 13 Nov 1996 08:52:41 -0800 (PST) Received: from localhost (bikesh@localhost) by ns2.t3tech.com (8.7.5/8.7.3) with SMTP id MAA24823 for ; Wed, 13 Nov 1996 12:00:38 GMT Date: Wed, 13 Nov 1996 12:00:38 +0000 () From: The UNIX Mighty! X-Sender: bikesh@ns2.t3tech.com To: "Majordomo user's mailing list" Subject: Re: Just try this, it will work In-Reply-To: <199611131558.JAA15926@miaow.risc.sps.mot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk All right! Let's kill the thread bikesh From majordomo-users-owner Wed Nov 13 09:09:37 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA21975 for majordomo-users-outgoing; Wed, 13 Nov 1996 08:50:29 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA21946 for ; Wed, 13 Nov 1996 08:50:15 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA12259 for majordomo-users@greatcircle.com; Wed, 13 Nov 96 09:50:25 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA21667 for majordomo-users@greatcircle.com; Wed, 13 Nov 96 09:50:21 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id KAA05183; Wed, 13 Nov 1996 10:50:20 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA15926; Wed, 13 Nov 1996 09:58:38 -0600 From: Dave Wolfe Message-Id: <199611131558.JAA15926@miaow.risc.sps.mot.com> Subject: Re: Just try this, it will work To: bikesh@tum.net (The UNIX Mighty!) Date: Wed, 13 Nov 1996 09:58:38 -0600 (CST) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list) In-Reply-To: from "The UNIX Mighty!" at Nov 13, 96 10:16:02 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ The UNIX Mighty! writes: ] > > someone spam this moran! Good luck. Either he's already been zapped or he forged an invalid e-mail address. Let's not compound his spam by continuing to discuss it in this forum, OK? -- Dave Wolfe From majordomo-users-owner Wed Nov 13 09:18:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA23007 for majordomo-users-outgoing; Wed, 13 Nov 1996 09:10:29 -0800 (PST) Received: from clarinet.synapse.net (clarinet.synapse.net [199.84.54.19]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA23000 for ; Wed, 13 Nov 1996 09:10:16 -0800 (PST) Received: from piano.synapse.net (piano.synapse.net [199.84.54.20]) by clarinet.synapse.net (8.8.2/8.8.2) with ESMTP id MAA18660; Wed, 13 Nov 1996 12:10:16 -0500 (EST) Received: from piano.synapse.net (localhost [127.0.0.1]) by piano.synapse.net (8.8.2/8.8.2) with SMTP id MAA04371; Wed, 13 Nov 1996 12:10:16 -0500 (EST) Date: Wed, 13 Nov 1996 12:10:16 -0500 (EST) From: Evan Champion To: Chris Shenton cc: majordomo-users@GreatCircle.COM Subject: Re: Preventing spam via *-outgoing alias? In-Reply-To: <199611131631.QAA18215@wirehead.it.hq.nasa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Wed, 13 Nov 1996, Chris Shenton wrote: > One of NASA HQ's public affairs lists (total about 20K subscribers) > just got spammed by some jerk sending mail to one of the *-outgoing > aliases. Upgrade to 1.94 and run TLB. Then you don't need a -outgoing alias. Evan -- Evan Champion * Director, Network Operations mailto:evanc@synapse.net * Directeur, Exploitation du reseau http://www.synapse.net/ * Synapse Internet From majordomo-users-owner Wed Nov 13 09:32:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA22980 for majordomo-users-outgoing; Wed, 13 Nov 1996 09:09:12 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA22941 for ; Wed, 13 Nov 1996 09:08:50 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA15279 for majordomo-users@GreatCircle.COM; Wed, 13 Nov 96 10:09:03 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA22462 for majordomo-users@GreatCircle.COM; Wed, 13 Nov 96 10:09:02 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id LAA05653; Wed, 13 Nov 1996 11:08:59 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id LAA12220; Wed, 13 Nov 1996 11:08:56 -0600 From: Dave Wolfe Message-Id: <199611131708.LAA12220@miaow.risc.sps.mot.com> Subject: Re: Finishing installation of Majordomo To: kendall@his.com (Kendall P Bullen) Date: Wed, 13 Nov 1996 11:08:56 -0600 (CST) Cc: fellipe@dsc.ufpb.br, majordomo-users@GreatCircle.COM In-Reply-To: from "Kendall P Bullen" at Nov 13, 96 10:45:37 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Kendall P Bullen writes: ] > > lists:~# sendmail -v majordomo > WARNING: cannot open alias database /etc/aliases > /etc/aliases: 5 aliases, longest 46 bytes, 124 bytes total > WARNING: cannot open alias database > /usr/local/majordomo-1.94/majordomo.aliases > /usr/local/majordomo-1.94/majordomo.aliases: 35 aliases, longest 88 > bytes, 1943 > bytes total > majordomo... aliased to "|/usr/local/majordomo-1.94/wrapper majordomo" > > [1]+ Stopped sendmail -v majordomo > lists:~# v /etc/aliases > -rw-r--r-- 1 root root 141 Oct 26 00:41 /etc/aliases Fine, but what about /etc/aliases.dir and /etc/aliases.pag? Those are the "database" for /etc/aliases. -- Dave Wolfe From majordomo-users-owner Wed Nov 13 09:48:17 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA24035 for majordomo-users-outgoing; Wed, 13 Nov 1996 09:40:02 -0800 (PST) Received: from mail.his.com (mail.his.com [205.177.25.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA23992 for ; Wed, 13 Nov 1996 09:39:40 -0800 (PST) Received: from [205.177.25.164] (kendall.his.com [205.177.25.164]) by mail.his.com (8.6.9/8.6.12) with ESMTP id MAA17289; Wed, 13 Nov 1996 12:39:44 -0500 Message-Id: In-Reply-To: <199611131708.LAA12220@miaow.risc.sps.mot.com> References: from "Kendall P Bullen" at Nov 13, 96 10:45:37 am Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 13 Nov 1996 12:39:48 -0500 To: Dave Wolfe From: "Kendall P Bullen" Subject: Re: Finishing installation of Majordomo Cc: majordomo-users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 11:08 AM -0600 11/13/96, Dave Wolfe wrote: >Fine, but what about /etc/aliases.dir and /etc/aliases.pag? Those are >the "database" for /etc/aliases. Um. No such files; never heard of them. I guess I must've missed something in the doc's about making those files. Since things always worked (and I never tried it manually with the verbose option), I never knew I had missed a step. :) Oops. I will RTFineM post-haste, thanks. (Um, it is in there, right?) Kendall -- Kendall P. Bullen E-mail: kendall@his.com Web: http://www.his.com/~kendall/ From majordomo-users-owner Wed Nov 13 10:03:38 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA23939 for majordomo-users-outgoing; Wed, 13 Nov 1996 09:37:39 -0800 (PST) Received: from mail.his.com (mail.his.com [205.177.25.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA23932 for ; Wed, 13 Nov 1996 09:37:28 -0800 (PST) Received: from [205.177.25.164] (kendall.his.com [205.177.25.164]) by mail.his.com (8.6.9/8.6.12) with ESMTP id MAA17053 for ; Wed, 13 Nov 1996 12:37:39 -0500 Message-Id: In-Reply-To: <199611131631.QAA18215@wirehead.it.hq.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 13 Nov 1996 12:37:43 -0500 To: majordomo-users@GreatCircle.COM From: "Kendall P Bullen" Subject: Re:Preventing spam via *-outgoing alias? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 11:31 AM -0500 11/13/96, Chris Shenton wrote: >I also think using something like: > > listname-outgoing: :include:/usr/local/majordomo/lists/listname > >is naively dangerous and will be exploited eventually. Well, there is no requirement that you use -outgoing for your outgoing alias! That is one of the suggestions I received when I asked on this list -- use something non-obvious, like listname-arglebargle. (Well, that's not the one that was suggested, but it sure sounds good. ;) I do think that if it isn't menteiond or stressed enough already, that ever place in the doc's. where making outgoing list aliases is mentioned, it should be stressed that "listname-outgoing" is an abysmal alias name. >Seems silly for majordomo to check for valid sender, headers, special >keywords, etc on one alias, then do nothing about the alias that does >the sending. That's because (when someone e-mails your listname-outgoing alias) it is not going through Majordomo, so Majordomo can't do a heck of a lot about it. At least the way it's designed now, methinks. >Why isn't there a wrapper function which checks the sender, >Received-by: headers, etc, to ensure that the originator is not some >off-site toad, and if legitimate, then does the ":include:" thing >itself? I am curious as to how you could tell if someone were legit or not. (Remember that if your subscribe and post policies are open, then anyone could subscribe *anyway* and then spam the list.) >Do alternative list manager programs also suffer from this same >design >flaw? I am curious about this. I wonder if other list managers simply don't use aliases for outgoing e-mail. Kendall -- Kendall P. Bullen E-mail: kendall@his.com Web: http://www.his.com/~kendall/ From majordomo-users-owner Wed Nov 13 11:02:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA27963 for majordomo-users-outgoing; Wed, 13 Nov 1996 11:00:57 -0800 (PST) Received: from bock.ucs.ualberta.ca (bock.ucs.ualberta.ca [129.128.5.214]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA27956 for ; Wed, 13 Nov 1996 11:00:46 -0800 (PST) Received: from qm-gw.ucs.ualberta.ca by bock.ucs.ualberta.ca with SMTP (8.6.5/UA) id MAA04462 for ; Wed, 13 Nov 1996 12:00:56 -0700 Message-ID: Date: 13 Nov 1996 12:02:10 -0600 From: "Dennis Black" Subject: member count for 1.93 To: "Majordomo Users" X-Mailer: Mail*Link SMTP-QM 3.0.1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk REGARDING member count for 1.93 Some of the listowners at my site had asked me to find a way to print out the number of members in their lists. (Some are well over 100.) I haven't d/l'ed 1.94 yet, so I don't know if it's already included, but for those still on 1.93 like me, you just need to add two lines, as indicated: vi'ing "majordomo" at the "do_who" subroutine, don't enter the square-bracketed comments. #open it up and tell who's on it print REPLY "Members of list '$clean_list':\n\n"; if (&lopen(LIST, "", "$listdir/$clean_list")) { while () { print REPLY $_; $lncnt++; [new line] } print REPLY "\n $lncnt members in this list.\n"; [new line] &lclose(LIST); &log("who $clean_list"); } else { From majordomo-users-owner Wed Nov 13 11:12:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA27892 for majordomo-users-outgoing; Wed, 13 Nov 1996 11:00:05 -0800 (PST) Received: from vex.cs.colorado.edu (vex.cs.Colorado.EDU [128.138.241.27]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA27845 for ; Wed, 13 Nov 1996 10:59:54 -0800 (PST) Received: from vex.cs.colorado.edu (seidl@localhost.cs.colorado.edu [127.0.0.1]) by vex.cs.colorado.edu (8.7.6/8.7.3) with ESMTP id LAA04994; Wed, 13 Nov 1996 11:59:44 -0700 (MST) Message-Id: <199611131859.LAA04994@vex.cs.colorado.edu> To: majordomo-users@greatcircle.com cc: seidl@vex.cs.colorado.edu Subject: Re: Preventing spam via *-outgoing alias? In-reply-to: Your message of "Wed, 13 Nov 1996 12:10:16 EST." Date: Wed, 13 Nov 1996 11:59:43 -0700 From: Matthew Seidl Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Evan Champion said... >On Wed, 13 Nov 1996, Chris Shenton wrote: > >> One of NASA HQ's public affairs lists (total about 20K subscribers) >> just got spammed by some jerk sending mail to one of the *-outgoing >> aliases. > >Upgrade to 1.94 and run TLB. Then you don't need a -outgoing alias. > >Evan >-- >Evan Champion * Director, Network Operations >mailto:evanc@synapse.net * Directeur, Exploitation du reseau >http://www.synapse.net/ * Synapse Internet I just recently joined this list, in prerperation for migrating a number of medium sized lists from 1.92 to 1.94, and I've now seen mention of TLB in a couple of places, but no notion where to acquire it, or at least more docs on it. Can someone please enlighten me? -=- Matthew L. Seidl email: seidl@cs.colorado.edu =-= =-= Graduate Student Project . . . What Project? -=- -=- Gamer, Re-Enactor, hecka stressed We're here to make your life better!=-= =-= and trying not to be too homesick for the BA -Morrow Quotes -=- From majordomo-users-owner Wed Nov 13 12:08:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA00640 for majordomo-users-outgoing; Wed, 13 Nov 1996 11:47:42 -0800 (PST) Received: from sparkie.osl.state.or.us (sparkie.osl.state.or.us [192.84.215.34]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA00611 for ; Wed, 13 Nov 1996 11:47:26 -0800 (PST) Received: from [192.84.215.117] (mac117.osl.state.or.us [192.84.215.117]) by sparkie.osl.state.or.us (8.6.9/8.6.9) with SMTP id LAA20114 for ; Wed, 13 Nov 1996 11:47:05 -0800 Message-Id: <199611131947.LAA20114@sparkie.osl.state.or.us> Subject: Re: member count for 1.93 Date: Wed, 13 Nov 96 11:48:41 +1200 From: chris To: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Good idea. One question- How do I actually generate the statistics? Christopher Adams >Subject: member count for 1.93 >Sent: 11/14/96 6:02 AM >Received: 11/13/96 11:21 AM >From: Dennis Black, Dennis.Black@UAlberta.CA >To: Majordomo Users, majordomo-users@GreatCircle.COM > >REGARDING member count for 1.93 > >Some of the listowners at my site had asked me to find a way to print >out the number of members in their lists. (Some are well over 100.) >I haven't d/l'ed 1.94 yet, so I don't know if it's already included, but for >those still on 1.93 like me, you just need to add two lines, as indicated: > >vi'ing "majordomo" at the "do_who" subroutine, don't enter the >square-bracketed comments. > > #open it up and tell who's on it > print REPLY "Members of list '$clean_list':\n\n"; > if (&lopen(LIST, "", "$listdir/$clean_list")) { > while () { > print REPLY $_; > $lncnt++; > [new line] > } > print REPLY "\n $lncnt members in this list.\n"; [new line] > &lclose(LIST); > &log("who $clean_list"); > } else { > From majordomo-users-owner Wed Nov 13 12:29:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA00483 for majordomo-users-outgoing; Wed, 13 Nov 1996 11:45:52 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id LAA00401 for ; Wed, 13 Nov 1996 11:45:11 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id NAA01058; Wed, 13 Nov 1996 13:44:24 -0600 (CST) To: Chris Shenton Cc: majordomo-users@GreatCircle.COM Subject: Re: Preventing spam via *-outgoing alias? References: <199611131631.QAA18215@wirehead.it.hq.nasa.gov> From: Jason L Tibbitts III Date: 13 Nov 1996 13:44:23 -0600 In-Reply-To: Chris Shenton's message of Wed, 13 Nov 1996 11:31:20 -0500 Message-ID: Lines: 41 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "CS" == Chris Shenton writes: CS> Why isn't there a wrapper function which checks the sender, CS> Received-by: headers, etc, to ensure that the originator is not some CS> off-site toad, and if legitimate, then does the ":include:" thing CS> itself? Because it would still have to pass the authenticated mail off to sendmail, which needs an alias somewhere that points it at the address list, i.e. an outgoing alias. CS> Has anyone done something like this? It would do no good. CS> Do alternative list manager programs also suffer from this same design CS> flaw? Some do, others talk SMTP directly and thus bypass the need to have the mailer see an address list in a file somewhere. Fortunately it is not necessary to run Majordomo his way, viz: fvwm-announce: "|/usr/local/lists/majordomo/wrapper resend -l fvwm-announce -h hpc.uh.edu nobody" See, no outgoing alias. EXPN and VRFY are allowed, with no security risk to the list. You cannot bypass the moderation, period, even if you are on my site and can read the aliases file. This is possible because I have written software called TLB (already mentioned here by Evan) which acts as an intermediary between Majordomo and your MTA. You can retrieve a copy from ftp.hpc.uh.edu:/pub/tlb. The current version is 0.09a. You must have Majordomo 1.94 to use it. The documentation could use some work (I'm no tech writer) but it is in use at several sites and will eliminate the problem you describe. Note that it is not the only way to solve the problem; sometimes it can be solved by using an alternate sendmail config file which is used only within Majordomo. I think there is a FAQ entry on this, but I'm not sure. - J< From majordomo-users-owner Wed Nov 13 12:36:58 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA01817 for majordomo-users-outgoing; Wed, 13 Nov 1996 12:12:54 -0800 (PST) Received: from rigel.fa1.cie.uva.es (rigel.fa1.cie.uva.es [157.88.35.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id MAA01808 for ; Wed, 13 Nov 1996 12:12:31 -0800 (PST) Received: from localhost (chr@localhost) by rigel.fa1.cie.uva.es (8.7.5/8.7.3) with SMTP id UAA16078 for ; Wed, 13 Nov 1996 20:12:01 GMT Date: Wed, 13 Nov 1996 20:12:01 +0000 (GMT) From: Jose Antonio Vivanco Martos To: majordomo-users@GreatCircle.com Subject: Problem with majordomo Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk OOps, it's not really a problem of majordomo, it's my problem: I have majordomo insttaled in my system and works well, but I want, the address of the list appear on the outgoing mail. Actually, when a mail arrives to one of the list's member, he can see in his mail program (pine or elm) 7 Nov 13 Jose Antonio Vivanco this is a test and I like : 7 Nov 13 Test list from majordomo this is a test I supose that Imust change the from: ouf outgoing message but how???? Chr I'm SOORRRY but my english is very poor (I'm spanish) From majordomo-users-owner Wed Nov 13 12:47:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA02333 for majordomo-users-outgoing; Wed, 13 Nov 1996 12:31:51 -0800 (PST) Received: from dnacom.com (dnacom.com [205.147.66.209]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA02315 for ; Wed, 13 Nov 1996 12:31:16 -0800 (PST) Received: from dnacom.com (jdawson@dnacom.com [205.147.66.209]) by dnacom.com (8.6.12/8.6.12) with SMTP id MAA01295 for ; Wed, 13 Nov 1996 12:31:20 -0800 Date: Wed, 13 Nov 1996 12:31:18 -0800 (PST) From: Jim Dawson X-Sender: jdawson@dnacom.com To: majordomo-users@GreatCircle.COM Subject: Re: Finishing installation of Majordomo 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, 13 Nov 1996, Kendall P Bullen wrote: > At 11:08 AM -0600 11/13/96, Dave Wolfe wrote: > > >Fine, but what about /etc/aliases.dir and /etc/aliases.pag? Those are > >the "database" for /etc/aliases. > > Um. No such files; never heard of them. I guess I must've missed > something in the doc's about making those files. Since things always > worked (and I never tried it manually with the verbose option), I > never knew I had missed a step. :) Oops. I will RTFineM > post-haste, thanks. (Um, it is in there, right?) > Did you run newaliases after changing /etc/aliases? Jim __________________________________________________________________ Jim Dawson jdawson@navi.net GCN Communications, Inc. http://www.navi.net 2305 NW Kearney St. Ste. 239 voice: +1.503.531.1978 Portland, Or 97210 USA fax: +1.503.531.1979 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From majordomo-users-owner Wed Nov 13 13:21:21 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA02948 for majordomo-users-outgoing; Wed, 13 Nov 1996 12:45:55 -0800 (PST) Received: from bock.ucs.ualberta.ca (bock.ucs.ualberta.ca [129.128.5.214]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA02932 for ; Wed, 13 Nov 1996 12:45:38 -0800 (PST) Received: from qm-gw.ucs.ualberta.ca by bock.ucs.ualberta.ca with SMTP (8.6.5/UA) id NAA24676 for ; Wed, 13 Nov 1996 13:45:52 -0700 Message-ID: Date: 13 Nov 1996 13:47:43 -0600 From: "Dennis Black" Subject: Re: member count for 1.93 To: "Majordomo Users" X-Mailer: Mail*Link SMTP-QM 3.0.1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Reply to: RE>>member count for 1.93 On 11/13/96 Christopher Adams wrote: >Good idea. One question- How do I actually generate the statistics? In reply to: >>Some of the listowners at my site had asked me to find a way to print >>out the number of members in their lists. >vi'ing "majordomo" at the "do_who" subroutine, > #open it up and tell who's on it > print REPLY "Members of list '$clean_list':\n\n"; > if (&lopen(LIST, "", "$listdir/$clean_list")) { > while () { > print REPLY $_; > $lncnt++; [new line] > } > print REPLY "\n $lncnt members in this list.\n"; [new line] > &lclose(LIST); > &log("who $clean_list"); > } else { > Appology, this is in the do_who routine, so in response to a "who " command, you get a total. This simply counts the lines, assuming that one line = one subscriber. You've got a problem if it's in any other format. I just got notified by one of my listowners that if you do two "who's" in one message, it totals the first list fine, but keeps incrementing, so the final total is list one plus list two, not list one total, list two total. Back to variable arrays... From majordomo-users-owner Wed Nov 13 13:46:54 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA04745 for majordomo-users-outgoing; Wed, 13 Nov 1996 13:23:07 -0800 (PST) Received: from lambton.on.ca (white.lambton.on.ca [192.139.190.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id NAA04722 for ; Wed, 13 Nov 1996 13:22:54 -0800 (PST) Received: from localhost by white.lambton.on.ca with SMTP id AA00916; Wed, 13 Nov 1996 16:24:39 -0500 Date: Wed, 13 Nov 1996 16:24:39 -0500 (EST) From: David Grant To: Majordomo users Cc: David Grant Subject: 1.94 resend options fail? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm trying to upgrade from 1.93 to 1.94 on a DEC OSF/1 v2.0 box. The majordomo script seams to work fine, but the resend script barfs on its options. I've tried upgrading perl to 5.003 (from 5.001i) but still now luck. Here is the alias line (which works fine under 1.93): test: "| /usr/local/majordomo-1.94/wrapper resend -l test -r test -h lambton.on.ca -s test-outgoing" and here is what I get: # sendmail -v test test... aliased to "| /usr/local/majordomo-1.94/wrapper resend -l test -r test -h lambton.on.ca -s test-outgoing" Subject: test Here is a test ^D "| /usr/local/majordomo-1.94/wrapper resend -l test -r test -h lambton.on.ca -s test-outgoing"... Connecting to (prog)... about to exec Array found where operator expected at (eval 9) line 1, near "david@lambton" lambton.on.ca... User unknown Mailer /usr/lib/sendmail -oi -fowner-test@lambton.on.ca test -h lambton.on.ca -s test-outgoing exited unexpectedly with error 17152 ABORT Mailer /usr/lib/sendmail -oi -fowner-test@lambton.on.ca test -h lambton.on .ca -s test-outgoing exited unexpectedly with error 17152"| /usr/local/majordomo -1.94/wrapper resend -l test -r test -h lambton.on.ca -s test-outgoing"... Sent # If I take out all the options but the -l listname it seams to work although I still get the message about 'array found where operator expected'. Forgive me if this is a FAQ, but I couldn't find anything in the docs, and I don't know where a searchable index for the archives is. Ideas anyone? Dave ----- David Grant VE3DGR +1 519 542-7751 x348 Lambton College, Sarnia, ON, CANADA +1 519 542-6667 FAX From majordomo-users-owner Wed Nov 13 15:32:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA09939 for majordomo-users-outgoing; Wed, 13 Nov 1996 14:49:22 -0800 (PST) Received: from solstice.crest.org (solstice.crest.org [198.77.86.217]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id OAA09875 for ; Wed, 13 Nov 1996 14:48:51 -0800 (PST) Received: from localhost (zach@localhost) by solstice.crest.org (8.6.12/8.6.6) with SMTP id RAA27898 for ; Wed, 13 Nov 1996 17:51:16 -0500 Date: Wed, 13 Nov 1996 17:51:15 -0500 (EST) From: Zach Nobel X-Sender: zach@solstice To: majordomo-users@greatcircle.com Subject: Does perl 5.001 unoff. patch 1m count as being better than 5.001e? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Quick question for folks in the know. I've got perl version 5.001 Unofficial patchlevel 1m (as indicated by perl5 -v). Is this usable? Or is 5.001e an 'official' patch where the Unoffical patch (1m) doesn't have the requisite characteristics. Thanks much, Zachariah Nobel _________ Zachariah Nobel, Assistant in Internet Services Center for Renewable Energy and Sustainable Technology (CREST) zach@crest.org From majordomo-users-owner Wed Nov 13 15:38:12 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA10531 for majordomo-users-outgoing; Wed, 13 Nov 1996 14:55:45 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA10508 for ; Wed, 13 Nov 1996 14:55:29 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id QAA07831; Wed, 13 Nov 1996 16:54:26 -0600 (CST) To: David Grant Cc: Majordomo users Subject: Re: 1.94 resend options fail? References: From: Jason L Tibbitts III Date: 13 Nov 1996 16:54:26 -0600 In-Reply-To: David Grant's message of Wed, 13 Nov 1996 16:24:39 -0500 (EST) Message-ID: Lines: 16 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "DG" == David Grant writes: [Big snip. That's what References: is for.] DG> If I take out all the options but the -l listname it seams to work DG> although I still get the message about 'array found where operator DG> expected'. We botched the argument parsing of resend trying to patch the problem where Sendmail downcases the options. In this case, it really is best for you to get rid of everything but `-l' and just use the config file. As for the "array found..." error, I'd have to see your config file but Id wager that you've neglected to escape an `@' symbol in a string. - J< From majordomo-users-owner Wed Nov 13 15:45:12 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA13513 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:30:03 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA13491 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:29:57 -0800 (PST) Received: from lists.oulu.fi (lists.oulu.fi [130.231.241.85]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id XAA05295 for ; Sun, 10 Nov 1996 23:44:32 -0800 (PST) Received: from localhost (mhotti@localhost) by lists.oulu.fi (8.7.5/8.7.3) with SMTP id JAA32381; Mon, 11 Nov 1996 09:44:28 +0200 Date: Mon, 11 Nov 1996 09:44:28 +0200 (EET) From: Marko Hotti To: Christopher Adams cc: majordomo-users@GreatCircle.COM Subject: Re: turn off messages to listowner? 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, 9 Nov 1996, Christopher Adams wrote: > Is there a way to turn off the messages that are sent to the listowner > when an individual subscribes or unsubscribes? I have accomplished this using the following method: My majordomo aliases look like this: listname-owner: bounce-handler owner-listname: bounce-handler listname-approval: approval-handler ... and then: bounce-handler: mhotti approval-handler: mhotti Then - if I want to turn off the approval messages, I just rename the bounce/approval-handler addresses to point to /dev/null or some other applicable address. --Marko Marko Hotti WWW: http://www.lists.oulu.fi/~mhotti/ System Administrator Tel: +358 (0)40 552 8415 (work) University of Oulu, FINLAND +358 (0)8 530 4268 (home) From majordomo-users-owner Wed Nov 13 16:30:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA16456 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:54:54 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA16427 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:54:43 -0800 (PST) Received: from adinet.analog.com (adinet.analog.com [137.71.23.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA23851 for ; Tue, 12 Nov 1996 07:35:59 -0800 (PST) Received: by adinet.analog.com id AA07690 (InterLock SMTP Gateway 3.0 for majordomo-users@greatcircle.com); Tue, 12 Nov 1996 10:36:09 -0500 Received: by adinet.analog.com (Internal Mail Agent-2); Tue, 12 Nov 1996 10:36:09 -0500 Received: by adinet.analog.com (Internal Mail Agent-1); Tue, 12 Nov 1996 10:36:09 -0500 Date: Tue, 12 Nov 96 10:35:15 EST From: greg.harrison@analog.com (greg harrison) Message-Id: <9611121535.AA10428@sarah> To: majordomo-users@greatcircle.com Subject: Help with errors Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Can anyone tell me what the following errors mean, or where I can look them up (maybe there is a listing of all of the error numbers somewhere?)? I checked the Oreilly chapter, the FAQ, the User guide, the Admin guide and even some of the archives on greatcircle (any way they can be made searchable???) but found nothing of help.. MAJORDOMO ABORT Mailer /usr/lib/sendmail -oi -fowner-dsc@pilot.cld.analog.com dsc-outgoing exited unexpectedly with error 18176 MAJORDOMO ABORT Mailer /usr/lib/sendmail -oi -fowner-alldesign@pilot.cld.analog.com alldesign-outgoing exited unexpectedly with error 17920 Any help would be appreciated. I have tried various things to clear these errors up, but to no avail. -Greg Harrison From majordomo-users-owner Wed Nov 13 16:33:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA14939 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:41:44 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA14878 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:41:28 -0800 (PST) Received: from eros.gcsnet.com.br (eros.gcsnet.com.br [200.238.233.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA27034 for ; Mon, 11 Nov 1996 08:37:25 -0800 (PST) From: root@eros.gcsnet.com.br Received: from teste.gcsnet.com.br (vesta.gcsnet.com.br [200.238.233.3]) by eros.gcsnet.com.br (8.7.5/8.7.3) with SMTP id OAA04136 for ; Mon, 11 Nov 1996 14:37:30 -0200 Date: Mon, 11 Nov 1996 14:37:30 -0200 Message-Id: <199611111637.OAA04136@eros.gcsnet.com.br> X-Sender: root@eros.gcsnet.com.br X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: majordomo-users@GreatCircle.COM Subject: Re: Can't unsubscribe Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 04:34 PM 11/7/96 -0200, fred@pegasus.com.br wrote: >I'm using Majordomo 1.94 on an Linux. I have created a test list and >can 'subscribe', 'who list', 'lists' but cannot 'unsubscribe' from it. =20 >The message I get back as the issuer of unsubscribe is: >>>>> unsubscribe test > >The message I get back as the owner of the mailing list is: >MAJORDOMO ABORT > >chmod(33206, "/server/majordomo-1.94/lists/test.new"): Operation not >permitted > >the arquives are in 666 mod majordomo own and daemon group. > >Any help is appreciated. Dear Fred, change your wrapper arquive to 4755 mod, root own and daemon group and=20 you will be able to unsubscribe. Fabricio Campolina - Administra=E7=E3o Gcsnet From majordomo-users-owner Wed Nov 13 16:35:58 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA11378 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:05:08 -0800 (PST) Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id PAA11251 for ; Wed, 13 Nov 1996 15:04:29 -0800 (PST) Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-961106) id PAA24743; Wed, 13 Nov 1996 15:04:27 -0800 Received: from sina.hpc.uh.edu(129.7.3.5) by mycroft via smap (V1.3mjr) id sma024726; Wed Nov 13 15:04:01 1996 Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id RAA08037; Wed, 13 Nov 1996 17:03:02 -0600 (CST) To: Jose Antonio Vivanco Martos Cc: majordomo-users@GreatCircle.COM Subject: Re: Problem with majordomo References: From: Jason L Tibbitts III Date: 13 Nov 1996 17:03:02 -0600 In-Reply-To: Jose Antonio Vivanco Martos's message of Wed, 13 Nov 1996 20:12:01 +0000 (GMT) Message-ID: Lines: 20 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "JAVM" == Jose Antonio Vivanco Martos writes: JAVM> 7 Nov 13 Jose Antonio Vivanco this is a test JAVM> and I like : JAVM> 7 Nov 13 Test list from majordomo this is a test JAVM> I supose that Imust change the from: ouf outgoing message but how???? The mail actually came from a person; the list server just resent it. If you really, really want to do this, you can by adding a From: header to message_headers and doing a small edit to the resend code, but I wouldn't recommend it, especially since this completely loses track of who actually sent the message. Some like to use subject_prefix to prepend some string to the subject of the mail, so that mail from the list is immediately obvious. - J< From majordomo-users-owner Wed Nov 13 16:40:07 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA14968 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:41:54 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA14900 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:41:35 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA26784 for ; Mon, 11 Nov 1996 08:32:55 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id LAA17017; Mon, 11 Nov 1996 11:33:05 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id LAA07329; Mon, 11 Nov 1996 11:33:01 -0500 (EST) Message-Id: <199611111633.LAA07329@augusta.math.psu.edu> To: fred@pegasus.com.br cc: majordomo-users@GreatCircle.COM Subject: Re: Can't unsubscribe from test list In-reply-to: Your message of "Wed, 06 Nov 1996 10:41:46 -0200." <3280878A.370E@pegasus.com.br> References: <3280878A.370E@pegasus.com.br> 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: Mon, 11 Nov 1996 11:33:00 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <3280878A.370E@pegasus.com.br>, Frederico Ferreira da Silva writes: >I'm using Majordomo 1.94 on an Linux. I have created a test list and >can 'subscribe', 'who list', 'lists' but cannot 'unsubscribe' from it. >The message I get back as the issuer of unsubscribe is: >>>>> unsubscribe test fred@antares.pegasus.com.br > >The message I get back as the owner of the mailing list is: >MAJORDOMO ABORT > >Can't open /majordomo/lists/test.new: Permission denied What does ./wrapper config-test say? Try reading the FAQ, question 2.1. --Dave From majordomo-users-owner Wed Nov 13 16:41:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA16220 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:53:29 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA16045 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:52:56 -0800 (PST) Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id SAA22914 for ; Mon, 11 Nov 1996 18:14:37 -0800 (PST) Received: (from smap@localhost) by mailgate.Cadence.COM (8.6.8/8.6.8) id SAA21951 for ; Mon, 11 Nov 1996 18:14:42 -0800 Received: from jewels.cadence.com(158.140.32.165) by mailgate.cadence.com via smap (V1.0mjr) id sma847764877.021942; Mon Nov 11 18:14:37 1996 Received: (from julian@localhost) by jewels.Cadence.COM (8.6.8/8.6.8) id SAA28004; Mon, 11 Nov 1996 18:14:23 -0800 Date: Mon, 11 Nov 1996 18:14:23 -0800 From: Julian Gordon Message-Id: <199611120214.SAA28004@jewels.Cadence.COM> To: larry@garfield.wsc.mass.edu Subject: Re: Restricted postings Cc: majordomo-users@greatcircle.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: sbaiJU9i8Kb1c3AQMyQFQg== Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Larry, Here is the script. It took a couple of days because I was having a problem with unsubscribes, which I thought was because of the script, but turned out to be because of an incorrect gid. I use the NIS maps to determine whether someone is internal or not. I included a note with the change that would need to be done if you wanted to use a domain checking mechanism. I would also like to integrate the program more fully into majordomo. If there is a more general interest for it as a relevant solution to the "restricting subscriptions by domain" problem, I will go ahead and do that. Any feedback (as long as it's positive:-) is welcome. Julian > From larry@garfield.wsc.mass.edu Thu Nov 7 09:08:46 1996 > > Dear Julian, > > Could you send me the script to automatically subscribe people > in your company (or post it to the majordomo-users group)? Thanks. > > Larry > From majordomo-users-owner Wed Nov 13 16:46:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA13341 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:28:29 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA13328 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:28:25 -0800 (PST) Received: from relay1.UU.NET by ascb.saturnm.rosmail.com with ESMTP id JAA10999; (8.8.2/vak/1.9) Mon, 11 Nov 1996 09:31:39 +0300 (MSK) Received: from miles.greatcircle.com by relay1.UU.NET with ESMTP (peer crosschecked as: miles.greatcircle.com [198.102.244.34]) id QQbpif09038; Mon, 11 Nov 1996 01:26:44 -0500 (EST) Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id WAA02084 for majordomo-users-outgoing; Sun, 10 Nov 1996 22:08:31 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id WAA02076 for majordomo-users@greatcircle.com; Sun, 10 Nov 1996 22:08:27 -0800 (PST) Received: from mozart.quinncom.net (quinncom.net [205.136.86.11]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA12839 for ; Sun, 10 Nov 1996 15:21:58 -0800 (PST) Received: from tpupke.awod.com (chs0127.awod.com [198.81.225.46]) by mozart.quinncom.net (8.7.6/8.6.9) with SMTP id SAA15688 for ; Sun, 10 Nov 1996 18:20:54 -0500 Message-Id: <3.0.32.19961110182158.006a3e94@popserver.quinncom.net> X-Sender: tpupke@popserver.quinncom.net X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Sun, 10 Nov 1996 18:22:02 -0500 To: majordomo-users@GreatCircle.com From: Trace Pupke Subject: Majordomo ABORT - Can someone help? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm getting this error message when I try to unsubscribe. --- MAJORDOMO ABORT chown(54, 2, "/usr/local/majordomo/lists/test.new"): Operation not permitted --- I'm trying to set up majordomo on Linux 2.0.18 I have the user and group set as majordom:daemon (54:2) I added majordom to the group listing for daemon Does any have a little time and patience to help?? Thanks ~~~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ Trace Pupke <>< HTML Coordinator Quinn Communications tpupke@quinncom.net http://www.quinncom.net/ ~~~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ From majordomo-users-owner Wed Nov 13 16:46:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA16843 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:59:56 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA16831 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:59:50 -0800 (PST) Received: from caroline.cardiffcybercafe.co.uk (caroline.cardiffcybercafe.co.uk [194.168.44.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA18879 for ; Wed, 13 Nov 1996 07:50:46 -0800 (PST) Received: by caroline.cardiffcybercafe.co.uk (ElectricMail-MESSAGE-2.0-GAMMA) id PAA22326; Wed, 13 Nov 1996 15:42:33 GMT Date: Wed, 13 Nov 1996 15:42:32 +0000 (GMT) From: Andy Wild X-Sender: andywild@caroline To: majordomo-users@GreatCircle.COM Subject: Can't get Majordomo to unsubscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I've been playing with Majordomo for the last couple of days and almost have it working. I have been able to setup a mailing list, subscribe to it and receive any postings to it, but I have been unable to unsubscribe to it! I have tried e-mailing majordomo with a plain 'unsubscribe ' and a 'unsubscribe ' but all to no avail. Majordomo does e-mail me back but only echoes my commands back to me - there is no "Succeeded" message and the e-mail address stays in the main list's file. I was having a similar problem before when trying to subscribe to the list but worked out that it was simply a permission problem with the main list's file. Any ideas anyone? Cheers, Andy Wild. Technical Officer. The Cardiff CyberCafe Ltd./LightSpeed On-Line. ----------------------------------------------------------------------- The Cardiff CyberCafe Ltd. LightSpeed On-Line 9, Duke Street 9, Duke Street Cardiff, CF1 2AY Cardiff, CF1 2AY UNITED KINGDOM UNITED KINGDOM Tel: +44-1222-235757 Tel: +44-1222-235760 Fax: +44-1222-235758 Tel: +44-1222-235758 www.cardiffcybercafe.co.uk www.lightspeed.co.uk ----------------------------------------------------------------------- From majordomo-users-owner Wed Nov 13 16:47:13 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA15037 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:42:22 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA14972 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:41:55 -0800 (PST) Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA29860 for ; Mon, 11 Nov 1996 09:41:29 -0800 (PST) From: postmaster@cadence.com Received: (from smap@localhost) by mailgate.Cadence.COM (8.6.8/8.6.8) id JAA04900; Mon, 11 Nov 1996 09:41:39 -0800 Received: from jewels.cadence.com(158.140.32.165) by mailgate.cadence.com via smap (V1.0mjr) id sma847734095.004895; Mon Nov 11 09:41:35 1996 Received: (from Unknown UID 9833@localhost) by jewels.Cadence.COM (8.6.8/8.6.8) id JAA26987; Mon, 11 Nov 1996 09:41:33 -0800 Date: Mon, 11 Nov 1996 09:41:33 -0800 Message-Id: <199611111741.JAA26987@jewels.Cadence.COM> To: tpupke@quinncom.net Subject: Re: Majordomo ABORT - Can someone help? Cc: majordomo-users@GreatCircle.COM Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: d4LsvUspUqVacTOtFyXLCQ== Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk chown is only allowed by the user or super-user. So what it means is that majordomo is not running as the owner of the file, (or root) and so cannot chown. Julian > From majordomo-users-owner@GreatCircle.COM Sun Nov 10 22:34:36 1996 > Received-Date: Sun, 10 Nov 1996 22:34:35 -0800 > X-Sender: tpupke@popserver.quinncom.net > Date: Sun, 10 Nov 1996 18:22:02 -0500 > To: majordomo-users@GreatCircle.COM > From: Trace Pupke > Subject: Majordomo ABORT - Can someone help? > Mime-Version: 1.0 > > > I'm getting this error message when I try to unsubscribe. > > --- > > MAJORDOMO ABORT > > chown(54, 2, "/usr/local/majordomo/lists/test.new"): Operation not permitted > > --- > > I'm trying to set up majordomo on Linux 2.0.18 > I have the user and group set as majordom:daemon (54:2) > I added majordom to the group listing for daemon > > Does any have a little time and patience to help?? > > Thanks > > > ~~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ > Trace Pupke <>< HTML Coordinator Quinn Communications > tpupke@quinncom.net http://www.quinncom.net/ > ~~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~"~ > > From majordomo-users-owner Wed Nov 13 16:53:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA16804 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:59:23 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA16790 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:59:16 -0800 (PST) Received: from amber.ccs.neu.edu (amber.ccs.neu.edu [129.10.111.100]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id FAA13586 for ; Wed, 13 Nov 1996 05:59:23 -0800 (PST) Received: from k2.ccs.neu.edu (root@k2.ccs.neu.edu [129.10.112.116]) by amber.ccs.neu.edu (8.7.5/8.7.3) with ESMTP id IAA14491; Wed, 13 Nov 1996 08:59:36 -0500 (EST) Received: from localhost.ccs.neu.edu (thigpen@localhost.ccs.neu.edu [127.0.0.1]) by k2.ccs.neu.edu (8.7.5/8.6.4) with SMTP id IAA28689; Wed, 13 Nov 1996 08:59:35 -0500 (EST) Message-Id: <199611131359.IAA28689@k2.ccs.neu.edu> X-Authentication-Warning: k2.ccs.neu.edu: Host thigpen@localhost.ccs.neu.edu [127.0.0.1] didn't use HELO protocol To: Robert Byers cc: majordomo-users@greatcircle.com Subject: Re: The amazing shrinking subscriber list! In-reply-to: bob's message of Thu, 24 Oct 1996 20:28:17 -0400. X-face: )MW=NXLO6sTwb%nID[Y@9n][Y,nom#u2~RwbK++HC_A6BuAlqSYAhL2DCb"kZ7!"3{UNt9T px#FEDTvs{\[+9V2^=sI!(,!p[ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Nov 1996 08:59:33 -0500 From: Hank Hughes Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk } Over the last several weeks my MJ list included ~570 subscribers. } Yesterday I happened to look at the list and it was down to only 18 } subscribers. I quick scan of the Log file (which hasn't been flushed) } reveals only 54 UN-subscribe requests. } } Folks, unless my math skills fail me, 570 - 54 does NOT equal 18 !!! } } That's when that all-too-common sinking feeling hit my gut :( } } Now, after many hours of restoring the original list, I have a few } moments to think about what happened. } } I have to admit, I don't have much of a clue. } } The most likely culprit, I would say, is a panic crash our server } sufferred on three occasions over the last month. Perhaps the subscriber } list was open for writing at an inopportune moment. } } However, I would appreciate any input from list members. Has anyone } experienced this problem with MJ? } } Or, has anyone seen MJ cause panic crashes on SunOS 4.1.3? [we never did } identify what caused those crashes] } } } My vital stats are: } } MJ 1.93 } SunOS 4.1.3 } perl 4.0.1.8 pl36 Is it possible that the disk that the majordomo subscription lists are on had filled? Some role-playing: If the disk is full, you append to it (someone subsribes), the list is now zero-length since the disk filled, and then 18 more people subscribe afterward leaving you with a list of 18 people. Just offering alternatives, -Hank From majordomo-users-owner Wed Nov 13 16:54:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA15003 for majordomo-users-outgoing; Wed, 13 Nov 1996 15:42:05 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA14931 for majordomo-users@greatcircle.com; Wed, 13 Nov 1996 15:41:42 -0800 (PST) Received: from antares.pegasus.com.br (antares.pegasus.com.br [200.251.120.50]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA27452 for ; Mon, 11 Nov 1996 08:50:09 -0800 (PST) Received: from Mizar.INTERMAIL (algol.pegasus.com.br [200.251.120.35]) by antares.pegasus.com.br (8.6.12/8.6.9) with SMTP id NAA05361 for ; Mon, 11 Nov 1996 13:42:43 -0300 Message-ID: <328759A3.1C47@pegasus.com.br> Date: Mon, 11 Nov 1996 14:51:47 -0200 From: Frederico Ferreira da Silva Reply-To: fred@pegasus.com.br Organization: InterMail Ltda X-Mailer: Mozilla 3.01b1 (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Re: Can't unsubscribe from test list References: <3280878A.370E@pegasus.com.br> <199611111633.LAA07329@augusta.math.psu.edu> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Dave Barr wrote: > > In message <3280878A.370E@pegasus.com.br>, Frederico Ferreira da Silva writes: > >I'm using Majordomo 1.94 on an Linux. I have created a test list and > >can 'subscribe', 'who list', 'lists' but cannot 'unsubscribe' from it. > >The message I get back as the issuer of unsubscribe is: > >>>>> unsubscribe test fred@antares.pegasus.com.br > > > >The message I get back as the owner of the mailing list is: > >MAJORDOMO ABORT > > > >Can't open /majordomo/lists/test.new: Permission denied > > What does ./wrapper config-test say? > > Try reading the FAQ, question 2.1. > > --Dave --------------------- Obvious things: --------------------- ------------------ environment variables ------------------ HOME=/server/majordomo-1.94 LOGNAME=root MAJORDOMO_CF=/server/majordomo-1.94/majordomo.cf PATH=/bin:/usr/bin:/usr/ucb SHELL=/bin/csh USER=root --------------------- euid/egid checks --------------------- effective user = majordomo (uid 443) effective group = daemon floppy wheel disk adm sys daemon bin root (gid 2 11 10 6 4 3 2 1 0 ) ---------------------- uid/gid checks ---------------------- real user = majordomo (uid 443) real group = daemon floppy wheel disk adm sys daemon bin root (gid 2 11 10 6 4 3 2 1 0 ) ----------------------------- ----------------------------- Non obvious things that cause headaches: ----------------------------- ----------------------------- Good: "require"d /server/majordomo-1.94/majordomo.cf okay. Good: found ctime.pl okay. Good: found majordomo_version.pl okay. Good: found majordomo.pl okay. Good: found shlock.pl okay. Good: found config_parse.pl okay. You're running Majordomo Version 1.94. --==> Majordomo home directory is /server/majordomo-1.94. ------------------- Include directories ------------------- /server/majordomo-1.94 /usr/lib/perl5/i586-linux /usr/lib/perl5 . --------------------------- Home --------------------------- Good: changedir to /server/majordomo-1.94 succeeded. Good: Created a mock lock file. ---------------------- temp directory ---------------------- Good: Created a temp file in $TMPDIR (/usr/tmp). ---------------------- list directory ---------------------- Good: list directory /server/majordomo-1.94/lists has good permissions. --------------------------- log --------------------------- Good: logfile /server/majordomo-1.94/Log exists and is writeable. ------------------------- Mailers ------------------------- You have defined a mailer for delivery. Attempting to verify that this is a valid mailer...looks okay. You have defined a mailer for delivering administrative messages. Attempting to verify that this is a valid mailer...looks okay. ------------------ Checking majordomo.cf ------------------ Checking to see if there are new variables that should be in your majordomo.cf file...Nope, none that I see. ----------------------- end of tests ----------------------- Nothing bad found! Majordomo _should_ work correctly. If it doesn't, check your configuration file (/server/majordomo-1.94/majordomo.cf) closely, and if it still looks okay, consider asking the majordomo-users mailing list at "majordomo-users@greatcircle.com" for assistance. Be sure and fully specify what your problems are, and what type of machine (and operating system) you are using. Enjoy! Any help is Well come!!! []'s Fred. -- +-----------------------------------------------------+ | Frederico F. da Silva e-mail: fred@pegasus.com.br | | InterMail Ltda. Rua Sta Rita Durão, 321,209 | | 30140-110 - Belo Horizonte, MG Brazil | | http://www.pegasus.com.br +55-31-281-1508 | +-----------------------------------------------------+ From majordomo-users-owner Wed Nov 13 17:32:47 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA22977 for majordomo-users-outgoing; Wed, 13 Nov 1996 17:27:08 -0800 (PST) Received: from vex.cs.colorado.edu (vex.cs.Colorado.EDU [128.138.241.27]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id RAA22968 for ; Wed, 13 Nov 1996 17:27:00 -0800 (PST) Received: from vex.cs.colorado.edu (seidl@localhost.cs.colorado.edu [127.0.0.1]) by vex.cs.colorado.edu (8.7.6/8.7.3) with ESMTP id SAA06252; Wed, 13 Nov 1996 18:27:12 -0700 (MST) Message-Id: <199611140127.SAA06252@vex.cs.colorado.edu> To: majordomo-users@greatcircle.com cc: seidl@vex.cs.colorado.edu Subject: Mail Exploders Date: Wed, 13 Nov 1996 18:27:11 -0700 From: Matthew Seidl Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I recently picked up the TLB package for doing amil exploders in majordomo, and I have one question. It mentions things that have to be set up on the remote site, i.e. the one doing the exploding, but never mentions what those things are? Help? Is there some sendmail.cf flag to set, or is it as simple as asking permission? -=- Matthew L. Seidl email: seidl@cs.colorado.edu =-= =-= Graduate Student Project . . . What Project? -=- -=- Gamer, Re-Enactor, hecka stressed We're here to make your life better!=-= =-= and trying not to be too homesick for the BA -Morrow Quotes -=- From majordomo-users-owner Wed Nov 13 17:47:15 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA22795 for majordomo-users-outgoing; Wed, 13 Nov 1996 17:25:15 -0800 (PST) Received: from tahi.tradesrv.com.au ([203.63.230.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA22778 for ; Wed, 13 Nov 1996 17:25:01 -0800 (PST) Received: from neil.tradesrv.com.au ([203.63.230.20]) by tahi.tradesrv.com.au (8.6.12/8.6.9) with SMTP id MAA24492; Thu, 14 Nov 1996 12:11:50 +1100 Message-ID: <328A6E1A.75F1@tradesrv.com.au> Date: Thu, 14 Nov 1996 11:55:54 +1100 From: Neil Cotty Reply-To: neilc@tradesrv.com.au Organization: Internet Trading Services Pty. Ltd. X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: Dave Wolfe CC: majordomo-users@greatcircle.com Subject: Re: Remote Protocol # 3 References: <199611111708.LAA11090@miaow.risc.sps.mot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Dave + MJ users, > an unqualified name, that could be a problem. What is an unqualified name ? Does it mean I need an account on my system for that list. ie Vizsla ? (list is vizsla) > Perhaps you need to escape an '@' somewhere? My MJ is installed and working (except for this problem) and I haven't escaped any of my MJ files. Is there any reference to what I exactly have to do to the MJ files and to which. I'm afraid I don't know Perl very well. Do I have to re-install MJ once I've changed the source files or can I modify the installed/executable version ? Cheers, Neil. -- Internet Trading Services Access Providers Level 1, Fayworth House Internet Database Systems 379-383 Pitt Street Client/Server Sydney, NSW 2000 Consulting Australia Phone : +61 2 264 8811 Fax: +61 2 264 8822 Modems: +61 2 264 8810 URL: http://www.tradesrv.com.au Email: neilc@tradesrv.com.au From majordomo-users-owner Wed Nov 13 18:02:06 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA24106 for majordomo-users-outgoing; Wed, 13 Nov 1996 17:35:56 -0800 (PST) Received: from tahi.tradesrv.com.au ([203.63.230.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA24079 for ; Wed, 13 Nov 1996 17:35:38 -0800 (PST) Received: from neil.tradesrv.com.au ([203.63.230.20]) by tahi.tradesrv.com.au (8.6.12/8.6.9) with SMTP id MAA24533 for ; Thu, 14 Nov 1996 12:22:41 +1100 Message-ID: <328A70A6.5A3A@tradesrv.com.au> Date: Thu, 14 Nov 1996 12:06:46 +1100 From: Neil Cotty Reply-To: neilc@tradesrv.com.au Organization: Internet Trading Services Pty. Ltd. X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: ABORT message. Content-Type: multipart/mixed; boundary="------------265E6D6B1901" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. --------------265E6D6B1901 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all, I am periodically (every day to 2 days) receiving this message from MJ. Does anybody have any advice on this one ? Cheers, Neil. -- Internet Trading Services Access Providers Level 1, Fayworth House Internet Database Systems 379-383 Pitt Street Client/Server Sydney, NSW 2000 Consulting Australia Phone : +61 2 264 8811 Fax: +61 2 264 8822 Modems: +61 2 264 8810 URL: http://www.tradesrv.com.au Email: neilc@tradesrv.com.au --------------265E6D6B1901 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-POP3-Rcpt: neilc@tahi Return-Path: owner-vizsla@tradesrv.com.au Received: (from majordom@localhost) by tahi.tradesrv.com.au (8.6.12/8.6.9) id EAA23233; Thu, 14 Nov 1996 04:26:57 +1100 Date: Thu, 14 Nov 1996 04:26:57 +1100 From: owner-vizsla@tradesrv.com.au Message-Id: <199611131726.EAA23233@tahi.tradesrv.com.au> To: owner-vizsla@tradesrv.com.au Subject: MAJORDOMO ABORT Reply-To: owner-vizsla@tradesrv.com.au -- MAJORDOMO ABORT Mailer /usr/lib/sendmail -oi -fowner-vizsla@tradesrv.com.au vizsla-outgoing exited unexpectedly with error 16384 --------------265E6D6B1901-- From majordomo-users-owner Wed Nov 13 18:17:40 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA27166 for majordomo-users-outgoing; Wed, 13 Nov 1996 18:07:44 -0800 (PST) Received: from lettuce.salinas.net (salinas.net [205.179.129.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id SAA27118 for ; Wed, 13 Nov 1996 18:07:24 -0800 (PST) Received: (from drenalin@localhost) by lettuce.salinas.net (8.6.12/8.6.9) id RAA32597; Wed, 13 Nov 1996 17:30:12 -0800 Date: Wed, 13 Nov 1996 17:30:11 -0800 (PST) From: Scott Nelson To: majordomo-users@greatcircle.com Subject: Digest Indexes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've been on the list a while and I haven't seen anyone ask about it. I have a couple of lists on my machine and they have digest running fine. I've been looking for a script or code chunk that will index the messages of the digest and insert it in the header. I could of course do this in perl, but thought I'd ask before I go about reinventing the wheel. Thanks Scott Nelson --------------------------------------------------------------- Scott Nelson - drenalin@cloudfactory.org SalinasNet - admin@salinas.net http://www.salinas.net/ The WebWorks - webmaster@webworks.org http://www.webworks.org/ hyperreal - drenalin@hyperreal.com http://www.hyperreal.com/ --------------------------------------------------------------- From majordomo-users-owner Wed Nov 13 20:01:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA06903 for majordomo-users-outgoing; Wed, 13 Nov 1996 19:53:14 -0800 (PST) Received: from mail.his.com (mail.his.com [205.177.25.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id TAA06896 for ; Wed, 13 Nov 1996 19:52:57 -0800 (PST) Received: from [205.177.25.164] (kendall.his.com [205.177.25.164]) by mail.his.com (8.6.9/8.6.12) with ESMTP id WAA22255; Wed, 13 Nov 1996 22:52:52 -0500 Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 13 Nov 1996 22:52:56 -0500 To: Jim Dawson From: "Kendall P Bullen" Subject: Re: Finishing installation of Majordomo Cc: majordomo-users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 12:31 PM -0800 11/13/96, Jim Dawson wrote: >Did you run newaliases after changing /etc/aliases? Dave Wolfe's message was the first I'd heard of it. :) Thanks to him and to you. It worked fine without newaliases...I presume it's some performance enhancing thing (I have no man page for newaliases, so I just ran it blind). It was useful -- it told me about duplicate aliases. Kendall -- Kendall P. Bullen E-mail: kendall@his.com Web: http://www.his.com/~kendall/ From majordomo-users-owner Wed Nov 13 20:47:44 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA08606 for majordomo-users-outgoing; Wed, 13 Nov 1996 20:44:52 -0800 (PST) Received: from funny.things.org (accs06-3.ttu.edu [129.118.9.83]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id UAA08595 for ; Wed, 13 Nov 1996 20:44:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by funny.things.org (8.7.4/8.7.3) with SMTP id WAA06386 for ; Wed, 13 Nov 1996 22:45:21 -0600 X-Authentication-Warning: `cat: Host localhost [127.0.0.1] didn't use HELO protocol Message-ID: <328AA3E0.355AEFFB@ttu.edu> Date: Wed, 13 Nov 1996 22:45:20 -0600 From: taylor cc X-Mailer: Mozilla 3.0 (X11; I; Linux 1.2.13 i586) MIME-Version: 1.0 To: majordomo users Subject: sendmail error??? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk hello I recently installed majordomo and everything seemed to work until I tried to mail from a remote host. I got a internal mail error. errr here it is (I guess my sendmail is configured wrong). oh yeh.... I am running Linux 1.2.13 RedHat "Picasso", connected to the net via ppp. **** error email recieved ******** The original message was received at Wed, 13 Nov 1996 22:39:18 -0600 from tomserver.phys.ttu.edu [129.118.41.33] ----- The following addresses have delivery notifications ----- (unrecoverable error) ----- Transcript of session follows ----- 553 accs06-3.ttu.edu. config error: mail loops back to me (MX problem?) 554 ... Local configuration error [ Part 2: "Included Message" ] Reporting-MTA: dns; funny.things.org Received-From-MTA: DNS; tomserver.phys.ttu.edu Arrival-Date: Wed, 13 Nov 1996 22:39:18 -0600 Final-Recipient: RFC822; zeus@accs06-3.ttu.edu Action: failed Status: 5.5.0 Remote-MTA: DNS; accs06-3.ttu.edu Last-Attempt-Date: Wed, 13 Nov 1996 22:39:20 -0600 [ Part 3: "Included Message" ] Date: Wed, 13 Nov 1996 22:42:21 -0600 From: "Taylor C. Carpenter" hhithere From majordomo-users-owner Wed Nov 13 21:16:57 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA10164 for majordomo-users-outgoing; Wed, 13 Nov 1996 21:13:27 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id VAA10148 for ; Wed, 13 Nov 1996 21:13:15 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id XAA18794; Wed, 13 Nov 1996 23:13:21 -0600 (CST) To: greg.harrison@analog.com (greg harrison) Cc: majordomo-users@GreatCircle.COM Subject: Re: Help with errors References: <9611121535.AA10428@sarah> From: Jason L Tibbitts III Date: 13 Nov 1996 23:13:20 -0600 In-Reply-To: greg.harrison@analog.com's message of Tue, 12 Nov 96 10:35:15 EST Message-ID: Lines: 19 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "gh" == greg harrison writes: gh> Can anyone tell me what the following errors mean, or where I can look gh> them up (maybe there is a listing of all of the error numbers gh> somewhere?)? The error list is generally /usr/include/sysexits.h. You divide these numbers by 256 to get the proper values. I'll save you the trouble: 18176 = 256 * 71 = EX_OSERR /* system error (e.g., can't fork) */ 17920 = 256 * 70 = EX_SOFTWARE /* internal software error */ As for why Sendmail would be generating these, first check the debug logs ($TMPDIR/*.debug) and also check your sendmail configuration. Dave, we really need a FAQ entry for this kind of debugging. - J< From majordomo-users-owner Wed Nov 13 21:23:53 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA09987 for majordomo-users-outgoing; Wed, 13 Nov 1996 21:09:55 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id VAA09936 for ; Wed, 13 Nov 1996 21:09:27 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id XAA18656; Wed, 13 Nov 1996 23:09:37 -0600 (CST) To: Matthew Seidl Cc: majordomo-users@GreatCircle.COM Subject: Re: Mail Exploders References: <199611140127.SAA06252@vex.cs.colorado.edu> From: Jason L Tibbitts III Date: 13 Nov 1996 23:09:37 -0600 In-Reply-To: Matthew Seidl's message of Wed, 13 Nov 1996 18:27:11 -0700 Message-ID: Lines: 25 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "MS" == Matthew Seidl writes: MS> I recently picked up the TLB package for doing amil exploders in MS> majordomo, and I have one question. You should send TLB questions to me. I will start a mailing list if there is interest, but so far I haven't seen much of a need. MS> It mentions things that have to be set up on the remote site, i.e. the MS> one doing the exploding, but never mentions what those things are? MS> Help? Well, that depends on what software they're using, and since I haven't seen it all I can't really say what it is. Until sendmail 8.8 most of the relay prevention methods have been of the "local hack" variety, so no general information would do anyway. The best advise is to open a dialog with the remote site. If they have the security measures in place, they will know how to disable them for your site. If they don't have them in place, then their approval is a good start. I am interested in how you intend to use the remote exploder features. - J< From majordomo-users-owner Wed Nov 13 21:47:09 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA12711 for majordomo-users-outgoing; Wed, 13 Nov 1996 21:43:13 -0800 (PST) Received: from novell.com (prv-mail20.Provo.Novell.COM [137.65.40.4]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id VAA12699 for ; Wed, 13 Nov 1996 21:43:03 -0800 (PST) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Wed, 13 Nov 1996 22:43:16 -0700 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 13 Nov 1996 22:39:51 -0700 From: Brian Christensen To: majordomo-users@GreatCircle.com Subject: Filtering messages Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk ** Reply Requested When Convenient ** The following question is probably answered in one of the FAQs or list archives, but I'm not on a system right now that has an Internet connection, so I'm going to ask the knowledgeable people on this list- :-) Is there a way to automatically filter messages before they get sent to the mailing lists? I'll give an example of my situation and why I need a filter. I have a list called prem-info that sends out product information to premium customers. I have another list called cert-info that sends the same product information to certified product engineers. To make things easy, I have subscribed the cert-info list to the prem-info list so any information that goes to the prem-info list also goes to the cert-info list. But now some of the postings to the prem-info list are designated as Confidential, and we don't want the Confidential information going to the cert-info list. So I'm trying to find a way that I can filter Confidential postings so they don't go to the cert-info group, but all other postings do. Is there a command or mechanism available that will facilitate this for me? Thanks, Brian Christensen From majordomo-users-owner Wed Nov 13 22:02:01 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA14191 for majordomo-users-outgoing; Wed, 13 Nov 1996 21:59:00 -0800 (PST) Received: from goliat.eik.bme.hu (goliat.eik.bme.hu [152.66.250.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id VAA14152 for ; Wed, 13 Nov 1996 21:58:36 -0800 (PST) Received: from line7.dial.bme.hu (line7.dial.bme.hu [152.66.142.7]) by goliat.eik.bme.hu (8.8.2/8.8.2) with SMTP id GAA00009 for ; Thu, 14 Nov 1996 06:58:42 +0100 (MET) Message-Id: <199611140558.GAA00009@goliat.eik.bme.hu> From: "Amby" To: "s" Date: Thu, 14 Nov 96 06:59:09 +0100 Reply-To: "Amby" X-Mailer: Ambrozy Gabor's Registered PMMail 1.53 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Subject: Reply-to, digest Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi! I have 2 problems. First: there was a majordomo change in the last few days, and the headers contain wrong reply-to field. This means, that every reply goes to the writer, not to the list. The main problem, that in the config, the reply-to line has been set! The second problem: How to wrap the digest generated by majordomo? The "usual" digest formatters cannot handle majordomo's archives. Any tip? Amby (Ambrozy Gabor) -- Proud member of Team OS/2 Hungary ***Greetings from a 1100 year old country!*** From majordomo-users-owner Thu Nov 14 00:17:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id AAA22533 for majordomo-users-outgoing; Thu, 14 Nov 1996 00:04:09 -0800 (PST) Received: from ub4b.eunet.be (ub4b.eunet.be [192.92.130.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id AAA22518 for ; Thu, 14 Nov 1996 00:03:40 -0800 (PST) Received: from gate_e1.eurocontrol.be (gate.eurocontrol.be) by ub4b.eunet.be (ub4b_08) id AA12547; Thu, 14 Nov 1996 09:03:39 +0100 Received: (from uucp@localhost) by gate_e1.eurocontrol.be (8.7.1/8.7.1) id JAA02985; Thu, 14 Nov 1996 09:05:40 +0100 (MET) Received: from biscuit.eurocontrol.be(193.221.170.179) by gate_e1.eurocontrol.be via smap (V1.3) id sma002976; Thu Nov 14 09:05:12 1996 Received: from ir6mws15.mas.eurocontrol.be by biscuit.eurocontrol.be with SMTP (1.37.109.18/16.2) id AA256628648; Thu, 14 Nov 1996 09:04:08 +0100 Received: from masadm1b.mas.eurocontrol.be by ir6mws15.mas.eurocontrol.be (AIX 3.2/UCB 5.64/4.03) id AA25023; Thu, 14 Nov 1996 09:58:58 GMT Received: by masadm1.mas.eurocontrol.be (AIX 3.2/UCB 5.64/4.03) id AA63609; Thu, 14 Nov 1996 08:06:45 GMT Date: Thu, 14 Nov 1996 08:06:44 +0000 (CUT) From: Alan Buck Reply-To: Alan.Buck@eurocontrol.be To: zach@crest.org Cc: majordomo-users@GreatCircle.COM Subject: Perl 5.0001m Message-Id: Return_Receipt_To: Alan.Buck@eurocontrol.be Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Zach, we're using Perl 5.0001m for majordomo, and lots of other applications, and it works fine and appears to be complete. Cheers, Alan ----------------------------------------------------------- Alan Buck: Eurocontrol, Maastricht UAC; Brussels HQ Telephone: work: +31 (0)43-3661461; +32 2 7293653 home: +31 (0)35 6024594 Fax: work +31 (0)43-3661300; +32 2 7299066 email: work Alan.Buck@eurocontrol.be home Alan.Buck@inter.nl.net ----------------------------------------------------------- From majordomo-users-owner Thu Nov 14 03:02:14 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id CAA29836 for majordomo-users-outgoing; Thu, 14 Nov 1996 02:28:51 -0800 (PST) Received: from gatekeeper.msi-uk.com (gatekeeper.msi-uk.com [194.131.97.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id CAA29773 for ; Thu, 14 Nov 1996 02:28:13 -0800 (PST) Received: by gatekeeper.msi-uk.com; id KAA00969; Thu, 14 Nov 1996 10:17:09 GMT Received: from purple.msi-uk.com(192.240.0.144) by gatekeeper.msi-uk.com via smap (V1.3) id sma000965; Thu Nov 14 10:16:58 1996 Received: from scimitar.msi-uk.com by msi-uk.com (SMI-8.6/SMI-SVR4) id KAA00799; Thu, 14 Nov 1996 10:29:09 GMT Received: by scimitar.msi-uk.com (SMI-8.6/SMI-SVR4) id KAA19000; Thu, 14 Nov 1996 10:28:54 GMT Date: Thu, 14 Nov 1996 10:28:54 GMT From: tonycl@msi-uk.com (Tony Clark) Message-Id: <199611141028.KAA19000@scimitar.msi-uk.com> To: Majordomo-Users@greatcircle.com Subject: ./wrapper problem error=2 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk when i run this wrapper it complains about:- $./wrapper config-test ld.so.1: /usr/local/perl-4.36/bin/perl: fatal: libucb.so.1: can't open file: errno=2 Killed even if i run wrapper on a simple perl program (ie: print("test";)) $./wrapper tony.pl ld.so.1: /usr/local/perl-4.36/bin/perl: fatal: libucb.so.1: can't open file: err no=2 Killed what is causing this ? From majordomo-users-owner Thu Nov 14 05:02:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id EAA05412 for majordomo-users-outgoing; Thu, 14 Nov 1996 04:47:57 -0800 (PST) Received: from anjinho (anjinho.dsc.ufpb.br [150.165.2.21]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id EAA05301 for ; Thu, 14 Nov 1996 04:47:10 -0800 (PST) Received: from zevampir.dsc.ufpb.br (zevampir.dsc.ufpb.br [150.165.2.20]) by anjinho (8.7.5/8.7.3) with SMTP id JAA18172 for ; Thu, 14 Nov 1996 09:42:05 -0400 Received: by zevampir.dsc.ufpb.br (5.x/SMI-SVR4) id AA01952; Thu, 14 Nov 1996 09:53:15 -0200 Date: Thu, 14 Nov 1996 09:53:15 -0200 (EDT) From: Fellipe Araujo Aleixo X-Sender: fellipe@zevampir To: majordomo-users@GreatCircle.com Subject: Re: Finishing installation of Majordomo In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Sorry all, But here is the original message: On Wed, 13 Nov 1996, Fellipe Araujo Aleixo wrote: > > Hi Folks, > > Somebody could help me? > > I finished all steps to the installation of the Majordomo 1.94, i > tested it with the "wrapper config-test", and it work ok. > > But when i was testing sending an e-mail to majordomo the following > error happen to me: > > > ******Begin of test > > [anjinho] root# sendmail -v majordomo > majordomo... aliased to "| > /usr/local/share/src/majordomo-1.94/wrapper majordom" > lists > . > "| /usr/local/share/src/majordomo-1.94/wrapper majordomo"... > Connecting to prog.. > sh: wrapper not available for sendmail programs > "| /usr/local/share/src/majordomo-1.94/wrapper majordomo"... Service > unavailable > majordom... Connecting to local... > majordom... Sent > [anjinho] root# > > ******End of test > > > And this is part of the mail recived by mojordom: > > ******Begin part of the e-mail > > ----- The following addresses have delivery notifications ----- > "| /usr/local/share/src/majordomo-1.94/wrapper majordomo" (unrecoverable > error) > (expanded from: majordomo) > > > ----- Transcript of session follows ----- > Message delivered to mailing list majordomo > 554 "| /usr/local/share/src/majordomo-1.94/wrapper majordomo"... Service > unavailable > > > [ Part 2: "Included Message" ] > > Reporting-MTA: dns; anjinho.dsc.ufpb.br > Arrival-Date: Wed, 13 Nov 1996 09:03:33 -0400 > > Final-Recipient: RFC822; majordomo@anjinho.dsc.ufpb.br > Action: delivered (to mailing list) > Status: 2.0.0 > Last-Attempt-Date: Wed, 13 Nov 1996 09:03:45 -0400 > > Final-Recipient: RFC822; majordomo@anjinho.dsc.ufpb.br > X-Actual-Recipient: RFC822; | /usr/local/share/src/majordomo-1.94/wrapper > majordomo@anjinho.dsc.ufpb.br > Action: failed > Status: 5.5.0 > Last-Attempt-Date: Wed, 13 Nov 1996 09:03:45 -0400 > > *********End part the of e-mail > > Sorry all for the long mail, ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>< >< Fellipe Araujo Aleixo - LABCOM/DSC/UFPB >< >< (Estagio Supervisionado) >< >< http://www.dsc.ufpb.br/~fellipe >< >< fellipe@dsc.ufpb.br >< >< Fone: 331-1808 >;-) >< ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>< From majordomo-users-owner Thu Nov 14 05:32:43 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA06539 for majordomo-users-outgoing; Thu, 14 Nov 1996 05:24:02 -0800 (PST) Received: from apollo.it.hq.nasa.gov (apollo.it.hq.nasa.gov [131.182.119.87]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id FAA06530 for ; Thu, 14 Nov 1996 05:23:50 -0800 (PST) Received: from wirehead.it.hq.nasa.gov (WireHead.it.hq.nasa.gov [131.182.119.88]) by apollo.it.hq.nasa.gov (8.6.12/8.6.12) with ESMTP id NAA26082; Thu, 14 Nov 1996 13:24:27 GMT Received: from localhost (cshenton@localhost) by wirehead.it.hq.nasa.gov (8.6.12/8.6.12) with SMTP id NAA22673; Thu, 14 Nov 1996 13:23:38 GMT Message-Id: <199611141323.NAA22673@wirehead.it.hq.nasa.gov> X-Authentication-Warning: wirehead.it.hq.nasa.gov: cshenton owned process doing -bs X-Authentication-Warning: wirehead.it.hq.nasa.gov: Host localhost didn't use HELO protocol To: evanc@synapse.net Cc: majordomo-users@greatcircle.com Subject: Re: Preventing spam via *-outgoing alias? In-Reply-To: Your message of "Wed, 13 Nov 1996 12:10:16 -0500 (EST)" References: X-Mailer: Mew version 1.03 on Emacs 19.31.8 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 14 Nov 1996 08:23:38 -0500 From: Chris Shenton Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thanks! From majordomo-users-owner Thu Nov 14 06:03:58 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA08453 for majordomo-users-outgoing; Thu, 14 Nov 1996 05:55:58 -0800 (PST) Received: from ns1.fni.com (ns1.fni.com [204.181.104.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id FAA08425 for ; Thu, 14 Nov 1996 05:55:32 -0800 (PST) Received: from ns1.fni.com (ns1.fni.com [204.181.104.1]) by ns1.fni.com (8.7.6/8.7.3) with SMTP id HAA10983; Thu, 14 Nov 1996 07:55:07 -0600 Date: Thu, 14 Nov 1996 07:55:07 -0600 (CST) From: Michael Brennen To: Fellipe Araujo Aleixo cc: majordomo-users@GreatCircle.COM Subject: Re: Finishing installation of Majordomo In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is /usr/local/share/src/majordomo-1.94 where you unpacked the source or where you installed the configured package? -- Michael On Thu, 14 Nov 1996, Fellipe Araujo Aleixo wrote: > > ******Begin of test > > > > [anjinho] root# sendmail -v majordomo > > majordomo... aliased to "| > > /usr/local/share/src/majordomo-1.94/wrapper majordom" > > lists > > . > > "| /usr/local/share/src/majordomo-1.94/wrapper majordomo"... > > Connecting to prog.. > > sh: wrapper not available for sendmail programs > > "| /usr/local/share/src/majordomo-1.94/wrapper majordomo"... Service > > unavailable > > majordom... Connecting to local... > > majordom... Sent > > [anjinho] root# etc. From majordomo-users-owner Thu Nov 14 06:04:35 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA07879 for majordomo-users-outgoing; Thu, 14 Nov 1996 05:46:58 -0800 (PST) Received: from mserv1.dl.ac.uk (mserv1.dl.ac.uk [148.79.160.65]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id FAA07823 for ; Thu, 14 Nov 1996 05:46:08 -0800 (PST) Received: from xserv1.dl_sun_server by mserv1.dl.ac.uk with SMTP id NAA28548 (8.6.13/5.3[ref postmaster@dl.ac.uk] for dl.ac.uk from J.F.L.Hopkinson@dl.ac.uk); Thu, 14 Nov 1996 13:31:15 GMT Date: Thu, 14 Nov 1996 13:31:15 GMT Message-Id: <199611141331.NAA28548@mserv1.dl.ac.uk> Received: by xserv1.dl_sun_server (4.1/SMI-4.1) id AA16051; Thu, 14 Nov 96 13:31:17 GMT From: "J. Hopkinson" To: majordomo-users@greatcircle.com In-Reply-To: (Dennis.Black@UAlberta.CA) Subject: Re: Superlists (Re- Duplicat Reply-To: J.F.L.Hopkinson@dl.ac.uk Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk "Dennis Black" wrote: On 11/11/96 thomasg@ifi.uio.no wrote: >Well, it doesn't work that way for me. I'm testing this now, with >two listnames in the subscriber file. List 1 has A and B as >subscribers, list 2 has A and C as subscribers. A got the message >twice. >So, can it work -- all subscribers getting the message only once, >no matter how many lists they are subscribed to? Thomas, [...] If I understand your examples correctly, List1 contains subscribers A@yoursite and B@yoursite List2 contains subscribers A@yoursite and C@yoursite What you need is a third list. Let's call it List0. List1 and List2 subscribers can stay put, but for List0, enter two subscribers: List1@yoursite List2@yoursite I don't think this will do what you want, this will pass the message to both lists and process them separately. Rather you should use: List0-outgoing: :include:/path/to/list1, :include:/path/to/list2 This way the combined lists will be passed to sendmail, which de-duplicates the recipients. [...] Clear as mud? For your other concern, I don't think 1.92 is that much different - I'm still on 1.93. --Jerry --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Jerry Hopkinson e-mail: j.hopkinson@dl.ac.uk Daresbury Laboratory Voice: (+44) 1925 603355 Warrington WA4 4AD UK Fax: (+44) 1925 603100 --- --- --- --- --- --- --- --- --- --- --- --- --- --- --96/07- From majordomo-users-owner Thu Nov 14 06:33:52 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA09969 for majordomo-users-outgoing; Thu, 14 Nov 1996 06:29:26 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA09962 for ; Thu, 14 Nov 1996 06:29:12 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA04359 for majordomo-users@GreatCircle.COM; Thu, 14 Nov 96 07:29:28 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA17505 for majordomo-users@GreatCircle.COM; Thu, 14 Nov 96 07:29:26 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id IAA20989; Thu, 14 Nov 1996 08:29:25 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id IAA11700; Thu, 14 Nov 1996 08:29:23 -0600 From: Dave Wolfe Message-Id: <199611141429.IAA11700@miaow.risc.sps.mot.com> Subject: Re: Majordomo ABORT - Can someone help? To: tpupke@quinncom.net Date: Thu, 14 Nov 1996 08:29:23 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199611111741.JAA26987@jewels.Cadence.COM> from "cadence.com!postmaster" at Nov 11, 96 09:41:33 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ uunet!cadence.com!postmaster (Julian ?) writes: ] > > chown is only allowed by the user or super-user. So what it means is that > majordomo is not running as the owner of the file, (or root) and so cannot > chown. > > [ Trace Pupke writes: ] > > > > MAJORDOMO ABORT > > > > chown(54, 2, "/usr/local/majordomo/lists/test.new"): Operation not permitted I.e. you don't have Mj, specifically wrapper, installed correctly. -- Dave Wolfe From majordomo-users-owner Thu Nov 14 07:02:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA11606 for majordomo-users-outgoing; Thu, 14 Nov 1996 06:55:26 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA11583 for ; Thu, 14 Nov 1996 06:55:06 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id JAA10371; Thu, 14 Nov 1996 09:55:19 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id JAA23946; Thu, 14 Nov 1996 09:55:16 -0500 (EST) Message-Id: <199611141455.JAA23946@augusta.math.psu.edu> To: Fellipe Araujo Aleixo cc: majordomo-users@GreatCircle.COM Subject: Re: Finishing installation of Majordomo In-reply-to: Your message of "Thu, 14 Nov 1996 09:53:15 -0200." References: 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 Nov 1996 09:55:15 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , Fellipe Araujo A leixo writes: >> "| /usr/local/share/src/majordomo-1.94/wrapper majordomo"... >> Connecting to prog.. >> sh: wrapper not available for sendmail programs See the documentation for sendmail. This is a misconfiguration of sendmail. --Dave From majordomo-users-owner Thu Nov 14 07:07:53 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA11531 for majordomo-users-outgoing; Thu, 14 Nov 1996 06:54:08 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id GAA11524 for ; Thu, 14 Nov 1996 06:53:48 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id JAA10365; Thu, 14 Nov 1996 09:53:57 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id JAA23930; Thu, 14 Nov 1996 09:53:54 -0500 (EST) Message-Id: <199611141453.JAA23930@augusta.math.psu.edu> To: tonycl@msi-uk.com (Tony Clark) cc: Majordomo-Users@GreatCircle.COM Subject: Re: ./wrapper problem error=2 In-reply-to: Your message of "Thu, 14 Nov 1996 10:28:54 GMT." <199611141028.KAA19000@scimitar.msi-uk.com> References: <199611141028.KAA19000@scimitar.msi-uk.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, 14 Nov 1996 09:53:52 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <199611141028.KAA19000@scimitar.msi-uk.com>, Tony Clark writes: > >when i run this wrapper it complains about:- > >$./wrapper config-test >ld.so.1: /usr/local/perl-4.36/bin/perl: fatal: libucb.so.1: can't open file: e >rrno=2 >Killed Are you on a Solaris box? perl should not be using libucb. I suggest you re-install the current Perl version. --Dave From majordomo-users-owner Thu Nov 14 07:12:06 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA11996 for majordomo-users-outgoing; Thu, 14 Nov 1996 07:00:35 -0800 (PST) Received: from gatekeeper.msi-uk.com (gatekeeper.msi-uk.com [194.131.97.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA11968 for ; Thu, 14 Nov 1996 07:00:18 -0800 (PST) Received: by gatekeeper.msi-uk.com; id OAA05882; Thu, 14 Nov 1996 14:48:24 GMT Received: from purple.msi-uk.com(192.240.0.144) by gatekeeper.msi-uk.com via smap (V1.3) id sma005863; Thu Nov 14 14:48:02 1996 Received: from scimitar.msi-uk.com by msi-uk.com (SMI-8.6/SMI-SVR4) id PAA09019; Thu, 14 Nov 1996 15:00:22 GMT Received: from localhost by scimitar.msi-uk.com (SMI-8.6/SMI-SVR4) id PAA21197; Thu, 14 Nov 1996 15:00:05 GMT Date: Thu, 14 Nov 1996 15:00:04 +0000 (GMT) From: Tony Clark X-Sender: tonycl@scimitar To: Dave Barr cc: Majordomo-Users@GreatCircle.COM Subject: Re: ./wrapper problem error=2 In-Reply-To: <199611141453.JAA23930@augusta.math.psu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk thanx dave - i am just as we speak recompiling perl4 with the libucb -lucb option turned off. lets see if it works now. (it took me about two hours to work his one out :) ) lets hoipe it works. --- Tony Clark On Thu, 14 Nov 1996, Dave Barr wrote: > In message <199611141028.KAA19000@scimitar.msi-uk.com>, Tony Clark writes: > > > >when i run this wrapper it complains about:- > > > >$./wrapper config-test > >ld.so.1: /usr/local/perl-4.36/bin/perl: fatal: libucb.so.1: can't open file: e > >rrno=2 > >Killed > > Are you on a Solaris box? perl should not be using libucb. I suggest you > re-install the current Perl version. > > --Dave > From majordomo-users-owner Thu Nov 14 07:40:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA12547 for majordomo-users-outgoing; Thu, 14 Nov 1996 07:08:10 -0800 (PST) Received: from mail.eunet.ch (mail.eunet.ch [146.228.10.7]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA12484 for ; Thu, 14 Nov 1996 07:07:19 -0800 (PST) Received: from bellatrix by mail.eunet.ch (8.8.2/1.34) id PAA02580; Thu, 14 Nov 1996 15:07:13 GMT Received: from prokyon.mathconsult.ch by bellatrix (4.1/SMI-4.1) id AA06246; Thu, 14 Nov 96 15:51:03 +0100 Received: from localhost by prokyon.mathconsult.ch (SMI-8.6/SMI-SVR4) id PAA02606; Thu, 14 Nov 1996 15:51:00 +0100 Message-Id: <199611141451.PAA02606@prokyon.mathconsult.ch> To: exmh-users@sunlabs.eng.Sun.COM, majordomo-users@GreatCircle.COM Subject: approve for exmh? X-Uri: http://www.mathconsult.ch Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Thu, 14 Nov 1996 15:51:00 +0100 From: Roman Maeder Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Does anybody have code for adding an "approve" button or menu to exmh that lets list owners and moderators generate the appropriate replies, like the majordomo "approve" program does? (That is, approve administrative requests be extracting the template line and substituting the password, and sending approved contributions with an Approved: line to the list). Roman Maeder ---------------------------------------------------------------------- Roman E. Mäder, Aryanastrasse 21, CH-8704 Herrliberg Tel: +41-1-991 6341, Fax: +41-1-991 6345, Email: maeder@mathconsult.ch ---------------------------------------------------------------------- From majordomo-users-owner Thu Nov 14 07:47:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA14994 for majordomo-users-outgoing; Thu, 14 Nov 1996 07:42:34 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA14981 for ; Thu, 14 Nov 1996 07:42:23 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA15095 for majordomo-users@GreatCircle.COM; Thu, 14 Nov 96 08:42:37 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA20514 for majordomo-users@GreatCircle.COM; Thu, 14 Nov 96 08:42:36 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA22186; Thu, 14 Nov 1996 09:42:35 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA17089; Thu, 14 Nov 1996 09:42:33 -0600 From: Dave Wolfe Message-Id: <199611141542.JAA17089@miaow.risc.sps.mot.com> Subject: Re: 1.94 resend options fail? To: tibbs@hpc.uh.edu (Jason L Tibbitts III) Date: Thu, 14 Nov 1996 09:42:32 -0600 (CST) Cc: david@lambton.on.ca, majordomo-users@GreatCircle.COM In-Reply-To: from "Jason L Tibbitts III" at Nov 13, 96 04:54:26 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Jason L Tibbitts III writes: ] > > As for the "array found..." error, I'd have to see your config file but Id > wager that you've neglected to escape an `@' symbol in a string. I'm betting there's also a mismatched quote in there somewhere. Not escaping an '@' just gets a "Literal @something now requires backslash..." message. Unbalanced quotes gets the "Array found where operator expected..." -- Dave Wolfe From majordomo-users-owner Thu Nov 14 07:48:21 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA12793 for majordomo-users-outgoing; Thu, 14 Nov 1996 07:12:10 -0800 (PST) Received: from thewall.carlson.com (firewall.carlson.com [168.97.3.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA12766 for ; Thu, 14 Nov 1996 07:11:52 -0800 (PST) Received: from thewall.carlson.com (daemon@localhost) by thewall.carlson.com (8.7.2/8.7.2) with ESMTP id IAA12274 for ; Thu, 14 Nov 1996 08:32:55 -0600 (CST) Received: from spyder.carlson.com ([168.97.1.13]) by thewall.carlson.com (8.7.2/8.7.2) with SMTP id IAA12268 for ; Thu, 14 Nov 1996 08:32:54 -0600 (CST) Received: by spyder.carlson.com with Microsoft Exchange (IMC 4.0.838.14) id <01BBD20B.FEC2C0B0@spyder.carlson.com>; Thu, 14 Nov 1996 09:12:44 -0600 Message-ID: From: "Anderson, Scott (CCI IT)" To: "'mj'" Subject: Majrodomo Duping... Date: Thu, 14 Nov 1996 09:07:00 -0600 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.838.14 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I run a mailing list of approximately 2700 people, majordomo has been working well. I have recently changed to a new service provider in the Minneapolis area and the administrator there is having a heck of a time getting majordomo working correctly. Whenever I send one message to the list, two copies are being sent out. I forwarded the FAQ to my service provider so he could read about the duplication mentioned there, however he does not think that the list size is the problem. What other things might be causing duped messages? I'm just about ready to move my account since this has been going on for a month and my subscribers are dropping off the list like flies. Any ideas? Scott From majordomo-users-owner Thu Nov 14 07:58:21 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA15081 for majordomo-users-outgoing; Thu, 14 Nov 1996 07:44:19 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA15070 for ; Thu, 14 Nov 1996 07:44:08 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA15486 for majordomo-users@greatcircle.com; Thu, 14 Nov 96 08:44:22 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA20614 for majordomo-users@greatcircle.com; Thu, 14 Nov 96 08:44:20 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA22234; Thu, 14 Nov 1996 09:44:18 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA17101; Thu, 14 Nov 1996 09:44:17 -0600 From: Dave Wolfe Message-Id: <199611141544.JAA17101@miaow.risc.sps.mot.com> Subject: Re: Does perl 5.001 unoff. patch 1m count as being better than 5.001e? To: zach@crest.org (Zach Nobel) Date: Thu, 14 Nov 1996 09:44:16 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Zach Nobel" at Nov 13, 96 05:51:15 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Zach Nobel writes: ] > > Quick question for folks in the know. I've got perl version 5.001 > Unofficial patchlevel 1m (as indicated by perl5 -v). Is this usable? Or > is 5.001e an 'official' patch where the Unoffical patch (1m) doesn't have > the requisite characteristics. 'm' is just as (un)official as 'e', but several patches better. If you're thinking of updating (and you should be), get at least 5.003. -- Dave Wolfe From majordomo-users-owner Thu Nov 14 08:33:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA18479 for majordomo-users-outgoing; Thu, 14 Nov 1996 08:25:50 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA18452 for ; Thu, 14 Nov 1996 08:25:27 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA19941 for majordomo-users@GreatCircle.COM; Thu, 14 Nov 96 09:25:42 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA22351 for majordomo-users@GreatCircle.COM; Thu, 14 Nov 96 09:25:40 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id KAA23224; Thu, 14 Nov 1996 10:25:39 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id KAA11672; Thu, 14 Nov 1996 10:25:38 -0600 From: Dave Wolfe Message-Id: <199611141625.KAA11672@miaow.risc.sps.mot.com> Subject: Re: Majrodomo Duping... To: scanderson@carlson.com (Anderson Scott) Date: Thu, 14 Nov 1996 10:25:37 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Anderson, Scott" at Nov 14, 96 09:07:00 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Anderson, Scott writes: ] > > Whenever I send one message to the list, two copies are being sent out. Maybe your ISP has the aliases messed up, but without seeing them we're only guessing. -- Dave Wolfe From majordomo-users-owner Thu Nov 14 09:12:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA20268 for majordomo-users-outgoing; Thu, 14 Nov 1996 08:50:12 -0800 (PST) Received: from galleria (www.televisual.it [195.32.0.37]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA20185 for ; Thu, 14 Nov 1996 08:49:42 -0800 (PST) Received: from telephony.televisual.it by galleria (SMI-8.6/SMI-SVR4) id RAA29828; Thu, 14 Nov 1996 17:46:19 -0800 Message-Id: <199611150146.RAA29828@galleria> Comments: Authenticated sender is From: "Cristian D'Aloisio" To: majordomo-users@greatcircle.com Date: Thu, 14 Nov 1996 17:52:22 +0000 Subject: mail loop only with moderated list Reply-to: cristian@televisual.it X-mailer: Pegasus Mail for Win32 (v2.31) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi to all from a newbie :-) I'm setting a list with magiordomo vers. 1.93. When I use an open list, i.e. any subscribed user can post text, all is ok. Now I want a moderated list, so I put yes to the list config file. The owner list receive: Date sent: Thu, 14 Nov 1996 17:15:10 -0800 From: Mailer-Daemon (Mail Delivery Subsystem) Subject: Returned mail: Local configuration error To: owner-telev-bo To: postmaster The original message was received at Thu, 14 Nov 1996 17:15:09 -0800 from root@localhost ********************************************************************* ----- The following addresses had delivery problems ----- owner-telev-bo@www.televisual.it (unrecoverable error) ----- Transcript of session follows ----- 553 galleria config error: mail loops back to myself 554 owner-telev-bo@www.televisual.it... Local configuration error Message delivered to mailing list owner-telev-bo ----- Original message follows ----- Return-Path: Received: by galleria (SMI-8.6/SMI-SVR4) id RAA29653; Thu, 14 Nov 1996 17:15:09 -0800 Date: Thu, 14 Nov 1996 17:15:09 -0800 Message-Id: <199611150115.RAA29653@galleria> To: owner-telev-bo@www.televisual.it From: owner-telev-bo@www.televisual.it Subject: BOUNCE telev-bo@www.televisual.it: Approval required content-length: 552 >From info@www.televisual.it Thu Nov 14 17:15:08 1996 Return-Path: Received: from telephony.televisual.it by galleria (SMI-8.6/SMI-SVR4) id RAA29648; Thu, 14 Nov 1996 17:15:07 -0800 Message-Id: <199611150115.RAA29648@galleria> Comments: Authenticated sender is From: "Televisual Info" To: telev-bo@televisual.it Date: Thu, 14 Nov 1996 17:21:10 +0000 Subject: test con moderator Priority: normal X-mailer: Pegasus Mail for Win32 (v2.31) content-length: 19 test with a moderator ********************************************************************* The /etc/aliases file contains: owner-owner: postmaster # # Majordomo # owner-majordomo: cristian majordomo: "|/export/majordomo/wrapper majordomo" majordom: owner-majordomo # per majordomo 1.9x Majordomo-Owner: owner-majordomo # Inizio definizione Lista telev-bo # ##################################### owner-telev-bo: cristian , nobody telev-bo: "|/export/majordomo/wrapper resend -l telev-bo -h www.televisual.it telev-bo-outgoing" telev-bo-approval: owner-telev-bo telev-bo-outgoing: :include:/export/majordomo/lists/telev-bo owner-telev-bo-outgoing: owner-telev-bo telev-bo-request: "|/export/majordomo/wrapper request-answer telev-bo" owner-telev-bo-request: owner-telev-bo # Fine definizione lista telev-bo # ######################################## Have you any tip? Bye Cristian ======================================= PC programming & system administration for Televisual s.r.l (Bologna) Italy --------------------------------------- Ufficio / Office info: (++39) (051) 247536 (++39) (051) 240299 fax cristian@televisual.it --------------------------------------- Privato / Home: (++39) (051)470286 dif1754@iperbole.bologna.it ======================================= From majordomo-users-owner Thu Nov 14 09:46:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA22852 for majordomo-users-outgoing; Thu, 14 Nov 1996 09:30:16 -0800 (PST) Received: from senie.com (senie.com [204.69.207.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA22776 for ; Thu, 14 Nov 1996 09:29:53 -0800 (PST) Received: (qmail-queue invoked from smtpd); 14 Nov 1996 17:29:59 -0000 Received: from localhost (dts@127.0.0.1) by localhost with SMTP; 14 Nov 1996 17:29:59 -0000 Date: Thu, 14 Nov 1996 12:29:59 -0500 (EST) From: Daniel Senie To: majordomo-users@greatcircle.com Subject: Qmail vs MX records Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk QMAIL seems to insist that MX records exist for domains before it'll send mail. I've noticed a very limited number of addresses which do NOT get delivered to by my system now that I'm running QMAIL. I wonder if anyone else has seen this and might know how to alter the config of qmail to allow it to find an A record if there are no MX records found. Dan --------------------------------------------------------------- Daniel Senie Internet: dan@senie.com, Daniel Senie Consulting n1jeb@senie.com http://www.senie.com Packet Radio: N1JEB@KA1SRD.MA If we suffer tamely a lawless attack upon our liberty, we encourage it, and involve others in our doom. -- Samuel Adams From majordomo-users-owner Thu Nov 14 10:32:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA22767 for majordomo-users-outgoing; Thu, 14 Nov 1996 09:29:05 -0800 (PST) Received: from gatekeeper.msi-uk.com (gatekeeper.msi-uk.com [194.131.97.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA22709 for ; Thu, 14 Nov 1996 09:28:39 -0800 (PST) Received: by gatekeeper.msi-uk.com; id RAA14412; Thu, 14 Nov 1996 17:17:36 GMT Received: from purple.msi-uk.com(192.240.0.144) by gatekeeper.msi-uk.com via smap (V1.3) id sma014404; Thu Nov 14 17:17:31 1996 Received: from scimitar.msi-uk.com by msi-uk.com (SMI-8.6/SMI-SVR4) id RAA12131; Thu, 14 Nov 1996 17:29:57 GMT Received: from localhost by scimitar.msi-uk.com (SMI-8.6/SMI-SVR4) id RAA03006; Thu, 14 Nov 1996 17:29:41 GMT Date: Thu, 14 Nov 1996 17:29:40 +0000 (GMT) From: Tony Clark X-Sender: tonycl@scimitar To: Majordomo-Users@GreatCircle.COM Subject: Re: problem with majordomo ? In-Reply-To: <199611141453.JAA23930@augusta.math.psu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk i have some earlier problems with majordomo but this one stumps me again:- Subject: MAJORDOMO ABORT -- MAJORDOMO ABORT NON-DOMAINED ADDRESS tonycl@purple from /etc/aliases lists-exec: "|/var/lists/majordomo-1.94/wrapper majordomo" lists: lists-exec@purple owner-lists: tonycl@msi-uk.com i want the majordomo to run on one machine only. (purple) majordomo works fine on purple but when emailing from other machines i get the strange email response back. any help would be greatly appericated. thanx in advance. From majordomo-users-owner Thu Nov 14 10:38:02 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA24825 for majordomo-users-outgoing; Thu, 14 Nov 1996 09:54:55 -0800 (PST) Received: from pantheon.onShore.com (pantheon.onShore.com [206.69.90.241]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA24806 for ; Thu, 14 Nov 1996 09:54:38 -0800 (PST) Received: from pantheon.onShore.com (localhost [127.0.0.1]) by pantheon.onShore.com (8.7.1/8.7.1) with ESMTP id NAA16496; Thu, 14 Nov 1996 13:02:07 -0600 Message-Id: <199611141902.NAA16496@pantheon.onShore.com> X-Mailer: exmh version 1.6.4 10/10/95 To: cristian@televisual.it cc: majordomo-users@GreatCircle.COM Subject: Re: mail loop only with moderated list In-reply-to: Your message of "Thu, 14 Nov 1996 17:52:22 GMT." <199611150146.RAA29828@galleria> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Nov 1996 13:02:07 -0600 From: "Brian W. Fitzpatrick" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk -------- I'm not certain, but the first thing I would recommend is to replace the following line: telev-bo-approval: owner-telev-bo with telev-bo-approval: cristian in your /etc/aliases ... my guess is that your particular configuration of sendmail thinks that it is trying to send mail from owner-telev-bo *to* owner-telev-bo and it is getting confused, but I could be wrong. How do you have 'MeToo' configured in sendmail? In bocca al lupo, -Fitz (PS. Se trovi il problema, manda mi un messagio con il remedio... vorrei sapere la causa). ___________________________________________________________________________ Brian W. Fitzpatrick http://www.onShore.com/ Systems Administrator bwf@onShore.com Programmer > Hi to all from a newbie :-) > > I'm setting a list with magiordomo vers. 1.93. > When I use an open list, i.e. any subscribed user can post text, > all is ok. > Now I want a moderated list, so I put yes to the list config file. > > The owner list receive: > > Date sent: Thu, 14 Nov 1996 17:15:10 -0800 > >From: Mailer-Daemon (Mail Delivery Subsystem) > Subject: Returned mail: Local configuration error > To: owner-telev-bo > To: postmaster > > The original message was received at Thu, 14 Nov 1996 17:15:09 -0800 > from root@localhost > ********************************************************************* > > ----- The following addresses had delivery problems ----- > owner-telev-bo@www.televisual.it (unrecoverable error) > > ----- Transcript of session follows ----- > 553 galleria config error: mail loops back to myself > 554 owner-telev-bo@www.televisual.it... Local configuration error > Message delivered to mailing list owner-telev-bo > > ----- Original message follows ----- > Return-Path: > Received: by galleria (SMI-8.6/SMI-SVR4) > id RAA29653; Thu, 14 Nov 1996 17:15:09 -0800 > Date: Thu, 14 Nov 1996 17:15:09 -0800 > Message-Id: <199611150115.RAA29653@galleria> > To: owner-telev-bo@www.televisual.it > >From: owner-telev-bo@www.televisual.it > Subject: BOUNCE telev-bo@www.televisual.it: Approval required > content-length: 552 > > >From info@www.televisual.it Thu Nov 14 17:15:08 1996 > Return-Path: > Received: from telephony.televisual.it by galleria (SMI-8.6/SMI-SVR4) > id RAA29648; Thu, 14 Nov 1996 17:15:07 -0800 > Message-Id: <199611150115.RAA29648@galleria> > Comments: Authenticated sender is > >From: "Televisual Info" > To: telev-bo@televisual.it > Date: Thu, 14 Nov 1996 17:21:10 +0000 > Subject: test con moderator > Priority: normal > X-mailer: Pegasus Mail for Win32 (v2.31) > content-length: 19 > > test with a moderator > > ********************************************************************* > > The /etc/aliases file contains: > > owner-owner: postmaster > # > # Majordomo > # > owner-majordomo: cristian > majordomo: "|/export/majordomo/wrapper majordomo" > > > majordom: owner-majordomo > # per majordomo 1.9x > Majordomo-Owner: owner-majordomo > > # Inizio definizione Lista telev-bo > # ##################################### > owner-telev-bo: cristian , nobody > telev-bo: "|/export/majordomo/wrapper resend -l telev-bo > -h www.televisual.it telev-bo-outgoing" > telev-bo-approval: owner-telev-bo > telev-bo-outgoing: > :include:/export/majordomo/lists/telev-bo > owner-telev-bo-outgoing: owner-telev-bo > telev-bo-request: > "|/export/majordomo/wrapper request-answer telev-bo" > owner-telev-bo-request: owner-telev-bo > # Fine definizione lista telev-bo > # ######################################## > > > > Have you any tip? > > Bye > Cristian > > > > ======================================= > PC programming & system administration > for > Televisual s.r.l (Bologna) Italy > --------------------------------------- > Ufficio / Office info: > (++39) (051) 247536 > (++39) (051) 240299 fax > cristian@televisual.it > --------------------------------------- > Privato / Home: > (++39) (051)470286 > dif1754@iperbole.bologna.it > ======================================= From majordomo-users-owner Thu Nov 14 16:47:10 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA26623 for majordomo-users-outgoing; Thu, 14 Nov 1996 16:28:46 -0800 (PST) Received: from rc.trw.com (picard.rc.trw.com [129.193.136.200]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id QAA26587 for ; Thu, 14 Nov 1996 16:28:15 -0800 (PST) Received: from starbase.rc.trw.com by rc.trw.com (4.1/SMI-4.1) id AA28417; Thu, 14 Nov 96 16:28:41 PST Received: from starbase.rc.trw.com at Thu, 14 Nov 1996 16:25:10 -0800 Posted-Date: Thu, 14 Nov 1996 16:26:25 -0800 Received: by blaze.rc_eng (SMI-8.6/SMI-SVR4) id QAA29686; Thu, 14 Nov 1996 16:26:25 -0800 Date: Thu, 14 Nov 1996 16:26:25 -0800 From: moran@rc.trw.com (Derek Moran) Message-Id: <199611150026.QAA29686@blaze.rc_eng> To: majordomo-users@greatcircle.com Subject: Majordomo abort (help...) Cc: derek_moran@rc.trw.com Mime-Version: 1.0 Content-Type: multipart/mixed;boundary=5a90_13bc-2be5_2c58-58b3_3374 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk --5a90_13bc-2be5_2c58-58b3_3374 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: /qlAuSR/kiuuKCBuBQ+Meg== X-Sun-Data-Type: text Hello, I unsure as to why I am receiving an ABORT from Majordomo. Please see attachments for details. Thanks, -Derek Moran --5a90_13bc-2be5_2c58-58b3_3374 Content-Type: application/octet-stream Content-Transfer-Encoding: 7bit Content-MD5: ENlO+CiS93ll3y/Rrs0LsA== Content-Description: md.out --------------------- Obvious things: --------------------- ------------------ environment variables ------------------ HOME=/usr/local/majordomo-1.94 LOGNAME=majordomo MAJORDOMO_CF=/usr/local/majordomo-1.94/majordomo.cf PATH=/bin:/usr/bin:/usr/ucb SHELL=/bin/csh USER=majordomo --------------------- euid/egid checks --------------------- effective user = majordomo (uid 111) effective group = daemon daemon (gid 1 1 ) ---------------------- uid/gid checks ---------------------- real user = majordomo (uid 111) real group = daemon daemon (gid 1 1 ) ----------------------------- ----------------------------- Non obvious things that cause headaches: ----------------------------- ----------------------------- Good: "require"d /usr/local/majordomo-1.94/majordomo.cf okay. Good: found ctime.pl okay. Good: found majordomo_version.pl okay. Good: found majordomo.pl okay. Good: found shlock.pl okay. Good: found config_parse.pl okay. You're running Majordomo Version 1.94. --==> Majordomo home directory is /usr/local/majordomo-1.94. ------------------- Include directories ------------------- /usr/local/majordomo-1.94 /usr/local/lib/perl5/sun4-sunos/5.003 /usr/local/lib/perl5 /usr/local/lib/perl5/site_perl/sun4-sunos /usr/local/lib/perl5/site_perl . --------------------------- Home --------------------------- Good: changedir to /usr/local/majordomo-1.94 succeeded. Good: Created a mock lock file. ---------------------- temp directory ---------------------- Good: Created a temp file in $TMPDIR (/usr/tmp). ---------------------- list directory ---------------------- Good: list directory /usr/local/majordomo-1.94/lists has good permissions. --------------------------- log --------------------------- Good: logfile /usr/local/majordomo-1.94/Log exists and is writeable. ------------------------- Mailers ------------------------- You have defined a mailer for delivery. Attempting to verify that this is a valid mailer...looks okay. You have defined a mailer for delivering administrative messages. Attempting to verify that this is a valid mailer...looks okay. ------------------ Checking majordomo.cf ------------------ Checking to see if there are new variables that should be in your majordomo.cf file...Nope, none that I see. ----------------------- end of tests ----------------------- Nothing bad found! Majordomo _should_ work correctly. If it doesn't, check your configuration file (/usr/local/majordomo-1.94/majordomo.cf) closely, and if it still looks okay, consider asking the majordomo-users mailing list at "majordomo-users@greatcircle.com" for assistance. Be sure and fully specify what your problems are, and what type of machine (and operating system) you are using. Enjoy! --5a90_13bc-2be5_2c58-58b3_3374 Content-Type: application/octet-stream Content-Transfer-Encoding: 7bit Content-MD5: 4PLDktdmHoRMpU0BIJLl8Q== Content-Description: ABORT >From UNKNOWN Posted-Date: Thu, 14 Nov 96 16:11:42 PST Date: Thu, 14 Nov 96 16:11:42 PST Message-Id: <9611150011.AA23138@rc.trw.com> To: sysadm@rc.trw.com From: Majordomo@rc.trw.com Subject: MAJORDOMO ABORT Reply-To: Majordomo@rc.trw.com Status: RO -- MAJORDOMO ABORT While running with an effective uid of 1 and an effective gid of 1 1, Majordomo ran into the following problems: Unable to write to list directory $listdir, check permissions on /usr/local/majordomo-1.94/lists --5a90_13bc-2be5_2c58-58b3_3374-- From majordomo-users-owner Thu Nov 14 17:18:06 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA29675 for majordomo-users-outgoing; Thu, 14 Nov 1996 17:14:40 -0800 (PST) Received: from ponder (ponder.csci.unt.edu [129.120.3.16]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA29523 for ; Thu, 14 Nov 1996 17:12:45 -0800 (PST) Received: by ponder (5.61/1.36) id AA17140; Thu, 14 Nov 96 19:13:22 -0600 From: sshamim@ponder.csci.unt.edu (Syed Faraz Shamim) Message-Id: <9611150113.AA17140@ponder> Subject: Re: Majordomo abort (help...) To: majordomo-users@greatcircle.com Date: Thu, 14 Nov 1996 19:13:21 -0600 (CST) In-Reply-To: <199611150026.QAA29686@blaze.rc_eng> from "Derek Moran" at Nov 14, 96 04:26:25 pm X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk IN REPLY TO Derek Moran MAIL > > > MAJORDOMO ABORT > > While running with an effective uid of 1 and an effective gid of 1 1, Majordomo > ran into the following problems: > Unable to write to list directory $listdir, check permissions on > /usr/local/majordomo-1.94/lists > > > > Awww.. I think you must be running it under FreeBSD system.. whoever is a subscriber of majordomo-workers should let them know about it that there is no documentation for running majordomo under FreeBSD. or may be I am wrong . may be its the 'sendmail' that is causing this problem.. anyway the solution for this problem is change the majordomo dir. ownership to daemon.. that chown 1:1 .. All the smart guys out there please correct me if I am wrong because after I changed the ownership mine is working just fine .. -- Faraz E-mail: sshamim@cs.unt.edu From majordomo-users-owner Thu Nov 14 17:32:37 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id QAA28523 for majordomo-users-outgoing; Thu, 14 Nov 1996 16:58:25 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id QAA28437 for ; Thu, 14 Nov 1996 16:57:49 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id SAA21626; Thu, 14 Nov 1996 18:57:59 -0600 (CST) To: neilc@tradesrv.com.au Cc: majordomo-users@GreatCircle.COM Subject: Re: ABORT message. References: <328A70A6.5A3A@tradesrv.com.au> From: Jason L Tibbitts III Date: 14 Nov 1996 18:57:58 -0600 In-Reply-To: Neil Cotty's message of Thu, 14 Nov 1996 12:06:46 +1100 Message-ID: Lines: 26 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "NC" == Neil Cotty writes: NC> I am periodically (every day to 2 days) receiving this message from NC> MJ. Does anybody have any advice on this one ? OK, I spent some time tracking this down. It turns out that there are times when sendmail will exit with a nonzero exit code when nothing is really wrong. The source to sendmail is really convoluted, and even an expert has told me not to bother trying to figure out why this happens. The solution (hopefully) is to add `-oee' to the options that Sendmail is called with, like so: $mailer = "$sendmail_command -oi -oee -f\$sender"; $bounce_mailer = "$sendmail_command -oi -oee -f\$sender -t"; This causes sendmail to mail all errors instead of trying to report them on the command line. It seems to still complain about real command line usage errors, but should no longer complain needlessly. Could someone who is having these problems try this out and tell the list how it goes? I don't call Sendmail from Majordomo so I can't try it. If this works, it will go into the next release (and the coming bugfix release). - J< From majordomo-users-owner Thu Nov 14 20:47:28 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA21039 for majordomo-users-outgoing; Thu, 14 Nov 1996 20:42:57 -0800 (PST) Received: from tahi.tradesrv.com.au ([203.63.230.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id UAA21028 for ; Thu, 14 Nov 1996 20:42:35 -0800 (PST) Received: from www ([203.63.230.36]) by tahi.tradesrv.com.au (8.6.12/8.6.9) with SMTP id PAA00081; Fri, 15 Nov 1996 15:42:42 +1100 Message-ID: <328BE74A.25C0@tradesrv.com.au> Date: Fri, 15 Nov 1996 14:45:14 +1000 From: Neil Cotty Reply-To: neilc@tradesrv.com.au Organization: Internet Trading Services X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: Jason L Tibbitts III CC: majordomo-users@GreatCircle.COM Subject: Re: ABORT message. References: <328A70A6.5A3A@tradesrv.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Jason + all, > OK, I spent some time tracking this down. It turns out that there are > times when sendmail will exit with a nonzero exit code when nothing is > really wrong. The source to sendmail is really convoluted, and even an > expert has told me not to bother trying to figure out why this happens. > > The solution (hopefully) is to add `-oee' to the options that Sendmail is > called with, like so: Hmm.. I've put this into my majordomo.cf but I've discovered the reason for the problem. Someone had subscribed to my list with a ( before their Email address. Once I fixed this there were no more problems. (thanx Dave) Cheers, Neil. From majordomo-users-owner Thu Nov 14 21:18:04 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id VAA23224 for majordomo-users-outgoing; Thu, 14 Nov 1996 21:02:46 -0800 (PST) Received: from tahi.tradesrv.com.au ([203.63.230.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id VAA23090 for ; Thu, 14 Nov 1996 21:02:08 -0800 (PST) Received: from www ([203.63.230.36]) by tahi.tradesrv.com.au (8.6.12/8.6.9) with SMTP id QAA00244 for ; Fri, 15 Nov 1996 16:02:30 +1100 Message-ID: <328BEBEF.4044@tradesrv.com.au> Date: Fri, 15 Nov 1996 15:05:03 +1000 From: Neil Cotty Reply-To: neilc@tradesrv.com.au Organization: Internet Trading Services X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Reply To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is there a way to get majordomo to specify the Reply To: as the list instead of the sender ? I have tried setting the Reply-To in the config of the list to the lists email address but this did zip. Cheers, Neil. From majordomo-users-owner Thu Nov 14 22:18:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id WAA28399 for majordomo-users-outgoing; Thu, 14 Nov 1996 22:02:28 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id WAA28324 for ; Thu, 14 Nov 1996 22:02:06 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id AAA01310; Fri, 15 Nov 1996 00:02:17 -0600 (CST) To: neilc@tradesrv.com.au Cc: majordomo-users@GreatCircle.COM Subject: Re: Reply To: References: <328BEBEF.4044@tradesrv.com.au> From: Jason L Tibbitts III Date: 15 Nov 1996 00:02:16 -0600 In-Reply-To: Neil Cotty's message of Fri, 15 Nov 1996 15:05:03 +1000 Message-ID: Lines: 17 X-Mailer: Red Gnus v0.54/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "NC" == Neil Cotty writes: NC> Is there a way to get majordomo to specify the Reply To: as the list NC> instead of the sender ? Yeah, reply_to in the list config file. NC> I have tried setting the Reply-To in the config of the list to the NC> lists email address but this did zip. It works just fine. Perhaps you're not using resend? Show us your aliases. (I'll refrain from the usual "Reply-To: is bad" speech, as long as you don't complain when the bounces go to the wrong place.) - J< From majordomo-users-owner Thu Nov 14 23:19:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id XAA03061 for majordomo-users-outgoing; Thu, 14 Nov 1996 23:02:07 -0800 (PST) Received: from sun630mp.infomania.com (sun630mp.infomania.com [199.182.37.33]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id XAA03026; Thu, 14 Nov 1996 23:01:47 -0800 (PST) Received: (from tmornini@localhost) by sun630mp.infomania.com (8.7.5/8.7.3) id XAA23534; Thu, 14 Nov 1996 23:01:51 -0800 (PST) From: Tom Mornini Message-Id: <199611150701.XAA23534@sun630mp.infomania.com> Subject: Boing! The automated Majordomo list cleaner To: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Date: Thu, 14 Nov 1996 23:01:51 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Ok! I got a great number of responses about my automated list cleaner. I wrote some docs, cleaned up the code a bunch (even comments!) and have made it available at http://www.mornini.com I will say that this thing has cut down the number of bounced messages by 90% after its first run. And it did it all by itself! :-) If you have a list of any size, and you're tired of the bounces, you've got to give this a look. However, I'll point it out as I did the first time: You need to know about your system, Perl, and be a generally cautious person to run this at this time. This is not for the timid, it's an early release. -- Tom Mornini -- InfoMania From majordomo-users-owner Thu Nov 14 23:22:08 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id XAA03680 for majordomo-users-outgoing; Thu, 14 Nov 1996 23:12:28 -0800 (PST) Received: from tahi.tradesrv.com.au ([203.63.230.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id XAA03662 for ; Thu, 14 Nov 1996 23:12:15 -0800 (PST) Received: from www ([203.63.230.36]) by tahi.tradesrv.com.au (8.6.12/8.6.9) with SMTP id SAA01322; Fri, 15 Nov 1996 18:12:27 +1100 Message-ID: <328C2682.5CEC@tradesrv.com.au> Date: Fri, 15 Nov 1996 19:14:58 +1000 From: Neil Cotty Reply-To: neilc@tradesrv.com.au Organization: Internet Trading Services X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: dwolfe@risc.sps.mot.com CC: majordomo-users@greatcircle.com Subject: Remote Protocol Error Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Dave + all, I managed to solve the Remote Protocol error after analysing your information on unqualified names. Basically the MTA at the recipient sites were trying to confirm the existence of owner-vizsla-digest. Because resend_host was not set to my domain the Email address was unqualified and could not be verified by the MTA. I fixed it by simply setting this parameter in the config of the digest list. resend_host = tradesrv.com.au Shouldn't that be sent anyway if you specify -h tradesrv.com.au in the alias ? Silly me but I must have missed it.. but is this issue mentioned anywhere in the docs or FAQ ? I guess this problem only occurs if the MTA is smarter than your average MTA and checks senders addresses (?) Sounds great for filtering spam. :) Cheers + 'ava good weekend everyone, (thanx heaps to all the dedicated Mj workers who help the 98% of us mere users (ab-users ?!) !) Neil. From majordomo-users-owner Fri Nov 15 02:54:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id CAA14954 for majordomo-users-outgoing; Fri, 15 Nov 1996 02:38:30 -0800 (PST) Received: from free-me.marben.be (gatekeeper.marben.be [194.78.27.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id CAA14917 for ; Fri, 15 Nov 1996 02:37:36 -0800 (PST) Received: (from smap@localhost) by free-me.marben.be (8.7.5/8.7.3) id LAA17315 for <@gatekeeper.marben.be:majordomo-users@GreatCircle.COM>; Fri, 15 Nov 1996 11:37:40 +0100 (MET) X-Authentication-Warning: free-me.marben.be: smap set sender to using -f Received: from tarifa.marben.be(172.20.0.254) by free-me.marben.be via smap (V1.3) id sma017311; Fri Nov 15 11:37:29 1996 Received: from tarifa.marben.be by tarifa via SMTP (940816.SGI.8.6.9/940406.SGI.AUTO) for id LAA03877; Fri, 15 Nov 1996 11:31:29 +0100 Message-ID: <328C4680.7288@marben.be> Date: Fri, 15 Nov 1996 11:31:29 +0100 From: Jean-Pierre Morant Organization: Marben SA-NV X-Mailer: Mozilla 3.0Gold (X11; I; IRIX 5.3 IP22) MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Reply-To : on a moderated list Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello ! I am running a moderated list (fully moderated : subscribtions and postings) and I'm unhappy with the "From: " or the "Reply-To: " fields of the mails received from the list. Actually the mail looks like it is coming from the original sender, which is good, but I would like replies to go to the list by default. IU've tried different things : - in /etc/aliases, i've added to resend's parameters : -r list@host but with no apparent effect. - in the list.conf file, I've added : message_headers Reply-To: << END list@host END or : message_headers << END Reply-To: list@host END with no apparent effect either. - in the list.conf , when I set sender = list here something happens : incoming mails loops.... - still in list.conf, I've set reply_to = marben@fresco.marben.be but again, no apparent effect ... I'm using majordomo 1.93. Does someone know why I can't get that Reply-To: field? Thanks -- Jean-Pierre Morant c/o MARBEN S.A./N.V. La vie serait tellement Boulevard du Souverain,400, Vorstlaan plus facile 1160 Bruxelles Si seulement Belgium nous avions les sources.... + 32 2 663 1130 (phone) + 32 2 663 1199 (fax) http://www.marben.be jpm@marben.be From majordomo-users-owner Fri Nov 15 05:07:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id EAA18805 for majordomo-users-outgoing; Fri, 15 Nov 1996 04:39:04 -0800 (PST) Received: from mail.eunet.ch (mail.eunet.ch [146.228.10.7]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id EAA18786 for ; Fri, 15 Nov 1996 04:38:31 -0800 (PST) Received: from bellatrix by mail.eunet.ch (8.8.2/1.34) id MAA04494; Fri, 15 Nov 1996 12:38:44 GMT Received: from prokyon.mathconsult.ch by bellatrix (4.1/SMI-4.1) id AA24751; Fri, 15 Nov 96 13:20:53 +0100 Received: from localhost by prokyon.mathconsult.ch (SMI-8.6/SMI-SVR4) id NAA05556; Fri, 15 Nov 1996 13:20:50 +0100 Message-Id: <199611151220.NAA05556@prokyon.mathconsult.ch> To: majordomo-users@GreatCircle.COM Subject: disable "who" command? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Nov 1996 13:20:50 +0100 From: Roman Maeder Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am not comfortable with the "who" command, even for a "private" list, where only subscribers can use it. Is there a standard way to disable the who command on a per-list base (through the config file), or do I have to comment out the "who" code in majordomo? This is for version 1.93. Roman Maeder From majordomo-users-owner Fri Nov 15 05:32:23 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA20274 for majordomo-users-outgoing; Fri, 15 Nov 1996 05:31:16 -0800 (PST) Received: from iquest.net (iquest4.iquest.net [206.53.230.100]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id FAA20255 for ; Fri, 15 Nov 1996 05:30:57 -0800 (PST) Received: by iquest.net (Smail3.1.29.1 #5) id m0vOOMQ-003iVEC; Fri, 15 Nov 96 08:31 EST Received: (from alt@localhost) by aen.aen.org (8.6.12/8.6.12) id EAA10455; Fri, 15 Nov 1996 04:38:31 -0500 Date: Fri, 15 Nov 1996 04:38:31 -0500 (EST) From: Al Thompson To: Jason L Tibbitts III cc: Chris Shenton , majordomo-users@GreatCircle.COM Subject: Re: Preventing spam via *-outgoing alias? 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 13 Nov 1996, Jason L Tibbitts III wrote: > fvwm-announce: "|/usr/local/lists/majordomo/wrapper resend > -l fvwm-announce -h hpc.uh.edu nobody" > > See, no outgoing alias. EXPN and VRFY are allowed, with no security risk I'm running 1.93. Is this in the v1.93 FAQ anywhere, and does it work on that version? From majordomo-users-owner Fri Nov 15 07:05:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id GAA26787 for majordomo-users-outgoing; Fri, 15 Nov 1996 06:57:41 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id GAA26778 for ; Fri, 15 Nov 1996 06:57:26 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA17577 for majordomo-users@GreatCircle.COM; Fri, 15 Nov 96 07:57:42 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA20707 for majordomo-users@GreatCircle.COM; Fri, 15 Nov 96 07:57:40 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id IAA07609; Fri, 15 Nov 1996 08:57:39 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id IAA21999; Fri, 15 Nov 1996 08:57:38 -0600 From: Dave Wolfe Message-Id: <199611151457.IAA21999@miaow.risc.sps.mot.com> Subject: Re: disable "who" command? To: maeder@mathconsult.ch (Roman Maeder) Date: Fri, 15 Nov 1996 08:57:38 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199611151220.NAA05556@prokyon.mathconsult.ch> from "Roman Maeder" at Nov 15, 96 01:20:50 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Roman Maeder writes: ] > > I am not comfortable with the "who" command, even for a "private" list, > where only subscribers can use it. Is there a standard way to disable > the who command on a per-list base (through the config file), or do I > have to comment out the "who" code in majordomo? This is for version 1.93. Yes, or there are some patches floating around to limit who in various ways (see the archives), or you could upgrade to 1.94. -- Dave Wolfe From majordomo-users-owner Fri Nov 15 07:37:00 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA28535 for majordomo-users-outgoing; Fri, 15 Nov 1996 07:26:14 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA28505 for ; Fri, 15 Nov 1996 07:25:58 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA21703 for majordomo-users@GreatCircle.COM; Fri, 15 Nov 96 08:26:15 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA21868 for majordomo-users@GreatCircle.COM; Fri, 15 Nov 96 08:26:13 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA08335; Fri, 15 Nov 1996 09:26:12 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA15365; Fri, 15 Nov 1996 09:04:20 -0600 From: Dave Wolfe Message-Id: <199611151504.JAA15365@miaow.risc.sps.mot.com> Subject: Re: Reply-To : on a moderated list To: jpm@marben.be (Jean-Pierre Morant) Date: Fri, 15 Nov 1996 09:04:19 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <328C4680.7288@marben.be> from "Jean-Pierre Morant" at Nov 15, 96 11:31:29 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Jean-Pierre Morant writes: ] > > I am running a moderated list (fully moderated : subscribtions and > postings) and I'm unhappy with the "From: " or the "Reply-To: " fields > of the mails received from the list. > > Actually the mail looks like it is coming from the original sender, > which is good, but I would like replies to go to the list by default. > > IU've tried different things : [...] > - in the list.conf file, I've added : > message_headers Reply-To: << END > list@host > END Nope, that's flat wrong, but your next attempt is OK. > message_headers << END > Reply-To: list@host > END Note that you might be getting multiple Reply-To headers doing this, which could lead to some unpredictable results. > - still in list.conf, > I've set > reply_to = marben@fresco.marben.be That's the right way to do it. > Does someone know why I can't get that Reply-To: field? You don't show us any example headers to see whether or not the header is actually getting inserted, but I suspect your problem may be your subscribers' mail readers. Some brain dead mailers on toy systems don't pay any attention to things like Reply-To, so even if Mj is inserting the header it may not make any difference. Look at some real, live headers (not with your mail reader, it may be lying) and then decide what works and what doesn't. -- Dave Wolfe From majordomo-users-owner Fri Nov 15 08:48:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA01496 for majordomo-users-outgoing; Fri, 15 Nov 1996 08:00:59 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA01371; Fri, 15 Nov 1996 08:00:04 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA27178 for majordomo-users@greatcircle.com; Fri, 15 Nov 96 09:00:19 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA23591 for majordomo-workers@greatcircle.com; Fri, 15 Nov 96 09:00:14 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id KAA08936; Fri, 15 Nov 1996 10:00:13 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id KAA11261; Fri, 15 Nov 1996 10:00:11 -0600 From: Dave Wolfe Message-Id: <199611151600.KAA11261@miaow.risc.sps.mot.com> Subject: Re: Restricted postings (revisited) To: kevinwu@hploms.hpl.hp.com (Kevin Wu) Date: Fri, 15 Nov 1996 10:00:11 -0600 (CST) Cc: majordomo-users@greatcircle.com (Majordomo user's mailing list), majordomo-workers@greatcircle.com (Majordomo developer's mailing list) Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Remember this awhile back? > [ Kevin Wu writes: ] > > > > I have installed Majordomo 1.94. I would like to restrict postings > > to senders within my company. Setting the variable restrict_post > > in .config to is too restrictive. I have > > been experimenting with taboo_headers. [...] [ Dave Wolfe responds: ] > > Perl has a logical not operator ('!') that would be more appropriate, > but it looks like the grab_regexp_array processing in config_parse.pl > doesn't allow one to negate the taboo regexes. The regexes that check > the taboo regexes are a little arcane to say the least, but I think this > patch will allow you to specify a negated regex like so: > > !/^from:.*[\@.]hp.com[>\s]/i [ patch deleted ] That patch doesn't work, but in the opposite way that Kevin indicated: it bounces *everything*. The taboo_headers are matched against all the headers, so obviously a negated regex will fail on all the headers other than the intended header, i.e. the example above will fail on the Subject: header even though we didn't care about it. The solution has to be two sets of regexes, one to match and one to not match, much like advertise and noadvertise, or a significant expansion of the taboo_headers syntax, e.g.: from !/.*[\@.]hp.com[>\s]/i where the first token specifies the header to be examined and the regex applies only to that header's value. -- Dave Wolfe From majordomo-users-owner Fri Nov 15 08:54:07 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA02968 for majordomo-users-outgoing; Fri, 15 Nov 1996 08:28:08 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA02954 for ; Fri, 15 Nov 1996 08:27:56 -0800 (PST) Received: from sina.hpc.uh.edu (tibbs@localhost [127.0.0.1]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id KAA19131; Fri, 15 Nov 1996 10:27:36 -0600 (CST) Message-Id: <199611151627.KAA19131@sina.hpc.uh.edu> To: alt@aen.org Cc: cshenton@it.hq.nasa.gov, majordomo-users@GreatCircle.COM Subject: Re: Preventing spam via *-outgoing alias? In-Reply-To: Your message of "Fri, 15 Nov 1996 04:38:31 -0500 (EST)" References: X-Mailer: Mew beta version 0.98 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 15 Nov 1996 10:27:35 -0600 From: Jason L Tibbitts III Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "AT" == Al Thompson writes: AT> I'm running 1.93. Is this in the v1.93 FAQ anywhere, and does it work AT> on that version? No, it doesn't work on 1.93 without major hackage. 1.94 has a clear delineation between the mailer it uses to send mail out to the mailing lists and the mailer it uses to send normal administrative mail. 1.93 doesn't, and since you can't use TLB for anything but sending to a list, 1.93 just won't work. - J< From majordomo-users-owner Fri Nov 15 09:03:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA04392 for majordomo-users-outgoing; Fri, 15 Nov 1996 08:45:06 -0800 (PST) Received: from apollo.it.hq.nasa.gov (apollo.it.hq.nasa.gov [131.182.119.87]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA04353 for ; Fri, 15 Nov 1996 08:44:48 -0800 (PST) Received: from wirehead.it.hq.nasa.gov (WireHead.it.hq.nasa.gov [131.182.119.88]) by apollo.it.hq.nasa.gov (8.6.12/8.6.12) with ESMTP id QAA00533; Fri, 15 Nov 1996 16:45:20 GMT Received: from localhost (cshenton@localhost) by wirehead.it.hq.nasa.gov (8.6.12/8.6.12) with SMTP id QAA27997; Fri, 15 Nov 1996 16:44:30 GMT Message-Id: <199611151644.QAA27997@wirehead.it.hq.nasa.gov> X-Authentication-Warning: wirehead.it.hq.nasa.gov: cshenton owned process doing -bs X-Authentication-Warning: wirehead.it.hq.nasa.gov: Host localhost didn't use HELO protocol To: alt@aen.org Cc: tibbs@hpc.uh.edu, majordomo-users@greatcircle.com Subject: Re: Preventing spam via *-outgoing alias? In-Reply-To: Your message of "Fri, 15 Nov 1996 04:38:31 -0500 (EST)" References: X-Mailer: Mew version 1.03 on Emacs 19.31.8 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 15 Nov 1996 11:44:26 -0500 From: Chris Shenton Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I found it not in the 1.93 FAQ (which we are running, too), but in the FAQ on the web -- which is presumably for 1.94. The 1.93 FAQ did talk about using non-obvious alias names, but didn't mention that recent sendmails expose the alias name in the Received-by: headers, and how to avoid them with a goofy "nobody" alias. From majordomo-users-owner Fri Nov 15 09:32:25 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA06195 for majordomo-users-outgoing; Fri, 15 Nov 1996 09:09:18 -0800 (PST) Received: from sun630mp.infomania.com (sun630mp.infomania.com [199.182.37.33]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA06178; Fri, 15 Nov 1996 09:09:05 -0800 (PST) Received: (from tmornini@localhost) by sun630mp.infomania.com (8.7.5/8.7.3) id JAA06783; Fri, 15 Nov 1996 09:09:04 -0800 (PST) From: Tom Mornini Message-Id: <199611151709.JAA06783@sun630mp.infomania.com> Subject: Boing! The Majordomo List Cleaner To: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Date: Fri, 15 Nov 1996 09:09:04 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When I made the files available last night (very late) I didn't test the package well enough. There is a problem with boing-fixer that will cause it to fail. No harm will be done, but the package won't work correctly, either. The new version is available at http://www.mornini.com Someone sent me e-mail about difficulty accessing the site. The IP address is 199.182.37.33. If you grabbed your copy before you get this message, I highly recommend getting the new copy. -- Tom Mornini -- InfoMania From majordomo-users-owner Fri Nov 15 09:33:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA05630 for majordomo-users-outgoing; Fri, 15 Nov 1996 09:02:14 -0800 (PST) Received: from free-me.marben.be (gatekeeper.marben.be [194.78.27.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA05119 for ; Fri, 15 Nov 1996 08:53:55 -0800 (PST) Received: (from smap@localhost) by free-me.marben.be (8.7.5/8.7.3) id RAA18096; Fri, 15 Nov 1996 17:53:40 +0100 (MET) X-Authentication-Warning: free-me.marben.be: smap set sender to using -f Received: from tarifa.marben.be(172.20.0.254) by free-me.marben.be via smap (V1.3) id sma018093; Fri Nov 15 17:53:36 1996 Received: from tarifa.marben.be by tarifa via SMTP (940816.SGI.8.6.9/940406.SGI.AUTO) id RAA06958; Fri, 15 Nov 1996 17:47:28 +0100 Message-ID: <328C9E9F.3D17@marben.be> Date: Fri, 15 Nov 1996 17:47:27 +0100 From: Jean-Pierre Morant Organization: Marben SA-NV X-Mailer: Mozilla 3.0Gold (X11; I; IRIX 5.3 IP22) MIME-Version: 1.0 To: Dave Wolfe CC: majordomo-users@GreatCircle.COM Subject: Re: Reply-To : on a moderated list References: <199611151504.JAA15365@miaow.risc.sps.mot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Here is the actual content of such a message, after approval : (the list name is "marben") ========================== Received: from fresco.marben.be by tarifa via ESMTP (940816.SGI.8.6.9/940406.SGI.AUTO) id RAA06896; Fri, 15 Nov 1996 17:42:00 +0100 Received: (from majordom@localhost) by fresco.marben.be (8.7.5/8.7.3) id RAA22634 for marben-outgoing; Fri, 15 Nov 1996 17:45:21 +0100 (MET) Date: Fri, 15 Nov 1996 17:45:21 +0100 (MET) Message-Id: <199611151645.RAA22634@fresco.marben.be> From: Jean-Pierre Morant Subject: That's the right way to do it. Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: Apparently-To: X-Mozilla-Status: 0001 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > You don't show us any example headers to see whether or not the header > is actually getting inserted, but I suspect your problem may be your > subscribers' mail readers. Some brain dead mailers on toy systems don't > pay any attention to things like Reply-To, so even if Mj is inserting > the header it may not make any difference. Look at some real, live > headers (not with your mail reader, it may be lying) and then decide > what works and what doesn't. > -- > Jean-Pierre Morant > c/o MARBEN S.A./N.V. La vie serait tellement > Boulevard du Souverain,400, Vorstlaan plus facile > 1160 Bruxelles Si seulement > Belgium nous avions les sources.... > + 32 2 663 1130 (phone) > + 32 2 663 1199 (fax) > http://www.marben.be > jpm@marben.be ======================================= As you can see there is no mention of a "Reply-To: " field.... -- Jean-Pierre Morant c/o MARBEN S.A./N.V. La vie serait tellement Boulevard du Souverain,400, Vorstlaan plus facile 1160 Bruxelles Si seulement Belgium nous avions les sources.... + 32 2 663 1130 (phone) + 32 2 663 1199 (fax) http://www.marben.be jpm@marben.be From majordomo-users-owner Fri Nov 15 09:35:48 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA07138 for majordomo-users-outgoing; Fri, 15 Nov 1996 09:27:13 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA07128 for ; Fri, 15 Nov 1996 09:26:55 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id MAA10308; Fri, 15 Nov 1996 12:27:03 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id MAA03411; Fri, 15 Nov 1996 12:26:58 -0500 (EST) Message-Id: <199611151726.MAA03411@augusta.math.psu.edu> To: Chris Shenton cc: alt@aen.org, tibbs@hpc.uh.edu, majordomo-users@GreatCircle.COM Subject: Re: Preventing spam via *-outgoing alias? In-reply-to: Your message of "Fri, 15 Nov 1996 11:44:26 EST." <199611151644.QAA27997@wirehead.it.hq.nasa.gov> References: <199611151644.QAA27997@wirehead.it.hq.nasa.gov> 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: Fri, 15 Nov 1996 12:26:55 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <199611151644.QAA27997@wirehead.it.hq.nasa.gov>, Chris Shenton write s: >I found it not in the 1.93 FAQ (which we are running, too), but in the >FAQ on the web -- which is presumably for 1.94. > >The 1.93 FAQ did talk about using non-obvious alias names, but didn't >mention that recent sendmails expose the alias name in the >Received-by: headers, and how to avoid them with a goofy "nobody" alias. Both the 1.93 and the 1.94 FAQ's on the web cover this. I don't recall if the FAQ bundled with 1.93 did, but everybody should have removed that long ago. --Dave From majordomo-users-owner Fri Nov 15 10:06:58 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA09335 for majordomo-users-outgoing; Fri, 15 Nov 1996 09:58:14 -0800 (PST) Received: from mail.his.com (mail.his.com [205.177.25.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA09267 for ; Fri, 15 Nov 1996 09:57:52 -0800 (PST) Received: from [205.177.25.164] (kendall.his.com [205.177.25.164]) by mail.his.com (8.6.9/8.6.12) with ESMTP id MAA27775; Fri, 15 Nov 1996 12:57:39 -0500 Message-Id: In-Reply-To: <328C9E9F.3D17@marben.be> References: <199611151504.JAA15365@miaow.risc.sps.mot.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 15 Nov 1996 12:57:44 -0500 To: Jean-Pierre Morant From: "Kendall P Bullen" Subject: Re: Reply-To : on a moderated list Cc: majordomo-users@greatcircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hiya, Quick, unrelated comment -- At 5:47 PM +0100 11/15/96, Jean-Pierre Morant wrote: >Received: (from majordom@localhost) by fresco.marben.be >(8.7.5/8.7.3) id >RAA22634 for marben-outgoing; Fri, 15 Nov 1996 17:45:21 +0100 (MET) Eek, hide your outgoing list alias . . . and use something other than -outgoing (that's the "standard" and thus, most obvious). Otherwise, people can easily spam your list. :) I believe the FAQ and/or README should have instructions on how to hide it (things like picking an unobvious name, adding ,nobody to the alias, et al.). >Apparently-To: >Apparently-To: >Apparently-To: >Apparently-To: >Apparently-To: >Apparently-To: Hmmness. Messages on my list simply say "To: listname" and don't have any "Apparently-To:" lines -- this is a huge security hole (people can see everyone who's on your list from these lines). Maybe something else isn't configured right, either? Good luck getting stuff worked out. Kendall -- Kendall P. Bullen E-mail: kendall@his.com Web: http://www.his.com/~kendall/ From majordomo-users-owner Fri Nov 15 11:11:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA14239 for majordomo-users-outgoing; Fri, 15 Nov 1996 10:47:11 -0800 (PST) Received: from free-me.marben.be (gatekeeper.marben.be [194.78.27.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA14209 for ; Fri, 15 Nov 1996 10:46:43 -0800 (PST) Received: (from smap@localhost) by free-me.marben.be (8.7.5/8.7.3) id TAA18419; Fri, 15 Nov 1996 19:45:11 +0100 (MET) X-Authentication-Warning: free-me.marben.be: smap set sender to using -f Received: from tarifa.marben.be(172.20.0.254) by free-me.marben.be via smap (V1.3) id sma018417; Fri Nov 15 19:45:07 1996 Received: from tarifa.marben.be by tarifa via SMTP (940816.SGI.8.6.9/940406.SGI.AUTO) id TAA07693; Fri, 15 Nov 1996 19:39:03 +0100 Message-ID: <328CB8C7.257E@marben.be> Date: Fri, 15 Nov 1996 19:39:03 +0100 From: Jean-Pierre Morant Organization: Marben SA-NV X-Mailer: Mozilla 3.0Gold (X11; I; IRIX 5.3 IP22) MIME-Version: 1.0 To: Kendall P Bullen CC: majordomo-users@greatcircle.com Subject: Re: Reply-To : on a moderated list References: <199611151504.JAA15365@miaow.risc.sps.mot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Funny enough, in all the tests I've done those ugly "Apparently-to: " didn't appear EXCEPT the time I've added manually a "Reply-to: " just after the Approved: field .... Otherwize I've also tried to add a cc in the list.config file : message_headers << END Cc: marben@fresco.marben.be END but the damn' thing just ignore it ... Changing some other parameters cause a visible effect. So what ??? Does anyone see a reason (another variable with a higher precedence for instance) for this message not to be taken into account ???? Thanks to all for your help JPM -- ---- Jean-Pierre Morant c/o MARBEN S.A./N.V. La vie serait tellement Boulevard du Souverain,400, Vorstlaan plus facile 1160 Bruxelles Si seulement Belgium nous avions les sources.... + 32 2 663 1130 (phone) + 32 2 663 1199 (fax) http://www.marben.be jpm@marben.be From majordomo-users-owner Fri Nov 15 11:17:06 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA14476 for majordomo-users-outgoing; Fri, 15 Nov 1996 10:48:19 -0800 (PST) Received: from lambton.on.ca (white.lambton.on.ca [192.139.190.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA14079 for ; Fri, 15 Nov 1996 10:45:45 -0800 (PST) Received: from localhost by white.lambton.on.ca with SMTP id AA15184; Fri, 15 Nov 1996 13:46:53 -0500 Date: Fri, 15 Nov 1996 13:46:53 -0500 (EST) From: David Grant Reply-To: David Grant To: Jason L Tibbitts III Cc: Majordomo users Subject: Re: 1.94 resend options fail? 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 13 Nov 1996, Jason L Tibbitts III wrote: > We botched the argument parsing of resend trying to patch the problem where > Sendmail downcases the options. In this case, it really is best for you to > get rid of everything but `-l' and just use the config file. > > As for the "array found..." error, I'd have to see your config file but Id > wager that you've neglected to escape an `@' symbol in a string. OK, I've touched up my config files and pulled the options from resend. Everything seams fine! Maybe that little tidbit could be added to the FAQ? (slight backgound grumbling....) As for the "array found..." error, again right on the money. Figures my test list is the only one with an advertise list! Now my last glitch is with the password protected commands. I get: >>>> config test passpass **** config: invalid password. when I have: # grep _passwd test.config # admin_passwd [word] (test.admin) admin_passwd = test.admin # approve_passwd [word] (test.pass) approve_passwd = test.pass and: # ls -l test* -rw-rw-r-- 1 majordom majordom 0 Nov 15 10:19 test -rw-rw---- 1 majordom majordom 9 Nov 15 10:17 test.admin -rw-rw---- 1 majordom majordom 14535 Nov 15 10:09 test.config -rw-rw-r-- 1 majordom majordom 79 Oct 3 1994 test.info -rw-rw---- 1 majordom majordom 9 Nov 15 10:16 test.pass and of course: # cat test.admin passpass # cat test.pass passpass Anyone see anything obvious? Thanks, Dave ----- David Grant VE3DGR +1 519 542-7751 x348 Lambton College, Sarnia, ON, CANADA +1 519 542-6667 FAX From majordomo-users-owner Fri Nov 15 12:02:50 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA20527 for majordomo-users-outgoing; Fri, 15 Nov 1996 11:59:29 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA20487 for ; Fri, 15 Nov 1996 11:59:11 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA04078 for majordomo-users@GreatCircle.COM; Fri, 15 Nov 96 12:59:20 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA02587 for majordomo-users@GreatCircle.COM; Fri, 15 Nov 96 12:59:18 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id NAA12398; Fri, 15 Nov 1996 13:59:17 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id NAA12074; Fri, 15 Nov 1996 13:59:15 -0600 From: Dave Wolfe Message-Id: <199611151959.NAA12074@miaow.risc.sps.mot.com> Subject: Re: Reply-To : on a moderated list To: jpm@marben.be (Jean-Pierre Morant) Date: Fri, 15 Nov 1996 13:59:15 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <328C9E9F.3D17@marben.be> from "Jean-Pierre Morant" at Nov 15, 96 05:47:27 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Jean-Pierre Morant writes: ] > > Here is the actual content of such a message, after approval : (the list > name is "marben") > ========================== > Received: from fresco.marben.be by tarifa via ESMTP > (940816.SGI.8.6.9/940406.SGI.AUTO) > id RAA06896; Fri, 15 Nov 1996 17:42:00 +0100 > Received: (from majordom@localhost) by fresco.marben.be (8.7.5/8.7.3) id > RAA22634 for marben-outgoing; Fri, 15 Nov 1996 17:45:21 +0100 (MET) > Date: Fri, 15 Nov 1996 17:45:21 +0100 (MET) > Message-Id: <199611151645.RAA22634@fresco.marben.be> > From: Jean-Pierre Morant > Subject: That's the right way to do it. > Apparently-To: > Apparently-To: > Apparently-To: > Apparently-To: > Apparently-To: > Apparently-To: > X-Mozilla-Status: 0001 No To and using Netscape. Exactly how are you approving messages? Resend expects the original headers following the Approved header in the body. If the original headers aren't there (or there's a blank line immediately after the Approved header) then you get the wrong headers. You are using resend in your list alias, aren't you? If not then of course you won't see any resend features. -- Dave Wolfe From majordomo-users-owner Fri Nov 15 13:02:46 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA24415 for majordomo-users-outgoing; Fri, 15 Nov 1996 12:45:25 -0800 (PST) Received: from lambton.on.ca (white.lambton.on.ca [192.139.190.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA24341 for ; Fri, 15 Nov 1996 12:44:34 -0800 (PST) Received: from localhost by white.lambton.on.ca with SMTP id AA00689; Fri, 15 Nov 1996 15:46:10 -0500 Date: Fri, 15 Nov 1996 15:46:09 -0500 (EST) From: David Grant To: Dave Wolfe Cc: majordomo-users@GreatCircle.COM Subject: Re: 1.94 resend options fail? In-Reply-To: <199611152009.OAA11922@miaow.risc.sps.mot.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Before I get a dozen more answers... Thanks! (I won't admit how many times I read the comments in the config file incorrectly) Brain Fade....... Dave On Fri, 15 Nov 1996, Dave Wolfe wrote: > These *are* your passwords. They are *not* file names. > > That should be 'test.passwd', but the separate password is deprecated. ----- David Grant VE3DGR +1 519 542-7751 x348 Lambton College, Sarnia, ON, CANADA +1 519 542-6667 FAX From majordomo-users-owner Fri Nov 15 13:10:20 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA22090 for majordomo-users-outgoing; Fri, 15 Nov 1996 12:17:27 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA21906 for ; Fri, 15 Nov 1996 12:15:56 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA05486 for majordomo-users@GreatCircle.COM; Fri, 15 Nov 96 13:09:28 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA02990 for majordomo-users@GreatCircle.COM; Fri, 15 Nov 96 13:09:26 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id OAA12596; Fri, 15 Nov 1996 14:09:25 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id OAA11922; Fri, 15 Nov 1996 14:09:24 -0600 From: Dave Wolfe Message-Id: <199611152009.OAA11922@miaow.risc.sps.mot.com> Subject: Re: 1.94 resend options fail? To: david@lambton.on.ca Date: Fri, 15 Nov 1996 14:09:23 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "David Grant" at Nov 15, 96 01:46:53 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ David Grant writes: ] > > Now my last glitch is with the password protected commands. I get: > >>>> config test passpass > **** config: invalid password. > > when I have: > > # grep _passwd test.config > # admin_passwd [word] (test.admin) > admin_passwd = test.admin > # approve_passwd [word] (test.pass) > approve_passwd = test.pass These *are* your passwords. They are *not* file names. > and: > # ls -l test* > -rw-rw---- 1 majordom majordom 9 Nov 15 10:16 test.pass That should be 'test.passwd', but the separate password is deprecated. -- Dave Wolfe From majordomo-users-owner Fri Nov 15 13:48:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA28783 for majordomo-users-outgoing; Fri, 15 Nov 1996 13:27:26 -0800 (PST) Received: from reddog.sclfl.com (reddog.sclfl.com [204.117.69.17]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA28691 for ; Fri, 15 Nov 1996 13:26:43 -0800 (PST) Received: from [204.117.69.8] (michele [204.117.69.8]) by reddog.sclfl.com (8.7.3/8.7.3) with SMTP id QAA09702 for ; Fri, 15 Nov 1996 16:20:55 -0500 (EST) Date: Fri, 15 Nov 1996 16:20:55 -0500 (EST) Message-Id: <199611152120.QAA09702@reddog.sclfl.com> X-Sender: mercerm@reddog.sclfl.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@GreatCircle.COM From: mercerm@sclfl.com (Michele Mercer) Subject: Need help with majordomo build. Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I'm trying to build majordomo1.94 on a Sun Solaris machine using the gcc compiler. I havn't been successfull. This is the error I'm getting. # make wrapper gcc -DBIN=\"/opt/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/opt/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF=\"MAJORDOMO_CF=/opt/majordomo/majordomo.cf\" -DPOSIX_UID=273 -DPOSIX_GID=12 -o wrapper wrapper.c ld: fatal: file wrapper: cannot open file; errno=13 make: *** [wrapper] Error 1 Initially I built majordomo on another solaris system using the Sun compiler and it built fine. I thought I could take what was built on that system and move it over to the other solaris system. The reason I did this is because I couldn't get it to compile with the gcc compiler. Once I moved it over I modified the majordomo.cf file, where it had an entry for the sytem it was built on I put the new system name. When I ran the test at the end of the installation instructions, mail didn't get sent. Can anyone shed some light on this. Thanks Michele Mercer From majordomo-users-owner Fri Nov 15 15:17:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA06152 for majordomo-users-outgoing; Fri, 15 Nov 1996 15:02:15 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id PAA06050 for ; Fri, 15 Nov 1996 15:01:36 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id SAA16666; Fri, 15 Nov 1996 18:01:45 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id SAA06062; Fri, 15 Nov 1996 18:01:42 -0500 (EST) Message-Id: <199611152301.SAA06062@augusta.math.psu.edu> To: mercerm@sclfl.com (Michele Mercer) cc: majordomo-users@GreatCircle.COM Subject: Re: Need help with majordomo build. In-reply-to: Your message of "Fri, 15 Nov 1996 16:20:55 EST." <199611152120.QAA09702@reddog.sclfl.com> References: <199611152120.QAA09702@reddog.sclfl.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: Fri, 15 Nov 1996 18:01:40 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <199611152120.QAA09702@reddog.sclfl.com>, Michele Mercer writes: ># make wrapper >gcc -DBIN=\"/opt/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" >-DHOME=\"HOME=/opt/majordomo\" -DSHELL=\"SHELL=/bin/csh\" >-DMAJORDOMO_CF=\"MAJORDOMO_CF=/opt/majordomo/majordomo.cf\" -DPOSIX_UID=273 >-DPOSIX_GID=12 -o wrapper wrapper.c >ld: fatal: file wrapper: cannot open file; errno=13 Error 13 is "Permission Denied". You appear to be compiling this as root. Is this on an NFS partition? That's probably your problem, since root isn't normally root over NFS. Compile it as a normal user. --Dave From majordomo-users-owner Fri Nov 15 16:18:44 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA09201 for majordomo-users-outgoing; Fri, 15 Nov 1996 15:29:41 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA09092 for majordomo-users@greatcircle.com; Fri, 15 Nov 1996 15:29:06 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA12125 for ; Thu, 14 Nov 1996 07:02:09 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA08636 for majordomo-users@GreatCircle.COM; Thu, 14 Nov 96 08:02:24 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA18812 for majordomo-users@GreatCircle.COM; Thu, 14 Nov 96 08:02:23 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id JAA21507; Thu, 14 Nov 1996 09:02:22 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id JAA21306; Thu, 14 Nov 1996 09:02:20 -0600 From: Dave Wolfe Message-Id: <199611141502.JAA21306@miaow.risc.sps.mot.com> Subject: Re: Can't get Majordomo to unsubscribe To: andywild@lightspeed.co.uk (Andy Wild) Date: Thu, 14 Nov 1996 09:02:20 -0600 (CST) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Andy Wild" at Nov 13, 96 03:42:32 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Andy Wild writes: ] > > I have been able to setup a mailing list, subscribe to it and receive > any postings to it, but I have been unable to unsubscribe to it! [...] > Majordomo does e-mail me back but only echoes my commands back to me > - there is no "Succeeded" message and the e-mail address stays in the > main list's file. Someone (owner-majordomo?) should be getting some Mj ABORT messages. Mj probably doesn't have permission to do something (create file, chown, and/or chmod) in the lists directory, indicating that Mj isn't installed correctly. 'wrapper' is the most likely culprit, but maybe you don't have the owner/permissions right on the lists directory. -- Dave Wolfe From majordomo-users-owner Fri Nov 15 16:29:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA09299 for majordomo-users-outgoing; Fri, 15 Nov 1996 15:30:21 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA09159 for majordomo-users@greatcircle.com; Fri, 15 Nov 1996 15:29:28 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA17231 for ; Thu, 14 Nov 1996 08:09:20 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA18431 for majordomo-users@GreatCircle.com; Thu, 14 Nov 96 09:09:34 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA21689 for majordomo-users@GreatCircle.com; Thu, 14 Nov 96 09:09:32 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id KAA22857; Thu, 14 Nov 1996 10:09:31 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id KAA11572; Thu, 14 Nov 1996 10:09:29 -0600 From: Dave Wolfe Message-Id: <199611141609.KAA11572@miaow.risc.sps.mot.com> Subject: Re: Filtering messages To: BCCHRISTENSEN@novell.com (Brian Christensen) Date: Thu, 14 Nov 1996 10:09:29 -0600 (CST) Cc: majordomo-users@GreatCircle.com In-Reply-To: from "Brian Christensen" at Nov 13, 96 10:39:51 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Brian Christensen writes: ] > > Is there a way to automatically filter [ confidential ] messages before > they get sent to the mailing lists? Sounds risky to me, but you could always make an alias for the filter program and subscribe that instead of the non-confidential list, or better yet, append it to the alias for the confidential list, e.g.: confidential-filter: "|/path/to/filter whatever arguments" confidential-list: "|/path/to/wrapper resend -l confidential-list -h your.host confidential-list-outgoing,confidential-filter" If writing a filter script is too much of a stretch, you might look into various mail throwers like deliver or procmail to do the mail handling, then you just have to write the rules for whether or not the mail is dropped or remailed to the public list. -- Dave Wolfe From majordomo-users-owner Fri Nov 15 16:50:04 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id PAA09302 for majordomo-users-outgoing; Fri, 15 Nov 1996 15:30:33 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id PAA09207 for majordomo-users@greatcircle.com; Fri, 15 Nov 1996 15:29:44 -0800 (PST) Received: from ns.ucb.edu.bo ([166.114.18.10]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA21700 for ; Thu, 14 Nov 1996 09:12:59 -0800 (PST) Received: from localhost (cae@localhost) by ns.ucb.edu.bo (8.7.5/8.7.3) with SMTP id NAA07096 for ; Thu, 14 Nov 1996 13:07:30 -0400 Date: Thu, 14 Nov 1996 13:07:29 -0400 (AST) From: Carlos Eduardo Anibarro Zelaya To: majordomo-users@greatcircle.com Subject: Returned mail: Internal error: Error 0 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/REPORT; REPORT-TYPE=delivery-status; BOUNDARY="MAA00163.847975905/cc.ucb.edu.bo" 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. --MAA00163.847975905/cc.ucb.edu.bo Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Dear Sirs We have installed the Majordomo 1-94 program sucessfully. After creating a test list, when you try to send a mail to test@... it returns this error to the owner: ---------- Forwarded message ---------- Date: Thu, 14 Nov 1996 12:51:45 GMT From: Mail Delivery Subsystem To: postmaster@cc.ucb.edu.bo, cae@cc.ucb.edu.bo Subject: Returned mail: Internal error: Error 0 The original message was received at Thu, 14 Nov 1996 12:51:44 GMT from cae@localhost ----- The following addresses have delivery notifications ----- "|/usr/local/majordom/wrapper resend -l test test-list" (unrecoverable error) (expanded from: test) ----- Transcript of session follows ----- /usr/local/majordom/wrapper: error: Not running with proper UID and GID. Make certain that wrapper is installed setuid, and if so, recompile with POSIX flags. 554 "|/usr/local/majordom/wrapper resend -l test test-list"... Internal error: Error 0 And when you send a mail to majordom@... using a subscribe command, it doen`t it doen't reply anFrom majordomo-users-owner Fri Nov 15 18:02:15 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id RAA25869 for majordomo-users-outgoing; Fri, 15 Nov 1996 17:50:13 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id RAA25817 for ; Fri, 15 Nov 1996 17:49:50 -0800 (PST) Received: from jasper ([13.240.161.42]) by alpha.xerox.com with SMTP id <15201(2)>; Fri, 15 Nov 1996 17:50:05 PST Received: by jasper (SMI-8.6/SMI-SVR4-SD1.5) id RAA10722; Fri, 15 Nov 1996 17:49:48 -0800 Date: Fri, 15 Nov 1996 17:49:48 PST Message-Id: <199611160149.RAA10722@jasper> To: majordomo-users@greatcircle.com Subject: New install: "Cannot exec '/bin/none' errno=2" Cc: bhami@hesp.es.xerox.com From: Bruce Hamilton Reply-To: bhami@hesp.es.xerox.com X-Sun-Charset: US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When I send a "help" message to majordomo@hesp.es.xerox.com, I get the following bounce: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ From: Mailer-Daemon@hesp.es.xerox.com (Mail Delivery Subsystem) Subject: Returned mail: Service unavailable To: Postmaster@hesp.es.xerox.com ----- Transcript of session follows ----- Cannot exec '/bin/none' errno=2 554 "|/usr/majordomo/wrapper majordomo"... Service unavailable ... @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Thanks for any advice. This is majordomo-1.93 on SunOS 4.1.3 and perl-4.036. What I'd REALLY like is instructions on how to trace and debug, e.g. some way to do "perl -d" on something and get something useful out. /usr/majordomo # grep majord /etc/passwd majordom:*:26785:26785:majordomo system user:/usr/majordomo:/bin/csh /usr/majordomo # 13 # ls -l total 328 drwxrwxr-x 9 majordom majordom 1024 Nov 15 17:10 ./ drwxr-xr-x 35 root wheel 1024 Oct 31 11:22 ../ -rwxr-xr-x 1 majordom majordom 1254 Oct 29 07:37 .cshrc* -rwxr-xr-x 1 majordom majordom 552 Nov 11 1993 .login* -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 drwxrwxr-x 3 majordom majordom 512 Jan 10 1995 Doc/ -rw-r--r-- 1 majordom majordom 4631 Dec 26 1994 LICENSE drwxrwxr-x 2 majordom majordom 512 Nov 1 17:49 Log/ -rw-r--r-- 1 majordom majordom 4458 Nov 1 14:50 Makefile -rw-r--r-- 1 root daemon 4460 Nov 1 14:50 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* drwxrwxr-x 2 majordom majordom 512 Nov 1 16:05 archive/ -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 drwxrwxr-x 2 majordom majordom 512 Jan 10 1995 contrib/ drwxrwxr-x 2 majordom majordom 512 Jan 10 1995 digest/ drwxrwxr-x 2 majordom majordom 512 Nov 1 15:57 digestwork/ drwxrwxr-x 2 root majordom 512 Nov 1 17:31 lists/ -rwxr-xr-x 1 majordom majordom 42524 Jan 4 1995 majordomo* -rw-r--r-- 1 root daemon 3669 Nov 15 15:51 majordomo.cf -rw-r--r-- 1 root daemon 3667 Nov 15 15:51 majordomo.cf% -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* -rwsr-sr-x 1 root daemon 24576 Nov 1 14:50 wrapper* -rw-r--r-- 1 majordom majordom 2783 Jan 7 1995 wrapper.c -rwxr-xr-x 1 majordom majordom 223 May 9 1994 wrapper.sh* --Bruce 310-333-3538 fax: 310-333-6898 Xerox: 8*823-3538 m/s ESC1-615 From majordomo-users-owner Fri Nov 15 18:17:55 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA28050 for majordomo-users-outgoing; Fri, 15 Nov 1996 18:11:56 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id SAA28025 for ; Fri, 15 Nov 1996 18:11:38 -0800 (PST) Received: from jasper ([13.240.161.42]) by alpha.xerox.com with SMTP id <16177(1)>; Fri, 15 Nov 1996 18:11:51 PST Received: by jasper (SMI-8.6/SMI-SVR4-SD1.5) id SAA10825; Fri, 15 Nov 1996 18:11:33 -0800 Date: Fri, 15 Nov 1996 18:11:33 PST Message-Id: <199611160211.SAA10825@jasper> To: majordomo-users@greatcircle.com Subject: Re: New install: "Cannot exec '/bin/none' errno=2" Cc: bhami@hesp.es.xerox.com From: Bruce Hamilton Reply-To: bhami@hesp.es.xerox.com X-Sun-Charset: US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk p.p.s. Yes, I added majordom to the list of trusted users in /etc/sendmail.cf and killed and restarted sendmail. ### Trusted users T root daemon uucp majordom --Bruce 310-333-3538 fax: 310-333-6898 Xerox: 8*823-3538 m/s ESC1-615 From majordomo-users-owner Fri Nov 15 18:21:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA27608 for majordomo-users-outgoing; Fri, 15 Nov 1996 18:07:05 -0800 (PST) Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id SAA27579 for ; Fri, 15 Nov 1996 18:06:52 -0800 (PST) Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-961106) id SAA04869; Fri, 15 Nov 1996 18:06:54 -0800 Received: from alpha.xerox.com(13.1.64.93) by mycroft via smap (V1.3mjr) id sma004866; Fri Nov 15 18:06:52 1996 Received: from jasper ([13.240.161.42]) by alpha.xerox.com with SMTP id <16011(2)>; Fri, 15 Nov 1996 18:05:43 PST Received: by jasper (SMI-8.6/SMI-SVR4-SD1.5) id SAA10804; Fri, 15 Nov 1996 18:05:25 -0800 Date: Fri, 15 Nov 1996 18:05:25 PST Message-Id: <199611160205.SAA10804@jasper> To: majordomo-users@GreatCircle.COM Subject: Re: New install: "Cannot exec '/bin/none' errno=2" Cc: bhami@hesp.es.xerox.com From: Bruce Hamilton Reply-To: bhami@hesp.es.xerox.com X-Sun-Charset: US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk p.s. if I just do /usr/majordomo/wrapper majordomo on a command line on the server, and then construct a message body inline, it WORKS. So, I'm thinking it's not a majordomo problem per se, but somehow sendmail isn't letting me mail to a pipe. ??? # grep majordomo: /etc/aliases majordomo: "|/usr/majordomo/wrapper majordomo" --Bruce 310-333-3538 fax: 310-333-6898 Xerox: 8*823-3538 m/s ESC1-615 From majordomo-users-owner Fri Nov 15 22:18:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id WAA25747 for majordomo-users-outgoing; Fri, 15 Nov 1996 22:12:50 -0800 (PST) Received: from algol.cs.umbc.edu (algol.cs.umbc.edu [130.85.100.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id WAA25729 for ; Fri, 15 Nov 1996 22:12:39 -0800 (PST) Received: from 128.91.202.204 (TS11-51.UPENN.EDU [128.91.202.204]) by algol.cs.umbc.edu (8.7.6/8.6.9) with SMTP id BAA22563 for ; Sat, 16 Nov 1996 01:12:58 -0500 (EST) Message-ID: <328D5A88.2372@cs.umbc.edu> Date: Sat, 16 Nov 1996 01:09:14 -0500 From: tim finin Reply-To: finin@cs.umbc.edu OrgFrom majordomo-users-owner Sat Nov 16 05:48:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA20924 for majordomo-users-outgoing; Sat, 16 Nov 1996 05:46:21 -0800 (PST) Received: from infobahn.icubed.com (infobahn.icubed.com [208.0.145.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id FAA20907 for ; Sat, 16 Nov 1996 05:46:11 -0800 (PST) Received: by infobahn.icubed.com; (5.65/1.1.8.2/25Jun95-1044PM) id AA19587; Sat, 16 Nov 1996 08:43:08 -0500 Date: Sat, 16 Nov 1996 08:43:07 -0500 (EST) From: Eutychus II Reply-To: Bro-Dan@XC.Org To: majordomo-users@GreatCircle.COM Subject: no_who In-Reply-To: <199611160211.SAA10825@jasper> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Can anyone tell me whether the "no_who" configuration exists in any of the most recent versions of Majordomo? If so, which version? If not, does anyone have a program patch which I could obtain to make this modification in Majordomo? For the security of my subscriber bases, I desire to make the "who" command require a password, which is what the "no_who" command is, as I understand. Any help will be appreciated. * Brother Dan * Good News Cafe Bro-Dan@XC.Org http://www.cforc.com/gnc/ "seekfirst" - a free service: the largest e-mail "website" on the Net! To:hub@XC.Org in the body of the message, send: info seekfirst From majordomo-users-owner Sat Nov 16 07:18:09 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA25379 for majordomo-users-outgoing; Sat, 16 Nov 1996 07:16:47 -0800 (PST) Received: from senie.com (senie.com [204.69.207.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA25370 for ; Sat, 16 Nov 1996 07:16:36 -0800 (PST) Received: (qmail 32309 invoked from network); 16 Nov 1996 15:16:54 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 16 Nov 1996 15:16:54 -0000 Date: Sat, 16 Nov 1996 10:16:54 -0500 (EST) From: Daniel Senie To: Chael Hall cc: majordomo-users@greatcircle.com Subject: Re: Qmail vs MX records 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 Nov 1996, Chael Hall wrote: > On Thu, 14 Nov 1996, Daniel Senie wrote: > > >QMAIL seems to insist that MX records exist for domains before it'll send > >mail. I've noticed a very limited number of addresses which do NOT get > >delivered to by my system now that I'm running QMAIL. I wonder if anyone > >else has seen this and might know how to alter the config of qmail to > >allow it to find an A record if there are no MX records found. > > > >Dan > > Check out the qmail mailing list (djb-qmail@koobera.math.uic.edu) to find > out the latest about qmail. I'm running version 0.92 which no longer > insists on MX records. According to the RFC, it's supposed to fall back > to the IP address if it can't find an MX. Earlier versions did not. Thanks. Actually I put up 0.92 a little while after posting that message, when I got a response from the author of qmail. The problem wasn't an insistence on MX records, but a problem in looking for CNAME records. Some BIND (DNS) software apparently has a bug and won't respond to CNAMEs, rather than giving a negative response. It did seem that all the sites that didn't have MX records were the ones that failed. Those sites also had DNS servers that didn't respond to CNAME record requests. Coincidence? :-) Dan --------------------------------------------------------------- Daniel Senie Internet: dan@senie.com, Daniel Senie Consulting n1jeb@senie.com http://www.senie.com Packet Radio: N1JEB@KA1SRD.MA If we suffer tamely a lawless attack upon our liberty, we encourage it, and involve others in our doom. -- Samuel Adams From majordomo-users-owner Sat Nov 16 08:06:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA26774 for majordomo-users-outgoing; Sat, 16 Nov 1996 07:50:33 -0800 (PST) Received: from vyger.net (gcap.visi.com [206.8.50.16]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA26765 for ; Sat, 16 Nov 1996 07:50:23 -0800 (PST) Received: from localhost (greg@localhost) by vyger.net (8.6.11/8.6.9) with SMTP id JAA03481; Sat, 16 Nov 1996 09:37:21 GMT Date: Sat, 16 Nov 1996 09:37:21 +0000 ( ) From: Greg Blakely To: Bruce Hamilton cc: majordomo-users@GreatCircle.COM Subject: Re: New install: "Cannot exec '/bin/none' errno=2" In-Reply-To: <199611160211.SAA10825@jasper> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 15 Nov 1996, Bruce Hamilton wrote: > p.p.s. Yes, I added majordom to the list of trusted users in /etc/sendmail.cf and killed and restarted sendmail. > > ### Trusted users > T root daemon uucp majordom > Mine is set up a bit differently, don't know if it matters: #### Trusted users Troot Tdaemon Tuucp Tmajordom # From majordomo-users-owner Sat Nov 16 10:06:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA02648 for majordomo-users-outgoing; Sat, 16 Nov 1996 09:55:52 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA02637 for ; Sat, 16 Nov 1996 09:55:43 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id LAA20931; Sat, 16 Nov 1996 11:56:01 -0600 (CST) To: Bro-Dan@XC.Org Cc: majordomo-users@GreatCircle.COM Subject: Re: no_who References: From: Jason L Tibbitts III Date: 16 Nov 1996 11:56:01 -0600 In-Reply-To: Eutychus II's message of Sat, 16 Nov 1996 08:43:07 -0500 (EST) Message-ID: Lines: 8 X-Mailer: Red Gnus v0.61/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "E" == Eutychus writes: E> Can anyone tell me whether the "no_who" configuration exists in any of E> the most recent versions of Majordomo? If so, which version? 1.94 has who_access and many other access features. - J< From majordomo-users-owner Sat Nov 16 10:47:53 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA04783 for majordomo-users-outgoing; Sat, 16 Nov 1996 10:38:38 -0800 (PST) Received: from hermes.etheron.net (HERMES.ETHERON.NET [200.30.8.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA04763 for ; Sat, 16 Nov 1996 10:38:28 -0800 (PST) Received: from hermes.etheron.net by hermes.etheron.net (NTMail 3.02.10) with ESMTP id oa078560 for ; Sat, 16 Nov 1996 14:40:15 -0400 Message-ID: <328BB428.72F3@etheron.net> Date: Thu, 14 Nov 1996 20:07:04 -0400 From: "Juan J. Vieira" Organization: UCV X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Problem with majordomo Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I Have majordomo 1.94 and perl 5.001 All the configuration are seems to be correct but when i mail a message to majordomo, majordomo create some process but he don't answer and he give a error message "Out of memory". Is it possible that the problem is the version of perl? Thank you Juan J. Vieira From majordomo-users-owner Sat Nov 16 23:23:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id XAA28129 for majordomo-users-outgoing; Sat, 16 Nov 1996 23:15:18 -0800 (PST) Received: from taz.hyperreal.com (taz.hyperreal.com [204.152.144.36]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id XAA28122 for ; Sat, 16 Nov 1996 23:15:10 -0800 (PST) Received: from localhost by taz.hyperreal.com (8.7.6/V2.0) with SMTP id XAA18815; Sat, 16 Nov 1996 23:15:28 -0800 (PST) Date: Sat, 16 Nov 1996 23:15:28 -0800 (PST) From: Brian Behlendorf To: Syed Faraz Shamim cc: majordomo-users@GreatCircle.COM Subject: Re: MAJORDOMO ABORT (fwd) In-Reply-To: <9611141320.AA04041@ponder> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 14 Nov 1996, Syed Faraz Shamim wrote: > IN REPLY TO Majordomo-Owner@psycho.csci.unt.edu MAIL > > > > MAJORDOMO ABORT > > > > chown(1009, 1, "/usr/users/sshamim/majordomo-1.94/lists/test.new"): Operation not permitted > > > > > > 1009 is the uid where majordomo is installed.. when i tried to unsubscribe > a user i got this mail I had problems with the chown's as well. I just commented them out. I haven't seen a problem with this, the files are still under a gid which allows the list owners to edit them. And yes, the wrapper test passed, wrapper was installed correctly. *shrug*. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- brian@hyperreal.com http://www.apache.org http://www.organic.com/jobs From majordomo-users-owner Sun Nov 17 05:18:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id FAA05109 for majordomo-users-outgoing; Sun, 17 Nov 1996 05:14:04 -0800 (PST) Received: from homegate (homegate.mmoran.com [206.138.122.85]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id FAA05102 for ; Sun, 17 Nov 1996 05:13:54 -0800 (PST) Received: from mine.mmoran.com (mine [10.0.2.5]) by homegate (8.6.12/8.6.9) with SMTP id IAA26839 for ; Sun, 17 Nov 1996 08:14:40 -0500 Message-Id: <3.0.32.19961117081042.006e041c@homegate> X-Sender: mmoran@homegate X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 17 Nov 1996 08:14:05 -0500 To: majordomo-users@greatcircle.com From: Mark Moran Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I thought I had everything setup correctly. ./wrapper config-test reports no errors and reports a correct uid of 443 and gid of 2: ------------------ environment variables ------------------ HOME=/usr/majordomo LOGNAME=majordomo MAJORDOMO_CF=/usr/majordomo/majordomo.cf PATH=/bin:/usr/bin SHELL=/bin/bash USER=majordomo --------------------- euid/egid checks --------------------- effective user = majordomo (uid 443) effective group = daemon (gid 2 ) ---------------------- uid/gid checks ---------------------- real user = majordomo (uid 443) real group = daemon (gid 2 ) ----------------------------- ----------------------------- But any command sent to majordomo reports this error: MAJORDOMO ABORT While running with an effective uid of 1 and an effective gid of 1, Majordomo ran into the following problems: Unable to write to log file, check permissions on /usr/majordomo/Log Unable to write to list directory $listdir, check permissions on /usr/majordomo/lists Here's a directory listing: total 225 drwxrwxr-x 6 majordom daemon 1024 Nov 17 08:05 . drwxr-xr-x 18 root root 1024 Nov 16 10:44 .. -rw-rw---- 1 majordom daemon 528 Nov 17 07:18 Log drwxrwx--- 2 majordom daemon 1024 Nov 16 10:44 Tools drwxrwx--- 2 majordom daemon 1024 Nov 16 22:29 bin -rwxrwx--x 1 majordom daemon 2771 Nov 16 10:44 bounce-remind -rwxrwx--x 1 majordom daemon 8827 Nov 16 10:44 config-test -rwxrwx--x 1 majordom daemon 47928 Nov 16 10:44 config_parse.pl drwxrwx--- 6 majordom daemon 1024 Nov 17 07:55 lists -rwxrwx--x 1 majordom daemon 55416 Nov 16 21:57 majordomo -rw-rw-r-- 1 majordom daemon 8630 Nov 16 22:41 majordomo.cf -rw-r--r-- 1 majordom daemon 8629 Nov 16 22:41 majordomo.cf~ -rwxrwx--x 1 majordom daemon 19842 Nov 16 10:44 majordomo.pl -rwxrwx--x 1 majordom daemon 124 Nov 16 10:44 majordomo_version.pl -rwxrwx--x 1 majordom daemon 3486 Nov 16 10:44 request-answer -rwxrwx--x 1 majordom daemon 29602 Nov 16 10:44 resend -rw-rw---- 1 majordom daemon 8620 Nov 16 10:51 sample.cf -rwxrwx--x 1 majordom daemon 7547 Nov 16 10:44 shlock.pl drwxrwx--- 2 majordom daemon 1024 Nov 17 08:05 tmp -rwxr-xr-x 1 majordom daemon 14145 Nov 17 07:57 wrapper From majordomo-users-owner Sun Nov 17 08:03:06 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA07667 for majordomo-users-outgoing; Sun, 17 Nov 1996 07:54:33 -0800 (PST) Received: from mail.his.com (mail.his.com [205.177.25.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id HAA07658 for ; Sun, 17 Nov 1996 07:54:25 -0800 (PST) Received: from [205.177.25.164] (kendall.his.com [205.177.25.164]) by mail.his.com (8.6.9/8.6.12) with ESMTP id KAA25995; Sun, 17 Nov 1996 10:53:29 -0500 Message-Id: In-Reply-To: <3.0.32.19961117081042.006e041c@homegate> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 17 Nov 1996 10:53:34 -0500 To: Mark Moran From: "Kendall P Bullen" Subject: Permissions, or whatever Cc: majordomo-users@greatcircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 8:14 AM -0500 11/17/96, Mark Moran wrote: >While running with an effective uid of 1 and an effective gid of 1, >Majordomo >ran into the following problems: >Unable to write to log file, check permissions on /usr/majordomo/Log >Unable to write to list directory $listdir, check permissions on >/usr/majordomo/lists ... >drwxrwx--- 6 majordom daemon 1024 Nov 17 07:55 lists I thought you needed drwxrwxr-- on lists? >-rwxr-xr-x 1 majordom daemon 14145 Nov 17 07:57 wrapper I thought wrapper was supposed to be setuid and owned by root? Kendall -- Kendall P. Bullen E-mail: kendall@his.com Web: http://www.his.com/~kendall/ From majordomo-users-owner Sun Nov 17 08:18:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA08030 for majordomo-users-outgoing; Sun, 17 Nov 1996 08:12:51 -0800 (PST) Received: from clarinet.synapse.net (clarinet.synapse.net [199.84.54.19]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id IAA08021 for ; Sun, 17 Nov 1996 08:12:42 -0800 (PST) Received: from piano.synapse.net (piano.synapse.net [199.84.54.20]) by clarinet.synapse.net (8.8.2/8.8.2) with ESMTP id LAA05918; Sun, 17 Nov 1996 11:13:01 -0500 (EST) Received: from piano.synapse.net (localhost [127.0.0.1]) by piano.synapse.net (8.8.2/8.8.2) with SMTP id LAA00780; Sun, 17 Nov 1996 11:13:01 -0500 (EST) Date: Sun, 17 Nov 1996 11:13:00 -0500 (EST) From: Evan Champion To: Kendall P Bullen cc: Mark Moran , majordomo-users@GreatCircle.COM Subject: Re: Permissions, or whatever 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 Sun, 17 Nov 1996, Kendall P Bullen wrote: > >drwxrwx--- 6 majordom daemon 1024 Nov 17 07:55 lists > > I thought you needed drwxrwxr-- on lists? No, 770 will do, and in fact you can probably even get away with 700. All the Majordomo programs get run setuid majordomo by the wrapper, so as long as the wrapper is executable then it shouldn't be a problem. > >-rwxr-xr-x 1 majordom daemon 14145 Nov 17 07:57 wrapper > > I thought wrapper was supposed to be setuid and owned by root? That is definitely a problem. Note that group daemon needs to be able to access the directory containing the wrapper, so make the directory containing the wrapper at least *:daemon 750. Evan -- Evan Champion * Director, Network Operations mailto:evanc@synapse.net * Directeur, Exploitation du reseau http://www.synapse.net/ * Synapse Internet From majordomo-users-owner Sun Nov 17 09:18:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA09189 for majordomo-users-outgoing; Sun, 17 Nov 1996 09:12:53 -0800 (PST) Received: from homegate (homegate.mmoran.com [206.138.122.85]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA09181 for ; Sun, 17 Nov 1996 09:12:44 -0800 (PST) Received: from mine.mmoran.com (mine [10.0.2.5]) by homegate (8.6.12/8.6.9) with SMTP id MAA28060 for ; Sun, 17 Nov 1996 12:13:35 -0500 Message-Id: <3.0.32.19961117121259.00726c18@homegate> X-Sender: mmoran@homegate X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 17 Nov 1996 12:13:02 -0500 To: majordomo-users@greatcircle.com From: Mark Moran Subject: Re: Permissions, or whatever Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 10:53 AM 11/17/96 -0500, you wrote: >At 8:14 AM -0500 11/17/96, Mark Moran wrote: > >>While running with an effective uid of 1 and an effective gid of 1, >>Majordomo >>ran into the following problems: >>Unable to write to log file, check permissions on /usr/majordomo/Log >>Unable to write to list directory $listdir, check permissions on >>/usr/majordomo/lists Well I finally got it to work but I had to chmod 666 to Log and 777 to lists. I don't think I should have to allow that broad of access?????? Also for some reason the 'effective' uid and gid is 1: which is bin.bin here. majordomo.daemon is 443.2. So now I get the error: chown(443, 2, "/usr/majordomo/lists/itw-talk.new"): Operation not permitted The file itw-talk.new is created and it's bin.bin?????????????? From majordomo-users-owner Sun Nov 17 09:23:58 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id JAA09095 for majordomo-users-outgoing; Sun, 17 Nov 1996 09:07:19 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id JAA09051 for ; Sun, 17 Nov 1996 09:07:01 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id MAA02936; Sun, 17 Nov 1996 12:07:20 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) with ESMTP id MAA11870; Sun, 17 Nov 1996 12:07:15 -0500 (EST) Message-Id: <199611171707.MAA11870@augusta.math.psu.edu> To: "Juan J. Vieira" cc: majordomo-users@GreatCircle.COM Subject: Re: Problem with majordomo In-reply-to: Your message of "Thu, 14 Nov 1996 20:07:04 -0400." <328BB428.72F3@etheron.net> References: <328BB428.72F3@etheron.net> 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: Sun, 17 Nov 1996 12:07:14 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <328BB428.72F3@etheron.net>, "Juan J. Vieira" writes: >I Have majordomo 1.94 and perl 5.001 >All the configuration are seems to be correct but when i mail a message >to majordomo, majordomo create some process but he don't answer and he >give a error message "Out of memory". > > Is it possible that the problem is the version of perl? Yes, As the FAQ says, Majordomo won't work with perl 5.001 -- it's too buggy. --Dave From majordomo-users-owner Sun Nov 17 13:52:52 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA20768 for majordomo-users-outgoing; Sun, 17 Nov 1996 13:45:31 -0800 (PST) Received: from sun630mp.infomania.com (sun630mp.infomania.com [199.182.37.33]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA20747; Sun, 17 Nov 1996 13:45:19 -0800 (PST) Received: (from tmornini@localhost) by sun630mp.infomania.com (8.7.5/8.7.3) id NAA14343; Sun, 17 Nov 1996 13:45:24 -0800 (PST) From: Tom Mornini Message-Id: <199611172145.NAA14343@sun630mp.infomania.com> Subject: Boing!, the automated list cleaner now updated To: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Date: Sun, 17 Nov 1996 13:45:24 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk My program, Boing!, is now available in version 1.01. Some problems with permissions on the fixed majordomo subscriber list files has been fixed. This program verifies the subscribers of your lists and automatically removes people who want to be removed, or that have addresses that generate bounces. :-) In addition, Boing! now saves backups of everything in its own directory. Previously it was saving list backups in the majordomo list directory, causing some havoc with majordomo's view of the world. As far as I know, this version is now 100% functional. It is still somewhat Sun Solaris oriented, the next version should work on anything that can run Majordomo. It is available from http://www.mornini.com, IP address 199.182.37.203 -- Tom Mornini -- http://www.mornini.com From majordomo-users-owner Sun Nov 17 14:18:49 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA22431 for majordomo-users-outgoing; Sun, 17 Nov 1996 14:07:41 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id OAA22421 for majordomo-users@greatcircle.com; Sun, 17 Nov 1996 14:07:37 -0800 (PST) Received: from sable.nus.sg (sable.nus.sg [137.132.1.21]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id BAA10723 for ; Fri, 15 Nov 1996 01:19:07 -0800 (PST) Received: from leonis.nus.sg (root@leonis.nus.sg [137.132.1.18]) by sable.nus.sg (8.6.10/8.6.9) with ESMTP id RAA00845 for ; Fri, 15 Nov 1996 17:19:05 +0800 Received: from mercy.cwc.nus.sg ([137.132.163.15]) by leonis.nus.sg (8.6.10/8.6.9/CNS-3.5) with SMTP id RAA06052 for ; Fri, 15 Nov 1996 17:19:04 +0800 Message-Id: <2.2.32.19961115092150.006c74a4@leonis.nus.sg> X-Sender: cwcmdv@leonis.nus.sg X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 15 Nov 1996 17:21:50 +0800 To: majordomo-users@greatcircle.com From: "Mercy D. Varakunan" Subject: Cannot unsubscribe Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a list set up. People can subscribe well, and can post messages too. But, When a member of the group tries to unsubscribe, the following message is sent to the owner, and the unsubscription doesn't happen. MAJORDOMO ABORT chmod(33276, "/usr/local/majordomo/lists/sample.new"): Not owner who should be the owner of sample.new? and who is trying to change its mode? I rely on some professional advice from you. (I am using sun solaris machine) Thanks. Mercy. From majordomo-users-owner Sun Nov 17 14:59:08 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA23896 for majordomo-users-outgoing; Sun, 17 Nov 1996 14:38:04 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id OAA22400 for majordomo-users@greatcircle.com; Sun, 17 Nov 1996 14:07:11 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id WAA28542 for ; Thu, 14 Nov 1996 22:04:51 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.2/8.7.3) with ESMTP id BAA03344 for ; Fri, 15 Nov 1996 01:05:05 -0500 (EST) From: Dave Barr Received: (barr@localhost) by augusta.math.psu.edu (8.8.2/8.6.9) id BAA01396 for Majordomo-Users@GreatCircle.COM; Fri, 15 Nov 1996 01:05:03 -0500 (EST) Date: Fri, 15 Nov 1996 01:05:03 -0500 (EST) Message-Id: <199611150605.BAA01396@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.113 1996/11/07 18:48:07 barr Exp barr $ Archive-Name: mail/list-admin/majordomo-faq Posting-Frequency: monthly Note: This FAQ has been recently updated to be exclusively for Majordomo 1.94. If you have a prior release of Majordomo, then you must either upgrade or refer to the old copy of the majordomo FAQ at http://www.math.psu.edu/barr/majordomo-faq-old.html I will not be making any future changes to the old FAQ. Table of Contents: 1. What is Majordomo and how can I get it? + 1.1 - What is Majordomo? + 1.2 - Where do I get Majordomo? + 1.3 - How do I install it? + 1.4 - How do I upgrade from an earlier release? + 1.5 - Where do I report bugs or get help with Majordomo? + 1.6 - Which is better, Majordomo or LISTSERV? 2. Problems setting up Majordomo + 2.1 - What are the proper permissions and ownership of all Majordomo files and directories? + 2.2 - I get "sh: wrapper: cannot execute" or "wrapper: permission denied" + 2.3 - I get "Unknown mailer error" when majordomo runs + 2.4 - I get an error "insecure usage" from the wrapper + 2.5 - I get "majordomo: No such file or directory" from the wrapper + 2.6 - I get an error "Can't locate majordomo.pl" + 2.7 - I told my majordomo.cf where to archive the list, why isn't it working? + 2.8 - config-test can't seem to find ctime.pl + 2.9 - A list is visible via lists, but can't subscribe or 'get' files + 2.10 - I get "Invalid archive directory. Aborting." 3. Setting up mailing lists and aliases + 3.1 - How do I direct bounces to the right address? + 3.2 - Semi-automated handling of bounced mail + 3.3 - What's this Owner-List and List-Owner stuff? Why both? + 3.4 - How should I configure resend for Reply-To headers? + 3.5 - How can I hide lists so they can't be viewed by 'lists'? + 3.6 - How can I restrict a list such that only subscribers can send mail to the list? + 3.7 - Can I have the list owner or approval person be changeable without intervention from the Majordomo owner? + 3.8 - What are all these different passwords? + 3.9 - How do I tell majordomo to handle "get"-ing of binary files? + 3.10 - How do I set up a moderated list? + 3.11 - How do I set up a digested version of a list? + 3.12 - How do I setup virtual majordomo domains? 4. Miscellaneous mailer and other problems + 4.1 - Address with blanks are being treated separately + 4.2 - Why aren't my digests going out? + 4.3 - Why do I get duplicate mail sent to the list? + 4.4 - How do I gate my list to and/or from a newsgroup? + 4.5 - How can I improve Majordomo's performance? + 4.6 - How can I handle X.400 addresses? This FAQ is Copyright 1996 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? 1.1 - 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 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). _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. It will work with Perl 4.036 or Perl 5.002 or greater. It will _not work with Perl 5.001!!! It has reportedly worked with Perl 5.000 on some but not all platforms_. This is due to bugs in Perl which have since been fixed. It is recommended that you use the latest release of Perl that you can get, which can be found at http://www.perl.com/perl/. While Majordomo 1.94 is still compatible with Perl 4.036, future versions will likely be Perl 5 only. 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 (version 5.002 is known to work). 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. 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. * Supports confirmation of subscriptions (to protect against forged subscription requests). * List filters There is a World Wide Web interface for Majordomo and other mail servers, called "Mailserv". Check it out at http://iquest.com/~fitz/www/mailserv/. There's also another one called LWGate at http://www.netspace.org/~dwb/lwgate.html. There's also "MajorCool" at http://www.digitalmasters.com/~bhoule/. 1.2 - Where do I get Majordomo? Via anonymous FTP at: ftp://ftp.greatcircle.com/pub/majordomo/ The current version is 1.94. This release is significantly easier to install and offers many features over 1.93. (Subscription confirmations, "taboo" checks to forward matched messages for approval, finer grained access control to who/which/get/index/info/intro, "config-test" script to test your installation, improvements to digest, and more) If you don't have Perl, you can get it from: http://www.perl.com/perl/ Use that link for more information about Perl, too. The FTPMAIL package can be found in ftp://src.doc.ic.ac.uk/packages/ftpmail or any comp.sources.misc archive (volume 37). 1.3 - How do I install it? Majordomo comes with a rather extensive INSTALL file. Read this file completely. There's also a README file which also covers some common problems. 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 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 tar to ignore user/group information. 1.4 - How do I upgrade from an earlier release? Be sure to browse the "Changelog" file 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. Be careful in upgrading to 1.94 that you update your $mailer and $bounce_mailer variables in your majordomo.cf! There are also some other new variables too. You may want to update the list .config files so they contain any new variables found in the new release. You just need to do a 'writeconfig' for each list, and majordomo will update the .config file using the existing values in the old .config file. Any new variables will be set to defaults for a new list. 1.5 - 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 actual bugs to majordomo-workers@greatcircle.com. (check the list archives below to see if the bug hasn't been reported or fixed already) 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. You can search the majordomo-workers and majordomo-users archives at http://www.meadow.net/Majordomo/ 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. 1.6 - 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 2.1 - 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. Once you install majordomo, run "./wrapper config-test" as some other user (like you) and read the results. Do _NOT_ run "./wrapper config-test" as 'root' or your 'majordom' user. That will defeat the test of the wrapper operation. The config-test script will check your installation for correct permissions (as well as other tests) and report any problems. It's not quite perfect, but it catches 95% of all problems. 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. The 1.94 INSTALL file suggests using 'daemon' as your majordomo group. This is the group that 'sendmail' runs as, and allows you to have $homedir permissions set to 750. This has the disadvantage in environments where there may be one or more administrators of the Majordomo system or where you don't want to always have to 'su' the the majordomo user to do administration. (you don't really want to put other normal users in the 'daemon' group for security reasons) If you create a separate 'majordom' group and add yourself and other majordomo administrators to it, then you'll need to make sure the $homedir and wrapper have world execute permission, and you may have to add 'majordom' to the 'trusted' list of users in your sendmail.cf. 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.94 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, IRIX 5.x, BSDI (and presumably other 4.4 BSD-based systems), Linux. Make sure W_PATH is right in the Makefile. On IRIX 5.x, you need to add /usr/bsd to the W_PATH to get the hostname (needed by Perl) command. (IRIX doesn't have a /usr/ucb). 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_USER and W_GROUP are the uid and gid of the "majordom" user and group. Don't ever set W_USER to be 0! Then compile the wrapper and install it. Do not install the wrapper on an NFS filesystem mounted 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 (see $config_umask in the majordomo.cf). 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. (they 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. All Majordomo programs must have the correct path to Perl in the #! line in the beginning of the script. The 'make install' process should do this all automatically for you. Majordomo directories All directories under Majordomo's control ($homedir, $listdir, $digest_work_dir, $filedir, as defined in your majordomo.cf) must be at least mode 750 (or 755). 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 then group-"majordom" writeable (770 or 775). 2.2 - I get "sh: wrapper: cannot execute" or "wrapper: permission denied" This is a bug in the 1.94 Makefile. You'll see this in new installs of Majordomo, if you don't use a majordomo group of 'daemon'. The majordomo $homedir needs to have permission of 755, not 750 otherwise sendmail won't have permission to execute the wrapper. You'll need to do a 'chmod 755 $homedir' after you install majordomo. Make sure 'wrapper' also has world execute permission. 2.3 - 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. See section 1.1> above for what versions of Perl won't work with Majordomo. 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 in spite of the lines shown by mailq. This is sendmail 5.x on Solaris 2.3, but it might apply to other versions of sendmail. 2.4 - 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_HOME" 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" 2.5 - 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_HOME directory as defined in the Makefile when you compiled the wrapper. 2.6 - 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. 2.7 - 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. 2.8 - config-test can't seem to find ctime.pl ctime.pl is included in the standard Perl distribution. If it can't find it, it means Perl was not installed correctly. Re-install Perl. (you may want to take the opportunity to upgrade Perl, too) 2.9 - 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. 2.10 - 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 3.1 - 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, administrivia checks, and others. 3.2 - Semi-automated handling of bounced mail This isn't true automation of bounced mail which is very hard to do, but getting easier thanks to a standardized format of delivery status messages. It's still hard because delivery sometimes can fail temporarily (due to temporary problems on the local host, such as NIS failures, disk failures, etc) and you don't want to necessarily take that person off the list immediately once you get a bounce message. What this does is the next best thing. You unsubscribe the user from the list, but add the user to a special 'bounces' list. The majordomo maintainer then runs (out of cron) the 'bounce-remind' script periodically, which sends mail to all the people on the bounces list, saying essentially "you were removed from list 'foo' because mail to you bounced. To subscribe yourself back to the list, send the following commands ...". There's no facility yet for trimming the bounces list, but it's easy to write one because the date the person was added to the bounces list is included (so you could write a perl script which removes anyone on the list for more than one week, assuming you run bounce-remind more than once a week). [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. 3.3 - 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". 3.4 - 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. 3.5 - 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. 3.6 - How can I restrict a list such that only subscribers can send mail to the list? See 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. (for example "mylist:|"/usr/local/lib/majordomo/wrapper resend -h foo.org -l mylist mylist,nobody"" where nobody is an alias for /dev/null) 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. 3.7 - 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) 3.8 - What are all these different passwords? 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. 3.9 - 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. 3.10 - 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". Do not try to use the now-deprecated "-A" option to resend. In fact you shouldn't be using ANY options to resend except "-h" and "-l", since all the others are handled in the config file. 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 entire contents of the original message. (meaning there should be a blank line before and after the "Approved:" line.) 3.11 - 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 use cron to send a mkdigest to push out a digest at set intervals regardless of the number of queued messages. See the question Why aren't my digests going out?". 3.12 - How do I setup virtual majordomo domains? [From Alan Millar, et. al.] Set up a majordomo.cf file for each virtual domain, defining $whereami as appropriate. Use your mailer's virtual domain stuff to get to it, making an alias for it if necessary. Alias entry: majordomo-domain2: |/your/wrapper majordomo -C /your/domain2.cf Virtual domain stuff: majordomo@domain2 = majordomo-domain2 majordomo-owner@domain2 = whoever I use the sendmail virtual domain examples right off the Sendmail FAQ. Works for me. You'll need to modify request-answer slightly if you want the virtual host to be used there in replies. Look for: From: $list-request in the source and change it to: From: $list-request\@$whereami Don't forget to use the -C option to request-answer for your virutal aliases. _________________________________________________________________ Section 4: Miscellaneous mailer problems 4.1 - 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 change to "strip = yes" in the config file so that none of the addresses are angle-bracketed. 4.2 - Why aren't my digests going out? [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. 4.3 - Why do I get duplicate mail sent to the list? If 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 ] 4.4 - How do I gate my list to and/or from a newsgroup? The easiest method is to use a program called newsgate. You can find it at http://www.isc.org/isc/. Installation instructions are straightforward, it provides sample entires for your newsfeeds/sys file and aliases entries. The newsgate package includes news2mail and mail2news. 4.5 - 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.x 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 in the way of 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. (no reports of using majordomo with qmail) 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" bulk_mailer 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 did have one problem. Until version 1.3 it didn't understand parenthesized comments in addresses, resulting in incorrect sorting and reduced performance. Your list must be configured with strip=yes in the configuration file if you don't upgrade to 1.3. 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. 4.6 - 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 "/". See the $no_x400at and $no_true_x400 variables and the associated comments in the majordomo.cf. There is a reported bug in 1.94 - you may need to change both tests for these variables in majordomo.pl to put "main'" before them. Like this: if (!$main'no_x400at) { if (!$main'no_true_x400) { From majordomo-users-owner Mon Nov 18 01:18:01 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id BAA10388 for majordomo-users-outgoing; Mon, 18 Nov 1996 01:03:31 -0800 (PST) Received: from thoth.mch.sni.de (thoth.mch.sni.de [192.35.17.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id BAA10370 for ; Mon, 18 Nov 1996 01:03:05 -0800 (PST) Received: from ares.mch.sni.de (ares.mch.sni.de [139.22.8.162]) by thoth.mch.sni.de (8.7.6/8.7.3) with SMTP id KAA03807 for ; Mon, 18 Nov 1996 10:03:23 +0100 (MET) Received: from gvkirsche.mch.sni.de ([139.22.8.207]) by ares.mch.sni.de (4.1/SMI-4.1) id AA23112; Mon, 18 Nov 96 10:02:25 +0100 Message-Id: <3290274C.426D@mch.sni.de> Date: Mon, 18 Nov 1996 10:07:24 +0100 From: Wilfried Wiehler Reply-To: Wilfried.Wiehler@mch.sni.de Organization: Siemens Nixdorf AG X-Mailer: Mozilla 3.0 (Win95; I) Mime-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Setup problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello there, I am new to Majordomo, and seem to have a setup problem: ares{wiehler}:/home/wiehler:7% echo 'lists' | mail -v majordomo majordomo... aliased to "|/usr/local/bin/majordomo/wrapper majordomo" "|/usr/local/bin/majordomo/wrapper majordomo"... Connecting to via prog... "|/usr/local/bin/majordomo/wrapper majordomo"... unknown mailer error 1 I have read the FAQ three times, did a config-test (see below), hacked about one week (o.k., only parttime), but I still did not find any reason. I suspect it to be access rights, sendmail or the POSIX section. Any help? Thanks in advance, Wilfried My configuration: SunOS ares 4.1.3_U1 4 sun4m (This is non-POSIX, but I had to hack the POSIX section to get the Makefile running) perl, version 5.002 beta3 sendmail version unknown (how do I get this?) Access rights: ares{wiehler}:/usr/local/bin/majordomo:18% ls -lag total 1098 drwxrwsr-x 9 majordom daemon 1024 Nov 18 09:25 ./ drwxr-sr-x 3 root staff 2560 Oct 28 14:39 ../ -rw-r--r-- 1 majordom daemon 7476 Oct 29 11:01 .cshrc drwxrwsr-x 2 majordom daemon 512 Nov 15 14:36 Log/ drwxr-sr-x 2 majordom daemon 512 Nov 15 14:58 Tools/ drwxrwsr-x 2 majordom daemon 512 Nov 15 14:58 bin/ -rwxr-xr-x 1 majordom daemon 2771 Nov 15 14:58 bounce-remind* -rwxr-xr-x 1 majordom daemon 8827 Nov 15 14:58 config-test* -rwxr-xr-x 1 majordom daemon 47928 Nov 15 14:58 config_parse.pl* drwxrwsr-x 2 majordom daemon 512 Nov 15 14:36 lists/ -rwxr-xr-x 1 majordom daemon 55403 Nov 15 14:58 majordomo* drwxrwsr-x 6 majordom daemon 1024 Nov 15 14:58 majordomo-1.94/ -rwxr--r-- 1 majordom daemon 6874 Nov 15 12:27 majordomo-1_94.license* -rwxr--r-- 1 majordom daemon 22123 Nov 15 12:27 majordomo-1_94.readme* -rwxr--r-- 1 majordom daemon 839680 Nov 15 12:27 majordomo-1_94.tar* -rw-r--r-- 1 majordom daemon 8626 Nov 15 14:58 majordomo.cf -rwxr-xr-x 1 majordom daemon 19842 Nov 15 14:58 majordomo.pl* -rwxr-xr-x 1 majordom daemon 124 Nov 15 14:58 majordomo_version.pl* drwxr-sr-x 4 majordom daemon 512 Nov 15 14:58 man/ -rwxr-xr-x 1 majordom daemon 3486 Nov 15 14:58 request-answer* -rwxr-xr-x 1 majordom daemon 29602 Nov 15 14:58 resend* -rw-r--r-- 1 majordom daemon 8627 Nov 15 14:58 sample.cf drwxr-xr-x 3 majordom daemon 512 Nov 15 12:26 save/ -rwxr-xr-x 1 majordom daemon 7547 Nov 15 14:58 shlock.pl* -rwsr-sr-x 1 majordom daemon 24576 Nov 15 14:59 wrapper* majordomo.cf: $whereami = "ares.mch.sni.de"; $whoami = "majordomo\@whereami"; $whoami_owner = "majordomo-owner\@$whereami"; if ( defined $ENV{"HOME"}) { $homedir = $ENV{"HOME"}; } else { $homedir = "/usr/test/majordomo"; } $listdir = "$homedir/lists"; $digest_work_dir = '/usr/local/mail/digest'; $log = "$homedir/Log"; $sendmail_command = "/usr/lib/sendmail"; $mailer = "$sendmail_command -oi -f\$sender"; $bounce_mailer = "$sendmail_command -oi -f\$sender -t"; makefile: PERL = /usr/bin/perl CHOWN = chown W_HOME = /usr/local/bin/majordomo W_MAN = $(W_HOME)/man MAN1 = $(W_HOME)/man/man1 MAN8 = $(W_HOME)/man/man8 W_CHMOD = 6755 W_PATH = /bin:/usr/bin:/usr/ucb W_BIN = $(W_HOME) W_SHELL = /bin/csh W_MAJORDOMO_CF = /usr/local/bin/majordomo/majordomo.cf W_USER = 30005 W_GROUP = 1 W_CHOWN = $(W_USER).$(W_GROUP) #------------- POSIX SECTION ----------------------------- # If you're running on a POSIX complient system: # Sun Solaris, # SGI Irix 5 and 6, # Dec Ultrix MIPS, # BSDI, # Linux # make sure the following are uncommented. # (Sun SunOS, SGI Irix 4, and HP DomainOS are NOT POSIX!!) # WRAPPER_CHOWN = 30005 WRAPPER_CHMOD = 6755 #POSIX = -DPOSIX_UID=$(W_USER) -DPOSIX_GID=$(W_GROUP) /etc/aliases: owner-owner: postmaster majordom: owner-majordomo majordomo: "|/usr/local/majordomo/wrapper majordomo" owner-majordomo: wiehler majordomo-owner: wiehler /etc/passwd: daemon:*:1:1::/: majordom:xlJUIN./YcINo:30005:1::/usr/local/bin/majordomo:/bin/csh /etc/group: daemon:*:1: majordom:*:3030:majordom ares{wiehler}:/usr/local/bin/majordomo:19% ./wrapper config-test --------------------- Obvious things: --------------------- ------------------ environment variables ------------------ HOME=/usr/local/bin/majordomo LOGNAME=wiehler MAJORDOMO_CF=/usr/local/bin/majordomo/majordomo.cf PATH=/bin:/usr/bin:/usr/ucb SHELL=/bin/csh USER=wiehler --------------------- euid/egid checks --------------------- effective user = majordom (uid 30005) effective group = daemon NISadmin bp42 bp42b (gid 1 2000 1000 1300 ) ---------------------- uid/gid checks ---------------------- real user = majordom (uid 30005) real group = daemon NISadmin bp42 bp42b (gid 1 2000 1000 1300 ) ----------------------------- ----------------------------- Non obvious things that cause headaches: ----------------------------- ----------------------------- Good: "require"d /usr/local/bin/majordomo/majordomo.cf okay. Good: found ctime.pl okay. Good: found majordomo_version.pl okay. Good: found majordomo.pl okay. Good: found shlock.pl okay. Good: found config_parse.pl okay. You're running Majordomo Version 1.94. --==> Majordomo home directory is /usr/local/bin/majordomo. ------------------- Include directories ------------------- /usr/local/bin/majordomo /usr/local/lib/perl5/sun4-sunos/5.002 /usr/local/lib/perl5 /usr/local/lib/perl5/site_perl/sun4-sunos /usr/local/lib/perl5/site_perl . --------------------------- Home --------------------------- Good: changedir to /usr/local/bin/majordomo succeeded. Good: Created a mock lock file. ---------------------- temp directory ---------------------- Good: Created a temp file in $TMPDIR (/usr/tmp). ---------------------- list directory ---------------------- Good: list directory /usr/local/bin/majordomo/lists has good permissions. --------------------------- log --------------------------- Good: logfile /usr/local/bin/majordomo/Log exists and is writeable. ------------------------- Mailers ------------------------- You have defined a mailer for delivery. Attempting to verify that this is a valid mailer...looks okay. You have defined a mailer for delivering administrative messages. Attempting to verify that this is a valid mailer...looks okay. ------------------ Checking majordomo.cf ------------------ Checking to see if there are new variables that should be in your majordomo.cf file...Nope, none that I see. ----------------------- end of tests ----------------------- From majordomo-users-owner Mon Nov 18 01:33:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id BAA11905 for majordomo-users-outgoing; Mon, 18 Nov 1996 01:29:34 -0800 (PST) Received: from galleria (www.televisual.it [195.32.0.37]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id BAA11863 for ; Mon, 18 Nov 1996 01:29:11 -0800 (PST) Received: from telephony.televisual.it by galleria (SMI-8.6/SMI-SVR4) id KAA04124; Mon, 18 Nov 1996 10:25:41 -0800 Message-Id: <199611181825.KAA04124@galleria> Comments: Authenticated sender is From: "Cristian D'Aloisio" To: majordomo-users@greatcircle.com Date: Mon, 18 Nov 1996 10:31:18 +0000 Subject: Mail loops back error Reply-to: cristian@televisual.it X-mailer: Pegasus Mail for Win32 (v2.31) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi to all. I'm setting a list with magiordomo vers. 1.93. When I use an open list, i.e. any subscribed user can post text, all is ok. Now I want a moderated list, so I put yes to the list config file. The owner list receive: Date sent: Thu, 14 Nov 1996 17:15:10 -0800 From: Mailer-Daemon (Mail Delivery Subsystem) Subject: Returned mail: Local configuration error To: owner-telev-bo To: postmaster The original message was received at Thu, 14 Nov 1996 17:15:09 -0800 from root@localhost ********************************************************************* ----- The following addresses had delivery problems ----- owner-telev-bo@www.televisual.it (unrecoverable error) ----- Transcript of session follows ----- 553 galleria config error: mail loops back to myself 554 owner-telev-bo@www.televisual.it... Local configuration error Message delivered to mailing list owner-telev-bo ----- Original message follows ----- Return-Path: Received: by galleria (SMI-8.6/SMI-SVR4) id RAA29653; Thu, 14 Nov 1996 17:15:09 -0800 Date: Thu, 14 Nov 1996 17:15:09 -0800 Message-Id: <199611150115.RAA29653@galleria> To: owner-telev-bo@www.televisual.it From: owner-telev-bo@www.televisual.it Subject: BOUNCE telev-bo@www.televisual.it: Approval required content-length: 552 >From info@www.televisual.it Thu Nov 14 17:15:08 1996 Return-Path: Received: from telephony.televisual.it by galleria (SMI-8.6/SMI-SVR4) id RAA29648; Thu, 14 Nov 1996 17:15:07 -0800 Message-Id: <199611150115.RAA29648@galleria> Comments: Authenticated sender is From: "Televisual Info" To: telev-bo@televisual.it Date: Thu, 14 Nov 1996 17:21:10 +0000 Subject: test con moderator Priority: normal X-mailer: Pegasus Mail for Win32 (v2.31) content-length: 19 test with a moderator ********************************************************************* The /etc/aliases file contains: owner-owner: postmaster # # Majordomo # owner-majordomo: cristian majordomo: "|/export/majordomo/wrapper majordomo" majordom: owner-majordomo # per majordomo 1.9x Majordomo-Owner: owner-majordomo # Inizio definizione Lista telev-bo # ##################################### owner-telev-bo: cristian , nobody telev-bo: "|/export/majordomo/wrapper resend -l telev-bo -h www.televisual.it telev-bo-outgoing" telev-bo-approval: owner-telev-bo telev-bo-outgoing: :include:/export/majordomo/lists/telev-bo owner-telev-bo-outgoing: owner-telev-bo telev-bo-request: "|/export/majordomo/wrapper request-answer telev-bo" owner-telev-bo-request: owner-telev-bo # Fine definizione lista telev-bo # ######################################## Have you any tip? Bye Cristian ======================================= PC programming & system administration for Televisual s.r.l (Bologna) Italy --------------------------------------- Ufficio / Office info: (++39) (051) 247536 (++39) (051) 240299 fax cristian@televisual.it --------------------------------------- Privato / Home: (++39) (051)470286 dif1754@iperbole.bologna.it ======================================= From majordomo-users-owner Mon Nov 18 10:26:23 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA03885 for majordomo-users-outgoing; Mon, 18 Nov 1996 10:11:52 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA03834 for ; Mon, 18 Nov 1996 10:11:30 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA14972 for majordomo-users@GreatCircle.COM; Mon, 18 Nov 96 11:11:51 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA18724 for majordomo-users@GreatCircle.COM; Mon, 18 Nov 96 11:11:50 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id MAA07632; Mon, 18 Nov 1996 12:11:49 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id MAA15196; Mon, 18 Nov 1996 12:11:48 -0600 From: Dave Wolfe Message-Id: <199611181811.MAA15196@miaow.risc.sps.mot.com> Subject: Re: MAJORDOMO ABORT (fwd) To: brian@hyperreal.com (Brian Behlendorf) Date: Mon, 18 Nov 1996 12:11:48 -0600 (CST) Cc: sshamim@ponder.csci.unt.edu, majordomo-users@GreatCircle.COM In-Reply-To: from "Brian Behlendorf" at Nov 16, 96 11:15:28 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Brian Behlendorf writes: ] > > On Thu, 14 Nov 1996, Syed Faraz Shamim wrote: > > IN REPLY TO Majordomo-Owner@psycho.csci.unt.edu MAIL > > > > > > MAJORDOMO ABORT > > > > > > chown(1009, 1, "/usr/users/sshamim/majordomo-1.94/lists/test.new"): Operation not permitted > > > > > > > 1009 is the uid where majordomo is installed.. when i tried to unsubscribe > > a user i got this mail > > I had problems with the chown's as well. I just commented them out. I > haven't seen a problem with this, the files are still under a gid which > allows the list owners to edit them. And yes, the wrapper test passed, > wrapper was installed correctly. *shrug*. Depending on how you were logged in when you ran config-test, wrapper can be installed quite incorrectly and config-test still say everything's just peachy. You both have installation problems or the system wouldn't complain about chown. -- Dave Wolfe From majordomo-users-owner Mon Nov 18 10:34:19 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA04169 for majordomo-users-outgoing; Mon, 18 Nov 1996 10:18:27 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA04122 for ; Mon, 18 Nov 1996 10:18:05 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA15909 for majordomo-users@greatcircle.com; Mon, 18 Nov 96 11:18:27 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA19032 for majordomo-users@greatcircle.com; Mon, 18 Nov 96 11:18:22 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id MAA07692; Mon, 18 Nov 1996 12:18:21 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id MAA15231; Mon, 18 Nov 1996 12:18:20 -0600 From: Dave Wolfe Message-Id: <199611181818.MAA15231@miaow.risc.sps.mot.com> Subject: Re: Returned mail: Internal error: Error 0 (fwd) To: cae@ns.ucb.edu.bo (Carlos Eduardo Anibarro Zelaya) Date: Mon, 18 Nov 1996 12:18:20 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Carlos Eduardo Anibarro Zelaya" at Nov 14, 96 01:07:29 pm Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Carlos Eduardo Anibarro Zelaya writes: ] > > We have installed the Majordomo 1-94 program sucessfully. > > After creating a test list, when you try to send a mail to test@... it > returns this error to the owner: [...] > ----- Transcript of session follows ----- > /usr/local/majordom/wrapper: error: Not running with proper UID and GID. > Make certain that wrapper is installed setuid, and if so, > recompile with POSIX flags. So did you do what it said? Reconfigure your Makefile using the POSIX options, remove wrapper, run 'make wrapper'. Then su and run 'make install-wrapper'. -- Dave Wolfe From majordomo-users-owner Mon Nov 18 11:05:06 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA06040 for majordomo-users-outgoing; Mon, 18 Nov 1996 10:48:49 -0800 (PST) Received: from jhuml1.hcf.jhu.edu (jhuml1.hcf.jhu.edu [128.220.2.86]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA06005 for ; Mon, 18 Nov 1996 10:48:34 -0800 (PST) Received: from chaos.press.jhu.edu by jhmail.hcf.jhu.edu (PMDF V5.0-7 #13870) id <01IBZRUAKNHC9TDP3P@jhmail.hcf.jhu.edu> for majordomo-users@greatcircle.com; Mon, 18 Nov 1996 13:47:55 -0500 (EST) Received: from chaos.press.jhu.edu by jhmail.hcf.jhu.edu (PMDF V5.0-7 #13870) id <01IBZRT42VJ69TDMPV@jhmail.hcf.jhu.edu> for majordomo-users@greatcircle.com; Mon, 18 Nov 1996 13:46:18 -0500 (EST) Received: by chaos.press.jhu.edu (940816.SGI.8.6.9/940406.SGI.AUTO) for majordomo-users@greatcircle.com id NAA03687; Mon, 18 Nov 1996 13:46:13 -0500 Date: Mon, 18 Nov 1996 13:46:11 -0500 From: Ken Overton Subject: No doc for resend ? To: majordomo-users@greatcircle.com Message-id: <9611181346.ZM3685@chaos.press.jhu.edu> MIME-version: 1.0 X-Mailer: Z-Mail (3.2.1 6apr95 MediaMail) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm trying very hard to RTFM and avoid spamming the group, but I can't seem to find any documentation on the "resend" program for me to read. There was also no Manifest with the distribution, so I don't know if everything's here. If anyone knows of a manpage, FAQ portion, clay tablet, *anything* that really explains resend, I'd rather not go through the code. If none exists I guess I could make one, as this seems to me to be an integral part of the Majordomo package and deserving of documentation. -- kov -- Ken Overton kov@jhu.edu Internet Sysadmin JHU Press -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Finger kov@chaos.press.jhu.edu for public key. From majordomo-users-owner Mon Nov 18 11:19:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA07962 for majordomo-users-outgoing; Mon, 18 Nov 1996 11:16:22 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id LAA07954 for ; Mon, 18 Nov 1996 11:16:09 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA24150 for majordomo-users@greatcircle.com; Mon, 18 Nov 96 12:16:28 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA21025 for majordomo-users@greatcircle.com; Mon, 18 Nov 96 12:16:23 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id NAA08302; Mon, 18 Nov 1996 13:16:23 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id NAA15211; Mon, 18 Nov 1996 13:16:21 -0600 From: Dave Wolfe Message-Id: <199611181916.NAA15211@miaow.risc.sps.mot.com> Subject: Re: your mail To: mmoran@mmoran.com (Mark Moran) Date: Mon, 18 Nov 1996 13:16:21 -0600 (CST) Cc: majordomo-users@greatcircle.com In-Reply-To: <3.0.32.19961117081042.006e041c@homegate> from "Mark Moran" at Nov 17, 96 08:14:05 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Mark Moran writes: ] > > But any command sent to majordomo reports this error: > > MAJORDOMO ABORT > > While running with an effective uid of 1 and an effective gid of 1, Majordomo > ran into the following problems: > Unable to write to log file, check permissions on /usr/majordomo/Log > Unable to write to list directory $listdir, check permissions on > /usr/majordomo/lists > > Here's a directory listing: [...] > -rwxr-xr-x 1 majordom daemon 14145 Nov 17 07:57 wrapper ^ ^^^^^^^^ You didn't install wrapper correctly. Su to root before running 'make install-wrapper'. -- Dave Wolfe From majordomo-users-owner Mon Nov 18 11:53:12 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA08735 for majordomo-users-outgoing; Mon, 18 Nov 1996 11:37:51 -0800 (PST) Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id LAA08707 for ; Mon, 18 Nov 1996 11:37:28 -0800 (PST) Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.8.3/8.7.3) with ESMTP id OAA19179; Mon, 18 Nov 1996 14:37:48 -0500 (EST) Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.8.3/8.6.9) with ESMTP id OAA16923; Mon, 18 Nov 1996 14:37:44 -0500 (EST) Message-Id: <199611181937.OAA16923@augusta.math.psu.edu> To: Ken Overton cc: majordomo-users@GreatCircle.COM Subject: Re: No doc for resend ? In-reply-to: Your message of "Mon, 18 Nov 1996 13:46:11 EST." <9611181346.ZM3685@chaos.press.jhu.edu> References: <9611181346.ZM3685@chaos.press.jhu.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: Mon, 18 Nov 1996 14:37:43 -0500 From: Dave Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <9611181346.ZM3685@chaos.press.jhu.edu>, Ken Overton writes: >If anyone knows of a manpage, FAQ portion, clay tablet, *anything* that really >explains resend, I'd rather not go through the code. If none exists I guess I >could make one, as this seems to me to be an integral part of the Majordomo >package and deserving of documentation. there was a resend.README which was removed because it's out of date. All options to resend except -l and -h have been deprecated, so what's in NEWLIST should really be sufficient though it could perhaps be explained a little clearer. I suggest you submit a patch to Chan for new wording in NEWLIST. --Dave From majordomo-users-owner Mon Nov 18 18:48:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA06856 for majordomo-users-outgoing; Mon, 18 Nov 1996 18:39:09 -0800 (PST) Received: from azimov.lib.uaa.alaska.edu ([137.229.112.145]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id SAA06849 for ; Mon, 18 Nov 1996 18:38:45 -0800 (PST) Received: from dickens (dickens.lib.uaa.alaska.edu [137.229.112.148]) by azimov.lib.uaa.alaska.edu (8.6.11/8.6.9) with SMTP id RAA00730; Mon, 18 Nov 1996 17:38:23 -0900 Message-ID: <32911DA9.324A@uaa.alaska.edu> Date: Mon, 18 Nov 1996 17:38:33 -0900 From: Michael Tibor Organization: University of Alaska Anchorage X-Mailer: Mozilla 3.01 (WinNT; I) MIME-Version: 1.0 To: Wilfried.Wiehler@mch.sni.de CC: majordomo-users@greatcircle.com Subject: Re: Setup problem References: <3290274C.426D@mch.sni.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Wilfried Wiehler wrote: > > Hello there, > > I am new to Majordomo, and seem to have a setup problem: > > My configuration: > > SunOS ares 4.1.3_U1 4 sun4m > (This is non-POSIX, but I had to hack the POSIX section to get the > Makefile running) > perl, version 5.002 beta3 > sendmail version unknown (how do I get this?) I didn't think Majordomo liked PERL version 5.002, but don't quote me, because I don't have a whole lot of experience with PERL. The latest version I think is 5.003 tho. BTW-- you can check your sendmail version by telnetting to your machine on port 25 (instead of port 23, the normal telnet port). Hope that helps, Mike From majordomo-users-owner Mon Nov 18 19:10:50 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA07863 for majordomo-users-outgoing; Mon, 18 Nov 1996 18:52:43 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id SAA07855 for majordomo-users@greatcircle.com; Mon, 18 Nov 1996 18:52:39 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id AAA11607 for ; Sat, 16 Nov 1996 00:09:24 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id CAA11169; Sat, 16 Nov 1996 02:06:27 -0600 (CST) To: "Mercy D. Varakunan" Cc: Majordomo-Users@GreatCircle.COM Subject: Re: majordomo or majordom? References: <2.2.32.19961114023538.006972cc@leonis.nus.sg> From: Jason L Tibbitts III Date: 16 Nov 1996 02:06:26 -0600 In-Reply-To: "Mercy D. Varakunan"'s message of Thu, 14 Nov 1996 10:35:38 +0800 Message-ID: Lines: 21 X-Mailer: Red Gnus v0.61/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "MDV" == Mercy D Varakunan writes: MDV> So, any mail to majordomo should be sent to majordom@hostname ( for MDV> subscriobe unsubscribe etc), am I right? Or is it still MDV> majordomo@hostname? It should be sent to whatever you called the alias. It could be: Majordomo: "|/path/to/wrapper majordomo" (in which case you send mail to "majordomo@host") or perhaps blurfl: "|/path/to/wrapper majordomo" in which case you send mail to blurfl@host. The ID you created is only for the purposes of permission checking by your operating system. I use "lists" on my system (hey, it's shorter), but mail is still sent to majordomo@my.host. - J< From majordomo-users-owner Mon Nov 18 19:15:20 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA08998 for majordomo-users-outgoing; Mon, 18 Nov 1996 19:02:05 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id TAA08988 for majordomo-users@greatcircle.com; Mon, 18 Nov 1996 19:02:01 -0800 (PST) Received: from eclectic.kluge.net (eclectic.kluge.net [130.215.248.68]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id RAA25045 for ; Fri, 15 Nov 1996 17:43:09 -0800 (PST) Received: from localhost (felicity@localhost) by eclectic.kluge.net (8.8.2/8.8.2) with SMTP id UAA28373; Fri, 15 Nov 1996 20:44:59 -0500 Date: Fri, 15 Nov 1996 20:44:59 -0500 (EST) From: Theo Van Dinter To: "Mercy D. Varakunan" cc: Majordomo-Users@GreatCircle.COM Subject: Re: majordomo or majordom? In-Reply-To: <2.2.32.19961114023538.006972cc@leonis.nus.sg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 14 Nov 1996, Mercy D. Varakunan wrote: > I am trying to set up majordomo. The user name I created for majordomo > is majordom. So, any mail to majordomo should be sent to > majordom@hostname ( for subscriobe unsubscribe etc), am I right? Or is > it still majordomo@hostname? it's still majordomo (or actually, whatever you set the alias up as...) The username doesn't need to match the mail name. -- ----------------------------------------------------------------------------- Theo Van Dinter www: http://www.kluge.net/~felicity/ Vice-President WPI Lens and Lights Active Member in SocComm Films Member of WPI ACM AME for the Masque B-Term Show 3 dreaded words when making love: "Is that it?" ----------------------------------------------------------------------------- From majordomo-users-owner Mon Nov 18 19:18:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA07910 for majordomo-users-outgoing; Mon, 18 Nov 1996 18:53:01 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id SAA07885 for majordomo-users@greatcircle.com; Mon, 18 Nov 1996 18:52:54 -0800 (PST) Received: from camco2.celestial.com (camco2.celestial.com [192.136.111.3]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA00898 for ; Sat, 16 Nov 1996 09:16:11 -0800 (PST) Received: by camco2.celestial.com (Smail3.1.29.1 #8) id m0vOoKq-000EmyC; Sat, 16 Nov 96 09:15 PST Message-Id: From: bill@celestial.com (Bill Campbell) Subject: Re: majordomo or majordom? To: cwcmdv@leonis.nus.sg (Mercy D. Varakunan) Date: Sat, 16 Nov 1996 09:15:15 -0800 (PST) Cc: Majordomo-Users@greatcircle.com In-Reply-To: <2.2.32.19961114023538.006972cc@leonis.nus.sg> from "Mercy D. Varakunan" at Nov 14, 96 10:35:38 am Reply-To: bill@Celestial.COM Organization: Celestial Software, Mercer Island, WA 98040 X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > > >Hi, > >I am trying to set up majordomo. The user name I created for majordomo is >majordom. So, any mail to majordomo should be sent to majordom@hostname ( >for subscriobe unsubscribe etc), am I right? Or is it still majordomo@hostname? > The real username doesn't matter in any case since all mail to majordomo@hostname will go to an alias where it will invoke the appropriate command with the alias line: majordomo: "|/usr/local/lib/mail/majordomo/wrapper majordomo" Bill -- INTERNET: bill@Celestial.COM Bill Campbell; Celestial Systems, Inc. UUCP: camco!bill PO Box 820; 2835 82nd Avenue S.E. S-100 FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ Government spending? I don't know what it's all about. I don't know any more about this thing than an economist does, and, God knows, he doesn't know much. -- Will Rogers From majordomo-users-owner Mon Nov 18 19:18:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA08985 for majordomo-users-outgoing; Mon, 18 Nov 1996 19:01:58 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id TAA08973 for majordomo-users@greatcircle.com; Mon, 18 Nov 1996 19:01:54 -0800 (PST) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id QAA16530 for ; Fri, 15 Nov 1996 16:21:00 -0800 (PST) Received: from Eng.Sun.COM ([129.146.1.13]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id QAA15874; Fri, 15 Nov 1996 16:17:16 -0800 Received: from sage.Eng.Sun.COM by Eng.Sun.COM (SMI-8.6/SMI-5.3) id QAA22036; Fri, 15 Nov 1996 16:17:11 -0800 Received: from sage by sage.Eng.Sun.COM (SMI-8.6/SMI-SVR4) id QAA21811; Fri, 15 Nov 1996 16:17:13 -0800 Message-Id: <199611160017.QAA21811@sage.Eng.Sun.COM> X-Mailer: exmh version 2.0alpha 10/9/96 To: Roman Maeder cc: exmh-users@sunlabs.Eng.Sun.COM, majordomo-users@GreatCircle.COM Subject: Re: approve for exmh? In-reply-to: maeder's message of Thu, 14 Nov 1996 15:51:00 +0100. <199611141451.PAA02606@prokyon.mathconsult.ch> X-URL: http://www.smli.com/~bwelch/index.html X-Face: "HxE|?EnC9fVMV8f70H83&{fgLE.|FZ^$>@Q(yb#N,Eh~N]e&]=>r5~UnRml1:4EglY{9B+ :'wJq$@c_C!l8@<$t,{YUr4K,QJGHSvS~U]H`<+L*x?eGzSk>XH\W:AK\j?@?c1o Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multipart MIME message. --==_Exmh_-12185561720 Content-Type: text/plain; charset=us-ascii Attached is "majordomo.tcl" that I've hacked up. It has glitches that I've been too lazy to fix. It assumes you have access to the mailing list files so it can grep for names to find out which list an address is on. I manage several lists. Also attached is my majrodomo menu for exmh. >>>Roman Maeder said: > Does anybody have code for adding an "approve" button or menu to exmh > that lets list owners and moderators generate the appropriate replies, > like the majordomo "approve" program does? (That is, approve administrati= > ve > requests be extracting the template line and substituting the password, > and sending approved contributions with an Approved: line to the list). > > Roman Maeder > > ---------------------------------------------------------------------- > Roman E. M=E4der, Aryanastrasse 21, CH-8704 Herrliberg > Tel: +41-1-991 6341, Fax: +41-1-991 6345, Email: maeder@mathconsult.ch > ---------------------------------------------------------------------- > > -- Brent Welch Sun Labs brent.welch@sun.com --==_Exmh_-12185561720 Content-Type: text/plain; charset=us-ascii Content-Description: .exmh-defaults Content-Disposition: attachment; filename=".exmh-defaults" !!!!!!!!!! Major Domo Menu !!!!!!!!!! *Mops.umenulist: exmh *Mops.exmh.text: EXMH *Mops.exmh.menu: m *Mops.exmh.m.entrylist: doit find bounce sep adduser deluser sep addann delann sep addwork delwork sep adddig deldig sep addtcl deltcl *Mops.exmh.m.t_sep: separator *Mops.exmh.m.l_doit: Summary *Mops.exmh.m.c_doit: BadAddr_Doit *Mops.exmh.m.l_find: Find *Mops.exmh.m.c_find: MD_Find *Mops.exmh.m.l_bounce: Bounce *Mops.exmh.m.c_bounce: MD_Bounce *Mops.exmh.m.l_adduser: Add to exmh-users *Mops.exmh.m.c_adduser: MD_Add exmh-users *Mops.exmh.m.l_deluser: Delete exmh-users *Mops.exmh.m.c_deluser: MD_Delete exmh-users *Mops.exmh.m.l_addann: Add to exmh-announce *Mops.exmh.m.c_addann: MD_Add exmh-announce *Mops.exmh.m.l_delann: Delete exmh-announce *Mops.exmh.m.c_delann: MD_Delete exmh-announce *Mops.exmh.m.l_addwork: Add to exmh-workers *Mops.exmh.m.c_addwork: MD_Add exmh-workers *Mops.exmh.m.l_delwork: Delete exmh-workers *Mops.exmh.m.c_delwork: MD_Delete exmh-workers *Mops.exmh.m.l_adddig: Add to exmh-digest *Mops.exmh.m.c_adddig: MD_Add exmh-users-digest *Mops.exmh.m.l_deldig: Delete exmh-digest *Mops.exmh.m.c_deldig: MD_Delete exmh-users-digest *Mops.exmh.m.l_addtcl: Add to tcl-interest *Mops.exmh.m.c_addtcl: MD_Add tcl-interest *Mops.exmh.m.l_deltcl: Delete tcl-interest *Mops.exmh.m.c_deltcl: MD_Delete tcl-interest --==_Exmh_-12185561720 Content-Type: application/x-tcl Content-Description: majordomo.tcl Content-Disposition: attachment; filename="majordomo.tcl" # Major Domo support for EXMH # There are two sets of features. The first provides # an Approve and Bounce function. # The second provides a way to explicitly add/delete folks from lists. # Those actions are carried out by sending messages to the MD controller. set majordomo(bin) /home/majordom/bin set majordomo(root) /home/majordom/mail/lists set majordomo(log) /home/bwelch/Mail/DL.log set majordomo(lists) {exmh-announce exmh-users exmh-workers exmh-users-digest tcl-interest} set majordomo(lists_exclusive) yes # Run the approve program on the current message proc MD_Approve {} { global exmh msg mhProfile majordomo exec $majordomo(bin)/approve < $mhProfile(path)/$exmh(folder)/$msg(id) Exmh_Status Approved } # Run the bounce program, trying to figure out the # list and the culprit, if possible. proc MD_Bounce {{who {}}} { global exwin majordomo set f [frame $exwin(mtext).mail -bd 4 -relief ridge] message $f.msg -text "MD Bounce" -aspect 1000 pack $f.msg -padx 10 -pady 10 if {[string length $who] == 0} { set who [MDGuessFrom] } set majordomo(who) $who set majordomo(list) [MDGuessList $majordomo(who)] Widget_BeginEntries 10 30 Widget_LabeledEntry $f.who Address majordomo(who) Widget_LabeledEntry $f.list List majordomo(list) Widget_EndEntries focus $f.who global tk_version if {$tk_version >= 4.0} { bindtags $f.who.entry [list $f $f.who.entry Entry] bindtags $f.list.entry [list $f $f.list.entry Entry] bind $f [list MDDestroy $f] bind $f.who.entry [list MDBounceContinue $f] bind $f.list.entry [list MDBounceCommit $f] } else { bind $f.who.entry [list MDBounceContinue $f] bind $f.who.entry [list MDDestroy $f] bind $f.list.entry [list MDBounceCommit $f] bind $f.list.entry [list MDDestroy $f] } bind $f.who.entry [list MDBounceContinue $f] bind $f.list.entry { set majordomo(list) [MDGuessList $majordomo(who)] } bind $f.list.entry [list focus $f.who.entry] frame $f.but -bd 10 pack $f.but -fill x frame $f.but.ok -bd 2 -relief sunken button $f.but.ok.b -text "Guess List" -command [list MDBounceContinue $f] pack $f.but.ok.b -padx 5 -pady 5 button $f.but.cancel -text Cancel -command [list MDDestroy $f] button $f.but.find -text Find -command [list MD_Find] pack $f.but.cancel $f.but.find $f.but.ok -side left -padx 10 focus $f.who.entry Widget_PlaceDialog $exwin(mtext) $f tkwait window $f } proc MDBounceContinue { f } { global majordomo set majordomo(list) [MDGuessList $majordomo(who)] bind $f.who.entry [list MDBounceCommit $f] bind $f.who.entry [list focus $f.list.entry] pack $f.list -after $f.who focus $f.list $f.but.ok.b config -text Bounce! -command [list MDBounceCommit $f] } proc MDBounceCommit { f } { global majordomo Exmh_Status "bounce $majordomo(list) $majordomo(who)" MDAck BOUNCE [string trim $majordomo(list)] $majordomo(who) MDDestroy $f } proc MDGuessFrom {} { if [catch {selection get} result] { return {} } else { return $result } } proc MDGuessList {who} { global majordomo if {[string length $who] == 0} { return [lindex $majordomo(lists) 0] } set result {} foreach l $majordomo(lists) { if ![catch {exec egrep -i $who $majordomo(root)/$l}] { lappend result [file tail $l] } } if {[llength $result] > 0} { return $result } while {[llength $result] <= 1} { set x [split $who @] set who [lindex $x 0]@[join [lrange [split [lindex $x 1] .] 1 end] .] set result $who foreach l $majordomo(lists) { if ![catch {exec egrep -i $who $majordomo(root)/$l}] { lappend result [file tail $l]? } } if {[string match *@ $who]} { break } } return $result } # Add the sender of the current message to a given list. proc MD_Add { what } { MDDialog $what ADD } # Remove the sender of the current message from a given list. proc MD_Delete { what } { MDDialog $what NUKE } proc MDDialog { what how } { global exwin majordomo set f [frame $exwin(mtext).mail -bd 4 -relief ridge] if {$how == "NUKE"} {set prep from} {set prep to} message $f.msg -text "$how $prep $what" -aspect 1000 pack $f.msg set majordomo(what) $what global mimeHdr if [catch {selection get} majordomo(who)] { set majordomo(who) [MsgParseFrom $mimeHdr(0=1,hdr,from)] } entry $f.who -bg white -textvariable majordomo(who) focus $f.who bind $f.who [list MDAccept $f] bind $f.who [list MDDestroy $f] pack $f.who -expand true -fill x -padx 20 frame $f.but -bd 10 pack $f.but set majordomo(how) $how radiobutton $f.but.nuke -text "Delete" -value NUKE -variable majordomo(how) radiobutton $f.but.add -text "Add" -value ADD -variable majordomo(how) frame $f.but.ok -bd 2 -relief sunken button $f.but.ok.b -text OK -command [list MDAccept $f] pack $f.but.ok.b -padx 10 -pady 5 button $f.but.cancel -text Cancel -command [list MDDestroy $f] pack $f.but.cancel $f.but.ok $f.but.add $f.but.nuke -side left -padx 10 Widget_PlaceDialog $exwin(mtext) $f tkwait window $f } # Send the subscripe or unsubscribe message to MajorDomo # Figure out what to do. proc MDAccept { f } { global majordomo set log [open $majordomo(log) a] puts $log "$majordomo(how) $majordomo(what) $majordomo(who)" close $log set what $majordomo(what) set path $majordomo(root)/$majordomo(what) set from $majordomo(who) set miss 1 set where {} foreach i $majordomo(lists) { if {! [catch {exec egrep -i $from $majordomo(root)/$i} value]} { set miss 0 lappend where $i } } Exmh_Status "$majordomo(how) $majordomo(what) $majordomo(who)" if {$majordomo(how) == "NUKE"} { if {[lsearch $where $what] < 0} { Exmh_Status "$from not in $path" } else { MDAck $majordomo(how) $majordomo(what) $majordomo(who) } } else { if {! $miss} { if {[string compare $where $majordomo(what)] != 0} { if {$majordomo(lists_exclusive) == "yes"} { Exmh_Status "Moving $from from $where to $majordomo(what)" MDAck NUKE $where $majordomo(who) } MDAck $majordomo(how) $majordomo(what) $majordomo(who) } else { Exmh_Status "$from in $where" } } else { MDAck $majordomo(how) $majordomo(what) $majordomo(who) } } Exmh_Focus catch {MDDestroy $f} } # Send the subscripe or unsubscribe message to MajorDomo proc MDAck { how what who } { global majordomo Exmh_Debug MDAck $how $what $who if ![info exists majordomo($what,passwd)] { set in [open ~/.majordomo] while {[gets $in line] >= 0} { set list [string tolower [lindex $line 0]] set majordomo($list,passwd) [lindex $line 1] set majordomo($list,server) [lindex $line 2] } close $in } set path /tmp/majordomo.ack.[pid] if [catch {open $path w} out] { Exmh_Status "Cannot open $path" purple return } if [catch { global env puts $out "To: $majordomo($what,server)" puts $out "" switch -- $how { NUKE { puts $out "approve $majordomo($what,passwd) unsubscribe $what $who" } BOUNCE { puts $out "approve $majordomo($what,passwd) unsubscribe $what $who" puts $out "approve $majordomo(bounces,passwd) subscribe bounces $who ([exec date +%y%m%d] $what)" } ADD { puts $out "approve $majordomo($what,passwd) subscribe $what $who" } } close $out } msg] { Exmh_Status "Cannot write $path: $msg" return } if [catch { exec send $path } msg] { Exmh_Status "Send error: $msg" purple return } } proc MDDestroy { f } { destroy $f catch {destroy .mdfind} Exmh_Focus } # Send a request message to MajorDomo proc MD_Request { } { global majordomo set path /tmp/majordomo.ack.[pid] if [catch {open $path w} out] { Exmh_Status "Cannot open $path" purple return } if [catch { global env puts $out "To: majordomo@sunlabs" puts $out "" puts $out "who exmh-announce" puts $out "who exmh-users" puts $out "who exmh-workers" puts $out "who bounces" close $out } msg] { Exmh_Status "Cannot write $path: $msg" } if [catch { exec send $path Exmh_Status "Sent who request" } msg] { Exmh_Status "Send error: $msg" purple return } } proc MD_Find { {what {}} } { global majordomo set list {} set who {} set h 0 if {$what == {}} { if [catch {set what [selection get]}] { set what $majordomo(who) } } if [catch { foreach line [split [eval {exec grep -i $what} [glob $majordomo(root)/exmh-*]] \n] { set parts [split $line :] lappend list [file tail [lindex $parts 0]] lappend who [lindex $parts 1] incr h } }] { Exmh_Status "No hits" return } Exmh_Status $who catch {destroy .mdfind} frame .mdfind -bd 4 -relief ridge if {$h > 10} {set h 5} set llist [listbox .mdfind.list -width 10 -height $h] set lwho [listbox .mdfind.who -width 30 -height $h] eval {$llist insert end} $list eval {$lwho insert end} $who pack $llist $lwho -fill y -expand true -side left if [winfo exists .msg.t.mail] { place .mdfind -in .msg.t.mail -relx .5 -rely 1.0 -anchor n } else { place .mdfind -in .msg.t -relx .5 -rely 1.0 -anchor s } } --==_Exmh_-12185561720 Content-Type: application/x-tcl Content-Description: badaddr.tcl Content-Disposition: attachment; filename="badaddr.tcl" #badaddr.tcl proc BadAddr_Scan {file whyArr} { upvar $whyArr why if [catch {open $file} in] { return } set addrs "" while {[gets $in line] >= 0} { if [regexp {Your message was not delivered to(.*)$} $line x addr] { set addr [string trim $addr] addlist addrs $addr set why($addr) notdelivered } if [regexp {^<([^>]+)>.*unrecoverable error} $line x addr] { set addr [string trim $addr {< >}] addlist addrs $addr set why($addr) unrecoverable } if [regexp {^<([^>]+)>.*Connection timed out} $line x addr] { set addr [string trim $addr {< >}] addlist addrs $addr set why($addr) timeout } if [regexp {^550 (.+)\.\.\. Host unknown} $line x addr] { set addr [string trim $addr {< >}] addlist addrs $addr set why($addr) badhost } if [regexp {^55. (.+)\.\.\. User unknown} $line x addr] { set addr [string trim $addr {< >}] addlist addrs $addr set why($addr) baduser } if [regexp {^55. too many hops.*from <.+>.* to <(.+)>} $line x addr] { set addr [string trim $addr {< >}] addlist addrs $addr set why($addr) toomanyhops } } close $in return $addrs } proc addlist {listVar value} { upvar $listVar list if {[lsearch $list $value] < 0} { lappend list $value } } proc BadAddr_Doit {} { set badaddr {} set count() {} set msg() {} set files {} foreach f [glob -nocomplain {~/Mail/automail/rejects/[0-9]*}] { set addrs [BadAddr_Scan $f why] if [llength $addrs] { lappend files $f foreach a $addrs { lappend msg($a) [file tail $f] if {[lsearch $badaddr $a] < 0} { lappend badaddr $a set count($a) 1 } else { incr count($a) } } } } set t .badaddr.t if {[Exwin_Toplevel .badaddr "Bad Addresses"]} { Widget_Text .badaddr 20 button .badaddr.but.cleanup -text Cleanup button .badaddr.but.doit -text Doit -command BadAddr_Doit pack .badaddr.but.cleanup .badaddr.but.doit -side right } .badaddr.but.cleanup config -command "exec rm $files ; Scan_FolderForce" $t delete 1.0 end set i 0 foreach addr $badaddr { set b [button $t.b[incr i] -text Msg \ -command "Msg_Change [lindex $msg($addr) end]"] $t window create end -window $b set b [button $t.b[incr i] -text Bounce \ -command "MD_Bounce $addr"] $t window create end -window $b $t insert end [format "%-30s %s %-15s %s\n" \ $addr N=$count($addr) $why($addr) [MDGuessList $addr]] } } --==_Exmh_-12185561720-- From majordomo-users-owner Mon Nov 18 19:22:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA09169 for majordomo-users-outgoing; Mon, 18 Nov 1996 19:03:30 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id TAA09122 for majordomo-users@greatcircle.com; Mon, 18 Nov 1996 19:03:20 -0800 (PST) Received: from flint.sentex.net (flint.sentex.net [199.212.134.7]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id FAA05711 for ; Sun, 17 Nov 1996 05:52:37 -0800 (PST) Received: (from uucp@localhost) by flint.sentex.net (8.7.5/8.7.3) with UUCP id IAA26871; Sun, 17 Nov 1996 08:53:01 -0500 (EST) Received: from localhost (nick@localhost) by xwing.xwing.org (8.7.5/8.7.3) with SMTP id HAA24808; Sun, 17 Nov 1996 07:47:18 -0500 Date: Sun, 17 Nov 1996 07:47:16 -0500 (EST) From: Nick Busigin To: "Mercy D. Varakunan" cc: Majordomo-Users@GreatCircle.COM Subject: Re: majordomo or majordom? In-Reply-To: <2.2.32.19961114023538.006972cc@leonis.nus.sg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 14 Nov 1996, Mercy D. Varakunan wrote: > I am trying to set up majordomo. The user name I created for majordomo > is majordom. So, any mail to majordomo should be sent to majordom@hostname > (for subscriobe unsubscribe etc), am I right? Or is it still > majordomo@hostname? "majordomo" is 9 characters long which will cause troubles on some UNIX systems so typically "majordom" is used instead. The userid "majordom" is usually aliased to the system administrator in sendmail's aliases file. For example, here's an excerpt from my aliases file: owner-majordomo: nick majordomo: "|/usr/lib/majordomo/wrapper majordomo" majordom: owner-majordomo As you can see, mail sent to "majordomo" gets piped to the "wrapper" program and mail to "majordom" gets sent to the user who maintains Majordomo (me) on my system. Hope this helps. Nick -------------------------------------------------------------------------- Nick Busigin nick@xwing.org To obtain my pgp public key, email me with the subject: "get pgp-key" -------------------------------------------------------------------------- From majordomo-users-owner Mon Nov 18 19:26:09 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA09312 for majordomo-users-outgoing; Mon, 18 Nov 1996 19:04:05 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id TAA09283 for majordomo-users@greatcircle.com; Mon, 18 Nov 1996 19:03:56 -0800 (PST) Received: from londo.asds.com (londo.prescienttech.com [199.103.216.62]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id KAA12039 for ; Sun, 17 Nov 1996 10:24:24 -0800 (PST) Received: from gkar.asds.com (gkar.asds.com [111.17.19.1]) by londo.asds.com (8.8.2/8.8.2) with ESMTP id NAA00975 for ; Sun, 17 Nov 1996 13:24:31 -0500 Received: (from ratinox@localhost) by gkar.asds.com (8.8.2/8.8.2) id NAA03572; Sun, 17 Nov 1996 13:24:32 -0500 From: Rich Pieri To: Majordomo-Users@GreatCircle.COM Subject: Re: majordomo or majordom? References: <2.2.32.19961114023538.006972cc@leonis.nus.sg> Date: 17 Nov 1996 13:24:15 -0500 Message-ID: In-Reply-To: "Mercy D. Varakunan"'s message of Thu, 14 Nov 1996 10:35:38 +0800 Lines: 34 X-Mailer: Gnus v5.2.40/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- >>>>> "MDV" == Mercy D Varakunan writes: MDV> I am trying to set up majordomo. The user name I created for MDV> majordomo is majordom. So, any mail to majordomo should be sent to MDV> majordom@hostname ( for subscriobe unsubscribe etc), am I right? Or MDV> is it still majordomo@hostname? The "majordom" account is a local UID/GID pair for ownership of Majordomo files. It usually has an entry in the aliases file pointing to majordomo-owner. The "majordomo" alias is just that, an alias, which should have an aliases file entry that looks like this: majordomo: |"/home/majordom/wrapper majordomo" All administrative mail should go to the "majordomo" address. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Charset: noconv iQCVAwUBMo9YUp6VRH7BJMxHAQGIlAQAqho0Yws1j9/3bdXbw+Z++Fn4+MGfjLjz x56Y/D/Thvjomhli97nlJIuwt9DwDsFKPmSc1aR1cnvADUvNYAipt16XVL80J5V2 yaADWmm7S1eRllG/+AXT33608S6+qgsrQdlOLk+LhP3ZyqejYNp6chkgTCyNVDqX jZ6/ODuWqAw= =rb+R -----END PGP SIGNATURE----- -- Rich Pieri \ Never sleep alone when you can sleep on Prescient Technologies, Inc. \ someone's face. -A cat's guide to life rich.pieri@PrescientTech.com \ From majordomo-users-owner Tue Nov 19 00:33:07 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id AAA22574 for majordomo-users-outgoing; Tue, 19 Nov 1996 00:23:26 -0800 (PST) Received: from thoth.mch.sni.de (thoth.mch.sni.de [192.35.17.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id AAA22561 for ; Tue, 19 Nov 1996 00:23:16 -0800 (PST) Received: from ares.mch.sni.de (ares.mch.sni.de [139.22.8.162]) by thoth.mch.sni.de (8.7.6/8.7.3) with SMTP id JAA18209 for ; Tue, 19 Nov 1996 09:23:34 +0100 (MET) Received: from gvkirsche.mch.sni.de ([139.22.8.207]) by ares.mch.sni.de (4.1/SMI-4.1) id AA10054; Tue, 19 Nov 96 09:22:07 +0100 Message-Id: <32916F7A.5E21@mch.sni.de> Date: Tue, 19 Nov 1996 09:27:38 +0100 From: Wilfried Wiehler Reply-To: Wilfried.Wiehler@mch.sni.de Organization: Siemens Nixdorf AG X-Mailer: Mozilla 3.0 (Win95; I) Mime-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Re: Setup problem References: <3290274C.426D@mch.sni.de> <32911DA9.324A@uaa.alaska.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Michael Tibor wrote: > > I didn't think Majordomo liked PERL version 5.002, but don't quote me, > because I don't have a whole lot of experience with PERL. The latest > version I think is 5.003 tho. > > BTW-- you can check your sendmail version by telnetting to your machine > on port 25 (instead of port 23, the normal telnet port). > Mike, thanks for your help. I realized that I have sendmail 4.1. Seems to be rather old... The FAQ says that PERL 5.002 should work; but perhaps my beta version doesn't. Next thing I'll do is trying to install sendmail 8.x, perl 5.003 and then, hopefully, enjoy Majordomo. Bye, Wilfried From majordomo-users-owner Tue Nov 19 08:03:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id HAA13851 for majordomo-users-outgoing; Tue, 19 Nov 1996 07:48:55 -0800 (PST) Received: from siumedtr.siumed.edu (siumedtr.siumed.edu [198.88.63.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id HAA13831 for ; Tue, 19 Nov 1996 07:48:42 -0800 (PST) Received: from education.siutr.siumed.edu (cfagan.edaff.siumed.edu [198.88.79.1]) by siumedtr.siumed.edu (8.7.3/8.7.3) with SMTP id JAA07062 for ; Tue, 19 Nov 1996 09:51:19 -0600 (CST) Date: Tue, 19 Nov 1996 09:51:19 -0600 (CST) Message-Id: <199611191551.JAA07062@siumedtr.siumed.edu> X-Sender: cfagan@siumed.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: cfagan@siumed.edu (Chuck Fagan) Subject: uncompressing or untarring a Majordomo-1.94 file X-Mailer: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have tried several ways that I thought would allow me to use the majordomo-1.94.tar.Z file and nothing works. I tried uncompress, tar, bring down different files with no luck. Any assistance would be appreciated. Chuck cfagan@siumed.edu Director of Educational Computing SIU School of Medicine - 1217 Office of Education and Curriculum PO Box 19230 Springfield, IL 62794-1217 217-785-2094 217-524-0192 - FAX From majordomo-users-owner Tue Nov 19 08:50:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id IAA18327 for majordomo-users-outgoing; Tue, 19 Nov 1996 08:42:23 -0800 (PST) Received: from llama.swcp.com (llama.swcp.com [198.59.115.19]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id IAA18320 for ; Tue, 19 Nov 1996 08:42:10 -0800 (PST) Received: (from lazlo@localhost) by llama.swcp.com (8.6.9/8.6.9) id JAA17751 for majordomo-users@greatcircle.com; Tue, 19 Nov 1996 09:42:10 -0700 Message-Id: <199611191642.JAA17751@llama.swcp.com> Subject: 1.94 question: # in address? To: majordomo-users@greatcircle.com (mu) Date: Tue, 19 Nov 1996 09:42:09 -0700 (MST) From: "Lazlo Nibble" X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Does 1.94 truncate addresses with # signs in them the way 1.93 does? -- ::: Lazlo (lazlo@swcp.com; http://www.swcp.com/lazlo) From majordomo-users-owner Tue Nov 19 10:20:58 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA24539 for majordomo-users-outgoing; Tue, 19 Nov 1996 10:11:20 -0800 (PST) Received: from caxy.lfa.lfc.edu (caxy.lfa.lfc.edu [164.68.100.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA24523 for ; Tue, 19 Nov 1996 10:11:12 -0800 (PST) Received: from caxy.lfa.lfc.edu by caxy.lfa.lfc.edu (SMI-8.6/SMI-SVR4) id MAA25529; Tue, 19 Nov 1996 12:10:28 -0600 Date: Tue, 19 Nov 1996 12:10:28 -0600 (CST) From: Eric Shafto To: Majordomo list Subject: -request in welcome message solved. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Of course, I found it immediately after sending the message to the list. For those of us like myself who are clueless: $majordomo_request is set in majordomo.cf. For the record, I now feel stupid. :-) Eric Shafto Dir. Academic Computing, Lake Forest Academy From majordomo-users-owner Tue Nov 19 12:49:25 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA04871 for majordomo-users-outgoing; Tue, 19 Nov 1996 12:40:39 -0800 (PST) Received: from caroline.cardiffcybercafe.co.uk (caroline.cardiffcybercafe.co.uk [194.168.44.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id MAA04861 for ; Tue, 19 Nov 1996 12:40:31 -0800 (PST) Received: by caroline.cardiffcybercafe.co.uk (ElectricMail-MESSAGE-2.0-GAMMA) id UAA04960; Tue, 19 Nov 1996 20:32:36 GMT Date: Tue, 19 Nov 1996 20:32:35 +0000 (GMT) From: Andy Wild X-Sender: andywild@caroline To: majordomo-users@greatcircle.com Subject: Digest *-outgoing alias Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I'm having problems setting up a digest version of one of my mailing lists. I noticed in earlier discussion on this list that using a *-outgoing alias was not wise and followed the suggestion of using a different alias in my aliases file. However, it would seem majordomo or one of the related programs insists on using a *-outgoing alias for sending out a digest in response to the "mkdigest" command. I have checked through both majordomo.cf and the digest's config file to see if there is a way of forcing it to use another alias but to no avail. What follows is the output I get from Majordomo in response to "mkdigest". -- >>>> mkdigest cybercafe-digest producing Cybercafe Digest V1 #1 processing /ibm/local/majordomo/digest/cybercafe-digest/001 processing /ibm/local/majordomo/digest/cybercafe-digest/002 processing /ibm/local/majordomo/digest/cybercafe-digest/003 processing /ibm/local/majordomo/digest/cybercafe-digest/004 cybercafe-digest-outgoing... User unknown >>>> What am I missing? I have no reference to cybercafe-digest-outgoing at all in my aliases file so why is majordomo looking for it? BTW, I am using Majordomo 1.94 Also, since trying to set up a digest version, one of the test users on the main mailing list is no longer receiving posts. I have tried unsubscribing and re-subscribing the user several times but it still fails to receive any posts made either by it or other users. I thought it may have been a result of being on both the digest and normal versions so removed it from the digest version but still to no avail. The e-mail address also happens to be the address to which e-mails for owner-* of Majordomo and the list is directed to but I don't see how this would stop it getting normal posts to the mailing list. Any ideas anyone? Cheers, Andy Wild. Technical Officer. The Cardiff CyberCafe Ltd./LightSpeed On-Line. ----------------------------------------------------------------------- The Cardiff CyberCafe Ltd. LightSpeed On-Line 9, Duke Street 9, Duke Street Cardiff, CF1 2AY Cardiff, CF1 2AY UNITED KINGDOM UNITED KINGDOM Tel: +44-1222-235757 Tel: +44-1222-235760 Fax: +44-1222-235758 Tel: +44-1222-235758 www.cardiffcybercafe.co.uk www.lightspeed.co.uk ----------------------------------------------------------------------- From majordomo-users-owner Tue Nov 19 14:04:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA09470 for majordomo-users-outgoing; Tue, 19 Nov 1996 13:55:52 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id NAA09459 for majordomo-users@greatcircle.com; Tue, 19 Nov 1996 13:55:48 -0800 (PST) Received: from caxy.lfa.lfc.edu (caxy.lfa.lfc.edu [164.68.100.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id KAA23462 for ; Tue, 19 Nov 1996 10:00:43 -0800 (PST) Received: from caxy.lfa.lfc.edu by caxy.lfa.lfc.edu (SMI-8.6/SMI-SVR4) id MAA25355; Tue, 19 Nov 1996 12:00:09 -0600 Date: Tue, 19 Nov 1996 12:00:09 -0600 (CST) From: Eric Shafto To: Majordomo list Subject: reference to -request in welcome message Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I would like the welcome message to tell people to use the -request address to unsubscribe, but it gives Majordomo@dom.ain instead. It appears that $majordomo_request isn't getting set correctly. Does anyone know what I might be doing wrong? The -request address is working correctly, and I don't see anything about it in the .config file, NEWLIST, README, or the FAQ. Eric Shafto Dir. Academic Computing, Lake Forest Academy From majordomo-users-owner Tue Nov 19 14:20:41 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id NAA09068 for majordomo-users-outgoing; Tue, 19 Nov 1996 13:52:48 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id NAA09027 for majordomo-users@greatcircle.com; Tue, 19 Nov 1996 13:52:35 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id TAA10038 for ; Mon, 18 Nov 1996 19:18:32 -0800 (PST) Received: from jasper ([13.240.161.42]) by alpha.xerox.com with SMTP id <19376(5)>; Mon, 18 Nov 1996 19:18:52 PST Received: by jasper (SMI-8.6/SMI-SVR4-SD1.5) id TAA12094; Mon, 18 Nov 1996 19:18:31 -0800 Date: Mon, 18 Nov 1996 19:18:31 PST Message-Id: <199611190318.TAA12094@jasper> To: majordomo-users@greatcircle.com Subject: digest subscription fails Cc: bhami@hesp.es.xerox.com From: Bruce Hamilton Reply-To: bhami@hesp.es.xerox.com X-Sun-Charset: US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I imagine this is just a simple configuration problem... I tried setting up a test list called "testlist" according to the "complex" example in the Readme, with testlist-digest aliased to testlist. But if I try to "subscribe testlist-digest", I get "subscribe: unknown list 'testlist-digest'." Thanks for any ideas. I've created the lists/testlist.archive/ and digestwork/testlist/ directories with proper ownership, as indicated in the Readme. --Bruce 310-333-3538 fax: 310-333-6898 Xerox: 8*823-3538 m/s ESC1-615 From majordomo-users-owner Tue Nov 19 14:28:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA11186 for majordomo-users-outgoing; Tue, 19 Nov 1996 14:14:54 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id OAA11170 for majordomo-users@greatcircle.com; Tue, 19 Nov 1996 14:14:48 -0800 (PST) Received: from ns1.acadiacom.net (ns1.acadiacom.net [206.104.52.150]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id NAA16352 for ; Mon, 18 Nov 1996 13:52:36 -0800 (PST) Received: (from tom@localhost) by ns1.acadiacom.net (8.7.5/8.7.3) id PAA08435 for majordomo-users@greatcircle.com; Mon, 18 Nov 1996 15:50:03 -0600 Date: Mon, 18 Nov 1996 15:50:03 -0600 From: Tom Gallagher Message-Id: <199611182150.PAA08435@ns1.acadiacom.net> To: majordomo-users@greatcircle.com Subject: Help w/ install on Linux 2.0.0 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am attempting to install Majordomo-1.94 on my linux box running Linux 2.0.0 I am have a hard time with the install. I get the following error message. Can't locate majordomo_version.pl in @INC at ./majordomo line 63. I have already tried to check if i had the paths set wrong but everything seems okay. Also I have to copy majordomo.cf to /etc. (I though the install would do that? Is this okay?). Please let me know what I can do to resolve this problem. Thank you. Tom Gallagher tom@ns1.acadiacom.net From majordomo-users-owner Tue Nov 19 14:32:25 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA11065 for majordomo-users-outgoing; Tue, 19 Nov 1996 14:14:00 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id OAA11046 for majordomo-users@greatcircle.com; Tue, 19 Nov 1996 14:13:53 -0800 (PST) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA01756 for ; Mon, 18 Nov 1996 09:42:27 -0800 (PST) Received: from gymir.ifi.uio.no (1368@gymir.ifi.uio.no [129.240.80.2]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id ; Mon, 18 Nov 1996 18:42:45 +0100 Received: (from thomasg@localhost) by gymir.ifi.uio.no ; Mon, 18 Nov 1996 18:42:42 +0100 Date: Mon, 18 Nov 1996 18:42:39 +0100 From: Thomas Gramstad Reply-To: thomasg@ifi.uio.no To: Dave Wolfe Cc: majordomo-users@GreatCircle.COM Subject: Re: Can't get Majordomo to unsubscribe In-Reply-To: Dave Wolfe 's message of Thu, 14 Nov 1996 09:02:20 -0600 (CST) References: <199611141502.JAA21306@miaow.risc.sps.mot.com> Message-ID: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Someone (owner-majordomo?) should be getting some Mj ABORT messages. On a related note, owner-majordomo also receives error messages generated in the case that someone sends a subscribe request, but Mj (or sendmail?) can't find the address that the request is supposed to come from. It would seem more logical that such error messages were sent to owner-listname rather than owner-majordomo. Is it possible for me to change that? Thomas Gramstad From majordomo-users-owner Tue Nov 19 14:33:38 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA11610 for majordomo-users-outgoing; Tue, 19 Nov 1996 14:20:22 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id OAA11601 for ; Tue, 19 Nov 1996 14:20:10 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id QAA14241; Tue, 19 Nov 1996 16:20:16 -0600 (CST) To: Andy Wild Cc: majordomo-users@GreatCircle.COM Subject: Re: Digest *-outgoing alias References: From: Jason L Tibbitts III Date: 19 Nov 1996 16:20:16 -0600 In-Reply-To: Andy Wild's message of Tue, 19 Nov 1996 20:32:35 +0000 (GMT) Message-ID: Lines: 17 X-Mailer: Red Gnus v0.61/Emacs 19.34 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >>>>> "AW" == Andy Wild writes: AW> What am I missing? I have no reference to cybercafe-digest-outgoing at AW> all in my aliases file so why is majordomo looking for it? BTW, I am AW> using Majordomo 1.94 Because if you don't give mkdigest the name of the outgoing alias, it uses the default. AW> Also, since trying to set up a digest version, one of the test users on AW> the main mailing list is no longer receiving posts. No idea, but seeing as though you haven't the aliases properly for the digest, perhaps something else is messed up. We'd have to see your aliases to be sure. - J< From majordomo-users-owner Tue Nov 19 14:36:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id OAA11042 for majordomo-users-outgoing; Tue, 19 Nov 1996 14:13:51 -0800 (PST) Received: (mcb@localhost) by miles.greatcircle.com (8.7.4/Miles-960830-1) id OAA11023 for majordomo-users@greatcircle.com; Tue, 19 Nov 1996 14:13:46 -0800 (PST) Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id JAA00800 for ; Mon, 18 Nov 1996 09:24:41 -0800 (PST) Received: from mogate.sps.mot.com by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA07399 for Majordomo-Users@greatcircle.com; Mon, 18 Nov 96 10:25:02 MST Received: from risc.risc.sps.mot.com (risc.sps.mot.com) by mogate.sps.mot.com (4.1/SMI-4.1/Email-2.0) id AA16704 for Majordomo-Users@greatcircle.com; Mon, 18 Nov 96 10:25:00 MST Received: from miaow.risc.sps.mot.com (miaow.risc.sps.mot.com [223.72.249.15]) by risc.risc.sps.mot.com (8.7.1/8.7.1) with ESMTP id LAA06898; Mon, 18 Nov 1996 11:24:59 -0600 (CST) Received: (from dwolfe@localhost) by miaow.risc.sps.mot.com (8.7.1/8.7.3) id LAA15304; Mon, 18 Nov 1996 11:24:57 -0600 From: Dave Wolfe Message-Id: <199611181724.LAA15304@miaow.risc.sps.mot.com> Subject: Re: majordomo or majordom? To: cwcmdv@leonis.nus.sg (Mercy D. Varakunan) Date: Mon, 18 Nov 1996 11:24:57 -0600 (CST) Cc: Majordomo-Users@greatcircle.com In-Reply-To: <2.2.32.19961114023538.006972cc@leonis.nus.sg> from "Mercy D. Varakunan" at Nov 14, 96 10:35:38 am Reply-To: Dave Wolfe X-Mailer: ELM [version 2.4 PL25 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [ Mercy D. Varakunan writes: ] > > I am trying to set up majordomo. The user name I created for > majordomo is majordom. So, any mail to majordomo should be sent to > majordom@hostname ( for subscriobe unsubscribe etc), am I right? Or is > it still majordomo@hostname? The majordomo *alias* is where administrative requests for your lists should go. The majordom *user* is primarily a placeholder uid for Mj to run under. You might want to alias majordom to majordomo if anyone is confused as to the difference, but I prefer aliasing it to owner-majordomo so I can correct the misguided before it becomes a habit. -- Dave Wolfe From majordomo-users-owner Tue Nov 19 18:52:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id SAA09193 for majordomo-users-outgoing; Tue, 19 Nov 1996 18:39:40 -0800 (PST) Received: from hermes.etheron.net (HERMES.ETHERON.NET [200.30.8.2]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id SAA09176 for ; Tue, 19 Nov 1996 18:39:28 -0800 (PST) Received: from hermes.etheron.net by hermes.etheron.net (NTMail 3.02.10) with ESMTP id na080639 for ; Tue, 19 Nov 1996 22:41:15 -0400 Message-ID: <328C0701.2AD7@etheron.net> Date: Fri, 15 Nov 1996 02:00:33 -0400 From: "Juan J. Vieira" Organization: UCV X-Mailer: Mozilla 3.0 (Win95; I) MIME-Version: 1.0 To: majordomo-users@Greatcircle.com Subject: Out of Memory Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello I have installed Majordomo 1.94, Linux 1.2.13 and Perl 5.001, majordomo give me an error message "Out of Memory" I think that the problem is the Perl Version, I have installed Perl 5.003 with the basic steps sh configure -des make make test make install majordomo mail the message to the mailing list fine, but when I mail a message to majordomo (help,subscribe), the process create by perl to consume all the memory of the system. I kill the process and shutdown the system, when the system reboot, sendmail execute the mqueue and the answer of majordomo arrive. Pleas help me !!!! Thank You > > Juan J. Vieira M. > Jvieira@etheron.net >. From majordomo-users-owner Tue Nov 19 19:48:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id TAA15640 for majordomo-users-outgoing; Tue, 19 Nov 1996 19:35:05 -0800 (PST) Received: from aamc.org (wpo.aamc.org [143.220.26.49]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id TAA15629 for ; Tue, 19 Nov 1996 19:34:57 -0800 (PST) Received: from AAMC-Message_Server by aamc.org with Novell_GroupWise; Tue, 19 Nov 1996 22:32:20 -0500 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Tue, 19 Nov 1996 22:36:01 -0500 From: Robert Yearwood To: majordomo-users@GreatCircle.com Subject: Mial loops and missing "Subject' Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have been successfully running Majordomo-1.93 for about a year, but I have two problems that I have been unable to resolve. The first problem involves mail loops created when the "reply_to" configuration option is set to the list_name, and a list member has an automatic receipt or some other type of automatic reply set in their local mail system. The two options I know of are 1) change the "reply_to" config parm to "$SENDER", or 2) make the list a moderated list. Are there any other options? The second problem is the loss of the "Subject:" when a message is approved on a moderated list; I'm on a moderated list and I post a message, the message gets BOUNCED to the list owner, but when the owner approves the message, the Subject gets dropped. Has anyone else experienced this problem? Any assistance with either or both of these problems would be greatly appreciated. TIA. From majordomo-users-owner Tue Nov 19 20:33:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA20417 for majordomo-users-outgoing; Tue, 19 Nov 1996 20:21:09 -0800 (PST) Received: from homegate (homegate.mmoran.com [206.138.122.85]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with SMTP id UAA20381 for ; Tue, 19 Nov 1996 20:20:57 -0800 (PST) Received: from mine.mmoran.com (mine [10.0.2.5]) by homegate (8.6.12/8.6.9) with SMTP id XAA14628 for ; Tue, 19 Nov 1996 23:21:35 -0500 Message-Id: <3.0.32.19961119232106.0070fa2c@homegate> X-Sender: mmoran@homegate X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 19 Nov 1996 23:21:09 -0500 To: majordomo-users@GreatCircle.COM From: Mark Moran Subject: Dupe msg's Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Well I finally got it all running and digests too! I do have one problem. I have a part-time connection to the internet w/ a fixed IP and a registered domain. Not sure if this is a msg which can be answered here but here goes anyway: I'm running 1.94 on Linux 1.2.13 w/ sendmail 8.something. All works fine while I'm on-line, but if I send a msg to a list from the Linux server or any node on the local network the msg is duped everything the sendmail demon runs until I'm back on-line then they all go out. I.e., shut down the connection to the ISP. Send a msg to one of the lists. Wait an hour. The sendmail demon is running the queue every 10 minutes. I'll then have 6 of the msg's I just sent, to every user on the list. How can I stop this, short of tripling my expenses by going to a 24 hour connection? Mark Moran mmoran@mmoran.com (Please note new email address!!!) http://ourworld.compuserve.com/homepages/markmoran From majordomo-users-owner Tue Nov 19 21:05:14 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id UAA23149 for majordomo-users-outgoing; Tue, 19 Nov 1996 20:54:17 -0800 (PST) Received: from roentgen.gdl.iteso.mx ([148.201.193.9]) by miles.greatcircle.com (8.7.4/Miles-960830-1) with ESMTP id UAA23141 for ; Tue, 19 Nov 1996 20:54:12 -0800 (PST) Received: (from root@localhost) by roentgen.gdl.iteso.mx (8.7.4/8.6.9) id XAA03624 for majordomo-users@greatcircle.com; Tue, 19 Nov 1996 23:04:13 -0600 (CST) Date: Tue, 19 Nov 1996 23:04:13 -0600 (CST) From: Ing E Palomar Lever Message-Id: <199611200504.XAA03624@roentgen.gdl.iteso.mx> To: majordomo-users@greatcirc