From majordomo-users-owner Mon May 2 16:51:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA11416; Mon, 2 May 1994 16:51:38 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA11410; Mon, 2 May 1994 09:51:26 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA19930 (5.65c/IDA-1.4.4 for ); Mon, 2 May 1994 12:49:06 -0400 Message-Id: <199405021649.AA19930@cs.umb.edu> To: Ben Smith Cc: majordomo-users@greatcircle.com Subject: Re: Where do I turn In-Reply-To: Your message of "Mon, 02 May 1994 10:48:09 EDT." <9405021448.AA10089@bytepb.byte.com> Date: Mon, 02 May 1994 12:49:05 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk This posting originally appeared on list-managers. Posts about majordomo operation should be done to the list majordomo-users@greatcircle.com and not to list-managers. In message <9405021448.AA10089@bytepb.byte.com>, Ben Smith writes: > I seem to have everything (include new-list, more on that) > working at ronin.com, but am having trouble with the address > resolution of incoming messages. This appears to be either a > sendmail or smail problem. Does anyone know where to post > questions about that. (I do not participate in Usenet). You could try the Back Bay (as in Back Bay Boston, although we have members all over New England) syadamin list bblisa@bblisa.org. You can subscribe using majordomo@bblisa.org. Majordomo-users may also have an answer if you can describe what is happening. > Now, back to new-list: I found a bug (at least as far as my Perl > version is concerned). What perl version? Nothing I have access to (4.019-4.036) complains about it. Note that majordomo only is designed to work with 4.035 or above. > On line 38, the > $list = @ARGV[0]; > is incorrect syntax. It should read > $list = $ARGV[0]; > When addressing elements of a list, the list-name is preceded by > the $ not the list designator, @. Yes and no. Technically @ARGV[0] is an array slice of one element, namely $ARGV[0]. There is however no real reason to have an array slice there, so I have changed it to a simple variable dereference for version 1.90. -- John John Rouillard Special Projects Volunteer 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 May 2 17:43:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA12206; Mon, 2 May 1994 17:43:56 GMT Received: from disserv.stu.umn.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA12200; Mon, 2 May 1994 10:43:42 -0700 Received: by disserv.stu.umn.edu (Smail3.1.28.1 #2) id m0py22V-0002RnC; Mon, 2 May 94 12:44 CDT Message-Id: From: thingles@disserv.stu.umn.edu (Jamie Thingelstad) Subject: Majordomo log summmary and HTML To: majordomo-users@greatcircle.com (Majordomo Users List) Date: Mon, 2 May 1994 12:44:19 -0600 (CDT) X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 694 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I want to put out a feeler before I send out a diff and script. I made a shell script to wrap around logsummary.pl as well as make some modifications to logsummary.pl that make the log HTML formatted. You can see the majordomo log from disserv at http://disserv.stu.umn.edu/~majrdomo If people are intersted, I'll post a diff and the shell script. This is rebuilt everynight by cron. -- = http://disserv.stu.umn.edu/~thingles ================= Jamie Thingelstad W-612.626.7846 F-612.625.5572 Technical Coordinator 101 Pleasant St SE, 12 Johnston, Mpls, MN 55455 Disability Services = thingles@disserv.stu.umn.edu =================== University of Minnesota From majordomo-users-owner Mon May 2 20:01:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA13329; Mon, 2 May 1994 20:01:19 GMT Received: from flowbee.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA13323; Mon, 2 May 1994 13:01:04 -0700 Received: from localhost (larry@localhost) by flowbee.interaccess.com (8.6.5/8.6.5) id PAA23017; Mon, 2 May 1994 15:01:39 -0500 Date: Mon, 2 May 1994 15:01:39 -0500 (CDT) From: "Larry Q. Public" Subject: what is the request alias for? To: majordomo Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I can't seem to find any documentation on what the list-request alias is for. How can the list owner "put" files there (where?) to be retrieved? Many thanks, - Larry@interaccess.com From majordomo-users-owner Wed May 4 16:20:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA27073; Wed, 4 May 1994 16:20:47 GMT Received: from postman.osf.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA27067; Wed, 4 May 1994 09:20:39 -0700 Received: from nermal.osf.org by postman.osf.org (5.64+/OSF 1.0) id AA04993; Wed, 4 May 94 12:20:44 -0400 Message-Id: <9405041620.AA04993@postman.osf.org> To: majordomo-users@GreatCircle.com Subject: Need help with passwd files Reply-To: cheryl@osf.org Voice-Mail: 617 621-8904 Date: Wed, 04 May 1994 12:20:43 -0400 From: Cheryl Ann Korizis Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi. I've recently installed majordomo. When I started testing I made a few bogus lists names to play with and created both .closed and .passwd files for each, in the same place as where my lists are kept on the majordomo server. When I tried to put three REAL lists into action, I created a .majordomo file in each of the approval user's home directory on the majordomo server. I have the format in 3 columns separated by tabs. Are there any restrictions on the characters for the password? For all three approval users, it generates the same message below, regardless of what I've changed the password to be. Also the "passwd " command doesn't work for them either. How does majordomo find the home directory of the approval sender and check the sender of the approve command and that the password is correct for that person and listname? Although most of our users have pcs or their own workstations, they all still have a home directory on the majordomo server, and we update hesiod database so the automounter can find it. Suggestions about this .majordomo file? Another unrelated question, what was the final outcome on the discussions on X400 address formats? I currently administer 727 mail lists with X400 addresses and other types that have a "/" in them. Thank you for your help in advance!! > >From Majordomo-Owner@osf.org Tue May 3 21:06:54 1994 > Received: by bubba.osf.org (5.65/OSF 1.0) > id AA28806; Tue, 3 May 94 21:06:52 -0400 > Date: Tue, 3 May 94 21:06:52 -0400 > Message-Id: <9405040106.AA28806@bubba.osf.org> > To: groff@bubba.osf.org > From: Majordomo@osf.org > Subject: Majordomo results > Reply-To: Majordomo@osf.org > > - -- > > >>>> approve subscribe pgstaff cheryl@osf.org > **** approve: invalid list or password. > **** Help for Majordomo@osf.org: ============================================================================ Cheryl Korizis, Postmaster ___ ___ ___ Voice: (617) 621-8904 Open Software Foundation / / /__ /__ Fax: (617) 621-0584 11 Cambridge Center /__/ ___/ / Internet: cheryl@osf.org Cambridge, MA 02142 UUCP: uunet!osf!cheryl ============================================================================ From majordomo-users-owner Thu May 5 21:59:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA07305; Thu, 5 May 1994 21:59:31 GMT Received: from tree.egr.uh.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA07292; Thu, 5 May 1994 14:59:16 -0700 Received: from thanatos by tree.egr.uh.edu (NX5.67d/NX3.0M) id AA28733; Thu, 5 May 94 17:00:03 -0500 From: "Paul S. Sears" Message-Id: <9405052200.AA28733@tree.egr.uh.edu> Received: by thanatos.egr.uh.edu (NX5.67d/NX3.0X) id AA10165; Thu, 5 May 94 17:00:02 -0500 Date: Thu, 5 May 94 17:00:02 -0500 Received: by NeXT.Mailer (1.100) Received: by NeXT Mailer (1.100) To: majordomo-users@GreatCircle.COM Subject: Problem with digests Reply-To: sears@uh.edu Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We recently started up some mailing lists with 1.90b2 of Majordomo. However, we are having a strange problem with the Digests. With each new issue of a digest, all the previous issues are included! Is this a feature or did I misconfigure something? Is there something in the config file that I need to change? Here are my aliases: #ENSAIN mailing list ensain:"|/usr/local/listserv/majordomo-1.90/wrapper resend -l ensain -h tree.egr.uh.edu ensain-outgoing" ensain-digest:ensain ensain-outgoing: :include:/usr/local/listserv/majordomo-1.90/mailing-lists/ensain, "| /usr/local/listserv/majordomo-1.90/wrapper digest -r -C -l ensain-digest ensain-digest-outgoing", "| /usr/local/listserv/majordomo-1.90/wrapper archive2.pl -a -m -f /usr/local/listserv/majordomo-1.90/Archive/ensain/ensain.archive" ensain-digest-outgoing: :include:/usr/local/listserv/majordomo-1.90/mailing-lists/ensain-digest ensain-request: "| /usr/local/listserv/majordomo-1.90/wrapper majordomo -l ensain" ensain-digest-request: "| /usr/local/listserv/majordomo-1.90/wrapper majordomo -l ensain-digest" owner-ensain: sears@uh.edu owner-ensain-outgoing:owner-ensain owner-ensain-digest: owner-ensain owner-ensain-digest-outgoing:owner-ensain --- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime." ******* I do not represent the University of Houston ********* From majordomo-users-owner Fri May 6 20:03:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA13312; Fri, 6 May 1994 20:03:33 GMT Received: from home.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA13305; Fri, 6 May 1994 13:03:25 -0700 Received: (from larry@localhost) by home.interaccess.com (8.6.9/8.6.9) id PAA12742; Fri, 6 May 1994 15:02:55 -0500 Date: Fri, 6 May 1994 15:02:54 -0500 (CDT) From: "Larry Q. Public" Subject: what does the maillist-request do? To: majordomo Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk What is that alias used for? I can't seem to figure it out. Any help would be most appreciated. -Larry@interaccess.com From majordomo-users-owner Fri May 6 16:23:32 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14232; Fri, 6 May 1994 23:15:21 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA06785; Thu, 5 May 1994 13:39:25 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id OAA15080 for ; Thu, 5 May 1994 14:53:11 -0400 Message-Id: <199405051853.OAA15080@bosnia.pop.psu.edu> To: majordomo-users@greatcircle.com Subject: prelim majordomo FAQ X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Date: Thu, 05 May 1994 14:53:10 -0400 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here's my first draft on a FAQ to be released in conjunction with the upcoming 1.90 full release. Please read this over and report any errors or additions to me. In a couple days I'm going to send this off to the *.answers team for approval for regular posting to the comp.mail.* groups. (probably .sendmail, .smail, and .misc) --Dave ------------------------------------ This FAQ is split into several sections: 1. What is Majordomo and how can I get it? 2. Problems setting up Majordomo 3. Setting up mailing lists and aliases 4. Miscellaneous mailer problems This FAQ is Copyright 1994 by David Barr and The Pennsylvania State University. This document may be reproduced for free or for profit, 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. 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. Section 1: What is Majordomo and how can I get it? ================================================== Subject: 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). 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). Subject: 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 Section 2: Problems setting up Majordomo ======================================== Subject: I get an error "insecure usage" from the wrapper --------------------------------------------------------- > Hello, I'm trying to install majordomo and after putting everything the > way the documentation told me I'm getting the following error message when > I send a message to majordomo: > > /usr/local/udla/etc/majordomo/wrapper: error: insecure usage > 554 "|/usr/local/udla/etc/majordomo/wrapper > /usr/local/udla/etc/majordomo"... > unknown mailer error 2 > > > I double checked the permissions and everything looks fine to me, does any > have any tip that would help me? Thanks in advance. The argument to ".../wrapper" should be simply "majordomo", not "/usr/local/udla/etc/majordomo". "wrapper" has where to look (/usr/local/udla/etc) compiled in to it (the "W_BIN" setting in the Makefile), for security reasons. Your alias should say: |"/users/majordomo/wrapper majordomo" Subject: I get "majordomo: No such file or directory" from the wrapper ---------------------------------------------------------------------- Make sure that the #! statement at the beginning of all the Majordomo executables contain the correct path to the perl program. (the default is /usr/local/bin/perl) Make sure also that majordomo and all the related scripts are in the W_BIN directory as defined in the Makefile. Subject: 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. Subject: 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, > <_GEN_1> 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. Section 3: Setting up mailing lists and aliases =============================================== Subject: 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@GreatCircle.COM, 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@GreatCircle.COM" in the envelope from instead of "owner-sample@greatcircle.com". Either address will work, of course, but the generic address is preferred should the owner ever change. Subject: What's this Owner-List and List-Owner stuff? Why both? ---------------------------------------------------------------- >I see both of these in use, but I get tired of assigning both of them for >every alias I add in the list. I looked in RFC 822 and 1123, but neither >specified anything. So is there a standard? Or should I just add both >owner-list and list-owner to be safe? [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". Subject: 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. If you are using resend, use the '-r ' flag to set the Reply-To field to the list. Subject: How can I hide lists so they can't be viewed by 'lists'? ----------------------------------------------------------------- > Could you add a 'private_lists' parameter to the config file that would > prevent people from seeing that the list exists (and from getting the > description for the list). I think you've given us the ability to lock down > pretty much everything else. 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. Subject: 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) Subject: 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 .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 .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. Brent Chapman's digest program has been integrated with Majordomo in the current release. All digest options can now be specified directly in the list configuration file. The Subject: 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). Subject: Majordomo seems to be taking many minutes to process commands ---------------------------------------------------------------------- | Commands are being processed at the rate of about two per | hour. It should take about three days for all 160 users to be | unsubscribed! Majordomo tries to lock the log file (by creating a lock file in the directory with the log file) for 10 minutes for each log message, before giving up. It's typically going to log one log message for each command in the input. If the directory containing the file is not writable by the Majordomo user/group, then majordomo won't be able to lock the file and thus will take a very long time to process commands. Section 4: Miscellaneous mailer problems ======================================== Subject: 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) From majordomo-users-owner Fri May 6 23:31:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14585; Fri, 6 May 1994 23:31:37 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14577; Fri, 6 May 1994 16:31:32 -0700 Message-Id: <199405062331.QAA14577@mycroft.GreatCircle.COM> To: majordomo-users Subject: I'm about to resend a whole bunch of Majordomo-Users messages Date: Fri, 06 May 1994 16:31:31 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm about to send a whole bunch of messages to Majordomo-Users, because almost nobody (including me!) has seen them yet... I had some disk problems a couple of weeks ago that messed up the Majordomo-Users list (and a couple of my other lists). Unfortunately, I didn't notice this until recently; I thought things had just been Real Quiet for once... :-) Sorry... -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 May 6 23:33:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14606; Fri, 6 May 1994 23:33:04 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14598; Fri, 6 May 1994 16:32:59 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id EAA05474; Thu, 28 Apr 1994 04:33:16 GMT Received: from kaukau.comp.vuw.ac.nz by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA05468; Wed, 27 Apr 1994 21:33:02 -0700 Received: from bats.comp.vuw.ac.nz (bats.comp.vuw.ac.nz [130.195.8.13]) by kaukau.comp.vuw.ac.nz (8.6.8/8.6.6) with ESMTP id QAA05162; Thu, 28 Apr 1994 16:33:01 +1200 From: Mark Davies Received: from localhost (mark@localhost) by bats.comp.vuw.ac.nz (8.6.8/8.6.6) with SMTP id QAA29103; Thu, 28 Apr 1994 16:33:00 +1200 Message-Id: <199404280433.QAA29103@bats.comp.vuw.ac.nz> To: Brent Chapman cc: pdc@lunch.asd.sgi.com (Paul Close), eichin@cygnus.com (Mark Eichin), spp@cis.ufl.edu, 0001020203@mcimail.com, majordomo-users@GreatCircle.COM Subject: Re: Fwd: hostile address In-reply-to: Your message of "Wed, 27 Apr 1994 21:05:38 MST." <199404280405.VAA05155@mycroft.GreatCircle.COM> X-Mailer: exmh version 1.3 4/7/94 Date: Thu, 28 Apr 1994 16:32:59 +1200 Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk From: Brent Chapman Date: Wed, 27 Apr 1994 21:05:38 -0700 > # Still hard to read. Why not simply > # > # # if there's a "|" or a "/" in it, it's hostile > # if (m^|/^) { > Because that matches, literally, "|/", not "|" or "/", which is the > intent of the thing. OK then: if (m^[|/]^) { cheers mark From majordomo-users-owner Fri May 6 23:34:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14623; Fri, 6 May 1994 23:34:07 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14615; Fri, 6 May 1994 16:34:02 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA09300; Thu, 28 Apr 1994 14:11:34 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA09292; Thu, 28 Apr 1994 07:10:33 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HBPFWEQY6O00002R@SYSWRK.UCIS.DAL.CA>; Thu, 28 Apr 1994 11:10:47 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HBPFW1JZLC0000LZ@AC.DAL.CA>; Thu, 28 Apr 1994 11:10:31 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA08255; Thu, 28 Apr 94 09:58:04 -0300 Date: Thu, 28 Apr 1994 09:58:03 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Multi-line commands? To: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9404281258.AA08255@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: 576 Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk A quick look at the documentation doesn't tell me how to send commands that extend over several lines. One of my list owners is trying to send messages like: approve PASSWORD list user@address.domain (firstname lastname) from a system that forcibly wraps lines, so that commands over about 76 characters long get broken in two. Is there a way around this? -- Bill Silvert at the Bedford Institute of Oceanography P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2 InterNet Address: silvert@biome.bio.ns.ca (the address bill@biome.bio.ns.ca is only for mailing lists) From majordomo-users-owner Fri May 6 23:35:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14668; Fri, 6 May 1994 23:35:08 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14660; Fri, 6 May 1994 16:35:04 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA09443; Thu, 28 Apr 1994 14:30:18 GMT Received: from mercury.SDL.usu.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA09429; Thu, 28 Apr 1994 07:29:57 -0700 Received: by mercury.SDL.usu.EDU (5.0/SMI-SVR4) id AA22322; Thu, 28 Apr 1994 08:30:21 +0700 Date: Thu, 28 Apr 1994 08:30:21 +0700 From: eyoung@mercury.SDL.usu.EDU (Ed Young) Message-Id: <9404281430.AA22322@mercury.SDL.usu.EDU> To: majordomo-users@GreatCircle.COM Subject: Unknown mailer error 5 X-Sun-Charset: US-ASCII content-length: 1986 Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Recently, I compiled perl4.036 with the new sparc c 3.x compiler and ever since majordomo gives me the following error; ----- Begin Included Message ----- >From Mailer-Daemon@zeus Thu Apr 28 08:07 MDT 1994 Subject: Returned mail: unknown mailer error 5 To: Content-Type: text Content-Length: 687 X-Lines: 18 ----- Transcript of session follows ----- resend: Permission denied 554 "|/opt/mail/majordomo/wrapper resend -p bulk -M 10000 -l test -f test-owner -h sdl.usu.edu -s test-outgoing"... unknown mailer error 5 ----- Unsent message follows ----- Received: from mercury.SDL.usu.EDU by zeus.SDL.usu.edu (5.0/SMI-SVR4) id AA22506; Thu, 28 Apr 1994 08:07:18 +0700 Errors-To: Received: by mercury.SDL.usu.EDU (5.0/SMI-SVR4) id AA22263; Thu, 28 Apr 1994 08:07:18 +0700 Date: Thu, 28 Apr 1994 08:07:18 +0700 From: eyoung@mercury (Ed Young) Message-Id: <9404281407.AA22263@mercury.SDL.usu.EDU> To: test@zeus.SDL.usu.edu Subject: test of majordomo Content-Length: 7 delete ----- End Included Message ----- The operating system is Solaris 2.3 and I was using perl4.036 compiled under SunOs 4.1.3 running in the binary compatability mode on Solaris. Any help would be greatly appreciated. Thank You, Ed Young +<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>+ | Ed.Young@sdl.usu.edu Ed Young -- Network Manager | | Space Dynamics Laboratory | | (801) 755-4352 [office] Computational Sciences Division | | (801) 770-0318 [cell] 1747 North Research Parkway | | (801) 755-4366 [fax] Logan, UT 84321 | | -------------------------------------------------------------------- | | Harried Call, " The NETWORK is DOWN !!! " | | 99% of the time, It is a computer OPERATOR malfunction!!! | +<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>+ From majordomo-users-owner Fri May 6 23:39:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14733; Fri, 6 May 1994 23:39:18 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14725; Fri, 6 May 1994 16:39:12 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA12600; Thu, 28 Apr 1994 17:01:08 GMT Received: from mercury.SDL.usu.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA12583; Thu, 28 Apr 1994 10:00:51 -0700 Received: by mercury.SDL.usu.EDU (5.0/SMI-SVR4) id AA22669; Thu, 28 Apr 1994 11:01:23 +0700 Date: Thu, 28 Apr 1994 11:01:23 +0700 From: eyoung@mercury.SDL.usu.EDU (Ed Young) Message-Id: <9404281701.AA22669@mercury.SDL.usu.EDU> To: majordomo-users@greatcircle.com Subject: Returned mail: unknown mailer error 5 X-Sun-Charset: US-ASCII content-length: 1507 Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thanks to all who replied. The actual problem was the execute permissions of perl. Much to my chagrin they were 700 rather than the 755 that i normally use. A special thanks to rouilj@cs.umb.edu who got me looking in the right area with his message. unknown mailer error 5 - This can be caused by a number of things all relating to the wrappers inability to execute the perl script. This can include: the perl script is not executable the location of the perl program specified with the #! line is incorrect the location where the wrapper looks for the perl scripts is not the location where the scripts are located. The current wrapper doesn't use the standard sendmail error codes, hence the "unknowm mailer error" annotation in the error message. A future wrapper version will use the appropriate errors from sysexits.h. Again thanks to all. Ed Young In my recent message: > Recently, I compiled perl4.036 with the new sparc c 3.x compiler > and ever since majordomo gives me the following error; > > ----- Begin Included Message ----- > > >From Mailer-Daemon@zeus Thu Apr 28 08:07 MDT 1994 > Subject: Returned mail: unknown mailer error 5 > To: > Content-Type: text > Content-Length: 687 > X-Lines: 18 > > ----- Transcript of session follows ----- > resend: Permission denied > 554 "|/opt/mail/majordomo/wrapper resend -p bulk -M 10000 -l test - > f test-owner -h sdl.usu.edu -s test-outgoing"... unknown mailer err > or 5 > From majordomo-users-owner Fri May 6 23:40:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14751; Fri, 6 May 1994 23:40:20 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14743; Fri, 6 May 1994 16:40:15 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA17974; Thu, 28 Apr 1994 17:42:44 GMT Received: from gatekeeper.mcimail.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA17967; Thu, 28 Apr 1994 10:42:16 -0700 Received: by gatekeeper.mcimail.com (5.65/fma-120691); id AA22473; Thu, 28 Apr 94 12:43:32 -0500 Received: by MCIGATEWAY.MCIMail.com id cw28146; 28 Apr 94 17:34 GMT Received: from mcimail.com by MCIGATEWAY.MCIMail.com id bk07725; 27 Apr 94 20:23 GMT Date: Wed, 27 Apr 94 15:29 EST From: Pat Crawford <0001020203@mcimail.com> To: majordomo-users Subject: Fwd: Return Receipt... Message-Id: <15940427202951/0001020203DB2EM@mcimail.com> Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk All: Seems to be my week. This just came from a list subscriber. Any comments? Pat Crawford MCI Communications ------- Forwarded Message Received: from gatekeeper.mcimail.com by herman.messaging.cs.mci.com id aa23982; 26 Apr 94 8:36 MDT Received: by gatekeeper.mcimail.com (5.65/fma-120691); id AA05354; Tue, 26 Apr 94 09:36:57 -0500 Received: by us2.navo.navy.mil id AA26226 (5.67b/IDA-1.5 for mcimail-info-owner@gatekeeper.mcimail.com); Tue, 26 Apr 1994 09:36:34 -0500 Date: Tue, 26 Apr 1994 09:36:34 -0500 From: don newcomb Message-Id: <199404261436.AA26226@us2.navo.navy.mil> To: mcimail-info-owner@gatekeeper.mcimail.com Subject: Majordomo and return reciepts. Reply-To: newcomb@pops.navo.navy.mil FYI, Majordomo gives a rather strange response when a return reciept request is added to a mail header. >From MAILER-DAEMON@gatekeeper.mcimail.com Tue Apr 26 14:30:12 1994 >Received: from us2.navo.navy.mil (us2) by us1.navo.navy.mil with SMTP id AA13189 > (5.67b/IDA-1.5 for ); Tue, 26 Apr 1994 09:30:59 -0500 >Received: from gatekeeper.mcimail.com by us2.navo.navy.mil with SMTP id AA26151 > (5.67b/IDA-1.5 for ); Tue, 26 Apr 1994 09:29:58 -0500 >Received: by gatekeeper.mcimail.com (5.65/fma-120691); > id AA04887; Tue, 26 Apr 94 09:30:12 -0500 >Date: Tue, 26 Apr 94 09:30:12 -0500 >From: MAILER-DAEMON@gatekeeper.mcimail.com (Mail Delivery Subsystem) >Subject: Returned mail: Return receipt >Message-Id: <9404261430.AA04887@gatekeeper.mcimail.com> >To: newcomb@us2.navo.navy.mil >Status: R > > ----- Transcript of session follows ----- >Can't unlink /tmp/majordomo.4889.*: No such file or directory at /usr/users/majordom/majordomo line 1225, <> line 2. >get_config(/usr/users/majordom/lists, mcimail-info) >adding site-wide defaults >Overriding with existing config files >parsing config get_config(/usr/users/majordom/lists, mcimail-info) > > ----- Recipients of this delivery ----- >Sent successfully: > > "|/usr/users/majordom/wrapper majordomo" > > ----- Message header follows ----- >Received: by gatekeeper.mcimail.com (5.65/fma-120691); > id AA04885; Tue, 26 Apr 94 09:30:12 -0500 >Received: by us2.navo.navy.mil id AA26147 > (5.67b/IDA-1.5 for Majordomo@gatekeeper.mcimail.com); Tue, 26 Apr 1994 09:29:49 -0500 >Date: Tue, 26 Apr 1994 09:29:49 -0500 >From: don newcomb >Message-Id: <199404261429.AA26147@us2.navo.navy.mil> >To: Majordomo >Subject: Re: Welcome to mcimail-info >Reply-To: newcomb@pops.navo.navy.mil >Return-Receipt-To: newcomb@us2.navo.navy.mil > - ---- Donald R. Newcomb * newcomb@pops.navo.navy.mil Naval Oceanographic Office * drn@fiddle.noo.navy.mil Stennis Space Center, MS 39522 * Voice: (601) 688-5998 FAX: (601) 688-5485 * DSN: 485-5998 ------- End of Forwarded Message From majordomo-users-owner Fri May 6 23:41:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14767; Fri, 6 May 1994 23:41:23 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14759; Fri, 6 May 1994 16:41:18 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA19838; Thu, 28 Apr 1994 19:52:00 GMT Received: from chronos.synopsys.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA19821; Thu, 28 Apr 1994 12:51:40 -0700 Received: from gaea.synopsys.com by chronos.synopsys.com with SMTP id AA15376 (5.65c/IDA-1.4.4 for ); Thu, 28 Apr 1994 12:52:08 -0700 Received: from mango.synopsys.com (mango-backbone.synopsys.com) by gaea.synopsys.com with SMTP id AA11800 (5.65c/IDA-1.4.4 for ); Thu, 28 Apr 1994 12:52:05 -0700 Received: (from arnold@localhost) by mango.synopsys.com (8.6.9/8.6.9) id MAA20834 for majordomo-users@greatcircle.com; Thu, 28 Apr 1994 12:52:04 -0700 Date: Thu, 28 Apr 1994 12:52:04 -0700 From: Arnold de Leon Message-Id: <199404281952.MAA20834@mango.synopsys.com> To: majordomo-users@greatcircle.com Subject: outgoing aliases and protecting them Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Majordomo uses "hidden" aliases to actually send mail to the members of the lists (typically listname-out). Anyone who knows the name of the list can send mail to the members directly. Sendmail version 8 makes it easier for recipients to discover this name since it is very good at recording envelope information in the "Received" headers. Protecting this list becomes more important with moderated lists. My current idea for a "solution" is give majordomo a separate aliase file. The separte alise file can use "listname" as the address for resend to use for actually delivering mail. When resend invokes sendmail it will use the alternate (private) alias file. Are there better way of doing this? What about having resend talk to port 25 directly and expand the alias itself? Comments, ideas? arnold From majordomo-users-owner Fri May 6 23:42:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14783; Fri, 6 May 1994 23:42:25 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14775; Fri, 6 May 1994 16:42:20 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA20017; Thu, 28 Apr 1994 20:11:58 GMT Received: from chronos.synopsys.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA20011; Thu, 28 Apr 1994 13:11:46 -0700 Received: from gaea.synopsys.com by chronos.synopsys.com with SMTP id AA15746 (5.65c/IDA-1.4.4 for ); Thu, 28 Apr 1994 13:12:19 -0700 Received: from mango.synopsys.com (mango-backbone.synopsys.com) by gaea.synopsys.com with SMTP id AA12595 (5.65c/IDA-1.4.4 for ); Thu, 28 Apr 1994 13:12:18 -0700 Received: (from arnold@localhost) by mango.synopsys.com (8.6.9/8.6.9) id NAA20900 for majordomo-users@greatcircle.com; Thu, 28 Apr 1994 13:12:17 -0700 Date: Thu, 28 Apr 1994 13:12:17 -0700 From: Arnold de Leon Message-Id: <199404282012.NAA20900@mango.synopsys.com> To: majordomo-users@greatcircle.com Subject: pre approved postings for moderated lists Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk resend assumes that it finds an "Approved" header in the body that the header is about to follow. Unfortunately this may not always be true. In particular I would like to have several lists moderated by non unix types. These lists are typically announcement type lists. The indiviual making the initial posting is typically going to be the moderator. Unfortunately they won't have easy means of inserting an "Approved" line as part of the header. But if they insert the "Approved" line in the body resend will expect headers to follow. Since there won't be any, the result is missing headers. I am considering a couple of alternatives: Create an approve like header for use in the body that does not look for headers in the body. For example "List-Approval:" Change the behaviour of resend. If it finds an "Approved" header look for headers immediately following, if it finds some then use them otherwise keep what it has. arnold From majordomo-users-owner Fri May 6 16:43:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14695; Fri, 6 May 1994 23:36:11 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14687; Fri, 6 May 1994 16:36:05 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA09618; Thu, 28 Apr 1994 14:58:17 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA09610; Thu, 28 Apr 1994 07:57:28 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.5/8.6.5) with ESMTP id KAA13060; Thu, 28 Apr 1994 10:57:25 -0400 Message-Id: <199404281457.KAA13060@bosnia.pop.psu.edu> To: eyoung@mercury.SDL.usu.EDU (Ed Young) cc: majordomo-users@GreatCircle.COM Subject: Re: Unknown mailer error 5 In-reply-to: Your message of "Thu, 28 Apr 1994 08:30:21 +0700." <9404281430.AA22322@mercury.SDL.usu.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: Thu, 28 Apr 1994 10:57:24 -0400 From: David Barr Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9404281430.AA22322@mercury.SDL.usu.EDU>, Ed Young writes: >Recently, I compiled perl4.036 with the new sparc c 3.x compiler >and ever since majordomo gives me the following error; > >----- Begin Included Message ----- > ----- Transcript of session follows ----- >resend: Permission denied Check the permissions on resend. --Dave From majordomo-users-owner Fri May 6 23:53:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15061; Fri, 6 May 1994 23:53:38 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14883; Fri, 6 May 1994 16:44:27 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA20164; Thu, 28 Apr 1994 20:30:37 GMT Received: from terminus.cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA20158; Thu, 28 Apr 1994 13:30:30 -0700 Received: by terminus.cs.umb.edu id AA04771 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Thu, 28 Apr 1994 13:38:49 -0400 From: "John P. Rouillard" Message-Id: <199404281738.AA04771@terminus.cs.umb.edu> Subject: Multi line commands Date: Thu, 28 Apr 1994 13:38:48 -0400 (EDT) To: majordomo-users@greatcircle.com X-Mailer: fastmail [version 2.4 PL17] Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9404281258.AA08255@biome.bio.ns.ca>, Bill Silvert writes: > A quick look at the documentation doesn't tell me how to send commands > that extend over several lines. > > One of my list owners is trying to send messages like: > > approve PASSWORD list user@address.domain (firstname lastname) > > from a system that forcibly wraps lines, so that commands over about 76 > characters long get broken in two. Is there a way around this? The newest version (1.90b2/1.90) supports splitting commands across lines. I had to do it for a client that runs QuickMail (blecherous package if there ever was one). >From the README: Command lines can be continued by using a \ at the end of the line. -- John John Rouillard Special Projects Volunteer 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 May 6 17:28:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15143; Fri, 6 May 1994 23:56:19 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA15121; Fri, 6 May 1994 16:56:06 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id EAA27042; Fri, 29 Apr 1994 04:07:07 GMT Received: from halcyon.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA27033; Thu, 28 Apr 1994 21:06:58 -0700 Received: by halcyon.com id AA13153 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Thu, 28 Apr 1994 21:07:31 -0700 Date: Thu, 28 Apr 1994 21:07:31 -0700 (PDT) From: Norm Gregory To: majordomo-users@greatcircle.com In-Reply-To: <199404290341.UAA26645@mycroft.GreatCircle.COM> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk lists From majordomo-users-owner Fri May 6 17:33:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15208; Fri, 6 May 1994 23:58:24 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA15198; Fri, 6 May 1994 16:58:13 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA07391; Sat, 30 Apr 1994 01:28:47 GMT Received: from halcyon.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA07385; Fri, 29 Apr 1994 18:28:39 -0700 Received: by halcyon.com id AA07289 (5.65c/IDA-1.4.4 for users ); Fri, 29 Apr 1994 18:09:05 -0700 Date: Fri, 29 Apr 1994 18:09:04 -0700 (PDT) From: "Dallas R. Stafford" Subject: list manager To: users Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I want to run majordomo on my slip but perhaps I should become a list manager first. Is there someone who would let me temporarily manage a few lists on your machine until I know what I'm doing. I'm trying to learn unix and sendmail and majordomo all at the same time and I've got eager subscribers waiting for me to get it running. Dallas \(^o^)/ Cheers From majordomo-users-owner Fri May 6 17:41:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14799; Fri, 6 May 1994 23:43:27 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14791; Fri, 6 May 1994 16:43:23 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA20140; Thu, 28 Apr 1994 20:29:28 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA20134; Thu, 28 Apr 1994 13:29:22 -0700 Received: by netcom.com (8.6.8.1/SMI-4.1/Netcom) id NAA21130; Thu, 28 Apr 1994 13:31:10 -0700 Date: Thu, 28 Apr 1994 13:31:09 -0700 (PDT) From: James Cook Subject: Re: outgoing aliases and protecting them To: Arnold de Leon cc: majordomo-users@GreatCircle.COM In-Reply-To: <199404281952.MAA20834@mango.synopsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Thu, 28 Apr 1994, Arnold de Leon wrote: > Majordomo uses "hidden" aliases to actually send mail > to the members of the lists (typically listname-out). > > Anyone who knows the name of the list can send mail to > the members directly. Sendmail version 8 makes it easier > for recipients to discover this name since it is very > good at recording envelope information in the > "Received" headers. > > Protecting this list becomes more important > with moderated lists. > Thank for pointing out this additional "leak" in security for majordomo lists. Are there any other good list management programs which don't have these leaks and are practical to switch to? James From majordomo-users-owner Fri May 6 17:43:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15052; Fri, 6 May 1994 23:53:03 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA15044; Fri, 6 May 1994 16:52:59 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA26135; Fri, 29 Apr 1994 01:43:03 GMT Received: from sws1.ctd.ornl.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA26129; Thu, 28 Apr 1994 18:42:52 -0700 Received: (from de5@localhost) by sws1.ctd.ornl.gov (8.6.9/8.6.9) id VAA22643; Thu, 28 Apr 1994 21:43:07 -0400 Date: Thu, 28 Apr 1994 21:43:07 -0400 From: Dave Sill Message-Id: <199404290143.VAA22643@sws1.ctd.ornl.gov> To: James Cook Cc: Arnold de Leon , majordomo-users@GreatCircle.COM Subject: Re: outgoing aliases and protecting them In-Reply-To: References: <199404281952.MAA20834@mango.synopsys.com> Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >Thank for pointing out this additional "leak" in security for majordomo >lists. Are there any other good list management programs which don't have >these leaks and are practical to switch to? YEH D00D, I HERE LISTPROK IZ REELY K00L!!!! -- Dave Sill (de5@ornl.gov) I dream of a televisionland where it will be Martin Marietta Energy Systems as hard for a network to expose us to violence Workstation Support as it is for me to tell someone they have spinach on their teeth. --Paula Poundstone URL http://www.dec.com/pub/DEC/DECinfo/html/dsill.html From majordomo-users-owner Fri May 6 17:49:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14705; Fri, 6 May 1994 23:37:12 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14697; Fri, 6 May 1994 16:37:07 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA09661; Thu, 28 Apr 1994 15:01:46 GMT Received: from sodium.mps.ohio-state.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA09655; Thu, 28 Apr 1994 08:01:39 -0700 Received: from localhost (parker@localhost) by sodium.mps.ohio-state.edu (8.6.4/8.6.4) id LAA04516 for majordomo-users@GreatCircle.Com; Thu, 28 Apr 1994 11:01:51 -0400 Date: Thu, 28 Apr 1994 11:01:51 -0400 From: Steve Parker Message-Id: <199404281501.LAA04516@sodium.mps.ohio-state.edu> To: majordomo-users@GreatCircle.Com Subject: Unknown mailer error... Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Ed, Ed Young recently wrote: > ----- Transcript of session follows ----- > resend: Permission denied > 554 "|/opt/mail/majordomo/wrapper resend -p bulk -M 10000 -l test -f test-owner -h sdl.usu.edu -s test-outgoing"... unknown mailer error 5 > The operating system is Solaris 2.3 and I was using perl4.036 compiled under > SunOs 4.1.3 running in the binary compatability mode on Solaris. although I am not running solaris 2.3, I did get the same error. My problems was that resend did not have execute permissions, try ls -l /opt/mail/majordomo/resend And see if ownership or permissions are incorrect. Dr. Steven Parker parker@mps.ohio-state.edu Dept of Chemistry 201 McPherson Lab. Ohio State University 614-292-5042 From majordomo-users-owner Fri May 6 17:52:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14952; Fri, 6 May 1994 23:47:53 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14935; Fri, 6 May 1994 16:47:42 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA20539; Thu, 28 Apr 1994 21:18:33 GMT Received: from chronos.synopsys.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA20531; Thu, 28 Apr 1994 14:18:19 -0700 Received: from gaea.synopsys.com by chronos.synopsys.com with SMTP id AA16964 (5.65c/IDA-1.4.4 for ); Thu, 28 Apr 1994 14:18:49 -0700 Received: from mango.synopsys.com (mango-backbone.synopsys.com) by gaea.synopsys.com with SMTP id AA15575 (5.65c/IDA-1.4.4 for ); Thu, 28 Apr 1994 14:18:48 -0700 Received: (from arnold@localhost) by mango.synopsys.com (8.6.9/8.6.9) id OAA21364 for majordomo-users@greatcircle.com; Thu, 28 Apr 1994 14:18:47 -0700 Date: Thu, 28 Apr 1994 14:18:47 -0700 From: Arnold de Leon Message-Id: <199404282118.OAA21364@mango.synopsys.com> In-Reply-To: Andy Finkenstadt "Re: outgoing aliases and protecting them" (Apr 28, 4:39pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: majordomo-users@greatcircle.com Subject: Re: outgoing aliases and protecting them Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Let me add that most configurations of sendmail do *not* record envelope information in headers. You should know what your system does. Sendmail V8 does by default but it also changeable. In any case you are still vulnernable someone guessing the name of your real outgoing list. I suspect most majordomo servers are setup following the examples. This means most outgoing lists are named "listname-outgoing". If you have private lists you can use "obscure" names for the outgoing lists and just make sure that sendmail doesn't reveal them. I suspect that the best longterm fix is for majordomo to open port 25 to some machine and send mail that way. arnold From majordomo-users-owner Fri May 6 17:53:34 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15079; Fri, 6 May 1994 23:54:05 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14920; Fri, 6 May 1994 16:46:38 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA20270; Thu, 28 Apr 1994 20:44:32 GMT Received: from panix.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA20264; Thu, 28 Apr 1994 13:44:18 -0700 Received: by panix.com id AA10399 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Thu, 28 Apr 1994 16:39:14 -0400 From: Andy Finkenstadt Message-Id: <199404282039.AA10399@panix.com> Subject: Re: outgoing aliases and protecting them To: jcook@netcom.com (James Cook) Date: Thu, 28 Apr 1994 16:39:13 -0400 (EDT) Cc: arnold@Synopsys.COM, majordomo-users@greatcircle.com In-Reply-To: from "James Cook" at Apr 28, 94 01:31:09 pm Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1020 Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > On Thu, 28 Apr 1994, Arnold de Leon wrote: > > Anyone who knows the name of the list can send mail to > > the members directly. Sendmail version 8 makes it easier > > for recipients to discover this name since it is very > > good at recording envelope information in the > > "Received" headers. > > > Thank for pointing out this additional "leak" in security for majordomo > lists. Are there any other good list management programs which don't have > these leaks and are practical to switch to? > Excuse me.... majordomo is not the culprit here. Sendmail is. If you want perfect security on the Internet, pull the plug. Or do as I do: my site is(was/will be) UUCP connected and unless you can somehow gain physical access to teh console, there is no way you will obtain the secret list name used for outgoing mail. Andy -- andy@genie.geis.com | Andy Finkenstadt, GEnie Sysop, GEnie Postmaster andy@tml.com | Systems Engineer, TML Information Services, Inc. genie@panix.com | +1 718-793-9099 From majordomo-users-owner Fri May 6 17:57:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15108; Fri, 6 May 1994 23:55:14 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA15096; Fri, 6 May 1994 16:55:04 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id DAA26653; Fri, 29 Apr 1994 03:41:42 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA26645; Thu, 28 Apr 1994 20:41:34 -0700 Message-Id: <199404290341.UAA26645@mycroft.GreatCircle.COM> To: Michael Myers cc: majordomo-users@GreatCircle.COM Subject: Re: outgoing aliases and protecting them In-reply-to: Your message of Thu, 28 Apr 1994 19:27:00 -0700 (PDT) Date: Thu, 28 Apr 1994 20:41:33 -0700 From: Brent Chapman Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Michael Myers writes: # I don't want to start any type of "religious" war here so I'll clarify my # position right at the start: I don't really like listproc (especially now # that it's been sold) but I'm a little hesitant to jump into a new system # and the fact that Majordomo is written in perl worries me: I don't write # perl and I've heard it's rather a resource hog. I'll leave the rest for other folks to answer, but I'll say something about the resource issue... Mycroft.GreatCircle.COM is a Sun 3/60 (about 3 MIPS) running SunOS 4.1.1 and Sendmail 8.*, connected to the Internet via a 9.6 kb/s dialup link. There are 22 mailing lists here, with a total of over 4000 subscribers, and a total list volume of something like 1000 messages per month. The biggest of these, the Firewalls mailing list, has over 1700 subscribers on it and accounts for about 400 messages per month. Majordomo here handles some 1500 or so requests (each of which may contain multiple commands) per month, on average. I have no performance problems with Majordomo. I generally don't even notice it running on the machine, and this is my main work environment. -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 May 6 18:02:02 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15091; Fri, 6 May 1994 23:54:56 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14912; Fri, 6 May 1994 16:45:35 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA20215; Thu, 28 Apr 1994 20:39:00 GMT Received: from mail.teleport.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA20208; Thu, 28 Apr 1994 13:38:51 -0700 Received: by mail.teleport.com (/\==/\ Smail3.1.28.1 #28.2) id ; Thu, 28 Apr 94 13:39 PDT Date: Thu, 28 Apr 1994 13:39:19 -0700 (PDT) From: Paradise Cowgirl Subject: Re: pre approved postings for moderated lists To: Arnold de Leon cc: majordomo-users@GreatCircle.COM In-Reply-To: <199404282012.NAA20900@mango.synopsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Thu, 28 Apr 1994, Arnold de Leon wrote: > resend assumes that it finds an "Approved" header in the > body that the header is about to follow. > Unfortunately this may not always be true. > > In particular I would like to have several lists > moderated by non unix types. These lists are typically > announcement type lists. The indiviual making the > initial posting is typically going to be the moderator. > Unfortunately they won't have easy means of inserting > an "Approved" line as part of the header. > > But if they insert the "Approved" line in the body > resend will expect headers to follow. Since there > won't be any, the result is missing headers. > The way around this is for the moderator to use the built in process of the moderator sending the announcement to the list (without doing any thing for approval) and used the bounced back version which will include the original headers. Yes, this is an extra step :-) -- ------ Paradise Cowgirl - minerva@teleport.com - minerva@netcom.com \ --/--- \ \/ / Don't support discrimination and bigotry -- don't support the OCA! \/\ / http://vector.casti.com/QRD/.html/People/Darci.html \/ "What would happen if the far right held a campaign and nobody came?" -Lee Lynch From majordomo-users-owner Fri May 6 18:03:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14990; Fri, 6 May 1994 23:49:59 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14982; Fri, 6 May 1994 16:49:51 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA20711; Thu, 28 Apr 1994 21:41:12 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA20705; Thu, 28 Apr 1994 14:41:03 -0700 Received: by netcom.com (8.6.8.1/SMI-4.1/Netcom) id OAA24293; Thu, 28 Apr 1994 14:42:48 -0700 Date: Thu, 28 Apr 1994 14:42:48 -0700 (PDT) From: James Cook Subject: Re: outgoing aliases and protecting them To: Andy Finkenstadt cc: arnold@Synopsys.COM, majordomo-users@GreatCircle.COM In-Reply-To: <199404282039.AA10399@panix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Thu, 28 Apr 1994, Andy Finkenstadt wrote: > > On Thu, 28 Apr 1994, Arnold de Leon wrote: > > > Anyone who knows the name of the list can send mail to > > > the members directly. Sendmail version 8 makes it easier > > > for recipients to discover this name since it is very > > > good at recording envelope information in the > > > "Received" headers. > > > > > Thank for pointing out this additional "leak" in security for majordomo > > lists. Are there any other good list management programs which don't have > > these leaks and are practical to switch to? > > > Excuse me.... majordomo is not the culprit here. Sendmail is. > > If you want perfect security on the Internet, pull the plug. Or do > as I do: my site is(was/will be) UUCP connected and unless you can > somehow gain physical access to teh console, there is no way you will > obtain the secret list name used for outgoing mail. > If by pull the plug you mean stop participating, that's not practical. I have a dial up account, not a UUCP or slip or PPP or something similar. What would I have to do and know, and how much more time must I invest in maintaining hardware and software by having "my own site" or the UUCP you refer to? Some of us, like me, are not computer wizards and don't know which pieces of the puzzle belong where to effect our goals. I already spend a lot of time running a mail list. I wonder how much more time having my own site entails? Thanks. James From majordomo-users-owner Fri May 6 18:05:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15082; Fri, 6 May 1994 23:54:09 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA15071; Fri, 6 May 1994 16:54:01 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA26312; Fri, 29 Apr 1994 02:27:07 GMT Received: from earth.willamette.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA26306; Thu, 28 Apr 1994 19:26:50 -0700 Received: from minerva.willamette.edu (mmyers@minerva.willamette.edu [158.104.64.1]) by earth.willamette.edu (8.6.8.1/8.6.4) with ESMTP id TAA29934 for ; Thu, 28 Apr 1994 19:26:52 -0700 Received: (mmyers@localhost) by minerva.willamette.edu (8.6.7/8.6.4) id TAA29864; Thu, 28 Apr 1994 19:27:01 -0700 Date: Thu, 28 Apr 1994 19:27:00 -0700 (PDT) From: Michael Myers Subject: Re: outgoing aliases and protecting them To: majordomo-users@GreatCircle.COM In-Reply-To: <199404290143.VAA22643@sws1.ctd.ornl.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Despite it's moronic humor, this message actually points to something I'm interested in. We currently run a listproc at our site (I'm in charge of it). Just a few weeks ago, I noticed that net-happenings moved to majordomo, which made me decide to at least evaluate it as well. My question is this: are there any people here who's had experience with both packages and can offer an un-biased recount of their experiences? I don't want to start any type of "religious" war here so I'll clarify my position right at the start: I don't really like listproc (especially now that it's been sold) but I'm a little hesitant to jump into a new system and the fact that Majordomo is written in perl worries me: I don't write perl and I've heard it's rather a resource hog. These are the sorts of issues I'm interested in. Any one else? Thanks, - Mike On Thu, 28 Apr 1994, Dave Sill wrote: > >Thank for pointing out this additional "leak" in security for majordomo > >lists. Are there any other good list management programs which don't have > >these leaks and are practical to switch to? > > YEH D00D, I HERE LISTPROK IZ REELY K00L!!!! > > -- > Dave Sill (de5@ornl.gov) I dream of a televisionland where it will be > Martin Marietta Energy Systems as hard for a network to expose us to violence > Workstation Support as it is for me to tell someone they have > spinach on their teeth. --Paula Poundstone > URL http://www.dec.com/pub/DEC/DECinfo/html/dsill.html > From majordomo-users-owner Fri May 6 18:10:34 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15026; Fri, 6 May 1994 23:52:01 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA15018; Fri, 6 May 1994 16:51:57 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA21319; Thu, 28 Apr 1994 22:22:29 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA21312; Thu, 28 Apr 1994 15:22:21 -0700 Message-Id: <199404282222.PAA21312@mycroft.GreatCircle.COM> To: "John P. Rouillard" cc: Arnold de Leon , majordomo-users@greatcircle.com Subject: Re: outgoing aliases and protecting them In-reply-to: Your message of Thu, 28 Apr 1994 17:35:54 -0400 Date: Thu, 28 Apr 1994 15:22:19 -0700 From: Brent Chapman Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "John P. Rouillard" writes: # In message <199404281952.MAA20834@mango.synopsys.com>, Arnold de Leon writes: # > Majordomo uses "hidden" aliases to actually send mail # > to the members of the lists (typically listname-out). # > # > Anyone who knows the name of the list can send mail to # > the members directly. Sendmail version 8 makes it easier # > for recipients to discover this name since it is very # > good at recording envelope information in the # > "Received" headers. # # Actually you could always get it because resend has the outgoing list # name right in the command invocation which is viewable with SMTP vrfy. Depends on the invocation of "resend". If you use the "@argfile" mechanism (which allows you to put all the arguments for "resend" into a file, then reference the filename), then you can put the outgoing list name in the argfile, where sendmail won't see it. I added the argfile capability because I had several lists whose "resend" arguments were growing beyond 256 characters, but it's also very effective at hiding information from sendmail. For instance, the "majordomo-users" aliases here are: majordomo-users: "|/usr/local/mail/majordomo/wrapper resend @/usr/local/mail/lists/majordomo-users.resend" majordomo-users-outgoing: :include:/usr/local/mail/lists/majordomo-users and the file /usr/local/mail/lists/majordomo-users.resend contains: -a /usr/local/mail/lists/majordomo-users.passwd -b Majordomo-Users-Approval@GreatCircle.COM -p bulk -M 10000 -l Majordomo-Users -f Majordomo-Users-Owner -h GreatCircle.COM -s majordomo-users-outgoing -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 May 6 18:12:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14964; Fri, 6 May 1994 23:48:54 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14954; Fri, 6 May 1994 16:48:47 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA20658; Thu, 28 Apr 1994 21:35:52 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA20652; Thu, 28 Apr 1994 14:35:39 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA00948 (5.65c/IDA-1.4.4 for ); Thu, 28 Apr 1994 17:35:55 -0400 Message-Id: <199404282135.AA00948@cs.umb.edu> To: Arnold de Leon Cc: majordomo-users@greatcircle.com Subject: Re: outgoing aliases and protecting them In-Reply-To: Your message of "Thu, 28 Apr 1994 12:52:04 PDT." <199404281952.MAA20834@mango.synopsys.com> Date: Thu, 28 Apr 1994 17:35:54 -0400 From: "John P. Rouillard" Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi Arnold: In message <199404281952.MAA20834@mango.synopsys.com>, Arnold de Leon writes: > Majordomo uses "hidden" aliases to actually send mail > to the members of the lists (typically listname-out). > > Anyone who knows the name of the list can send mail to > the members directly. Sendmail version 8 makes it easier > for recipients to discover this name since it is very > good at recording envelope information in the > "Received" headers. Actually you could always get it because resend has the outgoing list name right in the command invocation which is viewable with SMTP vrfy. > My current idea for a "solution" is give majordomo > a separate aliase file. The separte alise file > can use "listname" as the address for resend to > use for actually delivering mail. When resend > invokes sendmail it will use the alternate (private) > alias file. I proposed this a few days ago on majordomo workers. If the sendmail won't allow changing alias files using -o on the command line, have it use a different config file. > Are there better way of doing this? > What about having resend talk to port 25 directly and > expand the alias itself? One problem is that the incomming addresses would show up in the received headers. You know "Received: from localhost for rouilj@cs.umb.edu ...". Sendmail 8 and most versions of IDA supply this as do sgi default version (IDA based), and some svr4 based sendmails. Sadly one of the features of majordomo is easy setup even for those that are sendmail illiterate. Also what about the other SMTP mailers that allow expn/vrfy? > Comments, ideas? The split alias idea is the only solution I can see. We have to allow sendmail to expand the alias otherwise it can nicely put info into the received headers that doesn't belong there. -- John John Rouillard Special Projects Volunteer 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 May 6 18:13:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15005; Fri, 6 May 1994 23:50:59 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14997; Fri, 6 May 1994 16:50:54 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA20848; Thu, 28 Apr 1994 21:59:22 GMT Received: from chronos.synopsys.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA20842; Thu, 28 Apr 1994 14:59:12 -0700 Received: from gaea.synopsys.com by chronos.synopsys.com with SMTP id AA17710 (5.65c/IDA-1.4.4 for ); Thu, 28 Apr 1994 14:59:39 -0700 Received: from mango.synopsys.com (mango-backbone.synopsys.com) by gaea.synopsys.com with SMTP id AA17570 (5.65c/IDA-1.4.4); Thu, 28 Apr 1994 14:59:36 -0700 Received: (from arnold@localhost) by mango.synopsys.com (8.6.9/8.6.9) id OAA21630; Thu, 28 Apr 1994 14:59:35 -0700 Date: Thu, 28 Apr 1994 14:59:35 -0700 From: Arnold de Leon Message-Id: <199404282159.OAA21630@mango.synopsys.com> In-Reply-To: "John P. Rouillard" "Re: outgoing aliases and protecting them" (Apr 28, 5:35pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "John P. Rouillard" , Arnold de Leon Subject: Re: outgoing aliases and protecting them Cc: majordomo-users@greatcircle.com Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Apr 28, 5:35pm, "John P. Rouillard" wrote: } Subject: Re: outgoing aliases and protecting them } } Actually you could always get it because resend has the outgoing list } name right in the command invocation which is viewable with SMTP vrfy. } I thought in V8 verify only told you if an address was ok (expn expanded). Of course in V8 you can turn off expn. Of course in my case mjd runs inside my firewall on another machine so expn and vrfy won't do people any good (they'll be talking to my firewall) } } I proposed this a few days ago on majordomo workers. If the sendmail } won't allow changing alias files using -o on the command line, have it } use a different config file. } Ah, I joined the workers list only yesterday. I forgot to retrieve the archive. V8 will allow you to change alias files, unfortunately you lose priviledges when you do that so you can't write in the mail queue. I am considering using a wrapper around the sendmail that resend invokes. } > Are there better way of doing this? } > What about having resend talk to port 25 directly and } > expand the alias itself? } } One problem is that the incomming addresses would show up in the } received headers. You know "Received: from localhost for } rouilj@cs.umb.edu ...". Sendmail 8 and most versions of IDA supply } this as do sgi default version (IDA based), and some svr4 based } sendmails. Sadly one of the features of majordomo is easy setup even } for those that are sendmail illiterate. Also what about the other SMTP } mailers that allow expn/vrfy? } I don't think this is the case if there are multiple "rcpt to lines" (at least with V8 sendmail). I still think the port 25 option may still turn out to be the best longterm option. majordomo would be able to keep its subscriber lists to itself and no sendmail hacking. }-- End of excerpt from "John P. Rouillard" arnold From majordomo-users-owner Fri May 6 18:14:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14723; Fri, 6 May 1994 23:38:15 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14715; Fri, 6 May 1994 16:38:10 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA09695; Thu, 28 Apr 1994 15:08:05 GMT Received: from weber.ucsd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA09682; Thu, 28 Apr 1994 08:07:49 -0700 Received: from weber.ucsd.edu (corrigan@localhost [127.0.0.1]) by weber.ucsd.edu (8.6.9/8.6.9) with ESMTP id IAA22340; Thu, 28 Apr 1994 08:08:11 -0700 Message-Id: <199404281508.IAA22340@weber.ucsd.edu> To: eyoung@mercury.SDL.usu.EDU (Ed Young) Cc: majordomo-users@GreatCircle.COM Reply-To: majordomo-users@GreatCircle.COM Subject: Re: Unknown mailer error 5 In-reply-to: Your message of "Thu, 28 Apr 1994 08:30:21 +0700." <9404281430.AA22322@mercury.SDL.usu.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22336.767545690.1@weber.ucsd.edu> Date: Thu, 28 Apr 1994 08:08:10 -0700 From: "Michael J. Corrigan" Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk wrapper cannot run resend is the problem. Things to check: 1. permissions on resend - are they at least 555 ? 2. W_BIN in the Makefile is set to the directory in which resend lies 3. perl is in /usr/local/bin -mike > Recently, I compiled perl4.036 with the new sparc c 3.x compiler > and ever since majordomo gives me the following error; > > ----- Begin Included Message ----- > > From Mailer-Daemon@zeus Thu Apr 28 08:07 MDT 1994 > Subject: Returned mail: unknown mailer error 5 > To: > Content-Type: text > Content-Length: 687 > X-Lines: 18 > > ----- Transcript of session follows ----- > resend: Permission denied > 554 "|/opt/mail/majordomo/wrapper resend -p bulk -M 10000 -l test -f test-own er -h sdl.usu.edu -s test-outgoing"... unknown mailer error 5 > > ----- Unsent message follows ----- > Received: from mercury.SDL.usu.EDU by zeus.SDL.usu.edu (5.0/SMI-SVR4) > id AA22506; Thu, 28 Apr 1994 08:07:18 +0700 > Errors-To: > Received: by mercury.SDL.usu.EDU (5.0/SMI-SVR4) > id AA22263; Thu, 28 Apr 1994 08:07:18 +0700 > Date: Thu, 28 Apr 1994 08:07:18 +0700 > From: eyoung@mercury (Ed Young) > Message-Id: <9404281407.AA22263@mercury.SDL.usu.EDU> > To: test@zeus.SDL.usu.edu > Subject: test of majordomo > Content-Length: 7 > > delete > > > ----- End Included Message ----- > The operating system is Solaris 2.3 and I was using perl4.036 compiled under > SunOs 4.1.3 running in the binary compatability mode on Solaris. > > Any help would be greatly appreciated. > > Thank You, > > Ed Young > +<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>+ > | Ed.Young@sdl.usu.edu Ed Young -- Network Manager | > | Space Dynamics Laboratory | > | (801) 755-4352 [office] Computational Sciences Division | > | (801) 770-0318 [cell] 1747 North Research Parkway | > | (801) 755-4366 [fax] Logan, UT 84321 | > | -------------------------------------------------------------------- | > | Harried Call, " The NETWORK is DOWN !!! " | > | 99% of the time, It is a computer OPERATOR malfunction!!! | > +<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>+ > > From majordomo-users-owner Fri May 6 18:20:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA15159; Fri, 6 May 1994 23:57:21 GMT Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA15148; Fri, 6 May 1994 16:57:09 -0700 Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA11678; Fri, 29 Apr 1994 16:10:11 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA11670; Fri, 29 Apr 1994 09:09:52 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA29441 (5.65c/IDA-1.4.4 for ); Fri, 29 Apr 1994 12:09:07 -0400 Message-Id: <199404291609.AA29441@cs.umb.edu> To: Pat Crawford <0001020203@mcimail.com> Cc: majordomo-users@greatcircle.com Subject: Re: Fwd: Return Receipt... In-Reply-To: Your message of "Wed, 27 Apr 1994 15:29:00 EST." <15940427202951/0001020203DB2EM@mcimail.com> Date: Fri, 29 Apr 1994 12:09:06 -0400 From: "John P. Rouillard" Status: R Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <15940427202951/0001020203DB2EM@mcimail.com>, Pat Crawford writes: > All: > > Seems to be my week. > > This just came from a list subscriber. Any comments? > > Pat Crawford > MCI Communications > > ------- Forwarded Message > > Received: from gatekeeper.mcimail.com by herman.messaging.cs.mci.com > idaa23982; > 26 Apr 94 8:36 MDT > Received: by gatekeeper.mcimail.com (5.65/fma-120691); > id AA05354; Tue, 26 Apr 94 09:36:57 -0500 > Received: by us2.navo.navy.mil id AA26226 > (5.67b/IDA-1.5 for mcimail-info-owner@gatekeeper.mcimail.com); Tue, > 26 Apr > 1994 09:36:34 -0500 > Date: Tue, 26 Apr 1994 09:36:34 -0500 > From: don newcomb > Message-Id: <199404261436.AA26226@us2.navo.navy.mil> > To: mcimail-info-owner@gatekeeper.mcimail.com > Subject: Majordomo and return reciepts. > Reply-To: newcomb@pops.navo.navy.mil > > FYI, Majordomo gives a rather strange response when a return reciept request > is added to a mail header. > > >From MAILER-DAEMON@gatekeeper.mcimail.com Tue Apr 26 14:30:12 1994 > >Received: from us2.navo.navy.mil (us2) by us1.navo.navy.mil with SMTP id > > AA13189 (5.67b/IDA-1.5 for ); Tue, 26 Apr 1994 > > 09:30:59-0500 > >Received: from gatekeeper.mcimail.com by us2.navo.navy.mil with SMTP id > > AA26151 (5.67b/IDA-1.5 for ); Tue, 26 Apr 1994 > > 09:29:58 -0500 > >Received: by gatekeeper.mcimail.com (5.65/fma-120691); > > id AA04887; Tue, 26 Apr 94 09:30:12 -0500 > >Date: Tue, 26 Apr 94 09:30:12 -0500 > >From: MAILER-DAEMON@gatekeeper.mcimail.com (Mail Delivery Subsystem) > >Subject: Returned mail: Return receipt > >Message-Id: <9404261430.AA04887@gatekeeper.mcimail.com> > >To: newcomb@us2.navo.navy.mil > >Status: R > > > > ----- Transcript of session follows ----- > >Can't unlink /tmp/majordomo.4889.*: No such file or directory at > /usr/users/majordom/majordomo line 1225, <> line 2. > >get_config(/usr/users/majordom/lists, mcimail-info) > >adding site-wide defaults > >Overriding with existing config files > >parsing config get_config(/usr/users/majordom/lists, mcimail-info) > > > > ----- Recipients of this delivery ----- > >Sent successfully: > > > > "|/usr/users/majordom/wrapper majordomo" > > > > ----- Message header follows ----- > >Received: by gatekeeper.mcimail.com (5.65/fma-120691); > > id AA04885; Tue, 26 Apr 94 09:30:12 -0500 > >Received: by us2.navo.navy.mil id AA26147 > > (5.67b/IDA-1.5 for Majordomo@gatekeeper.mcimail.com); Tue, 26 Ap > r 1994 > 09:29:49 -0500 > >Date: Tue, 26 Apr 1994 09:29:49 -0500 > >From: don newcomb > >Message-Id: <199404261429.AA26147@us2.navo.navy.mil> > >To: Majordomo > >Subject: Re: Welcome to mcimail-info > >Reply-To: newcomb@pops.navo.navy.mil > >Return-Receipt-To: newcomb@us2.navo.navy.mil > > > - ---- > Donald R. Newcomb * newcomb@pops.navo.navy.mil > > Naval Oceanographic Office * drn@fiddle.noo.navy.mil > Stennis Space Center, MS 39522 * Voice: (601) 688-5998 > FAX: (601) 688-5485 * DSN: 485-5998 > > ------- End of Forwarded Message Looks like a standard log file for a sendmail delivery. That is probably how that version of sendmail handles return receipts. The stuff in the transcript section is what majordomo puts out for debugging. The failed unlink message is supresesed in the 1.90 full release, but the rest of the debugging info is still put out. -- John John Rouillard Special Projects Volunteer 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 opFrom majordomo-users-owner Fri Apr 29 21:28:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA19779; Fri, 29 Apr 1994 21:28:17 GMT Received: from csrp.tamu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA19724; Fri, 29 Apr 1994 14:28:01 -0700 From: neils@csrp.tamu.edu Received: from CSRP15.TAMU.EDU by csrp.tamu.edu (AIX 3.2/UCB 5.64/4.03) id AA22831; Fri, 29 Apr 1994 16:26:01 -0500 Message-Id: <9404292126.AA22831@csrp.tamu.edu> Date: Fri, 29 Apr 1994 15:32:17 -0600 To: Majordomo-Users@GreatCircle.COM Subject: which alias sample? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >From a newbie -- I got the 1.62 version. The aliases in the sample.aliases file don't match the aliases in test.aliases provided in the Doc/samples directory for sample lists. eg., in sample.aliases, the list alias invokes wrapper with numerous arguments, while the test.aliases file list alias just contains the path to the list file. What's that all about? Furthermore, there is no auto feature described in the docs or REAMDMEs (that I can find) to correspond to the sample auto list in the Doc/samples directory. What gives? Also, the sample aliases in sample.aliases have the auto and private list directory paths different from the open and closed lists. Is this required? Does 1.62 have the archive feature, and where is documentation on it? Thanks, ----------------------------------------------------------------------- Neil R. Smith, Research Associate neils@csrp.tamu.edu Climate System Research Program (409) 862-4342 Department of Meteorology (409) 862-4132 FAX Texas A&M University College Station, TX 77843-3150 ----------------------------------------------------------------------- From majordomo-users-owner Sat May 7 19:56:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA19517; Sat, 7 May 1994 19:56:23 GMT Received: from tree.egr.uh.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA19502; Sat, 7 May 1994 12:56:10 -0700 Received: from thanatos by tree.egr.uh.edu (NX5.67d/NX3.0M) id AA05007; Sat, 7 May 94 14:57:00 -0500 From: "Paul S. Sears" Message-Id: <9405071957.AA05007@tree.egr.uh.edu> Received: by thanatos.egr.uh.edu (NX5.67d/NX3.0X) id AA12234; Sat, 7 May 94 14:56:59 -0500 Date: Sat, 7 May 94 14:56:59 -0500 Received: by NeXT.Mailer (1.100) Received: by NeXT Mailer (1.100) To: majordomo-users@GreatCircle.COM Subject: Digest poblem with 1.90b2 Reply-To: sears@uh.edu Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We are having a problem with our digests - every one that is sent out has all the previous digest appended to it. For example, if we are on #3, #2 and #1 are included (they are nested). What is misconfigured? Everything looks ok... Here are my aliases and a sample digest: #ENSAIN mailing list ensain:"|/usr/local/listserv/majordomo-1.90/wrapper resend -l ensain -h tree.egr.uh.edu ensain-outgoing" ensain-digest:ensain ensain-outgoing: :include:/usr/local/listserv/majordomo-1.90/mailing-lists/ensain, "| /usr/local/listserv/majordomo-1.90/wrapper digest -r -C -l ensain-digest ensain-digest-outgoing", "| /usr/local/listserv/majordomo-1.90/wrapper archive2.pl -a -m -f /usr/local/listserv/majordomo-1.90/Archive/ensain/ensain.archive" ensain-digest-outgoing: :include:/usr/local/listserv/majordomo-1.90/mailing-lists/ensain-digest ensain-request: "| /usr/local/listserv/majordomo-1.90/wrapper majordomo -l ensain" ensain-digest-request: "| /usr/local/listserv/majordomo-1.90/wrapper majordomo -l ensain-digest" owner-ensain: sears@uh.edu owner-ensain-outgoing:owner-ensain owner-ensain-digest: owner-ensain owner-ensain-digest-outgoing:owner-ensain ensain-approval: sears@uh.edu ensain-digest-approval:ensain-approval Date: Sat, 7 May 94 14:50:02 -0500 From: owner-ensain To: ensain-digest@tree.egr.uh.edu Subject: ensain-digest V1 #6 Reply-To: ensain@tree.egr.uh.edu Errors-To: owner-ensain Precedence: bulk ensain-digest Saturday, 7 May 1994 Volume 01 : Number 006 [All the stuff deleted] - - - - - ------------------------------ End of ensain V1 #1 ******************* - - - - ------------------------------ End of ensain-digest V1 #2 ************************** - - - ------------------------------ End of ensain-digest V1 #3 ************************** - - - ----------------------------<<<<<<>>>>>>>-------------------------------- The ENSAIN digest [a digest of all postings to the ENSAIN mailing-list] To contribute to the list, send to ensain@tree.egr.uh.edu. Direct all administrative requests (subscribe, unsubscribe) to ensain-digest-request@tree.egr.uh.edu - - ------------------------------ End of ensain-digest V1 #4 ************************** - - ----------------------------<<<<<<>>>>>>>-------------------------------- The ENSAIN digest [a digest of all postings to the ENSAIN mailing-list] To contribute to the list, send to ensain@tree.egr.uh.edu. Direct all administrative requests (subscribe, unsubscribe) to ensain-digest-request@tree.egr.uh.edu - ------------------------------ End of ensain-digest V1 #5 ************************** - ----------------------------<<<<<<>>>>>>>-------------------------------- The ENSAIN digest [a digest of all postings to the ENSAIN mailing-list] To contribute to the list, send to ensain@tree.egr.uh.edu. Direct all administrative requests (subscribe, unsubscribe) to ensain-digest-request@tree.egr.uh.edu ------------------------------ End of ensain-digest V1 #6 ************************** ----------------------------<<<<<<>>>>>>>-------------------------------- The ENSAIN digest [a digest of all postings to the ENSAIN mailing-list] To contribute to the list, send to ensain@tree.egr.uh.edu. Direct all administrative requests (subscribe, unsubscribe) to ensain-digest-request@tree.egr.uh.edu From majordomo-users-owner Sat May 7 20:49:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA20095; Sat, 7 May 1994 20:49:25 GMT Received: from uni.INS.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA20089; Sat, 7 May 1994 13:49:12 -0700 Received: from [199.0.193.230] (dynamic230.ins.com) by uni.INS.COM (4.1/SMI-4.1) id AA17567; Sat, 7 May 94 13:49:40 PDT Message-Id: <9405072049.AA17567@uni.INS.COM> X-Sender: ljrebar@uni.ins.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 7 May 1994 13:49:35 -0700 To: Pat Crawford <0001020203@mcimail.com>, majordomo-users From: (Larry Rebarchik) Subject: Re: Fwd: Return Receipt... Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk At 3:29 PM 4/27/94 -0500, Pat Crawford wrote: >All: > >Seems to be my week. > >This just came from a list subscriber. Any comments? > >Pat Crawford >MCI Communications > >------- Forwarded Message > >Received: from gatekeeper.mcimail.com by herman.messaging.cs.mci.com id >aa23982; > 26 Apr 94 8:36 MDT >Received: by gatekeeper.mcimail.com (5.65/fma-120691); > id AA05354; Tue, 26 Apr 94 09:36:57 -0500 >Received: by us2.navo.navy.mil id AA26226 > (5.67b/IDA-1.5 for mcimail-info-owner@gatekeeper.mcimail.com); Tue, 26 Apr >1994 09:36:34 -0500 >Date: Tue, 26 Apr 1994 09:36:34 -0500 >From: don newcomb >Message-Id: <199404261436.AA26226@us2.navo.navy.mil> >To: mcimail-info-owner@gatekeeper.mcimail.com >Subject: Majordomo and return reciepts. >Reply-To: newcomb@pops.navo.navy.mil > >FYI, Majordomo gives a rather strange response when a return reciept request >is >added to a mail header. > >>Date: Tue, 26 Apr 94 09:30:12 -0500 >>From: MAILER-DAEMON@gatekeeper.mcimail.com (Mail Delivery Subsystem) >>Subject: Returned mail: Return receipt >>Message-Id: <9404261430.AA04887@gatekeeper.mcimail.com> >>To: newcomb@us2.navo.navy.mil >>Status: R >> >> ----- Transcript of session follows ----- >>Can't unlink /tmp/majordomo.4889.*: No such file or directory at >/usr/users/majordom/majordomo line 1225, <> line 2. >>get_config(/usr/users/majordom/lists, mcimail-info) >>adding site-wide defaults >>Overriding with existing config files >>parsing config get_config(/usr/users/majordom/lists, mcimail-info) >> >> ----- Recipients of this delivery ----- >>Sent successfully: >> >> "|/usr/users/majordom/wrapper majordomo" >> >> ----- Message header follows ----- >>Received: by gatekeeper.mcimail.com (5.65/fma-120691); >> id AA04885; Tue, 26 Apr 94 09:30:12 -0500 >>Received: by us2.navo.navy.mil id AA26147 >> (5.67b/IDA-1.5 for Majordomo@gatekeeper.mcimail.com); Tue, 26 Apr 1994 >09:29:49 -0500 >>Date: Tue, 26 Apr 1994 09:29:49 -0500 >>From: don newcomb >>Message-Id: <199404261429.AA26147@us2.navo.navy.mil> >>To: Majordomo >>Subject: Re: Welcome to mcimail-info >>Reply-To: newcomb@pops.navo.navy.mil >>Return-Receipt-To: newcomb@us2.navo.navy.mil > >------- End of Forwarded Message Pat, You're doing better than I on this. I just tested this with Majordomo 1.60 and received the following: Looks like it's a sendmail problem on my host to start, received a bounce for both my address and the list address. Something new to persue (-; Return-Path: Received: by uni.INS.COM (4.1/SMI-4.1) id AA17507; Sat, 7 May 94 13:39:55 PDT Date: Sat, 7 May 94 13:39:55 PDT From: Mailer-Daemon (Mail Delivery Subsystem) Subject: Returned mail: Return receipt Message-Id: <9405072039.AA17507@uni.INS.COM> To: ----- Transcript of session follows ----- ----- Message header follows ----- Return-Path: Received: from hobbes.ins.COM by uni.INS.COM (4.1/SMI-4.1) id AA17503; Sat, 7 May 94 13:39:55 PDT Received: from uni.INS.COM by hobbes.ins.COM (4.1/SMI-4.1) id AA16559; Sat, 7 May 94 13:39:51 PDT Received: from [199.0.193.230] (dynamic230.ins.com) by uni.INS.COM (4.1/SMI-4.1) id AA17500; Sat, 7 May 94 13:39:42 PDT Message-Id: <9405072039.AA17500@uni.INS.COM> X-Sender: ljrebar@uni.ins.com Return-Receipt-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 7 May 1994 13:39:36 -0700 To: ljrebar@hobbes.INS.COM, microlib-mac-local@INS.COM From: (Larry Rebarchik) Subject: test RR Have a tremendous day :-) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Lawrence J. Rebarchik ljrebar@ins.com International Network Services 415.254.4228 650 Castro Street, #260 (fax) 415.254.4288 Mountain View, CA 94041 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- "Your mind is a database, it depends on how you access it that makes it work" -me- From majordomo-users-owner Sat May 7 14:03:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA20220; Sat, 7 May 1994 20:55:12 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA20211; Sat, 7 May 1994 13:55:01 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA02704 (5.65c/IDA-1.4.4 for ); Sat, 7 May 1994 16:55:44 -0400 Message-Id: <199405072055.AA02704@cs.umb.edu> To: sears@uh.edu Cc: majordomo-users@greatcircle.com Subject: Re: Digest poblem with 1.90b2 In-Reply-To: Your message of "Sat, 07 May 1994 14:56:59 CDT." <9405071957.AA05007@tree.egr.uh.edu> Date: Sat, 07 May 1994 16:55:43 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Where is your digest incoming directory ($digest_work_dir in majordomo.cf)? It can't be the same as the digest archive directory otherwise you would see this sort of thing. $V{'ARCHIVE'} = "$filedir/$opt_l$filedir_suffix"; $V{'INCOMING'} = "$digest_work_dir/$opt_l"; If the filedir in majordomo.cf is the same as the digest_work_dir, and $filedir_suffix is null, you could get this problem. In message <9405071957.AA05007@tree.egr.uh.edu>, "Paul S. Sears" writes: > > We are having a problem with our digests - every one that is sent out has > all the previous digest appended to it. For example, if we are on #3, #2 > and #1 are included (they are nested). If this is the problem, I will add code to warn and skip any files in the incoming directory that don't have the form "\d*" when creating the digest. -- John John Rouillard Special Projects Volunteer 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 May 7 23:13:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA21353; Sat, 7 May 1994 23:13:33 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA21347; Sat, 7 May 1994 16:13:27 -0700 Received: by netcom.com (8.6.8.1/SMI-4.1/Netcom) id QAA08947; Sat, 7 May 1994 16:14:17 -0700 Date: Sat, 7 May 1994 16:14:16 -0700 (PDT) From: Dick Moores Reply-To: Dick Moores Subject: list of Majordomos? To: majordomo-users@greatcircle.com cc: David L Miller 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 find a list of Majordomos, or better yet, a list of majordomo lists (something like the list you can get from a Bitnet Listserve with the command "list global"). Any suggestions? Below are the Majordomos I've found so far. Any additions would be appreciated. majordomo@cac.washington.edu majordomo@connect.com.au majordomo@coombs.anu.edu.au majordomo@gemstar.com majordomo@greatcircle.com majordomo@halcyon.com majordomo@mcs.net majordomo@netcom.com majordomo@traffic.engr.washington.edu majordomo@ucar.edu majordomo@world.std.com From majordomo-users-owner Sun May 8 02:07:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA22079; Sun, 8 May 1994 02:07:26 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA22073; Sat, 7 May 1994 19:06:59 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0pzyGe-00014xC; Sat, 7 May 94 19:06 PDT Message-Id: To: Dick Moores cc: majordomo-users@greatcircle.com Subject: Re: list of Majordomos? In-reply-to: Your message of Sat, 07 May 1994 16:14:16 -0700. Date: Sat, 07 May 1994 19:06:51 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I am trying to find a list of Majordomos, or better yet, a list of > majordomo lists (something like the list you can get from a Bitnet > Listserve with the command "list global"). Any suggestions? Unlike Listserv, which is a network of semi-integrated list management processors, Majordomo sites are separate. Many of us would like to keep it that way. Hell, many of us would even like the fact that we run Majordomo not to be well-known. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Sun May 8 21:41:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA26237; Sun, 8 May 1994 21:41:46 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA26231; Sun, 8 May 1994 14:41:40 -0700 Received: by netcom.com (8.6.8.1/SMI-4.1/Netcom) id OAA07076; Sun, 8 May 1994 14:42:34 -0700 From: sylviac@netcom.com (Sylvia Caras) Message-Id: <199405082142.OAA07076@netcom.com> Subject: Tally technology To: majordomo-users@greatcircle.com Date: Sun, 8 May 1994 14:42:34 -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: 904 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm involved in a lot of NII lobbying, free nets, etc. and often get messages about writing to electeds WHO DON'T HAVE E MAIL . Is there a way to use majordomo or some program to be an address to tally pros and cons, save the names and addresses, and then generate a wrap up message which would be snailed to the right place? Until all the electeds are on line, this would be useful. I am not a programmer, and I don't know C, and I struggle with the unix commands to use internet effectively. So this is an idea, but I haven't the skill to put it into operation. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ sylviac@netcom.com v/f:408 426 5335 Sylvia Caras, 146-5 Chrystal Ter, Santa Cruz CA 95060 It is not up to you to finish the work, but neither are you free to not take it up. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From majordomo-users-owner Sun May 8 22:40:02 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA26649; Sun, 8 May 1994 22:40:02 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA26640; Sun, 8 May 1994 15:39:55 -0700 Message-Id: <199405082239.PAA26640@mycroft.GreatCircle.COM> To: sylviac@netcom.com (Sylvia Caras) cc: majordomo-users@greatcircle.com Subject: Re: Tally technology In-reply-to: Your message of Sun, 8 May 1994 14:42:34 -0700 (PDT) Date: Sun, 08 May 1994 15:39:54 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk sylviac@netcom.com (Sylvia Caras) writes: # I'm involved in a lot of NII lobbying, free nets, etc. and # often get messages about writing to electeds WHO DON'T # HAVE E MAIL . # # Is there a way to use majordomo or some program to be an # address to tally pros and cons, save the names and addresses, # and then generate a wrap up message which would be snailed # to the right place? # # Until all the electeds are on line, this would be useful. # # I am not a programmer, and I don't know C, and I struggle # with the unix commands to use internet effectively. # So this is an idea, but I haven't the skill to put it # into operation. Interesting question... You could create two Majordomo-managed lists, named "issue-yes" and "issue-no" (for whatever "issue" is), make them both "auto" lists (so that all subscription requests would succeed), and tell people to use Majordomo to subscribe to the list that expressed their opinion. You'd have to worry about people stuffing the ballot box or registering others, but you have to worry about that even with paper petitions. -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 May 8 22:59:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA26765; Sun, 8 May 1994 22:59:18 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA26759; Sun, 8 May 1994 15:59:08 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA04078 (5.65c/IDA-1.4.4); Sun, 8 May 1994 18:59:52 -0400 Message-Id: <199405082259.AA04078@cs.umb.edu> To: Brent Chapman Cc: majordomo-users@greatcircle.com Subject: Re: Tally technology In-Reply-To: Your message of "Sun, 08 May 1994 15:39:54 PDT." <199405082239.PAA26640@mycroft.GreatCircle.COM> Date: Sun, 08 May 1994 18:59:51 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199405082239.PAA26640@mycroft.GreatCircle.COM>, Brent Chapman writes: > sylviac@netcom.com (Sylvia Caras) writes: > > # I'm involved in a lot of NII lobbying, free nets, etc. and > # often get messages about writing to electeds WHO DON'T > # HAVE E MAIL . > # > # Is there a way to use majordomo or some program to be an > # address to tally pros and cons, save the names and addresses, > # and then generate a wrap up message which would be snailed > # to the right place? > # > # Until all the electeds are on line, this would be useful. > # > # I am not a programmer, and I don't know C, and I struggle > # with the unix commands to use internet effectively. > # So this is an idea, but I haven't the skill to put it > # into operation. > > Interesting question... You could create two Majordomo-managed lists, > named "issue-yes" and "issue-no" (for whatever "issue" is), make them > both "auto" lists (so that all subscription requests would succeed), > and tell people to use Majordomo to subscribe to the list that > expressed their opinion. > > You'd have to worry about people stuffing the ballot box or > registering others, but you have to worry about that even with paper > petitions. Actually rather than auto, make them normal open lists. That helps limit the amount of abuse, although forging email is simple. What I have done in the past is to have the voters put some special word or number in the address (we used our membership numbers). So a vote looked like: subscribe amalgam-yes id#452198 Then these numbers were compared against the valid voting membership lists. This does of course assume that your voters can craft a valid email address. The version of majordomo we used actually had a "vote" command that acted like subscribe, but that would add the default address if it looked like there wasn't an address provided. The "lists" command could be used to see what issues were available for voting and the info file was public, and they info files contained the text of the voting issue. Note that you should make sure to make who private, and not bother creating the mail aliases until voting is closed. Once voting is closed, and the id#'s have been validated, set up the mail aliases and send a message of the form: You are receiving the message because you voted yes on the issue of ... It makes a useful check for peole who may have voted incorrectly, or may not have had their votes counted. -- John John Rouillard Special Projects Volunteer 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 Tue May 10 19:56:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA10469; Tue, 10 May 1994 19:56:33 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA10463; Tue, 10 May 1994 12:56:14 -0700 Received: from bolis by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA09890; Tue, 10 May 94 12:57:03 -0700 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0q0wlb-0002YUC; Tue, 10 May 94 11:42 PDT Message-Id: From: Alan Millar Subject: Re: Tally technology To: sylviac@netcom.com (Sylvia Caras) Date: Tue, 10 May 1994 11:42:53 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199405082142.OAA07076@netcom.com> from "Sylvia Caras" at May 8, 94 02:42:34 pm Reply-To: Alan Millar X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1285 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Sylvia Caras spake of these matters: > > I'm involved in a lot of NII lobbying, free nets, etc. and > often get messages about writing to electeds WHO DON'T > HAVE E MAIL . > > Is there a way to use majordomo or some program to be an > address to tally pros and cons, save the names and addresses, > and then generate a wrap up message which would be snailed > to the right place? As Brent and John mentioned, setting up mailing lists of the form "issue-yes" and "issue-no" should be fairly straightforward. If you don't make them "auto", then people aren't likely to be able to stuff them easily (forging notwithstanding). The nice thing about Majordomo/similar is automatic detection/rejection of duplicates. When the petition period is done, you could fax the results to the target official instead of snail-mail. Check out the mail-to-fax service by sending a message to tpc-faq@town.hall.org (subject and body not important). The process could be automated fairly easily. - Alan ---- ,,,, Alan Millar amillar@bolis.SF-Bay.org __oo \ System Administrator =___/ Reason notwithstanding, the universe continues unabated. From majordomo-users-owner Tue May 10 21:41:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA11110; Tue, 10 May 1994 21:41:54 GMT Received: from csrp.tamu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA11099; Tue, 10 May 1994 14:41:35 -0700 From: neils@csrp.tamu.edu Received: from CSRP15.TAMU.EDU by csrp.tamu.edu (AIX 3.2/UCB 5.64/4.03) id AA18528; Tue, 10 May 1994 16:39:46 -0500 Message-Id: <9405102139.AA18528@csrp.tamu.edu> Date: Tue, 10 May 1994 15:46:40 -0600 To: Majordomo-Users@GreatCircle.COM Subject: archiving isn't working Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk 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 = ""; while the aliases look like: # # test mailing list # tester: "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l tester -f owner-tester -h csrp.tamu.edu -s tester-outgoing" owner-tester: tester-owner tester-owner: neils@csrp2.tamu.edu tester-request:"|/usr/local/mail/majordomo/wrapper request-answer tester" tester-outgoing: :include:/usr/local/mail/majordomo/lists/tester, tester-archive owner-tester-outgoing: tester-owner tester-archive: /usr/local/mail/majordomo/archive/tester owner-tester-archive: tester-owner tester-approval: tester-owner and the listings look like: /usr/local/mail/majordomo -rw-rw-r-- 1 majordom Major 6200 May 10 16:08 Log drwxrwsr-x 5 majordom Major 512 May 10 10:59 archive/ drwxrwsr-x 4 majordom Major 1024 May 9 15:20 bin/ drwxrwsr-x 2 majordom Major 512 May 10 15:49 lists/ -r--r--r-- 1 majordom Major 1574 May 9 17:26 majordomo.cf -rwsr-xr-x 1 root Major 8061 May 9 15:17 wrapper* and /usr/local/mail/majordomo/archive drwxrwsr-x 2 majordom Major 512 May 10 09:29 csrplist/ drwxrwsr-x 2 majordom Major 512 May 10 10:43 tccslist/ drwxrwsr-x 2 majordom Major 512 May 10 10:59 tester/ So what's wrong with that? Why doesn't it archive the test messages I sent to the list "tester" -- the directory /usr/local/mail/majordomo/archive/tester is empty, and remains so. Does anyone have any suggestions? Thanks in advance. ----------------------------------------------------------------------- Neil R. Smith, Research Associate neils@csrp.tamu.edu Climate System Research Program (409) 862-4342 Department of Meteorology (409) 862-4132 FAX Texas A&M University College Station, TX 77843-3150 ----------------------------------------------------------------------- From majordomo-users-owner Tue May 10 22:00:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA11345; Tue, 10 May 1994 22:00:28 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA11339; Tue, 10 May 1994 15:00:19 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0q0zqP-00014zC; Tue, 10 May 94 15:00 PDT Message-Id: To: neils@csrp.tamu.edu cc: Majordomo-Users@greatcircle.com Subject: Re: archiving isn't working In-reply-to: Your message of Tue, 10 May 1994 15:46:40 -0600. <9405102139.AA18528@csrp.tamu.edu> Date: Tue, 10 May 1994 14:59:57 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I don't get it: is the list archive a file or a directory? That all depends on how you archive it. Majordomo always *retrieves* files from a directory. However, a pathname in a sendmail alias tells sendmail to put the stuff in a file; it doesn't deal with directories at all. --- 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 Tue May 10 22:37:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA11487; Tue, 10 May 1994 22:37:00 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA11481; Tue, 10 May 1994 15:36:46 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA06516 (5.65c/IDA-1.4.4 for ); Tue, 10 May 1994 18:37:36 -0400 Message-Id: <199405102237.AA06516@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: archiving isn't working In-Reply-To: Your message of "Tue, 10 May 1994 15:46:40 MDT." <9405102139.AA18528@csrp.tamu.edu> Date: Tue, 10 May 1994 18:37:35 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Sigh, here's one for the FAQ. I just laid 1.90 to bed today, so it won't go in to the distribution. In message <9405102139.AA18528@csrp.tamu.edu>, neils@csrp.tamu.edu writes: > 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: The archive variables in majordomo.cf arent used to archive anything, you have to use a seperate archive program, or a sendmail alias to do the archiving. The info is used to generate a driectory where the archive files are being placed by some other mechanism. > $filedir = "/usr/local/mail/majordomo/archive"; > $filedir_suffix = ""; 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. Listname would be tester in your example. > while the aliases look like: > > # > # test mailing list > # > tester: "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 > -l tester -f owner-tester -h csrp.tamu.edu -s > tester-outgoing" > owner-tester: tester-owner > tester-owner: neils@csrp2.tamu.edu > tester-request:"|/usr/local/mail/majordomo/wrapper request-answer tester" > tester-outgoing: :include:/usr/local/mail/majordomo/lists/tester, > tester-archive > owner-tester-outgoing: tester-owner > tester-archive: /usr/local/mail/majordomo/archive/tester ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When using a sendmail alias, the ^^^ section must be a file, usually mode 666 because of the differing uid's that sendmail can run under. However, you need something like: /usr/local/mail/majordomo/archive/tester/archive to be a file with mode 666 permissions instead of: /usr/local/mail/majordomo/archive/tester being a directory. Then when you do a majordomo index tester or a get tester archive majordomo will 'ls -lR' the directory /usr/local/mail/majordomo/archive/tester > [...] > /usr/local/mail/majordomo/archive > drwxrwsr-x 2 majordom Major 512 May 10 09:29 csrplist/ > drwxrwsr-x 2 majordom Major 512 May 10 10:43 tccslist/ > drwxrwsr-x 2 majordom Major 512 May 10 10:59 tester/ > > So what's wrong with that? Why doesn't it archive the test messages Because sendmail is (most likely) unable to write a 775 directory. > I sent to the list "tester" -- the directory > /usr/local/mail/majordomo/archive/tester > is empty, and remains so. That's because sendmail a) can't write the directory as a file, b) doesn't create any files. You may want to wait until 1.90 is offically available it has three different archive programs that run under wrapper, that do various types of archiving. Or you can look at the majordomo-users ftp area on ftp.greatcircle.com and get the archive program that exists there. -- John John Rouillard Special Projects Volunteer 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 Tue May 10 23:52:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA13718; Wed, 11 May 1994 06:40:04 GMT Received: from runningman.rs.itd.umich.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA07367; Tue, 10 May 1994 06:41:09 -0700 Received: from aoce.itd.umich.edu by runningman.rs.itd.umich.edu (8.6.9/2.25) with SMTP id JAA26102; Tue, 10 May 1994 09:42:01 -0400 Message-Id: <199405101342.JAA26102@runningman.rs.itd.umich.edu> Date: 10 May 1994 09:41:31 -0400 From: "Mike Nowak" Subject: Help, unknown list. To: "majordomo-users@greatcircle.com" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I just tried to set up a mailing list using majordomo. My list show up when I send the lists command but when I try to subscribe, I get back the message unknown list. I can send my aliases and .cf files if that would be helpful. Help! Mike Nowak (mnowak@umich.edu) From majordomo-users-owner Wed May 11 12:19:16 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA15232; Wed, 11 May 1994 12:19:16 GMT Received: from runningman.rs.itd.umich.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA15226; Wed, 11 May 1994 05:19:07 -0700 Received: from aoce.itd.umich.edu by runningman.rs.itd.umich.edu (8.6.9/2.25) with SMTP id IAA26120; Wed, 11 May 1994 08:19:47 -0400 Message-Id: <199405111219.IAA26120@runningman.rs.itd.umich.edu> Date: 11 May 1994 08:19:46 -0400 From: "Mike Nowak" Subject: Re(2): Help, unknown list. To: "Brent Chapman" Cc: "majordomo-users@greatcircle.com" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk You're right!! My group is called Newton-Announce. I'll change it right now and see if it works. Mike. ------ From: Brent Chapman, Wed, May 11, 1994 ------ 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_ all need to be "majordomo-users*". -Brent From majordomo-users-owner Wed May 11 16:05:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA16614; Wed, 11 May 1994 16:05:07 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA14064; Wed, 11 May 1994 00:12:45 -0700 Message-Id: <199405110712.AAA14064@mycroft.GreatCircle.COM> To: "Mike Nowak" cc: "majordomo-users@greatcircle.com" Subject: Re: Help, unknown list. In-reply-to: Your message of 10 May 1994 09:41:31 -0400 Date: Wed, 11 May 1994 00:12:44 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Mike Nowak" writes: # Hi, I just tried to set up a mailing list using majordomo. My list show up # when I send the lists command but when I try to subscribe, I get back the # message unknown list. # # I can send my aliases and .cf files if that would be helpful. 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_ all need to be "majordomo-users*". -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 May 11 11:49:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA17699; Wed, 11 May 1994 17:47:24 GMT Received: from watson.ibm.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA17687; Wed, 11 May 1994 10:47:05 -0700 Received: from WATSON by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 6629; Wed, 11 May 94 13:47:48 EDT Received: from YKTVMV by watson.vnet.ibm.com with "VAGENT.V1.0" id 3345; Wed, 11 May 1994 13:47:48 EDT Received: from np2.watson.ibm.com by yktvmv.watson.ibm.com (IBM VM SMTP V2R3) with TCP; Wed, 11 May 94 13:47:48 EDT Received: by np2.watson.ibm.com (AIX 3.2/UCB 5.64/930311) id AA25708; Wed, 11 May 1994 13:47:45 -0400 From: perk@watson.ibm.com (Charlie Perkins) Message-Id: <9405111747.AA25708@np2.watson.ibm.com> To: majordomo-users@GreatCircle.COM Subject: Configuration question Date: Wed, 11 May 94 13:47:44 -0500 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've installed majordomo, and it works. However, there are two things I haven't figured out how to do, and would appreciate some advice. I admit that I haven't read through all the archives yet, but I have read through most of the "normal" documentation. What I'd like to do is have each contribution archived as a separate file, much as is done by the news system. Then, I'd like to have the filename (e.g, "listname/57743") be sent out as part of the Subject: line for the outgoing mail. Thanks for your help. Plus, I'm finally being forced to learn Perl, which is in itself a good thing :-) And, thanks already to Brent and the seeming crowds of people who have collaborated to make this software available. Charlie P. From majordomo-users-owner Wed May 11 14:49:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA19117; Wed, 11 May 1994 20:52:51 GMT Received: from inet-gw-2.pa.dec.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA19111; Wed, 11 May 1994 13:52:40 -0700 Received: from us4rmc.pko.dec.com by inet-gw-2.pa.dec.com (5.65/21Mar94) id AA21163; Wed, 11 May 94 13:45:31 -0700 Received: from wrksys.enet by us4rmc.pko.dec.com (5.65/rmc-22feb94) id AA04496; Wed, 11 May 94 16:48:43 -0400 Message-Id: <9405112048.AA04496@us4rmc.pko.dec.com> Received: from wrksys.enet; by us4rmc.enet; Wed, 11 May 94 16:48:45 EDT Date: Wed, 11 May 94 16:48:45 EDT From: Jim Reisert To: majordomo-users@greatcircle.com Apparently-To: majordomo-users@greatcircle.com Subject: Need help with resend and From, Reply-To fields Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I want to set up the resend wrapper so that: 1. The From field has the address of the poster to the list (i.e. brent@greatcircle.com) 2. The Reply-To field has the address of the list (i.e. Majordomo-Users@GreatCircle.COM). I also want all bounced mail to return to me. Right now I have the following switches: -l my-list -h my-node -s my-list-outgoing (which has the file of users) -r my-list@my-node However, it doesn't seem like the "Reply-to" field is being filled in, and all mail sent to the list appears to come from "my-list-request@my-node". >From the description of the resend wrapper, it sounds like if I add the -f flag to be the name of the list ("-f my-list"), then all bounces will be mailed out to everyone on the list! But this wouldn't do what I want anyway, because I want the poster's address to be the from address, not the list address. Help! - Jim From majordomo-users-owner Wed May 11 22:53:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA20332; Wed, 11 May 1994 22:53:47 GMT Received: from mgc.mentorg.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA20325; Wed, 11 May 1994 15:53:33 -0700 Received: from warren.mentorg.com by mgc.mentorg.com with SMTP (16.6/15.5+MGC-TD 2.20) id AA11426; Wed, 11 May 94 15:54:27 -0700 Received: by Warren.MENTORG.COM id AA19420 (5.65c/IDA-1.4.4); Wed, 11 May 1994 18:54:25 -0400 Date: Wed, 11 May 1994 18:54:25 -0400 From: Tom Limoncelli Message-Id: <9405111854.ZM19418@sdl> In-Reply-To: Alan Millar "Re: Tally technology" (May 10, 11:42) References: X-Face: *0$,bn:Ak@/SnHYUC7xW=P5jNmcs_C?}BQz?`_"cpCQ(W#[_w70]s5.fAgo1}{12`k4dE2h=z/rBMcsOxg{!h"b8>I__^3!05)sVC3-1*Sg1*q~3FdQk;,5^I(HFE,{R%e!XBJf+:;Ry X-Mailer: Z-Mail (3.0.0 15dec93) To: Alan Millar , sylviac@netcom.com (Sylvia Caras) Subject: Re: Tally technology Cc: majordomo-users@greatcircle.com Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk There is another use for this kind of thing. I'll describe it because others may find it useful. $GROUPNAME is the New Jersey Unix Sysadmin group (Like a local SAGE). We were looking for a tally system to handle our RSVP's for meetings where we needed to know how many people would be there. Right now we do it manually but soon I'll set up a mailing list called groupname-rsvp@warren.mentorg.com so that people can get on and off the "RSVP'ed list" themselves. The ".info" file has directions, etc. to the event. We can then mail to this list if the time/date/directions/etc change. In fact, we can send a reminder on the last day, and include directions, etc. in case people have forgotten, etc. Tom "Better Living Through Majordomo" Limoncelli From majordomo-users-owner Wed May 11 23:29:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA20579; Wed, 11 May 1994 23:29:13 GMT Received: from cs.utexas.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA20573; Wed, 11 May 1994 16:29:06 -0700 Received: from im4u.cs.utexas.edu (lwb@im4u.cs.utexas.edu [128.83.139.6]) by cs.utexas.edu (8.6.9/8.6.9) with SMTP id SAA25212 for ; Wed, 11 May 1994 18:29:46 -0500 Message-Id: <9405112329.AA21173@im4u.cs.utexas.edu> Received: by im4u.cs.utexas.edu (5.64/1.44/uucp) id AA21173; Wed, 11 May 94 18:29:59 -0500 Subject: Preventing Posting by non-members To: majordomo-users@greatcircle.com (majordomo users) Date: Wed, 11 May 1994 18:29:57 -0500 (CDT) From: "Lance W. Bledsoe" X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 532 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello all, I would like to prevent post to my lists by people who are *not* members of the list. Currently the lists are "closed". Will it make any difference if they were "private"? How can I stop outsiders from posting to a list where they arn't wanted??? Thanks, Lance Bledsoe -- "Thoughtcrime was not a thing that could be concealed forever. You might dodge sucessfully for a while, even for years, but sooner or later they were bound to get you." -- George Orwell, Nineteen Eighty-Four From majordomo-users-owner Thu May 12 00:22:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA20934; Thu, 12 May 1994 00:22:52 GMT Received: from netcom.netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA20928; Wed, 11 May 1994 17:22:41 -0700 Received: by netcom.netcom.com (8.6.8.1/Netcom) id RAA26062; Wed, 11 May 1994 17:23:17 -0700 From: essmjf@netcom.com (Michael Faklis) Message-Id: <199405120023.RAA26062@netcom.netcom.com> Subject: Auto-Relying to Mail bounced from Majordomo ? To: majordomo-users@greatcircle.com, procmail@informatik.rwth-aachen.de Date: Wed, 11 May 1994 17:23:16 -0700 (PDT) Reply-To: essmjf@netcom.com (Michael Faklis) Expires: +1 month X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2300 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm the moderator of a Majordomo maillist and I use PROCMAIL to filter my mail. My mailllist is for a national public radio show, and I need to auto-reply to incoming mail (to the maillist) with a release form to allow us to broadcast the email. Yes, it's true, some people are shocked when their letter to a mail list for a national public radio show is broadcasted over the air or distributed to the subscribers of the mail list. My problem is that mail sent to the mail list has additional headers added to the begining of the message, so the reply-to address is now majordomo, and not the originator of the message. An example is appended to this message. So, the note (as it appears in my inbox, and as seen by PROCMAIL) has two From: headers. How can I get PROCMAIL to recognise the orignator's address, in stead of where majordomo bounced the message from? An example follows; From west_coast_live-owner Wed May 11 09:48:22 1994 Return-Path: Received: by mail.netcom.com (8.6.8.1/Netcom) id JAA08209; Wed, 11 May 1994 09:37:42 -0700 Date: Wed, 11 May 1994 09:37:42 -0700 Message-Id: <199405111637.JAA08209@mail.netcom.com> To: west_coast_live-owner@netcom.com From: west_coast_live-owner@netcom.com Subject: BOUNCE west_coast_live@netcom.com: Approval required Status: RO >From essmjf Wed May 11 09:37:23 1994 Return-Path: Received: from gateway.rosedale.org by mail.netcom.com (8.6.8.1/Netcom) id JAA08200; Wed, 11 May 1994 09:37:20 -0700 Received: from pclan.rosedale.org by gateway.rosedale.org with SMTP id AA05629 (5.65c/IDA-1.4.4 for ); Wed, 11 May 1994 12:35:47 -0400 Received: by pclan.rosedale.org; Wed, 11 May 94 12:43:18 EDT Date: Wed, 11 May 94 12:37:59 EDT Message-Id: From: "michael faklis" To: west_coast_live@netcom.com Subject: Non-audience adventure X-Incognito-Sn: 283 X-Incognito-Format: VERSION=1.60f ENCRYPTED=NO Thanks for any insights. -- Michael Faklis, Computer Scientist email: essmjf@netcom.com Evolutionary Software Systems Phone: (415) 323-2222 P.O. Box 1121 FAX: (415) 323-1417 Palo Alto, California 94302-1121 From majordomo-users-owner Thu May 12 03:58:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id DAA21620; Thu, 12 May 1994 03:58:21 GMT Received: from kksys.skypoint.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA21614; Wed, 11 May 1994 20:58:14 -0700 Received: by kksys.skypoint.net (Smail3.1.28.1 #15) id m0q1RfX-0004CPC; Wed, 11 May 94 22:42 CDT Received: by cdsmn (/\==/\ Smail3.1.28.1 #28.5) id ; Wed, 11 May 94 22:13 CDT Message-Id: From: plate@cdsmn.mn.org (Doug Plate) Subject: Splitting list messages into files To: Majordomo-Users@Greatcircle.com Date: Wed, 11 May 94 22:13:46 CDT X-Mailer: ELM [version 2.2 PL7] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I sent this to Charlie Perkins, but messed up the Cc: to the list. I thought this might be of interest to others so here it is: >I've installed majordomo, and it works. However, there are two >things I haven't figured out how to do, and would appreciate some >advice. I admit that I haven't read through all the archives >yet, but I have read through most of the "normal" documentation. > >What I'd like to do is have each contribution archived as a separate >file, much as is done by the news system. Then, I'd like to have >the filename (e.g, "listname/57743") be sent out as part of the >Subject: line for the outgoing mail. > I can help you with the first part, not the second. I have some perl utilities available from my site's Majordomo. Send the command "get public save-files" to Majordomo@cdsmn.mn.org to receive my perl script for separating articles into files. Also available is a file indexer ("index public" for example output) and a list creation script (you'll need to hack it to suit yourself, beware hard coded path names). Regards, Doug Plate Sr. From majordomo-users-owner Thu May 12 05:30:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA21894; Thu, 12 May 1994 05:30:55 GMT Received: from netcomsv.netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA21888; Wed, 11 May 1994 22:30:43 -0700 Received: from nightowl.UUCP by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id WAA29163; Wed, 11 May 1994 22:31:45 -0700 Received: from nightowl.qualtrak.com by QualTrak.COM (4.1/SMI-4.1) id AA02029; Wed, 11 May 94 22:28:40 PDT Received: from localhost by nightowl (8.6.5/1.37) id WAA00829; Wed, 11 May 1994 22:27:11 -0700 Message-Id: <199405120527.WAA00829@nightowl> To: essmjf@netcom.netcom.com (Michael Faklis) Cc: majordomo-users@greatcircle.com, procmail@informatik.rwth-aachen.de Subject: Re: Auto-Relying to Mail bounced from Majordomo ? In-Reply-To: Your message of "Wed, 11 May 1994 17:23:16 PDT." <199405120023.RAA26062@netcom.netcom.com> Date: Wed, 11 May 1994 22:27:10 -0700 From: John Birchfield Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199405120023.RAA26062@netcom.netcom.com>you write: >I'm the moderator of a Majordomo maillist and I use PROCMAIL to filter >my mail. My mailllist is for a national public radio show, and I need >to auto-reply to incoming mail (to the maillist) with a release form >to allow us to broadcast the email. Yes, it's true, some people are >shocked when their letter to a mail list for a national public radio >show is broadcasted over the air or distributed to the subscribers of >the mail list. > >My problem is that mail sent to the mail list has additional headers >added to the begining of the message, so the reply-to address is now >majordomo, and not the originator of the message. An example is >appended to this message. So, the note (as it appears in my inbox, >and as seen by PROCMAIL) has two From: headers. > >How can I get PROCMAIL to recognise the orignator's address, in stead >of where majordomo bounced the message from? > >An example follows; > >>From west_coast_live-owner Wed May 11 09:48:22 1994 >Return-Path: >Received: by mail.netcom.com (8.6.8.1/Netcom) id JAA08209; Wed, 11 May 1994 0 >9:37:42 -0700 >Date: Wed, 11 May 1994 09:37:42 -0700 >Message-Id: <199405111637.JAA08209@mail.netcom.com> >To: west_coast_live-owner@netcom.com >From: west_coast_live-owner@netcom.com >Subject: BOUNCE west_coast_live@netcom.com: Approval required >Status: RO > >>From essmjf Wed May 11 09:37:23 1994 >Return-Path: >Received: from gateway.rosedale.org by mail.netcom.com (8.6.8.1/Netcom) > id JAA08200; Wed, 11 May 1994 09:37:20 -0700 >Received: from pclan.rosedale.org by gateway.rosedale.org with SMTP id AA05629 > (5.65c/IDA-1.4.4 for ); Wed, 11 May 1994 12:35:4 >7 -0400 >Received: by pclan.rosedale.org; Wed, 11 May 94 12:43:18 EDT >Date: Wed, 11 May 94 12:37:59 EDT >Message-Id: >From: "michael faklis" >To: west_coast_live@netcom.com >Subject: Non-audience adventure >X-Incognito-Sn: 283 >X-Incognito-Format: VERSION=1.60f ENCRYPTED=NO > >Thanks for any insights. > >-- >Michael Faklis, Computer Scientist email: essmjf@netcom.com >Evolutionary Software Systems Phone: (415) 323-2222 >P.O. Box 1121 FAX: (415) 323-1417 >Palo Alto, California 94302-1121 > From majordomo-users-owner Thu May 12 15:52:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA24488; Thu, 12 May 1994 15:52:22 GMT Received: from inet-gw-2.pa.dec.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA24482; Thu, 12 May 1994 08:52:08 -0700 Received: from us4rmc.pko.dec.com by inet-gw-2.pa.dec.com (5.65/21Mar94) id AA13822; Thu, 12 May 94 08:48:24 -0700 Received: from wrksys.enet by us4rmc.pko.dec.com (5.65/rmc-22feb94) id AA19379; Thu, 12 May 94 11:51:36 -0400 Message-Id: <9405121551.AA19379@us4rmc.pko.dec.com> Received: from wrksys.enet; by us4rmc.enet; Thu, 12 May 94 11:51:37 EDT Date: Thu, 12 May 94 11:51:37 EDT From: Alpha Personal Systems -- DTN 223-5747 -- MLO5-2/36A To: majordomo-users@greatcircle.com Apparently-To: majordomo-users@greatcircle.com Subject: RE: Need help with resend and From, Reply-To fields Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I figured out what was wrong - I had stuck some arguments at the end of the "wrapper resend" command, after the mailing list name - oops! It seems to be working right now. - Jim From majordomo-users-owner Thu May 12 09:49:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA24924; Thu, 12 May 1994 16:41:29 GMT Received: from xmission.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA24918; Thu, 12 May 1994 09:41:01 -0700 Received: by xmission.com (4.1/Xmission/SMI-4.1) id AA22307; Thu, 12 May 94 10:41:25 MDT Date: Thu, 12 May 94 10:41:25 MDT From: pashdown@xmission.com (Pete Ashdown) Message-Id: <9405121641.AA22307@xmission.com> To: Majordomo-Users@GreatCircle.COM Subject: HELP! Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I just installed 1.90 and I'm having some real unexplained headaches with the .config files. 1. I used to have the list owner set to "listname-owner". Now resend insists that I should use "owner-listname_list". I want it BACK! Right now I'm trying to track this down, but problem #2 is getting in the way. 2. It is creating THREE config files for each list that has a digest. listname.config (which is what it should be IMHO) listname-digest.config listname_mailing_list.config and sometimes listname_list.config ARRGHGHGHGH!! I'm going ballistic! Why does an upgrade have to muck so many things up at once? From majordomo-users-owner Thu May 12 18:49:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA29583; Fri, 13 May 1994 01:32:50 GMT Received: from digi.syd.deg.csiro.au by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA29577; Thu, 12 May 1994 18:32:23 -0700 Received: by digi.syd.deg.csiro.au id AA17461 (5.67b/IDA-1.5 for majordomo-users@greatcircle.com); Fri, 13 May 1994 11:33:16 +1000 Date: Fri, 13 May 1994 11:27:00 +1000 (EST) From: Jack Churchill Subject: bounce testing To: majordomo-users@greatcircle.com In-Reply-To: <9405111747.AA25708@np2.watson.ibm.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've just installed Majordomo 1.90 and I wanted to test the bounce mechanism. So, I've added a non-existant user in one list for sendmail to bounce with a Unknown user error. However, I don't see this user removed from the list and placed on the bounces lists. The list-owner doen't get a message either. Using bounce manually works though. Any clues please? Everything works very well - nice package. -- Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From majordomo-users-owner Thu May 12 22:49:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA00602; Fri, 13 May 1994 05:18:13 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA00595; Thu, 12 May 1994 22:18:07 -0700 Message-Id: <199405130518.WAA00595@mycroft.GreatCircle.COM> To: Jack Churchill cc: majordomo-users@greatcircle.com Subject: Re: bounce testing In-reply-to: Your message of Fri, 13 May 1994 11:27:00 +1000 (EST) Date: Thu, 12 May 1994 22:18:05 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Jack Churchill writes: # I've just installed Majordomo 1.90 and I wanted to test the bounce # mechanism. So, I've added a non-existant user in one list for sendmail to # bounce with a Unknown user error. However, I don't see this user removed # from the list and placed on the bounces lists. The list-owner doen't get # a message either. Using bounce manually works though. Any clues please? # Everything works very well - nice package. Uh... Unless John Rouillard has changed things more than I think in 1.90, there is still no automatic bounce handling mechanism; you _have_ to run "bounce" manually. -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 May 13 07:16:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA01848; Fri, 13 May 1994 07:16:08 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA01842; Fri, 13 May 1994 00:15:59 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA21131 (5.65c/IDA-1.4.4 for ); Fri, 13 May 1994 03:16:27 -0400 Message-Id: <199405130716.AA21131@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: bounce testing In-Reply-To: Your message of "Thu, 12 May 1994 22:18:05 PDT." <199405130518.WAA00595@mycroft.GreatCircle.COM> Date: Fri, 13 May 1994 03:16:26 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199405130518.WAA00595@mycroft.GreatCircle.COM>, Brent Chapman writes: > Jack Churchill writes: > > # I've just installed Majordomo 1.90 and I wanted to test the bounce > # mechanism. So, I've added a non-existant user in one list for sendmail to > # bounce with a Unknown user error. However, I don't see this user removed > # from the list and placed on the bounces lists. The list-owner doen't get > # a message either. Using bounce manually works though. Any clues please? > # Everything works very well - nice package. > > Uh... Unless John Rouillard has changed things more than I think in > 1.90, there is still no automatic bounce handling mechanism; you > _have_ to run "bounce" manually. Brent's instincts are right in that there is no automatic bounce handling mechanism, but the list owner should get a messahe about the bounce. Things to check: 1) The alias owner-list points to list-owner (if you choose to use the list-owner alias) 2) The sender keyword in the config file is set to list-owner or owner-list. If neither of the above apply, try setting the "debug" keyword to true and look at the output of /usr/ucb/mail -v list" for clues about the envelope address and the message headers. -- John John Rouillard Special Projects Volunteer 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 May 13 11:05:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA03485; Fri, 13 May 1994 11:05:57 GMT Received: from campino.informatik.rwth-aachen.de by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id EAA03479; Fri, 13 May 1994 04:05:45 -0700 Received: from tabaqui (tabaqui.Informatik.RWTH-Aachen.DE) by campino.informatik.rwth-aachen.de (4.1/campino-5) id AA00417; Fri, 13 May 94 13:06:02 +0200 Received: by tabaqui (4.1/POOL.3) id AA21379; Fri, 13 May 94 13:05:35 +0200 Message-Id: <9405131105.AA21379@tabaqui> From: berg@pool.Informatik.RWTH-Aachen.DE (Stephen R. van den Berg) Date: Fri, 13 May 1994 13:05:34 +0200 In-Reply-To: Michael Faklis's message as of 1994 May 11 Wed 17:23. <199405120023.RAA26062@netcom.netcom.com> To: essmjf@netcom.com (Michael Faklis), majordomo-users@greatcircle.com, procmail@informatik.rwth-aachen.de Subject: Re: Auto-Relying to Mail bounced from Majordomo ? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Michael Faklis wrote: >my mail. My mailllist is for a national public radio show, and I need >to auto-reply to incoming mail (to the maillist) with a release form >to allow us to broadcast the email. Yes, it's true, some people are >My problem is that mail sent to the mail list has additional headers >added to the begining of the message, so the reply-to address is now >majordomo, and not the originator of the message. An example is >appended to this message. So, the note (as it appears in my inbox, >and as seen by PROCMAIL) has two From: headers. I'm of course no expert in majordomo mailinglist setup, but from the look of it, I'd say that majordomo is needlessly generating an extra header. A configuration problem perhaps? >How can I get PROCMAIL to recognise the orignator's address, in stead >of where majordomo bounced the message from? Presumably, inside of procmail, you're feeding the mail to "formail -r" somewhere to "reverse" the header and generate an auto-reply header. The simplest solution would probably be to simply delete the leading header first. I.e. feed it through: sed -e '1,/^$/ d' | formail -r A slightly more involved solution will be needed if you insist on getting the Subject: Re: line from the first header. >A [shortened] example follows; >From west_coast_live-owner Wed May 11 09:48:22 1994 >Return-Path: >To: west_coast_live-owner@netcom.com >From: west_coast_live-owner@netcom.com >Subject: BOUNCE west_coast_live@netcom.com: Approval required > >From essmjf Wed May 11 09:37:23 1994 >Return-Path: >From: "michael faklis" >To: west_coast_live@netcom.com >Subject: Non-audience adventure -- From majordomo-users-owner Fri May 13 15:34:35 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA04991; Fri, 13 May 1994 15:34:35 GMT Received: from mercury.SDL.usu.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA04983; Fri, 13 May 1994 08:34:19 -0700 Received: by mercury.SDL.usu.EDU (5.0/SMI-SVR4) id AA06575; Fri, 13 May 1994 08:48:56 +0700 Date: Fri, 13 May 1994 08:48:56 +0700 From: eyoung@mercury.SDL.usu.EDU (Ed Young) Message-Id: <9405131448.AA06575@mercury.SDL.usu.EDU> To: majordomo-users@GreatCircle.COM Subject: unknown user error X-Sun-Charset: US-ASCII content-length: 0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have majordomo running on 2 suns using Solaris2.3 and NIS+. They have been working admirably until yesterday. When I got this unknown user error. A debugging output follows; eyoung@zeus::/opt/mail>mailx -v test Subject: test of majordomo Cc: delete From majordomo-users-owner Mon May 16 04:01:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id EAA21880; Mon, 16 May 1994 04:01:39 GMT Received: from digi.syd.deg.csiro.au by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA21874; Sun, 15 May 1994 21:01:31 -0700 Received: by digi.syd.deg.csiro.au id AA15317 (5.67b/IDA-1.5 for majordomo-users@greatcircle.com); Mon, 16 May 1994 14:03:33 +1000 Date: Mon, 16 May 1994 13:57:03 +1000 (EST) From: Jack Churchill Subject: lost bounced 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 I've followed the suggestion is the installation notes and put the archive and digest programs in the outgoing lists. Everything is working fine except bounced messages caused by bad e-mail addresses are lost. That is, testlist: :include:/usr/local/majordom/lists/testlist works ok with bounced messages going to root testlist: "|/usr/local/majordom/bin/wrapper resend -l testlist -h full.domain.name testlist-outgoing" testlist-digest: testlist testlist-outgoing: :include:/usr/local/majordom/lists/testlist, "| /usr/local/majordom/bin/wrapper digest -r -C -l testlist-digest testlist-digest-outgoing", "| /usr/local/majordom/bin/wrapper archive2.pl -a -m -f /usr/local/majordom/archive/testlist/testlist" testlist-digest-outgoing: :include:/usr/local/majordom/lists/testlist-digest works ok but with no bounced messages for bad e-mail addresses. I'm using Ultrix and the latest IDA-sendmail. Please help. -- Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From majordomo-users-owner Mon May 16 13:54:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA24213; Mon, 16 May 1994 13:54:25 GMT Received: from mercury.SDL.usu.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA24207; Mon, 16 May 1994 06:54:18 -0700 Received: by mercury.SDL.usu.EDU (5.0/SMI-SVR4) id AA01839; Mon, 16 May 1994 07:55:26 +0700 Date: Mon, 16 May 1994 07:55:26 +0700 From: eyoung@mercury.SDL.usu.EDU (Ed Young) Message-Id: <9405161355.AA01839@mercury.SDL.usu.EDU> To: majordomo-users@GreatCircle.COM Subject: Re: unknown user error X-Sun-Charset: US-ASCII content-length: 724 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thanks, I blew it. Ed ----- Begin Included Message ----- >From corrigan@weber.ucsd.edu Fri May 13 20:15 MDT 1994 To: eyoung@SDL.usu.EDU (Ed Young) Reply-To: majordomo-users@GreatCircle.COM Subject: Re: unknown user error Mime-Version: 1.0 Content-Id: <25702.768881695.1@weber.ucsd.edu> Content-Type: text/plain; charset="us-ascii" Content-Length: 320 X-Lines: 13 Actually, no debugging output follows... > I have majordomo running on 2 suns using Solaris2.3 and NIS+. > > They have been working admirably until yesterday. When I got > this unknown user error. > A debugging output follows; > > eyoung@zeus::/opt/mail>mailx -v test > Subject: test of majordomo > Cc: > delete > ----- End Included Message ----- From majordomo-users-owner Mon May 16 17:41:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA25622; Mon, 16 May 1994 17:41:40 GMT Received: from mail.teleport.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA25616; Mon, 16 May 1994 10:41:33 -0700 Received: by mail.teleport.com (/\==/\ Smail3.1.28.1 #28.2) id ; Mon, 16 May 94 10:42 PDT Date: Mon, 16 May 1994 10:42:36 -0700 (PDT) From: Paradise Cowgirl Subject: Quick Question To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm currently using version 1.62 (with the version of resend that allows for "resend" files). If version 1.90 is installed, will I have to change any of my configuration (.closed, .passwd, etc) files immediately or can upgrade on a list by list basis? Thanks! >>-Darci-> -- ------ Paradise Cowgirl - minerva@teleport.com - minerva@netcom.com \ --/--- Boycott Rush Limbaugh oranges! \ \/ / Don't support discrimination and bigotry -- don't support the OCA! \/\ / http://vector.casti.com/QRD/.html/People/Darci.html \/ "What would happen if the far right held a campaign and nobody came?" -Lee Lynch From majordomo-users-owner Mon May 16 18:07:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA25780; Mon, 16 May 1994 18:07:30 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA25774; Mon, 16 May 1994 11:07:21 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HCETG4JQHC000ZCD@SYSWRK.UCIS.DAL.CA>; Mon, 16 May 1994 15:08:19 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HCETFUBDBK0077B4@AC.DAL.CA>; Mon, 16 May 1994 15:08:08 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA23761; Mon, 16 May 94 15:04:56 -0300 Date: Mon, 16 May 1994 15:04:55 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Mailing List Etiquette To: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9405161804.AA23761@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: 1091 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >From: arielle@taronga.com (Stephanie da Silva) > >He seems to think there's nothing wrong with sending email to lists one >doesn't belong to and in fact, it's a common practice, it happens all the >time. And that it's a *condoned* practice. His reasoning is that it's >okay to do it because there's nothing there stopping you (I was like, yeah, >there's nothing stopping people from forging to a moderated newsgroup but >that doesn't mean it's okay to do that) and he says there's nothing in >Usenet etiquette denouncing the practice. I see nothing wrong with this as a general practice, although in specific cases (such as the one you cite) it can be improper. I run a lot of scientific mailing lists, and if I spot an item that might be of interest to a particular group I post it to them. So long as the postings are appropriate, what is wrong with this? For example, if someone picks up some hot news about an outbreak of red tides or a new kind of shellfish poisoning, they would be welcome to share it with the phycotoxins mailing list whether they belong or not. Bill Silvert From majordomo-users-owner Tue May 17 13:17:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA02220; Tue, 17 May 1994 13:17:30 GMT Received: from loki.cee.hw.ac.uk by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA02214; Tue, 17 May 1994 06:17:18 -0700 Received: from danel.cee.hw.ac.uk by loki.cee.hw.ac.uk with smtp tap_id root (Smail3.1.28.1 #81) id m0q3O8D-000eHAC; Tue, 17 May 94 13:20 BST Received: by danel.cee.hw.ac.uk (Smail3.1.28.1 #27) id m0q3O60-000IeUC; Tue, 17 May 94 13:18 WET DST Message-Id: From: steve@cee.hw.ac.uk (Steve Salvini) Subject: digest & FROM/ERRORS-TO fields To: majordomo-users@GreatCircle.COM Date: Tue, 17 May 1994 13:18:03 +0100 (BST) Cc: steve@cee.hw.ac.uk (Steve Salvini) X-Motto: Forza Gran Bretagna! X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 604 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi - I've just upgraded to 1.90 and it looks great to me. Just one minor problem, I can't get the Errors-to: & From: header fields to include the domain part of my mail address when using 'digest' - it works fine for 'resend'. I want to have uk-hockey-digest-owner@cee.hw.ac.uk but I only get uk-hockey-digest-owner. I have resend_host = cee.hw.ac.uk and sender = uk-hockey-digest-owner in uk-hockey-digest.config. From teh commenst in the config file I thought that ought to do it - for now I've just hard-wired the FROM & ERRORS-TO variables in 'digest' :-( Help! Steve. From majordomo-users-owner Tue May 17 14:14:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA02519; Tue, 17 May 1994 14:14:45 GMT Received: from digi.syd.deg.csiro.au by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA02513; Tue, 17 May 1994 07:14:08 -0700 Received: by digi.syd.deg.csiro.au id AA25033 (5.67b/IDA-1.5 for majordomo-users@greatcircle.com); Wed, 18 May 1994 00:15:50 +1000 Date: Wed, 18 May 1994 00:03:19 +1000 (EST) From: Jack Churchill Subject: Re: lost bounced messages To: majordomo-users@greatcircle.com Cc: "John P. Rouillard" In-Reply-To: <199405160516.AA01013@cs.umb.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Update on my earlier problem with no bounced message to postmaster. I've managed to get it working by moving the include entry from the outgoing list to the list alias itself as follows. testl: :include:/usr/local/majordom/lists/testl, <--- addded this "|/usr/local/majordom/bin/wrapper resend -l testl -h my.host.name testl-outgoing" testl-digest: testl # ##testl-outgoing: :include:/usr/local/majordom/lists/testl, <--- removed this testl-outgoing: "| /usr/local/majordom/bin/wrapper digest -r -C -l testl-digest testl-digest-outgoing", "| /usr/local/majordom/bin/wrapper archive2.pl -a -m -f /usr/local/majordom/archive/testl/testl" So why is resend stopping bounced messages (i.e., undeliverable messages) from being sent? Could it be a quirk with IDA-sendmail? When I have time I might use the debug switch in perl (not majordomo) and step through the process to see if I can track down the problem. Also, am I doing something bad with the approach above that works? -- Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From majordomo-users-owner Tue May 17 19:11:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA04724; Tue, 17 May 1994 19:11:10 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA04718; Tue, 17 May 1994 12:10:54 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA18651 (5.65c/IDA-1.4.4 for ); Tue, 17 May 1994 15:11:44 -0400 Message-Id: <199405171911.AA18651@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: digest & FROM/ERRORS-TO fields In-Reply-To: Your message of "Tue, 17 May 1994 13:18:03 BST." Date: Tue, 17 May 1994 15:11:43 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Steve Salvini writes: > > Hi - I've just upgraded to 1.90 and it looks great to me. Just one > minor problem, I can't get the Errors-to: & From: header fields to > include the domain part of my mail address when using 'digest' - it > works fine for 'resend'. > > I want to have uk-hockey-digest-owner@cee.hw.ac.uk but I only get > uk-hockey-digest-owner. > > I have > > resend_host = cee.hw.ac.uk > and > sender = uk-hockey-digest-owner > > in uk-hockey-digest.config. From teh commenst in the config file > I thought that ought to do it - for now I've just hard-wired the FROM > & ERRORS-TO variables in 'digest' :-( > > Help! Ack a BUG BUG BUG BUG BUG!!! I goofed. There are two workarounds. 1) set sender to be: uk-hockey-digest-owner@cee.hw.ac.uk 2) Change the code that reads: $V{'ERRORS-TO'} = $config_opts{$opt_l,"sender"}; $V{'FROM'} = $config_opts{$opt_l, "sender"}; to read something like: $V{'ERRORS-TO'} = $config_opts{$opt_l,"sender"} . "@" . $config_opts{$opt_l,"resend_host"}; $V{'FROM'} = $config_opts{$opt_l, "sender"}. "@" . $config_opts{$opt_l,"resend_host"}; I have just fixed this in my 1.91 development tree. -- John John Rouillard Special Projects Volunteer 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 Tue May 17 20:05:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA05168; Tue, 17 May 1994 20:05:22 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA05162; Tue, 17 May 1994 13:05:08 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HCGBUL0Q4G00163X@SYSWRK.UCIS.DAL.CA>; Tue, 17 May 1994 17:06:10 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HCGBUBO6SG007O26@AC.DAL.CA>; Tue, 17 May 1994 17:05:58 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA04778; Tue, 17 May 94 17:02:47 -0300 Date: Tue, 17 May 1994 17:02:46 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Can some hostile addresses be parsed? To: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9405172002.AA04778@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: 716 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I didn't follow most of the discussion of hostile addresses, but suddenly (either because of a popular new list or because of the upgrade to 1.90) I'm having problems with Banyan Vines addresses. I get stuff like: /R=IML3/R=AM/U=user_name/FFN=USER_NAME/@mr.dfo.ca which is equivalent to user_name%AM%IML3@mr.dfo.ca, and apparently the translation conforms to standards. Any chance that these names could be parsed by majordomo (this is clearly something that perl can do) into a non-hostile form? -- Bill Silvert at the Bedford Institute of Oceanography P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2 InterNet Address: silvert@biome.bio.ns.ca (the address bill@biome.bio.ns.ca is only for mailing lists) From majordomo-users-owner Tue May 17 20:29:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA05296; Tue, 17 May 1994 20:29:53 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA05290; Tue, 17 May 1994 13:29:45 -0700 Received: from lunch.asd.sgi.com by sgi.sgi.com via SMTP (940510.SGI.8.6.9/910110.SGI) id NAA08322; Tue, 17 May 1994 13:30:55 -0700 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:majordomo-users@greatcircle.com id AA03175; Tue, 17 May 94 13:30:53 -0700 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9405172030.AA03175@lunch.asd.sgi.com> Subject: bug in 1.90 with mungedomain=yes To: majordomo-workers@greatcircle.com Date: Tue, 17 May 1994 13:30:52 -0700 (PDT) Cc: majordomo-users@greatcircle.com X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 927 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Sorry I didn't find this sooner. If you turn on mungedomain, addresses with no '@' will always fail in addr_match. The code in question is below: if ($partial == 2) { # see if addresses are foo@baz.bax.edu, foo@bax.edu local(@addr1,@addr2); @addr1 = split(/@/, $a1[0]); @addr2 = split(/@/, $a2[0]); if ( $#addr1 == $#addr2 && $#addr1 == 1 && $addr1[0] eq $addr2[0] && (index($addr1[1], $addr2[1]) >= $[)) { return(1); } else { return(undef); } } The problem is, if addr1 has no '@' character, $#addr1 will not == 1, and thus addr_match will fail. I would suggest changing the first line to: # see if non-matching addresses are foo@baz.bax.edu, foo@bax.edu if ($partial == 2 && $a1[0] ne $a2[0]) { -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Tue May 17 21:07:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA05613; Tue, 17 May 1994 21:07:13 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA05595; Tue, 17 May 1994 14:06:42 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA24846 (5.65c/IDA-1.4.4); Tue, 17 May 1994 17:07:38 -0400 Message-Id: <199405172107.AA24846@cs.umb.edu> To: pdc@lunch.asd.sgi.com (Paul Close) Cc: majordomo-workers@greatcircle.com, majordomo-users@greatcircle.com Subject: Re: bug in 1.90 with mungedomain=yes In-Reply-To: Your message of "Tue, 17 May 1994 13:30:52 PDT." <9405172030.AA03175@lunch.asd.sgi.com> Date: Tue, 17 May 1994 17:07:37 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405172030.AA03175@lunch.asd.sgi.com>, Paul Close writes: > Sorry I didn't find this sooner. If you turn on mungedomain, addresses with > no '@' will always fail in addr_match. The code in question is below: > [...] > The problem is, if addr1 has no '@' character, $#addr1 will not == 1, and > thus addr_match will fail. I would suggest changing the first line to: > > # see if non-matching addresses are foo@baz.bax.edu, foo@bax.edu > if ($partial == 2 && $a1[0] ne $a2[0]) { Got it. I put it into the 1.91 working tree. -- John John Rouillard Special Projects Volunteer 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 Tue May 17 21:27:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA05711; Tue, 17 May 1994 21:27:26 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA05705; Tue, 17 May 1994 14:27:13 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA25864 (5.65c/IDA-1.4.4 for ); Tue, 17 May 1994 17:27:53 -0400 Message-Id: <199405172127.AA25864@cs.umb.edu> To: bill@biome.bio.dfo.ca (Bill Silvert) Cc: majordomo-users@greatcircle.com Subject: Re: Can some hostile addresses be parsed? In-Reply-To: Your message of "Tue, 17 May 1994 17:02:46 -0300." <9405172002.AA04778@biome.bio.ns.ca> Date: Tue, 17 May 1994 17:27:51 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405172002.AA04778@biome.bio.ns.ca>, Bill Silvert writes: > I didn't follow most of the discussion of hostile addresses, but > suddenly (either because of a popular new list or because of the upgrade > to 1.90) I'm having problems with Banyan Vines addresses. I get stuff > like: > /R=IML3/R=AM/U=user_name/FFN=USER_NAME/@mr.dfo.ca > Yup that looks like an internet->X.400 translation, transliteration, munging, trashing. > which is equivalent to user_name%AM%IML3@mr.dfo.ca, and apparently the > translation conforms to standards. Any chance that these names could be > parsed by majordomo (this is clearly something that perl can do) into a > non-hostile form? The problem is that there is no great way to handle it. I know of one vendor sendmail that will happily try to write to a file of that name. Sendmail 8.6 on the otherhand won't attempt to treat it as a file since it has an @ in it. I think the best we can do is something like: if there is a / at the front of the address, split the address on / does the first component of the address exist, if so bounce the address. (Anybody who has a subdirectory of / with an = sign in the name should lose.) if the first component doesn't exist, accept the address. To do this change the code in main'valid_addr to something like: sub main'valid_addr { local($addr) = @_; local(@addrs,@components) = (); # Parse the address out into parts @addrs = &main'ParseAddrs($addr); # if there's not exactly 1 part, it's no good if ($#addrs != 0) { return undef; } # if there's a "|" in it, it's hostile if (m/|/) { &main'abort("HOSTILE ADDRESS $addr"); return undef; } local($_) = $addrs[0]; if (m#^/#) { @components = split(/\//, $_); if ( -e "/$components[0]" ) { &main'abort("HOSTILE ADDRESS $addr"); return undef; } } return $_; } Quips, comments, evasions, questions, answers, testers? This is what I will use in 1.91 if somebody can test it and tell me that it works properly, otherwise I'll just stay with the current valid_addr. -- John John Rouillard Special Projects Volunteer 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 Tue May 17 21:40:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA05844; Tue, 17 May 1994 21:40:30 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA05837; Tue, 17 May 1994 14:40:23 -0700 Message-Id: <199405172140.OAA05837@mycroft.GreatCircle.COM> To: "John P. Rouillard" Cc: majordomo-users@greatcircle.com Subject: Re: Can some hostile addresses be parsed? In-reply-to: Your message of Tue, 17 May 1994 17:27:51 -0400 Date: Tue, 17 May 1994 14:40:21 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "John P. Rouillard" writes: # The problem is that there is no great way to handle it. I know of one # vendor sendmail that will happily try to write to a file of that # name. Sendmail 8.6 on the otherhand won't attempt to treat it as a # file since it has an @ in it. I think the best we can do is something # like: # # # if there is a / at the front of the address, # # split the address on / # # does the first component of the address exist, if so bounce # the address. (Anybody who has a subdirectory of / with # an = sign in the name should lose.) # # if the first component doesn't exist, accept the address. Not all of them begin with "/". I'd suggest adding a flag to make the whole "Hostile address" check optional (but leave it enabled by default). -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 Tue May 17 21:52:59 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA05963; Tue, 17 May 1994 21:52:59 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA05957; Tue, 17 May 1994 14:52:31 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA27437 (5.65c/IDA-1.4.4); Tue, 17 May 1994 17:53:16 -0400 Message-Id: <199405172153.AA27437@cs.umb.edu> To: Brent Chapman Cc: majordomo-users@greatcircle.com Subject: Re: Can some hostile addresses be parsed? In-Reply-To: Your message of "Tue, 17 May 1994 14:40:21 PDT." <199405172140.OAA05837@mycroft.GreatCircle.COM> Date: Tue, 17 May 1994 17:53:15 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199405172140.OAA05837@mycroft.GreatCircle.COM>, Brent Chapman writes: > "John P. Rouillard" writes: > > # The problem is that there is no great way to handle it. I know of one > # vendor sendmail that will happily try to write to a file of that > # name. Sendmail 8.6 on the otherhand won't attempt to treat it as a > # file since it has an @ in it. I think the best we can do is something > # like: > # > # > # if there is a / at the front of the address, > # > # split the address on / > # > # does the first component of the address exist, if so bounce > # the address. (Anybody who has a subdirectory of / wit > h > # an = sign in the name should lose.) > # > # if the first component doesn't exist, accept the address. > > Not all of them begin with "/". Are you sure, every X.400 address (mapped into internet space) I've seen starts with a "/". I think the / is an introducer (wrong term I know) to the address space. As I remember, the inital '/' was required according to the RFC that defines mapping from X.400 to Internet addresses. Does anybody out ther have the RFC and can check/verify this assumption of mine. I know of no sendmail that will use: test: tmp/foo as a file. All sendmails I have seen (BSD 4.2, SunOS, IDA, King James, 8.6) check for a fully specified filename, i.e. one with a "/" at the front, but I can belive such a dain-bramage sendmail exists. Maybe the check should be rewritten to include: if there is no / at the front, but there are internal /'s bounce the address. > I'd suggest adding a flag to make the whole "Hostile address" check > optional (but leave it enabled by default). Well, this is something that should not be left to the discresion of the list administrator. It should be under the sole control of the majordomo admin. If the majordomo admin wants to allow it, s/he can modify the valid_addr function directly and remove the '/' check, right? -- John John Rouillard Special Projects Volunteer 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 Tue May 17 22:22:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA06106; Tue, 17 May 1994 22:22:06 GMT Received: from hplms26.hpl.hp.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA06100; Tue, 17 May 1994 15:21:47 -0700 Received: from hplabsz.hpl.hp.com by hplms26.hpl.hp.com with SMTP (1.36.108.4/15.5+ECS 3.3+HPL1.1S) id AA28559; Tue, 17 May 1994 15:24:15 -0700 Received: by hplabsz.hpl.hp.com (1.37.109.8/15.5+ECS 3.3+HPL1.1) id AA23302; Tue, 17 May 1994 15:24:52 -0700 From: "Laura de Leon" Message-Id: <9405171524.ZM23300@hplabsz.hpl.hp.com> Date: Tue, 17 May 1994 15:24:52 -0700 In-Reply-To: "John P. Rouillard" "Re: Can some hostile addresses be parsed?" (May 17, 5:53pm) References: <199405172153.AA27437@cs.umb.edu> X-Mailer: Z-Mail (3.0.0 15dec93) To: "John P. Rouillard" , Brent Chapman Subject: Re: Can some hostile addresses be parsed? Cc: majordomo-users@GreatCircle.COM Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On May 17, 5:53pm, John P. Rouillard wrote: > > > > Not all of them begin with "/". > > Are you sure, every X.400 address (mapped into internet space) I've > seen starts with a "/". I think the / is an introducer (wrong term I > know) to the address space. As I remember, the inital '/' was required > according to the RFC that defines mapping from X.400 to Internet > addresses. Does anybody out ther have the RFC and can check/verify > this assumption of mine. I can't check the RFC right now, but I know quite a few addresses come out of HP looking like last_first/node@gateway.dom.hp.com These addresses are from HP's Openmail mail system, and all mail coming from HP's mail system on the MPE systems come through these gateways when going to Unix, and the wider world. I hope that someone checked the RFC before settling on that form of address, but I was not involved, and can't say for certain. laura de leon deleon@hpl.hp.com From majordomo-users-owner Tue May 17 16:19:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA06207; Tue, 17 May 1994 22:37:37 GMT Received: from weber.ucsd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA06201; Tue, 17 May 1994 15:37:27 -0700 Received: from localhost (corrigan@localhost [127.0.0.1]) by weber.ucsd.edu (8.6.9/8.6.9) with ESMTP id PAA14039 for ; Tue, 17 May 1994 15:38:32 -0700 Message-Id: <199405172238.PAA14039@weber.ucsd.edu> To: majordomo-users@greatcircle.com Subject: Re: Can some hostile addresses be parsed? In-reply-to: Your message of "Tue, 17 May 1994 17:53:15 -0400." <199405172153.AA27437@cs.umb.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14034.769214311.1@weber.ucsd.edu> Date: Tue, 17 May 1994 15:38:32 -0700 From: "Michael J. Corrigan" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >From rfc 1123: 5.2.16 RFC-822 Local-part: RFC-822 Section 6.2 The basic mailbox address specification has the form: "local- part@domain". Here "local-part", sometimes called the "left- hand side" of the address, is domain-dependent. A host that is forwarding the message but is not the destination host implied by the right-hand side "domain" MUST NOT interpret or modify the "local-part" of the address. From majordomo-users-owner Wed May 18 00:55:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA07961; Wed, 18 May 1994 00:55:42 GMT Received: from hp.k12.ar.us by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA07955; Tue, 17 May 1994 17:55:31 -0700 Received: by hp.k12.ar.us (1.37.109.4/16.2) id AA25779; Tue, 17 May 94 19:55:28 -0500 Date: Tue, 17 May 1994 19:55:28 -0500 (CDT) From: Gary Day Subject: Linux - anything odd? To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm trying to put majordomo up on a linux system. I'm new at mailing lists so, no, I'm not sure I'm doing all the right things. Just as a good starting point I'd like to know if: 1. Linux has anything odd about the setup not in the instructions? 2. What kinds of testing methods would reveal more information that would be useful to those that might help me? {I use pine normally, but reading the instructions had me try sendmail directly with -v and it seemed interesting, but I'm still not sure what is wrong.} From majordomo-users-owner Wed May 18 01:26:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA08229; Wed, 18 May 1994 01:26:13 GMT Received: from hp.k12.ar.us by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA08106; Tue, 17 May 1994 18:08:42 -0700 Received: by hp.k12.ar.us (1.37.109.4/16.2) id AA25948; Tue, 17 May 94 20:08:36 -0500 Date: Tue, 17 May 1994 20:08:36 -0500 (CDT) From: Gary Day Subject: Linux - anything odd - part 2 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 Just in case this will help, here is the sendmail verbose output to a subscribe message: ======================================================== write_log:received | from: gday | program: sendmail | size: 90 bytes director aliases: matched majordomo, aliased to "|/usr/local/majordomo/bin/wrapp er majordomo" directed majordomo --> "|/usr/local/majordomo/bin/wrapper majordomo" ... sen d to pipe transport transport pipe uses driver pipe pipe: exec: "/bin/sh" "-c" "/usr/local/majordomo/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:se nder_proto:with $sender_proto }($osname Smail$version #$compile_num) } write_log:note: "|/usr/local/majordomo/bin/wrapper majordomo" ... transport pipe : child returned status EX_2 (2) write_log:delivered | to: /usr/local/majordomo/bin/wrapper majordomo | orig-to: majordomo | director: aliases | transport: pipe From majordomo-users-owner Wed May 18 02:29:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA08728; Wed, 18 May 1994 02:29:10 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA08721; Tue, 17 May 1994 19:29:01 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA12022 (5.65c/IDA-1.4.4 for ); Tue, 17 May 1994 22:30:09 -0400 Message-Id: <199405180230.AA12022@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: Can some hostile addresses be parsed? In-Reply-To: Your message of "Tue, 17 May 1994 15:38:32 PDT." <199405172238.PAA14039@weber.ucsd.edu> Date: Tue, 17 May 1994 22:30:08 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199405172238.PAA14039@weber.ucsd.edu>, "Michael J. Corrigan" writes: > >From rfc 1123: > > 5.2.16 RFC-822 Local-part: RFC-822 Section 6.2 > > The basic mailbox address specification has the form: "local- > part@domain". Here "local-part", sometimes called the "left- > hand side" of the address, is domain-dependent. > > A host that is forwarding the message but is not the > destination host implied by the right-hand side "domain" MUST > NOT interpret or modify the "local-part" of the address. Sorry, I should have been more explicit. I think the rfc I wanted was 1327 which explains mapping from X.400->rfc822 space. Wile pure X.400 addresses may be an issue in the future, I hope not in my lifetime 8-). It seems (from my reading of the grammar) that / is always the leading character in an rfc 822 encoding of the X.400 address. In message <9405171524.ZM23300@hplabsz.hpl.hp.com>, "Laura de Leon" writes: > On May 17, 5:53pm, John P. Rouillard wrote: > > > > > > Not all of them begin with "/". > > > > Are you sure, every X.400 address (mapped into internet space) I've > > seen starts with a "/". I think the / is an introducer (wrong term I > > know) to the address space. As I remember, the inital '/' was required > > according to the RFC that defines mapping from X.400 to Internet > > addresses. Does anybody out ther have the RFC and can check/verify > > this assumption of mine. > > I can't check the RFC right now, but I know quite a few addresses come > out of HP looking like last_first/node@gateway.dom.hp.com Sigh. That definately isn't an X.400 name/value paried address, but it would certainly trigger the hostile address setup unless I limited the checks for a / to the initial charater of the string. > I hope that someone checked the RFC before settling on that form of > address, but I was not involved, and can't say for certain. As rfc 1123 says above, it has to be a valid address since nearly anything goes in the local part of an rfc822 address, but I still say blech. I guess its time to post to comp.mail.sendmail to see if anybody's sendmail interprets "text/text" as a file name. -- John John Rouillard Special Projects Volunteer 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. -- John John Rouillard Special Projects Volunteer 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 Tue May 17 23:20:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA09457; Wed, 18 May 1994 05:59:21 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA08821; Tue, 17 May 1994 19:36:51 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA12375 (5.65c/IDA-1.4.4 for ); Tue, 17 May 1994 22:37:52 -0400 Message-Id: <199405180237.AA12375@cs.umb.edu> To: Gary Day Cc: majordomo-users@greatcircle.com Subject: Re: Linux - anything odd - part 2 In-Reply-To: Your message of "Tue, 17 May 1994 20:08:36 CDT." Date: Tue, 17 May 1994 22:37:51 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Gary Day writes: > Just in case this will help, here is the sendmail verbose output to a > subscribe message: > > ======================================================== > write_log:note: "|/usr/local/majordomo/bin/wrapper majordomo" ... > transport pipe : child returned status EX_2 (2) Make sure that the perl program is in the location expected by the wrapper, and make sure that the #! magic number in the majordomo script is the same location that perl is on your system. Check the README and the FAQ for more debugging tips. Also look at the wrapper for the locations where it exits with status 2. > write_log:delivered > | to: /usr/local/majordomo/bin/wrapper majordomo > | orig-to: majordomo > | director: aliases > | transport: pipe By the way what version of sendmail are you running? I am not familiar with this debugging output. -- John John Rouillard Special Projects Volunteer 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 May 18 06:49:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA09841; Wed, 18 May 1994 06:49:52 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA09835; Tue, 17 May 1994 23:49:43 -0700 Received: by netcom.com (8.6.8.1/SMI-4.1/Netcom) id XAA06032; Tue, 17 May 1994 23:51:01 -0700 Date: Tue, 17 May 1994 23:51:00 -0700 (PDT) From: Dick Moores Reply-To: Dick Moores Subject: Majordomo list additions--Thank You! To: Majordomo-users@GreatCircle.COM In-Reply-To: <199405180606.GAA09569@mycroft.GreatCircle.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk A while back I asked for help in adding to my list of majordomos. The response was terrific! Here's my list now with 29 majordomos. Any more? majordomo@acpub.duke.edu majordomo@baylisa.org majordomo@bolis.sf-bay.org majordomo@cac.washington.edu majordomo@connect.com.au majordomo@coombs.anu.edu.au majordomo@cs.umbc.edu majordomo@disserv.stu.umn.edu majordomo@gemstar.com majordomo@greatcircle.com majordomo@halcyon.com majordomo@is.internic.net majordomo@math.ohio-state.edu majordomo@mcs.net majordomo@mlo.dec.com majordomo@mtu.edu majordomo@netcom.com majordomo@netmgrs.co.uk majordomo@oi.uchicago.edu majordomo@ornl.gov majordomo@plts.org majordomo@svcdudes.com majordomo@toad.com majordomo@traffic.engr.washington.edu majordomo@ucar.edu majordomo@usenix.org majordomo@warren.mentorg.com majordomo@world.std.com majordomo@xmission.com From majordomo-users-owner Wed May 18 14:42:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA13209; Wed, 18 May 1994 14:42:53 GMT Received: from ritz.mordor.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA13197; Wed, 18 May 1994 07:42:24 -0700 Received: from terrapin.UUCP (terrapin@localhost) by ritz.mordor.com (8.6.8/8.6.7) with UUCP id KAA25461 for majordomo-users@greatcircle.com; Wed, 18 May 1994 10:37:50 -0400 Received: by Xyzzy.COM (4.1/SMI-4.1) id AA19375; Wed, 18 May 94 10:34:45 EDT Date: Wed, 18 May 94 10:34:45 EDT From: reb@xyzzy.com Message-Id: <9405181434.AA19375@Xyzzy.COM> To: majordomo-users@greatcircle.com Subject: Permission problems on SunOS 4.1.3_U1 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Help! I find I can't get Majordomo to work unless I set the permissions on its directory structure open to the world, and even then I have problems. I've got the binaries (& perl stuff) in /usr/local/majordomo and the list stuff, log, and archive in /install/lists ... I think I followed all the instructions, but even when I set the permissions on the directories to 777 I get the following error when I try to send something to the list. 550 /install/lists/archive/listname... Can't create output By the way, the wrapper is owned by daemon, group majordomo. Its permissions are 6775. Also, it never creates a log file or gives me an error that it can't. I'm sure it's something stupid I'm overlooking. I have no idea why the permissions need to be set so loosely on the main directory structures. That bothers me too. Any help would be appreciated. reb reb@xyzzy.com From majordomo-users-owner Wed May 18 15:11:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA13360; Wed, 18 May 1994 15:11:47 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA13354; Wed, 18 May 1994 08:11:38 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id LAA07741; Wed, 18 May 1994 11:12:34 -0400 Message-Id: <199405181512.LAA07741@bosnia.pop.psu.edu> To: reb@xyzzy.com Cc: majordomo-users@greatcircle.com Subject: Re: Permission problems on SunOS 4.1.3_U1 In-reply-to: Your message of "Wed, 18 May 1994 10:34:45 EDT." <9405181434.AA19375@Xyzzy.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, 18 May 1994 11:12:33 -0400 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405181434.AA19375@Xyzzy.COM>, reb@xyzzy.com writes: >Help! > >550 /install/lists/archive/listname... Can't create output in order to archive messages, you need to pass the message to one of the archive programs. (I use archive2.pl, in the contrib/ directory) See the README. >By the way, the wrapper is owned by daemon, group majordomo. Its >permissions are 6775. Also, it never creates a log file or gives me >an error that it can't. Are you sure that the majordomo.cf is right? Are you sure that all invocations of majordomo and friends are wrapped by the wrapper first? It helps if you'd include the aliases you're using for the list, as well as for majordomo. --Dave From majordomo-users-owner Wed May 18 20:43:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA16504; Wed, 18 May 1994 20:43:52 GMT Received: from ritz.mordor.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA16497; Wed, 18 May 1994 13:42:55 -0700 Received: from terrapin.UUCP (terrapin@localhost) by ritz.mordor.com (8.6.8/8.6.7) with UUCP id QAA05730 for majordomo-users@greatcircle.com; Wed, 18 May 1994 16:38:54 -0400 Received: by Xyzzy.COM (4.1/SMI-4.1) id AA21190; Wed, 18 May 94 16:34:27 EDT Date: Wed, 18 May 94 16:34:27 EDT From: reb@xyzzy.com Message-Id: <9405182034.AA21190@Xyzzy.COM> To: ritz!pop.psu.edu!barr@spcvxa.spc.EDU Cc: majordomo-users@greatcircle.com In-Reply-To: <199405181512.LAA07741@bosnia.pop.psu.edu> (ritz!pop.psu.edu!barr) Subject: Re: Permission problems on SunOS 4.1.3_U1 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Okay, here is more information... (and of course in trying to fix this I've gotten part way but now have other related problems ;-) I'm pretty sure almost everything is set up correctly. I know it's a permission problem. Things run fine if I run them from user 'majordom'. But, if I try to subscribe from a list as user 'test' I get errors because apparantly it's executing the wrapper as user 'test' ... I've tried setting the execution user & group IDs on the wrapper to no avail. It's set to run as daemon. Daemon is part of the majordom group. The directories are owned by user majordom group majordom. What am I overlooking? Any suggestions? Aliases are set up as follows: listname: "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l listname -f Listname-Owner -h Xyzzy.COM -s listname-outgoing" owner-listname: listname-owner listname-outgoing: :include:/install/lists/listname, "|/usr/local/majordomo/wrapper archive2.pl -a -m -f /install/lists/archive/listname/listname.archive" majordomo: "|/install/majordomo/wrapper majordomo" [and a few others pointing to each other deleted for sake of brevity] Errors I now get are: Can't append to /install/lists/listname: Permission denied ABORT Can't append to /install/lists/listname: Permission denied at /usr/local/majordomo/majordomo.pl line 209. "|/install/majordomo/wrapper majordomo"... unknown mailer error 13 As noted above, I get the above when sending a subscribe message as 'test' ... works fine if I run it as 'majordom' reb From majordomo-users-owner Wed May 18 23:52:36 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA17500; Wed, 18 May 1994 23:52:36 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA17494; Wed, 18 May 1994 16:52:28 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA15648 (5.65c/IDA-1.4.4 for ); Wed, 18 May 1994 19:53:30 -0400 Message-Id: <199405182353.AA15648@cs.umb.edu> To: reb@xyzzy.com Cc: majordomo-users@greatcircle.com Subject: Re: Permission problems on SunOS 4.1.3_U1 In-Reply-To: Your message of "Wed, 18 May 1994 16:34:27 EDT." <9405182034.AA21190@Xyzzy.COM> Date: Wed, 18 May 1994 19:53:29 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405182034.AA21190@Xyzzy.COM>, reb@xyzzy.com writes: > Okay, here is more information... (and of course in trying to fix this > I've gotten part way but now have other related problems ;-) > > I'm pretty sure almost everything is set up correctly. I know it's a > permission problem. Things run fine if I run them from user > 'majordom'. But, if I try to subscribe from a list as user 'test' I > get errors because apparantly it's executing the wrapper as user > 'test' ... I've tried setting the execution user & group IDs on the > wrapper to no avail. It's set to run as daemon. Daemon is part of > the majordom group. The directories are owned by user majordom group > majordom. What am I overlooking? Any suggestions? > [...] > As noted above, I get the above when sending a subscribe message as > 'test' ... works fine if I run it as 'majordom' Make sure the fileystem the wrapper is on isn't mounted nosuid. -- John John Rouillard Special Projects Volunteer 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 May 19 07:44:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA18984; Thu, 19 May 1994 07:44:47 GMT Received: from digi.syd.deg.csiro.au by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA18978; Thu, 19 May 1994 00:44:34 -0700 Received: by digi.syd.deg.csiro.au id AA20093 (5.67b/IDA-1.5 for majordomo-users@greatcircle.com); Thu, 19 May 1994 17:46:19 +1000 Date: Thu, 19 May 1994 17:39:40 +1000 (EST) From: Jack Churchill Subject: Re: lost bounced messages To: majordomo-users@greatcircle.com In-Reply-To: <199405171858.AA18139@cs.umb.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Finally fixed the problem I've been having although I don't fully understand why. The Precedence: bulk header was causing IDA sendmail to junk the mail. A message kept coming from IDA sendmail "Dumping junk mail" when executed in verbose mode. By removing the Precedence header the bounced messages got through. Is there any penalty leaving out the precedence header? -- Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From majordomo-users-owner Thu May 19 03:40:16 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA19554; Thu, 19 May 1994 09:24:13 GMT Received: from ns.elsevier.nl by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA19548; Thu, 19 May 1994 02:23:55 -0700 Received: from elrond (actually elrond.elsevier.nl) by ns.elsevier.nl with SMTP (PP); Thu, 19 May 1994 11:27:53 +0200 Received: by elrond (4.1) id AA16714; Thu, 19 May 94 11:24:59 +0200 Message-Id: <9405190924.AA16714@elrond> To: majordomo-users@greatcircle.com Reply-To: f.scholtens@elsevier.nl Subject: Re: Permission problems on SunOS 4.1.3_U1 In-Reply-To: Your message of "Wed, 18 May 1994 16:34:45 +0200." <9405181434.AA19375@Xyzzy.COM> Date: Thu, 19 May 1994 11:25:16 +0200 From: Frank Scholtens Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Help! > > I find I can't get Majordomo to work unless I set the permissions on its > directory structure open to the world, and even then I have problems. > > I've got the binaries (& perl stuff) in /usr/local/majordomo and the > list stuff, log, and archive in /install/lists ... > > I think I followed all the instructions, but even when I set the > permissions on the directories to 777 I get the following error when I > try to send something to the list. > > 550 /install/lists/archive/listname... Can't create output > > By the way, the wrapper is owned by daemon, group majordomo. Its > permissions are 6775. Also, it never creates a log file or gives me > an error that it can't. > I set the owner of the lists and log directory to daemon too and it worked on my Sun. Frank Scholtens From majordomo-users-owner Thu May 19 15:56:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA21082; Thu, 19 May 1994 15:56:22 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA21076; Thu, 19 May 1994 08:56:04 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA02792 (5.65c/IDA-1.4.4 for ); Thu, 19 May 1994 11:56:47 -0400 Message-Id: <199405191556.AA02792@cs.umb.edu> To: Jack Churchill Cc: majordomo-users@greatcircle.com Subject: Re: lost bounced messages In-Reply-To: Your message of "Thu, 19 May 1994 17:39:40 +1000." Date: Thu, 19 May 1994 11:56:46 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Jack Churchill writes: > Finally fixed the problem I've been having although I don't fully > understand why. The Precedence: bulk header was causing IDA sendmail to > junk the mail. A message kept coming from IDA sendmail "Dumping junk > mail" when executed in verbose mode. By removing the Precedence header > the bounced messages got through. > > Is there any penalty leaving out the precedence header? I should have figured. No there is no penalty other than not receiving the bounce messages. -- John John Rouillard Special Projects Volunteer 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 May 19 10:10:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA21532; Thu, 19 May 1994 16:53:23 GMT Received: from research1.bryant.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA21525; Thu, 19 May 1994 09:53:01 -0700 Received: by research1.bryant.edu (5.65/DEC-Ultrix/4.3) id AA21498; Thu, 19 May 1994 12:52:49 -0400 Date: Thu, 19 May 1994 12:52:48 -0400 (EDT) From: Stephen Frazier To: majordomo-users@greatcircle.com In-Reply-To: <199405191618.QAA21283@mycroft.GreatCircle.COM> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi! I'm trying to set up Majordomo on a DEC 3000/600 running OSF/1 v. 2.0. The machine is not currently connected to the net but has perl-4.036 installed. If someone has had experience with the DEC alpha or can point me in the right direction, I sure would appreciate help. Most likely, however, it is not a machine specific problem... :-) I've been following the information provided in the majordomo.manual (from the Nutshell Handbook "Managing Internet Information Services"... copying the alias file information. I used the POSIX information in the Makefile (although I am not certain if this is correct). Also, I have changed the perl variables as noted in the manual... but also left those that it did not reference in the majordomo.cf file. Initially, I got the following error when attempting to send the help command: % echo help | /usr/lib/sendmail -v majordomo majordomo... aliased to "|/usr/local/majordomo/bin/wrapper majordomo" "|/usr/local/majordomo/bin/wrapper majordomo"... Connecting to (prog)... about to exec majordomo: Permission denied "|/usr/local/majordomo/bin/wrapper majordomo"... unknown mailer error 5 owner-majordomo... aliased to majordomo-owner majordomo-owner... aliased to steve steve... Connecting to (local)... about to exec steve... Sent I then decided to change permissions in /usr/local/majordomo/bin to 775... and now I am receiving memory faults: % echo help | /usr/lib/sendmail -v majordomo majordomo... aliased to "|/usr/local/majordomo/bin/wrapper majordomo" "|/usr/local/majordomo/bin/wrapper majordomo"... Connecting to (prog)... about to exec sh: 24276 Memory fault "|/usr/local/majordomo/bin/wrapper majordomo"... unknown mailer error 139 owner-majordomo... aliased to majordomo-owner majordomo-owner... aliased to steve steve... Connecting to (local)... about to exec steve... Sent Thanks! I'm at a loss as to what to try next. -- Stephen L. Frazier Mgr. of Academic Computing Research Bryant College 401-232-6363 _/_/_/ _/_/_/ _/ _/_/_/ _/ _/_/_/ _/_/_/ _/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/_/_/ _/_/_/ _/ _/ _/ _/ _/_/_/ _/_/_/ _/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/ _/ _/_/_/ _/ _/ From majordomo-users-owner Thu May 19 18:06:48 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA22221; Thu, 19 May 1994 18:06:48 GMT Received: from weber.ucsd.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA22215; Thu, 19 May 1994 11:06:28 -0700 Received: from localhost (corrigan@localhost [127.0.0.1]) by weber.ucsd.edu (8.6.9/8.6.9) with ESMTP id LAA14933; Thu, 19 May 1994 11:07:15 -0700 Message-Id: <199405191807.LAA14933@weber.ucsd.edu> To: Stephen Frazier Cc: majordomo-users@GreatCircle.COM Reply-To: majordomo-users@GreatCircle.COM In-reply-to: Your message of "Thu, 19 May 1994 12:52:48 -0400." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14928.769370834.1@weber.ucsd.edu> Date: Thu, 19 May 1994 11:07:14 -0700 From: "Michael J. Corrigan" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dunno DEC Alpha, but some things to try, check: 1. maybe some other permissions are wrong - what are the perms on majordomo itself ? 2. Is the path #!/usr/local/bin/perl in line 1 of majordomo right ? 3. Is the permission of wrapper right ? suid root (recommended for POSIX situations) 4. You could try making sure that the prog mailer works: alias: "| /bin/tee /tmp/a" see if mail to alias ends up in /tmp/a 5. You could make sure that wrapper works: Recompile cc -DBIN=\"/bin\" -o wrapper2 wrapper.c put wrapper2 in /usr/local/bin, 755 make an alias alias2: "| /usr/local/bin/wrapper2 tee /tmp/b" and see if mail to alias2 comes out in /tmp/b. (Remove these aliases afterwards). 6. (Does #!work ?) -mike > Hi! > > I'm trying to set up Majordomo on a DEC 3000/600 running OSF/1 v. 2.0. > The machine is not currently connected to the net but has perl-4.036 > installed. If someone has had experience with the DEC alpha or can point > me in the right direction, I sure would appreciate help. Most likely, > however, it is not a machine specific problem... :-) > > I've been following the information provided in the majordomo.manual > (from the Nutshell Handbook "Managing Internet Information Services"... > copying the alias file information. I used the POSIX information in the > Makefile (although I am not certain if this is correct). Also, I have > changed the perl variables as noted in the manual... but also left those > that it did not reference in the majordomo.cf file. > > Initially, I got the following error when attempting to send the help > command: > > % echo help | /usr/lib/sendmail -v majordomo > majordomo... aliased to "|/usr/local/majordomo/bin/wrapper majordomo" > "|/usr/local/majordomo/bin/wrapper majordomo"... Connecting to (prog)... > about to exec > majordomo: Permission denied > "|/usr/local/majordomo/bin/wrapper majordomo"... unknown mailer error 5 > owner-majordomo... aliased to majordomo-owner > majordomo-owner... aliased to steve > steve... Connecting to (local)... > about to exec > steve... Sent > > > I then decided to change permissions in /usr/local/majordomo/bin to > 775... and now I am receiving memory faults: > > % echo help | /usr/lib/sendmail -v majordomo > majordomo... aliased to "|/usr/local/majordomo/bin/wrapper majordomo" > "|/usr/local/majordomo/bin/wrapper majordomo"... Connecting to (prog)... > about to exec > sh: 24276 Memory fault > "|/usr/local/majordomo/bin/wrapper majordomo"... unknown mailer error 139 > owner-majordomo... aliased to majordomo-owner > majordomo-owner... aliased to steve > steve... Connecting to (local)... > about to exec > steve... Sent > > Thanks! I'm at a loss as to what to try next. > > -- > Stephen L. Frazier > Mgr. of Academic Computing Research > Bryant College > 401-232-6363 > > > > _/_/_/ _/_/_/ _/ _/_/_/ _/ _/_/_/ _/_/_/ > _/ _/ _/ _/_/ _/ _/ _/ _/ _/ > _/_/_/ _/_/_/ _/ _/ _/ _/ _/_/_/ _/_/_/ > _/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/ > _/ _/ _/ _/ _/ _/_/_/ _/ _/_/_/ _/ _/ > > From majordomo-users-owner Thu May 19 20:24:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA23239; Thu, 19 May 1994 20:24:10 GMT Received: from relay1.UU.NET by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA23133; Thu, 19 May 1994 13:04:51 -0700 Received: from page.bose.com (via gateway.BOSE.COM) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AAwqpk05719; Thu, 19 May 94 16:06:01 -0400 Received: from nuno.bose.com (root@nuno.bose.com [139.68.201.1]) by page.bose.com (8.6.1/8.6) with SMTP id QAA20135 for ; Thu, 19 May 1994 16:05:55 -0400 Received: by nuno.bose.com (4.1/SMI-4.1) id AA06126; Thu, 19 May 94 16:05:10 EDT Date: Thu, 19 May 94 16:05:10 EDT From: mora@bose.com (Carlos Mora) Message-Id: <9405192005.AA06126@nuno.bose.com> To: majordomo-users@GreatCircle.COM Subject: Unsubscribe weirdness.... Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am running majordomo.1.62. I have setup a closed list and find that periodically an unsubscribe will not require the list owner's intervention. Has anyone come across this and is there a workaround. 1.90?? Thanks, ---------------------------------------------------------------- Carlos Mora e-mail: mora@bose.com Unix System Administrator phone : (508) 879-1916 x6437 Bose Corporation fax : (508) 820-4865 The Mountain Framingham, MA 01701-9168 ---------------------------------------------------------------- From majordomo-users-owner Thu May 19 14:40:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA23704; Thu, 19 May 1994 21:34:14 GMT Received: from mail.teleport.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA23484; Thu, 19 May 1994 14:01:38 -0700 Received: by mail.teleport.com (/\==/\ Smail3.1.28.1 #28.2) id ; Thu, 19 May 94 14:02 PDT Date: Thu, 19 May 1994 14:02:19 -0700 (PDT) From: Paradise Cowgirl Subject: Re: Unsubscribe weirdness.... To: Carlos Mora cc: majordomo-users@GreatCircle.COM In-Reply-To: <9405192005.AA06126@nuno.bose.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Thu, 19 May 1994, Carlos Mora wrote: > > I am running majordomo.1.62. I have setup a closed list and find that > periodically an unsubscribe will not require the list owner's intervention. > > Has anyone come across this and is there a workaround. 1.90?? > > Thanks, > ---------------------------------------------------------------- > Carlos Mora e-mail: mora@bose.com > ---------------------------------------------------------------- I didn't think the listowner's intervention was ever needed for *un*subscribe unless the requested address didn't match the from address. Am I missing something here? >>-Darci-> -- ------ Paradise Cowgirl - minerva@teleport.com - minerva@netcom.com \ --/--- Boycott Rush Limbaugh oranges! \ \/ / Don't support discrimination and bigotry -- don't support the OCA! \/\ / http://vector.casti.com/QRD/.html/People/Darci.html \/ "What would happen if the far right held a campaign and nobody came?" -Lee Lynch From majordomo-users-owner Thu May 19 14:50:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA23739; Thu, 19 May 1994 21:35:11 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA23550; Thu, 19 May 1994 14:08:52 -0700 Received: from cs.umb.edu by cs.umb.edu with SMTP id AA20151 (5.65c/IDA-1.4.4 for ); Thu, 19 May 1994 17:08:36 -0400 Message-Id: <199405192108.AA20151@cs.umb.edu> To: mora@bose.com (Carlos Mora) Cc: majordomo-users@greatcircle.com Subject: Re: Unsubscribe weirdness.... In-Reply-To: Your message of "Thu, 19 May 1994 16:05:10 EDT." <9405192005.AA06126@nuno.bose.com> Date: Thu, 19 May 1994 17:08:34 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405192005.AA06126@nuno.bose.com>, Carlos Mora writes: > I am running majordomo.1.62. I have setup a closed list and find that > periodically an unsubscribe will not require the list owner's intervention. Unfortunately unsubscribes never require list operators attention. I know a number of people who have wanted that feature for a while. It is very useful for lists that employees must be on. > Has anyone come across this and is there a workaround. 1.90?? No there isn't a workaround in 1.90, however I would suggest upgrading to 1.90 if you are planning on adding this feature. It makes a much nicer framework for adding features. With 1.90 you could add an unsubscribe_policy keyword for this feature and it could parallel the subscribe_policy keyword. Heck, if you take me out to lunch, I might even write the code for you and include it in 1.91 myself. -- John John Rouillard Special Projects Volunteer 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 May 19 15:00:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA23701; Thu, 19 May 1994 21:34:09 GMT Received: from relay1.UU.NET by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA23466; Thu, 19 May 1994 14:00:18 -0700 Received: from page.bose.com (via gateway.BOSE.COM) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AAwqpo22158; Thu, 19 May 94 17:00:59 -0400 Received: from nuno.bose.com (root@nuno.bose.com [139.68.201.1]) by page.bose.com (8.6.1/8.6) with SMTP id RAA20939; Thu, 19 May 1994 17:00:56 -0400 Received: by nuno.bose.com (4.1/SMI-4.1) id AA06332; Thu, 19 May 94 17:00:43 EDT From: mora@bose.com (Carlos Mora) Message-Id: <9405192100.AA06332@nuno.bose.com> Subject: Re: Unsubscribe weirdness.... To: dans@ans.net (Dan Simoes) Date: Thu, 19 May 1994 17:00:42 -0400 (EDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <199405192042.AA74730@foo.ans.net> from "Dan Simoes" at May 19, 94 04:42:38 pm X-Mailer: ELM [version 2.4 PL23+BOSE] Content-Type: text Content-Length: 949 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > > I am running majordomo.1.62. I have setup a closed list and find that > > periodically an unsubscribe will not require the list owner's intervention. > Closed lists do not require approval for unsubscribes. > In fact, no lists do, to the best of my knowledge. > The fact that it is closed applies only to subscription requests. Directly from the Doc/list-owner-info file for 1.62: You can get detailed explanations of all of these by asking for "help" from Majordomo. The "undocumented" commands for use by list owners are: approve {subscribe|unsubscribe} [
] This is so that you can approve subscription or unsubscription actions that need approval by the list owner. Note that this is just a standard "subscribe" or "unsubscribe" command prefixed with "approve " (where you substitute the password for your list, which is listed above, for ""). From majordomo-users-owner Thu May 19 15:09:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA23729; Thu, 19 May 1994 21:34:53 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA23532; Thu, 19 May 1994 14:06:30 -0700 Received: by interlock.ans.net id AA17405 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Thu, 19 May 1994 17:06:53 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 19 May 1994 17:06:53 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 19 May 1994 17:06:53 -0400 From: Dan Simoes Message-Id: <199405192103.AA35956@foo.ans.net> Subject: Re: Unsubscribe weirdness.... To: mora@bose.com (Carlos Mora) Date: Thu, 19 May 1994 17:03:40 -0400 (EDT) Cc: dans@ans.net, majordomo-users@greatcircle.com In-Reply-To: <9405192100.AA06332@nuno.bose.com> from "Carlos Mora" at May 19, 94 05:00:42 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1012 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Directly from the Doc/list-owner-info file for 1.62: > approve {subscribe|unsubscribe} [
] > This is so that you can approve subscription or unsubscription > actions that need approval by the list owner. Note that this > is just a standard "subscribe" or "unsubscribe" command prefixed > with "approve " (where you substitute the password for >From my own docs on majordomo: 3) Closed list: a list where all subscribe requests must be approved, by being bounced to list-approval. Unsubscribe requests for the individual's own address are performed automatically - attempting to unsubscribe others will bounce the request to list-approval. A closed list requires the file list.closed in $listdir. This was written around the time of 1.60 and I don't think it has changed. | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From majordomo-users-owner Thu May 19 23:03:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA24384; Thu, 19 May 1994 23:03:14 GMT Received: from mail.teleport.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA24042; Thu, 19 May 1994 15:25:31 -0700 Received: by mail.teleport.com (/\==/\ Smail3.1.28.1 #28.2) id ; Thu, 19 May 94 15:26 PDT Date: Thu, 19 May 1994 15:26:03 -0700 (PDT) From: Paradise Cowgirl Subject: Re: Unsubscribe weirdness.... To: Carlos Mora cc: Dan Simoes , majordomo-users@GreatCircle.COM In-Reply-To: <9405192100.AA06332@nuno.bose.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Thu, 19 May 1994, Carlos Mora wrote: > > > > > I am running majordomo.1.62. I have setup a closed list and find that > > > periodically an unsubscribe will not require the list owner's intervention. > > Closed lists do not require approval for unsubscribes. > > In fact, no lists do, to the best of my knowledge. > > The fact that it is closed applies only to subscription requests. > > Directly from the Doc/list-owner-info file for 1.62: > > You can get detailed explanations of all of these by asking for "help" > from Majordomo. > > The "undocumented" commands for use by list owners are: > > approve {subscribe|unsubscribe} [
] > This is so that you can approve subscription or unsubscription > actions that need approval by the list owner. Note that this > is just a standard "subscribe" or "unsubscribe" command prefixed > with "approve " (where you substitute the password for > your list, which is listed above, for ""). This feature allows the listowner to unilaterally unsubscribe an address (ie, bouncing addresses). It has nothing to do with the list being closed, private, or what have you. I use this feature all the time on open lists. >>-Darci-> -- ------ Paradise Cowgirl - minerva@teleport.com - minerva@netcom.com \ --/--- Boycott Rush Limbaugh oranges! \ \/ / Don't support discrimination and bigotry -- don't support the OCA! \/\ / http://vector.casti.com/QRD/.html/People/Darci.html \/ "What would happen if the far right held a campaign and nobody came?" -Lee Lynch From majordomo-users-owner Fri May 20 14:52:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA28127; Fri, 20 May 1994 14:52:57 GMT Received: from relay1.UU.NET by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA27872; Fri, 20 May 1994 06:40:12 -0700 Received: from page.bose.com (via gateway.BOSE.COM) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AAwqsc27980; Fri, 20 May 94 09:41:24 -0400 Received: from nuno.bose.com (root@nuno.bose.com [139.68.201.1]) by page.bose.com (8.6.1/8.6) with SMTP id JAA04458 for ; Fri, 20 May 1994 09:41:08 -0400 Received: by nuno.bose.com (4.1/SMI-4.1) id AA07533; Fri, 20 May 94 09:36:14 EDT From: mora@bose.com (Carlos Mora) Message-Id: <9405201336.AA07533@nuno.bose.com> Subject: Re: Unsubscribe weirdness.... To: majordomo-users@greatcircle.com Date: Fri, 20 May 1994 09:36:13 -0400 (EDT) Cc: mora@uunet.UU.NET (Carlos Mora) X-Mailer: ELM [version 2.4 PL23+BOSE] Content-Type: text Content-Length: 646 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thanks to all that responded. I miss read the docs. I saw the approve unsubscribe and assumed (foolish me :-) that unsubscribe would require an approval. Again thanks. John, No problem on the lunch. It would be great if that could be added to 1.91. Let me know when you want the lunch and we can meet somewhere. Thanks, ---------------------------------------------------------------- Carlos Mora e-mail: mora@bose.com Unix System Administrator phone : (508) 879-1916 x6437 Bose Corporation fax : (508) 820-4865 The Mountain Framingham, MA 01701-9168 ---------------------------------------------------------------- From majordomo-users-owner Sat May 21 03:32:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id DAA00879; Sat, 21 May 1994 03:32:29 GMT Received: from is.internic.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA00873; Fri, 20 May 1994 20:32:20 -0700 Received: (from paulp@localhost) by is.internic.net (8.6.8/8.6.6) id UAA09917; Fri, 20 May 1994 20:33:15 -0700 Date: Fri, 20 May 1994 20:33:14 -0700 (PDT) From: Paul Phillips Subject: All messages to list bouncing 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 all, I am having a bit of difficulty with majordomo. Every message sent to the list gets sent to the approval address with BOUNCE prepended, whether it's administrivia or not. In the documentation I found: >>> Majordomo may bounce certain messages that people attempt to post to your mailing list. These messages may be bounced because they appear to be administrative requests (i.e., someone mailed a request to subscribe or unsubscribe to the posting address rather than to Majordomo or to the -request address), because they are too long, or for any of a number of other reasons. >>> It's the "any of a number of other reasons" that throws me. I am running majordomo 1.90 with everything fairly "out of the box" configuration wise. The messages can be approved and sent out to the list in the normal BOUNCE way, but for some reason proper headers are not being generated. Any help appreciated, --- Paul Phillips | EMAIL: paulp@is.internic.net | InterNIC Information Services | WWW: http://www.internic.net/~paulp/ | InfoGuide Administrator | PHONE: 619-455-4626 FAX: 619-455-4640 | From majordomo-users-owner Sat May 21 17:46:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA03398; Sat, 21 May 1994 17:46:05 GMT Received: from flowbee.interaccess.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA03392; Sat, 21 May 1994 10:45:57 -0700 Received: from localhost (larry@localhost) by flowbee.interaccess.com (8.6.5/8.6.5) id MAA03304 for majordomo-users@GreatCircle.COM; Sat, 21 May 1994 12:47:05 -0500 From: Larry Q Public Message-Id: <199405211747.MAA03304@flowbee.interaccess.com> Subject: wrapper problems To: majordomo-users@GreatCircle.COM Date: Sat, 21 May 1994 12:47:04 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1596 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here's the error message that Majordomo gives me. I'm using the same wrapper I'm using for the maillist too - just can't seem to get to the achive. The only change that was made was that we moved up a few levels of sendmail versions. Any ideas? - Larry@interaccess.com > >with internal id UAA11373; Thu, 19 May 1994 20:36:29 -0500 > >Date: Thu, 19 May 1994 20:36:29 -0500 > >From: Mail Delivery Subsystem > >Subject: Returned mail: Address > >:include:/usr/home/majordomo/lists/appware-info is unsafe for mailing to > >programs > >Message-Id: <199405200136.UAA11373@home.interaccess.com> > >To: weidl > > > >The original message was received at Thu, 19 May 1994 19:51:22 -0500 > >from root@localhost > > > > ----- The following addresses had delivery problems ----- > >|/usr/adm/sm.bin/wrapper archive -f > >/opt/anonftp/parallel/appware/appware-info-archives/appware.archive -m -a > >(unrecoverable error) > > (expanded from: :include:/usr/home/majordomo/lists/appware-info) > > > > ----- Transcript of session follows ----- > >550 /usr/home/majordomo/lists/appware-info: line 5: |/usr/adm/sm.bin/wrapper > >archive -f /opt/anonftp/parallel/appware/appware-info-archives/appware.archive > >-m -a... Address :include:/usr/home/majordomo/lists/appware-info is unsafe for > >mailing to programs > >coyote@sti.com,glenn@sti.com,kevinm@sti.com,mab@sti.com... Deferred: > >Connection timed out during initial connection with smurf.sti.com. > >"Fuchs, Dave" ... Deferred: Connection timed out > >during initial connection with hq.walldata.com. From majordomo-users-owner Sat May 21 17:58:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA03418; Sat, 21 May 1994 17:58:38 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA03412; Sat, 21 May 1994 10:58:29 -0700 Received: from cs.umb.edu by cs.umb.edu with SMTP id AA01429 (5.65c/IDA-1.4.4 for ); Sat, 21 May 1994 13:59:41 -0400 Message-Id: <199405211759.AA01429@cs.umb.edu> To: Larry Q Public Cc: majordomo-users@greatcircle.com Subject: Re: wrapper problems In-Reply-To: Your message of "Sat, 21 May 1994 12:47:04 CDT." <199405211747.MAA03304@flowbee.interaccess.com> Date: Sat, 21 May 1994 13:59:39 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199405211747.MAA03304@flowbee.interaccess.com>, Larry Q Public writes: > > >with internal id UAA11373; Thu, 19 May 1994 20:36:29 -0500 > > >Date: Thu, 19 May 1994 20:36:29 -0500 > > >From: Mail Delivery Subsystem > > >Subject: Returned mail: Address > > >:include:/usr/home/majordomo/lists/appware-info is unsafe for mailing to > > >programs > > >Message-Id: <199405200136.UAA11373@home.interaccess.com> > > >To: weidl > > > > > >The original message was received at Thu, 19 May 1994 19:51:22 -0500 > > >from root@localhost > > > > > > ----- The following addresses had delivery problems ----- > > >|/usr/adm/sm.bin/wrapper archive -f > > >/opt/anonftp/parallel/appware/appware-info-archives/appware.archive -m -a > > >(unrecoverable error) > > > (expanded from: :include:/usr/home/majordomo/lists/appware-info) > > > > > > -----Transcript of session follows ----- > > >550 /usr/home/majordomo/lists/appware-info: line 5: |/usr/adm/sm.bin/wrapper > > >archive -f /opt/anonftp/parallel/appware/appware-info-archives/appware.archive > > >-m -a... Address :include:/usr/home/majordomo/lists/appware-info is unsafe for > > >mailing to programs > > >coyote@sti.com,glenn@sti.com,kevinm@sti.com,mab@sti.com... Deferred: > > >Connection timed out during initial connection with smurf.sti.com. > > >"Fuchs, Dave" ... Deferred: Connection timed out > > >during initial connection with hq.walldata.com. It looks like you have the archive command in an include file and sendmail doesn't allow programs in an include file. Put the archive declaration in /etc/aliases. -- John John Rouillard Special Projects Volunteer 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 May 21 20:55:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA04070; Sat, 21 May 1994 20:55:29 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA04061; Sat, 21 May 1994 13:54:56 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA04473 (5.65c/IDA-1.4.4 for ); Sat, 21 May 1994 16:55:47 -0400 Message-Id: <199405212055.AA04473@cs.umb.edu> To: Paul Phillips Cc: majordomo-users@greatcircle.com Subject: Re: All messages to list bouncing In-Reply-To: Your message of "Fri, 20 May 1994 20:33:14 PDT." Date: Sat, 21 May 1994 16:55:47 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Paul Phillips writes: > I am having a bit of difficulty with majordomo. Every message sent to > the list gets sent to the approval address with BOUNCE prepended, whether > it's administrivia or not. In the documentation I found: > [...] > It's the "any of a number of other reasons" that throws me. I am running > majordomo 1.90 with everything fairly "out of the box" configuration > wise. The messages can be approved and sent out to the list in the > normal BOUNCE way, but for some reason proper headers are not being > generated. You haven't given us a heck of a lot to go on. Do you have an example bounce message that you are receiving. The subject line of the bounced message says why it is being bounced. Is the list moderated? Are you using the approve(1) command to approve the bounced messages, or are you doing it by hand. If you are doing it by hand, are you keeping all of the original headers that are encapsulated in the bounce message? -- John John Rouillard Special Projects Volunteer 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 May 23 23:06:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA17807; Tue, 24 May 1994 05:37:05 GMT Received: from interlock.ans.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA23353; Thu, 19 May 1994 13:45:22 -0700 Received: by interlock.ans.net id AA08132 (InterLock SMTP Gateway 1.1 for majordomo-users@greatcircle.com); Thu, 19 May 1994 16:45:50 -0400 Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 19 May 1994 16:45:50 -0400 Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 19 May 1994 16:45:50 -0400 From: Dan Simoes Message-Id: <199405192042.AA74730@foo.ans.net> Subject: Re: Unsubscribe weirdness.... To: mora@bose.com (Carlos Mora) Date: Thu, 19 May 1994 16:42:38 -0400 (EDT) Cc: majordomo-users@greatcircle.com (majordomo-users) In-Reply-To: <9405192005.AA06126@nuno.bose.com> from "Carlos Mora" at May 19, 94 04:05:10 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 472 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I am running majordomo.1.62. I have setup a closed list and find that > periodically an unsubscribe will not require the list owner's intervention. Closed lists do not require approval for unsubscribes. In fact, no lists do, to the best of my knowledge. The fact that it is closed applies only to subscription requests. | Dan | -- Dan Simoes dans@ans.net Associate Programmer (914) 789-5378 Advanced Network & Services Elmsford, NY From majordomo-users-owner Mon May 23 23:11:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id FAA17788; Tue, 24 May 1994 05:36:49 GMT Received: from kksys.skypoint.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA13239; Wed, 18 May 1994 07:48:17 -0700 Received: by kksys.skypoint.net (Smail3.1.28.1 #15) id m0q3mbD-0002kMC; Wed, 18 May 94 09:27 CDT Received: by cdsmn (/\==/\ Smail3.1.28.1 #28.5) id ; Wed, 18 May 94 09:27 CDT Message-Id: Date: Wed, 18 May 94 09:27 CDT X-Sender: plate@cdsmn Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Majordomo-users@Greatcircle.Com From: Doug.Plate@cdsmn.mn.org (Doug Plate Sr.) Subject: Re: Linux - anything odd - part 2 X-Mailer: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > >In message , Gary Day writes: >> Just in case this will help, here is the sendmail verbose output to a >> subscribe message: transport: pipe > >By the way what version of sendmail are you running? I am not familiar >with this debugging output. > > -- John > FYI Gary, that's Smail, not sendmail. The confusion is understandable since Smail is aliased as sendmail (for compatibility with packages such as Majordomo), and also as rmail. Regards, Doug Plate Sr. ////////////////////////////////////////////////////////////////////////////// Doug Plate Sr. Doug.Plate@cdsmn.mn.org Senior Design Technician, Dicomed Inc. Systems Adminstrator Digital Photo Retouch Products ////////////////////////////////////////////////////////////////////////////// From majordomo-users-owner Tue May 24 06:31:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA20744; Tue, 24 May 1994 13:18:36 GMT Received: from clouso.crim.ca by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA20737; Tue, 24 May 1994 06:18:25 -0700 Received: from sgi-res.cdst.hydro.qc.ca by clouso.crim.ca (4.1/SMI-4.1) id AA25627; Tue, 24 May 94 09:19:45 EDT Received: by sgi-res.cdst.hydro.qc.ca (920330.SGI/920502.SGI) for @CLOUSO.CRIM.CA:majordomo-users@GreatCircle.com id AA05292; Tue, 24 May 94 09:19:44 -0400 From: gendron@sgi-res.cdst.hydro.qc.ca () Message-Id: <9405240919.ZM5290@sgi-res.cdst.hydro.qc.ca> Date: Tue, 24 May 1994 09:19:44 -0400 X-Mailer: Z-Mail (2.1.4 02apr93) To: majordomo-users@GreatCircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi everybody I am configuring majordomo on an sgi and I wonder which mechanism makes it approve the mailing from outside, automaticaly. I read the doc but did not see much on it. Thanks again if you can help me. bob -- +--------------------------------------------------------------------------+ | Robert Gendron Hydro Quebec | | Division SSCER Edifice Raycom | | gendron@sgi-res.cdst.hydro.qc.ca 5100 rue Sherbrooke Est 7 ieme Mtl.| | Tel. (514)251-3001 (812-3001) Quebec Canada | | Fax (514) 251-3080 HIV-3R9 | +--------------------------------------------------------------------------+ From majordomo-users-owner Tue May 24 19:10:36 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA24080; Tue, 24 May 1994 19:10:36 GMT Received: from clouso.crim.ca by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA24064; Tue, 24 May 1994 12:10:16 -0700 Received: from sgi-res.cdst.hydro.qc.ca by clouso.crim.ca (4.1/SMI-4.1) id AA10164; Tue, 24 May 94 15:11:34 EDT Received: by sgi-res.cdst.hydro.qc.ca (920330.SGI/920502.SGI) for @CLOUSO.CRIM.CA:majordomo-users@GreatCircle.com id AA05888; Tue, 24 May 94 15:11:32 -0400 From: gendron@sgi-res.cdst.hydro.qc.ca () Message-Id: <9405241511.ZM5886@sgi-res.cdst.hydro.qc.ca> Date: Tue, 24 May 1994 15:11:32 -0400 X-Mailer: Z-Mail (2.1.4 02apr93) To: majordomo-users@GreatCircle.com Subject: Cannot mail to the list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi I cannot mail to the list I created. I beleive that the problem may be whith the aliases. Here is a copy of it. groupe-dev-interface: "|/usr/people/major/wrapper resend -p bulk -M 10000 -l groupe-dev-interface -f groupe-dev-interface-owner -h sgi_serv.cdst.hydro.qc.ca " Need help in config. bob -- +--------------------------------------------------------------------------+ | Robert Gendron Hydro Quebec | | Division SSCER Edifice Raycom | | gendron@sgi-res.cdst.hydro.qc.ca 5100 rue Sherbrooke Est 7 ieme Mtl.| | Tel. (514)251-3001 (812-3001) Quebec Canada | | Fax (514) 251-3080 HIV-3R9 | +--------------------------------------------------------------------------+ From majordomo-users-owner Tue May 24 19:59:16 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA24343; Tue, 24 May 1994 19:59:16 GMT Received: from is.internic.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA24337; Tue, 24 May 1994 12:59:04 -0700 Received: (from paulp@localhost) by is.internic.net (8.6.8/8.6.6) id NAA09709; Tue, 24 May 1994 13:00:07 -0700 Date: Tue, 24 May 1994 13:00:06 -0700 (PDT) From: Paul Phillips Reply-To: Paul Phillips Subject: Re: All messages to list bouncing To: "John P. Rouillard" cc: majordomo-users@greatcircle.com In-Reply-To: <199405212055.AA04473@cs.umb.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Out of town for the weekend, thus the delay... On Sat, 21 May 1994, John P. Rouillard wrote: > You haven't given us a heck of a lot to go on. > > Do you have an example bounce message that you are receiving. Sample bounce message: >>> Date: Tue, 24 May 1994 12:15:39 -0700 From: owner-sample@is.internic.net To: owner-sample@is.internic.net Subject: BOUNCE sample@is.internic.net: Approval required >From owner-sample Tue May 24 12:15:37 1994 Received: (from paulp@localhost) by is.internic.net (8.6.8/8.6.6) id MAA04456; Tue, 24 May 1994 12:15:37 -0700 Date: Tue, 24 May 1994 12:15:37 -0700 (PDT) From: Paul Phillips Subject: New release To: sample@is.internic.net Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Announcement... etc, etc, etc. -PSP >>> Sending this back to the list with an "Approved" line first does send it out, but the new message has no subject and other problems that seem to be due to the header (everyone from the same domain appears on the To: line, for example.) The driving force behind fixing this is that the many subscribers of the list are rather irked to have lost their subject headers. Any quick fix that would return that would give me some time to figure out the rest, but it appears that it's all codependent. > The subject line of the bounced message says why it is being > bounced. Is the list moderated? Are you using the approve(1) command > to approve the bounced messages, or are you doing it by hand. If you > are doing it by hand, are you keeping all of the original headers that > are encapsulated in the bounce message? The subject line just says "Approval required" which according to the docs (?) should do: The requests for approval that Majordomo generates all start with "APPROVE" in the "Subject:" line. I was doing the approval by hand, at the bottom of the enclosed bounced message header. In case the problem lies here, the /etc/aliases section looks like this: >>> owner-sample: paulp@is.internic.net sample-approval: paulp@is.internic.net owner-sample-digest: owner-sample sample-digest-approval: sample-approval sample: "|/infoguide/majordomo-1.90/wrapper resend -l sample -h is.internic.net -s sample-outgoing" sample-digest: sample owner-sample-outgoing: owner-sample sample-outgoing: :include:/infoguide/majordomo-1.90/lists/sample, "|/infoguide/majordomo-1.90/wrapper digest -r -C -l sample-digest sample-digest-outgoing" owner-sample-digest-outgoing: owner-sample sample-digest-outgoing: :include:/infoguide/majordomo-1.90/lists/sample-digest owner-sample-request: owner-sample sample-request: "|/infoguide/majordomo-1.90/wrapper majordomo -l sample" owner-sample-digest-request: sample-digest-owner sample-digest-request: "|/infoguide/majordomo-1.90/wrapper majordomo -l sample-digest" >>> I do apologize if this is easy stuff, but I have no experience with mailing lists, and the obvious may be non-obvious to me right now. --- Paul Phillips | EMAIL: paulp@is.internic.net | InterNIC Information Services | WWW: http://www.internic.net/~paulp/ | InfoGuide Administrator | PHONE: 619-455-4626 FAX: 619-455-4640 | From majordomo-users-owner Tue May 24 23:46:59 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA25631; Tue, 24 May 1994 23:46:59 GMT Received: from is.internic.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA25624; Tue, 24 May 1994 16:46:44 -0700 Received: (from paulp@localhost) by is.internic.net (8.6.8/8.6.6) id QAA29292; Tue, 24 May 1994 16:47:51 -0700 Date: Tue, 24 May 1994 16:47:50 -0700 (PDT) From: Paul Phillips Subject: Resend vs. config file To: majordomo-users@greatcircle.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk It appears that certain aspects of the list can be controlled with command line options to resend as well as in the config file (for example, moderated = yes vs. -A.) Is this because the software is evolving and/or is there a preferred way to control these? --- Paul Phillips | EMAIL: paulp@is.internic.net | InterNIC Information Services | WWW: http://www.internic.net/~paulp/ | InfoGuide Administrator | PHONE: 619-455-4626 FAX: 619-455-4640 | From majordomo-users-owner Wed May 25 01:33:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA26159; Wed, 25 May 1994 01:33:22 GMT Received: from uakari.primate.wisc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA26153; Tue, 24 May 1994 18:33:15 -0700 Received: by uakari.primate.wisc.edu; id AA10057; 5.61/41.7; Tue, 24 May 94 20:34:37 -0500 From: Software Development Message-Id: <9405250134.AA10057@uakari.primate.wisc.edu> Subject: When does disgest volume number roll over? To: majordomo-users@greatcircle.com Date: Tue, 24 May 1994 20:34:37 -0500 (CDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 204 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk For a digested majordomo list, when does the volume number roll over and the issue number reset to 1? Or do I just do that manually in the list's configuration file? Paul DuBois dubois@primate.wisc.edu From majordomo-users-owner Tue May 24 19:11:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA26356; Wed, 25 May 1994 02:08:50 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA26350; Tue, 24 May 1994 19:08:37 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA09017 (5.65c/IDA-1.4.4 for ); Tue, 24 May 1994 22:09:54 -0400 Message-Id: <199405250209.AA09017@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: various Re: (NULL) and Cannot mail to the list Date: Tue, 24 May 1994 22:09:52 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I am configuring majordomo on an sgi and I wonder which mechanism makes Which version of majordomo? > it approve the mailing from outside, automaticaly. I read the doc but did > not see much on it. i am not sure what you mean. If you don't set up a restriction on the list using the moderate or the restrict_post varible all messages sent to the list are "approved". > I cannot mail to the list I created. How can you not mail to the list? Is an error message generated? Do you get a bounce message? Does the message just dissapear entirely? > I beleive that the problem may be whith the aliases. Here is a copy of it. > >groupe-dev-interface: "|/usr/people/major/wrapper resend -p bulk -M 10000 > -l groupe-dev-interface -f groupe-dev-interface-owner > -h sgi_serv.cdst.hydro.qc.ca " > >Need help in config. I don't know what version of majordomo you are using. If you are using 1.90 the only flags that should be used are: -h and -l All of the rest of the options should be set using the perl list configuration file as described in the README. -- John John Rouillard 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 Tue May 24 19:21:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA26328; Wed, 25 May 1994 02:00:21 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA26307; Tue, 24 May 1994 19:00:09 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA06882 (5.65c/IDA-1.4.4 for ); Tue, 24 May 1994 22:01:29 -0400 Message-Id: <199405250201.AA06882@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: various answers: Re: all messages to list bouncing and new release Date: Tue, 24 May 1994 22:01:28 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Paul Phillips said: > rouilj> Do you have an example bounce message that you are receiving. > > Sample bounce message: > >>> > Date: Tue, 24 May 1994 12:15:39 -0700 > From: owner-sample@is.internic.net > To: owner-sample@is.internic.net > Subject: BOUNCE sample@is.internic.net: Approval required This subject line indicated that the list is being moderated. Somewhere you have set moderate to yes, or have provided an opt_a flag. === This is where your approved header line should go > >From owner-sample Tue May 24 12:15:37 1994 > Received: (from paulp@localhost) by is.internic.net (8.6.8/8.6.6) id > MAA04456; > Tue, 24 May 1994 12:15:37 -0700 > Date: Tue, 24 May 1994 12:15:37 -0700 (PDT) > From: Paul Phillips > Subject: New release > To: sample@is.internic.net > Message-ID: > MIME-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII {{{{ Do not put the approved header line here }}}} > > Announcement... etc, etc, etc. > Sending this back to the list with an "Approved" line first does send it > out, but the new message has no subject and other problems that seem to > be due to the header (everyone from the same domain appears on the To: > line, for example.) > rouilj> bounced. Is the list moderated? Are you using the > rouilj> approve(1) command to approve the bounced messages, or are > rouilj> you doing it by hand. If you are doing it by hand, are you > rouilj> keeping all of the original headers that are encapsulated in > rouilj> the bounce message? > > I was doing the approval by hand, at the bottom of the enclosed bounced > message header. Check the example above. I this looks like you problem, the approved header MUST come before the headers encapsulated in the message otherwise all of those headers will be lost. > In case the problem lies here, the /etc/aliases section looks like this: > sample: "|/infoguide/majordomo-1.90/wrapper resend -l sample -h > is.internic.net -s sample-outgoing" > sample-digest: sample > owner-sample-outgoing: owner-sample > sample-outgoing: :include:/infoguide/majordomo-1.90/lists/sample, > "|/infoguide/majordomo-1.90/wrapper digest -r -C -l sample-digest sample-digest-outgoing" > Don't use -s on the command line for resend in the aliases file. As documented int he README, the only flags that should be used when using resend with majordomo are -l and -h. See below for more info. > It appears that certain aspects of the list can be controlled with > command line options to resend as well as in the config file (for > example, moderated = yes vs. -A.) Is this because the software is > evolving and/or is there a preferred way to control these? Resend is meant to be used with or without the rest of majordomo. If used WITHOUT majordomo you would use the command line flags. If used with majordomo, ONLY the -h and -l flags should be used, otherwise the defaults listed in the configuration file may not be correct leading to confusion. Just a note, I think I broke the ability to use resend without majordomo in the 1.90 release. I will fix it for 1.91. -- John John Rouillard 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 Tue May 24 19:31:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA26454; Wed, 25 May 1994 02:23:17 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA26448; Tue, 24 May 1994 19:23:04 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA12787 (5.65c/IDA-1.4.4 for ); Tue, 24 May 1994 22:24:16 -0400 Message-Id: <199405250224.AA12787@cs.umb.edu> To: Software Development Cc: majordomo-users@greatcircle.com Subject: Re: When does disgest volume number roll over? In-Reply-To: Your message of "Tue, 24 May 1994 20:34:37 CDT." <9405250134.AA10057@uakari.primate.wisc.edu> Date: Tue, 24 May 1994 22:24:15 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405250134.AA10057@uakari.primate.wisc.edu>, Software Development writes: > For a digested majordomo list, when does the volume number roll over > and the issue number reset to 1? Never. > Or do I just do that manually in the list's configuration file? Bingo, you got the joke. Basically there is no way I can determine when a new volume number needs to be issued. It seems to me that there is a limit of 999 issues per volume, but I doubt many people will allow the issue numbers to get that high before issuing a new volume. -- John John Rouillard 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 May 25 02:59:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA26610; Wed, 25 May 1994 02:59:20 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA26603; Tue, 24 May 1994 19:59:12 -0700 Message-Id: <199405250259.TAA26603@mycroft.GreatCircle.COM> To: "John P. Rouillard" cc: Software Development , majordomo-users@greatcircle.com Subject: Re: When does disgest volume number roll over? In-reply-to: Your message of Tue, 24 May 1994 22:24:15 -0400 Date: Tue, 24 May 1994 19:59:11 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "John P. Rouillard" writes: # # In message <9405250134.AA10057@uakari.primate.wisc.edu>, Software Development # writes: # > For a digested majordomo list, when does the volume number roll over # > and the issue number reset to 1? # # Never. # # > Or do I just do that manually in the list's configuration file? # # Bingo, you got the joke. Basically there is no way I can determine # when a new volume number needs to be issued. It seems to me that there # is a limit of 999 issues per volume, but I doubt many people will allow # the issue numbers to get that high before issuing a new volume. I roll them over by hand every year on January 1. In addition to incrementing the volume number, you need to set the issue number back to "1". -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 May 25 06:16:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA27911; Wed, 25 May 1994 06:16:18 GMT Received: from saimiri.primate.wisc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA27905; Tue, 24 May 1994 23:16:07 -0700 Received: by saimiri.primate.wisc.edu; id AA25766; 4.1/41.8; Wed, 25 May 94 01:17:22 CDT From: Software Development Message-Id: <9405250617.AA25766@saimiri.primate.wisc.edu> Subject: Re: When does disgest volume number roll over? To: rouilj@terminus.cs.umb.edu (John P. Rouillard) Date: Wed, 25 May 1994 01:17:21 -0500 (CDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <199405250224.AA12787@cs.umb.edu> from "John P. Rouillard" at May 24, 94 10:24:15 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 985 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > In message <9405250134.AA10057@uakari.primate.wisc.edu>, Software Development > writes: > > For a digested majordomo list, when does the volume number roll over > > and the issue number reset to 1? > > Never. > > > Or do I just do that manually in the list's configuration file? > > Bingo, you got the joke. Basically there is no way I can determine > when a new volume number needs to be issued. It seems to me that there > is a limit of 999 issues per volume, but I doubt many people will allow > the issue numbers to get that high before issuing a new volume. I guess I don't know what you mean by there being no way to determine when a new volume number needs to be issued. Wouldn't it work to have a configuration parameter indicating the maximum number of issues per volume? (I'm not saying, "please make this change", I'm trying to understand what the difficulty might be.) A value of 0 might indicate "no maximum, never rollover." Paul DuBois dubois@primate.wisc.edu From majordomo-users-owner Wed May 25 08:21:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA28268; Wed, 25 May 1994 08:21:21 GMT Received: from les.pc.uec.ac.jp by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA28262; Wed, 25 May 1994 01:21:11 -0700 Received: from power1.pc.uec.ac.jp by les.pc.uec.ac.jp (5.61/6.4J.6-pcgwy.pc.uec.ac.jp-2.4) id AA01739; Wed, 25 May 94 17:22:32 +0900 Received: from localhost by power1.pc.uec.ac.jp (AIX 3.2/UCB 5.64/4.03) id AA17749; Wed, 25 May 1994 17:23:27 +0900 Message-Id: <9405250823.AA17749@power1.pc.uec.ac.jp> To: Majordomo-Users@greatcircle.com Subject: Help! Date: Wed, 25 May 1994 17:23:27 +0900 From: Shinichi Watanabe Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dear Folks, 5/25/94 How do you do? I hesitate to pose you a question and to disturbe you like this but the problem with majordomo appears out of my hand. So here I am. I installed majordomo on our system, IBM RS6000/320H (AIX 3.2.5) It works fine in so far as "subscribe" goes. Majordomo returns the result properly, makes a necessary addition to the mailing list, and sends out the welcoming message. "Unsubscribe" also works fine. The problem is with the other commands such as lists, get, .... It seems things printed to REPLY, for example, does not get properly transmitted. As a result, a blank mail is sent. Things in MSG are fine. I wondered if this had to do with the ownership and/or permission of the files. But funny thing is that when everything was owned by myself, I could obtain information properly, i.e. lists worked. I have made various attempts, but now I am at my wits' end. Could you please help me? Thank you so much. S. Watanabe Associate Professor of Applied Physics %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Shinichi Watanabe # email : shin@power1.pc.uec.ac.jp Dept. of Applied Physics # FAX : +81-424-89-4666 1-5-1, Chofugaoka # Voice : +81-424-83-2161 x3923 Chofu-shi, Tokyo 182 U. of Electro-Communications Japan %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From majordomo-users-owner Wed May 25 14:59:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA00617; Wed, 25 May 1994 14:59:20 GMT Received: from taurus.fwl.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA00610; Wed, 25 May 1994 07:59:11 -0700 Received: by taurus.fwl.org (4.1/SMI-4.1) id AA28676; Wed, 25 May 94 07:59:35 PDT Date: Wed, 25 May 94 07:59:35 PDT From: brownal@fwl.org (Albert Brown) Message-Id: <9405251459.AA28676@taurus.fwl.org> To: majordomo-users@greatcircle.com Subject: RE; List of Majordomos? Content-Type: X-sun-attachment Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk ---------- X-Sun-Data-Type: text X-Sun-Data-Description: text X-Sun-Data-Name: text X-Sun-Content-Lines: 4 Please add our site to the list of majordomo servers, our address is: majordomo@fwl.org. We are Far West Laboratory, we provide research and development for the K-12 educational industry. The administrator is Albert Brown, brownal@fwl.org. ---------- X-Sun-Data-Type: default X-Sun-Data-Description: default X-Sun-Data-Name: .signature X-Sun-Content-Lines: 22 +-------------------------------------------------------------------+ + Albert S. Brown + + Home Phone: 916-684-4864 + + Home Fax: 916-684-4864 + Home Address: 5111 Laguna Park Drive + + Elk Grove, Ca. 95758 + + + + Far West Laboratory + + 730 Harrison Street + + San Francisco, Ca. 94107 + + Work Phone: 415-565-3030 + + Work Fax: 415-565-3012 + + + + E-mail Address: brownal@fwl.org + + brownal@acm.org + + + + Senior Research Associate + + + + " IMPROVING EDUCATION THROUGH TECHNOLOGY " + +-------------------------------------------------------------------+ From majordomo-users-owner Wed May 25 15:41:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA01020; Wed, 25 May 1994 15:41:43 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA01010; Wed, 25 May 1994 08:41:30 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA21554 (5.65c/IDA-1.4.4 for ); Wed, 25 May 1994 11:42:52 -0400 Message-Id: <199405251542.AA21554@cs.umb.edu> To: Software Development Cc: majordomo-users@greatcircle.com Subject: Re: When does disgest volume number roll over? In-Reply-To: Your message of "Wed, 25 May 1994 01:17:21 CDT." <9405250617.AA25766@saimiri.primate.wisc.edu> Date: Wed, 25 May 1994 11:42:52 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405250617.AA25766@saimiri.primate.wisc.edu>, Software Development writes: > > [rouilj writes:] > > Bingo, you got the joke. Basically there is no way I can determine > > when a new volume number needs to be issued. It seems to me that there > > is a limit of 999 issues per volume, but I doubt many people will allow > > the issue numbers to get that high before issuing a new volume. > > I guess I don't know what you mean by there being no way to determine when > a new volume number needs to be issued. Actually I should have said, there is know way to know apriori. Somebody would have to give me a clue. > Wouldn't it work to have a > configuration parameter indicating the maximum number of issues per > volume? (I'm not saying, "please make this change", I'm trying to understand > what the difficulty might be.) A value of 0 might indicate "no maximum, > never rollover." Yes, it probably would, but people usually want to change the issue number yearly or biyearly, and not based on the number of issues in the volume. Look at volume numbers for Newsweek, or Time, or your local paper. Special issues of the magazine/paper are number sequentially with the rest of the issues. Some years have more issues than others. Ditto with digests since they can be (and often need to be) triggered based on size which is related to mailing list traffic rather than based on "dates of issue". Trying to come up with a syntax for handling various rollover dates and the explanations about how to use such a feature would have been even worse than requiring regular expression use in the config file 8-). An increment volume command along the lines of mkdigest would be a valid request though. Probably in a 2.0 addin unless somebody writes a clean implementation first. -- John John Rouillard 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 May 25 08:51:34 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA01134; Wed, 25 May 1994 15:48:34 GMT Received: from hermes.intel.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA01128; Wed, 25 May 1994 08:48:23 -0700 Received: from pcocd2.intel.com by hermes.intel.com (5.65/10.0i); Wed, 25 May 94 08:49:20 -0700 Received: from fiw007 (fiw007.fm.intel.com) by pcocd2.intel.com with SMTP id AA21817 (5.65c/IDA-1.4.4 for ); Wed, 25 May 1994 08:49:14 -0700 Received: by fiw007 (4.1/FMDT-RS6000) id AA08123; Wed, 25 May 94 08:50:02 PDT From: "Anant Bukkapatnam - FES" Message-Id: <9405250850.ZM8121@fiw007.fm.intel.com> Date: Wed, 25 May 1994 08:50:01 -0700 X-Mailer: Z-Mail (3.0.1 23feb94) To: Majordomo-Users@greatcircle.com Subject: Need some help Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I am tring to set up majordomo. I have got all that is to be done from the set instuctions. I am having some of these problems. 1. I am using resend. If there is wrong address in the mailing list I want the list owner to be notified about the bounced mail. I dont want the mail to go back to the initiator of the message. 2. I also observed that the a user can subscribe multiple times to the same list. This is not a problem, but I was just wondering the use of it. Majordomo does not complain about this. If anyone of you have any suggestions please do so. I appreciate your help. Anant From majordomo-users-owner Wed May 25 19:32:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA03164; Wed, 25 May 1994 19:32:33 GMT Received: from vaxa.cis.uwosh.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA03158; Wed, 25 May 1994 12:32:23 -0700 Received: from vaxa.cis.uwosh.edu by vaxa.cis.uwosh.edu (PMDF #5575 ) id <01HCRCOZ9W9C005W9C@vaxa.cis.uwosh.edu>; Wed, 25 May 1994 14:30:35 CDT Date: 25 May 1994 14:30:35 -0500 (CDT) From: "Charles R. Milam - UW-Oshkosh" Subject: Step-by-step docs for upgrade to 1.90? To: majordomo-users@greatcircle.com Message-id: <01HCRCOZ9W9E005W9C@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 Date sent: 25-MAY-1994 14:29:01 Is there any step-by-step documentation for upgrading from Majordomo 1.62 to 1.90? I have information for a new install, but what if I want to preserve my exsisting lists, etc.? Thanks. ------------------------------------------------------------------------------ Charles R. Milam milamc@vaxa.cis.uwosh.edu University of Wisconsin-Oshkosh milamc@sol.acs.uwosh.edu Academic Computing KF9FR@KA9JAC.WI.USA.NA Oshkosh, WI 54901 Badger 112 -- WI0112 (414) 424-2309 Delta Sigma Phi - EB Chapter ------------------------------------------------------------------------------ Bunker's Admonition: "You cannot buy beer, you can only rent it." From majordomo-users-owner Wed May 25 20:23:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id UAA03601; Wed, 25 May 1994 20:23:38 GMT Received: from mail.teleport.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA03595; Wed, 25 May 1994 13:23:30 -0700 Received: by mail.teleport.com (/\==/\ Smail3.1.28.1 #28.2) id ; Wed, 25 May 94 13:01 PDT Received: by nehalem.rain.com (4.1/SMI-4.1) id AA03200; Wed, 25 May 94 13:01:20 PDT From: "Paradise Cowgirl" Message-Id: <9405251301.ZM3198@teleport.com> Date: Wed, 25 May 1994 13:01:18 -0700 In-Reply-To: "Charles R. Milam - UW-Oshkosh" "Step-by-step docs for upgrade to 1.90?" (May 25, 2:30pm) References: <01HCRCOZ9W9E005W9C@vaxa.cis.uwosh.edu> Reply-To: minerva@teleport.com X-Mailer: Z-Mail (3.0.0 15dec93) To: "Charles R. Milam - UW-Oshkosh" , majordomo-users@GreatCircle.COM Subject: Re: Step-by-step docs for upgrade to 1.90? Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On May 25, 2:30pm, Charles R. Milam - UW-Oshkosh wrote: -> Date sent: 25-MAY-1994 14:29:01 -> -> Is there any step-by-step documentation for upgrading from Majordomo 1.62 -> to 1.90? I have information for a new install, but what if I want to -> preserve my exsisting lists, etc.? -> -> Thanks. -> I asked a somewhat similar question and got no response. Can majordomo 1.90 be installed in the existing 1.62 directory without changes to the aliases and config/resend files? Can I "upgrade" my lists one at a time? Remarks greatly appreciated!! >>-Darci-> -- ------ Love thy enemies: they'll go crazy trying to figure out what you're up to \ --/--- Bumpersticker of the Week: "Higher Powered" \ \/ / Don't support discrimination -- don't support the OCA! \/\ / http://vector.casti.com/QRD/.html/People/Darci.html \/ Paradise Cowgirl - minerva@teleport.com - minerva@netcom.com From majordomo-users-owner Wed May 25 21:31:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA04139; Wed, 25 May 1994 21:31:18 GMT Received: from vespucci.iquest.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA04133; Wed, 25 May 1994 14:31:08 -0700 Received: by vespucci.iquest.com (Linux Smail3.1.28.1 #14) id m0q6PlD-0003K9C; Wed, 25 May 94 15:41 CDT Received: from cc:Mail by multi.iquest.com id AA769908149 Wed, 25 May 94 16:22:29 Date: Wed, 25 May 94 16:22:29 From: "Dougal Campbell" Encoding: 1552 Text Message-Id: <9404257699.AA769908149@multi.iquest.com> To: majordomo-users@GreatCircle.COM Subject: Re[2]: Step-by-step docs for upgrade to 1.90? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >-> Is there any step-by-step documentation for upgrading from Majordomo 1.62 >-> to 1.90? I have information for a new install, but what if I want to >-> preserve my exsisting lists, etc.? > >I asked a somewhat similar question and got no response. Can >majordomo 1.90 be installed in the existing 1.62 directory without >changes to the aliases and config/resend files? Can I "upgrade" my >lists one at >a time? > >Remarks greatly appreciated!! > >>>-Darci-> I might be able to give some views on this question in a couple of weeks. I have a couple of small lists running on 1.62 currently. I've just gotten 1.90 compiled on a different machine and I'm getting ready to do some testing and converting. I'll try to keep track of what changes I find necessary and let the majordomo-users list know the results. I did notice a note in the 1.90 README file about converting from previous versions, but all it says is that resend has very few command line arguments and that you should strip the arguments, else they'll conflict with what's in the config file. (i.e. the command line args will override the commented defaults in the config file, leading to what might appear to be unexpected results) ------------------------------+----------------------------------------------- Ernest MacDougal Campbell III |"Those who dream by day are cognizant of many dougal@multi.iquest.com | things which escape those who dream only by #include | night." -- Edgar Allan Poe From majordomo-users-owner Wed May 25 23:52:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA05510; Wed, 25 May 1994 23:52:56 GMT Received: from saimiri.primate.wisc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA05504; Wed, 25 May 1994 16:52:47 -0700 Received: by saimiri.primate.wisc.edu; id AA28483; 4.1/41.8; Wed, 25 May 94 18:53:56 CDT From: Software Development Message-Id: <9405252353.AA28483@saimiri.primate.wisc.edu> Subject: Re: Re[2]: Step-by-step docs for upgrade to 1.90? To: Dougal@multi.iquest.com (Dougal Campbell) Date: Wed, 25 May 1994 18:53:56 -0500 (CDT) Cc: majordomo-users@greatcircle.com In-Reply-To: <9404257699.AA769908149@multi.iquest.com> from "Dougal Campbell" at May 25, 94 04:22:29 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 663 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I did notice a note in the 1.90 README file about converting from previous > versions, but all it says is that resend has very few command line arguments > and that you should strip the arguments, else they'll conflict with what's in > the config file. (i.e. the command line args will override the commented > defaults in the config file, leading to what might appear to be unexpected > results) My experience is that the list's configuration file takes precedence over what's specified on the resend command line. (It took me a while to figure this out, and I'm still unsure whether that's the intended behavior.) Paul DuBois dubois@primate.wisc.edu From majordomo-users-owner Thu May 26 00:04:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA05695; Thu, 26 May 1994 00:04:00 GMT Received: from saimiri.primate.wisc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA05689; Wed, 25 May 1994 17:03:52 -0700 Received: by saimiri.primate.wisc.edu; id AA28647; 4.1/41.8; Wed, 25 May 94 19:05:18 CDT From: Software Development Message-Id: <9405260005.AA28647@saimiri.primate.wisc.edu> Subject: How to suppress archive of digested list To: majordomo-users@greatcircle.com Date: Wed, 25 May 1994 19:05:17 -0500 (CDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 589 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have two lists, a non-digest version xxx and an accompanying digest version xxx-digest. For the non-digested list, I create an archive by explicitly listing archive2.pl as one of the "recipients". The the digested list, I do *not* want to create an archive (it would be redundant, given that there are already archive files for the xxx list. But how do I suppress archive creation for xxx-digest? It appears that the digest program wants to generate the digest file in an archive directory, and fails with an error if there is no such directory. Paul DuBois dubois@primate.wisc.edu From majordomo-users-owner Thu May 26 00:30:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA05842; Thu, 26 May 1994 00:30:11 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA05831; Wed, 25 May 1994 17:30:02 -0700 Message-Id: <199405260030.RAA05831@mycroft.GreatCircle.COM> To: Software Development cc: majordomo-users@greatcircle.com Subject: Re: How to suppress archive of digested list In-reply-to: Your message of Wed, 25 May 1994 19:05:17 -0500 (CDT) Date: Wed, 25 May 1994 17:29:59 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Software Development writes: # I have two lists, a non-digest version xxx and an accompanying digest # version xxx-digest. # # For the non-digested list, I create an archive by explicitly listing # archive2.pl as one of the "recipients". # # The the digested list, I do *not* want to create an archive (it would # be redundant, given that there are already archive files for the xxx # list. But how do I suppress archive creation for xxx-digest? It # appears that the digest program wants to generate the digest file in an # archive directory, and fails with an error if there is no such # directory. # # Paul DuBois # dubois@primate.wisc.edu Here are the relevant aliases I use for Firewalls and Firewalls-Digest. Does this help? Beware that these are for use with Majordomo 1.62, by the way; I haven't had time to upgrade to 1.90 yet, so I don't know what changes will be necessary to make these work with them (probably just changes to the arguments for "resend"). firewalls: "|/usr/local/mail/majordomo/wrapper resend @/usr/local/mail/lists/firewalls.resend firewalls-outgoing" firewalls-outgoing: :include:/usr/local/mail/lists/firewalls, firewalls-archive, firewalls-digestify firewalls-digest: firewalls firewalls-digestify: "|/usr/local/mail/majordomo/wrapper digest -r -c /usr/local/mail/digest/firewalls-digest.cf" firewalls-digest-send: "|/usr/local/mail/majordomo/wrapper resend @/usr/local/mail/lists/firewalls-digest.resend firewalls-digest-outgoing" firewalls-digest-outgoing: :include:/usr/local/mail/lists/firewalls-digest Thus, incoming mail sent to either "Firewalls" or "Firewalls-Digest" goes into the same queue, which includes "Firewalls-Digestify". "Firewalls-Digestify" is what feeds things to the "digest" program. "Firewalls-Digest-Send" is where the cron job sends the actual digest every night, after it's been created. -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 May 26 00:35:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id AAA05922; Thu, 26 May 1994 00:35:38 GMT Received: from saimiri.primate.wisc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA05873; Wed, 25 May 1994 17:33:11 -0700 Received: by saimiri.primate.wisc.edu; id AA28863; 4.1/41.8; Wed, 25 May 94 19:34:33 CDT From: Software Development Message-Id: <9405260034.AA28863@saimiri.primate.wisc.edu> Subject: Recognition of "sub" and "unsub" To: majordomo-users@greatcircle.com Date: Wed, 25 May 1994 19:34:31 -0500 (CDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 276 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I notice that majordomo recognizes "subscribe" and "unsubscribe" but not "sub" or "unsub". On the other hand, the administrivia checks done by resend recognize all four. Is there a reason not to recognize "sub" and "unsub" in majordomo? Paul DuBois dubois@primate.wisc.edu From majordomo-users-owner Thu May 26 13:45:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id NAA10519; Thu, 26 May 1994 13:45:26 GMT Received: from DRAGON.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id GAA10511; Thu, 26 May 1994 06:45:17 -0700 Date: Thu, 26 May 1994 06:45:17 -0700 From: dithots!root Message-Id: <199405261345.GAA10511@mycroft.GreatCircle.COM> Received: from dithots by dragon.com (MX V4.0-1 VAX) with UUCP; Thu, 26 May 1994 09:42:33 EST Received: by dithots.dithots.org (Linux Smail3.1.28.1 #1) To: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk id m0q6eIU-00017FC; Thu, 26 May 94 08:12 EDT Message-Id: Date: Thu, 26 May 94 08:12 EDT From: root@dithots.dithots.org (root) To: majordomo-users@greatcircle.com Subject: Help with advertise... I don't want to advertise of  a list, but for th  e last two dayt s I can't seem to get me   y advers tise  = line in the config to work. What command should I place on this line  ? I've      And how does              If someone has an exampe le, please send it to me. bill From majordomo-users-owner Thu May 26 14:21:15 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA10734; Thu, 26 May 1994 14:21:15 GMT Received: from dataware.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id HAA10728; Thu, 26 May 1994 07:21:06 -0700 Received: from fatness (fatness.dataware.com) by dataware.com with SMTP id AA22481 (5.67b8/IDA-1.5 for ); Thu, 26 May 1994 10:24:25 -0400 Date: Thu, 26 May 1994 10:24:25 -0400 Message-Id: <199405261424.AA22481@dataware.com> X-Sender: ian@dataware.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: IPoynter@dataware.com (Ian Poynter) Subject: Majordomo on VMS? X-Mailer: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk A friend of mine just asked me whether Majordomo could be used on VMS. She doesn't really want to deal with the Listserv software (who can blame her :-). I figure that the main problem would be the interface with the mail system, since I believe Perl already runs on VMS. Any thoughts from people who have done or contemplated doing this would be gratefully received. I realize this is a shot in the dark since Majordomo is pretty Unix-centric. I think she may have to fall back on that dusty Unix box in the corner of the faculty office... Ian ----- Ian Poynter, Dataware Technologies, Inc. ian@dataware.com 222 Third Street, Cambridge, MA 02142 (617) 621-0820 I can also be reached as ian@world.std.com In many matters, I don't speak for Dataware. From majordomo-users-owner Thu May 26 16:07:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA11541; Thu, 26 May 1994 16:07:20 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA11535; Thu, 26 May 1994 09:07:11 -0700 Received: from xt.cs.umb.edu by cs.umb.edu with SMTP id AA29637 (5.65c/IDA-1.4.4 for ); Thu, 26 May 1994 12:08:25 -0400 Message-Id: <199405261608.AA29637@cs.umb.edu> To: Software Development Cc: majordomo-users@greatcircle.com Subject: Re: How to suppress archive of digested list In-Reply-To: Your message of "Wed, 25 May 1994 19:05:17 CDT." <9405260005.AA28647@saimiri.primate.wisc.edu> Date: Thu, 26 May 1994 12:08:25 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405260005.AA28647@saimiri.primate.wisc.edu>, Software Development writes: > I have two lists, a non-digest version xxx and an accompanying digest > version xxx-digest. > > For the non-digested list, I create an archive by explicitly listing > archive2.pl as one of the "recipients". > > The the digested list, I do *not* want to create an archive (it would > be redundant, given that there are already archive files for the xxx > list. But how do I suppress archive creation for xxx-digest? It > appears that the digest program wants to generate the digest file in an > archive directory, and fails with an error if there is no such > directory. Use cron to delete the archives. Yes, it is a bug. It comes from the way that digests creates its digest. It looks at all files in the digest directory, not just files that match [0-9][0-9][0-9]. Consequently there had to be some location to build the digest that was going out that was seperate from the digest spool directory. This is the archive directory. I added the patch to ignore and complain about files in the digest directory that didn't match the three digit format above, but I didn't make the changes to remove the need for the archive directory. Jerry Peek pointed this bug out to me when he was writing the 1.90 version of the majordomo chapter for his book. This bug is listed in the README as item 28 in section 5.1.1. I don't have a timetable on fixing it however. -- John John Rouillard 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 May 26 09:11:51 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA11428; Thu, 26 May 1994 16:00:34 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA11415; Thu, 26 May 1994 09:00:10 -0700 Received: from xt.cs.umb.edu by cs.umb.edu with SMTP id AA29176 (5.65c/IDA-1.4.4 for ); Thu, 26 May 1994 12:01:13 -0400 Message-Id: <199405261601.AA29176@cs.umb.edu> To: Software Development Cc: majordomo-users@greatcircle.com Subject: Re: Re[2]: Step-by-step docs for upgrade to 1.90? In-Reply-To: Your message of "Wed, 25 May 1994 18:53:56 CDT." <9405252353.AA28483@saimiri.primate.wisc.edu> Date: Thu, 26 May 1994 12:01:12 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405252353.AA28483@saimiri.primate.wisc.edu>, Software Development writes: > > I did notice a note in the 1.90 README file about converting from previous > > versions, but all it says is that resend has very few command line arguments > > and that you should strip the arguments, else they'll conflict with what's in > > the config file. (i.e. the command line args will override the commented > > defaults in the config file, leading to what might appear to be unexpected > > results) > > My experience is that the list's configuration file takes precedence > over what's specified on the resend command line. (It took me a while > to figure this out, and I'm still unsure whether that's the intended > behavior.) Yes, it is the intended behavior. If the opposite was true the list-manager would have no mechanism for changing any of resends's options. The one problem is that the options given on resend's command line aren't reflected in the comments in the config file, and the default values for the configure file override the command line arguments as well. In theory if you don't provide any values for the defaults (i.e. initalize them to undef) the command line values should pass through unscathed, but I haven't tested this and I have a feeling that it doesn;t work in some cases. If you are changing a few lists at a time over to 1.90 run the 1.90 majordomo with the 1.62 (or whatever) version of resend. All of the majordomo option files are supported. (1.9X will be the last release where these are supported hence my recommendation to upgrade.) The only thing you really case about is the digests and resend changeover, and those can be done on a per list basis. One thing to note is that you will get cconfig file for all of the lists once you run the new majordomo, but majordomo will be the only program looking at the config files until you upgrade to the new resend/digest. The next major iteration of the software will provide for a majordomo owner supplied perl file that allows overriding of the options in the config file (as well as specifying options that shoulddn't be changed by the list-manager like archive directories etc.) -- John John Rouillard 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 May 26 16:19:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA11599; Thu, 26 May 1994 16:19:33 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA11593; Thu, 26 May 1994 09:19:19 -0700 Received: from xt.cs.umb.edu by cs.umb.edu with SMTP id AA00370 (5.65c/IDA-1.4.4 for ); Thu, 26 May 1994 12:20:19 -0400 Message-Id: <199405261620.AA00370@cs.umb.edu> To: dithots!root@uunet.uu.net Cc: majordomo-users@greatcircle.com In-Reply-To: Your message of "Thu, 26 May 1994 06:45:17 PDT." <199405261345.GAA10511@mycroft.GreatCircle.COM> Date: Thu, 26 May 1994 12:20:18 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk If you don't want to advertise a list, leave advertise blank and put /.*/ in noadvertise. In message <199405261345.GAA10511@mycroft.GreatCircle.COM>, dithots!root@uunet. UU.NET writes: > id m0q6eIU-00017FC; Thu, 26 May 94 08:12 EDT > Message-Id: > Date: Thu, 26 May 94 08:12 EDT > From: root@dithots.dithots.org (root) > To: majordomo-users@greatcircle.com > Subject: Help with advertise... > > I don't want to advertise of  a list, but for th  e last two dayt s I can't > seem > to get me   y advers tise  = line in the config to work. What command shoul > d I > place on this line  ? I've      And how does              If someone has an exampe le, please send it to me > . > > bill -- John John Rouillard 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 May 26 18:04:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA12513; Thu, 26 May 1994 18:04:37 GMT Received: from atc.boeing.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA12507; Thu, 26 May 1994 11:04:26 -0700 Received: by atc.boeing.com (5.57) id AA02273; Thu, 26 May 94 11:07:52 -0700 Received: from aw102.iasl.ca.boeing.com.iasl.ca.boeing.com (aw102.iasl.ca.boeing.com) by aw101.iasl.ca.boeing.com with SMTP id AA23512 (5.67a/IDA-1.4.4 for ); Thu, 26 May 1994 11:05:46 -0700 From: "Vincent D. Skahan" Received: by aw102.iasl.ca.boeing.com.majordomo-users@greatcircle.com (5.65c/client-1.3) id AA10511; Thu, 26 May 1994 11:05:44 -0700 Message-Id: <199405261805.AA10511@aw102.iasl.ca.boeing.com.majordomo-users@greatcircle.com> Subject: archiving messages to a list...then what ? To: majordomo-users@greatcircle.com Date: Thu, 26 May 1994 11:05:43 -0700 (PDT) X-Mailer: ELM [version 2.4 PL20] Content-Type: text Content-Length: 675 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Dumb question that I'm stuck on... I know how to set up the aliases to save an archive of the traffic flowing through a list. But then what ? How do people deal with making the archive accessible to people in an automated manner ? Cron jobs every so often ? Use 'digest' ? Something else ? We don't support anon ftp at all, so I'd like to make it something that they can either request with majordomo or that I can hook into an external ftp-by-mail program like 'mserv'. Any help would be appreciated... -- ----------- Vince Skahan ------ vds7789@aw101.iasl.ca.boeing.com ----------- "Play it as it lies"-golf's second major axiom after "Wear it if it clashes" From majordomo-users-owner Thu May 26 18:31:41 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA12754; Thu, 26 May 1994 18:31:41 GMT Received: from infoexp.express.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id LAA12748; Thu, 26 May 1994 11:31:28 -0700 Received: from alto.express.com (alto.express.com [199.74.247.4]) by infoexp.express.com (8.6.8/8.6.6) with ESMTP id LAA12737 for ; Thu, 26 May 1994 11:32:46 -0700 Received: from [199.74.247.5] (macsnoopy.express.com [199.74.247.5]) by alto.express.com (8.6.8/8.6.6) with SMTP id LAA00203 for ; Thu, 26 May 1994 11:32:56 -0700 Message-Id: <199405261832.LAA00203@alto.express.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 26 May 1994 11:31:09 -0800 To: Majordomo-Users@GreatCircle.COM From: pzee@express.com (Philip J. Zee) Subject: Majordomo help Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I wonder if anyone could answer my question about majordomo. I have installed majordomo on my machine. I am at Information Express in Palo Alto. I used one machie (infoexp) as mail server and another (alto) as pop server. So, all mail messages are kept on alto. I installed majordomo on alto. Its source code is in /usr/local/src/majordomo and its home directory is :/usr/local/tools/majordomo and its listdir is /usr/local/tools/domolist. I have an entry in /etc/passwd file for majordomo: majordom:rP0nXigu4u2:100:30:majordomo list server:/usr/local/tools/majordomo: and there is a group called majordomo. The following is in my /etc/aliases file concerning majordomo and my sample list: ########################### # majordomo aliases below # ########################### majordomo: "|/usr/local/tools/majordomo/wrapper majordomo" majordomo-owner: pzee owner-majordomo: pzee # # Sample mailing list # owner-sample: sample-owner sample: "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -R -l sample -f Sample-Owner -h express.com -s sample-outgoing" sample-owner: pzee sample-approval: sample-owner sample-outgoing: :include:/usr/local/tools/domolist/sample, sample-archive owner-sample-outg oing: sample-owner sample-archive: /usr/local/tools/domolist/sample owner-sample-archive: sample-owner sample-request: "|/usr/local/tools/majordomo/wrapper request-answer sample" owner-sample -request: sample-owner owner-sample-owner: pzee My perl program is in /usr/bin/perl and this is the first line of my resend program which is a perl script and exeutable. When I was about to test it, I issued a command: echo help | /usr/lib/sendmail -v sample and here is the output: sample... aliased to "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -R -l sample -f Sample-Owner -h express.com -s sample-outgoing" "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -R -l sample -f Samp le-Owner -h express.com -s sample-outgoing"... unknown mailer error 1 sample-owner... aliased to pzee pzee... Sent and the returned message is: Date: Thu, 26 May 1994 11:23:20 -0700 From: Mail Delivery Subsystem Subject: Returned mail: unknown mailer error 1 To: sample-owner MIME-Version: 1.0 The original message was received at Thu, 26 May 1994 11:23:20 -0700 from pzee@localhost ----- The following addresses had delivery problems ----- "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -R -l sample -f Sample-Owner -h express.com -s sample-outgoing" (unrecoverable error) (expanded from: sample) ----- Transcript of session follows ----- 554 "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -R -l sample -f Sample-Owner -h express.com -s sample-outgoing"... unknown mailer error 1 ----- Original message follows ----- Content-Type: message/rfc822 Return-Path: pzee Received: (from pzee@localhost) by alto.express.com (8.6.8/8.6.6) id LAA00163 for sample; Thu, 26 May 1994 11:23:20 -0700 Date: Thu, 26 May 1994 11:23:20 -0700 From: "Philip J. Zee" Message-Id: <199405261823.LAA00163@alto.express.com> Apparently-To: sample help Could anyone who's installed this before tell me what I did wrong? By the way, here is my config file: # $whereami -- What machine am I running on? $whereami = "alto.express.com"; # $whoami -- Who do users send requests to me as? $whoami = "Majordomo@$whereami"; # $whoami_owner -- Who is the owner of the above, in case of problems? $whoami_owner = "Majordomo-owner@$whereami"; # $homedir -- Where can I find my extra .pl files, like majordomo.pl? # the environment variable HOME is set by the wrapper if ( defined $ENV{"HOME"}) { $homedir = $ENV{"HOME"}; } else { $homedir = "/usr/local/tools/majordomo"; } # $listdir -- Where are the mailing lists? $listdir = "/usr/local/tools/domolist"; # $digest_work_dir -- the parent directory for digest's queue area # Each list must have a subdirectory under this directory in order for # digest to work. E.G. The bblisa list would use: # /usr/local/mail/digest/bblisa # as its directory. $digest_work_dir = '/usr/local/tools/mail/digest'; # $log -- Where do I write my log? $log = "$homedir/Log"; # $mailer -- What program and args do I use to send mail? $mailer = "/usr/lib/sendmail -f\$sender \$to"; # Majordomo will look for "get" and "index" files related to $list in # directory "$filedir/$list$filedir_suffix", so set $filedir and # $filedir_suffix appropriately. For instance, to look in # /usr/local/mail/files/$list, use: # $filedir = "/usr/local/mail/files"; # $filedir_suffix = ""; # empty string # or to look in $listdir/$list.archive, use: # $filedir = "$listdir"; # $filedir_suffix = ".archive"; $filedir = "$listdir"; $filedir_suffix = ".archive"; # What command should I use to process an "index" request? $index_command = "/bin/ls -lRL"; # If you want to use FTPMAIL, rather than local access, for file transfer # and access, define the following: # $ftpmail_address = "ftpmail@decwrl.dec.com"; # $ftpmail_location = "FTP.$whereami"; # if you want the subject of the request to be included as part of the # subject of the reply (useful when automatically testing, or submitting # multiple command sets), set $return_subject to 1. $return_subject = 1; # If you are using majordomo at the -request address, set the # following variable to 1. This affects the welcome message that is # sent to a new subscriber as well as the help text that is generated. $majordomo_request = 0; # Set the umask for the process. Used to set default file status for # config file. umask(007); # the safe locations for archive directories # None of the parameters that use safedirs are actually used, so # @safedirs is a placeholder for future functionality. # Just ignore it for version 1.90. @safedirs = ( ); 1; # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.4 1994/05/08 20:27:38 rouil j Exp $ Thank you all for your time, 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 May 26 19:40:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA13063; Thu, 26 May 1994 19:40:23 GMT Received: from vespucci.iquest.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id MAA13057; Thu, 26 May 1994 12:40:16 -0700 Received: by vespucci.iquest.com (Linux Smail3.1.28.1 #14) id m0q6kTL-0003O4C; Thu, 26 May 94 13:48 CDT Received: from cc:Mail by multi.iquest.com id AA769988241 Thu, 26 May 94 14:37:21 Date: Thu, 26 May 94 14:37:21 From: "Dougal Campbell" Encoding: 1224 Text Message-Id: <9404267699.AA769988241@multi.iquest.com> To: Majordomo-Users@GreatCircle.COM, pzee@express.com (Philip J. Zee) Subject: Re: Majordomo help Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >I wonder if anyone could answer my question about majordomo. > >[...] > >I installed majordomo on alto. Its source code is in /usr/local/src/majordomo >and its home directory is :/usr/local/tools/majordomo and its listdir is >/usr/local/tools/domolist. ^^^^^^^^^^^^^^^^^^^^^^^^^^^ >[...] > >The following is in my /etc/aliases file concerning majordomo and my sample >list: >########################### ># majordomo aliases below # >########################### >majordomo: "|/usr/local/tools/majordomo/wrapper majordomo" >majordomo-owner: pzee >owner-majordomo: pzee > ># ># Sample mailing list ># >owner-sample: sample-owner >sample: "|/usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -R -l ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >[...] It appears that you have the wrong path here (/usr/local/mail/... instead of /usr/local/tools/...) ------------------------------+----------------------------------------------- Ernest MacDougal Campbell III |"Those who dream by day are cognizant of many dougal@multi.iquest.com | things which escape those who dream only by #include | night." -- Edgar Allan Poe From majordomo-users-owner Thu May 26 23:29:16 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA14785; Thu, 26 May 1994 23:29:16 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA14779; Thu, 26 May 1994 16:29:08 -0700 Received: from xt.cs.umb.edu by cs.umb.edu with SMTP id AA22341 (5.65c/IDA-1.4.4 for ); Thu, 26 May 1994 19:30:30 -0400 Message-Id: <199405262330.AA22341@cs.umb.edu> To: "Anant Bukkapatnam - FES" Cc: majordomo-users@greatcircle.com Subject: Re: Need some help In-Reply-To: Your message of "Wed, 25 May 1994 08:50:01 PDT." <9405250850.ZM8121@fiw007.fm.intel.com> Date: Thu, 26 May 1994 19:30:29 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9405250850.ZM8121@fiw007.fm.intel.com>, "Anant Bukkapatnam - FES" writes: > I am tring to set up majordomo. Which version, what MTA? I will assume 1.90 and sendmail. > I have got all that is to be done from the set instuctions. > I am having some of these problems. > > 1. I am using resend. > If there is wrong address in the mailing > list I want the list owner to be notified about the bounced > mail. I dont want the mail to go back to the initiator of the > message. Set the sendmail alias owner-listname to be the list owner. Set the sender configuration file entry to be owner-listname. This is about all you can do. There are some braindead mailers out there that insist on mailing bounces to the From: address regardless of what you do. > 2. I also observed that the a user can subscribe multiple > times to the same list. This is not a problem, but I was just > wondering the use of it. Majordomo does not complain > about this. It should. The same person can subscribe under multiple addresses, but if the same address is used, the following message should be returned in response to a subscribe request:
is already subscribed to -- John John Rouillard 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 May 27 15:03:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA19112; Fri, 27 May 1994 15:03:42 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA19102; Fri, 27 May 1994 08:03:32 -0700 Received: by netcom.com (8.6.8.1/SMI-4.1/Netcom) id IAA04246; Fri, 27 May 1994 08:04:46 -0700 From: artg@netcom.com (Art Graham) Message-Id: <199405271504.IAA04246@netcom.com> To: majordomo-users@GreatCircle.com Date: Fri, 27 May 1994 08:04:46 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 27 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk index majordomo-users end From majordomo-users-owner Fri May 27 16:09:36 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA19454; Fri, 27 May 1994 16:09:36 GMT Received: from taurus.fwl.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA19448; Fri, 27 May 1994 09:09:25 -0700 Received: by taurus.fwl.org (4.1/SMI-4.1) id AA07125; Fri, 27 May 94 09:10:09 PDT Date: Fri, 27 May 94 09:10:09 PDT From: brownal@fwl.org (Albert Brown) Message-Id: <9405271610.AA07125@taurus.fwl.org> To: majordomo-users@greatcircle.com Subject: majordomo help Content-Type: X-sun-attachment Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk ---------- X-Sun-Data-Type: text X-Sun-Data-Description: text X-Sun-Data-Name: text X-Sun-Content-Lines: 20 I have installed majordomo 1.62. I setup a test list and I have experienced the following problems: (1) When I subscribe or unsubscribe to the list it looks for an approval. It sends mail to testlist-approval even though I did not setup the list for subscription approval. (2) I subscribed myself to the list, and my subscription succeeded, but when I tried to post to the list, it said that I was not subscribed to the list. All other commands are working perfectly. I must have a problem in my configuration. The list name is "testlist". I have included a copy of my /etc/aliases file. Any help would be greatly appreciated, as I would like to setup several other mailing lists. Albert S. Brown Far West Laboratory brownal@fwl.org 415-565-3030 (office) ---------- X-Sun-Data-Type: default X-Sun-Data-Description: default X-Sun-Data-Name: aliases X-Sun-Content-Lines: 22 # # Majordomo # majordomo: "|/usr/local/etc/majordomo/wrapper majordomo" majordomo-owner: brownal owner-majordomo: brownal # # Test mailing list - testlist # testlist: "|/usr/local/etc/majordomo/wrapper resend -p bulk -M 10000 -l testlist -f testlist-owner -h fwl.org -I /usr/local/mail/testlist -s testlist-outgoing" owner-testlist: testlist-owner testlist-outgoing: :include:/usr/local/mail/testlist owner-testlist-outgoing: testlist-owner testlist-request: "|/usr/local/etc/majordomo/wrapper request-answer testlist" owner-testlist-request: testlist-owner testlist-owner: brownal owner-testlist-owner: brownal From majordomo-users-owner Fri May 27 21:36:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id VAA21124; Fri, 27 May 1994 21:36:06 GMT Received: from is.internic.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id OAA21118; Fri, 27 May 1994 14:35:53 -0700 Received: (from paulp@localhost) by is.internic.net (8.6.8/8.6.6) id OAA04289; Fri, 27 May 1994 14:36:40 -0700 Date: Fri, 27 May 1994 14:36:38 -0700 (PDT) From: Paul Phillips Subject: Majordomo inducing high load 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 Greetings -- We are now running a 4000 subscriber list that gets roughly 15-20 messages per day. Under listproc, this occasionally had a heavy impact on the machine, but was mostly benign. Since moving to majordomo, however, we have been under very high loads, often as high as 10, once hitting 38. I'm looking for suggestions as to the best way to keep the load to a reasonable level for users. I have some ideas, but has anyone else encountered this with a large list and solved it to their satisfaction? --- Paul Phillips | EMAIL: paulp@is.internic.net | InterNIC Information Services | WWW: http://www.internic.net/~paulp/ | InfoGuide Administrator | PHONE: 619-455-4626 FAX: 619-455-4640 | From majordomo-users-owner Fri May 27 22:30:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA21305; Fri, 27 May 1994 22:30:08 GMT Received: from recepsen.aa.msen.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA21291; Fri, 27 May 1994 15:29:59 -0700 Received: by recepsen.aa.msen.com (Smail3.1.28.1 #12) id m0q7AR1-000anGC; Fri, 27 May 94 18:31 EDT Message-Id: To: Paul Phillips cc: majordomo-users@greatcircle.com Subject: Re: Majordomo inducing high load In-reply-to: Your message of "Fri, 27 May 1994 14:36:38 PDT." Date: Fri, 27 May 1994 18:31:22 -0400 From: Edward Vielmetti Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > high load The usual approach to dealing with high server load for mail systems is to split up the outbound load to a second system (or perhaps to multiple other systems), breaking up the responsibilty for addressing mail and doing final delivery to different systems. This involves e.g. configuring your mail system on the relay machine to attempt delivery to a second system nearby, which would attempt to make the final delivery and queue if it's incapable of doing so. The usual reason for high loads on mail systems is long mail queues, lots of sendmail processes running trying to deliver mail to systems which are not there. If you can possibly move the queues off to a separate machine from the one that ahndles addressing, you'll be better off. (Not so fond memories of gatewaying an IBM mainframe's worth of mail all through a 9600 baud link to a Vax omitted...) --Ed From majordomo-users-owner Fri May 27 22:30:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA21319; Fri, 27 May 1994 22:30:39 GMT Received: from infoexp.express.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA21310; Fri, 27 May 1994 15:30:28 -0700 Received: from alto.express.com (alto.express.com [199.74.247.4]) by infoexp.express.com (8.6.8/8.6.6) with ESMTP id PAA13541; Fri, 27 May 1994 15:31:48 -0700 Received: from [199.74.247.5] (macsnoopy.express.com [199.74.247.5]) by alto.express.com (8.6.8/8.6.6) with SMTP id PAA02935; Fri, 27 May 1994 15:31:57 -0700 Message-Id: <199405272231.PAA02935@alto.express.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 27 May 1994 15:30:10 -0800 To: Paul Phillips From: pzee@express.com (Philip J. Zee) Subject: Re: Majordomo inducing high load Cc: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >Greetings -- > > We are now running a 4000 subscriber list that gets roughly 15-20 >messages per day. Under listproc, this occasionally had a heavy impact >on the machine, but was mostly benign. Since moving to majordomo, >however, we have been under very high loads, often as high as 10, once >hitting 38. > > I'm looking for suggestions as to the best way to keep the load to a >reasonable level for users. I have some ideas, but has anyone else >encountered this with a large list and solved it to their satisfaction? Well, I have a suggestion. It may not be very good. You can split the big list into small lists to be kept on other machies at different sites. When a messages is received, you machine distributes the message to subscribers on you machine. On the subscriber list of your machine, you could include other mailing lists on other machies so the message is sent to mailing lists on other machies. In this way, your system load could be reduced. Philip Zee ______________________________________________________________________ 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 Sat May 28 01:03:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id BAA21840; Sat, 28 May 1994 01:03:58 GMT Received: from alpha.xerox.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id SAA21834; Fri, 27 May 1994 18:03:52 -0700 Received: from avalon.parc.xerox.com ([13.1.101.241]) by alpha.xerox.com with SMTP id <14485(6)>; Fri, 27 May 1994 18:04:41 PDT Received: by avalon.parc.xerox.com id <2440>; Fri, 27 May 1994 18:04:36 -0700 From: Mark Verber To: paulp@is.internic.net, pzee@express.com Subject: Re: Majordomo inducing high load Cc: majordomo-users@greatcircle.com Message-Id: <94May27.180436pdt.2440@avalon.parc.xerox.com> Date: Fri, 27 May 1994 18:04:27 PDT Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I would note that the problem with your load going very high when majordomo exploders a mailing list is not so much a problem with majordomo as your mailer. I would guess that you are running on old version of sendmail. My guess is that zmailers or sendmail 8.x would help some of your problems. --mark From majordomo-users-owner Sat May 28 17:30:21 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA25325; Sat, 28 May 1994 17:30:21 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA25319; Sat, 28 May 1994 10:30:13 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA02482 (5.65c/IDA-1.4.4 for ); Sat, 28 May 1994 13:31:40 -0400 Message-Id: <199405281731.AA02482@cs.umb.edu> To: Paul Phillips Cc: majordomo-users@greatcircle.com Subject: Re: Majordomo inducing high load In-Reply-To: Your message of "Fri, 27 May 1994 14:36:38 PDT." Date: Sat, 28 May 1994 13:31:39 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Paul Phillips writes: > We are now running a 4000 subscriber list that gets roughly 15-20 >messages per day. Under listproc, this occasionally had a heavy impact >on the machine, but was mostly benign. Since moving to majordomo, >however, we have been under very high loads, often as high as 10, once >hitting 38. It is probably a sendmail issue, but make sure that there aren't majordomo processes sitting around trying to get a lock on log file etc. That will also drive the load average up on some systems, but it doesn't usually consume major resources, it just increases the load average. To do this use sendmail -bp or mailq to look at the queue and see if majordomo jobs are active, then as root look at the corresponding xf file for the job in the queue. The xf file should be mostly empty. If it has a lot of messages about locks, you need to change the permissions on the directories in your majordomo installation. -- John John Rouillard 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 Tue May 31 02:32:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id CAA09110; Tue, 31 May 1994 02:32:38 GMT Received: from callisto.pas.rochester.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id TAA09103; Mon, 30 May 1994 19:32:21 -0700 Received: (from colin@localhost) by callisto.pas.rochester.edu (8.6.9/8.6.9) id WAA17650 for majordomo-users@greatcircle.com; Mon, 30 May 1994 22:33:49 -0400 Date: Mon, 30 May 1994 22:33:49 -0400 From: colin sebastian roald Message-Id: <199405310233.WAA17650@callisto.pas.rochester.edu> To: majordomo-users@greatcircle.com Subject: sendmail 8.6.9 breaks resend? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk a few weeks ago, we had some breakins here, and went through the laborious process of reinstalling the system (SunOs 4.1.3_U1, i believe) with full patches, and upgrades to all the vulnerable utilities. this included sendmail 8.6.9. and ever since that time, resend has not worked for me. i can't guarantee the problem was sendmail, since an enormous number of things were changed all at the same time, and during that time our connections to the outside world were all disabled anyway. but i seems the most likely culprit. i have just upgraded to majordomo release 1.90, which didn't seem to fix any part of my problem. anyway, the error message looks like this: > From MAILER-DAEMON Mon May 30 21:54:25 1994 > Date: Mon, 30 May 1994 21:54:24 -0400 > From: Mail Delivery Subsystem > Subject: Returned mail: unknown mailer error 1 > To: psi-owner > > This is a MIME-encapsulated message > > --VAA17550.770349265/callisto.pas.rochester.edu > > The original message was received at Mon, 30 May 1994 21:54:24 -0400 > from colin@localhost > > ----- The following addresses had delivery problems ----- > "|/applic/ath/majordomo/wrapper resend -p bulk -l psi -h callisto.pas.rocheste> r.edu -r psi -f psi-owner psi-outgoing" (unrecoverable error) > (expanded from: psi) > > ----- Transcript of session follows ----- > Message delivered to mailing list psi > 554 "|/applic/ath/majordomo/wrapper resend -p bulk -l psi -h callisto.pas.roch> ester.edu -r psi -f psi-owner psi-outgoing"... unknown mailer error 1 > > ----- Original message follows ----- the entry in /etc/aliases looks like: | psi: "|/applic/ath/majordomo/wrapper resend -p bulk -l psi -h callisto.pas.ro\ | chester.edu -r psi -f psi-owner psi-outgoing" | psi-outgoing: :include:/applic/ath/majordomo/lists/psi [there are also some -owner and -request aliases.] so. can anyone help me? :-/ -- colin | it's all true. we're all space aliens. i'm amazed it took you so roald | long to find out. (sen. phil gramm, in weekly world news, jun 7 94) From majordomo-users-owner Tue May 31 15:03:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA13042; Tue, 31 May 1994 15:03:20 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id IAA13035; Tue, 31 May 1994 08:03:06 -0700 Received: from [192.26.65.78] by sgi.sgi.com via SMTP (920330.SGI/910110.SGI) for majordomo-users@GreatCircle.COM id AA15592; Tue, 31 May 94 08:04:41 -0700 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:majordomo-users@GreatCircle.COM id AA20506; Tue, 31 May 94 08:04:39 -0700 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9405311504.AA20506@lunch.asd.sgi.com> Subject: Re: Step-by-step docs for upgrade to 1.90? To: minerva@teleport.com Date: Tue, 31 May 1994 08:04:39 -0700 (PDT) Cc: MILAMC@vaxa.cis.uwosh.edu, majordomo-users@GreatCircle.COM In-Reply-To: <9405251301.ZM3198@teleport.com> from "Paradise Cowgirl" at May 25, 94 01:01:18 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 2060 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I asked a somewhat similar question and got no response. Can majordomo > 1.90 be installed in the existing 1.62 directory without changes to > the aliases and config/resend files? Can I "upgrade" my lists one at > a time? Yes. I have this setup for testing new betas, but it works great for integration once the new release is out too. What I do is make a separate directory for the new stuff, called /usr/local/majordomo-1.90. Make sure that wrapper and all your majordomo files point to this new directory. Then set up aliases for majordomo itself, called majordomo-1.90 or some such. Note that with the new -request handling, users have very little need to mail to majordomo directly, which helps limit confusion.... Now, I set up my lists, one at a time, and subscribe just me. The "incoming" alias for the list consists of the old majordomo resend, and the new 1.90 resend. This way, all incoming traffic goes through the old setup, and sends me a message using the new setup. Then I can compare the two messages. This is especially important for digests, where it might take a few tries to get the new setup just right (in my experience, anyway). Here's a few lines from my alias file to show you what I mean: > # > # majordomo setup > # > majordomo: "|/usr/local/majordomo/wrapper majordomo" > majordomo-owner: pdc > owner-majordomo: pdc > > majordomo-beta: "|/usr/local/majordomo-1.90/wrapper majordomo" > majordomo-beta-owner: pdc > owner-majordomo-beta: majordomo-beta-owner > mjd-test: majordomo-beta > > test-f-costume-digest: "| /local/majordomo-1.90/wrapper digest -r -C -l f-costume-digest test-f-costume-outgoing" > test-f-costume-outgoing: pdc > > [...] > f-costume: "|/usr/local/majordomo/wrapper resend -R -p bulk -M 50000 -l f-costume -f f-costume-owner -h lunch.asd.sgi.com -s f-costume-outgoing" > f-costume-outgoing: :include:/usr/local/majordomo/lists/f-costume, > f-costume-digestify, test-f-costume-digest > [...] -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Tue May 31 16:47:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA13949; Tue, 31 May 1994 16:47:39 GMT Received: from uni.INS.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id JAA13943; Tue, 31 May 1994 09:47:32 -0700 Received: from [151.144.86.124] by uni.INS.COM (4.1/SMI-4.1) id AA02618; Tue, 31 May 94 09:48:26 PDT Message-Id: <9405311648.AA02618@uni.INS.COM> X-Sender: ljrebar@uni.ins.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 31 May 1994 09:48:03 -0700 To: colin sebastian roald From: (Larry Rebarchik) Subject: Re: sendmail 8.6.9 breaks resend? Cc: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Colin, I know where you are coming from, This happened to me first time out of the gate. Though the exact problem was OLD Perl executables, 4.0.1.1, patch 3, gave the same error messages. Had me going around and around for a couple of hours until I suspected the Perl code. Larry At 12:11 AM 5/31/94 -0400, colin sebastian roald wrote: >Larry wrote: >> This may seem obvious, but is Perl up to date and are the executables chmod >> with executable permissions? >> Try perl -v to find the latest, should be 4.0.1.6 patch level 19 or so. > >oops. you know, it seems we might not ever have reinstalled perl when >we rebuilt the system. heh. :-/ > >thanks for the pointer, > > >-- >colin | precisely why all of the above should be so is not clear, but goes some >roald | way to explaining why, on the Disc, the Gods are not so much worshipped > as blamed. (pratchett) -- Have a tremendous day :-) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Lawrence J. Rebarchik ljrebar@ins.com International Network Services 415.254.4228 650 Castro Street, #260 (fax) 415.254.4288 Mountain View, CA 94041 "I shot an arrow into the air, and it stuck." -- Graffito in Los Angeles From majordomo-users-owner Tue May 31 17:36:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id RAA14383; Tue, 31 May 1994 17:36:30 GMT Received: from skat.usc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id KAA14375; Tue, 31 May 1994 10:36:18 -0700 Received: from rastaban.usc.edu (rastaban.usc.edu [128.125.18.48]) by skat.usc.edu (8.6.8.1/8.6.4) with ESMTP id KAA24798 for ; Tue, 31 May 1994 10:37:38 -0700 Received: (whb@localhost) by rastaban.usc.edu (8.6.8.1/8.6.4) id KAA06383 for majordomo-users@greatcircle.com; Tue, 31 May 1994 10:37:31 -0700 Date: Tue, 31 May 1994 10:37:31 -0700 From: Win Bent Message-Id: <199405311737.KAA06383@rastaban.usc.edu> To: majordomo-users@greatcircle.com Subject: Re: sendmail 8.6.9 breaks resend? X-Sun-Charset: US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >>> This may seem obvious, but is Perl up to date and are the executables chmod >>> with executable permissions? >>> Try perl -v to find the latest, should be 4.0.1.6 patch level 19 or so. >> >>oops. you know, it seems we might not ever have reinstalled perl when >>we rebuilt the system. heh. :-/ Doesn't it seem appropriate to have majordomo check for the minimum patch level? die "Perl version $] too old\n" if ($] < 4.016); A one-line fix that would have saved a lot of headaches... - Win Bent ----- Wilson H. Bent, Jr. whb@usc.edu USC University Comp. Services (213) 740-3181 From majordomo-users-owner Tue May 31 22:31:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id WAA16711; Tue, 31 May 1994 22:31:17 GMT Received: from sashimi.wwa.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id PAA16705; Tue, 31 May 1994 15:30:59 -0700 Received: by sashimi.wwa.com (Smail3.1.28.1 #8) id m0q8cMt-000bltC; Tue, 31 May 94 17:33 CDT Message-Id: From: dave@sashimi.wwa.com (David Vrona) Subject: how to archive each piece of mail???? To: majordomo-users@greatcircle.com Date: Tue, 31 May 1994 17:33:07 -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: 441 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi All, How does one archive each and every piece of mail sent to a list? Sorry if this is obvious but I did RTFM. thanks, dave -- David Vrona N9QNZ +1 708 367 1870 (voice) Internet: dave@wwa.com Computing Engineers Inc. +1 708 367 1871 (data) +1 708 367 1872 (fax) Home of WorldWide Access (SM), Internet services for the Chicagoland area. Send e-mail to info@wwa.com for information, or call +1 708 367 1871 (data). From majordomo-users-owner Tue May 31 23:32:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id XAA17132; Tue, 31 May 1994 23:32:20 GMT Received: from sparc.acu.edu.au by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-931103) id QAA17126; Tue, 31 May 1994 16:32:12 -0700 Received: from localhost (dorte@localhost) by sparc.acu.edu.au (8.6.4/8.6.4) id JAA03275; Wed, 1 Jun 1994 09:31:47 +1000 Date: Wed, 1 Jun 1994 09:31:46 +1000 (EST) From: Dorte Larsen Subject: Digest question To: Majordomo-Users@GreatCircle.COM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm a new manager of Majordomo. I just installed Majordomo in SUN station. It works fine, but one thing I couldn't do is the Digest. I'm using ver 1.90, is it possible to do the Digest ? - If it's possible, where can I find the docs to do that? Or I would be very appreciated if you can send me a help to do that. Thank you for your help. ------------------------------------------------- Dorte Larsen Australian Catholic University Phone : 61 +3 563 3711 Fax : 61 +3 563 3605 -------------------------------------------------