From majordomo-users-owner Tue Feb 1 06:55:55 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA11130; Tue, 1 Feb 2000 06:40:23 -0800 (PST) Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA11121 for ; Tue, 1 Feb 2000 06:40:17 -0800 (PST) Received: from 209-122-214-130.s384.tnt3.lnh.md.dialup.rcn.com ([209.122.214.130] helo=noydb) by smtp03.mrf.mail.rcn.net with smtp (Exim 2.12 #3) id 12FehL-0003HF-00 for majordomo-users@greatcircle.com; Tue, 1 Feb 2000 09:54:31 -0500 Message-Id: <4.1.20000201094137.00977230@kajor.com> X-Sender: jack@kajor.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 01 Feb 2000 09:49:00 -0500 To: majordomo-users@greatcircle.com From: Jack Schnapper Subject: Putting Listmember's Email Address in Footer? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi - I noticed the following footer in a message I received from another list: >The e-mail address for your subscription is >jack@KAJOR.COM >To insure prompt service, please include the address, >exactly as it appears above, in any correspondence to us. Is there any way (possibly using some token?) that I can get and include each individual's email address (and use it in a similar footer message as above) as they are subscribed to my lists so they can use it when they are having problems or wish to unsubscribe? One of the most annoying problems I experience is when someone tries to unsubscribe from one of my lists but haven't a clue under what address they are actually subscribed. Thanks, Jack Schnapper From majordomo-users-owner Tue Feb 1 09:11:35 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA12261; Tue, 1 Feb 2000 08:54:52 -0800 (PST) Received: from mercury.libpubinc.com (mercury.libpubinc.com [208.249.203.55]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA12254 for ; Tue, 1 Feb 2000 08:54:45 -0800 (PST) Received: from dmoyer (dhcp93.libpubinc.com [208.249.203.93]) by mercury.libpubinc.com (8.9.3/8.9.3) with ESMTP id JAA05080; Tue, 1 Feb 2000 09:08:49 -0800 Message-Id: <4.2.2.20000201090520.00a87720@mercury.libpubinc.com> X-Sender: dmoyer@mercury.libpubinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 01 Feb 2000 09:08:45 -0800 To: Sandeep Singh Cheema From: Dave Moyer Subject: Re: problems!!! Cc: majordomo-users@GreatCircle.COM In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk You have configured SendMail to use the SendMail Restricted Shell (smrsh). Sendmail will not allow MajorDomo to run because it is not on the list of approved programs. To approve the program, you will need to find where smrsh is configured to look for allowable programs (probably /etc/smrsh) and create a symbolic link to the wrapper program. The smrsh issue is covered more completely in the FAQ. Dave At 11:37 AM 2/1/00 +0530, you wrote: >hi >i installed majordomo 1.94.4, the wrapper config-test gives clean results, >but when i send a mail to majordomo as another user, the root gets this >msg from mailer daemon: > > ----- The following addresses had permanent fatal errors ----- >"|/usr/test/majordomo-1.94.4/wrapper majordomo" > (expanded from: majordomo) > > ----- Transcript of session follows ----- >sh: wrapper not available for sendmail programs >554 "|/usr/test/majordomo-1.94.4/wrapper majordomo"... Service unavailable > > > >pl tell me where things gone wrong > >thanx in advance, > > > > >------------------------------------------------------ >Sandeep Singh Cheema >ACT-PSO >HCL Infosystems >3rd Floor Subharam Complex >144 MG Road Bangalore- 560001 > >****************************************************** >I am a conscientious man, when I throw rocks at seabirds I leave no tern >unstoned. > -- Ogden Nash, "Everybody's Mind to Me a Kingdom Is" From majordomo-users-owner Tue Feb 1 13:13:13 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA14665; Tue, 1 Feb 2000 12:53:30 -0800 (PST) Received: from mail1.den.wantweb.net (mail1.den.wantweb.net [24.236.11.6]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA14658 for ; Tue, 1 Feb 2000 12:53:23 -0800 (PST) Message-Id: <200002012053.MAA14658@honor.greatcircle.com> Received: from rgallegos ([24.236.12.50]) by mail1.den.wantweb.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 605-42905U2500L250S0) with SMTP id AAA226 for ; Tue, 1 Feb 2000 14:06:01 -0700 From: "Raul A. Gallegos" To: "majordomo-users@greatcircle.com" Date: Tue, 01 Feb 2000 14:07:22 -0700 Reply-To: "Raul A. Gallegos" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="_=_=_=IMA.BOUNDARY.HTML_4963392=_=_=_" Subject: question aboutlog Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk --_=_=_=IMA.BOUNDARY.HTML_4963392=_=_=_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I keep getting this every time a message is sent to the list and don't know what it means or if I have to do anything about it. Feb 1 13:07:53 asmodean sendmail[15698]: NAA15698: clone NAA15697, owner=raul@asmodean.net Feb 1 13:07:55 asmodean sendmail[15700]: NAA15700: Authentication-Warning: asmodean.net: majordomo set sender to owner-blindadult@asmodean.net using -f Email: raul@asmodean.net -- icq# 5283055 Join Blindadult mailing list email majordomo@asmodean.net Mystical Gates: telnet://mg.asmodean.net:2369 Info about MG builders email mg@asmodean.net --_=_=_=IMA.BOUNDARY.HTML_4963392=_=_=_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit I keep getting this every time a message is sent to the list and don't know what it means or if I have to do anything about it.

Feb 1 13:07:53 asmodean sendmail[15698]: NAA15698: clone NAA15697, owner=raul@asmodean.net
Feb 1 13:07:55 asmodean sendmail[15700]: NAA15700: Authentication-Warning: asmodean.net: majordomo set sender to owner-blindadult@asmodean.net using -f



Email: raul@asmodean.net -- icq# 5283055
Join Blindadult mailing list email majordomo@asmodean.net
Mystical Gates: telnet://mg.asmodean.net:2369
Info about MG builders email mg@asmodean.net
--_=_=_=IMA.BOUNDARY.HTML_4963392=_=_=_-- From majordomo-users-owner Tue Feb 1 16:57:01 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA16520; Tue, 1 Feb 2000 16:43:27 -0800 (PST) Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA16513 for ; Tue, 1 Feb 2000 16:43:20 -0800 (PST) Received: from 209-122-214-130.s384.tnt3.lnh.md.dialup.rcn.com ([209.122.214.130] helo=noydb) by smtp03.mrf.mail.rcn.net with smtp (Exim 2.12 #3) id 12Fo6V-0005VC-00; Tue, 1 Feb 2000 19:57:08 -0500 Message-Id: <4.1.20000201195230.0096adb0@kajor.com> X-Sender: jack@kajor.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 01 Feb 2000 19:54:42 -0500 To: "Chris McEwen" From: Jack Schnapper Subject: Re: Putting Listmember's Email Address in Footer? Cc: majordomo-users@greatcircle.com In-Reply-To: <00a301bf6d16$d1d70120$0100a8c0@earthlink> References: <4.1.20000201094137.00977230@kajor.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Sorry but $SENDER puts the email address of the person writing the message not the email address of the individual list member for his personal use when requesting to be removed from the list (I already tried it). Thanks anyway, Jack At 04:45 PM 2/1/00 -0800, Chris McEwen wrote: >The token is $SENDER. > >-- Chris McEwen > Socrates Press, Keyport WA > chris@nwstamps.com > > >----- Original Message ----- >From: Jack Schnapper > >Is there any way (possibly using some token?) that I can get and include >each individual's email address (and use it in a similar footer message as >above) as they are subscribed to my lists so they can use it when they are >having problems or wish to unsubscribe? > From majordomo-users-owner Tue Feb 1 18:25:38 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA17318; Tue, 1 Feb 2000 18:15:05 -0800 (PST) Received: from raven.a001.sprintmail.com (raven.prod.itd.earthlink.net [209.178.63.9]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA17303 for ; Tue, 1 Feb 2000 18:14:57 -0800 (PST) Received: from earthlink (sdn-ar-005waseatP168.dialsprint.net [168.191.237.104]) by raven.a001.sprintmail.com (8.8.7/8.8.5) with SMTP id SAA27614; Tue, 1 Feb 2000 18:29:16 -0800 (PST) Message-ID: <004c01bf6d25$03d6f5a0$0100a8c0@earthlink> Reply-To: "Chris McEwen" From: "Chris McEwen" To: "Jack Schnapper" Cc: References: <4.1.20000201094137.00977230@kajor.com> <4.1.20000201195230.0096adb0@kajor.com> Subject: Re: Putting Listmember's Email Address in Footer? Date: Tue, 1 Feb 2000 18:27:11 -0800 Organization: Socrates Press, Keyport WA MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Sorry, I see now what you want. You would like the address that is used to each individual member to be displayed in the mail addressed to him. In this, a message posted to a list would have my address in the footer when I read it, and your address when you read it. Intriguing. I can't imagine the overhead this would involve. Let us know if you find a solution. -- Chris McEwen Socrates Press, Keyport WA chris@nwstamps.com ----- Original Message ----- From: Jack Schnapper Sorry but $SENDER puts the email address of the person writing the message not the email address of the individual list member for his personal use when requesting to be removed from the list (I already tried it). From majordomo-users-owner Wed Feb 2 06:54:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA26886; Wed, 2 Feb 2000 06:48:01 -0800 (PST) Received: from smtp.umr.edu (mrelay.cc.umr.edu [131.151.1.89]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA26879 for ; Wed, 2 Feb 2000 06:47:56 -0800 (PST) Received: from umr-mail01.cc.umr.edu (umr-mail01.cc.umr.edu [131.151.37.121]) via ESMTP by mrelay.cc.umr.edu (8.9.3/R.4.20) id JAA04509; Wed, 2 Feb 2000 09:01:39 -0600 Received: by umr-mail01 with Internet Mail Service (5.5.2650.21) id ; Wed, 2 Feb 2000 08:49:01 -0600 Message-ID: <9DA8D24B915BD1118911006094516EAF029EF03C@umr-mail02> From: "Neulinger, Nathan R." To: "'Chris McEwen'" , Jack Schnapper Cc: majordomo-users@GreatCircle.COM Subject: RE: Putting Listmember's Email Address in Footer? Date: Wed, 2 Feb 2000 08:49:01 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="ISO-8859-1" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The primary overhead would be that messages could no longer be batched by the mail server, instead of 1 message to 10000 recipients, you would have 10000 messages. -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: nneul@umr.edu University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 > -----Original Message----- > From: Chris McEwen [mailto:socrates@sprintmail.com] > Sent: Tuesday, February 01, 2000 8:27 PM > To: Jack Schnapper > Cc: majordomo-users@GreatCircle.COM > Subject: Re: Putting Listmember's Email Address in Footer? > > > Sorry, I see now what you want. You would like the address > that is used to > each individual member to be displayed in the mail addressed > to him. In > this, a message posted to a list would have my address in the > footer when I > read it, and your address when you read it. > > Intriguing. I can't imagine the overhead this would involve. > Let us know if > you find a solution. > > -- Chris McEwen > Socrates Press, Keyport WA > chris@nwstamps.com > > > ----- Original Message ----- > From: Jack Schnapper > > > Sorry but $SENDER puts the email address of the person > writing the message > not the email address of the individual list member for his > personal use > when requesting to be removed from the list (I already tried it). > > From majordomo-users-owner Wed Feb 2 07:24:18 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA27226; Wed, 2 Feb 2000 07:08:09 -0800 (PST) Received: from mail.netdirect.net (mail.netdirect.net [209.212.192.7]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA27201 for ; Wed, 2 Feb 2000 07:07:57 -0800 (PST) Received: from jason (p29-term11-in.netdirect.net [209.212.195.157]) by mail.netdirect.net (8.9.0/8.9.0) with SMTP id KAA24012 for ; Wed, 2 Feb 2000 10:22:24 -0500 (EST) Message-ID: <009801bf6d9a$3c310560$0200a8c0@jason> From: "Jason Lile" To: Subject: installation Date: Wed, 2 Feb 2000 10:26:18 -0600 Organization: Zionsville Autosport MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello I'm trying to install version 1.94.4 on my own web space as my ISP has an older version that cannot lock out the "who" request from any list members. Anyway, I'm fairly comfortable with installing perl applications. I'm okay up to the point where I need to be able to modify the user and group settings. I'm simply using my own web space, not an actual server. I've asked my ISP about getting majordomo user and group permissions, but they have ignored me ;) Any tips on how this can be done? Any help is greatly appreciated. Thanks in advance. ----------------------------------- Jason Lile Zionsville Autosport "BMW Parts Specialists" 1-800-BIMMERS http://www.zionsvilleautosport.com Administrator - BMW Parts Digest ----------------------------------- From majordomo-users-owner Wed Feb 2 12:57:31 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA00538; Wed, 2 Feb 2000 12:39:23 -0800 (PST) Received: from mhub2.tc.umn.edu (mhub2.tc.umn.edu [128.101.131.42]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA00531 for ; Wed, 2 Feb 2000 12:39:16 -0800 (PST) Received: from garnet.tc.umn.edu by mhub2.tc.umn.edu with ESMTP for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 14:53:34 -0600 Received: from localhost by garnet.tc.umn.edu with ESMTP for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 14:53:33 -0600 Date: Wed, 2 Feb 2000 14:53:33 -0600 (CST) From: mjn To: majordomo-users@greatcircle.com Subject: Question about archiving... Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I modified my lists slightly so that the files reside inside of a folder named after the list inside of /runtime/majordomo/lists. It works fine except that when a message is sent to the list majordomo is creating a new .config file in lists/ and ignoring the one in lists/listname/. Is there a way that one would be able to change this? I noticed that there is the $listdir variable in majordomo.cf but I doubt that putting in $listname is going to work. Now that I am thinking about it, majordomo will likely also put any newinfo of newintro files in the list directory too... We are going to have ~150 lists when all is said and done and it is going to be messy to have all of them in the same directory. 150 directories would be much cleaner than ~600 config files. Any suggestions? ____________________________ Mike Neuharth ADCS Technology Specialist http://www.umn.edu/adcs E-Mail : mjn@tc.umn.edu Page Mail : 6123065932@messaging.sprintpcs.com http://nifty.dsl.visi.com/ ____________________________ From majordomo-users-owner Wed Feb 2 13:42:02 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA01025; Wed, 2 Feb 2000 13:22:56 -0800 (PST) Received: from psiwest.com (enterprise.psiwest.com [208.235.128.169]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA01018 for ; Wed, 2 Feb 2000 13:22:49 -0800 (PST) Received: from bboulding.vicorp.com (machine.qwest.net [204.154.239.5]) by psiwest.com (8.8.6/8.8.6) with SMTP id NAA20525 for ; Wed, 2 Feb 2000 13:36:51 -0800 (PST) Reply-To: From: "Bruce Boulding" To: Subject: MJ2 and Ack Messages... Date: Wed, 2 Feb 2000 14:38:28 -0700 Message-ID: <003d01bf6dc5$d7d971c0$bd00000a@bboulding.vicorp.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_003E_01BF6D8B.2B7A99C0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 X-MS-TNEF-Correlator: 000000006B0F7C0587F6D211922D503C07C1000044003400 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_003E_01BF6D8B.2B7A99C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I have a moderated list. I am posting a message from a user that gets accepted. At acceptance time, there is a message returned to the user that says the message was posted. How do I turn that off? When I look at the user profile and the default_flags, the NOACK is on. ******************************** Bruce Boulding Vicorp.com mailto: Bruce.Boulding@Vicorp.com 905 673-5666 x202 ------=_NextPart_000_003E_01BF6D8B.2B7A99C0 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IhwVAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANAHAgACAA4AJQAAAAMAEQEB A5AGACAGAAAnAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB AAAAGAAAAE1KMiBhbmQgQWNrIE1lc3NhZ2VzLi4uAAIBcQABAAAAFgAAAAG/bcXFUceew1nZXhHT kjgAgMflEpUAAAIBHQwBAAAAHwAAAFNNVFA6QlJVQ0UuQk9VTERJTkdAVklDT1JQLkNPTQAACwAB DgAAAABAAAYOAOb6osVtvwECAQoOAQAAABgAAAAAAAAAaw98BYf20hGSLVA8B8EAAGKNAAALAB8O AQAAAAMABhCSXJUBAwAHEDcBAAAeAAgQAQAAAGUAAABJSEFWRUFNT0RFUkFURURMSVNUSUFNUE9T VElOR0FNRVNTQUdFRlJPTUFVU0VSVEhBVEdFVFNBQ0NFUFRFREFUQUNDRVBUQU5DRVRJTUUsVEhF UkVJU0FNRVNTQUdFUkVUVVJOAAAAAAIBCRABAAAArQEAAKkBAACUAgAATFpGdSzoALMDAAoAcmNw ZzEyNQYyAPgLYG5nNDEwOjUB9yACpANjAgBjaMEKwHNldDAgB20Cg/8AUANVEY8B8Q5QA9UHEwKA Mn0KgXVjAFALA3Vsim4CIGULpiBJIBEAIHZlIGEgBGNhdIkJgCBsBAB0LiAXQWBhbSBwbxigC4Bn 4xeyB5BzYWcXoANSF7F2dREwBcB0EQAFQBowdHMEIADQY2UFMAmAGMFBvwVAG8QAcBvgGxAHcSwb Ed8EkBegBAAZuQlwdAhwFqC5GGB0bx2iGskaEHkEIHMfohnmd2EEIBlCHCNIem8H4GQfgBdQHwIb FG/1ASA/GNBXHcADoBdQCQBcb2sXsAVAH6dwA2BmuwMQF6FuH1EfsQEBYRZgZHRfDvFncx2TB7BP 2EFDSx4CAiAuCqIKhEcorwshErJzMTgoxCpnKx8sDCjEQnIV0BegQtkIYGxkGYEoxFYN4AWw9HAu BaBtKMUBkRfQC3BZJsBvOi3ALYIuLdZACy6/L8I5D2AgNjczyC01NjNQIHgB0A5QvyjUFIMMASma NKUVkQA2MAAAAAMAEBAAAAAAAwAREAAAAAALAASACCAGAAAAAADAAAAAAAAARgAAAAADhQAAAAAA AAMABYAIIAYAAAAAAMAAAAAAAABGAAAAABCFAAAAAAAAAwAHgAggBgAAAAAAwAAAAAAAAEYAAAAA UoUAANYZAAAeAAiACCAGAAAAAADAAAAAAAAARgAAAABUhQAAAQAAAAQAAAA4LjUAAwAJgAggBgAA AAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALAAqACCAGAAAAAADAAAAAAAAARgAAAAAOhQAAAAAAAAMA C4AIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAMgAggBgAAAAAAwAAAAAAAAEYAAAAAGIUA AAAAAAAeAA2ACCAGAAAAAADAAAAAAAAARgAAAAA2hQAAAQAAAAEAAAAAAAAAHgAOgAggBgAAAAAA wAAAAAAAAEYAAAAAN4UAAAEAAAABAAAAAAAAAB4AD4AIIAYAAAAAAMAAAAAAAABGAAAAADiFAAAB AAAAAQAAAAAAAAALABCACyAGAAAAAADAAAAAAAAARgAAAAAAiAAAAAAAAAsAEYALIAYAAAAAAMAA AAAAAABGAAAAAAWIAAAAAAAACwASgAggBgAAAAAAwAAAAAAAAEYAAAAABoUAAAAAAAALABOACCAG AAAAAADAAAAAAAAARgAAAACChQAAAQAAAAIB+A8BAAAAEAAAAGsPfAWH9tIRki1QPAfBAAACAfoP AQAAABAAAABrD3wFh/bSEZItUDwHwQAAAgH7DwEAAABbAAAAAAAAADihuxAF5RAaobsIACsqVsIA AFBTVFBSWC5ETEwAAAAAAAAAAE5JVEH5v7gBAKoAN9luAAAARDpcRGF0YSBGaWxlc1xPdXRMb29r XE91dExvb2sucHN0AAADAP4PBQAAAAMADTT9NwAAAgF/AAEAAAAxAAAAMDAwMDAwMDA2QjBGN0Mw NTg3RjZEMjExOTIyRDUwM0MwN0MxMDAwMDQ0MDAzNDAwAAAAAHoo ------=_NextPart_000_003E_01BF6D8B.2B7A99C0-- From majordomo-users-owner Wed Feb 2 13:57:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA01572; Wed, 2 Feb 2000 13:50:13 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id NAA01555 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 13:50:09 -0800 (PST) Received: from sun2.kkf.de (privat.kkf.net [212.63.32.16]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA06781 for ; Mon, 17 Jan 2000 14:58:36 -0800 (PST) Received: from designofsites.de (h1-dial25.privat.kkf.net [212.63.34.56]) by sun2.kkf.de (8.9.1/8.9.1) with ESMTP id AAA03119 for ; Tue, 18 Jan 2000 00:10:04 +0100 (MET) Message-ID: <3883A121.550E6@designofsites.de> Date: Tue, 18 Jan 2000 00:09:21 +0100 From: Ralf Semroch Organization: design of sites X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: de,en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Problem with an email-adress Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello, somebody subscribed my flash4-list using the adress " unsubscribe.flash4@milestone.prohost.de". I am the listowner of the list and I can't get this adress out of my list... approve unsubscribe flash4 unsubscribe.flash4@milestone.prohost.de doesn't work... Any ideas? Thanks in advance, Ralf -- mit freundlichen gruessen ralf semroch semroch@designofsites.de visit http://www.flash4-center.de From majordomo-users-owner Wed Feb 2 14:11:05 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA01552; Wed, 2 Feb 2000 13:50:08 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id NAA01542 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 13:50:05 -0800 (PST) Received: from ffmail.nctda.org ([208.214.40.250]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA06697 for ; Mon, 17 Jan 2000 14:51:04 -0800 (PST) Received: from remarketing.com (ROBERT [208.214.40.25]) by ffmail.nctda.org with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id CHKZML47; Mon, 17 Jan 2000 17:59:06 -0500 Message-ID: <388395EE.EE71FACA@remarketing.com> Date: Mon, 17 Jan 2000 17:21:34 -0500 From: "Affiliated ReMarketing Web--ITParade.com" Organization: Affiliated ReMarketing Web--ITParade.com X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo-Users@GreatCircle.COM Subject: Sending multiple messages Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Has anyone experienced majordomo sending out the same message multiple times to each address on the list? We have several mailing lists but on the large one, 2500 subscribers, it does not stop sending out messages. We've had to kill the list. Any help would be appreciated -- Robert Davie ITParade.com/Affiliated ReMarketing Web www.itparade.com www.remarketing.com corporate.itparade.com (919)572-1775 (919)572-1776 fax From majordomo-users-owner Wed Feb 2 14:41:56 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA02070; Wed, 2 Feb 2000 14:30:50 -0800 (PST) Received: from femiweb.com (sagittarius.hosting4u.net [209.15.2.33]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id OAA02061 for ; Wed, 2 Feb 2000 14:30:41 -0800 (PST) Received: from jtadore1 ([213.56.41.218]) by femiweb.com ; Wed, 02 Feb 2000 16:44:55 -0600 Reply-To: From: "Redacteur FemiWeb" To: "MajordomoUsers" Subject: Maj. does not recognize the address of the list Date: Wed, 2 Feb 2000 23:28:45 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Can you say something about this ? I am on communitech. I have some lists there. Since 2 or 3 days, I receive that : Hi. This is the qmail-send program at phoebe.hosting4u.net. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : This message is looping: it already has my Delivered-To line. (#5.4.6) --- Below this line is a copy of the message. Return-Path: Received: (qmail 16777 invoked by alias); 2 Feb 2000 22:27:32 -0000 Delivered-To: sagittarius-femiweb-femilist-list@phoebe.hosting4u.net ..... Well, my list is femilist and I am on sagittarius. And support is elsewhere... Thanks. (In a simple english, or in french ;-)) Albert Ohayon, redacteur. http://www.femiweb.com http://www.epsyweb.com http://www.petitweb.com Etre humain ou ne pas être, serait ce la question ? From majordomo-users-owner Wed Feb 2 17:10:31 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA03176; Wed, 2 Feb 2000 15:58:15 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id PAA03166 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 15:58:13 -0800 (PST) Received: from orenco.com (orenco.com [209.130.191.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA23093 for ; Tue, 18 Jan 2000 14:46:20 -0800 (PST) Message-Id: <200001182246.OAA23093@honor.greatcircle.com> Received: from 192.168.200.130 by orenco.com with SMTP (QuickMail Pro Server for MacOS 1.1.2); 18-Jan-2000 14:59:29 -0800 Date: 18 Jan 00 15:03:25 -0800 From: Pete Norton Subject: RE: Majorcool question... To: "majordomo-users" , mjn X-Mailer: QuickMail Pro 1.5.4 (Mac) X-Priority: 3 Reply-To: Pete Norton MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-Ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Reply to: RE: Majorcool question... You have to run the mj_key_cache script to update the cache that Majorcool uses. The command is typically //wrapper mj_key_cache -------------- Pete Norton pnorton@orenco.com Orenco Systems, Inc. ------------------------------- mjn wrote: >I just added a list to majordomo and it is operating properly but the new >list does not show up in the 'modify' section of majorcool...any ideas? > From majordomo-users-owner Wed Feb 2 17:25:37 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA03589; Wed, 2 Feb 2000 16:06:06 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA03581 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 16:06:03 -0800 (PST) Received: from dogbert.precisioncs.net (pcsi2.coast.net [207.158.140.138]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA04129 for ; Mon, 24 Jan 2000 07:56:10 -0800 (PST) Received: from jtaylor (really [131.107.2.215]) by precisioncs.net via in.smtpd with smtp id (Debian Smail3.2.0.102) for ; Mon, 24 Jan 2000 11:08:58 -0500 (EST) From: "Jason M. Taylor" To: Subject: aliases file Date: Mon, 24 Jan 2000 11:05:08 -0500 Message-ID: <000601bf6684$c9757ea0$0800a8c0@precisioncs.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I can't seem to get the aliases file right. Below is what I have so far = and it doesn't seem to be working, if someone could point me in the = right direction that would be great. thanks.. majordomo: "|/home/majordomo/wrapper majordomo" owner-majordomo: me, =20 majordom: owner-majordomo Majordomo-Owner: owner-majordomo owner-admin-list: me, =20 admin-list-approval: owner-admin-list admin-list-request: "|/home/majordomo/wrapper majordomo -l admin-list" owner-admin-list-request: owner-admin-list admin-list: "|/usr/majordomo/wrapper majordomo -l admin-list" -Jason From majordomo-users-owner Wed Feb 2 17:40:06 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA03093; Wed, 2 Feb 2000 15:54:57 -0800 (PST) Received: from bifrost.lesbell.com.au (bifrost.lesbell.com.au [203.35.202.154]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id PAA03086 for ; Wed, 2 Feb 2000 15:54:50 -0800 (PST) Received: by bifrost.lesbell.com.au(Lotus SMTP MTA v1.2 (600.1 3-26-1998)) id 4B25687A.0000DBDA ; Thu, 3 Feb 2000 11:09:22 +1100 X-Lotus-FromDomain: LES BELL AND ASSOCIATES PTY LTD From: "Les Bell" To: majordomo-users@greatcircle.com Message-ID: <4B256879.0083686B.00@bifrost.lesbell.com.au> Date: Thu, 3 Feb 2000 11:09:08 +1100 Subject: CNAME for list server Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is probably a simple question, but I've been re-reading the docs to the extent that I can't see the wood for the trees: I have a host, canonical name abelard.lesbell.com.au, on which I have set up a list. It's running majordomo 1.94.3 and sendmail 8.9.1. Because I might well move the list to a different host later, I set up a CNAME record for this purpose in the DNS, giving it the CNAME lists.lesbell.com.au. sendmail.cw has an entry for the lists CNAME, and majordomo.cf has $whereami = "lists.lesbell.com.au";. The list.config file has reply_to = "nc-instructors@lists.lesbell.com.au";. Yet, sendmail is mangling the hostname as it sends messages, so that the hostname in all the header fields is "abelard" rather than "lists" (irrelevant lines excised): Received: (from majordom@localhost) by abelard.lesbell.com.au (8.9.1a/8.9.1) id KAA03174 for nc-instructors-outgoing; Thu, 3 Feb 2000 10:20:56 +1100 From: "Les Bell" To: nc-instructors@abelard.lesbell.com.au Sender: owner-nc-instructors@abelard.lesbell.com.au Precedence: bulk Reply-To: nc-instructors@abelard.lesbell.com.au I know I've overlooked something obvious, somewhere, but I can't, for the life of me, see what it is. Anybody? Best, --- Les [http://www.lesbell.com.au] From majordomo-users-owner Wed Feb 2 17:52:25 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA03352; Wed, 2 Feb 2000 16:02:03 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA03329 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 16:01:58 -0800 (PST) Received: from sol.airfiberinc.com ([209.68.254.177]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA11091 for ; Wed, 19 Jan 2000 15:14:26 -0800 (PST) Received: from airfiberinc.com ([192.168.1.164]) by sol.airfiberinc.com (Netscape Messaging Server 3.62) with ESMTP id 78; Wed, 19 Jan 2000 15:26:29 -0800 Message-ID: <38864851.E96B3CB0@airfiberinc.com> Date: Wed, 19 Jan 2000 15:27:13 -0800 From: "Bill Houle" X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Lawler CC: majordomo-users@GreatCircle.COM Subject: Re: subscription tests and web server error on MajorCool References: <38853D47.E51633CE@wsadmin6.cv.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Bill Lawler wrote: > > If I use the Quick View mode, it works ok. Why would the web server > think there are too many headers from the cgi-script if I don't use > Quick View mode? It's probably a case of premature end-of-headers (caused by Perl error) rather than "too many headers" (very few headers HTTP are actually generated by the script). The fact that Quick View works means that the is_subscribed() routine is likely barfing as it processes your lists. If I had to guess, I'd say you have a funky non-MJ-readable file sitting in the lists directory and MjC is failing on open. > If I try to browse lists and check the Unsubscribed or Subscribed and > use Quck View mode, Majorcool says "You Must Enable Subscription Tests > For This Browse Function.". "Subscription Tests" == "Not Quick View" mode. By definition, Quick View and "show [un]subscribed" are mutually exclusive concepts. The whole point of Quick View is to NOT do any subscription tests in the interest of speed. --bill From majordomo-users-owner Wed Feb 2 17:58:15 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA03538; Wed, 2 Feb 2000 16:05:34 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA03526 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 16:05:29 -0800 (PST) Received: from mail.linkup.net (mail.linkup.net [206.156.227.5]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA19721 for ; Sun, 23 Jan 2000 10:52:25 -0800 (PST) Received: by mail.linkup.net from localhost (router,SLMail V3.2); Sun, 23 Jan 2000 13:12:43 -0600 Received: by mail.linkup.net from [206.156.227.157] (206.156.227.157::mail daemon; unverified,SLMail V3.2); Sun, 23 Jan 2000 13:12:42 -0600 Mime-Version: 1.0 X-Sender: "Ross Anderson" Message-Id: Date: Sun, 23 Jan 2000 13:03:15 -0600 To: Majordomo-Users@GreatCircle.COM From: "Ross Anderson" Subject: Help with detailed Aliases Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-SLUIDL: 9CC54B9D-D07D11D3-8B5800A0-C98D89DD Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hey, I've recently installed Majordomo on a local Linux (redhat 6.1) machine. 1.94-5 version. We're moving over 30 some lists from an old majordomo server version 1.4 something. The major probelm I am experiencing is that I can't find a doc document that details how to set up the aliases file correctly for all the issues I need to invoke. If someone could either point me in a direction where I can find an expample of what I descibe or a create one and e-mail it to me I'd be greatly appreiciative. I need to have the following setup. A list that is checked using the resend feature, has digesting and archiving. And then another digest list for the "digestified messages" from the main list and also add's in thoes who are sub scribed to the digest list. Any help is greatly appreciated. rosander@linkup.net Ross Anderson DBA Cameron Theatre and Sound Home:1-218-291-9327 fax or voice. AOL IM:RossWolfie ICQ:20501774 E-mail: rosander@linkup.net Alt E-mail:Lonewolfnight@hotmail.com http://www.linkup.net/users/rosander/FM_LARP.html From majordomo-users-owner Wed Feb 2 18:02:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA03523; Wed, 2 Feb 2000 16:05:28 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA03510 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 16:05:24 -0800 (PST) Received: from callisto.geotec.net (callisto.geotec.net [208.244.246.5]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA09584 for ; Sat, 22 Jan 2000 17:02:44 -0800 (PST) Received: from dcurryhome ([63.73.7.10]) by callisto.geotec.net (Post.Office MTA v3.5.3 release 223 ID# 0-63701U10000L1000S0V35) with SMTP id net for ; Sat, 22 Jan 2000 19:15:31 -0600 From: "Daniel Curry" To: Date: Sat, 22 Jan 2000 19:16:39 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Version 1.94.9 on RH6.1 AMD K6-400 w/256Mb ram I get the following messages when I try to subscribe myself to the list. Geotec.net is my ISP. I have used the RPM available on the redhat FTP site and Webmin to configure majordomo. I wish to set up majorcool as soon as I can get this working. Config-test states that all is OK. Does anyone have any ideas? The original message was received at Sat, 22 Jan 2000 16:38:50 -0600 from callisto.geotec.net [208.244.246.5] ----- The following addresses had permanent fatal errors ----- "|/usr/lib/majordomo/wrapper majordomo" (expanded from: ) ----- Transcript of session follows ----- sh: wrapper not available for sendmail programs 554 "|/usr/lib/majordomo/wrapper majordomo"... Service unavailable Daniel Curry Professional Computer Programming and Networking e-mail:dcurry@pcpn.net It is by caffeine alone that I set my mind in motion; It is by the beans of Java that my thoughts acquire speed; The hands acquire shakes, the shakes become a warning; It is by caffeine alone that I set my mind in motion. From majordomo-users-owner Wed Feb 2 18:15:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA03149; Wed, 2 Feb 2000 15:57:36 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id PAA03139 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 15:57:34 -0800 (PST) Received: from mail1.den.wantweb.net (mail1.den.wantweb.net [24.236.11.6]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA18756 for ; Tue, 18 Jan 2000 08:37:36 -0800 (PST) Message-Id: <200001181637.IAA18756@honor.greatcircle.com> Received: from rgallegos ([24.236.12.50]) by mail1.den.wantweb.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 605-42905U2500L250S0) with SMTP id AAA159; Tue, 18 Jan 2000 09:47:20 -0700 From: "Raul A. Gallegos" To: "Bruce.Boulding@Vicorp.com" Cc: "majordomo-users@greatcircle.com" Date: Tue, 18 Jan 2000 09:49:20 -0700 Reply-To: "Raul A. Gallegos" X-Mailer: PMMail 2000 Professional (2.10.2000) For Windows 98 (4.10.2222) In-Reply-To: <000e01bf61c0$ef42a2c0$14fc8bcf@vicorp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Information on MJ 2 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk There is a web interface you can use to configure majordomo once the initial installation is done and you have it working. This web config will allow you to create/remove lists, update the .cf file as well as maintain the lists themselves. The program is caled webmin. Webmin is not just for majordomo, it's for administering your entire box. All though I think it's a great utility I still prefer using the box directly as this allows me to know what I'm putting where. You can get webmin from http://www.freshmeat.com and search under web tools. Regards. On Tue, 18 Jan 2000 09:33:05 -0500, Bruce Boulding wrote: >I have MJ 2, but am looking for clarification on >- location (if it exists) on documentation >- web interface for configuration (if it exists) > >Any help would be appreciated. Just got my own presence on the Internet: http://www.asmodean.net Email: raul@asmodean.net -- icq# 5283055 Mystical Gates: telnet://mg.asmodean.net:2369 Info about MG builders email mg@asmodean.net From majordomo-users-owner Wed Feb 2 18:30:20 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA03569; Wed, 2 Feb 2000 16:05:52 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA03551 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 16:05:44 -0800 (PST) Received: from zulu.ctp.com (zulu.ctp.com [149.44.2.12]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA21635 for ; Sun, 23 Jan 2000 14:51:02 -0800 (PST) Received: from ctp.com (mailigw.ctp.com [149.44.9.32]) by zulu.ctp.com (8.8.8/8.8.8) with ESMTP id SAA25993 for ; Sun, 23 Jan 2000 18:03:47 -0500 (EST) Received: from thebrain.ctp.com (thebrain.ctp.com [149.44.15.21]) by ctp.com (8.8.6/8.8.5) with ESMTP id SAA07082 for ; Sun, 23 Jan 2000 18:03:47 -0500 (EST) Received: from tsunami by thebrain.ctp.com (8.8.8+Sun/C.1.0.6) id SAA26890; Sun, 23 Jan 2000 18:03:46 -0500 (EST) Reply-To: From: "Deepak Vaidya" To: Subject: Error messages with subscribe or unsubscribe messages Date: Sun, 23 Jan 2000 18:03:42 -0500 Message-ID: <000901bf65f6$18843160$0c0ba8c0@tsunami> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello, I am having problems with majordomo, where it is using up all the resources on a Sun Sparc 20 system. I get the following error message, when I try to subscribe 600+ users to the mailing list, which is automatically generated. ============================================================= MAJORDOMO ABORT (mj_majordomo)!! Can't append to /opt/local/majordomo/majordomo-1.94.4/lists/fri-remind: Interrupted system call ============================================================== When I look at /var/adm/messages it gives me out of process for user id 1 and majordomo userid. The system has 64MB of memory 768MB of swap (I know I need to add more memory). Running majordomo 1.94.4, Perl version 5.005_02, stock sendmail v8.8.8. I can fix the problem by increasing the user process limit or putting in sleep commands between each subscribe. Has anyone run into similar situation, if so how did you fix the problem. Is there a way to make majordomo fork only certain amount of processes? Thanks in Advance. - Deepak From majordomo-users-owner Wed Feb 2 18:30:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA03306; Wed, 2 Feb 2000 16:01:41 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA03296 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 16:01:39 -0800 (PST) Received: from yog-sothoth.emea.sgi.com (eugate.sgi.com [192.48.160.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA06158; Wed, 19 Jan 2000 07:12:38 -0800 (PST) Received: from eurohub.neu.sgi.com (gate-eurohub.neu.sgi.com [144.253.133.139]) by yog-sothoth.emea.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA811675; Wed, 19 Jan 2000 16:22:47 +0100 (MET) mail_from (cwilson@neu.sgi.com) Received: from slurp.neu.sgi.com (slurp.neu.sgi.com [144.253.130.8]) by eurohub.neu.sgi.com (980427.SGI.8.8.8/19990607.SGI.cwilson.europe.hoststrip) via ESMTP id QAA57252; Wed, 19 Jan 2000 16:22:20 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by slurp.neu.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id QAA34962; Wed, 19 Jan 2000 16:22:13 +0100 (MET) To: majordomo-announce@greatcircle.com, majordomo-workers@greatcircle.com, majordomo-users@greatcircle.com Subject: Majordomo 1.94.5 released -- security and bugfix release X-Mailer: Mew version 1.95b3 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000119162213B.cwilson@unknown-domain> Date: Wed, 19 Jan 2000 16:22:13 +0100 (MET) From: Chan Wilson X-Dispatcher: imput version 991025(IM133) Lines: 62 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Majordomo 1.94.5 has been released, another security bugfix release. Available from ftp.GreatCircle.com and ftp.sgi.com: ftp://ftp.greatcircle.com/pub/majordomo/majordomo.tgz ftp://ftp.sgi.com/other/majordomo/majordomo.tgz Thanks to all the volunteers who have produced the patches and made them available to the community. --Chan Changes from 1.94.4 to 1.94.5 A straightforward patch release, 99% from the collected 1.94.4 patches: o digest_rm_fronter and digest_rm_footer now work. o unsubcribe_policy now has +confirm feature o More hostile address checking o archive2.pl makes archives world readable. o bounce had an innocuous y2k bug, and wanted a 'bounces' list password even when called as unsub o better description of the moderator function. o Fixes 'restrict_post = #!$list' substitution and blank lines in config files o Better error reporting when majordomo.cf is wrong. o Detects some attachments sent as commands o Approve commands can span lines now. o resend has better messages for taboo_headers problems o fixed: header corruption when Subject: is blank and subject tags are used. ========================================================================================= archive2.pl.0 () Ensures archives are world readable. bounce.0 () Bounce script and unsub. config_parse.pl.1 () Another trivial 1.94.4 patch: moderator config_parse.pl.2 (B) Fixes 'restrict_post = #!$list' substitution config_parse.pl.5 (F) Fixes failing to accept newconfig... (cleaned) config_parse.pl.6 (B) Fixes bug when several consecutive blank lines or a trailing blank line appear in a string array digest-config_parse.pl.1 (F) Adds the functionality promised by digest_rm_fronter majordomo-config.1 (F) +config patches for unsubscribe_policy majordomo.0b (B+) Fixes some error messages and minor bugs related to aliasing -request to invoking majordomo with -l majordomo.1 (F) PATCH: no attachments (was Re: Strange stuff) majordomo.3 () A minor little patch that cleans up newinfo/newintro majordomo.6 (F) Patch for APPROVE linewraps majordomo.7 () Work-around for Perl 5.005 problem majordomo.pl.1 (S+) Fixes security hole with :include:syslog (untested) request-answer.0 () Request-answer should not reply to mailer-daemon et al resend.2 (F) A nice patch for debugging taboo_headers resend.5 (B++) Fixes header corruption when Subject: is blank and subject tags are used resend.8 () More headers for the skip headers string resend_parse.1 () Corrected PATCH: moderator behavior From majordomo-users-owner Wed Feb 2 18:42:30 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA03403; Wed, 2 Feb 2000 16:02:35 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA03392 for majordomo-users@greatcircle.com; Wed, 2 Feb 2000 16:02:32 -0800 (PST) Received: from server.totalnetnh.net (server.totalnetnh.net [216.64.14.16]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA23667 for ; Thu, 20 Jan 2000 07:50:02 -0800 (PST) Received: from morbus (morbus.totalnetnh.net [216.64.14.23]) by server.totalnetnh.net (8.9.3/8.9.3) with SMTP id KAA14858 for ; Thu, 20 Jan 2000 10:59:41 -0500 Message-ID: <00d401bf635f$b71c6e80$170e40d8@morbus> From: "Kevin Hemenway" To: Subject: Only Sends to Two People? Help, please! Date: Thu, 20 Jan 2000 11:02:13 -0500 Organization: Total Net NH, LLC MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Good day. I'm running sendmail 8.9.3, perl 5.04 something or other (the one that comes with Redhat 6.0) and majordomo 1.94.4. Majordomo is configured for virtual domains, and I've been running four mailing lists for about a year now without a problem. I'd like to get this problem resolved as quickly as possible - the list needs to be running in a week. I started to add a mailing list yesterday, and ran into all sort of problems, the primary being that sendmail/majordomo only seems to send out to the first two people in my subscriber list. Before I give you some logs and examples, this is what I'm trying to accomplish: I want all email addresses to look like "vd-*@disobey.com" but I want people to be able to subscribe by doing "subscribe viewerdiscretion". As such, here is my virtusertable concerning this entry: owner-vd@disobey.com owner-vd vd-owner@disobey.com owner-vd vd@disobey.com vd vd-request@disobey.com vd-request vd-approval@disobey.com vd-approval And my majordomo-aliases file (which is automatically rebuilt upon save): Pardon wrapping - I've prefaced new lines with a ### for readability in this mail: owner-vd: morbus,nobody ### vd: "|/usr/local/majordomo/runtime/wrapper resend -l viewerdiscretion -C /usr/local/majordomo/runtime/majordomo-disobey.cf -h disobey.com viewerdiscretion-doit,nobody" ### vd-approval: owner-vd ### viewerdiscretion-doit: :include:/usr/local/majordomo/lists.disobey/viewerdiscretion ### owner-vd-doit: owner-vd ### vd-request: "|/usr/local/majordomo/runtime/wrapper -C /usr/local/majordomo/runtime/majordomo-disobey.cf request-answer viewerdiscretion" ### owner-vd-request: owner-vd I can subscribe to the list fine (which is currently using a configuration that I can send upon request) and I can send using one of the two addresses listed in my restricted post file. I can also unsubscribe and approve commands correctly, yet whenever I send, it will only send to the first two addresses in the list, which is currently: info@totalnetnh.net morbus@disobey.com testing@disobey.com ugly@disobey.com My sendmail log reports the following (the extraneous spaces in the log are for formatting on my console). You'll see below my initial send (KAA27119) to the list, and then the resending to only two addresses - should be the four above... Jan 20 10:47:42 red sendmail[27119]: KAA27119: from=, size=777, class=0, pri=30777, nrcpts=1, msgid=<00bb01bf635d$adfcd6c0$170e40d8@morbus>, proto=SMTP, relay=morbus.totalnetnh.net [216.64.14.23] Jan 20 10:47:43 red sendmail[27120]: KAA27120: clone KAA27119, owner=owner-vd Jan 20 10:47:43 red sendmail[27123]: KAA27123: from=owner-vd@disobey.com, size=1025, class=-60, pri=199025, nrcpts=3, msgid=<00bb01bf635d$adfcd6c0$170e40d8@morbus>, relay=majordomo@localhost Jan 20 10:47:43 red sendmail[27120]: KAA27120: to="|/usr/local/majordomo/runtime/wrapper resend -l n -C e/majordomo-disobey.cf -h disobey.com viewerdiscretion-doit,nobody", delay=00:00:01, xdelay=00:00:00, mailer=prog, stat=Sent Jan 20 10:47:43 red sendmail[27125]: KAA27123: to=/dev/null^I, delay=00:00:00, xdelay=00:00:00, mailer=*file*, stat=Sent Jan 20 10:47:43 red sendmail[27125]: KAA27123: to=info@totalnetnh.net, delay=00:00:00, xdelay=00:00:00, mailer=esmtp, relay=server.totalnetnh.net. [216.64.14.16], stat=Sent (KAA14324 Message accepted for delivery) Jan 20 10:47:43 red sendmail[27125]: KAA27123: to=morbus@disobey.com, delay=00:00:00, xdelay=00:00:00, mailer=local, stat=Sent Kevin Hemenway -- ----------------------------------------------------------------- Total Net NH, LLC EMAIL: 15 Pleasant St., Suite 11 WEBSITE: Concord, NH 03301 PHONE: (603) 225-8422 -------------------------------------------------------------------- From majordomo-users-owner Wed Feb 2 19:00:45 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA05594; Wed, 2 Feb 2000 18:45:22 -0800 (PST) Received: from usinter.net (mail.usinter.net [206.171.66.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA05577 for ; Wed, 2 Feb 2000 18:45:12 -0800 (PST) Received: from usinter.net [209.85.130.137] by usinter.net [206.171.66.25] with SMTP (MDaemon.v2.8.7.0.R) for ; Wed, 02 Feb 2000 18:59:16 -0800 Message-ID: <3898EE73.C126792F@usinter.net> Date: Wed, 02 Feb 2000 18:56:51 -0800 From: "Todd A. Lyons" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Re: Sending multiple messages References: <388395EE.EE71FACA@remarketing.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: majordomo-users@GreatCircle.COM X-Return-Path: cannonball@usinter.net Reply-To: cannonball@usinter.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk "Affiliated ReMarketing Web--ITParade.com" wrote: > We have several mailing lists but on the large one, 2500 subscribers, it > does not stop sending out messages. We've had to kill the list. Did you check the messages going out to see if they were being relayed back to you by somebody's misconfigured mailer? If you are affixing a footer to the message it's pretty obvious by the multiple footers appended, one per trip through. -- Blue skies... Cannonball * One ring to rule them all, One ring to find them * * One ring to bring them all, and in the darkness bind them * Sauron From majordomo-users-owner Wed Feb 2 22:39:57 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA07852; Wed, 2 Feb 2000 22:31:23 -0800 (PST) Received: from riverside.jatek.net ([209.250.124.146]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id WAA07842 for ; Wed, 2 Feb 2000 22:31:16 -0800 (PST) Received: from jc300 ([192.168.0.101]) by riverside.jatek.net with SMTP (Mailtraq/1.1.4.1066) id RVRS74143E2B3 for majordomo-users@greatcircle.com; Wed, 02 Feb 2000 22:44:57 -0800 Message-Id: <4.2.0.58.20000202224412.00a7de30@192.168.0.67> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 02 Feb 2000 22:44:54 -0800 To: majordomo-users@greatcircle.com From: Jeff Lasman Subject: Re: Sending multiple messages In-Reply-To: <388395EE.EE71FACA@remarketing.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Hops: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 02:21 PM 1/17/00 Affiliated ReMarketing Web--ITParade.com wrote: >Has anyone experienced majordomo sending out the same message multiple >times to each address on the list? Yes, sporadically, and I've never been able to find out why. If you get any help offlist, please summarize it on the list for us. Thanks. Jeff -- Jeff Lasman, nobaloney.net , , From majordomo-users-owner Thu Feb 3 05:49:40 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA14480; Thu, 3 Feb 2000 05:37:48 -0800 (PST) Received: from riverside.jatek.net (node2.jatek2.dslspeed.ienet.com [209.250.124.146]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id FAA14473 for ; Thu, 3 Feb 2000 05:37:41 -0800 (PST) Received: from jc300 ([192.168.0.101]) by riverside.jatek.net with SMTP (Mailtraq/1.1.4.1066) id RVRS74213E30F for majordomo-users@greatcircle.com; Thu, 03 Feb 2000 05:51:51 -0800 Message-Id: <4.2.0.58.20000203055015.00abbb40@192.168.0.67> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 03 Feb 2000 05:51:47 -0800 To: majordomo-users@greatcircle.com From: Jeff Lasman Subject: Re: Only Sends to Two People? Help, please! In-Reply-To: <00d401bf635f$b71c6e80$170e40d8@morbus> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Hops: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Missing bit of information? Are the two addresses that are getting the list the addresses in your restricted post file? If so, then majordomo is finding the restricted posts file when it should be finding the list file. Jeff At 08:02 AM 1/20/00 Kevin Hemenway wrote: >Good day. I'm running sendmail 8.9.3, perl 5.04 something or other (the one >that comes with Redhat 6.0) and majordomo 1.94.4. Majordomo is configured >for virtual domains, and I've been running four mailing lists for about a >year now without a problem. I'd like to get this problem resolved as quickly >as possible - the list needs to be running in a week. > ...... -- Jeff Lasman, nobaloney.net , , From majordomo-users-owner Thu Feb 3 07:49:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA15586; Thu, 3 Feb 2000 07:36:24 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id HAA15579 for ; Thu, 3 Feb 2000 07:36:18 -0800 (PST) Received: (qmail 12898 invoked from network); 3 Feb 2000 15:50:55 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 3 Feb 2000 15:50:55 -0000 Date: Thu, 3 Feb 2000 08:49:00 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: Daniel Curry cc: majordomo-users@GreatCircle.COM Subject: Re: your mail In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is the smrsh problem. Grep in the FAQ for smrsh. Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com On Sat, 22 Jan 2000, Daniel Curry wrote: > Version 1.94.9 on RH6.1 AMD K6-400 w/256Mb ram > > I get the following messages when I try to subscribe myself to the list. > Geotec.net is my ISP. > I have used the RPM available on the redhat FTP site and Webmin to configure > majordomo. > I wish to set up majorcool as soon as I can get this working. Config-test > states that all is OK. > Does anyone have any ideas? > > The original message was received at Sat, 22 Jan 2000 16:38:50 -0600 > from callisto.geotec.net [208.244.246.5] > > ----- The following addresses had permanent fatal errors ----- > "|/usr/lib/majordomo/wrapper majordomo" > (expanded from: ) > > ----- Transcript of session follows ----- > sh: wrapper not available for sendmail programs > 554 "|/usr/lib/majordomo/wrapper majordomo"... Service unavailable > > > > Daniel Curry > Professional Computer Programming and Networking > e-mail:dcurry@pcpn.net > > It is by caffeine alone that I set my mind in motion; > It is by the beans of Java that my thoughts acquire speed; > The hands acquire shakes, the shakes become a warning; > It is by caffeine alone that I set my mind in motion. > > > From majordomo-users-owner Thu Feb 3 07:59:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA15603; Thu, 3 Feb 2000 07:38:35 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA15596 for ; Thu, 3 Feb 2000 07:38:29 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id KAA20580; Thu, 3 Feb 2000 10:52:16 -0500 (EST) Date: Thu, 3 Feb 2000 10:52:16 -0500 (EST) From: "Bill Casti (System Admin)" To: Pete Norton cc: majordomo-users , mjn Subject: RE: Majorcool question... In-Reply-To: <200001182246.OAA23093@honor.greatcircle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I installed a cron job to run the script every 30 minutes--probably more often than I need, but it's gets it run.... 0,30 * * * * /usr/local/majordomo/wrapper mj_key_cache ============================================================================= Bill Casti, CQA Email: help@quality.org - Domain Owner, QUALITY.ORG Pager: +1 800 604 6149 - List Moderator, "TQM in Manufacturing and Service Industries" ----------------------------------------------------------------------------- Self-service list subscription service at www.quality.org/cgi-bin/majordomo ============================================================================= On 18 Jan 2000, Pete Norton wrote: > Reply to: RE: Majorcool question... > You have to run the mj_key_cache script to update the cache that > Majorcool uses. The command is typically > > //wrapper mj_key_cache > > -------------- > Pete Norton > pnorton@orenco.com > Orenco Systems, Inc. > > ------------------------------- > mjn wrote: > >I just added a list to majordomo and it is operating properly but the > new > >list does not show up in the 'modify' section of majorcool...any ideas? > > > > > > > From majordomo-users-owner Thu Feb 3 08:26:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA15985; Thu, 3 Feb 2000 08:12:50 -0800 (PST) Received: from orenco.com (orenco.com [209.130.191.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA15978 for ; Thu, 3 Feb 2000 08:12:43 -0800 (PST) Message-Id: <200002031612.IAA15978@honor.greatcircle.com> Received: from 192.168.200.36 by orenco.com with SMTP (QuickMail Pro Server for MacOS 1.1.2); 03-Feb-2000 08:28:53 -0800 Date: 03 Feb 00 08:32:47 -0800 From: Pete Norton Subject: RE: Majorcool question... To: "majordomo-users" X-Mailer: QuickMail Pro 1.5.4 (Mac) X-Priority: 3 Reply-To: Pete Norton MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-Ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Reply to: RE: Majorcool question... Speaking of Majordomo problems, I send this message out Jan 18, and just got it back message from the listserver today (Feb 3)! Pete Norton wrote: > Reply to: RE: Majorcool question... >You have to run the mj_key_cache script to update the cache that >Majorcool uses. The command is typically > >//wrapper mj_key_cache > From majordomo-users-owner Thu Feb 3 09:56:19 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA17108; Thu, 3 Feb 2000 09:51:03 -0800 (PST) Received: from smtp.virginnet.co.uk (smtp-outbound1.ic24.net [195.44.63.11]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA17101 for ; Thu, 3 Feb 2000 09:50:57 -0800 (PST) Received: from [150.55.55.4] ([195.44.225.202]) by smtp.virginnet.co.uk with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 3 Feb 2000 18:03:46 +0000 Subject: What do do about BOUNCES? Date: Thu, 3 Feb 2000 18:01:00 +0000 x-sender: chris@post.cybonet.co.uk x-mailer: Claris Emailer 2.0v3, January 22, 1998 From: Chris To: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Message-ID: <0fcd44603180320MAIL4@smtp.virginnet.co.uk> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk As a newbie I would appreciate some guidance. I have set up a list for an organisation who get a lot of traffic on their web site and about a dozen people joining their list each day. I am using a great little cgi script that allows people just to enter their email address in a text field and click GO. This subscribes them to the list. But for some reason, maybe because many non-English speakers are using the site, quite a number of the email addresses are wrong. Majordomo seems to reformat the address and put my domain (businessdata.com) in as the 2nd part of the address ie trashaddress@businessdata.com. Therefore all the messages like the foll come through to me: >>>> subscribe mlmworld trashaddress@businessdata.com **** Your request to Majordomo@businessdata.com: **** **** subscribe mlmworld secres@businessdata.com **** **** must be authenticated. How do I stop this, or at the least get these routed to the list owner? Chris St Cartmail From majordomo-users-owner Thu Feb 3 13:40:37 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA19724; Thu, 3 Feb 2000 13:36:22 -0800 (PST) Received: from dna.fi (dna.fi [62.236.152.249]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA19717 for ; Thu, 3 Feb 2000 13:36:15 -0800 (PST) Received: from chamber.dna.fi (dummy@chamber.dna.fi [62.236.155.125]) by dna.fi (8.9.1/8.9.1) with SMTP id XAA08764 for ; Thu, 3 Feb 2000 23:50:53 +0200 (EET) Received: (qmail 7242 invoked by uid 501); 3 Feb 2000 23:50:54 +0200 Date: Thu, 3 Feb 2000 23:50:54 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: Redacteur FemiWeb Cc: MajordomoUsers Subject: Re: Maj. does not recognize the address of the list Message-ID: <20000203235054.C7143@chamber.dna.fi> Reply-To: Mikko.Hanninen@iki.fi Mail-Followup-To: Redacteur FemiWeb , MajordomoUsers References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.1.2i In-Reply-To: ; from redacteur@femiweb.com on Wed, Feb 02, 2000 at 11:28:45PM +0100 Organization: None Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Redacteur FemiWeb wrote on Wed, 02 Feb 2000: > Can you say something about this ? Let's see. > I am on communitech. I have some lists there. > > Since 2 or 3 days, I receive that : > > Hi. This is the qmail-send program at phoebe.hosting4u.net. > I'm afraid I wasn't able to deliver your message to the following addresses. > This is a permanent error; I've given up. Sorry it didn't work out. > > : > This message is looping: it already has my Delivered-To line. (#5.4.6) Okay, that's a qmail error message, sent from phoebe.hosting4u.net. I'm guessing that sagittarius-femiweb-femilist-list is a mailing list, and it's probably run with ezmlm (most lists on qmail servers are). > --- Below this line is a copy of the message. > > Return-Path: > Received: (qmail 16777 invoked by alias); 2 Feb 2000 22:27:32 -0000 > Delivered-To: sagittarius-femiweb-femilist-list@phoebe.hosting4u.net > ..... > > Well, my list is femilist and I am on sagittarius. > And support is elsewhere... What server is your list running on? Is it phoebe.hosting4u.net, or something else? If it's something else, then what is happening is that 1) Someone subscribed the address sagittarius-femiweb-femilist-list@phoebe.hosting4u.net to your mailing list, or at least an address that forwards there 2) For some reason, the email is getting delivered twice to that address. It's possibly because the address sagittarius-femiweb-femilist-list@phoebe.hosting4u.net might be a mailing list. Could your list be subscribed to this list? (Creating a loop, if both lists are subscribed to each other...) If that's the case, then this is simply an error for one of your subscribed addresses; no different than getting a "mailbox full" message or something like that. I can't say anything more, there's not enough details... Hope this helps, Mikko -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / ST, DS9: FRofA #1: Once you have their money ... never give it back. From majordomo-users-owner Fri Feb 4 11:39:21 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA04767; Fri, 4 Feb 2000 11:32:10 -0800 (PST) Received: from lynx.smtp-gw.to (lynx.altaway.net [209.207.141.92]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA04760 for ; Fri, 4 Feb 2000 11:32:04 -0800 (PST) Received: from briannt by lynx.smtp-gw.to (8.8.8/8.8.8) with ESMTP id OAA17425 for ; Fri, 4 Feb 2000 14:45:00 -0500 (EST) From: "Brian Sullivan" To: "MajordomoUsers" Subject: Excluding certain email addresses Date: Fri, 4 Feb 2000 14:46:53 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20000203235054.C7143@chamber.dna.fi> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is there anything I can change in the config file to guarantee that MJ 1.94.4) never sends email ( of any kind including help messages) to a particular email address or to a particular domain. From majordomo-users-owner Fri Feb 4 11:54:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA04708; Fri, 4 Feb 2000 11:26:05 -0800 (PST) Received: from lsi.lsil.com (lsi.lsil.com [147.145.40.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA04701 for ; Fri, 4 Feb 2000 11:25:57 -0800 (PST) Received: from mhbs.lsil.com ([147.145.31.100]) by lsi.lsil.com (8.9.3+Sun/8.9.1) with ESMTP id LAA05053 for ; Fri, 4 Feb 2000 11:40:39 -0800 (PST) Received: from [147.145.207.10] by mhbs.lsil.com with ESMTP for majordomo-users@greatcircle.com; Fri, 4 Feb 2000 11:40:26 -0800 Received: from mint-tech.com (jjr-pc [147.145.207.91]) by mint-tech.com (8.8.8/8.8.8) with ESMTP id OAA20817 for ; Fri, 4 Feb 2000 14:40:24 -0500 (EST) Message-Id: <389B2B27.CC2AE14F@mint-tech.com> Date: Fri, 04 Feb 2000 14:40:23 -0500 From: Jim Reisert Organization: Mint Technology, Inc. X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Problem with 1.94.5 recognizing some commands? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I got the following response back from my new 1.94.5 installation when I tried to zubscribe myself: Subject: Majordomo results: (no subject) Date: Fri, 4 Feb 2000 14:20:59 -0500 (EST) From: Majordomo@test.host To: Jim_Reisert@mint-tech.com -- >>>> approve test.admin zubscribe **** approve: who? Succeeded (to list test). >>>> Anyone have an idea what's going on here? Is 1.94.5 more stringent about actually requiring an address? I did a clean install, I did not try to patch or upgrade my 1.94.4 installation. I have not migrated any lists yet. Perl is version 5.004_04 built for i386-bsdos - Jim -- Jim Reisert Voice: 781-685-3928 Mint Technology Fax: 781-685-3801 77 South Bedford Street Email: jim_reisert@mint-tech.com Burlington, MA 01803 WWW: http://www.mint-tech.com/ From majordomo-users-owner Fri Feb 4 13:39:21 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA05880; Fri, 4 Feb 2000 13:32:58 -0800 (PST) Received: from lepton.etown.com (adsl-207-212-51-167.dsl.snfc21.pacbell.net [207.212.51.167]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA05873 for ; Fri, 4 Feb 2000 13:32:52 -0800 (PST) Received: from lepton.etown.com (lepton.etown.com [207.212.51.167]) by lepton.etown.com (8.9.2/8.9.2) with ESMTP id NAA21819 for ; Fri, 4 Feb 2000 13:47:35 -0800 (PST) Date: Fri, 4 Feb 2000 13:47:35 -0800 (PST) From: ramon via lepton To: majordomo-users@GreatCircle.COM Subject: email validator Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, Does anyone have a working email validator for majordomo lists? Thanks, ramon. From majordomo-users-owner Fri Feb 4 17:09:21 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA08002; Fri, 4 Feb 2000 16:56:27 -0800 (PST) Received: from mailmsgone.thenew.net (smtp.thenew.net [207.245.252.177]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA07995 for ; Fri, 4 Feb 2000 16:56:21 -0800 (PST) Received: from [209.112.15.112] by mailmsgone.thenew.net (NTMail 4.20.0009/NU7668.00.391cc02b) with ESMTP id ahvgcaaa for ; Fri, 4 Feb 2000 20:05:27 -0500 Message-Id: <3.0.6.32.20000204203113.008972d0@mail.thenew.net> X-Sender: atscott@mail.thenew.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 04 Feb 2000 20:31:13 -0500 To: "Chris McEwen" From: Andrew Scott Subject: Re: Patch to "invisibly" zubscribe someone to a list? Cc: majordomo-users@GreatCircle.COM In-Reply-To: <002701bf63b5$c300c060$0100a8c0@earthlink> References: <38873072.F7D2E656@mint-tech.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 06:18 PM 2000/01/20 -0800, you wrote: >You can do a "replacelist" command do this. Be sure you are working from a >brand spankin' new copy of the WHO report, and put When I was with Esosoft, I was able to use the "replacelist" command, but now with my new majordomo service, I cannot get this command to work. Is there a patch we can install for this? (and where can we get it?) Andrew Scott From majordomo-users-owner Fri Feb 4 17:39:21 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA08361; Fri, 4 Feb 2000 17:32:30 -0800 (PST) Received: from ratchet.skechers.com (mail.skechers.com [207.238.255.5]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA08354 for ; Fri, 4 Feb 2000 17:32:23 -0800 (PST) Received: (from clay@localhost) by ratchet.skechers.com (8.9.3/8.9.3) id RAA09169; Fri, 4 Feb 2000 17:47:15 -0800 (PST) Date: Fri, 4 Feb 2000 17:47:15 -0800 From: Clay Irving To: ramon via lepton Cc: majordomo-users@GreatCircle.COM Subject: Re: email validator Message-ID: <20000204174715.D2312@ratchet.skechers.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: ; from ramon via lepton on Fri, Feb 04, 2000 at 01:47:35PM -0800 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, Feb 04, 2000 at 01:47:35PM -0800, ramon via lepton wrote: > Does anyone have a working email validator for majordomo lists? I use the Perl module Email::Valid to weed out obvious bad addresses: #!/usr/local/bin/perl use Email::Valid; $input_file = "foo.txt"; # Input file $good_addresses = "good.txt"; # File to store good addresses $bad_addresses = "bad.txt"; # File to store bad addresses open F, "$input_file" or die "$!\n"; open G, ">$good_addresses" or die "$!\n"; open R, ">$bad_addresses" or die "$!\n"; while ($address = ) { # Read the list of Email addresses chomp $address; $address =~ s/^\s+//; # Remove spaces in the Email address $valid = new Email::Valid; if ($valid->address( -address => $address)) { print G "$address\n"; # The address is valid } else { print R "$address\n"; # the address is not valid } } -- Clay Irving clay@skechers.com From majordomo-users-owner Sat Feb 5 12:23:07 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19874; Sat, 5 Feb 2000 11:07:32 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19861 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:07:30 -0800 (PST) Received: from nadal.loyno.edu (nadal.loyno.edu [141.164.24.217]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA12413 for ; Tue, 1 Feb 2000 09:05:13 -0800 (PST) Received: from klein.loyno.edu (klein.loyno.edu [141.164.240.128]) by nadal.loyno.edu (8.9.3/8.7) with ESMTP id LAA16534 for ; Tue, 1 Feb 2000 11:15:58 -0600 Date: Tue, 01 Feb 2000 11:19:32 -0600 From: Mike Klein To: majordomo-users@greatcircle.com Subject: scheduled sending of messages Message-ID: <5215919.3158392772@klein.loyno.edu> X-Mailer: Mulberry/2.0.0b8 (MacOS) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is there a way to schedule when majordomo sends out it messages. I would like to have all list activity take place between 2am and 5:30 am. Mike Klein Manager, System Services Loyola University New Orleans 6363 St. Charles Ave. New Orleans, LA 70118 Phone: 504.865.3470 Fax: 504.865.3470 From majordomo-users-owner Sat Feb 5 12:38:01 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19753; Sat, 5 Feb 2000 11:05:55 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19743 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:05:53 -0800 (PST) Received: from dns.iies.es (dns.iies.es [194.224.30.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id DAA09176 for ; Fri, 28 Jan 2000 03:26:05 -0800 (PST) Received: (from root@localhost) by dns.iies.es (8.8.5/8.8.5) id MAA06563 for Majordomo-Users@GreatCircle.COM; Fri, 28 Jan 2000 12:42:28 GMT Date: Fri, 28 Jan 2000 12:42:28 GMT From: Daniel Manero Bernao Message-Id: <200001281242.MAA06563@dns.iies.es> To: Majordomo-Users@GreatCircle.COM Subject: I Need Some Help! Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello to everybody, i am looking for some help in Majordomo-1.94.4 with Perl 5.004 and Sendmail 8.8.5: we are trying to restrict post to the menbers of the mailing list and we have tried all thing we have read in the FAQ's: -Change the outgoing alias and restric-post set to "listname" - Using -I in resend .And using the @filename directive. But what i always get is that nobody can post!!.No one from the list can post a message ! I would be so thankfull if anybody help me, Thanks in advance: webmaster@iies.es From majordomo-users-owner Sat Feb 5 12:47:07 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19679; Sat, 5 Feb 2000 11:05:11 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19668 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:05:07 -0800 (PST) Received: from cliff.advtech.uswest.com (at-fw.advtech.uswest.com [192.231.90.254]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA09996 for ; Wed, 26 Jan 2000 11:11:21 -0800 (PST) Received: from terran (terran [130.13.4.47]) by cliff.advtech.uswest.com (Pro-8.9.3/8.9.3) with ESMTP id MAA18651; Wed, 26 Jan 2000 12:25:54 -0700 (MST) Date: Wed, 26 Jan 2000 12:24:36 -0700 (MST) From: Robert Ellis X-Sender: rjellis@terran To: Majordomo-Users@GreatCircle.COM cc: Robert Ellis Subject: message_footer is intermittent Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We have a mailing list that includes a message_footer. When some users mail to it, the footer is included in their message. When other users mail to it, the footer is not. Does anyone have a guess why the footer is sometimes omitted? We're running majordomo 1.94.4 on Solaris 2.7 with sendmail 8.9.3. --Rob Ellis rjellis@advtech.uswest.com From majordomo-users-owner Sat Feb 5 12:48:23 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19646; Sat, 5 Feb 2000 11:04:57 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19638 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:04:55 -0800 (PST) Received: from ns1.nomorehotels.com (ns1.nomorehotels.com [209.73.40.30]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id CAA03188 for ; Wed, 26 Jan 2000 02:52:29 -0800 (PST) Received: from new (crow.dialup.access.net [166.84.196.166]) by ns1.nomorehotels.com (8.9.3/8.8.7) with SMTP id GAA03411 for ; Wed, 26 Jan 2000 06:05:33 -0500 Message-ID: <001001bf67ec$dfaa83a0$4100a8c0@new> From: "Webmaster" To: Subject: reply to in majordomo Date: Wed, 26 Jan 2000 06:02:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk hi im using the latest version of majordomo and redhat 6.0 and i cant seem to able to get the reply to the list working i changed the default in the list configuration file and it still dont work does this only work in digest mode? Thanks From majordomo-users-owner Sat Feb 5 13:01:36 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA20103; Sat, 5 Feb 2000 11:10:31 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA20093 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:10:28 -0800 (PST) Received: from nadal.loyno.edu (nadal.loyno.edu [141.164.24.217]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA02453 for ; Fri, 4 Feb 2000 08:23:11 -0800 (PST) Received: from klein.loyno.edu (klein.loyno.edu [141.164.240.128]) by nadal.loyno.edu (8.9.3/8.7) with ESMTP id KAA137100 for ; Fri, 4 Feb 2000 10:34:27 -0600 Date: Fri, 04 Feb 2000 10:38:07 -0600 From: Mike Klein To: Majordomo-Users@GreatCircle.COM Subject: multiple mail queues Message-ID: <10244985.3158649487@klein.loyno.edu> X-Mailer: Mulberry/2.0.0b8 (MacOS) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have set up two versions of majordomo. The second is to put mail into a separate mail queue so that it can be handled differently. However, when I include the -oQ /var/spool/listq to the mailer definition it blows up and returns an error 65335 (??) Without the -oQ it works fine. I am using sendmail 8.9.3 (I think). I shouldn't need to have two seperate versions of sendmail, should I? Mike Klein Manager, System Services Loyola University New Orleans 6363 St. Charles Ave. New Orleans, LA 70118 Phone: 504.865.3470 Fax: 504.865.2021 From majordomo-users-owner Sat Feb 5 13:09:17 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA20020; Sat, 5 Feb 2000 11:09:20 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA20010 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:09:18 -0800 (PST) Received: from spectre.atext.com (spectre.atext.com [204.62.245.27]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA18480 for ; Thu, 3 Feb 2000 11:49:03 -0800 (PST) Received: from cobra (cobra.atext.com [204.62.245.129]) by spectre.atext.com (8.9.3/8.9.3) with SMTP id MAA18727 for ; Thu, 3 Feb 2000 12:02:40 -0800 (PST) Received: from cobra by cobra (SMI-8.6/Spike-2.0) id MAA07642; Thu, 3 Feb 2000 12:03:35 -0800 Message-Id: <200002032003.MAA07642@cobra> Date: Thu, 3 Feb 2000 12:03:35 -0800 (PST) From: Allister Lee Reply-To: Allister Lee Subject: break up the recipients To: Majordomo-Users@GreatCircle.COM MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 7MF1UD2hIO4HT1L/Hm2Cmw== X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I'm having a problem distributing a message to my list because my majordomo is set up to send the message to all the subscribers all at once. The reason is that some domains have their MTA bounce the messages if the number of recipients is over a certain limit. They do this for spam prevention. How do I set up my majordomo so that it will breakup the list and send the messages as seperate messages? My majordomo server is using sendmail8.9.3 thanks, -al- From majordomo-users-owner Sat Feb 5 13:16:06 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19996; Sat, 5 Feb 2000 11:08:45 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19986 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:08:43 -0800 (PST) Received: from sun2.kkf.de (privat.kkf.net [212.63.32.16]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA16829 for ; Thu, 3 Feb 2000 09:22:09 -0800 (PST) Received: from designofsites.de (h1-dial31.privat.kkf.net [212.63.34.62]) by sun2.kkf.de (8.9.1/8.9.1) with ESMTP id SAA19696 for ; Thu, 3 Feb 2000 18:36:35 +0100 (MET) Message-ID: <3899BC3E.F60E7E1B@designofsites.de> Date: Thu, 03 Feb 2000 18:34:54 +0100 From: Ralf Semroch Organization: design of sites X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: de,en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Cannot post if only subscribed to the digest Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello, I am the list-owner of a majordomo-mailinglist "flash4". It started in december '99 as a "normal" list. A few weeks later some people want to get a digest version of the list and I ask the provider to add a digest list. The provider sets up the digest and some people unsubscribe from the "normal" list and subscribe the digest. But when they are only members of the digest-version they can't post into the list and I get the bounces... What can we do? Any tips? Thanks in advanve, Ralf -- mit freundlichen gruessen ralf semroch semroch@designofsites.de visit http://www.flash4-center.de From majordomo-users-owner Sat Feb 5 13:24:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19965; Sat, 5 Feb 2000 11:08:21 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19954 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:08:19 -0800 (PST) Received: from riverside.jatek.net ([209.250.124.146]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id WAA07815 for ; Wed, 2 Feb 2000 22:30:07 -0800 (PST) Received: from jc300 ([192.168.0.101]) by riverside.jatek.net with SMTP (Mailtraq/1.1.4.1066) id RVRS74143E2A9 for majordomo-users@greatcircle.com; Wed, 02 Feb 2000 22:43:45 -0800 Message-Id: <4.2.0.58.20000202224227.00a2b750@192.168.0.67> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 02 Feb 2000 22:43:44 -0800 To: majordomo-users@greatcircle.com From: Jeff Lasman Subject: Re: Problem with an email-adress In-Reply-To: <3883A121.550E6@designofsites.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Hops: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk If you've got telnet or terminal access you can just manually edit the file /usr/local/majordomo/lists/flash4 (or whatever your path actually is). At 03:09 PM 1/17/00 Ralf Semroch wrote: >Hello, > >somebody subscribed my flash4-list using the adress " >unsubscribe.flash4@milestone.prohost.de". >I am the listowner of the list and I can't get this adress out of my >list... >approve unsubscribe flash4 >unsubscribe.flash4@milestone.prohost.de doesn't work... >Any ideas? > >Thanks in advance, > >Ralf -- Jeff Lasman, nobaloney.net , , From majordomo-users-owner Sat Feb 5 13:39:20 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19926; Sat, 5 Feb 2000 11:08:06 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19902 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:08:01 -0800 (PST) Received: from mail.okmicro.co.jp (ns.okmicro.co.jp [210.169.238.98]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA19225 for ; Tue, 1 Feb 2000 22:25:05 -0800 (PST) Received: from okmicro.co.jp ([192.168.111.31]) by mail.okmicro.co.jp (8.9.1/3.6W) with ESMTP id PAA15565 for ; Wed, 2 Feb 2000 15:39:24 +0900 (JST) Message-ID: <3897D0FF.3B71887C@okmicro.co.jp> Date: Wed, 02 Feb 2000 15:38:55 +0900 From: Norio Ohki Organization: OK Microsystems X-Mailer: Mozilla 4.7 [ja] (Win98; I) X-Accept-Language: ja MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: install problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I'm newbie here. Just installed majordomo-1.94.3 to Solasis2.6. Results of config-test seems to be ok. But I received following error message from Mailer Demon. ----- The following addresses had permanent fatal errors ----- :include:/usr/local/majordomo-1.94.3/lists/abt (expanded from: ) ----- Transcript of session follows ----- 550 :include:/usr/local/majordomo-1.94.3/lists/abt... Cannot open /usr/local/majordomo-1.94.3/lists/abt: Group writable directory Message delivered to mailing list 554 ... aliasing/forwarding loop broken I tried to modify permissions of directory and files, in vain. What should I check settings? Any advice will be appreciated. Norio, Nagoya Japan From majordomo-users-owner Sat Feb 5 13:54:17 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19849; Sat, 5 Feb 2000 11:07:13 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19837 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:07:09 -0800 (PST) Received: from igw1.ericsson.com.au (igw1.ericsson.com.au [203.61.155.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA02703 for ; Mon, 31 Jan 2000 20:07:34 -0800 (PST) Received: from brsi02.epa.ericsson.se ([146.11.15.8]) by igw1.ericsson.com.au (8.9.1b+Sun/8.9.1) with ESMTP id PAA11315 for ; Tue, 1 Feb 2000 15:21:44 +1100 (EST) Received: from mcsi00.epa.ericsson.se (mcsi00 [146.11.8.201]) by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id PAA25887 for ; Tue, 1 Feb 2000 15:22:23 +1100 (EST) Received: from ericsson.com.au (brdhcp015-086.epa.ericsson.se [146.11.15.86]) by mcsi00.epa.ericsson.se (8.9.3+Sun/8.9.1) with ESMTP id PAA05819 for ; Tue, 1 Feb 2000 15:20:52 +1100 (EST) Message-ID: <38965F55.5DF9FDB4@ericsson.com.au> Date: Tue, 01 Feb 2000 15:21:41 +1100 From: Paul Crawford X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: Majordomo-Users@GreatCircle.COM Subject: Help with Majordomo bounce messages. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk G'day, I'm trying to set up a mailing list on a sun-solaris-2.6 system. I am receiveing some strange messages from majordomo. I can do things such as >>>> approve voohou2 unsubscribe test epacraw Succeeded. >>>> >>>> I can view the lists avaliable, view the info of lists, however whenever I try to subscribe from a windows system the following error occurs. MAJORDOMO ABORT (mj_majordomo)!! major@brsw362.epa.se punting to avoid mail loop Can anyone suggest any reasons as to why this problem is occurring?? Thanks Paul From majordomo-users-owner Sat Feb 5 13:54:43 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19949; Sat, 5 Feb 2000 11:08:14 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19937 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:08:11 -0800 (PST) Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA27027 for ; Wed, 2 Feb 2000 06:54:39 -0800 (PST) Received: from rjh1.cse.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Wed, 2 Feb 2000 15:09:02 +0000 From: Richard Hopkins Date: Wed, 2 Feb 2000 15:08:59 +0000 To: majordomo-users@greatcircle.com Subject: 1.94.5 and approving messages with attachments and moderated lists Message-ID: X-Mailer: Execmail for Win32 5.2 b1 Build (4) -- Evaluation Copy MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all - I recently upgraded from 1.94.4 to 1.95.5 and (think I) have noticed a change in behaviour when trying to send messages containing MIME attachments to *moderated* lists, when I want to approve the messages at the time that I send them (rather than wait for them to bounce and then approve them). Our mailers don't allow us to insert headers, so our documented procedure has been... http://www.bris.ac.uk/ISC/mdmc/mdmcfaq.html#approvemod which includes... 2.If your mailer does not allow you to add additional headers, you can add the line: Approved: sekrit as the first line of the message, followed by a blank line (which is required for your message to be sent properly) followed by the text of your message. The Approved: line and one following blank line will be deleted and the message will be passed without being checked. The blank line is important because it is used to differentiate between a pre-approval and the approval of a bounced message. I'm sure this worked with 1.94.4, but with 1.94.5 the messages are being bounced for approval (just to emphaise that this only happens when I send messages which include attachments and only when the target is a moderated list). Is this a change in behaviour, or is my memory playing tricks on me (again). Cheers, Richard Hopkins, Computing Service, University of Bristol, Bristol, BS8 1UD, UK Tel +44 117 928 7859 Fax +44 117 929 1576 RFC-822: Richard.Hopkins@bristol.ac.uk From majordomo-users-owner Sat Feb 5 14:09:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA20065; Sat, 5 Feb 2000 11:10:08 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA20055 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:10:05 -0800 (PST) Received: from cc-server9.massey.ac.nz (its-mail1.massey.ac.nz [130.123.128.11]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA21387 for ; Thu, 3 Feb 2000 16:14:16 -0800 (PST) Received: from its-xchg1.massey.ac.nz (its-xchg1.massey.ac.nz [130.123.128.14]) by cc-server9.massey.ac.nz (8.9.3/8.9.3) with ESMTP id NAA30218 for ; Fri, 4 Feb 2000 13:28:55 +1300 (NZDT) Received: by its-xchg1.massey.ac.nz with Internet Mail Service (5.5.2607.0) id ; Fri, 4 Feb 2000 13:30:58 +1300 Message-ID: From: "Edwards, Jenny" To: "'Majordomo-Users@GreatCircle.COM'" Subject: Problem with 'old' majordomo list owner commands Date: Fri, 4 Feb 2000 13:30:52 +1300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2607.0) Content-Type: text/plain; charset="ISO-8859-1" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I hope someone can help me with this or point me in the right direction of where to look! I've been looking through the web pages, archives etc but have been unable to find the information I require. Massey University (New Zealand) has recently upgraded to majordomo 1.94.4. We have been getting calls from list owners saying they have been getting messages with the 'set' command returned e.g.: >>>> set cs-jae campus-support description Mailing list for computer support staff at Massey University **** Command 'set' not recognized. **** No valid commands found. **** Commands must be in message BODY, not in HEADER. (The commands are in the message body.) Thank you, Jenny ========================================================================= | Jenny Edwards, Computing Services |EMail: J.A.Edwards@massey.ac.nz | | Massey University, Private Bag 11222 | Tel: (06) 356 9099 ext. 7633 | | Palmerston North, New Zealand | FAX: (06) 350-5607 | ========================================================================= ========================================================================= | Jenny Edwards, Computing Services |EMail: J.A.Edwards@massey.ac.nz | | Massey University, Private Bag 11222 | Tel: (06) 356 9099 ext. 7633 | | Palmerston North, New Zealand | FAX: (06) 350-5607 | ========================================================================= From majordomo-users-owner Sat Feb 5 14:24:17 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19769; Sat, 5 Feb 2000 11:06:01 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19758 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:05:58 -0800 (PST) Received: from tictac.etown.com (tictac.etown.com [209.249.73.40]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA14918 for ; Fri, 28 Jan 2000 12:59:32 -0800 (PST) Received: from lepton.etown.com ([207.212.51.167]) by tictac.etown.com (Post.Office MTA v3.5.3 release 223 ID# 0-63516U1000L100S0V35) with ESMTP id com; Fri, 28 Jan 2000 13:13:09 -0800 Date: Fri, 28 Jan 2000 13:13:05 -0800 (PST) From: ramon To: Sandeep Singh Cheema cc: majordomo users Subject: Re: subscription policy? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk To change the subscription policy check the config file for the list you want to change. Each list should have it's own config file. I would suggest reading it thoroughly. In there you will find: # subscribe_policy [enum] (open+confirm) /open;closed # One of three values: open, closed, auto; plus an optional # modifier: '+confirm'. Open allows people to subscribe themselves # to the list. Auto allows anybody to subscribe anybody to the list # without maintainer approval. Closed requires maintainer approval # for all subscribe requests to the list. Adding '+confirm', ie, # 'open+confirm', will cause majordomo to send a reply back to the # subscriber which includes a authentication number which must be # sent back in with another subscribe command. subscribe_policy = closed ramon. On Fri, 28 Jan 2000, Sandeep Singh Cheema wrote: > hi > new to the list > i m using majordomo 1.94.4 on hp-ux. > how do i change the subscription policy? can i hv different policies for > different lists? pl help > > thanx in advance. > > > ------------------------------------------------------ > Sandeep Singh Cheema > ACT-PSO > HCL Infosystems > 3rd Floor Subharam Complex > 144 MG Road Bangalore- 560001 > > ****************************************************** > Humor in the Court: > Q: The truth of the matter is that you were not an unbiased, objective > witness, isn't it. You too were shot in the fracas? > A: No, sir. I was shot midway between the fracas and the naval. > From majordomo-users-owner Sat Feb 5 14:36:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19698; Sat, 5 Feb 2000 11:05:19 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19686 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:05:15 -0800 (PST) Received: from ommadawn.cegep-heritage.qc.ca ([206.167.123.49]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA11334 for ; Wed, 26 Jan 2000 13:16:30 -0800 (PST) Received: from ommadawn.cegep-heritage.qc.ca (ommadawn.cegep-heritage.qc.ca [206.167.123.49]) by ommadawn.cegep-heritage.qc.ca (8.8.7/8.8.7) with ESMTP id QAA09417 for ; Wed, 26 Jan 2000 16:32:02 -0500 Message-ID: <388F67CE.73B406B5@ommadawn.cegep-heritage.qc.ca> Date: Wed, 26 Jan 2000 16:31:58 -0500 From: "Maurice G. Lafleur" X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.0.36 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: approve password Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi everyone, I have some 8 ML running on one server without a glitch an a single one I am trying to set up on a second server. I am not new to MJ. I went through the full motion: create majordomo user, create directory for MJ to reside and a sub directory for its list. I unpacked the software and did the installation procedure (make wrapper, make wrapper-install and make install), checked the configuration and all seems to be just fine. I then try to subscribe as a regular user, from a different machine. I get the notification that my sub will be approve by the owner, log on as the owner, reply to the approve message and get the following: (the actual password is hidden on this message for security reasons) >>>> approve PASSWORD subscribe clo **** approve: invalid list or password. **** Help for Majordomo@ux.cegep-heritage.qc.ca: I am 100% certain I typed the right password and that the list exists. I am totally flabbergastered. I re-installed the package twice with no more luck. I check the permissions and ownership of everything and all seems to jiive. I did a few more tests where as list owner I tried to approve subscription to a non-existing list. The message is slightly different: it says: "List does not exist". I assume then that the password is the culprit. I tried to change the password to something else, no go again. As I mentioned, I am not new to MJ, I have seen all sorts of situation in the past, but never like this. My set up is: Linux RedHat 5.2, Latest Perl interpreter, Majordomo 1.94.4 (not the RH CD version, the real McCoy from the MJ site). Help Please!!! Thanks -- MGL -- Maurice Lafleur Teacher, Heritage College mailto: admin@ommadawn.cegep-heritage.qc.ca 325 Cite des Jeunes http://ommadawn.cegep-heritage.qc.ca Hull. Qc. Canada Voice: +1(819).778.2270 x1412 J8Y 6T3 Fax: +1(819)778.7364 From majordomo-users-owner Sat Feb 5 14:52:30 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19572; Sat, 5 Feb 2000 11:03:19 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19562 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:03:15 -0800 (PST) Received: from sunone.fresno.edu (host16-209-203-119.fresno.skyk.net [209.203.119.16]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA04138 for ; Mon, 24 Jan 2000 07:56:26 -0800 (PST) Received: from choyt (host19-209-203-119.fresno.skyk.net [209.203.119.19] (may be forged)) by sunone.fresno.edu (8.9.2/8.9.2) with SMTP id IAA09700 for ; Mon, 24 Jan 2000 08:09:19 -0800 (PST) Message-Id: <3.0.6.32.20000124080557.0079f120@mail.fresno.edu> X-Sender: choyt@mail.fresno.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 24 Jan 2000 08:05:57 -0800 To: majordomo-users@greatcircle.com From: Chris Hoyt Subject: Help Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have tried to get majordomo running and having problems. I know it must be something obvious staring me right in the eye. We are also running sendmail 8.9.2 Here is my setup: drwxrwxr-x 7 smtp majordom 1024 Jan 24 07:59 majordomo drwxrwxrwx 3 smtp majordom 7680 Jan 24 07:59 lists example of a list -rwxr--r-- 1 majordom majordom 3863 Jan 19 15:11 tec2008 -rwxr--r-- 1 root other 9 Jan 18 15:44 tec2008.admin -rwxr--r-- 1 root other 14828 Aug 16 13:58 tec2008.config -rwxr--r-- 1 root other 137 Aug 16 13:58 tec2008.info -rwxr-xr-- 1 majordom majordom 0 Jan 20 08:51 tec2008.new -rwxr--r-- 1 root other 9 Aug 16 13:58 tec2008.passwd Here is the results of the wrapper test. ------------------------------------------------------------ ---------------- Config-test for Majordomo ---------------- ------------------------------------------------------------ --------------------- Obvious things: --------------------- ------------------ environment variables ------------------ HOME=/usr/local/majordomo LOGNAME=choyt MAJORDOMO_CF=/usr/local/majordomo/majordomo.cf PATH=/bin:/usr/bin:/usr/ucb SHELL=/bin/sh TZ=US/Pacific --------------------- euid/egid checks --------------------- effective user = choyt (uid 1507) effective group = staff majordom sysop email wmaster misc sysadmin tty mail a dm sys bin other root staff (gid 10 16 15 401 402 400 14 7 6 4 3 2 1 0 10 ) ---------------------- uid/gid checks ---------------------- real user = choyt (uid 1507) real group = staff majordom sysop email wmaster misc sysadmin tty mail a dm sys bin other root staff (gid 10 16 15 401 402 400 14 7 6 4 3 2 1 0 10 ) ------------------------------------------------------------ Non obvious things that cause headaches: ------------------------------------------------------------ Good: 'require'd /usr/local/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.4. --==> Majordomo home directory is /usr/local/majordomo. ------------------- Include directories ------------------- /usr/local/majordomo /usr/local/lib/perl5/sun4-solaris/5.00404 /usr/local/lib/perl5 /usr/local/lib/perl5/site_perl/sun4-solaris /usr/local/lib/perl5/site_perl . --------------------------- Home --------------------------- Good: changedir to /usr/local/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/majordomo/lists has good permissions. --------------------------- log --------------------------- Good: logfile /usr/local/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... New configuration variables (see sample.cf): $config'default_subscribe_policy Have you configured where Majordomo is? $whereami is fresno.edu Good: yup! ----------------------- end of tests ----------------------- Nothing bad found! Majordomo _should_ work correctly. If it doesn't, check your configuration file (/usr/local/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. Enjoy! Chris Hoyt Network Administrator Fresno Pacific University From majordomo-users-owner Sat Feb 5 15:01:47 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA20084; Sat, 5 Feb 2000 11:10:19 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA20074 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:10:16 -0800 (PST) Received: from mail.brussels2000.org (mail.brussels2000.org [194.78.4.226]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA00488 for ; Fri, 4 Feb 2000 04:28:46 -0800 (PST) Reply-To: From: "Eric Hanuise" To: Date: Fri, 4 Feb 2000 13:43:24 +0100 Message-ID: <39A29FFE7681D311AC8100508B733646D47C@EXCHANGE> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have majordomo 1.94.4 and I use smail. I've set up several simple lists which work OK ( no resend) I wanted this week to create some moderated lists and started to use = resend. I tried several configurations and aliases but I can't seem to get it = right. What happens is that messages sent to the lists are processed OK, but = while the headers from resent appears normally, the original headers of the = mail do appear in teh message body. I guess this is because the headers are separated by a blank line after = the X-UIDL tag, but I can't figure out how to remove it :( ( note that my /etc/mailname file has no trailing linefeed) here is an example output from majordomo : >Return-Path: >Received by liza: by brussels2000.org > via sendmail from stdin > id (Debian Smail3.2.0.102) > for test-list; Thu, 13 Jan 2000 15:51:54 +0100 (CET)=20 >Message-Id: >Date: Thu, 13 Jan 2000 15:51:54 +0100 (CET) >From: owner-test@brussels2000.org >Apparently-To: test-list >X-UIDL: bdefb38710899a3085e8dbc6751df228 > >Received by liza: from sysadmin (really [194.78.4.225]) by = brussels2000.org > via in.smtpd with smtp (ident fwuser using rfc1413) > id (Debian Smail3.2.0.102) > for ; Thu, 13 Jan 2000 15:51:54 +0100 (CET)=20 >Message-Id: <3.0.6.32.20000113160436.00799440@mail.brussels2000.org> >Date: Thu, 13 Jan 2000 16:04:36 +0100 >To: test@brussels2000.org >From: eric hanuise >Subject: just a test >Mime-Version: 1.0 >Content-Type: text/plain; charset=3D"us-ascii" >Sender: owner-test@brussels2000.org >Precedence: bulk >Reply-To: test@brussels2000.org > >this is the test >------------------------------------------------------------------------= > Eric Hanuise - Brussels 2000 system administrator > ehanuise@brussels2000.org=20 > Tel. 02 214 20 50 Fax 02.214 20 20 > > Here's my alias definitions for that list : # liste test test: "|/usr/lib/majordomo/wrapper resend -l test -R test-list" test-list: :include:/var/lib/majordomo/lists/test # this was the plain 'no resend' definition. (worked OK) # test: :include:/var/lib/majordomo/lists/test owner-test: test-owner owner-test-list: owner-test test-request: "|/usr/lib/majordomo/wrapper request-answer -l test" owner-test-request: test-owner test-owner: ehanuise test-approval: ehanuise and here's the test.config file : (long # header removed as a courtesy ;-) # defined or used. # admin_passwd [word] (test.admin) # The password for handling administrative tasks on the list. admin_passwd =3D test.admin # administrivia [bool] (yes) # Look for administrative requests (e.g. subscribe/unsubscribe) and # forward them to the list maintainer instead of the list. administrivia =3D yes # advertise [regexp_array] (undef) # If the requestor email address matches one of these regexps, then # the list will be listed in the output of a lists command. Failure # to match any regexp excludes the list from the output. The # regexps under noadvertise override these regexps. advertise << END END # announcements [bool] (yes) # If set to yes, comings and goings to the list will be sent to the # list owner. These SUBSCRIBE/UNSUBSCRIBE event announcements are # informational only (no action is required), although it is highly # recommended that they be monitored to watch for list abuse. announcements =3D yes # approve_passwd [word] (test.pass) # Password to be used in the approved header to allow posting to # moderated list, or to bypass resend checks. approve_passwd =3D test.pass # archive_dir [absolute_dir] (undef) # The directory where the mailing list archive is kept. This item # does not currently work. Leave it blank. archive_dir =3D # comments [string_array] (undef) # Comment string that will be retained across config file rewrites. comments << END END # date_info [bool] (yes) # Put the last updated date for the info file at the top of the # info file rather than having it appended with an info command. # This is useful if the file is being looked at by some means other # than majordomo (e.g. finger). date_info =3D yes # date_intro [bool] (yes) # Put the last updated date for the intro file at the top of the # intro file rather than having it appended with an intro command. # This is useful if the file is being looked at by some means other # than majordomo (e.g. finger). date_intro =3D yes # debug [bool] (no) # Don't actually forward message, just go though the motions. debug =3D no # description [string] (undef) # Used as description for mailing list when replying to the lists # command. There is no quoting mechanism, and there is only room # for 50 or so characters. description =3D # digest_archive [absolute_dir] (undef) # The directory where the digest archive is kept. This item does # not currently work. Leave it blank. digest_archive =3D # digest_issue [integer] (1) # The issue number of the next issue digest_issue =3D 1 # digest_maxdays [integer] (undef) # automatically generate a new digest when the age of the oldest # article in the queue exceeds this number of days. digest_maxdays =3D # digest_maxlines [integer] (undef) # automatically generate a new digest when the size of the digest # exceeds this number of lines. digest_maxlines =3D # digest_name [string] (test) # The subject line for the digest. This string has the volume and # issue appended to it. digest_name =3D test # digest_rm_footer [word] (undef) # The value is the name of the list that applies the header and # footers to the messages that are received by digest. This allows # the list supplied headers and footers to be stripped before the # messages are included in the digest. This keyword is currently # non operative. digest_rm_footer =3D # digest_rm_fronter [word] (undef) # Works just like digest_rm_footer, except it removes the front # material. Just like digest_rm_footer, it is also non-operative. digest_rm_fronter =3D # digest_volume [integer] (1) # The current volume number digest_volume =3D 1 # digest_work_dir [absolute_dir] (undef) # The directory used as scratch space for digest. Don't change # this unless you know what you are doing digest_work_dir =3D # get_access [enum] (list) /open;closed;list/ # One of three values: open, list, closed. Open allows anyone # access to this command and closed completely disables the command # for everyone. List allows only list members access, or if # restrict_post is defined, only the addresses in those files are # allowed access. get_access =3D list # index_access [enum] (open) /open;closed;list/ # One of three values: open, list, closed. Open allows anyone # access to this command and closed completely disables the command # for everyone. List allows only list members access, or if # restrict_post is defined, only the addresses in those files are # allowed access. index_access =3D open # info_access [enum] (open) /open;closed;list/ # One of three values: open, list, closed. Open allows anyone # access to this command and closed completely disables the command # for everyone. List allows only list members access, or if # restrict_post is defined, only the addresses in those files are # allowed access. info_access =3D open # intro_access [enum] (list) /open;closed;list/ # One of three values: open, list, closed. Open allows anyone # access to this command and closed completely disables the command # for everyone. List allows only list members access, or if # restrict_post is defined, only the addresses in those files are # allowed access. intro_access =3D list # maxlength [integer] (40000) # The maximum size of an unapproved message in characters. When # used with digest, a new digest will be automatically generated if # the size of the digest exceeds this number of characters. maxlength =3D 40000 # message_footer [string_array] (undef) # Text to be appended at the end of all messages posted to the # list. The text is expanded before being used. The following # expansion tokens are defined: $LIST - the name of the current # list, $SENDER - the sender as taken from the from line, $VERSION, # the version of majordomo. If used in a digest, no expansion # tokens are provided message_footer << END END # message_fronter [string_array] (undef) # Text to be prepended to the beginning of all messages posted to # the list. The text is expanded before being used. The following # expansion tokens are defined: $LIST - the name of the current # list, $SENDER - the sender as taken from the from line, $VERSION, # the version of majordomo. If used in a digest, only the expansion # token _SUBJECTS_ is available, and it expands to the list of # message subjects in the digest message_fronter << END END # message_headers [string_array] (undef) # These headers will be appended to the headers of the posted # message. The text is expanded before being used. The following # expansion tokens are defined: $LIST - the name of the current # list, $SENDER - the sender as taken from the from line, $VERSION, # the version of majordomo. message_headers << END END # moderate [bool] (no) # If yes, all postings to the list must be approved by the # moderator. moderate =3D no # moderator [word] (undef) # Send bounces to moderator instead of owner- moderator =3D # mungedomain [bool] (no) # If set to yes, a different method is used to determine a matching # address. When set to yes, addresses of the form user@dom.ain.com # are considered equivalent to addresses of the form user@ain.com. # This allows a user to subscribe to a list using the domain # address rather than the address assigned to a particular machine # in the domain. This keyword affects the interpretation of # addresses for subscribe, unsubscribe, and all private options. mungedomain =3D no # noadvertise [regexp_array] (undef) # If the requestor name matches one of these regexps, then the list # will not be listed in the output of a lists command. Noadvertise # overrides advertise. noadvertise << END END # precedence [word] (bulk) # Put a precedence header with value into the outgoing # message. precedence =3D bulk # purge_received [bool] (no) # Remove all received lines before resending the message. purge_received =3D yes # reply_to [word] () # Put a reply-to header with value into the outgoing # message. If the token $SENDER is used, then the address of the # sender is used as the value of the reply-to header. This is the # value of the reply-to header for digest lists. reply_to =3D test@brussels2000.org # resend_host [word] (undef) # The host name that is appended to all address strings specified # for resend. resend_host =3D brussels2000.org # restrict_post [restrict_post] (undef) # If defined, only addresses listed in these files (colon or space # separated) can post to the mailing list. By default, these files # are relative to the lists directory. These files are also checked # when get_access, index_access, info_access, intro_access, # which_access, or who_access is set to 'list'. This is less useful # than it seems it should be since there is no way to create these # files if you do not have access to the machine running resend. # This mechanism will be replaced in a future version of # majordomo/resend. restrict_post =3D # sender [word] (owner-test) # The envelope and sender address for the resent mail. This string # has "@" and the value of resend_host appended to it to make a # complete address. For majordomo, it provides the sender address # for the welcome mail message generated as part of the subscribe # command. sender =3D owner-test # strip [bool] (yes) # When adding address to the list, strip off all comments etc, and # put just the raw address in the list file. In addition to the # keyword, if the file .strip exists, it is the same as # specifying a yes value. That yes value is overridden by the value # of this keyword. strip =3D yes # subject_prefix [word] (undef) # This word will be prefixed to the subject line, if it is not # already in the subject. The text is expanded before being used. # The following expansion tokens are defined: $LIST - the name of # the current list, $SENDER - the sender as taken from the from # line, $VERSION, the version of majordomo. subject_prefix =3D # subscribe_policy [enum] (open) /open;closed;auto;op # One of three values: open, closed, auto; plus an optional # modifier: '+confirm'. Open allows people to subscribe themselves # to the list. Auto allows anybody to subscribe anybody to the list # without maintainer approval. Closed requires maintainer approval # for all subscribe requests to the list. Adding '+confirm', ie, # 'open+confirm', will cause majordomo to send a reply back to the # subscriber which includes a authentication number which must be # sent back in with another subscribe command. subscribe_policy =3D open # taboo_body [regexp_array] (undef) # If any line of the body matches one of these regexps, then the # message will be bounced for review. taboo_body << END END # taboo_headers [regexp_array] (undef) # If any of the headers matches one of these regexps, then the # message will be bounced for review. taboo_headers << END END # unsubscribe_policy [enum] (open) /open;closed;auto/ # One of three values: open, closed, auto. Open allows people to # unsubscribe themselves from the list. Auto allows anybody to # unsubscribe anybody to the list without maintainer approval. The # existence of the file .auto is the same as specifying # the value auto. Closed requires maintainer approval for all # unsubscribe requests to the list. In addition to the keyword, if # the file .closed exists, it is the same as specifying # the value closed. The value of this keyword overrides the value # supplied by any existent files. unsubscribe_policy =3D open # welcome [bool] (yes) # If set to yes, a welcome message (and optional 'intro' file) will # be sent to the newly subscribed user. welcome =3D yes # which_access [enum] (open) /open;closed;list/ # One of three values: open, list, closed. Open allows anyone # access to this command and closed completely disables the command # for everyone. List allows only list members access, or if # restrict_post is defined, only the addresses in those files are # allowed access. which_access =3D open # who_access [enum] (open) /open;closed;list/ # One of three values: open, list, closed. Open allows anyone # access to this command and closed completely disables the command # for everyone. List allows only list members access, or if # restrict_post is defined, only the addresses in those files are # allowed access. who_access =3D open #[Last updated Mon Jan 10 16:52:56 2000] Any help is welcomed. I've tried looking for this in previous messages = here, but I yet have to learn how to efficiently use GREP and the greatcircle.com = archive ain't searchable so sorry if this has been asked before. Didn't find it in the FAQ though :) ------------------------------------------------------------------------ Eric Hanuise - Brussels 2000 system administrator ehanuise@brussels2000.org=20 Tel. 02 214 20 50 Fax 02.214 20 20 From majordomo-users-owner Sat Feb 5 15:15:30 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19599; Sat, 5 Feb 2000 11:03:36 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id LAA19587 for majordomo-users@greatcircle.com; Sat, 5 Feb 2000 11:03:31 -0800 (PST) Received: from barr.dsl.visi.com (barr.dsl.visi.com [209.98.142.216]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA20893 for ; Tue, 25 Jan 2000 08:27:22 -0800 (PST) Received: (from barr@localhost) by barr.dsl.visi.com (8.9.3/8.9.3) id KAA13652 for majordomo-users@greatcircle.com; Tue, 25 Jan 2000 10:40:25 -0600 Date: Tue, 25 Jan 2000 10:40:25 -0600 Message-Id: <200001251640.KAA13652@barr.dsl.visi.com> From: barr@visi.com (Dave Barr) To: majordomo-users@greatcircle.com Reply-To: barr@visi.com Subject: Majordomo Frequently Asked Questions Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Version: $Id: majordomo-faq.html,v 1.240 2000/01/25 16:37:09 barr Exp barr $ URL: http://www.visi.com/~barr/majordomo-faq.html Archive-Name: mail/majordomo-faq Posting-Frequency: monthly Note: Be sure to read the updated Section 2.1 below which explains how to address local security issues in majordomo if you're not running majordomo on a host with restricted logins. 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? + 1.7 - How can I access Majordomo via the Web? + 1.8 - Is Majordomo Y2K (Year 2000) compliant? 2. Problems setting up Majordomo + 2.1 - What are the proper permissions and ownership of all Majordomo files and directories? + 2.2 - I get a MAJORDOMO ABORT with "chown(...): Not owner" or ".. Operation not permitted" + 2.3 - I get "sh: wrapper: cannot execute" or "wrapper: permission denied" + 2.4 - I get "Unknown mailer error" when majordomo runs + 2.5 - I get an error "insecure usage" from the wrapper + 2.6 - I get "majordomo: No such file or directory" from the wrapper + 2.7 - I get an error "Can't locate majordomo.pl" + 2.8 - I told my majordomo.cf where to archive the list, why isn't it working? + 2.9 - config-test can't seem to find ctime.pl or resend can't find getopts.pl + 2.10 - A list is visible via lists, but can't subscribe or 'get' files + 2.11 - I get "sh: wrapper not available for sendmail programs" + 2.12 - I get "aliasing/forwarding loop broken" 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? How do I approve messages? + 3.11 - How do I set up a digested version of a list? + 3.12 - How do I setup virtual majordomo domains? + 3.13 - How can I stop people from using my mailing list to spam my subscribers? 4. Mailer and list administration 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? + 4.7 - Why is the Subject of my messages missing? + 4.8 - I'm getting mail from majordomo with "BOUNCE:" what do I do? How do I stop this? + 4.9 - My list configuration doesn't seem to be working. + 4.10 - How do I set it up so that the originator of a message doesn't get a copy of his/her own message back? + 4.11 - With Smail or Exim, users subscribing to a list sometimes get mail sent before they subscribed + 4.12 - Majordomo doesn't seem to work with sendmail 8.9 + 4.13 - I can't get Majordomo to work with RedHat Linux This FAQ is Copyright 1996 by David Barr and The Ohio 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.visi.com/~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@visi.com (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 maintenance. Once a list is set up, virtually all operations can be performed remotely, requiring no intervention upon the postmaster of the list site. See the main Majordomo web page at: http://www.greatcircle.com/majordomo/ 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 is recommended that you use the latest release of Perl that you can get. You can find it at http://www.perl.com/perl/. You must upgrade to version 1.94.3 in order for it to work with Perl 5.004, due to changes in regular expressions. Unfortunately, Majordomo does NOT work with Perl 5.005_01, due to a bug in Perl with respect to regular expressions. Use Perl 5.005_02 (or greater). While Majordomo is still compatible with Perl 4.036, future versions will likely be Perl 5 only. RedHat 5.2 is unfortunately shipping a prerelease version of Perl ("5.004m4") with some of their Linux distributions. This version is buggy and won't work with Majordomo (you will get "Unknown mailer error 9" errors). Download an install the 5.004 or 5.005 RPM instead, or download and updated RPM from updates.redhat.com. Many people have been having problems with Majordomo on DEC OSF/1 AXP systems. 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 haven't been recent reports in this area, so it's assumed that later versions also 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 could be made to 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. There is no known port of Majordomo to Windows NT, Win95 or Mac. For more information, see the comp.os.msdos.mail-news FAQ. At last check there was a port of an old version (1.93) to MS-DOS/Waffle, and an old version (1.93) ported to OS/2. These probably aren't all that helpful for anyone porting Majordomo to NT. 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 See other references throughout this FAQ for some further notes on using these packages. 1.2 - Where do I get Majordomo? Via the Web at: http://www.greatcircle.com/majordomo/ Via anonymous FTP at: ftp://ftp.greatcircle.com/pub/majordomo/ ftp://ftp.sgi.com/other/majordomo/ ftp://ftp.sgi.com/other/majordomo/ The current version is 1.94.5, released Jan 18 2000. It is a collection of bugfixes and minor changes. Be sure to read the INSTALL file carefully so you don't leave yourself vulnerable to a security hole in the "wrapper" program. 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). Majordomo 2 is currently being developed by Jason Tibbits. Currently it's "alpha" quality. Join the majordomo-workers list (see below) if you want to use this release. You can find out how to get Majordomo 2, as well as information about this release at http://www.hpc.uh.edu/majordomo/ 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 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, or download it from the Majordomo distribution. If you have permission problems unpacking the distribution, try using the 'o' flag to tar to ignore user/group information. Although Majordomo is written in Perl, it does have one component written in C that must be compiled. This 'wrapper' program runs "setuid" and ensures that all Majordomo functions operate with the proper permissions. You will need root access to install this program with the correct privileges. Majordomo interfaces to the mail system (sendmail, exim, etc) through aliases. Adding aliases is generally a root-bound process. However, on some systems the process can be delegated to a separate file under your control. Once you get past the above two requirements, it is possible to maintain Majordomo lists without root access. At best, your local sysadmin would only be bothered twice -- once for the installation, and once for designating a separate alias file for your use. Majordomo 1.x is designed to work with sendmail, however will work with other UNIX-based mailers. For more information on setting up Majordomo with other mailers, see the following pages: * qmail - ftp://ftp.eyrie.org/pub/software/majordomo/mjqmail * exim - http://www.netmaster.ca/exim/majordomo.html * Netscape Messaging Server 2.x and 3.x - http://interstroom.nl/docs/nsmajordomo * Cyrus IMAP - see "Sendmail can't mail to a file or pipe..." at http://andrew2.andrew.cmu.edu/cyrus/imapd/install-FAQ.html#sendmai l. This is necessary because Majordomo works by delivering mail via pipe. 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 when upgrading to 1.94 that you update your $mailer and $bounce_mailer variables in your majordomo.cf! There are 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? Please DO NOT ask the FAQ maintainer for help on Majordomo. I will accidentally delete your message. I'm sorry, I don't have time to do consulting on Majordomo. I am not a Majordomo help service. I, along with many others, do answer questions on the mailing lists. Let me say that about 90% of the answers I get are from the documentation or this FAQ. Many of the rest are answered by reading the source. It's really not that hard to figure out. The remainder of the questions I get are usually sendmail questions, which really should be asked in comp.mail.sendmail. 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. It's a good idea to search or browse the list archives below for the last couple months since many of the same questions are asked (and answered) regularly. There are searchable list archives (thanks to Jason Tibbitts) at http://www.hpc.uh.edu/majordomo-users/ and http://www.hpc.uh.edu/majordomo-workers/. 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, qmail, 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 the 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 it is probably not the most recent version. There is an FTP site for unofficial patches. See http://sol.ccsf.cc.ca.us/ftp/majordomo-patches/ . What's in it? Messages that are saved from the majordomo-users and -workers mailing lists. There are INDEX files in each part with one-line summaries of each patch, and a README file in the top directory with overall information. If you have patches that you think should be in the archive, you can FTP or email them in. The top-level README file tells how to do it. Please contribute -- to save other people the headaches you had. NOTE: The patches are NOT "official" patches approved by Chan Wilson or anyone else. Use your own judgment before (and after) you apply them. Nick Perry also has various patches for 1.94.3 at ftp://ftp.amulation.co.uk/pub/majordomo_patches/. They are patches which add various functions to majordomo. 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://docuspace.uchicago.edu/dpc/general/g_maj-adm.html. Look for a great book out now from O'Reilly and Associates called "Managing Mailing Lists", by Alan Schwartz. You can read my review of the book at http://www.visi.com/~barr/managing-maillist-review.html. I was one of the book's technical reviewers. You can order the book at a discount (currently 20%) from amazon.com via the web: * http://www.amazon.com/exec/obidos/ASIN/156592259X/greatcircleassoc Besides getting you the book at a discounted price, using this link earns Great Circle Associates a small commission, which helps pay for their support of the majordomo and list-managers mailing lists, as well as distributing majordomo on their FTP site. 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. http://www.faqs.org/faqs/mail/list-admin/software-faq. Contact naleks@library.ummed.edu (Norm Aleks) for more information. 1.7 - How can I access Majordomo via the Web? There are various Web interfaces to Majordomo available. Some are management interfaces for list maintenance, and some are interfaces for list archives (some do searching too). * LWGate - http://www.netspace.org/users/dwb/lwgate.html * Regan's - http://www.peak.org/peak_info/mlists/Majordomo.html * MajorCool - http://ncrinfo.ncr.com/pub/contrib/unix/MajorCool/ Link dead.. it looks like it's supposed to be moved to http://www.ncr.com/pub/software/MajorCool/. * MailServ - http://www.csicop.org/~fitz/www/mailserv/ * Pandora - http://www.ed.umuc.edu/pandora/ * Maitre-d - http://www.landw.com/wps/content2.htm#ch12 * Marcos' - http://www.inf.utfsm.cl/~marcos/majordomo/www.html * ListTool - http://www.listtool.com/ * Wilma (a list archive interface) - ftp://sol.ccsf.cc.ca.us/majordomo-contrib/ * ListQuest ( a list archive and search interface) - http://lq.corenetworks.com/ 1.8 - Is Majordomo Y2K (Year 2000) compliant? The current release of Majordomo has no known year 2000 issues. Older versions had problems only if you used the "archive" program to maintain list archives, since it used only a 2-digit year. If you use the new 4-digit year flags to archive you should not have any year 2000 problems. No one has officially certified Majordomo to be Y2K compliant, and I don't foresee anyone paying money to do so, so don't go looking for someone to sue if it breaks. All we are saying is that we know of no year 2000 issues with Majordomo. That being said, as you can see by reading the Majordomo source, except for the "archive" program majordomo doesn't directly deal with dates so it's extremely unlikely there are any year 2000 issues. Even places where it does use dates (archive) it doesn't do any date comparisons, which is the crux of all non-cosmetic year 2000 bugs. At worst "archive" would overwrite your 100-year-old mailing list archives. I really really doubt Majordomo will still be used for 100 years. _________________________________________________________________ Section 2: Problems setting up Majordomo 2.1 - What are the proper permissions and ownership of all Majordomo files and directories? If you are running Majordomo on a host which allows logins by untrusted users, see the paragraph Wrapper security!" below. 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 it 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.3 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 (See the paragraph in Section 2.1 called Wrapper security!). 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' to 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. (otherwise sendmail 8.x will probably give "X-Authentication-Warning:"'s) Because Majordomo does not run with any "special" (root) privileges, 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 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 non-POSIX: SunOS 4.x, Ultrix, most BSD 4.2 and 4.3-based systems. POSIX systems include: Solaris 2.x, IRIX 5.x, BSDI (and 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. Wrapper security! If you are running Majordomo on a host which allows untrusted logins, you will need to restrict who can run the "wrapper" program. By default (as explained above) the wrapper can be run by "anyone" (that is, it has other execute permission). Because the wrapper program runs programs as majordomo, and because majordomo programs (such as "resend") allow loading of arbitrary configuration files (which are simply perl scripts), it's trivially possible to run arbitrary commands as the majordomo user. Again, this is an issue only to local users on the system -- if you don't have untrusted local users (i.e. only administrators can log into your mail server), then this is not an issue to worry about. To close down this hole, change the permissions of the Majordomo home directory to mode 750. (this is what is recommended in the INSTALL file) This will prevent the access by local users to the setuid wrapper script (which lives inside this directory). To make this work, you must make sure the group ownership of the home directory is the same as the gid your mailer runs as (for sendmail, this is "daemon"). Otherwise, sendmail will be unable to read your list subscription files (the files that you :include: in your alias file). Closing down the majordomo home directory has the added benefit that local users will be unable to read your list subscription files, bypassing any privacy restrictions you may have set in majordomo. The downside of closing the majordomo home directory is that it makes it harder to do local administration, and also to properly run "./wrapper config-test" to check your configuration (since you need to run it as a non-root, non-majordom user, and such a user won't have access to the home directory). 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 if you don't use "daemon" as your majordomo group -- see 2.3below.). 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" writable (770 or 775). 2.2 - I get a MAJORDOMO ABORT with "chown(...): Not owner" or ".. Operation not permitted" Most likely your wrapper is not installed correctly. Re-check the Makefile and see if the wrapper was compiled with the right UID and GID. See the README and the above section on how to set the permissions correctly. Make sure after you fix the wrapper that you remove (or rename) any "listname.new" or "L.listname" files found in your lists directory. These will likely have the wrong ownerships, and will cause you problems. You should have seen an error if you ran "./wrapper config-test" as a non-root, non-majordom user. If not, it's a bug in config-test and should be fixed. 2.3 - I get "sh: wrapper: cannot execute" or "wrapper: permission denied" Your mailer doesn't have permission to execute the wrapper. Usually this is the result of too-strict permissions on either the Majordomo home directory or the wrapper executable. See Section 2.1 and especially the paragraph on wrapper security for the correct permissions on all majordomo directories and programs. 2.4 - I get "Unknown mailer error" when majordomo runs First, see Question 4.13 if you are running RedHat 5.2 and are getting "Unknown mailer error 9". 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 usually see some sort of error message. If you just get a return code, check the Majordomo README for further explanation on sendmail return codes. If you get "Unknown mailer error XX" where XX is less than 255, look for the error in /usr/include/errno.h . Otherwise, see the README. See section 1.1 above for what versions of Perl won't work with Majordomo. [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.5 - 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: majordomo: |"/path/to/majordomo/wrapper majordomo" 2.6 - 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.7 - 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.8 - 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 retrieved 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.9 - config-test can't seem to find ctime.pl or resend can't find getopts.pl ctime.pl and getopts.pl are 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.10 - 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.11 - I get "sh: wrapper not available for sendmail programs" You're on a system which uses smrsh. (sendmail restricted shell). You have to configure smrsh to allow it to execute the wrapper. Normally this is done by creating a symlink in /var/adm/sm.bin (in some it's /etc/smrsh) to Majordomo's wrapper program. 2.12 - I get "aliasing/forwarding loop broken" [ Reported by Wade Williams ] Some people have noted sendmail will generate a bounce message if you send to a list, but the list file is empty (there are no subscribers). Add a subscriber to the list and the error should go away. You will also get this error if the permissions on the list file for that list in the lists directory are too strict. If the list directory or list file is not readable by sendmail, you will also get the error "Cannot open /path/to/lists/listname: Permission denied". See Section 2.1 above for the full discussion of how to correctly set permissions on directories and files within Majordomo. _________________________________________________________________ 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" variable in the list 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. (This address is what gets copied into 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 in the bounce process. 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 most of majordomo's other features like moderating, administrivia checks, and others. 3.2 - Semi-automated handling of bounced mail This is not true automation of bounced mail. What this does is the next best thing. You unsubscribe the user from the list, but add the user to a special 'bounces' list (there's a perl script in the distribution called bounce you run to make this easier) 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). There's no facility for automatically detecting what addresses are failing. You have to determine that based on the bounce messages you receive from other sites. [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. The most important reason why Reply-To: to the list is bad is that it can cause mail loops if any of the members of your list are running fairly-common but broken software which doesn't know what an envelope address is. (Many Microsoft products, as well as many other PC-based non-SMTP/Internet mail systems which work through an SMTP gateway.) You should read the following FAQ on why you shouldn't set the Reply-To: field. http://www.unicom.com/pw/reply-to-harmful.html If you are using resend, use the 'reply_to' configuration variable in the list .config file. 3.5 - How can I hide lists so they can't be viewed by 'lists'? That is what advertise and noadvertise are for. These two variables 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 variable in the config file. Just set it to the filename that holds the list of subscribers, which is just simply the name of the list. ("restrict-post = listname"). However, there is an issue to keep in mind. 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. (That means don't use something easy to guess like "-outgoing" or "-list"). Next, you need to make it such that people can't find out what your -outgoing alias is. You can use the "@filename" directive of resend. Put the all the normal command-line options of resend into a file readable only by the majordomo user/group. Then the alias for the list simply becomes ".../resend @/path/to/filename". 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. This doesn't prevent a user reading the local /etc/aliases file (if they can), however. Another approach is to simply disable EXPN or VRFY altogether. See the documentation for your mailer on how to do this. In sendmail this is done by adding "noexpn" to the "O PrivacyOptions=" line in your sendmail.cf (multiple options are separated with a comma). However this doesn't prevent a local user reading the aliases file. This isn't generally a problem if your mail server is restricted to staff only users. Unfortunately, Sendmail 8.x will log your -outgoing alias in the "Received:" lines. To prevent 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-seekrit,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 comma). Otherwise sendmail will set the envelope address of outgoing mail to contain your secret outgoing alias. Again if you're using the @filename directive, the entire command line is simply put into the specified file (starting with "-h foo.org ...". Here's another creative idea from matt@primefactor.com (Matt Perry): I've had a report that this no longer works with sendmail 8.9.1, but that it does work with 8.9.3. Sendmail allows you to rewrite incoming and outgoing addresses. The one that handles incoming is virtualusertable.text. For a list called test with the test-outgoing alias, I put the following into my virtualusertable.text file and remade the db with the appropriate command: test-outgoing@mydomain.com error:nouser User unknown Sendmail can still get to the alias and expand it into the list of recipients. However, any mail that appears at port 25 marked for test-outgoing@mydomain.com will bounce back with "User unknown". Finally it should be noted that it is impossible with any of these methods above to prevent people from forging mail as someone who is subscribed to the list, and sending to the list that way. Of course a spammer can also subscribe to the list legitimately and then send spam. The restrict_post option blocks the vast majority of problems, however. 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. This is also a "backup password" in case the .config file gets corrupted. 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? How do I approve messages? First, you need to tell Majordomo that the list is moderated. In the configuration file for the list, you set "moderate = 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, automates this for you. Whenever you get a message which needs approval, from your mail reader pipe the message through "approve". The password for each list needs to be put in your .majordomo file. Read the "approve" script for more information. 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, and then the entire contents of the original message. (meaning there should not be a blank line before and after the "Approved:" line.). Don't forget to edit out the headers which were added by the bounce process. For example: To: your-list@example.com Subject: doesn't matter Approved: your-approval-password Received: by some.site.org.... Received: by another.site.org.... From: joe@another.com (Joe User) Subject: this list is great! To: your-list@example.com Hey, this list is great, and the moderator sure is sexy! Joe It's also possible, if your mailer allows it, to approve a message another way by just inserting an Approved: header in the original body and passing the original message on without adding your own header. This is in a sense "forging" mail, so many mailers either won't allow it or will insert some sort of authentication warning. This form is used most often by moderators when they send mail to the list and don't want to go and approve their own message again. Here's an example: To: your-list@example.com Approved: your-approval-password Subject: Thanks! I like this list too, but sorry, I'm married! :-) -- your moderator Note that this requires a mail-user-agent (MUA) that allows one to add headers to a message. If your MUA doesn't let you do this, you'll need to use the first method. Note that in either case the "Approved:" line will be stripped out by Majordomo before it gets sent to the list, so the list members won't see your list password. 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, Anthony Baratta, 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. Create separate list directories for each virtual domain. http://www.sendmail.org/virtual-hosting.html first. See also the Sendmail FAQ there. Virtual domain stuff (in your virtusertable): #Domain 1 majordomo@domain1.com majordomo-1 majordomo-owner@domain1.com user ListOne@domain1.com ListOne ListOne-owner@domain1.com user owner-ListOne@domain1.com user ListOne-request@domain1.com ListOne-request @domain1.com user #Domain 2 majordomo@domain2.com majordomo-2 majordomo-owner@domain2.com user ListTwo@domain2.com ListTwo ListTwo-owner@domain2.com user owner-ListTwo@domain2.com user ListOne-request@domain2.com ListTwo-request @domain2.com user Don't forget to run 'makemap hash /etc/virtusertable < /etc/virtusertable'. Substitute "hash" for whatever database you wish to use (some vendor sendmail's don't support hash, but do support dbm). It's suggested to have separate alias files for each virtual domain. You can configure sendmail to have multiple alias files. Here's how the aliases will look: #MajorDomo Aliases ## System Info majordomo-1: "|/usr/local/majordomo/wrapper majordomo -C /usr/local/majordomo/ majordomo-1.cf" majordomo-2: "|/usr/local/majordomo/wrapper majordomo -C /usr/local/majordomo/ majordomo-2.cf" #Domain 1 ListOne: "|/usr/local/majordomo/wrapper resend -l ListOne -C /usr/local/major domo/majordomo-domain1.cf ListOne-OutGoing" ListOne-OutGoing: :include:/usr/local/majordomo/lists-domain1/listone ListOne-request: "|/usr/local/majordomo/wrapper majordomo -l ListOne -C /usr/lo cal/majordomo/majordomo-domain1.cf" #Domain 2 ListTwo: "|/usr/local/majordomo/wrapper resend -l Listtwo -C /usr/local/major domo/majordomo-domain2.cf ListTwo-OutGoing" ListTwo-OutGoing: :include:/usr/local/majordomo/lists-domain1/listtwo ListTwo-request: "|/usr/local/majordomo/wrapper majordomo -l ListTwo -C /usr/lo cal/majordomo/majordomo-domain2.cf" 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 virtual aliases. Check out http://o2.towery.com/~ernestm/admin/majordomo/majorvirt.html also for good instructions on configuring virtual domains with Majordomo. 3.13 - How can I stop people from using my mailing list to spam my subscribers? [From mcr@solidum.com (Michael Richardson) ] There are two approaches to solving spam. They are complementary. The most general solution is to make sure that your list host will not accept spam. See http://spam.abuse.net/ for extensive recipes on this. The majordomo specific way is to use the "restrict_post" mechanism to disallow posts from addresses that are not on the list. Please see section 3.6 for some of the pitfalls of using restrict_post. They all apply. My experience is that spammers have not yet learnt about the "-outgoing" alias, and the techniques in section 3.6 would apply when they do. The major objection to using restrict_post to deflect spam is that it may deflect posts from legitimate people -- people who've subscribed with one address but are posting from another address. It may also restrict cross-posts from other lists, or from people who read the list via news. The solution to the above objections is twofold: 1. the moderator must forward legitimate posts. This can be a pain, but it does work. 2. the restrict_post header can be extended. The typical way to do #2 is to set restrict_post to: mylist:mylist-nomail Then, create a configuration file and password for "mylist-nomail", but DO NOT create any aliases. (If you use something like mj_build_aliases, then don't set the owner) The moderator, or subscribers may then subscribe themselves to this second list. Subscribers to the -nomail list will then be allowed to post to the first list, but won't receive duplicate copies of the first list. _________________________________________________________________ Section 4: Mailer and list administration problems 4.1 - Address with blanks are being treated separately If a subscriber to the list is John Doe < jdoe@node.com> it gets treated these as the three addresses: John Doe < jdoe@node.com> [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 often 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 ftp://ftp.isc.org/isc/inn/contrib/. Installation instructions are straightforward, it provides sample entries 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 towards 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 has met with varying success. Exim can also be used (see http://www.exim.org/). qmail has been used with majordomo, and performance with either Exim or qmail I'm told generally will well exceed that of sendmail. At least qmail also is written in a far more secure way than sendmail (some would say paranoid). See http://www.qmail.org. The qmail site includes at least one way to get majordomo to work with qmail. Note that it is possible to get majordomo working under qmail without using the 'wrapper', which is a nice idea. Some majordomo-under-qmail solutions just involve qmail's sendmail emulation feature. For more info, see the Using Majordomo with qmail FAQ, written by Russ Allbery. If you are using Exim instead of sendmail there are more things you can do. Instead of concealing the -outgoing addresses, it is possible to configure Exim so that those addresses are only usable by the local majordomo user. A description of how to do that can be found at http://www.netmaster.ca/exim/majordomo.html as well as other information about configuring majordomo with Exim. 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 list configuration file if you don't upgrade to 1.3 or higher. TLB is another package which is like bulk_mailer, but has other features. You can get it from ftp://ftp.hpc.uh.edu/pub/tlb/. The advantage of TLB is its greater configuration flexibility, and also the fact that it's possible with TLB to eliminate the -outgoing address, making configuration easier and lists more secure. 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 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) { This is fixed in Majordomo 1.94.1 and higher. 4.7 - Why is the Subject of my messages missing? [from Dave Wolfe] But it's not. Oh, you probably mean "Why is the subject line of messages to my moderated list blank?" Because you didn't include any headers after the Approved: header in the body of the messages. Or you deleted them when you approved the bounced messages. When resend finds an Approved: header in the first line of the body, it throws away all the headers it's collected for the message and looks for more headers following the Approved: header (which is the format of a bounced message). So if you put the Approved: header in an original message (as opposed to a bounced message), you have to also fill in some headers to be sent out, such as Subject:, To:, and From:. See section Question 3.10 on how to approve messages to moderated lists. This is also explained in Doc/list-owner-info, which should be sent to all list owners and moderators. 4.8 - I'm getting mail from majordomo with "BOUNCE:" what do I do? How do I stop this? Whenever majordomo encounters mail to the list which it sees a problem with, it forwards it to person at the approval address to deal with manually. There are lots of reasons Majordomo does this. Majordomo will tell you why in the Subject of the message. Here's a list of the most common bounce reasons: An "Admin request" bounce means that the list is configured to filter out what it thinks are "administrivia" messages, and it thought that message was one. These are messages such as "subscribe" or "unsubscribe" or "help", which get sent to the list instead of majordomo. Lists generally have this turned on by default. If you don't like it, set "administrivia=no" in the list config file. If that doesn't work, check your aliases to make sure the "-s" option to resend isn't being used on that list. An "Approval required" bounce means that the list is moderated, and the message needs to be approved. (see section 3.10 of this FAQ) A "Message too long" bounce means that the message was longer than the "maxlength" setting in the list config file. If you get any of these bounces messages and you think the mail is OK to send to the list, you'll need to approve it. See the file Doc/list-owner-info on the correct procedure(s) for approving mail with Majordomo. It's also covered in section 3.10 of this FAQ. 4.9 - My list configuration doesn't seem to be working. If you changed your list configuration and the list doesn't seem to be behaving any differently, make sure that the list is being sent through "resend". See the installation documentation and section 3.1 of this FAQ on how to set up the aliases for the list correctly to pipe mail through "resend". Other things to check would be that the arguments to "resend" are only "-h", and "-l" (and perhaps "-C" if you use virtual domains). resend used to be configured with other command line flags to do things such as have moderated lists. However these flags override any config file settings, so remove them if they are present. All configuration should be done now through the config file. 4.10 - How do I set it up so that the originator of a message doesn't get a copy of his/her own message back? You can't. Sorry. The "metoo" setting in sendmail has no effect after a message is piped through an external program. Unless you're willing to give up piping messages through "resend", there's no way to stop this. 4.11 - With Smail or Exim, users subscribing to a list sometimes get mail sent before they subscribed [from Lazlo Nibble and Philip Hazel] This is due to the way Smail and Exim deliver mail. With sendmail, it expands its delivery list when the mail first arrives. If the list gets changed, the message will still get delivered to the original recipient list, since the original list is never referred to again. As sendmail delivers mail, it removes addresses from its expanded list as they get delivered. However Smail and Exim don't expand the list when the message is first queued. Instead as they go through the queue of pending messages to deliver, and maintain state on what addresses they have successfully delivered mail to and compare that with the current list contents. As long as the message is queued waiting for one or more addresses in the list, it will get sent to any new recipients whenever the queue gets processed next. This is rather unexpected for those used to sendmail's behavior. The advantage of smail and exim's approach is that if an address in your list is unreachable (or has a bad .forward file), you can change the list contents (or the .forward file) and the message will be delivered to the new address when the queue next gets processed. It won't deliver to the old, bad address. There really isn't an easy solution to this, but it's really not a serious problem. 4.12 - Majordomo doesn't seem to work with sendmail 8.9 The new security features of sendmail don't allow :include: directories to be group writable. Unfortunately, by default these directories are group writable with Majordomo. If you have this problem you will see errors from sendmail like "Cannot open /path/name: Group writable directory" and "aliasing/forwarding loop broken". One solution is to add: O DontBlameSendmail=groupwritabledirpathsafe in your sendmail.cf and restart sendmail. The other method (and generally the recommended one) is to remove the group-write bit on the lists directory and any list files. Make sure also any parent directories to not have the group or other write bit set. If Majordomo is working correctly having group write permission is not necessary. However, some people find it convenient to have group-write access so users can be put in the majordomo group and not need root access all the time to work on majordomo. 4.13 - I can't get Majordomo to work with RedHat Linux If you are trying to use the Majordomo RPM, it is broken. The majordomo.cf which comes with the RPM has the line $whereami = `hostname`; This is broken for two reasons. First, the hostname may not necessarily be a fully-qualified domain name, and thus this won't generate a valid Internet email address. Secondly, using `hostname` generates a linefeed character at the end, which totally screws things up, and you end up getting blank lines in headers (and you'll start to see headers appear in the body of the message). The solution is to edit the line and put in your correct host name or mail domain. A bug report has been filed with RedHat. RedHat 5.2 also ships with an interim (buggy) release of Perl, which does not work with Majordomo. (you will get "Unknown mailer error 9" errors). Download and install the updated Perl RPM from ftp://updates.redhat.com/. From majordomo-users-owner Sat Feb 5 17:08:57 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA23246; Sat, 5 Feb 2000 17:03:21 -0800 (PST) Received: from pali.cps.cmich.edu (pali.cps.cmich.edu [141.209.131.81]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA23239 for ; Sat, 5 Feb 2000 17:03:14 -0800 (PST) Received: (from ishwar@localhost) by pali.cps.cmich.edu (8.9.2/8.9.1) id UAA08203; Sat, 5 Feb 2000 20:18:13 -0500 (EST) (envelope-from ishwar) Date: Sat, 5 Feb 2000 20:18:13 -0500 (EST) From: Ish Rattan Message-Id: <200002060118.UAA08203@pali.cps.cmich.edu> To: majordomo-users@GreatCircle.COM, norio@okmicro.co.jp Subject: Re: install problem In-Reply-To: <3897D0FF.3B71887C@okmicro.co.jp> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > From: Norio Ohki > > ----- Transcript of session follows ----- > 550 :include:/usr/local/majordomo-1.94.3/lists/abt... Cannot open All directoires in the path must have permissions 755. - ishwar From majordomo-users-owner Sat Feb 5 18:38:07 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA24258; Sat, 5 Feb 2000 18:32:33 -0800 (PST) Received: from usinter.net (mail.usinter.net [206.171.66.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA24231 for ; Sat, 5 Feb 2000 18:32:23 -0800 (PST) Received: from usinter.net [209.85.130.137] by usinter.net [206.171.66.25] with SMTP (MDaemon.v2.8.7.0.R) for ; Sat, 05 Feb 2000 18:47:14 -0800 Message-ID: <389CE01C.D52196FD@usinter.net> Date: Sat, 05 Feb 2000 18:44:44 -0800 From: "Todd A. Lyons" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Re: install problem References: <3897D0FF.3B71887C@okmicro.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: majordomo-users@GreatCircle.COM X-Return-Path: cannonball@usinter.net Reply-To: cannonball@usinter.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Norio Ohki wrote: > :include:/usr/local/majordomo-1.94.3/lists/abt > I tried to modify permissions of directory and files, in vain. > What should I check settings? Any advice will be appreciated. It's Saturday and your message just popped up, but I wanted to let you know that you weren't alone. It took me a couple of hours to figure this one out. -----From the sendmail 8.9 FAQ Question 3.32: Now the differences that make this work that may not be the same as instructed by the majordomo instructions: 1) Put the majordomo.aliases file in /etc, not in the majordomo install directory. 2) Make the permissions on /usr/local/majordomo 0751, not 0775. 3) Make the permissions on /usr/local/majordomo/Log 0664, owned by majordomo, group majordomo. 4) /usr/local/majordomo/lists is mode 0755, owner majordomo, group majordomo 5) The permissions owners for the lists should be 0755 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/ 0664 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/abt 0660 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/abt.config 0664 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/abt.info ------End quote The only difference between sendmail's recommendation and my working system are that I have all groups set to daemon (ie majordomo.daemon) -- Blue skies... Cannonball * One ring to rule them all, One ring to find them * * One ring to bring them all, and in the darkness bind them * Sauron From majordomo-users-owner Sat Feb 5 21:53:05 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA26207; Sat, 5 Feb 2000 21:50:48 -0800 (PST) Received: from mail.okmicro.co.jp (ns.okmicro.co.jp [210.169.238.98]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA26200 for ; Sat, 5 Feb 2000 21:50:40 -0800 (PST) Received: from okmicro.co.jp ([192.168.111.31]) by mail.okmicro.co.jp (8.9.1/3.6W) with ESMTP id PAA21224; Sun, 6 Feb 2000 15:05:33 +0900 (JST) Message-ID: <389D0F05.6F501BD9@okmicro.co.jp> Date: Sun, 06 Feb 2000 15:04:53 +0900 From: Norio Ohki Organization: OK Microsystems X-Mailer: Mozilla 4.7 [ja] (Win98; I) X-Accept-Language: ja MIME-Version: 1.0 To: Ish Rattan CC: majordomo-users@GreatCircle.COM Subject: Re: install problem References: <200002060118.UAA08203@pali.cps.cmich.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Ishwar, thanks for the responses and advice's. I found solution in latest FAQ on the web site which say sendmail8.9 requests no grup-writable permission and to put option in sendmail.cf. By this alteration, I'm successfully operating the list. Thanks again for your taking your time for me. Regards, Norio Ish Rattan wrote: > > > From: Norio Ohki > > > > ----- Transcript of session follows ----- > > 550 :include:/usr/local/majordomo-1.94.3/lists/abt... Cannot open > All directoires in the path must have permissions 755. > > - ishwar From majordomo-users-owner Sat Feb 5 22:53:06 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA26775; Sat, 5 Feb 2000 22:49:50 -0800 (PST) Received: from server1.mich.com (server1.mich.com [198.108.16.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA26768 for ; Sat, 5 Feb 2000 22:49:43 -0800 (PST) Received: from lindy.nuge.com (root@pm012-006.dialip.mich.com [207.75.116.166]) by server1.mich.com (8.9.3/8.9.3) with ESMTP id CAA11109; Sun, 6 Feb 2000 02:04:18 -0500 Received: from localhost (rtg@localhost) by lindy.nuge.com (8.9.3/8.9.3) with ESMTP id CAA13224; Sun, 6 Feb 2000 02:04:15 -0500 X-Authentication-Warning: lindy.nuge.com: rtg owned process doing -bs Date: Sun, 6 Feb 2000 02:04:14 -0500 (EST) From: Rick Green To: Robert Ellis cc: Majordomo-Users@GreatCircle.COM Subject: Re: message_footer is intermittent 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, 26 Jan 2000, Robert Ellis wrote: > We have a mailing list that includes a message_footer. > When some users mail to it, the footer is included in their message. > When other users mail to it, the footer is not. > > Does anyone have a guess why the footer is sometimes omitted? > I would guess that those messsages where the footer appears to be omitted, were sent by the posters as mime-encoded. Since majordomo (1.94.x) is not mime-aware, the footer is appended at the end of the message, not inserted at the end of the text part of the message. -- Rick Green From majordomo-users-owner Sun Feb 6 12:45:00 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA07358; Sun, 6 Feb 2000 12:28:04 -0800 (PST) Received: from limerence.net (northwood-156-168.reshall.umich.edu [141.213.156.168]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA07351 for ; Sun, 6 Feb 2000 12:27:57 -0800 (PST) Received: from northwood (hate.limerence.net [141.213.156.167]) by limerence.net (8.9.3/8.9.3) with SMTP id DAA08676 for ; Sun, 6 Feb 2000 03:47:36 -0500 From: "Sandoz" To: Subject: abort message (mj_resend) Date: Sun, 6 Feb 2000 15:45:57 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.100 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk hi, i would appreciate it if someone could help: When sending mail to my list, I get the following abort message in return: MAJORDOMO ABORT (mj_resend)!! shlock: '/home/majordomo/lists' is not writable by UID 8 GID 12 when I make the directory available to uid 8 (mail) by changing permissions, I get: The original message was received at Sun, 6 Feb 2000 02:42:34 -0500 from mail@localhost ----- The following addresses had permanent fatal errors ----- pod-imm-outgoing :include:/home/majordomo/lists/pod-imm (expanded from: pod-imm-outgoing) ----- Transcript of session follows ----- 550 :include:/home/majordomo/lists/pod-imm... Cannot open /home/majordomo/lists/pod-imm: World writable directory Message delivered to mailing list pod-imm-outgoing 554 pod-imm-outgoing... aliasing/forwarding loop broken It's kind of like a catch22... --John From majordomo-users-owner Sun Feb 6 16:59:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA09902; Sun, 6 Feb 2000 16:48:02 -0800 (PST) Received: from mailmsgone.thenew.net (smtp.thenew.net [207.245.252.177]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA09895 for ; Sun, 6 Feb 2000 16:47:57 -0800 (PST) Received: from [209.112.15.113] by mailmsgone.thenew.net (NTMail 4.20.0009/NU7668.00.391cc02b) with ESMTP id ooehcaaa for ; Sun, 6 Feb 2000 19:57:29 -0500 Message-Id: <3.0.6.32.20000206202328.0080e3e0@mail.thenew.net> X-Sender: atscott@mail.thenew.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 06 Feb 2000 20:23:28 -0500 To: majordomo-users@GreatCircle.COM From: Andrew Scott Subject: Address/Name problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm still trying to set up my majordomo list after Esosoft got out of the business! Anyway, here's my problem I am now having: I want to list names along with addresses in the subscription list. However, for some reason, when the mail goes out, extra < > 's are added, and creates an invalid email address. For example, I have subscribed myself as follows: "Andrew Scott" This always worked in the past. But now, I get an error message as follows: --------------------------------------------- <"Andrew Scott" >: Sorry, I couldn't find any host named thenew.net>. (#5.1.2) --------------------------------------------- It appears as though an extra set of <> are being added. What is causing this, and how can we rectify it? Note, when I subscribe myself just as atscott@thenew.net then there are now problems. I have also tried the following: 1. I have tried it without the quote marks around the name 2. Without the < > marks around the address 3. With the name after the address 4. With neither quote marks, nor < > marks None of these work. Thanks! From majordomo-users-owner Sun Feb 6 19:24:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA11015; Sun, 6 Feb 2000 19:10:21 -0800 (PST) Received: from mail.okmicro.co.jp (ns.okmicro.co.jp [210.169.238.98]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA11008 for ; Sun, 6 Feb 2000 19:10:14 -0800 (PST) Received: from okmicro.co.jp ([192.168.111.31]) by mail.okmicro.co.jp (8.9.1/3.6W) with ESMTP id MAA22116; Mon, 7 Feb 2000 12:25:16 +0900 (JST) Message-ID: <389E3AF9.755BAE10@okmicro.co.jp> Date: Mon, 07 Feb 2000 12:24:41 +0900 From: Norio Ohki Organization: OK Microsystems X-Mailer: Mozilla 4.7 [ja] (Win98; I) X-Accept-Language: ja MIME-Version: 1.0 To: Sandoz CC: majordomo-users@greatcircle.com Subject: Re: abort message (mj_resend) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Sandoz, if I could mention about your second case, I've just experienced same thing. Recently posted faq will be helpful, if your server is using sendmail8.9*. I could successfully fix it. Norio >From FAQ posted by Dave Barr. ---------------------------------------------------------------------- 4.12 - Majordomo doesn't seem to work with sendmail 8.9 The new security features of sendmail don't allow :include: directories to be group writable. Unfortunately, by default these directories are group writable with Majordomo. If you have this problem you will see errors from sendmail like "Cannot open /path/name: Group writable directory" and "aliasing/forwarding loop broken". One solution is to add: O DontBlameSendmail=groupwritabledirpathsafe in your sendmail.cf and restart sendmail. The other method (and generally the recommended one) is to remove the group-write bit on the lists directory and any list files. Make sure also any parent directories to not have the group or other write bit set. If Majordomo is working correctly having group write permission is not necessary. However, some people find it convenient to have group-write access so users can be put in the majordomo group and not need root access all the time to work on majordomo. ------------------------------------------------------------------------ Sandoz wrote: > > hi, i would appreciate it if someone could help: > > When sending mail to my list, I get the following abort message in return: > > MAJORDOMO ABORT (mj_resend)!! > > shlock: '/home/majordomo/lists' is not writable by UID 8 GID 12 > > when I make the directory available to uid 8 (mail) by changing permissions, > I get: > > The original message was received at Sun, 6 Feb 2000 02:42:34 -0500 > from mail@localhost > > ----- The following addresses had permanent fatal errors ----- > pod-imm-outgoing > :include:/home/majordomo/lists/pod-imm > (expanded from: pod-imm-outgoing) > > ----- Transcript of session follows ----- > 550 :include:/home/majordomo/lists/pod-imm... Cannot open > /home/majordomo/lists/pod-imm: World writable directory > Message delivered to mailing list pod-imm-outgoing > 554 pod-imm-outgoing... aliasing/forwarding loop broken > > It's kind of like a catch22... > > --John From majordomo-users-owner Sun Feb 6 19:39:32 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA11193; Sun, 6 Feb 2000 19:32:11 -0800 (PST) Received: from mailmsgone.thenew.net (smtp.thenew.net [207.245.252.177]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA11185 for ; Sun, 6 Feb 2000 19:32:05 -0800 (PST) Received: from [209.112.15.68] by mailmsgone.thenew.net (NTMail 4.20.0009/NU7668.00.391cc02b) with ESMTP id wgfhcaaa for ; Sun, 6 Feb 2000 22:41:34 -0500 Message-Id: <3.0.6.32.20000206230731.00829c80@mail.thenew.net> X-Sender: atscott@mail.thenew.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 06 Feb 2000 23:07:31 -0500 To: majordomo-users@GreatCircle.COM From: Andrew Scott Subject: Address/Name problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm still trying to set up my majordomo list after Esosoft got out of the business! Anyway, here's my problem I am now having: I want to list names along with addresses in the subscription list. However, for some reason, when the mail goes out, extra < > 's are added, and creates an invalid email address. For example, I have subscribed myself as follows: "Andrew Scott" This always worked in the past. But now, I get an error message as follows: --------------------------------------------- <"Andrew Scott" >: Sorry, I couldn't find any host named thenew.net>. (#5.1.2) --------------------------------------------- It appears as though an extra set of <> are being added. What is causing this, and how can we rectify it? Note, when I subscribe myself just as atscott@thenew.net then there are now problems. I have also tried the following: 1. I have tried it without the quote marks around the name 2. Without the < > marks around the address 3. With the name after the address 4. With neither quote marks, nor < > marks None of these work. Thanks! From majordomo-users-owner Sun Feb 6 20:24:25 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id UAA11571; Sun, 6 Feb 2000 20:09:40 -0800 (PST) Received: from usinter.net (mail.usinter.net [206.171.66.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA11563 for ; Sun, 6 Feb 2000 20:09:32 -0800 (PST) Received: from usinter.net [209.85.130.137] by usinter.net [206.171.66.25] with SMTP (MDaemon.v2.8.7.0.R) for ; Sun, 06 Feb 2000 20:24:25 -0800 Message-ID: <389E4860.BE424510@usinter.net> Date: Sun, 06 Feb 2000 20:21:52 -0800 From: "Todd A. Lyons" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM, Sandoz Subject: Re: abort message (mj_resend) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: majordomo-users@GreatCircle.COM X-Return-Path: cannonball@usinter.net Reply-To: cannonball@usinter.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Sandoz wrote: > ----- The following addresses had permanent fatal errors ----- > pod-imm-outgoing > :include:/home/majordomo/lists/pod-imm > (expanded from: pod-imm-outgoing) > > ----- Transcript of session follows ----- > 550 :include:/home/majordomo/lists/pod-imm... Cannot open > /home/majordomo/lists/pod-imm: World writable directory > Message delivered to mailing list pod-imm-outgoing > 554 pod-imm-outgoing... aliasing/forwarding loop broken -----From the sendmail 8.9 FAQ Question 3.32: Now the differences that make this work that may not be the same as instructed by the majordomo instructions: 1) Put the majordomo.aliases file in /etc, not in the majordomo install directory. 2) Make the permissions on /usr/local/majordomo 0751, not 0775. 3) Make the permissions on /usr/local/majordomo/Log 0664, owned by majordomo, group majordomo. 4) /usr/local/majordomo/lists is mode 0755, owner majordomo, group majordomo 5) The permissions owners for the lists should be 0755 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/ 0664 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/abt 0660 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/abt.config 0664 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/abt.info ------End quote The only difference between sendmail's recommendation and my working system are that I have all groups set to daemon (ie majordomo.daemon) -- Blue skies... Cannonball * One ring to rule them all, One ring to find them * * One ring to bring them all, and in the darkness bind them * Sauron From majordomo-users-owner Mon Feb 7 04:40:12 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id EAA19024; Mon, 7 Feb 2000 04:27:35 -0800 (PST) Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA19017 for ; Mon, 7 Feb 2000 04:27:28 -0800 (PST) Received: from 209-122-216-86.s86.tnt3.lnh.md.dialup.rcn.com ([209.122.216.86] helo=noydb) by smtp02.mrf.mail.rcn.net with smtp (Exim 2.12 #3) id 12HnUb-0004IL-00; Mon, 7 Feb 2000 07:42:14 -0500 Message-Id: <4.1.20000207073902.009a4db0@kajor.com> X-Sender: jack@kajor.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 07 Feb 2000 07:39:47 -0500 To: Clay Irving From: Jack Schnapper Subject: Re: email validator Cc: majordomo-users@GreatCircle.COM In-Reply-To: <20000204174715.D2312@ratchet.skechers.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am rather a neophyte when it comes to perl. Where would I insert this module? Thanks, Jack At 05:47 PM 2/4/00 -0800, Clay Irving wrote: >On Fri, Feb 04, 2000 at 01:47:35PM -0800, ramon via lepton wrote: > >> Does anyone have a working email validator for majordomo lists? > >I use the Perl module Email::Valid to weed out obvious bad addresses: > >#!/usr/local/bin/perl > >use Email::Valid; > >$input_file = "foo.txt"; # Input file >$good_addresses = "good.txt"; # File to store good addresses >$bad_addresses = "bad.txt"; # File to store bad addresses > >open F, "$input_file" or die "$!\n"; >open G, ">$good_addresses" or die "$!\n"; >open R, ">$bad_addresses" or die "$!\n"; > >while ($address = ) { # Read the list of Email addresses > chomp $address; > $address =~ s/^\s+//; # Remove spaces in the Email address > $valid = new Email::Valid; > if ($valid->address( -address => $address)) { > print G "$address\n"; # The address is valid > } else { > print R "$address\n"; # the address is not valid > } >} > >-- >Clay Irving >clay@skechers.com From majordomo-users-owner Mon Feb 7 06:09:31 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA19944; Mon, 7 Feb 2000 05:57:16 -0800 (PST) Received: from tomts1-srv.bellnexxia.net (tomts1.bellnexxia.net [209.226.175.139]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA19937 for ; Mon, 7 Feb 2000 05:57:10 -0800 (PST) Received: from epbc ([216.209.153.107]) by tomts1-srv.bellnexxia.net (InterMail vM.4.01.02.07 201-229-116-107) with ESMTP id <20000207141227.WRHQ24271.tomts1-srv.bellnexxia.net@epbc>; Mon, 7 Feb 2000 09:12:27 -0500 Message-Id: <4.2.2.20000207091348.00af6a30@mail.woodvale.on.ca> X-Sender: idouglas@mail.woodvale.on.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 07 Feb 2000 09:16:04 -0500 To: Andrew Scott , majordomo-users@GreatCircle.COM From: Ian Douglas Subject: Re: Address/Name problems In-Reply-To: <3.0.6.32.20000206230731.00829c80@mail.thenew.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > >"Andrew Scott" If you set strip=no in your list.config file, it should add you exactly that way (full text taken from the From: field, I believe). So if you try to add yourself as such: From: Andrew Scott To: majordomo@wherever.com Subj: subscribe list atscott@thenew.net ... it should take the full text from the From: field and append that to the list. Anyone need to correct me on anything? I've been running a list like that for a little while now and it works great for us. Ian From majordomo-users-owner Mon Feb 7 06:24:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA20195; Mon, 7 Feb 2000 06:17:18 -0800 (PST) Received: from ommadawn.cegep-heritage.qc.ca ([206.167.123.49]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA20185 for ; Mon, 7 Feb 2000 06:17:06 -0800 (PST) Received: from ommadawn.cegep-heritage.qc.ca (ommadawn.cegep-heritage.qc.ca [206.167.123.49]) by ommadawn.cegep-heritage.qc.ca (8.8.7/8.8.7) with ESMTP id JAA20566 for ; Mon, 7 Feb 2000 09:37:01 -0500 Message-ID: <389ED88B.15B2CB40@ommadawn.cegep-heritage.qc.ca> Date: Mon, 07 Feb 2000 09:36:59 -0500 From: "Maurice G. Lafleur" X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.0.36 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: approve password Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I wrote: > > Hi everyone, > > I have some 8 ML running on one server without a glitch an a single one > I am trying to set up on a second server. I am not new to MJ. I went > through the full motion: create majordomo user, create directory for MJ [...snipped..] Never mind this question. I found my problem. I am so ashamed I've been walking around with a brown bag over my head for the past week or so. One question though: why did it take my post a good week to trun up on the list? Regards, -- MGL -- Maurice Lafleur Teacher, Heritage College mailto: admin@ommadawn.cegep-heritage.qc.ca 325 Cite des Jeunes http://ommadawn.cegep-heritage.qc.ca Hull. Qc. Canada Voice: +1(819).778.2270 x1412 J8Y 6T3 Fax: +1(819)778.7364 From majordomo-users-owner Mon Feb 7 07:24:29 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA20466; Mon, 7 Feb 2000 06:50:35 -0800 (PST) Received: from dilbert.yvcc.cc.wa.us (dilbert.yvcc.cc.wa.us [134.39.161.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA20453 for ; Mon, 7 Feb 2000 06:50:26 -0800 (PST) Received: from [208.26.175.7] (yakimauser004.bossig.com [208.26.175.7]) by dilbert.yvcc.cc.wa.us with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 1JSQK4G2; Mon, 7 Feb 2000 07:04:49 -0800 User-Agent: Microsoft Outlook Express Macintosh Edition - 5.0 (1513) Date: Mon, 07 Feb 2000 07:07:05 -0800 Subject: setting the moderator & owner From: David Lynx To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am having trouble with the syntax for setting the moderator and owner. Can these be two different things email addresses? Not sure where to write them in the config file. Thanks From majordomo-users-owner Mon Feb 7 09:26:08 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA22048; Mon, 7 Feb 2000 09:17:50 -0800 (PST) Received: from lepton.etown.com (adsl-207-212-51-167.dsl.snfc21.pacbell.net [207.212.51.167]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA22033 for ; Mon, 7 Feb 2000 09:17:42 -0800 (PST) Received: from lepton.etown.com (lepton.etown.com [207.212.51.167]) by lepton.etown.com (8.9.2/8.9.2) with ESMTP id JAA29990; Mon, 7 Feb 2000 09:32:52 -0800 (PST) Date: Mon, 7 Feb 2000 09:32:52 -0800 (PST) From: ramon via lepton To: Jack Schnapper cc: Clay Irving , majordomo-users@GreatCircle.COM Subject: Re: email validator In-Reply-To: <4.1.20000207073902.009a4db0@kajor.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk It is not the module that is listed here. You have to go and get it from one of the CPAN sites and then install it. To install the module just uncompress/untar and then: to install: perl Makefile.PL make make test make install It's all in the readme file. ramon. On Mon, 7 Feb 2000, Jack Schnapper wrote: > I am rather a neophyte when it comes to perl. Where would I insert this > module? > > Thanks, > Jack > > At 05:47 PM 2/4/00 -0800, Clay Irving wrote: > > >On Fri, Feb 04, 2000 at 01:47:35PM -0800, ramon via lepton wrote: > > > >> Does anyone have a working email validator for majordomo lists? > > > >I use the Perl module Email::Valid to weed out obvious bad addresses: > > > >#!/usr/local/bin/perl > > > >use Email::Valid; > > > >$input_file = "foo.txt"; # Input file > >$good_addresses = "good.txt"; # File to store good addresses > >$bad_addresses = "bad.txt"; # File to store bad addresses > > > >open F, "$input_file" or die "$!\n"; > >open G, ">$good_addresses" or die "$!\n"; > >open R, ">$bad_addresses" or die "$!\n"; > > > >while ($address = ) { # Read the list of Email addresses > > chomp $address; > > $address =~ s/^\s+//; # Remove spaces in the Email address > > $valid = new Email::Valid; > > if ($valid->address( -address => $address)) { > > print G "$address\n"; # The address is valid > > } else { > > print R "$address\n"; # the address is not valid > > } > >} > > > >-- > >Clay Irving > >clay@skechers.com > From majordomo-users-owner Mon Feb 7 11:56:07 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA23856; Mon, 7 Feb 2000 11:39:42 -0800 (PST) Received: from lepton.etown.com (adsl-207-212-51-167.dsl.snfc21.pacbell.net [207.212.51.167]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA23849 for ; Mon, 7 Feb 2000 11:39:36 -0800 (PST) Received: from lepton.etown.com (lepton.etown.com [207.212.51.167]) by lepton.etown.com (8.9.2/8.9.2) with ESMTP id LAA00637; Mon, 7 Feb 2000 11:54:36 -0800 (PST) Date: Mon, 7 Feb 2000 11:54:36 -0800 (PST) From: ramon via lepton To: Jack Schnapper cc: Clay Irving , majordomo-users@GreatCircle.COM Subject: Re: email validator In-Reply-To: <4.1.20000207073902.009a4db0@kajor.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I want to run something like this for many different types of lists. Do I need to call flock on my majordomo list files to avoid corruption. What happens when I lock the file and majordomo attempts to write to it? ramon. On Mon, 7 Feb 2000, Jack Schnapper wrote: > I am rather a neophyte when it comes to perl. Where would I insert this > module? > > Thanks, > Jack > > At 05:47 PM 2/4/00 -0800, Clay Irving wrote: > > >On Fri, Feb 04, 2000 at 01:47:35PM -0800, ramon via lepton wrote: > > > >> Does anyone have a working email validator for majordomo lists? > > > >I use the Perl module Email::Valid to weed out obvious bad addresses: > > > >#!/usr/local/bin/perl > > > >use Email::Valid; > > > >$input_file = "foo.txt"; # Input file > >$good_addresses = "good.txt"; # File to store good addresses > >$bad_addresses = "bad.txt"; # File to store bad addresses > > > >open F, "$input_file" or die "$!\n"; > >open G, ">$good_addresses" or die "$!\n"; > >open R, ">$bad_addresses" or die "$!\n"; > > > >while ($address = ) { # Read the list of Email addresses > > chomp $address; > > $address =~ s/^\s+//; # Remove spaces in the Email address > > $valid = new Email::Valid; > > if ($valid->address( -address => $address)) { > > print G "$address\n"; # The address is valid > > } else { > > print R "$address\n"; # the address is not valid > > } > >} > > > >-- > >Clay Irving > >clay@skechers.com > From majordomo-users-owner Mon Feb 7 12:11:21 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA24145; Mon, 7 Feb 2000 11:56:28 -0800 (PST) Received: from ratchet.skechers.com (mail.skechers.com [207.238.255.5]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA24134 for ; Mon, 7 Feb 2000 11:56:22 -0800 (PST) Received: (from clay@localhost) by ratchet.skechers.com (8.9.3/8.9.3) id MAA16209; Mon, 7 Feb 2000 12:11:04 -0800 (PST) Date: Mon, 7 Feb 2000 12:11:04 -0800 From: Clay Irving To: ramon via lepton Cc: Jack Schnapper , Clay Irving , majordomo-users@GreatCircle.COM Subject: Re: email validator Message-ID: <20000207121104.F24625@ratchet.skechers.com> References: <4.1.20000207073902.009a4db0@kajor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: ; from ramon via lepton on Mon, Feb 07, 2000 at 11:54:36AM -0800 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Mon, Feb 07, 2000 at 11:54:36AM -0800, ramon via lepton wrote: > I want to run something like this for many different types of lists. Do I > need to call flock on my majordomo list files to avoid corruption. What > happens when I lock the file and majordomo attempts to write to it? Take a look at the code again -- It never writes to the majordomo list file. It writes good addresses to one file and rejected addresses to another file. After you get your good addresses replace the majordomo list file... -- Clay Irving clay@skechers.com From majordomo-users-owner Mon Feb 7 12:36:58 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA24339; Mon, 7 Feb 2000 12:08:59 -0800 (PST) Received: from mail1.den.wantweb.net (mail1.den.wantweb.net [24.236.11.6]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA24332 for ; Mon, 7 Feb 2000 12:08:53 -0800 (PST) Message-Id: <200002072008.MAA24332@honor.greatcircle.com> Received: from rgallegos ([24.236.12.50]) by mail1.den.wantweb.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 605-42905U2500L250S0) with SMTP id AAA195; Mon, 7 Feb 2000 13:22:32 -0700 From: "Raul A. Gallegos" To: "David Lynx" Cc: "majordomo-users@greatcircle.com" Date: Mon, 07 Feb 2000 13:24:08 -0700 Reply-To: "Raul A. Gallegos" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: setting the moderator & owner Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The owner is set in the alias file when you create the list. The moderator is set in the config file. REgards. On Mon, 07 Feb 2000 07:07:05 -0800, David Lynx wrote: >I am having trouble with the syntax for setting the moderator and owner. >Can these be two different things email addresses? Not sure where to write >them in the config file. > >Thanks > Email: raul@asmodean.net -- icq# 5283055 Join Blindadult mailing list email majordomo@asmodean.net Mystical Gates: telnet://mg.asmodean.net:2369 Info about MG builders email mg@asmodean.net From majordomo-users-owner Mon Feb 7 12:41:04 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA24321; Mon, 7 Feb 2000 12:08:00 -0800 (PST) Received: from wolfenet.com (ratty.wolfe.net [204.157.98.9]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA24314 for ; Mon, 7 Feb 2000 12:07:54 -0800 (PST) Received: from [192.168.100.101] (yak-p2-27.wolfenet.com [207.66.140.154]) by wolfenet.com (8.9.3/8.9.3) with ESMTP id MAA01792; Mon, 7 Feb 2000 12:23:13 -0800 (PST) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.0 (1513) Date: Mon, 07 Feb 2000 12:23:57 -0800 Subject: okay.. great! From: David Lynx To: CC: Message-ID: Mime-version: 1.0 Content-type: multipart/alternative; boundary="MS_Mac_OE_3032771038_604150_MIME_Part" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --MS_Mac_OE_3032771038_604150_MIME_Part Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Thanks!.. I see now, both of these email addresses are in the aliases file. So what what email does the owner receive? on 2/7/2000 11:50 AM, Bill wrote: LIST-approval: MODERATOR'S EMAIL ADDRESS LIST-owner: LIST-OWNER'S EMAIL ADDRESS --MS_Mac_OE_3032771038_604150_MIME_Part Content-type: text/html; charset="US-ASCII" Content-transfer-encoding: quoted-printable okay.. great! Thanks!.. I see now, both of these email addresses are in the aliases f= ile.

So what what email does the owner receive?

on 2/7/2000 11:50 AM, Bill wrote:

LIST-approval: MODERATOR'S EMAIL ADDRESS
LIST-owner: LIST-OWNER'S EMAIL ADDRESS

--MS_Mac_OE_3032771038_604150_MIME_Part-- From majordomo-users-owner Mon Feb 7 12:55:52 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA24283; Mon, 7 Feb 2000 12:04:39 -0800 (PST) Received: from wolfenet.com (ratty.wolfe.net [204.157.98.9]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA24276 for ; Mon, 7 Feb 2000 12:04:33 -0800 (PST) Received: from [192.168.100.101] (yak-p2-27.wolfenet.com [207.66.140.154]) by wolfenet.com (8.9.3/8.9.3) with ESMTP id MAA01831; Mon, 7 Feb 2000 12:19:51 -0800 (PST) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.0 (1513) Date: Mon, 07 Feb 2000 12:20:37 -0800 Subject: Re: setting the moderator & owner From: David Lynx To: CC: Jim Reisert Message-ID: In-Reply-To: <389F1A0B.346C2A43@mint-tech.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Okay.. I see, the other one is in alias. in moderator = how does it know who the moderator is? do you put moderater = joe@qpublic.com ? Does the moderator just get email addressed to the list and the owner other things? I am curious if the owner can be sent to get mail delivery problems.. Thanks so much for your help. > The owner is set in /etc/aliases: > > owner-list: owner > > The moderator is set in the list.config file > > moderator = moderator > > You can set moderator = owner-list if you want the list owner to always > be the moderator. This makes it easier to switch list owners because > you just have to edit the /etc/aliases file once. > > If you want them to be different (and they can be), you have 2 files to > maintain. > > David Lynx wrote: >> >> I am having trouble with the syntax for setting the moderator and owner. >> Can these be two different things email addresses? Not sure where to write >> them in the config file. >> >> Thanks > > -- > Jim Reisert Voice: 781-685-3928 > Mint Technology Fax: 781-685-3801 > 77 South Bedford Street Email: jim_reisert@mint-tech.com > Burlington, MA 01803 WWW: http://www.mint-tech.com/ -- From majordomo-users-owner Mon Feb 7 13:10:48 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA25073; Mon, 7 Feb 2000 13:04:36 -0800 (PST) Received: from ceris.purdue.edu (pennant.ceris.purdue.edu [128.210.64.11]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA25063 for ; Mon, 7 Feb 2000 13:04:29 -0800 (PST) Received: (from root@localhost) by ceris.purdue.edu (8.9.3+Sun/8.9.2) id QAA13881; Mon, 7 Feb 2000 16:19:45 -0500 (EST) From: Virginia Walters Message-Id: <200002072119.QAA13881@ceris.purdue.edu> Subject: Re: Problem with 1.94.5 recognizing some commands? To: Jim_Reisert@mint-tech.com (Jim Reisert) Date: Mon, 7 Feb 2000 16:19:45 -0500 (EST) Cc: majordomo-users@greatcircle.com In-Reply-To: <389F1EED.3F874A11@mint-tech.com> from "Jim Reisert" at Feb 07, 2000 02:37:17 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk According to Jim Reisert: > >Virginia Walters wrote: >> >> On Fri Feb 4 14:40:23 2000 Jim Reisert wrote: >> > >> >I got the following response back from my new 1.94.5 installation when I >> >tried to zubscribe myself: >> > >> >>>>> approve test.admin zubscribe >> >**** approve: who? >> >Succeeded (to list test). >> >> >> Jim, >> >> majordomo reads the address when a potential subscriber sends a request, >> but, in my 1.94.4 version, approve does need to know who is being subscribed. > >I was trying to auto-approve subscribing myself. 1.94.4 did not require >an address, but 1.94.5 apparently does. And if you look at the message >above, it claims that it doesn't know 'who' to approve, but subscribes >the unspecified user (me) successfully anyway. > >> BTW, it has also been my experience (maybe because of the way I've configured >> sendmail) that subscribing local users requires _only_ their user id. If >> I include full addresses, they are not recognized as being valid. (My list >> is restricted to subscriber-only access.) > >That may be true, depending on what the From: address really looks like. > >1.94.5 does NOT accept any admin commands if you don't have a fully >qualified outgoing (From:) mail address. For example, if I try to >approve a subscribe request from the command line, it says "Name" >is not a valid address. However, if I send the request within Emacs, >where my @node is tacked on (i.e. ) then the request goes >through. This is good to know. Having just gotten 1.94.4 to work, I'm _really_ skittish about upgrading to 5. I don't look forward to a melt-down. I have a similar experience with going through a web interface in which I've configured a host name default. If I use my MUA, I'm subscribed as just me; while the web script adds me as me@my.host.edu, and looks for me in the list (restricted) as me@my.host.edu. Because me and me@ are different entries.... oh well. There are just too many variables. -vlw ======================================================================= Virginia Walters, CERIS Network Services Voice: 765/494-0442 Email: vwalters@ceris.purdue.edu FAX: 765/494-9727 From majordomo-users-owner Mon Feb 7 15:58:20 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA26880; Mon, 7 Feb 2000 15:44:17 -0800 (PST) Received: from limerence.net (northwood-156-168.reshall.umich.edu [141.213.156.168]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA26873 for ; Mon, 7 Feb 2000 15:44:08 -0800 (PST) Received: from northwood (hate.limerence.net [141.213.156.167]) by limerence.net (8.9.3/8.9.3) with SMTP id HAA19530; Mon, 7 Feb 2000 07:03:23 -0500 From: "Sandoz" To: "Norio Ohki" , "Sandoz" Cc: Subject: RE: abort message (mj_resend) Date: Mon, 7 Feb 2000 19:01:57 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <389E3AF9.755BAE10@okmicro.co.jp> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.100 Importance: Normal Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk yep, that was it, thanks :P -----Original Message----- From: Norio Ohki [mailto:norio@okmicro.co.jp] Sent: Sunday, February 06, 2000 10:25 PM To: Sandoz Cc: majordomo-users@greatcircle.com Subject: Re: abort message (mj_resend) Hi Sandoz, if I could mention about your second case, I've just experienced same thing. Recently posted faq will be helpful, if your server is using sendmail8.9*. I could successfully fix it. Norio >From FAQ posted by Dave Barr. ---------------------------------------------------------------------- 4.12 - Majordomo doesn't seem to work with sendmail 8.9 The new security features of sendmail don't allow :include: directories to be group writable. Unfortunately, by default these directories are group writable with Majordomo. If you have this problem you will see errors from sendmail like "Cannot open /path/name: Group writable directory" and "aliasing/forwarding loop broken". One solution is to add: O DontBlameSendmail=groupwritabledirpathsafe in your sendmail.cf and restart sendmail. The other method (and generally the recommended one) is to remove the group-write bit on the lists directory and any list files. Make sure also any parent directories to not have the group or other write bit set. If Majordomo is working correctly having group write permission is not necessary. However, some people find it convenient to have group-write access so users can be put in the majordomo group and not need root access all the time to work on majordomo. ------------------------------------------------------------------------ Sandoz wrote: > > hi, i would appreciate it if someone could help: > > When sending mail to my list, I get the following abort message in return: > > MAJORDOMO ABORT (mj_resend)!! > > shlock: '/home/majordomo/lists' is not writable by UID 8 GID 12 > > when I make the directory available to uid 8 (mail) by changing permissions, > I get: > > The original message was received at Sun, 6 Feb 2000 02:42:34 -0500 > from mail@localhost > > ----- The following addresses had permanent fatal errors ----- > pod-imm-outgoing > :include:/home/majordomo/lists/pod-imm > (expanded from: pod-imm-outgoing) > > ----- Transcript of session follows ----- > 550 :include:/home/majordomo/lists/pod-imm... Cannot open > /home/majordomo/lists/pod-imm: World writable directory > Message delivered to mailing list pod-imm-outgoing > 554 pod-imm-outgoing... aliasing/forwarding loop broken > > It's kind of like a catch22... > > --John From majordomo-users-owner Mon Feb 7 16:12:05 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA27094; Mon, 7 Feb 2000 16:06:50 -0800 (PST) Received: from mailmsgone.thenew.net (smtp.thenew.net [207.245.252.177]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA27087 for ; Mon, 7 Feb 2000 16:06:43 -0800 (PST) Received: from [209.112.15.186] by mailmsgone.thenew.net (NTMail 4.20.0009/NU7668.00.391cc02b) with ESMTP id ixkhcaaa for ; Mon, 7 Feb 2000 19:16:20 -0500 Message-Id: <3.0.6.32.20000207194159.008b3a40@mail.thenew.net> X-Sender: atscott@mail.thenew.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 07 Feb 2000 19:41:59 -0500 To: majordomo-users@GreatCircle.COM From: Andrew Scott Subject: Re: Address/Name problems Cc: Ian Douglas In-Reply-To: <4.2.2.20000207091348.00af6a30@mail.woodvale.on.ca> References: <3.0.6.32.20000206230731.00829c80@mail.thenew.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The config is set strip=no already. The problem isn't the way it looks in the file. It *appears* to be OK, i.e. as: "Andrew Scott" The problem is that when majordomo goes to send, it attempts to send to: <"Andrew Scott" > which is not a valid address. I am just in the setting up process, and tried it with a couple of other subscribers as well, and ran into the same problem with there address to. It seems that whatever way majordomo is set up, it want to add these extra < >'s. Any solutions? At 09:16 AM 2000/02/07 -0500, you wrote: >If you set strip=no in your list.config file, it should add you exactly >that way (full text taken from the From: field, I believe). From majordomo-users-owner Mon Feb 7 19:11:19 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA28715; Mon, 7 Feb 2000 19:01:00 -0800 (PST) Received: from mailmsgone.thenew.net (smtp.thenew.net [207.245.252.177]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA28708 for ; Mon, 7 Feb 2000 19:00:54 -0800 (PST) Received: from [209.112.15.125] by mailmsgone.thenew.net (NTMail 4.20.0009/NU7668.00.391cc02b) with ESMTP id bbmhcaaa for ; Mon, 7 Feb 2000 22:10:38 -0500 Message-Id: <3.0.6.32.20000207223638.00864a10@mail.thenew.net> X-Sender: atscott@mail.thenew.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 07 Feb 2000 22:36:38 -0500 To: majordomo-users@GreatCircle.COM From: Andrew Scott Subject: Re: Address/Name problems In-Reply-To: <3.0.6.32.20000206202328.0080e3e0@mail.thenew.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I don't know if it makes any difference or not, but the mail program used is qmail. I will post the complete delivery failure message below. Thanks, Andrew Scott ------------------------------------------------------------ Hi. This is the qmail-send program at supressed.host.net. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <"Andrew Scott" >: Sorry, I couldn't find any host named thenew.net>. (#5.1.2) --- Below this line is a copy of the message. Return-Path: Received: (qmail 1553 invoked by alias); 8 Feb 2000 03:09:46 -0000 Delivered-To: pisces-gospelh-ghf-list@supressed.hos.net Received: (qmail 1550 invoked by alias); 8 Feb 2000 03:09:46 -0000 Message-Id: <3.0.6.32.20000207222933.0086ad40@mail.thenew.net> X-Sender: atscott@mail.thenew.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 07 Feb 2000 22:29:33 -0500 To: From: Andrew Scott Subject: ghf- test Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ghf@supressed.com Precedence: bulk test ------------------------------------------------------------ original posting: At 08:23 PM 2000/02/06 -0500, you wrote: >I'm still trying to set up my majordomo list after Esosoft got out of the >business! > >Anyway, here's my problem I am now having: > >I want to list names along with addresses in the subscription list. >However, for some reason, when the mail goes out, extra < > 's are added, >and creates an invalid email address. For example, I have subscribed >myself as follows: > >"Andrew Scott" > >This always worked in the past. But now, I get an error message as follows: > >--------------------------------------------- ><"Andrew Scott" >: >Sorry, I couldn't find any host named thenew.net>. (#5.1.2) >--------------------------------------------- > >It appears as though an extra set of <> are being added. What is causing >this, and how can we rectify it? > >Note, when I subscribe myself just as atscott@thenew.net then there are >now problems. I have also tried the following: > >1. I have tried it without the quote marks around the name >2. Without the < > marks around the address >3. With the name after the address >4. With neither quote marks, nor < > marks > >None of these work. > >Thanks! > From majordomo-users-owner Mon Feb 7 20:56:56 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id UAA29579; Mon, 7 Feb 2000 20:43:36 -0800 (PST) Received: from mail.iconz.co.nz (mail.iconz.co.nz [210.48.22.36]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA29567 for ; Mon, 7 Feb 2000 20:43:29 -0800 (PST) Received: from ARENA (p207.ipa1-n8-16.iconz.net.nz [210.48.24.207]) by mail.iconz.co.nz (8.9.3/8.9.3) with SMTP id RAA059780949985981 for ; Tue, 8 Feb 2000 17:59:41 +1300 (NZDT) Message-ID: <000701bf71f0$73938280$2000000a@ARENA> From: "Michael Joyce" To: Subject: New Lists Date: Tue, 8 Feb 2000 17:53:31 +1300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I have heard that you have to send a config list list.admin command to Majordomo. The documentation doesn't explain this very well. What should the aliases be set to? Cheers, Michael Joyce From majordomo-users-owner Mon Feb 7 22:55:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA00789; Mon, 7 Feb 2000 22:49:38 -0800 (PST) Received: from ns1.cserver.dk ([194.239.155.141]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA00774 for ; Mon, 7 Feb 2000 22:49:30 -0800 (PST) Received: from jsconsult.dk (113.ppp1-8.image.dk [212.54.76.241]) by ns1.cserver.dk (8.9.3/8.9.3) with ESMTP id IAA00552 for ; Tue, 8 Feb 2000 08:04:54 +0100 Message-ID: <389FC00A.D4C7E0AF@jsconsult.dk> Date: Tue, 08 Feb 2000 08:04:43 +0100 From: "Jens W. Skov" Reply-To: jens@jsconsult.dk Organization: JS Consult X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Banned users. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Can I make a list of email-addresses, that are not allowed to sybscribe to or send to the list? -- Jens W. Skov, JS Consult. For high quality web and mail hosting at fair prices visit http://www.jnet.dk or contact webmaster@jnet.dk For hard- & software visit http://www.jsconsult.dk From majordomo-users-owner Tue Feb 8 00:54:28 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id XAA01548; Mon, 7 Feb 2000 23:51:09 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id XAA01532 for majordomo-users@greatcircle.com; Mon, 7 Feb 2000 23:51:04 -0800 (PST) Received: from teapot21.domain3.bigpond.com (teapot21.domain3.bigpond.com [139.134.5.159]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id VAA12167 for ; Sun, 6 Feb 2000 21:20:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by teapot21.domain3.bigpond.com (NTMail 3.02.13) with ESMTP id aa823940 for ; Mon, 7 Feb 2000 15:35:45 +1000 Received: from WBBH-T-005-p-170-52.tmns.net.au ([139.134.170.52]) by mail3.bigpond.com (Claudes-Reliable-MailRouter V2.7 5/505356); 07 Feb 2000 15:35:44 Message-ID: <389E4A33.3D48BF09@kapital.com.au> Date: Mon, 07 Feb 2000 15:29:40 +1100 From: Simon Ravenscroft Reply-To: simon@kapital.com.au Organization: Kapital X-Mailer: Mozilla 4.7 (Macintosh; U; PPC) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo-Users@GreatCircle.COM Subject: Is there a way to reduce excessive admin emails? Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hey, I have had a complaint from a client that they are receiving too many admin emails (subscribe/unsubscribe notifications) from their Majorodomo lists. On the most part there is no response required from them, the emails are just notifications. Is there a way to reduce these emails to an "action required only" status?? I'm new to mailing lists, and am only the web developer, so I don't host any of the software - I just need to follow it up before the lient kills me (or I kill them). -- Simon Ravenscroft Kapital Ph: (07) 3367 2588 Fax: (07) 3367 2557 simon@kapital.com.au From majordomo-users-owner Tue Feb 8 01:24:38 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id XAA01505; Mon, 7 Feb 2000 23:50:42 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id XAA01486 for majordomo-users@greatcircle.com; Mon, 7 Feb 2000 23:50:31 -0800 (PST) Received: from server1.mich.com (server1.mich.com [198.108.16.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA26723 for ; Sat, 5 Feb 2000 22:41:00 -0800 (PST) Received: from lindy.nuge.com (root@pm012-006.dialip.mich.com [207.75.116.166]) by server1.mich.com (8.9.3/8.9.3) with ESMTP id BAA10544; Sun, 6 Feb 2000 01:56:01 -0500 Received: from localhost (rtg@localhost) by lindy.nuge.com (8.9.3/8.9.3) with ESMTP id BAA13195; Sun, 6 Feb 2000 01:55:57 -0500 X-Authentication-Warning: lindy.nuge.com: rtg owned process doing -bs Date: Sun, 6 Feb 2000 01:55:56 -0500 (EST) From: Rick Green To: Ralf Semroch cc: majordomo-users@GreatCircle.COM Subject: Re: Cannot post if only subscribed to the digest In-Reply-To: <3899BC3E.F60E7E1B@designofsites.de> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 3 Feb 2000, Ralf Semroch wrote: > Hello, > > I am the list-owner of a majordomo-mailinglist "flash4". It started in > december '99 as a "normal" list. A few weeks later some people want to > get a digest version of the list and I ask the provider to add a digest > list. The provider sets up the digest and some people unsubscribe from > the "normal" list and subscribe the digest. But when they are only > members of the digest-version they can't post into the list and I get > the bounces... > What can we do? > Any tips? In the config file for your main list, set restrict_post = flash4 flash4-digest that way, members of either list may post without a bounce to the owner. You may also want to set up the flash4-digest alias to be identical to the flash4 alias, so that subscribers to the digest who post to the digest name instead of the listname, will still be read by everybody. -- Rick Green From majordomo-users-owner Tue Feb 8 07:24:53 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA08813; Tue, 8 Feb 2000 07:16:57 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA08805 for ; Tue, 8 Feb 2000 07:16:51 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id KAA07006; Tue, 8 Feb 2000 10:31:32 -0500 (EST) Date: Tue, 8 Feb 2000 10:31:31 -0500 (EST) From: "Bill Casti (System Admin)" To: "Jens W. Skov" cc: majordomo-users@GreatCircle.COM Subject: Re: Banned users. In-Reply-To: <389FC00A.D4C7E0AF@jsconsult.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Yes. Put each of their addresses in the "taboo headers" field in the majordomo.cf file, as: /^from: jillmasters@email.msn.com/i /^from: mary_smith@aol.com/i /^from: joe.blow@execpc.com/i Bill On Tue, 8 Feb 2000, Jens W. Skov wrote: > Can I make a list of email-addresses, that are not allowed to sybscribe > to or send to the list? > > -- > Jens W. Skov, JS Consult. > For high quality web and mail hosting at fair prices visit > http://www.jnet.dk or contact webmaster@jnet.dk > For hard- & software visit http://www.jsconsult.dk > > > From majordomo-users-owner Tue Feb 8 10:54:58 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA11396; Tue, 8 Feb 2000 10:29:51 -0800 (PST) Received: from nms01 (nms01.srv.hcvlny.cv.net [167.206.112.64]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA11389 for ; Tue, 8 Feb 2000 10:29:40 -0800 (PST) Received: from s1.nassau.cv.net (s1.optonline.net [167.206.112.6]) by nms01 (8.9.3+Sun/8.9.1) with ESMTP id NAA05370 for ; Tue, 8 Feb 2000 13:45:09 -0500 (EST) Received: from office (hicks13-83.optonline.net [167.206.13.83]) by s1.nassau.cv.net (8.9.1/8.9.1) with SMTP id NAA04043 for ; Tue, 8 Feb 2000 13:45:10 -0500 (EST) Reply-To: From: "Wayne Spivak" To: Subject: Abort, due to invalid return addess v 1.94.5 Date: Tue, 8 Feb 2000 13:43:43 -0500 Message-ID: <015101bf7264$6db90000$530dcea7@office.optonline.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Importance: Normal Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I patched 1.94.4 to 19.94.5. I keep getting these: majordomo@foo.org: root (Cron Daemon) is not a valid return address. When I run this command from Cron: echo mkdigest psml-digest psml-digest.admin | sendmail -froot@foo.org majordomo@foo.org Any ideas? Wayne Spivak SBA * Consulting® - Systems for Business & Accounting SBA.NET.WEB® - Internet & World Wide Web Consulting 2711 Bellmore Avenue, Bellmore, New York 11710-4319 Tel: 516-221-3306 Fax: 516-221-7129 mailto:WSpivak@sbanetweb.com http://www.sbanetweb.com or http://www.sbaconsulting.com http://guide.sbanetweb.com -- Guide to Computer Vendors(TM) http://guide.sbanetweb.com/library.html -- Published Articles Join the Internet Society -- http://www.isoc.org From majordomo-users-owner Tue Feb 8 11:09:30 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA11830; Tue, 8 Feb 2000 10:59:07 -0800 (PST) Received: from chamber.dna.fi (chamber.dna.fi [62.236.155.125]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id KAA11823 for ; Tue, 8 Feb 2000 10:59:00 -0800 (PST) Received: (qmail 28319 invoked by uid 501); 8 Feb 2000 21:14:31 +0200 Date: Tue, 8 Feb 2000 21:14:31 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: Andrew Scott Cc: majordomo-users@GreatCircle.COM Subject: Re: Address/Name problems Message-ID: <20000208211431.H27988@chamber.dna.fi> Reply-To: Mikko.Hanninen@iki.fi Mail-Followup-To: Andrew Scott , majordomo-users@GreatCircle.COM References: <3.0.6.32.20000206202328.0080e3e0@mail.thenew.net> <3.0.6.32.20000207223638.00864a10@mail.thenew.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.1.2i In-Reply-To: <3.0.6.32.20000207223638.00864a10@mail.thenew.net>; from atscott@thenew.net on Mon, Feb 07, 2000 at 10:36:38PM -0500 Organization: None Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Andrew Scott wrote on Mon, 07 Feb 2000: > I don't know if it makes any difference or not, but the mail program > used is qmail. I will post the complete delivery failure message below. It certainly does. qmail's .qmail files (which I assume are used to get majordomo to work under qmail) can't contain addresses in the form of "Name ", they need to be strictly address-only, as in "email@address". If you try using only the address (no name in front, no <>'s around), what happens? You said something about "new problems" but didn't give any details. majordomo out-of-the-box doesn't work with qmail-out-of-the-box; either or both need to be adjusted -- I don't know the details, but the qmail web page (http://www.qmail.org) should give you some information at least. Perhaps this has already been taken into account with your majordomo installation though. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Half of the people in the world are below average. From majordomo-users-owner Tue Feb 8 17:37:09 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA15977; Tue, 8 Feb 2000 16:54:52 -0800 (PST) Received: from lawnet.LawNet.Com (lawnet.com [207.38.13.32]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id QAA15970 for ; Tue, 8 Feb 2000 16:54:44 -0800 (PST) Received: from guardian.lawnet.com by lawnet.LawNet.Com id aa25871; 8 Feb 2000 17:09 PST Message-ID: <38A0BE71.8B41D9D8@lawnet.com> Date: Tue, 08 Feb 2000 17:10:09 -0800 From: Tim Lee X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,zh-TW,zh MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: list too large ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We are running 1.94.4 under SCO OSR 5.0.5. Our subscriber file contains about 2000 email addresses and growing. It seems email addresses 800 or later do not get the mails. I have put in my own address: 800 or later, it failed. at 300, it worked. I am still trying to pin point the trouble spot. But I thought someone maybe able to help us. I have also removed some obvious bad email addresses, but so far no luck yet. 1) Is there some special string of characters that may somehow made majordomo stop processing the rest of the email addresses? 2) Is this some kind of configuration or majordomo issue? Thanks Tim Lee MIS Manager The Petersen Law Firm From majordomo-users-owner Tue Feb 8 17:44:00 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA16384; Tue, 8 Feb 2000 17:36:25 -0800 (PST) Received: from mailmsgone.thenew.net (smtp.thenew.net [207.245.252.177]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA16377 for ; Tue, 8 Feb 2000 17:36:19 -0800 (PST) Received: from [209.112.15.56] by mailmsgone.thenew.net (NTMail 4.20.0009/NU7668.00.391cc02b) with ESMTP id jathcaaa for ; Tue, 8 Feb 2000 20:46:11 -0500 Message-Id: <3.0.6.32.20000208211215.0089eea0@mail.thenew.net> X-Sender: atscott@mail.thenew.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 08 Feb 2000 21:12:15 -0500 To: Mikko.Hanninen@iki.fi, majordomo-users@GreatCircle.COM From: Andrew Scott Subject: Re: Address/Name problems In-Reply-To: <20000208211431.H27988@chamber.dna.fi> References: <3.0.6.32.20000207223638.00864a10@mail.thenew.net> <3.0.6.32.20000206202328.0080e3e0@mail.thenew.net> <3.0.6.32.20000207223638.00864a10@mail.thenew.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thank you for your help! >It certainly does. >If you try using only the address (no name in front, >no <>'s around), what happens? Actually, with no name at all, only addresses, there were no problems at all. Problems only occurred when names were used. Does anyone else know anyway around this problem with qmail? From majordomo-users-owner Tue Feb 8 18:04:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA15428; Tue, 8 Feb 2000 16:00:41 -0800 (PST) Received: from stmpy.cais.net (stmpy.cais.net [199.0.216.101]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA15415 for ; Tue, 8 Feb 2000 16:00:30 -0800 (PST) Received: from dorothy ([198.69.129.60]) by stmpy.cais.net (8.8.8/8.8.8) with ESMTP id TAA16363 for ; Tue, 8 Feb 2000 19:15:31 -0500 (EST) Message-Id: <4.3.0.33.0.20000208191112.00dcb8f0@pop.cais.com> X-Sender: firschng@pop.cais.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.0.33 (Beta) Date: Tue, 08 Feb 2000 19:13:38 -0500 To: From: Dorothy Firsching Subject: Re: Communigate Pro In-Reply-To: <39A29FFE7681D311AC8100508B733646D47C@EXCHANGE> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The list hosting provider I now use has just told me that effective March 1, they will be discontinuing Majordomo support because it is "archaic", and switching my lists over to "Communigate Pro". Do any of you have experience with this? Is it really better, or should I hop to it and get another Majordomo provider? My lists are not huge but they are a few thousand subscribers and fairly active. Thanks! /Dorothy Firsching list owner Dorothy Firsching CEO Nautilus Systems, Inc. 3867 Alder Woods Court Fairfax, VA 22033 http://www.nautilus-systems.com/ firschng@nautilus-systems.com From majordomo-users-owner Wed Feb 9 05:25:33 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA25705; Wed, 9 Feb 2000 05:07:34 -0800 (PST) Received: from femiweb.com (sagittarius.hosting4u.net [209.15.2.33]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id FAA25698 for ; Wed, 9 Feb 2000 05:07:21 -0800 (PST) Received: from jtadore1 ([213.56.40.158]) by femiweb.com ; Wed, 09 Feb 2000 07:20:35 -0600 Reply-To: From: "Redacteur FemiWeb" To: "MajordomoUsers" Subject: statistique usage report of mailing list Date: Wed, 9 Feb 2000 13:59:54 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Can someone tell me how to configure majordomo to send a statistique report ? Regards. Albert Ohayon, redacteur. http://www.femiweb.com http://www.epsyweb.com http://www.petitweb.com Etre humain ou ne pas être, serait ce la question ? From majordomo-users-owner Wed Feb 9 06:09:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA26126; Wed, 9 Feb 2000 05:58:21 -0800 (PST) Received: from sr1.srnet.com (sr1.srnet.com [206.148.68.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA26118 for ; Wed, 9 Feb 2000 05:58:15 -0800 (PST) Received: from 101.srnet.com (office.srnet.com [206.148.68.101]) by sr1.srnet.com (8.8.5/8.8.7) with SMTP id JAA22388 for ; Wed, 9 Feb 2000 09:08:40 -0500 (EST) Message-ID: <086301bf7307$17f10520$654494ce@srnet.com> From: "Benn Boulton" To: References: <000701bf71f0$73938280$2000000a@ARENA> Subject: Pricing for hosting lists Date: Wed, 9 Feb 2000 09:08:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have been asked to host a few lists and was wondering what is a fair fee structure. until now I have used majordomo for my customer base announcements Benn From majordomo-users-owner Wed Feb 9 06:54:36 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA26590; Wed, 9 Feb 2000 06:51:40 -0800 (PST) Received: from ns.msic.dia.mil ([136.205.45.59]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id GAA26583 for ; Wed, 9 Feb 2000 06:51:34 -0800 (PST) Received: from msic.dia.mil ([136.205.227.85]) by ns.msic.dia.mil (8.6.10/Solaris 2.3) with ESMTP id JAA11502 for ; Wed, 9 Feb 2000 09:07:39 -0600 Message-ID: <38A18268.FED9535D@msic.dia.mil> Date: Wed, 09 Feb 2000 09:06:16 -0600 From: Allan Newsome Reply-To: allan@msic.dia.mil X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-US MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Re: Communigate Pro Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Here where I work (I'm the email administrator), we use the CommuniGate Pro Mail server and it is Good. You will like it and you can do more with them than you can with Majordomo. It will take some time to learn how to use the features of the CommuniGate mailing lists but all in all I think you will like it. Of course I'm looking at it as the administrator who has all the passwords. Some of the things I would wonder about and would ask the provider you're using is how you will be able to change the settings for the CommuniGate Mailing lists? To the best of my knowledge, you must be the administrator to be able to make setting changes that control the list. There's nothing like a "config" file that you can edit and send to the server to make changes. Everything is web based but only the admin can login to make those changes. That means that you will have to have support anytime you want to make "configuration" changes. You can go and see what the mailing lists will look like by going to: http://mail.stalker.com/ When you get there, click on the Mailing List link. You can also go to Stalkers web site to read more about CommuniGate Pro. http://www.stalker.com/ The information on the way the mailing lists work is found at - http://www.stalker.com/CommuniGatePro/LIST.html Good luck. Allan Newsome The Andy Griffith Show Rerun Watcher Club http://mayberry.com/tagsrwc/ Dorothy Firsching wrote: > The list hosting provider I now use has just told me that effective March 1, > they will be discontinuing Majordomo support because it is "archaic", > and switching my lists over to "Communigate Pro". > > Do any of you have experience with this? Is it really better, or should > I hop to it and get another Majordomo provider? My lists are not huge > but they are a few thousand subscribers and fairly active. > > Thanks! > /Dorothy Firsching > list owner > Dorothy Firsching > CEO > Nautilus Systems, Inc. > 3867 Alder Woods Court > Fairfax, VA 22033 > http://www.nautilus-systems.com/ > firschng@nautilus-systems.com From majordomo-users-owner Wed Feb 9 08:39:35 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA27748; Wed, 9 Feb 2000 08:35:55 -0800 (PST) Received: from geek.net (geek.net [216.91.168.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA27741 for ; Wed, 9 Feb 2000 08:35:49 -0800 (PST) Received: from localhost (rhayden@localhost) by geek.net (8.9.3/8.9.3) with ESMTP id KAA14647; Wed, 9 Feb 2000 10:51:26 -0600 Date: Wed, 9 Feb 2000 10:51:26 -0600 (CST) From: "Robert A. Hayden" To: Dorothy Firsching cc: majordomo-users@GreatCircle.COM Subject: Re: Communigate Pro In-Reply-To: <4.3.0.33.0.20000208191112.00dcb8f0@pop.cais.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Tue, 8 Feb 2000, Dorothy Firsching wrote: > The list hosting provider I now use has just told me that effective March 1, > they will be discontinuing Majordomo support because it is "archaic", > and switching my lists over to "Communigate Pro". > > Do any of you have experience with this? Is it really better, or should > I hop to it and get another Majordomo provider? My lists are not huge > but they are a few thousand subscribers and fairly active. I've looked a little into Communigate as a mail system and it seems pretty good. It's basicly web-managed and such. Your functionality shouldn't change any if they can easily cut you over. =-=-=-=-=-= Robert Hayden rhayden@geek.net UIN: 16570192 From majordomo-users-owner Wed Feb 9 09:10:35 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA28065; Wed, 9 Feb 2000 09:05:03 -0800 (PST) Received: from mhub1.tc.umn.edu (mhub1.tc.umn.edu [160.94.5.41]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA28054 for ; Wed, 9 Feb 2000 09:04:55 -0800 (PST) Received: from garnet.tc.umn.edu by mhub1.tc.umn.edu with ESMTP for majordomo-users@greatcircle.com; Wed, 9 Feb 2000 11:20:29 -0600 Received: from localhost by garnet.tc.umn.edu with ESMTP for majordomo-users@greatcircle.com; Wed, 9 Feb 2000 11:20:28 -0600 Date: Wed, 9 Feb 2000 11:20:28 -0600 (CST) From: mjn To: majordomo-users@greatcircle.com Subject: Some things... Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I posted a question awhile back aobut a creating a more organized setup for my lists directory. Mainly, what I wanted to do was to set things up so each list would have its own sub directory and all of the files corresponding to that list would be held inside of that directory. I have found that i can do this with any file that is pointed to from /etc/aliases but the configurationfiles (listname.config, .passwd, et al) cannot beused in this fashion; most likely because majordomo looks to $home/lists for all of the config files for the slick remote list config and admin. We may be bringing over some 250 lists to Majordomo and right now 1000+ files in a single directory would be a nightmare. Any ideas on this or whether something is going to implimented in MD2 that is similar to this? The other question i have is not directly related to Majordomo but it something that might be useful to many people managing majordomo and listening on this list. I am looking for some good information/examples on how to setup host masquerading with sendmail. Does anyone know where i might go to find something like this? I have been all through sendmail.org's examples and they don't seem to do exactly what i want, which is to have mail to and from my majordomo lists masquerade as a separate hostname but leave the rest of my configuration alone. Anyway, any help folks can give would be great. ____________________________ Mike Neuharth ADCS Technology Specialist http://www.umn.edu/adcs E-Mail : mjn@tc.umn.edu Page Mail : 6123065932@messaging.sprintpcs.com http://nifty.dsl.visi.com/ ____________________________ From majordomo-users-owner Wed Feb 9 09:28:03 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA28171; Wed, 9 Feb 2000 09:10:52 -0800 (PST) Received: from himssnotes.himss.org ([207.154.216.123]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA28164 for ; Wed, 9 Feb 2000 09:10:45 -0800 (PST) From: BField@himss.org Subject: MAJORDOMO ABORT (mj_resend) To: majordomo-users@greatcircle.com X-Mailer: Lotus Notes Release 5.0.2a November 23, 1999 Message-ID: Date: Wed, 9 Feb 2000 11:27:19 -0600 X-Priority: 3 (Normal) X-MIMETrack: Serialize by Router on himssnotes/HIMSS(Release 5.0.1|July 16, 1999) at 02/09/2000 11:27:19 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I need help on this one big time. I get the following message when anyone tries to post to certain lists. Other lists work just fine. MAJORDOMO ABORT (mj_resend)!! Mailer /usr/lib/sendmail -oi -oee -fowner-(listname) -h himss.org (listname)-outgoing exited unexpectedly with error 65535 This is on a Sun Ultra 10 running Solaris 2.6, Majordomo 1.94 and sendmail 8.8.8+SUN. I know from previous posts to this list that this is a sendmail error and that I should divide the error code by 256 and compare that to the sysexits.h file to determine the error. This process however gives an error code of 255 which is way out of range of anything in the sysexits.f file. This began after upgrading to this machine from an older Sun Ultra 1 running 2.6 with default sendmail and Majordomo 1.93. The only unusual thing with the upgrade was that I am still using the old sendmail.cf file. I could not get sendmail 8.8.8+SUN to run with the .cf file that came with the patch so I modified the old .cf file and it is working in all other respects. I tend to think that the .cf file is not the culprit on this because other lists work OK. I am getting desperate on this and would greatly appreciate your help. Brad Field Network Engineer HIMSS (312) 912-9274 bfield@himss.org www.himss.org From majordomo-users-owner Wed Feb 9 09:55:00 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA28554; Wed, 9 Feb 2000 09:43:38 -0800 (PST) Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA28535 for ; Wed, 9 Feb 2000 09:43:31 -0800 (PST) Received: (from uucp@localhost) by uucphost.mcs.net (8.9.3/8.8.8) with UUCP id LAA52675; Wed, 9 Feb 2000 11:59:02 -0600 (CST) Received: (from david@localhost) by midrange.dynip.com (8.9.3/8.8.7) id KAA20282; Wed, 9 Feb 2000 10:27:35 -0600 From: David Gibbs Message-Id: <200002091627.KAA20282@midrange.dynip.com> Subject: Re: statistique usage report of mailing list To: redacteur@femiweb.com Date: Wed, 9 Feb 2000 10:27:34 -0600 (CST) Cc: Majordomo-Users@GreatCircle.COM (MajordomoUsers) In-Reply-To: from "Redacteur FemiWeb" at Feb 09, 2000 01:59:54 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Can someone tell me how to configure majordomo to send a statistique report ? Majordomo doesn't collect any statistics itself ... but I find the "logmail" utilities by David Barr to be quite useful... they can be found at ftp://sol.ccsf.cc.ca.us/majordomo-contrib/ david From majordomo-users-owner Wed Feb 9 11:04:15 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA29725; Wed, 9 Feb 2000 10:48:57 -0800 (PST) Received: from web3601.mail.yahoo.com (web3601.mail.yahoo.com [204.71.203.96]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id KAA29718 for ; Wed, 9 Feb 2000 10:48:50 -0800 (PST) Message-ID: <20000209181859.16165.qmail@web3601.mail.yahoo.com> Received: from [129.237.245.19] by web3601.mail.yahoo.com; Wed, 09 Feb 2000 10:18:59 PST Date: Wed, 9 Feb 2000 10:18:59 -0800 (PST) From: Shauna Swenson Subject: Fwd: To: majordomo-users@greatcircle.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi! I'm not sure if this question is appropriate for this list. If not, I would appreciate it if you would guide me in the right direction. I've got a moderated listserv. Someone sent unsolicited mail to the list, set the list owner as the sender, and bypassed the approval. How do I prevent this from happening again? Here's what I found in the mail log: == Feb 8 16:49:03 sendmail[17732]: QAA17732: Authentication-Warning: : majordom set sender to owner-majordomo using -f -- According to the sendmail man page, only a trusted user (normally root, daemon, and network) can use the "-f" option in that manner. The user majordom has a UID of 43 and a GID of 41 which is not the same as root's or daemon's. "network" is not in the passwd file. I would appreciate all the information you can provide. Thank you. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From majordomo-users-owner Wed Feb 9 11:57:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA00680; Wed, 9 Feb 2000 11:38:20 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA00672 for ; Wed, 9 Feb 2000 11:38:09 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id OAA10825; Wed, 9 Feb 2000 14:52:47 -0500 (EST) Date: Wed, 9 Feb 2000 14:52:46 -0500 (EST) From: "Bill Casti (System Admin)" To: Benn Boulton cc: majordomo-Users@GreatCircle.COM Subject: Re: Pricing for hosting lists In-Reply-To: <086301bf7307$17f10520$654494ce@srnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I charge $10/month/list, in 6-month increments. OR, a flat-rate of $100/year/list when paid upfront ($20 savings). this applies whether it's an open or closed, moderated or unmoderated, discussion or distribution list. And, the price is the same no matter which of my 30+ domains they want to use for their list. Regards. Bill ============================================================================= Bill Casti, CQA Email: help@quality.org - Domain Owner, QUALITY.ORG Pager: +1 800 604 6149 - List Moderator, "TQM in Manufacturing and Service Industries" ----------------------------------------------------------------------------- Self-service list subscription service at www.quality.org/cgi-bin/majordomo See http://www.quality.org/lists/lists_at_quality.org.html for the List of Lists supported at QUALITY.ORG ============================================================================= On Wed, 9 Feb 2000, Benn Boulton wrote: > I have been asked to host a few lists and was wondering > what is a fair fee structure. > > until now I have used majordomo for my customer base announcements > > Benn > > From majordomo-users-owner Wed Feb 9 12:44:45 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA01302; Wed, 9 Feb 2000 12:26:47 -0800 (PST) Received: from lawnet.LawNet.Com (lawnet.com [207.38.13.32]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id MAA01295 for ; Wed, 9 Feb 2000 12:26:41 -0800 (PST) Received: from guardian.lawnet.com by lawnet.LawNet.Com id aa10663; 9 Feb 2000 12:41 PST Message-ID: <38A1D0E7.6B6BB127@lawnet.com> Date: Wed, 09 Feb 2000 12:41:11 -0800 From: Tim Lee X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,zh-TW,zh MIME-Version: 1.0 To: Richard Welty , majordomo-users@greatcircle.com Subject: Re: list too large ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thanks Richard, We are using MMDF, but I have yet to find out what version it is. So is this now a MMDF issue? What can we do about it? Thanks Tim Richard Welty wrote: > > At 05:10 PM 2/8/00 -0800, you wrote: > >2) Is this some kind of configuration or majordomo issue? > > it's a mail transport issue. you don't say what MTA you're using, but i bet > it's an out-of-box sendmail installation, or at least one that hasn't been > fiddled very much > > sendmail has some basic issues in it's mail queueing & delivery strategy > that directly affect large lists. there is probably a problem email address > about 1/2 way down in your list that is wedging delivery; eventually your > subscribers will get their mail, but not until after quite a wait. > > you have a couple of choices: > > 1) learn a _lot_ about sendmail > (potentially very painful and time consuming) > > 2) use bulk_mailer between majordomo & sendmail > (i did this for a while, but it has some serious issues, and is > at best a band aid) > > 3) switch to an MTA with a better queuing strategy > (i switched to exim (http://www.exim.org/) some years ago, and have > never regretted it for one minute; 3000 member lists are delivered > so quickly it will make your head spin.) > > richard > > -- > Richard Welty rwelty@suespammers.org > Any type of UBE (Unsolicited Bulk EMail) to this account > is unwanted. > Join the fight against spam: http://www.cauce.org/ From majordomo-users-owner Wed Feb 9 14:27:29 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA02821; Wed, 9 Feb 2000 14:09:58 -0800 (PST) Received: from orenco.com (orenco.com [209.130.191.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA02814 for ; Wed, 9 Feb 2000 14:09:48 -0800 (PST) Message-Id: <200002092209.OAA02814@honor.greatcircle.com> Received: from 192.168.200.36 by orenco.com with SMTP (QuickMail Pro Server for MacOS 1.1.2); 09-Feb-2000 14:27:13 -0800 Date: 09 Feb 00 14:31:07 -0800 From: Pete Norton Subject: RE: MAJORDOMO ABORT (mj_resend) To: BField , "majordomo-users" X-Mailer: QuickMail Pro 1.5.4 (Mac) X-Priority: 3 MIME-Version: 1.0 Reply-To: Pete Norton Content-Type: multipart/alternative; boundary="====57575357485753524955===1" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk --====57575357485753524955===1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="US-Ascii" Reply to: RE: MAJORDOMO ABORT (mj_resend) This looks a lot like a problem I had a while back with sending out = digests. If this is a similar problem, I believe you will find that your = sendmail command that is sent to the system is getting split into to parts = by a newline character. = If I'm right, then if you go into the '.config' file for the = list, and set 'resend_host', the problem will go away. In my case, with = the 'resend_host' set to nothing, the Digest script was obtaining the = value for resend host from /bin/dnsdomainname (on Linux), which introduced = a newline when there shouldn't have been one. ------------ Pete Norton pnorton@orenco.com Orenco Systems, Inc. The = BField wrote: >I need help on this one big time. I get the following message when anyone >tries to post to certain lists. Other lists work just fine. > >MAJORDOMO ABORT (mj_resend)!! > >Mailer /usr/lib/sendmail -oi -oee -fowner-(listname) > -h himss.org (listname)-outgoing exited unexpectedly with error 65535 > >This is on a Sun Ultra 10 running Solaris 2.6, Majordomo 1.94 and = sendmail >8.8.8+SUN. I know from previous posts to this list that this is a = sendmail >error and that I should divide the error code by 256 and compare that to >the sysexits.h file to determine the error. This process however gives = an >error code of 255 which is way out of range of anything in the sysexits.f >file. > >This began after upgrading to this machine from an older Sun Ultra 1 >running 2.6 with default sendmail and Majordomo 1.93. The only unusual >thing with the upgrade was that I am still using the old sendmail.cf file.= >I could not get sendmail 8.8.8+SUN to run with the .cf file that came = with >the patch so I modified the old .cf file and it is working in all other >respects. >I tend to think that the .cf file is not the culprit on this because = other >lists work OK. > >I am getting desperate on this and would greatly appreciate your help. > >Brad Field >Network Engineer >HIMSS >(312) 912-9274 >bfield@himss.org >www.himss.org > > > >RFC822 header >----------------------------------- > > RECEIVED: from SF_Database by POP_Mailbox_-1262019353 ; 09 FEB 00 13:32:= 23 UT > Received: from HONOR.GREATCIRCLE.COM by orenco.com > with SMTP (QuickMail Pro Server for MacOS 1.1.2); 09-Feb-2000 = >13:32:10 -0800 > Received: (majordom@localhost) by honor.greatcircle.com = >(8.8.5/Honor-Lists-980720-1) id JAA28171; Wed, 9 Feb 2000 09:10:52 -0800 (= PST) > Received: from himssnotes.himss.org ([207.154.216.123]) by = >honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA28164 for = >; Wed, 9 Feb 2000 09:10:45 -0800 (PST) > From: BField@himss.org > Subject: MAJORDOMO ABORT (mj_resend) > To: majordomo-users@greatcircle.com > X-Mailer: Lotus Notes Release 5.0.2a November 23, 1999 > Message-ID: > Date: Wed, 9 Feb 2000 11:27:19 -0600 > X-Priority: 3 (Normal) > X-MIMETrack: Serialize by Router on himssnotes/HIMSS(Release 5.0.1|July = >16, 1999) at 02/09/2000 > 11:27:19 AM > MIME-Version: 1.0 > Content-type: text/plain; charset=3Dus-ascii > Sender: majordomo-users-owner@GreatCircle.COM > Precedence: bulk > --====57575357485753524955===1 Content-Type: text/html; charset="US-Ascii" Content-Transfer-Encoding: quoted-printable 
         Reply to:   RE: MAJORDOMO ABORT (mj_resend)
This looks a lot like = a problem I had a while back with sending = out digests. If this is a similar problem, = I believe you will find that your sendmail = command that is sent to the system is getting = split into to parts by a newline character. =

If I'm right, then if you go into = the '<listname>.config' file for the = list, and set 'resend_host', the problem = will go away. In my case, with the 'resend_host' = set to nothing, the Digest script was obtaining = the value for resend host from /bin/dnsdomainname = (on Linux), which introduced a newline when = there shouldn't have been one.

------------
Pete = Norton
pnorton@orenco.com
Orenco Systems, = Inc.



The
BField wrote:
>I need help on = this one big time. I get the following message = when anyone
>tries to post to certain = lists. Other lists work just fine.
>
>MAJORDOMO = ABORT (mj_resend)!!
>
>Mailer = /usr/lib/sendmail -oi -oee -fowner-(listname)
> = -h himss.org (listname)-outgoing exited = unexpectedly with error 65535
>
>This = is on a Sun Ultra 10 running Solaris 2.6, = Majordomo 1.94 and sendmail
>8.8.8+SUN. = I know from previous posts to this list = that this is a sendmail
>error and that = I should divide the error code by 256 and = compare that to
>the sysexits.h file = to determine the error. This process however = gives an
>error code of 255 which is = way out of range of anything in the sysexits.f
>file.
>
>This = began after upgrading to this machine from = an older Sun Ultra 1
>running 2.6 with = default sendmail and Majordomo 1.93. The = only unusual
>thing with the upgrade = was that I am still using the old sendmail.cf = file.
>I could not get sendmail 8.8.8+SUN = to run with the .cf file that came with
>the = patch so I modified the old .cf file and = it is working in all other
>respects.
>I = tend to think that the .cf file is not the = culprit on this because other
>lists = work OK.
>
>I am getting desperate = on this and would greatly appreciate your = help.
>
>Brad Field
>Network = Engineer
>HIMSS
>(312) 912-9274
>bfield@himss.org<= FONT = FACE=3D"Geneva" SIZE=3D1 COLOR=3D"#000000">
>www.himss.org
>
>
>
>RFC822 = header
>-----------------------------------
>
> = RECEIVED: from SF_Database by POP_Mailbox_-1262019353 = ; 09 FEB 00 13:32:23 UT
> Received: = from HONOR.GREATCIRCLE.COM by orenco.com
> = with SMTP (QuickMail Pro Server for = MacOS 1.1.2); 09-Feb-2000
>13:32:10 = -0800
> Received: (majordom@localhost) by honor.greatcircle.com
>(8.8.5/Honor-Lists-980720-1) = id JAA28171; Wed, 9 Feb 2000 09:10:52 -0800 = (PST)
> Received: from himssnotes.himss.org = ([207.154.216.123]) by
>honor.greatcircle.com = (8.8.5/Honor-980202-1) with ESMTP id JAA28164 = for
><= majordomo-users@greatcircle.com>; Wed, 9 Feb 2000 = 09:10:45 -0800 (PST)
> From: BField@himss.org<= FONT = FACE=3D"Geneva" SIZE=3D1 COLOR=3D"#000000">
> Subject: MAJORDOMO = ABORT (mj_resend)
> To: majordomo-users@greatcircle.com<= FONT = FACE=3D"Geneva" SIZE=3D1 COLOR=3D"#000000">
> X-Mailer: Lotus = Notes Release 5.0.2a November 23, 1999
> = Message-ID: <= OF72A6580D.BDC2DC32-ON86256880.005A3366@himss.org>
> Date: Wed, = 9 Feb 2000 11:27:19 -0600
> X-Priority: = 3 (Normal)
> X-MIMETrack: Serialize = by Router on himssnotes/HIMSS(Release 5.0.1|July =
>16, 1999) at 02/09/2000
> 11:27:19 = AM
> MIME-Version: 1.0
> Content-type: = text/plain; charset=3Dus-ascii
> Sender: = majordomo-users-= owner@GreatCircle.COM
> Precedence: bulk
> = --====57575357485753524955===1-- From majordomo-users-owner Wed Feb 9 15:57:56 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA03991; Wed, 9 Feb 2000 15:43:23 -0800 (PST) Received: from mail.lls.edu (mail.lls.edu [206.17.96.221]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA03984 for ; Wed, 9 Feb 2000 15:43:17 -0800 (PST) Received: from lls.edu ([206.17.98.35]) by mail.lls.edu (Netscape Messaging Server 3.6) with ESMTP id AAA3CC8 for ; Wed, 9 Feb 2000 15:57:34 -0800 Message-ID: <38A1FF85.BAF04F79@lls.edu> Date: Wed, 09 Feb 2000 16:00:05 -0800 From: "George Rajapaksa" Organization: Loyola Law School X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-Users@GreatCircle.COM Subject: Bounce messages Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk How can I checked for the bounced messages. Where does the bounce messages are saved. George - From majordomo-users-owner Wed Feb 9 16:42:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA04668; Wed, 9 Feb 2000 16:36:45 -0800 (PST) Received: from smtp-relay.noc.dsvr.net (smtp-relay.noc.dsvr.net [212.69.192.4]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA04659 for ; Wed, 9 Feb 2000 16:36:38 -0800 (PST) Received: from [212.69.208.40] (helo=oemcomputer) by smtp-relay.noc.dsvr.net with smtp (Exim 3.13 #1) id 12Ihq5-000Im5-00; Thu, 10 Feb 2000 00:52:09 +0000 Reply-To: From: "Bob Shepherd, Screen Play" To: "Bill Casti (System Admin)" Cc: Subject: RE: Pricing for hosting lists Date: Thu, 10 Feb 2000 00:51:50 -0000 Message-ID: <001501bf7361$043b99a0$0dd045d4@oemcomputer> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Bill Do you also charge a set-up fee or do you consider the $100/yr enough to cover the list creation and the inevitable support that's needed for a new administrator in the early days? Just interested. Bob >-----Original Message----- >From: majordomo-users-owner@GreatCircle.COM >[mailto:majordomo-users-owner@GreatCircle.COM]On Behalf Of Bill Casti >(System Admin) >Sent: 09 February 2000 19:53 >To: Benn Boulton >Cc: majordomo-Users@GreatCircle.COM >Subject: Re: Pricing for hosting lists > > > >I charge $10/month/list, in 6-month increments. OR, a flat-rate of >$100/year/list when paid upfront ($20 savings). this applies whether it's >an open or closed, moderated or unmoderated, discussion or distribution >list. And, the price is the same no matter which of my 30+ domains they >want to use for their list. > >Regards. >Bill > >=================================================================== >========== > Bill Casti, CQA Email: >help@quality.org > - Domain Owner, QUALITY.ORG Pager: +1 800 604 6149 > - List Moderator, "TQM in Manufacturing and Service Industries" >------------------------------------------------------------------- >---------- > Self-service list subscription service at >www.quality.org/cgi-bin/majordomo > See http://www.quality.org/lists/lists_at_quality.org.html > for the List of Lists supported at QUALITY.ORG >=================================================================== >========== > > >On Wed, 9 Feb 2000, Benn Boulton wrote: > >> I have been asked to host a few lists and was wondering >> what is a fair fee structure. >> >> until now I have used majordomo for my customer base announcements >> >> Benn >> >> > From majordomo-users-owner Wed Feb 9 17:26:11 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA05146; Wed, 9 Feb 2000 17:15:54 -0800 (PST) Received: from zoso.net (zoso.net [204.122.18.193]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA05139 for ; Wed, 9 Feb 2000 17:15:44 -0800 (PST) Received: from localhost (mirader@localhost) by zoso.net (8.9.3/8.9.3) with ESMTP id RAA03910; Wed, 9 Feb 2000 17:22:46 -0800 Date: Wed, 9 Feb 2000 17:22:46 -0800 (PST) From: Bob To: Shauna Swenson cc: majordomo-users@GreatCircle.COM Subject: Re: Fwd: In-Reply-To: <20000209181859.16165.qmail@web3601.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Wed, 9 Feb 2000, Shauna Swenson wrote: > Hi! > > I'm not sure if this question is appropriate for this > list. If not, I would appreciate it if you would guide > me in the right direction. > > I've got a moderated listserv. Someone sent > unsolicited mail to the list, set the list owner as > the sender, and bypassed the approval. > > How do I prevent this from happening again? > > Here's what I found in the mail log: > == > Feb 8 16:49:03 sendmail[17732]: QAA17732: > Authentication-Warning: : majordom set > sender to owner-majordomo using -f > -- > > According to the sendmail man page, only a trusted > user (normally root, daemon, and network) can use the > "-f" option in that manner. > > The user majordom has a UID of 43 and a GID of 41 > which is not the same as root's or daemon's. "network" > is not in the passwd file. > > I would appreciate all the information you can > provide. Thank you. > __________________________________________________ > Do You Yahoo!? > Talk to your friends online with Yahoo! Messenger. > http://im.yahoo.com > From majordomo-users-owner Wed Feb 9 18:42:23 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA06019; Wed, 9 Feb 2000 18:28:35 -0800 (PST) Received: from zoso.net (zoso.net [204.122.18.193]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA06012 for ; Wed, 9 Feb 2000 18:28:27 -0800 (PST) Received: from localhost (mirader@localhost) by zoso.net (8.9.3/8.9.3) with ESMTP id SAA04609; Wed, 9 Feb 2000 18:44:36 -0800 Date: Wed, 9 Feb 2000 18:44:36 -0800 (PST) From: Bob To: "Bill Casti (System Admin)" cc: "Jens W. Skov" , majordomo-users@GreatCircle.COM Subject: Re: Banned users. 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 it possible to only moderate one address on a open list. What I would like to do is review mail from one address and then approve it and send it on. Also, should taboo headers in the list.config also be edited? Thanks in advance Bob On Tue, 8 Feb 2000, Bill Casti (System Admin) wrote: > > Yes. Put each of their addresses in the "taboo headers" field in the > majordomo.cf file, as: > > /^from: jillmasters@email.msn.com/i > /^from: mary_smith@aol.com/i > /^from: joe.blow@execpc.com/i > > Bill SNIP From majordomo-users-owner Wed Feb 9 21:42:19 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA07974; Wed, 9 Feb 2000 21:26:59 -0800 (PST) Received: from europe.std.com (europe.std.com [199.172.62.20]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA07967 for ; Wed, 9 Feb 2000 21:26:53 -0800 (PST) Received: from world.std.com (world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id AAA14292; Thu, 10 Feb 2000 00:42:38 -0500 (EST) Received: from localhost (jkaplan@localhost) by world.std.com (8.9.3/8.9.3) with ESMTP id AAA16262; Thu, 10 Feb 2000 00:42:37 -0500 (EST) Date: Thu, 10 Feb 2000 00:42:36 -0500 From: Jeffrey Kaplan To: Bob cc: Majordomo Users Subject: Re: Banned users. 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, 9 Feb 2000, Bob wrote: > Is it possible to only moderate one address on a open list. What I would > like to do is review mail from one address and then approve it and send it > on. Also, should taboo headers in the list.config also be edited? Per list, editing the taboo_headers for the list is the way to go. -- Jeffrey Kaplan gordol@gordol.org <*> I'm set up for PGP. Are you? "Draal, I'm not alone. It sees me, it knows I'm here. They're pulling me in. I can't stop it." "It is the Enemy. Pull away, go back to the Path." "I can't, it... it knows I'm here, it knows my name." (Cmdr. Ivanova and Draal, B5 "Voices Of Authority") From majordomo-users-owner Thu Feb 10 08:28:03 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA17845; Thu, 10 Feb 2000 08:11:40 -0800 (PST) Received: from mail1.ebsi.ca (mail2.ebsi.net [204.101.96.114]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA17813 for ; Thu, 10 Feb 2000 08:11:28 -0800 (PST) Received: from roaddogg (table.ebsi.net [204.101.96.7]) by mail1.ebsi.ca (8.9.3/8.9.0) with SMTP id LAA20432 for ; Thu, 10 Feb 2000 11:27:02 -0500 Message-ID: <00e001bf73e3$b3008770$1301a8c0@ebsi.ca> From: "Scott Robinson" To: Subject: Installing Date: Thu, 10 Feb 2000 11:27:18 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DD_01BF73B9.C9FC91A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_00DD_01BF73B9.C9FC91A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have just finished installing majordomo and was doing the last test = and I got nothing from typing in the command. I checked the processes = running and did not find the majordomo daemon running. When I tried to = run it I got an error message. It told me that I installed it fine when = I ran the wrapper config-test command. Am I doing something wrong? Regards, Scott Robinson ------=_NextPart_000_00DD_01BF73B9.C9FC91A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have just finished installing = majordomo and was=20 doing the last test and I got nothing from typing in the command.  = I=20 checked the processes running and did not find the majordomo daemon=20 running.  When I tried to run it I got an error message.  It = told me=20 that I installed it fine when I ran the wrapper config-test = command.  Am I=20 doing something wrong?
 
Regards,
 
Scott = Robinson
------=_NextPart_000_00DD_01BF73B9.C9FC91A0-- From majordomo-users-owner Thu Feb 10 13:27:13 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA21025; Thu, 10 Feb 2000 13:20:41 -0800 (PST) Received: from riverside1.nobaloney.net (riverside1.nobaloney.net [209.250.124.146]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id NAA21012 for ; Thu, 10 Feb 2000 13:20:30 -0800 (PST) Received: from jc300 ([192.168.0.101]) by riverside1.nobaloney.net with SMTP (Mailtraq/1.1.4.1066) id RVRS75973EA14 for majordomo-users@greatcircle.com; Thu, 10 Feb 2000 13:36:18 -0800 Message-Id: <4.2.0.58.20000210133231.009753a0@192.168.0.67> X-Sender: c1000010#mail.nobaloney.net@192.168.0.67 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 10 Feb 2000 13:36:18 -0800 To: majordomo-users@greatcircle.com From: Jeff Lasman Subject: Re: Fwd: In-Reply-To: <20000209181859.16165.qmail@web3601.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Hops: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Usually when this happens it's because someone has figured out how to send to an outgoing alias address. Setting the sender to the list owner is done by Majordomo. Even if YOU send a post through majordomo as the list-owner it still requires the password for a moderated list. Read the Majordomo FAQ; specifically look at Hope this helps . Jeff At 10:18 AM 2/9/00 -0800, you wrote: >Hi! > >I'm not sure if this question is appropriate for this >list. If not, I would appreciate it if you would guide >me in the right direction. > >I've got a moderated listserv. Someone sent >unsolicited mail to the list, set the list owner as >the sender, and bypassed the approval. > >How do I prevent this from happening again? -- Jeff Lasman From majordomo-users-owner Thu Feb 10 13:42:13 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA21090; Thu, 10 Feb 2000 13:25:51 -0800 (PST) Received: from riverside1.nobaloney.net (riverside1.nobaloney.net [209.250.124.146]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id NAA21083 for ; Thu, 10 Feb 2000 13:25:45 -0800 (PST) Received: from jc300 ([192.168.0.101]) by riverside1.nobaloney.net with SMTP (Mailtraq/1.1.4.1066) id RVRS75973EA28 for majordomo-users@greatcircle.com; Thu, 10 Feb 2000 13:41:30 -0800 Message-Id: <4.2.0.58.20000210134053.0097f510@192.168.0.67> X-Sender: c1000010#mail.nobaloney.net@192.168.0.67 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 10 Feb 2000 13:41:29 -0800 To: majordomo-users@greatcircle.com From: Jeff Lasman Subject: Re: Banned users. In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Hops: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 12:42 AM 2/10/00 -0500, you wrote: >On Wed, 9 Feb 2000, Bob wrote: > > > Is it possible to only moderate one address on a open list. What I would > > like to do is review mail from one address and then approve it and send it > > on. Also, should taboo headers in the list.config also be edited? > >Per list, editing the taboo_headers for the list is the way to go. I don't think that's what he asked. I think he means can he set individual users to be moderated. The answer is: not without patching majordomo. Jeff -- Jeff Lasman From majordomo-users-owner Thu Feb 10 13:57:13 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA21058; Thu, 10 Feb 2000 13:23:51 -0800 (PST) Received: from riverside1.nobaloney.net (riverside1.nobaloney.net [209.250.124.146]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id NAA21050 for ; Thu, 10 Feb 2000 13:23:45 -0800 (PST) Received: from jc300 ([192.168.0.101]) by riverside1.nobaloney.net with SMTP (Mailtraq/1.1.4.1066) id RVRS75973EA1E for majordomo-users@greatcircle.com; Thu, 10 Feb 2000 13:39:24 -0800 Message-Id: <4.2.0.58.20000210133643.0097a930@192.168.0.67> X-Sender: c1000010#mail.nobaloney.net@192.168.0.67 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 10 Feb 2000 13:39:24 -0800 To: majordomo-users@greatcircle.com From: Jeff Lasman Subject: Re: Pricing for hosting lists In-Reply-To: References: <086301bf7307$17f10520$654494ce@srnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Hops: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 02:52 PM 2/9/00 -0500, you wrote: >I charge $10/month/list, in 6-month increments. OR, a flat-rate of >$100/year/list when paid upfront ($20 savings). this applies whether it's >an open or closed, moderated or unmoderated, discussion or distribution >list. So you don't care about how many users or how much traffic? >And, the price is the same no matter which of my 30+ domains they >want to use for their list. We allow people to use either their own domain OR . We're very sensitive about our domain names and what they're used for. For exmaple, NONE of our ISP customers use ; that's reserved for us. Our ISP customers can use (stands for "Southern California Internet Exchange) or their own domain name. Jeff -- Jeff Lasman From majordomo-users-owner Thu Feb 10 14:12:13 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA21156; Thu, 10 Feb 2000 13:31:18 -0800 (PST) Received: from nms01 (nms01.srv.hcvlny.cv.net [167.206.112.64]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA21149 for ; Thu, 10 Feb 2000 13:31:10 -0800 (PST) Received: from s1.nassau.cv.net (s1.optonline.net [167.206.112.6]) by nms01 (8.9.3+Sun/8.9.1) with ESMTP id QAA25892 for ; Thu, 10 Feb 2000 16:46:51 -0500 (EST) Received: from office (hicks13-83.optonline.net [167.206.13.83]) by s1.nassau.cv.net (8.9.1/8.9.1) with SMTP id QAA29725 for ; Thu, 10 Feb 2000 16:46:53 -0500 (EST) Reply-To: From: "Wayne Spivak" To: Subject: RE: Abort, due to invalid return addess v 1.94.5 Date: Thu, 10 Feb 2000 16:45:09 -0500 Message-ID: <004501bf7410$1ab288b0$530dcea7@office.optonline.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <015101bf7264$6db90000$530dcea7@office.optonline.net> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Importance: Normal Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk 2nd try.... I patched 1.94.4 to 19.94.5. I keep getting these: majordomo@foo.org: root (Cron Daemon) is not a valid return address. When I run this command from Cron: echo mkdigest psml-digest psml-digest.admin | sendmail -froot@foo.org majordomo@foo.org I've put resend_host = foo.org, but to no avail. Any ideas? Wayne Spivak SBA * Consulting® - Systems for Business & Accounting SBA.NET.WEB® - Internet & World Wide Web Consulting 2711 Bellmore Avenue, Bellmore, New York 11710-4319 Tel: 516-221-3306 Fax: 516-221-7129 mailto:WSpivak@sbanetweb.com http://www.sbanetweb.com or http://www.sbaconsulting.com http://guide.sbanetweb.com -- Guide to Computer Vendors(TM) http://guide.sbanetweb.com/library.html -- Published Articles Join the Internet Society -- http://www.isoc.org From majordomo-users-owner Thu Feb 10 17:26:33 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA23061; Thu, 10 Feb 2000 17:02:48 -0800 (PST) Received: from www.guldennet.nl (guldennet.nl [195.81.35.224]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA23054 for ; Thu, 10 Feb 2000 17:02:37 -0800 (PST) Received: from guldennet.nl (c18752226.telekabel.chello.nl [212.187.52.226]) by www.guldennet.nl (8.9.3/8.9.3) with ESMTP id CAA00038; Fri, 11 Feb 2000 02:17:29 +0100 Message-ID: <38A36330.9524671@guldennet.nl> Date: Fri, 11 Feb 2000 02:17:36 +0100 From: Rogier Maas Reply-To: icarus@guldennet.nl Organization: Stichting Het GuldenNet - www.guldennet.nl X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 Subject: ENTIRELY OFF-TOPIC, but please have a minute to Inline-forward this. Thanks. Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I wanted to say I was terribly sorry for sending this E-Mail, but since I'm not, I won't say it. I think this is also what mailinglists are meant for (reaching lots of people), as long as this doesn't become a habit. I only send this E-Mail because I feel myself personally attached to the subject of this call for help. I'm usually against mass-mailing, but hey. For once. I'm sorry for any inconvieniances I've caused by sending this, but please bare in mind that this might be for a good cause. Thank You (forward only the following) ----------- On the 28th of October 1999, a young 12-year old girl's future was completely shattered. She was raped and almost stabbed to death. She sustained multiple stab wounds in the back, chest and stomach as well as the face. One of the stabs she received penetrated her spine and she is now paralysed for life. This little girl is my cousin. I went to see her in hospital on Friday. When I saw her, she was lying on her side and all I could see was her stitched face. Because her whole little body was riddled with stab wounds, she is unable to find a comfortable position. When I asked her how she was doing, she whispered: " I am sore, I am sore". She asked her mother to turn her over on the other side, and as I helped her mother to do so, I saw that her whole throat was covered in the most terrible blue and deep purple bruises. Her rapist tried to shut her up when she was screaming. When that did not help, he tried to stab her to death. All I can say is thank God she is alive. The reason for this email is plain and simple. The South African judicial system is up to muggets, and corruption and discrimination is rife. No justice will be brought to this case. Give it a couple of years, and the rapist (who was caught I might add) will be out on parole in a couple of months. In the meantime, one beautiful little girl's life has been changed. Not only does she have to live with this memory, but she has to be reminded of it every single day in the form of her paralysis. The South African government wants to implement something called chemical castration, where they inject men with a chemical that decreases their sex drive. This is NOT good enough. Rape is not in the male member, but in the male mind. I know this happens to women all over the world on an hourly basis, but this time it has hit too close to home and I CANNOT and I repeat CANNOT stand by and do nothing about it. Therefore I would like your help in signing this petition for a harsher sentence for rape. Life imprisonment might be a good suggestion as ironically enough, prisoners do not tolerate child molesters and rapists, and because of this, they have their own "system of punishment" in prison. I want this man to go through agony for the rest of his life.I want him to be reminded of the pain that this little girl has to go through for the rest of HER life. Why should this animal deserve ANY better? Please forward this to as many people as you can. The more signatures we have from all over the world, the better our chances that someone in power might listen. If we don't do something about it, some or other time it might it too close to your home... Also, please keep me updated by regularly sending back a list to me, so I can keep record of our progress. I sincerely appreciate your help and support in this matter, and so do Luke Homan and her mother. EVERY 100th PERSON PLEASE FORWARD THE LIST BACK TO Nikki Botha, Johannesburg, RSA, e-mail address: Nikki@comnet.co.za Please make a new list (by Inline-forwarding or copying and pasting) and forward that again to people you know. Kindly remove the headers and footers, as this keeps the list tidy and does not block the on-line system with unnecessary detail. Thank you and GOD BLESS all those who add their names here and to all those who have sadly been victims of violence - OUR PRAYERS ARE WITH YOU. WE, THE UNDERSIGNED DO HEREBY PETITION THE GOVERNMENT TO DO SOMETHING ABOUT THE CRIME RATE IN OUR COUNTRY, PARTICULARLY RAPE! 1 Melanie Benson, JHB. 2 Pam Immelman, JHB. 3 Sheralynn Anderson, JHB 4 Elisabeth Ambros, JHB 5 Natasha Momberg, JHB 6 Heather Odendaal, NLP 7 Lisa Cochrane, JHB 8 Gia Bischofberger, JHB 9 Andrea Gavan, JHB 10 SHELLEY PRETORIUS-JHB 11 Amanda Clifford 12 Bernita Noble - JHB 13 Natasha Williams - JHB 14 Karen Pires - JHB 15 Vanessa Hutcheon - JHB 16 Tarren Coetzee - CT 17 Lisa Taylor - CPT 18 Natalie Lodewyk - CPT 19 Kim Franks-CPT> 20 Belinda Fish - CPT 21 Valerie Small - Cape Town 22 Renee Olivier - Cape Town 23 Zelda du toit - CPT 24 Liezl Grobler - CPT 25 Cindy Haupt - cpt 26 Louisa v. Houwer - JHB 27 Tracy Haylett - JHB 28 Michelle Schwegmann-JHB 29 Catherine Stander - JHB 30 Lulu Greyling 31 Marla Naidoo - The Netherlands 32 Arma Bertuso - Philippines 33 Leo E. Parreqo - Phil. 34 Rowena Parreqo- Phil. 35 Riz Pulumbarit - Philippines 36 Vernie Pulumbarit - Philippines 37 Andy Adan - Philippines 38 Menchu Adan - Philippines 39 Lennie S. Gunda - Philippines 40 Karen L. Hilado - Philippines 41 George V. Villaruz - Philippines 42 Grace Buendia - Philippines 43 Raquel Pasaraba - Philippines 44 Randale Pasaraba - Philippines 45 Vicky Morales - Philippines 46 Ross Morales - Philippines 47 Nicky Galedo - Philippines 48 Mark Alupay - Philippines 49 Sheila Roxas - Philippines 50 Loida Mena - Philippines 51 Let Catalan - Philippines 52 Vic Roxas - Philippines 53 Mike Piccio - Philippines 54 Jerry Bautista - Philippines 55 Bernard Requerme - Philippines 56 Lilian Requerme - Philippines 57 Bea Louise Requerme - Philippines 58 Ricky Mayani - Saint Maarten NA 59 Umesh Chhatlani - Saint Maarten NA 60 Neetu Shamdasani - India 61 Manju Hariramani - St. Lucia 62 Kalpana Vaswani - Barbados 63 Gareth Bowman - United Kingdom 64 Michelle de Caires - Barbados 65 Tracey Garcia - Barbados 66 Rachel Inniss - Barbados 67 Sarah Inniss - Barbados 68 Samantha Springer- Barbados 69 Broderick Taylor - Jamaica 70 Lee-Ann Simmons - Barbados 71 Cheryl Walrond - Barbados 72 Mariette Simmons - Barbados 73 Gina Greaves - Barbados 74 Navendra Ramnarace - Barbados 75 Barry Mustor -Barbados 76 Angelique Bjerkhamn-Barbados 77 Monique Archer - Barbados 78 Ralph Williams - Barbados 79 Wendy williams - Barbados 80 Neomi Weir - Barbados 81 Stuart Williams - Barbados 82 Audrey Williams - Barbados 83 Carolyn Carrington - Barbados 84 Stephen Carrington - Barbados 85 Adrian Z Tabona - Malta 86 Cliff Agius - Malta 87 Martin Buhagiar - Malta 88 Claudette Bonello - Malta 89 James Handyside - Malta 90 Franco Galea - Malta 91 Kathy Josevski-Canada 92 Pero Businoksi - Canada 93 Jennifer Lianne Hall - Canada 94 Charlene Mendes - Canada 95 Krista Lopes - Canada 96 Thaddea Goddard-Canada 97 Elise Goddard -Canada 98 Heidi Pinter - Canada 99 Kimberley Leppik - Canada 100 Mohamad Khan - Canada 101 David Pritchard - Canada 102 Bryan Uyede - Canada 103 Vincent Pun - Canada 104 Andrew Wong-Canada 105 Eva Li - Canada 106 Rebecca Chan - Canada 107 Ellen Jewett - Canada 108 Dina Zivanovic-yugoslavia 109 Sean McConnell - Canada 110 Richard Rubenstein - Canada 111 Shelby Kagan - Canada 112 Matt Diamond - Canada 113.Julia Duong-Canada 114.Eric Kubicki- Canada 115.shane fine- Canada 116. Elisha Chesler-Canada 117. Daniel Vivat - Canada 118. Julia Leung - Canada 119. Margot - nederland 120. Miriam - Nederland 121. Viper - Holland 122. Leroy - Netherlands 123. Mark van Liefland-Netherlands 124. Arief Huehn-Netherlands 125. Jean-Paul Bregonje - Netherlands 126. Jordy Kersten - Netherlands 127. Bas van Duren - Netherlands 128 Tim Lely - netherlands 129 Mick bouman- Netherlands 130 Syafei Lutter- Netherlands 130 Chiron Limjoco - Netherlands 131 Joey Stork-Netherlands 132 Mémé Hazelhoff - The Netherlands 133 John Vijver - The Netherlands 134 Arjan de Jong - The Netherlands 135 Alex v. Meerendonk - Netherlands 136 Johan Klaassen - The Netherlands 137 Kim Larsen - Denmark 138 PJ W - ontario 139 Summit Sud - Ontario 140 Alrick Scott - Canada 141 Dominic - Netherlands 142 DJ -Netherlands 143 Joris Aurik - Netherlands 144 mOnTEuR - Netherlands 145 Elegy(Fly Guy) - Netherlands 146 Brian Hollander - Netherlands 147 Laura- The Netherlands 148 Telemarkie - The Netherlands, Lisse ZH 149 Lotti de Jong - The Netherlands 150 Rogier Maas - The Netherlands From majordomo-users-owner Thu Feb 10 18:55:52 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA23869; Thu, 10 Feb 2000 18:29:14 -0800 (PST) Received: from zoso.net (zoso.net [204.122.18.193]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA23862 for ; Thu, 10 Feb 2000 18:29:04 -0800 (PST) Received: from localhost (mirader@localhost) by zoso.net (8.9.3/8.9.3) with ESMTP id SAA00623; Thu, 10 Feb 2000 18:45:16 -0800 Date: Thu, 10 Feb 2000 18:45:16 -0800 (PST) From: Bob To: Jeff Lasman cc: majordomo-users@GreatCircle.COM Subject: Re: Banned users. In-Reply-To: <4.2.0.58.20000210134053.0097f510@192.168.0.67> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 10 Feb 2000, Jeff Lasman wrote: > At 12:42 AM 2/10/00 -0500, you wrote: SNIP > >Per list, editing the taboo_headers for the list is the way to go. > > I don't think that's what he asked. I think he means can he set individual > users to be moderated. The answer is: not without patching majordomo. The reason I need to be able to bounce one certain email is, I have a subscriber from ix.netcom.com using netcomplete 4.0 and every time she posts to the list she has a trail of ^@^@^@^@^@^@^@^@^@ at the end of the msg body on every post. She says she has no sig file, and that these characters just appear. What these characters do; everytime a digest goes out, it gets trunicated where these characters appear, the digests stops at the end of her post causing only certain people not to receive the full digest. Can anyone help with this? :) Bob From majordomo-users-owner Thu Feb 10 19:44:33 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA24569; Thu, 10 Feb 2000 19:28:49 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA24554 for ; Thu, 10 Feb 2000 19:28:43 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id WAA29075; Thu, 10 Feb 2000 22:43:54 -0500 (EST) Date: Thu, 10 Feb 2000 22:43:54 -0500 (EST) From: "Bill Casti (System Admin)" To: Jeff Lasman cc: majordomo-users@GreatCircle.COM Subject: Re: Pricing for hosting lists In-Reply-To: <4.2.0.58.20000210133643.0097a930@192.168.0.67> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 10 Feb 2000, Jeff Lasman wrote: > At 02:52 PM 2/9/00 -0500, you wrote: > > >I charge $10/month/list, in 6-month increments. OR, a flat-rate of > >$100/year/list when paid upfront ($20 savings). this applies whether it's > >an open or closed, moderated or unmoderated, discussion or distribution > >list. > > So you don't care about how many users or how much traffic? Nope, don't care in the list. Convince me why I should. > >And, the price is the same no matter which of my 30+ domains they > >want to use for their list. > > We allow people to use either their own domain OR . We're > very sensitive about our domain names and what they're used for. For > exmaple, NONE of our ISP customers use ; that's > reserved for us. Our ISP customers can use (stands for > "Southern California Internet Exchange) or their own domain name. Yep, they can use their own domain names here, too. There's a $25/year domain hosting fee for the administrative overhead it entails. Why are you being so hostile? Bill From majordomo-users-owner Thu Feb 10 19:56:59 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA24549; Thu, 10 Feb 2000 19:28:29 -0800 (PST) Received: from queernet.queernet.org (queernet.queernet.org [170.1.118.14]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA24542 for ; Thu, 10 Feb 2000 19:28:25 -0800 (PST) Received: from localhost (rogerk@localhost) by queernet.queernet.org (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e1B3iAi28544 Date: Thu, 10 Feb 2000 19:44:05 -0800 (PST) From: "Roger B.A. Klorese" To: Jeff Lasman cc: majordomo-users@GreatCircle.COM Subject: Re: Banned users. In-Reply-To: <4.2.0.58.20000210134053.0097f510@192.168.0.67> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 10 Feb 2000, Jeff Lasman wrote: > >On Wed, 9 Feb 2000, Bob wrote: > > > > > Is it possible to only moderate one address on a open list. What I would > > > like to do is review mail from one address and then approve it and send it > > > on. Also, should taboo headers in the list.config also be edited? > > > >Per list, editing the taboo_headers for the list is the way to go. > > I don't think that's what he asked. I think he means can he set individual > users to be moderated. The answer is: not without patching majordomo. Let's spell it out more clearly, then. Putting: /^from:.*moron@clueless.net/i in the taboo_headers section of a list's config causes their posts to be trapped by the taboo checks and bounced to the moderator. In what way is that NOT equivalent to "moderating a specific user", other than the words that are printed in the subject line of the referred post? -- ROGER B.A. KLORESE rogerk@QueerNet.ORG urgent: rogerk-page@QueerNet.ORG PO Box 14309 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 Feb 11 05:31:06 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA02757; Fri, 11 Feb 2000 05:05:58 -0800 (PST) Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.59]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id FAA02750 for ; Fri, 11 Feb 2000 05:05:51 -0800 (PST) Received: (qmail 27990 invoked by uid 0); 11 Feb 2000 13:21:51 -0000 Received: from queequeg.clarkson.edu (128.153.28.83) by mail.clarkson.edu with SMTP; 11 Feb 2000 13:21:51 -0000 Date: Fri, 11 Feb 2000 08:21:51 -0500 (EST) From: "Brian T. Huntley" To: majordomo-users@greatcircle.com Subject: Redundant mj servers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all.... Has anyone had any experience w/ setting up redundant mj servers? I would like to do this, then DNS round-robin them to help distribute load a bit. I have the machines which an access a common filespace, into which I was thinking of placing everything except the MJ executables, which would reside on local disk... Any thoughts on this? TIA! - Best regards, Brian +-----------------------------------------------------------------------+ | Brian T. Huntley Systems and Network Engineer | | Campus Information Services, Clarkson University | | Ph/FAX: 315.268-2292/6570 | | bth@clarkson.edu www.clarkson.edu/cis | +-----------------------------------------------------------------------+ UNIX *is* user friendly. It's just selective about who its friends are. PGP Public Key available. finger bth@clarkson.edu From majordomo-users-owner Fri Feb 11 07:46:42 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA04077; Fri, 11 Feb 2000 07:24:53 -0800 (PST) Received: from riverside1.nobaloney.net (riverside1.nobaloney.net [209.250.124.146]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id HAA04066 for ; Fri, 11 Feb 2000 07:24:31 -0800 (PST) Received: from jc300 ([192.168.0.101]) by riverside1.nobaloney.net with SMTP (Mailtraq/1.1.4.1066) id RVRS76153EA64 for majordomo-users@greatcircle.com; Fri, 11 Feb 2000 07:40:09 -0800 Message-Id: <4.2.0.58.20000211073904.0095fad0@192.168.0.67> X-Sender: c1000010#mail.nobaloney.net@192.168.0.67 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 11 Feb 2000 07:40:07 -0800 To: majordomo-users@greatcircle.com From: Jeff Lasman Subject: Re: Banned users. In-Reply-To: References: <4.2.0.58.20000210134053.0097f510@192.168.0.67> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Hops: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 07:44 PM 2/10/00 -0800, you wrote: >Let's spell it out more clearly, then. > >Putting: > > /^from:.*moron@clueless.net/i > >in the taboo_headers section of a list's config causes their posts to be >trapped by the taboo checks and bounced to the moderator. In what way is >that NOT equivalent to "moderating a specific user", other than the words >that are printed in the subject line of the referred post? I never saw the tree, Roger; I was looking at the forest. Sorry about that. You're right of course, and it's a good way to moderate her out of existence. Jeff -- Jeff Lasman From majordomo-users-owner Fri Feb 11 08:46:10 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA04739; Fri, 11 Feb 2000 08:29:56 -0800 (PST) Received: from riverside1.nobaloney.net (riverside1.nobaloney.net [209.250.124.146]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id IAA04732 for ; Fri, 11 Feb 2000 08:29:49 -0800 (PST) Received: from jc300 ([192.168.0.101]) by riverside1.nobaloney.net with SMTP (Mailtraq/1.1.4.1066) id RVRS76163EA6E; Fri, 11 Feb 2000 08:45:33 -0800 Message-Id: <4.2.0.58.20000211074120.00960390@192.168.0.67> X-Sender: c1000010#mail.nobaloney.net@192.168.0.67 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 11 Feb 2000 08:45:30 -0800 To: majordomo-users@greatcircle.com From: Jeff Lasman Subject: Re: Pricing for hosting lists Cc: "Bill Casti (System Admin)" In-Reply-To: References: <4.2.0.58.20000210133643.0097a930@192.168.0.67> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Hops: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 10:43 PM 2/10/00 -0500, you wrote: >On Thu, 10 Feb 2000, Jeff Lasman wrote: > > > So you don't care about how many users or how much traffic? > >Nope, don't care in the list. Convince me why I should. Not my intention. Really. I was just asking what you did, to be sure to have it clarified in my mind. Pricing Majordomo lists has always been a mystery for me; we charge differently for announcement lists and discussion lists, and we charge based on list size. Here's our price list, quite imperfect, I know, and certainly subject to change as more people reply to this thread and give us all some good ideas: Announcement List Setup: $15 Announcement List up to 500 email addresses: $5/month Announcement List up to 1000 email addresses: $10/month Discussion List Setup: $25 Discussion List up to 20 msgs/day up to 200 addressees: $5/month Discussion List up to 20 msgs/day up to 500 addressees: $10/month Discussion List up to 20 msgs/day up to 1000 addressees: $20/month Unlimited Discussion Setup: $25 Unlimited Discussion List up to 200 addressees: $10/month Unlimited Discussion List up to 400 addressees: $20/month Unlimited Discussion List up to 600 addressees: $30/month Unlimited Discussion List up to 800 addressees: $40/month Unlimited Discussion List up to 1000 addressees: $50/month Moving a pre-existing Mailing List: $25 (in addition to setup) (includes moving addresses and archives where available) Web-based Mailing List Administration: $10/setup, $2/month Web-based Mailing List Signup Page: $10/setup, $2/month Mailing List Custom Domain Return Address: $10/setup $2/month Mailing List Archive Storage $10/setup $5/month/10 megabytes Web-based Mailing List Archive Retrieval, $10/setup $2/month Web-based Archive Search Engine, $10/setup $2/month Additionally we limit NEW lists (with no past history) to a growth rate of 100 new users per week; that tends to keep spammers from using our Majordomo services . We also show on our price list (but we've never yet had to charge) for spam-related problems: Subscriber-caused Received spam complaint: $10/each Subscriber-sent outgoing spam: $5/each Subscriber-caused interruption of Internet service to us: $250/hour No charge extra for moderation, but a digest is priced as a separate list. While not trying to convince you of anything, let me give you some of my rationale: Pricing in any field is an arcane art. It was easiest when I was in the blue jean business. We marked up everything 100 + 10% to the stores, they marked it up another 100% + 10% percent ($12 cost, so we sold it at $26.40, the store sold it at $58). Now you see why stores can hold clearance sales cutting prices in half and still make money. Hardest I've ever done was in the typesetting business in the late 70s. No one knew how to price typesetting as it evolved from hot-metal to film and computers. We told our customers we were charging them $50/hour (pretty good in those days) for custom advertising-agency quality typography (custom letter-fit, copy-counting, etc.) but in reality we had a computer (an old 8080-based processor as I recall) doing most of the work, and we really billed the computer at $100/hour. We were a lot cheaper for finished jobs than the old-fashioned houses doing it manually at $120/hour, so we got a lot of business. We also picked up a good bit of spare change every month or so from recycled silver from the film. Somewhere in the middle was the computer-reseller business. We bought the cheapest parts, slapped the machine together will free labor (got kids from high-schools and the school-district would actually pay their salary under various inner-city vocational programs), make a minimum markup, move a lot of boxes, and eventually go broke . Personally, I consider it important to charge in some way for storage, and for the amount of usage, because we're actually in the list business; it's not just an afterthought. Therefore it needs to pay for itself and return a profit. A few large lists can eat up system cycles and bandwidth in a hurry. (And yes, I've been in a few businesses over the years, starting as an entrepreneur when still in High School; I'm now in my 50s.) >Yep, they can use their own domain names here, too. There's a $25/year >domain hosting fee for the administrative overhead it entails. About the same as ours, as you can see from the above. >Why are you being so hostile? I didn't realize I was. I think I just came across as hostile, because I asked questions and didn't post my own prices. I apologize for that; it's been hectic the past few days (still is). But I don't mind sharing my rationale. I do apologize for any lack of etiquette/netiquette on my part. In my rushed state, I didn't realize I was doing it. Jeff -- Jeff Lasman From majordomo-users-owner Fri Feb 11 09:31:09 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA05159; Fri, 11 Feb 2000 09:09:07 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA05152 for ; Fri, 11 Feb 2000 09:09:00 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id MAA06948; Fri, 11 Feb 2000 12:24:16 -0500 (EST) Date: Fri, 11 Feb 2000 12:24:15 -0500 (EST) From: "Bill Casti (System Admin)" To: Jeff Lasman cc: majordomo-users@greatcircle.com Subject: Re: Pricing for hosting lists In-Reply-To: <4.2.0.58.20000211074120.00960390@192.168.0.67> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Too much bookkeeping for me to deal with. If this was my full-time job, I might consider an infinitely-graduated scale like that, but it's not. I don't need to make a profit or very much of one, just enough to cover the T1 and occasional software and hardware upgrades, and those are all minimal. So, flat rates are simple and easy for everyone to understand. Regards. Bill ============================================================================= Opinions expressed are entirely mine, not necessarily those of my employer. ----------------------------------------------------------------------------- Bill Casti, CQA Email: help@quality.org - Domain Owner, QUALITY.ORG Pager: 1 800 604 6149 - List Moderator, "TQM in Manufacturing and Service Industries" - President, Associated Quality Consultants, Inc., Reston VA - Immediate Past Chair and E-Media Chairman American Society for Quality (ASQ), Chapter 0511, Northern VA - Senior Administrator, UNIX Systems & Security Bell Atlantic Federal Systems Phone: 202 263 5022 Network Operations Cell: 703 244 0497 1710 H Street, NW Text Pages: 7032440497@message.bam.com Washington DC 20006 ----------------------------------------------------------------------------- Self-service list subscription service at www.quality.org/cgi-bin/majordomo See http://www.quality.org/lists/lists_at_quality.org.html for the List of Lists supported at QUALITY.ORG ----------------------------------------------------------------------------- My PGP Public Key is at: www.casti.com/casti/quire-rsa.asc ----------------------------------------------------------------------------- QUALITY RESOURCES ONLINE at: http://www.quality.org ONLINE RECOVERY RESOURCES at: http://www.recovery.org ============================================================================= On Fri, 11 Feb 2000, Jeff Lasman wrote: > At 10:43 PM 2/10/00 -0500, you wrote: > > >On Thu, 10 Feb 2000, Jeff Lasman wrote: > > > > > So you don't care about how many users or how much traffic? > > > >Nope, don't care in the list. Convince me why I should. > > Not my intention. Really. I was just asking what you did, to be sure to > have it clarified in my mind. Pricing Majordomo lists has always been a > mystery for me; we charge differently for announcement lists and discussion > lists, and we charge based on list size. > > Here's our price list, quite imperfect, I know, and certainly subject to > change as more people reply to this thread and give us all some good ideas: > > Announcement List Setup: $15 > Announcement List up to 500 email addresses: $5/month > Announcement List up to 1000 email addresses: $10/month > > Discussion List Setup: $25 > Discussion List up to 20 msgs/day up to 200 addressees: $5/month > Discussion List up to 20 msgs/day up to 500 addressees: $10/month > Discussion List up to 20 msgs/day up to 1000 addressees: $20/month > > Unlimited Discussion Setup: $25 > Unlimited Discussion List up to 200 addressees: $10/month > Unlimited Discussion List up to 400 addressees: $20/month > Unlimited Discussion List up to 600 addressees: $30/month > Unlimited Discussion List up to 800 addressees: $40/month > Unlimited Discussion List up to 1000 addressees: $50/month > > Moving a pre-existing Mailing List: $25 (in addition to setup) > (includes moving addresses and archives where available) > > Web-based Mailing List Administration: $10/setup, $2/month > Web-based Mailing List Signup Page: $10/setup, $2/month > Mailing List Custom Domain Return Address: $10/setup $2/month > Mailing List Archive Storage $10/setup $5/month/10 megabytes > Web-based Mailing List Archive Retrieval, $10/setup $2/month > Web-based Archive Search Engine, $10/setup $2/month > > Additionally we limit NEW lists (with no past history) to a growth rate of > 100 new users per week; that tends to keep spammers from using our > Majordomo services . > > We also show on our price list (but we've never yet had to charge) for > spam-related problems: > > Subscriber-caused Received spam complaint: $10/each > Subscriber-sent outgoing spam: $5/each > Subscriber-caused interruption of Internet service to us: $250/hour > > No charge extra for moderation, but a digest is priced as a separate list. > > While not trying to convince you of anything, let me give you some of my > rationale: > > Pricing in any field is an arcane art. It was easiest when I was in the > blue jean business. We marked up everything 100 + 10% to the stores, they > marked it up another 100% + 10% percent ($12 cost, so we sold it at $26.40, > the store sold it at $58). Now you see why stores can hold clearance sales > cutting prices in half and still make money. > > Hardest I've ever done was in the typesetting business in the late 70s. No > one knew how to price typesetting as it evolved from hot-metal to film and > computers. We told our customers we were charging them $50/hour (pretty > good in those days) for custom advertising-agency quality typography > (custom letter-fit, copy-counting, etc.) but in reality we had a computer > (an old 8080-based processor as I recall) doing most of the work, and we > really billed the computer at $100/hour. We were a lot cheaper for > finished jobs than the old-fashioned houses doing it manually at $120/hour, > so we got a lot of business. We also picked up a good bit of spare change > every month or so from recycled silver from the film. > > Somewhere in the middle was the computer-reseller business. We bought the > cheapest parts, slapped the machine together will free labor (got kids from > high-schools and the school-district would actually pay their salary under > various inner-city vocational programs), make a minimum markup, move a lot > of boxes, and eventually go broke . > > Personally, I consider it important to charge in some way for storage, and > for the amount of usage, because we're actually in the list business; it's > not just an afterthought. Therefore it needs to pay for itself and return > a profit. A few large lists can eat up system cycles and bandwidth in a hurry. > > (And yes, I've been in a few businesses over the years, starting as an > entrepreneur when still in High School; I'm now in my 50s.) > > >Yep, they can use their own domain names here, too. There's a $25/year > >domain hosting fee for the administrative overhead it entails. > > About the same as ours, as you can see from the above. > > >Why are you being so hostile? > > I didn't realize I was. I think I just came across as hostile, because I > asked questions and didn't post my own prices. I apologize for that; it's > been hectic the past few days (still is). But I don't mind sharing my > rationale. > > I do apologize for any lack of etiquette/netiquette on my part. In my > rushed state, I didn't realize I was doing it. > > Jeff > > -- > Jeff Lasman > > From majordomo-users-owner Fri Feb 11 10:31:16 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA05887; Fri, 11 Feb 2000 10:09:14 -0800 (PST) Received: from dax.vicorp.com (dax.vicorp.com [207.139.252.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA05880 for ; Fri, 11 Feb 2000 10:09:06 -0800 (PST) Received: from bboulding.vicorp.com (bboulding.vicorp.com [207.139.252.20]) by dax.vicorp.com (8.9.1a/8.9.1) with SMTP id NAA10832 for ; Fri, 11 Feb 2000 13:25:03 -0500 (EST) Reply-To: From: "Bruce Boulding" To: Subject: RE: Redundant mj servers Date: Fri, 11 Feb 2000 13:25:47 -0500 Message-ID: <000501bf74bd$6a541700$14fc8bcf@bboulding.vicorp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 In-Reply-To: Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk set majordomo-users digest bruce.boulding@vicorp.com From majordomo-users-owner Fri Feb 11 11:04:30 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA06317; Fri, 11 Feb 2000 10:41:18 -0800 (PST) Received: from bialystok.tpsa.pl (sask.bialystok.tpsa.pl [194.204.183.253]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA06310 for ; Fri, 11 Feb 2000 10:41:09 -0800 (PST) Received: from an (pa88.bialystok.ppp.tpnet.pl [212.160.61.88]) by bialystok.tpsa.pl (8.8.8/8.8.4) with ESMTP id TAA05677 for ; Fri, 11 Feb 2000 19:59:16 +0100 Message-Id: <200002111859.TAA05677@bialystok.tpsa.pl> From: "Andrzej Kasperowicz" To: Majordomo-Users@greatcircle.com Date: Fri, 11 Feb 2000 19:58:52 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Restrict-post facility and mungedomain; headers in approved messages. X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi! I have a problem with restrict_post facilty. For example a message sent to my list chemfan by ckingsbu@unlserve.unl.edu has been bounced because the address didn't match the member list. He's on the list of subscribers as ckingsbu@unlinfo.unl.edu . Mungedomain option is set to 'yes' but apparently it doesn't work in that kind of situation. Can you see any good solution of the problem? Maybe you could include it in the next ver. of majordomo to mungedomain domains also when using restrict_post facility. I wouldn't be happy to approve all the time that kind of messages or to ask majordomo-owner to add that kind of addresses to a separate additional file. Actually I often may encounter persons who use various machines, so that I would have to change their addresses each time they send a mail to the list - that's rediculous. I told majordomo-owner that if it's going to be like that all the time I will cancel that restrict post facility, but then he threatened that he will ask me to host the list elsewhere. :( Besides, when I approve a message to send, it is then send with my name in the header, not the original sender - are you going to do something about this problem in the future? I'm using pegasus mail to resend approved messages. I would be also grateful if you could suggest me a free bounce filter, which could deal automatically with bounced messages unsubscribing appropriate e-mail addresses (would be nice if that option would co-operate with mungedomain, too). Cheers! Andrzej Kasperowicz | There is but one way to avoid mistakes; chemfan & minerals list-owner | to do nothing. This however, maybe the andyk@termisoc.org | greatest mistake of all... http://www.termisoc.org/~andyk/ | Albert Szent-Gyorgy From majordomo-users-owner Fri Feb 11 12:17:53 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA07129; Fri, 11 Feb 2000 11:56:43 -0800 (PST) Received: from chinet.chinet.com ([209.219.112.20]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA07122 for ; Fri, 11 Feb 2000 11:56:37 -0800 (PST) Received: from localhost (ahk@localhost) by chinet.chinet.com (8.9.3/8.9.3) with ESMTP id OAA18358 for ; Fri, 11 Feb 2000 14:12:40 -0600 Date: Fri, 11 Feb 2000 14:12:40 -0600 (CST) From: "Adam H. Kerman" To: majordomo-users@GreatCircle.COM Subject: trapping null subjects In-Reply-To: <4.2.0.58.20000211073904.0095fad0@192.168.0.67> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Occassionally, the name of the header following the Subject gets appended as text in the Subject header. Either the message was sent with a null Subject or something else got screwed up. The list owner insists on adding tag text at the head of the Subject. Could this be tripping up the headers? To prevent this from happening, I'd like to trap any messages with a null Subject. What Regular Expression would I use? Is the taboo_header check performed before or after the tag text is prepended? From majordomo-users-owner Fri Feb 11 13:47:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA08169; Fri, 11 Feb 2000 13:25:15 -0800 (PST) Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA08160 for ; Fri, 11 Feb 2000 13:25:08 -0800 (PST) Received: (from uucp@localhost) by uucphost.mcs.net (8.9.3/8.8.8) with UUCP id PAA63605 for majordomo-users@greatcircle.com; Fri, 11 Feb 2000 15:41:10 -0600 (CST) Received: (from david@localhost) by midrange.dynip.com (8.9.3/8.8.7) id KAA01490 for majordomo-users@greatcircle.com; Fri, 11 Feb 2000 10:26:33 -0600 From: David Gibbs Message-Id: <200002111626.KAA01490@midrange.dynip.com> Subject: Insecure dependency when running medit To: majordomo-users@greatcircle.com Date: Fri, 11 Feb 2000 10:26:32 -0600 (CST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Folks: I'm trying to use medit to edit my mailing list files in 1.94.4 but keep running into a problem ... here's what happens: /usr/local/home/david $medit midrange-l Insecure dependency in link while running setuid at /usr/local/majordomo-1.94/shlock.pl line 35. I always got an error when running this, but since I upgraded to RH 6.1 (not using the MJ rpm, my own install) I'm now getting an actual error message. I can use medit find when I'm root. Any suggestions? Thanks! david From majordomo-users-owner Fri Feb 11 15:01:01 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA08910; Fri, 11 Feb 2000 14:33:10 -0800 (PST) Received: from sparkie.elmo.osl.state.or.us (elmo.osl.state.or.us [159.121.122.35]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA08903 for ; Fri, 11 Feb 2000 14:33:05 -0800 (PST) Received: by sparkie.elmo.osl.state.or.us (Postfix, from userid 1006) id A85BD1ED71; Fri, 11 Feb 2000 14:49:08 -0800 (PST) Date: Fri, 11 Feb 2000 14:49:08 -0800 (PST) From: "Christopher A. Adams" X-Sender: chris@elmo.osl.state.or.us To: Majordomo-Users@greatcircle.com Subject: Re: Restrict-post facility and mungedomain; headers in approved messages. In-Reply-To: <200002111859.TAA05677@bialystok.tpsa.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I was going to post something about this problem, so I will add my 2 cents. Maybe a solution has been posted before, but I missed it. In my case, the problem is mostly with the zubscribed address not matching the sender's address, as their domain has slightly changed since they initially zubscribed. joe.blow@state.or.us is equivalent to joe.blow@ode-ex1.ode.state.or.us for receiving, but only the latter works for sending. Munge domain is set to yes. Sometimes individuals are zubscribed in batch by the list owner at the former address, because they are not aware of the actual address to zubscribe. How have y'all dealt with this? Christopher Adams Oregon State Library chris@opac.osl.st On Fri, 11 Feb 2000, Andrzej;80R Kasperowicz wrote: > Hi! > > I have a problem with restrict_post facilty. > For example a message sent to my list chemfan by > ckingsbu@unlserve.unl.edu has been bounced because the address didn't > match the member list. He's on the list of subscribers as > ckingsbu@unlinfo.unl.edu . > Mungedomain option is set to 'yes' but apparently it doesn't work in that kind > of situation. > Can you see any good solution of the problem? > Maybe you could include it in the next ver. of majordomo to mungedomain > domains also when using restrict_post facility. > I wouldn't be happy to approve all the time that kind of messages or to ask > majordomo-owner to add that kind of addresses to a separate additional file. > Actually I often may encounter persons who use various machines, so that I > would have to change their addresses each time they send a mail to the list - > that's rediculous. I told majordomo-owner that if it's going to be like that all > the time I will cancel that restrict post facility, but then he threatened that he > will ask me to host the list elsewhere. :( > > Besides, when I approve a message to send, it is then send with my name > in the header, not the original sender - are you going to do something > about this problem in the future? I'm using pegasus mail to resend > approved messages. > > I would be also grateful if you could suggest me a free bounce filter, which > could deal automatically with bounced messages unsubscribing appropriate > e-mail addresses (would be nice if that option would co-operate with > mungedomain, too). > > Cheers! > > Andrzej Kasperowicz | There is but one way to avoid mistakes; > chemfan & minerals list-owner | to do nothing. This however, maybe the > andyk@termisoc.org | greatest mistake of all... > http://www.termisoc.org/~andyk/ | Albert Szent-Gyorgy > Christopher Adams Automated Systems Oregon State Library chris@sparkie.osl.state.or.us From majordomo-users-owner Fri Feb 11 16:16:00 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA09853; Fri, 11 Feb 2000 16:03:55 -0800 (PST) Received: from Jerome.reboot.com (gate.reboot.com [207.194.87.97]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA09846 for ; Fri, 11 Feb 2000 16:03:48 -0800 (PST) Received: (from uucp@localhost) by Jerome.reboot.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) id QAA82366 for ; Fri, 11 Feb 2000 16:19:52 -0800 (PST) Received: from reboot.com(172.16.129.22) by Jerome.reboot.com via smap (4.1) id xma216698; Fri, 11 Feb 00 16:19:10 -0800 Received: from reboot.com (Hull [172.16.130.97]) by newman.reboot.com (980427.SGI.8.8.8/8.8.8) with ESMTP id QAA70411; Fri, 11 Feb 2000 16:19:09 -0800 (PST) Message-ID: <38A4A6FD.BF4E5B4E@reboot.com> Date: Fri, 11 Feb 2000 16:19:09 -0800 From: Mark Tigges X-Mailer: Mozilla 4.51 [en] (X11; I; IRIX64 6.5 IP28) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com CC: rap@reboot.com Subject: ?? Administering multiple lists Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk FYI: My first post to this list, my (admittly brief) search of the archive did not turn up a solution. Nor does the FAQ seem to address my problem. If this is a previously solved topic, my apologies. We have what is becoming a serious problem. Two internal lists ('trivia' and 'news') are being cross posted frequently. Some users who are subscribed to both dislike getting the same message twice. Most of us don't care about that, but without fail everybody else hates the vitriolic flames that ensue for the next twenty minutes. Is there a way to make sure that if a message is addressed to the recipients of two lists, that the message is only sent once to each person. What is required is to cross check the recipients for duplicate final addresses. tia Mark Tigges From majordomo-users-owner Fri Feb 11 19:29:51 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA11582; Fri, 11 Feb 2000 19:22:18 -0800 (PST) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA11575 for ; Fri, 11 Feb 2000 19:22:09 -0800 (PST) Received: from ee-nt (eckert@netcom2.netcom.com [199.183.9.102]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id TAA23014; Fri, 11 Feb 2000 19:38:05 -0800 (PST) Message-Id: <3.0.5.32.20000211193435.009b0a60@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 11 Feb 2000 19:34:35 -0800 To: Mark Tigges From: SRE Subject: Re: ?? Administering multiple lists Cc: majordomo-users@GreatCircle.COM In-Reply-To: <38A4A6FD.BF4E5B4E@reboot.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 04:19 PM 2/11/00 -0800, Mark Tigges wrote: >Is there a way to make sure that if a >message is addressed to the recipients of >two lists, that the message is only sent >once to each person. When you find the answer, please let me know! I looked into that some time ago, and didn't find a solution. One possible architecture would be a number of "combo" lists that represent all the cross-posting combinations you expect. These lists would have generated subscribers, no one would actually subscribe themselves. Using taboo rules and perhaps some custom coding, cross-posts could be sent to a combo list (for posting) instead of to a list owner (for approval). Nightly regeneration of the combo list would keep people more or less in synch. People subscribed to one list but getting email from the combo list might be confused, but this is as close as I've gotten to a workable solution... and it's never been done to my knowledge. From majordomo-users-owner Sat Feb 12 00:45:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id AAA13673; Sat, 12 Feb 2000 00:27:39 -0800 (PST) Received: from bialystok.tpsa.pl (sask.bialystok.tpsa.pl [194.204.183.253]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id AAA13666 for ; Sat, 12 Feb 2000 00:27:31 -0800 (PST) Received: from an (pa208.bialystok.ppp.tpnet.pl [212.160.61.208]) by bialystok.tpsa.pl (8.8.8/8.8.4) with ESMTP id JAA17725; Sat, 12 Feb 2000 09:45:33 +0100 Message-Id: <200002120845.JAA17725@bialystok.tpsa.pl> From: "Andrzej Kasperowicz" To: Eric Crump Date: Sat, 12 Feb 2000 09:45:07 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Restrict-post facility and mungedomain; headers in approved messages. CC: Majordomo-Users@greatcircle.com References: <200002111859.TAA05677@bialystok.tpsa.pl> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > That seems to work. However, if you are not the majordomo site > administratror you do need to get that person to make the addition to the > config file and include the full path to the auth file, which I assume Which config file do you mean? The one to which I have an access through e- mail? Where/how in the file should he add that path? > you would want to have under your home directory (assuming you're on the > same system; if you're not, I guess the administrator would have to > maintain the auth file too). I was doing as you suggested for a while, but I am not the majordomo-owner, so I am just asking him to add these addresses to the file. This however is not a very good solution as I also have to send a message with information what happened to the person whose post was bounced, requesting that he/she should resend his/her mail. Is author of majordomo reading this list? Couldn't he tell us why mungedomain does not work in that situation? Will he fix it in next version of majordomo? And what about two other issues which I mentioned in my previous e-mail (i.e. bouncing filter, and headers in approved messages). Cheers! Andrzej Kasperowicz - chemfan & minerals list-owner andyk@termisoc.org http://www.termisoc.org/~andyk/chemfan/ http://www.termisoc.org/~andyk/minerals/ Murphy's Law: "Anything that can go wrong, will go wrong". Parkinson's Law -- "Work expands to exceed available time". Forget Einstein -- these are the laws that REALLY govern the universe. From majordomo-users-owner Sat Feb 12 08:24:02 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA20451; Sat, 12 Feb 2000 08:07:04 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id IAA20444 for ; Sat, 12 Feb 2000 08:06:57 -0800 (PST) Received: (qmail 10136 invoked from network); 12 Feb 2000 16:23:09 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 12 Feb 2000 16:23:09 -0000 Date: Sat, 12 Feb 2000 09:20:44 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: SRE cc: Mark Tigges , majordomo-users@GreatCircle.COM Subject: Re: ?? Administering multiple lists In-Reply-To: <3.0.5.32.20000211193435.009b0a60@pop.climber.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Here is a suggestion. Others on the list probably will know a simpler way to use the same concept. 1. Create a database with the following schema simpler method): CREATE TABLE SENT_MESSAGES ( ADDRESS CHAR(50), MESSAGE_DATE DATE, MESSAGE_DIGEST INTEGER, UNIQUE(ADDRESS, MESSAGE_DIGEST) ); You can use any SQL database. If you don't have one, you can use my open source database (www.cql.com). 2. As part of the check of whether to send a message to a subscriber, add a row to this table. 3. If the insert into the table succeeds, send the message. 4. If the insert into the table fails (because it is a duplicate row), don't send the message. There are lots of ways to generate the message digest (security jargon for a hash). Use the password hash, or use sum, or get code for one of the RSA hashes. It really doesn't matter much, and the hash doesn't have to be perfect, as the only consequence of a collision is that an extra message is sent. You need to do the hash on the message **without** the headers, obviously. The MESSAGE_DATE column is there to allow you to prune the database by deleting, say once a day, everything that is old. Old might be a day, or a few days. Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com On Fri, 11 Feb 2000, SRE wrote: > At 04:19 PM 2/11/00 -0800, Mark Tigges wrote: > >Is there a way to make sure that if a > >message is addressed to the recipients of > >two lists, that the message is only sent > >once to each person. > > When you find the answer, please let me know! I looked into > that some time ago, and didn't find a solution. One possible > architecture would be a number of "combo" lists that > represent all the cross-posting combinations you expect. > These lists would have generated subscribers, no one would > actually subscribe themselves. Using taboo rules and perhaps > some custom coding, cross-posts could be sent to a combo > list (for posting) instead of to a list owner (for approval). > Nightly regeneration of the combo list would keep people > more or less in synch. People subscribed to one list but > getting email from the combo list might be confused, but > this is as close as I've gotten to a workable solution... > and it's never been done to my knowledge. > From majordomo-users-owner Sun Feb 13 12:15:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA06598; Sun, 13 Feb 2000 11:59:37 -0800 (PST) Received: from smtp13.bellglobal.com (smtp13.bellglobal.com [204.101.251.52]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA06591 for ; Sun, 13 Feb 2000 11:59:30 -0800 (PST) Received: from shogun.apt.samurai.com (HSE-Toronto-ppp89186.sympatico.ca [216.209.33.183]) by smtp13.bellglobal.com (8.8.5/8.8.5) with ESMTP id PAA06074 for ; Sun, 13 Feb 2000 15:18:45 -0500 (EST) Received: by shogun.apt.samurai.com (Postfix, from userid 1000) id EE437203; Sun, 13 Feb 2000 15:15:51 -0500 (EST) Date: Sun, 13 Feb 2000 15:15:51 -0500 From: bjf To: majordomo-users@GreatCircle.COM Subject: Re: Pricing for hosting lists Message-ID: <20000213151551.A6264@samurai.com> References: <4.2.0.58.20000210133643.0097a930@192.168.0.67> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: ; from help@quality.org on Thu, Feb 10, 2000 at 10:43:54PM -0500 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, Feb 10, 2000 at 10:43:54PM -0500, "Bill Casti (System Admin)" wrote: > > > So you don't care about how many users or how much traffic? > > Nope, don't care in the list. Convince me why I should. Ok, say I have a 20,000 subscriber discussion list which averages 5,000 inbound messages per day (1,000,000 outbound messages, plus bounces and admin traffic). Still $10? :) Bryan -- Bryan Fullerton http://bryanfullerton.com/ Core Competency Samurai Consulting Can you feel the Ohmu call? From majordomo-users-owner Sun Feb 13 23:14:55 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA12614; Sun, 13 Feb 2000 22:57:06 -0800 (PST) Received: from rock.jetty.net (rock.jetty.net [216.59.68.134]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA12607 for ; Sun, 13 Feb 2000 22:57:00 -0800 (PST) Received: from a (david.steele.web [1.1.1.4]) by rock.jetty.net (8.9.3/8.9.3) with SMTP id XAA05303 for ; Sun, 13 Feb 2000 23:13:47 -0800 Message-Id: <2.2.32.20000214071355.006b9f70@jetty.net> X-Sender: david@jetty.net X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 13 Feb 2000 23:13:55 -0800 To: Majordomo-Users@GreatCircle.COM From: David Steele Subject: majordomo digesting / sendmail problem Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am having a problem with a newer version of sendmail which came out of the box with Redhat's Linux 6.0 and majordomo's digest option. I've spent way too much time now... and thought I'd ask for some more help. First, some important details: o The majordomo version is 1.94.4 o The sendmail version is 8.9.3 o The perl version is 5.005, patch 03 (or so says the man page) o The OS is Redhat's Linux 6.0 (no patches) Anyway, the problem I'm having is with this version of sendmail and majordomo's list *digest* option. I say this version as the digesting feature used to work just fine before the upgrade (same version of majordomo and same permissions, same lists, same config files, same /etc/aliases, etc...) - but after the upgrade to sendmail 8.9.3 the digest part doesn't work. Ok, here is the deal... I get an error when majordomo tries to process a digest. As you may know, lists in majordomo are driven by the /etc/alaises file which I've pasted below. The regular list expansion of the alias works fine, so I've simply commented out the digesting portion of the alias for active lists until I fix the problem. The problem with the digest portion of the alias appears to be that sendmail isn't passing the full arguement from the aliase file to the wrapper program - which is called via a pipe in the alias file. When I send mail to the list "test" which uses the digesting feature, I get an error from the digest portion of the alias, AND I get the mail via the list as a regular list member. Here is the error message I get - returned to majordomo-owner: ---------- To: majordomo-owner Subject: MAJORDOMO ABORT (mj_digest) Reply-To: majordomo-owner MAJORDOMO ABORT (mj_digest)!! -l: No such file or directory ---------- Here is a copy of the digest portion (only) of the alias: test: "|/usr/local/majordomo/wrapper digest -r -C -l test-digest test-digest-outgoing" So, it looks like everything after the -l is stripped off by sendmail, and not passed to wrapper. Now, if I push a peice of mail to the wrapper program by hand, not thru an alias or sendmail it works just fine: $/usr/local/majordomo/wrapper digest -r -C -l test-digest test-digest-outgoing ; Mon, 14 Feb 2000 04:45:20 -0800 (PST) Received: from world.std.com (world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id IAA03292; Mon, 14 Feb 2000 08:01:51 -0500 (EST) Received: from localhost (jkaplan@localhost) by world.std.com (8.9.3/8.9.3) with ESMTP id IAA27263; Mon, 14 Feb 2000 08:01:49 -0500 (EST) Date: Mon, 14 Feb 2000 08:01:49 -0500 From: Jeffrey Kaplan To: Jeff Lasman cc: majordomo-users@GreatCircle.COM Subject: Re: Banned users. In-Reply-To: <4.2.0.58.20000210134053.0097f510@192.168.0.67> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 10 Feb 2000, Jeff Lasman wrote: > > > Is it possible to only moderate one address on a open list. What I would > >Per list, editing the taboo_headers for the list is the way to go. > > I don't think that's what he asked. I think he means can he set individual > users to be moderated. The answer is: not without patching majordomo. Adding the address to 'taboo_headers' of a list does effectively moderate that one peson, since Majordomo will then bounce anything from that person to the moderator/list admin just like a regular moderated list will do for all posts. The bounce message will, of cource, be different, but the effect is the same. -- Jeffrey Kaplan gordol@gordol.org <*> I'm set up for PGP. Are you? "...One moment of perfect beauty." (Amb. Kosh, B5 "There All The Honor Lies") From majordomo-users-owner Mon Feb 14 05:11:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA18905; Mon, 14 Feb 2000 05:07:33 -0800 (PST) Received: from europe.std.com (europe.std.com [199.172.62.20]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA18898 for ; Mon, 14 Feb 2000 05:07:28 -0800 (PST) Received: from world.std.com (world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id IAA06112; Mon, 14 Feb 2000 08:23:59 -0500 (EST) Received: from localhost (jkaplan@localhost) by world.std.com (8.9.3/8.9.3) with ESMTP id IAA18252; Mon, 14 Feb 2000 08:23:58 -0500 (EST) Date: Mon, 14 Feb 2000 08:23:58 -0500 From: Jeffrey Kaplan To: Jeff Lasman cc: Majordomo Users Subject: Re: Pricing for hosting lists In-Reply-To: <4.2.0.58.20000211074120.00960390@192.168.0.67> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 11 Feb 2000, Jeff Lasman wrote: > Announcement List Setup: $15 > Discussion List Setup: $25 Why are these differnet? Isn't the setup the same? I know it is at my site. BTW, the prices here are: $5/month per list per 500 addresses. No setup fee. List owners must have login accounts, and the higher of the two levels of those have up to two lists included in their monthly charges. Digests are separate lists as far as billing issues go. -- Jeffrey Kaplan gordol@gordol.org <*> I'm set up for PGP. Are you? "Now according to his file, Sheridan's a good tactical thinker, he can take an inferior defensive force and turn it into an offensive force capable of taking on a better equipped enemy." (Mr. Garibaldi, B5 "A Day In The Strife") From majordomo-users-owner Mon Feb 14 05:24:46 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id EAA18680; Mon, 14 Feb 2000 04:48:26 -0800 (PST) Received: from europe.std.com (europe.std.com [199.172.62.20]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA18673 for ; Mon, 14 Feb 2000 04:48:20 -0800 (PST) Received: from world.std.com (world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id IAA03526; Mon, 14 Feb 2000 08:04:51 -0500 (EST) Received: from localhost (jkaplan@localhost) by world.std.com (8.9.3/8.9.3) with ESMTP id IAA11911; Mon, 14 Feb 2000 08:04:50 -0500 (EST) Date: Mon, 14 Feb 2000 08:04:50 -0500 From: Jeffrey Kaplan To: Bob cc: Majordomo Users Subject: Re: Banned users. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 10 Feb 2000, Bob wrote: > > >Per list, editing the taboo_headers for the list is the way to go. > > The reason I need to be able to bounce one certain email is, I have a > subscriber from ix.netcom.com using netcomplete 4.0 and every time she > posts to the list she has a trail of ^@^@^@^@^@^@^@^@^@ at the end of the > msg body on every post. She says she has no sig file, and that these > characters just appear. What these characters do; everytime a digest goes > out, it gets trunicated where these characters appear, the digests stops > at the end of her post causing only certain people not to receive the full > digest. 'taboo_header' the address. When the mail bounces to you, edit out the string of '^@' characters. BTW, I occasionally see those in corrupted mail spools. That may or may not be related. You might want to pass that on to her: There may be some form of corruption in her mail system. -- Jeffrey Kaplan gordol@gordol.org <*> I'm set up for PGP. Are you? "...One moment of perfect beauty." (Amb. Kosh, B5 "There All The Honor Lies") From majordomo-users-owner Mon Feb 14 07:54:42 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA20589; Mon, 14 Feb 2000 07:48:31 -0800 (PST) Received: from home.us.net (home.us.net [198.240.72.28]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA20582 for ; Mon, 14 Feb 2000 07:48:24 -0800 (PST) Received: from wef.org (mail.wef.org [198.240.82.1]) by home.us.net (8.8.8/8.8.8) with SMTP id LAA19987 for ; Mon, 14 Feb 2000 11:04:57 -0500 (EST) X-Provider: US Net - Advanced Internet Services - 301-361-USNET - info@us.net Where Business Connects! (tm) -- http://www.us.net/ Received: from WEFGW-Message_Server by wef.org with Novell_GroupWise; Mon, 14 Feb 2000 11:02:22 -0500 Message-Id: X-Mailer: Novell GroupWise 5.5 Date: Mon, 14 Feb 2000 11:02:03 -0500 From: "Greg McNelly" To: Subject: sorting the list returned by the WHO request... Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've searched the archive (updated only to Nov '98???), read the FAQ, and = the README....with no luck. How can I get Majordomo to return an alphabetized list in response to the = "who" request? Yes, my config file is set to: strip =3D no I want my users to use the file generated by "who," instead of alway = bugging for an individual's e-mail address... Thanks, Greg From majordomo-users-owner Mon Feb 14 11:24:51 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA22354; Mon, 14 Feb 2000 10:23:28 -0800 (PST) Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA22347 for ; Mon, 14 Feb 2000 10:23:16 -0800 (PST) Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id KAA07447 for ; Mon, 14 Feb 2000 10:36:05 -0800 (PST) Received: from netscape.com ([207.1.145.44]) by judge.mcom.com (Netscape Messaging Server 4.03) with ESMTP id FPXNU800.NBG for ; Mon, 14 Feb 2000 10:39:44 -0800 Message-ID: <38A84BF0.653CC9A5@netscape.com> Date: Mon, 14 Feb 2000 10:39:44 -0800 From: Sudhakar Chandrasekharan Organization: I didn't do it, nobody saw me do it, no one can prove a thing X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.13 i686) X-Accept-Language: en, fr MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: RegExps for filtering virii Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, One of the mailing lists that I run recently had a repeat episode of someone posting the happy99.exe virus. I have stepped in and created a taboo_body entry for this virus. I was wondering weather someone on this list has a set of reg exps to grep for various other virii. S. -- "Am I the only one who just wants to play hopscotch, bake cookies, and watch '"The McLaughlin Group?'" -- Lisa Simpson Sudhakar C13n http://people.netscape.com/thaths/ Lead Indentured Slave From majordomo-users-owner Mon Feb 14 12:56:40 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA23855; Mon, 14 Feb 2000 12:23:30 -0800 (PST) Received: from zoso.net (zoso.net [204.122.18.193]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA23847 for ; Mon, 14 Feb 2000 12:23:22 -0800 (PST) Received: from localhost (mirader@localhost) by zoso.net (8.9.3/8.9.3) with ESMTP id MAA07689; Mon, 14 Feb 2000 12:40:15 -0800 Date: Mon, 14 Feb 2000 12:40:15 -0800 (PST) From: Bob To: Jeffrey Kaplan cc: Majordomo Users Subject: Re: Banned users. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Mon, 14 Feb 2000, Jeffrey Kaplan wrote: > On Thu, 10 Feb 2000, Bob wrote: > > > > >Per list, editing the taboo_headers for the list is the way to go. > > > > The reason I need to be able to bounce one certain email is, I have a > > subscriber from ix.netcom.com using netcomplete 4.0 and every time she > > posts to the list she has a trail of ^@^@^@^@^@^@^@^@^@ at the end of the > > msg body on every post. She says she has no sig file, and that these > > characters just appear. What these characters do; everytime a digest goes > > out, it gets trunicated where these characters appear, the digests stops > > at the end of her post causing only certain people not to receive the full > > digest. > > 'taboo_header' the address. When the mail bounces to you, edit out > the string of '^@' characters. I have added her email address to taboo_header in the list.config 2 different ways and her email still goes out to the list without being bounced. I am sure I must be overlooking something simple as most newbies do. The first time I added her to taboo_headers I did it like this: # taboo_headers [regexp_array] (undef) # If any of the headers matches one of these regexps, then the # message will be bounced for review. taboo_headers << END /^from:.*user@ix.netcom.com/i END The second time I did it like this: # taboo_headers [regexp_array] (undef) # If any of the headers matches one of these regexps, then the # message will be bounced for review. taboo_headers << END /^from: user@ix.netcom.com/i END BTW I am using 1.94.5 on a linux box. > BTW, I occasionally see those in corrupted mail spools. That may or > may not be related. You might want to pass that on to her: There may > be some form of corruption in her mail system. I have passed it on, Thank You! Bob mirader@zoso.net From majordomo-users-owner Mon Feb 14 13:45:01 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA24323; Mon, 14 Feb 2000 12:59:44 -0800 (PST) Received: from ns1.pad.com (ns1.pad.com [216.44.162.50]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA24316 for ; Mon, 14 Feb 2000 12:59:38 -0800 (PST) Received: (from peter@localhost) by ns1.pad.com (8.9.3/8.9.3/Debian 8.9.3-6) id QAA26604 for majordomo-users@GreatCircle.COM; Mon, 14 Feb 2000 16:11:29 -0500 Date: Mon, 14 Feb 2000 16:11:29 -0500 From: Peter Dominguez To: majordomo-users Subject: format of e-mail address in list with strip = no Message-ID: <20000214161129.K12846@pad.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i X-Operating-System: Linux 2.3.42 on an i686 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The comma in the following address tries to send e-mail to Dominguez@localhost: Dominguez, Peter With out the comma i.e. Dominguez Peter seems to work fine. Is there a substitute character for the comma so that: Last Name, First Name can be used. Thanks. -- Peter Dominguez 72 Belvedere Dr Yonkers, NY 10705-2814 US tel: (914) 423-4000 fax: (914) 423-8640 The 21st century begins on January 1, 2001. see: http://astro.nmsu.edu/~lhuber/leaphist.html http://pschye.usno.navy.mil From majordomo-users-owner Mon Feb 14 15:15:29 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA25746; Mon, 14 Feb 2000 14:38:32 -0800 (PST) Received: from tor.abc.se (ns.abc.se [195.17.72.11]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA25739 for ; Mon, 14 Feb 2000 14:38:27 -0800 (PST) Received: from atle (atle [195.17.72.10]) by tor.abc.se (8.9.1b+Sun/8.9.1) with ESMTP id XAA05172; Mon, 14 Feb 2000 23:54:38 +0100 (MET) Date: Mon, 14 Feb 2000 23:54:36 +0100 (MET) From: Mats Dufberg X-Sender: m8698@atle To: Peter Dominguez cc: majordomo-users Subject: Re: format of e-mail address in list with strip = no In-Reply-To: <20000214161129.K12846@pad.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Mon, 14 Feb 2000, Peter Dominguez wrote: > The comma in the following address tries to send e-mail to Dominguez@localhost: > > Dominguez, Peter > > With out the comma i.e. > > Dominguez Peter > > seems to work fine. Is there a substitute character for the comma so that: > > Last Name, First Name can be used. Put the name in quotes: "Dominguez, Peter" ----------------------------------------------------------------- Mats Dufberg mats.dufberg@abc.se Alvdalsvagen 133 +46 8 38 48 59 SE-165 75 Hasselby, Sweden From majordomo-users-owner Mon Feb 14 16:52:06 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA27269; Mon, 14 Feb 2000 16:34:11 -0800 (PST) Received: from chamber.dna.fi (chamber.dna.fi [62.236.155.125]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id QAA27255 for ; Mon, 14 Feb 2000 16:34:03 -0800 (PST) Received: (qmail 18301 invoked by uid 501); 15 Feb 2000 02:50:36 +0200 Date: Tue, 15 Feb 2000 02:50:36 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: Peter Dominguez Cc: majordomo-users Subject: Re: format of e-mail address in list with strip = no Message-ID: <20000215025036.K17898@chamber.dna.fi> Reply-To: Mikko.Hanninen@iki.fi Mail-Followup-To: Peter Dominguez , majordomo-users References: <20000214161129.K12846@pad.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.1.3i In-Reply-To: <20000214161129.K12846@pad.com>; from peter@pad.com on Mon, Feb 14, 2000 at 04:11:29PM -0500 Organization: None Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Peter Dominguez wrote on Mon, 14 Feb 2000: > Is there a substitute character for the comma so that: > > Last Name, First Name can be used. Not really, but if you put the name in quotes, then it will work. "Last Name, First Name" Hope this helps, Mikko -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Today's subliminal message is " " From majordomo-users-owner Mon Feb 14 18:51:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA27657; Mon, 14 Feb 2000 16:39:42 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA27649 for majordomo-users@greatcircle.com; Mon, 14 Feb 2000 16:39:39 -0800 (PST) Received: from johanna5.ux.his.no (johanna5.ux.his.no [152.94.1.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA10268 for ; Tue, 8 Feb 2000 09:13:06 -0800 (PST) Received: from gorina14.ux.his.no (atlwe@gorina14.ux.his.no [152.94.1.54]) by johanna5.ux.his.no (8.9.3/8.9.3) with ESMTP id SAA00945 for ; Tue, 8 Feb 2000 18:28:35 +0100 (MET) Received: by gorina14.ux.his.no id MAA28598; Tue, 8 Feb 2000 12:28:34 -0500 (EST) Date: Tue, 8 Feb 2000 18:28:34 +0100 (MET) From: Atle Weibell To: majordomo-users@greatcircle.com Subject: html-tags disturbing commands Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I'm the owner of a list that is supposed to be used by a lot of students using some web-based Lotus Notes mail client. When they try to subscribe, Majordomo reads the html-tags preceding and following the subscribe- command, which causes an error, because the html-tags are not recognized as part of a valid command. The Notes-administrator didn't know how to set up Notes to send plain text, so the question is if there is a way to tell Majordomo to skip those < >-tags? Regards, /\tle \/\/eibell / aw@ux.his.no \ pr 51690007 / mo 90690010 \ fx 51690431 / From majordomo-users-owner Mon Feb 14 19:06:47 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA27678; Mon, 14 Feb 2000 16:39:57 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA27668 for majordomo-users@greatcircle.com; Mon, 14 Feb 2000 16:39:54 -0800 (PST) Received: from sjmail1.loancity.com (afsloans.com [216.132.92.20]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA13076 for ; Tue, 8 Feb 2000 12:44:42 -0800 (PST) Received: by afsloans.com with Internet Mail Service (5.5.2650.21) id <1RZVMHCY>; Tue, 8 Feb 2000 13:00:14 -0800 Message-ID: <918FBC7BB49BD3118D8F009027D08DA06102C1@afsloans.com> From: Jeremy Gordon To: "'Majordomo-Users@GreatCircle.COM'" Subject: Serious Looping Problem Date: Tue, 8 Feb 2000 13:00:13 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm running the latest version of majordomo on the October '99 release of freeBSD 3.3 and I'm having a pretty weird problem. When using a short subscriber list (a test list), I have no problems at all. when I go and change over to the main list which has about 1500 subscribers and I send a message to it, it starts looping. The original message is sent to all subscribers with the footer appended to the bottom of the message, and then after it's done with it's first round, it goes and does it again with a second copy of the footer attached, and then again with yet another copy of the footer attached. I checked the subscriber list and there are no addresses that point back to the list. I have the reply-to set to an e-mail address outside of the system. It just doesn't make any sense. any help would be appreciated. Ps. I'm not subscribed to this list, so I need a private response. thanks again - jer From majordomo-users-owner Mon Feb 14 19:21:37 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA27852; Mon, 14 Feb 2000 16:43:33 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA27841 for majordomo-users@greatcircle.com; Mon, 14 Feb 2000 16:43:30 -0800 (PST) Received: from mail.wnonline.net (mail.wnonline.net [216.4.88.11]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA07609 for ; Wed, 9 Feb 2000 20:56:46 -0800 (PST) Received: from wnonline.net (houze.slipmat.net [216.4.88.90]) by mail.wnonline.net (8.9.3/8.9.3) with ESMTP id XAA47803 for ; Wed, 9 Feb 2000 23:12:39 -0600 (CST) (envelope-from brian.mcgowan@wnonline.net) Message-ID: <38A24979.38B388A2@wnonline.net> Date: Wed, 09 Feb 2000 23:15:37 -0600 From: Brian McGowan X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Majordomo-Users@GreatCircle.COM Subject: Hiding the senders address Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm trying to hide the From: address in the email that goes out to the list, I only want certain addy's to post to it and think it would be more secure if their emails were unknown to the rest of the list. I've tried changing the $mailer and various other things, but cannot get it to hide the senders address. any help would be greatly appreciated, please cc my email if you reply as I am not on this list. thanks! Brian- From majordomo-users-owner Mon Feb 14 19:42:10 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA27926; Mon, 14 Feb 2000 16:44:32 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA27916 for majordomo-users@greatcircle.com; Mon, 14 Feb 2000 16:44:29 -0800 (PST) Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.59]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id MAA20402 for ; Thu, 10 Feb 2000 12:16:22 -0800 (PST) Received: (qmail 19627 invoked by uid 0); 10 Feb 2000 20:31:27 -0000 Received: from queequeg.clarkson.edu (128.153.28.83) by mail.clarkson.edu with SMTP; 10 Feb 2000 20:31:27 -0000 Date: Thu, 10 Feb 2000 15:31:27 -0500 (EST) From: "Brian T. Huntley" To: majordomo-users@greatcircle.com Subject: Redundant Mj servers? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all... Has anyone any experience w/ redundant MJ servers? I have an environment where two separate boxes can (and do) access the same filespace, and I would like to set up two servers and DNS round-robin them for load sharing. Any thoughts on this would be greatly appreciated. TIA! - Best regards, Brian +-----------------------------------------------------------------------+ | Brian T. Huntley Systems and Network Engineer | | Campus Information Services, Clarkson University | | Ph/FAX: 315.268-2292/6570 | | bth@clarkson.edu www.clarkson.edu/cis | +-----------------------------------------------------------------------+ UNIX *is* user friendly. It's just selective about who its friends are. PGP Public Key available. finger bth@clarkson.edu From majordomo-users-owner Mon Feb 14 19:46:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA27749; Mon, 14 Feb 2000 16:41:24 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA27739 for majordomo-users@greatcircle.com; Mon, 14 Feb 2000 16:41:21 -0800 (PST) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id DAA22642 for ; Wed, 9 Feb 2000 03:09:14 -0800 (PST) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id EAA11500 for ; Wed, 9 Feb 2000 04:24:42 -0700 (MST) Received: from ip-44-130.tus.primenet.com(206.165.44.130), claiming to be "gateway.localnet" via SMTP by smtp02.primenet.com, id smtpdAAA3Saayw; Wed Feb 9 04:24:29 2000 Received: from bob.localnet (root@bob.localnet [192.168.1.1]) by gateway.localnet (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id EAA30844 for ; Wed, 9 Feb 2000 04:24:31 -0700 Received: by primenet.com via sendmail from stdin id (Debian Smail3.2.0.102) for majordomo-users@greatcircle.com; Wed, 9 Feb 2000 04:24:35 -0700 (MST) Date: Wed, 9 Feb 2000 04:24:34 -0700 From: Bob Nielsen To: majordomo-users@greatcircle.com Subject: abort message Message-ID: <20000209042434.A4864@bob.localnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When trying to approve an unsubscribe request, I get the following abort message (1003 is the UID for majordomo): MAJORDOMO ABORT (mj_majordomo)!! chown(1003, 1, "/usr/local/majordomo-1.94.5/lists/mylist.new"): Operation not permitted A listing shows that mylist.new has been created as owned by daemon, group daemon. All other files in this directory are majordomo.daemon. Approval of subscribe requests doesn't seem to be affected. I didn't have this problem with majordomo-1.94.4. Has something changed? -- Bob Nielsen, N7XY (RN2) nielsen@primenet.com Tucson, AZ DM42nh QRP-L #1985 http://www.primenet.com/~nielsen From majordomo-users-owner Mon Feb 14 19:52:54 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA27866; Mon, 14 Feb 2000 16:43:39 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id QAA27855 for majordomo-users@greatcircle.com; Mon, 14 Feb 2000 16:43:36 -0800 (PST) Received: from bialystok.tpsa.pl (sask.bialystok.tpsa.pl [194.204.183.253]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA07566 for ; Wed, 9 Feb 2000 20:54:20 -0800 (PST) Received: from an (pa74.bialystok.ppp.tpnet.pl [212.160.61.74]) by bialystok.tpsa.pl (8.8.8/8.8.4) with ESMTP id GAA04285 for ; Thu, 10 Feb 2000 06:12:05 +0100 Message-Id: <200002100512.GAA04285@bialystok.tpsa.pl> From: "Andrzej Kasperowicz" To: Majordomo-Users@GreatCircle.COM Date: Thu, 10 Feb 2000 06:11:38 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Restrict-post facility and mungedomain; headers in approved messages. X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi! I have a problem with restrict_post facilty. For example a message sent to my list chemfan by ckingsbu@unlserve.unl.edu has been bounced because the address didn't match the member list. He's on the list of subscribers as ckingsbu@unlinfo.unl.edu . Mungedomain option is set to 'yes' but apparently it doesn't work in that kind of situation. Can you see any solution of the problem? Maybe you could include it in the next ver. of majordomo to mungedomain domains also when using restrict_post facility. I wouldn't be happy to approve all the time that kind of messages or to ask majordomo-owner to add that kind of addresses to a separate additional file. Actually I often may encounter persons who use various machines, so that I would have to change their addresses each time they send a mail to the list - that's rediculous. I told majordomo-owner that if it's going to be like that all the time I will cancel that restrict post facility, but then he threatened that he will ask me to host the list elsewhere. :( Besides, when I approve a message to send, it is then send with my name in the header, not the original sender - are you going to do something regarding this problem in the future? I'm using pegasus mail to resend approved messages. *Please*, send answer also to my private address, as I'm not subscribed to the list. Cheers Andrzej Kasperowicz - chemfan & minerals list-owner andyk@termisoc.org http://www.termisoc.org/~andyk/chemfan/ http://www.termisoc.org/~andyk/minerals/ Murphy's Law: "Anything that can go wrong, will go wrong". Parkinson's Law -- "Work expands to exceed available time". Forget Einstein -- these are the laws that REALLY govern the universe. From majordomo-users-owner Mon Feb 14 20:03:35 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA28841; Mon, 14 Feb 2000 17:43:39 -0800 (PST) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA28834 for ; Mon, 14 Feb 2000 17:43:32 -0800 (PST) Received: from ee-nt (eckert@netcom3.netcom.com [199.183.9.103]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id RAA14378; Mon, 14 Feb 2000 17:59:58 -0800 (PST) Message-Id: <3.0.5.32.20000214172041.009f78e0@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 14 Feb 2000 17:20:41 -0800 To: Peter Dominguez From: SRE Subject: Re: format of e-mail address in list with strip = no Cc: majordomo-users@GreatCircle.COM In-Reply-To: <20000214161129.K12846@pad.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 04:11 PM 2/14/00 -0500, peter@pad.com wrote: >Is there a substitute character for the comma so that: >Last Name, First Name can be used. Use quotes instead of angles: "last name, first name" user@host.com From majordomo-users-owner Mon Feb 14 20:05:49 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA28393; Mon, 14 Feb 2000 17:08:08 -0800 (PST) Received: from queernet.queernet.org (queernet.queernet.org [170.1.118.14]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA28386 for ; Mon, 14 Feb 2000 17:08:04 -0800 (PST) Received: from localhost (rogerk@localhost) by queernet.queernet.org (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e1F1OKo24138 Date: Mon, 14 Feb 2000 17:24:15 -0800 (PST) From: "Roger B.A. Klorese" To: Peter Dominguez cc: majordomo-users Subject: Re: format of e-mail address in list with strip = no In-Reply-To: <20000214161129.K12846@pad.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Mon, 14 Feb 2000, Peter Dominguez wrote: > The comma in the following address tries to send e-mail to Dominguez@localhost: > > Dominguez, Peter ...as it should. According to the RFC's, this is two separate addresses. Commas and dots MUST be inside quoted strings in a comment. -- ROGER B.A. KLORESE rogerk@QueerNet.ORG urgent: rogerk-page@QueerNet.ORG PO Box 14309 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy -- the refusal of joy!" -- Paul Rudnick From majordomo-users-owner Tue Feb 15 03:41:35 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id DAA07462; Tue, 15 Feb 2000 03:27:15 -0800 (PST) Received: from mail.unina.it (mail.unina.it [192.132.34.20]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id DAA07455 for ; Tue, 15 Feb 2000 03:26:50 -0800 (PST) Received: from unina.it (blaster.cds.unina.it [143.225.209.101]) by mail.unina.it (8.9.3/8.9.3) with ESMTP id MAA07553 for ; Tue, 15 Feb 2000 12:41:27 +0100 (MET) Message-ID: <38A93C58.A7942BAB@unina.it> Date: Tue, 15 Feb 2000 12:45:29 +0100 From: "Niko!" X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686) X-Accept-Language: it, en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Information bounces... is it possible ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello! I manage several moderated lists, and i'd like to know if is it possible to send users posting to my lists an automated message like: "Your message to the list xxxxxx was accepted and sent to xxxx (list-owner) for approval! if possible it will be approved in 24 hours. Thanks". Regards Niko From majordomo-users-owner Tue Feb 15 06:29:04 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA09105; Tue, 15 Feb 2000 06:18:41 -0800 (PST) Received: from mhub1.tc.umn.edu (mhub1.tc.umn.edu [160.94.5.41]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA09098 for ; Tue, 15 Feb 2000 06:18:36 -0800 (PST) Received: from garnet.tc.umn.edu by mhub1.tc.umn.edu with ESMTP for majordomo-users@greatcircle.com; Tue, 15 Feb 2000 08:35:17 -0600 Received: from localhost by garnet.tc.umn.edu with ESMTP for majordomo-users@greatcircle.com; Tue, 15 Feb 2000 08:35:17 -0600 Date: Tue, 15 Feb 2000 08:35:17 -0600 (CST) From: mjn To: majordomo-users@greatcircle.com Subject: Mderated lists... Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Anyone have any advice for setting up a list with multiple moderators? Is it 1) possible and/or 2) advisable? ____________________________ Mike Neuharth ADCS Technology Specialist http://www.umn.edu/adcs E-Mail : mjn@tc.umn.edu Page Mail : 6123065932@messaging.sprintpcs.com http://nifty.dsl.visi.com/ ____________________________ From majordomo-users-owner Tue Feb 15 06:43:53 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA09168; Tue, 15 Feb 2000 06:25:57 -0800 (PST) Received: from clifford.inch.com (clifford.inch.com [207.240.140.163]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA09156 for ; Tue, 15 Feb 2000 06:25:52 -0800 (PST) Received: (from omar@localhost) by clifford.inch.com (8.9.3/8.8.5) id IAA29059; Tue, 15 Feb 2000 08:45:17 -0500 Message-ID: <20000215084517.A29007@clifford.inch.com> Date: Tue, 15 Feb 2000 08:45:17 -0500 From: Omar Thameen To: David Steele , Majordomo-Users@GreatCircle.COM Subject: Re: majordomo digesting / sendmail problem References: <2.2.32.20000214071355.006b9f70@jetty.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <2.2.32.20000214071355.006b9f70@jetty.net>; from David Steele on Sun, Feb 13, 2000 at 11:13:55PM -0800 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Does the test-digest directory actually exist? Omar On Sun, Feb 13, 2000 at 11:13:55PM -0800, David Steele wrote: > > MAJORDOMO ABORT (mj_digest)!! > > -l: No such file or directory > > ---------- > > Here is a copy of the digest portion (only) of the alias: > > test: "|/usr/local/majordomo/wrapper digest -r -C -l test-digest > test-digest-outgoing" From majordomo-users-owner Tue Feb 15 06:59:09 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA09233; Tue, 15 Feb 2000 06:33:25 -0800 (PST) Received: from web3.hq.eso.org (web3.hq.eso.org [134.171.7.4]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA09226 for ; Tue, 15 Feb 2000 06:33:18 -0800 (PST) Received: from mailrelay.hq.eso.org by web3.hq.eso.org with ESMTP (8.8.5/ eso-5.3) id PAA15411; Tue, 15 Feb 2000 15:50:13 +0100 (MET) Received: from eso.org (sjohnsto@fenris [134.171.40.51]) by mailrelay.hq.eso.org (8.8.5/eso_cl_6.0) with ESMTP id PAA25847 for ; Tue, 15 Feb 2000 15:50:24 +0100 (MET) Message-ID: <38A9677A.6F9AA5A7@eso.org> Date: Tue, 15 Feb 2000 15:49:30 +0100 From: Stephen Johnston Organization: Terma Elektronic AS X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: From address in majordomo command responses Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi I have majordomo@. when I should have majordomo@I've looked at 'whoami' and 'whereami' in the .cf but cannot see anything wrong. Adittionally the majordomo machine is our mail hub as well (so it might be a sendmail.cf thing). Any help here would be appreciated. TIA Stephen. -- Stephen Johnston Phone: +49 89 32006322 UNIX Administrator Fax : +49 89 32006380 European Southern Observatory Karl-Schwarzschild-Strasse 2 D-85748 Garching bei Muenchen http://www.eso.org From majordomo-users-owner Tue Feb 15 08:00:14 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA10088; Tue, 15 Feb 2000 07:49:57 -0800 (PST) Received: from rock.jetty.net (rock.jetty.net [216.59.68.134]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA10081 for ; Tue, 15 Feb 2000 07:49:50 -0800 (PST) From: david@jetty.net Received: from a (david.steele.web [1.1.1.4]) by rock.jetty.net (8.9.3/8.9.3) with SMTP id IAA11986; Tue, 15 Feb 2000 08:06:35 -0800 Message-Id: <2.2.32.20000215160650.0069af34@jetty.net> X-Sender: david@jetty.net X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 15 Feb 2000 08:06:50 -0800 To: Omar Thameen , Majordomo-Users@GreatCircle.COM Subject: Re: majordomo digesting / sendmail problem Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 08:45 AM 2/15/2000 -0500, Omar Thameen wrote: >Does the test-digest directory actually exist? Yes, and if I push a peice of mail to the wrapper program by hand, not thru an alias or sendmail it works just fine: $/usr/local/majordomo/wrapper digest -r -C -l test-digest test-digest-outgoing > MAJORDOMO ABORT (mj_digest)!! >> >> -l: No such file or directory >> >> ---------- >> >> Here is a copy of the digest portion (only) of the alias: >> >> test: "|/usr/local/majordomo/wrapper digest -r -C -l test-digest >> test-digest-outgoing" > From majordomo-users-owner Tue Feb 15 08:29:22 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA10553; Tue, 15 Feb 2000 08:20:50 -0800 (PST) Received: from student.dei.uc.pt (student.dei.uc.pt [193.137.203.231]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA10546 for ; Tue, 15 Feb 2000 08:20:41 -0800 (PST) Received: from localhost (rjperes@localhost) by student.dei.uc.pt (8.9.3/8.9.3) with ESMTP id QAA07078 for ; Tue, 15 Feb 2000 16:41:30 GMT Date: Tue, 15 Feb 2000 16:41:30 +0000 (WET) From: Ricardo Peres To: Majordomo Users Subject: Blank Mail Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I have this problem with majordomo: majordomo always sends mails to a list without the original mail's body or subject; also, the sender is always listname-owner, not the person who first sent the mail. I am pretty sure the configuration of majordomo and the lists are ok. Permissions are ok too, I think. Has anyone ever had this problem? Any ideas on how to solve this? TIA! ----------------------------------------------------------------------------- Ricardo Peres DSG Researcher E-Mail: rjperes@student.dei.uc.pt Cellular: +351 919459192 ICQ: 32940804 Dependable Systems Group Informatics Engineering Department University of Coimbra PORTUGAL ----------------------------------------------------------------------------- From majordomo-users-owner Tue Feb 15 08:46:25 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA10576; Tue, 15 Feb 2000 08:23:53 -0800 (PST) Received: from raven.a001.sprintmail.com (raven.prod.itd.earthlink.net [209.178.63.9]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA10567 for ; Tue, 15 Feb 2000 08:23:46 -0800 (PST) Received: from earthlink (sdn-ar-005waseatP159.dialsprint.net [168.191.237.95]) by raven.a001.sprintmail.com (8.8.7/8.8.5) with SMTP id IAA17439; Tue, 15 Feb 2000 08:39:42 -0800 (PST) Message-ID: <003401bf77d3$36e44e80$0100a8c0@earthlink> Reply-To: "Chris McEwen" From: "Chris McEwen" To: "Niko!" , References: <38A93C58.A7942BAB@unina.it> Subject: Re: Information bounces... is it possible ? Date: Tue, 15 Feb 2000 08:39:21 -0800 Organization: Socrates Press, Keyport WA MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk There are a couple of ways you could do this. If you have access to the aliases file on your server you can set up an autoresponder. Or you can use an autoresponder in a mail client, though this would wait until you check your mail to respond to the sender. -- Chris McEwen Socrates Press, Keyport WA chris@nwstamps.com ----- Original Message ----- From: Niko! To: Sent: Tuesday, February 15, 2000 3:45 AM Subject: Information bounces... is it possible ? Hello! I manage several moderated lists, and i'd like to know if is it possible to send users posting to my lists an automated message like: "Your message to the list xxxxxx was accepted and sent to xxxx (list-owner) for approval! if possible it will be approved in 24 hours. Thanks". Regards Niko From majordomo-users-owner Tue Feb 15 09:53:11 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA11397; Tue, 15 Feb 2000 09:34:21 -0800 (PST) Received: from smtp.mathworks.com (turing.mathworks.com [144.212.95.101]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA11390 for ; Tue, 15 Feb 2000 09:34:13 -0800 (PST) Received: from skywalker.mathworks.com (skywalker.mathworks.com [144.212.2.82]) by smtp.mathworks.com (8.9.3/8.9.3) with ESMTP id MAA01525 for ; Tue, 15 Feb 2000 12:50:57 -0500 (EST) Received: from localhost (tallpaul@localhost) by skywalker.mathworks.com (8.9.3/8.9.3) with ESMTP id MAA11005 for ; Tue, 15 Feb 2000 12:50:56 -0500 (EST) X-Authentication-Warning: skywalker.mathworks.com: tallpaul owned process doing -bs Date: Tue, 15 Feb 2000 12:50:55 -0500 (EST) From: Paul English To: majordomo-users@GreatCircle.COM Subject: moderated list question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I'm new to the list and of course I have a question. I'm trying to set up my first moderated list, but all posts are going through with no approval requested or required. The FAQ says to simply set moderate = yes which I did. majordomo version is 1.94.4 perl version is 5.004_04 os is Solaris 2.6 mailer is sendmail 8.9.3 Thanks, Paul From majordomo-users-owner Tue Feb 15 10:57:37 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA12161; Tue, 15 Feb 2000 10:45:32 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA12143 for ; Tue, 15 Feb 2000 10:45:16 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id OAA28751; Tue, 15 Feb 2000 14:01:10 -0500 (EST) Date: Tue, 15 Feb 2000 14:01:09 -0500 (EST) From: "Bill Casti (System Admin)" To: mjn cc: majordomo-users@GreatCircle.COM Subject: Re: Mderated 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 Sounds like a "too many cooks" scenario.... On Tue, 15 Feb 2000, mjn wrote: > > Anyone have any advice for setting up a list with multiple > moderators? Is it 1) possible and/or 2) advisable? > > ____________________________ > Mike Neuharth > ADCS Technology Specialist > http://www.umn.edu/adcs > > E-Mail : mjn@tc.umn.edu > Page Mail : 6123065932@messaging.sprintpcs.com > http://nifty.dsl.visi.com/ > ____________________________ > > From majordomo-users-owner Tue Feb 15 13:10:05 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA13616; Tue, 15 Feb 2000 13:06:56 -0800 (PST) Received: from sun1.rentpayment.com ([38.194.38.165]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA13608 for ; Tue, 15 Feb 2000 13:06:49 -0800 (PST) Received: from chesternet.net (node1.chesternet.net [207.87.127.98]) by sun1.rentpayment.com (Netscape Messaging Server 4.1) with ESMTP id FPZQ2V00.C00 for ; Tue, 15 Feb 2000 16:23:19 -0500 Message-ID: <38A9C37E.F5B43B73@chesternet.net> Date: Tue, 15 Feb 2000 16:22:06 -0500 From: "Daniel chester" Reply-To: talamar@chesternet.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo Users Subject: Majordomo and Netscape Messaging Server Content-Type: multipart/mixed; boundary="------------601FB3E7A675C94A50E73988" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. --------------601FB3E7A675C94A50E73988 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm running Messaging Server 4.X with the laterst Majordomo on the latest Perl. All I ever get from the list is help messages. It doesn't matter if I send test messages from navigator, mailx, mail, etc... I'm using the To Program delivery. Anyone else have any luck? --------------601FB3E7A675C94A50E73988 Content-Type: text/x-vcard; charset=us-ascii; name="talamar.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Daniel Chester Content-Disposition: attachment; filename="talamar.vcf" begin:vcard n:Chester;Daniel tel;work:440-734-9348 x-mozilla-html:TRUE url:www.rentpayment.com org:RentPayment.COM adr:;;;;;; version:2.1 email;internet:dan@chesternet.net title:Technical Analyst fn:Daniel Chester end:vcard --------------601FB3E7A675C94A50E73988-- From majordomo-users-owner Tue Feb 15 13:32:44 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA13460; Tue, 15 Feb 2000 12:55:31 -0800 (PST) Received: from notrump.whiteoaks.com (notrump.whiteoaks.com [216.200.131.96]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA13450 for ; Tue, 15 Feb 2000 12:55:20 -0800 (PST) Received: from localhost (mojo@localhost [127.0.0.1]) by notrump.whiteoaks.com (8.9.3/8.9.3) with ESMTP id NAA06925 for ; Tue, 15 Feb 2000 13:12:05 -0800 Date: Tue, 15 Feb 2000 13:12:05 -0800 (PST) From: Morris Jones To: majordomo-users@greatcircle.com Subject: "virtual hosting" 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 I did a little hack to majordomo 1.94 to add a "-w " option to the majordomo script. This allows me to specify the $whereami variable on the command line of majordomo. If -w is specified, then I also set the $whoami variable, which clobbers the $whoami from majordomo.cf. At my site I host mailing lists for three astronomy clubs and one bridge club, and while it's no big deal to have all of the majordomo administrative email referring to "Majordomo@whiteoaks.com," I find it aesthetically pleasing to use the registered domain names for each of the organizations involved. Below is a patch, if anyone is interested. Does anyone have a good reason not to do this? Best regards, Mojo -- Morris Jones <*> Campbell, CA mojo@whiteoaks.com http://www.whiteoaks.com Patch to add "-w " option to majordomo follows: ------------------ cut here ------------------- cut here ---------------- diff -Naur old/majordomo new/majordomo --- old/majordomo Tue Feb 15 21:02:14 2000 +++ new/majordomo Tue Feb 15 21:01:51 2000 @@ -26,6 +26,7 @@ # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; +undef $newwhereami; while ($ARGV[0]) { # parse for config file or default list if ($ARGV[0] =~ /^-C$/i) { # sendmail v8 clobbers case @@ -36,6 +37,10 @@ $deflist = $ARGV[1]; shift(@ARGV); shift(@ARGV); + } elsif ($ARGV[0] eq "-w") { + $newwhereami = $ARGV[1]; + shift(@ARGV); + shift(@ARGV); } else { die "Unknown argument $ARGV[0]\n"; } @@ -45,6 +50,10 @@ } require "$cf"; +if (defined($newwhereami)) { + $whereami = $newwhereami; + $whoami = "Majordomo\@$whereami"; +}; # Go to the home directory specified by the .cf file chdir("$homedir") || die "chdir to $homedir failed, $!\n"; From majordomo-users-owner Tue Feb 15 14:41:20 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA14355; Tue, 15 Feb 2000 14:33:22 -0800 (PST) Received: from server1.mich.com (server1.mich.com [198.108.16.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA14348 for ; Tue, 15 Feb 2000 14:33:16 -0800 (PST) Received: from lindy.nuge.com (root@pm011-043.dialip.mich.com [207.75.116.155]) by server1.mich.com (8.9.3/8.9.3) with ESMTP id RAA17651; Tue, 15 Feb 2000 17:49:59 -0500 Received: from localhost (rtg@localhost) by lindy.nuge.com (8.9.3/8.9.3) with ESMTP id RAA04461; Tue, 15 Feb 2000 17:49:56 -0500 X-Authentication-Warning: lindy.nuge.com: rtg owned process doing -bs Date: Tue, 15 Feb 2000 17:49:55 -0500 (EST) From: Rick Green To: Paul English cc: majordomo-users@GreatCircle.COM Subject: Re: moderated list question 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, 15 Feb 2000, Paul English wrote: > > Hi, > I'm new to the list and of course I have a question. I'm trying to > set up my first moderated list, but all posts are going through with no > approval requested or required. The FAQ says to simply set moderate = yes > which I did. > > majordomo version is 1.94.4 > perl version is 5.004_04 > os is Solaris 2.6 > mailer is sendmail 8.9.3 > make sure that the list is piped thru the resend script, where the moderate check is done. Compare your alias with the _second_ example in the NEWLIST document. -- Rick Green From majordomo-users-owner Tue Feb 15 18:02:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA16168; Tue, 15 Feb 2000 17:52:58 -0800 (PST) Received: from mercury.libpubinc.com (mercury.libpubinc.com [208.249.203.55]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA16161 for ; Tue, 15 Feb 2000 17:52:52 -0800 (PST) Received: from dmoyer (dhcp93.libpubinc.com [208.249.203.93]) by mercury.libpubinc.com (8.9.3/8.9.3) with ESMTP id SAA09821 for ; Tue, 15 Feb 2000 18:09:39 -0800 Message-Id: <4.2.2.20000215180037.00a90840@mercury.libpubinc.com> X-Sender: dmoyer@mercury.libpubinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 15 Feb 2000 18:09:37 -0800 To: majordomo-users@GreatCircle.COM From: Dave Moyer Subject: infinite loop {shudder} Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Greetings, I came across an interesting problem last night and I was wondering if any one else had seen it and/or might have a suggestion on how to avoid it in the future. The problem is this: I had a list of people to add to a particular majordomo list. I wrote a short perl script to use sendmail to automatically send the names to MajorDomo and add them to the list. It all worked fine except for one poor fellow. It turns out he was on vacation and his vacation auto-responder continually responded to the confirmation e-mail. This caused a hideous loop that was creating 100-150 bounces every 5 minutes. Needless to say, I was amazed this morning when I found out I had 5300 emails (most of which were letting me know about the problem with this one address). I have a theory on why this happened. I believe that the auto-responder responded to majordomo, copying the body of the message in the response. Majordomo would then parse the returned message and see the word "Subscribe" and attempt to subscribe this poor fellow again. Since "Subscribe" shows up more than once in the message, the number of subscribe requests increased geometrically each time the vacation auto-responder replied. If any one else has an idea, please let me know. Anyway, if any one has an idea on how to avoid this particular problem in the future, I would be most happy to hear it. Dave From majordomo-users-owner Tue Feb 15 18:19:30 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA16091; Tue, 15 Feb 2000 17:42:59 -0800 (PST) Received: from raven.a001.sprintmail.com (raven.prod.itd.earthlink.net [209.178.63.9]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA16084 for ; Tue, 15 Feb 2000 17:42:53 -0800 (PST) Received: from earthlink (sdn-ar-005waseatP022.dialsprint.net [168.191.237.30]) by raven.a001.sprintmail.com (8.8.7/8.8.5) with SMTP id RAA26609; Tue, 15 Feb 2000 17:59:38 -0800 (PST) Message-ID: <005101bf7821$6ec94000$0100a8c0@earthlink> Reply-To: "Chris McEwen" From: "Chris McEwen" To: "mjn" , References: Subject: Re: Mderated lists... Date: Tue, 15 Feb 2000 17:59:15 -0800 Organization: Socrates Press, Keyport WA MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Yes, this is entirely possible. You want to set up an alias on your mail server with multiple addresses. For example, in your aliases file, you would have list-moderator: first-person@his-isp.com, second-one@next-isp.com, third-moderator@the-last-isp.com (above line broken into three to avoid line-wrap). Run newaliases and you're done. This assumes you have access to your unix server's mail aliases file, or can talk the sysad into doing this for you. Once done, all mail to list-moderator@your-isp.com will be forwarded to the addresses given. Is it advisable? That depends on how well the moderators work together. -- Chris McEwen Socrates Press, Keyport WA chris@nwstamps.com ----- Original Message ----- From: mjn To: Sent: Tuesday, February 15, 2000 6:35 AM Subject: Mderated lists... Anyone have any advice for setting up a list with multiple moderators? Is it 1) possible and/or 2) advisable? ____________________________ Mike Neuharth ADCS Technology Specialist http://www.umn.edu/adcs E-Mail : mjn@tc.umn.edu Page Mail : 6123065932@messaging.sprintpcs.com http://nifty.dsl.visi.com/ ____________________________ From majordomo-users-owner Tue Feb 15 20:50:03 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id UAA17706; Tue, 15 Feb 2000 20:34:30 -0800 (PST) Received: from dsl-207-105-45-243.hollywood.relaypoint.net (dsl-207-105-45-243.hollywood.relaypoint.net [207.105.45.243]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA17699 for ; Tue, 15 Feb 2000 20:34:24 -0800 (PST) Received: from pajamian.dhs.org (WLA19-16.WLA.Access1.net [63.192.92.169]) by dsl-207-105-45-243.hollywood.relaypoint.net (8.9.3/8.9.3) with ESMTP id UAA22836 for ; Tue, 15 Feb 2000 20:59:14 -0800 Message-ID: <38AA2DD6.4BDA2911@pajamian.dhs.org> Date: Tue, 15 Feb 2000 20:55:50 -0800 From: Peter Ajamian X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users list Subject: [MajorCool] Looking for Patches... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Does anyone know of/have/know where I can get a patch for MajorCool to allow web access to archives? I will take what I can get but I am especially interested in one that is searchable. I just want to find out before I re-invent the wheel. I am also interested in security patches to allow for encrypted passwords for both users and admins, if anyone knows of anything like this I would be most greatfull. TIA, Peter From majordomo-users-owner Tue Feb 15 21:13:14 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA18123; Tue, 15 Feb 2000 21:01:22 -0800 (PST) Received: from virtual-solutions.net (virtual-solutions.net [192.41.14.175]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA18116 for ; Tue, 15 Feb 2000 21:01:18 -0800 (PST) Received: from office (19-139.018.popsite.net [64.24.32.139]) by virtual-solutions.net (8.8.5) id WAA02090; Tue, 15 Feb 2000 22:17:56 -0700 (MST) X-Authentication-Warning: virtual-solutions.net: Host 19-139.018.popsite.net [64.24.32.139] claimed to be office Message-Id: <4.2.0.58.20000215211423.03a7a6b0@pop.esosoft.com> X-Sender: lisa@pop.virtual-solutions.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 15 Feb 2000 21:18:23 -0800 To: majordomo-users@greatcircle.com From: Lisa Bohm Subject: MJ2 and server resources... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, all- Is anyone having trouble with MJ2 eating up a lot more server resources than the 1.94.X versions? I was hoping to avoid upgrading to MJ2 until my Lyris server is built (but because majordomo still makes list services affordable to people, I will always keep it in the repertoire), but I think I'll need to upgrade to it sooner than later... I played with an older version of MJ2, I'm suspecting it was one of the alpha versions, and it just seemed to really bog down the server. Anyone with thoughs, comments, good or bad, about the comparison between 1.94.X and 2.0b are greatly appreciated. Regards- Lisa From majordomo-users-owner Tue Feb 15 21:42:40 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA18377; Tue, 15 Feb 2000 21:33:59 -0800 (PST) Received: from europe.std.com (europe.std.com [199.172.62.20]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA18369 for ; Tue, 15 Feb 2000 21:33:54 -0800 (PST) Received: from world.std.com (world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id AAA07730; Wed, 16 Feb 2000 00:50:42 -0500 (EST) Received: from localhost (jkaplan@localhost) by world.std.com (8.9.3/8.9.3) with ESMTP id AAA18789; Wed, 16 Feb 2000 00:50:41 -0500 (EST) Date: Wed, 16 Feb 2000 00:50:41 -0500 From: Jeffrey Kaplan To: Bob cc: Majordomo Users Subject: Re: Banned users. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Mon, 14 Feb 2000, Bob wrote: > I have added her email address to taboo_header in the list.config 2 > different ways and her email still goes out to the list without being > bounced. I am sure I must be overlooking something simple as most > newbies do. The first time I added her to taboo_headers I did it like > this: > > # taboo_headers [regexp_array] (undef) > # If any of the headers matches one of these regexps, then the > # message will be bounced for review. > taboo_headers << END > /^from:.*user@ix.netcom.com/i > END You have to "quote" the punctuation marks: /^From:.*user\@ix\.netcom\.com/i -- Jeffrey Kaplan gordol@gordol.org <*> I'm set up for PGP. Are you? "If I fall then another will take my place, and another, and another!" "But your great cause..." "This is my cause, LIFE! One life or a billion, it's all the same." (Amb. Delenn and Sebastian, B5 "Comes The Inquisitor") From majordomo-users-owner Wed Feb 16 09:45:45 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA27211; Wed, 16 Feb 2000 09:25:30 -0800 (PST) Received: from chinet.chinet.com ([209.219.112.20]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA27204 for ; Wed, 16 Feb 2000 09:25:24 -0800 (PST) Received: from localhost (ahk@localhost) by chinet.chinet.com (8.9.3/8.9.3) with ESMTP id LAA03079 for ; Wed, 16 Feb 2000 11:42:18 -0600 Date: Wed, 16 Feb 2000 11:42:18 -0600 (CST) From: "Adam H. Kerman" To: Majordomo Users Subject: Re: Banned users. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >From: Bob >Date: Mon, 14 Feb 2000 12:40:15 -0800 (PST) >I have added her email address to taboo_header in the list.config 2 >different ways and her email still goes out to the list without being >bounced. I am sure I must be overlooking something simple as most >newbies do. The first time I added her to taboo_headers I did it like >this: > > # taboo_headers [regexp_array] (undef) > # If any of the headers matches one of these regexps, then the > # message will be bounced for review. >taboo_headers << END >/^from:.*user@ix.netcom.com/i >END >The second time I did it like this: > > # taboo_headers [regexp_array] (undef) > # If any of the headers matches one of these regexps, then the > # message will be bounced for review. >taboo_headers << END >/^from: user@ix.netcom.com/i >END >BTW I am using 1.94.5 on a linux box. You neglected to escape the "@" with a "\", as currently required by Perl. Read the file "list-owner-info" in the Majordomo distribution for more tips. From majordomo-users-owner Wed Feb 16 12:11:30 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28293; Wed, 16 Feb 2000 10:09:47 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28285 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:09:45 -0800 (PST) Received: from www.migvan.co.il ([192.116.100.161]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id BAA14967 for ; Mon, 14 Feb 2000 01:20:40 -0800 (PST) Received: from migvan.co.il [192.116.100.187] by www.migvan.co.il with ESMTP (SMTPD32-6.00) id ACBA14D2013E; Mon, 14 Feb 2000 11:36:58 +0200 Message-ID: <38A7CB7C.EA459D40@migvan.co.il> Date: Mon, 14 Feb 2000 11:31:40 +0200 From: Eric Yellin Organization: Migvan Effect X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Web interface Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am looking for a CGI script that will give a web interface for list managment and subscribe-unsubscribe. The solution I am looking for should give a web interface to create and control lists by a list administrator and manage personal accounts by users. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Eric Yellin - Migvan Effect Internet Solutions for Organizations Eric@migvan.co.il http://www.migvan.co.il ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From majordomo-users-owner Wed Feb 16 12:12:33 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28418; Wed, 16 Feb 2000 10:11:42 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28407 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:11:39 -0800 (PST) Received: from kirkwood.hoosier.net (kirkwood.hoosier.net [206.106.64.12]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA21948 for ; Mon, 14 Feb 2000 09:51:50 -0800 (PST) Received: from localhost (drernst@localhost) by kirkwood.hoosier.net (8.9.3/8.8.7) with ESMTP id NAA22282; Mon, 14 Feb 2000 13:08:22 -0500 Date: Mon, 14 Feb 2000 13:08:22 -0500 (EST) From: David Ernst X-Sender: drernst@kirkwood.hoosier.net To: majordomo-users@greatcircle.com cc: info@bloomington.in.us Subject: uid 91 from out of nowhere! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello. We're running majordomo 1.94.4 on a redhat linux 6.0 system. We're having a strange problem. Whenever we try to do something that changes a list (such as subscribe or unsubscribe) we get the following error: -- MAJORDOMO ABORT (mj_majordomo)!! While running with an effective uid of 91 and an effective gid of 91 91 12, Majordomo ran into the following problems: Unable to create log file in /var/lib/majordomo, check permissions. Unable to write to list directory $listdir, check permissions on /var/lib/majordomo/lists -- weird things here: majordomo has uid 16, not 91, in fact there is no user with id 91. $homedir should be set to /usr/local/majordomo, not /var/lib/majordomo. I ran config-test as described in readme and it said --------------------- euid/egid checks --------------------- effective user = majordomo (uid 16) effective group = daemon wheel disk adm sys daemon bin root (gid 2 10 6 4 3 2 1 0 ) ---------------------- uid/gid checks ---------------------- real user = majordomo (uid 16) real group = daemon wheel disk adm sys daemon bin root (gid 2 10 6 4 3 2 1 0 ) ------------------------------------------------------------ so we're quite confused as to what's happening. Any suggestions? Thanks in advance! David From majordomo-users-owner Wed Feb 16 12:40:12 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28329; Wed, 16 Feb 2000 10:10:22 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28319 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:10:19 -0800 (PST) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA20136 for ; Mon, 14 Feb 2000 07:06:44 -0800 (PST) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id IAA18855 for ; Mon, 14 Feb 2000 08:23:04 -0700 (MST) Received: from ip-84-56.tus.primenet.com(207.218.84.56), claiming to be "gateway.localnet" via SMTP by smtp03.primenet.com, id smtpdAAA0JaiHK; Mon Feb 14 08:22:44 2000 Received: from bob.localnet (bob.localnet [192.168.1.1]) by gateway.localnet (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id IAA11422 for ; Mon, 14 Feb 2000 08:22:46 -0700 Received: by primenet.com via sendmail from stdin id (Debian Smail3.2.0.102) for majordomo-users@greatcircle.com; Mon, 14 Feb 2000 08:22:45 -0700 (MST) Date: Mon, 14 Feb 2000 08:22:45 -0700 From: Bob Nielsen To: majordomo-users@greatcircle.com Subject: abort message Message-ID: <20000214082245.A14612@bob.localnet> References: <20000209042434.A4864@bob.localnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <20000209042434.A4864@bob.localnet>; from nielsen on Wed, Feb 09, 2000 at 04:24:34AM -0700 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm resending this because I never saw it hit the list (??). On Wed, Feb 09, 2000 at 04:24:34AM -0700, Bob Nielsen wrote: > When trying to approve an unsubscribe request, I get the following > abort message (1003 is the UID for majordomo): > > MAJORDOMO ABORT (mj_majordomo)!! > > chown(1003, 1, "/usr/local/majordomo-1.94.5/lists/mylist.new"): > Operation not permitted > > A listing shows that mylist.new has been created as owned by daemon, > group daemon. All other files in this directory are majordomo.daemon. > > Approval of subscribe requests doesn't seem to be affected. > > I didn't have this problem with majordomo-1.94.4. Has something > changed? > > -- > Bob Nielsen, N7XY (RN2) nielsen@primenet.com > Tucson, AZ DM42nh QRP-L #1985 http://www.primenet.com/~nielsen From majordomo-users-owner Wed Feb 16 13:14:35 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28431; Wed, 16 Feb 2000 10:11:50 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28421 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:11:46 -0800 (PST) Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA22168 for ; Mon, 14 Feb 2000 10:04:44 -0800 (PST) Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate2.mot.com (VWALL-IN-motgate2 2.0) with ESMTP id LAA26173 for ; Mon, 14 Feb 2000 11:21:18 -0700 (MST)] Received: [from msgtls1.sps.mot.com (msgtls1.sps.mot.com [216.15.65.1]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id LAA15001 for ; Mon, 14 Feb 2000 11:21:17 -0700 (MST)] Received: from email.sps.mot.com ([223.188.37.104]) by msgtls1.sps.mot.com (Netscape Messaging Server 3.61) with ESMTP id AAA360D for ; Mon, 14 Feb 2000 19:21:14 +0100 Message-ID: <38A84799.72AD5610@email.sps.mot.com> Date: Mon, 14 Feb 2000 19:21:13 +0100 From: "Leslie Sherman (r47842)" Organization: SoCDT, Motorola X-Mailer: Mozilla 4.06 [en] (X11; I; SunOS 5.6 sun4u) MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Please help me solve this 1.94.5 puzzle of a problem! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I just upgraded my lists to 1.94.5 from 1.94.4. I had no problems with installing the new version. While testing the installation I was able to *email requests to majordomo@domain.com like help, lists, which, etc but am not able to * send an email to a test list and receive back the email message from the list. The curious thing is that the message is archived correctly in the test list and I never receive an error message. Even though it seems to work correctly, I (the only user to the list) never receive any of the messages I send to it. The list's /etc/aliases entries are: mj-test: "|/home/admin_user/majordomo/majordomo/wrapper resend -l mj-test mj-test-out going" mj-test-outgoing: :include:/home/admin_user/majordomo/majordomo/lists/mj-test, "|/home/admin_user/majordomo/majordomo/wrapper archive2.pl -a -m -f /home/admin_user/majordomo/majordomo/lists/mj-test.archive" owner-mj-test: lists_owner owner-mj-test-outgoing: owner-mj-test mj-test-owner: owner-mj-test mj-test-request: "|/home/minerva/majordomo/majordomo/wrapper majordomo -l mj-test" mj-test-approval: owner-mj-test -- -------------------------------------------------------- Leslie A. Sherman SoCDT-Europe Motorola Munich phone: +49-89-92103-459 Schatzbogen 7 Fax : +49-89-92103-680 81829 Munich email: R47842@email.sps.mot.com - Germany - -------------------------------------------------------- From majordomo-users-owner Wed Feb 16 13:27:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28710; Wed, 16 Feb 2000 10:15:28 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28700 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:15:23 -0800 (PST) Received: from dxcnaf.cnaf.infn.it (dxcnaf.cnaf.infn.it [131.154.3.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA09081 for ; Tue, 15 Feb 2000 06:15:57 -0800 (PST) Received: from cnaf.infn.it (pluto.cnaf.infn.it [131.154.3.27]) by dxcnaf.cnaf.infn.it (8.8.8/8.8.8) with ESMTP id PAA23115; Tue, 15 Feb 2000 15:32:36 +0100 (MET) Message-ID: <38A96147.D23C9CE5@cnaf.infn.it> Date: Tue, 15 Feb 2000 15:23:03 +0100 From: Giulia Vita Finzi Organization: INFN CNAF X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo-users@GreatCircle.COM Subject: limit posting to my domain Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I installed majordomo-1.94.4. It seems that the configuration doesn't allow to limit posting to a domain, so I would like to know if someone can suggest how to solve this problem (without moderating lists). Many thanks, Giulia Vita Finzi From majordomo-users-owner Wed Feb 16 13:28:43 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28541; Wed, 16 Feb 2000 10:13:18 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28519 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:13:10 -0800 (PST) Received: from mail.globalynk.net (1Cust179.tnt5.sfo3.da.uu.net [63.23.15.179]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id SAA29598; Mon, 14 Feb 2000 18:53:06 -0800 (PST) Message-ID: <73754.20479@mail.globalynk.net> From: "merch22229@mailcity.com" Subject: Business Necessity (26529) Date: Fri, 05 Mar 1999 17:40:13 -0400 (EDT) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk ACCEPT CREDIT CARDS OVER THE INTERNET Regardless of Your Credit Rating! Limited Time Offer ZERO SETUP FEES!! We've Helped 1000's of Businesses INCREASE PROFITS DRAMATICALLY! Call Us Today and Put YOUR BUSINESS ON THE FAST TRACK! >>>>> CALL 1(800) 644-2659 <<<<< This message is sent in compliance of the new email bill section 301. Per Section 301, Paragraph (a)(2)(C) of S. 1618, further transmissions to you by the sender of this email may be stopped at no cost to you. TO REMOVE CLICK ON mailto:merch22230@mailcity.com?subject=remove *************** 39447 From majordomo-users-owner Wed Feb 16 13:40:51 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28471; Wed, 16 Feb 2000 10:12:17 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28461 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:12:14 -0800 (PST) Received: from mailbox.cyberspace.com.br (mailbox.cyberspace.com.br [200.246.107.17]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA22914 for ; Mon, 14 Feb 2000 11:09:51 -0800 (PST) Received: from dantas ([200.246.107.207]) by mailbox.cyberspace.com.br (Post.Office MTA v3.5.2 release 221 ID# 0-0U10L2S100) with SMTP id br for ; Mon, 14 Feb 2000 17:27:19 -0300 Message-ID: <001a01bf7729$958d67a0$0200a8c0@dantas> Reply-To: "Eduardo Dantas Correia" From: "Eduardo Dantas Correia" To: Subject: i need majordomo Date: Mon, 14 Feb 2000 17:25:00 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk im looking for majordomo download !!! hellp me please !! Eduardo Dantas Correia ICQ 14646201 021-11-9322-3724 www.welcome.to/dantas From majordomo-users-owner Wed Feb 16 13:44:12 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28737; Wed, 16 Feb 2000 10:15:51 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28727 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:15:49 -0800 (PST) Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA10298 for ; Tue, 15 Feb 2000 08:03:27 -0800 (PST) Received: from [199.174.130.245] (user-33qt0nl.dialup.mindspring.com [199.174.130.245]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id LAA11924 for ; Tue, 15 Feb 2000 11:20:08 -0500 (EST) Mime-Version: 1.0 X-Sender: mirator@pop.mindspring.com Message-Id: In-Reply-To: <20000215084517.A29007@clifford.inch.com> References: <2.2.32.20000214071355.006b9f70@jetty.net> <20000215084517.A29007@clifford.inch.com> Date: Tue, 15 Feb 2000 10:20:31 -0600 To: Majordomo-Users@GreatCircle.COM From: Donna Subject: replacelist Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi - I hope I am asking this question in the right place. I am in the process of moving an existing list to a majordomo list. I am familiar with majordomo commands but when I tried to use the replacelist command it was not recognized. I would like to avoid having to "approve subscribe" each list member. Thanks for your help! Donna From majordomo-users-owner Wed Feb 16 13:57:29 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA00496; Wed, 16 Feb 2000 12:13:29 -0800 (PST) Received: from firewall.globeset.com (firewall.globeset.com [207.239.133.67]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA00489 for ; Wed, 16 Feb 2000 12:13:21 -0800 (PST) Received: from earth.globeset.com (earth.globeset.com [10.1.1.5]) by firewall.globeset.com (8.9.3/8.9.3) with ESMTP id OAA27441 for ; Wed, 16 Feb 2000 14:30:16 -0600 (CST) Received: from globeset.com (funk1ntw.globeset.com [10.1.194.156]) by earth.globeset.com (8.9.3/8.9.3) with ESMTP id OAA08571 for ; Wed, 16 Feb 2000 14:30:16 -0600 (CST) Message-ID: <38AB08D8.A364186@globeset.com> Date: Wed, 16 Feb 2000 14:30:16 -0600 From: Wade Funk Organization: Globeset X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Digest creation problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Any ideas? Wade Subject: MAJORDOMO ABORT (mj_digest) Date: Wed, 16 Feb 2000 14:23:38 -0600 (CST) From: Majordomo@Globeset.com To: Majordomo-Owner@Globeset.com MAJORDOMO ABORT (mj_digest)!! open(DIGEST, ">/opt/depot/majordomo-1.94.4/lists/sysoperations-digest.archive/v01.n001"): No such file or directory From majordomo-users-owner Wed Feb 16 14:00:00 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28680; Wed, 16 Feb 2000 10:15:14 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28670 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:15:11 -0800 (PST) Received: from web3.hq.eso.org (web3.hq.eso.org [134.171.7.4]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA08383 for ; Tue, 15 Feb 2000 05:12:33 -0800 (PST) Received: from mailrelay.hq.eso.org by web3.hq.eso.org with ESMTP (8.8.5/ eso-5.3) id OAA06827; Tue, 15 Feb 2000 14:29:26 +0100 (MET) Received: from eso.org (sjohnsto@fenris [134.171.40.51]) by mailrelay.hq.eso.org (8.8.5/eso_cl_6.0) with ESMTP id OAA24477 for ; Tue, 15 Feb 2000 14:29:36 +0100 (MET) Message-ID: <38A9548A.10823E3B@eso.org> Date: Tue, 15 Feb 2000 14:28:42 +0100 From: Stephen Johnston Organization: Terma Elektronic AS X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo-Users@GreatCircle.COM Subject: From line includes hostname Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Our From line is majordomo@. it should be simply @ ? I have checked the whoami and whereami in the majordomo.cf and it appears to be ok. Any ideas? Thanks, Stephen. -- Stephen Johnston Phone: +49 89 32006322 UNIX Administrator Fax : +49 89 32006380 European Southern Observatory Karl-Schwarzschild-Strasse 2 D-85748 Garching bei Muenchen http://www.eso.org From majordomo-users-owner Wed Feb 16 14:11:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28697; Wed, 16 Feb 2000 10:15:21 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28688 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:15:18 -0800 (PST) Received: from firewall.unesco.org (mercure.unesco.org [193.242.192.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA08916 for ; Tue, 15 Feb 2000 06:00:32 -0800 (PST) Received: from internet.unesco.org (gateway.unesco.org [193.242.192.33]) by firewall.unesco.org (8.6.12/kit5.1-1811) with ESMTP id OAA21532 ; Tue, 15 Feb 2000 14:49:08 +0100 Received: from unesco.org ([10.2.99.20]) by internet.unesco.org (8.6.12/kit5.1-1507) with ESMTP id OAA105500 ; Tue, 15 Feb 2000 14:50:56 +0100 Message-ID: <38A95E11.33A19A3C@unesco.org> Date: Tue, 15 Feb 2000 15:09:21 +0100 From: "Yassin Baruani, Walid" Reply-To: y.baruani@unesco.org Organization: UNESCO X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: majordomo 1.94.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk hello everyone, i have installed MD 1.94.5 on my LINUX SUSE 6.0 Box The isntallation went fine. and the check ./wrapper config-test as non MD user and non root revealed no anomalities at all. But MD doesnt respond to the commands such as help, info, subscribe etc etc. In desparation, I even made all files world-readable but in vain. I set user as user majordom(504) and grp majordom (102) I would any helpful idea/suggestions be sent to me personally at this e mail: y.baruani@unesco.org Regards WY baruani. UNESCO PARIS FRANCE From majordomo-users-owner Wed Feb 16 14:20:43 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28663; Wed, 16 Feb 2000 10:15:03 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28645 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:14:59 -0800 (PST) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id DAA07654 for ; Tue, 15 Feb 2000 03:53:21 -0800 (PST) Received: from solva.ifi.uio.no (1368@solva.ifi.uio.no [129.240.64.20]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with SMTP id NAA12212; Tue, 15 Feb 2000 13:10:01 +0100 (MET) Received: (from thomasg@localhost) by solva.ifi.uio.no ; Tue, 15 Feb 2000 13:10:00 +0100 Date: Tue, 15 Feb 2000 13:09:59 +0100 From: Thomas Gramstad Reply-To: thomasg@ifi.uio.no To: majordomo-users@greatcircle.com Subject: Re: html-tags disturbing commands In-Reply-To: Atle Weibell 's message of Tue, 8 Feb 2000 18:28:34 +0100 (MET) References: Message-ID: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Hi, > > I'm the owner of a list that is supposed to be used by a lot of students > using some web-based Lotus Notes mail client. When they try to subscribe, > Majordomo reads the html-tags preceding and following the subscribe- > command, which causes an error, because the html-tags are not recognized > as part of a valid command. > > The Notes-administrator didn't know how to set up Notes to send plain > text, so the question is if there is a way to tell Majordomo to skip those > < >-tags? HTML tags do not belong in E-mail. See http://www.geocities.com/CapitolHill/1236/nomime.html or http://www.rootsweb.com/rootsweb/listowners/html-off.htm for instructions about how to turn them off in most mail clients. Thomas Gramstad thomasg@ifi.uio.no From majordomo-users-owner Wed Feb 16 14:22:55 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28501; Wed, 16 Feb 2000 10:13:03 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28491 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:13:01 -0800 (PST) Received: from vanakam.cc.columbia.edu (vanakam.cc.columbia.edu [128.59.35.23]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA25213 for ; Mon, 14 Feb 2000 14:00:46 -0800 (PST) Received: from sodor.cc.columbia.edu (sodor.cc.columbia.edu [128.59.39.201]) by vanakam.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id RAA04466; Mon, 14 Feb 2000 17:17:11 -0500 (EST) Date: Mon, 14 Feb 2000 17:17:06 -0500 From: Joseph Brennan Reply-To: Postmaster To: Peter Dominguez , majordomo-users cc: Postmaster Subject: Re: format of e-mail address in list with strip = no Message-ID: <17484890.3159537426@sodor.cc.columbia.edu> In-Reply-To: <20000214161129.K12846@pad.com> X-Mailer: Mulberry/2.0.0b8 (MacOS) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The comment (real name) has to be quoted as per RFC 822 if it contains almost any punctuation, like: "Dominguez, Peter" Joseph Brennan postmaster@columbia.edu Academic Technologies Group, Academic Information Systems (AcIS) --On Monday, February 14, 2000 16:11 -0500 Peter Dominguez wrote: > The comma in the following address tries to send e-mail to > Dominguez@localhost: > > Dominguez, Peter > > With out the comma i.e. > > Dominguez Peter > > seems to work fine. Is there a substitute character for the comma so that: > > Last Name, First Name can be used. From majordomo-users-owner Wed Feb 16 14:32:32 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28516; Wed, 16 Feb 2000 10:13:08 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28504 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:13:05 -0800 (PST) Received: from owbn.org (mail.owbn.org [206.156.227.57]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA28199 for ; Mon, 14 Feb 2000 16:59:06 -0800 (PST) Received: from rosander (helo=localhost) by owbn.org with local-esmtp (Exim 3.03 #1) id 12KWeI-0000Em-00 for majordomo-users@greatcircle.com; Mon, 14 Feb 2000 19:19:30 -0600 Date: Mon, 14 Feb 2000 19:19:30 -0600 (CST) From: To: majordomo-users@greatcircle.com Subject: Permissions problems with exim Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Well I've reached an impass. I'm running Red hat 6.1. The most current version of exim 3.0.3. Here's the problem. I've run the wrapper test and all comes up good. If I want the messages to be processed I've had to set up the lists as being owned by majordomo and the group being mail. Thus messages are sent out. If left as uid and gid as majordomo exim freezes all the messages and Majordomo does not distrubute messages. Here's the real trick. If I send a subscribe request to the list it works just fine. If I unsubscribe a user from a list Majordomo kicks back a chown (15,91 /usr/var/lib/majordomo/owbn-net.new ) operation not permitted. Obviously a permissions problem. If I change the group of the file to majordomo then it will unsubscribe users from the list but not messages are processed. I believe they call this a rock and a hard place. I'll try and watch this list but if anyone out there has any ideas could you reply to:rosander@owbn.org I would greatly apreciate any help. BTW I did make mail a member of the majordomo group. this did not work. From majordomo-users-owner Wed Feb 16 14:40:56 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA01181; Wed, 16 Feb 2000 13:20:27 -0800 (PST) Received: from smtp.mathworks.com (turing.mathworks.com [144.212.95.101]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA01173 for ; Wed, 16 Feb 2000 13:20:18 -0800 (PST) Received: from skywalker.mathworks.com (skywalker.mathworks.com [144.212.2.82]) by smtp.mathworks.com (8.9.3/8.9.3) with ESMTP id QAA25411; Wed, 16 Feb 2000 16:37:07 -0500 (EST) Received: from localhost (tallpaul@localhost) by skywalker.mathworks.com (8.9.3/8.9.3) with ESMTP id QAA02024; Wed, 16 Feb 2000 16:37:06 -0500 (EST) X-Authentication-Warning: skywalker.mathworks.com: tallpaul owned process doing -bs Date: Wed, 16 Feb 2000 16:37:06 -0500 (EST) From: Paul English To: Rick Green cc: majordomo-users@GreatCircle.COM Subject: Re: moderated list question 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, 15 Feb 2000, Rick Green wrote: > On Tue, 15 Feb 2000, Paul English wrote: > > set up my first moderated list, but all posts are going through with no > > approval requested or required. The FAQ says to simply set moderate = yes > > which I did. > > > > majordomo version is 1.94.4 > > perl version is 5.004_04 > > os is Solaris 2.6 > > mailer is sendmail 8.9.3 > > > make sure that the list is piped thru the resend script, where the > moderate check is done. Compare your alias with the _second_ > example in the NEWLIST document. That was exactly the problem, thanks for the tip. All of the other things which people were mentioned are appreciated too, but I luckily had those right. Paul From majordomo-users-owner Wed Feb 16 15:21:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28793; Wed, 16 Feb 2000 10:17:37 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28785 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:17:35 -0800 (PST) Received: from huron.dnepr.net.ua (GuardTower.dnepr.net.ua [195.248.180.229]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA18950 for ; Tue, 15 Feb 2000 22:56:20 -0800 (PST) Received: from ontario.dnepr.net.ua (ontario.dnepr.net.ua [195.248.180.33]) by huron.dnepr.net.ua (8.9.3/8.9.3) with ESMTP id JAA67523 for ; Wed, 16 Feb 2000 09:13:53 +0200 (EET) Received: from onyx.extra.dp.ua (mttyb.dnepr.net.ua [195.248.180.77]) by ontario.dnepr.net.ua (8.9.3/8.9.3z) with ESMTP id JAA91842 for ; Wed, 16 Feb 2000 09:13:01 +0200 (EET) Received: (from white@localhost) by onyx.extra.dp.ua (8.9.3/8.9.3/BSD) id JAA03256 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 09:13:00 +0200 (EET) Date: Wed, 16 Feb 2000 09:13:00 +0200 From: Alexander Prohorenko To: majordomo-users@greatcircle.com Subject: [Q] listing all mail-lists using 'lists' command Message-ID: <20000216091259.I931@la.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: Extra Solutions X-Operating-System: FreeBSD 2.2.8-STABLE i386 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello Everybody, Please, let me know what should I switch on/off [ ;-) ] to make my mail-lists be visible when somebody requests 'lists' command. Currently, I've several mail-lists, and only one of them is visible. 'test-l' mail-lists were visible both, and I've just renamed an apropriate files. Thank you for your attention and looking forward your replies, Sincerely, ps. Please, send me your replies directly to email, because I'm not subscribed to this mail-list. Thank you. -- Alexander Prohorenko, Extra Solutions ..."You labeled me - I'll label you, so I dub the Unforgiven" --Metallica From majordomo-users-owner Wed Feb 16 16:30:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28753; Wed, 16 Feb 2000 10:16:08 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28743 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:16:05 -0800 (PST) Received: from queernet.queernet.org (queernet.queernet.org [170.1.118.14]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA16654 for ; Tue, 15 Feb 2000 18:39:14 -0800 (PST) Received: from localhost (rogerk@localhost) by queernet.queernet.org (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e1G2tqt17545 Date: Tue, 15 Feb 2000 18:55:47 -0800 (PST) From: "Roger B.A. Klorese" To: Dave Moyer cc: majordomo-users@GreatCircle.COM Subject: Re: infinite loop {shudder} In-Reply-To: <4.2.2.20000215180037.00a90840@mercury.libpubinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Tue, 15 Feb 2000, Dave Moyer wrote: > Since > "Subscribe" shows up more than once in the message, the number of subscribe > requests increased geometrically each time the vacation auto-responder > replied. If any one else has an idea, please let me know. > Anyway, if any one has an idea on how to avoid this particular problem in > the future, I would be most happy to hear it. The actual "vacation auto-responder" would never do this, as it replies to the envelope sender. However, some broken reply scripts (and products, like vintage Microsoft Mail) will do this. Once you catch it, you could put the user-part of the address in the majordomo_dont_reply variable in the majordomo.cf and let the flood die down... but there's no way to do something that's right for good software and not deadly for broken software. -- ROGER B.A. KLORESE rogerk@QueerNet.ORG urgent: rogerk-page@QueerNet.ORG PO Box 14309 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy -- the refusal of joy!" -- Paul Rudnick From majordomo-users-owner Wed Feb 16 16:30:48 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28766; Wed, 16 Feb 2000 10:16:12 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28756 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:16:09 -0800 (PST) Received: from mail.linkup.net (mail.linkup.net [206.156.227.5]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA18333 for ; Tue, 15 Feb 2000 21:31:32 -0800 (PST) Received: by mail.linkup.net from localhost (router,SLMail V3.2); Tue, 15 Feb 2000 23:56:37 -0600 Received: by mail.linkup.net from [206.156.227.133] (206.156.227.133::mail daemon; unverified,SLMail V3.2); Tue, 15 Feb 2000 23:56:35 -0600 Mime-Version: 1.0 X-Sender: "Ross Anderson" Message-Id: Date: Tue, 15 Feb 2000 23:48:05 -0600 To: majordomo-users@GreatCircle.COM From: "Ross Anderson" Subject: Majordomo and Exim Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-SLUIDL: 7B8EFBD9-E31E11D3-8B5900A0-C98D89DD Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I having a heck of a time getting majordomo to work properly. Here's the setup. redhat 6.1 Exim 3.0.3 Majordomo 1.9.4 This is the problem I'm having. Exim freezes all messages for any of the lists if the lists are UID and GID by Majordomo. I've had majordomo working in a hacked sort of way. By making the list owned by majordomo and group of mail, Exim will deliver messages. I've added mail (the group that exim runs as) to the group majordomo. This didn't allow exim to deliver the mail either. This wouldn't be a problem except when majordomo itself processes an un-subscribe it fails because it is being denied the chown to the files because the group is mail. I get an Abort message operation not permitted. The lock file *.new gets all messed up. Anyone have any ideas? Ross Anderson DBA Cameron Theatre and Sound Home:1-218-291-9327 fax or voice. AOL IM:RossWolfie ICQ:20501774 E-mail: rosander@linkup.net Alt E-mail:Lonewolfnight@hotmail.com http://www.linkup.net/users/rosander/FM_LARP.html From majordomo-users-owner Wed Feb 16 16:41:08 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA02848; Wed, 16 Feb 2000 15:53:02 -0800 (PST) Received: from clifford.inch.com (clifford.inch.com [207.240.140.163]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA02841 for ; Wed, 16 Feb 2000 15:52:52 -0800 (PST) Received: (from omar@localhost) by clifford.inch.com (8.9.3/8.8.5) id SAA05599; Wed, 16 Feb 2000 18:12:34 -0500 Message-ID: <20000216181233.A5588@clifford.inch.com> Date: Wed, 16 Feb 2000 18:12:33 -0500 From: Omar Thameen To: Stephen Johnston , Majordomo-Users@GreatCircle.COM Subject: Re: From line includes hostname References: <38A9548A.10823E3B@eso.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <38A9548A.10823E3B@eso.org>; from Stephen Johnston on Tue, Feb 15, 2000 at 02:28:42PM +0100 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Are you running sendmail? If so, check your "MasqueradeAs" settings. Omar On Tue, Feb 15, 2000 at 02:28:42PM +0100, Stephen Johnston wrote: > Our From line is majordomo@. it should be simply > @ ? I have checked the whoami and whereami in the > majordomo.cf and it appears to be ok. Any ideas? From majordomo-users-owner Wed Feb 16 16:46:15 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28612; Wed, 16 Feb 2000 10:14:11 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id KAA28594 for majordomo-users@greatcircle.com; Wed, 16 Feb 2000 10:14:04 -0800 (PST) Received: from barr.dsl.visi.com (barr.dsl.visi.com [209.98.142.216]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA01706 for ; Mon, 14 Feb 2000 22:48:23 -0800 (PST) Received: (from barr@localhost) by barr.dsl.visi.com (8.9.3/8.9.3) id BAA07581 for majordomo-users@greatcircle.com; Tue, 15 Feb 2000 01:05:00 -0600 Date: Tue, 15 Feb 2000 01:05:00 -0600 Message-Id: <200002150705.BAA07581@barr.dsl.visi.com> From: barr@visi.com (Dave Barr) To: majordomo-users@greatcircle.com Reply-To: barr@visi.com Subject: Majordomo Frequently Asked Questions Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Version: $Id: majordomo-faq.html,v 1.240 2000/01/25 16:37:09 barr Exp barr $ URL: http://www.visi.com/~barr/majordomo-faq.html Archive-Name: mail/majordomo-faq Posting-Frequency: monthly Note: Be sure to read the updated Section 2.1 below which explains how to address local security issues in majordomo if you're not running majordomo on a host with restricted logins. 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? + 1.7 - How can I access Majordomo via the Web? + 1.8 - Is Majordomo Y2K (Year 2000) compliant? 2. Problems setting up Majordomo + 2.1 - What are the proper permissions and ownership of all Majordomo files and directories? + 2.2 - I get a MAJORDOMO ABORT with "chown(...): Not owner" or ".. Operation not permitted" + 2.3 - I get "sh: wrapper: cannot execute" or "wrapper: permission denied" + 2.4 - I get "Unknown mailer error" when majordomo runs + 2.5 - I get an error "insecure usage" from the wrapper + 2.6 - I get "majordomo: No such file or directory" from the wrapper + 2.7 - I get an error "Can't locate majordomo.pl" + 2.8 - I told my majordomo.cf where to archive the list, why isn't it working? + 2.9 - config-test can't seem to find ctime.pl or resend can't find getopts.pl + 2.10 - A list is visible via lists, but can't subscribe or 'get' files + 2.11 - I get "sh: wrapper not available for sendmail programs" + 2.12 - I get "aliasing/forwarding loop broken" 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? How do I approve messages? + 3.11 - How do I set up a digested version of a list? + 3.12 - How do I setup virtual majordomo domains? + 3.13 - How can I stop people from using my mailing list to spam my subscribers? 4. Mailer and list administration 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? + 4.7 - Why is the Subject of my messages missing? + 4.8 - I'm getting mail from majordomo with "BOUNCE:" what do I do? How do I stop this? + 4.9 - My list configuration doesn't seem to be working. + 4.10 - How do I set it up so that the originator of a message doesn't get a copy of his/her own message back? + 4.11 - With Smail or Exim, users subscribing to a list sometimes get mail sent before they subscribed + 4.12 - Majordomo doesn't seem to work with sendmail 8.9 + 4.13 - I can't get Majordomo to work with RedHat Linux This FAQ is Copyright 1996 by David Barr and The Ohio 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.visi.com/~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@visi.com (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 maintenance. Once a list is set up, virtually all operations can be performed remotely, requiring no intervention upon the postmaster of the list site. See the main Majordomo web page at: http://www.greatcircle.com/majordomo/ 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 is recommended that you use the latest release of Perl that you can get. You can find it at http://www.perl.com/perl/. You must upgrade to version 1.94.3 in order for it to work with Perl 5.004, due to changes in regular expressions. Unfortunately, Majordomo does NOT work with Perl 5.005_01, due to a bug in Perl with respect to regular expressions. Use Perl 5.005_02 (or greater). While Majordomo is still compatible with Perl 4.036, future versions will likely be Perl 5 only. RedHat 5.2 is unfortunately shipping a prerelease version of Perl ("5.004m4") with some of their Linux distributions. This version is buggy and won't work with Majordomo (you will get "Unknown mailer error 9" errors). Download an install the 5.004 or 5.005 RPM instead, or download and updated RPM from updates.redhat.com. Many people have been having problems with Majordomo on DEC OSF/1 AXP systems. 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 haven't been recent reports in this area, so it's assumed that later versions also 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 could be made to 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. There is no known port of Majordomo to Windows NT, Win95 or Mac. For more information, see the comp.os.msdos.mail-news FAQ. At last check there was a port of an old version (1.93) to MS-DOS/Waffle, and an old version (1.93) ported to OS/2. These probably aren't all that helpful for anyone porting Majordomo to NT. 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 See other references throughout this FAQ for some further notes on using these packages. 1.2 - Where do I get Majordomo? Via the Web at: http://www.greatcircle.com/majordomo/ Via anonymous FTP at: ftp://ftp.greatcircle.com/pub/majordomo/ ftp://ftp.sgi.com/other/majordomo/ ftp://ftp.sgi.com/other/majordomo/ The current version is 1.94.5, released Jan 18 2000. It is a collection of bugfixes and minor changes. Be sure to read the INSTALL file carefully so you don't leave yourself vulnerable to a security hole in the "wrapper" program. 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). Majordomo 2 is currently being developed by Jason Tibbits. Currently it's "alpha" quality. Join the majordomo-workers list (see below) if you want to use this release. You can find out how to get Majordomo 2, as well as information about this release at http://www.hpc.uh.edu/majordomo/ 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 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, or download it from the Majordomo distribution. If you have permission problems unpacking the distribution, try using the 'o' flag to tar to ignore user/group information. Although Majordomo is written in Perl, it does have one component written in C that must be compiled. This 'wrapper' program runs "setuid" and ensures that all Majordomo functions operate with the proper permissions. You will need root access to install this program with the correct privileges. Majordomo interfaces to the mail system (sendmail, exim, etc) through aliases. Adding aliases is generally a root-bound process. However, on some systems the process can be delegated to a separate file under your control. Once you get past the above two requirements, it is possible to maintain Majordomo lists without root access. At best, your local sysadmin would only be bothered twice -- once for the installation, and once for designating a separate alias file for your use. Majordomo 1.x is designed to work with sendmail, however will work with other UNIX-based mailers. For more information on setting up Majordomo with other mailers, see the following pages: * qmail - ftp://ftp.eyrie.org/pub/software/majordomo/mjqmail * exim - http://www.netmaster.ca/exim/majordomo.html * Netscape Messaging Server 2.x and 3.x - http://interstroom.nl/docs/nsmajordomo * Cyrus IMAP - see "Sendmail can't mail to a file or pipe..." at http://andrew2.andrew.cmu.edu/cyrus/imapd/install-FAQ.html#sendmai l. This is necessary because Majordomo works by delivering mail via pipe. 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 when upgrading to 1.94 that you update your $mailer and $bounce_mailer variables in your majordomo.cf! There are 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? Please DO NOT ask the FAQ maintainer for help on Majordomo. I will accidentally delete your message. I'm sorry, I don't have time to do consulting on Majordomo. I am not a Majordomo help service. I, along with many others, do answer questions on the mailing lists. Let me say that about 90% of the answers I get are from the documentation or this FAQ. Many of the rest are answered by reading the source. It's really not that hard to figure out. The remainder of the questions I get are usually sendmail questions, which really should be asked in comp.mail.sendmail. 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. It's a good idea to search or browse the list archives below for the last couple months since many of the same questions are asked (and answered) regularly. There are searchable list archives (thanks to Jason Tibbitts) at http://www.hpc.uh.edu/majordomo-users/ and http://www.hpc.uh.edu/majordomo-workers/. 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, qmail, 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 the 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 it is probably not the most recent version. There is an FTP site for unofficial patches. See http://sol.ccsf.cc.ca.us/ftp/majordomo-patches/ . What's in it? Messages that are saved from the majordomo-users and -workers mailing lists. There are INDEX files in each part with one-line summaries of each patch, and a README file in the top directory with overall information. If you have patches that you think should be in the archive, you can FTP or email them in. The top-level README file tells how to do it. Please contribute -- to save other people the headaches you had. NOTE: The patches are NOT "official" patches approved by Chan Wilson or anyone else. Use your own judgment before (and after) you apply them. Nick Perry also has various patches for 1.94.3 at ftp://ftp.amulation.co.uk/pub/majordomo_patches/. They are patches which add various functions to majordomo. 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://docuspace.uchicago.edu/dpc/general/g_maj-adm.html. Look for a great book out now from O'Reilly and Associates called "Managing Mailing Lists", by Alan Schwartz. You can read my review of the book at http://www.visi.com/~barr/managing-maillist-review.html. I was one of the book's technical reviewers. You can order the book at a discount (currently 20%) from amazon.com via the web: * http://www.amazon.com/exec/obidos/ASIN/156592259X/greatcircleassoc Besides getting you the book at a discounted price, using this link earns Great Circle Associates a small commission, which helps pay for their support of the majordomo and list-managers mailing lists, as well as distributing majordomo on their FTP site. 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. http://www.faqs.org/faqs/mail/list-admin/software-faq. Contact naleks@library.ummed.edu (Norm Aleks) for more information. 1.7 - How can I access Majordomo via the Web? There are various Web interfaces to Majordomo available. Some are management interfaces for list maintenance, and some are interfaces for list archives (some do searching too). * LWGate - http://www.netspace.org/users/dwb/lwgate.html * Regan's - http://www.peak.org/peak_info/mlists/Majordomo.html * MajorCool - http://ncrinfo.ncr.com/pub/contrib/unix/MajorCool/ Link dead.. it looks like it's supposed to be moved to http://www.ncr.com/pub/software/MajorCool/. * MailServ - http://www.csicop.org/~fitz/www/mailserv/ * Pandora - http://www.ed.umuc.edu/pandora/ * Maitre-d - http://www.landw.com/wps/content2.htm#ch12 * Marcos' - http://www.inf.utfsm.cl/~marcos/majordomo/www.html * ListTool - http://www.listtool.com/ * Wilma (a list archive interface) - ftp://sol.ccsf.cc.ca.us/majordomo-contrib/ * ListQuest ( a list archive and search interface) - http://lq.corenetworks.com/ 1.8 - Is Majordomo Y2K (Year 2000) compliant? The current release of Majordomo has no known year 2000 issues. Older versions had problems only if you used the "archive" program to maintain list archives, since it used only a 2-digit year. If you use the new 4-digit year flags to archive you should not have any year 2000 problems. No one has officially certified Majordomo to be Y2K compliant, and I don't foresee anyone paying money to do so, so don't go looking for someone to sue if it breaks. All we are saying is that we know of no year 2000 issues with Majordomo. That being said, as you can see by reading the Majordomo source, except for the "archive" program majordomo doesn't directly deal with dates so it's extremely unlikely there are any year 2000 issues. Even places where it does use dates (archive) it doesn't do any date comparisons, which is the crux of all non-cosmetic year 2000 bugs. At worst "archive" would overwrite your 100-year-old mailing list archives. I really really doubt Majordomo will still be used for 100 years. _________________________________________________________________ Section 2: Problems setting up Majordomo 2.1 - What are the proper permissions and ownership of all Majordomo files and directories? If you are running Majordomo on a host which allows logins by untrusted users, see the paragraph Wrapper security!" below. 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 it 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.3 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 (See the paragraph in Section 2.1 called Wrapper security!). 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' to 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. (otherwise sendmail 8.x will probably give "X-Authentication-Warning:"'s) Because Majordomo does not run with any "special" (root) privileges, 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 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 non-POSIX: SunOS 4.x, Ultrix, most BSD 4.2 and 4.3-based systems. POSIX systems include: Solaris 2.x, IRIX 5.x, BSDI (and 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. Wrapper security! If you are running Majordomo on a host which allows untrusted logins, you will need to restrict who can run the "wrapper" program. By default (as explained above) the wrapper can be run by "anyone" (that is, it has other execute permission). Because the wrapper program runs programs as majordomo, and because majordomo programs (such as "resend") allow loading of arbitrary configuration files (which are simply perl scripts), it's trivially possible to run arbitrary commands as the majordomo user. Again, this is an issue only to local users on the system -- if you don't have untrusted local users (i.e. only administrators can log into your mail server), then this is not an issue to worry about. To close down this hole, change the permissions of the Majordomo home directory to mode 750. (this is what is recommended in the INSTALL file) This will prevent the access by local users to the setuid wrapper script (which lives inside this directory). To make this work, you must make sure the group ownership of the home directory is the same as the gid your mailer runs as (for sendmail, this is "daemon"). Otherwise, sendmail will be unable to read your list subscription files (the files that you :include: in your alias file). Closing down the majordomo home directory has the added benefit that local users will be unable to read your list subscription files, bypassing any privacy restrictions you may have set in majordomo. The downside of closing the majordomo home directory is that it makes it harder to do local administration, and also to properly run "./wrapper config-test" to check your configuration (since you need to run it as a non-root, non-majordom user, and such a user won't have access to the home directory). 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 if you don't use "daemon" as your majordomo group -- see 2.3below.). 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" writable (770 or 775). 2.2 - I get a MAJORDOMO ABORT with "chown(...): Not owner" or ".. Operation not permitted" Most likely your wrapper is not installed correctly. Re-check the Makefile and see if the wrapper was compiled with the right UID and GID. See the README and the above section on how to set the permissions correctly. Make sure after you fix the wrapper that you remove (or rename) any "listname.new" or "L.listname" files found in your lists directory. These will likely have the wrong ownerships, and will cause you problems. You should have seen an error if you ran "./wrapper config-test" as a non-root, non-majordom user. If not, it's a bug in config-test and should be fixed. 2.3 - I get "sh: wrapper: cannot execute" or "wrapper: permission denied" Your mailer doesn't have permission to execute the wrapper. Usually this is the result of too-strict permissions on either the Majordomo home directory or the wrapper executable. See Section 2.1 and especially the paragraph on wrapper security for the correct permissions on all majordomo directories and programs. 2.4 - I get "Unknown mailer error" when majordomo runs First, see Question 4.13 if you are running RedHat 5.2 and are getting "Unknown mailer error 9". 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 usually see some sort of error message. If you just get a return code, check the Majordomo README for further explanation on sendmail return codes. If you get "Unknown mailer error XX" where XX is less than 255, look for the error in /usr/include/errno.h . Otherwise, see the README. See section 1.1 above for what versions of Perl won't work with Majordomo. [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.5 - 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: majordomo: |"/path/to/majordomo/wrapper majordomo" 2.6 - 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.7 - 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.8 - 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 retrieved 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.9 - config-test can't seem to find ctime.pl or resend can't find getopts.pl ctime.pl and getopts.pl are 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.10 - 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.11 - I get "sh: wrapper not available for sendmail programs" You're on a system which uses smrsh. (sendmail restricted shell). You have to configure smrsh to allow it to execute the wrapper. Normally this is done by creating a symlink in /var/adm/sm.bin (in some it's /etc/smrsh) to Majordomo's wrapper program. 2.12 - I get "aliasing/forwarding loop broken" [ Reported by Wade Williams ] Some people have noted sendmail will generate a bounce message if you send to a list, but the list file is empty (there are no subscribers). Add a subscriber to the list and the error should go away. You will also get this error if the permissions on the list file for that list in the lists directory are too strict. If the list directory or list file is not readable by sendmail, you will also get the error "Cannot open /path/to/lists/listname: Permission denied". See Section 2.1 above for the full discussion of how to correctly set permissions on directories and files within Majordomo. _________________________________________________________________ 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" variable in the list 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. (This address is what gets copied into 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 in the bounce process. 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 most of majordomo's other features like moderating, administrivia checks, and others. 3.2 - Semi-automated handling of bounced mail This is not true automation of bounced mail. What this does is the next best thing. You unsubscribe the user from the list, but add the user to a special 'bounces' list (there's a perl script in the distribution called bounce you run to make this easier) 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). There's no facility for automatically detecting what addresses are failing. You have to determine that based on the bounce messages you receive from other sites. [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. The most important reason why Reply-To: to the list is bad is that it can cause mail loops if any of the members of your list are running fairly-common but broken software which doesn't know what an envelope address is. (Many Microsoft products, as well as many other PC-based non-SMTP/Internet mail systems which work through an SMTP gateway.) You should read the following FAQ on why you shouldn't set the Reply-To: field. http://www.unicom.com/pw/reply-to-harmful.html If you are using resend, use the 'reply_to' configuration variable in the list .config file. 3.5 - How can I hide lists so they can't be viewed by 'lists'? That is what advertise and noadvertise are for. These two variables 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 variable in the config file. Just set it to the filename that holds the list of subscribers, which is just simply the name of the list. ("restrict-post = listname"). However, there is an issue to keep in mind. 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. (That means don't use something easy to guess like "-outgoing" or "-list"). Next, you need to make it such that people can't find out what your -outgoing alias is. You can use the "@filename" directive of resend. Put the all the normal command-line options of resend into a file readable only by the majordomo user/group. Then the alias for the list simply becomes ".../resend @/path/to/filename". 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. This doesn't prevent a user reading the local /etc/aliases file (if they can), however. Another approach is to simply disable EXPN or VRFY altogether. See the documentation for your mailer on how to do this. In sendmail this is done by adding "noexpn" to the "O PrivacyOptions=" line in your sendmail.cf (multiple options are separated with a comma). However this doesn't prevent a local user reading the aliases file. This isn't generally a problem if your mail server is restricted to staff only users. Unfortunately, Sendmail 8.x will log your -outgoing alias in the "Received:" lines. To prevent 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-seekrit,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 comma). Otherwise sendmail will set the envelope address of outgoing mail to contain your secret outgoing alias. Again if you're using the @filename directive, the entire command line is simply put into the specified file (starting with "-h foo.org ...". Here's another creative idea from matt@primefactor.com (Matt Perry): I've had a report that this no longer works with sendmail 8.9.1, but that it does work with 8.9.3. Sendmail allows you to rewrite incoming and outgoing addresses. The one that handles incoming is virtualusertable.text. For a list called test with the test-outgoing alias, I put the following into my virtualusertable.text file and remade the db with the appropriate command: test-outgoing@mydomain.com error:nouser User unknown Sendmail can still get to the alias and expand it into the list of recipients. However, any mail that appears at port 25 marked for test-outgoing@mydomain.com will bounce back with "User unknown". Finally it should be noted that it is impossible with any of these methods above to prevent people from forging mail as someone who is subscribed to the list, and sending to the list that way. Of course a spammer can also subscribe to the list legitimately and then send spam. The restrict_post option blocks the vast majority of problems, however. 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. This is also a "backup password" in case the .config file gets corrupted. 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? How do I approve messages? First, you need to tell Majordomo that the list is moderated. In the configuration file for the list, you set "moderate = 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, automates this for you. Whenever you get a message which needs approval, from your mail reader pipe the message through "approve". The password for each list needs to be put in your .majordomo file. Read the "approve" script for more information. 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, and then the entire contents of the original message. (meaning there should not be a blank line before and after the "Approved:" line.). Don't forget to edit out the headers which were added by the bounce process. For example: To: your-list@example.com Subject: doesn't matter Approved: your-approval-password Received: by some.site.org.... Received: by another.site.org.... From: joe@another.com (Joe User) Subject: this list is great! To: your-list@example.com Hey, this list is great, and the moderator sure is sexy! Joe It's also possible, if your mailer allows it, to approve a message another way by just inserting an Approved: header in the original body and passing the original message on without adding your own header. This is in a sense "forging" mail, so many mailers either won't allow it or will insert some sort of authentication warning. This form is used most often by moderators when they send mail to the list and don't want to go and approve their own message again. Here's an example: To: your-list@example.com Approved: your-approval-password Subject: Thanks! I like this list too, but sorry, I'm married! :-) -- your moderator Note that this requires a mail-user-agent (MUA) that allows one to add headers to a message. If your MUA doesn't let you do this, you'll need to use the first method. Note that in either case the "Approved:" line will be stripped out by Majordomo before it gets sent to the list, so the list members won't see your list password. 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, Anthony Baratta, 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. Create separate list directories for each virtual domain. http://www.sendmail.org/virtual-hosting.html first. See also the Sendmail FAQ there. Virtual domain stuff (in your virtusertable): #Domain 1 majordomo@domain1.com majordomo-1 majordomo-owner@domain1.com user ListOne@domain1.com ListOne ListOne-owner@domain1.com user owner-ListOne@domain1.com user ListOne-request@domain1.com ListOne-request @domain1.com user #Domain 2 majordomo@domain2.com majordomo-2 majordomo-owner@domain2.com user ListTwo@domain2.com ListTwo ListTwo-owner@domain2.com user owner-ListTwo@domain2.com user ListOne-request@domain2.com ListTwo-request @domain2.com user Don't forget to run 'makemap hash /etc/virtusertable < /etc/virtusertable'. Substitute "hash" for whatever database you wish to use (some vendor sendmail's don't support hash, but do support dbm). It's suggested to have separate alias files for each virtual domain. You can configure sendmail to have multiple alias files. Here's how the aliases will look: #MajorDomo Aliases ## System Info majordomo-1: "|/usr/local/majordomo/wrapper majordomo -C /usr/local/majordomo/ majordomo-1.cf" majordomo-2: "|/usr/local/majordomo/wrapper majordomo -C /usr/local/majordomo/ majordomo-2.cf" #Domain 1 ListOne: "|/usr/local/majordomo/wrapper resend -l ListOne -C /usr/local/major domo/majordomo-domain1.cf ListOne-OutGoing" ListOne-OutGoing: :include:/usr/local/majordomo/lists-domain1/listone ListOne-request: "|/usr/local/majordomo/wrapper majordomo -l ListOne -C /usr/lo cal/majordomo/majordomo-domain1.cf" #Domain 2 ListTwo: "|/usr/local/majordomo/wrapper resend -l Listtwo -C /usr/local/major domo/majordomo-domain2.cf ListTwo-OutGoing" ListTwo-OutGoing: :include:/usr/local/majordomo/lists-domain1/listtwo ListTwo-request: "|/usr/local/majordomo/wrapper majordomo -l ListTwo -C /usr/lo cal/majordomo/majordomo-domain2.cf" 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 virtual aliases. Check out http://o2.towery.com/~ernestm/admin/majordomo/majorvirt.html also for good instructions on configuring virtual domains with Majordomo. 3.13 - How can I stop people from using my mailing list to spam my subscribers? [From mcr@solidum.com (Michael Richardson) ] There are two approaches to solving spam. They are complementary. The most general solution is to make sure that your list host will not accept spam. See http://spam.abuse.net/ for extensive recipes on this. The majordomo specific way is to use the "restrict_post" mechanism to disallow posts from addresses that are not on the list. Please see section 3.6 for some of the pitfalls of using restrict_post. They all apply. My experience is that spammers have not yet learnt about the "-outgoing" alias, and the techniques in section 3.6 would apply when they do. The major objection to using restrict_post to deflect spam is that it may deflect posts from legitimate people -- people who've subscribed with one address but are posting from another address. It may also restrict cross-posts from other lists, or from people who read the list via news. The solution to the above objections is twofold: 1. the moderator must forward legitimate posts. This can be a pain, but it does work. 2. the restrict_post header can be extended. The typical way to do #2 is to set restrict_post to: mylist:mylist-nomail Then, create a configuration file and password for "mylist-nomail", but DO NOT create any aliases. (If you use something like mj_build_aliases, then don't set the owner) The moderator, or subscribers may then subscribe themselves to this second list. Subscribers to the -nomail list will then be allowed to post to the first list, but won't receive duplicate copies of the first list. _________________________________________________________________ Section 4: Mailer and list administration problems 4.1 - Address with blanks are being treated separately If a subscriber to the list is John Doe < jdoe@node.com> it gets treated these as the three addresses: John Doe < jdoe@node.com> [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 often 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 ftp://ftp.isc.org/isc/inn/contrib/. Installation instructions are straightforward, it provides sample entries 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 towards 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 has met with varying success. Exim can also be used (see http://www.exim.org/). qmail has been used with majordomo, and performance with either Exim or qmail I'm told generally will well exceed that of sendmail. At least qmail also is written in a far more secure way than sendmail (some would say paranoid). See http://www.qmail.org. The qmail site includes at least one way to get majordomo to work with qmail. Note that it is possible to get majordomo working under qmail without using the 'wrapper', which is a nice idea. Some majordomo-under-qmail solutions just involve qmail's sendmail emulation feature. For more info, see the Using Majordomo with qmail FAQ, written by Russ Allbery. If you are using Exim instead of sendmail there are more things you can do. Instead of concealing the -outgoing addresses, it is possible to configure Exim so that those addresses are only usable by the local majordomo user. A description of how to do that can be found at http://www.netmaster.ca/exim/majordomo.html as well as other information about configuring majordomo with Exim. 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 list configuration file if you don't upgrade to 1.3 or higher. TLB is another package which is like bulk_mailer, but has other features. You can get it from ftp://ftp.hpc.uh.edu/pub/tlb/. The advantage of TLB is its greater configuration flexibility, and also the fact that it's possible with TLB to eliminate the -outgoing address, making configuration easier and lists more secure. 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 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) { This is fixed in Majordomo 1.94.1 and higher. 4.7 - Why is the Subject of my messages missing? [from Dave Wolfe] But it's not. Oh, you probably mean "Why is the subject line of messages to my moderated list blank?" Because you didn't include any headers after the Approved: header in the body of the messages. Or you deleted them when you approved the bounced messages. When resend finds an Approved: header in the first line of the body, it throws away all the headers it's collected for the message and looks for more headers following the Approved: header (which is the format of a bounced message). So if you put the Approved: header in an original message (as opposed to a bounced message), you have to also fill in some headers to be sent out, such as Subject:, To:, and From:. See section Question 3.10 on how to approve messages to moderated lists. This is also explained in Doc/list-owner-info, which should be sent to all list owners and moderators. 4.8 - I'm getting mail from majordomo with "BOUNCE:" what do I do? How do I stop this? Whenever majordomo encounters mail to the list which it sees a problem with, it forwards it to person at the approval address to deal with manually. There are lots of reasons Majordomo does this. Majordomo will tell you why in the Subject of the message. Here's a list of the most common bounce reasons: An "Admin request" bounce means that the list is configured to filter out what it thinks are "administrivia" messages, and it thought that message was one. These are messages such as "subscribe" or "unsubscribe" or "help", which get sent to the list instead of majordomo. Lists generally have this turned on by default. If you don't like it, set "administrivia=no" in the list config file. If that doesn't work, check your aliases to make sure the "-s" option to resend isn't being used on that list. An "Approval required" bounce means that the list is moderated, and the message needs to be approved. (see section 3.10 of this FAQ) A "Message too long" bounce means that the message was longer than the "maxlength" setting in the list config file. If you get any of these bounces messages and you think the mail is OK to send to the list, you'll need to approve it. See the file Doc/list-owner-info on the correct procedure(s) for approving mail with Majordomo. It's also covered in section 3.10 of this FAQ. 4.9 - My list configuration doesn't seem to be working. If you changed your list configuration and the list doesn't seem to be behaving any differently, make sure that the list is being sent through "resend". See the installation documentation and section 3.1 of this FAQ on how to set up the aliases for the list correctly to pipe mail through "resend". Other things to check would be that the arguments to "resend" are only "-h", and "-l" (and perhaps "-C" if you use virtual domains). resend used to be configured with other command line flags to do things such as have moderated lists. However these flags override any config file settings, so remove them if they are present. All configuration should be done now through the config file. 4.10 - How do I set it up so that the originator of a message doesn't get a copy of his/her own message back? You can't. Sorry. The "metoo" setting in sendmail has no effect after a message is piped through an external program. Unless you're willing to give up piping messages through "resend", there's no way to stop this. 4.11 - With Smail or Exim, users subscribing to a list sometimes get mail sent before they subscribed [from Lazlo Nibble and Philip Hazel] This is due to the way Smail and Exim deliver mail. With sendmail, it expands its delivery list when the mail first arrives. If the list gets changed, the message will still get delivered to the original recipient list, since the original list is never referred to again. As sendmail delivers mail, it removes addresses from its expanded list as they get delivered. However Smail and Exim don't expand the list when the message is first queued. Instead as they go through the queue of pending messages to deliver, and maintain state on what addresses they have successfully delivered mail to and compare that with the current list contents. As long as the message is queued waiting for one or more addresses in the list, it will get sent to any new recipients whenever the queue gets processed next. This is rather unexpected for those used to sendmail's behavior. The advantage of smail and exim's approach is that if an address in your list is unreachable (or has a bad .forward file), you can change the list contents (or the .forward file) and the message will be delivered to the new address when the queue next gets processed. It won't deliver to the old, bad address. There really isn't an easy solution to this, but it's really not a serious problem. 4.12 - Majordomo doesn't seem to work with sendmail 8.9 The new security features of sendmail don't allow :include: directories to be group writable. Unfortunately, by default these directories are group writable with Majordomo. If you have this problem you will see errors from sendmail like "Cannot open /path/name: Group writable directory" and "aliasing/forwarding loop broken". One solution is to add: O DontBlameSendmail=groupwritabledirpathsafe in your sendmail.cf and restart sendmail. The other method (and generally the recommended one) is to remove the group-write bit on the lists directory and any list files. Make sure also any parent directories to not have the group or other write bit set. If Majordomo is working correctly having group write permission is not necessary. However, some people find it convenient to have group-write access so users can be put in the majordomo group and not need root access all the time to work on majordomo. 4.13 - I can't get Majordomo to work with RedHat Linux If you are trying to use the Majordomo RPM, it is broken. The majordomo.cf which comes with the RPM has the line $whereami = `hostname`; This is broken for two reasons. First, the hostname may not necessarily be a fully-qualified domain name, and thus this won't generate a valid Internet email address. Secondly, using `hostname` generates a linefeed character at the end, which totally screws things up, and you end up getting blank lines in headers (and you'll start to see headers appear in the body of the message). The solution is to edit the line and put in your correct host name or mail domain. A bug report has been filed with RedHat. RedHat 5.2 also ships with an interim (buggy) release of Perl, which does not work with Majordomo. (you will get "Unknown mailer error 9" errors). Download and install the updated Perl RPM from ftp://updates.redhat.com/. From majordomo-users-owner Wed Feb 16 17:11:55 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA02128; Wed, 16 Feb 2000 14:46:13 -0800 (PST) Received: from www.texas-atheist.org (www.texas-atheist.org [206.222.216.115]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA02120 for ; Wed, 16 Feb 2000 14:45:54 -0800 (PST) From: mthompson@texas-atheist.org Received: from hohos (lin-dsl1-static-212-107.inetnebr.com [206.222.212.107]) by www.texas-atheist.org (8.9.3/8.9.3) with SMTP id RAA31109 for ; Wed, 16 Feb 2000 17:09:34 -0600 Message-ID: <000901bf78d2$d9d4a400$1d02a8c0@datadf.com> To: Subject: Automate Bouncing Process?? Date: Wed, 16 Feb 2000 17:09:17 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm fairly new to Majordomo and have been watching the mailing list for the past week. Please forgive me if you've answered this question 100 times before. Is there any way (add-on Perl script) that I can automate the process of adding bounced messages to my bounces list? I dislike having to 'manually' manage those that bounce. I have the O'Reilly 'Managing Mailing Lists' book and have turned it inside-out without any luck. Answers, pointers, questions are appreciated, Marc Thompson Data Definitions, Inc. Lincoln, NE From majordomo-users-owner Wed Feb 16 18:56:40 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA04631; Wed, 16 Feb 2000 18:49:12 -0800 (PST) Received: from owbn.org (mail.owbn.org [206.156.227.57]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA04624 for ; Wed, 16 Feb 2000 18:49:05 -0800 (PST) Received: from [206.156.227.238] (helo=[206.156.227.238]) by owbn.org with esmtp (Exim 3.03 #1) id 12LHKJ-0003XV-00 for majordomo-users@GreatCircle.COM; Wed, 16 Feb 2000 21:10:00 -0600 Mime-Version: 1.0 X-Sender: rosander@mail.owbn.org Message-Id: Date: Wed, 16 Feb 2000 21:05:58 -0600 To: majordomo-users@GreatCircle.COM From: Fargo/Moorhead HST Subject: Majordomo and Exim Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I having a heck of a time getting majordomo to work properly. Here's the setup. redhat 6.1 Exim 3.0.3 Majordomo 1.9.4 This is the problem I'm having. Exim freezes all messages for any of the lists if the lists are UID and GID by Majordomo. I've had majordomo working in a hacked sort of way. By making the list owned by majordomo and group of mail, Exim will deliver messages. I've added mail (the group that exim runs as) to the group majordomo. This didn't allow exim to deliver the mail either. This wouldn't be a problem except when majordomo itself processes an un-subscribe it fails because it is being denied the chown to the files because the group is mail. I get an Abort message operation not permitted. The lock file *.new gets all messed up. Anyone have any ideas? Ross Anderson Fargo Moorhead HST/Council vote. rosander@owbn.org Tremere Justicar Coordinator tremere-justicar@owbn.org AOL IM:RossWolfie ICQ:20501774 http://phoenix.owbn.org Part of One World By Night http://www.owbn.org Network Contact and Administrator for OWBN.org From majordomo-users-owner Wed Feb 16 22:32:44 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA06416; Wed, 16 Feb 2000 22:09:23 -0800 (PST) Received: from universe.uohyd.ernet.in (universe.uohyd.ernet.in [202.41.85.90]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA06404 for ; Wed, 16 Feb 2000 22:07:09 -0800 (PST) Received: (from uucp@localhost) by universe.uohyd.ernet.in (8.9.0/8.9.0) id LAA04880 for majordomo-users@GreatCircle.COM; Thu, 17 Feb 2000 11:24:25 -0500 (GMT) >Received: (gvsm@localhost) by nfc.ernet.in (8.6.8.1/SCA-6.6) id FAA02635; Thu, 17 Feb 2000 05:53:15 GMT Date: Thu, 17 Feb 2000 11:23:15 +0530 (IST) From: GVSM Siva Kumar To: majordomo-users@GreatCircle.COM Subject: mailing list for sysadmins In-Reply-To: Message-ID: MIME-Version: 1.0 Received: from nfc by universe.uohyd.ernet.in; Thu, 17 Feb 2000 11:24 GMT Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk hi all, Iam sure this is not the right question for this group. But since most of you appear to be system administrator/postmaster, I felt you will be able to help me with this. I find this majordomo questions and answers to be very helpful. Is there a similar list for system administration tasks (any unix). If you know of any such list, kindly do let me know with the admin-address, subscription syntax. Thanks a lot in advance. sivakumar From majordomo-users-owner Thu Feb 17 02:56:19 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id CAA09910; Thu, 17 Feb 2000 02:41:45 -0800 (PST) Received: from hn.hn.planet.gen.nz (hn.hn.planet.gen.nz [203.98.43.200]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id CAA09903 for ; Thu, 17 Feb 2000 02:41:35 -0800 (PST) Received: from oscar (ts25.hn.planet.gen.nz [203.98.34.250]) by hn.hn.planet.gen.nz (8.9.3/8.9.3) with SMTP id AAA12106 for ; Fri, 18 Feb 2000 00:01:13 +1300 Message-ID: <007a01bf7935$d7032b80$39d1fea9@oscar> From: "Michael Joyce" To: Subject: New Lists Date: Thu, 17 Feb 2000 23:57:51 +1300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi I get the error message: sh: wrapper not available for sendmail programs I have added a symbolic link in the smrsh dir to the wrapper program. Here is the file listing of /usr/local/majordomo-1.94.5 (this is where it was installed) [root@hn majordomo-1.94.5]# ls -l total 260 lrwxrwxrwx 1 majordom daemon 7 Feb 8 16:29 Lists -> ./lists -rw-rw-r-- 1 majordom daemon 0 Feb 7 23:19 Log drwxr-x--- 2 majordom daemon 1024 Feb 7 23:33 Tools -rwxr-x--- 1 majordom daemon 5267 Feb 7 23:17 archive2.pl drwxr-x--- 2 majordom daemon 1024 Feb 7 23:15 bin -rwxr-x--- 1 majordom daemon 2795 Feb 7 23:16 bounce-remind -rwxr-x--- 1 majordom daemon 10671 Feb 7 23:17 config-test -rwxr-x--- 1 majordom daemon 51130 Feb 7 23:16 config_parse.pl -rwxr-x--- 1 majordom daemon 14201 Feb 7 23:17 digest drwxrwx--- 2 majordom daemon 1024 Feb 7 23:22 lists -rwxr-x--- 1 majordom daemon 62511 Feb 7 23:16 majordomo -rw-r----- 1 majordom daemon 10544 Feb 7 23:15 majordomo.cf -rwxr-x--- 1 majordom daemon 24381 Feb 7 23:16 majordomo.pl -rwxr-x--- 1 majordom daemon 137 Feb 7 23:16 majordomo_version.pl drwxr-x--- 4 majordom daemon 1024 Feb 7 23:15 man -rwxr-x--- 1 majordom daemon 3791 Feb 7 23:16 request-answer -rwxr-x--- 1 majordom daemon 29919 Feb 7 23:16 resend -rw-r----- 1 majordom daemon 10462 Feb 7 23:17 sample.cf -rwxr-x--- 1 majordom daemon 8060 Feb 7 23:16 shlock.pl -rwsr-xr-x 1 root daemon 14882 Feb 7 23:17 wrapper And here is the listing for the /etc/smrsh directory [root@hn majordomo-1.94.5]# ls -l /etc/smrsh/ total 0 lrwxrwxrwx 1 root root 40 Feb 10 21:22 wrapper -> ../../usr/loca l/majordomo-1.94.5/wrapper Here is the e-mail sent back The original message was received at Sun, 13 Feb 2000 22:35:05 +1300 from p058.ipa1-n8-16.iconz.net.nz [210.48.24.58] ----- The following addresses had permanent fatal errors ----- "|/etc/smrsh/wrapper majordomo" (expanded from: ) ----- Transcript of session follows ----- sh: wrapper not available for sendmail programs 554 "|/etc/smrsh/wrapper majordomo"... Service unavailable I have also tried this with the alias being "|/usr/local/majordomo-1.94.5/wrapper majordomo" this came up with the same error Any ideas. Regards, Michael Joyce ----- Original Message ----- From: "Rick Green" To: "Michael Joyce" Sent: Sunday, February 13, 2000 7:41 PM Subject: Re: New Lists > On Sat, 12 Feb 2000, Michael Joyce wrote: > > > Hey, all of what you said worked. However now I get the message > > > > sh: wrapper: cannot execute" or "wrapper: permission denied > > > > I have put a symbolic link in smrsh like they suggest and restarted sendmail > > > > Any ideas. > > I am running RedHat 6.1 > > > The smrsh error is more like 'wrapper not permitted by sendmail', so I > would guess this is a more elementary permission problem. What are the > ownership and permissions of wrapper? What uid:gid was compiled into > wrapper? Specifically, is the execute bit turned on? > > -- Rick Green > > From majordomo-users-owner Thu Feb 17 03:42:25 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id DAA12419; Thu, 17 Feb 2000 03:33:46 -0800 (PST) Received: from janus.hosting4u.net (janus.communitech.net [209.15.2.37]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id DAA12412 for ; Thu, 17 Feb 2000 03:33:39 -0800 (PST) Received: (qmail 2717 invoked from network); 17 Feb 2000 11:50:42 -0000 Received: from sagittarius.hosting4u.net (HELO femiweb.com) (209.15.2.33) by janus.hosting4u.net with SMTP; 17 Feb 2000 11:50:42 -0000 Received: from jtadore1 ([213.56.40.200]) by femiweb.com ; Thu, 17 Feb 2000 05:50:22 -0600 Reply-To: From: "Redacteur FemiWeb" To: "MajordomoUsers" Subject: badmailfrom Date: Thu, 17 Feb 2000 12:30:38 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Please, help if you can : One of my subscribers get that when she post on my list. When trying to deliver your message, the mail server at >phoebe.communitech.net encounteredproblems with the following address: >For , the destination >server said: sorry, your envelope sender is in my badmailfrom list (#5.7.1) >(from phoebe.communitech.net:209 How can this happens if I did not ban the adress? Thanks. Albert Ohayon, redacteur. http://www.femiweb.com http://www.epsyweb.com http://www.petitweb.com Etre humain ou ne pas être, serait ce la question ? From majordomo-users-owner Thu Feb 17 04:42:31 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id EAA12909; Thu, 17 Feb 2000 04:25:26 -0800 (PST) Received: from server.pyrenet.fr (server.pyrenet.fr [194.250.190.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA12900 for ; Thu, 17 Feb 2000 04:25:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by server.pyrenet.fr (8.9.3/8.9.3) with ESMTP id NAA23263 for ; Thu, 17 Feb 2000 13:42:16 +0100 (MET) Date: Thu, 17 Feb 2000 13:42:10 +0100 (MET) From: Olivier PRENANT Reply-To: ohp@pyrenet.fr To: majordomo-users@greatcircle.com Subject: Majordomo 2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi everyone, Does anyone know where to find Majordomo 2? I've been looking all over the place and could'nt find it! TIA -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp@pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery) From majordomo-users-owner Thu Feb 17 06:57:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA14073; Thu, 17 Feb 2000 06:39:20 -0800 (PST) Received: from mhub3.tc.umn.edu (mhub3.tc.umn.edu [128.101.131.43]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA14066 for ; Thu, 17 Feb 2000 06:39:14 -0800 (PST) Received: from garnet.tc.umn.edu by mhub3.tc.umn.edu with ESMTP; Thu, 17 Feb 2000 08:56:13 -0600 Received: from localhost by garnet.tc.umn.edu with ESMTP; Thu, 17 Feb 2000 08:56:12 -0600 Date: Thu, 17 Feb 2000 08:56:12 -0600 (CST) From: mjn To: Michael Joyce cc: majordomo-Users@GreatCircle.COM Subject: Re: New Lists In-Reply-To: <007a01bf7935$d7032b80$39d1fea9@oscar> Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > And here is the listing for the /etc/smrsh directory > > [root@hn majordomo-1.94.5]# ls -l /etc/smrsh/ > total 0 > lrwxrwxrwx 1 root root 40 Feb 10 21:22 wrapper -> > ../../usr/loca > l/majordomo-1.94.5/wrapper > > Here is the e-mail sent back > > The original message was received at Sun, 13 Feb 2000 22:35:05 +1300 > from p058.ipa1-n8-16.iconz.net.nz [210.48.24.58] > > ----- The following addresses had permanent fatal errors ----- > "|/etc/smrsh/wrapper majordomo" > (expanded from: ) > > ----- Transcript of session follows ----- > sh: wrapper not available for sendmail programs > 554 "|/etc/smrsh/wrapper majordomo"... Service unavailable > > I have also tried this with the alias being > "|/usr/local/majordomo-1.94.5/wrapper majordomo" > this came up with the same error > I don't know if it would actually cause a problem but the syntax of you symlink appears a little funky. It should be more like this: lrwxrwxrwx 1 root root 26 Nov 17 14:34 wrapper -> /usr/lib/majordomo/wrapper The way you have it right now ../../usr/lib/majordomo-1.94.5 which is not the same as /usr/lib/majordomo-1.94.5. the link that you have is like saying "move up two directories and then look for usr/". Which isn't going to be there because two directories up from /usr/lib/majordomo-1.94.5 is actually in usr/. It won't work. Delete the link and re-add it like this: ln -s /usr/lib/majordomo-1.94.5/wrapper wrapper That should work. Hope that helps. Um I might have the syntax backwards for ln but you get the idea.... robble robble. ____________________________ Mike Neuharth ADCS Technology Specialist http://www.umn.edu/adcs E-Mail : mjn@tc.umn.edu Page Mail : 6123065932@messaging.sprintpcs.com http://nifty.dsl.visi.com/ ____________________________ From majordomo-users-owner Thu Feb 17 07:12:31 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA14302; Thu, 17 Feb 2000 07:02:19 -0800 (PST) Received: from beta.uni-x.net (beta.uni-X.net [194.64.77.5]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA14295 for ; Thu, 17 Feb 2000 07:02:12 -0800 (PST) Received: from aeon (aeon.uni-X.de [194.122.192.53]) by beta.uni-x.net (8.9.3/8.9.3) with ESMTP id QAA27168 for ; Thu, 17 Feb 2000 16:19:16 +0100 X-Ncc-RegID: de.uni-x Message-ID: <200002171622520322.05895154@smtp.uni-X.net> X-Mailer: Calypso Version 3.00.00.13 (1) Date: Thu, 17 Feb 2000 16:22:52 +0100 Reply-To: joan@anexia.de From: "Joan Lee" To: majordomo-users@GreatCircle.COM Subject: Personalized emails? Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I'm wondering if it is possible to send out personalized mails to the list. I use my list to contribute a newsletter and would like to greet all= subscribers personally with their name. Has anyone done this with majordomo (1.94.4) before? Any hints will be appreciated! .joan. -- +----------------------+ | All is lost. | | All is lost. | | joan@anexia.de | +----------------------+ From majordomo-users-owner Thu Feb 17 07:44:02 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA14350; Thu, 17 Feb 2000 07:09:39 -0800 (PST) Received: from www.texas-atheist.org (www.texas-atheist.org [206.222.216.115]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA14343 for ; Thu, 17 Feb 2000 07:09:31 -0800 (PST) From: mthompson@texas-atheist.org Received: from hohos (lin-dsl1-static-212-107.inetnebr.com [206.222.212.107]) by www.texas-atheist.org (8.9.3/8.9.3) with SMTP id JAA09223 for ; Thu, 17 Feb 2000 09:33:36 -0600 Message-ID: <00e801bf795c$4fa24550$1d02a8c0@datadf.com> To: Subject: Automate Bounce Process?? Date: Thu, 17 Feb 2000 09:33:16 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm fairly new to Majordomo (1.94.?) and have been watching the mailing list for the past week. Please forgive me if you've answered this question 100 times before. Is there any way (add-on Perl script) that I can automate the process of adding bounced messages to my bounces list? I dislike having to 'manually' manage those that bounce. I have the O'Reilly 'Managing Mailing Lists' book and have turned it inside-out without any luck. Answers, pointers, questions are appreciated, Marc Thompson Data From majordomo-users-owner Thu Feb 17 07:57:46 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA14311; Thu, 17 Feb 2000 07:03:36 -0800 (PST) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA14304 for ; Thu, 17 Feb 2000 07:03:28 -0800 (PST) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id IAA07277; Thu, 17 Feb 2000 08:20:23 -0700 (MST) Received: from ip-43-124.tus.primenet.com(206.165.43.124), claiming to be "gateway.localnet" via SMTP by smtp01.primenet.com, id smtpdAAAsWa4eo; Thu Feb 17 08:20:13 2000 Received: from bob.localnet (bob.localnet [192.168.1.1]) by gateway.localnet (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id IAA04170; Thu, 17 Feb 2000 08:20:03 -0700 Received: by primenet.com via sendmail from stdin id (Debian Smail3.2.0.102) for majordomo-users@GreatCircle.COM; Thu, 17 Feb 2000 08:20:08 -0700 (MST) Date: Thu, 17 Feb 2000 08:20:08 -0700 From: Bob Nielsen To: Fargo/Moorhead HST Cc: majordomo-users@GreatCircle.COM Subject: Re: Majordomo and Exim Message-ID: <20000217082008.A5777@bob.localnet> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: ; from rosander@owbn.org on Wed, Feb 16, 2000 at 09:05:58PM -0600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk You probably need to configure exim to include majordomo as a "trusted user". See http://www.netmaster.ca/exim/majordomo.html for a discussion of of using majordomo with exim. On Wed, Feb 16, 2000 at 09:05:58PM -0600, Fargo/Moorhead HST wrote: > I having a heck of a time getting majordomo to work properly. > Here's the setup. > redhat 6.1 > Exim 3.0.3 > Majordomo 1.9.4 > > This is the problem I'm having. Exim freezes all messages for > any of the lists if the lists are UID and GID by Majordomo. I've had > majordomo working in a hacked sort of way. By making the list owned > by majordomo and group of mail, Exim will deliver messages. I've > added mail (the group that exim runs as) to the group majordomo. > This didn't allow exim to deliver the mail either. > This wouldn't be a problem except when majordomo itself > processes an un-subscribe it fails because it is being denied the > chown to the files because the group is mail. I get an Abort message > operation not permitted. The lock file *.new gets all messed up. > > Anyone have any ideas? > > Ross Anderson Fargo Moorhead HST/Council vote. rosander@owbn.org > Tremere Justicar Coordinator tremere-justicar@owbn.org > AOL IM:RossWolfie ICQ:20501774 > http://phoenix.owbn.org Part of One World By Night http://www.owbn.org > Network Contact and Administrator for OWBN.org > -- Bob Nielsen, N7XY (RN2) nielsen@primenet.com Tucson, AZ DM42nh QRP-L #1985 SOC #77 http://www.primenet.com/~nielsen From majordomo-users-owner Thu Feb 17 08:35:39 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA15184; Thu, 17 Feb 2000 08:21:54 -0800 (PST) Received: from raven.a001.sprintmail.com (raven.prod.itd.earthlink.net [209.178.63.9]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA15177 for ; Thu, 17 Feb 2000 08:21:48 -0800 (PST) Received: from earthlink (sdn-ar-005waseatP257.dialsprint.net [168.191.239.19]) by raven.a001.sprintmail.com (8.8.7/8.8.5) with SMTP id IAA18942; Thu, 17 Feb 2000 08:34:45 -0800 (PST) Message-ID: <012501bf7964$dd169b40$0100a8c0@earthlink> Reply-To: "Chris McEwen" From: "Chris McEwen" To: "GVSM Siva Kumar" , References: Subject: Re: mailing list for sysadmins Date: Thu, 17 Feb 2000 08:34:25 -0800 Organization: Socrates Press, Keyport WA MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Yep, yep, yep. There is such a list called "vsowners" at vlists.net. Use the usual majordomo sub process: mailto:majordomo@vlists.net in body of message say sub vsowners respond to confirmation message. The list owner is Paul Rice. Very nice person. Be sure to introduce yourself. BTW, the name stands for Virtual Server Owners. The target audience is those who rent a virtual server on other systems. Such service typically includes a virtual root access. -- Chris McEwen ----- Original Message ----- From: GVSM Siva Kumar I find this majordomo questions and answers to be very helpful. Is there a similar list for system administration tasks (any unix). If you know of any such list, kindly do let me know with the admin-address, subscription syntax. From majordomo-users-owner Thu Feb 17 08:43:55 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA15251; Thu, 17 Feb 2000 08:26:31 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA15244 for ; Thu, 17 Feb 2000 08:26:24 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id LAA27251; Thu, 17 Feb 2000 11:42:00 -0500 (EST) Date: Thu, 17 Feb 2000 11:41:59 -0500 (EST) From: "Bill Casti (System Admin)" To: Olivier PRENANT cc: "Majordomo Users' List" Subject: Re: Majordomo 2 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 couldn't have looked very hard. Read the FAQ, Section 1.2: "Majordomo 2 is currently being developed by Jason Tibbits. Currently it's "alpha" quality. Join the majordomo-workers list (see below) if you want to use this release. You can find out how to get Majordomo 2, as well as information about this release at http://www.hpc.uh.edu/majordomo/#mj2 " (Yes! A bad-attitude response worthy of Roger "Bad Attitude" Klorese.) On Thu, 17 Feb 2000, Olivier PRENANT wrote: > Hi everyone, > > Does anyone know where to find Majordomo 2? > > I've been looking all over the place and could'nt find it! > > TIA > > -- > Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) > Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) > 31190 AUTERIVE +33-6-07-63-80-64 (GSM) > FRANCE Email: ohp@pyrenet.fr > ------------------------------------------------------------------------------ > Make your life a dream, make your dream a reality. (St Exupery) > > From majordomo-users-owner Thu Feb 17 09:13:02 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA15556; Thu, 17 Feb 2000 09:00:15 -0800 (PST) Received: from lepton.etown.com (adsl-207-212-51-167.dsl.snfc21.pacbell.net [207.212.51.167]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA15532 for ; Thu, 17 Feb 2000 08:59:55 -0800 (PST) Received: from lepton.etown.com (lepton.etown.com [207.212.51.167]) by lepton.etown.com (8.9.2/8.9.2) with ESMTP id JAA20561; Thu, 17 Feb 2000 09:16:42 -0800 (PST) Date: Thu, 17 Feb 2000 09:16:42 -0800 (PST) From: ramon via lepton To: Redacteur FemiWeb cc: MajordomoUsers Subject: Re: badmailfrom In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk There is a badmailfrom control file in qmail: badmailfrom Unacceptable envelope sender addresses. qmail-smtpd will reject every recipient address for a message if the envelope sender address is listed in badmailfrom. A line in badmailfrom may be of the form @host, meaning every address at host. Looks like they may be rejecting your mail or mail from your domain. ramon. On Thu, 17 Feb 2000, Redacteur FemiWeb wrote: > Please, help if you can : > One of my subscribers get that when she post on my list. >=20 > When trying to deliver your message, the mail server at > >phoebe.communitech.net encounteredproblems with the following address: > >For , the destinati= on > >server said: sorry, your envelope sender is in my badmailfrom list (#5.7= =2E1) > >(from phoebe.communitech.net:209 >=20 > How can this happens if I did not ban the adress? >=20 > Thanks. > Albert Ohayon, redacteur. > http://www.femiweb.com > http://www.epsyweb.com > http://www.petitweb.com > Etre humain ou ne pas =EAtre, serait ce la question ? >=20 From majordomo-users-owner Thu Feb 17 10:14:10 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA16346; Thu, 17 Feb 2000 10:05:26 -0800 (PST) Received: from mail.cobaltnet.com (firewall.cobalt.com [63.77.128.251]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA16337 for ; Thu, 17 Feb 2000 10:05:16 -0800 (PST) Received: from cobalt.com (lease8.cobaltnet.com [10.9.23.8]) by mail.cobaltnet.com (8.9.2/8.9.2) with ESMTP id KAA03940 for ; Thu, 17 Feb 2000 10:22:22 -0800 (PST) Message-ID: <38AC3C99.37D97D4F@cobalt.com> Date: Thu, 17 Feb 2000 10:23:21 -0800 From: Jeff Lovell Reply-To: jlovell@cobalt.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo-Users@GreatCircle.COM Subject: Re: i need majordomo References: <001a01bf7729$958d67a0$0200a8c0@dantas> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Eduardo Dantas Correia wrote: > > im looking for majordomo download !!! > hellp me please !! You can manage to get subscribed to the list, but failed to notice the distributions listed above the mailing-list section on greatcircle's page? http://www.greatcircle.com/majordomo/1.94.5/majordomo-1.94.5.tar.gz Jeff From majordomo-users-owner Thu Feb 17 10:57:35 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA16713; Thu, 17 Feb 2000 10:41:13 -0800 (PST) Received: from mw2.texas.net (mw2.texas.net [206.127.30.12]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA16706 for ; Thu, 17 Feb 2000 10:41:03 -0800 (PST) Received: from b1h074.dsla1n1.houston.texas.net (b1h074.dsla1n1.houston.texas.net [209.99.91.74]) by mw2.texas.net (2.4/2.4) with SMTP id MAA23096 for ; Thu, 17 Feb 2000 12:58:08 -0600 (CST) From: Gary Peake To: majordomo-users@greatcircle.com Subject: approve script Date: Thu, 17 Feb 2000 13:01:47 -0600 Organization: http://www.owlnet.net Reply-To: gpeake@texas.net Message-ID: X-Mailer: Forte Agent 1.7/32.534 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 read and re-read the docs on approving posts but can not make it work. Can someone provide an example and explanation that is a little more clear or a script that I can run to automagically approve posts to a moderated list? Thanks -- Gary Peake http://www.owlnet.net Team AMIGA "Far better it is to dare mighty things, to win glorious triumphs, even though checkered by failure, than to rank with those poor spirits who neither suffer much nor enjoy much because they live in the gray twilight that knows neither victory nor defeat." -- From majordomo-users-owner Thu Feb 17 11:27:33 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA17136; Thu, 17 Feb 2000 11:18:14 -0800 (PST) Received: from mercury.libpubinc.com (mercury.libpubinc.com [208.249.203.55]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA17129 for ; Thu, 17 Feb 2000 11:18:07 -0800 (PST) Received: from dmoyer (dhcp93.libpubinc.com [208.249.203.93]) by mercury.libpubinc.com (8.9.3/8.9.3) with ESMTP id LAA07615; Thu, 17 Feb 2000 11:35:12 -0800 Message-Id: <4.2.2.20000217113428.00a66e60@mercury.libpubinc.com> X-Sender: dmoyer@mercury.libpubinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 17 Feb 2000 11:34:54 -0800 To: majordomo-Users@GreatCircle.COM From: Dave Moyer Subject: Re: New Lists Cc: michael.joyce@xtra.co.nz Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk You might also want to check your permissions. Try changing the permissions on the executable and the link to something other than root (mail or majordomo). At 08:56 AM 2/17/00 -0600, you wrote: > > And here is the listing for the /etc/smrsh directory > > > > [root@hn majordomo-1.94.5]# ls -l /etc/smrsh/ > > total 0 > > lrwxrwxrwx 1 root root 40 Feb 10 21:22 wrapper -> > > ../../usr/loca > > l/majordomo-1.94.5/wrapper > > > > Here is the e-mail sent back > > > > The original message was received at Sun, 13 Feb 2000 22:35:05 +1300 > > from p058.ipa1-n8-16.iconz.net.nz [210.48.24.58] > > > > ----- The following addresses had permanent fatal errors ----- > > "|/etc/smrsh/wrapper majordomo" > > (expanded from: ) > > > > ----- Transcript of session follows ----- > > sh: wrapper not available for sendmail programs > > 554 "|/etc/smrsh/wrapper majordomo"... Service unavailable > > > > I have also tried this with the alias being > > "|/usr/local/majordomo-1.94.5/wrapper majordomo" > > this came up with the same error > > > >I don't know if it would actually cause a problem but the syntax of you >symlink appears a little funky. It should be more like this: > >lrwxrwxrwx 1 root root 26 Nov 17 14:34 wrapper -> >/usr/lib/majordomo/wrapper > >The way you have it right now ../../usr/lib/majordomo-1.94.5 which is not >the same as /usr/lib/majordomo-1.94.5. the link that you have is like >saying "move up two directories and then look for usr/". Which isn't >going to be there because two directories up from >/usr/lib/majordomo-1.94.5 is actually in usr/. It won't work. Delete the >link and re-add it like this: > >ln -s /usr/lib/majordomo-1.94.5/wrapper wrapper > >That should work. > >Hope that helps. Um I might have the syntax backwards for ln but you get >the idea.... > >robble robble. > > >____________________________ >Mike Neuharth >ADCS Technology Specialist >http://www.umn.edu/adcs > >E-Mail : mjn@tc.umn.edu >Page Mail : 6123065932@messaging.sprintpcs.com >http://nifty.dsl.visi.com/ >____________________________ From majordomo-users-owner Thu Feb 17 13:57:53 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA19258; Thu, 17 Feb 2000 13:52:27 -0800 (PST) Received: from bard.net (bard.net [207.159.145.137]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA19251 for ; Thu, 17 Feb 2000 13:52:21 -0800 (PST) Received: from RINGWRAITH (MORDOR-PROXY@ip-141-249.gw.total-web.net [209.187.141.249]) by bard.net (8.9.3/8.9.3) with ESMTP id RAA28967 for ; Thu, 17 Feb 2000 17:09:27 -0500 (EST) Message-Id: <4.2.2.20000217170751.02a0a6d0@bard.net> X-Sender: webmaster@bard.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 17 Feb 2000 17:09:23 -0500 To: Majordomo-Users@GreatCircle.COM From: Michael Donohue Subject: MAJORDOMO ABORT (mj_digest)!! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm getting one of these about every 3 days. Any ideas? MAJORDOMO ABORT (mj_digest)!! mj_digest: can't get lock '/usr/local/majordomo/Lists/digestname-digest.config.LOCK' From majordomo-users-owner Thu Feb 17 14:57:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA19951; Thu, 17 Feb 2000 14:50:27 -0800 (PST) Received: from www.texas-atheist.org (www.texas-atheist.org [206.222.216.115]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA19942 for ; Thu, 17 Feb 2000 14:50:19 -0800 (PST) From: mthompson@texas-atheist.org Received: from hohos (lin-dsl1-static-212-107.inetnebr.com [206.222.212.107]) by www.texas-atheist.org (8.9.3/8.9.3) with SMTP id RAA09363 for ; Thu, 17 Feb 2000 17:14:29 -0600 Message-ID: <010201bf799c$afc7a8e0$1d02a8c0@datadf.com> To: References: Subject: Re: Automate Bounce Process?? Date: Thu, 17 Feb 2000 17:14:03 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Bill, Thanks for mentioning the FAQ. I'm still looking for an answer. My problem is that I need to have some way to make majordomo catch a real-time failure to send. For example, if during the dialog with the SMTP server majordomo receives a non-transient (fatal) error, I'd like for it to automatically place the recipient's name in the bounces list. This prevents me from having to manually subscribe addresses to the bounces list and unsubscribe them from the list their currently subscribed to. So what I am looking for is something that catches a bad e-mail during the ESMTP exchange and removes that e-mail from its subscribed list and puts it in the bounces list. I realize that this wouldn't catch them all, but it'd catch most. I didn't see an answer to this in a FAQ. Am I trying to get majordomo to do too much. Should I quit complaining about having to move names to the bounces list? Thanks, Marc Thompson Marc Thompson Data Definitions, Inc. Lincoln, NE ----- Original Message ----- From: Bill Casti (System Admin) To: Sent: Thursday, February 17, 2000 2:31 PM Subject: Re: Automate Bounce Process?? > > Have you read the Majordomo FAQ FIRST, before posting??? > http://www.visi.com/~barr/majordomo-faq.html > > > > On Thu, 17 Feb 2000 mthompson@texas-atheist.org wrote: > > > I'm fairly new to Majordomo (1.94.?) and have been watching the mailing list > > for the > > past week. Please forgive me if you've answered this question 100 times > > before. > > > > Is there any way (add-on Perl script) that I can automate the process of > > adding bounced messages to my bounces list? I dislike having to 'manually' > > manage those that bounce. I have the O'Reilly 'Managing Mailing Lists' book > > and have turned it inside-out without any luck. > > > > Answers, pointers, questions are appreciated, > > Marc Thompson > > Data > > > > > > > > > > > > > > > > > > > > > > From majordomo-users-owner Thu Feb 17 15:12:32 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA20187; Thu, 17 Feb 2000 15:06:42 -0800 (PST) Received: from mercury.libpubinc.com (mercury.libpubinc.com [208.249.203.55]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA20180 for ; Thu, 17 Feb 2000 15:06:36 -0800 (PST) Received: from dmoyer (dhcp93.libpubinc.com [208.249.203.93]) by mercury.libpubinc.com (8.9.3/8.9.3) with ESMTP id PAA11994 for ; Thu, 17 Feb 2000 15:23:43 -0800 Message-Id: <4.2.2.20000217152312.00a58110@mercury.libpubinc.com> X-Sender: dmoyer@mercury.libpubinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 17 Feb 2000 15:23:40 -0800 To: majordomo-Users@GreatCircle.COM From: Dave Moyer Subject: Re: approve script In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Doesn't that kind of defeat the purpose of moderating the list? At 01:01 PM 2/17/00 -0600, you wrote: >I have read and re-read the docs on approving posts but can not make it >work. Can someone provide an example and explanation that is a little more >clear or a script that I can run to automagically approve posts to a >moderated list? > >Thanks >-- >Gary Peake >http://www.owlnet.net >Team AMIGA > >"Far better it is to dare mighty things, to win glorious triumphs, >even though checkered by failure, than to rank with those poor spirits >who neither suffer much nor enjoy much because they live in the gray >twilight that knows neither victory nor defeat." >-- From majordomo-users-owner Thu Feb 17 18:26:57 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA21924; Thu, 17 Feb 2000 18:17:46 -0800 (PST) Received: from mail.checkout.com (mail.checkout.com [216.101.74.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA21917 for ; Thu, 17 Feb 2000 18:17:40 -0800 (PST) Received: from buster (buster.checkout.com [172.16.0.15] (may be forged)) by mail.checkout.com (8.9.3/8.9.3) with SMTP id SAA02667 for ; Thu, 17 Feb 2000 18:34:49 -0800 Message-ID: <088001bf79b8$cbcd3570$0f0010ac@buster> From: "John Castillo" To: Subject: enabling web enabled approve through majorcool and Approval Queue Date: Thu, 17 Feb 2000 18:35:18 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_087D_01BF7975.BD9DC070" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_087D_01BF7975.BD9DC070 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear users: After setting up a moderated list, i am now trying to configure = Majorcool to provide moderators with a web method of approving posts to = a moderated group. As of right now, I do not see an Approval Queue = option under Majorcool's Modify option. I've seen this option enabled with majordomo before on other websites. = How is this done? are there patches that need to be applied? what do i = change in majordomo (or majorcool for that matter) to enable the = Approval Queue? I'm an a RH6.1 box running majordomo 1.94.5, and majorcool 1.3.2. john castillo system administrator CheckOut.com 310-860-8775 ------=_NextPart_000_087D_01BF7975.BD9DC070 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Dear users:
 
After setting up a moderated list, i am = now trying=20 to configure Majorcool to provide moderators with a web method of = approving=20 posts to a moderated group.  As of right now, I do not see an = Approval=20 Queue option under Majorcool's Modify option.
 
I've seen this option enabled with = majordomo before=20 on other websites.  How is this done?  are there patches that = need to=20 be applied?  what do i change in majordomo (or majorcool for that = matter)=20 to enable the Approval Queue?
 
I'm an a RH6.1 box running majordomo = 1.94.5, and=20 majorcool 1.3.2.
 
john=20 castillo
system administrator
CheckOut.com
310-860-8775
------=_NextPart_000_087D_01BF7975.BD9DC070-- From majordomo-users-owner Thu Feb 17 19:27:11 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA22599; Thu, 17 Feb 2000 19:18:26 -0800 (PST) Received: from webfrogs.iserver.net (webfrogs.iserver.net [192.41.18.45]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA22592 for ; Thu, 17 Feb 2000 19:18:20 -0800 (PST) Received: from rtslap (gw7.dsl.iadfw.net [207.136.8.8]) by webfrogs.iserver.net (8.8.5) id UAA26053; Thu, 17 Feb 2000 20:35:37 -0700 (MST) X-Authentication-Warning: webfrogs.iserver.net: Host gw7.dsl.iadfw.net [207.136.8.8] claimed to be rtslap From: "Roger Sams" To: Subject: Please Help Date: Thu, 17 Feb 2000 21:32:29 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a new install of majordomo on a solaris box. majordomo: 1.94.4 , sendmail: 8.9.3 , solaris: 7 I followed the directions in the INSTALL file to the letter. Everything was looking great until I got to step 10. 10. Test the configuration by creating an empty file 'test' in $listdir, and issue a 'list' command to Majordomo. % touch /path/to/majordomo/lists/test % echo 'list' | mail majordomo If everything is working correctly, you should get a message back from Majordomo, and not from Mailer-Daemon. Well, I was able to send the command "echo 'list' | mail majordomo", but I got nothing back. Where should the message come to? I assume it would go to majordomo-owner. I also tried to create a new group and send the 'config .admin' command to majordomo. No results there either. it appeared to work, but I did not get any e-mail. By the way, I got no errors with ./wrapper config-test in step 9, and I can send mail thought the command line to majordomo-owner I am new to Majordomo an would appreciate any help. Thanks, -Roger From majordomo-users-owner Thu Feb 17 19:56:10 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA22802; Thu, 17 Feb 2000 19:48:57 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id TAA22795 for ; Thu, 17 Feb 2000 19:48:52 -0800 (PST) Received: (qmail 5875 invoked from network); 18 Feb 2000 04:06:01 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 18 Feb 2000 04:06:01 -0000 Date: Thu, 17 Feb 2000 21:03:19 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: Dave Moyer cc: majordomo-Users@GreatCircle.COM Subject: Re: approve script In-Reply-To: <4.2.2.20000217152312.00a58110@mercury.libpubinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Or are there criteria for approval that you wish to automate? Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com On Thu, 17 Feb 2000, Dave Moyer wrote: > Doesn't that kind of defeat the purpose of moderating the list? > > At 01:01 PM 2/17/00 -0600, you wrote: > >I have read and re-read the docs on approving posts but can not make it > >work. Can someone provide an example and explanation that is a little more > >clear or a script that I can run to automagically approve posts to a > >moderated list? > > > >Thanks > >-- > >Gary Peake > >http://www.owlnet.net > >Team AMIGA > > > >"Far better it is to dare mighty things, to win glorious triumphs, > >even though checkered by failure, than to rank with those poor spirits > >who neither suffer much nor enjoy much because they live in the gray > >twilight that knows neither victory nor defeat." > >-- > From majordomo-users-owner Fri Feb 18 00:55:59 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id AAA25320; Fri, 18 Feb 2000 00:52:30 -0800 (PST) Received: from chameleon.view.net.au (calypso.view.net.au [203.30.237.210]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id AAA25312 for ; Fri, 18 Feb 2000 00:52:22 -0800 (PST) Received: from localhost (mtw@localhost) by chameleon.view.net.au (8.9.3/8.9.3) with ESMTP id QAA20527; Fri, 18 Feb 2000 16:27:45 +1030 Date: Fri, 18 Feb 2000 16:27:45 +1030 (CST) From: Michael Talbot-Wilson To: Gary Peake cc: majordomo-users@GreatCircle.COM Subject: Re: approve script In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 17 Feb 2000, Gary Peake wrote: > I have read and re-read the docs on approving posts but can not make it > work. Can someone provide an example and explanation that is a little more > clear or a script that I can run to automagically approve posts to a > moderated list? I agree that the approve documentation is perplexing and seems to miss essential points, but this particular inquiry strikes me as strange indeed. Could you say a little more about what you are trying to achieve? Possibly you have a list addresses that you want to be able to post to the list without moderator approval. But rather than us answering imaginary questions, perhaps you can say. Obviously, if you just don't want list members in general to require approval you convert it to a non-moderated list. Regards, Michael Talbot-Wilson -- Hike esas du o tri bokali per qui ni facos kelka experimenti, e me montros a vi la maxim bona moyeno por facar ica exerimenti. Me ne timas montrar to a vi, pro ke me deziras ke vi facos experimenti, se vu nur facos oli kun sorgo ed atenco, e la asento di li cirkum vu.---MICHAEL FARADAY From majordomo-users-owner Fri Feb 18 05:42:21 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA00918; Fri, 18 Feb 2000 05:33:36 -0800 (PST) Received: from www.texas-atheist.org (www.texas-atheist.org [206.222.216.115]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA00904 for ; Fri, 18 Feb 2000 05:33:27 -0800 (PST) From: mthompson@texas-atheist.org Received: from hohos (lin-dsl1-static-212-107.inetnebr.com [206.222.212.107]) by www.texas-atheist.org (8.9.3/8.9.3) with SMTP id HAA09664 for ; Fri, 18 Feb 2000 07:57:49 -0600 Message-ID: <000b01bf7a18$14102770$1d02a8c0@datadf.com> To: References: Subject: Re: Automate Bounce Process?? Date: Fri, 18 Feb 2000 07:57:21 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Bill, I hadn't thought to handle it on the Sendmail side. I think that your recommendation is good. Problem for me is that I'd prefer not to tackle that task; I will, though, if I must. I wonder if anyone has tackled this problem before? Does anyone have the type of script that Bill is recommending? If so, would they be willing to pass it along to the group (read: me)? Thanks in advance, Marc Thompson ----- Original Message ----- From: Bill Casti (System Admin) To: Sent: Thursday, February 17, 2000 10:31 PM Subject: Re: Automate Bounce Process?? > > Why don't you set up a filter on your mailer to catch those messages and > shunt them to a file? then, periodically run a perl script against that > file to strip out everything except what is between the "< >" in the > particular field writing the results to a file, one line at a time. That > will remove the onus from Majordomo having to do something it was not > built to do and still giving you the bounces file you want. > > Bill > > > On Thu, 17 Feb 2000 mthompson@texas-atheist.org wrote: > > > Bill, > > > > Thanks for mentioning the FAQ. I'm still looking for an answer. > > > > My problem is that I need to have some way to make majordomo catch a > > real-time failure to send. For example, if during the dialog with the SMTP > > server majordomo receives a non-transient (fatal) error, I'd like for it to > > automatically place the recipient's name in the bounces list. > > > > This prevents me from having to manually subscribe addresses to the bounces > > list and unsubscribe them from the list their currently subscribed to. > > > > So what I am looking for is something that catches a bad e-mail during the > > ESMTP exchange and removes that e-mail from its subscribed list and puts it > > in the bounces list. I realize that this wouldn't catch them all, but it'd > > catch most. > > > > I didn't see an answer to this in a FAQ. > > > > Am I trying to get majordomo to do too much. Should I quit complaining > > about having to move names to the bounces list? > > > > Thanks, > > Marc Thompson > > > > Marc Thompson > > Data Definitions, Inc. > > Lincoln, NE > > > > > > > > ----- Original Message ----- > > From: Bill Casti (System Admin) > > To: > > Sent: Thursday, February 17, 2000 2:31 PM > > Subject: Re: Automate Bounce Process?? > > > > > > > > > > Have you read the Majordomo FAQ FIRST, before posting??? > > > http://www.visi.com/~barr/majordomo-faq.html > > > > > > > > > > > > On Thu, 17 Feb 2000 mthompson@texas-atheist.org wrote: > > > > > > > I'm fairly new to Majordomo (1.94.?) and have been watching the mailing > > list > > > > for the > > > > past week. Please forgive me if you've answered this question 100 times > > > > before. > > > > > > > > Is there any way (add-on Perl script) that I can automate the > > process of > > > > adding bounced messages to my bounces list? I dislike having to > > 'manually' > > > > manage those that bounce. I have the O'Reilly 'Managing Mailing Lists' > > book > > > > and have turned it inside-out without any luck. > > > > > > > > Answers, pointers, questions are appreciated, > > > > Marc Thompson > > > > Data > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From majordomo-users-owner Fri Feb 18 21:41:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA09598; Fri, 18 Feb 2000 21:33:31 -0800 (PST) Received: from mazama.FIAL.COM ([206.58.211.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA09588 for ; Fri, 18 Feb 2000 21:33:25 -0800 (PST) Received: from rf ([206.58.211.74]) by mazama.FIAL.COM (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-0U10L2S100) with SMTP id AAA94 for ; Fri, 18 Feb 2000 21:50:44 -0800 Message-Id: <3.0.32.20000218213820.00fb8010@mail.fial.com> X-Sender: ron@mail.fial.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 18 Feb 2000 21:38:20 -0800 To: majordomo-users@GreatCircle.COM From: ron@fial.com (Ron Fial) Subject: Lets get rid of X-Authentication-Warning Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am a long-time list manager, but a newbie for installing Majordomo. I have it up and running on Red Hat 6.0 with sendmail and the latest (downloaded) version of Perl. Have read all the FAQs, have test lists running, and finally got a digested list to work, and am learning Perl. (whew!). Can anyone tell me how to get rid of this line in the headers: X-Authentication-Warning: server.fial.com majordomo set sender to owner-99-l@fial.com using -f This appears in the header of each message sent out by majordomo. Already tried the -R option for resend. I have often seen a similar line in messages from other majordomo lists. Is this just sendmail being too cautious? Is there any way to loosen up sendmail, or perhaps tell majordomo not to specify the 'sender'. It would be nice to get rid of the 'Return-Path:' also -- really just wastes bandwidth. Below is a typical header the subscriber sees on the screen. Regards, Ron Fial (ron@fial.com) -------- Return-Path: X-Authentication-Warning: server.fial.com: majordomo set sender to owner-99-l@fial.com using -f X-Sender: ron@mail.fial.com Date: Fri, 18 Feb 2000 21:18:02 -0800 To: 99-l@fial.com From: ron@fial.com (Ron Fial) Subject: [99-l] Test message Sender: owner-99-l@fial.com Reply-To: 99-l@fial.com From majordomo-users-owner Sat Feb 19 06:45:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA17605; Sat, 19 Feb 2000 06:32:24 -0800 (PST) Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA17598 for ; Sat, 19 Feb 2000 06:32:18 -0800 (PST) Received: (from uucp@localhost) by uucphost.mcs.net (8.9.3/8.8.8) with UUCP id IAA41958; Sat, 19 Feb 2000 08:49:40 -0600 (CST) Received: from david (dustpuppy [10.168.100.1]) by midrange.dynip.com (8.9.3/8.8.7) with ESMTP id IAA14334; Sat, 19 Feb 2000 08:50:32 -0600 Message-Id: <4.2.2.20000219080330.00a36ba0@midrange> X-Sender: david@midrange X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 19 Feb 2000 08:05:32 -0600 To: ron@fial.com (Ron Fial), majordomo-users@GreatCircle.COM From: David Gibbs Subject: Re: Lets get rid of X-Authentication-Warning In-Reply-To: <3.0.32.20000218213820.00fb8010@mail.fial.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >Can anyone tell me how to get rid of this line in the headers: > X-Authentication-Warning: server.fial.com majordomo set sender to > owner-99-l@fial.com using -f Add majordomo to the sendmail's trusted user list. This can be done in linuxconf using the menus, or directly in the sendmail.cf by adding the following line... # Trust users Troot Tdaemon Tuucp Tmajordomo <----------------- david -- | Internet: david@midrange.com | WWW: http://www.midrange.com/david | | This message was written and delivered using 100% | post-consumer (recycled) data bits. From majordomo-users-owner Sat Feb 19 09:07:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA18687; Sat, 19 Feb 2000 08:41:29 -0800 (PST) Received: from guinness.digisle.net (guinness.digisle.net [167.216.152.33]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA18680 for ; Sat, 19 Feb 2000 08:41:23 -0800 (PST) Received: from visi.com (dhcp-dialup-226-0-37-sf.digisle.com [206.220.226.103]) by guinness.digisle.net (8.9.3/8.9.3/digisle) with ESMTP id QAA03875; Sat, 19 Feb 2000 16:58:44 GMT Message-ID: <38AECBC1.293D7098@visi.com> Date: Sat, 19 Feb 2000 10:58:41 -0600 From: David Barr X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Ron Fial CC: majordomo-users@GreatCircle.COM Subject: Re: Lets get rid of X-Authentication-Warning References: <3.0.32.20000218213820.00fb8010@mail.fial.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Search for X-Authentication-Warning in the Majordomo FAQ. --Dave Ron Fial wrote: > > I am a long-time list manager, but a newbie for installing Majordomo. I have it up and running on Red Hat 6.0 with sendmail and the latest (downloaded) version of Perl. Have read all the FAQs, have test lists running, and finally got a digested list to work, and am learning Perl. (whew!). > > Can anyone tell me how to get rid of this line in the headers: > X-Authentication-Warning: server.fial.com majordomo set sender to owner-99-l@fial.com using -f > > This appears in the header of each message sent out by majordomo. Already tried the -R option for resend. I have often seen a similar line in messages from other majordomo lists. > Is this just sendmail being too cautious? Is there any way to loosen up sendmail, or perhaps tell majordomo not to specify the 'sender'. > It would be nice to get rid of the 'Return-Path:' also -- really just wastes bandwidth. Below is a typical header the subscriber sees on the screen. > Regards, Ron Fial (ron@fial.com) > -------- > > Return-Path: > X-Authentication-Warning: server.fial.com: majordomo set sender to owner-99-l@fial.com using -f > X-Sender: ron@mail.fial.com > Date: Fri, 18 Feb 2000 21:18:02 -0800 > To: 99-l@fial.com > From: ron@fial.com (Ron Fial) > Subject: [99-l] Test message > Sender: owner-99-l@fial.com > Reply-To: 99-l@fial.com From majordomo-users-owner Sat Feb 19 10:06:07 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA19268; Sat, 19 Feb 2000 09:41:42 -0800 (PST) Received: from story.washere.com (w215.z208176094.bos-ma.dsl.cnc.net [208.176.94.215]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA19246 for ; Sat, 19 Feb 2000 09:41:32 -0800 (PST) Received: from ransom (w212.z208176094.bos-ma.dsl.cnc.net [208.176.94.212]) by story.washere.com (8.9.3/8.9.3) with SMTP id NAA20262 for ; Sat, 19 Feb 2000 13:01:21 -0500 (EST) Message-ID: <003c01bf7b02$e4b8ca90$d45eb0d0@ransom> From: "Ric Messier" To: Subject: Weird shlock problem Date: Sat, 19 Feb 2000 12:58:14 -0500 Organization: Chaotic @Best MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0039_01BF7AD8.FBB7E200" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0039_01BF7AD8.FBB7E200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm having some problems with the permissions required for majordomo. I = have an OpenBSD 2.6 system. I followed the readme, install and FAQ. I = ran into an odd loop, though. When sendmail 8.9.3 was configured = correctly (and securely), I got the following error: shlock: '/usr/local/majordomo-1.94.5/lists' is not writable by UID 1 GID = 31=20 UID 1 is root, obviously, GID 31 is guest. No idea why it was trying to = run as GID 31. I have my UID and GID set to 969. To work around the = problem and at least get things working, I opened all permissions to the = majordomo directory and shut off sendmails ability to care about it = (won't whine about group writable permissions anymore). Now, I'm getting = a mail loop (multiple messages resulting from one test message. The = first message says: open of temp file '/usr/local/majordomo-1.94.5/lists/shlock.12271' = failed: Permission denied The second message says about the same thing but the subject says Can't = open log. Any suggestions would be greatly appreciated. I don't want to have to = run with my permissions wide open and (to my way of thinking), majordomo = shouldn't rely on group-writable directories when it knows that sendmail = doesn't like that.=20 Thanks, Ric ------=_NextPart_000_0039_01BF7AD8.FBB7E200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I'm having some problems with the = permissions=20 required for majordomo. I have an OpenBSD 2.6 system. I followed the = readme,=20 install and FAQ. I ran into an odd loop, though. When sendmail 8.9.3 was = configured correctly (and securely), I got the following = error:
shlock: = '/usr/local/majordomo-1.94.5/lists' is not=20 writable by UID 1 GID 31
 
UID 1 is root, obviously, GID 31 is = guest. No idea=20 why it was trying to run as GID 31. I have my UID and GID set to 969. To = work=20 around the problem and at least get things working, I opened all = permissions to=20 the majordomo directory and shut off sendmails ability to care about it = (won't=20 whine about group writable permissions anymore). Now, I'm getting a mail = loop=20 (multiple messages resulting from one test message. The first message=20 says:
 
open of temp file=20 '/usr/local/majordomo-1.94.5/lists/shlock.12271' failed: Permission=20 denied
 
The second message says about the same = thing but=20 the subject says Can't open log.
 
Any suggestions would be greatly = appreciated. I=20 don't want to have to run with my permissions wide open and (to my way = of=20 thinking), majordomo shouldn't rely on group-writable directories when = it knows=20 that sendmail doesn't like that.
 
Thanks,
Ric
 
------=_NextPart_000_0039_01BF7AD8.FBB7E200-- From majordomo-users-owner Sat Feb 19 10:35:49 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA19665; Sat, 19 Feb 2000 10:17:58 -0800 (PST) Received: from bom2.vsnl.net.in (bom2.vsnl.net.in [202.54.1.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA19657 for ; Sat, 19 Feb 2000 10:17:46 -0800 (PST) Received: from hal9k.myip.org (IDENT:root@[203.197.57.51]) by bom2.vsnl.net.in (8.9.3/8.9.1) with ESMTP id AAA30374 for ; Sun, 20 Feb 2000 00:05:03 +0530 (IST) Received: from localhost (IDENT:satyap@localhost [127.0.0.1]) by hal9k.myip.org (8.9.3/8.8.7) with ESMTP id AAA07300 for ; Sun, 20 Feb 2000 00:02:44 +0530 Date: Sun, 20 Feb 2000 00:02:44 +0530 (IST) From: Satya X-Sender: satyap@hal9k.myip.org To: majordomo-users@GreatCircle.COM Subject: Re: Lets get rid of X-Authentication-Warning In-Reply-To: <3.0.32.20000218213820.00fb8010@mail.fial.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Feb 18, 2000 at 21:38, Ron Fial wrote: > Return-Path: This is required. I think one of the email RFCs requires it. > X-Authentication-Warning: server.fial.com: majordomo set sender to owner-99-l@fial.com using -f This is inserted by sendmail. It doesn't like majordomo setting a different sender than itself. I'll guess that the solution is to put majordomo in a trusted group after reading all the related security advisories. -- Satya. http://satyaonline.cjb.net/ Mumbai bus guide at http://satyaonline.cjb.net/ ! FREE! Email reminder service at http://satyaonline.cjb.net/rem.html <<< Hi! I'm a tagline virus! Steal me & join in the fun! >>> From majordomo-users-owner Sun Feb 20 11:00:20 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA04319; Sun, 20 Feb 2000 10:52:52 -0800 (PST) Received: from hn.hn.planet.gen.nz (hn.hn.planet.gen.nz [203.98.43.200]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA04312 for ; Sun, 20 Feb 2000 10:52:43 -0800 (PST) Received: from oscar (ts14.hn.planet.gen.nz [203.98.34.239]) by hn.hn.planet.gen.nz (8.9.3/8.9.3) with SMTP id IAA25195 for ; Mon, 21 Feb 2000 08:12:49 +1300 Message-ID: <001101bf7bd6$22862e20$6abffea9@oscar> From: "Michael Joyce" To: Subject: Permissions Date: Mon, 21 Feb 2000 08:10:19 +1300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I would like to know whta permissions work for people out there when they have smrsh installed. I have tried creating a sym link tried putting in a shell script. Neither of these have worked. Specifically the permissions and UID:GID of the wrapper and link. Regards, Michael From majordomo-users-owner Sun Feb 20 20:15:52 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA09160; Sun, 20 Feb 2000 18:06:49 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA09152 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:06:46 -0800 (PST) Received: from mail.investec.co.za ([196.4.0.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA00218 for ; Fri, 18 Feb 2000 04:34:23 -0800 (PST) Received: from investec.co.za ([10.0.17.19]) by mail.investec.co.za (8.9.3/8.9.0) with SMTP id OAA07720 for ; Fri, 18 Feb 2000 14:50:20 +0200 (GMT) Received: from ROUTEDOM-Message_Server by investec.co.za with Novell_GroupWise; Fri, 18 Feb 2000 14:50:22 +0200 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.2.1 Date: Fri, 18 Feb 2000 14:50:06 +0200 From: "Denton McGregor" To: Subject: Flat File input Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Dear Sir/Madam Could you please answer the following question. Does Majordomo support flat file input. ie can you take a flat file with = 100 names and input it into a list? Thanks Denton McGregor Investec Bank From majordomo-users-owner Sun Feb 20 20:22:48 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA09032; Sun, 20 Feb 2000 18:03:22 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA09022 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:03:18 -0800 (PST) Received: from hotmail.com (f104.law3.hotmail.com [209.185.241.104]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id HAA14477 for ; Thu, 17 Feb 2000 07:17:40 -0800 (PST) Received: (qmail 43131 invoked by uid 0); 17 Feb 2000 15:34:35 -0000 Message-ID: <20000217153435.43130.qmail@hotmail.com> Received: from 134.36.16.148 by www.hotmail.com with HTTP; Thu, 17 Feb 2000 07:34:34 PST X-Originating-IP: [134.36.16.148] From: "Wee Sin Koh" To: majordomo-users@GreatCircle.COM Subject: Sending mail to test list Date: Thu, 17 Feb 2000 23:34:34 SGT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi I sent a mail to the test list but I receive the error message.How can I solve the problem. ----- The following addresses had permanent fatal errors ----- "/export/home/majordomo/wrapper resend -1 test test-list" (expanded from: ) ----- Transcript of session follows ----- 550 "/export/home/majordomo/wrapper resend -1 test test-list"... Can't create output: Permission denied ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From majordomo-users-owner Sun Feb 20 20:28:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA09116; Sun, 20 Feb 2000 18:05:59 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA09106 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:05:57 -0800 (PST) Received: from firewall.globeset.com (firewall.globeset.com [207.239.133.67]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA18776 for ; Thu, 17 Feb 2000 13:16:41 -0800 (PST) Received: from earth.globeset.com (earth.globeset.com [10.1.1.5]) by firewall.globeset.com (8.9.3/8.9.3) with ESMTP id PAA02348 for ; Thu, 17 Feb 2000 15:33:47 -0600 (CST) Received: from globeset.com (funk1ntw.globeset.com [10.1.194.156]) by earth.globeset.com (8.9.3/8.9.3) with ESMTP id PAA07801 for ; Thu, 17 Feb 2000 15:33:48 -0600 (CST) Message-ID: <38AC693B.D00629D8@globeset.com> Date: Thu, 17 Feb 2000 15:33:47 -0600 From: Wade Funk Organization: Globeset X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Disable Digest? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk How do I disable digests on a certain list once it's enabled? Wade -- Wade T. Funk Globeset, Inc. Network & Systems Administrator phone: (512) 427-7849 cell#: (512) 554-5499 email: funk@globeset.com From majordomo-users-owner Sun Feb 20 20:42:40 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA08927; Sun, 20 Feb 2000 18:00:54 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA08917 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:00:52 -0800 (PST) Received: from web1405.mail.yahoo.com (web1405.mail.yahoo.com [128.11.23.169]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id OAA01974 for ; Wed, 16 Feb 2000 14:36:18 -0800 (PST) Received: (qmail 7044 invoked by uid 60001); 16 Feb 2000 22:53:11 -0000 Message-ID: <20000216225311.7043.qmail@web1405.mail.yahoo.com> Received: from [12.7.224.244] by web1405.mail.yahoo.com; Wed, 16 Feb 2000 14:53:11 PST Date: Wed, 16 Feb 2000 14:53:11 -0800 (PST) From: Jyothi Gandla Subject: Subscribed recipients do not receive email To: majordomo-users@greatcircle.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a problem with Majordomo mailing list. Could anybody help me please. The problem is that E-mail to the 'ABCD' Majordomo mailing list is disappearing into the great unknown and never been recieved by the subscribed recipients. The following are the tests conducted : 1. owner = test sender = user1 to = user2 recieved = All but owner 2. owner = test sender = user1 to = user2@XYZ.com received = All but sender Thanks in advance -Jyothi __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From majordomo-users-owner Sun Feb 20 21:00:25 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA08874; Sun, 20 Feb 2000 18:00:19 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA08821 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:00:09 -0800 (PST) Received: from exchange1.ctghub.com (cablestogo.com [207.90.74.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA26164 for ; Wed, 16 Feb 2000 07:51:51 -0800 (PST) Received: by EXCHANGE1 with Internet Mail Service (5.5.2650.21) id <1TSMV2B1>; Wed, 16 Feb 2000 11:01:56 -0500 Message-ID: <1BB0B8DF028AD21191C200A0C9E92B714359D7@EXCHANGE1> From: Chris Sweeney To: "'majordomo-users@greatcircle.com'" Subject: Help please Date: Wed, 16 Feb 2000 11:01:56 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am having problems getting Majordomo to work properly. I have it setup on Redhat Linux 6.0 and I keep getting the error message that sendmail doesnt have the permission to execute the wrapper. I have changed directory permissions to allow full access, setup the user and groups per the manual. Everything appears to work fine except when I send a message to majordomo@server3.ohiowebhosting.com I get the can't execute problem. Suggestions? Thanks! Chris Sweeney Product Manager CTG, Inc. (800)826-7904 ext. 483 (937)496-2662 FAX http://www.ctghub.com csweeney@ctghub.com From majordomo-users-owner Sun Feb 20 21:03:06 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA09149; Sun, 20 Feb 2000 18:06:41 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA09139 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:06:39 -0800 (PST) Received: from mail.investec.co.za ([196.4.0.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA24292 for ; Thu, 17 Feb 2000 22:58:36 -0800 (PST) Received: from investec.co.za ([10.0.17.19]) by mail.investec.co.za (8.9.3/8.9.0) with SMTP id JAA23221 for ; Fri, 18 Feb 2000 09:15:09 +0200 (GMT) Received: from ROUTEDOM-Message_Server by investec.co.za with Novell_GroupWise; Fri, 18 Feb 2000 09:13:34 +0200 Message-Id: X-Mailer: Novell GroupWise Internet Agent 5.5.2.1 Date: Fri, 18 Feb 2000 09:13:24 +0200 From: "Denton McGregor" To: Subject: Support Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi Please could you help. I am trying to install Majordomo. I am almost = there, however when I send a command to the majordomo address I get the = following error back. ----- The following addresses had permanent fatal errors ----- "|/majordomo/wrapper majordomo" (expanded from: ) ----- Transcript of session follows ----- sh: wrapper not available for sendmail programs 554 "|/majordomo/wrapper majordomo"... Service unavailable The following is what is installed.=20 Compaq Prosignia 300=20 150 MHz 128 MB RAM Linux ver 6.0 Sendmail ver 8.9.3 Majordomo ver 1.94.5 Can you please help. Thank you. Denton McGregor Investec Bank South Africa From majordomo-users-owner Sun Feb 20 21:12:11 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA09684; Sun, 20 Feb 2000 18:50:56 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA09674 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:50:54 -0800 (PST) Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA24222 for ; Sat, 19 Feb 2000 19:43:09 -0800 (PST) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA15608; Sat, 19 Feb 2000 20:00:33 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38AF66E1.57CEA996@gorean.org> Date: Sat, 19 Feb 2000 20:00:33 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Les Bell CC: majordomo-users@GreatCircle.COM Subject: Re: CNAME for list server References: <4B256879.0083686B.00@bifrost.lesbell.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Les Bell wrote: > > This is probably a simple question, but I've been re-reading the docs to > the extent that I can't see the wood for the trees: > > I have a host, canonical name abelard.lesbell.com.au, on which I have set > up a list. It's running majordomo 1.94.3 and sendmail 8.9.1. Because I > might well move the list to a different host later, I set up a CNAME record > for this purpose in the DNS, giving it the CNAME lists.lesbell.com.au. Aside from the fact that sendmail is probably masquerading, you should never use a CNAME as the destination for an MX record. Check out http://www.simplenet.com/support/faqs/faq-dns-mx.html if you need a reference. Good luck, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" From majordomo-users-owner Sun Feb 20 21:15:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA08870; Sun, 20 Feb 2000 18:00:16 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA08778 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:00:04 -0800 (PST) Received: from namaste.cc.columbia.edu (namaste.cc.columbia.edu [128.59.35.141]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA25494 for ; Wed, 16 Feb 2000 06:24:14 -0800 (PST) Received: from sodor.cc.columbia.edu (sodor.cc.columbia.edu [128.59.39.201]) by namaste.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id JAA25095 for ; Wed, 16 Feb 2000 09:41:06 -0500 (EST) Date: Wed, 16 Feb 2000 09:41:04 -0500 From: Joseph Brennan Reply-To: Postmaster To: majordomo-users@GreatCircle.COM Subject: Re: infinite loop {shudder} Message-ID: <26233605.3159682864@sodor.cc.columbia.edu> In-Reply-To: <4.2.2.20000215180037.00a90840@mercury.libpubinc.com> X-Mailer: Mulberry/2.0.0b8 (MacOS) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk It all worked fine except for one poor > fellow. It turns out he was on vacation and his vacation auto-responder > continually responded to the confirmation e-mail. A good vacation program like the old standard unix "vacation" [a] does not respond repeatedly to the same sender and [b] responds only to mail addressed explicitly to the user. A vacation program like that will not loop like this. There are unfortunately some bad vacation programs out there and they will stupidly loop like this. The only defensive mechanism would be to maintain some form of message database and either compare messages to recently received messages, or, more grossly, limit how many messages a sender can post per time period. I think Listproc or Listserv has implemented the former using a checksum; Majordomo does not have this feature. If a stupid vacation reply is involved there still may be a load problem with a tight loop between the list software and the subscriber, but at least the subscribers won't get their mailboxes flooded. Joseph Brennan postmaster@columbia.edu Academic Technologies Group, Academic Information Systems (AcIS) From majordomo-users-owner Sun Feb 20 21:30:49 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA09093; Sun, 20 Feb 2000 18:05:43 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA09083 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:05:41 -0800 (PST) Received: from palladium.nextlink.net (palladium.nextlink.net [208.234.218.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA17924 for ; Thu, 17 Feb 2000 12:10:50 -0800 (PST) Received: from txplanex401.internal.nextlink.net (formal.nextlink.net [208.234.219.192]) by palladium.nextlink.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id OAA06236 for ; Thu, 17 Feb 2000 14:26:38 -0600 (CST) Received: by TXPLANEX401.internal.nextlink.net with Internet Mail Service (5.5.2650.21) id <1X4ZK129>; Thu, 17 Feb 2000 14:27:27 -0600 Received: from javelin (javelin.internal.nextlink.net [10.76.100.104]) by txplanex401.internal.nextlink.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 1X4ZK128; Thu, 17 Feb 2000 14:27:20 -0600 From: "Ryan T. Smith" To: majordomo-users@greatcircle.com Subject: new install of majordomo Date: Thu, 17 Feb 2000 14:26:40 -0600 Message-ID: <01bf7985$4c74d680$0a4c6468@javelin.internal.nextlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express Unix 5.00.2013.1312 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2013.1312 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I am new to majordomo. I have just compleated a new install of majordomo-1.94.5 on Solaris. After going through the INSTALL instructions, I get to the last step, 10) Test the configuration again by creating an empty file 'test' in $listdir, and issue a 'lists' command to Majordomo: % touch /path/to/majordomo/lists/test % echo 'lists' | mail majordomo If everything is working correctly, you should get a message back from Majordomo, and not Mailer-Daemon. then I do this: > echo 'lists' |/usr/ucb/mail -v majordomo > majordomo... aliased to "|/majordomo/majordom/majordomo-1.94.5/wrapper majordomo" "|/majordomo/majordom/majordomo-1.94.5/wrapper majordomo"... Connecting to prog... "|/majordomo/majordom/majordomo-1.94.5/wrapper majordomo"... Sent It looks like the message went, but I did not receive a message from majordomo. What exactly is this testing, and what do you think I am doing wrong? Thanks for the help, -Ryan From majordomo-users-owner Sun Feb 20 21:39:09 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA08889; Sun, 20 Feb 2000 18:00:26 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA08879 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:00:22 -0800 (PST) Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA29384 for ; Wed, 16 Feb 2000 11:00:53 -0800 (PST) Received: from voltaire ([24.2.161.117]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with SMTP id <20000216191748.QBAM18674.mail.rdc1.ct.home.com@voltaire> for ; Wed, 16 Feb 2000 11:17:48 -0800 Message-ID: <026c01bf78b2$828aa7a0$1801a8c0@htfdc1.ct.home.com> From: "Gregg Burton" To: Subject: Potential way to add option of sender not receiving post to resend. Date: Wed, 16 Feb 2000 14:17:47 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I know that support for this is planned in a future version of Majordomo but: Unless there is something that I am not seeing or a post that I missed (which is possible it is a bit late), it seems that there is a way to prevent the sender from getting a duplicate of his post and still use resend (in future release of Majordomo). Difficulty to implement this solution I am not sure of, haven't had a chance to look at the code for resend. Possibly allow the sender option in the list config file to accept the $SENDER variable as it will accept as a Reply-To. Some code change surely needed as current From: variable is constructed from sender+@+resend_host. If this were done though, the outgoing message, following processing by 'resend' would appear from the original sender, allowing Sendmail to filter the message from the original sender with the Metoo option. PLEASE.. Email me directly at greggburton@home.com if you see an obvious problem with this method, otherwise I may go digging into the resend code as soon as I get a chance. The problem I have is that posts to one of my lists frequently contain large ">1.5mb" attachments. For a user on a dial-up line they are forced to wait while the message uploads, and then turn right around and wait for it to download. As a result I am unable to use resend right now. Gregg greggburton@home.com gburton@law.uconn.edu From majordomo-users-owner Sun Feb 20 21:51:58 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA09017; Sun, 20 Feb 2000 18:03:15 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id SAA09006 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 18:03:12 -0800 (PST) Received: from pandora.csd.plymouth.ac.uk (pandora.csd.plymouth.ac.uk [141.163.2.62]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA13130 for ; Thu, 17 Feb 2000 04:52:56 -0800 (PST) Received: from jhorne.csd.plymouth.ac.uk ([141.163.17.61]) by pandora.csd.plymouth.ac.uk with esmtp (Exim 3.12 #2) id 12LQgY-0000RY-00 for majordomo-users@greatcircle.com; Thu, 17 Feb 2000 13:09:34 +0000 Received: from john by jhorne.csd.plymouth.ac.uk with local (Exim 3.13 #1) id 12LQgX-0005X6-00 for majordomo-users@GreatCircle.COM; Thu, 17 Feb 2000 13:09:33 +0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 17 Feb 2000 13:09:33 -0000 (GMT) Organization: University of Plymouth From: John Horne To: majordomo-users@GreatCircle.COM Subject: RE: Majordomo and Exim Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On 16-Feb-00 at 05:48:05 Ross Anderson wrote: > This is the problem I'm having. Exim freezes all messages for > any of the lists if the lists are UID and GID by Majordomo. I've had > majordomo working in a hacked sort of way. By making the list owned > by majordomo and group of mail, Exim will deliver messages. I've > added mail (the group that exim runs as) to the group majordomo. > This didn't allow exim to deliver the mail either. > This wouldn't be a problem except when majordomo itself > processes an un-subscribe it fails because it is being denied the > chown to the files because the group is mail. I get an Abort message > operation not permitted. The lock file *.new gets all messed up. > We run md 1.94.4 with exim 3.12 on Sun solaris 7 systems. Both exim and md are group mail. Exim runs under its own userid, as does majordomo. I just tried unsubscribing myself from a list and it worked fine. I may be a bit thick here but where does the chown come into it? What is trying to chown the list file and why? The exim configure file specifies 'group=mail' on the majordomo directors. John. -------------------------------------------------------------------------- John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914 E-mail: jhorne@plymouth.ac.uk Finger for PGP key: john@jhorne.csd.plymouth.ac.uk From majordomo-users-owner Sun Feb 20 23:17:44 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA12361; Sun, 20 Feb 2000 22:55:44 -0800 (PST) Received: from mail.rdc1.sdca.home.com (ha1.rdc1.sdca.home.com [24.0.3.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA12349 for ; Sun, 20 Feb 2000 22:55:30 -0800 (PST) Received: from cx588769a ([24.4.67.154]) by mail.rdc1.sdca.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <20000221071310.IPOK28464.mail.rdc1.sdca.home.com@cx588769a> for ; Sun, 20 Feb 2000 23:13:10 -0800 Message-ID: <002d01bf7c3b$a7a227c0$9a430418@elcjn1.sdca.home.com> From: "Anthony M. Abate" To: Subject: 1.94.5 Problem Date: Sun, 20 Feb 2000 23:17:04 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I installed 1-94.5 on one of linux machines and configured it like the other installations I've done and I get the following message. I'm stumped. This is a RH 6.1 installation and the other machine is RH 6.0. Am i missing something? ----- The following addresses had permanent fatal errors ----- ptr :include:/usr/test/majordomo-1.94.5/lists/ptr-fa (expanded from: ptr) ----- Transcript of session follows ----- 550 :include:/usr/test/majordomo-1.94.5/lists/ptr-fa... Cannot open /usr/test/majordomo-1.94.5/lists/ptr-fa: World writable directory Message delivered to mailing list ptr 554 ptr... aliasing/forwarding loop broken From majordomo-users-owner Mon Feb 21 00:45:18 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id AAA13178; Mon, 21 Feb 2000 00:25:57 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id AAA13171 for ; Mon, 21 Feb 2000 00:25:51 -0800 (PST) Received: (qmail 4309 invoked from network); 21 Feb 2000 08:43:33 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 21 Feb 2000 08:43:33 -0000 Date: Mon, 21 Feb 2000 01:40:41 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: Denton McGregor cc: majordomo-users@GreatCircle.COM Subject: Re: Support In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is the infamous smrsh problem that everyone runs into. Search the FAQ for "smrsh" and you will see how to enable the sendmail service. Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com On Fri, 18 Feb 2000, Denton McGregor wrote: > Hi > > Please could you help. I am trying to install Majordomo. I am almost there, however when I send a command to the majordomo address I get the following error back. > > ----- The following addresses had permanent fatal errors ----- > "|/majordomo/wrapper majordomo" > (expanded from: ) > > ----- Transcript of session follows ----- > sh: wrapper not available for sendmail programs > 554 "|/majordomo/wrapper majordomo"... Service unavailable > > The following is what is installed. > > Compaq Prosignia 300 > 150 MHz > 128 MB RAM > > Linux ver 6.0 > Sendmail ver 8.9.3 > Majordomo ver 1.94.5 > > > Can you please help. > > Thank you. > Denton McGregor > Investec Bank > South Africa > > From majordomo-users-owner Mon Feb 21 02:45:33 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id CAA15410; Mon, 21 Feb 2000 02:33:12 -0800 (PST) Received: from mazama.FIAL.COM ([206.58.211.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id CAA15402 for ; Mon, 21 Feb 2000 02:33:04 -0800 (PST) Received: from toshiba ([206.58.211.79]) by mazama.FIAL.COM (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-0U10L2S100) with SMTP id AAA225 for ; Mon, 21 Feb 2000 02:51:12 -0800 Message-Id: <3.0.1.32.20000221024737.00dac7b8@mazama.fial.com> X-Sender: ron@mazama.fial.com X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Mon, 21 Feb 2000 02:47:37 -0800 To: majordomo-users@GreatCircle.COM From: ron@fial.com (Ron Fial) Subject: Thank You, all Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thank you very much, all who replied to my question about: Lets get rid of X-Authentication Warning. Majordomo is now a Sendmail trusted user, and the warning is gone. I'm a happy camper..er list manager. Ron Fial From majordomo-users-owner Mon Feb 21 04:13:50 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id EAA18104; Mon, 21 Feb 2000 04:08:10 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA18097 for ; Mon, 21 Feb 2000 04:08:03 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id HAA10389; Mon, 21 Feb 2000 07:24:49 -0500 (EST) Date: Mon, 21 Feb 2000 07:24:49 -0500 (EST) From: "Bill Casti (System Admin)" To: "Anthony M. Abate" cc: majordomo-users@GreatCircle.COM Subject: Re: 1.94.5 Problem In-Reply-To: <002d01bf7c3b$a7a227c0$9a430418@elcjn1.sdca.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Permissions for the /usr/local/majordomo/lists directory should be 775, not 777. Bill On Sun, 20 Feb 2000, Anthony M. Abate wrote: > > I installed 1-94.5 on one of linux machines and configured it like the other > installations I've done and I get the following message. I'm stumped. This > is a RH 6.1 installation and the other machine is RH 6.0. Am i missing > something? > > > ----- The following addresses had permanent fatal errors ----- > ptr > :include:/usr/test/majordomo-1.94.5/lists/ptr-fa > (expanded from: ptr) > > ----- Transcript of session follows ----- > 550 :include:/usr/test/majordomo-1.94.5/lists/ptr-fa... Cannot open > /usr/test/majordomo-1.94.5/lists/ptr-fa: World writable directory > Message delivered to mailing list ptr > 554 ptr... aliasing/forwarding loop broken > > From majordomo-users-owner Mon Feb 21 04:28:53 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id DAA17969; Mon, 21 Feb 2000 03:55:16 -0800 (PST) Received: from dsl-207-105-45-243.hollywood.relaypoint.net (dsl-207-105-45-243.hollywood.relaypoint.net [207.105.45.243]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id DAA17960 for ; Mon, 21 Feb 2000 03:55:09 -0800 (PST) Received: from pajamian.dhs.org (WLA20-25.WLA.Access1.net [63.192.92.226]) by dsl-207-105-45-243.hollywood.relaypoint.net (8.9.3/8.9.3) with ESMTP id EAA01926 for ; Mon, 21 Feb 2000 04:21:09 -0800 Message-ID: <38B12CF9.30A77F06@pajamian.dhs.org> Date: Mon, 21 Feb 2000 04:18:01 -0800 From: Peter Ajamian X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Re: 1.94.5 Problem References: <002d01bf7c3b$a7a227c0$9a430418@elcjn1.sdca.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk "Anthony M. Abate" wrote: > > I installed 1-94.5 on one of linux machines and configured it like the other > installations I've done and I get the following message. I'm stumped. This > is a RH 6.1 installation and the other machine is RH 6.0. Am i missing > something? > > ----- The following addresses had permanent fatal errors ----- > ptr > :include:/usr/test/majordomo-1.94.5/lists/ptr-fa > (expanded from: ptr) > > ----- Transcript of session follows ----- > 550 :include:/usr/test/majordomo-1.94.5/lists/ptr-fa... Cannot open > /usr/test/majordomo-1.94.5/lists/ptr-fa: World writable directory > Message delivered to mailing list ptr > 554 ptr... aliasing/forwarding loop broken The newer versions of sendmail will not allow your to run programs in world writable (and I think not even group writable) subdirectories (or branches off of the same). Simply chmod 755 the offending directory. Regards, Peter Disclaimer: I am still relatively new to Majordomo myself, take my advice for what it is, the advice of a fellow user, and not that of a professional. From majordomo-users-owner Mon Feb 21 06:42:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA19293; Mon, 21 Feb 2000 06:33:45 -0800 (PST) Received: from mail1.wits.ac.za (mail1.wits.ac.za [146.141.15.210]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA19286 for ; Mon, 21 Feb 2000 06:33:36 -0800 (PST) Received: from [146.141.15.230] (helo=iqbal) by mail1.wits.ac.za with smtp (Exim 2.12 #1) id 12MvwR-0000Ss-00 for majordomo-users@greatcircle.com; Mon, 21 Feb 2000 16:44:11 +0000 From: sherona@cns.wits.ac.za To: majordomo-users@greatcircle.com Date: Mon, 21 Feb 2000 16:57:20 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: majordomo and exim Message-Id: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi I am currently running majordomo-1.94.4 on a SUn sparc Server 1000 running solaris 2.7 I am using exim2.12 as a mailer. Everything seems to be running OK except that the archives don't work. They do not update at all. Is there anything that should be configured differently for exim or anything else. Any help would be greatly appreciated. Thanks cheers sherona Computer and Network Services University Of The Witwatersrand, http://www.wits.ac.za Johannesburg South Africa From majordomo-users-owner Mon Feb 21 07:12:35 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA19716; Mon, 21 Feb 2000 07:08:05 -0800 (PST) Received: from usinter.net (mail.usinter.net [206.171.66.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA19707 for ; Mon, 21 Feb 2000 07:07:58 -0800 (PST) Received: from usinter.net [209.85.130.137] by usinter.net [206.171.66.25] with SMTP (MDaemon.v2.8.7.0.R) for ; Mon, 21 Feb 2000 07:25:16 -0800 Message-ID: <38B15917.7DC856B3@usinter.net> Date: Mon, 21 Feb 2000 07:26:15 -0800 From: "Todd A. Lyons" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Re: CNAME for list server References: <4B256879.0083686B.00@bifrost.lesbell.com.au> <38AF66E1.57CEA996@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: majordomo-users@GreatCircle.COM X-Return-Path: cannonball@usinter.net Reply-To: cannonball@usinter.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Doug Barton wrote: > Aside from the fact that sendmail is probably masquerading, you should > never use a CNAME as the destination for an MX record. Check out > http://www.simplenet.com/support/faqs/faq-dns-mx.html if you need a > reference. I knew that only because I have been told repeatedly to not use a CNAME as an MX record. But the link you supplied does not make one mention of CNAME's in regard to MX records. Not complaining, just looking for somewhere that explains WHY I can't do this. -- Blue skies... Cannonball http://www.mrball.net * One ring to rule them all, One ring to find them * * One ring to bring them all, and in the darkness bind them * Sauron From majordomo-users-owner Mon Feb 21 07:43:54 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA19703; Mon, 21 Feb 2000 07:06:36 -0800 (PST) Received: from exchange1.ctghub.com (cablestogo.com [207.90.74.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA19696 for ; Mon, 21 Feb 2000 07:06:28 -0800 (PST) Received: by EXCHANGE1 with Internet Mail Service (5.5.2650.21) id <1TSMVN1C>; Mon, 21 Feb 2000 10:17:03 -0500 Message-ID: <1BB0B8DF028AD21191C200A0C9E92B71435A01@EXCHANGE1> From: Chris Sweeney To: "'cannonball@usinter.net'" Cc: "'majordomo-users@greatcircle.com'" Subject: RE: [Fwd: Majordomo problem] Date: Mon, 21 Feb 2000 10:16:55 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thanks, I had done all that with still no luck. Turns out I needed to make a link to the wapper. 2.11 - I get "sh: wrapper not available for sendmail programs" You're on a system which uses smrsh. (sendmail restricted shell). You have to configure smrsh to allow it to execute the wrapper. Normally this is done by creating a symlink in /var/adm/sm.bin (in some it's /etc/smrsh) to Majordomo's wrapper program. I kept missing this in the FAQ until I got the one via the list last week. Perhaps it was a new addition, but it fixed the problem. Thanks for your help! Chris Sweeney Product Manager CTG, Inc. (800)826-7904 ext. 483 (937)496-2662 FAX http://www.ctghub.com csweeney@ctghub.com -----Original Message----- From: Todd A. Lyons [mailto:cannonball@usinter.net] Sent: Monday, February 21, 2000 10:12 AM To: Chris Sweeney Subject: [Fwd: Majordomo problem] Here is a standard reply for majordomo permissions problems. It may not apply in your case since the problem involves the wrapper, but check read through it and make adjustments accordingly. If you're having problems with the wrapper, the test procedure should have caught it when you were compiling. Stupid questions, but when you were compiling, were you compiling as root? What uid.gid is sendmail running as? What uid.gid is majordomo running as? Don't forget to make majordomo a trusted user of sendmail. Blue skies... Cannonball http://www.mrball.net -------- Original Message -------- Subject: Re: install problem Date: Sat, 05 Feb 2000 18:45:27 -0800 From: "Todd A. Lyons" To: Norio Ohki Norio Ohki wrote: > :include:/usr/local/majordomo-1.94.3/lists/abt > I tried to modify permissions of directory and files, in vain. > What should I check settings? Any advice will be appreciated. -----From the sendmail 8.9 FAQ Question 3.32: Now the differences that make this work that may not be the same as instructed by the majordomo instructions: 1) Put the majordomo.aliases file in /etc, not in the majordomo install directory. 2) Make the permissions on /usr/local/majordomo 0751, not 0775. 3) Make the permissions on /usr/local/majordomo/Log 0664, owned by majordomo, group majordomo. 4) /usr/local/majordomo/lists is mode 0755, owner majordomo, group majordomo 5) The permissions owners for the lists should be 0755 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/ 0664 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/abt 0660 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/abt.config 0664 majordomo.majordomo /usr/local/majordomo-1.94.4/lists/abt.info ------End quote The only difference between sendmail's recommendation and my working system are that I have all groups set to daemon (ie majordomo.daemon) -- Blue skies... Cannonball * One ring to rule them all, One ring to find them * * One ring to bring them all, and in the darkness bind them * Sauron From majordomo-users-owner Mon Feb 21 08:12:01 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA20415; Mon, 21 Feb 2000 08:05:09 -0800 (PST) Received: from owbn.org (mail.owbn.org [206.156.227.57]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA20405 for ; Mon, 21 Feb 2000 08:05:00 -0800 (PST) Received: from rosander (helo=localhost) by owbn.org with local-esmtp (Exim 3.03 #1) id 12Mvfa-00016g-00; Mon, 21 Feb 2000 10:26:46 -0600 Date: Mon, 21 Feb 2000 10:26:46 -0600 (CST) From: To: John Horne cc: majordomo-users@GreatCircle.COM Subject: RE: Majordomo and Exim In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Thu, 17 Feb 2000, John Horne wrote: > On 16-Feb-00 at 05:48:05 Ross Anderson wrote: > > This is the problem I'm having. Exim freezes all messages for > > any of the lists if the lists are UID and GID by Majordomo. I've had > > majordomo working in a hacked sort of way. By making the list owned > > by majordomo and group of mail, Exim will deliver messages. I've > > added mail (the group that exim runs as) to the group majordomo. > > This didn't allow exim to deliver the mail either. > > This wouldn't be a problem except when majordomo itself > > processes an un-subscribe it fails because it is being denied the > > chown to the files because the group is mail. I get an Abort message > > operation not permitted. The lock file *.new gets all messed up. > > > We run md 1.94.4 with exim 3.12 on Sun solaris 7 systems. Both exim and md > are group mail. Exim runs under its own userid, as does majordomo. I just > tried unsubscribing myself from a list and it worked fine. I may be a bit > thick here but where does the chown come into it? What is trying to chown > the list file and why? Well the Chown comes from Majordomo. Honestly I'm not sure what it is trying to do by chowning. I know that it is creating a lock file of the subscription list and that is where it is having fits. Why it is I'm not sure. > > The exim configure file specifies 'group=mail' on the majordomo directors. > > John. > > -------------------------------------------------------------------------- > John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914 > E-mail: jhorne@plymouth.ac.uk > Finger for PGP key: john@jhorne.csd.plymouth.ac.uk > > From majordomo-users-owner Mon Feb 21 08:57:16 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA20831; Mon, 21 Feb 2000 08:27:11 -0800 (PST) Received: from mail.rdc1.sdca.home.com (ha1.rdc1.sdca.home.com [24.0.3.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA20824 for ; Mon, 21 Feb 2000 08:27:03 -0800 (PST) Received: from cx588769a ([24.4.67.154]) by mail.rdc1.sdca.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <20000221164449.NXXP28464.mail.rdc1.sdca.home.com@cx588769a>; Mon, 21 Feb 2000 08:44:49 -0800 Message-ID: <002701bf7c8b$835446a0$9a430418@elcjn1.sdca.home.com> From: "Anthony M. Abate" To: "Peter Ajamian" , References: <002d01bf7c3b$a7a227c0$9a430418@elcjn1.sdca.home.com> <38B12CF9.30A77F06@pajamian.dhs.org> Subject: Re: 1.94.5 Problem Date: Mon, 21 Feb 2000 08:48:43 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thanks for all the help everyone, I discovered the permissions problem on the home directory of Majordomo at about midnight last night. Everything is up and running perfectly. -T Sent: Monday, February 21, 2000 4:18 AM Subject: Re: 1.94.5 Problem > "Anthony M. Abate" wrote: > > > > I installed 1-94.5 on one of linux machines and configured it like the other > > installations I've done and I get the following message. I'm stumped. This > > is a RH 6.1 installation and the other machine is RH 6.0. Am i missing > > something? > > > > ----- The following addresses had permanent fatal errors ----- > > ptr > > :include:/usr/test/majordomo-1.94.5/lists/ptr-fa > > (expanded from: ptr) > > > > ----- Transcript of session follows ----- > > 550 :include:/usr/test/majordomo-1.94.5/lists/ptr-fa... Cannot open > > /usr/test/majordomo-1.94.5/lists/ptr-fa: World writable directory > > Message delivered to mailing list ptr > > 554 ptr... aliasing/forwarding loop broken > > The newer versions of sendmail will not allow your to run programs in > world writable (and I think not even group writable) subdirectories (or > branches off of the same). Simply chmod 755 the offending directory. > > Regards, Peter > > Disclaimer: I am still relatively new to Majordomo myself, take my > advice for what it is, the advice of a fellow user, and not that of a > professional. From majordomo-users-owner Mon Feb 21 09:26:15 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA21402; Mon, 21 Feb 2000 09:07:47 -0800 (PST) Received: from burlma1-smrt1.gtei.net (burlma1-smrt1.gtei.net [4.2.35.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA21395 for ; Mon, 21 Feb 2000 09:07:40 -0800 (PST) Received: from rmessier (rmessier.sys.gtei.net [4.2.32.147]) by burlma1-smrt1.gtei.net (8.9.3/8.9.3) with SMTP id RAA16477; Mon, 21 Feb 2000 17:24:59 GMT Message-ID: <00f701bf7c90$941cbf30$93200204@sys.gtei.net> From: "Ric Messier" To: "Bill Casti \(System Admin\)" , "Anthony M. Abate" Cc: References: Subject: Re: 1.94.5 Problem Date: Mon, 21 Feb 2000 12:24:58 -0500 Organization: Chaotic @Best MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk And then sendmail bitches about group-writable directory. Any good way around that other than to tell sendmail not to care (which I don't think is a great solution)? ----- Original Message ----- From: "Bill Casti (System Admin)" To: "Anthony M. Abate" Cc: Sent: Monday, February 21, 2000 7:24 AM Subject: Re: 1.94.5 Problem > > Permissions for the /usr/local/majordomo/lists directory should be 775, > not 777. > > Bill > > On Sun, 20 Feb 2000, Anthony M. Abate wrote: > > > > > I installed 1-94.5 on one of linux machines and configured it like the other > > installations I've done and I get the following message. I'm stumped. This > > is a RH 6.1 installation and the other machine is RH 6.0. Am i missing > > something? > > > > > > ----- The following addresses had permanent fatal errors ----- > > ptr > > :include:/usr/test/majordomo-1.94.5/lists/ptr-fa > > (expanded from: ptr) > > > > ----- Transcript of session follows ----- > > 550 :include:/usr/test/majordomo-1.94.5/lists/ptr-fa... Cannot open > > /usr/test/majordomo-1.94.5/lists/ptr-fa: World writable directory > > Message delivered to mailing list ptr > > 554 ptr... aliasing/forwarding loop broken > > > > > > From majordomo-users-owner Mon Feb 21 12:42:42 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA23673; Mon, 21 Feb 2000 12:28:42 -0800 (PST) Received: from mail.bcpl.net ([204.255.212.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA23666 for ; Mon, 21 Feb 2000 12:28:36 -0800 (PST) Received: from localhost (fold@localhost) by mail.bcpl.net (8.9.1/8.9.1) with ESMTP id PAA16041 for ; Mon, 21 Feb 2000 15:46:21 -0500 (EST) Date: Mon, 21 Feb 2000 15:46:21 -0500 (EST) From: Chip Old To: Majordomo-Users List Subject: Re: CNAME for list server In-Reply-To: <38B15917.7DC856B3@usinter.net> Message-ID: X-Organization: BCPL.NET Internet Services MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Mon, 21 Feb 2000, Todd A. Lyons wrote to majordomo-users@GreatCircle.COM: > I knew that only because I have been told repeatedly to not use a > CNAME as an MX record. But the link you supplied does not make one > mention of CNAME's in regard to MX records. Not complaining, just > looking for somewhere that explains WHY I can't do this. Sendmail (and most other MTAs) expects to find the canonical name of the local host on which it is running on the right-hand side of an MX record. It doesn't check for aliases on the left side of CNAME records. This means the MTA can't find itself in the MX list, resulting in a mail loop. In older versions of sendmail this resulted in "I refuse to talk to myself" error messages. In newer versions the error message is "MX list for points back to . local configuration error. -- Chip Old (Francis E. Old) E-Mail: fold@bcpl.net Manager, BCPL Network Services Voice: 410-887-6180 Manager, BCPL.NET Internet Services FAX: 410-887-2091 Baltimore County Public Library ICBM: 39.39910 N 320 York Road 76.60300 W Towson, Maryland 21204 U.S.A. From majordomo-users-owner Mon Feb 21 13:14:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA23618; Mon, 21 Feb 2000 12:23:49 -0800 (PST) Received: from athena.wsee.local (mail.35wsee.com [208.166.71.89]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA23611 for ; Mon, 21 Feb 2000 12:23:41 -0800 (PST) Received: from mars (mars.wsee.local [192.168.10.13]) by athena.wsee.local (8.9.3/8.9.3) with SMTP id PAA09445 for ; Mon, 21 Feb 2000 15:41:29 -0500 Message-ID: <03cc01bf7cac$0765e280$0d0aa8c0@wsee.local> Reply-To: "Dan Nungesser" From: "Dan Nungesser" To: Subject: noadvertise is selective about when it works. Date: Mon, 21 Feb 2000 15:41:25 -0500 Organization: WSEE Television Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk If someone has time, I could use a little help. Noadvertise seems to be selective about where it works. This is a new install of 1.94.5 on linux 2.2.5 I am administering with Webmin-0.72 I have two small lists: stocks and test. Stocks was set up first by hand and later tweeked with webmin. Test was set up with webmin. When I set noadvertise to /.*/ on both lists, the lists command shows stocks but not test. I have gone so far as to copy the test.config to stocks.config and then change the appropriate parameters to make the list work again and I get the same results. Perms are: -rw-r--rw- 1 majordom majordom 109 Feb 15 08:21 stocks -rw-r--r-- 1 majordom majordom 1326 Feb 21 15:22 stocks.config -rw-rw-rw- 1 majordom majordom 387 Feb 21 15:06 stocks.info -rw-rw-r-- 1 majordom majordom 511 Feb 21 15:06 stocks.intro -rw-rw-r-- 1 majordom majordom 14 Feb 21 11:38 test -rw-r--r-- 1 majordom majordom 756 Feb 21 15:23 test.config -rw-rw-r-- 1 majordom majordom 0 Feb 21 11:38 test.info -rw-rw-r-- 1 majordom majordom 511 Feb 21 15:08 test.intro Postmaster is the owner of both lists. Postmaster is aliased to root which is aliased to me. Anyone have any ideas? I sure would appreciate the help. Thanks Dan Nungesser Chief Engineer WSEE Television Inc. Erie, PA. 16501 Tel: 814-455-7575 Fax: 814-454-2564 Watch our newscast at http://www.newscastnow.com/stations/wsee/player.shtml or Visit our web site at http://www.35wsee.com/ Because e-mail can be forged and altered electronically, the integrity of this communication cannot be guaranteed From majordomo-users-owner Mon Feb 21 15:11:43 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA25248; Mon, 21 Feb 2000 14:05:46 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA25229 for majordomo-users@greatcircle.com; Mon, 21 Feb 2000 14:05:36 -0800 (PST) Received: from sarc.phyb.uic.edu (sarc.phyb.uic.edu [128.248.33.246]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA09516 for ; Sun, 20 Feb 2000 18:42:50 -0800 (PST) From: pdetombe@sarc.phyb.uic.edu Received: (from pdetombe@localhost) by sarc.phyb.uic.edu (8.9.3/8.9.3) id UAA05190 for majordomo-users@greatcircle.com; Sun, 20 Feb 2000 20:55:56 -0500 Date: Sun, 20 Feb 2000 20:55:56 -0500 Message-Id: <200002210155.UAA05190@sarc.phyb.uic.edu> To: majordomo-users@greatcircle.com Subject: invalid return address on LINUXPPC Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I am trying to install Majordomo on a LINUXPPC system (Q3 1999 release) All seem well but I can't get majordomo to work. I keep getting the error invalid return address, even though $whereami is set correctly to my domain name and $whoami to the correct address : majordomo@xx.xx Any help is appreciated. Pieter de Tombe From majordomo-users-owner Mon Feb 21 15:26:30 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA24369; Mon, 21 Feb 2000 13:10:41 -0800 (PST) Received: from firewall.globeset.com (firewall.globeset.com [207.239.133.67]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA24357 for ; Mon, 21 Feb 2000 13:10:31 -0800 (PST) Received: from earth.globeset.com (earth.globeset.com [10.1.1.5]) by firewall.globeset.com (8.9.3/8.9.3) with ESMTP id PAA24895 for ; Mon, 21 Feb 2000 15:28:19 -0600 (CST) Received: from globeset.com (funk1ntw.globeset.com [10.1.194.156]) by earth.globeset.com (8.9.3/8.9.3) with ESMTP id PAA29646 for ; Mon, 21 Feb 2000 15:28:19 -0600 (CST) Message-ID: <38B1ADF3.234BAF0B@globeset.com> Date: Mon, 21 Feb 2000 15:28:19 -0600 From: Wade Funk Organization: Globeset X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Security? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is there a way to provide my internal users information via 'lists' while making it invisible to external viewers? Thanks, Wade From majordomo-users-owner Mon Feb 21 15:44:16 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA25197; Mon, 21 Feb 2000 14:04:23 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA25187 for majordomo-users@greatcircle.com; Mon, 21 Feb 2000 14:04:21 -0800 (PST) Received: from sparky (d185fdede.rochester.rr.com [24.95.222.222]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA06131 for ; Sun, 20 Feb 2000 14:31:19 -0800 (PST) Received: from mac.com ([192.168.0.2]) by sparky (8.9.3/8.8.7) with ESMTP id WAA03541 for ; Tue, 20 Feb 2001 22:55:54 -0500 Message-ID: <38B06F4A.7880AE09@mac.com> Date: Sun, 20 Feb 2000 17:48:39 -0500 From: laura despard Reply-To: laurades@rochester.rr.com X-Mailer: Mozilla 4.61 (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo-Users@GreatCircle.COM Subject: problem with permisions Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk i just set up majordomo and am having a proble, i ca nsubscribe to a list but when i try to send mail to the list, the owner of the list(owner-family) gets back this: The original message was received at Tue, 20 Feb 2001 22:46:24 -0500 from majordomo@localhost ----- The following addresses had permanent fatal errors ----- family-list :include:/usr/test/majordomo-1.94.4/lists/family (expanded from: family-list) ----- Transcript of session follows ----- 550 :include:/usr/test/majordomo-1.94.4/lists/family... Cannot open /usr/test/majordomo-1.94.4/lists/family: Group writable directory 554 family-list... aliasing/forwarding loop broken any ideas? please send responces to edwarddes@mac.com thanks! From majordomo-users-owner Mon Feb 21 15:59:21 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA24960; Mon, 21 Feb 2000 13:52:11 -0800 (PST) Received: from krusty1.krusty-motorsports.com (krusty1.krusty-motorsports.com [192.94.170.8]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA24953 for ; Mon, 21 Feb 2000 13:52:05 -0800 (PST) Received: from ts2p44.wizvax.net ([204.97.162.109] helo=shelflife ident=hidden-user) by krusty1.krusty-motorsports.com with smtp (Exim 3.03 #1) id 12N114-0001Un-00; Mon, 21 Feb 2000 17:09:18 -0500 X-Sender: rwelty_suespammers.org@mail.suespammers.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Mon, 21 Feb 2000 17:08:09 -0500 To: cannonball@usinter.net From: Richard Welty Subject: Re: CNAME for list server Cc: majordomo-users@greatcircle.com In-Reply-To: <38B15917.7DC856B3@usinter.net> References: <4B256879.0083686B.00@bifrost.lesbell.com.au> <38AF66E1.57CEA996@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 07:26 AM 2/21/00 -0800, you wrote: >I knew that only because I have been told repeatedly to not use a CNAME >as an MX record. But the link you supplied does not make one mention of >CNAME's in regard to MX records. Not complaining, just looking for >somewhere that explains WHY I can't do this. it's in an RFC somewhere. i don't recall which one, but there is an RFC that explicitly calls this practice out as bad. most MTAs will actually follow the CNAME and make it work. the problem is that properly functioning MTAs will have to do extra lookups to resolve any CNAMEs; it may not seem so bad for one or two, but for a Very Large mail server farm, this could be a tremendous amount of extra overhead, incurred in DNS lookups. richard -- Richard Welty rwelty@suespammers.org Any type of UBE (Unsolicited Bulk EMail) to this account is unwanted. Join the fight against spam: http://www.cauce.org/ From majordomo-users-owner Mon Feb 21 15:59:59 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA24804; Mon, 21 Feb 2000 13:44:24 -0800 (PST) Received: from guinness.digisle.net (guinness.digisle.net [167.216.152.33]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA24797 for ; Mon, 21 Feb 2000 13:44:18 -0800 (PST) Received: from visi.com (dhcp-vpn-sf-64-30.digisle.com [172.16.64.30]) by guinness.digisle.net (8.9.3/8.9.3/digisle) with ESMTP id WAA26162; Mon, 21 Feb 2000 22:00:07 GMT Message-ID: <38B1B55F.D0499099@visi.com> Date: Mon, 21 Feb 2000 15:59:59 -0600 From: David Barr X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Ric Messier CC: "Bill Casti (System Admin)" , "Anthony M. Abate" , majordomo-users@GreatCircle.COM Subject: Re: 1.94.5 Problem References: <00f701bf7c90$941cbf30$93200204@sys.gtei.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Ric Messier wrote: > > And then sendmail bitches about group-writable directory. > > Any good way around that other than to tell sendmail not to care (which I > don't think is a great solution)? The Majordomo FAQ goes into excruitiating detail on how to get all the majordomo files and directory permissions right. --Dave From majordomo-users-owner Mon Feb 21 16:57:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA26926; Mon, 21 Feb 2000 16:49:07 -0800 (PST) Received: from linuxrealm.wintembergs.com (digital-7-155.exis.net [205.252.74.155]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA26919 for ; Mon, 21 Feb 2000 16:48:58 -0800 (PST) Received: from linuxfan.com (IDENT:eagle3@localhost.localdomain [127.0.0.1]) by linuxrealm.wintembergs.com (8.9.3/8.9.3) with ESMTP id UAA03082 for ; Mon, 21 Feb 2000 20:05:37 -0500 Message-ID: <38B1E0E0.9858645C@linuxfan.com> Date: Mon, 21 Feb 2000 20:05:37 -0500 From: Bobby Wintemberg X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Majordomo Error: Service Unavailable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Ok, I setup a mailing list with 18 e-mail addresses. All of these ones give errors: The original message was received at Mon, 21 Feb 2000 19:55:16 -0500 from mail@localhost ----- The following addresses had permanent fatal errors ----- ----- Transcript of session follows ----- 451 ... lilsaiyans.4mg.com: Name server timeout ... while talking to yg.mx.aol.com.: >>> MAIL From: <<< 550 REQUESTED ACTION NOT TAKEN: DNS FAILURE 554 ,,,,... Service unavailable ... while talking to mx.jersey.juno.com.: >>> RCPT To: <<< 550 cracker_jack@juno.com Account Inactive 550 ... User unknown ... while talking to mail6.bellatlantic.net.: >>> MAIL From: SIZE=521 <<< 501 ... Sender domain must exist 501 ... Data format error ... while talking to mail.sybercom.net.: >>> MAIL From: SIZE=521 <<< 550 5.1.8 Invalid address 554 ... Service unavailable ... while talking to a-mx.gateway.net.: >>> MAIL From: <<< 550 REQUESTED ACTION NOT TAKEN: DNS FAILURE 554 ... Service unavailable [ Part 2: "Delivery Status" ] Reporting-MTA: dns; linuxrealm.wintembergs.com Arrival-Date: Mon, 21 Feb 2000 19:55:16 -0500 Final-Recipient: RFC822; Bhavnfun@aol.com Action: failed Status: 5.0.0 Remote-MTA: DNS; yg.mx.aol.com Diagnostic-Code: SMTP; 550 REQUESTED ACTION NOT TAKEN: DNS FAILURE Last-Attempt-Date: Mon, 21 Feb 2000 19:56:49 -0500 Final-Recipient: RFC822; PDJTJ@aol.com Action: failed Status: 5.0.0 Remote-MTA: DNS; yg.mx.aol.com Diagnostic-Code: SMTP; 550 REQUESTED ACTION NOT TAKEN: DNS FAILURE Last-Attempt-Date: Mon, 21 Feb 2000 19:56:49 -0500 I won't post the rest because it's mostly the same just different e-mail addresses basically. What's wrong with this? -- Bobby Wintemberg - eagle3@linuxfan.com http://linuxrealm.dyndns.org #linux on irc.starchat.net From majordomo-users-owner Mon Feb 21 21:12:37 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA29299; Mon, 21 Feb 2000 21:00:30 -0800 (PST) Received: from usinter.net (mail.usinter.net [206.171.66.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA29290 for ; Mon, 21 Feb 2000 21:00:22 -0800 (PST) Received: from usinter.net [209.85.130.137] by usinter.net [206.171.66.25] with SMTP (MDaemon.v2.8.7.0.R) for ; Mon, 21 Feb 2000 21:17:28 -0800 Message-ID: <38B21C21.D07CD8F3@usinter.net> Date: Mon, 21 Feb 2000 21:18:25 -0800 From: "Todd A. Lyons" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Re: Majordomo Error: Service Unavailable References: <38B1E0E0.9858645C@linuxfan.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: majordomo-users@GreatCircle.COM X-Return-Path: cannonball@usinter.net Reply-To: cannonball@usinter.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Bobby Wintemberg wrote: > <<< 501 ... Sender domain > must exist It's telling you what the problem is. I think this might also point to what the problem might be: [root@arm /pub]# nslookup wintembergs.com Server: ns1.usinter.net Address: 206.171.66.2 *** ns1.usinter.net can't find wintembergs.com: Non-existent host/domain Your domain must exist. If not, most mail servers will deny your relay. -- Blue skies... Cannonball http://www.mrball.net * One ring to rule them all, One ring to find them * * One ring to bring them all, and in the darkness bind them * Sauron From majordomo-users-owner Tue Feb 22 06:56:21 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA07375; Tue, 22 Feb 2000 06:50:57 -0800 (PST) Received: from seymour39.SNMP.COM (seymour39.snmp.com [192.147.142.39]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA07368 for ; Tue, 22 Feb 2000 06:50:52 -0800 (PST) Received: from aix43.snmp.com (aix43.snmp.com [192.147.142.137]) by seymour39.SNMP.COM (8.9.3/m.000221) with ESMTP id KAA29687 for ; Tue, 22 Feb 2000 10:08:47 -0500 (EST) Received: from aix43.snmp.com (LOCALHOST [127.0.0.1]) by aix43.snmp.com (8.9.3/snmpclient.mc-990615) with ESMTP id KAA22390 for ; Tue, 22 Feb 2000 10:08:47 -0500 Message-Id: <200002221508.KAA22390@aix43.snmp.com> to: majordomo-users@greatcircle.com Subject: rewriting "From:" Date: Tue, 22 Feb 2000 10:08:47 -0500 From: Steve Moulton Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a customer who has gotten himself in some hot water by blindly replying to a mailing list rather than a user. He wants me to rewrite the "From:" lines so that rather than reading From: user@dom.ain they read From: [listname] user@dom.ain so that the From: address stands out more and he is less likely to blindly reply. He asserts that listserv can do this. I've been through the FAQ, and, short of making changes to resend, I don't see a way of doing this. . Has anyone dealt with a request like this? . How? Thanks! --- Steve Moulton SNMP Research, Inc voice: +1 865 573 1434 Software Engineer 3001 Kimberlin Heights Rd. fax: +1 865 573 9197 moulton@snmp.com Knoxville, TN 37920-9716 http://www.snmp.com From majordomo-users-owner Tue Feb 22 08:57:12 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA08613; Tue, 22 Feb 2000 08:42:09 -0800 (PST) Received: from herald.colloquium.co.uk (herald.colloquium.co.uk [192.153.153.244]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA08606 for ; Tue, 22 Feb 2000 08:42:02 -0800 (PST) Received: from cyhost.cysoft.net (IDENT:root@cyhost.colloquium.co.uk [192.153.153.192]) by herald.colloquium.co.uk (8.9.3/8.9.3) with ESMTP id QAA21111 for ; Tue, 22 Feb 2000 16:54:46 GMT Received: from cysoft.net (tom.colloquium.co.uk [192.153.153.16]) by cyhost.cysoft.net (8.8.7/8.8.7) with ESMTP id RAA03232 for ; Tue, 22 Feb 2000 17:09:41 GMT Message-ID: <38B2C2C5.B89E66A3@cysoft.net> Date: Tue, 22 Feb 2000 17:09:25 +0000 From: Quietman X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Virtual list domains Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hope someone here can help with this... I recently set up a majordomo list server (version 1.94.5) and it works fine, the problem is when I try to set up virtual domains for lists. Whenever I set up a list on a virtual domain all list items are still going through the primary domain. I'm probably overlooking something simple but I just can't see it. I'm using Redhat 6.1 with kernel 2.2.12, sendmail 8.9.3 and majordomo 1.94.5 Cheers, Tom From majordomo-users-owner Tue Feb 22 10:12:49 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA09691; Tue, 22 Feb 2000 10:03:54 -0800 (PST) Received: from hotmail.com (f58.law8.hotmail.com [216.33.241.58]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id KAA09684 for ; Tue, 22 Feb 2000 10:03:48 -0800 (PST) Received: (qmail 92122 invoked by uid 0); 22 Feb 2000 18:21:46 -0000 Message-ID: <20000222182146.92121.qmail@hotmail.com> Received: from 198.204.133.70 by www.hotmail.com with HTTP; Tue, 22 Feb 2000 10:21:46 PST X-Originating-IP: [198.204.133.70] From: "D B" To: majordomo-users@greatcircle.com Date: Tue, 22 Feb 2000 13:21:46 EST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Greetings all, I have read majordomo documentation (README, NEWLIST files), the FAQ and the 'Managing Mailing Lists' book written by Alan Schwartz. I am looking for an example (code fragment) for using the 'bounce' script. I assume it can be used from a Sendmail alias, but I would like to see an example usage. None of the documentation I have read explicitly shows it's use. Thank you in advance. DB ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From majordomo-users-owner Tue Feb 22 10:42:23 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA10060; Tue, 22 Feb 2000 10:32:27 -0800 (PST) Received: from doberman.cablew.com (doberman.cwusa.com [146.135.27.33]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA10053 for ; Tue, 22 Feb 2000 10:32:21 -0800 (PST) Received: from sts-gy.cwi.cablew.com (tiger.cwi.cablew.com [146.135.107.64]) by doberman.cablew.com (8.9.1/8.9.1) with ESMTP id NAA07295; Tue, 22 Feb 2000 13:50:08 -0500 (EST) Received: from skiblack.com by sts-gy.cwi.cablew.com (8.8.8+Sun/SMI-SVR4) id NAA27160; Tue, 22 Feb 2000 13:49:49 -0500 (EST) Message-ID: <38B2DA4D.686AEE37@skiblack.com> Date: Tue, 22 Feb 2000 13:49:55 -0500 From: Bryan Blackwell Reply-To: bryan@skiblack.com X-Mailer: Mozilla 4.7 (Macintosh; U; PPC) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Steve Moulton CC: majordomo-users@GreatCircle.COM Subject: Re: rewriting "From:" References: <200002221508.KAA22390@aix43.snmp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I believe what you're looking for is: # subject_prefix [word] (undef) # This word will be prefixed to the subject line, if it is not # already in the subject. The text is expanded before being used. # The following expansion tokens are defined: $LIST - the name of # the current list, $SENDER - the sender as taken from the from # line, $VERSION, the version of majordomo. subject_prefix = Steve Moulton wrote: > > I have a customer who has gotten himself in some hot water by > blindly replying to a mailing list rather than a user. He > wants me to rewrite the "From:" lines so that rather than > reading > > From: user@dom.ain > > they read > > From: [listname] user@dom.ain > > so that the From: address stands out more and he is less likely > to blindly reply. He asserts that listserv can do this. > > I've been through the FAQ, and, short of making changes to resend, > I don't see a way of doing this. > > . Has anyone dealt with a request like this? > > . How? > -- _ _ | |_| C o l l e c t i v e |_| | Bryan Blackwell, Consultant |___ ___| | bryan@colltech.com [] technologies [] | Client: Cable & Wireless http://www.colltech.com | From majordomo-users-owner Tue Feb 22 10:56:58 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA10203; Tue, 22 Feb 2000 10:41:02 -0800 (PST) Received: from seymour39.SNMP.COM (seymour39.snmp.com [192.147.142.39]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA10196 for ; Tue, 22 Feb 2000 10:40:56 -0800 (PST) Received: from aix43.snmp.com (aix43.snmp.com [192.147.142.137]) by seymour39.SNMP.COM (8.9.3/m.000221) with ESMTP id NAA06409; Tue, 22 Feb 2000 13:58:52 -0500 (EST) Received: from aix43.snmp.com (LOCALHOST [127.0.0.1]) by aix43.snmp.com (8.9.3/snmpclient.mc-990615) with ESMTP id NAA16320; Tue, 22 Feb 2000 13:58:51 -0500 Message-Id: <200002221858.NAA16320@aix43.snmp.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: bryan@skiblack.com cc: majordomo-users@GreatCircle.COM Subject: Re: rewriting "From:" In-Reply-To: Message from Bryan Blackwell of "Tue, 22 Feb 2000 13:49:55 EST." <38B2DA4D.686AEE37@skiblack.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Feb 2000 13:58:51 -0500 From: Steve Moulton Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Tuesday, February 22 2000, Bryan Blackwell wrote: > I believe what you're looking for is: > > # subject_prefix [word] (undef) > # This word will be prefixed to the subject line, if it is not > # already in the subject. The text is expanded before being used. > # The following expansion tokens are defined: $LIST - the name of > # the current list, $SENDER - the sender as taken from the from > # line, $VERSION, the version of majordomo. This is a neat idea, and I am doing it. What the customer would like is for the "From:" line to be rewritten, and that does not appear to be quite so easy. - Steve > Steve Moulton wrote: > > > > I have a customer who has gotten himself in some hot water by > > blindly replying to a mailing list rather than a user. He > > wants me to rewrite the "From:" lines so that rather than > > reading > > > > From: user@dom.ain > > > > they read > > > > From: [listname] user@dom.ain > > > > so that the From: address stands out more and he is less likely > > to blindly reply. He asserts that listserv can do this. > > > > I've been through the FAQ, and, short of making changes to resend, > > I don't see a way of doing this. > > > > . Has anyone dealt with a request like this? > > > > . How? --- Steve Moulton SNMP Research, Inc voice: +1 865 573 1434 Software Engineer 3001 Kimberlin Heights Rd. fax: +1 865 573 9197 moulton@snmp.com Knoxville, TN 37920-9716 http://www.snmp.com Note: Our area code changed to 865 from 423 in November. If you have trouble reaching us via area code 865, please try the old area code (423) and let us know. Both area codes should work until April. From majordomo-users-owner Tue Feb 22 11:11:25 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA10488; Tue, 22 Feb 2000 11:03:43 -0800 (PST) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA10480 for ; Tue, 22 Feb 2000 11:03:36 -0800 (PST) Received: from ee-nt (eckert@netcom11.netcom.com [199.183.9.111]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id LAA16630; Tue, 22 Feb 2000 11:20:52 -0800 (PST) Message-Id: <3.0.5.32.20000222104944.009cb9e0@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 22 Feb 2000 10:49:44 -0800 To: Steve Moulton From: SRE Subject: Re: rewriting "From:" Cc: majordomo-users@GreatCircle.COM In-Reply-To: <200002221508.KAA22390@aix43.snmp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 10:08 AM 2/22/00 -0500, Steve Moulton wrote: > From: [listname] user@dom.ain >so that the From: address stands out more and he is less likely >to blindly reply. He asserts that listserv can do this. You can change the SUBJECT line to include any prefix you want, but not the FROM line. Some software (Mj2, listserv?) allows you to define a subject prefix for the list, then each user can turn it off in their personal settings. You can probably configure the default subscription options to have it off. From majordomo-users-owner Tue Feb 22 11:26:22 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA10651; Tue, 22 Feb 2000 11:20:17 -0800 (PST) Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA10642 for ; Tue, 22 Feb 2000 11:20:10 -0800 (PST) Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id LAA19418 for ; Tue, 22 Feb 2000 11:36:07 -0800 (PST) Received: from netscape.com ([207.1.145.44]) by judge.mcom.com (Netscape Messaging Server 4.03) with ESMTP id FQCJVJ03.D4G; Tue, 22 Feb 2000 11:38:07 -0800 Message-ID: <38B2E59F.8B512978@netscape.com> Date: Tue, 22 Feb 2000 11:38:07 -0800 From: Sudhakar Chandrasekharan Organization: I didn't do it, nobody saw me do it, no one can prove a thing X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.13 i686) X-Accept-Language: en, fr MIME-Version: 1.0 To: Wade Funk CC: majordomo-users@GreatCircle.COM Subject: Re: Security? References: <38B1ADF3.234BAF0B@globeset.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Wade Funk proclaimed: > Is there a way to provide my internal users information via 'lists' > while making it invisible to external viewers? # advertise [regexp_array] (undef) # If the requestor email address matches one of these regexps, then # the list will be listed in the output of a lists command. Failure # to match any regexp excludes the list from the output. The # regexps under noadvertise override these regexps. advertise << END END Thaths -- "I have two questions for you: How much? and I'll take it." -- Homer J. Simpson Sudhakar C13n http://people.netscape.com/thaths/ Lead Indentured Slave From majordomo-users-owner Tue Feb 22 11:45:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA10622; Tue, 22 Feb 2000 11:16:54 -0800 (PST) Received: from astro.sgsnet.com (astro.sgsnet.com [204.217.154.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA10615 for ; Tue, 22 Feb 2000 11:16:46 -0800 (PST) Received: from sgsnet.com (tiberius.sgsnet.com [204.217.154.30]) by astro.sgsnet.com (8.9.3/8.9.3) with ESMTP id NAA27217 for ; Tue, 22 Feb 2000 13:33:34 -0600 (CST) Message-ID: <38B2E42B.5F744A91@sgsnet.com> Date: Tue, 22 Feb 2000 13:31:55 -0600 From: anna hook Organization: SGS Net, LLC X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo-users@GreatCircle.COM Subject: Fwd: Question about " Invalid'Approved:' header " P.S. Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms4DBB78AA0D780639B666D580" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a cryptographically signed message in MIME format. --------------ms4DBB78AA0D780639B666D580 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit P.S. Here is a copy of my aliases for sendmail: newtest: "|/export/home/majordom/wrapper resend -l newtest -h myhost.mydomain.com newtest-list newtest-list: :include:/export/home/majordom/lists/newtest owner-newtest: anna newtest-owner: anna newtest-request: "|/export/home/majordom/wrapper majordomo -l newtest" newtest-approval: anna First, sorry for being an idiot and sending a 'subscribe message' to majordomo-users. I guess it just shows how frustrated I am. Ok I can't figure out how to send an 'approved' message to a moderated list? I am following the directions... at least I think I am? Here is what I am doing: 1) I compose a message 2) In the body I put the following: Approved: password 3) I send the message 4) It bounces with the message "Invalid 'Approved:' header" 5) I curse at my monitor. I have tried many variations. -I send the message with no lines in between the top of the message and the body, e.g.: Approved: password Majordomo is driving me nuts. -I send it with a space in between: Approved: password Majordomo is driving me nuts. -I put an extra return character at the top of the body: Approved: password Majordomo is driving me nuts. -I do the same and omit the 2nd return charter: Approved: password Majordomo is driving me nuts. I am running majordomo 1.94.5 with a successful clean install. Should I just delete the directory and install 1.94.4? That's about the only thing I haven't done. I have been playing with the listname.config file. I have read the README, the man pages, the list-owner-info, the FAQ etc... I have followed the instruction.. haven't I? In the FAQ 3.10 says that this should work. It says the same thing in the list-owner-info file about BOUNCE messages? This is what I want to do. I want to send a mass mailing to a moderated list. I want the return address to be something that I specify, i.e. not who is sending the message (I have an alias user I want the replies to go to). I haven't even gotten to messing with the 'sender' option in the listname.config file because for the life of me I can't figure out how to send a message with an approval to a moderated list. Please someone... tell me what to read? Point me in the right direction? I don't know where else to look? I have done numerous online searches for majordomo tutorials and error messages and I have read just about everything that's out there. And in advance, if it turns out to be some stupid mistake, my apologies for wasting everyone's time. Thanx. -anna --------------ms4DBB78AA0D780639B666D580 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJ5gYJKoZIhvcNAQcCoIIJ1zCCCdMCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B50wggRnMIID0KADAgECAhA5sjPxPhkrPaIpvmUzD2E5MA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAwMDIxNzAwMDAw MFoXDTAxMDIxNjIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxEjAQBgNVBAMUCUFubmEgSG9vazEeMBwGCSqGSIb3DQEJ ARYPYW5uYUBzZ3NuZXQuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDQcdrFEq3s MJ+/fuq3gU+Wdanqyl60FyQbCk/OYa5S7zoqASm22oPm7zsFbMVvtCRKG4NeTO2y+rBxFBTE VEYtmPwhlOaIHHcoZOTcoi53VmZOExISTC8HGdD30dX3+lHtEo3xlG+QHWLbkAerKOuKaWn0 cukVv8x6iDT+36sq4QIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24u Y29tL2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEApRyTKxTsXTOureTZtzuYHcVZxQNW bzZsuw8zcf65JPb5+by8nrGzM5+8JsS9CMqPHuNWKpQE11XcD/IIABjWMWKNXIBvzKADqb3Z YeItAD3NeDadLLUf1QoVw1TbN6QNH8gqDcy/CbrgtzCXf9WnKZSnxRtS7jxrdgnKDXykI2Ew ggMuMIICl6ADAgECAhEA0nYujRQMPX2yqCVdr+4NdTANBgkqhkiG9w0BAQIFADBfMQswCQYD VQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDEgUHVi bGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNOTgwNTEyMDAwMDAwWhcN MDgwNTEyMjM1OTU5WjCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZl cmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3Np dG9yeS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlT aWduIENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlk YXRlZDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAu1pEigQWu1X9A3qKLZRPFXg2uA1K sm+cVL+86HcqnbnwaLuV2TFBcHqBS7lIE1YtxwjhhEKrwKKSq0RcqkLwgg4C6S/7wju7vskn Cl22sDZCM7VuVIhPh0q/Gdr5FegPh7Yc48zGmo5/aiSS4/zgZbqnsX7vyds3ashKyAkG5JkC AwEAAaN8MHowEQYJYIZIAYb4QgEBBAQDAgEGMEcGA1UdIARAMD4wPAYLYIZIAYb4RQEHAQEw LTArBggrBgEFBQcCARYfd3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQTAPBgNVHRME CDAGAQH/AgEAMAsGA1UdDwQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQCIuDc73dqUNwCtqp/h gQFxHpJqbS/28Z3TymQ43BuYDAeGW4UVag+5SYWklfEXfWe0fy0s3ZpCnsM+tI6q5QsG3vJW Kvozx74Z11NMw73I4xe1pElCY+zCphcPXVgaSTyQXFWjZSAA/Rgg5V+CprGoksVYasGNAzzr w80FopCubjGCAhEwggINAgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO b3QgVmFsaWRhdGVkAhA5sjPxPhkrPaIpvmUzD2E5MAkGBSsOAwIaBQCggYYwGAYJKoZIhvcN AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDAwMjIyMTkzMTU4WjAjBgkqhkiG 9w0BCQQxFgQUWZ3fcvDse2sMWsVP2/oXd8fSlD8wJwYJKoZIhvcNAQkPMRowGDAHBgUrDgMC BzANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgFve/gS2r6e4emKnaCdzwyXXGQA1 9BSeJnJU5ede+pUi7njAK1EcQ1ANVBINKCTSsVZBIB0bemmsqXhVVf8LciQLXP3npd/h5fA2 wFf0vjMfuqlBEu2CK/8k82PmcrvpyVIZGnw6KRrI70M9QgLZ/g+9aA7D1lBdqDQO6g2j4A0U --------------ms4DBB78AA0D780639B666D580-- From majordomo-users-owner Tue Feb 22 12:26:22 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA11352; Tue, 22 Feb 2000 12:20:53 -0800 (PST) Received: from usinter.net (mail.usinter.net [206.171.66.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA11345 for ; Tue, 22 Feb 2000 12:20:45 -0800 (PST) Received: from usinter.net [209.85.130.137] by usinter.net [206.171.66.25] with SMTP (MDaemon.v2.8.7.0.R) for ; Tue, 22 Feb 2000 12:37:36 -0800 Message-ID: <38B2F3C8.CB2E3381@usinter.net> Date: Tue, 22 Feb 2000 12:38:32 -0800 From: "Todd A. Lyons" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo Users Subject: Re: rewriting "From:" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: majordomo-users@greatcircle.com X-Return-Path: cannonball@usinter.net Reply-To: cannonball@usinter.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Steve Moulton wrote: > > I have a customer who has gotten himself in some hot water by > blindly replying to a mailing list rather than a user. He > wants me to rewrite the "From:" lines so that rather than > reading By the sound of it, your reply-to field in your list config file is set to the listname@domain. Alter it to something like [listname] $SENDER > so that the From: address stands out more and he is less likely > to blindly reply. He asserts that listserv can do this. The true answer is that he needs to be less blind. Some people, you just can't tell them anything. -- Blue skies... Cannonball http://www.mrball.net * One ring to rule them all, One ring to find them * * One ring to bring them all, and in the darkness bind them * Sauron From majordomo-users-owner Tue Feb 22 12:41:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA11327; Tue, 22 Feb 2000 12:19:47 -0800 (PST) Received: from usinter.net (mail.usinter.net [206.171.66.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA11320 for ; Tue, 22 Feb 2000 12:19:39 -0800 (PST) Received: from usinter.net [209.85.130.137] by usinter.net [206.171.66.25] with SMTP (MDaemon.v2.8.7.0.R) for ; Tue, 22 Feb 2000 12:37:00 -0800 Message-ID: <38B2F3A4.DC70266B@usinter.net> Date: Tue, 22 Feb 2000 12:37:56 -0800 From: "Todd A. Lyons" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Re: rewriting "From:" References: <200002221508.KAA22390@aix43.snmp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: majordomo-users@GreatCircle.COM X-Return-Path: cannonball@usinter.net Reply-To: cannonball@usinter.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Steve Moulton wrote: > > I have a customer who has gotten himself in some hot water by > blindly replying to a mailing list rather than a user. He > wants me to rewrite the "From:" lines so that rather than > reading By the sound of it, your reply-to field in your list config file is set to the listname@domain. Alter it to something like [listname] $SENDER > so that the From: address stands out more and he is less likely > to blindly reply. He asserts that listserv can do this. The true answer is that he needs to be less blind. Some people, you just can't tell them anything. -- Blue skies... Cannonball http://www.mrball.net * One ring to rule them all, One ring to find them * * One ring to bring them all, and in the darkness bind them * Sauron From majordomo-users-owner Tue Feb 22 13:11:22 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA11700; Tue, 22 Feb 2000 13:00:25 -0800 (PST) Received: from guinness.digisle.net (guinness.digisle.net [167.216.152.33]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA11637 for ; Tue, 22 Feb 2000 12:59:59 -0800 (PST) Received: from visi.com (dhcp-vpn-sf-64-30.digisle.com [172.16.64.30]) by guinness.digisle.net (8.9.3/8.9.3/digisle) with ESMTP id VAA20235 for ; Tue, 22 Feb 2000 21:17:55 GMT Message-ID: <38B2FD01.7B14D3C4@visi.com> Date: Tue, 22 Feb 2000 15:17:53 -0600 From: David Barr X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM Subject: Re: rewriting "From:" References: <200002221508.KAA22390@aix43.snmp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Steve Moulton wrote: > > I have a customer who has gotten himself in some hot water by > blindly replying to a mailing list rather than a user. The correct way to handle is this to not set Reply-To: to the list. In order to reply to the list, he'd have to explicitly use the 'group reply' or 'reply all' function of his mail client. If you don't have Reply-To: pointing to the list and he did say reply-all, then that's his fault and drop it. > He > wants me to rewrite the "From:" lines so that rather than > reading > > From: user@dom.ain > > they read > > From: [listname] user@dom.ain Watch out. You run the risk of generating a syntactically invalid address. > so that the From: address stands out more and he is less likely > to blindly reply. He asserts that listserv can do this. > > I've been through the FAQ, and, short of making changes to resend, > I don't see a way of doing this. > > . Has anyone dealt with a request like this? The first response is to not mess with From:. That's totally evil. --Dave From majordomo-users-owner Tue Feb 22 13:56:28 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA12102; Tue, 22 Feb 2000 13:45:43 -0800 (PST) Received: from smtp.ntrnet.net ([206.66.160.16]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA12091 for ; Tue, 22 Feb 2000 13:45:34 -0800 (PST) Received: from mail.ntrnet.net (mail.ntrnet.net [206.66.160.4]) by smtp.ntrnet.net (Postfix) with ESMTP id 5745C1F010 for ; Tue, 22 Feb 2000 17:03:33 -0500 (EST) Received: from ASARian.org (piglet.asarian.org [208.241.154.83]) by mail.ntrnet.net (Postfix) with ESMTP id 2507676809 for ; Tue, 22 Feb 2000 17:03:30 -0500 (EST) Received: from localhost (fuzzy@localhost) by ASARian.org (8.6.12/8.6.12) with SMTP id RAA04806 for ; Tue, 22 Feb 2000 17:03:27 -0500 Date: Tue, 22 Feb 2000 17:03:25 -0500 (EST) From: Fuzzy To: Majordomo-users List Subject: Re: rewriting "From:" In-Reply-To: <38B2DA4D.686AEE37@skiblack.com> Message-ID: X-No-Archive: yes Organization: ASARian Inc. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk the closest we could come was to cludge the Reply-To: to add the comment field. it seems that while the real syntax doesn't allow a comment field, putting one as shown below, causes the resulting header to appear: (actually, its all on one line line-wrapped to be visable: Reply-To: "Board of Director's list for ASARian Inc." once people reply, thier To: shows up as what was in the Reply-To:. I have not seen a place to add comments on other lines. One could edit the "resend" script to deleted the incoming To: and subsistitute your own with the listname in it. That would require seperate scripts, for each list though. # reply_to [word] () # Put a reply-to header with value into the outgoing # message. If the token $SENDER is used, then the address of the # sender is used as the value of the reply-to header. This is the # value of the reply-to header for digest lists. reply_to = "Board of Director's list for ASARian Inc." # resend_host [word] (undef) # The host name that is appended to all address strings specified # for resend. resend_host = piglet.ASARian.org Fuz On Tue, 22 Feb 2000, Bryan Blackwell wrote: > > I believe what you're looking for is: > > # subject_prefix [word] (undef) > # This word will be prefixed to the subject line, if it is not > # already in the subject. The text is expanded before being used. > # The following expansion tokens are defined: $LIST - the name of > # the current list, $SENDER - the sender as taken from the from > # line, $VERSION, the version of majordomo. > subject_prefix = > > Steve Moulton wrote: > > > > I have a customer who has gotten himself in some hot water by > > blindly replying to a mailing list rather than a user. He > > wants me to rewrite the "From:" lines so that rather than > > reading > > > > From: user@dom.ain > > > > they read > > > > From: [listname] user@dom.ain > > > > so that the From: address stands out more and he is less likely > > to blindly reply. He asserts that listserv can do this. > > > > I've been through the FAQ, and, short of making changes to resend, > > I don't see a way of doing this. > > > > . Has anyone dealt with a request like this? > > > > . How? > > > -- > _ _ | > |_| C o l l e c t i v e |_| | Bryan Blackwell, Consultant > |___ ___| | bryan@colltech.com > [] technologies [] | Client: Cable & Wireless > http://www.colltech.com | > From majordomo-users-owner Tue Feb 22 14:11:29 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA12391; Tue, 22 Feb 2000 14:06:03 -0800 (PST) Received: from chamber.dna.fi (chamber.dna.fi [62.236.155.125]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id OAA12384 for ; Tue, 22 Feb 2000 14:05:56 -0800 (PST) Received: (qmail 9153 invoked by uid 501); 23 Feb 2000 00:23:54 +0200 Date: Wed, 23 Feb 2000 00:23:54 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: Steve Moulton Cc: majordomo-users@GreatCircle.COM Subject: Re: rewriting "From:" Message-ID: <20000223002354.C8942@chamber.dna.fi> Reply-To: Mikko.Hanninen@iki.fi Mail-Followup-To: Steve Moulton , majordomo-users@GreatCircle.COM References: <200002221858.NAA16320@aix43.snmp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.1.4i In-Reply-To: <200002221858.NAA16320@aix43.snmp.com>; from moulton@snmp.com on Tue, Feb 22, 2000 at 01:58:51PM -0500 Organization: None Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Steve Moulton wrote on Tue, 22 Feb 2000: > This is a neat idea, and I am doing it. What the customer would like is for > the "From:" line to be rewritten, and that does not appear to be quite > so easy. Indeed, I don't think it's possible without modifying majordomo. Mikko -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Dyslexia rules KO! From majordomo-users-owner Tue Feb 22 14:43:10 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA12648; Tue, 22 Feb 2000 14:30:16 -0800 (PST) Received: from cmailg4.svr.pol.co.uk (cmailg4.svr.pol.co.uk [195.92.195.174]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA12623 for ; Tue, 22 Feb 2000 14:29:55 -0800 (PST) Received: from modem-36.crixivan.dialup.pol.co.uk ([62.136.87.36] helo=skirza.fsnet.co.uk) by cmailg4.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12NO5w-0001bw-00 for majordomo-users@greatcircle.com; Tue, 22 Feb 2000 22:47:53 +0000 Received: from skirza.fsnet.co.uk (localhost [127.0.0.1]) by skirza.fsnet.co.uk (8.9.3/8.9.3) with ESMTP id WAA01809 for ; Tue, 22 Feb 2000 22:44:54 GMT Message-ID: <38B31166.10644E59@skirza.fsnet.co.uk> Date: Tue, 22 Feb 2000 22:44:54 +0000 From: Kenny Shields Reply-To: kenny@skirza.fsnet.co.uk Organization: Skirza Lobsters X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Re: problem with permisions References: <38B06F4A.7880AE09@mac.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk laura despard wrote: > > i just set up majordomo and am having a proble, i ca nsubscribe to a > list but when i try to send mail to the list, the owner of the > list(owner-family) gets back this: > > The original message was received at Tue, 20 Feb 2001 22:46:24 -0500 > from majordomo@localhost > > ----- The following addresses had permanent fatal errors ----- > family-list > :include:/usr/test/majordomo-1.94.4/lists/family > (expanded from: family-list) > > ----- Transcript of session follows ----- > 550 :include:/usr/test/majordomo-1.94.4/lists/family... Cannot open > /usr/test/majordomo-1.94.4/lists/family: Group writable directory > 554 family-list... aliasing/forwarding loop broken > > any ideas? > > please send responces to edwarddes@mac.com > > thanks! I have the exact same error yet when I run the included install test programme it reports all (including list directory permissions) is well. I can subscribe, unsubscribe, in fact do anything except successfully post to the list. I am running Majordomo on linux (SuSe 6.1) using Webmin to install and configure it. Any help you can give me would be greatly appreciated. -- Cheers, Kenny Shields Home: kenny@skirza.fsnet.co.uk Work: kenny.shields@norscot.co.uk From majordomo-users-owner Tue Feb 22 15:26:07 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA13346; Tue, 22 Feb 2000 15:21:47 -0800 (PST) Received: from astro.sgsnet.com (astro.sgsnet.com [204.217.154.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA13339 for ; Tue, 22 Feb 2000 15:21:38 -0800 (PST) Received: from sgsnet.com (tiberius.sgsnet.com [204.217.154.30]) by astro.sgsnet.com (8.9.3/8.9.3) with ESMTP id RAA04413; Tue, 22 Feb 2000 17:35:04 -0600 (CST) Message-ID: <38B31CC5.D4F7AA01@sgsnet.com> Date: Tue, 22 Feb 2000 17:33:25 -0600 From: anna hook Organization: SGS Net, LLC X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Mikko.Hanninen@iki.fi CC: Majordomo-users@GreatCircle.COM Subject: Re: Question about " Invalid'Approved:' header " P.S. References: <38B2E42B.5F744A91@sgsnet.com> <20000223011833.A9298@chamber.dna.fi> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msFFDB8F1FC5A752012619CE63" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a cryptographically signed message in MIME format. --------------msFFDB8F1FC5A752012619CE63 Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Mikko Hänninen wrote: > > anna hook wrote on Tue, 22 Feb 2000: > > First, sorry for being an idiot and sending a 'subscribe message' to > > majordomo-users. I guess it just shows how frustrated I am. > > We never saw it... (Majordomo at work, I'm sure.) > > > Ok I can't > > figure out how to send an 'approved' message to a moderated list? I am > > following the directions... at least I think I am? > > > > Here is what I am doing: > > 1) I compose a message > > 2) In the body I put the following: > > Approved: password > > 3) I send the message > > 4) It bounces with the message "Invalid 'Approved:' header" > > 5) I curse at my monitor. > > How about you show us an example of the bounce message? (With the > password x'd out or something.) > > > -I send it with a space in between: > > Approved: password > > > > Majordomo is driving me nuts. > > This is the proper format, but I think you should be submitting also > some headers of your own: > > Approved: password > From: anna hook > To: your-list@yourserver.com > Subject: Majordomo is driving me nuts. > > Majordomo is driving me nuts. > > This goes all in the message body, starting right at the top, no return > or anything before. Since you're submitting the headers yourself, you > can put any address you want in the From: line for example... Also, > make sure you're not sending the text out in HTML format or anything > like that, though it doesn't sound like that's the problem. > > Disclaimer: I haven't done manual message approval in a good while since > I always use the handy "approve" script that comes with Majordomo, for > approving bounced messages and also subscribe/unsubscribe requests. > > Mikko Hi Mikko, I realized after I sent the message that I should have sent a copy of what I sent, here goes: Approved: password >From anna Tue Feb 22 09:56:33 2000 Received: mail routing information all on the same line with no return characters breaking up the info From: anna@sgsnet.com Date: Tue, 22 Feb 2000 09:56:32 -0600 (CST) X-Sender: anna@hostname To: newtest@my.domain.com Subject: this is a test Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 42 test test test I also tried it as follows: Approved: password >From anna Tue Feb 22 09:56:33 2000 Received: mail routing information all on the same line with no return characters breaking up the info From: anna@sgsnet.com Date: Tue, 22 Feb 2000 09:56:32 -0600 (CST) X-Sender: anna@hostname To: newtest@my.domain.com Subject: this is a test Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 42 test test test And many other combinations, Approved:password approved:password etc etc etc None work I always get this message: Date: Tue, 22 Feb 2000 14:12:12 -0600 (CST) From: newtest-request@my.domain.com To: anna@sgsnet.com Subject: BOUNCE newtest@my.domain.com: Approval required: Invalid 'Approved:' header I have moderation set to 'yes' and I have the listname.pass file in the right folder with the correct ownership and the passwords match (in the Approved: header and in the listname.pass file). I also have the list restriced with the: restrict_post = /export/home/majordom/restrict_post.txt And I am listed in this file which is also owned by the majordomo user. Any thoughts? Sorry I didn't leave more information. > -- > // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ > // The Corrs list maintainer // net.freak // DALnet IRC operator / > // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / > There is a 70% probability of tomorrow. (Actual weatherman quote, 1988) --------------msFFDB8F1FC5A752012619CE63 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIJ5gYJKoZIhvcNAQcCoIIJ1zCCCdMCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B50wggRnMIID0KADAgECAhA5sjPxPhkrPaIpvmUzD2E5MA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAwMDIxNzAwMDAw MFoXDTAxMDIxNjIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxEjAQBgNVBAMUCUFubmEgSG9vazEeMBwGCSqGSIb3DQEJ ARYPYW5uYUBzZ3NuZXQuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDQcdrFEq3s MJ+/fuq3gU+Wdanqyl60FyQbCk/OYa5S7zoqASm22oPm7zsFbMVvtCRKG4NeTO2y+rBxFBTE VEYtmPwhlOaIHHcoZOTcoi53VmZOExISTC8HGdD30dX3+lHtEo3xlG+QHWLbkAerKOuKaWn0 cukVv8x6iDT+36sq4QIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24u Y29tL2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEApRyTKxTsXTOureTZtzuYHcVZxQNW bzZsuw8zcf65JPb5+by8nrGzM5+8JsS9CMqPHuNWKpQE11XcD/IIABjWMWKNXIBvzKADqb3Z YeItAD3NeDadLLUf1QoVw1TbN6QNH8gqDcy/CbrgtzCXf9WnKZSnxRtS7jxrdgnKDXykI2Ew ggMuMIICl6ADAgECAhEA0nYujRQMPX2yqCVdr+4NdTANBgkqhkiG9w0BAQIFADBfMQswCQYD VQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1BgNVBAsTLkNsYXNzIDEgUHVi bGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNOTgwNTEyMDAwMDAwWhcN MDgwNTEyMjM1OTU5WjCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZl cmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3Np dG9yeS9SUEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlT aWduIENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlk YXRlZDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAu1pEigQWu1X9A3qKLZRPFXg2uA1K sm+cVL+86HcqnbnwaLuV2TFBcHqBS7lIE1YtxwjhhEKrwKKSq0RcqkLwgg4C6S/7wju7vskn Cl22sDZCM7VuVIhPh0q/Gdr5FegPh7Yc48zGmo5/aiSS4/zgZbqnsX7vyds3ashKyAkG5JkC AwEAAaN8MHowEQYJYIZIAYb4QgEBBAQDAgEGMEcGA1UdIARAMD4wPAYLYIZIAYb4RQEHAQEw LTArBggrBgEFBQcCARYfd3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQTAPBgNVHRME CDAGAQH/AgEAMAsGA1UdDwQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQCIuDc73dqUNwCtqp/h gQFxHpJqbS/28Z3TymQ43BuYDAeGW4UVag+5SYWklfEXfWe0fy0s3ZpCnsM+tI6q5QsG3vJW Kvozx74Z11NMw73I4xe1pElCY+zCphcPXVgaSTyQXFWjZSAA/Rgg5V+CprGoksVYasGNAzzr w80FopCubjGCAhEwggINAgEBMIHhMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UE AxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO b3QgVmFsaWRhdGVkAhA5sjPxPhkrPaIpvmUzD2E5MAkGBSsOAwIaBQCggYYwGAYJKoZIhvcN AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDAwMjIyMjMzMzI2WjAjBgkqhkiG 9w0BCQQxFgQU7o7+5BcjwskBSzACdIZMLbLWH3QwJwYJKoZIhvcNAQkPMRowGDAHBgUrDgMC BzANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgGA0L1gW83HNeLX5tRjszRkaIQov fNayAkMnhKawp3OC7IVEfni9gIjWuufebZCt23s6mzpO6aEDKgrx2fD74QVVvbiq4pjByeID BtuwmSTuIb0b/JzPbD8K/kelPqdKBSfMifeCzI78IPyNIDkbdJbslYP4VBNqLEmN1pSC4aX9 --------------msFFDB8F1FC5A752012619CE63-- From majordomo-users-owner Tue Feb 22 15:41:09 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA13403; Tue, 22 Feb 2000 15:28:37 -0800 (PST) Received: from foodog.towery.com (foodog.towery.com [208.16.202.19]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA13396 for ; Tue, 22 Feb 2000 15:28:31 -0800 (PST) Received: from towery.com (hydra.towery.com [208.16.202.29]) by foodog.towery.com (8.9.3/8.9.3) with ESMTP id RAA24584; Tue, 22 Feb 2000 17:46:12 -0600 Message-ID: <38B32099.C3B2A038@towery.com> Date: Tue, 22 Feb 2000 17:49:45 -0600 From: Ernest Mueller X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Quietman CC: majordomo-users@greatcircle.com Subject: Re: Virtual list domains References: <38B2C2C5.B89E66A3@cysoft.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have some Web pages some have found helpful on installing and configuring Majordomo 1.94.4 and making virtual lists work. http://o2.towery.com/~ernestm/admin/majordomo/majordomo.html http://o2.towery.com/~ernestm/admin/majordomo/majorvirt.html Hope this helps Ernest Quietman wrote: > > Hope someone here can help with this... > > I recently set up a majordomo list server (version 1.94.5) and it works > fine, the problem is when I try to set up virtual domains for lists. > > Whenever I set up a list on a virtual domain all list items are still > going through the primary domain. > > I'm probably overlooking something simple but I just can't see it. I'm > using Redhat 6.1 with kernel 2.2.12, sendmail 8.9.3 and majordomo 1.94.5 > > Cheers, > Tom -- Ernest C. Mueller ernestm@towery.com Vice President for Technical Development Phone: (901) 251-7000 Towery Publishing http://www.towery.com From majordomo-users-owner Tue Feb 22 16:41:07 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA13902; Tue, 22 Feb 2000 16:27:43 -0800 (PST) Received: from mail.rdc1.sdca.home.com (ha1.rdc1.sdca.home.com [24.0.3.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA13895 for ; Tue, 22 Feb 2000 16:27:36 -0800 (PST) Received: from cx588769a ([24.4.67.154]) by mail.rdc1.sdca.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <20000223004533.BCZS22732.mail.rdc1.sdca.home.com@cx588769a> for ; Tue, 22 Feb 2000 16:45:33 -0800 Message-ID: <009501bf7d97$4c2fd4c0$9a430418@elcjn1.sdca.home.com> From: "Anthony M. Abate" To: References: <38B06F4A.7880AE09@mac.com> <38B31166.10644E59@skirza.fsnet.co.uk> Subject: Re: problem with permisions Date: Tue, 22 Feb 2000 16:45:35 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Set the permissions of the majordomo root diretory to drwxr-xr-x this should fix it. Did you create a new group for majordomo like majordomo.daemon? If this directory should be a member. Sent: Tuesday, February 22, 2000 2:44 PM Subject: Re: problem with permisions > laura despard wrote: > > > > i just set up majordomo and am having a proble, i ca nsubscribe to a > > list but when i try to send mail to the list, the owner of the > > list(owner-family) gets back this: > > > > The original message was received at Tue, 20 Feb 2001 22:46:24 -0500 > > from majordomo@localhost > > > > ----- The following addresses had permanent fatal errors ----- > > family-list > > :include:/usr/test/majordomo-1.94.4/lists/family > > (expanded from: family-list) > > > > ----- Transcript of session follows ----- > > 550 :include:/usr/test/majordomo-1.94.4/lists/family... Cannot open > > /usr/test/majordomo-1.94.4/lists/family: Group writable directory > > 554 family-list... aliasing/forwarding loop broken > > > > any ideas? > > > > please send responces to edwarddes@mac.com > > > > thanks! > > I have the exact same error yet when I run the included install test > programme it reports all (including list directory permissions) is well. > I can subscribe, unsubscribe, in > fact do anything except successfully post to the list. > > I am running Majordomo on linux (SuSe 6.1) using Webmin to install and > configure it. > > Any help you can give me would be greatly appreciated. > > -- > Cheers, > Kenny Shields > > Home: kenny@skirza.fsnet.co.uk > Work: kenny.shields@norscot.co.uk From majordomo-users-owner Tue Feb 22 19:00:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA15874; Tue, 22 Feb 2000 18:38:02 -0800 (PST) Received: from hotmail.com (f36.law8.hotmail.com [216.33.241.36]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id SAA15867 for ; Tue, 22 Feb 2000 18:37:51 -0800 (PST) Received: (qmail 45561 invoked by uid 0); 23 Feb 2000 02:55:52 -0000 Message-ID: <20000223025552.45560.qmail@hotmail.com> Received: from 168.143.28.212 by www.hotmail.com with HTTP; Tue, 22 Feb 2000 18:55:52 PST X-Originating-IP: [168.143.28.212] From: "D B" To: majordomo-users@greatcircle.com Subject: example of running the 'bounce' script Date: Tue, 22 Feb 2000 21:55:52 EST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Greetings all, I have read majordomo documentation (README, NEWLIST files), the FAQ and the 'Managing Mailing Lists' book written by Alan Schwartz. I am looking for an example (code fragment) for using the 'bounce' script. I assume it can be used from a Sendmail alias, but I would like to see an example usage. None of the documentation I have read explicitly shows it's use. Thank you in advance. DB ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From majordomo-users-owner Tue Feb 22 19:12:29 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA15006; Tue, 22 Feb 2000 17:27:52 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id RAA14995 for majordomo-users@greatcircle.com; Tue, 22 Feb 2000 17:27:49 -0800 (PST) Received: from skynet.usb.ve (skynet.usb.ve [159.90.200.7]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA22059 for ; Mon, 21 Feb 2000 10:09:33 -0800 (PST) Received: from altair.usb.ve (altair.usb.ve [159.90.200.8]) by skynet.usb.ve (Postfix) with SMTP id 1DF01E20 for ; Mon, 21 Feb 2000 14:27:25 -0400 (GMT-0400) Date: Mon, 21 Feb 2000 14:27:26 -0400 (GMT-0400) From: "Anabel Fraga Vazquez (Administradora de Sistemas Unix)" To: Majordomo-Users@GreatCircle.COM Subject: Majordomo 1.94.5 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi ! We are using Majordomo 1.94.5, I would like to know, what's the meaning of the new function for detect some attachments? Because we need to detect and reject e-mails with attachments in order to send them to the moderator of the list. Or someone knows how to do that?. Thanks in advance for your help. Anabel Fraga From majordomo-users-owner Tue Feb 22 19:23:35 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA14975; Tue, 22 Feb 2000 17:27:35 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id RAA14963 for majordomo-users@greatcircle.com; Tue, 22 Feb 2000 17:27:31 -0800 (PST) Received: from www.ngonet.be ([195.95.39.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA18717 for ; Mon, 21 Feb 2000 05:21:03 -0800 (PST) Received: from koekie2 (u212-239-133-193.dialup.planetinternet.be [212.239.133.193]) by www.ngonet.be (8.9.3/8.9.3) with ESMTP id OAA29831 for ; Mon, 21 Feb 2000 14:37:48 +0100 Message-Id: <4.2.0.58.20000221143504.00a77da0@mail.ngonet.be> X-Sender: pieter@mail.ngonet.be X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 21 Feb 2000 14:38:42 +0100 To: majordomo-users@greatcircle.com From: Pieter Sellenslagh Subject: formated mail to moderated lists Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I know formated mail is not ok, but one of our clients wants to use it on a= =20 moderated list. This doesn't work because the approved line is no longer the first line in= =20 with formated mail. Is there a way arround this. The only suggestion i found in the faq was to add a header to your mail.=20 Which emailclients allow this sort of action? Pieter Sellenslagh Co=F6rdinator ************* Ngonet, Netwerk van Vlaamse NGO's http://www.ngonet.be - info@ngonet.be p/a NCOS, Vlasfabriekstraat 11, 1060 Brussel di en vrij: 02/536.19.14 ma, woe, do: 09/344.54.83 GSM: 0476/89.14.22 fax: 02/536.19.01 ************* From majordomo-users-owner Tue Feb 22 19:30:40 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA14960; Tue, 22 Feb 2000 17:27:26 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id RAA14950 for majordomo-users@greatcircle.com; Tue, 22 Feb 2000 17:27:24 -0800 (PST) Received: from tirad.internal.iphil.net (tirad.internal.iphil.net [203.176.9.125]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA18576 for ; Mon, 21 Feb 2000 05:08:12 -0800 (PST) Received: from localhost (gmg@localhost) by tirad.internal.iphil.net (8.9.3/8.9.3) with ESMTP id VAA01526 for ; Mon, 21 Feb 2000 21:25:55 +0800 Date: Mon, 21 Feb 2000 21:25:55 +0800 (PHT) From: "Grace M. Garcia" To: majordomo-users@greatcircle.com Subject: HELP!!! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk majordomo version: majordomo-1.94.5 perl version: per 5.004m4 OS and version: Red hat Linux release 5.2/ kernel 2.0.36 mailer ans version: sendmail 8.8.7 PROBLEM: 1. When I susbscribe to the maling list I created, even if I set the mailinglist.config to be auto+confirm, it doesn't send confirmation note, it just sends the following: Subject: Majordomo Results >>>>> subscribe [mailinglist name] Then when I check the cd /lists for the mailinglist my email add was not added. 2. when i checked the /var/log/maillog this error appears: DSN: unknown mailer error 9 3. when I manually run, ./wrapper majordomo, the following appears: Susbtitution loop @ /home/majordomo/majordomo.pl line 122, <> chunk 1 Please be warned that I don't have background with perl programming. I desperately need help. Please reply soon! Thanks! Grace M. Garcia Operations Engineer Iphil Communications Network Inc. "A well-timed silence is more eloquent than words." -odb From majordomo-users-owner Tue Feb 22 20:15:00 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id UAA16908; Tue, 22 Feb 2000 20:07:05 -0800 (PST) Received: from dsl-207-105-45-243.hollywood.relaypoint.net (dsl-207-105-45-243.hollywood.relaypoint.net [207.105.45.243]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA16901 for ; Tue, 22 Feb 2000 20:06:58 -0800 (PST) Received: from pajamian.dhs.org (WLA12-46.WLA.Access1.net [63.192.91.103]) by dsl-207-105-45-243.hollywood.relaypoint.net (8.9.3/8.9.3) with ESMTP id UAA09970 for ; Tue, 22 Feb 2000 20:33:19 -0800 Message-ID: <38B36259.6E367EE2@pajamian.dhs.org> Date: Tue, 22 Feb 2000 20:30:17 -0800 From: Peter Ajamian X-Mailer: Mozilla 4.7 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 CC: Majordomo-users@GreatCircle.COM Subject: Re: Fwd: Question about " Invalid'Approved:' header " P.S. References: <38B2E42B.5F744A91@sgsnet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk anna hook wrote: > Here is what I am doing: > 1) I compose a message > 2) In the body I put the following: > Approved: password > 3) I send the message > 4) It bounces with the message "Invalid 'Approved:' header" > 5) I curse at my monitor. This is what I see when I look at the raw text of your message to this list... > Precedence: bulk > Status: O > X-Mozilla-Status: 8001 > X-Mozilla-Status2: 00000000 > X-UIDL: 38aa17300000012c > > This is a cryptographically signed message in MIME format. > > --------------ms4DBB78AA0D780639B666D580 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > > P.S. > Here is a copy of my aliases for sendmail: > newtest: "|/export/home/majordom/wrapper resend -l newtest -h > myhost.mydomain.com newtest-list > newtest-list: :include:/export/home/majordom/lists/newtest This is just a guess, but if you're trying to approve the messages with the cryptographic headers then it can easily cause the problems you are getting. Try sending out the message in plain text without signing it. Regards, Peter Disclaimer: I am still relatively new to Majordomo myself, take my advice for what it is, the advice of a fellow user, and not that of a professional. From majordomo-users-owner Wed Feb 23 05:27:50 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA24761; Wed, 23 Feb 2000 05:16:41 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA24754 for ; Wed, 23 Feb 2000 05:16:35 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id IAA11794; Wed, 23 Feb 2000 08:33:48 -0500 (EST) Date: Wed, 23 Feb 2000 08:33:48 -0500 (EST) From: "Bill Casti (System Admin)" To: "Anabel Fraga Vazquez (Administradora de Sistemas Unix)" cc: Majordomo-Users@GreatCircle.COM Subject: Re: Majordomo 1.94.5 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I just use the taboo_headers parameter in the majordomo.cf file, eg. /^Parts/Attachments:\*.exe/i /^Parts/Attachments:\*.bat/i /^Parts/Attachments:\*.pdf/i /^Parts/Attachments:\*.com/i Bill On Mon, 21 Feb 2000, Anabel Fraga Vazquez (Administradora de Sistemas Unix) wrote: > > Hi ! > We are using Majordomo 1.94.5, I would like to know, what's the > meaning of the new function for detect some attachments? Because we need > to detect and reject e-mails with attachments in order to send them to > the moderator of the list. Or someone knows how to do that?. > Thanks in advance for your help. > > Anabel Fraga > > > From majordomo-users-owner Wed Feb 23 05:42:45 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA24774; Wed, 23 Feb 2000 05:18:22 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA24766 for ; Wed, 23 Feb 2000 05:18:16 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id IAA11799; Wed, 23 Feb 2000 08:34:57 -0500 (EST) Date: Wed, 23 Feb 2000 08:34:57 -0500 (EST) From: "Bill Casti (System Admin)" To: Peter Ajamian cc: Majordomo-users@GreatCircle.COM Subject: Re: Fwd: Question about " Invalid'Approved:' header " P.S. In-Reply-To: <38B36259.6E367EE2@pajamian.dhs.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk There can't be ANY blank lines between the "Approved:" header and the first line of the post. If there's any blanks, the post will be bounced. On Tue, 22 Feb 2000, Peter Ajamian wrote: > anna hook wrote: > > Here is what I am doing: > > 1) I compose a message > > 2) In the body I put the following: > > Approved: password > > 3) I send the message > > 4) It bounces with the message "Invalid 'Approved:' header" > > 5) I curse at my monitor. > > This is what I see when I look at the raw text of your message to this > list... > > > Precedence: bulk > > Status: O > > X-Mozilla-Status: 8001 > > X-Mozilla-Status2: 00000000 > > X-UIDL: 38aa17300000012c > > > > This is a cryptographically signed message in MIME format. > > > > --------------ms4DBB78AA0D780639B666D580 > > Content-Type: text/plain; charset=us-ascii > > Content-Transfer-Encoding: 7bit > > > > > > P.S. > > Here is a copy of my aliases for sendmail: > > newtest: "|/export/home/majordom/wrapper resend -l newtest -h > > myhost.mydomain.com newtest-list > > newtest-list: :include:/export/home/majordom/lists/newtest > > This is just a guess, but if you're trying to approve the messages with > the cryptographic headers then it can easily cause the problems you are > getting. Try sending out the message in plain text without signing it. > > Regards, Peter > > Disclaimer: I am still relatively new to Majordomo myself, take my > advice for what it is, the advice of a fellow user, and not that of a > professional. > From majordomo-users-owner Wed Feb 23 06:41:51 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA25453; Wed, 23 Feb 2000 06:28:40 -0800 (PST) Received: from conecta.mgconecta.com.br (conecta.mgconecta.com.br [200.238.205.101]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA25446 for ; Wed, 23 Feb 2000 06:28:31 -0800 (PST) Received: from localhost.localdomain (IDENT:root@line019M [200.238.205.29]) by conecta.mgconecta.com.br (8.9.3/8.9.3) with SMTP id MAA14685; Wed, 23 Feb 2000 12:46:41 -0300 (EST) From: mendes Organization: Working at home To: "Anthony M. Abate" Subject: Problems with permission Date: Wed, 23 Feb 2000 12:50:53 -0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: majordomo-users@GreatCircle.COM MIME-Version: 1.0 Message-Id: <00022312525702.00762@localhost.localdomain> Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello Sorry for bothering you like that but I've got the same problems although my /us/lib/majordomo is set as: [root@angel majordomo]# ls -ld drwxr-xr-x 8 majordom daemon 4096 Feb 23 02:24 . Why can't post to the list? Thanks a lot for your help. Regards Eduardo From majordomo-users-owner Wed Feb 23 06:58:54 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA25477; Wed, 23 Feb 2000 06:30:24 -0800 (PST) Received: from mail1.bna.bellsouth.net (mail1.bna.bellsouth.net [205.152.150.13]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA25468 for ; Wed, 23 Feb 2000 06:30:17 -0800 (PST) Received: from default (adsl-78-216-231.rdu.bellsouth.net [216.78.216.231]) by mail1.bna.bellsouth.net (3.3.5alt/0.75.2) with SMTP id JAA29235 for ; Wed, 23 Feb 2000 09:48:28 -0500 (EST) Message-Id: X-Sender: 5martin@mail.rdu.bellsouth.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 23 Feb 2000 09:49:00 -0500 To: Majordomo-Users@greatcircle.com From: Allison & Rick Martin <5martin@bellsouth.net> Subject: how to use taboo? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm sorry but I am not that familiar with perl. I checked the archives but could use a little assistance. What is the exact syntax for the config list to set a word to taboo? Is it something like: taboo_body =/\bnaughtyword\b/i << END Also do I need to include end, and to do this line for upper and lowercase? Allison Martin 5martin@bellsouth.net From majordomo-users-owner Wed Feb 23 09:41:18 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA27590; Wed, 23 Feb 2000 09:35:40 -0800 (PST) Received: from chamber.dna.fi (chamber.dna.fi [62.236.155.125]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id JAA27578 for ; Wed, 23 Feb 2000 09:35:31 -0800 (PST) Received: (qmail 11424 invoked by uid 501); 23 Feb 2000 19:53:37 +0200 Date: Wed, 23 Feb 2000 19:53:37 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: Allison & Rick Martin <5martin@bellsouth.net> Cc: Majordomo-Users@GreatCircle.COM Subject: Re: how to use taboo? Message-ID: <20000223195337.A11389@chamber.dna.fi> Reply-To: Mikko.Hanninen@iki.fi Mail-Followup-To: Allison & Rick Martin <5martin@bellsouth.net>, Majordomo-Users@GreatCircle.COM References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.1.4i In-Reply-To: ; from 5martin@bellsouth.net on Wed, Feb 23, 2000 at 09:49:00AM -0500 Organization: None Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Allison & Rick Martin <5martin@bellsouth.net> wrote on Wed, 23 Feb 2000: > What is the exact syntax for the config list to set a word to taboo? Is it > something like: > > taboo_body =/\bnaughtyword\b/i > << END Something close to that, yes: taboo_body << END /\bnaughtyword\b/i END Add any other words between the taboo_body and END lines. > Also do I need to include end, and to do this line for upper and lowercase? Yes, the i at the end tells that the match should be case-insensitive. If you leave out the i (eg. "/\bnaughtyword\b/") then it's case-sensitive. Hope this helps, Mikko -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / It really is just the little things that bug a person. From majordomo-users-owner Wed Feb 23 09:56:52 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA27788; Wed, 23 Feb 2000 09:51:31 -0800 (PST) Received: from rottweiler.cwusa.com (rottweiler-dmz.cwusa.com [146.135.88.50]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA27781 for ; Wed, 23 Feb 2000 09:51:25 -0800 (PST) Received: from sts-gy.cwi.cablew.com (tiger.cwusa.com [146.135.107.64]) by rottweiler.cwusa.com (8.9.1/8.9.1) with ESMTP id NAA15896; Wed, 23 Feb 2000 13:09:32 -0500 (EST) Received: from skiblack.com by sts-gy.cwi.cablew.com (8.8.8+Sun/SMI-SVR4) id NAA19289; Wed, 23 Feb 2000 13:09:31 -0500 (EST) Message-ID: <38B4225B.581454C@skiblack.com> Date: Wed, 23 Feb 2000 13:09:36 -0500 From: Bryan Blackwell Reply-To: bryan@skiblack.com X-Mailer: Mozilla 4.7 (Macintosh; U; PPC) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Allison & Rick Martin <5martin@bellsouth.net> CC: Majordomo-Users@GreatCircle.COM Subject: Re: how to use taboo? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Here's what I use for body and header, blocks attachments, MIME, HTML, etc: taboo_body << END /^Content-Type: text\/html/i /^Content-Type: application/i /^Content-Disposition: attachment/i /^Content-transfer-encoding: base64/i /^begin [0-9][0-9][0-9]/ /begin 6\d\d winmail.dat/i /make money fast/i /octet-stream/i END taboo_headers << END /^Content-Type: multipart/mixed;/i /^Content-Type: multipart\/alternative;/i /^Content-Type: multipart\/signed;/i /^Content-Type: message\/partial/i /^Content-Type:.*text\/html/i /^Content-Transfer-Encoding: base64/i END -- _ _ | |_| C o l l e c t i v e |_| | Bryan Blackwell, Consultant |___ ___| | bryan@colltech.com [] technologies [] | Client: Cable & Wireless http://www.colltech.com | From majordomo-users-owner Wed Feb 23 10:26:17 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA28005; Wed, 23 Feb 2000 10:10:20 -0800 (PST) Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA27996 for ; Wed, 23 Feb 2000 10:10:10 -0800 (PST) Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id KAA08022 for ; Wed, 23 Feb 2000 10:26:16 -0800 (PST) Received: from netscape.com ([207.1.145.44]) by judge.mcom.com (Netscape Messaging Server 4.03) with ESMTP id FQEAYU01.JBN; Wed, 23 Feb 2000 10:20:54 -0800 Message-ID: <38B42506.C839822@netscape.com> Date: Wed, 23 Feb 2000 10:20:54 -0800 From: Sudhakar Chandrasekharan Organization: I didn't do it, nobody saw me do it, no one can prove a thing X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.13 i686) X-Accept-Language: en, fr MIME-Version: 1.0 To: D B CC: majordomo-users@GreatCircle.COM Subject: Re: example of running the 'bounce' script References: <20000223025552.45560.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk D B proclaimed: > I am looking for an example (code fragment) for using the 'bounce' script. I > assume it can be used from a Sendmail alias, but I would like to see an > example usage. http://www.greatcircle.com/majordomo/majordomo-faq.html#3.2 The only thing that you need to do in /etc/aliases is add the entries (just like you'd do for any newly created mailing list) for the bounces list. Thaths -- "I have two questions for you: How much? and I'll take it." -- Homer J. Simpson Sudhakar C13n http://people.netscape.com/thaths/ Lead Indentured Slave From majordomo-users-owner Wed Feb 23 11:41:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA28796; Wed, 23 Feb 2000 11:26:41 -0800 (PST) Received: from surf.monterey.k12.ca.us (surf.monterey.k12.ca.us [205.155.53.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA28789 for ; Wed, 23 Feb 2000 11:26:33 -0800 (PST) Received: from stingray.pacbell.net (adsl-63-193-160-94.dsl.lsan03.pacbell.net [63.193.160.94]) by surf.monterey.k12.ca.us (Pro-8.9.3/8.9.3) with SMTP id LAA00907 for ; Wed, 23 Feb 2000 11:40:09 -0800 (PST) From: David Stihler Date: Wed, 23 Feb 2000 19:44:09 GMT Message-ID: <20000223.19440973@stingray.pacbell.net> Subject: Permission Probelms To: majordomo-users@greatcircle.com X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.1; Win32) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Well: I had majordomo installed last year successfully with several=20 lists going but it was a victim of Y2K reloads. Now I'm starting over=20= with the error below: Does anyone have any ideas? Also, for a normal=20= list would it be possible to forward the aliases which are considered=20= standard when not using digests or anything fancy. Thanks. :include:/usr/local/majordomo/lists/test (expanded from: ) ----- Transcript of session follows ----- 550 :include:/usr/local/majordomo/lists/test... Cannot open=20 /usr/local/majordomo/lists/test: Group writable directory 554 ... aliasing/forwarding loop broken From majordomo-users-owner Wed Feb 23 11:56:20 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA28987; Wed, 23 Feb 2000 11:43:21 -0800 (PST) Received: from msic.dia.mil ([136.205.227.211]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA28980 for ; Wed, 23 Feb 2000 11:43:15 -0800 (PST) Received: from [136.205.227.85] (HELO msic.dia.mil) by msic.dia.mil (CommuniGate Pro SMTP 3.2.3) with ESMTP id 511782 for Majordomo-users@GreatCircle.COM; Wed, 23 Feb 2000 14:01:59 -0600 Message-ID: <38B43CA7.BCC7FB29@msic.dia.mil> Date: Wed, 23 Feb 2000 14:01:43 -0600 From: Allan Newsome Reply-To: allan@msic.dia.mil X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-US MIME-Version: 1.0 To: Majordomo Users Mailing list Subject: Re: Fwd: Question about " Invalid'Approved:' header " P.S. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've had that error when I typed in "APPROVED: password " with a "space" after the password. I have to make sure to hit return right after the password. Took a few times to catch this one. Allan Newsome The Andy Griffith Show Rerun Watchers Club http://mayberry.com/tagsrwc/ "Bill Casti (System Admin)" wrote: > > There can't be ANY blank lines between the "Approved:" header and the > first line of the post. If there's any blanks, the post will be bounced. > From majordomo-users-owner Wed Feb 23 12:11:50 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA28996; Wed, 23 Feb 2000 11:44:42 -0800 (PST) Received: from lccpdxm1.dms.usace.army.mil (lccpdxm1.dms.usace.army.mil [137.161.250.20]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA28989 for ; Wed, 23 Feb 2000 11:44:35 -0800 (PST) Received: by lccpdxm1.dms.usace.army.mil with Internet Mail Service (5.5.2448.0) id ; Wed, 23 Feb 2000 12:02:38 -0800 Message-ID: <0A4857C61983D3119E8400508B1377EF07FAC5@lccpdxm1.dms.usace.army.mil> From: "Wilson, Sue LCC" To: Majordomo-users@GreatCircle.COM Subject: Newbie Question Date: Wed, 23 Feb 2000 12:02:37 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF7E38.EE6BB92E" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF7E38.EE6BB92E Content-Type: text/plain; charset="iso-8859-1" I am new to Installing MajorDomo and I cannot get the wrapper to work. I have never done a makefile or wrapper before sooo...any help would be appreciated. Thanks in advance. I am trying to install Majordomo Version 1.94.5 on a SunSolaris 2.5 system. When I do " make wrapper" this is what I get: cc -DBIN=\"/export/opt/majordomo-1.94.5\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/export/opt/majordomo-1.94.5\" -DSHELL=\"SHELL=/bin/sh\" -DMAJORDOMO_CF=\"MAJORDOMO_CF=/export/opt/majordomo-1.94.5/majordomo.cf\" -DPOSIX_UID=501 -DPOSIX_GID=501 -o wrapper wrapper.c /usr/ucb/cc: language optional software package not installed *** Error code 1 make: Fatal error: Command failed for target `wrapper' ------_=_NextPart_001_01BF7E38.EE6BB92E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Newbie Question

I am new to Installing MajorDomo and I cannot get the = wrapper to work. I have never done a makefile or wrapper before = sooo...any help would be appreciated.  Thanks in = advance.

I am trying to install Majordomo Version 1.94.5 on a = SunSolaris 2.5 system.


When I do " make wrapper" this is what I = get:
cc  = -DBIN=3D\"/export/opt/majordomo-1.94.5\" = -DPATH=3D\"PATH=3D/bin:/usr/bin:/usr/ucb\"  = -DHOME=3D\"HOME=3D/export/opt/majordomo-1.94.5\" = -DSHELL=3D\"SHELL=3D/bin/sh\"  = -DMAJORDOMO_CF=3D\"MAJORDOMO_CF=3D/export/opt/majordomo-1.94.5/majo= rdomo.cf\"       -DPOSIX_UID=3D501 = -DPOSIX_GID=3D501 -o wrapper wrapper.c

/usr/ucb/cc:  language optional software package = not installed
*** Error code 1
make: Fatal error: Command failed for target = `wrapper'

------_=_NextPart_001_01BF7E38.EE6BB92E-- From majordomo-users-owner Wed Feb 23 13:58:04 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA00594; Wed, 23 Feb 2000 13:51:25 -0800 (PST) Received: from conecta.mgconecta.com.br (conecta.mgconecta.com.br [200.238.205.101]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA00587 for ; Wed, 23 Feb 2000 13:51:14 -0800 (PST) Received: from localhost.localdomain (IDENT:root@line042M [200.238.205.52]) by conecta.mgconecta.com.br (8.9.3/8.9.3) with SMTP id UAA09357 for ; Wed, 23 Feb 2000 20:09:42 -0300 (EST) From: mendes Organization: Working at home To: majordomo-users@GreatCircle.COM Subject: It doesn't matter what I do, majordomo won't work ..... Date: Wed, 23 Feb 2000 20:11:06 -0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <0002232015580C.00762@localhost.localdomain> Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello I sent some messages to the list asking about the permissions. I tried everything that was said. Unfortunately majordomo refuses to work and just fills my maibox with The original message was received at Wed, 23 Feb 2000 17:03:15 -0300from majordomo@localhost ----- The following addresses had permanent fatal errors ----- iniciacao-list :include:/usr/lib/majordomo/lists/iniciacao (expanded from: iniciacao-list) ----- Transcript of session follows ----- 550 :include:/usr/lib/majordomo/lists/iniciacao... Cannot open /usr/lib/majordomo/lists/iniciacao: Group writable directory 554 iniciacao-list... aliasing/forwarding loop broken What can I do to sort this out? Thanks a lot. Eduardo. PS. These are my file permissions: [root@angel majordomo]# ls -l total 312 drwxr-xr-x 5 majordom daemon 4096 Feb 22 14:02 Desktop -rw-rw-r-- 1 majordom daemon 2663 Feb 23 02:24 Log drwxr-xr-x 2 majordom daemon 4096 Feb 22 14:16 Tools -rwxr-xr-x 1 majordom daemon 5267 Feb 22 14:15 archive2.pl drwxrwxr-x 2 majordom daemon 4096 Feb 23 17:00 archives drwxr-xr-x 2 majordom daemon 4096 Feb 22 14:09 bin -rwxr-xr-x 1 majordom daemon 2795 Feb 22 14:15 bounce-remind -rwxr-xr-x 1 majordom daemon 10671 Feb 22 14:15 config-test -rwxr-xr-x 1 majordom daemon 51130 Feb 22 14:15 config_parse.pl -rwxr-xr-x 1 majordom daemon 14201 Feb 22 14:15 digest drwxrwxr-x 2 majordom daemon 4096 Feb 23 17:00 digests drwxrwxr-x 2 majordom daemon 4096 Feb 23 14:53 lists -rwxr-xr-x 1 majordom daemon 62511 Feb 22 14:15 majordomo -rw-r--r-- 1 majordom daemon 107 Feb 22 17:57 majordomo.aliases -rwxr-x--- 1 majordom daemon 0 Feb 22 17:59 majordomo.aliases.db -rw-r--r-- 1 majordom daemon 10471 Feb 22 14:16 majordomo.cf -rwxr-xr-x 1 majordom daemon 24381 Feb 22 14:15 majordomo.pl -rwxr-xr-x 1 majordom daemon 137 Feb 22 14:15 majordomo_version.pl drwxr-xr-x 4 majordom daemon 4096 Feb 22 14:16 man -rwxr-xr-x 1 majordom daemon 3791 Feb 22 14:15 request-answer -rwxr-xr-x 1 majordom daemon 29919 Feb 22 14:15 resend -rw-r--r-- 1 majordom daemon 10462 Feb 22 14:16 sample.cf -rwxr-xr-x 1 majordom daemon 8060 Feb 22 14:15 shlock.pl -rwsr-xr-x 1 root daemon 14826 Feb 22 14:16 wrapper From majordomo-users-owner Wed Feb 23 15:12:33 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01542; Wed, 23 Feb 2000 14:36:17 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA01520 for majordomo-users@greatcircle.com; Wed, 23 Feb 2000 14:36:10 -0800 (PST) Received: from offworld.tca.net (offworld.tca.net [208.162.121.253]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA16552 for ; Tue, 22 Feb 2000 19:40:14 -0800 (PST) Received: (from cmenzel@localhost) by offworld.tca.net (8.9.3/8.9.3) id VAA12294; Tue, 22 Feb 2000 21:58:15 -0600 Date: Tue, 22 Feb 2000 21:58:15 -0600 From: Chris Menzel To: majordomo-users@greatcircle.com Subject: sendmail problem solved Message-ID: <20000222215815.F1584@offworld.tca.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Sent off my request for help a bit too soon. The right keyword search on dejanews pointed me to info that eventually led me to section 3, Question 3.34 of the sendmail FAQ (http://www.sendmail.org/faq/section3.html). The suggestion there solved my problem. This is a problem arising out of tighter security features in sendmail 8.9. Chris Menzel From majordomo-users-owner Wed Feb 23 15:27:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01432; Wed, 23 Feb 2000 14:35:18 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA01422 for majordomo-users@greatcircle.com; Wed, 23 Feb 2000 14:35:15 -0800 (PST) Received: from conecta.mgconecta.com.br (conecta.mgconecta.com.br [200.238.205.101]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA10818 for ; Tue, 22 Feb 2000 11:33:07 -0800 (PST) Received: from localhost.localdomain (IDENT:root@line027M [200.238.205.37]) by conecta.mgconecta.com.br (8.9.3/8.9.3) with SMTP id RAA24365 for ; Tue, 22 Feb 2000 17:51:35 -0300 (EST) From: mendes Organization: Working at home To: Majordomo-Users@GreatCircle.COM Subject: Why majordomo replies email as majordomo@ether? Date: Tue, 22 Feb 2000 17:55:51 -0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00022217571302.03860@localhost.localdomain> Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello I am newbie and although majordomo seems to be running I noticed that majordomo retunrs all message as majordomo@ether instead of majordomo@angel.funrei.br. Why is that? Thanks a lot Eduardo From majordomo-users-owner Wed Feb 23 15:42:36 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01543; Wed, 23 Feb 2000 14:36:21 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA01533 for majordomo-users@greatcircle.com; Wed, 23 Feb 2000 14:36:14 -0800 (PST) Received: from cartman.uwec.edu (cartman.uwec.edu [137.28.1.65]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id XAA18243 for ; Tue, 22 Feb 2000 23:03:00 -0800 (PST) From: KERRAA@uwec.edu Received: by cartman.uwec.edu with Internet Mail Service (5.5.2650.21) id ; Wed, 23 Feb 2000 01:21:53 -0600 Message-ID: <3DD3BED8DB4DD311B0EE0020484050DC65D510@kyle.uwec.edu> To: majordomo-users@greatcircle.com Subject: FW: Returned mail: Service unavailable Date: Wed, 23 Feb 2000 01:22:00 -0600 X-Mailer: Internet Mail Service (5.5.2650.21) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The following is an error that I get when I try to send a message to majordomo I am using Red Hat 6.1 any help would be greatly appreciated. ----- The following addresses had permanent fatal errors ----- "|/home/majordomo/wrapper majordomo" (expanded from: majordomo) ----- Transcript of session follows ----- sh: wrapper not available for sendmail programs 554 "|/home/majordomo/wrapper majordomo"... Service unavailable From majordomo-users-owner Wed Feb 23 15:59:16 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01724; Wed, 23 Feb 2000 14:48:54 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA01717 for ; Wed, 23 Feb 2000 14:48:48 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id SAA18556; Wed, 23 Feb 2000 18:05:39 -0500 (EST) Date: Wed, 23 Feb 2000 18:05:39 -0500 (EST) From: "Bill Casti (System Admin)" To: mendes cc: "Anthony M. Abate" , majordomo-users@GreatCircle.COM Subject: Re: Problems with permission In-Reply-To: <00022312525702.00762@localhost.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Change the permissions to 775, not 755. Bill On Wed, 23 Feb 2000, mendes wrote: > Hello > Sorry for bothering you like that but I've got the same problems > although my /us/lib/majordomo is set as: > > [root@angel majordomo]# ls -ld > drwxr-xr-x 8 majordom daemon 4096 Feb 23 02:24 . > > Why can't post to the list? > > > Thanks a lot for your help. > > Regards > > Eduardo > From majordomo-users-owner Wed Feb 23 16:10:23 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01507; Wed, 23 Feb 2000 14:35:58 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA01495 for majordomo-users@greatcircle.com; Wed, 23 Feb 2000 14:35:53 -0800 (PST) Received: from conecta.mgconecta.com.br (conecta.mgconecta.com.br [200.238.205.101]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA15639 for ; Tue, 22 Feb 2000 18:17:54 -0800 (PST) Received: from localhost.localdomain (IDENT:root@line028M [200.238.205.38]) by conecta.mgconecta.com.br (8.9.3/8.9.3) with SMTP id AAA20002 for ; Wed, 23 Feb 2000 00:36:26 -0300 (EST) From: mendes Organization: Working at home To: majordomo-users@GreatCircle.COM Subject: Newbie question - list is setup ok but no messages received Date: Wed, 23 Feb 2000 00:38:15 -0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <0002230042440F.00762@localhost.localdomain> Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello I am newbie (although I read the faq and stuff). I followed the instructions line by line in order to setup a list. Everything seems fine and I could subscribe and unsubscribe without a problem. However when I sent a message to the list it simply disappeared. No return email of any kind. Did I miss something when configuring the list? Thanks a lot. Regards Eduardo From majordomo-users-owner Wed Feb 23 16:12:32 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01492; Wed, 23 Feb 2000 14:35:52 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA01482 for majordomo-users@greatcircle.com; Wed, 23 Feb 2000 14:35:48 -0800 (PST) Received: from szilu.bgk.bme.hu (szilu.bgk.bme.hu [152.66.233.96]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA13427 for ; Tue, 22 Feb 2000 15:32:23 -0800 (PST) Received: from szilu by szilu.bgk.bme.hu with local-esmtp (Exim 2.05 #1 (Debian)) id 12NP4N-000243-00; Wed, 23 Feb 2000 00:50:19 +0100 Date: Wed, 23 Feb 2000 00:50:19 +0100 (CET) From: Aradi Szilard To: majordomo-users@greatcircle.com Subject: help me Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi! I`m from Hungary. I`ve got Debian Linux 2.1. The kernel version is 2.2.12. My sendmail program is exim. I installed majordomo firstly and it doesn`t work. I follow the install file correctly. The config-test ran without any errors. I made a test list by the newlist file. I wrote the neccessary lines into /etc/aliases. But if i wrote a mail to majordomo with any command, it doesn`t work and in the exim`s mainlog there`s the following error message: Neither the system_aliases director nor the address_pipe transport set a uid for local delivery of |/usr/local/majordomo-1.94.5/wrapper majordomo. Please, SOMEBODY HELP ME! I haven`t got any idea. Bye Szilu From majordomo-users-owner Wed Feb 23 16:27:36 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01369; Wed, 23 Feb 2000 14:33:26 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA01359 for majordomo-users@greatcircle.com; Wed, 23 Feb 2000 14:33:23 -0800 (PST) Received: from snipe.prod.itd.earthlink.net (snipe.prod.itd.earthlink.net [207.217.120.62]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA08723 for ; Tue, 22 Feb 2000 08:49:36 -0800 (PST) Received: from lw1 (dialup-209.246.108.103.NewYork2.Level3.net [209.246.108.103]) by snipe.prod.itd.earthlink.net (8.9.3/8.9.3) with SMTP id JAA27904 for ; Tue, 22 Feb 2000 09:07:31 -0800 (PST) Reply-To: From: "Tom Baurley" To: Subject: automating unsubscribe Date: Tue, 22 Feb 2000 12:06:38 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Greetings - I have a question for any Majordomo list managers out there --- Basically what we'd like to do (if it's possible) is a way to have majordomo auto-unsub people who have invalid addresses. Say for example a user is signed up for a particular list but they switch ISPs and forget to unsubscribe from our list. Majordomo tries to send them mail, but the address it's sending to doesn't exist, so it bounces back. our mail administrator or mailing list manager gets a "message could not be delivered" e-mail, and the procedure we are doing now is to go into our webmin program or send a mail to majordomo to unsub the person manually. The problem is that we get a *lot* of bad addresses, and we end up spending quite a bit of time taking them out. So it would be a lot easier if we had some way of getting majordomo to unsub any address that is returned as undeliverable. Is there a way to to handle this? Anyone know of scripts or adjustments we could run? Also - I posted this question before on some majordomo lists but never got a response from anyone, perhaps it's because there is no answer, but let me ask once again Is there anyway to automatically stop autoresponders (on vacation replys) from posting to our lists outside of manually going in and unsubscribing them. (This is actually quite related to the above) Please let me know if anyone has a solution for us. Thank you, Tom Baurley webmaster, Expatexchange From majordomo-users-owner Wed Feb 23 16:42:32 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01479; Wed, 23 Feb 2000 14:35:48 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA01468 for majordomo-users@greatcircle.com; Wed, 23 Feb 2000 14:35:44 -0800 (PST) Received: from chamber.dna.fi (chamber.dna.fi [62.236.155.125]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id PAA13130 for ; Tue, 22 Feb 2000 15:00:34 -0800 (PST) Received: (qmail 9360 invoked by uid 501); 23 Feb 2000 01:18:33 +0200 Date: Wed, 23 Feb 2000 01:18:33 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: anna hook Cc: Majordomo-users@GreatCircle.COM Subject: Re: Question about " Invalid'Approved:' header " P.S. Message-ID: <20000223011833.A9298@chamber.dna.fi> Reply-To: Mikko.Hanninen@iki.fi Mail-Followup-To: anna hook , Majordomo-users@GreatCircle.COM References: <38B2E42B.5F744A91@sgsnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.1.4i In-Reply-To: <38B2E42B.5F744A91@sgsnet.com>; from anna@sgsnet.com on Tue, Feb 22, 2000 at 01:31:55PM -0600 Organization: None Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk anna hook wrote on Tue, 22 Feb 2000: > First, sorry for being an idiot and sending a 'subscribe message' to > majordomo-users. I guess it just shows how frustrated I am. We never saw it... (Majordomo at work, I'm sure.) > Ok I can't > figure out how to send an 'approved' message to a moderated list? I am > following the directions... at least I think I am? > > Here is what I am doing: > 1) I compose a message > 2) In the body I put the following: > Approved: password > 3) I send the message > 4) It bounces with the message "Invalid 'Approved:' header" > 5) I curse at my monitor. How about you show us an example of the bounce message? (With the password x'd out or something.) > -I send it with a space in between: > Approved: password > > Majordomo is driving me nuts. This is the proper format, but I think you should be submitting also some headers of your own: Approved: password From: anna hook To: your-list@yourserver.com Subject: Majordomo is driving me nuts. Majordomo is driving me nuts. This goes all in the message body, starting right at the top, no return or anything before. Since you're submitting the headers yourself, you can put any address you want in the From: line for example... Also, make sure you're not sending the text out in HTML format or anything like that, though it doesn't sound like that's the problem. Disclaimer: I haven't done manual message approval in a good while since I always use the handy "approve" script that comes with Majordomo, for approving bounced messages and also subscribe/unsubscribe requests. Mikko -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / There is a 70% probability of tomorrow. (Actual weatherman quote, 1988) From majordomo-users-owner Wed Feb 23 16:57:33 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01530; Wed, 23 Feb 2000 14:36:14 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA01510 for majordomo-users@greatcircle.com; Wed, 23 Feb 2000 14:36:03 -0800 (PST) Received: from offworld.tca.net (offworld.tca.net [208.162.121.253]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id SAA15742 for ; Tue, 22 Feb 2000 18:26:32 -0800 (PST) Received: (from cmenzel@localhost) by offworld.tca.net (8.9.3/8.9.3) id UAA12153; Tue, 22 Feb 2000 20:44:33 -0600 Date: Tue, 22 Feb 2000 20:44:33 -0600 From: Chris Menzel To: majordomo-users@greatcircle.com Subject: wrapper not being found... Message-ID: <20000222204433.D1584@offworld.tca.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi majordomo-users. This seems like a problem with an obvious solution, but I have been banging my head against the wall for a couple of hours now and have not found the answer. I installed majordomo 1.94 on my Linux box via an RPM file. (This is my first experience with majordomo.) I have set up a list called "testing", following each step in the directions carefully. I have compared my setup with that on another Linux box. My /etc/aliases and /etc/majordomo.cf files are (as far as I can tell) set up properly. Yet I keep getting an error when I submit a message to the testing list to the effect that "wrapper is not available for sendmail programs"; note that I got exactly the same message when, in mucking with the /etc/aliases file, I had specified the wrong directory for wrapper -- one that didn't even exist. So it is as if wrapper isn't being found. Yet it is indeed there in the specified directory (/usr/lib/majordomo), with the correct permissions. I would really appreciate some suggestions here. I include the error message I get when I try to subscribe to the list in question below; I get a similar message no matter what I send to the list. Can anyone see what might be wrong? I'd be much obliged. Chris Menzel ************ Date: Tue, 22 Feb 2000 20:33:16 -0600 From: Mail Delivery Subsystem To: Subject: Returned mail: Service unavailable Auto-Submitted: auto-generated (failure) The original message was received at Tue, 22 Feb 2000 20:33:16 -0600 from smtp-relay-2.tamu.edu [128.194.103.91] ----- The following addresses had permanent fatal errors ----- "|/usr/lib/majordomo/wrapper request-answer testing" (expanded from: ) ----- Transcript of session follows ----- sh: wrapper not available for sendmail programs 554 "|/usr/lib/majordomo/wrapper request-answer testing"... Service unavailable Reporting-MTA: dns; philebus.tamu.edu Received-From-MTA: DNS; smtp-relay-2.tamu.edu Arrival-Date: Tue, 22 Feb 2000 20:33:16 -0600 Final-Recipient: RFC822; X-Actual-Recipient: RFC822; |/usr/lib/majordomo/wrapper request-answer testing@philebus.tamu.edu Action: failed Status: 5.5.0 Last-Attempt-Date: Tue, 22 Feb 2000 20:33:16 -0600 Date: Tue, 22 Feb 2000 20:33:15 -0600 From: Chris Menzel To: testing-request@philebus.tamu.edu subscribe From majordomo-users-owner Wed Feb 23 17:05:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA01447; Wed, 23 Feb 2000 14:35:24 -0800 (PST) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA01435 for majordomo-users@greatcircle.com; Wed, 23 Feb 2000 14:35:20 -0800 (PST) Received: from mercury.cmaontheweb.com (ip239-14.drxpress.com [204.252.239.14]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA11461 for ; Tue, 22 Feb 2000 12:38:32 -0800 (PST) Received: from jjwdell ([204.252.239.196]) by mercury.cmaontheweb.com (Lotus Domino Release 5.0.2b) with SMTP id 2000022214443168:8 ; Tue, 22 Feb 2000 14:44:31 -0600 Message-ID: <000801bf7d77$5179a4d0$c4effccc@cmaontheweb.com> From: "Jeremy Wesley" To: Subject: help, Date: Tue, 22 Feb 2000 14:56:40 -0600 MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-MIMETrack: Itemize by SMTP Server on mercury/CMA(Release 5.0.2b |December 16, 1999) at 02/22/2000 02:44:31 PM, Serialize by Router on mercury/CMA(Release 5.0.2b |December 16, 1999) at 02/22/2000 02:44:40 PM, Serialize complete at 02/22/2000 02:44:40 PM Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BF7D45.06C85170" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BF7D45.06C85170 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" i have Rh6.0 linux running, i installed majordomo with a rpm. i was = following the HOWTO from linuxdoc.com and it said to run ...../wrapper = config-test to test the config i got the following error. --------------------- Obvious things: --------------------- ------------------ environment variables ------------------ HOME=3D/usr/lib/majordomo LOGNAME=3Djerm MAJORDOMO_CF=3D/etc/majordomo.cf PATH=3D/bin:/usr/bin SHELL=3D/bin/sh USER=3Djerm --------------------- euid/egid checks --------------------- effective user =3D majordomo (uid 91) effective group =3D majordomo jerm (gid 91 500 ) ---------------------- uid/gid checks ---------------------- real user =3D majordomo (uid 91) real group =3D majordomo jerm (gid 91 500 ) ------------------------------------------------------------ Non obvious things that cause headaches: ------------------------------------------------------------ Good: 'require'd /etc/majordomo.cf okay. Good: found ctime.pl okay. Can't locate majordomo_version.pl in @INC (@INC contains: = /usr/lib/perl5/5.00503 /i386-linux /usr/lib/perl5/5.00503 = /usr/lib/perl5/site_perl/5.005/i386-linux /us r/lib/perl5/site_perl/5.005 .) at /usr/lib/majordomo/config-test line = 129. ********************************** I know that CANT thing has to be a bad thing, but what is it? Please note that i am not a supper linux guru.=20 Anyhelp apperciated. JeRm ------=_NextPart_000_0005_01BF7D45.06C85170 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1"
i have Rh6.0 linux running, i installed = majordomo=20 with a rpm.  i was following the HOWTO from linuxdoc.com and it = said to run=20 ...../wrapper config-test     to test the config i = got the=20 following error.
 
--------------------- Obvious things:=20 ---------------------
------------------ environment variables=20 ------------------
   = HOME=3D/usr/lib/majordomo
  =20 LOGNAME=3Djerm
   = MAJORDOMO_CF=3D/etc/majordomo.cf
  =20 PATH=3D/bin:/usr/bin
   SHELL=3D/bin/sh
  =20 USER=3Djerm
--------------------- euid/egid checks=20 ---------------------
   effective user  =3D majordomo = (uid=20 91)
   effective group =3D majordomo jerm (gid 91 500=20 )
---------------------- uid/gid checks=20 ----------------------
   = real     =20 user  =3D majordomo (uid 91)
  =20 real      group =3D majordomo jerm (gid 91 500=20 )
------------------------------------------------------------<= /DIV>
 
        Non=20 obvious things that cause headaches:
 
------------------------------------------------------------
= Good:=20 'require'd /etc/majordomo.cf okay.
Good: found ctime.pl = okay.
Can't locate=20 majordomo_version.pl in @INC (@INC contains:=20 /usr/lib/perl5/5.00503
/i386-linux /usr/lib/perl5/5.00503=20 /usr/lib/perl5/site_perl/5.005/i386-linux = /us
r/lib/perl5/site_perl/5.005 .)=20 at /usr/lib/majordomo/config-test line 129.
**********************************
I know that CANT thing has to be a bad = thing, but=20 what is it?
Please note that i am not a supper = linux guru.=20
Anyhelp apperciated.
JeRm
------=_NextPart_000_0005_01BF7D45.06C85170-- From majordomo-users-owner Wed Feb 23 17:17:00 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA02348; Wed, 23 Feb 2000 15:45:28 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id PAA02335 for ; Wed, 23 Feb 2000 15:44:58 -0800 (PST) Received: (qmail 21867 invoked from network); 24 Feb 2000 00:03:08 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 24 Feb 2000 00:03:08 -0000 Date: Wed, 23 Feb 2000 17:00:07 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: "Wilson, Sue LCC" cc: Majordomo-users@GreatCircle.COM Subject: Re: Newbie Question In-Reply-To: <0A4857C61983D3119E8400508B1377EF07FAC5@lccpdxm1.dms.usace.army.mil> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Unfortunately, Sun no longer includes the C compiler with the Solaris distribution. You either have to (1) buy the C compiler or (2, better) download the GNU compiler already built for Solaris. Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com On Wed, 23 Feb 2000, Wilson, Sue LCC wrote: > I am new to Installing MajorDomo and I cannot get the wrapper to work. I > have never done a makefile or wrapper before sooo...any help would be > appreciated. Thanks in advance. > > I am trying to install Majordomo Version 1.94.5 on a SunSolaris 2.5 system. > > > When I do " make wrapper" this is what I get: > cc -DBIN=\"/export/opt/majordomo-1.94.5\" > -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" > -DHOME=\"HOME=/export/opt/majordomo-1.94.5\" -DSHELL=\"SHELL=/bin/sh\" > -DMAJORDOMO_CF=\"MAJORDOMO_CF=/export/opt/majordomo-1.94.5/majordomo.cf\" > -DPOSIX_UID=501 -DPOSIX_GID=501 -o wrapper wrapper.c > /usr/ucb/cc: language optional software package not installed > *** Error code 1 > make: Fatal error: Command failed for target `wrapper' > From majordomo-users-owner Wed Feb 23 17:30:52 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA00899; Wed, 23 Feb 2000 14:24:56 -0800 (PST) Received: from surf.monterey.k12.ca.us (surf.monterey.k12.ca.us [205.155.53.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA00892 for ; Wed, 23 Feb 2000 14:24:49 -0800 (PST) Received: from stingray.pacbell.net (adsl-63-193-160-94.dsl.lsan03.pacbell.net [63.193.160.94]) by surf.monterey.k12.ca.us (Pro-8.9.3/8.9.3) with SMTP id OAA00895 for ; Wed, 23 Feb 2000 14:38:26 -0800 (PST) From: David Stihler Date: Wed, 23 Feb 2000 22:42:27 GMT Message-ID: <20000223.22422737@stingray.pacbell.net> Subject: Request help with permissions To: majordomo-users@greatcircle.com X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.1; Win32) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I don't seem to be able to get majordomo working again. Does anyone=20= recognize these errors. Thanks in advance. I'm getting the following error on Delivery-Status Final-Recipient: RFC822; test-list@surf.monterey.k12.ca.us Action: failed Status: 5.4.6 Last-Attempt-Date: Wed, 23 Feb 2000 14:31:34 -0800 (PST) Final-Recipient: RFC822; test-list@surf.monterey.k12.ca.us X-Actual-Recipient: RFC822;=20 /usr/local/majordomo/lists/test@surf.monterey.k12.ca.us Action: failed Status: 5.2.4 Last-Attempt-Date: Wed, 23 Feb 2000 14:31:34 -0800 (PST) The following error as a subject:=20 The original message was received at Wed, 23 Feb 2000 14:31:34 -0800=20= (PST) from majordom@localhost ----- The following addresses had permanent fatal errors ----- test-list :include:/usr/local/majordomo/lists/test (expanded from: test-list) ----- Transcript of session follows ----- 550 :include:/usr/local/majordomo/lists/test... Cannot open=20 /usr/local/majordomo/lists/test: Group writable directory 554 test-list... aliasing/forwarding loop broken From majordomo-users-owner Wed Feb 23 17:58:55 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA03531; Wed, 23 Feb 2000 17:52:41 -0800 (PST) Received: from pali.cps.cmich.edu (pali.cps.cmich.edu [141.209.131.81]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA03524 for ; Wed, 23 Feb 2000 17:52:32 -0800 (PST) Received: (from ishwar@localhost) by pali.cps.cmich.edu (8.9.2/8.9.1) id VAA24208; Wed, 23 Feb 2000 21:09:50 -0500 (EST) (envelope-from ishwar) Date: Wed, 23 Feb 2000 21:09:50 -0500 (EST) From: Ish Rattan Message-Id: <200002240209.VAA24208@pali.cps.cmich.edu> To: majordomo-users@GreatCircle.COM, mendes@mgconecta.com.br Subject: Re: It doesn't matter what I do, majordomo won't work ..... In-Reply-To: <0002232015580C.00762@localhost.localdomain> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk All directories should have permissions 755. From majordomo-users-owner Wed Feb 23 19:29:08 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA04390; Wed, 23 Feb 2000 19:14:03 -0800 (PST) Received: from kappa (adsl-151-200-26-75.bellatlantic.net [151.200.26.75]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA04383 for ; Wed, 23 Feb 2000 19:13:52 -0800 (PST) Received: from kappa ([127.0.0.1]) by kappa with Microsoft SMTPSVC(5.0.2172.1); Wed, 23 Feb 2000 22:32:23 -0500 Message-Id: <4.1.20000223222457.00a2a8b8@mailbox.bellatlantic.net> X-Sender: jeasterl@mailbox.bellatlantic.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 23 Feb 2000 22:32:23 -0500 To: majordomo-users@greatcircle.com From: Julian Easterling Subject: Majordomo 1.94.5 configuration problems? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 24 Feb 2000 03:32:23.0569 (UTC) FILETIME=[C37E1010:01BF7E77] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I installed sendmail 8.9.3 onto Linux Mandrake 7.0 I then installed majordomo 1.94.5 following the directions in O'Reilly's Managing Mailing Lists (Chapter 10) When I send a message to the majordomo user to using the command lists nothing ever comes back. The mailer-daemon mail is forwarded to my email and this is a partial clip from the message: ----- The following addresses had permanent fatal errors ----- "|/home/majordom/runtime/wrapper majordomo" (expanded from: ) ----- Transcript of session follows ----- sh: wrapper not available for sendmail programs 554 "|/home/majordom/runtime/wrapper majordomo"... Service unavailable I couldn't find any help in the book for this. Running ./wrapper config-test doesn't show any errors. Does anyone know what else to try? From majordomo-users-owner Wed Feb 23 19:44:09 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA04587; Wed, 23 Feb 2000 19:32:31 -0800 (PST) Received: from firewall.globeset.com (firewall.globeset.com [207.239.133.67]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA04580 for ; Wed, 23 Feb 2000 19:32:22 -0800 (PST) Received: from earth.globeset.com (earth.globeset.com [10.1.1.5]) by firewall.globeset.com (8.9.3/8.9.3) with ESMTP id VAA10505; Wed, 23 Feb 2000 21:50:33 -0600 (CST) Received: from globeset.com (root@firewall.globeset.com [10.1.1.254]) by earth.globeset.com (8.9.3/8.9.3) with ESMTP id VAA16761; Wed, 23 Feb 2000 21:50:22 -0600 (CST) Message-ID: <38B4A9FD.BD7FA826@globeset.com> Date: Wed, 23 Feb 2000 21:48:14 -0600 From: "Wade T. Funk" X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: mendes CC: majordomo-users@GreatCircle.COM Subject: Re: It doesn't matter what I do, majordomo won't work ..... References: <0002232015580C.00762@localhost.localdomain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Your "lists" directory can NOT be group writable....I suggest you do a chmod 755 lists. Wade mendes wrote: > Hello > I sent some messages to the list asking about the permissions. I tried > everything that was said. Unfortunately majordomo refuses to work and just > fills my maibox with > > The original message was received at Wed, 23 Feb 2000 17:03:15 -0300from majordomo@localhost > ----- The following addresses had permanent fatal errors ----- > iniciacao-list > :include:/usr/lib/majordomo/lists/iniciacao > (expanded from: iniciacao-list) > > ----- Transcript of session follows ----- > 550 :include:/usr/lib/majordomo/lists/iniciacao... Cannot open /usr/lib/majordomo/lists/iniciacao: Group writable directory > 554 iniciacao-list... aliasing/forwarding loop broken > > What can I do to sort this out? > > Thanks a lot. > > Eduardo. > > PS. These are my file permissions: > > [root@angel majordomo]# ls -l > total 312 > drwxr-xr-x 5 majordom daemon 4096 Feb 22 14:02 Desktop > -rw-rw-r-- 1 majordom daemon 2663 Feb 23 02:24 Log > drwxr-xr-x 2 majordom daemon 4096 Feb 22 14:16 Tools > -rwxr-xr-x 1 majordom daemon 5267 Feb 22 14:15 archive2.pl > drwxrwxr-x 2 majordom daemon 4096 Feb 23 17:00 archives > drwxr-xr-x 2 majordom daemon 4096 Feb 22 14:09 bin > -rwxr-xr-x 1 majordom daemon 2795 Feb 22 14:15 bounce-remind > -rwxr-xr-x 1 majordom daemon 10671 Feb 22 14:15 config-test > -rwxr-xr-x 1 majordom daemon 51130 Feb 22 14:15 config_parse.pl > -rwxr-xr-x 1 majordom daemon 14201 Feb 22 14:15 digest > drwxrwxr-x 2 majordom daemon 4096 Feb 23 17:00 digests > drwxrwxr-x 2 majordom daemon 4096 Feb 23 14:53 lists > -rwxr-xr-x 1 majordom daemon 62511 Feb 22 14:15 majordomo > -rw-r--r-- 1 majordom daemon 107 Feb 22 17:57 majordomo.aliases > -rwxr-x--- 1 majordom daemon 0 Feb 22 17:59 majordomo.aliases.db > -rw-r--r-- 1 majordom daemon 10471 Feb 22 14:16 majordomo.cf > -rwxr-xr-x 1 majordom daemon 24381 Feb 22 14:15 majordomo.pl > -rwxr-xr-x 1 majordom daemon 137 Feb 22 14:15 majordomo_version.pl > drwxr-xr-x 4 majordom daemon 4096 Feb 22 14:16 man > -rwxr-xr-x 1 majordom daemon 3791 Feb 22 14:15 request-answer > -rwxr-xr-x 1 majordom daemon 29919 Feb 22 14:15 resend > -rw-r--r-- 1 majordom daemon 10462 Feb 22 14:16 sample.cf > -rwxr-xr-x 1 majordom daemon 8060 Feb 22 14:15 shlock.pl > -rwsr-xr-x 1 root daemon 14826 Feb 22 14:16 wrapper From majordomo-users-owner Wed Feb 23 20:13:57 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id UAA04844; Wed, 23 Feb 2000 20:01:05 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id UAA04837 for ; Wed, 23 Feb 2000 20:00:59 -0800 (PST) Received: (qmail 16335 invoked from network); 24 Feb 2000 04:19:11 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 24 Feb 2000 04:19:11 -0000 Date: Wed, 23 Feb 2000 21:16:10 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: KERRAA@uwec.edu cc: majordomo-users@GreatCircle.COM Subject: Re: FW: Returned mail: Service unavailable In-Reply-To: <3DD3BED8DB4DD311B0EE0020484050DC65D510@kyle.uwec.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Search the FAQ for "smrsh", and you'll find instructions on how to enable the service. Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com On Wed, 23 Feb 2000 KERRAA@uwec.edu wrote: > The following is an error that I get when I try to send a message to majordomo > > I am using Red Hat 6.1 any help would be greatly appreciated. > > > > ----- The following addresses had permanent fatal errors ----- > > "|/home/majordomo/wrapper majordomo" > > (expanded from: majordomo) > > > > ----- Transcript of session follows ----- > > sh: wrapper not available for sendmail programs > > 554 "|/home/majordomo/wrapper majordomo"... Service unavailable > > From majordomo-users-owner Wed Feb 23 20:29:00 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id UAA04996; Wed, 23 Feb 2000 20:22:35 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id UAA04989 for ; Wed, 23 Feb 2000 20:22:27 -0800 (PST) Received: (qmail 26786 invoked from network); 24 Feb 2000 04:40:39 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 24 Feb 2000 04:40:39 -0000 Date: Wed, 23 Feb 2000 21:37:37 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: Chris Menzel cc: majordomo-users@GreatCircle.COM Subject: Re: wrapper not being found... In-Reply-To: <20000222204433.D1584@offworld.tca.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I think this is the smrsh problem that usually gets everyone who starts with Major. Search for "smrsh" in the FAQ. Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com On Tue, 22 Feb 2000, Chris Menzel wrote: > Hi majordomo-users. This seems like a problem with an obvious solution, > but I have been banging my head against the wall for a couple of hours > now and have not found the answer. I installed majordomo 1.94 on my > Linux box via an RPM file. (This is my first experience with > majordomo.) I have set up a list called "testing", following each step > in the directions carefully. I have compared my setup with that on > another Linux box. My /etc/aliases and /etc/majordomo.cf files are (as > far as I can tell) set up properly. Yet I keep getting an error when I > submit a message to the testing list to the effect that "wrapper is not > available for sendmail programs"; note that I got exactly the same > message when, in mucking with the /etc/aliases file, I had specified the > wrong directory for wrapper -- one that didn't even exist. So it is as > if wrapper isn't being found. Yet it is indeed there in the specified > directory (/usr/lib/majordomo), with the correct permissions. > > I would really appreciate some suggestions here. I include the error > message I get when I try to subscribe to the list in question below; I > get a similar message no matter what I send to the list. Can anyone see > what might be wrong? I'd be much obliged. > > Chris Menzel > > ************ > > Date: Tue, 22 Feb 2000 20:33:16 -0600 > From: Mail Delivery Subsystem > To: > Subject: Returned mail: Service unavailable > Auto-Submitted: auto-generated (failure) > > The original message was received at Tue, 22 Feb 2000 20:33:16 -0600 > from smtp-relay-2.tamu.edu [128.194.103.91] > > ----- The following addresses had permanent fatal errors ----- > "|/usr/lib/majordomo/wrapper request-answer testing" > (expanded from: ) > > ----- Transcript of session follows ----- > sh: wrapper not available for sendmail programs > 554 "|/usr/lib/majordomo/wrapper request-answer testing"... Service unavailable > > Reporting-MTA: dns; philebus.tamu.edu > Received-From-MTA: DNS; smtp-relay-2.tamu.edu > Arrival-Date: Tue, 22 Feb 2000 20:33:16 -0600 > > Final-Recipient: RFC822; > X-Actual-Recipient: RFC822; |/usr/lib/majordomo/wrapper request-answer testing@philebus.tamu.edu > Action: failed > Status: 5.5.0 > Last-Attempt-Date: Tue, 22 Feb 2000 20:33:16 -0600 > > Date: Tue, 22 Feb 2000 20:33:15 -0600 > From: Chris Menzel > To: testing-request@philebus.tamu.edu > > subscribe > > From majordomo-users-owner Wed Feb 23 20:43:50 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id UAA05079; Wed, 23 Feb 2000 20:33:47 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id UAA05072 for ; Wed, 23 Feb 2000 20:33:37 -0800 (PST) Received: (qmail 1936 invoked from network); 24 Feb 2000 04:51:47 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 24 Feb 2000 04:51:47 -0000 Date: Wed, 23 Feb 2000 21:48:45 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: Jeremy Wesley cc: Majordomo-Users@GreatCircle.COM Subject: Re: help, In-Reply-To: <000801bf7d77$5179a4d0$c4effccc@cmaontheweb.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk It can't find perl. The easiest way to fix it is to make a symbolic link to wherever perl actually is. You can find perl, assuming it is in the search path, by doing: type perl or which perl which will tell you where perl is. Then do something like this: ln -s $(type perl) /usr/lib/perl5/5.00503... You'll have to create the directory, e.g., /usr/lib/perl5. Hope that helps. Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com On Tue, 22 Feb 2000, Jeremy Wesley wrote: > i have Rh6.0 linux running, i installed majordomo with a rpm. i was following the HOWTO from linuxdoc.com and it said to run ...../wrapper config-test to test the config i got the following error. > > --------------------- Obvious things: --------------------- > ------------------ environment variables ------------------ > HOME=/usr/lib/majordomo > LOGNAME=jerm > MAJORDOMO_CF=/etc/majordomo.cf > PATH=/bin:/usr/bin > SHELL=/bin/sh > USER=jerm > --------------------- euid/egid checks --------------------- > effective user = majordomo (uid 91) > effective group = majordomo jerm (gid 91 500 ) > ---------------------- uid/gid checks ---------------------- > real user = majordomo (uid 91) > real group = majordomo jerm (gid 91 500 ) > ------------------------------------------------------------ > > Non obvious things that cause headaches: > > ------------------------------------------------------------ > Good: 'require'd /etc/majordomo.cf okay. > Good: found ctime.pl okay. > Can't locate majordomo_version.pl in @INC (@INC contains: /usr/lib/perl5/5.00503 > /i386-linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux /us > r/lib/perl5/site_perl/5.005 .) at /usr/lib/majordomo/config-test line 129. > ********************************** > I know that CANT thing has to be a bad thing, but what is it? > Please note that i am not a supper linux guru. > Anyhelp apperciated. > JeRm > From majordomo-users-owner Wed Feb 23 23:28:51 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id XAA06965; Wed, 23 Feb 2000 23:23:29 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id XAA06958 for ; Wed, 23 Feb 2000 23:23:23 -0800 (PST) Received: (qmail 3456 invoked from network); 24 Feb 2000 07:41:37 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 24 Feb 2000 07:41:37 -0000 Date: Thu, 24 Feb 2000 00:38:35 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: Julian Easterling cc: majordomo-users@GreatCircle.COM Subject: Re: Majordomo 1.94.5 configuration problems? In-Reply-To: <4.1.20000223222457.00a2a8b8@mailbox.bellatlantic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Search the FAQ for "smrsh" to see how to enable the service. Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com On Wed, 23 Feb 2000, Julian Easterling wrote: > I installed sendmail 8.9.3 onto Linux Mandrake 7.0 > I then installed majordomo 1.94.5 following the directions in > O'Reilly's Managing Mailing Lists (Chapter 10) > > When I send a message to the majordomo user to using the command lists > nothing ever comes back. The mailer-daemon mail is forwarded to my email > and this is a partial clip from the message: > > ----- The following addresses had permanent fatal errors ----- > "|/home/majordom/runtime/wrapper majordomo" > (expanded from: ) > > ----- Transcript of session follows ----- > sh: wrapper not available for sendmail programs > 554 "|/home/majordom/runtime/wrapper majordomo"... Service unavailable > > I couldn't find any help in the book for this. Running ./wrapper config-test > doesn't show any errors. Does anyone know what else to try? > From majordomo-users-owner Thu Feb 24 04:15:10 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id EAA15332; Thu, 24 Feb 2000 04:04:49 -0800 (PST) Received: from mail.rentpayment.com ([38.194.38.165]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA15325 for ; Thu, 24 Feb 2000 04:04:41 -0800 (PST) Received: from chesternet.net ([207.87.127.98]) by mail.rentpayment.com (Netscape Messaging Server 4.1) with ESMTP id FQFP1G00.C05; Thu, 24 Feb 2000 07:22:28 -0500 Message-ID: <38B52234.E40F19F1@chesternet.net> Date: Thu, 24 Feb 2000 07:21:08 -0500 From: "Daniel chester" Reply-To: talamar@chesternet.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Wilson Sue LCC" CC: Majordomo-users@GreatCircle.COM Subject: Re: Newbie Question References: <0A4857C61983D3119E8400508B1377EF07FAC5@lccpdxm1.dms.usace.army.mil> Content-Type: multipart/mixed; boundary="------------212A25B727654AD35B8BB03A" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. --------------212A25B727654AD35B8BB03A Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit You have no C compiler, Solaris does not ship with one.  Go to www.sunfreeware.com and download gcc.  If you already have, modify your path statemenet so that /usr/local/bin is before /usr/ccs/bin.

"Wilson, Sue LCC" wrote:

 

I am new to Installing MajorDomo and I cannot get the wrapper to work. I have never done a makefile or wrapper before sooo...any help would be appreciated.  Thanks in advance.

I am trying to install Majordomo Version 1.94.5 on a SunSolaris 2.5 system.

When I do " make wrapper" this is what I get:
cc  -DBIN=\"/export/opt/majordomo-1.94.5\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\"  -DHOME=\"HOME=/export/opt/majordomo-1.94.5\" -DSHELL=\"SHELL=/bin/sh\"  -DMAJORDOMO_CF=\"MAJORDOMO_CF=/export/opt/majordomo-1.94.5/majordomo.cf\"       -DPOSIX_UID=501 -DPOSIX_GID=501 -o wrapper wrapper.c

/usr/ucb/cc:  language optional software package not installed
*** Error code 1
make: Fatal error: Command failed for target `wrapper'

--------------212A25B727654AD35B8BB03A Content-Type: text/x-vcard; charset=us-ascii; name="talamar.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Daniel Chester Content-Disposition: attachment; filename="talamar.vcf" begin:vcard n:Chester;Daniel tel;work:440-734-9348 x-mozilla-html:TRUE url:www.rentpayment.com org:RentPayment.COM adr:;;;;;; version:2.1 email;internet:dan@chesternet.net title:Technical Analyst fn:Daniel Chester end:vcard --------------212A25B727654AD35B8BB03A-- From majordomo-users-owner Thu Feb 24 05:45:11 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA16046; Thu, 24 Feb 2000 05:30:21 -0800 (PST) Received: from kappa (adsl-151-200-26-75.bellatlantic.net [151.200.26.75]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA16039 for ; Thu, 24 Feb 2000 05:30:13 -0800 (PST) Received: from kappa ([127.0.0.1]) by kappa with Microsoft SMTPSVC(5.0.2172.1); Thu, 24 Feb 2000 08:48:51 -0500 Message-Id: <4.1.20000224081931.00a432e0@mailbox.bellatlantic.net> X-Sender: jeasterl@mailbox.bellatlantic.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 24 Feb 2000 08:48:50 -0500 To: Seth Kurtzberg From: Julian Easterling Subject: Re: Majordomo 1.94.5 configuration problems? Cc: majordomo-users@GreatCircle.COM In-Reply-To: References: <4.1.20000223222457.00a2a8b8@mailbox.bellatlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 24 Feb 2000 13:48:51.0065 (UTC) FILETIME=[E1C20E90:01BF7ECD] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I apologize for posting the original message without checking the FAQ first. I did look at the FAQ after sending the message and found the section on Service not Available I created a symbolic link in /etc/smrsh by typing: "ln /home/majordom/runtime/wrapper wrapper" I don't get the messages from mailer-daemon now, but majordomo still isn't responding to any commands. I send a "help" command to it so that it sends me the help message. I double checked my $whoami because I read about this being "broke" in the RPM for Redhat Linux even though I used the source that I downloaded from great circle to install my majordomo. I have it set to the hostname that should be receiving the mail: "mailhost.happyhourdc.com". I tried sending the message to that address as well as the "real" host name for the computer running majordomo: "mu.julianscorner.com" I am running Perl version 5.005_03. Is there something that I am missing? Thanks for any help you can give me. -Julian Easterling. At 12:38 AM 2/24/2000 -0700, Seth Kurtzberg wrote: >Search the FAQ for "smrsh" to see how to enable the service. > >Seth Kurtzberg >Machine Independent Software >Cell (602) 478-5511 >Fax: (480) 614-8909 >email: seth@cql.com >pager: 888-605-9296 or email 6059296@skytel.com > > >On Wed, 23 Feb 2000, Julian Easterling wrote: > >> I installed sendmail 8.9.3 onto Linux Mandrake 7.0 >> I then installed majordomo 1.94.5 following the directions in >> O'Reilly's Managing Mailing Lists (Chapter 10) >> >> When I send a message to the majordomo user to using the command lists >> nothing ever comes back. The mailer-daemon mail is forwarded to my email >> and this is a partial clip from the message: >> >> ----- The following addresses had permanent fatal errors ----- >> "|/home/majordom/runtime/wrapper majordomo" >> (expanded from: ) >> >> ----- Transcript of session follows ----- >> sh: wrapper not available for sendmail programs >> 554 "|/home/majordom/runtime/wrapper majordomo"... Service unavailable >> >> I couldn't find any help in the book for this. Running ./wrapper config-test >> doesn't show any errors. Does anyone know what else to try? >> From majordomo-users-owner Thu Feb 24 06:00:12 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA16162; Thu, 24 Feb 2000 05:42:58 -0800 (PST) Received: from conecta.mgconecta.com.br (conecta.mgconecta.com.br [200.238.205.101]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA16155 for ; Thu, 24 Feb 2000 05:42:50 -0800 (PST) Received: from localhost.localdomain (IDENT:root@line019M [200.238.205.29]) by conecta.mgconecta.com.br (8.9.3/8.9.3) with SMTP id MAA23557 for ; Thu, 24 Feb 2000 12:01:39 -0300 (EST) From: mendes Organization: Working at home To: majordomo-users@GreatCircle.COM Subject: Getting better but I still have problems .... Date: Thu, 24 Feb 2000 12:04:29 -0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00022412075703.00766@localhost.localdomain> Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello It seems that finally the list is sort of working. The list has two members. Using one member's account I sent an email to the list. The other member received the message but the sender did not. Any suggestions? Many thanks for the replies - they helped a lot. Kind regards Eduardo From majordomo-users-owner Thu Feb 24 07:15:04 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA17096; Thu, 24 Feb 2000 07:02:54 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id HAA17089 for ; Thu, 24 Feb 2000 07:02:48 -0800 (PST) Received: (qmail 9323 invoked from network); 24 Feb 2000 15:21:05 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 24 Feb 2000 15:21:05 -0000 Date: Thu, 24 Feb 2000 08:18:02 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: Majordomo mailing list Subject: Re: Newbie Question (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In case Toby's note didn't make it to the list... Seth Kurtzberg Machine Independent Software Cell (602) 478-5511 Fax: (480) 614-8909 email: seth@cql.com pager: 888-605-9296 or email 6059296@skytel.com ---------- Forwarded message ---------- Date: Thu, 24 Feb 2000 07:31:51 -0500 From: Toby Bluhm To: Seth Kurtzberg Subject: Re: Newbie Question A great site for pre-compiled Solaris stuff . . . . http://smc.vnet.net/solaris_2.5.html Seth Kurtzberg wrote: > Unfortunately, Sun no longer includes the C compiler with the Solaris > distribution. You either have to (1) buy the C compiler or (2, better) > download the GNU compiler already built for Solaris. > > Seth Kurtzberg > Machine Independent Software > Cell (602) 478-5511 > Fax: (480) 614-8909 > email: seth@cql.com > pager: 888-605-9296 or email 6059296@skytel.com > > On Wed, 23 Feb 2000, Wilson, Sue LCC wrote: > > > I am new to Installing MajorDomo and I cannot get the wrapper to work. I > > have never done a makefile or wrapper before sooo...any help would be > > appreciated. Thanks in advance. > > > > I am trying to install Majordomo Version 1.94.5 on a SunSolaris 2.5 system. > > > > > > When I do " make wrapper" this is what I get: > > cc -DBIN=\"/export/opt/majordomo-1.94.5\" > > -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" > > -DHOME=\"HOME=/export/opt/majordomo-1.94.5\" -DSHELL=\"SHELL=/bin/sh\" > > -DMAJORDOMO_CF=\"MAJORDOMO_CF=/export/opt/majordomo-1.94.5/majordomo.cf\" > > -DPOSIX_UID=501 -DPOSIX_GID=501 -o wrapper wrapper.c > > /usr/ucb/cc: language optional software package not installed > > *** Error code 1 > > make: Fatal error: Command failed for target `wrapper' > > -- Toby Bluhm tkb@mr.marconimed.com 440-483-5323 From majordomo-users-owner Thu Feb 24 11:13:51 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19717; Thu, 24 Feb 2000 11:00:45 -0800 (PST) Received: from sporter.bestdist.com (proxy.bestdist.com [216.77.43.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA19705 for ; Thu, 24 Feb 2000 11:00:34 -0800 (PST) Received: from bestdist.com (IDENT:sporter@localhost.localdomain [127.0.0.1]) by sporter.bestdist.com (8.9.3/8.9.3) with ESMTP id OAA16930 for ; Thu, 24 Feb 2000 14:18:52 -0500 Message-ID: <38B5841C.33B5AB6A@bestdist.com> Date: Thu, 24 Feb 2000 14:18:52 -0500 From: Sean Porterfield Organization: Best Distributing Co. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: "majordomo-users@greatcircle.com" Subject: show subscribed address Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I looked through the FAQ and README, but didn't find what I was looking for. Perhaps it's not there, or I don't know what to search on. I'm trying to add the user's email address to the body of the mail such as "You are subscribed to the $LIST as $EMAIL" but I'm not sure of the proper variable. I tried $SENDER but that seems to be my majordomo-owner alias. Anyone know how to set this up properly? TIA! From majordomo-users-owner Thu Feb 24 11:30:25 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA19847; Thu, 24 Feb 2000 11:11:16 -0800 (PST) Received: from hotmail.com (f35.law8.hotmail.com [216.33.241.35]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id LAA19840 for ; Thu, 24 Feb 2000 11:11:10 -0800 (PST) Received: (qmail 96247 invoked by uid 0); 24 Feb 2000 19:29:29 -0000 Message-ID: <20000224192929.96246.qmail@hotmail.com> Received: from 198.204.133.71 by www.hotmail.com with HTTP; Thu, 24 Feb 2000 11:29:28 PST X-Originating-IP: [198.204.133.71] From: "D B" To: thaths@netscape.com, majordomo-users@GreatCircle.COM Subject: ROUND TWO RE: example of running the 'bounce' script Date: Thu, 24 Feb 2000 14:29:28 EST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I read the FAQ section you mentioned in the replying email, but it still doesn't seem to make sense. Here's my understanding, please correct me if I'm wrong: If a message is sent out from a mailing list and bounces, it will return to the designated "list-owner". If the "list-owner" is someone's actual email address, that address would receive all the bounces without any intervention from 'bounce' or any other process. My conclusion would be, I need to somehow call the 'bounce' script from my "list-owner" mail alias - instead of putting my email address as the alias. That way I'm out of the loop. An example would be: content: "|/scripts/majordomo/resend -l content content-list" content-list: :include:/scripts/majordomo/lists/content content-owner: email@address.com OR content-owner: "call the bounce script to remove this email address" An I completely off base? I cannot see how the preceding alias entries would have anything to do with a bounces list even if the alias file looked like the following: content: "|/scripts/majordomo/resend -l content content-list" content-list: :include:/scripts/majordomo/lists/content content-owner: email@address.com bounces: "|/scripts/majordomo/resend -l bounces bounces-list" bounces-list: :include:/scripts/majordomo/lists/bounces bounces-owner: email@address.com Thanks in advance for your help -DB >D B proclaimed: > > I am looking for an example (code fragment) for using the 'bounce' >script. I > > assume it can be used from a Sendmail alias, but I would like to see an > > example usage. > >http://www.greatcircle.com/majordomo/majordomo-faq.html#3.2 > >The only thing that you need to do in /etc/aliases is add the entries (just >like you'd do for any newly created mailing list) for the bounces list. > >Thaths >-- > "I have two questions for you: How much? and I'll take it." > -- Homer J. Simpson >Sudhakar C13n http://people.netscape.com/thaths/ Lead Indentured Slave ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From majordomo-users-owner Thu Feb 24 12:13:58 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA20340; Thu, 24 Feb 2000 11:54:08 -0800 (PST) Received: from server.postmodern.com (server.postmodern.com [216.240.39.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA20333 for ; Thu, 24 Feb 2000 11:54:00 -0800 (PST) Received: from mail.rentpayment.com ([38.194.38.165]) by server.postmodern.com (8.8.5/mcb-980201) with ESMTP id MAA16556 for ; Thu, 24 Feb 2000 12:11:21 -0800 (PST) Received: from chesternet.net ([207.87.127.98]) by mail.rentpayment.com (Netscape Messaging Server 4.1) with ESMTP id FQGARO00.605; Thu, 24 Feb 2000 15:11:48 -0500 Message-ID: <38B59038.A3CD8247@chesternet.net> Date: Thu, 24 Feb 2000 15:10:32 -0500 From: "Daniel chester" Reply-To: talamar@chesternet.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Seth Kurtzberg CC: Majordomo mailing list Subject: Re: Newbie Question (fwd) References: Content-Type: multipart/mixed; boundary="------------84DA628DAEF3085A0C461ABD" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. --------------84DA628DAEF3085A0C461ABD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit easier to remember www.sunfreeware.com It's the new revision to the site with precompiles for all the Solaris Versions. Seth Kurtzberg wrote: > In case Toby's note didn't make it to the list... > > Seth Kurtzberg > Machine Independent Software > Cell (602) 478-5511 > Fax: (480) 614-8909 > email: seth@cql.com > pager: 888-605-9296 or email 6059296@skytel.com > > ---------- Forwarded message ---------- > Date: Thu, 24 Feb 2000 07:31:51 -0500 > From: Toby Bluhm > To: Seth Kurtzberg > Subject: Re: Newbie Question > > A great site for pre-compiled Solaris stuff . . . . > http://smc.vnet.net/solaris_2.5.html > > Seth Kurtzberg wrote: > > > Unfortunately, Sun no longer includes the C compiler with the Solaris > > distribution. You either have to (1) buy the C compiler or (2, better) > > download the GNU compiler already built for Solaris. > > > > Seth Kurtzberg > > Machine Independent Software > > Cell (602) 478-5511 > > Fax: (480) 614-8909 > > email: seth@cql.com > > pager: 888-605-9296 or email 6059296@skytel.com > > > > On Wed, 23 Feb 2000, Wilson, Sue LCC wrote: > > > > > I am new to Installing MajorDomo and I cannot get the wrapper to work. I > > > have never done a makefile or wrapper before sooo...any help would be > > > appreciated. Thanks in advance. > > > > > > I am trying to install Majordomo Version 1.94.5 on a SunSolaris 2.5 system. > > > > > > > > > When I do " make wrapper" this is what I get: > > > cc -DBIN=\"/export/opt/majordomo-1.94.5\" > > > -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" > > > -DHOME=\"HOME=/export/opt/majordomo-1.94.5\" -DSHELL=\"SHELL=/bin/sh\" > > > -DMAJORDOMO_CF=\"MAJORDOMO_CF=/export/opt/majordomo-1.94.5/majordomo.cf\" > > > -DPOSIX_UID=501 -DPOSIX_GID=501 -o wrapper wrapper.c > > > /usr/ucb/cc: language optional software package not installed > > > *** Error code 1 > > > make: Fatal error: Command failed for target `wrapper' > > > > > -- > Toby Bluhm > tkb@mr.marconimed.com > 440-483-5323 --------------84DA628DAEF3085A0C461ABD Content-Type: text/x-vcard; charset=us-ascii; name="talamar.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Daniel Chester Content-Disposition: attachment; filename="talamar.vcf" begin:vcard n:Chester;Daniel tel;work:440-734-9348 x-mozilla-html:TRUE url:www.rentpayment.com org:RentPayment.COM adr:;;;;;; version:2.1 email;internet:dan@chesternet.net title:Technical Analyst fn:Daniel Chester end:vcard --------------84DA628DAEF3085A0C461ABD-- From majordomo-users-owner Thu Feb 24 15:47:05 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA22630; Thu, 24 Feb 2000 15:34:10 -0800 (PST) Received: from chamber.dna.fi (chamber.dna.fi [62.236.155.125]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id PAA22622 for ; Thu, 24 Feb 2000 15:34:03 -0800 (PST) Received: (qmail 14908 invoked by uid 501); 25 Feb 2000 01:52:24 +0200 Date: Fri, 25 Feb 2000 01:52:24 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: Sean Porterfield Cc: "majordomo-users@greatcircle.com" Subject: Re: show subscribed address Message-ID: <20000225015224.C14788@chamber.dna.fi> Reply-To: Mikko.Hanninen@iki.fi Mail-Followup-To: Sean Porterfield , "majordomo-users@greatcircle.com" References: <38B5841C.33B5AB6A@bestdist.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.1.4i In-Reply-To: <38B5841C.33B5AB6A@bestdist.com>; from sporter@bestdist.com on Thu, Feb 24, 2000 at 02:18:52PM -0500 Organization: None Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Sean Porterfield wrote on Thu, 24 Feb 2000: > I'm trying to add the user's email address to the body of the mail such > as "You are subscribed to the $LIST as $EMAIL" but I'm not sure of the > proper variable. I tried $SENDER but that seems to be my > majordomo-owner alias. This can't be done without modifying Majordomo. Majordomo sends the exact same email to each recipient, changing this would require rewriting parts of Majordomo. Mikko -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Did you know that 7/5 people don't know how to use fractions? From majordomo-users-owner Thu Feb 24 16:00:07 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA22619; Thu, 24 Feb 2000 15:32:23 -0800 (PST) Received: from chamber.dna.fi (chamber.dna.fi [62.236.155.125]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id PAA22612 for ; Thu, 24 Feb 2000 15:32:16 -0800 (PST) Received: (qmail 14897 invoked by uid 501); 25 Feb 2000 01:50:36 +0200 Date: Fri, 25 Feb 2000 01:50:36 +0200 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= To: mendes Cc: majordomo-users@GreatCircle.COM Subject: Re: Getting better but I still have problems .... Message-ID: <20000225015036.B14788@chamber.dna.fi> Reply-To: Mikko.Hanninen@iki.fi Mail-Followup-To: mendes , majordomo-users@GreatCircle.COM References: <00022412075703.00766@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.1.4i In-Reply-To: <00022412075703.00766@localhost.localdomain>; from mendes@mgconecta.com.br on Thu, Feb 24, 2000 at 12:04:29PM -0200 Organization: None Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk mendes wrote on Thu, 24 Feb 2000: > The list has two members. Using one member's account I sent an > email to the list. The other member received the message but the sender did not. > Any suggestions? Are these members local? sendmail may be doing some "optimizing" and not sending the email to someone who originally sent it (on the local system). There's a configuration directive for sendmail which you can use to tell sendmail that users should be copied their own posts. I don't remember what it is, but searching the list archives should help, it's been answered at least a few times. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // wiz@iki.fi // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Make it idiot-proof and someone will make a better idiot. From majordomo-users-owner Thu Feb 24 16:15:06 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA22692; Thu, 24 Feb 2000 15:43:17 -0800 (PST) Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA22685 for ; Thu, 24 Feb 2000 15:43:11 -0800 (PST) Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id PAA12464 for ; Thu, 24 Feb 2000 15:57:30 -0800 (PST) Received: from netscape.com ([207.1.145.44]) by judge.mcom.com (Netscape Messaging Server 4.03) with ESMTP id FQGLEC01.H47; Thu, 24 Feb 2000 16:01:24 -0800 Message-ID: <38B5C654.39B0C25@netscape.com> Date: Thu, 24 Feb 2000 16:01:24 -0800 From: Sudhakar Chandrasekharan Organization: I didn't do it, nobody saw me do it, no one can prove a thing X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.13 i686) X-Accept-Language: en, fr MIME-Version: 1.0 To: Aradi Szilard CC: majordomo-users@GreatCircle.COM Subject: Re: help me References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Aradi Szilard proclaimed: > I`m from Hungary. I`ve got Debian Linux 2.1. The kernel version is > 2.2.12. My sendmail program is exim. I installed majordomo firstly and it > doesn`t work. I follow the install file correctly. The config-test ran > without any errors. Save yourself a lot of trouble by installing the Debian package for majordomo that is in Debian 2.1 > I made a test list by the newlist file. I wrote the > neccessary lines into /etc/aliases. But if i wrote a mail to majordomo > with any command, it doesn`t work and in the exim`s mainlog there`s the > following error message: Neither the system_aliases director nor the > address_pipe transport set a uid for local delivery of > |/usr/local/majordomo-1.94.5/wrapper majordomo. You should have something like so in your /etc/exim.conf file: system_aliases: driver = aliasfile file_transport = address_file pipe_transport = address_pipe file = /etc/aliases search_type = lsearch user = majordom Thaths -- "I have two questions for you: How much? and I'll take it." -- Homer J. Simpson Sudhakar C13n http://people.netscape.com/thaths/ Lead Indentured Slave From majordomo-users-owner Thu Feb 24 16:30:05 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA22805; Thu, 24 Feb 2000 15:57:59 -0800 (PST) Received: from guinness.digisle.net (guinness.digisle.net [167.216.152.33]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA22798 for ; Thu, 24 Feb 2000 15:57:53 -0800 (PST) Received: from visi.com (dhcp-vpn-sf-64-21.digisle.com [172.16.64.21]) by guinness.digisle.net (8.9.3/8.9.3/digisle) with ESMTP id AAA22829; Fri, 25 Feb 2000 00:15:59 GMT Message-ID: <38B5C9BD.3651235@visi.com> Date: Thu, 24 Feb 2000 18:15:57 -0600 From: David Barr X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: D B CC: thaths@netscape.com, majordomo-users@GreatCircle.COM Subject: Re: ROUND TWO RE: example of running the 'bounce' script References: <20000224192929.96246.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Automated bounce handling is not something you can just whip together lightly (if it were, it would have been done by now). Majordomo 1 just isn't written to make this easy. You'll have much better luck with Majordomo 2. See the FAQ for details on where to get it. --Dave D B wrote: > > I read the FAQ section you mentioned in the replying email, but it still > doesn't seem to make sense. > > Here's my understanding, please correct me if I'm wrong: > > If a message is sent out from a mailing list and bounces, it will return to > the designated "list-owner". If the "list-owner" is someone's actual email > address, that address would receive all the bounces without any intervention > from 'bounce' or any other process. My conclusion would be, I need to > somehow call the 'bounce' script from my "list-owner" mail alias - instead > of putting my email address as the alias. That way I'm out of the loop. An > example would be: > > content: "|/scripts/majordomo/resend -l content content-list" > content-list: :include:/scripts/majordomo/lists/content > content-owner: email@address.com > > OR > > content-owner: "call the bounce script to remove this email address" > > An I completely off base? I cannot see how the preceding alias entries would > have anything to do with a bounces list even if the alias file looked like > the following: > > content: "|/scripts/majordomo/resend -l content content-list" > content-list: :include:/scripts/majordomo/lists/content > content-owner: email@address.com > > bounces: "|/scripts/majordomo/resend -l bounces bounces-list" > bounces-list: :include:/scripts/majordomo/lists/bounces > bounces-owner: email@address.com > > Thanks in advance for your help > > -DB > > >D B proclaimed: > > > I am looking for an example (code fragment) for using the 'bounce' > >script. I > > > assume it can be used from a Sendmail alias, but I would like to see an > > > example usage. > > > >http://www.greatcircle.com/majordomo/majordomo-faq.html#3.2 > > > >The only thing that you need to do in /etc/aliases is add the entries (just > >like you'd do for any newly created mailing list) for the bounces list. > > > >Thaths > >-- > > "I have two questions for you: How much? and I'll take it." > > -- Homer J. Simpson > >Sudhakar C13n http://people.netscape.com/thaths/ Lead Indentured Slave > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com From majordomo-users-owner Thu Feb 24 16:46:34 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA22790; Thu, 24 Feb 2000 15:55:51 -0800 (PST) Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA22783 for ; Thu, 24 Feb 2000 15:55:43 -0800 (PST) Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id QAA14162 for ; Thu, 24 Feb 2000 16:10:03 -0800 (PST) Received: from netscape.com ([207.1.145.44]) by judge.mcom.com (Netscape Messaging Server 4.03) with ESMTP id FQGLZE01.44L; Thu, 24 Feb 2000 16:14:02 -0800 Message-ID: <38B5C94A.C8510DC5@netscape.com> Date: Thu, 24 Feb 2000 16:14:02 -0800 From: Sudhakar Chandrasekharan Organization: I didn't do it, nobody saw me do it, no one can prove a thing X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.13 i686) X-Accept-Language: en, fr MIME-Version: 1.0 To: D B CC: majordomo-users@GreatCircle.COM Subject: Re: ROUND TWO RE: example of running the 'bounce' script References: <20000224192929.96246.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk D B proclaimed: > Here's my understanding, please correct me if I'm wrong: > > If a message is sent out from a mailing list and bounces, it will return to > the designated "list-owner". You are on track so far. > If the "list-owner" is someone's actual email > address, that address would receive all the bounces without any intervention > from 'bounce' or any other process. My conclusion would be, I need to > somehow call the 'bounce' script from my "list-owner" mail alias - instead > of putting my email address as the alias. That way I'm out of the loop. An > example would be: Here is where you are making the mistake. list-owner should point to a real existing user (It is convenient to have one system-wide account to handle all bounced / administrative messages from the mailing lists). The real user should check their email every so often. When this user see that emails to some addresses are bouncing consistently for a few days the user should run the bounce script from the command line like so: /scriptsmajordomo/path/to/bounce list-name email@address.that.bounces [replace list-name with the list from which you want the user moved to the bounces list and email@address.... with the person's email addr.] Read the manpage for the bounce script. You have to create a file called ~/.majordomo where you would have to place the password for the various lists. > content: "|/scripts/majordomo/resend -l content content-list" > content-list: :include:/scripts/majordomo/lists/content > content-owner: email@address.com > > OR > > content-owner: "call the bounce script to remove this email address" The first. > content: "|/scripts/majordomo/resend -l content content-list" > content-list: :include:/scripts/majordomo/lists/content > content-owner: email@address.com > > bounces: "|/scripts/majordomo/resend -l bounces bounces-list" > bounces-list: :include:/scripts/majordomo/lists/bounces > bounces-owner: email@address.com You are right about creating aliases for bounces in /etc/aliases. I think the basic misunderstanding came from not knowing that the bounce script has to be run manually on the command line. There are other solutions that claim to handle bounces automagically. But I have't tried any of them. They all sound too complex and also clearly state that their ability to handle bounces is not perfect. Thaths -- "I have two questions for you: How much? and I'll take it." -- Homer J. Simpson Sudhakar C13n http://people.netscape.com/thaths/ Lead Indentured Slave From majordomo-users-owner Thu Feb 24 19:00:13 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id SAA24484; Thu, 24 Feb 2000 18:48:50 -0800 (PST) Received: from mail.neta.com (nfs.neta.com [206.124.164.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with SMTP id SAA24477 for ; Thu, 24 Feb 2000 18:48:44 -0800 (PST) Received: (qmail 2409 invoked from network); 25 Feb 2000 03:07:05 -0000 Received: from functionalprogramming.cql.com (HELO functionalprogramming.com) (seth@208.194.82.228) by nfs.neta.com with SMTP; 25 Feb 2000 03:07:05 -0000 Date: Thu, 24 Feb 2000 20:04:00 -0700 (MST) From: Seth Kurtzberg X-Sender: seth@functionalprogramming.com To: Majordomo mailing list cc: abela@4cm.com Subject: Majordomo Question (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I just have three simple questions. 1. When I changed the listconfig, it allowed it, but I have a little problem. 2. I can't seem to get the header & footer to work. 3. I can't seem to get the subject-prefix to work. Now, I'm new to majorodomo configuring, but have 5+ years in html, and a few years in other languages... but this thing has got me really confussed! Thanks, either way. John B. Abela abela@4cm.com From majordomo-users-owner Fri Feb 25 02:30:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id CAA29383; Fri, 25 Feb 2000 02:16:24 -0800 (PST) Received: from Trademart-1.ednet.ns.ca (Trademart-1.EDnet.NS.CA [142.227.51.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id CAA29374 for ; Fri, 25 Feb 2000 02:15:54 -0800 (PST) Received: from iolan15.ednet.ns.ca ([142.227.51.25] helo=ednet.ns.ca) by Trademart-1.ednet.ns.ca with esmtp (Exim 3.13 #2) id 12OI4g-0002qA-00 for majordomo-users@greatcircle.com; Fri, 25 Feb 2000 06:34:18 -0400 Message-ID: <38B65AA6.1D77BC35@ednet.ns.ca> Date: Fri, 25 Feb 2000 06:34:14 -0400 From: Patrick Boutilier X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Incomplete Digests Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Majordomo 1.94.5 RedHat 6.1 I have a problem with majordomo sending incomplete digest. I have majordomo setup so that each message sent to list "test" appears in the $digest_dir/test-digest directory but when it comes time to send a digest (either automatically or by forcing it) majordomo always misses 2-3 of the messages. Of course this causes majordomo to send a one message digest afterwards each time a new message is sent to list "test" because there are left over messages that the original digest missed that are more than a day old. Any thoughts or ideas? I have searched the archives but didn't see anything there. From majordomo-users-owner Fri Feb 25 05:00:06 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id EAA02621; Fri, 25 Feb 2000 04:51:23 -0800 (PST) Received: from noether.central.cranfield.ac.uk (mailsvr.central.cranfield.ac.uk [138.250.48.46]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA02614 for ; Fri, 25 Feb 2000 04:51:18 -0800 (PST) Received: from neumann.ccc.cranfield.ac.uk ([138.250.24.137] ident=cc047) by noether.central.cranfield.ac.uk with esmtp (Exim 3.13 #1) id 12OKV6-0007ti-00; Fri, 25 Feb 2000 13:09:44 +0000 Date: Fri, 25 Feb 2000 13:09:44 +0000 (GMT) From: Jeffrey Goldberg X-Sender: cc047@neumann.ccc.cranfield.ac.uk Reply-To: Jeffrey Goldberg To: Aradi Szilard cc: majordomo-users@greatcircle.com Subject: Re: help me In-Reply-To: Message-ID: Organization: Cranfield University Computer Centre MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [mailed and posted] On Wed, 23 Feb 2000, Aradi Szilard wrote: > I`m from Hungary. Pontosabb, a Budapest Muszaki Egytememrol irsz. Nem jol ismerem, mert en ELTEn dolgoztam. > I wrote the neccessary lines into /etc/aliases. But if i wrote a mail > to majordomo with any command, it doesn`t work and in the exim`s > mainlog there`s the > following error message: Neither the system_aliases director nor the > address_pipe transport set a uid for local delivery of > |/usr/local/majordomo-1.94.5/wrapper majordomo. The exim FAQ at http://www.exim.org/ has pointers to information about running exim with majordomo. The problem is that because you haven't set up "user" and "group" for your aliases file director in exim, it is not allowing pipes. It is best to set up a separate director for majordomo aliases and keep the majordomo aliases in a separate file form the other aliases. Here is (almost) what I have majordomo_aliases: driver = aliasfile file_transport = address_file pipe_transport = address_pipe file = TABLES/majordomo.aliases search_type = dbm modemask=002 user = majordom group = majordom -j -- Jeffrey Goldberg +44 (0)1234 750 111 x 2826 Cranfield Computer Centre FAX 751 814 J.Goldberg@Cranfield.ac.uk http://WWW.Cranfield.ac.uk/public/cc/cc047/ Relativism is the triumph of authority over truth, convention over justice. From majordomo-users-owner Fri Feb 25 07:44:20 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA03986; Fri, 25 Feb 2000 07:26:40 -0800 (PST) Received: from student.ednet.ns.ca (Student.EDnet.NS.CA [142.227.51.33]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA03978; Fri, 25 Feb 2000 07:26:31 -0800 (PST) Received: from bart.ednet.ns.ca ([142.227.51.200] helo=ednet.ns.ca ident=boutilpj) by student.ednet.ns.ca with esmtp (Exim 3.03 #4) id 12OMu9-0008Qc-00; Fri, 25 Feb 2000 11:43:45 -0400 Message-ID: <38B6A3F7.C78BD625@ednet.ns.ca> Date: Fri, 25 Feb 2000 11:47:03 -0400 From: Patrick Boutilier X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.15pre2 i686) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Subject: Re: Incomplete Digests References: <38B65AA6.1D77BC35@ednet.ns.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk With some help from the local Perl guru we have solved the problem. The problem was that the digest program was not sorting the files from the $digest_dir/test-digest directory properly. For example if there were files 001 through 017 it would go through them in what appears to be random order. The digest code would only keep looping until it hit message 017 then stop, leaving usually 3 to 5 messages behind. The fix was just a one liner on line 178 of digest. Orginal line: foreach (@files) { Fixed line: foreach (sort @files) { This fix sorts the files from lowest number to highest and therefore gets all the messages properly. Not sure why this bug hasn't show up before but it may have crept up on us because we are using a Reiser file system. Patrick Boutilier wrote: > Majordomo 1.94.5 > RedHat 6.1 > > I have a problem with majordomo sending incomplete digest. I have > majordomo setup so that each message sent to list "test" appears in the > $digest_dir/test-digest directory but when it comes time to send a > digest (either automatically or by forcing it) majordomo always misses > 2-3 of the messages. > > Of course this causes majordomo to send a one message digest afterwards > each time a new message is sent to list "test" because there are left > over messages that the original digest missed that are more than a day > old. Any thoughts or ideas? > > I have searched the archives but didn't see anything there. From majordomo-users-owner Sat Feb 26 16:54:55 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA24329; Sat, 26 Feb 2000 16:47:09 -0800 (PST) Received: from adsl-77-249-201.jax.bellsouth.net (adsl-77-249-201.jax.bellsouth.net [216.77.249.201]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA24322 for ; Sat, 26 Feb 2000 16:47:03 -0800 (PST) Received: from adsl-77-249-201.jax.bellsouth.net (IDENT:pdavis@adsl-77-249-201.jax.bellsouth.net [216.77.249.201]) by adsl-77-249-201.jax.bellsouth.net (8.9.3/8.9.3) with ESMTP id UAA04420 for ; Sat, 26 Feb 2000 20:10:55 -0500 Date: Sat, 26 Feb 2000 20:10:55 -0500 (EST) From: Paul E Davis X-Sender: pdavis@adsl-77-249-201.jax.bellsouth.net To: majordomo-users@greatcircle.com Subject: User Unknown error Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk For some reason my aliases do not seem to be working properly. I am totally lost on this one. If (from the same machine as majordomo) I send an email using "echo 'message' |mail majordomo@host" it works great. Goes where it is suppose to. However if I send mail through pine (same machine, pine connects to an IMAP server on same machine) it gives me user unknown. Same with sending from any where on the internet. Why would the aliases be strictly local? Could this be due to IMAP? To better give an idea, I am running RedHat 6.1. Thanks in advance. - Paul E Davis From majordomo-users-owner Sat Feb 26 21:54:54 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA27123; Sat, 26 Feb 2000 21:51:32 -0800 (PST) Received: from server1.mich.com (server1.mich.com [198.108.16.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA27116 for ; Sat, 26 Feb 2000 21:51:26 -0800 (PST) Received: from lindy.nuge.com (root@pm003-029.dialip.mich.com [207.74.178.93]) by server1.mich.com (8.9.3/8.9.3) with ESMTP id BAA19975; Sun, 27 Feb 2000 01:10:07 -0500 Received: from localhost (rtg@localhost) by lindy.nuge.com (8.9.3/8.9.3) with ESMTP id BAA13774; Sun, 27 Feb 2000 01:00:50 -0500 X-Authentication-Warning: lindy.nuge.com: rtg owned process doing -bs Date: Sun, 27 Feb 2000 01:00:49 -0500 (EST) From: Rick Green To: Paul E Davis cc: majordomo-users@GreatCircle.COM Subject: Re: User Unknown error 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, 26 Feb 2000, Paul E Davis wrote: > For some reason my aliases do not seem to be working properly. I am > totally lost on this one. If (from the same machine as majordomo) I send > an email using "echo 'message' |mail majordomo@host" it works great. > Goes where it is suppose to. However if I send mail through pine (same > machine, pine connects to an IMAP server on same machine) it gives me user > unknown. Same with sending from any where on the internet. Why would the > aliases be strictly local? Could this be due to IMAP? To better give an > idea, I am running RedHat 6.1. Thanks in advance. > > - Paul E Davis It appears to me that you took the option of defining your majordomo aliases in a separate file, and declaring that file in addition to /etc/aliases in sendmail.cf. When you change sendmail.cf, you must completely stop and restart the sendmail daemon. HUP doesn't force the config to be re-read. So the daemon doesn't know about the new aliases. The reason it appears to work when you use /bin/mail to send the message, is that mail spawns a new copy of sendmail to process the message, rather than talking to the daemon listening on port 25. Of course, the new copy has to read sendmail.cf for itself. -- Rick Green From majordomo-users-owner Sun Feb 27 04:11:14 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id EAA02719; Sun, 27 Feb 2000 04:06:02 -0800 (PST) Received: from adsl-77-249-201.jax.bellsouth.net (adsl-77-249-201.jax.bellsouth.net [216.77.249.201]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA02711 for ; Sun, 27 Feb 2000 04:05:56 -0800 (PST) Received: from adsl-77-249-201.jax.bellsouth.net (IDENT:pdavis@adsl-77-249-201.jax.bellsouth.net [216.77.249.201]) by adsl-77-249-201.jax.bellsouth.net (8.9.3/8.8.7) with ESMTP id HAA09242 for ; Sun, 27 Feb 2000 07:29:51 -0500 Date: Sun, 27 Feb 2000 07:29:51 -0500 (EST) From: Paul E Davis X-Sender: pdavis@adsl-77-249-201.jax.bellsouth.net To: majordomo-users@greatcircle.com Subject: Fixed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Please ignore my last post about the aliases. I completely forgot to run newaliases after adding the aliases for majordomo. - Paul E Davis From majordomo-users-owner Mon Feb 28 06:08:45 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA18383; Mon, 28 Feb 2000 05:58:30 -0800 (PST) Received: from kappa ([209.193.174.230]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA18376 for ; Mon, 28 Feb 2000 05:58:24 -0800 (PST) Received: from kappa ([127.0.0.1]) by kappa with Microsoft SMTPSVC(5.0.2172.1); Mon, 28 Feb 2000 00:23:47 -0500 Message-Id: <4.1.20000228002253.00a52a00@mailbox.bellatlantic.net> X-Sender: jeasterl@mailbox.bellatlantic.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 28 Feb 2000 00:23:47 -0500 To: majordomo-users@greatcircle.com From: Julian Easterling Subject: MAJORDOMO ABORT (mj_majordomo) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 28 Feb 2000 05:23:47.0982 (UTC) FILETIME=[FD5D8AE0:01BF81AB] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have been working on this problem for almost a week now. Looking a the various FAQ and other web sites just hasn't solve my problem. This list has been pretty good to me so far, so I would like to ask for your help. Let me describe the situation: I have Majordomo 1.94.5 running on Mandrake Linux 7.0. I have Perl 5.005_03 and Sendmail 8.9.3 All of my servers are host in julianscorner.com domain. I run a second domain: happyhourdc.com. This domain is where Majordomo is running. I have set up MX records in both domains to point to this machine as mailhost. Each domain is: mailhost.happyhourdc.com and mailhost.julianscorner.com Whenever I send email to the happyhourdc.com MX, my sendmail complains 550 Relaying denied. I have tried to set up sendmail to accept mail for both domains, but this hasn't worked yet. I turned my attention to getting majordomo responding to me on the julianscorner.com MX and I get the message below: >Return-Path: >Received: (from mail@localhost) > by jclx2.julianscorner.com (8.9.3/8.9.3) id QAA24945; > Sun, 27 Feb 2000 16:51:15 -0500 >Date: Sun, 27 Feb 2000 16:51:15 -0500 >Message-Id: <200002272151.QAA24945@jclx2.julianscorner.com> >X-Authentication-Warning: jclx2.julianscorner.com: mail set sender to >Majordomo-Owner@mailhost.julianscorner.com using -f >To: Majordomo-Owner@mailhost.julianscorner.com >From: Majordomo@happyhourdc.com >Subject: MAJORDOMO ABORT (mj_majordomo) >Reply-To: Majordomo@happyhourdc.com >Status: > >-- > > >MAJORDOMO ABORT (mj_majordomo)!! > >While running with an effective uid of 8 and an effective gid of 12 12, >Majordomo >ran into the following problems: >Unable to write to log file, check permissions on /home/majordom/runtime/Log >Unable to write to list directory $listdir, check permissions on >/home/majordom/lists I checked the permissions on these directory and majordom (user and group) own the directories and files. Once I get Majordomo to respond to me using the hostname in the julianscorner.com domain, I will need to get it to work in the happyhourdc.com. So if any of you know how to or know where I can find the information for Sendmail to work under both domain. Thanks. From majordomo-users-owner Mon Feb 28 09:23:42 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA20445; Mon, 28 Feb 2000 09:13:24 -0800 (PST) Received: from atiseaservices.sea.wantweb.net (mail1.sea.wantweb.net [24.236.14.6]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA20437 for ; Mon, 28 Feb 2000 09:13:17 -0800 (PST) Message-Id: <200002281713.JAA20437@honor.greatcircle.com> Received: from rag1488 ([24.236.12.48]) by atiseaservices.sea.wantweb.net (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with SMTP id net for ; Mon, 28 Feb 2005 09:28:37 -0800 From: "Raul A. Gallegos" To: "majordomo-users@greatcircle.com" Date: Mon, 28 Feb 2000 10:32:05 -0700 Reply-To: "Raul A. Gallegos" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: spam in mailing list Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello. Today I got a spam message on my mailing list. This was sent by a user who is not subscribed on the list. I'm using slackware linux 7.0 with default software sendmail and perl. mj version is 1.94.4. What can I forward to this list to show my settings. I have the message with headers as well as the logs from /var/log/messages is that is needed. Thanks anyone for this help. *** New look for ASMODEAN.NET. Click http://www.asmodean.net *** Email me raul@asmodean.net or icq me 5283055 From majordomo-users-owner Mon Feb 28 11:09:13 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA21493; Mon, 28 Feb 2000 11:05:00 -0800 (PST) Received: from mercury.libpubinc.com (mercury.libpubinc.com [208.249.203.55]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA21486 for ; Mon, 28 Feb 2000 11:04:54 -0800 (PST) Received: from dmoyer (dhcp93.libpubinc.com [208.249.203.93]) by mercury.libpubinc.com (8.9.3/8.9.3) with ESMTP id LAA12886; Mon, 28 Feb 2000 11:10:40 -0800 Message-Id: <4.2.2.20000228105203.00a46670@mercury.libpubinc.com> X-Sender: dmoyer@mercury.libpubinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 28 Feb 2000 11:10:24 -0800 To: Julian Easterling , majordomo-users@GreatCircle.COM From: Dave Moyer Subject: Re: MAJORDOMO ABORT (mj_majordomo) In-Reply-To: <4.1.20000228002253.00a52a00@mailbox.bellatlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >Let me describe the situation: >I have Majordomo 1.94.5 running on Mandrake Linux 7.0. I have Perl >5.005_03 and Sendmail 8.9.3 >All of my servers are host in julianscorner.com domain. I run a second >domain: happyhourdc.com. This domain is where Majordomo is running. I >have set up MX records in both domains to point to this machine as >mailhost. Each domain is: mailhost.happyhourdc.com and >mailhost.julianscorner.com >Whenever I send email to the happyhourdc.com MX, my sendmail complains 550 >Relaying denied. I have tried to set up sendmail to accept mail for both >domains, but this hasn't worked yet. I turned my attention to getting >majordomo responding to me on the julianscorner.com MX and I get the >message below: Ok, the first problem is one that's new to SendMail 8.9.3. In previous releases of SM promiscuous relaying was allowed by default (don't you just love the terms people come up with). In 8.9.3, anti-Spam became a hot issue so promiscuous relaying is now off by default. There are a couple of ways to fix the problem. First, set promiscuous relaying on. Bad idea. That would allow any one and anything to use your system as a Spam relay. It would probably result in our system eventually getting black holed and people who were subscribed to your list may not be allowed to get their messages because they would be blocked by their ISPs. The second and better solution would be to set up a limited relay. You will need to set up an access db with happyhourdc.com given the value RELAY. Make sure SendMail is set up to use the access db and that should take care of the relaying problem. Details on how to set up the access db and make sure SM is configured to use it are in the SM docs. > >Return-Path: > >Received: (from mail@localhost) > > by jclx2.julianscorner.com (8.9.3/8.9.3) id QAA24945; > > Sun, 27 Feb 2000 16:51:15 -0500 > >Date: Sun, 27 Feb 2000 16:51:15 -0500 > >Message-Id: <200002272151.QAA24945@jclx2.julianscorner.com> > >X-Authentication-Warning: jclx2.julianscorner.com: mail set sender to > >Majordomo-Owner@mailhost.julianscorner.com using -f > >To: Majordomo-Owner@mailhost.julianscorner.com > >From: Majordomo@happyhourdc.com > >Subject: MAJORDOMO ABORT (mj_majordomo) > >Reply-To: Majordomo@happyhourdc.com > >Status: > > > >-- > > > > > >MAJORDOMO ABORT (mj_majordomo)!! > > > >While running with an effective uid of 8 and an effective gid of 12 12, > >Majordomo > >ran into the following problems: > >Unable to write to log file, check permissions on /home/majordom/runtime/Log > >Unable to write to list directory $listdir, check permissions on > >/home/majordom/lists This one is a bit more difficult. Double check the groups table. On RedHat, uid 8 and gid 12 are both mail. In the MD install instructions, it tells you to set the owner of all to MD files and directories to majordomo and the group to daemon. However, if Mandrake has the same id definitions, try changing the group on all of the MD files and directories to mail. >I checked the permissions on these directory and majordom (user and group) >own the directories and files. Once I get Majordomo to respond to me using >the hostname in the julianscorner.com domain, I will need to get it to work >in the happyhourdc.com. So if any of you know how to or know where I can >find the information for Sendmail to work under both domain. Thanks. Hope this helps Dave From majordomo-users-owner Mon Feb 28 12:38:45 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA22293; Mon, 28 Feb 2000 12:35:49 -0800 (PST) Received: from gainesvi.gagainesvi.fsc.usda.gov (gainesvi.gagainesvi.fsc.usda.gov [199.147.136.191]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA22278 for ; Mon, 28 Feb 2000 12:35:29 -0800 (PST) Received: from DELL_GIS by gainesvi.gagainesvi.fsc.usda.gov with SMTP (8.7.6/itc-cust.Revision: 1.11 $) id VAA10054; Mon, 28 Feb 2000 21:08:51 GMT Message-Id: <4.1.20000228155918.00a10b20@gagainesvi.fsc.usda.gov> X-Sender: aburns@gagainesvi.fsc.usda.gov X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 28 Feb 2000 16:03:22 -0500 To: Majordomo-users@GreatCircle.COM From: Anthony G Burns Subject: Bounce Message Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Majordomo users Everything was working just fine and now i suddenly start getting these messages when I send stuff out to my list. I am the owner of the list and the bounces only happen to me, tt seems to work just fine when other list members send messages. Subject: BOUNCE list_name @domain.gov: Admin request of type /\bcancel\b/i at line 7 Admin request of type /\bcancel\b/i at line 9 Any ideas where to start. I have been using Majordomo about 3 months and its the first bounce message I'm received since I've got the list running. Thanks Anthony X-UIDL: 9eb790e81157ddf32238477a727903c3 From majordomo-users-owner Mon Feb 28 13:23:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA22654; Mon, 28 Feb 2000 13:15:58 -0800 (PST) Received: from server10.quality.org (server10.quality.org [199.181.80.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA22647 for ; Mon, 28 Feb 2000 13:15:52 -0800 (PST) Received: from localhost (help@localhost) by server10.quality.org (8.9.3/8.9.3) with ESMTP id QAA21465; Mon, 28 Feb 2000 16:29:58 -0500 (EST) Date: Mon, 28 Feb 2000 16:29:58 -0500 (EST) From: "Bill Casti (System Admin)" To: Julian Easterling cc: majordomo-users@GreatCircle.COM Subject: Re: MAJORDOMO ABORT (mj_majordomo) In-Reply-To: <4.1.20000228002253.00a52a00@mailbox.bellatlantic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Have you tried putting the domain you're trying to relay into your /etc/mail/relay-domains file and then restarting sendmail? Bill On Mon, 28 Feb 2000, Julian Easterling wrote: > I have been working on this problem for almost a week now. Looking a the > various FAQ and other web sites just hasn't solve my problem. This list > has been pretty good to me so far, so I would like to ask for your help. > Let me describe the situation: > I have Majordomo 1.94.5 running on Mandrake Linux 7.0. I have Perl > 5.005_03 and Sendmail 8.9.3 > All of my servers are host in julianscorner.com domain. I run a second > domain: happyhourdc.com. This domain is where Majordomo is running. I > have set up MX records in both domains to point to this machine as > mailhost. Each domain is: mailhost.happyhourdc.com and > mailhost.julianscorner.com > Whenever I send email to the happyhourdc.com MX, my sendmail complains 550 > Relaying denied. I have tried to set up sendmail to accept mail for both > domains, but this hasn't worked yet. I turned my attention to getting > majordomo responding to me on the julianscorner.com MX and I get the > message below: > > >Return-Path: > >Received: (from mail@localhost) > > by jclx2.julianscorner.com (8.9.3/8.9.3) id QAA24945; > > Sun, 27 Feb 2000 16:51:15 -0500 > >Date: Sun, 27 Feb 2000 16:51:15 -0500 > >Message-Id: <200002272151.QAA24945@jclx2.julianscorner.com> > >X-Authentication-Warning: jclx2.julianscorner.com: mail set sender to > >Majordomo-Owner@mailhost.julianscorner.com using -f > >To: Majordomo-Owner@mailhost.julianscorner.com > >From: Majordomo@happyhourdc.com > >Subject: MAJORDOMO ABORT (mj_majordomo) > >Reply-To: Majordomo@happyhourdc.com > >Status: > > > >-- > > > > > >MAJORDOMO ABORT (mj_majordomo)!! > > > >While running with an effective uid of 8 and an effective gid of 12 12, > >Majordomo > >ran into the following problems: > >Unable to write to log file, check permissions on /home/majordom/runtime/Log > >Unable to write to list directory $listdir, check permissions on > >/home/majordom/lists > > I checked the permissions on these directory and majordom (user and group) > own the directories and files. Once I get Majordomo to respond to me using > the hostname in the julianscorner.com domain, I will need to get it to work > in the happyhourdc.com. So if any of you know how to or know where I can > find the information for Sendmail to work under both domain. Thanks. > From majordomo-users-owner Mon Feb 28 13:38:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA22775; Mon, 28 Feb 2000 13:31:00 -0800 (PST) Received: from mercury.libpubinc.com (mercury.libpubinc.com [208.249.203.55]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA22768 for ; Mon, 28 Feb 2000 13:30:54 -0800 (PST) Received: from dmoyer (dhcp93.libpubinc.com [208.249.203.93]) by mercury.libpubinc.com (8.9.3/8.9.3) with ESMTP id NAA15482; Mon, 28 Feb 2000 13:49:54 -0800 Message-Id: <4.2.2.20000228134618.00aae4d0@mercury.libpubinc.com> X-Sender: dmoyer@mercury.libpubinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 28 Feb 2000 13:49:52 -0800 To: "Raul A. Gallegos" , "majordomo-users@greatcircle.com" From: Dave Moyer Subject: Re: spam in mailing list In-Reply-To: <200002281713.JAA20437@honor.greatcircle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Set the "restrict_post" parameter in the list config file to the users list (i.e. restrict_post = {file name of list addresses} with out the curly braces, of course) At 10:32 AM 2/28/00 -0700, Raul A. Gallegos wrote: >Hello. Today I got a spam message on my mailing list. This was sent by a >user who is not subscribed on the list. I'm using slackware linux 7.0 >with default >software sendmail and perl. mj version is 1.94.4. What can I forward to >this list to show my settings. I have the message with headers as well as >the logs from >/var/log/messages is that is needed. > >Thanks anyone for this help. > > >*** New look for ASMODEAN.NET. Click http://www.asmodean.net >*** Email me raul@asmodean.net or icq me 5283055 From majordomo-users-owner Mon Feb 28 13:53:42 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA22820; Mon, 28 Feb 2000 13:36:54 -0800 (PST) Received: from mail.bcpl.net (mail.bcpl.net [204.255.212.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA22813 for ; Mon, 28 Feb 2000 13:36:47 -0800 (PST) Received: from localhost (fold@localhost) by mail.bcpl.net (8.9.1/8.9.1) with ESMTP id QAA21044 for ; Mon, 28 Feb 2000 16:55:46 -0500 (EST) Date: Mon, 28 Feb 2000 16:55:46 -0500 (EST) From: Chip Old To: Majordomo Users List Subject: Re: spam in mailing list In-Reply-To: <200002281713.JAA20437@honor.greatcircle.com> Message-ID: X-Organization: BCPL.NET Internet Services MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Mon, 28 Feb 2000, Raul A. Gallegos wrote to majordomo-users@greatcircle.com: > Hello. Today I got a spam message on my mailing list. This was sent > by a user who is not subscribed on the list. I'm using slackware > linux 7.0 with default software sendmail and perl. mj version is > 1.94.4. What can I forward to this list to show my settings. I have > the message with headers as well as the logs from /var/log/messages is > that is needed. Look for this section of your list configuration file: # restrict_post [restrict_post] (undef) # If defined only address listed in one of the files (colon or # space separated) can post to the mailing list. This is less # useful than it seems it should be since there is no way to create # these files if you do not have access to the machine running # resend. This mechanism will be replaced in a future version of # majordomo/resend. restrict_post = listname Substitute the name of your list for "listname" to prevent anyone not subscribed from posting to the list. This will prevent non-subscribers from spamming the list. If a subscriber spams the list, unsubscribe him. -- Chip Old (Francis E. Old) E-Mail: fold@bcpl.net Manager, BCPL Network Services Voice: 410-887-6180 Manager, BCPL.NET Internet Services FAX: 410-887-2091 Baltimore County Public Library ICBM: 39.39910 N 320 York Road 76.60300 W Towson, Maryland 21204 U.S.A. From majordomo-users-owner Mon Feb 28 14:08:46 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA23134; Mon, 28 Feb 2000 14:08:20 -0800 (PST) Received: from mail.opticominc.com (www1.opticominc.com [216.64.106.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA23127 for ; Mon, 28 Feb 2000 14:08:12 -0800 (PST) Received: from opticominc.com (216-064-106-070.inaddr.vitts.com [216.64.106.70]) by mail.opticominc.com (8.8.8+Sun/8.7.2) with ESMTP id RAA08984 for ; Mon, 28 Feb 2000 17:27:03 -0500 (EST) Message-ID: <38BAF9D5.B575766F@opticominc.com> Date: Mon, 28 Feb 2000 17:42:29 -0500 From: Giff Hammar X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo Users Subject: Archiving messages Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, Maybe this is RTFM, but I haven't seen in any of the docs where is talks about pulling all of the pieces together. I would like to archive mail on my list into monthly archives. I'm using 1.94.4 and the list.cf explicitly says to not use the archive variable in there. I have added the -n flag to my alias name so that it keeps track of an index number for each message. My list alias look like: mylist "|/usr/local/majordomo/wrapper resend -l mylist -n mylist-list" It's obvious that I need to call the archive2.pl to put the message into the archive file. How do I call the archive2.pl so that it will archive each message, then send it to the list (or send and then archive)? Any help would be appreciated. Giff -- Giff Hammar hammar@opticominc.com Director of Operations Voice: 978.946.6219 Opticom, Inc. Fax: 978.946.6227 http://www.opticominc.com/ Pager: 603.599.3793 From majordomo-users-owner Mon Feb 28 14:25:08 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA22959; Mon, 28 Feb 2000 13:57:22 -0800 (PST) Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA22950 for ; Mon, 28 Feb 2000 13:57:14 -0800 (PST) Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate2.mot.com (motgate2 2.1) with ESMTP id PAA13546; Mon, 28 Feb 2000 15:16:16 -0700 (MST)] Received: [from relay1.cig.mot.com (relay1.cig.mot.com [136.182.15.23]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id PAA15922; Mon, 28 Feb 2000 15:16:15 -0700 (MST)] Received: from login00.cig.mot.com (login00 [136.182.14.84]) by relay1.cig.mot.com (8.8.8+Sun/SCERG-RELAY-1.11b) with ESMTP id QAA20132; Mon, 28 Feb 2000 16:16:14 -0600 (CST) Received: from localhost (keisler@localhost) by login00.cig.mot.com (8.8.8+Sun/8.8.8) with ESMTP id QAA28056; Mon, 28 Feb 2000 16:16:14 -0600 (CST) X-Authentication-Warning: login00.cig.mot.com: keisler owned process doing -bs Date: Mon, 28 Feb 2000 16:16:13 -0600 (CST) From: Mark Keisler X-Sender: keisler@login00 To: "Raul A. Gallegos" cc: "majordomo-users@greatcircle.com" Subject: Re: spam in mailing list In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk If you want to keep non-subscribers from posting to your list, you need to use restrict_post setting. Just set that value to the name of your list (also the name of the file that contains the addresses on your list). The only drawback is that your from address that you mailer provides must look exactly like what your subscribed address is in order for it to get through. On Mon, 28 Feb 2000, Raul A. Gallegos wrote: > Hello. Today I got a spam message on my mailing list. This was sent by a user who is not subscribed on the list. I'm using slackware linux 7.0 with default > software sendmail and perl. mj version is 1.94.4. What can I forward to this list to show my settings. I have the message with headers as well as the logs from > /var/log/messages is that is needed. > > Thanks anyone for this help. > > > *** New look for ASMODEAN.NET. Click http://www.asmodean.net > *** Email me raul@asmodean.net or icq me 5283055 > ------------------------------ Mark Keisler It has to happen somewhere. It has to happen sometime. What better place than here? What better time than now? ------------------------------ From majordomo-users-owner Mon Feb 28 14:38:42 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA23367; Mon, 28 Feb 2000 14:27:35 -0800 (PST) Received: from mail1.svr.pol.co.uk (mail1.svr.pol.co.uk [195.92.193.18]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA23360 for ; Mon, 28 Feb 2000 14:27:27 -0800 (PST) Received: from modem-49.coumadin.dialup.pol.co.uk ([62.136.86.177] helo=skirza.fsnet.co.uk) by mail1.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12PYvr-0004lA-00 for majordomo-users@greatcircle.com; Mon, 28 Feb 2000 22:46:28 +0000 Received: from skirza.fsnet.co.uk (localhost [127.0.0.1]) by skirza.fsnet.co.uk (8.9.3/8.9.3) with ESMTP id WAA02233 for ; Mon, 28 Feb 2000 22:44:22 GMT Message-ID: <38BAFA46.AA1CBC72@skirza.fsnet.co.uk> Date: Mon, 28 Feb 2000 22:44:22 +0000 From: Kenny Shields Reply-To: kenny@skirza.fsnet.co.uk Organization: Skirza Lobsters X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: "majordomo-users@greatcircle.com" Subject: Digest Setup Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Forgive me if this is a often repeated request, but I'm having trouble getting digests set up. There appears to be confusing (at least to me) information in the documentation included with the 1.9.4.4 version of Majordomo. I am a totally new user of Majordomo, but I have managed to set up a trial list and get it working. In the RPM I downloaded (for SuSe Linux 6.1) there is a document titled "quick digest set-up" which I have followed, but when it comes to editing the digest.config file the config file comments seem to indicate not to complete, for example $digest_archive entry as it "does not work and to leave it blank". Do I just ignore the warning and enter the relevant directories? Are the instructions contained in "quick digest set-up" the way to go? Any help would be greatly appreciated. -- Cheers, Kenny Shields Home: kenny@skirza.fsnet.co.uk Work: kenny.shields@norscot.co.uk From majordomo-users-owner Mon Feb 28 18:08:43 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA26281; Mon, 28 Feb 2000 17:55:42 -0800 (PST) Received: from bend.k12.or.us (bend.k12.or.us [198.237.38.219]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA26268 for ; Mon, 28 Feb 2000 17:55:34 -0800 (PST) Received: from cdesd.k12.or.us ([198.237.39.121]) by bend.k12.or.us (8.9.2/8.8.6/bend-k12-MX) with ESMTP id SAA12644 for ; Mon, 28 Feb 2000 18:14:37 -0800 (PST) Message-ID: <38BB2C21.D3B601A2@cdesd.k12.or.us> Date: Mon, 28 Feb 2000 18:17:05 -0800 From: Wesley Stout X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "majordomo-users@GreatCircle.COM" Subject: Admin Request Bounced... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Majordomo 1.94.4 Sendmail 8.9.2 Occasional bounce: Admin request of type /^sub\b/i at line 3] Ideas? From majordomo-users-owner Mon Feb 28 21:53:45 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA28214; Mon, 28 Feb 2000 21:40:16 -0800 (PST) Received: from kappa (adsl-151-200-26-75.bellatlantic.net [151.200.26.75]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA28205 for ; Mon, 28 Feb 2000 21:40:02 -0800 (PST) Received: from kappa ([127.0.0.1]) by kappa with Microsoft SMTPSVC(5.0.2172.1); Tue, 29 Feb 2000 00:59:36 -0500 Message-Id: <4.1.20000229004550.00a2b368@mailbox.bellatlantic.net> X-Sender: jeasterl@mailbox.bellatlantic.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 29 Feb 2000 00:59:36 -0500 To: Dave Moyer , majordomo-users@GreatCircle.COM From: Julian Easterling Subject: Re: MAJORDOMO ABORT (mj_majordomo) In-Reply-To: <4.2.2.20000228105203.00a46670@mercury.libpubinc.com> References: <4.1.20000228002253.00a52a00@mailbox.bellatlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 29 Feb 2000 05:59:37.0014 (UTC) FILETIME=[28B38D60:01BF827A] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thanks, Dave. The relay values did the trick for Sendmail accepting the mail. I finally got Majordomo to *not* send the "Majordomo Abort" messages. I used chmod to allow everyone write access to the files that majordomo was complaining about. (When I ran ./wrapper config-test). Having this "fixed", I turned my attention to Sendmail. When I looked at the mail log in /var/log directory I see where sendmail is trying to send the message out: Feb 29 00:39:15 jclx2 sendmail[1812]: XAA01307: to= , delay=01:13:40, xdelay=00:01:00, mailer=esmtp, relay=julianscorner.com. [151.2 00.26.75], stat=Deferred: Connection timed out with julianscorner.com. Feb 29 00:39:15 jclx2 sendmail[1812]: MAA00898: to=, delay=12:02:01, xdelay=00:00:00, mailer=esmtp, relay=happyhourdc.com., stat=Defe rred: Connection timed out with happyhourdc.com. I think that I know where this is coming from but I am not sure how to fix it. In my DNS I alias the domain to the web server (running on a different machine) by doing a simple @ IN A 151.200.26.75 I think sendmail is picking this up instead of the mx record. Do you know what else I could try? Thanks again. At 11:10 AM 2/28/2000 -0800, Dave Moyer wrote: > > >>Let me describe the situation: >>I have Majordomo 1.94.5 running on Mandrake Linux 7.0. I have Perl >>5.005_03 and Sendmail 8.9.3 >>All of my servers are host in julianscorner.com domain. I run a second >>domain: happyhourdc.com. This domain is where Majordomo is running. I >>have set up MX records in both domains to point to this machine as >>mailhost. Each domain is: mailhost.happyhourdc.com and >>mailhost.julianscorner.com >>Whenever I send email to the happyhourdc.com MX, my sendmail complains 550 >>Relaying denied. I have tried to set up sendmail to accept mail for both >>domains, but this hasn't worked yet. I turned my attention to getting >>majordomo responding to me on the julianscorner.com MX and I get the >>message below: > >Ok, the first problem is one that's new to SendMail 8.9.3. In previous >releases of SM promiscuous relaying was allowed by default (don't you just >love the terms people come up with). In 8.9.3, anti-Spam became a hot >issue so promiscuous relaying is now off by default. There are a couple of >ways to fix the problem. First, set promiscuous relaying on. Bad >idea. That would allow any one and anything to use your system as a Spam >relay. It would probably result in our system eventually getting black >holed and people who were subscribed to your list may not be allowed to get >their messages because they would be blocked by their ISPs. The second and >better solution would be to set up a limited relay. You will need to set >up an access db with happyhourdc.com given the value RELAY. Make sure >SendMail is set up to use the access db and that should take care of the >relaying problem. Details on how to set up the access db and make sure SM >is configured to use it are in the SM docs. > > >> >Return-Path: >> >Received: (from mail@localhost) >> > by jclx2.julianscorner.com (8.9.3/8.9.3) id QAA24945; >> > Sun, 27 Feb 2000 16:51:15 -0500 >> >Date: Sun, 27 Feb 2000 16:51:15 -0500 >> >Message-Id: <200002272151.QAA24945@jclx2.julianscorner.com> >> >X-Authentication-Warning: jclx2.julianscorner.com: mail set sender to >> >Majordomo-Owner@mailhost.julianscorner.com using -f >> >To: Majordomo-Owner@mailhost.julianscorner.com >> >From: Majordomo@happyhourdc.com >> >Subject: MAJORDOMO ABORT (mj_majordomo) >> >Reply-To: Majordomo@happyhourdc.com >> >Status: >> > >> >-- >> > >> > >> >MAJORDOMO ABORT (mj_majordomo)!! >> > >> >While running with an effective uid of 8 and an effective gid of 12 12, >> >Majordomo >> >ran into the following problems: >> >Unable to write to log file, check permissions on /home/majordom/runtime/Log >> >Unable to write to list directory $listdir, check permissions on >> >/home/majordom/lists > >This one is a bit more difficult. Double check the groups table. On >RedHat, uid 8 and gid 12 are both mail. In the MD install instructions, it >tells you to set the owner of all to MD files and directories to majordomo >and the group to daemon. However, if Mandrake has the same id definitions, >try changing the group on all of the MD files and directories to mail. > >>I checked the permissions on these directory and majordom (user and group) >>own the directories and files. Once I get Majordomo to respond to me using >>the hostname in the julianscorner.com domain, I will need to get it to work >>in the happyhourdc.com. So if any of you know how to or know where I can >>find the information for Sendmail to work under both domain. Thanks. > >Hope this helps > >Dave > From majordomo-users-owner Mon Feb 28 22:08:42 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA28452; Mon, 28 Feb 2000 22:02:58 -0800 (PST) Received: from usinter.net (mail.usinter.net [206.171.66.25]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA28445 for ; Mon, 28 Feb 2000 22:02:49 -0800 (PST) Received: from usinter.net [209.85.130.137] by usinter.net [206.171.66.25] with SMTP (MDaemon.v2.8.7.2.R) for ; Mon, 28 Feb 2000 22:21:49 -0800 Message-ID: <38BB65D9.EC2ABCD@usinter.net> Date: Mon, 28 Feb 2000 22:23:21 -0800 From: "Todd A. Lyons" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@GreatCircle.COM, Wesley Stout Subject: Re: Admin Request Bounced... References: <38BB2C21.D3B601A2@cdesd.k12.or.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: majordomo-users@GreatCircle.COM X-Return-Path: cannonball@usinter.net Reply-To: cannonball@usinter.net Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Wesley Stout wrote: > Occasional bounce: > Admin request of type /^sub\b/i at line 3] Quote a message that bounced. We need to see the source, specifically line 3. More than likely, there is something in there that's pattern matching (see next paragraph). I would guess that you have the administrivia option on in the listname.config file. Turn that off and I think your problem will go away. Now, if you actually *WANT* the administrivia function, that's just an occassional bounce you'll have to live with. -- Blue skies... Cannonball http://www.mrball.net * One ring to rule them all, One ring to find them * * One ring to bring them all, and in the darkness bind them * Sauron From majordomo-users-owner Tue Feb 29 01:53:44 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id BAA01082; Tue, 29 Feb 2000 01:42:05 -0800 (PST) Received: from mail6.svr.pol.co.uk (mail6.svr.pol.co.uk [195.92.193.212]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id BAA01072 for ; Tue, 29 Feb 2000 01:41:52 -0800 (PST) Received: from [195.92.198.123] (helo=mail17.svr.pol.co.uk) by mail6.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 12PjSa-0005IV-00; Tue, 29 Feb 2000 10:00:56 +0000 Received: from modem-40.aldaron.dialup.pol.co.uk ([62.136.101.168] helo=ukdserver1) by mail17.svr.pol.co.uk with smtp (Exim 3.13 #0) id 12PjSX-0001b9-00; Tue, 29 Feb 2000 10:00:54 +0000 Message-ID: <002a01bf829c$e1b41dd0$0200a8c0@ukdserver1.ukdirectory.co.uk> From: "Sam Stickland" To: "Giff Hammar" , "Majordomo Users" Subject: Re: Archiving messages Date: Tue, 29 Feb 2000 10:08:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, >Maybe this is RTFM, but I haven't seen in any of the docs >where is talks about pulling all of the pieces together. I would >like to archive mail on my list into monthly archives. I'm using >1.94.4 and the list.cf explicitly says to not use the archive >variable in there. > >I have added the -n flag to my alias name so that it keeps track >of an index number for each message. My list alias look like: > >mylist "|/usr/local/majordomo/wrapper resend -l mylist -n mylist-list" > >It's obvious that I need to call the archive2.pl to put the message >into the archive file. How do I call the archive2.pl so that it will >archive each message, then send it to the list (or send and then >archive)? Any help would be appreciated. Well personally I don't archive my lists, but it ought to be a case of making you mylist-list alias look a bit like this: test-outgoing: :include:/usr/local/Lists/mylist, "| /tools/majordomo/wrapper archive2.pl -a -m -f /usr/local/mail/archive/mylist/mylist.archive" Make sure you have the right permissions on all the files involved. This is all in the NEWLIST documentation that should had come with majordomo btw. :) Sam From majordomo-users-owner Tue Feb 29 06:09:04 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA05424; Tue, 29 Feb 2000 05:58:16 -0800 (PST) Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id FAA05417 for ; Tue, 29 Feb 2000 05:58:11 -0800 (PST) Received: from graphics (user-38ldcq6.dialup.mindspring.com [209.86.179.70]) by smtp6.mindspring.com (8.9.3/8.8.5) with SMTP id JAA24294 for ; Tue, 29 Feb 2000 09:17:19 -0500 (EST) Message-ID: <01aa01bf82bf$9f926880$d91ba6d0@ispchannel.com> From: "Eric" To: Subject: reselling majordomo list services Date: Tue, 29 Feb 2000 09:16:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We were considering running our own majordomo list servers for ourselves and for our clients however it seems like a somewhat tedious chore to get it set up and administer. I was just wondering if anybody on the list has a wholesale or reseller program for their list and also what everyone on this lists prices were. We may prefer to contract this stuff out rather than fight with majordomo to keep trying to set it up. Any comments, inquiries, and even offers are welcome =) Thanks in Advance, Eric From majordomo-users-owner Tue Feb 29 08:39:53 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA06818; Tue, 29 Feb 2000 08:22:02 -0800 (PST) Received: from voyager1.telesat.com.co (voyager1.mirave.com [208.221.130.4]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA06811 for ; Tue, 29 Feb 2000 08:21:53 -0800 (PST) Received: from samanea.wwf.org.co (wwf [63.71.208.32]) by voyager1.telesat.com.co (8.9.1/8.9.1) with ESMTP id LAA09657 for ; Tue, 29 Feb 2000 11:38:51 -0500 (Etc/GMT) Received: from ceiba (CEIBA.wwf.org.co [192.168.0.64]) by samanea.wwf.org.co (Postfix) with SMTP id E7D5C3BEAC for ; Tue, 29 Feb 2000 11:38:20 -0500 (COT) From: "Nicholas Waltham" To: Subject: Fully automatic bouncing address removal Date: Tue, 29 Feb 2000 11:38:19 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal In-Reply-To: <002701bf63b5$c300c060$0100a8c0@earthlink> Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello All, I would be intersted to know if anyone has produced a module for fully automatic removal of bouncing addresses from a majordomo list. If not, is there anything a bit more automatic than the bounce script that comes with Majordomo. Thanks in advance, Nicholas Waltham From majordomo-users-owner Tue Feb 29 11:12:27 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA08442; Tue, 29 Feb 2000 10:53:19 -0800 (PST) Received: from sportsurf.net (sportsurf.net [192.41.36.58]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA08435 for ; Tue, 29 Feb 2000 10:53:14 -0800 (PST) Received: from [171.209.35.89] (ABD12359.ipt.aol.com [171.209.35.89]) by sportsurf.net (8.8.5) id MAA01193; Tue, 29 Feb 2000 12:12:19 -0700 (MST) Message-Id: <200002291912.MAA01193@sportsurf.net> X-Mailer: Microsoft Outlook Express Macintosh Edition - 4.5 (0410) Date: Tue, 29 Feb 2000 14:14:23 -0500 Subject: Re: Fully automatic bouncing address removal From: "Mark Rauterkus" To: majordomo-users@greatcircle.com Mime-version: 1.0 X-Priority: 3 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, Question: > ...a module for fully automatic > removal of bouncing addresses from a majordomo list. If not, is there > anything a > bit more automatic than the bounce script that comes with Majordomo. Yes. Vince has done what you are looking for. See: http://www.smartbounce.com Mark Rauterkus mrauterkus@SportSurf.Net From majordomo-users-owner Tue Feb 29 11:27:29 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA08544; Tue, 29 Feb 2000 10:57:03 -0800 (PST) Received: from mail.rdc1.sdca.home.com (ha1.rdc1.sdca.home.com [24.0.3.66]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA08534 for ; Tue, 29 Feb 2000 10:56:55 -0800 (PST) Received: from cx588769a ([24.4.67.154]) by mail.rdc1.sdca.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <20000229191606.BMNK4555.mail.rdc1.sdca.home.com@cx588769a> for ; Tue, 29 Feb 2000 11:16:06 -0800 Message-ID: <008e01bf82e9$761f0b00$9a430418@elcjn1.sdca.home.com> From: "Anthony M. Abate" To: Subject: Error message Date: Tue, 29 Feb 2000 11:16:20 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I keep getting the following message form majordomo: MAJORDOMO ABORT (mj_majordomo)!! shlock: '/usr/test/majordomo-1.94.5' is not writable by UID 8 GID 12 All of my lists function no problems, but I am having a problem with new people trying to join. Any idea's ...... -Tony P.S. I'll send the ls of permissions if anyone would like to see them, just ask. From majordomo-users-owner Tue Feb 29 13:56:17 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA10380; Tue, 29 Feb 2000 13:42:08 -0800 (PST) Received: from conecta.mgconecta.com.br (conecta.mgconecta.com.br [200.238.205.101]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA10373 for ; Tue, 29 Feb 2000 13:41:59 -0800 (PST) Received: from armagedon (IDENT:root@line019M [200.238.205.29]) by conecta.mgconecta.com.br (8.9.3/8.9.3) with SMTP id TAA02903 for ; Tue, 29 Feb 2000 19:01:42 -0300 (EST) From: mendes Organization: Working at home To: majordomo-users@GreatCircle.Com Subject: A list with a receipt Date: Tue, 29 Feb 2000 19:57:40 -0300 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00022920051000.00765@armagedon> Content-Transfer-Encoding: 8bit Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello First of all I would like to thank you all for helping me to set up a list. Although I am having some trouble with SPAM the list is working OK. I need to setup an internal list for my department and I have been asked if it is possible that once a list member opens his/her email from the list a receipt is sent automatically to another member of the list which is responsible for all memos. Thanks for your help. Other suggestions other than a conventional list are most welcome. Regards Eduardo From majordomo-users-owner Tue Feb 29 15:41:18 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA11590; Tue, 29 Feb 2000 15:35:53 -0800 (PST) Received: from mercury.libpubinc.com (mercury.libpubinc.com [208.249.203.55]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA11583 for ; Tue, 29 Feb 2000 15:35:46 -0800 (PST) Received: from dmoyer (dhcp93.libpubinc.com [208.249.203.93]) by mercury.libpubinc.com (8.9.3/8.9.3) with ESMTP id PAA31341; Tue, 29 Feb 2000 15:54:58 -0800 Message-Id: <4.2.2.20000229155223.00b2d100@mercury.libpubinc.com> X-Sender: dmoyer@mercury.libpubinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 29 Feb 2000 15:54:57 -0800 To: "Anthony M. Abate" , From: Dave Moyer Subject: Re: Error message In-Reply-To: <008e01bf82e9$761f0b00$9a430418@elcjn1.sdca.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk It looks like a permissions problem on your MajorDomo directory. Try checking the permissions on the majordomo directory and see they are set to user majordomo and group mail. Dave At 11:16 AM 2/29/00 -0800, Anthony M. Abate wrote: >I keep getting the following message form majordomo: > >MAJORDOMO ABORT (mj_majordomo)!! > >shlock: '/usr/test/majordomo-1.94.5' is not writable by UID 8 GID 12 > >All of my lists function no problems, but I am having a problem with new >people trying to join. Any idea's ...... > >-Tony > >P.S. I'll send the ls of permissions if anyone would like to see them, just >ask. From majordomo-users-owner Tue Feb 29 16:11:18 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA11880; Tue, 29 Feb 2000 16:07:29 -0800 (PST) Received: from kappa ([209.193.174.230]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id QAA11873 for ; Tue, 29 Feb 2000 16:07:23 -0800 (PST) Received: from kappa ([127.0.0.1]) by kappa with Microsoft SMTPSVC(5.0.2172.1); Tue, 29 Feb 2000 19:27:02 -0500 Message-Id: <4.1.20000229191923.00a27f30@mailbox.bellatlantic.net> X-Sender: jeasterl@mailbox.bellatlantic.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 29 Feb 2000 19:27:02 -0500 To: From: Julian Easterling Subject: Re: Error message In-Reply-To: <008e01bf82e9$761f0b00$9a430418@elcjn1.sdca.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 01 Mar 2000 00:27:02.0799 (UTC) FILETIME=[DD79B9F0:01BF8314] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I just went through this, so I will tell you how I fixed mine. This has to do with the permission for you majordomo directory. 1. First, Log in (or SU) as someone that doesn't have super-user privileges and don't log in as the User(UID) that runs majordomo(usually majordom) 2. go to the directory that has wrapper in it. 3. run ./wrapper config-test 4. the script will complain when a file or directory doesn't have the correct write permissions 5. use CHMOD to change the write permissions for everyone. In my case "chmod o+w file" run the config-test until there are no more errors. Others might know of a better way of doing this, but this worked for me. At 11:16 AM 2/29/2000 -0800, Anthony M. Abate wrote: >I keep getting the following message form majordomo: > >MAJORDOMO ABORT (mj_majordomo)!! > >shlock: '/usr/test/majordomo-1.94.5' is not writable by UID 8 GID 12 > >All of my lists function no problems, but I am having a problem with new >people trying to join. Any idea's ...... > >-Tony > >P.S. I'll send the ls of permissions if anyone would like to see them, just >ask.