From majordomo-users-owner Sat Oct 1 03:11:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id DAA27994; Sat, 1 Oct 1994 03:11:39 GMT Received: from sdrc.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id UAA27988; Fri, 30 Sep 1994 20:11:29 -0700 Received: from sgi0 (sgi0.sdrc.com) by sdrc.com (4.1/SMI-4.1) id AA02327; Fri, 30 Sep 94 23:11:51 EDT Received: by sgi0 via SMTP (931110.SGI/920502.SGI) id AA26332; Fri, 30 Sep 94 23:11:32 -0400 Received: by sgiis10 (931110.SGI/930416.SGI) id AA17476; Fri, 30 Sep 94 23:11:31 -0400 From: eric.hammond@sdrc.com (Eric Hammond) Message-Id: <9410010311.AA17476@sdrc.com> Subject: (SUMMARY) Mailers replying to "From " address To: majordomo-users@GreatCircle.COM Date: Fri, 30 Sep 1994 23:11:31 -0500 (EDT) Cc: Bill.Kramer@sgi0.sdrc.com X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3345 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Recently I posted a notice that some of our users' mail readers were replying to the "From " address instead of the "From:" address. I asked for help and here are the results. Thanks to Ian Poynter for noting that in addition to the packages I listed the Microsoft Mail gateway also replies to the wrong address. Thanks to Ian and Michael J. Corrigan for helping me understand where bounced error messages go (envelope sender or "From " address). Michael also noted that the behavior of the mailx mailer that comes on HP-UX's can be corrected by adding the following line in the .mailrc: set SMARTMAILER There seems to be some confusion as to whether an "Errors-To:" header would help, but we seem to be leaning towards not (many speak it but few--if any--listen). Elizabeth Lear Newman pointed out the -r option in the "resend" script which can be used to direct replies back to the mailing list (see her message to this list). Now here's how I think I have solved it for my site. I have made a few changes to the "resend" script so that it adds a "Reply-To:" header pointing back to the poster of the message. It will only do this if the original message did not have a "Reply-To:" and if the list configuration or resend -r option did not specify a forced "Reply-To:" for the list. I have appended my resend patch below. Note, however, that I have already applied another patch to this script, so the patch provided will probably not work if you have a clean distribution resend. If you can't figure out how to apply this patch and you would like to, drop me a note and I'll help you out. I'm not sure how this works if there is a "Reply-To:" in the main header for an approve'd message, but not in the enclosed header. This looks like it might be a bug in the original resend script. If you see a significant problem with my changes, I'd also like to hear about it. I have not had extensive testing of this patch, but I'll forward any negative results to the list. -- Eric.Hammond@sdrc.com 513/576-5907 Structural Dynamics Research Corporation 2000 Eastman Drive, Milford OH 45150 USA ======================================== *** resend.orig Fri Sep 30 20:29:28 1994 --- resend Fri Sep 30 21:04:49 1994 *************** *** 137,142 **** --- 137,144 ---- open(IN, "/tmp/resend.$$.in") || die("resend: Can't open /tmp/resend.$$.tmp: $!"); + $seen_replyto = 0; # Did we see a "Reply-To:" in the original message? + $pre_hdr = 0; $in_hdr = 1; do { *************** *** 172,177 **** --- 174,185 ---- if (defined($opt_r)) { print OUT "Reply-To: ", &config'substitute_values($opt_r), "\n"; + } elsif ( ! $seen_replyto ) { + # -r wasn't specified and sender didn't have his own + # Reply-To: so we add the sender's name here. This + # gets around the bug in some email readers which + # reply to the "From " address instead of "From:" + print OUT "Reply-To: ", $from, "\n"; } # print out additonal headers *************** *** 251,256 **** --- 259,268 ---- } &check_hdr_line($_); # check for length & balance $kept_last = 1; + + # Note the fact if we copy a "Reply-To:" in the msg. + ++ $seen_replyto if /^reply-to:/i; + print OUT $_; } } else { From majordomo-users-owner Fri Sep 30 22:55:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id FAA28922; Sat, 1 Oct 1994 05:27:45 GMT Received: from nova.unix.portal.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id WAA28916; Fri, 30 Sep 1994 22:27:28 -0700 Received: from jobe.shell.portal.com (jobe.shell.portal.com [156.151.3.4]) by nova.unix.portal.com (8.6.7/8.6.5) with ESMTP id WAA10108 for ; Fri, 30 Sep 1994 22:27:39 -0700 Received: from localhost (chan@localhost) by jobe.shell.portal.com (8.6.4/8.6.5) id WAA18898 for majordomo-users@greatcircle.com; Fri, 30 Sep 1994 22:27:37 -0700 Date: Fri, 30 Sep 1994 22:27:37 -0700 From: Jeff Chan Message-Id: <199410010527.WAA18898@jobe.shell.portal.com> To: majordomo-users@greatcircle.com Subject: force reply to author, not list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk What can I do to force replies (in majordomo 1.6x) to go to the author instead of the list? If -r Reply-to is the appropriate resend flag, for example, what should the argument be? (I have a feeling -r alone wont's work since not all mailers pay attention to the Reply-to field....) TIA, Jeff Chan chan@shell.portal.com From majordomo-users-owner Sat Oct 1 17:27:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA02054; Sat, 1 Oct 1994 17:27:47 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA02042; Sat, 1 Oct 1994 10:27:37 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA28094 (5.65c/IDA-1.4.4 for ); Sat, 1 Oct 1994 13:27:18 -0400 Message-Id: <199410011727.AA28094@cs.umb.edu> To: "John F. Kastler" Cc: Majordomo-Users@greatcircle.com Subject: Re: moderated list question In-Reply-To: Your message of "Fri, 09 Sep 1994 14:26:14 EDT." <199409091826.AA20766@csteam.com> Date: Sat, 01 Oct 1994 13:27:04 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199409091826.AA20766@csteam.com>, "John F. Kastler" writes: >I am having a small problem that I hoe you can help me with. > >I am setting up majordomo V1.92. > >I have a moderated list with multiple moderators. > >The problem is that when I approve a posting, I am not getting a reply-to >field set. Here are the important lines: > >aliases file: > ># ># Majordomo aliases ># >majordomo: "|/gems1/majordom/wrapper majordomo" >owner-majordomo: staff >majordomo-owner: staff ># ># Ask The Real Estate Pros list ># >owner-atrep::include:/gems1/majordom/mail/lists/owner-atrep >atrep-owner:owner-atrep >owner-atrep-approval:owner-atrep >owner-owner-atrep: owner-majordomo ># >atrep: "|/gems1/majordom/wrapper resend -p bulk -A -a /gems1/majordom/mail/lists >/atrep.passwd -M 10000 -R -r atrep@gems.com -l owner-atrep -f owner-atrep \ > -h gems.com -s atrep-outgoing" > ^^^^^^^^^^^^^^^^^ get rid of the -f and the -r, only the -h and -l flags should be used if you are using the config file. The -f flag is what is setting the from address to be owner-atrep. >atrep.config file: >reply_to = atrep@gems.com > > >owner-atrep file: >reply_to = atrep@gems.com > >Can someone suggest an answer to this problem? My understanding was that >setting the reply_to line in the config files should do the trick for >me but all postings go to owner-atrep instead of atrep. (in all postings, the >from: line has owner-atrep on it). The reply-to adds (or should add) a Reply-to: header to the message. some gateways drop this header, and some mail readers don't use the Reply-To address if it is available, using the from address in all cases. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Sat Oct 1 17:31:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA02104; Sat, 1 Oct 1994 17:31:09 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA02098; Sat, 1 Oct 1994 10:31:00 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA28120 (5.65c/IDA-1.4.4 for ); Sat, 1 Oct 1994 13:30:50 -0400 Message-Id: <199410011730.AA28120@cs.umb.edu> To: Andrew Waegel Cc: majordomo-users@greatcircle.com Subject: Re: newbie "resend" question In-Reply-To: Your message of "Sat, 10 Sep 1994 15:28:19 EDT." Date: Sat, 01 Oct 1994 13:30:37 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Andrew Waegel writes: >Hi- > >Got majordomo running, lists set up, etc. Reading the docs, I noticed the >second "-l" option to resend; the one that allows you to specify a list >of folks allowed to post (as an alternative to moderation). What confuses >me is that this looks like the required "-l" option in which you specify >the list name. What's the difference? I think that is -I, not -l. did I put a typo in somewhere? >I've tried every combination of the above >and majordomo merrily allows anyone to post. I'm also unclear as to >whether archiving (-A to resend) needs to be activated in order for this >"-l" option to work. Heaps of praise and adoration for anyone who can >help me out on this. -A has nothing to do with archiving, you have to add archive as shown in the sample aliases in the README file. The -A option enabled moderation, the -a option sets the password. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Sat Oct 1 17:42:32 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA02180; Sat, 1 Oct 1994 17:42:32 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA02174; Sat, 1 Oct 1994 10:42:21 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA28494 (5.65c/IDA-1.4.4 for ); Sat, 1 Oct 1994 13:42:13 -0400 Message-Id: <199410011742.AA28494@cs.umb.edu> To: murphy@dccs.upenn.edu Cc: majordomo-users@greatcircle.com Subject: Re: How to get around a moderator of list and send your posting anyway In-Reply-To: Your message of "Wed, 14 Sep 1994 13:12:40 EDT." <9409141712.AA05970@lam.dccs.upenn.edu> Date: Sat, 01 Oct 1994 13:42:00 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9409141712.AA05970@lam.dccs.upenn.edu>, murphy@dccs.upenn.edu writes: >I thought that one feature of Majordomo is to be able to restrict >who can send mail messages to a list? E.g. Majordomo has >'moderated' lists, set moderate = yes in .config. > >I set up a list with moderate = yes, send a message to it, and >then got the "BOUNCE ..." for my approval (since I'm also the >list owner). > >Then, I sent mail to -outgoing and bypassed Majordomo >altogether, and the mail was distributed to the list subscribers. > >Isn't this a bug? I think of it as a feature since I have had to use it when someing in the majordomo installation breaks, gets tromped on etc. >For any list which is restricted or moderated, all I need to do >is guess the alias name for the :include alias (which is passed >to resend as the last argument), and '-outgoing' is a >pretty good guess. In fact, if I have a Unix account on the same >host where majordomo is running, I don't have to guess at all, I >can simply read the /etc/aliases file and look for the resend for >the list! > >Example of another moderated list: I just connected to the >sendmail daemon on the system where the Net Happenings list is >kept, and typed three vrfy commands, and got these results: > >vrfy majordomo >250 >vrfy net-happenings >250 >vrfy net-happenings-outgoing >250 > >Net-happenings is supposedly a moderated mailing list -- but I >wonder what would happen if I sent a message to >net-happenings-outgoing@is.internic.net? Wouldn't it be >distributed to everyone on the list by the system's MTA >regardless of the fact that Majordomo thinks it's moderated? yes. >Isn't that a problem? If they really cared they could run a split sendmail/alias installation. The outgoing aliases are in /etc/aliases. The incomming aliases (the alias file that the sendmail process running as a daemon is configured to see) doesn't have any of the outgoing aliases. So email sent to the daemon for foolist-outgoing will fail with no such user, but mail sent to foolist will invoke resend which invokes sendmail (reading /etc/aliases) which knows how to deliver to foolist-outgoing. Obviuosly anybody on the mailhub machine could use the foolist-outgoing, but at least you can figure out who that is since it isn't hiding behind a tcp connection. >Another question: Can I have a list with an open subscription >policy but where only the subscribers to the list can send mail >to the subscribers of the list? (I'm a little new to Majordomo, >so I'm not sure how I would configure such a list yet.) (This >kind of list would also be susceptible to the same problem >described above, I believe). Yes, it would. what you can use is the restrict_post item see the documentation for the -I flag in resend) in the config file and point it at the address file. This won;t work quite as well as is hoped if people are subscribed to different addresses than their mail comes in with, but its a start. This entire access list stuff will be cleaned up and normalized in 1.93, but I wouldn't hold your breath waiting for 1.93 to be released. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Sat Oct 1 17:55:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA02240; Sat, 1 Oct 1994 17:55:31 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA02234; Sat, 1 Oct 1994 10:55:20 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA29284 (5.65c/IDA-1.4.4 for ); Sat, 1 Oct 1994 13:54:20 -0400 Message-Id: <199410011754.AA29284@cs.umb.edu> To: richard welty Cc: majordomo-users@greatcircle.com Subject: Re: resend, administrative requests In-Reply-To: Your message of "Wed, 14 Sep 1994 14:53:15 EDT." <199409141853.OAA06168@homer.balltown.cma.com> Date: Sat, 01 Oct 1994 13:54:06 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199409141853.OAA06168@homer.balltown.cma.com>, richard welty writes: >so can anyone tell me why resend thinks that the following is >an administrative request? i just started using it in place >of my old header-rewriter, and this is the first one of these >that i've seen... > >richard >------------------------------- >Date: Wed, 14 Sep 1994 01:49:06 -0400 >To: owner-italian-cars >From: owner-italian-cars >Subject: BOUNCE italian-cars@balltown.cma.com: Admin request > >>From welty Wed Sep 14 01:49:00 1994 >Received: from agora.rdrop.com (agora.rdrop.com [199.2.210.241]) by balltown >.cma.com (8.6.9/CMA01) with SMTP id BAA05537 for com>; Wed, 14 Sep 1994 01:48:56 -0400 >Received: by agora.rdrop.com (Smail3.1.28.1 #8) > id m0qknEP-000BM9C; Tue, 13 Sep 94 22:49 PDT >Date: Tue, 13 Sep 1994 22:32:02 -0700 (PDT) >From: Robert Piacentini >Subject: MarelliPlex on a 2600 >To: italian-cars >Message-ID: >MIME-Version: 1.0 >Content-Type: TEXT/PLAIN; charset=US-ASCII > > > >Can anybody help me find a six cylinder distributer cap for a MarelliPlex ^^^^ The word help is a keyword. change the regexp in resend to be something line ^help (help at the beginning of a line) ^\s*help\s*$ help all alone on a line with whitespace. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Sat Oct 1 18:10:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA02384; Sat, 1 Oct 1994 18:10:44 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA02377; Sat, 1 Oct 1994 11:10:33 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA29973 (5.65c/IDA-1.4.4 for ); Sat, 1 Oct 1994 14:10:24 -0400 Message-Id: <199410011810.AA29973@cs.umb.edu> To: dmp@epg.harris.com (Donald Patterson) Cc: majordomo-users@greatcircle.com Subject: Re: strip=no option in .config In-Reply-To: Your message of "Fri, 16 Sep 1994 17:43:21 EDT." <9409162143.AA09552@iowa.epg.harris.com> Date: Sat, 01 Oct 1994 14:10:11 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9409162143.AA09552@iowa.epg.harris.com>, Donald Patterson writes: >I'm running Majordomo vsn. 1.92. I've set strip to "no" in my >.config files so that the "raw address" is not the only >thing going to my subscribe list: > >Does this really work, or is it too sensitive to the way return addresses >are set up? I'm picking up lots of different formats in my list, like: > Doug Burstedt at x8936 > joswald@tor.rand.com (Joe Oswald) > "Loughrin, Owen" with strip on you would see: DBURSTEDT@sv.hns.com joswald@tor.rand.com oloughri@uklans.uky.edu >Does Majordomo know how to strip out the email addresses in the above lines >when it mails messages? That's the responsibility of your MTA, not majordomo. Sendmail deals ok with wbeither of the above, smail sometimes has problems. Not sure about other MTA's. >It seems it does not. When I approve some of the >subscriptions above, I (the list owner) get the "welcome" message bounced >back to me. Seems like addresses in some of the above formats are bogus. Nope they are fine. Nice valid rfc822 addresses, you mailer may just not be able to hack them. >Should I just set strip to "yes", or am I missing something? You might have to. That's why strip was introduced to deal with mailer that only wanted th address spec of the address in their include files. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Sat Oct 1 18:13:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA02410; Sat, 1 Oct 1994 18:13:52 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA02404; Sat, 1 Oct 1994 11:13:45 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA29992 (5.65c/IDA-1.4.4 for ); Sat, 1 Oct 1994 14:13:29 -0400 Message-Id: <199410011813.AA29992@cs.umb.edu> To: Marko Hotti Cc: majordomo-users@greatcircle.com Subject: Re: Summary of subjects in a digest In-Reply-To: Your message of "Tue, 20 Sep 1994 08:50:04 +0200." Date: Sat, 01 Oct 1994 14:13:16 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Marko Hotti writes: >I've been trying to configure my digested mailing list in a manner >that in the beginning of each digest there is a summary of the >topics... like this: > >In this issue: Re: blah blah blah > Re: blah blah blah > New subject > Re: New subject > >... etc. I read the Majordomo 1.92 README file and there was something >about per lists configuration and changing the values of message_footer >and message_fronter. I copied the perl script part from the README and >tried it but all I got to the digests was the perl scripts and not the >actual output from them. How do I paste the script to the list-digest. >config file???? Use the majordomo commands config and newconfig. The config file itself explains how to configure the fronter material. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Sat Oct 1 18:17:15 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA02439; Sat, 1 Oct 1994 18:17:15 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA02433; Sat, 1 Oct 1994 11:17:04 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA00442 (5.65c/IDA-1.4.4 for ); Sat, 1 Oct 1994 14:16:45 -0400 Message-Id: <199410011816.AA00442@cs.umb.edu> To: tmanos@infi.net (Tom Manos) Cc: majordomo-users@greatcircle.com Subject: Re: Problem with new installation In-Reply-To: Your message of "Mon, 26 Sep 1994 10:18:22 EDT." Date: Sat, 01 Oct 1994 14:16:32 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Tom Manos writes: > >Hi Majordomo Gurus! > >I just installed Majordomo this weekend and though the install went >ok, I have a couple of problems which stop me cold. Maybe you can >help? > >Here's some background. We're using a Sparc 10 with Solaris 2.3. I >used the SysV defs in Makefile. We're running Perl 4.036. We also >run Smail 3.1.28 as our mailer. I've set up the aliases in >/usr/lib/aliases properly. > >Here's what happens... > >When using the software as installed, I get the following in my smail >log: > >09/26/94 09:54:46: [m0qpGVy-000GibC] note: "|/local/lib/majordomo-1.92/wrapp >er majordomo" ... transport pipe: write on pipe failed: Broken pipe >09/26/94 09:54:46: [m0qpGVy-000GibC] note: "|/local/lib/majordomo-1.92/wrapp >er majordomo" ... transport pipe: child returned status EX_1 (1) I think exit 1 was some sort of usage error. I would guess your alaiases might need a bit of work still. check the wrapper.c code for exit() statements. From majordomo-users-owner Sat Oct 1 18:49:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA02614; Sat, 1 Oct 1994 18:49:13 GMT Received: from noc4.dccs.upenn.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA02608; Sat, 1 Oct 1994 11:49:05 -0700 Received: from CCAT.SAS.UPENN.EDU by noc4.dccs.upenn.edu id AA29016; Sat, 1 Oct 94 14:49:28 -0400 Received: (from service@localhost) by ccat.sas.upenn.edu (8.6.8/CCAT) id OAA40599 for majordomo-users@GreatCircle.COM; Sat, 1 Oct 1994 14:50:09 -0400 From: Special Projects Message-Id: <199410011850.OAA40599@ccat.sas.upenn.edu> Subject: Approve: does it work on bounces? To: majordomo-users@GreatCircle.COM Date: Sat, 1 Oct 1994 14:50:09 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23-upenn2.9] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 458 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm having no luck trying to get moderated list running: -A -a is in place; .majordomo is in my home dir with mjd@here and tabs in between If I pipe the BOUNCEed message to approve or use "approve there is no message posted, no errors, nothing. Is there any way to trace/debug/try something to find what's going on? Frustrated, --Michael michael@ccat.sas.upenn.edu P.S. approve -d produces same void. From majordomo-users-owner Sat Oct 1 20:11:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id UAA02979; Sat, 1 Oct 1994 20:11:33 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id NAA02973; Sat, 1 Oct 1994 13:11:25 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA04505 (5.65c/IDA-1.4.4 for ); Sat, 1 Oct 1994 16:10:42 -0400 Message-Id: <199410012010.AA04505@cs.umb.edu> To: "Eric S. Theise" Cc: majordomo-users@greatcircle.com Subject: Re: off system owners? In-Reply-To: Your message of "Tue, 27 Sep 1994 14:00:51 PDT." <199409272100.OAA09570@lh.cyberwerks.com> Date: Sat, 01 Oct 1994 16:10:28 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199409272100.OAA09570@lh.cyberwerks.com>, "Eric S. Theise" writes: >I'm wondering how people manage off-system list-owners. My inclination >is to create an alias, say > >list-owner: :include:/usr/majordomo/lists/list.owner > >and store the address(es) in list.owner. Is there a better way? That works. Usually list-owners don't change much, so I just put them into the alias file directly. I have a couple of lists where there are multiple list owners, and I wanted them to be able to increase/decrease their number as time went on, so I created a set of aliases like: list-owner: :include:/usr/majordomo/lists/list.owner owner-list: :include:/usr/majordomo/lists/list.owner owner-owner-list: :include:/usr/majordomo/lists/list.owner This allows them to manage their own list of owners, and receive bounces for people on their list. One thing I should look out for is bounce loop, but I haven't had that problem so far. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Sat Oct 1 22:01:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id WAA03511; Sat, 1 Oct 1994 22:01:20 GMT Received: from vaxa.cis.uwosh.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id PAA03505; Sat, 1 Oct 1994 15:01:12 -0700 Received: from vaxa.cis.uwosh.edu by vaxa.cis.uwosh.edu (PMDF #7750 ) id <01HHRPACZ8O2009QME@vaxa.cis.uwosh.edu>; Sat, 1 Oct 1994 16:53:28 CDT Date: 01 Oct 1994 16:53:28 -0500 (CDT) From: "Charles R. Milam - UW-Oshkosh" Subject: Re: makeindex.pl question To: tmanos@infi.net Cc: majordomo-users@greatcircle.com Message-id: <01HHRPACZ8O4009QME@vaxa.cis.uwosh.edu> X-VMS-To: IN%"tmanos@infi.net" X-VMS-Cc: IN%"majordomo-users@greatcircle.com" MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >> ...and so on. Is there a way I can just have makeindex.pl recursively >> descend into the files subdirectory? > >Why not just write a shell wrapper around it: >Hope it helps! >-- >Tom Manos Norfolk, VA tmanos@infi.net >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >InfiNet | Hampton Roads' Premier Online Information System >(804) 622-4289 | 801 Boush St. Suite 203, Norfolk VA 23510 Sure did help! Thanks to all who responded, it works quite nicely now. ------------------------------------------------------------------------------ Charles R. Milam MilamC@vaxa.cis.uwosh.edu Academic Computing milamc@sol.acs.uwosh.edu University of Wisconsin-Oshkosh KF9FR@KA9JAC.WI.USA.NA Oshkosh, WI 54901 Badger 112 -- WI0112 (414) 424-2309 Delta Sigma Phi - EB Chapter ---------------<<>>---------------- From majordomo-users-owner Mon Oct 3 18:06:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA12284; Mon, 3 Oct 1994 18:06:25 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA12278; Mon, 3 Oct 1994 11:06:19 -0700 Received: from vacuum.org (vacuum.org [198.242.216.35]) by miles.greatcircle.com (8.6.5/Miles-941001) with SMTP id LAA18265 for ; Mon, 3 Oct 1994 11:07:08 -0700 Received: from auger by vacuum.org (5.0/SOLARIS-V1.0-American Vacuum Society) id AA07613; Mon, 3 Oct 94 14:05:51 EDT Message-Id: <9410031805.AA07613@vacuum.org> X-Sender: carlos@torr Date: Mon, 03 Oct 1994 14:05:09 -0400 To: majordomo-users@greatcircle.com From: carlos@vacuum.org (Carlos Toro) Subject: MCI-Mail Problems? X-Mailer: content-length: 645 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have a list (Majordomo 1.92) that seems to work fine with Internet mail, but someone on MCI-Mail sent a "help" message and got the response: > From: AVS-Majordomo \ Internet: (majordomo@vacuum.org) > To: Donna Bakale \ MCI Mail: (TMPDONNA / MCI ID: > 428-1920) > > Subject: Majordomo results: RFI > > -- > > >>>> -- [ From: Donna Bakale * EMC.Ver #2.0 ] -- > END OF COMMANDS i.e. the body of the reply was blank. Furthermore, there is no record in my Log file that this request was made. Is this indeed an MCI-Mail related problem, or is there something else going on? Thanks for all replies, Carlos From majordomo-users-owner Mon Oct 3 18:16:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA12392; Mon, 3 Oct 1994 18:16:13 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA12385; Mon, 3 Oct 1994 11:16:08 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.5/Miles-941001) with ESMTP id LAA18371; Mon, 3 Oct 1994 11:17:05 -0700 Message-Id: <199410031817.LAA18371@miles.greatcircle.com> To: carlos@vacuum.org (Carlos Toro) cc: majordomo-users@greatcircle.com Subject: Re: MCI-Mail Problems? In-reply-to: Your message of Mon, 03 Oct 1994 14:05:09 -0400 Date: Mon, 03 Oct 1994 11:17:04 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk carlos@vacuum.org (Carlos Toro) writes: # I have a list (Majordomo 1.92) that seems to work fine with Internet mail, # but someone on MCI-Mail sent a "help" message and got the response: # # > From: AVS-Majordomo \ Internet: (majordomo@vacuum.org) # > To: Donna Bakale \ MCI Mail: (TMPDONNA / MCI ID: # > 428-1920) # > # > Subject: Majordomo results: RFI # > # > -- # > # > >>>> -- [ From: Donna Bakale * EMC.Ver #2.0 ] -- # > END OF COMMANDS # # i.e. the body of the reply was blank. Furthermore, there is no record in my # Log file that this request was made. Is this indeed an MCI-Mail related # problem, or is there something else going on? # # Thanks for all replies, # # Carlos # # Looks to me like MCI begins their outgoing messages with "-- [ From: ...". Majordomo sees the leading "--" on the first line, thinks it's gotten to the signature block of the message, and stops processing commands (as if it had reached an "end" command). If you don't like this behavior, comment out the code in the main command-processing loop of Majordomo that recognizes lines beginning with "-" and treats them the same as the "end" command. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Mon Oct 3 13:03:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id TAA12758; Mon, 3 Oct 1994 19:16:24 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id MAA12752; Mon, 3 Oct 1994 12:16:17 -0700 Received: from webcom.com (webcom.com [165.227.43.1]) by miles.greatcircle.com (8.6.5/Miles-941001) with SMTP id MAA21323 for ; Mon, 3 Oct 1994 12:17:00 -0700 Message-Id: <199410031917.MAA21323@miles.greatcircle.com> Received: by webcom.com (1.38.193.5/16.2) id AA05302; Mon, 3 Oct 1994 12:13:13 -0700 From: Thomas Leavitt Subject: Usage tracking... To: majordomo-users@greatcircle.com Date: Mon, 3 Oct 94 12:13:12 PDT Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, Is there a simple way to track the number and size of mail messages sent by a particular list? We need to know this to be able to bill people properly for the resources they are consuming on our server. Are there any patches, or pieces of code we can insert in a pipeline, to do this? Thomas -- Web Communications Thomas Leavitt--leavitt@webcom.com Voice: (408) 457-9671 Lead Systems & Network Admin./Tech Suppt. Web Communications Home Page From majordomo-users-owner Wed Oct 5 00:13:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id AAA17236; Wed, 5 Oct 1994 00:13:21 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA17230; Tue, 4 Oct 1994 17:13:15 -0700 Received: from virginia.edu (uvaarpa.Virginia.EDU [128.143.2.7]) by miles.greatcircle.com (8.6.5/Miles-941004-1) with SMTP id RAA27387 for ; Tue, 4 Oct 1994 17:13:59 -0700 Received: from darwin.clas.virginia.edu by uvaarpa.virginia.edu id aa00642; 4 Oct 94 20:13 EDT Received: (from mre2b@localhost) by darwin.clas.Virginia.EDU (8.6.8/8.6.6) id UAA37482 for majordomo-users@greatcircle.com; Tue, 4 Oct 1994 20:13:15 -0400 From: Matthew Elkin Message-Id: <199410050013.UAA37482@darwin.clas.Virginia.EDU> Subject: Reply-to: header with mmdf mailer To: majordomo-users@greatcircle.com Date: Tue, 4 Oct 94 20:13:15 EDT X-Mailer: PENELM [version 2.3.1 PL11] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Majordomo-users: I looked up how to add Reply-To headers in the FAQ and it seemed pretty simple. However, when I asked the people who run majordomo here to add the header to my mailing list they gave me this reply. AC Capehart wrote: >From: AC Capehart >To: Matthew Elkin >Subject: Re: help on configuring mailing list (fwd) [...] >We use majordomo to administer lists, NOT to deliver mail. We use >mmdf to deliver mail. We do not use majordomo to deliver mail. Since >mmdf does not use /etc/aliases the way that majordomo does, we cannot >simply add a '-r' option to a line in /etc/aliases to provide the >behavior that you describe. [...] >As has already been stated, the internet community, through the use of >the "RFC" mechanism, has decided that proper list behavior is to have >replies go to the sender. We are in compliance with that standard and >intend to continue to be. [...] >implement the request. If the request made does not cause other >problems, we try to implement it. Your request has been deemed to >cause other problems. They are: >1) falling out of compliance with an RFC >2) undue amount of time to implement the requested changes >3) possible interruption of mail services to ALL other users. This sounds like nonsense to me, but I am not an expert. Is there something that prevents the Reply-to header from being implemented with an mmdf mailer? Could it interupt mail services to other users? we use version 1.92 of majordomo. I can get other details of our setup if necessary. Please send me private email replies and I can send a summary to majordomo-users if requested, or since I subscribed just for this question you can send it to the list. thanks for your help Matthew Elkin mre2b@virginia.edu From majordomo-users-owner Wed Oct 5 01:55:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id BAA18845; Wed, 5 Oct 1994 01:55:17 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA18839; Tue, 4 Oct 1994 18:55:13 -0700 Received: from vtucs.cc.vt.edu (mail.bev.net [128.173.4.72]) by miles.greatcircle.com (8.6.5/Miles-941004-3) with SMTP id SAA29092 for ; Tue, 4 Oct 1994 18:56:06 -0700 Message-Id: <199410050156.SAA29092@miles.greatcircle.com> Received: from shostakovich.music.vt.edu by vtucs.cc.vt.edu with SMTP (1.37.109.8/16.2) id AA14913; Tue, 4 Oct 1994 21:55:30 -0400 X-Sender: mdavis1@mail.vt.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 4 Oct 1994 21:55:55 -0500 To: majordomo-users@GreatCircle.COM From: mdavis1@vt.edu (Matthew Ross Davis) Subject: where is link() unlink()? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Where in the scripts are the link() and unlink() directives? Matthew Ross Davis Phone: 703 231 5799 | Networking Manager Fax: 703 231 5034 | Department of Music Internet: ross.davis@vt.edu | Virginia Tech http://www.music.vt.edu/ | Blacksburg, VA 24061-0240, USA From majordomo-users-owner Wed Oct 5 02:09:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id CAA18929; Wed, 5 Oct 1994 02:09:31 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id TAA18923; Tue, 4 Oct 1994 19:09:27 -0700 Received: from vtucs.cc.vt.edu (mail.bev.net [128.173.4.72]) by miles.greatcircle.com (8.6.5/Miles-941004-3) with SMTP id TAA29158 for ; Tue, 4 Oct 1994 19:10:21 -0700 Message-Id: <199410050210.TAA29158@miles.greatcircle.com> Received: from shostakovich.music.vt.edu by vtucs.cc.vt.edu with SMTP (1.37.109.8/16.2) id AA17743; Tue, 4 Oct 1994 22:09:51 -0400 X-Sender: mdavis1@mail.vt.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 4 Oct 1994 22:10:15 -0500 To: majordomo-users@GreatCircle.COM From: mdavis1@vt.edu (Matthew Ross Davis) Subject: link() unlink() Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Ok, nevermind, I found it. But I do have another question: is do_unsubscribe the only routine that uses the link() unlink()? To run this on MachTen, the script needs to rename() instead so that the entire file isn't deleted when someone unsubscribes from a list. If you can help or have a hack of your own, please send suggestions this way! Thanks Ross Matthew Ross Davis Phone: 703 231 5799 | Networking Manager Fax: 703 231 5034 | Department of Music Internet: ross.davis@vt.edu | Virginia Tech http://www.music.vt.edu/ | Blacksburg, VA 24061-0240, USA From majordomo-users-owner Wed Oct 5 04:56:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id IAA20893; Wed, 5 Oct 1994 08:59:50 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id BAA20887; Wed, 5 Oct 1994 01:59:44 -0700 Received: from post.demon.co.uk (post.demon.co.uk [158.152.1.72]) by miles.greatcircle.com (8.6.5/Miles-941004-3) with SMTP id CAA01033 for ; Wed, 5 Oct 1994 02:00:36 -0700 Received: from threel.demon.co.uk by post.demon.co.uk id aa29777; 5 Oct 94 9:42 GMT-60:00 Received: from delta.threel.co.uk by yankee.threel.co.uk (4.1/IAY-4Sep1994-1) id AA03043; Wed, 5 Oct 94 09:08:10 BST Received: from prospero.threel.co.uk by delta.threel.co.uk; (5.65/1.1.8.2/15Sep94-0257PM) id AA20883; Wed, 5 Oct 1994 09:08:10 +0100 Message-Id: <9410050808.AA20883@delta.threel.co.uk> X-Sender: iay@delta.threel.co.uk X-Mailer: Windows Eudora Version 1.4.3b4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 05 Oct 1994 09:08:14 -0100 To: majordomo-users@greatcircle.com From: Ian A Young Subject: multiple addresses in reply-to? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Our majordomo was recently sent a message from someone whose headers looked like this: From: x@y.com To: majordomo@threel.co.uk Reply-To: xx@yy.com, x@y.com Majordomo complained about this ("Majordomo@threel.co.uk: xx@yy.com, x@y.com is not a valid return address.") and did not register the subscription. I think a bounce message was probably sent back to the originator as well. Obviously I can subscribe this person myself. My question is: should this be a problem for majordomo, or should it be able to cope with people with multiple addresses in the reply-to field (which, according to my reading of RFC822, is perfectly legal)? I can't find any mention of this in the current FAQs and other documents. -- Ian From majordomo-users-owner Wed Oct 5 15:52:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id PAA23478; Wed, 5 Oct 1994 15:52:55 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id IAA23472; Wed, 5 Oct 1994 08:52:51 -0700 Received: from infoexp.express.com (infoexp.express.com [199.74.247.3]) by miles.greatcircle.com (8.6.5/Miles-941004-3) with ESMTP id IAA02610 for ; Wed, 5 Oct 1994 08:53:24 -0700 Received: from alto.express.com (alto.express.com [199.74.248.4]) by infoexp.express.com (8.6.8/8.6.6) with ESMTP id IAA08781 for ; Wed, 5 Oct 1994 08:52:32 -0700 Received: from [199.74.248.5] (snoopy.express.com [199.74.248.5]) by alto.express.com (8.6.8/8.6.6) with SMTP id IAA13890 for ; Wed, 5 Oct 1994 08:51:45 -0700 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 5 Oct 1994 08:53:58 -0800 To: majordomo-users@GreatCircle.COM From: pzee@express.com (Philip J. Zee) Subject: Two questions about majordomo Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have a couple of questions to ask about majordomo. After some testing of majordomo 1.92, I would like to have it manage several hundred mailing lists. By adding all the aliases to /etc/aliases file make this file huge. So, my first question is: Is it possibe to have /etc/aliases to include another file, which contains all aliases for majordomo and its mailing lists? My second question is asked on the list before, and I didn't pay much attention. I am sorry to ask again, but here it is: How do I disable the "who" command for a certain number of mailing lists, even for the list members? Any help is appreciated, Philip ______________________________________________________________________ Philip J. Zee / / / Information Express / / / 3250 Ash St. o o o / / / Palo Alto, CA 94306 o o / o / / Main: (415) 494-8787 DID: (415) 812-3530 o /o /o / Internet: pzee@express.com / / / ______________________________________________________________________ From majordomo-users-owner Wed Oct 5 16:52:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id QAA23993; Wed, 5 Oct 1994 16:52:04 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id JAA23987; Wed, 5 Oct 1994 09:52:00 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.5/Miles-941004-3) with ESMTP id JAA02946; Wed, 5 Oct 1994 09:52:58 -0700 Message-Id: <199410051652.JAA02946@miles.greatcircle.com> To: mdavis1@vt.edu (Matthew Ross Davis) cc: majordomo-users@greatcircle.com Subject: Re: where is link() unlink()? In-reply-to: Your message of Tue, 4 Oct 1994 21:55:55 -0500 Date: Wed, 05 Oct 1994 09:51:37 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk mdavis1@vt.edu (Matthew Ross Davis) writes: # Where in the scripts are the link() and unlink() directives? These are PERL built-in functions. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Wed Oct 5 17:10:32 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA24162; Wed, 5 Oct 1994 17:10:32 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA24156; Wed, 5 Oct 1994 10:10:27 -0700 Received: from vtucs.cc.vt.edu (mail.bev.net [128.173.4.72]) by miles.greatcircle.com (8.6.5/Miles-941004-3) with SMTP id KAA03086 for ; Wed, 5 Oct 1994 10:11:18 -0700 Message-Id: <199410051711.KAA03086@miles.greatcircle.com> Received: from server.music.vt.edu by vtucs.cc.vt.edu with SMTP (1.37.109.8/16.2) id AA05850; Wed, 5 Oct 1994 13:09:57 -0400 Date: Wed, 5 Oct 1994 13:09:57 -0400 X-Sender: mdavis1@mail.vt.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Brent Chapman From: mdavis1@vt.edu (Matthew Ross Davis) Subject: Re: where is link() unlink()? Cc: majordomo-users@greatcircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk At 09:51 10/5/94 -0700, Brent Chapman wrote: >mdavis1@vt.edu (Matthew Ross Davis) writes: > ># Where in the scripts are the link() and unlink() directives? > >These are PERL built-in functions. Well, I assume PERL recognizes rename() as well, cause I changed the majordomo script to rename() instead of link() and unlink() because of the problem I was having with MachTen. Apparently, this does work, because after I fixed it, I unsubscribed and then resubscribed to a list - everything was fine, and the file didn't get deleted. Matthew Ross Davis Phone: 703 231 5799 | Networking Manager Fax: 703 231 5034 | Department of Music Internet: ross.davis@vt.edu | Virginia Tech http://www.music.vt.edu/ | Blacksburg, VA 24061-0240, USA From majordomo-users-owner Wed Oct 5 17:12:48 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA24180; Wed, 5 Oct 1994 17:12:48 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA24174; Wed, 5 Oct 1994 10:12:43 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.5/Miles-941004-3) with ESMTP id KAA03099; Wed, 5 Oct 1994 10:13:41 -0700 Message-Id: <199410051713.KAA03099@miles.greatcircle.com> To: Ian A Young cc: majordomo-users@greatcircle.com Subject: Re: multiple addresses in reply-to? In-reply-to: Your message of Wed, 05 Oct 1994 09:08:14 -0100 Date: Wed, 05 Oct 1994 10:13:35 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Ian A Young writes: # Our majordomo was recently sent a message from someone whose headers looked # like this: # # From: x@y.com # To: majordomo@threel.co.uk # Reply-To: xx@yy.com, x@y.com # # Majordomo complained about this ("Majordomo@threel.co.uk: xx@yy.com, # x@y.com is not a valid return address.") and did not register the # subscription. I think a bounce message was probably sent back to the # originator as well. Obviously I can subscribe this person myself. # # My question is: should this be a problem for majordomo, or should it # be able to cope with people with multiple addresses in the reply-to # field (which, according to my reading of RFC822, is perfectly legal)? # I can't find any mention of this in the current FAQs and other documents. Majordomo uses the "Reply-To" address, if it's there, as the address to subscribe to the list. What would you say the correct behavior is, in the case of multiple "Reply-To" addresses? Subscribe them all? What if it's an unsubscribe? Or a "which"? I can see several possible answers to each of these, none of them obviously right or wrong. Majordomo currently assumes that there's one relevant address when processing a given message, and uses that address as context for a number of commands (for instance, it uses it as the default address to subscribe if a "subscribe" command doesn't list an address explicitly, or as the address to look for with a "which" command, or as the address to check for on a list in determining whether or not to show a private list in the output of a "lists" command). Making Majordomo support multiple addresses in this context would be _very_ difficult. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Wed Oct 5 22:10:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id WAA25851; Wed, 5 Oct 1994 22:10:11 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id PAA25845; Wed, 5 Oct 1994 15:10:03 -0700 Received: from infoexp.express.com (infoexp.express.com [199.74.247.3]) by miles.greatcircle.com (8.6.5/Miles-941004-3) with ESMTP id PAA04621 for ; Wed, 5 Oct 1994 15:10:58 -0700 Received: from alto.express.com (alto.express.com [199.74.248.4]) by infoexp.express.com (8.6.8/8.6.6) with ESMTP id PAA10055 for ; Wed, 5 Oct 1994 15:10:36 -0700 Received: from [199.74.248.5] (snoopy.express.com [199.74.248.5]) by alto.express.com (8.6.8/8.6.6) with SMTP id PAA15153 for ; Wed, 5 Oct 1994 15:09:49 -0700 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 5 Oct 1994 15:12:00 -0800 To: majordomo-users@GreatCircle.COM From: pzee@express.com (Philip J. Zee) Subject: Two questions about majordomo (summary and solution) Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have sent the following message to this list and I got my answers. >After some testing of majordomo 1.92, I would like to have it manage >several hundred mailing lists. By adding all the aliases to /etc/aliases >file make this file huge. So, my first question is: > >Is it possibe to have /etc/aliases to include another file, which contains >all aliases for majordomo and its mailing lists? Yes, it is possible. Thanks to Bryan Curnutt who pointed out that by adding a file to the OA entry of the sendmail.cf file, I can have multiple files that contain aliases. OA/etc/aliases,/usr/local/lib/majordomo/aliases Once the sendmail.cf is edited, sendmail should be killed and restarted. > >My second question is asked on the list before, and I didn't pay much >attention. I am sorry to ask again, but here it is: > >How do I disable the "who" command for a certain number of mailing lists, >even for the list members? Thanks to "John P. Rouillard" who responded by adding a line like: print REPLY "Who is disabled", return if $clean_list eq ""; in the function do_who. I finished the modification, and everything works as I requested. If anyone would like to see the patch, I'd be glad to supply it. My thanks to all who responded. Philip ______________________________________________________________________ Philip J. Zee / / / Information Express / / / 3250 Ash St. o o o / / / Palo Alto, CA 94306 o o / o / / Main: (415) 494-8787 DID: (415) 812-3530 o /o /o / Internet: pzee@express.com / / / ______________________________________________________________________ From majordomo-users-owner Thu Oct 6 00:12:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id AAA26802; Thu, 6 Oct 1994 00:12:22 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA26793; Wed, 5 Oct 1994 17:12:15 -0700 Received: from casbs.Stanford.EDU (casbs.Stanford.EDU [36.30.0.10]) by miles.greatcircle.com (8.6.5/Miles-941005-1) with SMTP id RAA06222 for ; Wed, 5 Oct 1994 17:13:10 -0700 Received: from localhost.Stanford.EDU by casbs.Stanford.EDU (4.1/1.34) id AA18258; Wed, 5 Oct 94 17:12:37 PDT Message-Id: <9410060012.AA18258@casbs.Stanford.EDU> To: majordomo-users@greatcircle.com Planet: Earth Subject: /tmp filling up with resend.xxxx.in/out files Date: Wed, 05 Oct 94 17:12:37 -0700 From: Patrick Goebel Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk [I sent this message to the list address a couple of days ago, but it *seems* to have vanished into the ether. Apologies if you are seeing this for the second time.] After upgrading from 1.62 to 1.92, I noticed that my /tmp directory is accumulating large numbers of files whose names are of the form: resend.xxxx.in resend.xxxx.out where is xxxx is typically a 4 or 5 digit number. Many of these files are up to a week old (I upgraded about a week ago). At last count, I am up to 730 such files. I don't believe these files should be sticking around so long. Do I have something configured incorrectly? As far as I can tell, all routine Majordomo operations are functioning smoothly. Cheers, -------------------------------------------------------------------> Patrick Goebel | voice: (415) 321-2052 ------ __o CASBS/GCN/VeloNet | fax: (415) 321-1192 ------- _`\<,_ 202 Junipero Serra Blvd. | ---- (*)/ (*) Stanford, CA 94305 | High Speed Digital Commuter -------------------------------------------------------------------> From majordomo-users-owner Thu Oct 6 00:31:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id AAA26897; Thu, 6 Oct 1994 00:31:44 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA26891; Wed, 5 Oct 1994 17:31:39 -0700 Received: from webcom.com (webcom.com [165.227.43.1]) by miles.greatcircle.com (8.6.5/Miles-941005-1) with SMTP id RAA06713 for ; Wed, 5 Oct 1994 17:32:26 -0700 Message-Id: <199410060032.RAA06713@miles.greatcircle.com> Received: by webcom.com (1.38.193.5/16.2) id AA03646; Wed, 5 Oct 1994 17:28:48 -0700 From: Thomas Leavitt Subject: /tmp filling up with resend.xxxx.in/out files (fwd) To: majordomo-users@greatcircle.com Date: Wed, 5 Oct 94 17:28:47 PDT Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > -------------------------------------------------------------------> > Patrick Goebel | voice: (415) 321-2052 ------ __o [Comments on /tmp filling up with resend.* ] I too have noticed this phenomenon with 1.92. An answer would be appreciated. -- Web Communications Thomas Leavitt--leavitt@webcom.com Voice: (408) 457-9671 Lead Systems & Network Admin./Tech Suppt. Web Communications Home Page From majordomo-users-owner Thu Oct 6 13:18:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id NAA01293; Thu, 6 Oct 1994 13:18:45 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id GAA01287; Thu, 6 Oct 1994 06:18:41 -0700 Received: from mv.mv.com (uucp@mv.MV.COM [192.80.84.1]) by miles.greatcircle.com (8.6.5/Miles-941005-1) with ESMTP id GAA10038 for ; Thu, 6 Oct 1994 06:19:35 -0700 Received: by mv.mv.com (8.6.9/mv(b)/mem-940616) id JAA06151; Thu, 6 Oct 1994 09:18:57 -0400 Received: from magpie.mv.com by summa4.mv.COM (4.1/SMI-4.1) id AA10604; Thu, 6 Oct 94 09:02:52 EDT Date: Thu, 6 Oct 94 09:02:52 EDT From: lrc@summa4.MV.COM (Lawrence R. Cook) Message-Id: <9410061302.AA10604@summa4.mv.COM> To: majordomo-users@GreatCircle.COM, patrick@casbs.Stanford.EDU, leavitt@webcom.com Subject: Re: /tmp filling up with resend.xxxx.in/out files Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > From: Patrick Goebel > After upgrading from 1.62 to 1.92, I noticed that my /tmp directory is > accumulating large numbers of files whose names are of the form: > > resend.xxxx.in > resend.xxxx.out > From: Thomas Leavitt > I too have noticed this phenomenon with 1.92. Here is the fix to resend that I made to solve the problem: 347c347 < unlink("/tmp/resend.$$.*"); --- > unlink(); The angle brackets are needed in order to do the filename expansion. --------------------------------------------------------------------- Larry Cook, Senior Software Engineer Email: lrc@summa4.mv.com Summa Four, Inc. Phone: (603) 625-4050 x2566 25 Sundial Ave, Manchester, NH 03103-7251 Fax : (603) 668-4491 From majordomo-users-owner Thu Oct 6 14:50:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id OAA01850; Thu, 6 Oct 1994 14:50:14 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id HAA01843; Thu, 6 Oct 1994 07:50:10 -0700 Received: from white.lambton.on.ca (white.lambton.on.ca [192.139.190.2]) by miles.greatcircle.com (8.6.5/Miles-941005-1) with SMTP id HAA10501 for ; Thu, 6 Oct 1994 07:51:01 -0700 Date: Thu, 6 Oct 1994 10:49:37 -0400 (EDT) From: David Grant Subject: Automatic processing of -request messages? To: Majordomo users Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I tried to post this once before and it seemed to get lost in the ether, sorry if you see it twice. Forgive me if this is a FAQ, I would like to have mail sent to the -request address with a single 'subscribe' or 'unsibscribe' command processed by majordomo (like the help messages say) instead of request-answer just sending the message back. I'm running version 1.92 on a DEC Alpha with Perl 4.036. If I change the -request alias to run majordomo it doesn't seem to know which list the mail was sent to. Is there a parameter you pass as well or is this a sendmail config problem or am I missing something obvious? Thanks, Dave ----- David Grant VE3DGR +1 519 542-7751 x348 Lambton College, Sarnia, ON, CANADA +1 519 542-6667 FAX From majordomo-users-owner Thu Oct 6 17:25:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA02977; Thu, 6 Oct 1994 17:25:27 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA02971; Thu, 6 Oct 1994 10:25:22 -0700 Received: from vader.egr.uri.edu (vader.egr.uri.edu [131.128.50.80]) by miles.greatcircle.com (8.6.5/Miles-941005-1) with SMTP id KAA11429 for ; Thu, 6 Oct 1994 10:26:17 -0700 Received: by vader.egr.uri.edu (5.65/DEC-Ultrix/4.3) id AA19784; Thu, 6 Oct 1994 13:12:45 -0400 From: whiten@vader.egr.uri.edu (Noah White) Message-Id: <9410061712.AA19784@vader.egr.uri.edu> Subject: Majordomo died suddenly! To: majordomo-users@greatcircle.com Date: Thu, 6 Oct 1994 13:12:44 -0400 (EDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 436 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk All of a sudden my mailing list died. It has worked fine for months, now all commands procesed return this error in a mail message to the list owner: |/turnstone/majordomo/wrapper majordomo...unknown mailer error 5 This is not limited to majordomo but also digest and anything else wrapper tries to run. Any help would be greatly appreciated because everything is dead, and the strange part is I did not change anything. -Noah From majordomo-users-owner Thu Oct 6 17:36:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA03060; Thu, 6 Oct 1994 17:36:18 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA03054; Thu, 6 Oct 1994 10:36:14 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.5/Miles-941005-1) with ESMTP id KAA11495; Thu, 6 Oct 1994 10:37:12 -0700 Message-Id: <199410061737.KAA11495@miles.greatcircle.com> To: whiten@vader.egr.uri.edu (Noah White) cc: majordomo-users@greatcircle.com Subject: Re: Majordomo died suddenly! In-reply-to: Your message of Thu, 6 Oct 1994 13:12:44 -0400 (EDT) Date: Thu, 06 Oct 1994 10:37:09 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk whiten@vader.egr.uri.edu (Noah White) writes: # # All of a sudden my mailing list died. It has worked fine for months, # now all commands procesed return this error in a mail message to the # list owner: # # |/turnstone/majordomo/wrapper majordomo...unknown mailer error 5 # # This is not limited to majordomo but also digest and anything else # wrapper tries to run. # # Any help would be greatly appreciated because everything is dead, and # the strange part is I did not change anything. # # -Noah # # Look at where the "wrapper.c" program does an "exit(5)" call. It only does that if the attempt to execute the script in question (majordomo, digest, or whatever) fails. Reasons it might fail include: The scripts aren't in the W_BIN that was compiled into wrapper. The scripts aren't executable any more The perl interpreter isn't executable any more The perl interpreter isn't in /usr/local/bin/perl any more etc. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Thu Oct 6 19:08:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id TAA04100; Thu, 6 Oct 1994 19:08:39 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id MAA04094; Thu, 6 Oct 1994 12:08:35 -0700 Received: from is5.mdc.com (IS5.MDC.COM [129.200.1.45]) by miles.greatcircle.com (8.6.5/Miles-941005-1) with SMTP id MAA12225 for ; Thu, 6 Oct 1994 12:09:15 -0700 Received: by is5.mdc.com (5.65c/1.921207) id AA05079; Thu, 6 Oct 1994 12:08:34 -0700 From: ken@is5.mdc.com (Ken Williams) Message-Id: <199410061908.AA05079@is5.mdc.com> Subject: Long file names To: Majordomo-Users@greatcircle.com Date: Thu, 6 Oct 94 12:08:33 PDT Reply-To: ken@is5.mdc.com X-Mailer: ELM [version 07.00.00.00 (2.3 PL11)] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have been running Majordomo 1.62 for a few years now, with a few patches of my own! I finally decided I had better look at 1.92 and see whats up. My problem is, the system I have it running on (Intergraph, CLIX) doesn't allow for very long file names. I think the max is 14. Majordomo 1.92 seems to want to put some long file names out there and it just doesn't work. Names like $listname.config.out. If the listname is >3 chars, it won't fit. It will create a file, truncating the name, but when there is a test for a file, it doesn't truncate. Has anyone run into this trouble? What did you do? Is there an easy fix without munging all of the file names? TIA -- ------------------------------------------------------- Ken Williams Douglas Aircraft Company Information Systems Long Beach, California Internet: ken@is5.mdc.com Mail Code 36-31 CIS: 71544,3070 (310) 496-6588 ------------------------------------------------------- From majordomo-users-owner Thu Oct 6 19:09:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id TAA04114; Thu, 6 Oct 1994 19:09:18 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id MAA04108; Thu, 6 Oct 1994 12:09:13 -0700 Received: from virginia.edu (uvaarpa.Virginia.EDU [128.143.2.7]) by miles.greatcircle.com (8.6.5/Miles-941005-1) with SMTP id MAA12229 for ; Thu, 6 Oct 1994 12:10:08 -0700 Received: from darwin.clas.virginia.edu by uvaarpa.virginia.edu id aa05277; 6 Oct 94 15:08 EDT Received: (from mre2b@localhost) by darwin.clas.Virginia.EDU (8.6.8/8.6.6) id PAA154444 for majordomo-users@greatcircle.com; Thu, 6 Oct 1994 15:08:27 -0400 From: Matthew Elkin Message-Id: <199410061908.PAA154444@darwin.clas.Virginia.EDU> Subject: Reply-to header, resend, mmdf To: majordomo-users@greatcircle.com Date: Thu, 6 Oct 94 15:08:27 EDT X-Mailer: PENELM [version 2.3.1 PL11] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk My problem that I posted earlier was getting the reply-to header added to the msgs sent on the mailing list. I've found that in 1.92 this is done through the config command. So I've set the reply-to header to refer to the mailing list. But apparently the header options in config aren't working. The precedence header which is supposed to say "bulk" isn't getting added either. Is the there a way to add the reply-to header without using resend? Can resend be used with our mailer: mmdf? I am able to add a header with elm and send it to the list and it will stay on, so it isn't getting stripped somewhere along the line. thanks for your help. matt; mre2b@virginia.edu From majordomo-users-owner Thu Oct 6 17:45:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id WAA05822; Thu, 6 Oct 1994 22:55:18 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id PAA05813; Thu, 6 Oct 1994 15:55:09 -0700 Received: from campus.mty.itesm.mx (lfasano@campus.mty.itesm.mx [131.178.4.5]) by miles.greatcircle.com (8.6.5/Miles-941005-1) with ESMTP id PAA14289 for ; Thu, 6 Oct 1994 15:56:01 -0700 Received: (from lfasano@localhost) by campus.mty.itesm.mx (8.6.9/8.6.9) id QAA48452 for majordomo-users@greatcircle.com; Thu, 6 Oct 1994 16:55:22 -0600 From: Luis Fasano Message-Id: <199410062255.QAA48452@campus.mty.itesm.mx> Subject: Help with this error!!!! To: majordomo-users@greatcircle.com Date: Thu, 6 Oct 1994 16:55:21 -0600 (CST) X-Mailer: ELM [version 2.4 PL13] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Well... i've already send something like this, but haven't received any response. I'm getting this message Date: Thu, 6 Oct 1994 21:26:11 GMT Subject: Returned mail: Insufficient permission: Error 0 To: servinf-owner@campus.mty.itesm.mx The original message was received at Thu, 6 Oct 1994 21:23:42 GMT from daemon@localhost ----- The following addresses had delivery problems ----- Lic. Ma. Magdalena Flores Ortega (unrecoverable error) (expanded from: :include:/home/majordom/lists/servinf) Ing. Orlando Pugliese (unrecoverable error) (expanded from: :include:/home/majordom/lists/servinf) Oscar I look for it in the FAQ and several other places, and i havent found anything related. Any pointer???? Luis From majordomo-users-owner Fri Oct 7 16:13:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id QAA13327; Fri, 7 Oct 1994 16:13:40 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id JAA13321; Fri, 7 Oct 1994 09:13:35 -0700 Received: from noc4.dccs.upenn.edu (NOC4.DCCS.UPENN.EDU [128.91.254.39]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id JAA21556 for ; Fri, 7 Oct 1994 09:14:13 -0700 From: murphy@dccs.upenn.edu Received: from LAM.DCCS.UPENN.EDU by noc4.dccs.upenn.edu id AA11682; Fri, 7 Oct 94 12:12:28 -0400 Received: by lam.dccs.upenn.edu id AA26078; Fri, 7 Oct 1994 12:11:53 -0400 Date: Fri, 7 Oct 1994 12:11:53 -0400 Posted-Date: Fri, 7 Oct 1994 12:11:53 -0400 Message-Id: <9410071611.AA26078@lam.dccs.upenn.edu> To: majordomo-users@greatcircle.com, unix-listproc@avs.com Subject: The results of the list server performance survey Reply-To: murphy@dccs.upenn.edu Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk http://lam.dccs.upenn.edu/~murphy/performance.listservice.survey.html If you don't have a www client, telnet to one of the many anonymous lynx browsers on the Internet and use the 'g' command. --lam ____________________________________________ | | | Linda A Murphy | | murphy@dccs.upenn.edu | | http://lam.dccs.upenn.edu/~murphy/ | | Lead Programmer/Analyst | | PennNet Services Development & Support | | Data Communications & Computing Services | | University of Pennsylvania | |__________________________________________| From majordomo-users-owner Fri Oct 7 17:49:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA13937; Fri, 7 Oct 1994 17:49:04 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA13930; Fri, 7 Oct 1994 10:48:59 -0700 Received: from webcom.com (webcom.com [165.227.43.1]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id KAA22051 for ; Fri, 7 Oct 1994 10:49:49 -0700 Message-Id: <199410071749.KAA22051@miles.greatcircle.com> Received: by webcom.com (1.38.193.5/16.2) id AA21259; Fri, 7 Oct 1994 10:45:49 -0700 From: Thomas Leavitt Subject: Include in /usr/lib/aliases To: majordomo-users@greatcircle.com Date: Fri, 7 Oct 94 10:45:49 PDT Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'd like to be able to edit the aliases for lists without having to go into root and modify the /usr/lib/aliases file directly. I am using HP-UX 9.04 with Sendmail 5.65 (default HP distribution). I tried the example in the documentation, but it didn't work. -- Web Communications Thomas Leavitt--leavitt@webcom.com Voice: (408) 457-9671 Lead Systems & Network Admin./Tech Suppt. Web Communications Home Page From majordomo-users-owner Fri Oct 7 19:44:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id TAA14826; Fri, 7 Oct 1994 19:44:54 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id MAA14820; Fri, 7 Oct 1994 12:44:48 -0700 Received: from nova.unix.portal.com (nova.unix.portal.com [156.151.1.101]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id MAA22547 for ; Fri, 7 Oct 1994 12:45:41 -0700 Received: from jobe.shell.portal.com (jobe.shell.portal.com [156.151.3.4]) by nova.unix.portal.com (8.6.7/8.6.5) with ESMTP id MAA02321 for ; Fri, 7 Oct 1994 12:45:03 -0700 Received: from localhost (chan@localhost) by jobe.shell.portal.com (8.6.4/8.6.5) id MAA26066 for majordomo-users@greatcircle.com; Fri, 7 Oct 1994 12:45:01 -0700 Date: Fri, 7 Oct 1994 12:45:01 -0700 From: Jeff Chan Message-Id: <199410071945.MAA26066@jobe.shell.portal.com> To: majordomo-users@greatcircle.com Subject: How to make replies go to author, not list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Can anyone tell me how to make replies go to the author and not the list under 1.62? Jeff Chan chan@shell.portal.com From majordomo-users-owner Fri Oct 7 22:14:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id WAA15526; Fri, 7 Oct 1994 22:14:11 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id PAA15520; Fri, 7 Oct 1994 15:14:06 -0700 Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id PAA22995 for ; Fri, 7 Oct 1994 15:12:28 -0700 Received: from questa.esd.sgi.com by sgi.sgi.com via ESMTP (940627.SGI.8.6.9/910110.SGI) for <@sgi.sgi.com:majordomo-users@GreatCircle.COM> id PAA22916; Fri, 7 Oct 1994 15:11:04 -0700 Received: by questa.esd.sgi.com (940816.SGI.8.6.9/940406.SGI.AUTO) for majordomo-users@GreatCircle.COM id PAA22813; Fri, 7 Oct 1994 15:10:52 -0700 From: "Mats Wichmann (mipsABI Consultant)" Message-Id: <9410071510.ZM22811@questa.esd.sgi.com> Date: Fri, 7 Oct 1994 15:10:49 -0700 X-Mailer: Z-Mail (3.2b.1001 01oct94 MediaMail) To: majordomo-users@GreatCircle.COM Subject: problem with digest Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm having a bit of strange behavior trying to set up digest. I get the following error back from sendmail when articles come in: ----- The following addresses had delivery problems ----- "| /usr/local/majordomo/wrapper digest -r -C -l cplusplus-digest" (unrecoverable error) (expanded from: cplusplus-outgoing) ----- Transcript of session follows ----- -l: No such file or directory 554 "| /usr/local/majordomo/wrapper digest -r -C -l cplusplus-digest"... unknown mailer error 2 Yet if I clip the line exactly from the above and use it manually, as in: # cat article | /usr/local/majordomo/wrapper digest -r -C -l cplusplus-digest It works exactly as I'd expect. Where am I erring? -- mats From majordomo-users-owner Fri Oct 7 23:53:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id XAA16020; Fri, 7 Oct 1994 23:53:19 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id QAA16014; Fri, 7 Oct 1994 16:53:13 -0700 Received: from moolah.fml.tuwien.ac.at (manitu@moolah.fml.tuwien.ac.at [128.130.167.135]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id QAA23547 for ; Fri, 7 Oct 1994 16:53:57 -0700 Received: by moolah.fml.tuwien.ac.at id AA02548 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Sat, 8 Oct 1994 00:53:11 +0100 From: Christian Greissing Message-Id: <199410072353.AA02548@moolah.fml.tuwien.ac.at> Subject: Reply-To problems To: majordomo-users@greatcircle.com Date: Sat, 8 Oct 1994 00:53:09 +0100 (MET) X-Mailer: ELM [version 2.4 PL5] Content-Type: text Content-Length: 373 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello 1 Could anyone help me with my mailer problem. I am using majordomo-1.92 The sendmail is configured to add the reply-to address for the domain and not the host. But I should have the reply-to address set to he host where majordomo is running! the -r option isn't working !! Thanks Christian ! Please send answers to manitu@moolah.fml.tuwien.ac.at or to the list From majordomo-users-owner Fri Oct 7 23:58:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id XAA16036; Fri, 7 Oct 1994 23:58:31 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id QAA16030; Fri, 7 Oct 1994 16:58:25 -0700 Received: from kbrown.oldcampus.yale.edu (root@kbrown.oldcampus.yale.edu [130.132.128.124]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id QAA23559 for ; Fri, 7 Oct 1994 16:59:19 -0700 Received: by kbrown.oldcampus.yale.edu (Linux Smail3.1.28.1 #1) id m0qtPBL-0005c3C; Fri, 7 Oct 94 19:58 EDT Date: Fri, 7 Oct 1994 19:58:33 +0100 From: Vince - The Almighty One Subject: need help for list/digest To: majordomo-users@GreatCircle.COM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've currently taken over the job of someone that used to run a digest under listserv for unix and it handled subscriptions using Majordomo, now I want to use Majordomo which I have gain permission for maintaining the digest, what i want to know is how do i begin with majordomo to maintain both a list and a digest. Any help would be greatly appreciated. Cheers, Vince E-mail: vince@kbrown.oldcampus.yale.edu,\|/ Sys Adm - CircleStar Technologies,Inc. root@berkeley.circlestar.com,(o o) San Francisco, California USA _________________________oOO__(_)__OOo_____________________________ | There are many forms of science but only physics is the quantum | | leap of the 21st Century. | \_________________________________________________________________/ uPoy@physics.ucla.edu UCLA Physics Los Angeles, California USA From majordomo-users-owner Sat Oct 8 00:53:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id AAA16459; Sat, 8 Oct 1994 00:53:08 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA16453; Fri, 7 Oct 1994 17:53:01 -0700 Received: from kbrown.oldcampus.yale.edu (root@kbrown.oldcampus.yale.edu [130.132.128.124]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id RAA23982 for ; Fri, 7 Oct 1994 17:53:47 -0700 Received: by kbrown.oldcampus.yale.edu (Linux Smail3.1.28.1 #1) id m0qtQ23-0005cAC; Fri, 7 Oct 94 20:53 EDT Date: Fri, 7 Oct 1994 20:53:02 +0100 From: Vince - The Almighty One Subject: need help for list/digest To: majordomo-users@GreatCircle.COM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've currently taken over the job of someone that used to run a digest under mailserv for unix and it handled subscriptions using Majordomo, now I want to use Majordomo which I have gain permission for maintaining the digest, what i want to know is how do i begin with majordomo to maintain both a list and a digest. Any help would be greatly appreciated. Cheers, Vince E-mail: vince@kbrown.oldcampus.yale.edu,\|/ Sys Adm - CircleStar Technologies,Inc. root@berkeley.circlestar.com,(o o) San Francisco, California USA _________________________oOO__(_)__OOo_____________________________ | There are many forms of science but only physics is the quantum | | leap of the 21st Century. | \_________________________________________________________________/ uPoy@physics.ucla.edu UCLA Physics Los Angeles, California USA From majordomo-users-owner Sat Oct 8 12:13:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id MAA21033; Sat, 8 Oct 1994 12:13:54 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id FAA21021; Sat, 8 Oct 1994 05:13:47 -0700 Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id FAA00239 for ; Sat, 8 Oct 1994 05:14:42 -0700 Received: from wolves.UUCP by duke.cs.duke.edu (5.65/3.10G/4.1.3) id AA25589; Sat, 8 Oct 94 08:14:18 -0400 Received: from dithots by wolves.durham.nc.us with uucp (Linux Smail3.1.28.1 #5) id m0qtaGq-0000b5C; Sat, 8 Oct 94 07:49 EDT Received: by dithots.dithots.org (Linux Smail3.1.28.1 #1) id m0qta4p-00014WC; Sat, 8 Oct 94 07:36 EDT Date: Sat, 8 Oct 1994 07:36:35 +0100 From: "George W. Pogue" Subject: Help. To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk How do I stop a mailing list from showing up in the lists command? I know it is the noadvertise/advertise options but I'm not familar enough with regexps yet to know how to set it up. Also, how does the bounce list work? Does it get updated automatically or do I do that by hand when I notice a bounced message? bill From majordomo-users-owner Sun Oct 9 16:44:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id QAA28201; Sun, 9 Oct 1994 16:44:08 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id JAA28195; Sun, 9 Oct 1994 09:44:03 -0700 Received: from netcom13.netcom.com (sylviac@netcom13.netcom.com [192.100.81.125]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id JAA05600 for ; Sun, 9 Oct 1994 09:45:01 -0700 Received: by netcom13.netcom.com (8.6.9/Netcom) id JAA12329; Sun, 9 Oct 1994 09:44:02 -0700 From: sylviac@netcom.com (Sylvia Caras) Message-Id: <199410091644.JAA12329@netcom13.netcom.com> Subject: Approve To: majordomo-users@greatcircle.com Date: Sun, 9 Oct 1994 09:44:01 -0700 (PDT) Organization: Mood Matters X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 760 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > >Because many subscriptions were improper in form and because netcom allows > >me access to back logs for only a few days, I asked that my list flag > >be set to approve all subscriptions. > > > >Since then, I have had NO subscriptions of improper form to correct! > >Is there something in the approve program that is filtering that wasn't > >happening before? > > > >Is there a difference between majordomo 1.92 and the earlier version? > >Netcom is using both. > > I don't know the answer, but this message really should have been posted to > Majordomo-Users@GreatCircle.COM, rather than List-Managers@GreatCircle.COM, > since it's completely Majordomo-specific. I suspect you'd get more and > better answers from Majordomo-Users, too. > > > -Brent > From majordomo-users-owner Mon Oct 10 04:03:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA03175; Mon, 10 Oct 1994 10:23:59 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id DAA03163; Mon, 10 Oct 1994 03:23:45 -0700 Received: from sigma.itu.ch (sigma.itu.ch [156.106.128.30]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id DAA08287 for ; Mon, 10 Oct 1994 03:24:39 -0700 Received: from MR.ITU.CH by ITU.CH (PMDF V4.3-7 #4298) id <01HI3YFC7ZZK9FP5WD@ITU.CH>; Mon, 10 Oct 1994 11:25:17 CET Received: with PMDF-MR; Mon, 10 Oct 1994 10:25:07 CET MR-Received: by mta TIES.MUAS; Relayed; Mon, 10 Oct 1994 10:25:07 +0100 MR-Received: by mta TAU; Relayed; Mon, 10 Oct 1994 10:25:24 +0100 Disclose-recipients: prohibited Date: Mon, 10 Oct 1994 10:25:07 +0100 (CET) From: JARLE MARTINSEN +41 22 730 5949 Subject: pid file...? To: Majordomo-Users Message-id: <8507251110101994/A31000/TAU/118A52D90400*@MHS> X-Envelope-to: Majordomo-Users@GreatCircle.COM Autoforwarded: false MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Importance: normal Priority: urgent Sensitivity: Company-Confidential UA-content-id: 118A52D90400 X400-MTS-identifier: [;8507251110101994/A31000/TAU] Hop-count: 1 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, wu-ftpd seems to be running OK on my DEC Alpha 3600, osf/1 v2.0 But I do get the following message in my syslog... daemon.log:Oct 9 23:44:06 seit ftpd[21999]: open of pid file failed: No such file or directory Any idea... Thanks Rgrds, /jarle Jarle Martinsen International Telecomunnication Union (ITU) Place des nations CH-1211 Geneva 20 Switzerland Internet: martinsen@itu.ch X.400: S=martinsen; P=itu; A=arcom; C=ch Voice: +41 22 730 5949 Fax: +41 22 730 5337 From majordomo-users-owner Mon Oct 10 13:19:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id NAA03962; Mon, 10 Oct 1994 13:19:29 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id GAA03956; Mon, 10 Oct 1994 06:19:24 -0700 Received: from sigma.itu.ch (sigma.itu.ch [156.106.128.30]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id GAA08762 for ; Mon, 10 Oct 1994 06:20:11 -0700 Received: from MR.ITU.CH by ITU.CH (PMDF V4.3-7 #4298) id <01HI44M6KLDC9FOZ8H@ITU.CH>; Mon, 10 Oct 1994 14:20:18 CET Received: with PMDF-MR; Mon, 10 Oct 1994 13:13:16 CET MR-Received: by mta TIES.MUAS; Relayed; Mon, 10 Oct 1994 13:13:16 +0100 MR-Received: by mta TAU; Relayed; Mon, 10 Oct 1994 13:13:22 +0100 Disclose-recipients: prohibited Date: Mon, 10 Oct 1994 13:13:16 +0100 (CET) From: JARLE MARTINSEN +41 22 730 5949 Subject: Re: pid file...? In-reply-to: <8507251110101994/A31000/TAU/118A52D90400*@MHS> To: Majordomo-Users Message-id: <6816131410101994/A31976/TAU/118A538D0E00*@MHS> X-Envelope-to: Majordomo-Users@GreatCircle.COM Autoforwarded: false MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Importance: normal Priority: urgent Sensitivity: Company-Confidential UA-content-id: 118A538D0E00 X400-MTS-identifier: [;6816131410101994/A31976/TAU] Hop-count: 1 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Please neglect previous mail (see subj). It was sent to wrong listserv. Sorry for any inconvinience. /jarle From majordomo-users-owner Mon Oct 10 17:09:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA04941; Mon, 10 Oct 1994 17:09:24 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA04935; Mon, 10 Oct 1994 10:09:19 -0700 Received: from freeside.fc.net (freeside.fc.net [198.6.198.2]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id KAA09445 for ; Mon, 10 Oct 1994 10:10:20 -0700 Received: (from kevintx@localhost) by freeside.fc.net (8.6.8.1/8.6.6) id MAA00785 for majordomo-users@greatcircle.com; Mon, 10 Oct 1994 12:13:27 -0500 From: Admin/Support Message-Id: <199410101713.MAA00785@freeside.fc.net> Subject: private mailing lists To: majordomo-users@greatcircle.com Date: Mon, 10 Oct 1994 12:13:26 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 478 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The README for Majordomo 1.92 claims that Majordomo supports mailing lists that don't show up to the "lists" command, and I've tried to use the noadvertise command in the .config file to accomplish this, but noadvertise * doesn't stop the list from appearing to "lists".. can anyone help me with this? thanks, kevin -- kevintx@fc.net support@fc.net (see also kevintx@paranoia.com) Freeside Communications (512) 339-6094 *Internet Access for the Future!* From majordomo-users-owner Mon Oct 10 18:02:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA05166; Mon, 10 Oct 1994 18:02:43 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA05160; Mon, 10 Oct 1994 11:02:39 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id LAA09607 for ; Mon, 10 Oct 1994 11:03:34 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA23430 (5.65c/IDA-1.4.4 for ); Mon, 10 Oct 1994 14:02:09 -0400 Message-Id: <199410101802.AA23430@cs.umb.edu> To: Admin/Support Cc: majordomo-users@greatcircle.com Subject: Re: private mailing lists In-Reply-To: Your message of "Mon, 10 Oct 1994 12:13:26 CDT." <199410101713.MAA00785@freeside.fc.net> Date: Mon, 10 Oct 1994 14:01:52 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199410101713.MAA00785@freeside.fc.net>, Admin/Support writes: >The README for Majordomo 1.92 claims that Majordomo supports mailing >lists that don't show up to the "lists" command, and I've tried to use >the noadvertise command in the .config file to accomplish this, but >noadvertise * doesn't stop the list from appearing to "lists".. can >anyone help me with this? Try /.*/ With the slashes, and the dot. It needs a perl regexp, not a glob pattern. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Mon Oct 10 18:50:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA05381; Mon, 10 Oct 1994 18:50:40 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA05375; Mon, 10 Oct 1994 11:50:36 -0700 Received: from crlmail.uchicago.edu (crlmail.uchicago.edu [128.135.73.3]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id LAA09757 for ; Mon, 10 Oct 1994 11:51:35 -0700 Received: from crlpc1.uchicago.edu (crlpc1.uchicago.edu [128.135.158.2]) by crlmail.uchicago.edu (8.6.5/8.6.5) with SMTP id NAA00274 for ; Mon, 10 Oct 1994 13:42:29 -0500 Message-Id: <199410101842.NAA00274@crlmail.uchicago.edu> X-Sender: oby@crlmail.uchicago.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 10 Oct 1994 13:46:16 -1100 To: majordomo-users@GreatCircle.COM From: oby@crlmail.uchicago.edu (Tyrone L. Oby) Subject: problems with permissions X-Mailer: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk After installing Majordomo 1.92, I started testing portion of it. It passed the help test + request test. When I try to scribe to my test list I get the following message mailed back: shlock: open(">/home/majordom/lists/shlock.180"): Permission denied at /home/majordomo/majordomo-1.92/shlock.pl line 131,<> line 1. I know permission is critical with Majordomo. but is their any simple method to insure the correct perms. From majordomo-users-owner Mon Oct 10 19:11:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id TAA05516; Mon, 10 Oct 1994 19:11:39 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id MAA05510; Mon, 10 Oct 1994 12:11:33 -0700 Received: from holonet.net (marvin.holonet.net [198.207.169.9]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id MAA09863 for ; Mon, 10 Oct 1994 12:12:29 -0700 From: root@cei.com Received: from ceigate.UUCP (uucp@localhost) by holonet.net with UUCP id GAA23378; Mon, 10 Oct 1994 06:23:44 -0700 Received: by ceigate (Linux Smail3.1.28.1 #14) id m0quKLd-0005Ada; Mon, 10 Oct 94 08:01 CDT Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by guardian.holonet.net with ESMTP id EAA22976; Mon, 10 Oct 1994 04:12:29 -0700 Received: from mycroft.GreatCircle.COM by relay2.UU.NET with SMTP id QQxkzs04358; Mon, 10 Oct 1994 07:09:04 -0400 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA03175; Mon, 10 Oct 1994 10:23:59 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id DAA03163; Mon, 10 Oct 1994 03:23:45 -0700 Received: from sigma.itu.ch (sigma.itu.ch [156.106.128.30]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id DAA08287 for ; Mon, 10 Oct 1994 03:24:39 -0700 Received: from MR.ITU.CH by ITU.CH (PMDF V4.3-7 #4298) id <01HI3YFC7ZZK9FP5WD@ITU.CH>; Mon, 10 Oct 1994 11:25:17 CET Received: with PMDF-MR; Mon, 10 Oct 1994 10:25:07 CET MR-Received: by mta TIES.MUAS; Relayed; Mon, 10 Oct 1994 10:25:07 +0100 MR-Received: by mta TAU; Relayed; Mon, 10 Oct 1994 10:25:24 +0100 Disclose-recipients: prohibited Date: Mon, 10 Oct 1994 10:25:07 +0100 (CET) Subject: pid file...? To: Majordomo-Users Message-id: <8507251110101994/A31000/TAU/118A52D90400*@MHS> X-Envelope-to: Majordomo-Users@GreatCircle.COM Autoforwarded: false MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Importance: normal Priority: urgent Sensitivity: Company-Confidential UA-content-id: 118A52D90400 X400-MTS-identifier: [;8507251110101994/A31000/TAU] Hop-count: 1 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, wu-ftpd seems to be running OK on my DEC Alpha 3600, osf/1 v2.0 But I do get the following message in my syslog... daemon.log:Oct 9 23:44:06 seit ftpd[21999]: open of pid file failed: No such file or directory Any idea... Thanks Rgrds, /jarle Jarle Martinsen International Telecomunnication Union (ITU) Place des nations CH-1211 Geneva 20 Switzerland Internet: martinsen@itu.ch X.400: S=martinsen; P=itu; A=arcom; C=ch Voice: +41 22 730 5949 Fax: +41 22 730 5337 From majordomo-users-owner Mon Oct 10 19:19:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id TAA05552; Mon, 10 Oct 1994 19:19:47 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id MAA05546; Mon, 10 Oct 1994 12:19:42 -0700 Received: from bosnia.pop.psu.edu (barr@bosnia.pop.psu.edu [146.186.111.25]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id MAA09885 for ; Mon, 10 Oct 1994 12:20:36 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id PAA10232; Mon, 10 Oct 1994 15:19:56 -0400 Message-Id: <199410101919.PAA10232@bosnia.pop.psu.edu> To: oby@crlmail.uchicago.edu (Tyrone L. Oby) Cc: majordomo-users@GreatCircle.COM Subject: Re: problems with permissions In-reply-to: Your message of "Mon, 10 Oct 1994 13:46:16 -1100." <199410101842.NAA00274@crlmail.uchicago.edu> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Mon, 10 Oct 1994 15:19:55 -0400 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199410101842.NAA00274@crlmail.uchicago.edu>, Tyrone L. Oby writes: > After installing Majordomo 1.92, I started testing portion of it. >It passed the help test + request test. When I try to scribe to my test >list I get the following message mailed back: > >shlock: open(">/home/majordom/lists/shlock.180"): Permission denied at >/home/majordomo/majordomo-1.92/shlock.pl line 131,<> line 1. > >I know permission is critical with Majordomo. but is their any simple method >to insure the correct perms. One of the simple methods is to follow the explanation in the Majordomo FAQ. Search for "permission". You can get the Majordomo FAQ by sending an e-mail message to majordomo@pop.psu.edu with "get file majordomo-faq" in the body of the message. You can get an HTML version on the World Wide Web at http://www.pop.psu.edu/~barr/majordomo-faq.html. --Dave From majordomo-users-owner Mon Oct 10 20:00:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id UAA05793; Mon, 10 Oct 1994 20:00:46 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id NAA05787; Mon, 10 Oct 1994 13:00:41 -0700 Received: from nbn.nbn.com (nbn.nbn.com [199.4.64.19]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id NAA10084 for ; Mon, 10 Oct 1994 13:01:34 -0700 Received: from sbt.sbtcorp.com (sbtcorp.com [199.4.101.1]) by nbn.nbn.com (8.6.4/8.6.4) with SMTP id NAA21812 for ; Mon, 10 Oct 1994 13:00:33 -0700 Received: from smtpgate.sbtcorp.com by sbt.sbtcorp.com id aa11210; 10 Oct 94 13:00 PDT Received: by sbtmain.sbtcorp.com with Microsoft Mail id <2E999DFE@sbtmain.sbtcorp.com>; Mon, 10 Oct 94 13:03:10 PDT From: KWAT - Ken Watkins To: "'smtp:majordomo-users@greatcircle.com'" Subject: No filename Date: Mon, 10 Oct 94 13:02:00 PDT Message-ID: <2E999DFE@sbtmain.sbtcorp.com> Encoding: 12 TEXT X-Mailer: Microsoft Mail V3.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am testing my newly installed Majordomo 1.92. Out of curiosity I sent it a request as follows: get (I left out the filespec argument). It sent me a line of gibberish as the answer. The archive directory for this list is empty. Have I setup something incorrectly? I expected it to send me the help file for correct syntax. Thanks for any help you can offer. - Ken kwat@sbtcorp.com From majordomo-users-owner Tue Oct 11 00:52:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id AAA07525; Tue, 11 Oct 1994 00:52:28 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA07519; Mon, 10 Oct 1994 17:52:23 -0700 Received: from merlion.singnet.com.sg (merlion.singnet.com.sg [165.21.1.10]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id RAA11176 for ; Mon, 10 Oct 1994 17:53:18 -0700 Received: (from gmlim@localhost) by merlion.singnet.com.sg (8.6.9/8.6.9/CNS-3.5) id IAA13584; Tue, 11 Oct 1994 08:52:21 +0800 Date: Tue, 11 Oct 1994 08:52:21 +0800 (SST) From: Lim Gek Meng Subject: setting up majordomo To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am still trying set up my majordomo. I've upgraded my system to OSF/1 V3.0 and perl5beta3. But I get this message when I send to majordomo asking for lists. Appreciate it if somebody out there can help me. ----- Transcript of session follows ----- Literal @: now requires backslash at /usr/local/majordomo/majordom/majordomo line 1302, within string Execution of /usr/local/majordomo/majordom/majordomo aborted due to compilation errors. 554 "|/usr/local/majordomo/majordom/wrapper majordomo"... unknown mailer error 255 ----- Unsent message follows ----- Received: by zpoint.sing.net; id AA04197; Mon, 10 Oct 1994 19:53:32 +0800 Received: (from gmlim@localhost) by merlion.singnet.com.sg (8.6.9/8.6.9/CNS-3.5) id TAA25892; Mon, 10 Oct 19 94 19:54:39 +0800 Date: Mon, 10 Oct 1994 19:54:39 +0800 (SST) From: Lim Gek Meng Subject: To: Majordomo@zpoint.sing.net Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII lists ************************************************************************** * LIM GEK MENG * "Whatever you do will be insignificant, * * SingNet * but it is very important that you do it." * * SINGAPORE TELECOMS * --Mahatma Gandhi * ************************************************************************** From majordomo-users-owner Tue Oct 11 01:08:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id BAA07594; Tue, 11 Oct 1994 01:08:47 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA07588; Mon, 10 Oct 1994 18:08:42 -0700 Received: from kbrown.oldcampus.yale.edu (root@kbrown.oldcampus.yale.edu [130.132.128.124]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id SAA11244 for ; Mon, 10 Oct 1994 18:09:42 -0700 Received: by kbrown.oldcampus.yale.edu (Linux Smail3.1.28.1 #1) id m0quVhr-0005LVC; Mon, 10 Oct 94 21:08 EDT Date: Mon, 10 Oct 1994 21:08:43 +0100 From: Vince Subject: Setting up Majordomo for list/digest To: majordomo-users@GreatCircle.COM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am currently running a digest under mailserv and I would like to use Majordomo but can someone tell me where I should start on using Majordomo for a digest/mailing list on a machine that already has Majordomo installed for other lists? Any help would be greatly appreciated! Thanks. Cheers, Vince E-mail: vince@kbrown.oldcampus.yale.edu,\|/ Sys Adm - CircleStar Technologies,Inc. root@berkeley.circlestar.com,(o o) San Francisco, California USA _________________________oOO__(_)__OOo_____________________________ | There are many forms of science but only physics is the quantum | | leap of the 21st Century. | \_________________________________________________________________/ uPoy@physics.ucla.edu UCLA Physics Los Angeles, California USA GUS Digest Adminstrator Advanced Gravis UltraSound Card - The ultimate in soundcard technology From majordomo-users-owner Tue Oct 11 01:20:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id BAA07691; Tue, 11 Oct 1994 01:20:30 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA07685; Mon, 10 Oct 1994 18:20:26 -0700 Received: from inet-gw-2.pa.dec.com (inet-gw-2.pa.dec.com [16.1.0.23]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id SAA11324 for ; Mon, 10 Oct 1994 18:21:26 -0700 Received: from us1rmc.bb.dec.com by inet-gw-2.pa.dec.com (5.65/10Aug94) id AA13869; Mon, 10 Oct 94 18:19:00 -0700 Received: from wrksys.enet by us1rmc.bb.dec.com (5.65/rmc-22feb94) id AA07198; Mon, 10 Oct 94 21:19:26 -0400 Message-Id: <9410110119.AA07198@us1rmc.bb.dec.com> Received: from wrksys.enet; by us1rmc.enet; Mon, 10 Oct 94 21:19:26 EDT Date: Mon, 10 Oct 94 21:19:26 EDT From: Jim Reisert -- MLO5-2/36A -- DTN 223-5747 10-Oct-1994 2122 To: gmlim@singnet.com.sg Cc: majordomo-users@us1RMC.bb.dec.com Apparently-To: majordomo-users@greatcircle.com Subject: RE: setting up majordomo Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Lim Gek Meng wrote: >I am still trying set up my majordomo. I've upgraded my system to OSF/1 >V3.0 and perl5beta3. But I get this message when I send to majordomo >asking for lists. Appreciate it if somebody out there can help me. > ----- Transcript of session follows ----- >Literal @: now requires backslash at >/usr/local/majordomo/majordom/majordomo line 1302, within string >Execution of /usr/local/majordomo/majordom/majordomo aborted due to >compilation errors. You have to go through majordomo (and resend) and look for instances of "@" character inside text strings "@" Change the "@" to "\@". This only happened with recent versions of Perl 5. If you try sending mail to MajorDomo, and try to use the RESEND script, you should be able to catch most of the errors. - Jim reisert@eng.pko.dec.com From majordomo-users-owner Tue Oct 11 04:06:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA10143; Tue, 11 Oct 1994 10:21:21 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id DAA10131; Tue, 11 Oct 1994 03:21:03 -0700 Received: from holonet.net (marvin.holonet.net [198.207.169.9]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id DAA12876 for ; Tue, 11 Oct 1994 03:22:02 -0700 From: root@cei.com Received: from ceigate.UUCP (uucp@localhost) by holonet.net with UUCP id TAA01168; Mon, 10 Oct 1994 19:27:34 -0700 Received: by ceigate (Linux Smail3.1.28.1 #14) id m0quWVz-00059la; Mon, 10 Oct 94 21:00 CDT Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by guardian.holonet.net with ESMTP id SAA02222; Mon, 10 Oct 1994 18:26:20 -0700 Received: from mycroft.GreatCircle.COM by relay2.UU.NET with SMTP id QQxlbw28116; Mon, 10 Oct 1994 21:14:23 -0400 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id BAA07594; Tue, 11 Oct 1994 01:08:47 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA07588; Mon, 10 Oct 1994 18:08:42 -0700 Received: from kbrown.oldcampus.yale.edu (root@kbrown.oldcampus.yale.edu [130.132.128.124]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id SAA11244 for ; Mon, 10 Oct 1994 18:09:42 -0700 Received: by kbrown.oldcampus.yale.edu (Linux Smail3.1.28.1 #1) id m0quVhr-0005LVC; Mon, 10 Oct 94 21:08 EDT Date: Mon, 10 Oct 1994 21:08:43 +0100 Subject: Setting up Majordomo for list/digest To: majordomo-users@GreatCircle.COM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am currently running a digest under mailserv and I would like to use Majordomo but can someone tell me where I should start on using Majordomo for a digest/mailing list on a machine that already has Majordomo installed for other lists? Any help would be greatly appreciated! Thanks. Cheers, Vince E-mail: vince@kbrown.oldcampus.yale.edu,\|/ Sys Adm - CircleStar Technologies,Inc. root@berkeley.circlestar.com,(o o) San Francisco, California USA _________________________oOO__(_)__OOo_____________________________ | There are many forms of science but only physics is the quantum | | leap of the 21st Century. | \_________________________________________________________________/ uPoy@physics.ucla.edu UCLA Physics Los Angeles, California USA GUS Digest Adminstrator Advanced Gravis UltraSound Card - The ultimate in soundcard technology From majordomo-users-owner Tue Oct 11 04:13:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA10145; Tue, 11 Oct 1994 10:21:26 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id DAA10137; Tue, 11 Oct 1994 03:21:09 -0700 Received: from holonet.net (marvin.holonet.net [198.207.169.9]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id DAA12878 for ; Tue, 11 Oct 1994 03:22:07 -0700 From: root@cei.com Received: from ceigate.UUCP (uucp@localhost) by holonet.net with UUCP id TAA01167; Mon, 10 Oct 1994 19:27:32 -0700 Received: by ceigate (Linux Smail3.1.28.1 #14) id m0quWHB-00059la; Mon, 10 Oct 94 20:45 CDT Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by guardian.holonet.net with ESMTP id SAA01270; Mon, 10 Oct 1994 18:08:22 -0700 Received: from mycroft.GreatCircle.COM by relay1.UU.NET with SMTP id QQxlbv14048; Mon, 10 Oct 1994 20:58:14 -0400 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id AAA07525; Tue, 11 Oct 1994 00:52:28 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id RAA07519; Mon, 10 Oct 1994 17:52:23 -0700 Received: from merlion.singnet.com.sg (merlion.singnet.com.sg [165.21.1.10]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id RAA11176 for ; Mon, 10 Oct 1994 17:53:18 -0700 Received: (from gmlim@localhost) by merlion.singnet.com.sg (8.6.9/8.6.9/CNS-3.5) id IAA13584; Tue, 11 Oct 1994 08:52:21 +0800 Date: Tue, 11 Oct 1994 08:52:21 +0800 (SST) Subject: setting up majordomo To: majordomo-users@GreatCircle.COM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am still trying set up my majordomo. I've upgraded my system to OSF/1 V3.0 and perl5beta3. But I get this message when I send to majordomo asking for lists. Appreciate it if somebody out there can help me. ----- Transcript of session follows ----- Literal @: now requires backslash at /usr/local/majordomo/majordom/majordomo line 1302, within string Execution of /usr/local/majordomo/majordom/majordomo aborted due to compilation errors. 554 "|/usr/local/majordomo/majordom/wrapper majordomo"... unknown mailer error 255 ----- Unsent message follows ----- Received: by zpoint.sing.net; id AA04197; Mon, 10 Oct 1994 19:53:32 +0800 Received: (from gmlim@localhost) by merlion.singnet.com.sg (8.6.9/8.6.9/CNS-3.5) id TAA25892; Mon, 10 Oct 19 94 19:54:39 +0800 Date: Mon, 10 Oct 1994 19:54:39 +0800 (SST) From: Lim Gek Meng Subject: To: Majordomo@zpoint.sing.net Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII lists ************************************************************************** * LIM GEK MENG * "Whatever you do will be insignificant, * * SingNet * but it is very important that you do it." * * SINGAPORE TELECOMS * --Mahatma Gandhi * ************************************************************************** From majordomo-users-owner Wed Oct 12 18:57:15 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA19044; Wed, 12 Oct 1994 18:57:15 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA19038; Wed, 12 Oct 1994 11:57:10 -0700 Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id LAA17871 for ; Wed, 12 Oct 1994 11:58:11 -0700 Received: from questa.esd.sgi.com by sgi.sgi.com via ESMTP (940627.SGI.8.6.9/910110.SGI) for <@sgi.sgi.com:majordomo-users@greatcircle.com> id LAA13894; Wed, 12 Oct 1994 11:57:56 -0700 Received: by questa.esd.sgi.com (940816.SGI.8.6.9/940406.SGI.AUTO) for majordomo-users@greatcircle.com id LAA07214; Wed, 12 Oct 1994 11:57:44 -0700 From: "Mats Wichmann (mipsABI Consultant)" Message-Id: <9410121157.ZM7212@questa.esd.sgi.com> Date: Wed, 12 Oct 1994 11:57:40 -0700 X-Mailer: Z-Mail (3.2b.1001 01oct94 MediaMail) To: majordomo-users@greatcircle.com Subject: digest footer/fronter Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk A while back, I asked a question about why I could run digest by hand but not via sendmail; Spider Boardman pointed out that my sendmail config file was missing a "u" flag in the specification for the "prog" mailer, which caused the "-C" flag to be lower-cased. This pointer solved my problme. Given that this default configuration appears on a number of systems, might it not be better to design the digest arguments to that it was immune to this (i.e., not use any upper-case argument flags). Just to be safe? Anyway, I'm having a new digest problem. The digests now collect just fine, but when they are made, the message_footer and message_fonter fields in the digest config file are chopped down to one line plus a blank. I had descriptive text in both, and was using the token _SUBJECTS_ in the fronter, but all that gets lost. This has happened several times on a couple of different machine types. What am I doing wrong this time? # (message footer comment text left out here for brevity) message_footer << END To subscribe to test-digest, send the command: END # (message fronter comment text left out here for brevity) message_fronter << END In this issue: END -- mats From majordomo-users-owner Thu Oct 13 13:35:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id NAA04948; Thu, 13 Oct 1994 13:35:25 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id GAA04942; Thu, 13 Oct 1994 06:35:20 -0700 Received: from inet-gw-1.pa.dec.com (inet-gw-1.pa.dec.com [16.1.0.22]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id GAA03036 for ; Thu, 13 Oct 1994 06:36:28 -0700 Received: from us1rmc.bb.dec.com by inet-gw-1.pa.dec.com (5.65/10Aug94) id AA27187; Thu, 13 Oct 94 06:26:24 -0700 Received: from wrksys.enet by us1rmc.bb.dec.com (5.65/rmc-22feb94) id AA24101; Thu, 13 Oct 94 09:26:48 -0400 Message-Id: <9410131326.AA24101@us1rmc.bb.dec.com> Received: from wrksys.enet; by us1rmc.enet; Thu, 13 Oct 94 09:26:50 EDT Date: Thu, 13 Oct 94 09:26:50 EDT From: Jim Reisert -- MLO5-2/36A -- DTN 223-5747 13-Oct-1994 0929 To: majordomo-users@us1RMC.bb.dec.com Apparently-To: majordomo-users@greatcircle.com Subject: How do resend a bounced message? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk When a message is bounced (false positive administrative request), how do I resubmit the message (using approve?) so that it goes to the list anyway? Thanks - Jim -- James J. Reisert Internet: reisert@wrksys.enet.dec.com Digital Equipment Corp. UUCP: ...decwrl!wrksys.enet.dec.com!reisert 146 Main Street - MLO5-2/M16 Voice: 508-493-5747 Maynard, MA 01754 FAX: 508-493-0700 From majordomo-users-owner Thu Oct 13 12:50:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA07353; Thu, 13 Oct 1994 18:53:56 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id KAA06569; Thu, 13 Oct 1994 10:18:29 -0700 Received: from SYSWRK.UCIS.DAL.CA (syswrk.UCIS.Dal.Ca [129.173.2.108]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id KAA04281 for ; Thu, 13 Oct 1994 10:19:52 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HI8BFOXIIO001I2Q@SYSWRK.UCIS.DAL.CA>; Thu, 13 Oct 1994 14:18:56 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HI8BF9DC7K00KZSH@AC.DAL.CA>; Thu, 13 Oct 1994 14:18:35 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA14888; Thu, 13 Oct 94 14:08:10 -0300 Date: Thu, 13 Oct 1994 14:08:09 -0300 (ADT) From: silvert@biome.bio.ns.ca (Bill Silvert) Subject: Re: Majordomo results: Re: APPROVE fuzzy-b In-reply-to: <9410131657.AA14738@biome.bio.ns.ca> from "Majordomo" at Oct 13, 94 04:57:16 pm To: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9410131708.AA14888@biome.bio.ns.ca> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Content-Length: 827 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have a persistent problem accessing lists on my own machine. If I subscribe, my address appears as "silvert (Bill Silvert)" but I prefer to have the full address appear so that users can get full addresses with the "who" command. But if I do this, Majordomo doesn't recognize me as a member of the list. Is there an easy fix that lets me have it both ways? Bill Silvert >>>>> which >The string 'silvert' appears in the following >entries in lists served by Majordomo@biome.bio.dfo.ca: > >List Address >==== ======= >... >fuzzy-b silvert@biome.bio.ns.ca (Bill Silvert) >... > >>>>> who fuzzy-b >**** List 'fuzzy-b' is a private list. >**** Only members of the list can do a 'who'. >**** You aren't a member of list 'fuzzy-b'. Bill Silvert (silvert@biome.bio.ns.ca) From majordomo-users-owner Thu Oct 13 20:30:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id UAA07922; Thu, 13 Oct 1994 20:30:12 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id NAA07915; Thu, 13 Oct 1994 13:30:06 -0700 Received: from vaxa.cis.uwosh.edu (vaxa.cis.uwosh.edu [141.233.128.1]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id NAA05516 for ; Thu, 13 Oct 1994 13:31:30 -0700 Received: from vaxa.cis.uwosh.edu by vaxa.cis.uwosh.edu (PMDF #7750 ) id <01HI8DQBX8WW00EJ4Q@vaxa.cis.uwosh.edu>; Thu, 13 Oct 1994 15:28:12 CDT Date: 13 Oct 1994 15:28:12 -0500 (CDT) From: "Charles R. Milam - UW-Oshkosh" Subject: Butchered headers with approved: To: majordomo-users@greatcircle.com Message-id: <01HI8DQBX8WY00EJ4Q@vaxa.cis.uwosh.edu> X-VMS-To: IN%"majordomo-users@greatcircle.com" MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Lately, I've run into problems with a moderated list. When I release a message to the list with the "approved:" command, part of the header ends up in the message. Help! Example below: >From: IN%"majordom@sol.acs.uwosh.edu" 13-OCT-1994 14:31:37.58 >To: IN%"kaiserd@vaxa.cis.uwosh.edu", IN%"MILAMC@vaxa.cis.uwosh.edu" >CC: >Subj: > >Return-path: >Received: from sol.acs.uwosh.edu by vaxa.cis.uwosh.edu (PMDF #7750 ) id > <01HI8BULVS0000EH4C@vaxa.cis.uwosh.edu>; Thu, 13 Oct 1994 14:30:59 CDT >Received: by sol.acs.uwosh.edu (4.1/SMI-4.1) id AA14559; Thu, > 13 Oct 94 14:38:02 CDT >Date: 13 Oct 1994 14:38:02 -0500 (CDT) >From: majordom@sol.acs.uwosh.edu (Majordomo-Owner) >To: kaiserd@vaxa.cis.uwosh.edu, MILAMC@vaxa.cis.uwosh.edu >Message-id: <9410131938.AA14559@sol.acs.uwosh.edu> >Content-transfer-encoding: 7BIT >Apparently-To: dsp-announce-outgoing > >Hey brothers on the info-bahn - >Just wanted to let you all know that you can contact Eta Eta Chapter at >Rochester Institute of Technology directly by sending e-mail to our account.. >Sender: owner-dsp-announce@sol.acs.uwosh.edu >Precedence: bulk >Reply-To: owner-dsp-announce > >DSP1899@rit.edu (get it?) ------------------------------------------------------------------------------ Charles R. Milam MilamC@vaxa.cis.uwosh.edu Academic Computing milamc@sol.acs.uwosh.edu University of Wisconsin-Oshkosh KF9FR@KA9JAC.WI.USA.NA Oshkosh, WI 54901 Badger 112 -- WI0112 (414) 424-2309 Delta Sigma Phi - EB Chapter ---------------<<>>---------------- From majordomo-users-owner Thu Oct 13 21:34:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id VAA08205; Thu, 13 Oct 1994 21:34:37 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id OAA08199; Thu, 13 Oct 1994 14:34:31 -0700 Received: from lobster.wellfleet.com (lobster.wellfleet.com [192.32.253.3]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id OAA05736 for ; Thu, 13 Oct 1994 14:35:56 -0700 Received: from wellfleet (pobox.wellfleet.com) by lobster.wellfleet.com (4.1/SMI-4.1) id AA10881; Thu, 13 Oct 94 17:28:25 EDT Received: from bee.wellfleet by wellfleet (4.1/SMI-4.1) id AA27300; Thu, 13 Oct 94 17:27:47 EDT Date: Thu, 13 Oct 94 17:27:47 EDT From: yi-shin_wu@wellfleet.com (Yi-Shin Wu) Message-Id: <9410132127.AA27300@wellfleet> To: majordomo-users@greatcircle.com Subject: Administrative commands? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've been told to try here. I've just been made an owner/administrator of a majordomo mailing list here at Wellfleet, but so far, I'm only aware of the "APPROVE" command. What other commands are there which an administrator can use?? Is there anywhere that I can look this information up?? Thanks! -wys ywu@wellfleet.com From majordomo-users-owner Thu Oct 13 22:57:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id WAA08717; Thu, 13 Oct 1994 22:57:04 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id PAA08711; Thu, 13 Oct 1994 15:56:59 -0700 Received: from virginia.edu (uvaarpa.Virginia.EDU [128.143.2.7]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id PAA06383 for ; Thu, 13 Oct 1994 15:58:27 -0700 Received: from darwin.clas.virginia.edu by uvaarpa.virginia.edu id aa07228; 13 Oct 94 18:57 EDT Received: (from mre2b@localhost) by darwin.clas.Virginia.EDU (8.6.8/8.6.6) id SAA47992 for majordomo-users@greatcircle.com; Thu, 13 Oct 1994 18:57:43 -0400 From: Matthew Elkin Message-Id: <199410132257.SAA47992@darwin.clas.Virginia.EDU> Subject: anyone use resend with mmdf? To: majordomo-users@greatcircle.com Date: Thu, 13 Oct 1994 18:57:43 -0400 (EDT) In-Reply-To: <9410132127.AA27300@wellfleet> from "Yi-Shin Wu" at Oct 13, 94 05:27:47 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 171 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk If your site uses majordomo and resend with mmdf please email me. Or if you have any info on resend working with mmdf please let me know. Matt Elkin; mre2b@virgnia.edu From majordomo-users-owner Thu Oct 13 23:26:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id XAA08911; Thu, 13 Oct 1994 23:26:39 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id QAA08899; Thu, 13 Oct 1994 16:26:29 -0700 Received: from nbn.nbn.com (nbn.nbn.com [199.4.64.19]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id QAA06552; Thu, 13 Oct 1994 16:27:54 -0700 Received: from sbt.sbtcorp.com (sbtcorp.com [199.4.101.1]) by nbn.nbn.com (8.6.4/8.6.4) with SMTP id QAA22440; Thu, 13 Oct 1994 16:26:42 -0700 Received: from smtpgate.sbtcorp.com by sbt.sbtcorp.com id aa00139; 13 Oct 94 16:26 PDT Received: by sbtmain.sbtcorp.com with Microsoft Mail id <2E9DC2C9@sbtmain.sbtcorp.com>; Thu, 13 Oct 94 16:29:13 PDT From: KWAT - Ken Watkins To: majordomo-users@greatcircle.com, majordomo-users-owner@greatcircle.com Subject: anyone use resend with mmdf? Date: Thu, 13 Oct 94 16:28:00 PDT Message-ID: <2E9DC2C9@sbtmain.sbtcorp.com> Encoding: 28 TEXT X-Mailer: Microsoft Mail V3.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We do. Send mail to jeffs@systemv.com for more information. - Ken Watkins (kwat@sbtcorp.com) ------------------------------------------------------------------------------ REPLY FROM: KWAT - Ken Watkins Return-Path: <@relay1.uu.net:majordomo-users-owner@greatcircle.com> From: Matthew Elkin Message-Id: <199410132257.SAA47992@darwin.clas.Virginia.EDU> Subject: anyone use resend with mmdf? To: majordomo-users@greatcircle.com Date: Thu, 13 Oct 1994 18:57:43 -0400 (EDT) In-Reply-To: <9410132127.AA27300@wellfleet> from "Yi-Shin Wu" at Oct 13, 94 05:27:47 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 171 Sender: Majordomo-Users-Owner@greatcircle.com Precedence: bulk If your site uses majordomo and resend with mmdf please email me. Or if you have any info on resend working with mmdf please let me know. Matt Elkin; mre2b@virgnia.edu From majordomo-users-owner Fri Oct 14 05:55:32 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id FAA12519; Fri, 14 Oct 1994 05:55:32 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id WAA12513; Thu, 13 Oct 1994 22:55:26 -0700 Received: from sgiblab.sgi.com (sgiblab.SGI.COM [192.82.208.3]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id WAA10842 for ; Thu, 13 Oct 1994 22:56:53 -0700 Received: from freke by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA21174; Thu, 13 Oct 94 23:18:33 -0700 Received: by freke.lerctr.org (/\==/\ Smail3.1.28.1 #28.9) id ; Thu, 13 Oct 94 22:55 PDT To: majordomo-users@greatcircle.com Newsgroups: mail.majordomo.users Path: mikepb From: mikepb@freke.lerctr.org (Michael P. Brininstool) Subject: Re: digest footer/fronter Message-Id: <1994Oct14.055525.20663@freke.lerctr.org> Organization: Valhalla MIS Department. References: <9410121157.ZM7212@questa.esd.sgi.com> Distribution: local Date: Fri, 14 Oct 1994 05:55:25 GMT Lines: 16 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In article <9410121157.ZM7212@questa.esd.sgi.com>, Mats Wichmann mipsABI Consultant wrote: >Anyway, I'm having a new digest problem. The digests now collect just >fine, but when they are made, the message_footer and message_fonter >fields in the digest config file are chopped down to one line plus a >blank. I had descriptive text in both, and was using the token >_SUBJECTS_ in the fronter, but all that gets lost. This has happened >several times on a couple of different machine types. What am I doing >wrong this time? I am having the same thing happening. Any ideas? ---------------------------------------------------------| | #include "std/disclaimer.h" Michael P. Brininstool | | mikepb@freke.lerctr.org OR mikepb@netcom.com | |--------------------------------------------------------- From majordomo-users-owner Fri Oct 14 00:40:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id FAA12187; Fri, 14 Oct 1994 05:17:49 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id WAA12181; Thu, 13 Oct 1994 22:17:42 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id WAA10405; Thu, 13 Oct 1994 22:19:13 -0700 Message-Id: <199410140519.WAA10405@miles.greatcircle.com> To: Jim Reisert -- MLO5-2/36A -- DTN 223-5747 13-Oct-1994 0929 cc: majordomo-users@miles.greatcircle.com Subject: Re: How do resend a bounced message? In-reply-to: Your message of Thu, 13 Oct 94 09:26:50 EDT Date: Thu, 13 Oct 1994 22:19:11 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Jim Reisert -- MLO5-2/36A -- DTN 223-5747 13-Oct-1994 0929 writes: # When a message is bounced (false positive administrative request), how do I # resubmit the message (using approve?) so that it goes to the list anyway? Yes, using the "approve" script is the best and easiest way. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Fri Oct 14 00:49:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id GAA12994; Fri, 14 Oct 1994 06:32:36 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id JAA18141; Wed, 12 Oct 1994 09:14:22 -0700 Received: from blackadder2.cis.mcmaster.ca (blackadder2.CIS.McMaster.CA [130.113.128.1]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id JAA17391 for ; Wed, 12 Oct 1994 09:14:38 -0700 Received: from insight.mcmaster.ca (insight.dcss.McMaster.CA) by blackadder2.cis.mcmaster.ca with SMTP id AA25497 (5.65c/IDA-1.4.4 for ); Wed, 12 Oct 1994 12:13:55 -0400 Received: by insight.mcmaster.ca (4.1/SMI-4.1) id AA29646; Wed, 12 Oct 94 12:13:58 EDT Date: Wed, 12 Oct 94 12:13:58 EDT From: djones@insight.dcss.McMaster.CA (David Jones) Message-Id: <9410121613.AA29646@insight.mcmaster.ca> To: majordomo-users@greatcircle.com Subject: problem with "approve". It complains it can't find "reply-to". Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am using Majordomo 1.92 with a moderated list. When I get a "subscribe" that needs approval (see example below) I try to pipe it to "approve". It complains: No "Reply-To:"; exiting at /usr/local/majordomo/bin/approve line 137, line 15. Any suggestions? Why doesn't it use the "From:" line instead of "Reply-To:" ? thanks, David Jones ===== "approve" can't handle this file ===== From majordomo-users-owner Fri Oct 14 08:22:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id OAA16896; Fri, 14 Oct 1994 14:31:37 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id HAA16890; Fri, 14 Oct 1994 07:31:31 -0700 Received: from polo.iquest.com (root@polo.iquest.com [199.170.120.63]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id HAA14338 for ; Fri, 14 Oct 1994 07:33:00 -0700 Received: by polo.iquest.com (Linux Smail3.1.28.1 #1) id m0qvnOk-002EGmC; Fri, 14 Oct 94 09:14 CDT Received: from cc:Mail by multi.iquest.com id AA782150514 Fri, 14 Oct 94 09:01:54 Date: Fri, 14 Oct 94 09:01:54 From: "Dougal Campbell" Encoding: 815 Text Message-Id: <9409147821.AA782150514@multi.iquest.com> To: majordomo-users@GreatCircle.COM, "Mats Wichmann (mipsABI Consultant)" Subject: Re: digest footer/fronter Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >Anyway, I'm having a new digest problem. The digests now collect just >fine, but when they are made, the message_footer and message_fonter >fields in the digest config file are chopped down to one line plus a >blank. I had descriptive text in both, and was using the token >_SUBJECTS_ in the fronter, but all that gets lost. This has happened >several times on a couple of different machine types. What am I doing >wrong this time? When I was first setting up my digests, I had similar problems. It turns out that I didn't read the docs closely enough. Try putting a dash ('-') at the beginning of each line of your message_footer and message_fronter text. I forget just what the purpose is, I just remember doing it :) Dougal Campbell dougal@mtronics.com dougal@iquest.com From majordomo-users-owner Fri Oct 14 18:00:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA18688; Fri, 14 Oct 1994 18:00:10 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA18671; Fri, 14 Oct 1994 11:00:03 -0700 Received: from asee.org ([198.76.10.11]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with SMTP id LAA15873 for ; Fri, 14 Oct 1994 11:01:26 -0700 From: h.bhatt@asee.org Received: from ASEE-Message_Server by asee.org with WordPerfect_Office; Fri, 14 Oct 1994 13:50:50 -0500 Message-Id: X-Mailer: WordPerfect Office 4.0 Date: Fri, 14 Oct 1994 13:51:28 -0500 To: majordomo-users@greatcircle.com Subject: Request for assistance with Majordomo installation. Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm trying to install Majordomo on a Sun SPARCserver 1000 running Solaris 2.3. While testing the setup, using: echo help | /usr/lib/sendmail -v majordomo I get the following output... ==================================================================== majordomo... aliased to "|/usr/local/majordomo/bin/wrapper majordomo" "|/usr/local/majordomo/bin/wrapper majordomo"... Connecting to via prog... majordomo: Permission denied "|/usr/local/majordomo/bin/wrapper majordomo"... unknown mailer error 5 ... ... (a few messages notifying "admin" about the above problem) ... ==================================================================== I've checked the permissions, but can't seem to locate the problem. Any assistance would be greatly appreciated. Harish. From majordomo-users-owner Fri Oct 14 18:27:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id SAA19076; Fri, 14 Oct 1994 18:27:17 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id LAA19069; Fri, 14 Oct 1994 11:27:09 -0700 Received: from crlmail.uchicago.edu (crlmail.uchicago.edu [128.135.73.3]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id LAA16280 for ; Fri, 14 Oct 1994 11:27:59 -0700 Received: from crlpc1.uchicago.edu (crlpc1.uchicago.edu [128.135.158.2]) by crlmail.uchicago.edu (8.6.5/8.6.5) with SMTP id NAA13093; Fri, 14 Oct 1994 13:19:28 -0500 Message-Id: <199410141819.NAA13093@crlmail.uchicago.edu> X-Sender: oby@crlmail.uchicago.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 14 Oct 1994 13:23:26 -1100 To: Majordomo@crlmail.uchicago.edu, majordomo-users@GreatCircle.COM From: oby@crlmail.uchicago.edu (Tyrone L. Oby) Subject: Re: Request for assistance with Majordomo installation. X-Mailer: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk At 01:51 PM 10/14/94 -0500, h.bhatt@asee.org wrote: >I'm trying to install Majordomo on a Sun SPARCserver 1000 running >Solaris 2.3. > >While testing the setup, using: > > echo help | /usr/lib/sendmail -v majordomo > >I get the following output... > >==================================================================== >majordomo... aliased to "|/usr/local/majordomo/bin/wrapper majordomo" > >"|/usr/local/majordomo/bin/wrapper majordomo"... Connecting to via >prog... > >majordomo: Permission denied > >"|/usr/local/majordomo/bin/wrapper majordomo"... unknown mailer >error 5 > >... >... >(a few messages notifying "admin" about the above problem) >... >==================================================================== > >I've checked the permissions, but can't seem to locate the problem. >Any assistance would be greatly appreciated. > >Harish. > > Try the the command "chmod 4775 /usr/local/majordomo" this will set the group id to allow writes by what group,user id you set wrapper to. From majordomo-users-owner Fri Oct 14 23:47:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id XAA20726; Fri, 14 Oct 1994 23:47:10 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id QAA20720; Fri, 14 Oct 1994 16:47:04 -0700 Received: from donald.uoregon.edu (donald.uoregon.edu [128.223.32.6]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id QAA20356 for ; Fri, 14 Oct 1994 16:48:30 -0700 Received: from RIS.OR.GOV by OREGON.UOREGON.EDU (PMDF V4.3-9 #7713) id <01HI9UXEZV8W8WXW0J@OREGON.UOREGON.EDU>; Fri, 14 Oct 1994 16:48:07 -0700 (PDT) Received: from RISMTP01.RIS.OR.GOV by RISVS.RIS.OR.GOV (PMDF V4.3-8 #2476) id <01HI9UK82ZZK001VE6@RISVS.RIS.OR.GOV>; Fri, 14 Oct 1994 16:37:03 -0700 (PDT) Received: by RISMTP01.RIS.OR.GOV with Microsoft Mail id <2E9F14DD@RISMTP01.RIS.OR.GOV>; Fri, 14 Oct 94 16:31:41 PDT Date: Fri, 14 Oct 1994 16:35:00 -0700 (PDT) From: CHAPIN Newt R Subject: Handling boundary information from Ms Mail messages To: "'Majordomo-Users'" Message-id: <2E9F14DD@RISMTP01.RIS.OR.GOV> MIME-version: 1.0 Content-type: MULTIPART/MIXED; BOUNDARY="Boundary (ID 9URzGkQWK+KBxVHDfJO+RA)" Content-transfer-encoding: 7BIT Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk --Boundary (ID 9URzGkQWK+KBxVHDfJO+RA) Content-type: TEXT/PLAIN Microsoft Mail adds boundary information to each message when it's sent. Here's a sample boundary line and a content line that automatically get added to my outgoing messages: Boundary (ID h/N3gl3UlBGTbPw2osD6PQ) Content-type: TEXT/PLAIN I've sent mail to some list servers that can handle this extra stuff just by telling me it can't figure out what that particular line means, then it moves on to the more important line (my actual request) and handles it appropriately. Unfortunately, majordomo just rejects the entire message because it couldn't understand the first line and it never checks anything past that. This is how one list server handled my Ms Mail message with it's inherent extra lines: > --Boundary (ID h/N3gl3UlBGTbPw2osD6PQ) Unknown command - "--BOUNDARY". Try HELP. > Content-type: TEXT/PLAIN Unknown command - "CONTENT-TYPE:". Try HELP. > subscribe xxxxxx Newt Chapin A confirmation request is being mailed to you. Please wait until it arrives before sending any SET command, or any other command that requires you to be subscribed to the list, as you have not yet been added to the list. > --Boundary (ID h/N3gl3UlBGTbPw2osD6PQ)-- Unknown command - "--BOUNDARY". Try HELP. Is there any way to make majordomo deal with extra lines in messages so seamlessly? Newt cedpnrc@eug001.ris.or.gov --Boundary (ID 9URzGkQWK+KBxVHDfJO+RA)-- From majordomo-users-owner Sat Oct 15 02:59:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id CAA22919; Sat, 15 Oct 1994 02:59:00 GMT Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id TAA22907; Fri, 14 Oct 1994 19:58:51 -0700 Received: from gaia.ucs.orst.edu (mailserv@gaia.UCS.ORST.EDU [128.193.4.2]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id UAA26897 for ; Fri, 14 Oct 1994 20:00:17 -0700 Received: (from mailserv@localhost) by gaia.ucs.orst.edu (8.6.8.1/8.6.6) id TAA20450; Fri, 14 Oct 1994 19:59:17 -0700 Date: Fri, 14 Oct 1994 19:59:16 -0700 (PDT) From: Vince - IE - Experimental Mail Server Admin Acct Subject: Upgrading from 1.46 to 1.92 To: majordomo-users@GreatCircle.COM In-Reply-To: <9410121613.AA29646@insight.mcmaster.ca> Message-ID: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The Majordomo software on this system is still version 1.46 and I am interested in upgrading to version 1.92 so can anyone out there tell me how hard it is to upgrade and what I must perform. Thanks in advance. Cheers, Vince E-mail: vince@kbrown.oldcampus.yale.edu,\|/ Sys Adm - CircleStar Technologies,Inc. root@berkeley.circlestar.com,(o o) San Francisco, California USA _________________________oOO__(_)__OOo_____________________________ | There are many forms of science but only physics is the quantum | | leap of the 21st Century. | \_________________________________________________________________/ uPoy@physics.ucla.edu UCLA Physics Los Angeles, California USA GUS Digest Adminstrator Advanced Gravis UltraSound Card - The ultimate in soundcard technology From majordomo-users-owner Sat Oct 15 15:28:47 1994 Received: from localhost (daemon@localhost) by miles.greatcircle.com (8.6.5/Miles-941006-1) id PAA08143 for majordomo-users-outgoing; Sat, 15 Oct 1994 15:28:47 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id PAA08138 for ; Sat, 15 Oct 1994 15:28:45 -0700 Message-Id: <199410152228.PAA08138@miles.greatcircle.com> To: majordomo-users@miles.greatcircle.com Subject: Majordomo@GreatCircle.COM _finally_ upgraded to 1.92... Date: Sat, 15 Oct 1994 15:28:45 -0700 From: Brent Chapman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk ------- Forwarded Message Date: Sat, 15 Oct 1994 15:22:40 -0700 Message-Id: <199410152222.PAA08110@miles.greatcircle.com> To: brent@miles.greatcircle.com From: Majordomo@GreatCircle.COM Subject: Majordomo results Reply-To: Majordomo@GreatCircle.COM -- >>>> help This is Brent Chapman's "Majordomo" mailing list manager, version 1.92. ... ------- End of forwarded message Notice anything different? How about the version number? :-) I finally found/made time this weekend to upgrade GreatCircle.COM to the latest released Majordomo. I did this as part of the process of moving most GreatCircle.COM stuff from our old Sun 3/60, mycroft.greatcircle.com, to our new 486/66 running BSDI, miles.greatcircle.com. FTP, WAIS, and so forth will be moving to the new machine over the next few days/weeks/months, as I have time and can get the software working. The Majordomo server and all the mailing lists have been moved, but it should be transparent to users. In other upgrade news, we have a 56 kb/s frame relay line on order, due for installation on 7 November, to address the longstanding congestion problems with our current 9.6 kb/s dialup SLIP line. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Sun Oct 16 22:07:43 1994 Received: from localhost (daemon@localhost) by miles.greatcircle.com (8.6.5/Miles-941015-1) id WAA07986 for majordomo-users-outgoing; Sun, 16 Oct 1994 22:07:43 -0700 Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id WAA24488; Fri, 14 Oct 1994 22:05:49 -0700 Received: from bosnia.pop.psu.edu (barr@bosnia.pop.psu.edu [146.186.111.25]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id WAA28601 for ; Fri, 14 Oct 1994 22:05:56 -0700 Received: (from barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) id BAA14679 for Majordomo-Users@GreatCircle.COM; Sat, 15 Oct 1994 01:05:01 -0400 Date: Sat, 15 Oct 1994 01:05:01 -0400 From: David Barr Message-Id: <199410150505.BAA14679@bosnia.pop.psu.edu> To: Majordomo-Users@GreatCircle.COM Reply-To: barr@pop.psu.edu Subject: Majordomo Frequently Asked Questions Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Version: $Id: majordomo-faq.html,v 1.20 1994/10/11 14:24:30 barr Exp barr $ Archive-Name: mail/majordomo-faq Posting-Frequency: monthly Table of Contents: 1. What is Majordomo and how can I get it? + What is Majordomo? + Where do I get it? + How do I install it? + How do I upgrade from an earlier release? + Where do I report bugs or get help with Majordomo? + Which is better, Majordomo or LISTSERV? 2. Problems setting up Majordomo + I get an error "insecure usage" from the wrapper + I get "majordomo: No such file or directory" from the wrapper + I get an error "Can't locate majordomo.pl" + I get "Permission denied at ..." when majordomo runs + I told majordomo where to archive the list, why isn't it working? + Majordomo seems to be taking many minutes to process commands + I'm accumulating lots of files called /tmp/resend.*.in and .out, 3. Setting up mailing lists and aliases + Handling bounced mail + Semi-automated handling of bounced mail + What's this Owner-List and List-Owner stuff? Why both? + How should I configure resend for Reply-To headers? + How can I hide lists so they can't be viewed by 'lists'? + Can I have the list owner or approval person be changeable without intervention from the Majordomo owner? + What about all of these passwords starting in version 1.90? + How do I tell majordomo to handle "get"-ing of binary files? + A list is visible via lists, but can't subscribe or 'get' files 4. Miscellaneous mailer and other problems + Address with blanks are being treated separately + Why aren't my digests going out? This FAQ is Copyright 1994 by David Barr and The Pennsylvania State University. This document may be reproduced, so long as it is kept in its entirety and in its original format. Credits: 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 this FAQ by sending an e-mail message to majordomo@pop.psu.edu with "get file majordomo-faq" in the body of the message. You can get an HTML version on the World Wide Web at http://www.pop.psu.edu/~barr/majordomo-faq.html. If you have any questions or submissions regarding this FAQ, send them to barr@pop.psu.edu (David Barr). _________________________________________________________________ Section 1: What is Majordomo and how can I get it? WHAT IS MAJORDOMO? Majordomo is a program which automates the management of Internet mailing lists. Commands are sent to Majordomo via electronic mail to handle all aspects of list maintainance. Once a list is set up, virtually all operations can be performed remotely, requiring no intervention upon the postmaster of the list site. majordomo - n: a person who speaks, makes arrangements, or takes charge for another. From latin "major domus" - "master of the house". Majordomo is written in Perl (at least 4.035, preferably 4.036). It is also known to work under Perl 5. Note that Majordomo doesn't seem to work with Perl 4 under OSF/1, though people have had success with running Perl 5 under OSF/1 (and other platforms) if you edit majordomo and resend and look for instances of "@" character inside text strings "@" Change the "@" to "\@". This only happened with recent versions of Perl 5. [from Jim Reisert] Majordomo controls a list of addresses for some mail transport system (like sendmail or smail) to handle. Majordomo itself performs no mail delivery (though it has scripts to format and archive messages). Here's a short list of some of the features of Majordomo. * supports various types of lists, including moderated ones. * List options can be set easily through a configuration file, editable remotely. * Supports archival and remote retrieval of messages. * Supports digests. * Written in Perl, - easily customizable and expandable. * Modular in design. * Includes support for FTPMAIL. WHERE DO I GET IT? Via anonymous FTP at: ftp://ftp.greatcircle.com/pub/majordomo/ If you don't have Perl, you can get it from: ftp://prep.ai.mit.edu/pub/gnu/perl-4.036.tar.gz The FTPMAIL package can be found in ftp://src.doc.ic.ac.uk/packages/ftpmail or any comp.sources.misc archive (volume 37). HOW DO I INSTALL IT? Majordomo comes with a rather extensive README. Read this file completely. This FAQ is meant to be a supplement to Majordomo's documentation, not a replacement for it. If you have any questions that this FAQ doesn't cover, chances are that it is covered in the README or other documentation in the Majordomo distribution. HOW DO I UPGRADE FROM AN EARLIER RELEASE? Be sure to browse the "Changes" and "Changelog" files to get an idea what has changed. There currently is no canned set of instructions for upgrading from an earlier release. The most straightforward method is to simply install the current release in a different directory, (with the same list/archive/digest directories) and change the mail aliases for each list to use the new Majordomo scripts as soon as you feel comfortable with the new setup. WHERE DO I REPORT BUGS OR GET HELP WITH MAJORDOMO? If you need help, there is a mailing list majordomo-workers@greatcircle.com, which is frequented by lots of users of Majordomo. Please don't send questions to me. Report bugs to majordomo-workers@greatcircle.com. Be sure always to include which version of Majordomo you are using. You should also include what operating system you are using, what version of Perl, and what mailer (sendmail, smail, etc) and version you are using, especially if you can't get Majordomo to work at all. But first, you must have thoroughly read the documentation to Majordomo and this FAQ. WHICH IS BETTER, MAJORDOMO OR LISTSERV? Here's a slight revision of something Chris Koenigsberg posted to comp.mail.misc, following up a thread there. Tasos, the author of ListProc, said that he was basically on the mark concerning ListProc. [ This section is currently under revision --Dave ] Chris Koenigsberg: ckk@uchicago.edu, ckoenig@midway.uchicago.edu U. of Chicago Academic Information Technologies The real LISTSERV (Revised LISTSERV) relies on Bitnet networking transport protocols. A complex Unix list processor was written, in a partial emulation of the Bitnet LISTSERV. The "LISTSERV for Unix" system was renamed "ListProc" last summer, after threats from the original LISTSERV author, because it differs in user interface and list owner interface from LISTSERV, and was accused of misleading users who would confuse it with the "real thing". Majordomo was written, in Perl, because ListProc (AKA Unix LISTSERV) was too complex and did not do quite what was needed to manage a set of Usenix SAGE mailing lists. LISTSERV and ListProc want the whole world to be interconnected, i.e. all mailing list server hosts can know about each other and exchange info on remote lists; someday I imagine there'll be a DNS-like namespace of mailing lists and server hosts out there somehow. Majordomo, on the other hand, is a much smaller package, designed for easier administration on an individual host, and I have even heard (on the Majordomo-Users list) that some Majordomo hosts do NOT wish their lists advertised publicly on the net. We (U. of Chicago Academic Information Technologies) are planning to go ahead and offer new campus list management service soon using Majordomo, but we did have some requests from faculty to use ListProc (they asked for LISTSERV but since this is on Unix, they would have to get ListProc instead). I tried briefly to configure and build ListProc for a comparison test, but gave up when it got weird, probably too soon, maybe I'll try again when I have more time to play with compilers etc :-) Listproc documentation etc. is a bit cryptic and not well thought out overall, at least from the point of view of someone new to the concept trying to understand all of its complex workings. I have seen correspondence from the Listproc author, on the ListProc users' mailing list archives, where he defends his documentation because it is in the usual Unix style. (maybe "damning by faint praise"? :-) Majordomo is simpler and written in Perl scripts, so documentation is more comprehensive, and is improving, as an active community of developers is contributing to it. It only took 2 days for the current maintainers to put out small patches to fix some recently-discovered potential security holes, and since it's Perl, no recompilation is needed. Listproc requires a server daemon to be alive, which forks off child processes somewhat like lpd, and appears to be designed to do a lot of complex, tricky things which requires a lot of C source code doing networking stuff (multi-level automated archiving and indexing, with retrieval via ftpmail, automatic digestification creation and propagation, remote cooperation of "peer" list hosts, interactive administration via TCP connections, operation over other transport and delivery protocols besides TCP and SMTP, maintain its own message queueing system independently of the system mail queues, ...), which are perhaps overkill (for us, in a completely Internet TCP/SMTP environment), perhaps not, this is what I'd like to hear more discussion about. Majordomo is more focused on the essentials of individual mailing list management, and is implemented as Perl scripts, which are modular and can be used in subsets, as they are individually invoked out of system mail aliases. It lets the underlying system software do the networking and message queueing stuff, so it doesn't have to deal with TCP sockets etc. Majordomo's recently-added archiving, digestification, etc. is simpler than ListProc's, and is undergoing more improvements. Apparently, Listproc's daemon with its own queueing system used to give better performance, for high-traffic lists on heavily loaded server hosts, than older versions of sendmail. But now, newer sendmail versions have greatly improved efficiency so Majordomo with new sendmail may be just as fast and load-capable as a Listproc system. (comments welcomed on this point?) With Listproc, if you can get it configured and running smoothly, you can apparently join a growing inter-operating network of cooperating "peer" list hosts, and even inter-operate with Bitnet LISTSERV list hosts too. Thus your local users can easily find out about other lists elsewhere, you can have local re-distributions for a larger global list, etc. (but re-distributions can be a source of administrative headache when global list owners try to track down mysterious errors, or unsubscribe requests from people who aren't subscribed to the global list.... :-). One big flaw in Listproc's design, in my opinion (correct me if I'm wrong!), is that it does funny things to the headers of outgoing messages which are arguably "wrong" in the RFC 822 SMTP world (I've seen arguments in the ListProc users' archives), and for incoming messages, it only uses the Unix From field (i.e. the SMTP Envelope MAIL FROM, in the SMTP world) to determine the sender's identity, for subscribing, unsubscribing, accepting or rejecting messages, etc. Majordomo on the other hand will use the RFC 822 headers (Gene Spafford's Perl code for parsing mail headers), so it will recognize a "Reply-To:" for example, and will allow you to subscribe your canonical address, even if the return path of your message is convoluted (although the list owner may need to approve your subscription). You have various per-list configuration options, about what appears in the various RFC 822/SMTP headers, concerning the return address for errors, the default reply address (to the list, to the original author, to the list owner/moderator, etc.)... Both Listproc and Majordomo share concepts like moderated lists. Listproc's moderated lists have a queue of incoming messages, and the moderator has to approve or reject them by giving the message queue numbers to the server, in order to clear the queue. For a moderated list, Majordomo simply bounces messages to the moderator and then forgets about them, so the moderator can easily re-submit them with an approval password in a new header. Any message arriving with the proper approval password header will be automatically approved and propagated to the list. An outfit called CREN, an offshoot of Educom, has taken over the development of both the Bitnet LISTSERV, and the Unix Listproc, and is planning to offer a commercial version of Listproc sometime later in 1994. They have a global vision building on the inter-operating "peer" list host concept, integrating gopher, ftp, etc. (their vision statement doesn't mention WWW but I assume that must be added soon :-). We are very interested to see if CREN's new Listproc version will come with improved support, including better documentation, and we might consider switching to it sometime in the future, but we are planning to stick with Majordomo for now. _________________________________________________________________ Section 2: Problems setting up Majordomo I GET AN ERROR "INSECURE USAGE" FROM THE WRAPPER The argument to ".../wrapper" should be simply "majordomo", not The full path to majordomo or resend. "wrapper" has where to look compiled in to it (the "W_BIN" setting in the Makefile) for security reasons, and will not let you specify another directory. Your alias should say: |"/path/to/majordomo/wrapper majordomo" I GET "MAJORDOMO: NO SUCH FILE OR DIRECTORY" FROM THE WRAPPER Make sure that the #! statement at the beginning of all the Majordomo Perl executables contain the correct path to the perl program. (the default is /usr/local/bin/perl) Make sure also that majordomo and all the related scripts are in the W_BIN directory as defined in the Makefile when you compiled the wrapper. I GET AN ERROR "CAN'T LOCATE MAJORDOMO.PL" > Whenever I send either mail to a list or a command to majordomo, receive > the following: > > Can't locate majordomo.pl in @INC at /usr/majordom/mjdm/resend line 61. > 554 "|/usr/majordom/mjdm/resend -p bulk -l test -f brian -h -s > test-outgoing". > .. unknown mailer error 2 [from Brent Chapman] Majordomo adds "$homedir" from the majordomo.cf file to the @INC array before it goes looking for "majordomo.pl". Since it's not finding it, I'd guess you have one of two problems: 1) $homedir is set improperly (or not set at all; there is no default) in your majordomo.cf file. 2) majordomo.pl is not in $homedir, or is not readable. [from John P. Rouillard] 3) Note that the new majordomo.cf file checks to see if the environment variable $HOME is set first, and uses that for $homedir. Since the wrapper always sets HOME to the correct directory, you get a nice default, unless you are running a previously built wrapper, in which case you may get the wrong directory. [from Andreas Fenner] 4) I had the same problem when I installed majordomo (1.62). My Problem was a missing ";" in the majordomo.cf file - just in the line before setting homedir .... My hint for you: Check your perl-files carefully. I GET "PERMISSION DENIED AT ..." WHEN MAJORDOMO RUNS > > shlock: open(">/usr/local/lib/majordomo/shlock.15260"): > Permission denied at /usr/local/lib/majordomo/shlock.pl line 131, > line 7. The directory "/usr/local/lib/majordomo" needs to be writable by the uid/gid that the "wrapper" program run as, so that Majordomo can create its lock file. In general, for any file Majordomo writes, both the file _AND_ the directory the file is in must be writable by Majordomo, so that it can create lock files and new versions of the data file (Majordomo usually "updates" a file by creating "file.new" and then, when that has succeeded, deleting "file" and renaming "file.new" to "file"). > Also, should everything in my majordomo directory by owned by > majordom and the group set to majordom? Basically, yes, and it should all (including the directory itself) be writable by whatever uid/gid wrapper is set to run as. I TOLD MAJORDOMO WHERE TO ARCHIVE THE LIST, WHY ISN'T IT WORKING? > I don't get it: is the list archive a file or a directory? > I chose directory and it doesn't work, though I'm not sure why. > The relevant majordomo.cf entry looks like: > $filedir = "/usr/local/mail/majordomo/archive"; > $filedir_suffix = ""; [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/ for files that it should allow to be gotten using the get command. Majordomo comes with three different archive programs that run under wrapper, that do various types of archiving. Look in the contrib directory. MAJORDOMO SEEMS TO BE TAKING MANY MINUTES TO PROCESS COMMANDS > Commands are being processed at the rate of about one every 10 minutes. > What's going wrong, why is Majordomo so slow? Majordomo tries to lock the log file (by creating a lock file in the directory with the log file) for 10 minutes for each log message, before giving up. It's typically going to log one log message for each command in the input. If the directory containing the file is not writable by the Majordomo user/group, then majordomo won't be able to lock the file and thus will take a very long time to process commands. Check the permissions on the log file and all the directories where majordomo files are located. Double-check the permission on the wrapper. If you are on a non-POSIX system, it must be both suid and sgid (mode 6755) to whatever you defined your majordomo user and group to be. It must not be setuid root! OR In a POSIX system the wrapper must be setuid root, and double-check that W_UID and W_GID are of the majordomo user and group. Don't set W_UID to be 0! I'M ACCUMULATING LOTS OF FILES CALLED /TMP/RESEND.*.IN AND .OUT WHAT ARE THESE AND HOW CAN I GET RID OF THEM? This is a known bug in Majordomo 1.92. There was a typo on line 347. Make this change to resend: 347c347 unlink(); _________________________________________________________________ Section 3: Setting up mailing lists and aliases HANDLING BOUNCED MAIL > If a subscriber sends a message to a mailing list containing addresses > that cause bounces, then the subscriber/sender gets a copy of the > bounced mail. They don't care to receive the bounce. Can this be > prevented? (Without removing the offending addresses from the list -- > I'm aware of the Majordomo 'bounce' utility.) This was somewhat of a RTFM question. The answer is to use 'resend' to your advantage. The following is an example of a sendmail alias that I was using: sample: :include:/usr/local/mail/lists/sample Whereas this example (from the 'sample.aliases' file distributed with Majordomo) fixes the problem. sample: "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Sample -f Owner-Sample -h GreatCircle.COM -s sample-outgoing" sample-outgoing: :include:/usr/local/mail/lists/sample owner-sample: joe See the 'resend.README' file for more info on resend's options. What this does is force outgoing mail to have the out-of-band envelope FROM be "Owner-Sample@GreatCircle.COM", and thus all bounces will be redirected to that address. (Users often see this mirrored in the message body as the "From " or "Return-Path:" header). 'resend' also inserts a "Sender:" line with the same address to help people identify where it came from, but that header is not used for the bounce address. If you are using sendmail v8.x, you don't have to use 'resend' to do the same thing. You simply have to define an alias like this: owner-sample: joe, Note the trailing comma is necessary to prevent sendmail from resolving the alias first before putting it in the header. Without the comma, it will put "joe" in the envelope from instead of "owner-sample". Either address will work, of course, but the generic address is preferred should the owner ever change. SEMI-AUTOMATED HANDLING OF BOUNCED MAIL >The documentation, I guess, isn't very clear on this, but how does one >implement the bounce list/bounce-remind program so that people that go >'boing' can be dealt with in a somewhat more automated manner? > >Uh . . . how exactly is this accomplished? [From John Rouillard] There is nothing special about this. Just create a mailing list called bounces. I usually set mine up as an auto list just to make life easier. All that bounce does is create an email message to that says: approve [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.GOV bounces passwd3 Majordomo@This.COM bounces passwd4 Majordomo@Other.GOV A command of "bounce this-list user@fubar.com" will mail the following message to Majordomo@This.COM: approve passwd1 unsubscribe this-list user@fubar.com approve passwd3 subscribe bounces user@fubar.com (930401 this-list) while a command of "bounce other-list user@fubar.com" will mail the following message to Majordomo@Other.COM: approve passwd2 unsubscribe other-list user@fubar.com approve passwd4 subscribe bounces user@fubar.com (930401 this-list) Note that the date and the list the user was bounced from are included as a comment in the address used for the "subscribe bounces" command. WHAT'S THIS OWNER-LIST AND LIST-OWNER STUFF? WHY BOTH? [From David Barr] The "standard" is spelled out in RFC 1211 - "Problems with the Maintenance of Large Mailing Lists". It's here where the "owner-listname" and "listname-request" concepts got their start. (well it was before this, but this is where it was first spelled out) Personally, I don't use "listname-owner" anywhere. You don't really have to put both, since the "owner" alias is usually only for bounces, which you add automatically anyway with resend's "-f" flag, or having Sendmail v8.x's "owner-listname" alias. (while I'm on the subject) The "-approval" is a Majordomo-ism, and is only necessary if you want bounces and approval notices to go to different mailboxes. (though you'll have to edit some code in majordomo and request-answer if you want to get rid of the -approval alias, since it's currently hardwired in) So, to answer your question, I'd say "no". You don't have to have both. You should just have "owner-list". HOW SHOULD I CONFIGURE RESEND FOR REPLY-TO HEADERS? Whether you should have a "Reply-To:" or not depends on the charter of your list and the nature of its users. If the list is a discussion list and you generally want replies to go back to the list, you can include one. Some people don't like being told what to do, and prefer to be able to choose whether to send a private reply or a reply to the list just by using the right function on their mail agent. Take note that if you do use a "Reply-To:", then some mail agents make it much harder for a person on the list to send a private reply. If you are using resend, use the '-r ' flag to set the Reply-To field to the list, or use the 'reply_to' config keyword for 1.9x or greater. HOW CAN I HIDE LISTS SO THEY CAN'T BE VIEWED BY 'LISTS'? That is what advertise and noadvertise are for. The two keywords take regular expressions that are matched against the from address of the sender. A list display follows the rules: 1. If the from address is on the list, it is shown. 2. If the from address matches a regexp in noadvertise (e.g. /.*/) the list is not shown. 3. If the advertise list is empty, the list is shown unless 2 applies. 4. If the advertise list is non-empty, the from address must match an address in advertise. Otherwise the list is not shown. Rule 2 applies, so you could allow all hosts in umb.edu except hosts in cs.umb.edu. CAN I HAVE THE LIST OWNER OR APPROVAL PERSON BE CHANGEABLE WITHOUT INTERVENTION FROM THE MAJORDOMO OWNER? Sure! Just make owner-listname and/or listname-approval be another majordomo list. (probably hidden, for simplicity's sake) WHAT ABOUT ALL OF THESE PASSWORDS STARTING IN VERSION 1.90? Think of three separate passwords: 1. A master password that can be used by both resend and majordomo contained in [listname].passwd. To be used by the master list manager when using writeconfig commands etc. This allows someone who handles a number of mailing lists all using the same password. 2. A password for the manager of this one list. The admin_passwd can be used by subsidiary majordomo list maintainers. 3. A password for those concerned with the list content (approve_passwd) This way the administration and moderation functions can be split. The original reason for maintaining [listname].passwd was to allow a new config file to be put in if the config file was trashed and the admin_password was obliterated, and may still be useful to allow a single password to be used for admin functions by the majordomo admin or some other "superadmin". > [...stupid question - is the admin passwd in the config file a file name > or the password itself for the list ? ...] The password itself. This is the only way that the list-maintainer could change the password since they wouldn't have access to the file. HOW DO I TELL MAJORDOMO TO HANDLE "GET"-ING OF BINARY FILES? Majordomo is not designed to be a general-purpose file-by-mail system. If you want to do anything more than trivial "get"-ing of text files (archives, etc) than you should get and install ftpmail. Majordomo has hooks to allow transparent access to files via ftpmail (see majordomo.cf). 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 files and archive directory all need to be "majordomo-users*". _________________________________________________________________ Section 4: Miscellaneous mailer problems ADDRESS WITH BLANKS ARE BEING TREATED SEPARATELY > Does anyone else have the problem: > > If a subscriber to the list is > John Doe > > Majordomo or sendmail treats this as 3 addresses: > John > Doe > > > Of course the first two always fail. [From Alan Millar] Majordomo does not treat these as three addresses. Your apparent version of Sendmail 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 comment at the end of each address it writes to the list file. You can also add the $listname.strip option so that none of the addresses are angle-bracketed. (the "strip" config option for 1.90) WHY AREN'T MY DIGESTS GOING OUT? >I'm not sure how to set up the digest feature of majordomo 1.92 to send >digests out. Currently, it is digesting incoming mail, but that's all it's >doing. [from John Rouillard] echo mkdigest | mail majordomo@... This will force a digest to be created. Or you can set the max size in the digest list config file down low, and force automatic generation. There are some patches for 1.92 that will allow other ways of specifying automatic digest sending. The patch is in the contrib directory. From majordomo-users-owner Sun Oct 16 22:07:57 1994 Received: from localhost (daemon@localhost) by miles.greatcircle.com (8.6.5/Miles-941015-1) id WAA08007 for majordomo-users-outgoing; Sun, 16 Oct 1994 22:07:57 -0700 Received: from miles.greatcircle.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940930) id IAA29283; Sat, 15 Oct 1994 08:34:38 -0700 Received: from saguenay.IRO.UMontreal.CA (root@saguenay.IRO.UMontreal.CA [132.204.32.54]) by miles.greatcircle.com (8.6.5/Miles-941006-1) with ESMTP id IAA03342 for ; Sat, 15 Oct 1994 08:36:06 -0700 From: mailhot@IRO.UMontreal.CA Received: from beauport.iro.umontreal.ca by saguenay.IRO.UMontreal.CA (8.6.9) with ESMTP id LAA16820; Sat, 15 Oct 1994 11:35:18 -0400 Received: (from mailhot@localhost) by beauport.iro.umontreal.ca (8.6.9/8.6.9) id LAA03092; Sat, 15 Oct 1994 11:35:12 -0400 Message-Id: <199410151535.LAA03092@beauport.iro.umontreal.ca> Subject: Problem with hostile address (X400) To: majordomo-users@greatcircle.com Date: Sat, 15 Oct 1994 11:35:11 -0400 (EDT) Cc: mailhot@IRO.UMontreal.CA X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1476 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello majordomo-users! I'm currently using majordomo-1.92 on a SunOS 4.1.3 system, and I've run into a small problem when X400 addresses trying to subscribe themselves to a list. To this date, I was using medit to add the "hostile addresses" to the list, but even then they couldn't use any of the commands because of this test in majordomo.pl : # if there's a "|" or a "/" in it, it's hostile if (tr/|\//|\// != 0) { &main'abort("HOSTILE ADDRESS $addr"); return undef; } In order to accept the X400 addresses as "not hostile", I add to modify this test to become: # if there's a "|" in it, it's hostile if (tr/|/|/ != 0) { &main'abort("HOSTILE ADDRESS $addr"); return undef; } After testing it, the X400 addresses could now use the Majordomo commands, but I had to return to the old test because I think this could cause a security problem with people trying to add addresses that are in fact commands to be executed on the Majordomo host. Isn't this test there for that reason anyway? And if so, how are people dealing with X400 addresses without modifying this security check? Any help would be greatly appreciated. Ciao! -- Pierre Mailhot, Analyste/SysAdmin E-Mail: mailhot@IRO.UMontreal.CA Universite de Montreal, Dept. IRO, Tel: (514) 343-6111 ext. 3530 C.P. 6128, Succ. Centre-Ville, Fax: (514) 343-5834 Montreal, Quebec, Canada, H3C 3J7 Pavillon Math-Info, local 3525 From majordomo-users-owner Sun Oct 16 22:30:25 1994 Received: from localhost (daemon@localhost) by miles.greatcircle.com (8.6.5/Miles-941015-1) id WAA08209 for majordomo-users-outgoing; Sun, 16 Oct 1994 22:30:25 -0700 Received: from fx.net (fx.net [165.251.1.3]) by miles.greatcircle.com (8.6.5/Miles-941015-1) with SMTP id MAA04209 for ; Sun, 16 Oct 1994 12:22:50 -0700 Received: by fx.net id AA20700 (5.67b/IDA-1.5 for majordomo-users@greatcircle.com); Sun, 16 Oct 1994 15:17:13 -0400 From: Rick Pasotto Message-Id: <199410161917.AA20700@fx.net> Subject: 1.92 setup prob on linux To: majordomo-users@greatcircle.com Date: Sun, 16 Oct 1994 15:17:12 -0400 (EDT) X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 917 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Help please. I get the following report from sendmail (smail): pipe: exec: "/bin/sh" "-c" "/u/contrib/misc/majordomo-1.92/bin/wrapper majordomo" expand_string: expansion failed for ${osname expand_string: expansion failed for ${if def:sender_host {from $sender_host by $primary_name ${if def:sender_proto: with $sender_proto} ($osname Smail$version #$compile_num) }else{by $primary_name ${if def:sender_proto:with $sender_proto }($osname Smail$version #$compile_num) } write_log:note: "|/u/contrib/misc/majordomo-1.92/bin/wrapper majordomo" ... transport pipe: child returned status EX_126 (126) -- Rick Pasotto | "If a thousand men were not to pay their tax bills, that rickp@fxnet.net | would not be so violent and bloody a measure as it would | be to pay them and enable the state to commit violence | and shed innocent blood." -- Henry David Thoreau From majordomo-users-owner Sun Oct 16 22:49:39 1994 Received: from localhost (daemon@localhost) by miles.greatcircle.com (8.6.5/Miles-941015-1) id WAA08396 for majordomo-users-outgoing; Sun, 16 Oct 1994 22:49:39 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.5/Miles-941015-1) with ESMTP id WAA08390; Sun, 16 Oct 1994 22:49:36 -0700 Message-Id: <199410170549.WAA08390@miles.greatcircle.com> To: barr@pop.psu.edu cc: Majordomo-Users@greatcircle.com Subject: Re: Majordomo Frequently Asked Questions In-reply-to: Your message of Sat, 15 Oct 1994 01:05:01 -0400 Date: Sun, 16 Oct 1994 22:49:35 -0700 From: Brent Chapman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk David Barr writes: # # Version: $Id: majordomo-faq.html,v 1.20 1994/10/11 14:24:30 barr Exp barr $ # Archive-Name: mail/majordomo-faq # Posting-Frequency: monthly Cool! Way Cool! Two minor problems that I see, though... # I'M ACCUMULATING LOTS OF FILES CALLED /TMP/RESEND.*.IN AND .OUT WHAT ARE # THESE AND HOW CAN I GET RID OF THEM? # # This is a known bug in Majordomo 1.92. There was a typo on line 347. # Make this change to resend: # # 347c347 # unlink(); # # The diff apparently got trashed in the posting. # ADDRESS WITH BLANKS ARE BEING TREATED SEPARATELY # # # # > Does anyone else have the problem: # > # > If a subscriber to the list is # > John Doe # > # > Majordomo or sendmail treats this as 3 addresses: # > John # > Doe # > # > # > Of course the first two always fail. Looks like the (or whatever the actual address was) got dropped from the example above; it only shows 2 addresses (not 3, as it claims). In fact, it looks kind of like everything in <...> got stripped from the FAQ before posting. Great otherwise, though; thanks! -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Mon Oct 17 06:18:24 1994 Received: from localhost (daemon@localhost) by miles.greatcircle.com (8.6.5/Miles-941015-1) id GAA12199 for majordomo-users-outgoing; Mon, 17 Oct 1994 06:18:24 -0700 Received: from scriabin.music.vt.edu (scriabin.music.vt.edu [128.173.232.139]) by miles.greatcircle.com (8.6.5/Miles-941015-1) with SMTP id GAA12192 for ; Mon, 17 Oct 1994 06:18:18 -0700 Received: by scriabin.music.vt.edu (5.64/Tenon-1.35.01) id AA05631; Mon, 17 Oct 94 12:22:38 -0400 (EDT) From: mrossd@scriabin.music.vt.edu (Matthew Ross Davis) Message-Id: <9410171622.AA05631@scriabin.music.vt.edu> Subject: Majordomo on MachTen fix To: Majordomo-Users@GreatCircle.COM Date: Mon, 17 Oct 1994 12:22:36 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 990 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Well folks, it seems as if the little switch I did to the script for Majordomo seems to have worked for MachTen, if anyone is interested. Several people since have subscribed and unsubscribed without a problem with linking. Essentially, as stated before, the script would make hard links of the file that had the list of users so it could update the list when someone unsubscribes...well, Mac doesn't have hard linking - MachTen does it with System 7 aliasing as a soft link, and sometimes MachTen will actually delete the original file when removing the 'hard link.' A friend of mine had this problem with ELM. So anyway, the script uses rename() now (which apparently Perl _does_ have in it's coffers) instead of link() unlink(). Should I send you a copy of the script, Brent? I don't know what your policy is over changes like that for system dependencies. Anyways, this has just been an informative note. Majordomo 1.92 seems to be working great on MachTen otherwise! Ross Davis From majordomo-users-owner Mon Oct 17 08:35:31 1994 Received: from localhost (daemon@localhost) by miles.greatcircle.com (8.6.5/Miles-941015-1) id IAA14127 for majordomo-users-outgoing; Mon, 17 Oct 1994 08:35:31 -0700 Received: from research1.bryant.edu (research1.bryant.edu [192.124.153.2]) by miles.greatcircle.com (8.6.5/Miles-941015-1) with SMTP id IAA14122 for ; Mon, 17 Oct 1994 08:35:24 -0700 Received: by research1.bryant.edu (5.65/DEC-Ultrix/4.3) id AA04263; Mon, 17 Oct 1994 11:32:02 -0400 Date: Mon, 17 Oct 1994 11:32:01 -0400 (EDT) From: Stephen Frazier To: Majordomo Users Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi all! I am running Majordomo 1.92 on a DEC 3000/600 (OSF/1) and just encountered a serious problem. One of our students began posting to lists which are private and closed. Even though he is not a member of the lists, the postings are distributed to the members of the list. Should someone be able to do this without being a member or is something wrong with my setup? Also, should I use the "-I" option to prevent this? Thanks! -- Stephen L. Frazier Mgr. of Academic Computing Research Bryant College 401-232-6363 _/_/_/ _/_/_/ _/ _/_/_/ _/ _/_/_/ _/_/_/ _/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/_/_/ _/_/_/ _/ _/ _/ _/ _/_/_/ _/_/_/ _/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/ _/ _/_/_/ _/ _/ From majordomo-users-owner Tue Oct 18 18:18:35 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA16834 for majordomo-users-outgoing; Tue, 18 Oct 1994 17:54:47 -0700 Received: from sgigate.sgi.com (sgigate.SGI.COM [192.82.208.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id RAA16829 for ; Tue, 18 Oct 1994 17:54:42 -0700 Received: from sgihub.corp.sgi.com (sgihub.corp.sgi.com [192.26.51.188]) by sgigate.sgi.com (940519.SGI.8.6.9/8.6.4) with ESMTP id RAA04614; Tue, 18 Oct 1994 17:53:54 -0700 Received: from fogno.corp.sgi.com by sgihub.corp.sgi.com via ESMTP (940519.SGI.8.6.9/911001.SGI) for <@sgihub.corp.sgi.com:majordomo-users@greatcircle.com> id RAA17899; Tue, 18 Oct 1994 17:53:52 -0700 Received: by fogno.corp.sgi.com (940816.SGI.8.6.9/911001.SGI) for majordomo-users@greatcircle.com id RAA21101; Tue, 18 Oct 1994 17:53:51 -0700 From: terryd@fogno.corp.sgi.com (Terry Diemer, Datacomette) Message-Id: <9410181753.ZM21099@fogno.corp.sgi.com> Date: Tue, 18 Oct 1994 17:53:49 -0700 Reply-To: terryd@fogno.corp.sgi.com X-Mailer: Z-Mail-SGI (3.0S.1026 26oct93 MediaMail) To: majordomo-users@greatcircle.com Subject: (Fwd) Returned mail: Can't create output: No such file or directory Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk what could be causing this? I am baffled. This is new behavior... --- Forwarded mail from MAILER-DAEMON (Mail Delivery Subsystem) To: daemon The original message was received at Mon, 17 Oct 1994 18:08:31 -0700 from daemon@localhost ----- The following addresses had delivery problems ----- 1000000 (unrecoverable error) -fowner-listname (unrecoverable error) ----- Transcript of session follows ----- 550 1000000... User unknown 550 -fowner-listname... User unknown Message delivered to mailing list listname-outgoing 550 /dead.letter... Can't create output: No such file or directory ----- Message body suppressed ----- --- End of forwarded mail from MAILER-DAEMON (Mail Delivery Subsystem) here is the alias: listname: "|/usr/local/majordomo/wrapper resend -p bulk -M 1000000 -l listname -f listname-owner -h postofc.corp.sgi.com -s listname-outgoing" **Note, ^this is all on one line, i checked... thanks... -t -- Ms. Terry Diemer|terryd@sgi.com|Network Administration|Mountain View, CA, USA --- --- Did you know the first computer bug was a moth? From majordomo-users-owner Wed Oct 19 08:17:57 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA23638 for majordomo-users-outgoing; Wed, 19 Oct 1994 07:54:41 -0700 Received: from polo.iquest.com (root@polo.iquest.com [199.170.120.63]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id HAA23633 for ; Wed, 19 Oct 1994 07:54:36 -0700 Received: by polo.iquest.com (Linux Smail3.1.28.1 #1) id m0qxc3q-002EGVC; Wed, 19 Oct 94 09:32 CDT Received: from cc:Mail by multi.iquest.com id AA782583975 Wed, 19 Oct 94 09:26:15 Date: Wed, 19 Oct 94 09:26:15 From: "Dougal Campbell" Encoding: 917 Text Message-Id: <9409197825.AA782583975@multi.iquest.com> To: majordomo-users@greatcircle.com Subject: Filtering headers.... Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On one mailing list I manage, we've been seeing a lot of "RCPT" messages. At first, I thought it was just some new user with an auto-reply set up. Then I started seeing it from two or three other addresses. At this point I thought perhaps our mailer was at fault (we just replaced the sendmail on our machine). But now I've also seen it on another mailing list which runs out of another domain, and doesn't pass through our majordomo machine to get to me. My guess is that there is a new version of some mail reader or MTA out there that is installed at a few sites which is putting a 'return receipt' header field into its outgoing messages. Can anyone confirm this possibility? And, is there any way I can get majordomo to rip this field out before redistributing a message? Dougal Campbell dougal@mtronics.com dougal@iquest.com owner-majordomo@magellan.iquest.com From majordomo-users-owner Wed Oct 19 14:48:10 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA26956 for majordomo-users-outgoing; Wed, 19 Oct 1994 14:33:43 -0700 Received: from polo.iquest.com (root@polo.iquest.com [199.170.120.63]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id OAA26948 for ; Wed, 19 Oct 1994 14:33:32 -0700 Received: by polo.iquest.com (Linux Smail3.1.28.1 #1) id m0qxiGz-002EJPC; Wed, 19 Oct 94 16:10 CDT Received: from cc:Mail by multi.iquest.com id AA782608111 Wed, 19 Oct 94 16:08:31 Date: Wed, 19 Oct 94 16:08:31 From: "Dougal Campbell" Encoding: 817 Text Message-Id: <9409197826.AA782608111@multi.iquest.com> To: "Joseph Kwiatkowski" , majordomo-users@greatcircle.com Subject: Re[2]: Filtering headers.... Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk My thanks to Larry Sheldon and Joseph Kwiatkowski for pointing out some info on the RCPT problem. Just before I read their messages I had perused our sendmail logs and found that al of the offending addresses seemed to have something in common: They all had MAILQUEUE in their Message-ID fields. Furthermore, some of these mentioned Mercury 1.11, which I knew to be an SMTP program used with Pegasus on Novell LANs. Armed with this knowledge, and the pointer that the trigger for the receipt is the PMAIL identifier in the X-Mailer field, I can modify resend to strip this out. If it's successful, I'll let everyone know. Dougal Campbell dougal@mtronics.com dougal@iquest.com owner-majordomo@magellan.iquest.com From majordomo-users-owner Wed Oct 19 17:47:23 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA27965 for majordomo-users-outgoing; Wed, 19 Oct 1994 17:42:36 -0700 Received: from netcomsv.netcom.com (uucp2-b.netcom.com [163.179.3.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id RAA27959 for ; Wed, 19 Oct 1994 17:42:23 -0700 Received: from localhost by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id RAA10250; Wed, 19 Oct 1994 17:25:41 -0700 Received: from [192.9.200.100] (don_mac [192.9.200.100]) by ncc1701a.talarian.com (8.6.9/8.6.9) with SMTP id RAA03001 for ; Wed, 19 Oct 1994 17:18:33 -0700 X-Sender: don@ncc1701a Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 19 Oct 1994 17:18:45 -0800 To: Majordomo-Users@GreatCircle.com From: don@talarian.com (Don Gray) Subject: "Info" alias problems Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm having some difficulty with Majordomo. I am trying to set up the "info" alias on my Unix machine so it does two things: 1) Automatically returns a the contents of a text file to the sender 2) Automatically logs the sender's original message to an archive file and mails a copy of the original message to an administrative person In order to do this, I have set up a mailing list called "info", which is closed and private. I'll also make it "NOADVERTISE" as soon as I figure out how to do that (any suggestions are welcome). I am the only subscriber on the list. I'll change this to the administrative person as soon as I get this working. The problem is when I send an email message to "info", I get the following response: >Date: Wed, 19 Oct 1994 14:50:48 -0700 >From: Mail Delivery Subsystem >Subject: Returned mail: Recipient names must be specified >To: info-owner >MIME-Version: 1.0 > >The original message was received at Wed, 19 Oct 1994 14:50:47 -0700 >from daemon@localhost > > ----- Transcript of session follows ----- >501 info-owner... Recipient names must be specified > > ----- Original message follows ----- > >Content-Type: message/rfc822 > >Return-Path: info-owner >Received: (from daemon@localhost) by ncc1701a.talarian.com (8.6.9/8.6.9) id >OAA01920; Wed, 19 Oct 1994 14:50:47 -0700 >Date: Wed, 19 Oct 1994 14:50:47 -0700 >From: info-owner >Message-Id: <199410192150.OAA01920@ncc1701a.talarian.com> > > What does "Recipient names must be specified" mean in this context? My "info" file contains the members of the list (only me at the moment), and all of the permissions and ownerships (incl. groups) are set correctly. Here is my /etc/aliases file. ># ># "info" alias/mailing list ># When someone mails to "info@talarian.com", it archives their ># message to a file and mails a canned message to them which tells ># them to mail their snail mail address and application description ># to the "lit-request" alias/mailing list ># >info-owner: don ># the "sendmail" command returns the text file >"/home/mdomo/lists/info.info" to ># the original sender >info: "|/usr/lib/sendmail -f info-owner \$SENDER < /home/mdomo/lists/info.info", ># the "wrapper resend" archives the message to disk and forwards a copy to an ># administrative person > "|/home/mdomo/bin/wrapper resend -p bulk -M 10000 -R -l info -f > info-owner -h Talarian.com -r info -s info-outgoing" >owner-info: info-owner >info-approval: info-owner >info-outgoing: :include:/home/mdomo/lists/info, info-archive >owner-info-outgoing: info-owner >info-archive: /home/mdomo/lists/info.archive/info_archive.txt >owner-info-archive: info-owner >#info-request: "|/home/mdomo/bin/wrapper request-answer info" >#owner-info-request: info-owner Any suggestions as to what is wrong? Is there a more efficient way of achieving my two goals? Thanks in advance, -- _____________________________________________________________________ Don Gray International Sales Director Talarian Corporation 444 Castro Street, Suite 140 e-mail (preferred): don@talarian.com Mountain View, CA 94041 Tel: +1-415-965-9066 x138 (direct) U.S.A. Fax: +1-415-965-9077 _____________________________________________________________________ From majordomo-users-owner Wed Oct 19 23:46:53 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id XAA29484 for majordomo-users-outgoing; Wed, 19 Oct 1994 23:26:09 -0700 Received: from itssrv1.ucsf.edu (itssrv1.ucsf.EDU [128.218.1.200]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id XAA29479 for ; Wed, 19 Oct 1994 23:26:05 -0700 From: majordom@itssrv1.ucsf.edu Received: (from majordom@localhost) by itssrv1.ucsf.edu (8.6.8/8.6.6) id XAA04309 for majordomo-users@greatcircle.com; Wed, 19 Oct 1994 23:22:07 -0700 Date: Wed, 19 Oct 1994 23:22:07 -0700 Message-Id: <199410200622.XAA04309@itssrv1.ucsf.edu> To: majordomo-users@greatcircle.com Subject: failure of make install & shlock hints Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I had a hell of a time getting Majordomo to work initially on AIX. Eventually with coaching from Randy Bush, I created some utilities to reveal what UID and GID were used by sendmail. I enclose them later. Could Majordomo test and reveal the difficulty encountered with wrong permissions instead of just trying 600 times? Now, trying to set up on a new AIX machine, I followed instructions as well as I could. I revised the Makefile and the majordomo.cf file, and put a copy of the latter in /etc. The make worked just the way I think it should but the make install failed. Actually, I think it failed because it was already done. Doesn't this suggest a modification that accepts success more gracefully? Enclosure: make install failure itssrv1 5>make install (test ! -f majordomo.cf && echo "using sample.cf" && \ cp sample.cf /u5/majordom/majordomo-1.92/majordomo.cf; ) (test -f majordomo.cf && echo "using majordomo.cf" && \ cp majordomo.cf /u5/majordom/majordomo-1.92/majordomo.c using majordomo.cf cp: /u5/majordom/majordomo-1.92/majordomo.cf and majordomo.cf are identical (no. The error code from the last failed command is 1. Make Quitting. [I shrank the indents, and lost the end of the cp message.] Enclosure: id-reveal #!/bin/sh ( id; ls -la /u5/majordom/lists; id ) | /usr/bin/mail -s shlock.hak maj ordom Enclosure: fake shlock.pl # `/u5/majordom/bin/id-reveal`; die("Enough already."); Dick Karpinski dick@itsa.ucsf.edu From majordomo-users-owner Thu Oct 20 01:17:23 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id BAA29938 for majordomo-users-outgoing; Thu, 20 Oct 1994 01:05:51 -0700 Received: from itssrv1.ucsf.edu (itssrv1.ucsf.EDU [128.218.1.200]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id BAA29932 for ; Thu, 20 Oct 1994 01:05:46 -0700 From: majordom@itssrv1.ucsf.edu Received: (from majordom@localhost) by itssrv1.ucsf.edu (8.6.8/8.6.6) id BAA09780; Thu, 20 Oct 1994 01:01:42 -0700 Date: Thu, 20 Oct 1994 01:01:42 -0700 Message-Id: <199410200801.BAA09780@itssrv1.ucsf.edu> To: majordom@itssrv1.ucsf.edu, majordomo-users@GreatCircle.COM Subject: Re: failure of make install & shlock hints Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Now I have more tests in my Makefile, and get no complaints. Should I post my changes or send them somewhere? What the hell, they're not that big Enclosure: suggested Makefile changes install-scripts: install-cf @-test -d $(W_BIN)/Tools || mkdir $(W_BIN)/Tools cp contrib/archive2.pl $(W_BIN)/Tools @-test -d $(W_BIN)/bin || mkdir $(W_BIN)/bin cp approve bounce medit $(W_BIN)/bin (test ! -f $(W_BIN)/bounce-remind && \ cp bounce-remind $(W_BIN); exit 0) (test ! -f $(W_BIN)/config_parse.pl && \ cp config_parse.pl $(W_BIN); exit 0) (test ! -f $(W_BIN)/majordomo && \ cp majordomo $(W_BIN); exit 0) (test ! -f $(W_BIN)/majordomo.pl && \ cp majordomo.pl $(W_BIN); exit 0) (test ! -f $(W_BIN)/majordomo_version.pl && \ cp majordomo_version.pl $(W_BIN); exit 0) (test ! -f $(W_BIN)/new-list && \ cp new-list $(W_BIN); exit 0) (test ! -f $(W_BIN)/request-answer && \ cp request-answer $(W_BIN); exit 0) (test ! -f $(W_BIN)/resend && \ cp resend $(W_BIN); exit 0) (test ! -f $(W_BIN)/resend.README && \ cp resend.README $(W_BIN); exit 0) (test ! -f $(W_BIN)/shlock.pl && \ cp shlock.pl $(W_BIN); exit 0) (test ! -f $(W_BIN)/digest/digest && \ cp digest/digest $(W_BIN); exit 0) # cp bounce-remind config_parse.pl majordomo \ # majordomo.pl majordomo_version.pl\ # new-list request-answer resend resend.README shlock.pl \ # digest/digest \ # $(W_BIN) # the install.cf target will install the sample config file in the # proper place unless a majordomo.cf file exists in whcih case the # majordomo.cf file will be used. install-cf: (test ! -f $(W_BIN)/majordomo.cf && \ test ! -f majordomo.cf && echo "using sample.cf" && \ cp sample.cf $(W_BIN)/majordomo.cf; exit 0) (test ! -f $(W_BIN)/majordomo.cf && \ test -f majordomo.cf && echo "using majordomo.cf" && \ cp majordomo.cf $(W_BIN)/majordomo.cf; exit 0) Dick Karpinski From majordomo-users-owner Thu Oct 20 07:49:03 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA02449 for majordomo-users-outgoing; Thu, 20 Oct 1994 07:40:41 -0700 Received: from campus.mty.itesm.mx (lfasano@campus.mty.itesm.mx [131.178.4.5]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id HAA02443 for ; Thu, 20 Oct 1994 07:40:25 -0700 Received: (from lfasano@localhost) by campus.mty.itesm.mx (8.6.9/8.6.9) id IAA38921 for majordomo-users@GreatCircle.COM; Thu, 20 Oct 1994 08:39:23 -0600 From: Luis Fasano Message-Id: <199410201439.IAA38921@campus.mty.itesm.mx> Subject: Re: Filtering headers.... To: majordomo-users@GreatCircle.COM Date: Thu, 20 Oct 1994 08:39:23 -0600 (CST) In-Reply-To: <9409197825.AA782583975@multi.iquest.com> from "Dougal Campbell" at Oct 19, 94 09:26:15 am X-Mailer: ELM [version 2.4 PL13] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > My guess is that there is a new version of some mail reader or MTA out there > that is installed at a few sites which is putting a 'return receipt' header > field into its outgoing messages. Can anyone confirm this possibility? > Well... you're right. There are some mail readers, that give the possibility of attaching a header for "RETURN RECEIPT", i think that even the last version of elm do, but at least ECS-Mail, Eudora and some others do it!!!! :) > And, is there any way I can get majordomo to rip this field out before > redistributing a message? I think that it only deserves a little hacking!!! I really can't tell much about this, but if you find a way, please let me know. Perhps it can help me with some other things i want to do with my lists!!!! > > Dougal Campbell > dougal@mtronics.com > dougal@iquest.com > owner-majordomo@magellan.iquest.com > Hope this helps!! Luis majordomo-owner@campus.mty.itesm.mx Luis_Fasano@campus.mty.itesm.mx From majordomo-users-owner Thu Oct 20 10:23:49 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA03222 for majordomo-users-outgoing; Thu, 20 Oct 1994 10:04:11 -0700 Received: from polo.iquest.com (root@polo.iquest.com [199.170.120.63]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id KAA03217 for ; Thu, 20 Oct 1994 10:03:43 -0700 Received: by polo.iquest.com (Linux Smail3.1.28.1 #1) id m0qy0XU-002EKMC; Thu, 20 Oct 94 11:40 CDT Received: from cc:Mail by multi.iquest.com id AA782679359 Thu, 20 Oct 94 11:55:59 Date: Thu, 20 Oct 94 11:55:59 From: "Dougal Campbell" Encoding: 638 Text Message-Id: <9409207826.AA782679359@multi.iquest.com> To: majordomo-users@greatcircle.com Subject: More on filtering headers Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I really meant to be more specific in my last message. For those of you who are interested, what I've done is added the "X-Mailer:" field to resend's list of headers to strip. Maybe in version 2.0 this could be a .config file option ("remove_headers << EOF"). I don't know yet whether this mod is working, but someone had given me a clue that this was the right header to strip. I'm going to send some email to the author of Pegasus and see if he has any reasons not to use a "Return-Receipt-To:" header instead of "X-Mailer:". dougal@mtronics.com dougal@iquest.com owner-majordomo@magellan.iquest.com From majordomo-users-owner Thu Oct 20 10:48:04 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA03356 for majordomo-users-outgoing; Thu, 20 Oct 1994 10:26:13 -0700 Received: from scriabin.music.vt.edu (scriabin.music.vt.edu [128.173.232.139]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id KAA03350 for ; Thu, 20 Oct 1994 10:26:01 -0700 Received: by scriabin.music.vt.edu (5.64/Tenon-1.35.01) id AA06296; Thu, 20 Oct 94 16:30:23 -0400 (EDT) From: mrossd@scriabin.music.vt.edu (Matthew Ross Davis) Message-Id: <9410202030.AA06296@scriabin.music.vt.edu> Subject: someone not getting mail To: majordomo-users@GreatCircle.COM (users) Date: Thu, 20 Oct 1994 16:30:20 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 430 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, I'm having a problem with one of the people in a list...he is sending messages to the list, and the list is receiving them and disbersing them (I know this because I'm on it). But the user tells me he isn't getting his own messages back. Is there some kind of option that majordomo has where the user doesn't get their own messages back, but gets everything else? Or could there just be something wrong with just him? Ross From majordomo-users-owner Thu Oct 20 17:03:44 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id QAA05953 for majordomo-users-outgoing; Thu, 20 Oct 1994 16:24:05 -0700 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id QAA05948 for ; Thu, 20 Oct 1994 16:24:00 -0700 Received: from glock.ramp.com by relay2.UU.NET with ESMTP id QQxmmn27348; Thu, 20 Oct 1994 19:21:10 -0400 Received: (from sharokh@localhost) by glock.ramp.com (8.6.9/8.6.6) id XAA06623; Thu, 20 Oct 1994 23:20:03 GMT Date: Thu, 20 Oct 1994 16:20:02 -0700 (MST) From: Sharokh Subject: problem To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk My admin has installed majordomo-1.92. we have created a list and i am the owner of that list. since I was gonna give my lists to a different acct, we made the list-owner to my other acct which: neda@ramp.com The following aliases is in the aliases database as well. #ident "@(#)ucb:common/ucbcmd/sendmail/lib/aliases 1.1" #ident "$Header: $" # RAFIGHAN - Prototype of Sharokhs list owner-rafighan: neda@ramp.com rafighan-approval: neda@ramp.com rafighan: "|/tools/majordomo-1.92/wrapper resend -l rafighan -h smtp.ramp.com rafighan-outgoing" owner-rafighan-outgoing: owner-rafighan rafighan-outgoing::include:/majordomo/lists/rafighan owner-rafighan-request: owner-rafighan rafighan-request: "|/tools/majordomo-1.92/wrapper majordomo -l rafighan" ----------------------------------------------------------------------------- According to list-owner-info, it said as soon as the list is created, send a newinfo command to get configuration files. I've tried it send an email from my 'neda@ramp.com' acct to 'rafighan@ramp.com' 'rafighan-request@ramp.com' 'rafighan-approval@ramp.com',and somehow my mails is being bounced back that it can't devliver, because of unknown user. I assumed if it's in all the above is in alias db and it should of recgonized it. Do I need to setup any kind of configuration file in my 'neda@ramp.com' accout to get it going. also, as users subscribe will majordomo creates a file in my neda directory so i can see it or edit any other configuration file? thanks sharokh From majordomo-users-owner Thu Oct 20 21:47:05 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id VAA07720 for majordomo-users-outgoing; Thu, 20 Oct 1994 21:43:45 -0700 Received: from nudge.io.org (root@nudge.io.org [198.133.36.4]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id VAA07715 for ; Thu, 20 Oct 1994 21:43:40 -0700 Received: (from mooseman@localhost) by nudge.io.org (8.6.9/8.6.9) id AAA20383; Wed, 19 Oct 1994 00:50:21 -0400 Date: Wed, 19 Oct 1994 00:50:20 -0400 (EDT) From: mooseman To: majordomo-users@GreatCircle.COM cc: support@io.org Subject: Magic Words needed, please! In-Reply-To: <9410181753.ZM21099@fogno.corp.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am trying to get my #$%&^^#%# list to work properly. It is a majordomo system and I want the replies to go to the list, rather than the sender. Due to its charter, it is meant to be a round-robin discussion type list. I have gone through the config file and done a few modifications (which the majordomo accepted), but still the replies go to the sender, not the list. What are the magic words to put in a config file to get it to do this? Or is it a function of the mail reader? (in "elm" I have to manually enter the address of the list under "cc:", put "pine" gives me the option of sending to both the sender and the list -- so somehow it is recognizing that the list is a sender) Please help -- with the replies being private, the whole purpose of the list is falling apart. Thanks in advance, \_\_\_____/_/_/ |--------------------------------------------| | mooseman@io.org | ] [ | May the MOOSE be with you! | [_] |--------------------------------------------| From majordomo-users-owner Thu Oct 20 22:17:05 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id WAA07967 for majordomo-users-outgoing; Thu, 20 Oct 1994 22:13:13 -0700 Received: from mail.barrnet.net (MAIL.BARRNET.NET [131.119.245.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id WAA07962 for ; Thu, 20 Oct 1994 22:13:06 -0700 Received: from nueva.pvt.k12.ca.us by mail.barrnet.net (5.67/1.37) id AA18806; Thu, 20 Oct 94 22:12:23 -0700 Received: by nueva1.nueva.pvt.k12.ca.us (5.67b/15.5+ECS 3.3+Nueva 0.9) id AA07113; Thu, 20 Oct 1994 22:12:23 -0700 Date: Thu, 20 Oct 1994 22:12:22 -0700 (PDT) From: Alexei Kosut To: mooseman Cc: majordomo-users@GreatCircle.COM, support@io.org Subject: Re: Magic Words needed, please! 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, 19 Oct 1994, mooseman wrote: > I am trying to get my #$%&^^#%# list to work properly. It is a majordomo > system and I want the replies to go to the list, rather than the sender. > Due to its charter, it is meant to be a round-robin discussion type list. > I have gone through the config file and done a few modifications (which > the majordomo accepted), but still the replies go to the sender, not the > list. What are the magic words to put in a config file to get it to do > this? Or is it a function of the mail reader? (in "elm" I have to > manually enter the address of the list under "cc:", put "pine" gives me > the option of sending to both the sender and the list -- so somehow it is > recognizing that the list is a sender) This is pretty darn easy... find in the config file (assuming you are using 1.92, I dunno about other versions), the "reply-to" entry and enter after the "=" the name of your list, including @host. This will then add a Reply-To: header into outgoing messages, and any desent mailer should reply using this header instead of the From: header. BTW, Pine knows that the list is to be mailed because it sees it in the To: header, not in any sort of from headers. Anyhow, have fun. > += Alexei Kosut == Pass the Prozac, please =+ | __ ___ ___ __ ___ __ // _____________________________________| | / / / _// _// / / _// | // "Computer viruses are the only life | | / /_ / _ / _// /_ / _ / / // form wholly created by humans... Talk | | /___//__//_/ /___//__//_/_| // about creating life in our own image." | += http://www.nueva.pvt.k12.ca.us/~akosut/ ========= Stephen W. Hawking =+ From majordomo-users-owner Fri Oct 21 06:49:25 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA11063 for majordomo-users-outgoing; Fri, 21 Oct 1994 06:39:05 -0700 Received: from nudge.io.org (root@nudge.io.org [198.133.36.4]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id GAA11058 for ; Fri, 21 Oct 1994 06:39:00 -0700 Received: (from mooseman@localhost) by nudge.io.org (8.6.9/8.6.9) id JAA19676; Fri, 21 Oct 1994 09:38:10 -0400 Date: Fri, 21 Oct 1994 09:38:09 -0400 (EDT) From: mooseman To: Alexei Kosut cc: majordomo-users@GreatCircle.COM, support@io.org Subject: Re: Magic Words needed, please! 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, 20 Oct 1994, Alexei Kosut wrote: > On Wed, 19 Oct 1994, mooseman wrote: > > > I am trying to get my #$%&^^#%# list to work properly. It is a majordomo > > system and I want the replies to go to the list, rather than the sender. > > This is pretty darn easy... find in the config file (assuming you are > using 1.92, I dunno about other versions), the "reply-to" entry and enter > after the "=" the name of your list, including @host. This will then add > a Reply-To: header into outgoing messages, and any desent mailer should > reply using this header instead of the From: header. > Well, that command exists in whatever version of majordomo I have (how can I check that?) and I have set it up with reply_to = listname@host (and yes, I substituted listname and host, not just actual "listname@host"). Is it supposed to be "reply-to" and not "reply_to?" the default config file had it as "reply_to." \_\_\_____/_/_/ |--------------------------------------------| | mooseman@io.org | ] [ | May the MOOSE be with you! | [_] |--------------------------------------------| From majordomo-users-owner Fri Oct 21 12:58:26 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA14667 for majordomo-users-outgoing; Fri, 21 Oct 1994 12:16:41 -0700 Received: from lobster.wellfleet.com (lobster.wellfleet.com [192.32.253.3]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id MAA14661 for ; Fri, 21 Oct 1994 12:16:37 -0700 Received: from wellfleet (pobox.wellfleet.com) by lobster.wellfleet.com (4.1/SMI-4.1) id AA15262; Fri, 21 Oct 94 15:08:57 EDT Received: from bee.wellfleet by wellfleet (4.1/SMI-4.1) id AA27621; Fri, 21 Oct 94 15:08:31 EDT Date: Fri, 21 Oct 94 15:08:31 EDT From: yi-shin_wu@wellfleet.com (Yi-Shin Wu) Message-Id: <9410211908.AA27621@wellfleet> To: majordomo-users@greatcircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is majordomo a public domain software? If so, could someone tell me where I can download a copy of it?? Thanks very much. -wys From majordomo-users-owner Fri Oct 21 14:47:09 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA16056 for majordomo-users-outgoing; Fri, 21 Oct 1994 14:21:14 -0700 Received: from cgl.bu.edu (CGL.BU.EDU [128.197.21.13]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id OAA16047 for ; Fri, 21 Oct 1994 14:20:56 -0700 Received: by cgl.bu.edu (8.6.8.1/Spike-2.1) id RAA00546; Fri, 21 Oct 1994 17:20:01 -0400 Date: Fri, 21 Oct 1994 17:20:01 -0400 From: jdh@cgl.bu.edu (Jason Heirtzler) Message-Id: <199410212120.RAA00546@cgl.bu.edu> To: Majordomo-Users@greatcircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk lists From majordomo-users-owner Fri Oct 21 15:18:39 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id PAA16273 for majordomo-users-outgoing; Fri, 21 Oct 1994 15:03:43 -0700 Received: from mail.barrnet.net (MAIL.BARRNET.NET [131.119.245.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id PAA16266 for ; Fri, 21 Oct 1994 15:03:37 -0700 Received: from nueva.pvt.k12.ca.us by mail.barrnet.net (5.67/1.37) id AA22906; Fri, 21 Oct 94 15:02:53 -0700 Received: by nueva1.nueva.pvt.k12.ca.us (5.67b/15.5+ECS 3.3+Nueva 0.9) id AA04563; Fri, 21 Oct 1994 15:02:50 -0700 Date: Fri, 21 Oct 1994 15:02:50 -0700 (PDT) From: Alexei Kosut To: mooseman Cc: majordomo-users@GreatCircle.COM, support@io.org Subject: Re: Magic Words needed, please! In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 21 Oct 1994, mooseman wrote: > (and yes, I substituted listname and host, not just actual > "listname@host"). Is it supposed to be "reply-to" and not "reply_to?" the > default config file had it as "reply_to." You're right.. it's reply_to. My mistake. += Alexei Kosut == Pass the Prozac, please =+ | __ ___ ___ __ ___ __ // _____________________________________| | / / / _// _// / / _// | // "Computer viruses are the only life | | / /_ / _ / _// /_ / _ / / // form wholly created by humans... Talk | | /___//__//_/ /___//__//_/_| // about creating life in our own image." | += http://www.nueva.pvt.k12.ca.us/~akosut/ ========= Stephen W. Hawking =+ From majordomo-users-owner Fri Oct 21 16:17:24 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id PAA16584 for majordomo-users-outgoing; Fri, 21 Oct 1994 15:51:51 -0700 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id PAA16579 for ; Fri, 21 Oct 1994 15:51:46 -0700 Received: from cygnus.com by relay2.UU.NET with ESMTP id QQxmqd24966; Fri, 21 Oct 1994 18:50:19 -0400 Received: from darkstar.cygnus.com (darkstar.cygnus.com [192.203.188.2]) by cygnus.com (8.6.9/8.6.9) with ESMTP id PAA15794 for ; Fri, 21 Oct 1994 15:50:05 -0700 Received: (from chicken@localhost) by darkstar.cygnus.com (8.6.9/8.6.9) id QAA19951 for Majordomo-Users@greatcircle.com; Fri, 21 Oct 1994 16:50:04 -0600 From: Chicken Message-Id: <199410212250.QAA19951@darkstar.cygnus.com> Subject: mail/news gateway To: Majordomo-Users@greatcircle.com Date: Fri, 21 Oct 1994 16:50:04 -0600 (MDT) X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 167 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I need to set up majordoom to gateway a list to news and news to the list. It is important that it does not loop endlessly. Any info would be helpful thanks chicken From majordomo-users-owner Sat Oct 22 00:16:55 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id XAA19840 for majordomo-users-outgoing; Fri, 21 Oct 1994 23:58:10 -0700 Received: from webcom.com (webcom.com [165.227.43.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id XAA19835 for ; Fri, 21 Oct 1994 23:58:05 -0700 Message-Id: <199410220658.XAA19835@miles.greatcircle.com> Received: by webcom.com (1.38.193.5/16.2) id AA29346; Fri, 21 Oct 1994 23:53:52 -0700 From: Thomas Leavitt Subject: Aliases somewhere besides /usr/lib/aliases To: majordomo-users@greatcircle.com Date: Fri, 21 Oct 94 23:53:52 PDT Mailer: Elm [revision: 70.85.2.1] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The OA /usr/lib/aliases, /users/majordomo/aliases solution someone forwarded me does not work, as sendmail 5.65 on HPUX will not accept more than one file in this line. It would be nice to have one less activity that requires mucking around in root. -- Web Communications (SM) Thomas Leavitt--leavitt@webcom.com Voice: (408) 457-9671 Lead Systems & Network Admin./Tech Suppt. Web Communications Home Page From majordomo-users-owner Sat Oct 22 12:18:27 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA22535 for majordomo-users-outgoing; Sat, 22 Oct 1994 12:03:49 -0700 Received: from [143.191.19.72] (host-72.greatcircle.com [143.191.19.72]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id MAA22529; Sat, 22 Oct 1994 12:03:41 -0700 Message-Id: <199410221903.MAA22529@miles.greatcircle.com> X-Sender: brent@miles.greatcircle.com (Unverified) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 22 Oct 1994 12:02:31 -0500 To: yi-shin_wu@wellfleet.com (Yi-Shin Wu), majordomo-users@greatcircle.com From: Brent@GreatCircle.COM (Brent Chapman) Subject: Re: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 15:08 10/21/94 -0400, Yi-Shin Wu wrote: >Is majordomo a public domain software? > >If so, could someone tell me where I can download a copy of it?? > >Thanks very much. It is not public domain, but it is freely available. It's available from host FTP.GreatCircle.COM, directory pub/majordomo. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Sat Oct 22 12:23:51 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA22479 for majordomo-users-outgoing; Sat, 22 Oct 1994 12:02:46 -0700 Received: from [143.191.19.72] (host-72.greatcircle.com [143.191.19.72]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id MAA22473; Sat, 22 Oct 1994 12:02:36 -0700 Message-Id: <199410221902.MAA22473@miles.greatcircle.com> X-Sender: brent@miles.greatcircle.com (Unverified) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 22 Oct 1994 12:01:26 -0500 To: mrossd@scriabin.music.vt.edu (Matthew Ross Davis), majordomo-users@GreatCircle.COM (users) From: Brent@GreatCircle.COM (Brent Chapman) Subject: Re: someone not getting mail Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 16:30 10/20/94 -0400, Matthew Ross Davis wrote: >Hi, > >I'm having a problem with one of the people in a list...he is sending >messages to the list, and the list is receiving them and disbersing them >(I know this because I'm on it). But the user tells me he isn't getting >his own messages back. > >Is there some kind of option that majordomo has where the user doesn't get >their own messages back, but gets everything else? Or could there just be >something wrong with just him? > >Ross No, but sendmail has such an option. Is the (non-)recipient a user on the same machine that Majordomo is running on? And is that where he's sending the messages from? I forget what the Sendmail option is, and don't have a reference handy (I'm offline, in a hotel room in Denver, at the moment), but I _think_ it's "Om". -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Sun Oct 23 12:47:01 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA28480 for majordomo-users-outgoing; Sun, 23 Oct 1994 12:40:30 -0700 Received: from cl-next4.cl.msu.edu (cl-next4.cl.msu.edu [35.8.4.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id MAA28475 for ; Sun, 23 Oct 1994 12:40:24 -0700 Received: by cl-next4.cl.msu.edu (NX5.67c/MSU-2.08A) id AA01474; Sun, 23 Oct 94 15:39:49 -0400 From: "Cris J. Holdorph" Message-Id: <9410231939.AA01474@cl-next4.cl.msu.edu> Subject: problems with approving messages To: majordomo-users@GreatCircle.COM Date: Sun, 23 Oct 1994 15:39:49 -36803936 (GMT-0400) Cc: strayert@cps.msu.edu Reply-To: holdorph@gdl.msu.edu X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2940 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've been having problems with a closed list I set up. The list owner has been getting messages with the subject that start out with "BOUNCE:". At first he tried to use the approve perl script. From elm he would do a "|approve" while having the BOUNCE message selected. However, this would result in a blank message going out to the list. Luckily (?) this causes an error for the machine where most of the list members are. It would generate a "too many recipients for blank message". However, the blank message would go to the users on other machines. This has happened more then 3 times. And the |approve mechanism has NEVER worked. Is this supposed to work? The man page for approve says so, but if so then what are we (me and the list owner) doing wrong? Next, I said, "well for now, just save the message, edit it, removed the majordomo stuff and add the 'Approved: password' line as the first line and resend it to the list". Fine. This worked ok. However, just yesterday it bombed. Below is a slightly trimmed version of the error message that came back to the majordomo id. ================================================== Date: Sat, 22 Oct 1994 12:44:18 +0500 From: Mailer-Daemon@cps.msu.edu (Mail Delivery Subsystem) Subject: Returned mail: Unable to deliver mail Message-Id: <9410221644.AC16074@arctic.cps.msu.edu> To: Content-Length: 2410 Status: RO ----- Transcript of session follows ----- 554 Too many recipients for no message body ----- Unsent message follows ----- Received: from acm.cps.msu.edu (landshark.cps.msu.edu) by arctic.cps.msu.edu (5.0/SMI-SVR4) id AA16074; Sat, 22 Oct 1994 12:44:18 +0500 Received: by acm.cps.msu.edu (4.1/MSU-2.01) id AA26196; Sat, 22 Oct 94 12:44:13 EDT Date: Sat, 22 Oct 94 12:44:13 EDT From: Majordomo ID Message-Id: <9410221644.AA26196@acm.cps.msu.edu> Sender: acmupe_announce-owner@acm.cps.msu.edu Precedence: bulk ******************** Navigating the Internet ********************* Tentative Plans --------------- I've cut out the remaining text of the message (a workshop posting for the local ACM chapter). Now what EMPTY message are they talking about? The whole message text is right there in the error message! Has anyone had this problem before? I'm afraid I might have to go back and make this an open list because it just is NOT working out the way it is right now. Any help fellow majordomo-users can give would be appreciated. BTW, it's version 1.92, and the last 4.x version of perl. ---- Cris J H -- ================================================== = Christopher J. Holdorph || Team OS/2 = = E-Mail: holdorph@acm.org || = ================================================== = "...Your dream is over, Or has it just begun?" = = ---"Silent Lucidity", Queensryche = ================================================== From majordomo-users-owner Sun Oct 23 14:21:59 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA28927 for majordomo-users-outgoing; Sun, 23 Oct 1994 14:08:25 -0700 Received: from netcomsv.netcom.com (uucp2-b.netcom.com [163.179.3.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id VAA19295 for ; Fri, 21 Oct 1994 21:12:06 -0700 Received: from localhost by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id UAA18374; Fri, 21 Oct 1994 20:56:47 -0700 Received: from [192.9.200.100] (don_mac [192.9.200.100]) by ncc1701a.talarian.com (8.6.9/8.6.9) with SMTP id SAA09836 for ; Fri, 21 Oct 1994 18:27:03 -0700 X-Sender: don@ncc1701a Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 21 Oct 1994 18:27:11 -0800 To: Majordomo-Users@GreatCircle.com From: don@talarian.com (Don Gray) Subject: HELP! "Info" alias autoresponder problems Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am trying to set up the "info" alias on my Unix (SunOS) machine so it automatically returns the contents of a text file to the sender. When I send a message to "info", the Sendmail command that is listed in the /etc/aliases file is executed, which looks like this: >info-owner: don ># the following "sendmail" command returns the text file ># "/home/mdomo/lists/info.info" to the original sender >info: "|/usr/lib/sendmail -f info-owner $SENDER < /home/mdomo/lists/info.info" ^^^^^^^^ ^^^^^^^ What happens at this point (according to the verbose output) is that the sender's actual address does not replace $SENDER, so it produces this error: > ----- Transcript of session follows ----- >501 info-owner... Recipient names must be specified I have been told by several people on the 'Net that they use this Sendmail command (just as I have it here) very successfully. I am using Sendmail V8 (just like them). However, I haven't been able to find *any* references to $SENDER in the O'Reilly Sendmail documentation book. I am now thinking that perhaps $SENDER is some sort of add-on script or macro that may not be defined on my system. Is this possible? If so, can someone send it to me? If this isn't the problem, does anyone have any ideas/suggestions? THIS CAN'T BE THAT HARD, SINCE EVERYONE'S DOING IT! (sorry, my exasperation is showing...) Is there a more efficient way of achieving my goal (other than using a Majordomo competitor like Procmail)? Thanks in advance, Don -- _____________________________________________________________________ Don Gray International Sales Director Talarian Corporation 444 Castro Street, Suite 140 e-mail (preferred): don@talarian.com Mountain View, CA 94041 Tel: +1-415-965-9066 x138 (direct) U.S.A. Fax: +1-415-965-9077 _____________________________________________________________________ From majordomo-users-owner Sun Oct 23 15:16:56 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id PAA29552 for majordomo-users-outgoing; Sun, 23 Oct 1994 15:11:14 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id PAA29547 for ; Sun, 23 Oct 1994 15:11:08 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA25144 (5.65c/IDA-1.4.4 for ); Sun, 23 Oct 1994 18:09:54 -0400 Message-Id: <199410232209.AA25144@cs.umb.edu> To: "Dougal Campbell" Cc: majordomo-users@greatcircle.com, "Mats Wichmann (mipsABI Consultant)" Subject: Re: digest footer/fronter In-Reply-To: Your message of "Fri, 14 Oct 1994 09:01:54." <9409147821.AA782150514@multi.iquest.com> Date: Sun, 23 Oct 1994 18:09:31 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <9409147821.AA782150514@multi.iquest.com>, "Dougal Campbell" writes: >>fine, but when they are made, the message_footer and message_fonter >>fields in the digest config file are chopped down to one line plus a >>blank. I had descriptive text in both, and was using the token >>_SUBJECTS_ in the fronter, but all that gets lost. This has happened >>several times on a couple of different machine types. What am I doing >>wrong this time? > >When I was first setting up my digests, I had similar problems. It turns out >that I didn't read the docs closely enough. Try putting a dash ('-') at the >beginning of each line of your message_footer and message_fronter text. I >forget just what the purpose is, I just remember doing it :) The reason is that a toally blank line is used to resync the config file parser, and detect missing "end" lines. E.G. fooble << END this is a fooble #oops missed an END here subscribe_policy = open blab << END buit I remebered it here END This has the effect of hiding the blab and subscribe_policy keywords entirely. However, by scanning for blank, or whitespace only lines, the config file parser reports an error after the #oops missed ... line above. The whitespace stripping is a side effect of this. I will try rethinking this mechanism since I can cache the config files and not have to parse them every time. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Mon Oct 24 06:19:46 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA04423 for majordomo-users-outgoing; Mon, 24 Oct 1994 06:14:05 -0700 Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id GAA04415 for ; Mon, 24 Oct 1994 06:13:58 -0700 Received: from wolves.UUCP by duke.cs.duke.edu (5.65/3.10G/4.1.3) id AA08460; Mon, 24 Oct 94 09:13:17 -0400 Received: by wolves.durham.nc.us (Linux Smail3.1.28.1 #5) id m0qzOoe-0000b5C; Mon, 24 Oct 94 08:47 EDT Received: (from gwp@localhost) by dithots.dithots.org (8.6.9/8.6.9) id IAA11796; Mon, 24 Oct 1994 08:37:54 -0400 Date: Mon, 24 Oct 1994 08:37:53 -0400 From: Bill Pogue Subject: USER: 32767 GROUP: 32767 To: majordomo-users@greatcircle.com In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have noticed in the past that certain files that majordomo updates get set with a UID and GID of 32767. Everything seemed to still work until last week when I upgraded the linux on my box. Now, all my majordomo archives are being set to this value. It's weird. My wrapper program is set to POSIX and UID:50 GID:50, which are both in the /etc/passwd and /etc/group respectively. What have I done wrong? bill From majordomo-users-owner Mon Oct 24 08:19:14 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA05130 for majordomo-users-outgoing; Mon, 24 Oct 1994 07:58:23 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id HAA05125 for ; Mon, 24 Oct 1994 07:58:16 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA12695 (5.65c/IDA-1.4.4 for ); Mon, 24 Oct 1994 10:57:00 -0400 Message-Id: <199410241457.AA12695@cs.umb.edu> To: CHAPIN Newt R Cc: Majordomo-Users Subject: Re: Handling boundary information from Ms Mail messages In-Reply-To: Your message of "Fri, 14 Oct 1994 16:35:00 PDT." <2E9F14DD@RISMTP01.RIS.OR.GOV> Date: Mon, 24 Oct 1994 10:56:37 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <2E9F14DD@RISMTP01.RIS.OR.GOV>, CHAPIN Newt R writes: >--Boundary (ID 9URzGkQWK+KBxVHDfJO+RA) >Content-type: TEXT/PLAIN > > >Microsoft Mail adds boundary information to each message when it's sent. > >Here's a sample boundary line and a content line that automatically get >added to my outgoing messages: > Boundary (ID h/N3gl3UlBGTbPw2osD6PQ) > Content-type: TEXT/PLAIN Not quite. The Boundary line (as can be seen above) starts with two '-' signs. This is what triggers the exit. If the - signs were missing, you would get exactly the behavior you describe. The scan for the -- prefix allows majordomo to exit before it processes a signature file (since most sig files start with --). Also it uses it internally. The Boundary line appears broken. It doesn't conform to the mime standard which is what the inclusion of the Content-Type: header would have me believe. >Is there any way to make majordomo deal with extra lines in messages so >seamlessly? Comment out the code that looks for the -- lines, but expect to get errors on your .signature file, and there may be problems with command loops as well (that's why majordomo reply messages start with --). -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Mon Oct 24 10:29:00 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA06245 for majordomo-users-outgoing; Mon, 24 Oct 1994 10:02:52 -0700 Received: from earth.willamette.edu (root@earth.willamette.edu [158.104.100.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id XAA01821 for ; Sun, 23 Oct 1994 23:02:12 -0700 Received: from jupiter (mrussell@jupiter.willamette.edu [158.104.1.1]) by earth.willamette.edu (8.6.8.1/8.6.4) with SMTP id XAA29126 for ; Sun, 23 Oct 1994 23:01:25 -0700 Date: Sun, 23 Oct 1994 23:01:24 -0700 (PDT) From: Marc Subject: just installed. . . weird errors. . . any ideas? To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi there. I just recently installed majordomo 1.92 on a SPARC 10. Since I performed the installation, all the mail I send to majordomo produces errors. In fact, each mail message produces three errors, and I have no idea why. I can see where they're coming from, but I don't know where to start in order to figure out what went wrong. If you can help, I'd appreciate it. Thanks in advance! The errors are reproduced below. ----- Transcript of session follows ----- shlock: open(">/home/majordomo-1.92/lists/shlock.14339"): Permission denied at /home/majordomo-1.92/shlock.pl line 131, <> line 1. Can't create new config file /home/majordomo-1.92/lists/admin.config.out at /home/majordomo-1.92/config_parse.pl line 440, <> line 1. 554 "|/home/majordomo-1.92/wrapper majordomo"... unknown mailer error 13 /home/majordomo-1.92 is the directory I installed majordomo in, lists is the list directory, and admin is the name of the list I'm trying to get going. Thanks for your help! marc mrussell@willamette.edu InfoX: sysadmin@olympus.dis.wa.gov ---------------------------------------------------------------------------- "A toast, before we go into battle -- true love. In whatever shape or form it may come, may we all in our dotage be proud to say, 'We were adored once, too.'" -Four Weddings and a Funeral ---------------------------------------------------------------------------- From majordomo-users-owner Mon Oct 24 11:50:49 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA07583 for majordomo-users-outgoing; Mon, 24 Oct 1994 11:46:07 -0700 Received: from disch2.disc.dla.mil (disch2.disc.dla.mil [131.82.180.4]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id LAA07569 for ; Mon, 24 Oct 1994 11:45:43 -0700 Message-Id: <199410241845.LAA07569@miles.greatcircle.com> Received: from isc3apc4056.disc.dla.mil by disch2.disc.dla.mil with SMTP (1.37.109.4/16.2) id AA19578; Mon, 24 Oct 94 14:45:51 -0400 X-Sender: i001952@disch2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 24 Oct 1994 14:44:11 -0400 To: majordomo-users@GreatCircle.COM From: ptyson@discg1.disc.dla.mil (Pat Tyson) Subject: list config help X-Mailer: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I've just installed majordomo-1.92, and established a 'test" list. When mail is sent to the list, the return path for replying to that mail is the sender and not the list. As the list owner I used the "config" command to get a copy of the listname.config file, edited it to set reply_to to listname@host, and used the "newconfig" command to install the new configuration file. The listname.config file looks like it was updated after I used the "newconfig" command, and I did not get an error message back. But . . . when I try to reply to a message sent to the list, it still sends the reply to me, the sender, instead of the list. Did I miss something installing the config file? Thanks! Pat Tyson From majordomo-users-owner Mon Oct 24 12:22:02 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA07764 for majordomo-users-outgoing; Mon, 24 Oct 1994 12:11:22 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id LAA06801 for ; Mon, 24 Oct 1994 11:05:02 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA24904 (5.65c/IDA-1.4.4 for ); Mon, 24 Oct 1994 14:03:22 -0400 Message-Id: <199410241803.AA24904@cs.umb.edu> To: silvert@biome.bio.dfo.ca (Bill Silvert) Cc: Majordomo-Users@greatcircle.com (Majordomo Users) Subject: Re: Majordomo results: Re: APPROVE fuzzy-b In-Reply-To: Your message of "Thu, 13 Oct 1994 14:08:09 -0300." <9410131708.AA14888@biome.bio.ns.ca> Date: Mon, 24 Oct 1994 14:02:58 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <9410131708.AA14888@biome.bio.ns.ca>, Bill Silvert writes: >I have a persistent problem accessing lists on my own machine. If I >subscribe, my address appears as "silvert (Bill Silvert)" but I prefer >to have the full address appear so that users can get full addresses >with the "who" command. But if I do this, Majordomo doesn't recognize >me as a member of the list. Is there an easy fix that lets me have it >both ways? The problem is that local mail delivery isn't creating fully qualified From: address lines. This is a sendmail/MTA problem. Does anybody have a copy of the Bat Book, and can give him the appropriate incantation for ruleset 0,3? It would be possible to hack majordomo's mungedomain so that user => user@(host specified in -h option) but I am inclined to think that the sendmail config should be fixed. I know that I would prefer it that way since I move my mailboxes around, and finding out that jim is not a local email address is a pain 8-). -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Mon Oct 24 12:42:11 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA06919 for majordomo-users-outgoing; Mon, 24 Oct 1994 11:22:56 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id LAA06914 for ; Mon, 24 Oct 1994 11:22:50 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA25960 (5.65c/IDA-1.4.4 for ); Mon, 24 Oct 1994 14:21:35 -0400 Message-Id: <199410241821.AA25960@cs.umb.edu> To: ken@is5.mdc.com Cc: Majordomo-Users@greatcircle.com Subject: Re: Long file names In-Reply-To: Your message of "Thu, 06 Oct 1994 12:08:33 PDT." <199410061908.AA05079@is5.mdc.com> Date: Mon, 24 Oct 1994 14:21:12 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <199410061908.AA05079@is5.mdc.com>, Ken Williams writes: >I have been running Majordomo 1.62 for a few years now, with a few >patches of my own! I finally decided I had better look at 1.92 and see >whats up. > >My problem is, the system I have it running on (Intergraph, CLIX) >doesn't allow for very long file names. I think the max is 14. Majordomo >1.92 seems to want to put some long file names out there and it just >doesn't work. Names like $listname.config.out. If the listname is >3 >chars, it won't fit. It will create a file, truncating the name, but >when there is a test for a file, it doesn't truncate. > >Has anyone run into this trouble? What did you do? Is there an easy fix >without munging all of the file names? 1.93 should be better in this regard, although changing over may be a pain. In the mailing-lists directory will be the following subdirectories: list - where the mailing list file resides config - where the config file for the list resides config/old - where the old config file for the list resides info - where the info file for the list resides passwd - where the passwd file for the list resides This way if the list name if blurbleganger (a nice 13 character name) the entire list name can be used. It also makes things easier for me from the point of scanning for different lists (fewer files to walk through) and makes it easier to check the update times on files for caching the majordomo config files to improve speed. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Mon Oct 24 12:53:37 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA07953 for majordomo-users-outgoing; Mon, 24 Oct 1994 12:18:27 -0700 Received: from bosnia.pop.psu.edu (barr@bosnia.pop.psu.edu [146.186.111.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA07934 for ; Mon, 24 Oct 1994 12:18:00 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id PAA12295; Mon, 24 Oct 1994 15:16:25 -0400 Message-Id: <199410241916.PAA12295@bosnia.pop.psu.edu> To: Marc cc: majordomo-users@GreatCircle.COM Subject: Re: just installed. . . weird errors. . . any ideas? In-reply-to: Your message of "Sun, 23 Oct 1994 23:01:24 PDT." X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Mon, 24 Oct 1994 15:16:24 -0400 From: David Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , Marc writes: >Hi there. I just recently installed majordomo 1.92 on a SPARC 10. Since >I performed the installation, all the mail I send to majordomo produces >errors. In fact, each mail message produces three errors, and I have no >idea why. I can see where they're coming from, but I don't know where to >start in order to figure out what went wrong. If you can help, I'd >appreciate it. Thanks in advance! The errors are reproduced below. > > ----- Transcript of session follows ----- >shlock: open(">/home/majordomo-1.92/lists/shlock.14339"): Permission >denied at /home/majordomo-1.92/shlock.pl line 131, <> line 1. Search for 'permission' in the Majordomo FAQ. You can get the Majordomo FAQ by sending an e-mail message to majordomo@pop.psu.edu with "get file majordomo-faq" in the body of the message. You can get an HTML version on the World Wide Web at http://www.pop.psu.edu/~barr/majordomo-faq.html. --Dave From majordomo-users-owner Mon Oct 24 23:46:58 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id XAA14553 for majordomo-users-outgoing; Mon, 24 Oct 1994 23:32:51 -0700 Received: from nova.unix.portal.com (nova.unix.portal.com [156.151.1.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id XAA14548 for ; Mon, 24 Oct 1994 23:32:42 -0700 Received: from jobe.shell.portal.com (chan@jobe.shell.portal.com [156.151.3.4]) by nova.unix.portal.com (8.6.7/8.6.5) with ESMTP id XAA13323 for ; Mon, 24 Oct 1994 23:32:03 -0700 Received: from localhost (chan@localhost) by jobe.shell.portal.com (8.6.4/8.6.5) id XAA04158 for majordomo-users@greatcircle.com; Mon, 24 Oct 1994 23:32:01 -0700 Date: Mon, 24 Oct 1994 23:32:01 -0700 From: Jeff Chan Message-Id: <199410250632.XAA04158@jobe.shell.portal.com> To: majordomo-users@greatcircle.com Subject: Automatic info address? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Can I with majordomo (1.62) or just a /etc/aliases entry make it so that mail to a given address results in a canned file being sent as the reply? I'm area of the info function in majordomo, but don't want to create an actual list. I'm also aware of the get command, but would like an address that doesn't require any commands, just an incoming message, to trigger the reply. Any help doing this with majordomo (or any other simple way) would be appreciated. Thanks in advance, Jeff C. From majordomo-users-owner Tue Oct 25 07:20:30 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA18014 for majordomo-users-outgoing; Tue, 25 Oct 1994 06:54:47 -0700 Received: from gateway.sctc.com (GATEWAY.SCTC.COM [192.55.214.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id GAA17998 for ; Tue, 25 Oct 1994 06:54:09 -0700 Received: from sccmailhost.sctc.com (sccmailhost.sctc.com [192.55.214.100]) by gateway.sctc.com (8.6.9/8.6.9) with SMTP id IAA01353 for ; Tue, 25 Oct 1994 08:52:00 -0500 Received: from sccmailhost.sctc.com by sccmailhost.sctc.com id 174030000; 25 Oct 94 8:54 CDT Received: from spirit by sccmailhost.sctc.com id 089350000; 25 Oct 94 8:54 CDT Received: from hector.sctc.com (hector [172.17.192.85]) by spirit.sctc.com (8.6.9/8.6.9) with ESMTP id IAA27620 for ; Tue, 25 Oct 1994 08:52:37 -0500 Received: (from jarocki@localhost) by hector.sctc.com (8.6.9/8.6.9) id IAA00421 for majordomo-users@greatcircle.com; Tue, 25 Oct 1994 08:52:35 -0500 From: Jim Jarocki Message-Id: <199410251352.IAA00421@hector.sctc.com> To: majordomo-users@greatcircle.com Date: Tue, 25 Oct 1994 08:52:34 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 11 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk lists list From majordomo-users-owner Tue Oct 25 11:49:47 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA20696 for majordomo-users-outgoing; Tue, 25 Oct 1994 11:24:14 -0700 Received: from nbn.nbn.com (nbn.nbn.com [199.4.64.19]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA20690 for ; Tue, 25 Oct 1994 11:24:06 -0700 Received: from sbt.sbtcorp.com (sbtcorp.com [199.4.101.1]) by nbn.nbn.com (8.6.4/8.6.4) with SMTP id LAA11690 for ; Tue, 25 Oct 1994 11:23:05 -0700 Received: from smtpgate.sbtcorp.com by sbt.sbtcorp.com id aa27902; 25 Oct 94 11:21 PDT Received: by sbtmain.sbtcorp.com with Microsoft Mail id <2EAD4DA9@sbtmain.sbtcorp.com>; Tue, 25 Oct 94 11:25:45 PDT From: KWAT - Ken Watkins To: "'majordomo-users@greatcircle.com'" Subject: A problem with mmdf Date: Tue, 25 Oct 94 11:25:00 PDT Message-ID: <2EAD4DA9@sbtmain.sbtcorp.com> Encoding: 16 TEXT X-Mailer: Microsoft Mail V3.0 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi. My problem is with just one of my lists. I'm using v 1.92 and mmdf on an SCO box, and I want a certain list to be a discussion list among the owners. However, the mail is always sent from the list manager alias rather than from the list itself. As far as I can tell, sendmail allows you to specify a "-f" switch to tell it from whom the mail came. And as far as I can tell, mmdf has no such option, so if the owners "Reply", it goes to the list manager rather than the users of the list. Is there some way I can tell mmdf to force the "from" field to be the list name rather than the list manager? Thanks for any help. - Ken Watkins kwat@sbtcorp.com From majordomo-users-owner Tue Oct 25 12:18:45 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA20687 for majordomo-users-outgoing; Tue, 25 Oct 1994 11:23:59 -0700 Received: from ftp.std.com (ftp.std.com [192.74.137.7]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA20681 for ; Tue, 25 Oct 1994 11:23:49 -0700 Received: from world.std.com by ftp.std.com (8.6.8.1/Spike-8-1.0) id OAA10055; Tue, 25 Oct 1994 14:23:08 -0400 Received: by world.std.com (5.65c/Spike-2.0) id AA01451; Tue, 25 Oct 1994 14:23:15 -0400 Message-Id: <199410251823.AA01451@world.std.com> To: Chicken Cc: Majordomo-Users@greatcircle.com Subject: Re: mail/news gateway In-Reply-To: Your message of "Fri, 21 Oct 1994 16:50:04 EDT." <199410212250.QAA19951@darkstar.cygnus.com> Date: Tue, 25 Oct 1994 14:23:15 -0400 From: Elizabeth Lear Newman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >I need to set up majordoom to gateway a list to news and news to the >list. It is important that it does not loop endlessly. Any info would >be helpful I actually have gateways going both ways: for the primarily-news lists, messages from the newsgroup are sent to the mailing list, and messages from the mailing list are posted to the newsgroup *only*. Other list members only see the messages once they are posted to the group and sent on through mail. This keeps it from looping. For the primarily-mail lists, messages to the mailing list are posted to the newsgroup. If someone posts to the newsgroup, it's sent *only* to the mailing list, and appears in the newsgroup after going to the mailing list. Both of these types use the "mail2news" and "news2mail" programs, with majordomo lists. ...eliz From majordomo-users-owner Tue Oct 25 12:50:44 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA21270 for majordomo-users-outgoing; Tue, 25 Oct 1994 12:27:39 -0700 Received: from netcomsv.netcom.com (uucp2-b.netcom.com [163.179.3.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA21265 for ; Tue, 25 Oct 1994 12:27:28 -0700 Received: from localhost by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id LAA10380; Tue, 25 Oct 1994 11:54:04 -0700 Received: from [192.9.200.100] (don_mac [192.9.200.100]) by ncc1701a.talarian.com (8.6.9/8.6.9) with SMTP id LAA07649; Tue, 25 Oct 1994 11:47:44 -0700 X-Sender: don@ncc1701a Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 25 Oct 1994 11:47:48 -0800 To: "John P. Rouillard" , Majordomo-Users@GreatCircle.com From: don@talarian.com (Don Gray) Subject: When will Majordomo 1.93 be available? Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk John Rouillard said: > 1.93 should be better in this regard, although changing over may be a pain. When will Majordomo 1.93 be available? Don don@talarian.com From majordomo-users-owner Tue Oct 25 14:07:28 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA22671 for majordomo-users-outgoing; Tue, 25 Oct 1994 13:42:01 -0700 Received: from xantia.caspur.it (xantia.caspur.it [193.204.5.5]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id FAA17411 for ; Tue, 25 Oct 1994 05:44:52 -0700 Received: by xantia.caspur.it; id AA08636; Tue, 25 Oct 1994 13:36:22 +0100 Date: Tue, 25 Oct 1994 13:36:22 +0100 From: Attilio Persi Message-Id: <9410251236.AA08636@xantia.caspur.it> To: majordomo-users@greatcircle.com Subject: help Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi, we are trying to build a moderate list on our majordomo and we have the following problem: when a user send a mail to a list, it arrives to the owner for approval as a BOUNCED mail with two set of headers: - the headers of the message from the sender to majordomo - the headers from majordomo to the owner of the list when the owner trys to approve the mail for forwarding it to the list without the approve script (the owner is not on a Unix system) the result is that he receives another BOUNCED message because majordomo doesn't understand the approved field. which is the right position of the the approved field? and which headers has to remain in the mail from the owner to the list? or where is the error? Thank you and greetings Virginia Calabritto & Attilio Persi From majordomo-users-owner Tue Oct 25 14:21:11 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA21740 for majordomo-users-outgoing; Tue, 25 Oct 1994 13:21:11 -0700 Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id OAA08971 for ; Mon, 24 Oct 1994 14:17:08 -0700 Received: from mars.mcs.com (root@Mars.mcs.com [192.160.127.85]) by kitten.mcs.com (8.6.9/8.6.9) with SMTP id QAA01357 for ; Mon, 24 Oct 1994 16:16:31 -0500 Received: by mars.mcs.com (/\==/\ Smail3.1.28.1 #28.1) id ; Mon, 24 Oct 94 16:16 CDT Message-Id: From: barnhart@mcs.com (Aaron Barnhart) Subject: Distributed mailing list -- please advise To: majordomo-users@greatcircle.com Date: Mon, 24 Oct 1994 16:16:28 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 611 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk As some of you know, I am trying to mount one of humanity's larger mailing lists -- the distribution for the David Letterman Top Tens -- which by the way if you want to subscribe to, *don't* mail me, mail letterman@mcs.net instead. It has about 30,000 subscribers. Rather than burden a single site with this, I am considering a semi-automated distributed system involving ten or more sites. I am wondering if Majordomo has capability, either currently or through a patch that could be written, to support placement and updating of names for a single list at different, let's say ftp'able, sites. Thanks. From majordomo-users-owner Tue Oct 25 14:52:36 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA22427 for majordomo-users-outgoing; Tue, 25 Oct 1994 13:38:44 -0700 Received: from seanet.com (kesha.seanet.com [199.181.164.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA21156 for ; Tue, 25 Oct 1994 12:14:30 -0700 Received: from hoss by seanet.com with SMTP (8.6.9/25-eef) id MAA09174; Tue, 25 Oct 1994 12:13:19 -0700 Date: Tue, 25 Oct 1994 12:12:57 -47900 From: Jim Radford To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I am having trouble getting my lists to work correctly. I believe there is some sort of list configuration file? I cannot find any of the options. I have went through the majordomo.ora file to setup a new list. When Majordomo recieves a message addresed to majordomo@hoss.seanet.com and there is a valid command sa: 'subscribe npinfo' Majordomo recognizes the list and replies >> subscribe npinfo But no other information is there. If I do a 'lists' it says that majordomo@hoss.seanet.com supports the following lists: and there is nothing else. If I try to subscribe to an invalid list it knows it doesn't exist and tells me so. Does somebody have a sample list (all files related to a list) that I can FTP from somewhere? That way I could get an idea of what is exactly supposed to go into the files I create for the lists. Thanks -- Jim ------------------------------------------------------------------------------ Jim Radford jim@hoss.seanet.com The Northwest PC Link IP:199.181.165.115 (206) 854-7057 - VOICE ------------------------------------------------------------------------------ From majordomo-users-owner Tue Oct 25 15:12:53 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA22410 for majordomo-users-outgoing; Tue, 25 Oct 1994 13:38:38 -0700 Received: from netcomsv.netcom.com (uucp2-b.netcom.com [163.179.3.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA20883 for ; Tue, 25 Oct 1994 11:43:49 -0700 Received: from localhost by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id LAA02840; Tue, 25 Oct 1994 11:06:31 -0700 Received: from [192.9.200.100] (don_mac [192.9.200.100]) by ncc1701a.talarian.com (8.6.9/8.6.9) with SMTP id LAA07430 for ; Tue, 25 Oct 1994 11:08:17 -0700 X-Sender: don@ncc1701a Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 25 Oct 1994 11:08:21 -0800 To: Majordomo-Users@GreatCircle.com From: don@talarian.com (Don Gray) Subject: HELP PLEASE! "Info" alias autoresponder problems (2nd try) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I would sure appreciate some help with the following problem... I don't think it should be very hard since it seems that everyone on the 'Net is doing it. I am trying to set up the "info" alias on my Unix (SunOS) machine so it automatically returns the contents of a text file to the sender. When I send a message to "info", the Sendmail command that is listed in the /etc/aliases file is executed, which looks like this: >info-owner: don ># the following "sendmail" command returns the text file ># "/home/mdomo/lists/info.info" to the original sender >info: "|/usr/lib/sendmail -f info-owner $SENDER < /home/mdomo/lists/info.info" ^^^^^^^^ ^^^^^^^ What happens at this point (according to the verbose output from sendmail) is that the sender's actual address does not replace $SENDER, so it produces this error: > ----- Transcript of session follows ----- >501 info-owner... Recipient names must be specified I have been told by several people on the 'Net that they use this Sendmail command (just as I have it here) very successfully. I am using Sendmail V8 (just like them). However, I haven't been able to find *any* references to $SENDER in the O'Reilly Sendmail documentation book. I am now thinking that perhaps $SENDER is some sort of add-on script or macro that may not be defined on my system. Is this possible? If so, can someone send it to me or tell me where I can get it? If this isn't the problem, does anyone have any ideas/suggestions? Is there a more efficient way of achieving my goal while still using Majordomo? (someone said that Procmail does this, but I think Procmail is a Majordomo competitor and I'd rather not switch since I know and like Majordomo, and since I finally got it installed successfully...). Thanks in advance, Don -- _____________________________________________________________________ Don Gray International Sales Director Talarian Corporation 444 Castro Street, Suite 140 e-mail (preferred): don@talarian.com Mountain View, CA 94041 Tel: +1-415-965-9066 x138 (direct) U.S.A. Fax: +1-415-965-9077 _____________________________________________________________________ From majordomo-users-owner Tue Oct 25 15:19:20 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA23487 for majordomo-users-outgoing; Tue, 25 Oct 1994 14:19:40 -0700 Received: from spsgate.sps.mot.com (spsgate.sps.mot.com [192.70.231.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id OAA23476 for ; Tue, 25 Oct 1994 14:19:11 -0700 Received: from mogate (mogate.sps.mot.com) by spsgate.sps.mot.com (4.1/SMI-4.1/Email 2.1 10/25/93) id AA09762; Tue, 25 Oct 94 14:18:07 MST Received: from motsps by mogate (4.1/SMI-4.1/Email-2.0) id AA23591; Tue, 25 Oct 94 14:18:03 MST Received: from risc.sps.mot.com by motsps (4.1/SMI-4.1/Email-2.1) id AA25835; Tue, 25 Oct 94 14:18:02 MST Received: from akamai.sps.mot.com by risc.sps.mot.com (4.1/SMI-3.0DEV3) id AA15830; Tue, 25 Oct 94 16:18:00 CDT Received: by akamai.sps.mot.com (4.1/SMI-4.1) id AA15132; Tue, 25 Oct 94 16:17:59 CDT From: jjoy@akamai.sps.mot.com (Jennifer Joy) Message-Id: <9410252117.AA15132@akamai.sps.mot.com> Subject: Summary from LISA BOF To: majordomo-users@greatcircle.com Date: Tue, 25 Oct 94 16:17:58 CDT X-Mailer: ELM [version 2.3 PL11b] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Well, finally, the majordomo BOF summary. John has added a lot of corrections and quite a bit of information which I just shamelessly folded in because it was looking too weird to credit him where necessary. ------ A Majordomo Birds-of-a-Feather (BOF) session was held at the USENIX Large Installation Systems Administration Conference (LISA VIII) on September 21, 1994. There was good attendance and it was nice to meet a lot of the people who are on this list (although I was becoming rather sleep deprived by that point on Wednesday). The BOF had a tight hour to fit into, as people were scheduled before and after in the same room. The BOF attempted to cover some of the concerns the development and user community had about its future. At last year's LISA the plan was to produce majordomo 2.0, a radical revision which would take the list management software from its initial intent (to manage Brent Chapman's 17 SAGE mailing lists) to something which would support a more general need. The development at that point had changed from Brent to John Rouillard as lunatic in charge. The two major revisions points of 2.0 were to restructure the list config, which was presently resulting in a proliferation of little files, to a single command script for each list. Secondly, the command parser needed to be rewritten. Before 2.0 could really get underway, the old 1.62 version began to mutate. Currently we are at version 1.92, and John's time is more limited so it will be a while before 1.93 comes out. The goals behind 2.0 are still valid, they have just been waylaid by bugs and mutations. In the realm of progress towards 2.0, Alan Stebbens has rewritten the command parser which is one chunk of the job. Some work is needed to fold it in, but it is a good step forward. One note on majordomo development: if you have an idea, you will want to join majordomo-workers (at greatcircle.com) and discuss it with folks there. That way the incompatible strains of majordomos may be kept to a minimum. One of the concerns as majordomo becomes more popular and subject to childish games is how to prevent people from creating mail loops by subscribing a redirector to the list. Alan suggested that incorporating something like mailagent to do message ID checks would be a good place to start. Mailagent will probably not become viable until 2.0. One area that needs work is the resend program. Among the things that need to be added are: recording of statistics such as mail message size, author, date sent, time spent in processing recording of message ID's and bouncing messages containing the message ID in a header like field to the list owner. If anybody would like to tackle this for 1.93 release, John would appreciate it. Also in 1.93 will be a complete rewrite of access list code. The new permissions stuff will be a table of patterns (regexp and glob style) versus actions: /.*cs.umb.edu$/ allow # action allowed *mit.edu deny # action denied *.bc.edu password=fooble # action allowed # if password is fooble * file=list # action allowed if name # found in file list * file=list-owners # ditto except file # is list-owners * deny # if it wasn't found deny it This will affect all options that currently have private options, as well as advertise, noadvertise, subscribe_policy/unsubscribe_policy. Performance is a big concern. [An interesting side note here is that Brent mentioned that because greatcircle.com has been a 3/60 perhaps a slow machine is a nice flame killer. Since the messages spread more slowly, there isn't that instant gratification feedback loop that causes people to go ballistic quite so quickly.] If you are interested in these issues, I'd also urge you to listen in on majordomo-workers. Also in 1.93 the fileystem layout will change. There will be standard Unix like layout structure (bin, lib, etc....) for the elements under the majordomo root. In addition the layour for mailing list directories may change. There will be one subdirectory for each type of file, mailing lists, per list config files, info files etc. This makes it much easier to create a precompiled global config file to improve performance, since it looks like reading in hundreds of config files is excessively expensive. What was mentioned in the meeting is folks are aware there are problems and code modifications need to be made. There is a need for better documentation and an installation time permission checker (for all the files, both POSIX and non). John's little wrapper checker will be included in 1.93. Other miscellaneous notes: A big win would be to get a taintperl version of the wrapper script. At the time of the original coding Perl was broken so the first attempt was aborted. Taintperl works now of course, so it should probably be done. There are plans to incorporate a real RFC822 header parser, thus handling a number of bugs with comment parsing etc. A consideration was put forth to consider the use of syslog to do the logging. There will be no more Error Code X messages, sysexits.h will be used which will give real messages. Sendmail uses sysexits.h to determine what happened to the child process. Brent is looking at changing the copyright status of majordomo. The copyleft as well as the Berkeley Copyright are being looked at. The hostile address message was never meant to catch x.400 addresses... freudian programming if you ask me. :-) The hostile address checks will be come smarter thanks to some experimentation by Anne Bennett. ----- And, that's all folks! Thanks to John for providing some needed editing and correction. jennifer -- Jennifer Joy sys/net admin Motorola/RISC HW Austin,TX jjoy@risc.sps.mot.com 512.891.8561 fax:512.891.3190 pgr:933-7333 #898561 From majordomo-users-owner Tue Oct 25 16:29:01 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id QAA24708 for majordomo-users-outgoing; Tue, 25 Oct 1994 16:00:20 -0700 Received: from cgl.ucsf.EDU (cgl.ucsf.EDU [128.218.14.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id PAA24651 for ; Tue, 25 Oct 1994 15:59:45 -0700 Received: from ccnext.ucsf.edu (ccnext.ucsf.EDU [128.218.80.24]) by cgl.ucsf.EDU (8.6.7/GSC4.24) with SMTP id PAA15793 for ; Tue, 25 Oct 1994 15:58:55 -0700 Received: by ccnext.ucsf.edu (NX5.67d/NeXT-1.0) id AA21728; Tue, 25 Oct 94 15:58:03 -0700 Date: Tue, 25 Oct 94 15:58:03 -0700 From: owner@ccnext.ucsf.edu (Richard Karpinski) Message-Id: <9410252258.AA21728@ccnext.ucsf.edu> To: majordomo-users@greatcircle.com Subject: UID and GID for shlock changes! Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk A few days ago, majordomo mail started failing in shlock.pl (line 131). I thought perhaps someone changed sendmail. I made shlock.pl reveal the UID and GID when it fails (see diff below). And now I see that when mail comes from the local machine, shlock gets run as them! What got done wrong and what can I do about it? Dick Enclosure: mods to reveal UID and GID 130a131,136 > $info = `id`; > $dirname = $tempname; > $dirname =~ s/\/shlock.*$//; > @stats = stat($dirname); > $dirinfa = join(' ', @stats); > warn("shlock: id = $info, dir = $dirinfa"); 168c174 < for ($tries = 0 ; $tries < 600 ; $tries++) { --- > for ($tries = 0 ; $tries < 20 ; $tries++) { 184c190 < sleep(1); --- > sleep(5); Enclosure: sample error messages trying lock "/u1/NOT/m/majordom/lists/emed-l.config.LOCK" for pid 108745 temporary filename "/u1/NOT/m/majordom/lists/shlock.108745" shlock: id = uid=5681(hwest) gid=5681(hwest) , dir = 1114113 65711 83453 3 4647 4647 66261 1024 783050625 782973733 782973733 4096 8 at /u1/NOT/m/majordom/bin/shlock.pl line 136. shlock: open(">/u1/NOT/m/majordom/lists/shlock.108745"): at /u1/NOT/m/majordom/bin/shlock.pl line 137. trying lock "/u1/NOT/m/majordom/lists/emed-l.config.LOCK" for pid 94404 temporary filename "/u1/NOT/m/majordom/lists/shlock.94404" shlock: id = uid=781(english) gid=781(english) , dir = 1114113 65711 83453 3 1 1 66261 1024 783104933 783113063 783113063 4096 8 at /u1/NOT/m/majordom/bin/shlock.pl line 136, <> line 1. shlock: open(">/u1/NOT/m/majordom/lists/shlock.94404"): at /u1/NOT/m/majordom/bin/shlock.pl line 137, <> line 1. From majordomo-users-owner Tue Oct 25 19:47:20 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA27849 for majordomo-users-outgoing; Tue, 25 Oct 1994 19:32:22 -0700 Received: from bosnia.pop.psu.edu (barr@bosnia.pop.psu.edu [146.186.111.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA27839 for ; Tue, 25 Oct 1994 19:32:02 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id WAA28697 for ; Tue, 25 Oct 1994 22:31:09 -0400 Message-Id: <199410260231.WAA28697@bosnia.pop.psu.edu> To: majordomo-users@GreatCircle.COM Subject: Re: Summary from LISA BOF In-reply-to: Your message of "Tue, 25 Oct 1994 16:17:58 CDT." <9410252117.AA15132@akamai.sps.mot.com> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Tue, 25 Oct 1994 22:31:08 -0400 From: David Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <9410252117.AA15132@akamai.sps.mot.com>, Jennifer Joy writes: >Well, finally, the majordomo BOF summary. John has added a lot of Was there any more mention of the distributed "List of Lists" proposal? majordomo.services.net is up and ready for MX records. --Dave From majordomo-users-owner Tue Oct 25 20:17:59 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA27998 for majordomo-users-outgoing; Tue, 25 Oct 1994 19:44:09 -0700 Received: from bosnia.pop.psu.edu (root@bosnia.pop.psu.edu [146.186.111.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA27992 for ; Tue, 25 Oct 1994 19:43:51 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id WAA28629; Tue, 25 Oct 1994 22:21:55 -0400 Message-Id: <199410260221.WAA28629@bosnia.pop.psu.edu> To: don@talarian.com (Don Gray) cc: Majordomo-Users@GreatCircle.COM Subject: Re: HELP PLEASE! "Info" alias autoresponder problems (2nd try) In-reply-to: Your message of "Tue, 25 Oct 1994 11:08:21 -0800." X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Tue, 25 Oct 1994 22:21:54 -0400 From: David Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk There's no special significance to "$SENDER" with sendmail. If you specify it in an alias, it will be treated as a shell variable and probably equate to a null argument. You're confusing sendmail with Majordomo. The example you're using doesn't use any Majordomo commands. You're not using Majordomo here, and Majordomo wasn't written to be able to do what you want. What you want to do is not provided by any program supplied with sendmail or Majordomo, though you could probably hack a one-page perl script to do it. Auto-replying with a canned message is an absolutely trivial thing -- you don't have to "switch" to another package. Just use the right tools for what they were designed for. If it means using multiple tools, fine. The persons who said they used $SENDER in this example were either lying or didn't understand the question. --Dave In message , Don Gray writes: >I would sure appreciate some help with the following problem... I don't >think it should be very hard since it seems that everyone on the 'Net is >doing it. > >I am trying to set up the "info" alias on my Unix (SunOS) machine so it >automatically returns the contents of a text file to the sender. > >When I send a message to "info", the Sendmail command that is listed in the >/etc/aliases file is executed, which looks like this: > >>info-owner: don >># the following "sendmail" command returns the text file >># "/home/mdomo/lists/info.info" to the original sender >>info: "|/usr/lib/sendmail -f info-owner $SENDER < /home/mdomo/lists/info.info >" > ^^^^^^^^ ^^^^^^^ > >What happens at this point (according to the verbose output from sendmail) >is that the sender's actual address does not replace $SENDER, so it >produces this error: > >> ----- Transcript of session follows ----- >>501 info-owner... Recipient names must be specified > >I have been told by several people on the 'Net that they use this Sendmail >command (just as I have it here) very successfully. I am using Sendmail V8 >(just like them). > >However, I haven't been able to find *any* references to $SENDER in the >O'Reilly Sendmail documentation book. I am now thinking that perhaps >$SENDER is some sort of add-on script or macro that may not be defined on >my system. Is this possible? If so, can someone send it to me or tell me >where I can get it? If this isn't the problem, does anyone have any >ideas/suggestions? > >Is there a more efficient way of achieving my goal while still using >Majordomo? (someone said that Procmail does this, but I think Procmail is >a Majordomo competitor and I'd rather not switch since I know and like >Majordomo, and since I finally got it installed successfully...). > >Thanks in advance, >Don > >-- >_____________________________________________________________________ > >Don Gray >International Sales Director Talarian Corporation > 444 Castro Street, Suite 140 >e-mail (preferred): don@talarian.com Mountain View, CA 94041 >Tel: +1-415-965-9066 x138 (direct) U.S.A. >Fax: +1-415-965-9077 > >_____________________________________________________________________ > > > From majordomo-users-owner Tue Oct 25 22:17:10 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id WAA29517 for majordomo-users-outgoing; Tue, 25 Oct 1994 22:05:48 -0700 Received: from webcom.com (webcom.com [165.227.43.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id WAA29512 for ; Tue, 25 Oct 1994 22:05:42 -0700 Message-Id: <199410260505.WAA29512@miles.greatcircle.com> Received: by webcom.com (1.38.193.5/16.2) id AA10016; Tue, 25 Oct 1994 22:01:30 -0700 From: Thomas Leavitt Subject: Not reading TZ in majordomo.cf! To: majordomo-users@greatcircle.com Date: Tue, 25 Oct 94 22:01:30 PDT Mailer: Elm [revision: 70.85.2.1] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk For some reason, messages from Majordomo are 7 hours ahead of us (us = PDT). It is currently 10:00 p.m. here, and Majordomo is sending mail in response to messages from this site with a date of 5:00 a.m. >From my majordomo.cf file: # time zone $ENV{"TZ"} = "PDT"; -- Web Communications (sm) Thomas Leavitt--leavitt@webcom.com Voice: (408) 457-9671 Lead Systems & Network Admin./Tech Suppt. Web Communications Home Page From majordomo-users-owner Tue Oct 25 22:46:59 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id WAA29756 for majordomo-users-outgoing; Tue, 25 Oct 1994 22:30:17 -0700 Received: from webcom.com (webcom.com [165.227.43.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id WAA29751 for ; Tue, 25 Oct 1994 22:30:11 -0700 Message-Id: <199410260530.WAA29751@miles.greatcircle.com> Received: by webcom.com (1.38.193.5/16.2) id AA10703; Tue, 25 Oct 1994 22:26:02 -0700 From: Thomas Leavitt Subject: restrict_post: BOUNCE ... non-member? To: majordomo-users@greatcircle.com Date: Tue, 25 Oct 94 22:26:02 PDT Mailer: Elm [revision: 70.85.2.1] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When a subscriber to a list with a restrict_post file controlling who can post to that list, the owner gets a message from Majordomo saying that the message was submitted by a non-member. It appears the function of this is to have a list that allows only certain people to post, while having the message sent to a greater number of people (moderation without the work, of a sort). -- Web Communications (sm) Thomas Leavitt--leavitt@webcom.com Voice: (408) 457-9671 Lead Systems & Network Admin./Tech Suppt. Web Communications Home Page From majordomo-users-owner Tue Oct 25 22:55:18 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id WAA29850 for majordomo-users-outgoing; Tue, 25 Oct 1994 22:38:29 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id WAA29843; Tue, 25 Oct 1994 22:38:26 -0700 Message-Id: <199410260538.WAA29843@miles.greatcircle.com> To: Thomas Leavitt cc: majordomo-users@greatcircle.com Subject: Re: Not reading TZ in majordomo.cf! In-reply-to: Your message of Tue, 25 Oct 94 22:01:30 PDT Date: Tue, 25 Oct 1994 22:38:25 -0700 From: Brent Chapman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Thomas Leavitt writes: # For some reason, messages from Majordomo are 7 hours ahead of us (us = PDT). # # It is currently 10:00 p.m. here, and Majordomo is sending mail in response # to messages from this site with a date of 5:00 a.m. # # >From my majordomo.cf file: # # # time zone # $ENV{"TZ"} = "PDT"; Majordomo doesn't use TZ itself; it doesn't generate "Date:" headers, it lets the underlying mailsystem do that for it. Setting TZ in the environment merely passes it along to programs that Majordomo runs, like Sendmail. If Sendmail doesn't pay any attention to it when putting "Date:" fields in messages (and yours apparently doesn't), there's probably nothing you can do about it from Majordomo. On the other hand, some systems _do_ use TZ, but use a different syntax (i.e., "PST8PDT" instead of simply "PDT"). You'll have to figure out for yourself whether your system pays attention to the TZ envariable, and what the right setting for it is. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Wed Oct 26 05:17:26 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA03277 for majordomo-users-outgoing; Wed, 26 Oct 1994 05:09:55 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id FAA03265 for ; Wed, 26 Oct 1994 05:09:49 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA09901 (5.65c/IDA-1.4.4 for ); Wed, 26 Oct 1994 08:04:27 -0400 Message-Id: <199410261204.AA09901@cs.umb.edu> To: Thomas Leavitt Cc: majordomo-users@greatcircle.com Subject: Re: restrict_post: BOUNCE ... non-member? In-Reply-To: Your message of "Tue, 25 Oct 1994 22:26:02 PDT." <199410260530.WAA29751@miles.greatcircle.com> Date: Wed, 26 Oct 1994 08:04:03 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <199410260530.WAA29751@miles.greatcircle.com>, Thomas Leavitt writes: >When a subscriber to a list with a restrict_post file controlling >who can post to that list, the owner gets a message from Majordomo >saying that the message was submitted by a non-member. Yes, the message is a bit misleading. Usually the -I flag works with the file of list subscribers. However, the address that is checked for is the From: (and possibly the reply-to address, although I don't think so in this case) address. So if somebody is on the list with an address that can't be derived from the From address (e.g. if mungedomain is turned on, it is applied during the search) they are improperly tagged a "non-member". Hopefully the access list stuff in 1.93 will allow the list manager to control this by subscribing john_rouillard@baz.com, and then adding rouilj@foobaz.com to the access lists for the lists. (1.93 will probably not have an "alternate members" keyword. Each access lists will have to be done by hand, sorry). >It appears the function of this is to have a list that allows >only certain people to post, while having the message sent to a >greater number of people (moderation without the work, of a sort). Well, yes, but those people who are allowed to post can still post garbage, which moderation would stop. It just reduces the number of people you have to shoot when the list degenerates into a flame war 8-). -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Wed Oct 26 05:26:57 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id EAA03118 for majordomo-users-outgoing; Wed, 26 Oct 1994 04:58:51 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id EAA03113 for ; Wed, 26 Oct 1994 04:58:44 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA09543 (5.65c/IDA-1.4.4 for ); Wed, 26 Oct 1994 07:57:05 -0400 Message-Id: <199410261157.AA09543@cs.umb.edu> To: David Barr Cc: majordomo-users@greatcircle.com Subject: Lists of lists (was Re: Summary from LISA BOF) In-Reply-To: Your message of "Tue, 25 Oct 1994 22:31:08 EDT." <199410260231.WAA28697@bosnia.pop.psu.edu> Date: Wed, 26 Oct 1994 07:56:41 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Since this is something of general interest that crops up again and again, I've decided to put this on majordomo-users rather than majordomo-workers. In message <199410260231.WAA28697@bosnia.pop.psu.edu>, David Barr writes: >In message <9410252117.AA15132@akamai.sps.mot.com>, Jennifer Joy writes: >>Well, finally, the majordomo BOF summary. John has added a lot of > >Was there any more mention of the distributed "List of Lists" >proposal? majordomo.services.net is up and ready for MX records. No actually, there wasn't. I'll add this to my todo list. The major (if you'll pardon the pun) problem with majordomo lists of lists is getting majordomo to supress the welcome message that is sent to new subscribers. For those of you who are new to this, the way it was supposed to work is that there would be one or two top level majordomi that would have lists called majordomos, so if you wanted to register your majordomo, you would simply send: subscribe majordomo@my.address.com to majordomo@majordomo.services.net. Once every polling period, a message consisting of the word "lists" with the reply address set to lists-collection@site would be sent to these majordomi lists. One problem with this picture is that the subscription process would send back a "welcome to this list" message to majordomo@my.address.com. The majordomo@my.address.com would send a reply to the welcome message (even though it is a null command message) to majordomo@majordomo.services.net. The services majordomo would then send a null reply to majordomo@my.address.com, can you say "mail loop" boys a girls. Even though the -- signs at the front of all majordomo messages would stop the majordomi from interpreting the body of the messages as commands, we would still have these little pieces of mail flying about. One thing I am wondering, is it worth adding a new config option: welcome = [yes|no] to control this, or should I just special case (and hard code) the name of the lists of lists (if a site is running it). Also we will get a mail loop if the person subscribing the majordomo uses the majordomo account since the reply message for the subscribe request will go to majordomo triggering the loop. The way I think I am going to handle this is to create a list of people who should never get majordomo REPLY mail. To start with: root, majordomo, daemon, manager any other suggestions (like anybody with / in their addresses 8-), Oops sorry that's another topic 8-).) ? -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Wed Oct 26 07:19:02 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA04116 for majordomo-users-outgoing; Wed, 26 Oct 1994 07:03:32 -0700 Received: from polo.iquest.com (root@polo.iquest.com [199.170.120.63]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id HAA04110 for ; Wed, 26 Oct 1994 07:03:26 -0700 Received: by polo.iquest.com (Linux Smail3.1.28.1 #1) id m0r08uh-002EFlC; Wed, 26 Oct 94 09:01 CDT Received: from cc:Mail by multi.iquest.com id AA783185060 Wed, 26 Oct 94 08:24:20 Date: Wed, 26 Oct 94 08:24:20 From: "Dougal Campbell" Encoding: 1288 Text Message-Id: <9409267831.AA783185060@multi.iquest.com> To: majordomo-users@greatcircle.com, Jim Radford Subject: Re: No subject given Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >I am having trouble getting my lists to work correctly. I believe there >is some sort of list configuration file? I cannot find any of the >options. I have went through the majordomo.ora file to setup a new list. >When Majordomo recieves a message addresed to majordomo@hoss.seanet.com >and there is a valid command sa: 'subscribe npinfo' Majordomo recognizes >the list and replies >> subscribe npinfo But no other information is >there. If I do a 'lists' it says that majordomo@hoss.seanet.com supports >the following lists: and there is nothing else. If I try to subscribe to >an invalid list it knows it doesn't exist and tells me so. > >Does somebody have a sample list (all files related to a list) that I can >FTP from somewhere? That way I could get an idea of what is exactly >supposed to go into the files I create for the lists. > >Thanks This sounds just like a problem I had just the other day when setting up a new list. It turned out to be a permissions problem. Double check your 'npinfo' file and make sure that: 1) It's owned by your majordomo user and group 2) Both user and group have read *and* write permissions. Dougal Campbell dougal@mtronics.com dougal@iquest.com owner-majordomo@magellan.iquest.com From majordomo-users-owner Wed Oct 26 07:39:41 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA04012 for majordomo-users-outgoing; Wed, 26 Oct 1994 06:51:11 -0700 Received: from ssi.edc.org (ssi.edc.org [155.38.10.5]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id GAA03997 for ; Wed, 26 Oct 1994 06:50:53 -0700 Received: from ssi.edc.org by ssi.edc.org id aa08019; 26 Oct 94 9:48 EDT Date: Wed, 26 Oct 1994 09:48:29 -0400 (EDT) From: Gunther Anderson To: KWAT - Ken Watkins cc: "'majordomo-users@greatcircle.com'" Subject: Re: A problem with mmdf In-Reply-To: <2EAD4DA9@sbtmain.sbtcorp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Tue, 25 Oct 1994, KWAT - Ken Watkins wrote: > As far as I can tell, sendmail allows you to specify a "-f" switch to tell > it from whom the mail came. And as far as I can tell, mmdf has no > such option, so if the owners "Reply", it goes to the list manager rather > than the users of the list. Is there some way I can tell mmdf to force the > "from" field to be the list name rather than the list manager? Thanks for > any help. MMDF's sendmail stub does in fact parse the -f parameter, it just mishandles it. A few months ago I went through this problem, and came up with patches to MMDF's sendmail.c to allow you to recompile it to handle the -f parameter correctly. I include below my instructions on how to tweak MMDF to work better with Majordomo. I include only the section pertinent to sendmail. However, there are a handful of other annoying problems you stand to run into, so you might want the full document. Actually, read closely the second part below where I talk about the things the list-processor channel does on MMDF. That's probably where your problem lies. Gunther Anderson p.s. write me back for the full document if you want it; it's also in the Majordomo list archives, for I sent it there when I finished. ------------- Majordomo can be fully utilized in a MMDF II 43b environment, it's just not easy. There are a number of features in both pieces which need to be overcome. ... The next problem is a little more severe, and a lot harder to fix. If you have the source to your MMDF, you're in luck. If you don't, just grit your teeth and bull it through. Because MMDF's sendmail has one honest-to-goodness bug, specifically in the way it handles the -f{sender} parameter. Normal sendmail uses the -f parameter to specify the envelope "From " header (the SMTP 'Mail From:' command) only. MMDF's sendmail deliberately uses the -f parameter not only for the "From " header, but also to rewrite the message-level "From:" header. In mailing lists, this means that the record of the original author of any message passing through resend is totally lost. This is bad. What you have to do is modify uip/other/sendmail.c, and then somehow manage to get it compiled. So, one thing at a time. First, get and unpack the MMDF II 43b source. If you already have it, and have used it to build your system, wonderful. You can ignore all sorts of things in the next few paragraphs. If not, we have some work to do. cd to uip/other, and apply the following diff to the file sendmail.c. ------------CUT HERE------------ *** sendmail.old.c Fri Oct 10 15:16:57 1986 --- sendmail.c Fri Aug 5 06:46:28 1994 *************** *** 28,33 **** --- 28,34 ---- int extract; int badaddrs; int rewritefrom; + int gotafrom; int die(); *************** *** 93,104 **** continue; } } ! if (rewritefrom) { syserr("More than one \"from\" person"); continue; } from = p; ! rewritefrom++; continue; case 'F': /* set full name */ --- 94,105 ---- continue; } } ! if (gotafrom) { syserr("More than one \"from\" person"); continue; } from = p; ! gotafrom++; continue; case 'F': /* set full name */ *************** *** 151,157 **** syserr("Verify mode not supported on header components"); strcpy(subflags, "ml"); ! if (rewritefrom) strcat(subflags, "t"); if (watch) strcat(subflags, "w"); --- 152,158 ---- syserr("Verify mode not supported on header components"); strcpy(subflags, "ml"); ! if (rewritefrom || gotafrom) strcat(subflags, "t"); if (watch) strcat(subflags, "w"); ----------CUT HERE--------- This little patch prevents sendmail from actively rewriting the "From:" header, so that the original authors are preserved. Now, you get to rebuild sendmail. Ignore the next section if you already know how. cd to the .../mmdf2/conf directory. There you will find a bunch of configuration directories. Find one that matches you. I couldn't. Actually, I wound up modifying the files in the bbn directory. sendmail.c only uses the Makefile.com file, and in that you need only deal with the C preprocessor directives, the host name, and the library files. Anyway, use your intelligence, read the other Makefile.com's, and get something that works. When you've got a Makefile.com that you think works, execute the command: $ sh sitesetup bbn from within the conf directory. Instead of bbn, of course, type whatever directory you were working with. This will copy the revised configuration files where they need to go. Then cd back to .../mmdf2/uip/other, and execute the command $ ./gen xsendmail Yes, the 'x' is important. Anyway, you have a new sendmail, named xsendmail, in that directory. If your compile didn't work, make the appropriate changes in the ../../Makefile.com (like missing libraries), and rerun ./gen. Since I don't trust anything I compiled, I left the original sendmail in /usr/lib, and copied the new xsendmail simply as xsendmail to /usr/lib, and changed the ownership and permissions to match the real sendmail. Finally, edit Majordomo's resend script, and change all references to sendmail to xsendmail, with all the same parameters. You will also probably want to change the references in majordomo.cf and majordomo.pl. Voila, now you have a working Majordomo. There is one more issue, though, that you'll want to consider. If you have, as you might very well want to, Majordomo pointing to an alias which specifies the list channel, the list channel will rewrite your envelope header again. Thankfully, it doesn't change the message From: header. Let me show you what I mean. If you have an series of entries in your aliases.list which look like this: testlist: "majordom|/usr/local/majordomo/bin/wrapper resend ... testlist-tem" testlist-tem: testlist-out@list-processor testlist-out: :include:/usr/local/majordomo/lists/testlist ...and so forth... thus explicitly using the list channel, the list channel will change the envelope "From " header from "owner-testlist" as Majordomo would have it, to "testlist-request". This affects things like bounce messages. If you want to use the list channel (check the man pages for its advantages), you'll need to be careful about using the -request address. If, on the other hand, you have entries which look like this: testlist: "majordom|/usr/local/majordomo/bin/wrapper resend ... testlist-out" testlist-out: :include:/usr/local/majordomo/lists/testlist ...and so forth... thereby going straight into the appropriate delivery channel, and bypassing the list channel, your envelope header will remain unchanged. Huge lists, though, will really want to think about the list channel, or about finding another way of deferring delivery. There aren't many options. Read the list man page if you haven't already. From majordomo-users-owner Wed Oct 26 08:49:51 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA04806 for majordomo-users-outgoing; Wed, 26 Oct 1994 08:27:04 -0700 Received: from hmco.com (hmgate.hmco.com [155.44.80.23]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id IAA04795 for ; Wed, 26 Oct 1994 08:26:52 -0700 Received: by hmco.com (5.65/DEC-Ultrix/4.3/jcurran+a1+umc+dnet) id AA04495; Wed, 26 Oct 1994 11:25:46 -0400 Received: by willy.hmco.com (5.0/SMI-SVR4) id AA02294; Wed, 26 Oct 1994 11:25:41 +0500 Date: Wed, 26 Oct 1994 11:25:41 +0500 From: alaka@hmco.com (Ghassan J. Alaka) Message-Id: <9410261525.AA02294@willy.hmco.com> To: majordomo-users@greatcircle.com Subject: approved messages X-Sun-Charset: US-ASCII Content-Length: 430 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have Majordomo 1.92 up and running with a couple of lists. One of the lists is moderated with less than 50 members. When I send a message with Approved: password the members only get the following: From owner-special@hmco.com Wed Oct 26 11:04 EDT 1994 Date: Wed, 26 Oct 1994 09:59:23 +0500 From: owner-special@hmco.com Nothing else, no text or the original approved message. Any ideas will be appreciated. alaka@hmco.com From majordomo-users-owner Wed Oct 26 09:52:38 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id JAA05146 for majordomo-users-outgoing; Wed, 26 Oct 1994 09:17:11 -0700 Received: from netcomsv.netcom.com (uucp2-b.netcom.com [163.179.3.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id JAA05129; Wed, 26 Oct 1994 09:16:42 -0700 Received: from localhost by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id IAA13241; Wed, 26 Oct 1994 08:53:51 -0700 Received: from [192.9.200.100] (don_mac [192.9.200.100]) by ncc1701a.talarian.com (8.6.9/8.6.9) with SMTP id IAA02643; Wed, 26 Oct 1994 08:48:50 -0700 X-Sender: don@ncc1701a Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Oct 1994 08:48:56 -0800 To: Majordomo-Users@GreatCircle.com From: don@talarian.com (Don Gray) Subject: Re: BRENT: "Info" alias autoresponder problems (2nd try) Cc: Brent Chapman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Just a quick note to say that Brent Chapman's hacked version of "request-answer" works like a charm! One comment: at about line 74 of the file is the line that says: print MAIL "\f\n"; On my Macintosh client where I read my mail, the "\f" produces a funny character on the screen. I took out the "\f" and it still seems to work fine. Do I actually need it for anything (such as when mail is received on some other types of machines/terminals)? Thanks in advance, Don From majordomo-users-owner Wed Oct 26 10:27:50 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA05970 for majordomo-users-outgoing; Wed, 26 Oct 1994 10:06:16 -0700 Received: from sextant.elpress.com (sextant.elpress.com [198.80.36.5]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA05946 for ; Wed, 26 Oct 1994 10:05:59 -0700 Received: from notes.elpress.com (notes.elpress.com [198.80.36.13]) by sextant.elpress.com (8.6.5/8.6.5) with SMTP id MAA19177 for <@sextant.elpress.com:Majordomo-Users@GreatCircle.com>; Wed, 26 Oct 1994 12:57:08 -0400 Received: by notes.elpress.com (IBM OS/2 SENDMAIL VERSION 1.3.2)/1.0) id AA0147; Wed, 26 Oct 94 12:56:56 -0700 Message-Id: <9410261956.AA0147@notes.elpress.com> Received: from Electric Press with "Lotus Notes Mail Gateway for SMTP" id 4A4E20CDAC339A51852560F4004D0E29; Wed, 26 Oct 94 12:56:55 To: Majordomo-Users From: Rob Main Date: 26 Oct 94 10:05:09 ES Subject: Subject absent Mime-Version: 1.0 Content-Type: Text/Plain Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have Majordomo 1.92 installed. I'm using Sendmail on BSDI Unix. I have a moderated, closed list and I am the owner. When I get a "BOUNCED" message for approval I edit the message and put the name of the list in the To: header and "Approved: password" as the first line in the body. I also fill in the subject on the subject line. When the message comes through, however, the subject is always -- No Subject --. Any idea what I'm doing wrong or point me to the appropriate FAQ. Thanks. Rob Main rmain@elpress.com From majordomo-users-owner Wed Oct 26 10:54:42 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id JAA05588 for majordomo-users-outgoing; Wed, 26 Oct 1994 09:56:24 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id JAA05582; Wed, 26 Oct 1994 09:56:22 -0700 Message-Id: <199410261656.JAA05582@miles.greatcircle.com> To: don@talarian.com (Don Gray) cc: Majordomo-Users@greatcircle.com Subject: Re: BRENT: "Info" alias autoresponder problems (2nd try) In-reply-to: Your message of Wed, 26 Oct 1994 08:48:56 -0800 Date: Wed, 26 Oct 1994 09:56:13 -0700 From: Brent Chapman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk don@talarian.com (Don Gray) writes: # Just a quick note to say that Brent Chapman's hacked version of # "request-answer" works like a charm! # # One comment: at about line 74 of the file is the line that says: # print MAIL "\f\n"; # On my Macintosh client where I read my mail, the "\f" produces a funny # character on the screen. I took out the "\f" and it still seems to work # fine. Do I actually need it for anything (such as when mail is received on # some other types of machines/terminals)? # # Thanks in advance, # Don # # "\f" is a "form feed"; if you print the file, it should cause the printer to begin a new page when it gets to that character. It was what I chose to do to separate multiple files; feel free to change it, if that's not the behavior you want. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Wed Oct 26 10:55:53 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id JAA05541 for majordomo-users-outgoing; Wed, 26 Oct 1994 09:54:43 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id PAA24305; Tue, 25 Oct 1994 15:29:53 -0700 Message-Id: <199410252229.PAA24305@miles.greatcircle.com> To: don@talarian.com (Don Gray) cc: Majordomo-Users@greatcircle.com Subject: Re: HELP PLEASE! "Info" alias autoresponder problems (2nd try) In-reply-to: Your message of Tue, 25 Oct 1994 11:08:21 -0800 Date: Tue, 25 Oct 1994 15:29:23 -0700 From: Brent Chapman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk don@talarian.com (Don Gray) writes: # I would sure appreciate some help with the following problem... I don't # think it should be very hard since it seems that everyone on the 'Net is # doing it. # # I am trying to set up the "info" alias on my Unix (SunOS) machine so it # automatically returns the contents of a text file to the sender. # # When I send a message to "info", the Sendmail command that is listed in the # /etc/aliases file is executed, which looks like this: # # >info-owner: don # ># the following "sendmail" command returns the text file # ># "/home/mdomo/lists/info.info" to the original sender # >info: "|/usr/lib/sendmail -f info-owner $SENDER < /home/mdomo/lists/info.info" # ^^^^^^^^ ^^^^^^^ # # What happens at this point (according to the verbose output from sendmail) # is that the sender's actual address does not replace $SENDER, so it # produces this error: # # > ----- Transcript of session follows ----- # >501 info-owner... Recipient names must be specified # # I have been told by several people on the 'Net that they use this Sendmail # command (just as I have it here) very successfully. I am using Sendmail V8 # (just like them). # # However, I haven't been able to find *any* references to $SENDER in the # O'Reilly Sendmail documentation book. I am now thinking that perhaps # $SENDER is some sort of add-on script or macro that may not be defined on # my system. Is this possible? If so, can someone send it to me or tell me # where I can get it? If this isn't the problem, does anyone have any # ideas/suggestions? I have never heard of this syntax in any version of Sendmail. # Is there a more efficient way of achieving my goal while still using # Majordomo? (someone said that Procmail does this, but I think Procmail is # a Majordomo competitor and I'd rather not switch since I know and like # Majordomo, and since I finally got it installed successfully...). I use a hacked-up version of the "request-answer" script, which I call "auto-answer", included below. The command line arguments are "-c Cc-address From file [file ...]" I.e., you give a "-c Cc-address" argument to add a "Cc: Cc-address" line to the outgoing mail, you specify who the outgoing mail should appear to be from with the "From" argument, and you specify the file (or files) that are to be sent back. The aliases I use for the Firewalls tutorial auto-responder (tutorial-info@GreatCircle.COM) look like this: info: brent, mcb tutorial-info: info, "|/mycroft/brent/majordomo/wrapper auto-answer -c Info Tutorial-Info /mycroft/brent/firewalls/tutorial/info/generic.README /mycroft/brent/firewalls/tutorial/info/generic.INFO" tutorial-info-owner: brent This causes each person who sends a message to "tutorial-info" to get a response containing copies of the "generic.README" and "generic.INFO" files, with headers that look like: From: Tutorial-Info-Owner@GreatCircle.COM Cc: Info Subject: Your mail to Tutorial-Info@GreatCircle.COM To: ... Note: you'll probably have to hack this script a little to make it do what you want. It may have hard-coded paths and so forth in it; that's why it's not in the Majordomo release yet. Note also that the name of the alias needs to be on the command line (after the "-c Cc-address" argument, if any), so that the headers of the reply can be constructed properly. Good luck! -Brent #!/usr/local/bin/perl # $Source: /mycroft/brent/majordomo/RCS/auto-answer,v $ # $Revision: 1.1 $ # $Date: 1993/12/18 07:49:14 $ # $Author: brent $ # $State: Exp $ # # $Locker: brent $ # set our path explicitly $ENV{'PATH'} = "/bin:/usr/bin:/usr/ucb"; # What shall we use for temporary files? $tmp = "/tmp/majordomo.$$"; # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; if ($ARGV[0] eq "-C") { $cf = $ARGV[1]; shift(@ARGV); shift(@ARGV); } if (! -r $cf) { die("$cf not readable; stopped"); } eval(`cat $cf`); chdir($homedir) || die("Can't chdir(\"$homedir\"): $!"); unshift(@INC, $homedir); require "majordomo.pl"; require "getopts.pl"; &Getopts("c:") || die("Getopts(): $!"); &ParseMailHeader(STDIN, *hdrs); $reply_to = &RetMailAddr(*hdrs); $reply_to = join(", ", &ParseAddrs($reply_to)); $in_reply_to = $hdrs{"message-id"} . ", from " . $hdrs{"from"}; $user = shift(@ARGV); open(MAIL, "|/usr/lib/sendmail -t -f$user-Owner") || die("Can't connect to sendmail: $!"); print MAIL <<"EOM"; From: $user-Owner@$whereami To: $reply_to EOM if (defined($opt_c)) { print MAIL <<"EOM"; Cc: $opt_c EOM } print MAIL <<"EOM"; Subject: Your mail to $user@$whereami In-Reply-To: $in_reply_to Reply-To: $user-Owner@$whereami Sender: $user-Owner@$whereami This pre-recorded message is being sent in response to your recent email to $user@$whereami. EOM foreach $file (@ARGV) { open(FILE, $file) || die("open(FILE, \"$file\"): $!"); while () { print MAIL $_; } print MAIL "\f\n"; close(FILE); } close(MAIL); exit 0; From majordomo-users-owner Wed Oct 26 11:17:55 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA06979 for majordomo-users-outgoing; Wed, 26 Oct 1994 11:08:20 -0700 Received: from ncar.UCAR.EDU (ncar.ucar.edu [192.52.106.6]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA06974 for ; Wed, 26 Oct 1994 11:08:14 -0700 Message-Id: <199410261807.MAA12730@ncar.ucar.EDU> Received: by ncar.ucar.EDU (NCAR-local/ NCAR Central Post Office 03/11/93) id MAA12730; Wed, 26 Oct 1994 12:07:40 -0600 Subject: Re: Subject absent To: rmain@elpress.com (Rob Main) Date: Wed, 26 Oct 94 12:07:39 MDT Cc: Majordomo-Users@GreatCircle.COM In-Reply-To: <9410261956.AA0147@notes.elpress.com>; from "Rob Main" at Oct 26, 94 10:05 am From: woods@ncar.ucar.edu (Greg Woods) X-Mailer: ELM [version 2.3 PL11] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > "Approved: password" as the first line in the body. I also fill in the subject > on the subject line. > > When the message comes through, however, the subject is always -- No Subject > --. Any idea what I'm doing wrong or point me to the appropriate FAQ. Make sure you include the old message headers *after* your Approved: line. If the Approved: line is found in the BODY instead of the header, then majordomo discards all the headers from the message and expects to find the rest of the headers for the outgoing message in the body following the Approved: line. --Greg From majordomo-users-owner Wed Oct 26 11:47:55 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA06985 for majordomo-users-outgoing; Wed, 26 Oct 1994 11:09:32 -0700 Received: from advantage.Advantage.com (gateway.advantage.com [134.87.158.254]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id LAA06971 for ; Wed, 26 Oct 1994 11:07:31 -0700 Received: from bugs_bunny by advantage.Advantage.com (NX5.67c/NX3.0M) id AA12999; Wed, 26 Oct 94 11:05:43 -0700 From: Paolo Bertoia Message-Id: <9410261805.AA12999@advantage.Advantage.com> Received: by bugs_bunny.Advantage.com (NX5.67c/NX3.0X) id AA08047; Wed, 26 Oct 94 11:04:43 -0700 Date: Wed, 26 Oct 94 11:04:43 -0700 Received: by NeXT.Mailer (1.87.1.RR) Received: by NeXT Mailer (1.87.1.RR) To: majordomo-users@GreatCircle.COM Subject: Configuring Reply_To with Majordomo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello: I have just recently set-up Majordomo s/w to run some lists and unfortunately have been unable to discover which files to edit to reflect the following info: Precedence: bulk Reply-To: listName@DomainName Sender: listName@DomainName Comments: This is a list for ... I have read the doucmentation supplied with Majordomo 1.92 as well as the FAQs for the past few months and have discovered what needs to be changed in so far as sender and reply_to are concerned, but I have not been able to find out where changes need to be made. I have carefully read the comments in the listname.config, resend, majordomo.pl and majordomo.cf files but don't see any obvious place where the flags indicated in the documentation should be set. If someone out there could point me in the right direction with an example I would greatly appreciate it. Thanks. Paolo Bertoia __________________________________________________________________________ Paolo Bertoia | Advantage Computers Ltd. | "Respect Mother Earth and her healing Ph: +1.604.231.5700 | ways or trade away our children's days." Fx: +1.604.244.0437 | - Neil Young - From majordomo-users-owner Wed Oct 26 12:48:28 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA07833 for majordomo-users-outgoing; Wed, 26 Oct 1994 12:45:42 -0700 Received: from bosnia.pop.psu.edu (root@bosnia.pop.psu.edu [146.186.111.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA07825 for ; Wed, 26 Oct 1994 12:44:36 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id PAA08748; Wed, 26 Oct 1994 15:33:25 -0400 Message-Id: <199410261933.PAA08748@bosnia.pop.psu.edu> To: Paolo Bertoia cc: majordomo-users@GreatCircle.COM Subject: Re: Configuring Reply_To with Majordomo In-reply-to: Your message of "Wed, 26 Oct 1994 11:04:43 PDT." <9410261805.AA12999@advantage.Advantage.com> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Wed, 26 Oct 1994 15:33:24 -0400 From: David Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <9410261805.AA12999@advantage.Advantage.com>, Paolo Bertoia writes: >Hello: > >I have just recently set-up Majordomo s/w to run some lists and >unfortunately have been unable to discover which files to edit to reflect >the following info: > >Precedence: bulk >Reply-To: listName@DomainName >Sender: listName@DomainName >Comments: This is a list for ... Closer RTFM'ing of the .config file reveals Precedence: is set by the "precedence" keyword Reply-To: is set by the "reply_to" keyword Sender: is set by the "sender" keyword Comments: can't be set, unless you hack resend. You either edit the .config file directly, or do a "config " edit the file, and do a "writeconfig " --Dave From majordomo-users-owner Wed Oct 26 17:22:50 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA10437 for majordomo-users-outgoing; Wed, 26 Oct 1994 17:06:19 -0700 Received: from magellan.iquest.com (root@magellan.iquest.com [199.170.120.21]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id RAA10432 for ; Wed, 26 Oct 1994 17:06:07 -0700 Received: (from dougal@localhost) by magellan.iquest.com (8.6.9/8.6.9) id TAA21043; Wed, 26 Oct 1994 19:01:50 -0500 Date: Wed, 26 Oct 1994 19:01:50 +0100 From: Dougal Campbell Subject: Re: HELP PLEASE! "Info" alias autoresponder problems (2nd tr To: majordomo-users@greatcircle.com In-Reply-To: <9409267832.AA783215014@multi.iquest.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Just an aside about the $SENDER stuff. We use this method, and it works fine. Things to keep in mind: 1) We have it in a .forward file 2) we use smail instead of sendmail. Here's an exerpt from the smail(5) man page about its "Sendmail-compatible forward files": ----------------------------------------------------------------------- A useful forward file is: # I am on vacation, save away my mail, but tell people # I won't be back for a while hustead, "|mailx -s 'Yep, gone fishing!' \"$SENDER\" < $HOME/.fish" Which will save to Ted Hustead's mailbox file and will also execute the following shell command: mailx -s 'Yep, gone fishing!' "$SENDER" < $HOME/.fish where the shell variables $HOME and $SENDER are available from the environment as the user's home directory and the sender address, respectively. ---------------------------------------------------------------------- It also mentions that several environment variables (including SENDER) are available when using the pipe driver. Dougal Campbell | Check out the interQuest home page: System Administrator | http://www.iquest.com/ dougal@iquest.com | interQuest: We can hook you up! From majordomo-users-owner Thu Oct 27 00:48:17 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id AAA12637 for majordomo-users-outgoing; Thu, 27 Oct 1994 00:24:12 -0700 Received: from spot.Colorado.EDU (root@spot.Colorado.EDU [128.138.129.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA11421 for ; Wed, 26 Oct 1994 19:25:10 -0700 Received: from spot.Colorado.EDU (callen@localhost [127.0.0.1]) by spot.Colorado.EDU (8.6.9/8.6.9/CNS-3.5) with ESMTP id UAA13586 for ; Wed, 26 Oct 1994 20:24:18 -0600 Message-Id: <199410270224.UAA13586@spot.Colorado.EDU> To: majordomo-users@greatcircle.com Subject: bug? Date: Wed, 26 Oct 1994 20:24:15 -0600 From: Colin Allen Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk First, my apologies for the subscribe request sent to this address by mistake. As the "owner" of a majordomo list I recently ran into the following problem. Someone subscribed to the list with a bad address, bali!cac, but when I tried to force an unsubscribe, majordomo replied with: ** unsubscribe: 'bali!cac' is not a member of list 'team-internet'. Even thought the address was clearly there in the list returned by "who". Is this a known problem? Thanks. -- Colin Allen, Asst. Prof \0/ 1994-95 address (Aug. 1 on) Philosophy, Texas A&M Univ. _@_ EPO Biology, Univ. of Colorado College Station TX 77843-4237 X Boulder CO 80309-0334 _______(409)845-5660_________ ^|^ _________(303)546-6552________ From majordomo-users-owner Thu Oct 27 00:53:59 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id AAA12601 for majordomo-users-outgoing; Thu, 27 Oct 1994 00:22:42 -0700 Received: from infoexp.express.com (infoexp.express.com [199.74.247.3]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA08282 for ; Wed, 26 Oct 1994 13:40:39 -0700 Received: from alto.express.com (alto.express.com [199.74.248.4]) by infoexp.express.com (8.6.8/8.6.6) with ESMTP id NAA17851 for ; Wed, 26 Oct 1994 13:40:08 -0700 Received: from [199.74.248.5] (snoopy.express.com [199.74.248.5]) by alto.express.com (8.6.8/8.6.6) with SMTP id NAA12863; Wed, 26 Oct 1994 13:39:10 -0700 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Oct 1994 13:41:14 -0800 To: philip@express.com From: pzee@express.com (Philip Zee) Subject: Re: HELP PLEASE! "Info" alias autoresponder problems (2nd try) Cc: Majordomo-Users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk don@talarian.com (Don Gray) writes: # I would sure appreciate some help with the following problem... I don't # think it should be very hard since it seems that everyone on the 'Net is # doing it. # # I am trying to set up the "info" alias on my Unix (SunOS) machine so it # automatically returns the contents of a text file to the sender. # # When I send a message to "info", the Sendmail command that is listed in the # /etc/aliases file is executed, which looks like this: # # >info-owner: don # ># the following "sendmail" command returns the text file # ># "/home/mdomo/lists/info.info" to the original sender # >info: "|/usr/lib/sendmail -f info-owner $SENDER < /home/mdomo/lists/info.info" # ^^^^^^^^ ^^^^^^^ # # What happens at this point (according to the verbose output from sendmail) # is that the sender's actual address does not replace $SENDER, so it # produces this error: # # > ----- Transcript of session follows ----- # >501 info-owner... Recipient names must be specified # # I have been told by several people on the 'Net that they use this Sendmail # command (just as I have it here) very successfully. I am using Sendmail V8 # (just like them). # # However, I haven't been able to find *any* references to $SENDER in the # O'Reilly Sendmail documentation book. I am now thinking that perhaps # $SENDER is some sort of add-on script or macro that may not be defined on # my system. Is this possible? If so, can someone send it to me or tell me # where I can get it? If this isn't the problem, does anyone have any # ideas/suggestions? I have never heard of this syntax in any version of Sendmail. # Is there a more efficient way of achieving my goal while still using # Majordomo? (someone said that Procmail does this, but I think Procmail is # a Majordomo competitor and I'd rather not switch since I know and like # Majordomo, and since I finally got it installed successfully...). I use a hacked-up version of the "request-answer" script, which I call "auto-answer", included below. The command line arguments are "-c Cc-address From file [file ...]" I.e., you give a "-c Cc-address" argument to add a "Cc: Cc-address" line to the outgoing mail, you specify who the outgoing mail should appear to be from with the "From" argument, and you specify the file (or files) that are to be sent back. The aliases I use for the Firewalls tutorial auto-responder (tutorial-info@GreatCircle.COM) look like this: info: brent, mcb tutorial-info: info, "|/mycroft/brent/majordomo/wrapper auto-answer -c Info Tutorial-Info /mycroft/brent/firewalls/tutorial/info/generic.README /mycroft/brent/firewalls/tutorial/info/generic.INFO" tutorial-info-owner: brent This causes each person who sends a message to "tutorial-info" to get a response containing copies of the "generic.README" and "generic.INFO" files, with headers that look like: From: Tutorial-Info-Owner@GreatCircle.COM Cc: Info Subject: Your mail to Tutorial-Info@GreatCircle.COM To: ... Note: you'll probably have to hack this script a little to make it do what you want. It may have hard-coded paths and so forth in it; that's why it's not in the Majordomo release yet. Note also that the name of the alias needs to be on the command line (after the "-c Cc-address" argument, if any), so that the headers of the reply can be constructed properly. Good luck! -Brent #!/usr/local/bin/perl # $Source: /mycroft/brent/majordomo/RCS/auto-answer,v $ # $Revision: 1.1 $ # $Date: 1993/12/18 07:49:14 $ # $Author: brent $ # $State: Exp $ # # $Locker: brent $ # set our path explicitly $ENV{'PATH'} = "/bin:/usr/bin:/usr/ucb"; # What shall we use for temporary files? $tmp = "/tmp/majordomo.$$"; # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; if ($ARGV[0] eq "-C") { $cf = $ARGV[1]; shift(@ARGV); shift(@ARGV); } if (! -r $cf) { die("$cf not readable; stopped"); } eval(`cat $cf`); chdir($homedir) || die("Can't chdir(\"$homedir\"): $!"); unshift(@INC, $homedir); require "majordomo.pl"; require "getopts.pl"; &Getopts("c:") || die("Getopts(): $!"); &ParseMailHeader(STDIN, *hdrs); $reply_to = &RetMailAddr(*hdrs); $reply_to = join(", ", &ParseAddrs($reply_to)); $in_reply_to = $hdrs{"message-id"} . ", from " . $hdrs{"from"}; $user = shift(@ARGV); open(MAIL, "|/usr/lib/sendmail -t -f$user-Owner") || die("Can't connect to sendmail: $!"); print MAIL <<"EOM"; From: $user-Owner@$whereami To: $reply_to EOM if (defined($opt_c)) { print MAIL <<"EOM"; Cc: $opt_c EOM } print MAIL <<"EOM"; Subject: Your mail to $user@$whereami In-Reply-To: $in_reply_to Reply-To: $user-Owner@$whereami Sender: $user-Owner@$whereami This pre-recorded message is being sent in response to your recent email to $user@$whereami. EOM foreach $file (@ARGV) { open(FILE, $file) || die("open(FILE, \"$file\"): $!"); while () { print MAIL $_; } print MAIL "\f\n"; close(FILE); } close(MAIL); exit 0; ______________________________________________________________________ Philip J. Zee / / / Information Express / / / 3250 Ash St. o o o / / / Palo Alto, CA 94306 o o / o / / Main: (415) 494-8787 DID: (415) 812-3530 o /o /o / Internet: pzee@express.com / / / ______________________________________________________________________ From majordomo-users-owner Thu Oct 27 06:47:14 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA15575 for majordomo-users-outgoing; Thu, 27 Oct 1994 06:42:01 -0700 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id GAA15570 for ; Thu, 27 Oct 1994 06:41:56 -0700 Received: from relay2.macom.com by relay2.UU.NET with SMTP id QQxnkw05555; Thu, 27 Oct 1994 09:41:13 -0400 Message-Id: Received: from technet.macom.com by relay2.macom.com with SMTP (1.37.109.4/16.2) id AA18489; Thu, 27 Oct 94 09:41:11 -0400 Received: by technet.macom.com (1.37.109.8/16.2) id AA10899; Thu, 27 Oct 1994 09:41:09 -0400 From: Matthew Cilento Subject: automatically generating digests ?'s To: majordomo-users@greatcircle.com Date: Thu, 27 Oct 94 9:41:08 EDT Reply-To: mtc@technet.macom.com Mailer: Elm [revision: 70.85] Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello, I've recently installed and setup majordomo-1.92 and have a few lists running (along with a cooresponding list-digests). My question is: Is there anyway that the digest can be processed automagically every week or month rather than the manual "mkdigest" message to majordomo each time one wants a digest generated? I gather I can setup a cron to do this but I was wondering if there is another way... I didn't find the answer among the copious DOCs included with the distribution. Thanks for your time, Matt mtc@technet.macom.com -- From majordomo-users-owner Thu Oct 27 15:17:00 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA18430 for majordomo-users-outgoing; Thu, 27 Oct 1994 14:56:29 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id OAA18425 for ; Thu, 27 Oct 1994 14:56:20 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA24716 (5.65c/IDA-1.4.4 for ); Thu, 27 Oct 1994 17:54:38 -0400 Message-Id: <199410272154.AA24716@cs.umb.edu> To: Colin Allen Cc: majordomo-users@greatcircle.com Subject: Re: bug? In-Reply-To: Your message of "Wed, 26 Oct 1994 20:24:15 MDT." <199410270224.UAA13586@spot.Colorado.EDU> Date: Thu, 27 Oct 1994 17:54:13 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message <199410270224.UAA13586@spot.Colorado.EDU>, Colin Allen writes: >As the "owner" of a majordomo list I recently ran into the following >problem. Someone subscribed to the list with a bad address, bali!cac, >but when I tried to force an unsubscribe, majordomo replied with: ** >unsubscribe: 'bali!cac' is not a member of list 'team-internet'. Even >thought the address was clearly there in the list returned by "who". >Is this a known problem? Yes. Its the same problem that was experienced a few days ago when somebody had a list of lists. It is basically that addr_match doesn't work right if there is no @ sign in the address. The patch has been put on the list a number of times. Check the archives for it, or perhaps somebody has a copy of the patch and can forward it. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Thu Oct 27 17:17:52 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id QAA19374 for majordomo-users-outgoing; Thu, 27 Oct 1994 16:48:07 -0700 Received: from noao.edu (noao.edu [140.252.1.54]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id QAA19367 for ; Thu, 27 Oct 1994 16:47:54 -0700 From: swampler@noao.edu Received: from orpheus.gemini.edu by noao.edu (4.1/SAG-Noao.G96) id AA29409; Thu, 27 Oct 94 16:47:06 MST; for Majordomo-Users@GreatCircle.com Received: by orpheus.gemini.edu (5.0/SMI-SVR4-SAG03X) id AA01910; Thu, 27 Oct 1994 16:47:01 +0700 Message-Id: <9410272347.AA01910@orpheus.gemini.edu> Date: Thu, 27 Oct 1994 16:47:00 GMT+447 X-Mailer: Mail User's Shell (7.2.3 5/22/91) To: Majordomo-Users@GreatCircle.com Subject: Replies to replies? Content-Length: 616 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk If I reply to a message in one of my mailing lists, my reply goes to all the subscribers (which is the behavior I want). However, replies to my reply (got that?) go only to me. I assume that the mailers are not 'extending' the "Reply-To:" header to my reply (being replied to). I'd like replies to replies to go to all subscribers (ad nauseum, of course). Can majordomo be configured to do this? Thanks for any info! -- Steve Wampler - swampler@gemini.edu [Gemini 8m Telescopes Project (under AURA)] -- The Gods that were smiling when you were born are laughing now. -- found in a fortune cookie From majordomo-users-owner Thu Oct 27 17:47:01 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA19974 for majordomo-users-outgoing; Thu, 27 Oct 1994 17:44:49 -0700 Received: from mail.barrnet.net (MAIL.BARRNET.NET [131.119.245.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id RAA19967 for ; Thu, 27 Oct 1994 17:44:44 -0700 Received: from nueva.pvt.k12.ca.us by mail.barrnet.net (5.67/1.37) id AA13946; Thu, 27 Oct 94 17:43:44 -0700 Received: by nueva1.nueva.pvt.k12.ca.us (5.67b/15.5+ECS 3.3+Nueva 0.9) id AA04972; Thu, 27 Oct 1994 17:43:39 -0700 Date: Thu, 27 Oct 1994 17:43:34 -0700 (PDT) From: Alexei Kosut To: majordomo-users@greatcircle.com Subject: question about sendmail Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hi: This doesn't directly have to do with majordomo, but has to do with sendmail as it related to... anyhow, let me explain. I'm runing Majordomo 1.92 on a Linux 1.0.9 box with sendmail (this is the version number it affixes to mail headers) 5.67b/15.5+ECS 3.3+Nueva 0.9. Anyhow, majordomo works fine, but what I'd like to do is possibly create a CNAME or MX record from lists.nueva.pvt.k12.ca.us (nueva... is the domain) to the mail handling machine. My question is whether it is possible to use a seperate aliases file for that one hostname (lists.nueva.pvt.k12.ca.us) than the standard aliases file, and if so, how would I go about this? Sorry if I seem incoherent, but I would appreciate a response. Thanks in advance. += Alexei Kosut == Pass the Prozac, please =+ | __ ___ ___ __ ___ __ // _____________________________________| | / / / _// _// / / _// | // Director of Miscellania | | / /_ / _ / _// /_ / _ / / // The DALnet IRC Network | | /___//__//_/ /___//__//_/_| // /server irc.ucdavis.edu 6666 | += http://www.nueva.pvt.k12.ca.us/~akosut/ ==============================+ From majordomo-users-owner Thu Oct 27 18:19:25 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id SAA20173 for majordomo-users-outgoing; Thu, 27 Oct 1994 18:07:53 -0700 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id SAA20167 for ; Thu, 27 Oct 1994 18:07:44 -0700 Received: from glock.ramp.com by relay2.UU.NET with ESMTP id QQxnmq25514; Thu, 27 Oct 1994 21:06:59 -0400 Received: (from sharokh@localhost) by glock.ramp.com (8.6.9/8.6.6) id BAA10536; Fri, 28 Oct 1994 01:06:24 GMT Date: Thu, 27 Oct 1994 18:06:24 -0700 (MST) From: Sharokh Subject: request messages To: majordomo-users@GreatCircle.COM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Hello, I was wondering if list-owner can change/edit any request messages when a subscriber sends to list-request. For example, the Welcome to mailing list when they are approved for subscribing, help files, errors, majordomo commands, etc. Thanks From majordomo-users-owner Thu Oct 27 20:47:01 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id UAA21020 for majordomo-users-outgoing; Thu, 27 Oct 1994 20:28:18 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id UAA21015 for ; Thu, 27 Oct 1994 20:28:13 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA11761 (5.65c/IDA-1.4.4 for ); Thu, 27 Oct 1994 23:26:41 -0400 Message-Id: <199410280326.AA11761@cs.umb.edu> To: Sharokh Cc: majordomo-users@greatcircle.com Subject: Re: request messages In-Reply-To: Your message of "Thu, 27 Oct 1994 18:06:24 PDT." Date: Thu, 27 Oct 1994 23:26:16 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , Sharokh writes: >I was wondering if list-owner can change/edit any request messages >when a subscriber sends to list-request. For example, the Welcome >to mailing list when they are approved for subscribing, help files, errors, >majordomo commands, etc. The info files can be changed, and if I get the patch together, there maybe a blurb that can be included only on subscriptions, but thats it. Help text etc isn't (currently) changeable. Programmable help text etc won't be in 1.93 either. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Fri Oct 28 12:47:40 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA25946 for majordomo-users-outgoing; Fri, 28 Oct 1994 12:30:44 -0700 Received: from ceres.rdc.puc-rio.br (ceres.rdc.puc-rio.br [139.82.34.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id MAA25941 for ; Fri, 28 Oct 1994 12:30:35 -0700 Received: by ceres.rdc.puc-rio.br (AIX 3.2/UCB 5.64/4.03) id AA15713; Fri, 28 Oct 1994 17:28:28 -0200 From: poyart@ceres.rdc.puc-rio.br (Eduardo Poyart) Message-Id: <9410281928.AA15713@ceres.rdc.puc-rio.br> Subject: That unlink bug To: majordomo-users@greatcircle.com Date: Fri, 28 Oct 1994 17:28:27 +22295807 (BDB) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 181 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Would anyone please post again that fix for the unlink bug, which left many resend.* files in the /tmp directory? They are starting to annoy me. Thanks in advance! Eduardo Poyart From majordomo-users-owner Fri Oct 28 13:55:23 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA26275 for majordomo-users-outgoing; Fri, 28 Oct 1994 13:37:34 -0700 Received: from ftp.std.com (ftp.std.com [192.74.137.7]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA26270 for ; Fri, 28 Oct 1994 13:37:16 -0700 Received: from world.std.com by ftp.std.com (8.6.8.1/Spike-8-1.0) id QAA09538; Fri, 28 Oct 1994 16:34:30 -0400 Received: by world.std.com (5.65c/Spike-2.0) id AA19344; Fri, 28 Oct 1994 16:34:33 -0400 Message-Id: <199410282034.AA19344@world.std.com> To: poyart@ceres.rdc.puc-rio.br (Eduardo Poyart) Cc: majordomo-users@greatcircle.com Subject: Re: That unlink bug In-Reply-To: Your message of "Fri, 28 Oct 1994 17:28:27." <9410281928.AA15713@ceres.rdc.puc-rio.br> Date: Fri, 28 Oct 1994 16:34:32 -0400 From: Elizabeth Lear Newman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk [From John Rouillard] This is a known bug in Majordomo 1.92. There was a typo on line 347. Make this change to resend: 347c347 < unlink("/tmp/resend.$$.*"); --- > unlink(); ...eliz From majordomo-users-owner Fri Oct 28 14:47:31 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA26830 for majordomo-users-outgoing; Fri, 28 Oct 1994 14:33:03 -0700 Received: from ftp.std.com (ftp.std.com [192.74.137.7]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id IAA15985 for ; Thu, 27 Oct 1994 08:17:23 -0700 Received: from world.std.com by ftp.std.com (8.6.8.1/Spike-8-1.0) id LAA00428; Thu, 27 Oct 1994 11:16:54 -0400 Received: by world.std.com (5.65c/Spike-2.0) id AA14509; Thu, 27 Oct 1994 11:17:03 -0400 Message-Id: <199410271517.AA14509@world.std.com> To: majordomo-users@greatcircle.com Subject: any way to restrict 'who'? Date: Thu, 27 Oct 1994 11:17:02 -0400 From: Elizabeth Lear Newman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Is there *any* way to set either majordomo 1.62 or 1.92 so that even the people on the lists can't get the list of members? This is really important, and I need an answer ASAP - any help is appreciated! ...eliz From majordomo-users-owner Fri Oct 28 15:41:20 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA27214 for majordomo-users-outgoing; Fri, 28 Oct 1994 14:56:27 -0700 Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA17860 for ; Thu, 27 Oct 1994 13:15:21 -0700 Received: from glock.ramp.com by relay1.UU.NET with ESMTP id QQxnlw21572; Thu, 27 Oct 1994 16:14:36 -0400 Received: (from sharokh@localhost) by glock.ramp.com (8.6.9/8.6.6) id UAA00330; Thu, 27 Oct 1994 20:13:59 GMT Date: Thu, 27 Oct 1994 13:13:59 -0700 (MST) From: Sharokh Subject: Help with list setup To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I got few small problems and I was wondering if someone out there can help me out. Once you create a list, is there way the list-owner can change the configuration of any list-request messages to its subscribers? Such as Welcome list messages, the help file, successed responses, error responses, etc. Another question is that if a subscriber or list-owner sends a request to list-request, you get your request message back fromm Majordomo@address than mylist-request@address. Is there anyway to change this that any request comes from mylist-request than Majordomo@address. What I like to do is that I dont want my subscribers have anything to do with Majordomo@address so that they won't be confused. If I send a request to mylist-request and get my request message from Majordomo@address, why is it necessary to have mylist-request@address for? It's useless. Thanx sharokh From majordomo-users-owner Fri Oct 28 15:50:12 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA27178 for majordomo-users-outgoing; Fri, 28 Oct 1994 14:54:54 -0700 Received: from sigma.itu.ch (sigma.itu.ch [156.106.128.30]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id JAA16695 for ; Thu, 27 Oct 1994 09:57:54 -0700 Received: from MR.ITU.CH by ITU.CH (PMDF V4.3-7 #4298) id <01HIS36IKETC9X57PD@ITU.CH>; Thu, 27 Oct 1994 17:58:30 CET Received: with PMDF-MR; Thu, 27 Oct 1994 16:24:48 CET MR-Received: by mta TIES.MUAS; Relayed; Thu, 27 Oct 1994 16:24:48 +0100 MR-Received: by mta TAU; Relayed; Thu, 27 Oct 1994 16:25:10 +0100 Disclose-recipients: prohibited Date: Thu, 27 Oct 1994 16:24:48 +0100 (CET) From: JARLE MARTINSEN +41 22 730 5949 Subject: help with undelivered mails To: Majordomo-Users Message-id: <1148241727101994/A32434/TAU/118ADC582A00*@MHS> X-Envelope-to: Majordomo-Users@GreatCircle.COM Autoforwarded: false MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Importance: normal Priority: urgent Sensitivity: Company-Confidential UA-content-id: 118ADC582A00 X400-MTS-identifier: [;1148241727101994/A32434/TAU] Hop-count: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Help - I have a mailing list setup fairly plain, sort of a true copy of sample. I just experienced 1 undelivered mail bouncing between the mailing list and the non-existing address. I.e. the non-delivery message was sent back to mailing list, forwarded to all subscribers on the list, failing again (of course),...etc. So I've probably missed something. Any pointers to what I've done wrong is appriciated. Rgrds, /jarle Jarle Martinsen International Telecomunnication Union (ITU) Place des nations CH-1211 Geneva 20 Switzerland Internet: martinsen@itu.ch X.400: S=martinsen; P=itu; A=arcom; C=ch Voice: +41 22 730 5949 Fax: +41 22 730 5337 From majordomo-users-owner Fri Oct 28 16:09:03 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id PAA27435 for majordomo-users-outgoing; Fri, 28 Oct 1994 15:01:50 -0700 Received: from sigma.itu.ch (sigma.itu.ch [156.106.128.30]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id AAA21594 for ; Fri, 28 Oct 1994 00:03:11 -0700 Received: from MR.ITU.CH by ITU.CH (PMDF V4.3-7 #4298) id <01HISWPM6YBK9X4V8I@ITU.CH>; Fri, 28 Oct 1994 08:03:44 CET Received: with PMDF-MR; Fri, 28 Oct 1994 06:53:27 CET MR-Received: by mta TIES.MUAS; Relayed; Fri, 28 Oct 1994 06:53:27 +0100 MR-Received: by mta TAU; Relayed; Fri, 28 Oct 1994 06:53:33 +0100 Disclose-recipients: prohibited Date: Fri, 28 Oct 1994 06:53:27 +0100 (CET) From: JARLE MARTINSEN +41 22 730 5949 Subject: help with undelivered mail To: Majordomo-Users Message-id: <5927530728101994/A35044/TAU/118AE1F51A00*@MHS> X-Envelope-to: Majordomo-Users@GreatCircle.COM Autoforwarded: false MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Importance: normal Priority: urgent Sensitivity: Company-Confidential UA-content-id: 118AE1F51A00 X400-MTS-identifier: [;5927530728101994/A35044/TAU] Hop-count: 1 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Help - I have a mailing list setup fairly plain, sort of a true copy of sample. I just experienced 1 undelivered mail bouncing between the mailing list and the non-existing address. I.e. the non-delivery message was sent back to the mailing list, forwarded to all subscribers on the list, failing again (of course),...etc. So I've probably missed something. Any pointers to what I've done wrong is appriciated. Rgrds, /jarle Jarle Martinsen International Telecomunnication Union (ITU) Place des nations CH-1211 Geneva 20 Switzerland Internet: martinsen@itu.ch X.400: S=martinsen; P=itu; A=arcom; C=ch Voice: +41 22 730 5949 Fax: +41 22 730 5337 From majordomo-users-owner Fri Oct 28 16:15:41 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA27293 for majordomo-users-outgoing; Fri, 28 Oct 1994 14:58:23 -0700 Received: from wubios (wubios.wustl.edu [128.252.117.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id NAA17968 for ; Thu, 27 Oct 1994 13:29:52 -0700 Received: by wubios.wustl.edu (4.1/SMI-4.1) id AA22571; Thu, 27 Oct 94 15:05:57 CDT From: erich@wubios (Erich Schraer) Message-Id: <9410272005.AA22571@wubios.wustl.edu> Subject: Errors-To: problem To: Majordomo-Users@GreatCircle.COM Date: Thu, 27 Oct 1994 15:05:56 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 1430 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I don't know if anyone can help me with this problem, but I con't figure it out. We're using Majordomo 1.92 with SunOS 4.1.2 using the sendmail.mx from the 100377-15 patch. It often seems to happen that when a message is sent to one of the mailing lists an "Errors-To:" header gets added to the message. When it does it gets set to the expansion of the list-owner alias: Errors-To: phil, kathy Then when the message is sent it doesn't get fully qualified and several hosts will bounce it back with messages like: <<< 554 phil@wubios, kathy@wubios... Never heard of wubios in domain ohsu . EDU The list is being called with an alias like this: list: "|/usr/local/majordomo/wrapper resend -l list -h wubios.wustl.edu list-outgoing The list.config has this line: resend_host = wubios.wustl.edu The problem only seems to happen when Majordomo sends a message (and not always then). If a message is sent directly to or through a problem site everything comes through fully qualified. Does anyone have any idea what is going on, or have any pointers to route me in the right direction? Thanks. --Erich -- / Erich Schraer St. Louis, MO 63110 \ / Division of Biostatistics erich@wubios.wustl.edu \ \ Washington University School of Medicine Voice: (314)362-3681 / \ 660 S. Euclid Ave., Box 8067 Fax: (314)362-2693 / From majordomo-users-owner Fri Oct 28 16:17:29 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA27116 for majordomo-users-outgoing; Fri, 28 Oct 1994 14:53:46 -0700 Received: from mv.mv.com (mv.MV.COM [192.80.84.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id OAA27111 for ; Fri, 28 Oct 1994 14:53:40 -0700 Received: by mv.mv.com (8.6.9/mv(b)/mem-940616) id RAA24519; Fri, 28 Oct 1994 17:14:37 -0400 Received: from magpie.mv.com by summa4.mv.COM (4.1/SMI-4.1) id AA07034; Fri, 28 Oct 94 17:03:00 EDT Date: Fri, 28 Oct 94 17:03:00 EDT From: lrc@summa4.MV.COM (Lawrence R. Cook) Message-Id: <9410282103.AA07034@summa4.mv.COM> To: poyart@ceres.rdc.puc-rio.br Subject: Re: That unlink bug Cc: majordomo-users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk > Would anyone please post again that fix for the unlink bug, which left > many resend.* files in the /tmp directory? They are starting to annoy me. > > Thanks in advance! > Eduardo Poyart In resend, change line 347 to be the same as line 335: 347c347 < unlink("/tmp/resend.$$.*"); --- > unlink(); --------------------------------------------------------------------- Larry Cook, Senior Software Engineer Email: lrc@summa4.mv.com Summa Four, Inc. Phone: (603) 625-4050 x2566 25 Sundial Ave, Manchester, NH 03103-7251 Fax : (603) 668-4491 From majordomo-users-owner Fri Oct 28 17:17:21 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id QAA29167 for majordomo-users-outgoing; Fri, 28 Oct 1994 16:51:48 -0700 Received: from earth.willamette.edu (root@earth.willamette.edu [158.104.100.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id QAA29159 for ; Fri, 28 Oct 1994 16:51:32 -0700 Received: from jupiter (mrussell@jupiter.willamette.edu [158.104.1.1]) by earth.willamette.edu (8.6.8.1/8.6.4) with SMTP id QAA04557 for ; Fri, 28 Oct 1994 16:50:16 -0700 Date: Fri, 28 Oct 1994 16:50:15 -0700 (PDT) From: Marc Subject: new-list script troubles To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk When I run the new-list script, I get the following error message: Can't locate majordomo.pl in @INC at ./new-list line 32. majordomo.pl is located in the majordomo home directory, and I don't know perl at all. Can someone help? marc mrussell@willamette.edu InfoX: sysadmin@olympus.dis.wa.gov ---------------------------------------------------------------------------- "A toast, before we go into battle -- true love. In whatever shape or form it may come, may we all in our dotage be proud to say, 'We were adored once, too.'" -Four Weddings and a Funeral ---------------------------------------------------------------------------- From majordomo-users-owner Fri Oct 28 18:17:02 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id SAA29748 for majordomo-users-outgoing; Fri, 28 Oct 1994 18:09:25 -0700 Received: from netcomsv.netcom.com (uucp2-b.netcom.com [163.179.3.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id SAA29743 for ; Fri, 28 Oct 1994 18:08:58 -0700 Received: from localhost by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id RAA10214; Fri, 28 Oct 1994 17:29:56 -0700 Received: from [192.9.200.100] (don_mac [192.9.200.100]) by ncc1701a.talarian.com (8.6.9/8.6.9) with SMTP id QAA24876; Fri, 28 Oct 1994 16:02:43 -0700 X-Sender: don@ncc1701a Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 28 Oct 1994 16:02:44 -0800 To: nelson@santafe.edu (Nelson Minar) From: don@talarian.com (Don Gray) Subject: Re: Hacked request-answer autoresponder (was: request-answer) Cc: Majordomo-Users@GreatCircle.com Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >what is this "hacked version" of request-answer? The one that comes >with 1.92 just spits back an error message - do you have one that >actually functions? Brent Chapman writes: I use a hacked-up version of the "request-answer" script, which I call "auto-answer", included below. The command line arguments are "-c Cc-address From file [file ...]" I.e., you give a "-c Cc-address" argument to add a "Cc: Cc-address" line to the outgoing mail, you specify who the outgoing mail should appear to be from with the "From" argument, and you specify the file (or files) that are to be sent back. The aliases I use for the Firewalls tutorial auto-responder (tutorial-info@GreatCircle.COM) look like this: info: brent, mcb tutorial-info: info, "|/mycroft/brent/majordomo/wrapper auto-answer -c Info Tutorial-Info /mycroft/brent/firewalls/tutorial/info/generic.README /mycroft/brent/firewalls/tutorial/info/generic.INFO" tutorial-info-owner: brent This causes each person who sends a message to "tutorial-info" to get a response containing copies of the "generic.README" and "generic.INFO" files, with headers that look like: From: Tutorial-Info-Owner@GreatCircle.COM Cc: Info Subject: Your mail to Tutorial-Info@GreatCircle.COM To: ... Note: you'll probably have to hack this script a little to make it do what you want. It may have hard-coded paths and so forth in it; that's why it's not in the Majordomo release yet. Note also that the name of the alias needs to be on the command line (after the "-c Cc-address" argument, if any), so that the headers of the reply can be constructed properly. Good luck! -Brent #!/usr/local/bin/perl # $Source: /mycroft/brent/majordomo/RCS/auto-answer,v $ # $Revision: 1.1 $ # $Date: 1993/12/18 07:49:14 $ # $Author: brent $ # $State: Exp $ # # $Locker: brent $ # set our path explicitly $ENV{'PATH'} = "/bin:/usr/bin:/usr/ucb"; # What shall we use for temporary files? $tmp = "/tmp/majordomo.$$"; # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; if ($ARGV[0] eq "-C") { $cf = $ARGV[1]; shift(@ARGV); shift(@ARGV); } if (! -r $cf) { die("$cf not readable; stopped"); } eval(`cat $cf`); chdir($homedir) || die("Can't chdir(\"$homedir\"): $!"); unshift(@INC, $homedir); require "majordomo.pl"; require "getopts.pl"; &Getopts("c:") || die("Getopts(): $!"); &ParseMailHeader(STDIN, *hdrs); $reply_to = &RetMailAddr(*hdrs); $reply_to = join(", ", &ParseAddrs($reply_to)); $in_reply_to = $hdrs{"message-id"} . ", from " . $hdrs{"from"}; $user = shift(@ARGV); open(MAIL, "|/usr/lib/sendmail -t -f$user-Owner") || die("Can't connect to sendmail: $!"); print MAIL <<"EOM"; From: $user-Owner@$whereami To: $reply_to EOM if (defined($opt_c)) { print MAIL <<"EOM"; Cc: $opt_c EOM } print MAIL <<"EOM"; Subject: Your mail to $user@$whereami In-Reply-To: $in_reply_to Reply-To: $user-Owner@$whereami Sender: $user-Owner@$whereami This pre-recorded message is being sent in response to your recent email to $user@$whereami. EOM foreach $file (@ARGV) { open(FILE, $file) || die("open(FILE, \"$file\"): $!"); while () { print MAIL $_; } print MAIL "\f\n"; close(FILE); } close(MAIL); exit 0; From majordomo-users-owner Fri Oct 28 19:17:02 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA29978 for majordomo-users-outgoing; Fri, 28 Oct 1994 19:09:43 -0700 Received: from sfi.santafe.edu (sfi.santafe.edu [192.12.12.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id TAA29973 for ; Fri, 28 Oct 1994 19:09:38 -0700 Received: from grasshopper.santafe.edu by sfi.santafe.edu (4.1/SMI-4.1) id AA14691; Fri, 28 Oct 94 20:08:00 MDT Date: Fri, 28 Oct 94 20:08:00 MDT Message-Id: <9410290208.AA14691@sfi.santafe.edu> Received: by grasshopper.santafe.edu (4.1/SMI-4.1) id AA16692; Fri, 28 Oct 94 20:08:00 MDT From: nelson@santafe.edu (Nelson Minar) To: Majordomo-Users@GreatCircle.com Subject: Re: Hacked request-answer autoresponder (was: request-answer) In-Reply-To: References: Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Ooops, I didn't make myself clear. I was hoping for a version of request-answer that would process commands in the body (and, ideally, the subject line) and automagically infer which list they apply to. With this filter, I could send mail to majordomo-user-request@greatcircle.com with the subject (or body) "subscribe" and it would work. It's not typical majordomo behaviour, but it would be useful for users. From majordomo-users-owner Fri Oct 28 19:47:10 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA00224 for majordomo-users-outgoing; Fri, 28 Oct 1994 19:33:30 -0700 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA00218; Fri, 28 Oct 1994 19:33:27 -0700 Message-Id: <199410290233.TAA00218@miles.greatcircle.com> To: nelson@santafe.edu (Nelson Minar) cc: Majordomo-Users@greatcircle.com Subject: Re: Hacked request-answer autoresponder (was: request-answer) In-reply-to: Your message of Fri, 28 Oct 94 20:08:00 MDT Date: Fri, 28 Oct 1994 19:33:20 -0700 From: Brent Chapman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk nelson@santafe.edu (Nelson Minar) writes: # Ooops, I didn't make myself clear. I was hoping for a version of # request-answer that would process commands in the body (and, ideally, # the subject line) and automagically infer which list they apply to. # # With this filter, I could send mail to majordomo-user-request@greatcircle.com # with the subject (or body) "subscribe" and it would work. It's not # typical majordomo behaviour, but it would be useful for users. 1.92 will do this. Set up "foo-request" as an alias for "|.../wrapper majordomo -l foo" -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Sat Oct 29 07:47:02 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA03040 for majordomo-users-outgoing; Sat, 29 Oct 1994 07:32:32 -0700 Received: from bosnia.pop.psu.edu (barr@bosnia.pop.psu.edu [146.186.111.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id HAA03035 for ; Sat, 29 Oct 1994 07:32:26 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id KAA09049; Sat, 29 Oct 1994 10:31:51 -0400 Message-Id: <199410291431.KAA09049@bosnia.pop.psu.edu> To: Marc cc: majordomo-users@GreatCircle.COM Subject: Re: new-list script troubles In-reply-to: Your message of "Fri, 28 Oct 1994 16:50:15 PDT." X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Sat, 29 Oct 1994 10:31:50 -0400 From: David Barr Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , Marc writes: >When I run the new-list script, I get the following error message: > > Can't locate majordomo.pl in @INC at ./new-list line 32. The FAQ a list of things to check on this. search for "@INC" You can get the Majordomo FAQ by sending an e-mail message to majordomo@pop.psu.edu with "get file majordomo-faq" in the body of the message. You can get an HTML version on the World Wide Web at http://www.pop.psu.edu/~barr/majordomo-faq.html. --Dave From majordomo-users-owner Sat Oct 29 08:17:17 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA03169 for majordomo-users-outgoing; Sat, 29 Oct 1994 08:12:59 -0700 Received: from skinner.cs.uoregon.edu (skinner.cs.uoregon.edu [128.223.4.13]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id IAA03164 for ; Sat, 29 Oct 1994 08:12:55 -0700 Received: from efn.org by skinner.cs.uoregon.edu with SMTP id AA17374 (5.65/IDA-1.4.2 for majordomo-users@greatcircle.com); Sat, 29 Oct 94 08:12:25 -0700 Received: by efn.efn.org (4.1/smail2.5/05-07-92) id AA03809; Sat, 29 Oct 94 08:11:38 PDT Date: Sat, 29 Oct 1994 08:11:38 -0700 (PDT) From: "Stephen A. Brenner" To: majordomo-users@greatcircle.com Subject: Moderated feature not working Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk We're using version 1.92. I've set the .config file to yes for moderate, but it doesn't intercept the messages. Do I need to go back to the "resend -A" method? Thanks, Steve From majordomo-users-owner Sat Oct 29 11:18:23 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA03521 for majordomo-users-outgoing; Sat, 29 Oct 1994 10:53:07 -0700 Received: from sfi.santafe.edu (sfi.santafe.edu [192.12.12.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id RAA29554 for ; Fri, 28 Oct 1994 17:33:02 -0700 Received: from grasshopper.santafe.edu by sfi.santafe.edu (4.1/SMI-4.1) id AA14211; Fri, 28 Oct 94 18:31:12 MDT Date: Fri, 28 Oct 94 18:31:12 MDT Message-Id: <9410290031.AA14211@sfi.santafe.edu> Received: by grasshopper.santafe.edu (4.1/SMI-4.1) id AA16267; Fri, 28 Oct 94 18:31:12 MDT From: nelson@santafe.edu (Nelson Minar) To: majordomo-users@greatcircle.com Cc: march@europa.com Subject: WWW + Majordomo Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Has anyone put any effort into making a WWW front end to Majordomo? http://coombs.anu.edu.au/CoombswebPages/Majordomo.html has the beginnings of one - you can use checkboxes to send a "subscribe" or "unsubscribe" message to their majordomo. I'm thinking of something more general, one that you could install anywhere, have it figure out what mailing lists you have (although first pass could require people to write the list themselves), and have the form take care of all of the user functions of majordomo. At a minimum, by majordomo command: lists: default front page for your majordomo document subscribe: give a list of the mailing lists at your site and let you easily subscribe to them which: give a list of the mailing lists you personally are on unsubcribe: let you easily unsubscribe from the lists you are on who, info, index: given list X, show the information get: clock on a file in the index one can imagine a similar set of commands for list administrators. I don't think any of this would be particularly difficult, but I don't have a lot of time to do it up. There is a question of security, but given how trivial it is to forge mail on the net anyway I don't think this is worth worrying about. From majordomo-users-owner Sat Oct 29 11:47:50 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA04080 for majordomo-users-outgoing; Sat, 29 Oct 1994 11:35:45 -0700 Received: from unpc.queernet.org (unpc.queernet.org [140.174.78.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id LAA04075 for ; Sat, 29 Oct 1994 11:35:24 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #9) id m0r1I7x-00014wC; Sat, 29 Oct 94 11:03 PDT Message-Id: To: Elizabeth Lear Newman cc: majordomo-users@greatcircle.com Subject: Re: any way to restrict 'who'? In-reply-to: Your message of Thu, 27 Oct 1994 11:17:02 -0400. <199410271517.AA14509@world.std.com> Date: Sat, 29 Oct 1994 11:03:37 -0700 From: "Roger B.A. Klorese" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >--------- > To: majordomo-users@greatcircle.com > From: Elizabeth Lear Newman > Subject: any way to restrict 'who'? > Date: Thu, 27 Oct 1994 11:17:02 -0400 > > > Is there *any* way to set either majordomo 1.62 or 1.92 so that even > the people on the lists can't get the list of members? This is really > important, and I need an answer ASAP - any help is appreciated! > > ...eliz > >--------- I have patches that should work on 1.62. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Sat Oct 29 14:47:33 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA04527 for majordomo-users-outgoing; Sat, 29 Oct 1994 14:34:58 -0700 Received: from ucsd.edu (ucsd.edu [132.239.254.201]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id OAA04521 for ; Sat, 29 Oct 1994 14:34:49 -0700 Received: from sdcc8.UCSD.EDU by ucsd.edu; id OAA14996 sendmail 8.6.9/UCSD-2.2-sun via SMTP Sat, 29 Oct 1994 14:34:09 -0700 for Received: by sdcc8.UCSD.EDU (4.1/UCSDGENERIC.3) id AA08786 to majordomo-users@GreatCircle.COM; Sat, 29 Oct 94 14:32:41 PDT Date: Sat, 29 Oct 1994 14:32:40 -0700 (PDT) From: Paul Phillips Subject: Re: WWW + Majordomo To: majordomo-users@GreatCircle.COM In-Reply-To: <9410290031.AA14211@sfi.santafe.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 28 Oct 1994, Nelson Minar wrote: > Has anyone put any effort into making a WWW front end to Majordomo? > http://coombs.anu.edu.au/CoombswebPages/Majordomo.html has the > beginnings of one - you can use checkboxes to send a "subscribe" or > "unsubscribe" message to their majordomo. When I was at InterNIC I put together something similar; it has subscribe, unsubscribe, and "send information" boxes for each of the lists available at that time. Putting others in would be trivial; it's at http://www.internic.net/internic/lists/majordomo.html Email guide@is.internic.net if you're interested in seeing the code (it's Perl.) > [good ideas about WWW interface snipped] > I don't think any of this would be particularly difficult, but I don't > have a lot of time to do it up. There is a question of security, but > given how trivial it is to forge mail on the net anyway I don't think > this is worth worrying about. It's a nice idea. You can log the machine name initiating the connection via the REMOTE_something http environment variable, which brings it to the same level of security that SMTP offers. We didn't have any problems with abuse of the InterNIC WWW-majordomo interface; about the worst you could do is subscribe someone else to a mailing list (fairly easy anyway.) This would only work with open lists; no private_who or other restrictive config options. If someone wants to work around the existing security limitations and implement something, I'm sure it would be used; I would prefer to wait until SMTP, http, or both offers superior authentication before inviting the coming WWW masses to mess around with it. -PSP From majordomo-users-owner Sat Oct 29 15:21:07 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA04700 for majordomo-users-outgoing; Sat, 29 Oct 1994 14:57:21 -0700 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id OAA04694 for ; Sat, 29 Oct 1994 14:57:09 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA21877 (5.65c/IDA-1.4.4 for ); Sat, 29 Oct 1994 17:55:30 -0400 Message-Id: <199410292155.AA21877@cs.umb.edu> To: Sharokh Cc: majordomo-users@greatcircle.com Subject: Re: Help with list setup In-Reply-To: Your message of "Thu, 27 Oct 1994 13:13:59 PDT." Date: Sat, 29 Oct 1994 17:55:04 -0400 From: "John P. Rouillard" Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk In message , Sharokh writes: >Once you create a list, is there way the list-owner can change the >configuration of any list-request messages to its subscribers? Such as >Welcome list messages, the help file, successed responses, error responses, >etc. Nope. >Another question is that if a subscriber or list-owner sends a request to >list-request, you get your request message back fromm Majordomo@address >than mylist-request@address. Is there anyway to change this that any >request comes from mylist-request than Majordomo@address. Nope, but I will see what I can do for 1.93. It seems it should be easy enough. Sigh, more feeping creaturism. >What I like to do is that I dont want my subscribers have anything to do >with Majordomo@address so that they won't be confused. Actually I have users that prefer it the other way around. One stop shopping as it were, no matter what list they want, they just go to the majordomo. -- John John Rouillard Senior Systems Administrator IDD Information Services rouilj@dstar.iddis.com Waltham, MA (617) 890-1576 x225 Senior Systems Consultant (SERL Project) University of Massachusetts at Boston rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480 =============================================================================== My employers don't acknowledge my existence much less my opinions. From majordomo-users-owner Sun Oct 30 05:47:03 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA11011 for majordomo-users-outgoing; Sun, 30 Oct 1994 05:22:59 -0800 Received: from SYSWRK.UCIS.DAL.CA (syswrk.UCIS.Dal.Ca [129.173.2.108]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id FAA11006 for ; Sun, 30 Oct 1994 05:22:54 -0800 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HIVS1UIAW0003GD4@SYSWRK.UCIS.DAL.CA>; Sun, 30 Oct 1994 09:22:21 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HIVS1NVUSG00MHZK@AC.DAL.CA>; Sun, 30 Oct 1994 09:22:13 -0400 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA06278; Sun, 30 Oct 94 09:22:03 -0400 Date: Sun, 30 Oct 1994 09:22:03 -0400 (AST) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Re: Help with list setup In-reply-to: <199410292155.AA21877@cs.umb.edu> from "John P. Rouillard" at Oct 29, 94 05:55:04 pm To: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9410301322.AA06278@biome.bio.ns.ca> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Content-Length: 840 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I agree with John: >>What I like to do is that I dont want my subscribers have anything to do >>with Majordomo@address so that they won't be confused. > >Actually I have users that prefer it the other way around. One stop >shopping as it were, no matter what list they want, they just go to >the majordomo. It depends on the type of lists you run of course, but in my case, where I have a lot of lists dealing with various aspects of marine ecology, it is common for subscribers to one list to use the `lists' command to find out what other lists of interest there might be. I suspect that this is pretty common. Bill -- Bill Silvert at the Bedford Institute of Oceanography P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2 Preferred InterNet Address: silvert@biome.bio.ns.ca HED runs a WWW server at URL=http://biome.bio.dfo.ca From majordomo-users-owner Sun Oct 30 08:40:19 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA11394 for majordomo-users-outgoing; Sun, 30 Oct 1994 08:17:45 -0800 Received: from sparc (Sparc.uccb.ns.ca [142.12.4.50]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id IAA11389 for ; Sun, 30 Oct 1994 08:17:37 -0800 Received: by sparc (5.0/SMI-SVR4) id AA25471; Sun, 30 Oct 1994 12:14:34 +0400 Date: Sun, 30 Oct 1994 12:14:33 -0400 (AST) From: Steve MacLeod Subject: Re: WWW + Majordomo To: Paul Phillips Cc: majordomo-users@GreatCircle.COM In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 2473 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Speaking of authentication, I am looking at installing Berkeley Sendmail 8.6.9 in place of the sendmail that comes from SUN (Solaris 2.3). What is the general opinion on this pident server and the pident support built into 8.6.9, I understand that PC's and MAC's can masquerade pretty easy with this stuff, is it worth installing? I already run tcp wrappers. Any known problems with 8.6.9 and Majordomo 1.92? Thanks -------------------------------------------------------------------- Steve MacLeod Microcomputer Specialist (902)539-5300x625 Computer Centre University College of Cape Breton Sydney, N.S. Fax (902)562-0119 Canada B1P 5S2 On Sat, 29 Oct 1994, Paul Phillips wrote: > > > On Fri, 28 Oct 1994, Nelson Minar wrote: > > > Has anyone put any effort into making a WWW front end to Majordomo? > > http://coombs.anu.edu.au/CoombswebPages/Majordomo.html has the > > beginnings of one - you can use checkboxes to send a "subscribe" or > > "unsubscribe" message to their majordomo. > > When I was at InterNIC I put together something similar; it has > subscribe, unsubscribe, and "send information" boxes for each of the > lists available at that time. Putting others in would be trivial; it's at > > http://www.internic.net/internic/lists/majordomo.html > > Email guide@is.internic.net if you're interested in seeing the code (it's > Perl.) > > > [good ideas about WWW interface snipped] > > I don't think any of this would be particularly difficult, but I don't > > have a lot of time to do it up. There is a question of security, but > > given how trivial it is to forge mail on the net anyway I don't think > > this is worth worrying about. > > It's a nice idea. You can log the machine name initiating the connection > via the REMOTE_something http environment variable, which brings it to > the same level of security that SMTP offers. We didn't have any problems > with abuse of the InterNIC WWW-majordomo interface; about the worst you > could do is subscribe someone else to a mailing list (fairly easy > anyway.) This would only work with open lists; no private_who or other > restrictive config options. > > If someone wants to work around the existing security limitations and > implement something, I'm sure it would be used; I would prefer to wait > until SMTP, http, or both offers superior authentication before inviting > the coming WWW masses to mess around with it. > > -PSP > From majordomo-users-owner Mon Oct 31 11:37:05 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA07937 for majordomo-users-outgoing; Mon, 31 Oct 1994 11:03:52 -0800 Received: from nd.edu (nd.edu [129.74.250.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id LAA07929 for ; Mon, 31 Oct 1994 11:03:41 -0800 Received: from nowaksg.chem.nd.edu by nd.edu with SMTP (PP) id ; Mon, 31 Oct 1994 13:49:27 -0500 Received: by nowaksg.chem.nd.edu (920330.SGI/HACK-1.0) id AA09822; Mon, 31 Oct 94 14:02:38 -0500 Date: Mon, 31 Oct 94 14:02:38 -0500 From: mike@nowaksg.chem.nd.edu (Mike Buening) Message-Id: <9410311902.AA09822@nowaksg.chem.nd.edu> To: majordomo-users@greatcircle.com Subject: resend unlink patch...again! Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I'm sorry to put this out there. But I copied the patch that someone posted and either I did something real stupid or the posted patch didn't work because as soon as I edited the resend script resend failed completely. Could someone send me the official patch (I'm referring to the one that cleans up the /tmp directory after itself). Mike | Mike Buening (web http://www.nd.edu/~mbuening)| | Beamer (the monster cocker) I could have missed the pain...but I'd have | | mike@nowaksg.chem.nd.edu had to miss the dance. | From majordomo-users-owner Mon Oct 31 13:09:16 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA08491 for majordomo-users-outgoing; Mon, 31 Oct 1994 12:44:56 -0800 Received: from earth.willamette.edu (root@earth.willamette.edu [158.104.100.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA08486 for ; Mon, 31 Oct 1994 12:44:27 -0800 Received: from jupiter (mrussell@jupiter.willamette.edu [158.104.1.1]) by earth.willamette.edu (8.6.8.1/8.6.4) with SMTP id MAA16727 for ; Mon, 31 Oct 1994 12:43:29 -0800 Date: Mon, 31 Oct 1994 12:43:29 -0800 (PST) From: Marc Subject: RE: my last post To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk Please disregard. It seems my mistake was in using two capital letters in the name of the list. Majordomo 1.92 doesn't seem to like capital letters. Is this a bug -- or a feature? marc mrussell@willamette.edu InfoX: sysadmin@olympus.dis.wa.gov ---------------------------------------------------------------------------- "A toast, before we go into battle -- true love. In whatever shape or form it may come, may we all in our dotage be proud to say, 'We were adored once, too.'" -Four Weddings and a Funeral ---------------------------------------------------------------------------- From majordomo-users-owner Mon Oct 31 15:10:10 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA09347 for majordomo-users-outgoing; Mon, 31 Oct 1994 14:49:28 -0800 Received: from keeper (keeper.nmr.varian.com [132.190.40.4]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id OAA09342 for ; Mon, 31 Oct 1994 14:49:17 -0800 Received: from [132.190.40.12] (pizza.nmr.varian.com) by keeper (4.1/SMI-4.1) id AA11080; Mon, 31 Oct 94 14:40:31 PST Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 31 Oct 1994 14:48:26 -0800 To: guide@is.internic.net From: saeedi@netcom.com (Steve Saeedi) Subject: Re: WWW + Majordomo Cc: majordomo-users@GreatCircle.COM Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk At 2:32 PM 10/29/94, Paul Phillips wrote: >On Fri, 28 Oct 1994, Nelson Minar wrote: > >> Has anyone put any effort into making a WWW front end to Majordomo? >> http://coombs.anu.edu.au/CoombswebPages/Majordomo.html has the >> beginnings of one - you can use checkboxes to send a "subscribe" or >> "unsubscribe" message to their majordomo. > >When I was at InterNIC I put together something similar; it has >subscribe, unsubscribe, and "send information" boxes for each of the >lists available at that time. Putting others in would be trivial; it's at > > http://www.internic.net/internic/lists/majordomo.html > >Email guide@is.internic.net if you're interested in seeing the code (it's >Perl.) I would be interested in seeing this code. Thanks in advance, - Steve From majordomo-users-owner Mon Oct 31 16:09:09 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id PAA09790 for majordomo-users-outgoing; Mon, 31 Oct 1994 15:53:54 -0800 Received: from ccc.uba.ar (dcfcen.uba.ar [157.92.1.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id PAA09785 for ; Mon, 31 Oct 1994 15:53:37 -0800 Received: from pucho.uba.ar by ccc.uba.ar with smtp (Smail3.1.28.1 #5) id m0r26Ls-000DmuC; Mon, 31 Oct 94 20:41 GMT-3:00 Received: by pucho.uba.ar (Smail3.1.28.1 #5) id m0r26J8-0000hMC; Mon, 31 Oct 94 20:38 GMT-2:00 Message-Id: From: rbravo@ccc.uba.ar (Ricardo Bravo) Subject: Re: Distributed mailing list -- please advise To: barnhart@mcs.com (Aaron Barnhart) Date: Mon, 31 Oct 1994 20:38:34 -0200 (GMT-2:00) Cc: majordomo-users@greatcircle.com In-Reply-To: from "Aaron Barnhart" at Oct 24, 94 04:16:28 pm X-Mailer: ELM [version 2.4 PL13] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1583 Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk rfc1429 describes a very useful protocol (Listserv Distribute Protocol), in which you send a mail containing the recipients' addresses along with the mail to be delivered to a certain nearby listserv server, and it resends it in an "intelligent" fashion (v.g. sending all the addresses in France in only one mail to its peer in France, and so on). I think you could manage the whole list locally with majordomo, and then use its addresses to send the messages in this way. If you are interested, I have written a bourne shell scripts that manages one of our lists (microsemanario, 900 subscribers) and that works fine. Regards, Ricardo Bravo Universidad de Buenos Aires rbravo@ccc.uba.ar > > > As some of you know, I am trying to mount one of humanity's larger > mailing lists -- the distribution for the David Letterman Top Tens > -- which by the way if you want to subscribe to, *don't* mail me, > mail letterman@mcs.net instead. > > It has about 30,000 subscribers. Rather than burden a single site > with this, I am considering a semi-automated distributed system > involving ten or more sites. > > I am wondering if Majordomo has capability, either currently or through > a patch that could be written, to support placement and updating of > names for a single list at different, let's say ftp'able, sites. > > Thanks. > > > > -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Ricardo Luis Bravo (rbravo@ccc.uba.ar) Centro de Comunicacion Cientifica Universidad de Buenos Aires Tel.: (54-1) 787-2674; Fax: (54-1) 787-2670 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From majordomo-users-owner Mon Oct 31 16:43:47 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id QAA10075 for majordomo-users-outgoing; Mon, 31 Oct 1994 16:14:51 -0800 Received: from netcomsv.netcom.com (uucp5.netcom.com [163.179.3.5]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA07838 for ; Mon, 31 Oct 1994 10:53:05 -0800 Received: from localhost by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id KAA23778; Mon, 31 Oct 1994 10:21:17 -0800 Received: from [192.9.200.100] (don_mac [192.9.200.100]) by ncc1701a.talarian.com (8.6.9/8.6.9) with SMTP id KAA06411 for ; Mon, 31 Oct 1994 10:03:55 -0800 X-Sender: don@ncc1701a Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 31 Oct 1994 10:03:54 -0800 To: Majordomo-Users@GreatCircle.com From: don@talarian.com (Don Gray) Subject: Re: WWW + Majordomo (plz post the InterNIC code) Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk >On Fri, 28 Oct 1994, Nelson Minar wrote: >> Has anyone put any effort into making a WWW front end to Majordomo? > >When I was at InterNIC I put together something similar; it has >subscribe, unsubscribe, and "send information" boxes for each of the >lists available at that time. Putting others in would be trivial; it's at > > http://www.internic.net/internic/lists/majordomo.html > >Email guide@is.internic.net if you're interested in seeing the code (it's >Perl.) Can someone post this when the get the code? I imagine a lot of people here would like to get a copy (or just send it to me, cause I could use it!). Thanks, Don From majordomo-users-owner Mon Oct 31 16:59:48 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id QAA10097 for majordomo-users-outgoing; Mon, 31 Oct 1994 16:15:11 -0800 Received: from earth.willamette.edu (earth.willamette.edu [158.104.100.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA08454 for ; Mon, 31 Oct 1994 12:35:02 -0800 Received: from jupiter (mrussell@jupiter.willamette.edu [158.104.1.1]) by earth.willamette.edu (8.6.8.1/8.6.4) with SMTP id MAA16153 for ; Mon, 31 Oct 1994 12:32:59 -0800 Date: Mon, 31 Oct 1994 12:32:58 -0800 (PST) From: Marc Subject: List exists, but can't subscribe. To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk I have a problem. I've successfully created one list, and now I need another. I created it in the same way as the first, but I can't seem to subscribe to it. When I send a subscribe message, the response is that the list doesn't exist. However, when I send a lists command, it shows up. Is there a reason for this? marc mrussell@willamette.edu InfoX: sysadmin@olympus.dis.wa.gov ---------------------------------------------------------------------------- "A toast, before we go into battle -- true love. In whatever shape or form it may come, may we all in our dotage be proud to say, 'We were adored once, too.'" -Four Weddings and a Funeral ---------------------------------------------------------------------------- From majordomo-users-owner Mon Oct 31 17:11:36 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id QAA09998 for majordomo-users-outgoing; Mon, 31 Oct 1994 16:11:40 -0800 Received: from netcomsv.netcom.com (netcomsv.netcom.com [192.100.81.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA04093 for ; Sat, 29 Oct 1994 11:44:08 -0700 Received: from ainet.com by netcomsv.netcom.com with SMTP (8.6.4/SMI-4.1) id LAA29203; Sat, 29 Oct 1994 11:40:35 -0700 Received: by ainet.com (4.1/SMI-4.1) id AA02831; Sat, 29 Oct 94 11:43:37 PDT Date: Sat, 29 Oct 1994 11:43:37 -0700 (PDT) From: "Peter W. Losher" To: Nelson Minar Cc: majordomo-users@greatcircle.com, march@europa.com Subject: Re: WWW + Majordomo In-Reply-To: <9410290031.AA14211@sfi.santafe.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Fri, 28 Oct 1994, Nelson Minar wrote: > Has anyone put any effort into making a WWW front end to Majordomo? > http://coombs.anu.edu.au/CoombswebPages/Majordomo.html has the > beginnings of one - you can use checkboxes to send a "subscribe" or > "unsubscribe" message to their majordomo. . . . I just checked it out and it looks great! . . . My compliments . . . > I don't think any of this would be particularly difficult, but I don't > have a lot of time to do it up. There is a question of security, but > given how trivial it is to forge mail on the net anyway I don't think > this is worth worrying about. . . . Yeah, I was very impressed with the homepage and I would be very interested in setting one up for my lists here at ainet.com . . . PwL ----------------------------------------------------------------------------- Peter W. Losher ******************************************* plosher@ainet.com **** "From this point forward, things get a *LITTLE* bit more confusing" **** --------------------------Finger for my PGP key------------------------------ From majordomo-users-owner Mon Oct 31 18:08:31 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA10984 for majordomo-users-outgoing; Mon, 31 Oct 1994 17:16:01 -0800 Received: from budman.lanl.gov (budman.lanl.gov [128.165.114.176]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id RAA10979 for ; Mon, 31 Oct 1994 17:15:37 -0800 Received: by budman.lanl.gov (1.38.193.4/16.2) id AA24524; Mon, 31 Oct 1994 18:14:12 -0700 From: "Douglas Gatchell" Message-Id: <9410311814.ZM24522@budman.lanl.gov> Date: Mon, 31 Oct 1994 18:14:12 -0700 X-Mailer: Z-Mail (3.2.0 16aug94) To: majordomo-users@GreatCircle.COM Subject: majordomo 1.92 - lists command doesn't work Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The lists command has ceased to work for us. I suspect it is the same problem that results when we try to ls the directory (ie ls /listdir/* results in Arguments too long.). I have looked at the code in majordomo ( while(<${listdir}/*>) { ) and have determined that this returns a null list. Is there anyway around this? Is there a finite number of lists that majordomo can handle. We curretly have 294 lists and 1725 entries in the directory. -- __ ---------------------------------------------------- __/ /_______/ Doug Gatchell/dgg@lanl.gov/(505)667-5119 / / / / / / Los Alamos National Labs/CIC-5 Network Engineering/ /___/_/ /_/ / MS B-255/Los Alamos, NM 87545/FAX(505)665-7793 / /__//__/___________________________________________________/ From majordomo-users-owner Mon Oct 31 18:38:27 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA11211 for majordomo-users-outgoing; Mon, 31 Oct 1994 17:51:42 -0800 Received: from skinner.cs.uoregon.edu (skinner.cs.uoregon.edu [128.223.4.13]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id RAA11206 for ; Mon, 31 Oct 1994 17:51:35 -0800 Received: from efn.org by skinner.cs.uoregon.edu with SMTP id AA16748 (5.65/IDA-1.4.2 for Majordomo-Users@GreatCircle.com); Mon, 31 Oct 94 17:49:57 -0800 Received: by efn.efn.org (4.1/smail2.5/05-07-92) id AA14771; Mon, 31 Oct 94 17:48:54 PST Date: Mon, 31 Oct 1994 17:48:53 -0800 (PST) From: "Stephen A. Brenner" To: Don Gray Cc: Majordomo-Users@GreatCircle.com Subject: Re: WWW + Majordomo (plz post the InterNIC code) 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, 31 Oct 1994, Don Gray wrote: > >On Fri, 28 Oct 1994, Nelson Minar wrote: > >> Has anyone put any effort into making a WWW front end to Majordomo? > > > >When I was at InterNIC I put together something similar; it has > >subscribe, unsubscribe, and "send information" boxes for each of the > >lists available at that time. Putting others in would be trivial; it's at > > > > http://www.internic.net/internic/lists/majordomo.html > > > >Email guide@is.internic.net if you're interested in seeing the code (it's > >Perl.) > > Can someone post this when the get the code? I imagine a lot of people > here would like to get a copy (or just send it to me, cause I could use > it!). > > Thanks, > Don Here's what I received when I requested this: --------------------------------------------------------------- >Date: Mon, 31 Oct 1994 12:07:36 -0800 >From: InterNIC Reference Desk >To: sbrenner@efn.org >Subject: Information. >X-UIDL: 783640334.007 > >#!/usr/local/bin/perl > >require '/infoguide/httpd/cgi-lib/cgi-lib.pl'; > ># This should match the mail program on your system. >$mailprog = '/usr/lib/sendmail'; > >&ReadParse; >print &PrintHeader; > >&print_error_message unless $in{'from_name'}; >&print_error_message unless $in{'from_email'}; > >if ( ($in{'net-happenings'} EQ "none") && > ($in{'scout-report'} EQ "none") && > ($in{'net-happenings-digest'} EQ "none") ) { > &print_error_message; >} > ># Now send mail to $recipient > >open (MAIL, "|$mailprog majordomo@is.internic.net") || die "Can't open $mailprog!\n"; >select(MAIL); >print "Reply-to: $in{'from_email'} ($in{'from_name'})\n"; >print "Subject:\n\n"; > >if($in{'net-happenings'} NE "none") { > if ($in{'net-happenings'} EQ "subscribe") { > print "subscribe net-happenings $from_email\n"; > } elsif ($in{'net-happenings'} EQ "unsubscribe") { > print "unsubscribe net-happenings $from_email\n"; > } elsif ($in{'net-happenings'} EQ "info") { > print "info net-happenings\n"; > } >} > >if($in{'net-happenings-digest'} NE "none") { > if ($in{'net-happenings-digest'} EQ "subscribe") { > print "subscribe net-happenings-digest $from_email\n"; > } elsif ($in{'net-happenings-digest'} EQ "unsubscribe") { > print "unsubscribe net-happenings-digest $from_email\n"; > } elsif ($in{'net-happenings-digest'} EQ "info") { > print "info net-happenings-digest\n"; > } >} > >if ($in{'scout-report'} NE "none") { > if ($in{'scout-report'} EQ "subscribe") { > print "subscribe scout-report $from_email\n"; > } elsif ($in{'scout-report'} EQ "unsubscribe") { > print "unsubscribe scout-report $from_email\n"; > } elsif ($in{'scout-report'} EQ "info") { > print "info scout-report\n"; > } >} > >select(STDOUT); >close (MAIL); > >&print_sent_message; >exit 0; > ># ------------------------------------------------------------ > ># Print out a content-type for HTTP/1.0 compatibility > >sub print_sent_message >{ > print "Request sent.\n\n"; > print "\n\n"; > print "

Your message has been been sent to majordomo.

\n"; > print "You should be receiving an acknowledgement shortly.\n\n"; > print "\n"; > exit 0; >} > >sub print_error_message >{ > print "Error processing your request!\n\n"; > print "\n\n

Error processing your request!

\n\n"; > print "Your message did not contain all the necessary information.

\n"; > print "Did you include both your name and email address?\n\n"; > print "\n"; > exit 0; >} > > > From majordomo-users-owner Mon Oct 31 18:38:31 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id SAA11472 for majordomo-users-outgoing; Mon, 31 Oct 1994 18:34:28 -0800 Received: from miles.greatcircle.com (localhost [127.0.0.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id SAA11466; Mon, 31 Oct 1994 18:34:25 -0800 Message-Id: <199411010234.SAA11466@miles.greatcircle.com> To: "Douglas Gatchell" cc: majordomo-users@greatcircle.com Subject: Re: majordomo 1.92 - lists command doesn't work In-reply-to: Your message of Mon, 31 Oct 1994 18:14:12 -0700 Date: Mon, 31 Oct 1994 18:34:08 -0800 From: Brent Chapman Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk "Douglas Gatchell" writes: # The lists command has ceased to work for us. I suspect it is the same # problem that results when we try to ls the directory (ie ls /listdir/* # results in # Arguments too long.). # # I have looked at the code in majordomo ( while(<${listdir}/*>) { ) # and have determined that this returns a null list. # # Is there anyway around this? Is there a finite number of lists that # majordomo can handle. We curretly have 294 lists and 1725 entries in the # directory. There's a limit to how big a directory you can handle with a <...> construct in perl (the limit isn't actually in perl, it's in sh or csh, which is what perl uses to expand the <...> constructs). What you need to do is replace the while (<${listdir}/*>) { ... } with something like: opendir(DIR, "$listdir") || die("opendir(DIR, \"$listdir\"): $!"); while ($_ = readdir(DIR)) { ... } closedir(DIR); -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Mon Oct 31 18:43:31 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA10953 for majordomo-users-outgoing; Mon, 31 Oct 1994 17:09:42 -0800 Received: from ucsd.edu (ucsd.edu [132.239.254.201]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id RAA10942 for ; Mon, 31 Oct 1994 17:09:07 -0800 Received: from sdcc8.UCSD.EDU by ucsd.edu; id RAA13853 sendmail 8.6.9/UCSD-2.2-sun via SMTP Mon, 31 Oct 1994 17:08:10 -0800 for Received: by sdcc8.UCSD.EDU (4.1/UCSDGENERIC.3) id AA04499 to Majordomo-Users@GreatCircle.COM; Mon, 31 Oct 94 17:06:32 PST Date: Mon, 31 Oct 1994 17:06:31 -0800 (PST) From: Paul Phillips Reply-To: Paul Phillips Subject: Re: WWW + Majordomo (here's the InterNIC code) To: Majordomo-Users@GreatCircle.COM In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk On Mon, 31 Oct 1994, Don Gray wrote: > Can someone post this when the get the code? I imagine a lot of people > here would like to get a copy (or just send it to me, cause I could use > it!). I wasn't aware that the response for this would be so high (as I said, I'm not at InterNIC any more but the person that now answers guide mail politely informed me of an incoming deluge...) I requested a copy for myself, I hadn't seen it in a while. Just so nobody gets the wrong idea, I can tell that I didn't write 100% of this by a couple comments that aren't my style. I hadn't intended this to go into production; I must have leveraged somebody else's work. I did write the majority however. I just performed a quick hack that should have made it Perl5 compatible; hopefully I didn't break it. This was never designed to be general, so the listnames are hardcoded. There, enough disclaimers :-) If there is enough interest, I can see if I can find the time to put together a more general and comprehensive package. It would appear that there is. To see how the form in the HTML page should look, see the URL http://www.internic.net/internic/lists/majordomo.html and here is the code it's passed to: --- Cut here -- #!/usr/local/bin/perl require '/infoguide/httpd/cgi-lib/cgi-lib.pl'; # This should match the mail program on your system. $mailprog = '/usr/lib/sendmail'; # Your majordomo $majordomo = 'majordomo@is.internic.net'; &ReadParse; print &PrintHeader; &print_error_message unless $in{'from_name'}; &print_error_message unless $in{'from_email'}; if ( ($in{'net-happenings'} EQ "none") && ($in{'scout-report'} EQ "none") && ($in{'net-happenings-digest'} EQ "none") ) { &print_error_message; } # Now send mail to $recipient open (MAIL, "|$mailprog $majordomo") || die "Can't open $mailprog!\n"; select(MAIL); print "Reply-to: $in{'from_email'} ($in{'from_name'})\n"; print "Subject:\n\n"; if($in{'net-happenings'} NE "none") { if ($in{'net-happenings'} EQ "subscribe") { print "subscribe net-happenings $from_email\n"; } elsif ($in{'net-happenings'} EQ "unsubscribe") { print "unsubscribe net-happenings $from_email\n"; } elsif ($in{'net-happenings'} EQ "info") { print "info net-happenings\n"; } } if($in{'net-happenings-digest'} NE "none") { if ($in{'net-happenings-digest'} EQ "subscribe") { print "subscribe net-happenings-digest $from_email\n"; } elsif ($in{'net-happenings-digest'} EQ "unsubscribe") { print "unsubscribe net-happenings-digest $from_email\n"; } elsif ($in{'net-happenings-digest'} EQ "info") { print "info net-happenings-digest\n"; } } if ($in{'scout-report'} NE "none") { if ($in{'scout-report'} EQ "subscribe") { print "subscribe scout-report $from_email\n"; } elsif ($in{'scout-report'} EQ "unsubscribe") { print "unsubscribe scout-report $from_email\n"; } elsif ($in{'scout-report'} EQ "info") { print "info scout-report\n"; } } select(STDOUT); close (MAIL); &print_sent_message; exit 0; # ------------------------------------------------------------ # Print out a content-type for HTTP/1.0 compatibility sub print_sent_message { print "Request sent.\n\n"; print "\n\n"; print "

Your message has been been sent to majordomo.

\n"; print "You should be receiving an acknowledgement shortly.\n\n"; print "\n"; exit 0; } sub print_error_message { print "Error processing your request!\n\n"; print "\n\n

Error processing your request!

\n\n"; print "Your message did not contain all the necessary information.

\n"; print "Did you include both your name and email address?\n\n"; print "\n"; exit 0; } -- Cut here -- -PSP From majordomo-users-owner Mon Oct 31 22:41:24 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id WAA12857 for majordomo-users-outgoing; Mon, 31 Oct 1994 22:32:13 -0800 Received: from primus.com (primus.com [199.2.50.200]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id WAA12847; Mon, 31 Oct 1994 22:32:00 -0800 Received: (from paulp@localhost) by primus.com (8.6.8.1/SMI 4.1+) id WAA12115; Mon, 31 Oct 1994 22:30:20 -0800 Date: Mon, 31 Oct 1994 22:30:19 -0800 (PST) From: Paul Phillips Subject: Initial release of www-majordomo To: majordomo-users@greatcircle.com, majordomo-workers@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk The interest in the WWW interface to majordomo has inspired me to take a crack at a more general package. This is tested and works, but I would appreciate feedback on what features you would like added or changed; I waffled on whether to include such commands as "get" and "index". Suggestions on what language to use for the commands that is both succinct and easily understood are also desired. -Paul Phillips Primus Consulting #!/usr/local/bin/perl # # WWW-Majordomo v0.1beta :-) # Copyright 1994, Paul Phillips (paulp@primus.com) # # Required software: # # majordomo, by Brent Chapman and John Rouillard # ftp://ftp.greatcircle.com/pub/majordomo/majordomo-1.92.tar.Z # # cgi-lib.pl, by Steven E. Brenner # ftp://ftp.ncsa.uiuc.edu/Web/httpd/Unix/ncsa_httpd/cgi/cgi-lib.pl.Z # # Be aware that this software is potentially abusable. The current # lack of security in smtp and http makes this situation unavoidable. # It does not make possible anything that was not already, but it # does make net foolishness easier. Neither I nor Primus take any # responsibility for any problems that arise due to the misuse of this # software. Caveat webmaster. # # Standard disclaimers apply. # Tune these for your system # Location of cgi-lib; this is required $cgilib = '/usr/local/etc/httpd/lib/cgi-lib.pl'; # Location of your delivery agent; usually /usr/lib/sendmail $mailprog = '/usr/lib/sendmail'; # Full hostname of machine majordomo runs on $whereami = 'primus.com'; # URL of this script $this_url = 'http://www.primus.com/htbin/www-majordomo'; # The mailing lists you want interfaces for should be listed here. # Follow each majordomo mailing list name with the name you would like # presented on the WWW page. Make sure to separate each entry by # commas, but do not trail the last one with a comma. %lists = ( "foo-list", "Foo List (for discussion of Foo!)" ); # You should not have to change anything below this line unless you # enjoy Perl hacking. require $cgilib; &ReadParse; print &PrintHeader; if($in{'from_email'}) { &majordomo_mail; } else { &majordomo_html; } exit 0; sub majordomo_mail { open (MAIL, "|$mailprog majordomo\@$whereami") || die "Can't open $mailprog!\n"; select(MAIL); print "Reply-to: $in{'from_email'}"; if($in{'from_name'}) { print " ($in{'from_name'})\n"; } else { print "\n"; } print "Subject:\n\n"; if($in{'which'} EQ "true") { print "which $from_email\n"; } if($in{'lists'} EQ "true") { print "lists\n"; } if($in{'help'} EQ "true") { print "help\n"; } foreach(keys(%lists)) { if($in{$_} EQ "subscribe") { print "subscribe $_ $from_email\n"; } elsif($in{$_} EQ "unsubscribe") { print "unsubscribe $_ $from_email\n"; } elsif($in{$_} EQ "index") { print "index $_\n"; } elsif($in{$_} EQ "which") { print "which $from_email\n"; } elsif($in{$_} EQ "who") { print "who $_\n"; } elsif($in{$_} EQ "info") { print "info $_\n"; } } select(STDOUT); close(MAIL); &print_sent_message; return; } sub majordomo_html { print <<"EOM"; WWW Majordomo for $whereami

WWW Majordomo: $whereami

You can perform majordomo mailing list commands for any of the available lists by using the pulldown menus. The default action for each list is to do nothing ("No Action"), but you can also subscribe, unsubscribe, send information to yourself, obtain a list of available files related to the list, or see who is subscribed to the list. The results will be sent to your email address, which you must supply in the "Email Address" input field.

Your Name (Optional):

Your E-Mail Address (Required!):

  • Which lists am I on?
  • Catalog of available lists
  • Help!
EOM foreach(keys(%lists)) { print <<"EOM";

$lists{$_}

EOM } print <<"EOM";

EOM return; } sub print_sent_message { print <<"EOM"; Request sent. Your message has been been sent to majordomo\@$whereami.

You should be receiving an acknowledgement shortly.

Return to WWW majordomo.

EOM return; } From majordomo-users-owner Mon Oct 31 23:09:24 1994 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id WAA12978 for majordomo-users-outgoing; Mon, 31 Oct 1994 22:54:31 -0800 Received: from earth.willamette.edu (root@earth.willamette.edu [158.104.100.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id WAA12973 for ; Mon, 31 Oct 1994 22:54:25 -0800 Received: from jupiter (mrussell@jupiter.willamette.edu [158.104.1.1]) by earth.willamette.edu (8.6.8.1/8.6.4) with SMTP id WAA11578 for ; Mon, 31 Oct 1994 22:53:34 -0800 Date: Mon, 31 Oct 1994 22:53:33 -0800 (PST) From: Marc Subject: shlock.pl problem To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-users-owner@GreatCircle.COM Precedence: bulk For some reason, whenever I send a message to my list, I get the following error message (after about 10 minutes or so, during which time majordomo keeps trying the same things): shlock: open(">/home/majordomo-1.92/lists/digest/infoxmaint-digest/shlock.2578"): No such file or directory at shlock.pl line 131. It isn't a permission problem, because everything is working as far as that goes. What does this mean? I've checked all the permissions, and they're correct. Majordom owns everything and can read/write everywhere necessary. The line the error shows up in is: warn("shlock: open(\">$tempname\"): $!"); Can anyone help? marc mrussell@willamette.edu InfoX: sysadmin@olympus.dis.wa.gov ---------------------------------------------------------------------------- "A toast, before we go into battle -- true love. In whatever shape or form it may come, may we all in our dotage be proud to say, 'We were adored once, too.'" -Four Weddings and a Funeral ----------------------------------------------------------------------------