From majordomo-users-owner Fri Jul 1 02:49:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id CAA04744; Fri, 1 Jul 1994 02:49:29 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA04737; Thu, 30 Jun 1994 19:49:23 -0700 Message-Id: <199407010249.TAA04737@mycroft.GreatCircle.COM> To: Alan Millar cc: majordomo-users@greatcircle.com Subject: Re: Call for bounces In-reply-to: Your message of Thu, 30 Jun 1994 13:04:51 -0800 (PDT) Date: Thu, 30 Jun 1994 19:49:21 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Alan Millar writes: # I meant to send this to everyone, not just Ian. Send me your # interesting bounces. Thanks! Also, if you want ongoing fodder, I could put an alias at your site on the Firewalls-Owner alias here, so you got a copy of all the new ones. -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 Jul 1 02:53:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id CAA04794; Fri, 1 Jul 1994 02:53:11 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA04788; Thu, 30 Jun 1994 19:53:01 -0700 Message-Id: <199407010253.TAA04788@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.38.193.5/16.2) id AA16540; Thu, 30 Jun 1994 21:55:02 -0500 From: Larry Sheldon Subject: Suspension? To: majordomo-users@greatcircle.com Date: Thu, 30 Jun 94 21:54:58 CDT Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Does majordomo have a way that people can suspend their own subscription (as while on vacation)? Please don't tell me it is in the docs--I'm at home on vacation and too lazy to look it up, because I _have_ read all that and I don't remember seeing it. -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . . - L. F. (Larry) Sheldon, Jr. - . Unix Systems Administration . - Creighton University Computer Center-Old Gym Most of us can do more - . 2500 California Plaza than we think we can, . - Omaha, Nebraska, U.S.A. 68178 but usually less than - . lsheldon@creighton.edu we think we do. . - 402 280-2254 (work) - . 402 977-2946 (pager) "Bits & Pieces" . - 402 332-4622 (residence) - . . .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Fri Jul 1 03:32:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id DAA05111; Fri, 1 Jul 1994 03:32:01 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA05105; Thu, 30 Jun 1994 20:31:43 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA10255 (5.65c/IDA-1.4.4 for ); Thu, 30 Jun 1994 23:34:12 -0400 Message-Id: <199407010334.AA10255@cs.umb.edu> To: Larry Sheldon Cc: majordomo-users@greatcircle.com Subject: Re: Suspension? In-Reply-To: Your message of "Thu, 30 Jun 1994 21:54:58 CDT." <199407010253.TAA04788@mycroft.GreatCircle.COM> Date: Thu, 30 Jun 1994 23:34:12 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199407010253.TAA04788@mycroft.GreatCircle.COM>, Larry Sheldon writes: >Does majordomo have a way that people can suspend their own subscription >(as while on vacation)? > >Please don't tell me it is in the docs--I'm at home on vacation and too lazy >to look it up, because I _have_ read all that and I don't remember seeing >it. The reason you didn't see it is because it is not there. The only thing they can do is unsubscribe from the list while on vacation, and then resubscribe when they come back. Since most lists allow self subscription/unsubscription this isn't usually a major problem. -- 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 Jul 1 03:46:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id DAA05350; Fri, 1 Jul 1994 03:46:24 GMT Received: from is.internic.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA05335; Thu, 30 Jun 1994 20:46:02 -0700 Received: (from paulp@localhost) by is.internic.net (8.6.8/8.6.6) id UAA19970; Thu, 30 Jun 1994 20:48:01 -0700 Date: Thu, 30 Jun 1994 20:48:01 -0700 (PDT) From: Paul Phillips Subject: Re: Suspension? To: "John P. Rouillard" cc: Larry Sheldon , majordomo-users@GreatCircle.COM In-Reply-To: <199407010334.AA10255@cs.umb.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Any ideas how to make this REALLY clear to subscribers? We have about ten thousand subscribers here, and far and away the most common question is "How do I POSTPONE or NOMAIL? Listserv lets me do that..." I think NOMAIL is a totally redundant feature on a list with open subscription and unsubscription, but I'm about ready to add it in anyway just to lower the incoming mail volume. --- 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 | On Thu, 30 Jun 1994, John P. Rouillard wrote: > The reason you didn't see it is because it is not there. The only > thing they can do is unsubscribe from the list while on vacation, and > then resubscribe when they come back. Since most lists allow self > subscription/unsubscription this isn't usually a major problem. > > -- John From majordomo-users-owner Fri Jul 1 05:39:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id FAA06120; Fri, 1 Jul 1994 05:39:33 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA06113; Thu, 30 Jun 1994 22:39:28 -0700 Message-Id: <199407010539.WAA06113@mycroft.GreatCircle.COM> To: Larry Sheldon cc: majordomo-users@greatcircle.com Subject: Re: Suspension? In-reply-to: Your message of Thu, 30 Jun 94 21:54:58 CDT Date: Thu, 30 Jun 1994 22:39:26 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Larry Sheldon writes: # Does majordomo have a way that people can suspend their own subscription # (as while on vacation)? # # Please don't tell me it is in the docs--I'm at home on vacation and too lazy # to look it up, because I _have_ read all that and I don't remember seeing # it. Unsubscribe. -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 Jul 1 07:20:50 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA06948; Fri, 1 Jul 1994 07:20:50 GMT Received: from shrug.dur.ac.uk by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA06941; Fri, 1 Jul 1994 00:20:38 -0700 Received: from shrug (scott@localhost [127.0.0.1]) by shrug.dur.ac.uk (8.6.9/8.6.9) with SMTP id IAA08551 for ; Fri, 1 Jul 1994 08:22:49 +0100 Date: Fri, 1 Jul 1994 08:22:48 +0100 (BST) From: "Scott A. McIntyre" Subject: Digest headers and footers. To: majordomo-users@GreatCircle.COM Message-ID: <940701082248.8524AACYF.scott@shrug> Mime-Version: 1.0 (Generated by Eloquent) Content-Type: text/plain; charset=US-ASCII X-Mailer: Eloquent [1.01e]; Eloquent is a Trademark of Take Three Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Has anyone created any form of an extension to the majordomo package that would make it easier to include a particular file as a header or footer to either messages sent to a list or sent to/by a digest? I saw in one of the examples (from the ORA book, I think) of a very long bit of text that could be applied to the .config file, but I was looking for something a bit easier to modify, especially visually. Something along the lines of .header and .footer would be nice.. Thanks, Scott From majordomo-users-owner Fri Jul 1 06:12:36 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA09269; Fri, 1 Jul 1994 13:01:27 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA09262; Fri, 1 Jul 1994 06:01:18 -0700 Message-Id: <199407011301.GAA09262@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.38.193.5/16.2) id AB12591; Fri, 1 Jul 1994 08:03:29 -0500 From: Larry Sheldon Subject: Re: Suspension? To: majordomo-users@greatcircle.com Date: Fri, 1 Jul 94 8:03:28 CDT In-Reply-To: ; from "Paul Phillips" at Jun 30, 94 8:48 pm Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The story so far: I asked if there was a way for folk to suspend their subscription, as while they are on vacation [some people actually display some concern and responsibility for un-necessary resource consumption]. John Rouillard confirmed the suspicion that there is not, beyond "unsubscribing" and "subscribing". [Which offers the un-attractive features of letting customers get away, making more work for list-managers in dealing with the two-step process, PLUS the requests for what-was-missed.] Paul Phillips then said: > Any ideas how to make this REALLY clear to subscribers? We have about ten > thousand subscribers here, and far and away the most common question is > "How do I POSTPONE or NOMAIL? Listserv lets me do that..." > > I think NOMAIL is a totally redundant feature on a list with open > subscription and unsubscription, but I'm about ready to add it in anyway > just to lower the incoming mail volume. And I say : I think a really customer-oriented, user-friendly thing would be something like what the (gasp, what a role model!) USPS does where you can stop deliveries for a period, then get all that was missed. -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . . - L. F. (Larry) Sheldon, Jr. - . Unix Systems Administration . - Creighton University Computer Center-Old Gym Most of us can do more - . 2500 California Plaza than we think we can, . - Omaha, Nebraska, U.S.A. 68178 but usually less than - . lsheldon@creighton.edu we think we do. . - 402 280-2254 (work) - . 402 977-2946 (pager) "Bits & Pieces" . - 402 332-4622 (residence) - . . .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Fri Jul 1 13:40:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA09459; Fri, 1 Jul 1994 13:40:08 GMT Received: from antares.mcs.anl.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA09451; Fri, 1 Jul 1994 06:39:54 -0700 Received: from mcs.anl.gov (skeeve.mcs.anl.gov [140.221.5.130]) by antares.mcs.anl.gov (8.6.4/8.6.4) with ESMTP id IAA21903; Fri, 1 Jul 1994 08:42:21 -0500 Message-Id: <199407011342.IAA21903@antares.mcs.anl.gov> To: Larry Sheldon cc: majordomo-users@GreatCircle.COM, rackow@antares.mcs.anl.gov Subject: Re: Suspension? In-reply-to: Your message of "Fri, 01 Jul 1994 08:03:28 CDT." <199407011301.GAA09262@mycroft.GreatCircle.COM> Date: Fri, 01 Jul 1994 08:42:20 -0500 From: Gene Rackow Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk The resources are still being taken somplace. Using your model, the USPS does storage of your mail while on vacation, then has the added work of doing the mass delivery when you return, OR your own mailbox does the storage for you. I do not see the advantage of a "NOMAIL" or "POSTPONE" options, it just moves the burden and resposibility. Now if what you want is something that drops you from the list for some amount of time while you are on vacation, then unsubscribe and subscribe will do just that. It can even be done on you own local end via an "at" job if unix, or similar function from other machines. For a large mailing list, how much would you be willing to store, for how long per individual to support the other options? I can see how you could do it by making a "news" style spooling system to save article pointers and send to each address from the "togo" list, but it could be really easy to burn more resources on the lists home machine than it has to do such a thing. I have several busy lists with 10+ to 2500++ people on them. I would not want the nightmare of dealing with individual remailers and holding articles per user. Doing archives for the lists, then allowing people to pick up the archives for the time periods they were gone takes care of getting back messages. This is possible via majordomo with the "get" and "index" command. --gene From majordomo-users-owner Fri Jul 1 15:16:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA10404; Fri, 1 Jul 1994 15:16:33 GMT Received: from relay1.UU.NET by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA10396; Fri, 1 Jul 1994 08:16:17 -0700 Received: from cygnus.com by relay1.UU.NET with ESMTP (relay) id QQwwrl01554; Fri, 1 Jul 1994 11:18:43 -0400 Received: from tweedledumber.cygnus.com (tweedledumber.cygnus.com [192.80.44.2]) by cygnus.com (8.6.9/8.6.9) with ESMTP id IAA11254; Fri, 1 Jul 1994 08:18:10 -0700 From: Mark Eichin Received: from localhost (eichin@localhost) by tweedledumber.cygnus.com (8.6.4/8.6.4) id LAA18036; Fri, 1 Jul 1994 11:18:07 -0400 Date: Fri, 1 Jul 1994 11:18:07 -0400 Message-Id: <199407011518.LAA18036@tweedledumber.cygnus.com> To: paulp@is.internic.net CC: rouilj@cs.umb.edu, lsheldon@bluejay.creighton.edu, majordomo-users@GreatCircle.COM In-reply-to: (message from Paul Phillips on Thu, 30 Jun 1994 20:48:01 -0700 (PDT)) Subject: Re: Suspension? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >> thousand subscribers here, and far and away the most common question is >> "How do I POSTPONE or NOMAIL? Listserv lets me do that..." Perhaps it would be enough for you to just add subs for POSTPONE and NOMAIL that send back a file of instructions. When I first set up Majordomo, I fed the -request addresses to it directly -- and *later* added code to recognize a subscribe command without a listname and stuff in the name of the list that the -request was for. Didn't get any complaints -- people typically got a help-bounce, and figured out how to deal from that. I'll grant that it might not be all that polite... but it is informative, and doesn't take much effort on the user's part to get what they want... _Mark_ From majordomo-users-owner Fri Jul 1 16:10:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA11158; Fri, 1 Jul 1994 16:10:54 GMT Received: from hub.ucsb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA11145; Fri, 1 Jul 1994 09:10:12 -0700 Received: from dokoka (dokoka.ucsb.edu) by hub.ucsb.edu; id AA05270 sendmail 4.1/UCSB-2.1-sun Fri, 1 Jul 94 09:11:49 PDT for majordomo-users@greatcircle.com Received: from localhost.ucsb.edu by dokoka via SMTP (931110.SGI/920502.SGI.v2) for @hub.ucsb.edu:majordomo-users@greatcircle.com id AA11470; Fri, 1 Jul 94 09:11:43 -0700 Message-Id: <9407011611.AA11470@dokoka> To: Mark Eichin Cc: paulp@is.internic.net, rouilj@cs.umb.edu, lsheldon@bluejay.creighton.edu, majordomo-users@greatcircle.com Subject: Re: Suspension? Reply-To: "Alan K. Stebbens" In-Reply-To: Your message of Fri, 01 Jul 1994 11:18:07 PDT. <199407011518.LAA18036@tweedledumber.cygnus.com> Comments: Hyperbole mail buttons accepted, v3.12P. Date: Fri, 01 Jul 1994 09:11:31 -0700 From: Alan Stebbens Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > >> thousand subscribers here, and far and away the most common > >> question is "How do I POSTPONE or NOMAIL? Listserv lets me do > >> that..." The difference between "NOMAIL" and the suggested implementation of multiple "unsubscribe"s is that with the former, the knowledge of the user's mailing lists is being maintained, whilst with the latter it is lost. In other words, after being unsubscribed to all the mailing lists managed by a particular majordomo, the user must then resubscribe to them all by hand. A true "NOMAIL" would unsubscribe the user, but retain a history of which lists of which he/she was a member, and then when mail was reenabled, the user would be automatically resubscribed to the same mailing lists. As for doing a POSTPHONE (notice the _correct_ spelling :^), let's remember the motivation for these two commands: the user is away and unable to read his/her mail. Only the user can know which mailing lists for which mail is important enough to be retained during his/her absence; and, as has been pointed out, it is unreasable to expect each mailing list manager to retain enough disk space to absorb the postphoned mail for all vacationing mailing list members. The correct approach to this problem is to distribute the work & storage back to the user: use an incoming mail filter. With a filter, the user can decide, during vacation mode, to either file or junk mail from any given mailing list. The decision making and storage requirements are thus distributed back to each user. As for mail filters, there are very many, and most are quite flexible enough to filter mail based on the appearance of a particular mailing list name. MH (slocal + .maildelivery), Perl mailaudit, RAM's Perl/C based mailagent are a few. So, I don't think majordomo needs to implement the "nomail" or "postphone" feature. However, I do think that it should be trivial to do a unsubscribe all command, in order to quickly remove oneself from all mailing lists managed by a particular Majordomo. +-------------------------+-----------------------------------------+ | Alan Stebbens | University of California, Santa Barbara | | Email: aks@hub.ucsb.edu | Center for Computational Sciences | | CCSE: (805) 893-3221 | & Engineering (CCSE) | | Voice: (805) 893-8135 | 3107 Engineering I | | Fax: (805) 893-8121 | Santa Barbara, CA 93106 | +-------------------------+-----------------------------------------+ From majordomo-users-owner Fri Jul 1 16:41:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA11465; Fri, 1 Jul 1994 16:41:38 GMT Received: from hub.ucsb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA11445; Fri, 1 Jul 1994 09:40:33 -0700 Received: from dokoka (dokoka.ucsb.edu) by hub.ucsb.edu; id AA06480 sendmail 4.1/UCSB-2.1-sun Fri, 1 Jul 94 09:42:54 PDT for majordomo-users@greatcircle.com Received: from localhost.ucsb.edu by dokoka via SMTP (931110.SGI/920502.SGI.v2) for @hub.ucsb.edu:majordomo-workers@greatcircle.com id AA11823; Fri, 1 Jul 94 09:43:02 -0700 Message-Id: <9407011643.AA11823@dokoka> To: "Majordomo Users" , "Majordomo Workers" Subject: New Perl script: "announce" Reply-To: Alan Stebbens Date: Fri, 01 Jul 1994 09:42:57 -0700 From: Alan Stebbens Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here's a new Perl script, called "announce". It is a command, run by the mailing list administrator, which will send an initial announcement to the named mailing lists. This is useful if you have created an initially "seeded" mailing list, say from another existing list, and you wish all of the initial members to be aware of the mailing list's new management. Essentially, it performs the "&welcome" function from Majordomo on each named mailing list, without the logging or password function. Enjoy. Alan ============================= cut here =================================== #!/usr/local/bin/perl # announce list ... # # Announce list to its members, giving instructions. # # This is almost the same as the "&welcome" message, except # it is used to announce a list, which has its membership # pre-initialized without actual "subscription" commands. # # Written by Alan Stebbens , June 1994. # $Source$ # $Revision$ # $Date$ # $Author$ # $State$ # # $Locker: $ # set our path explicitly # PATH it is set in the wrapper, so there is no need to set it here. #$ENV{'PATH'} = "/bin:/usr/bin:/usr/ucb"; # What shall we use for temporary files? $tmp = "/tmp/majordomo.$$"; # Before doing anything else tell the world I am majordomo # The mj_ prefix is reserved for tools that are part of majordomo proper. $main'program_name = 'mj_announce'; # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; while ($ARGV[0]) { # parse for config file or default list if ($ARGV[0] eq "-C") { $cf = $ARGV[1]; shift(@ARGV); shift(@ARGV); } elsif ($ARGV[0] eq "-l") { $deflist = $ARGV[1]; shift(@ARGV); shift(@ARGV); } else { last; } } if (! -r $cf) { die("$cf not readable; stopped"); } eval(`cat $cf`) || die "eval of majordomo.cf failed $@"; # Go to the home directory specified by the .cf file chdir("$homedir"); # All these should be in the standard PERL library unshift(@INC, $homedir); require "ctime.pl"; # To get MoY definitions for month abbrevs require "majordomo_version.pl"; # What version of Majordomo is this? require "majordomo.pl"; # all sorts of general-purpose Majordomo subs require "shlock.pl"; # NNTP-style file locking require "config_parse.pl"; # functions to parse the config files # Here's where the fun begins... $| = 1; # check to see if the cf file is valid die("listdir not defined. Is majordomo.cf being included correctly?") if !defined($listdir); # who do we send the body to if we step on a landmine? &set_abort_addr($whoami_owner); # who do sendmail messages appear to come from, by default? &set_mail_from($whoami); &set_mail_sender($whoami_owner); if (defined($mailer)) { &set_mailer($mailer); } # set our hostname (for use in log messages). $hostname = &chop_nl(`hostname`); # Announce a list; this is used to tell an initial list that it # is open for business. All the current users get email telling # them about the new list. # announce list sub do_announce { # Check to make sure we've got the right arguments # and Check that the list is valid local($sm) = "announce"; local($list) = shift; local($clean_list); if ( ((!$list) || ! ($clean_list = &valid_list($listdir, $list))) && defined($deflist)) { unshift(@_,$list) ; # Not a list name, put it back. $list=$deflist || &squawk("$sm: which list?"); # set the list to deflist $clean_list = &valid_list($listdir, $list); } if ($clean_list ne "") { print "Announcing $clean_list..\n"; # The list is valid, parse the config file &get_config($listdir, $clean_list) if !&cf_ck_bool($clean_list, '', 1); local($list_addr) = "$list@$whereami"; # Set up the sendmail process to send mail to the list &set_mail_sender($config_opts{$list,"sender"} . "@" . $whereami); &sendmail(MSG, $list_addr, "Welcome to $list"); &set_mail_sender($whoami_owner); print MSG "Welcome to the $list mailing list!\n"; if ( $majordomo_request ) { print MSG <<"EOM"; If you ever want to remove yourself from this mailing list, send the following command in email to "${clean_list}-request@$whereami": unsubscribe Or you can send mail to "$whoami" with the following command EOM } else { print MSG <<"EOM"; If you ever want to remove yourself from this mailing list, you can send mail to "$whoami" with the following command EOM } print MSG <<"EOM"; in the body of your email message: unsubscribe $list $subscriber Here's the general information for the list you are subscribed to, in case you don't already have it: EOM # send them the info for the list, if it's available if (&lopen(INFO, "", "$listdir/$list.info")) { while () { print MSG $_; } &lclose(INFO); } else { print MSG "#### No info available for $list.\n"; } if (&valid_filename($filedir, $clean_list, $filedir_suffix, 'archive')) { print MSG <<"EOM"; All messages sent to this list are being archived in a file called "archive". To retreive the archive, send a messge with the command: get $clean_list archive to $whoami. EOM } print MSG <<"EOM"; If you wish additional information on participating in this or other mailing lists managed by Majordomo, please send a message containing the command: help to $whoami. EOM # close (and thereby send) the announcement message to the list close(MSG); } else { &squawk("$sm: unknown list '$list'."); } } sub squawk { print STDERR $_[0]."\n"; exit(1); } # each arg is a list to announce while ($list = shift(@ARGV)) { &do_announce($list); } print "Done.\n"; exit; From majordomo-users-owner Fri Jul 1 18:09:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA12523; Fri, 1 Jul 1994 18:09:12 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA12511; Fri, 1 Jul 1994 11:08:58 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA23391 (5.65c/IDA-1.4.4 for ); Fri, 1 Jul 1994 14:11:42 -0400 Message-Id: <199407011811.AA23391@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Re: Suspension? In-Reply-To: Your message of "Fri, 01 Jul 1994 09:15:16 PDT." <9407011615.AA11522@dokoka> Date: Fri, 01 Jul 1994 14:11:41 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9407011615.AA11522@dokoka>, Alan Stebbens writes: >> I think NOMAIL is a totally redundant feature on a list with open >> subscription and unsubscription, but I'm about ready to add it in anyway >> just to lower the incoming mail volume. > >If you do, "NOMAIL" should be a synonym for "unsubscribe all" How about having nomail produces a reply message like: # You have been unsubscribed from the lists at cs.umb.edu # when you want to resubscribe, reply to this message, and send the # following lines: subscribe bblisa-announce subscribe bblisa-digest this way the state stays with the user. If the sent an email in the first place with a subject line of: nomail or something, then they would easily be able to scan the mail box. It's not perfect but the resources needed to handle the listserv type NOMAIL and POSTPONE commands just doesn't make any sense in the world of uncoordinated majordomi. -- 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 Jul 1 18:52:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA12974; Fri, 1 Jul 1994 18:52:37 GMT Received: from z.nsf.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA12968; Fri, 1 Jul 1994 11:52:16 -0700 Received: from localhost (mmorse@localhost) by z.nsf.gov (8.6.4/8.6.4) id OAA23929 for majordomo-users@greatcircle.com; Fri, 1 Jul 1994 14:55:39 -0400 Message-Id: <199407011855.OAA23929@z.nsf.gov> From: mmorse@nsf.gov (Michael H. Morse) Date: Fri, 1 Jul 1994 14:55:38 EDT In-Reply-To: "John P. Rouillard" "Re: Suspension?" (Jul 1, 2:11pm) X-Mailer: Mail User's Shell (7.1.1 5/02/90) To: majordomo-users@greatcircle.com Subject: Re: Suspension? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > In message <9407011615.AA11522@dokoka>, Alan Stebbens writes: > >> I think NOMAIL is a totally redundant feature on a list with open > >> subscription and unsubscription, but I'm about ready to add it in anyway > >> just to lower the incoming mail volume. We should hear from someone who knows LISTSERV about exactly why these features exist, but I remember a discussion way back where a LISTSERV person convinced me that these features are *not* redundant even with open subs and unsubs. It might be that they retain the user's options they've set, or maybe something even more useful. --Mike From majordomo-users-owner Fri Jul 1 13:03:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA13513; Fri, 1 Jul 1994 19:33:58 GMT Received: from hub.ucsb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA11187; Fri, 1 Jul 1994 09:12:45 -0700 Received: from dokoka (dokoka.ucsb.edu) by hub.ucsb.edu; id AA05428 sendmail 4.1/UCSB-2.1-sun Fri, 1 Jul 94 09:15:15 PDT for majordomo-users@greatcircle.com Received: from localhost.ucsb.edu by dokoka via SMTP (931110.SGI/920502.SGI.v2) for @hub.ucsb.edu:majordomo-users@greatcircle.com id AA11522; Fri, 1 Jul 94 09:15:17 -0700 Message-Id: <9407011615.AA11522@dokoka> To: Paul Phillips Cc: "John P. Rouillard" , Larry Sheldon , majordomo-users@greatcircle.com Subject: Re: Suspension? Reply-To: "Alan K. Stebbens" In-Reply-To: Your message of Thu, 30 Jun 1994 20:48:01 PDT. Comments: Hyperbole mail buttons accepted, v3.12P. Date: Fri, 01 Jul 1994 09:15:16 -0700 From: Alan Stebbens Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I think NOMAIL is a totally redundant feature on a list with open > subscription and unsubscription, but I'm about ready to add it in anyway > just to lower the incoming mail volume. If you do, "NOMAIL" should be a synonym for "unsubscribe all" Alan From majordomo-users-owner Sat Jul 2 03:40:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id DAA17712; Sat, 2 Jul 1994 03:40:04 GMT Received: from is.internic.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA17704; Fri, 1 Jul 1994 20:39:53 -0700 Received: (from paulp@localhost) by is.internic.net (8.6.8/8.6.6) id UAA20172; Fri, 1 Jul 1994 20:41:51 -0700 Date: Fri, 1 Jul 1994 20:41:51 -0700 (PDT) From: Paul Phillips Subject: Re: Suspension? To: Larry Sheldon cc: majordomo-users@GreatCircle.COM In-Reply-To: <199407011301.GAA09262@mycroft.GreatCircle.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I like this idea enough that I am going to implement it here. Because of the way we archive individual messages, it won't be very difficult, but I know there are at least a couple other ways to archive and I'm not quite up to providing a general solution. I have messages archiving numerically -- i.e., when one goes to the list it is copied into the archive dir as number 1725 or whatever number it is up to. When a user issues whatever command we use for this (and I don't want to use POSTPONE for the sake of less confusion) I will transfer the name to a different file, say listname.postpone, along with the current number. When the user issues RESUME, it will be a simple matter to package up all the posts that have gone out since then and mail them off. Of course, I will check the total file size and ask the user whether he wants to receive it. Thoughts on this? A better way, perhaps? --- 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 | On Fri, 1 Jul 1994, Larry Sheldon wrote: > And I say : > I think a really customer-oriented, user-friendly thing would be something like > what the (gasp, what a role model!) USPS does where you can stop deliveries > for a period, then get all that was missed. From majordomo-users-owner Sat Jul 2 23:32:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA22763; Sat, 2 Jul 1994 23:32:53 GMT Received: from vader.egr.uri.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA22756; Sat, 2 Jul 1994 16:32:45 -0700 Received: by vader.egr.uri.edu (5.65/DEC-Ultrix/4.3) id AA23763; Sat, 2 Jul 1994 19:35:18 -0400 From: noah@vader.egr.uri.edu (Noah White) Message-Id: <9407022335.AA23763@vader.egr.uri.edu> Subject: URGENT: majordomo question To: majordomo-users@greatcircle.com Date: Sat, 2 Jul 1994 19:35:18 -0400 (EDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 785 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, I am upgrading and moving a majordomo list. Unfortunately it was a year ago that I set it up and I forgot qhat to put in cron to have a digest sent out to list members each night. Unfortunatly I no longer have access to the original cron file so I can't figure out what I did before. I have majordomo up to the point where it takes a submission and puts it in the incomming direcotry etc, and it handles subscriptions etc. But I need to have it compile the incoming messages into a digest and send it out once a day. Please respond ASAP as it is causing me down time. I know I am just missing something small because I have been tringing to use wrapper resend because that rings a bell but I'm not sure....plus there is the digest program etc. Thanks in advance, Noah From majordomo-users-owner Sun Jul 3 06:59:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA24763; Sun, 3 Jul 1994 06:59:07 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA24757; Sat, 2 Jul 1994 23:58:59 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA29612 (5.65c/IDA-1.4.4 for ); Sun, 3 Jul 1994 03:01:09 -0400 Message-Id: <199407030701.AA29612@cs.umb.edu> To: noah@vader.egr.uri.edu (Noah White) Cc: majordomo-users@greatcircle.com Subject: Re: URGENT: majordomo question In-Reply-To: Your message of "Sat, 02 Jul 1994 19:35:18 EDT." <9407022335.AA23763@vader.egr.uri.edu> Date: Sun, 03 Jul 1994 03:01:07 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Withmajordomo 1.92 there is a mkdigest command. So your cron job looks like: mail majordomo@wherever < /home/noah/.mkdigtext where .mkdigtext has: mkdigest Works like a charm. Alternatively you can use an echo of the command above, but it doesn't work as well since a ps will give away your list password. In message <9407022335.AA23763@vader.egr.uri.edu>, Noah White writes: > > Hi all, I am upgrading and moving a majordomo list. Unfortunately >it was a year ago that I set it up and I forgot qhat to put in cron >to have a digest sent out to list members each night. Unfortunatly I no >longer have access to the original cron file so I can't figure out what >I did before. I have majordomo up to the point where it takes a submission >and puts it in the incomming direcotry etc, and it handles subscriptions etc >. >But I need to have it compile the incoming messages into a digest and send i >t >out once a day. Please respond ASAP as it is causing me down time. I >know I am just missing something small because I have been tringing to >use wrapper resend because that rings a bell but I'm not sure....plus there >is the digest program etc. > >Thanks in advance, >Noah -- 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 Sun Jul 3 12:23:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA28468; Sun, 3 Jul 1994 19:07:07 GMT Received: from vader.egr.uri.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA18846; Fri, 1 Jul 1994 22:43:58 -0700 Received: by vader.egr.uri.edu (5.65/DEC-Ultrix/4.3) id AA21547; Sat, 2 Jul 1994 01:46:48 -0400 From: noah@vader.egr.uri.edu (Noah White) Message-Id: <9407020546.AA21547@vader.egr.uri.edu> Subject: Digesting To: majordomo-users@greatcircle.com Date: Sat, 2 Jul 1994 01:46:47 -0400 (EDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 324 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have been setting up a majordomo server and I have it up to the point where I can subscribe, unsubscribe etc. I can also send in a post which is put in the incoming directory, but I was wondering what the proper line to put in cron would be to send a digest of all the posts out once a day. Thanks in advance, Noah From majordomo-users-owner Sun Jul 3 12:43:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA28824; Sun, 3 Jul 1994 19:32:11 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA28816; Sun, 3 Jul 1994 12:32:02 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qKXCc-00014wC; Sun, 3 Jul 94 12:27 PDT Message-Id: To: majordomo-users@greatcircle.com Subject: Changing "From:" via resend Date: Sun, 03 Jul 1994 12:27:44 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk For one of the QueerNet lists, it is important that we rewrite the From: headers on some posts. (Support for anonymous posting is required, without use of anonymous posting services.) Is there a reason *not* to add a "-F" option that removes the "From:" header and replaces it? Are there other headers that should be rewritten or omitted that are not currectly rewritable? --- 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 Jul 3 22:16:15 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA29873; Sun, 3 Jul 1994 22:16:15 GMT Received: from saimiri.primate.wisc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA29863; Sun, 3 Jul 1994 15:16:07 -0700 Received: by saimiri.primate.wisc.edu; id RAA00689; 8.6.8.1/41.8; Sun, 3 Jul 1994 17:19:04 -0500 From: Software Development Message-Id: <199407032219.RAA00689@saimiri.primate.wisc.edu> Subject: Re: Changing "From:" via resend To: rogerk@unpc.queernet.org (Roger B.A. Klorese) Date: Sun, 3 Jul 1994 17:19:03 -0500 (CDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Roger B.A. Klorese" at Jul 3, 94 12:27:44 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 750 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > For one of the QueerNet lists, it is important that we rewrite the From: > headers on some posts. (Support for anonymous posting is required, without > use of anonymous posting services.) > > Is there a reason *not* to add a "-F" option that removes the "From:" header > and replaces it? Are there other headers that should be rewritten or > omitted that are not currectly rewritable? Yes, and the reason is that any number of us can come up with special-case header rewriting, and putting all that stuff in resend isn't the place to do it. Have resend send the messages to an alias for another script that does this rewriting. Then you can do whatever you want to your messages, without changing resend. Paul DuBois dubois@primate.wisc.edu From majordomo-users-owner Sun Jul 3 22:54:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA00146; Sun, 3 Jul 1994 22:54:23 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA00138; Sun, 3 Jul 1994 15:53:55 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qKaLt-00014wC; Sun, 3 Jul 94 15:49 PDT Message-Id: To: Software Development cc: majordomo-users@greatcircle.com Subject: Re: Changing "From:" via resend In-reply-to: Your message of Sun, 03 Jul 1994 17:19:03 -0500. <199407032219.RAA00689@saimiri.primate.wisc.edu> Date: Sun, 03 Jul 1994 15:49:29 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > Is there a reason *not* to add a "-F" option that removes the "From:" header > > and replaces it? Are there other headers that should be rewritten or > > omitted that are not currectly rewritable? > > Yes, and the reason is that any number of us can come up with special-case > header rewriting, and putting all that stuff in resend isn't the place > to do it. The same case can be made for some of the rewrites it *already* does. --- 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 Jul 3 23:32:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA00294; Sun, 3 Jul 1994 23:32:42 GMT Received: from nda.nda.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA00288; Sun, 3 Jul 1994 16:32:33 -0700 Received: from localhost (kovar@localhost) by nda.nda.com (8.6.4/8.6.4) id TAA09805; Sun, 3 Jul 1994 19:35:11 -0400 From: David Kovar Message-Id: <199407032335.TAA09805@nda.nda.com> Subject: Re: Changing "From:" via resend To: junkyard@primate.wisc.edu (Software Development) Date: Sun, 3 Jul 1994 19:35:09 -0400 (EDT) Cc: rogerk@unpc.queernet.org, majordomo-users@GreatCircle.COM In-Reply-To: <199407032219.RAA00689@saimiri.primate.wisc.edu> from "Software Development" at Jul 3, 94 05:19:03 pm X-Mailer: ELM [version 2.4 PL20] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 827 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Yes, and the reason is that any number of us can come up with special-case > header rewriting, and putting all that stuff in resend isn't the place > to do it. > > Have resend send the messages to an alias for another script that does > this rewriting. Then you can do whatever you want to your messages, without > changing resend. This is adding of complexity that I think is unwarrented, particularly since resend already munges several of the header lines. It seems to me that it would be best to keep all the header rewriting in one place. This piece of functionality would also help some news-mail gateways that I run. Currently, mail messages that come in from the newsgroup go to a -gate address. Replies go back to that -gate address rather than to the whole list, which isn't the right thing to do. -David From majordomo-users-owner Mon Jul 4 00:13:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA04419; Mon, 4 Jul 1994 06:48:36 GMT Received: from vader.egr.uri.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA04388; Sun, 3 Jul 1994 23:48:15 -0700 Received: by vader.egr.uri.edu (5.65/DEC-Ultrix/4.3) id AA01496; Mon, 4 Jul 1994 02:51:08 -0400 From: noah@vader.egr.uri.edu (Noah White) Message-Id: <9407040651.AA01496@vader.egr.uri.edu> Subject: More questions To: majordomo-users@greatcircle.com Date: Mon, 4 Jul 1994 02:51:08 -0400 (EDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 562 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am having trouble getting the 'message_fronter' to work. I copied Paul Pomes example supplied in the README and I put it in the config_parse.pl file. It is all once line and I didn't get any errors from majordomo, but when I made the digest it never included the fronter in it. I take it the .header and .footer files used in 1.6 are no longer used in 1.92? Also, the digest Reply-To and From addresses are in the form DigestName@machine.domain.edu. Is there anyway to keep the machine name out of this address? Thanks for all your help! -Noah From majordomo-users-owner Mon Jul 4 07:30:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA05082; Mon, 4 Jul 1994 07:30:39 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA05074; Mon, 4 Jul 1994 00:30:32 -0700 Message-Id: <199407040730.AAA05074@mycroft.GreatCircle.COM> To: majordomo-users@greatcircle.com Subject: Re: Changing "From:" via resend In-reply-to: Your message of Sun, 03 Jul 1994 15:49:29 -0700 Date: Mon, 04 Jul 1994 00:30:30 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Roger B.A. Klorese" writes: # > > Is there a reason *not* to add a "-F" option that removes the "From:" header # > > and replaces it? Are there other headers that should be rewritten or # > > omitted that are not currectly rewritable? # > # > Yes, and the reason is that any number of us can come up with special-case # > header rewriting, and putting all that stuff in resend isn't the place # > to do it. # # The same case can be made for some of the rewrites it *already* does. The rewrites that "resend" already does are, for the most part, the ones _I_ needed it to do (or thought I did at the time, anyway) for the various lists I run. That doesn't imply there aren't other rewrites that other folks would find useful for the lists _they_ run, or that such rewrites don't necessarily belong in "resend". Now, that said, "resend" (at least the 1.6x version; I'm not that familiar with 1.92's yet) suffers from a terrible case of command line option bloat... There are already over a dozen command line options, some of which are case-sensitive (which causes problems for some mailers, including Sendmail when running with certain configurations). So, on the one hand, in general I think that "resend" _is_ the right place to do header-hacking; that is precisely what it was written for. On the other hand, it's not clear that the current command-line option mechanism for specifying these rewrites is adequate or scalable (it's certainly not general); it may be time to come up with a different method for specifying the rewrites. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Mon Jul 4 06:03:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA07133; Mon, 4 Jul 1994 12:59:24 GMT Received: from mail.swip.net by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id FAA07127; Mon, 4 Jul 1994 05:59:16 -0700 Received: by mail.swip.net (8.6.8/2.01) id PAA27854; Mon, 4 Jul 1994 15:02:11 +0200 Received: by ufs.uf.se (/\==/\ Smail3.1.21.1 #21.7) id ; Mon, 4 Jul 94 14:01 MDT Received: by proxxi.uf.se (/\==/\ Smail3.1.21.1 #21.8) id ; Mon, 4 Jul 94 11:49 MET DST Date: Mon, 4 Jul 1994 11:45:52 +0200 (MET DST) From: Bror Hellman Subject: SMAIl .vs. SendMail cc: majordomo-users@GreatCircle.COM In-Reply-To: <9407020546.AA21547@vader.egr.uri.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have several ptoblems with my MajorDomo. I think it's due to incompatibility between SMAIL and SENDMAIL, but I don't really know for sure since I can't get hold of the SMAIL-manual. Can anyone tell me what (if anything) that needs to be changed in MajorDomo when running smail instead of sendmail? I *think* that the "-t" option doesn't comply with smail. Steamboat Willie ---------------------------------------------- ... Does The Little Mermaid wear an algebra? ---------------------------------------------- Internet: hellman@proxxi.uf.se, DuckNet: hellman@313:100/13.0 From majordomo-users-owner Mon Jul 4 09:33:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA08015; Mon, 4 Jul 1994 16:23:51 GMT Received: from saimiri.primate.wisc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA08009; Mon, 4 Jul 1994 09:23:43 -0700 Received: by saimiri.primate.wisc.edu; id LAA16553; 8.6.8.1/41.8; Mon, 4 Jul 1994 11:26:43 -0500 From: Software Development Message-Id: <199407041626.LAA16553@saimiri.primate.wisc.edu> Subject: Re: Changing "From:" via resend To: rogerk@unpc.queernet.org (Roger B.A. Klorese) Date: Mon, 4 Jul 1994 11:26:42 -0500 (CDT) Cc: junkyard@primate.wisc.edu, majordomo-users@greatcircle.com In-Reply-To: from "Roger B.A. Klorese" at Jul 3, 94 03:49:29 pm X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 947 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > > Is there a reason *not* to add a "-F" option that removes the "From:" header > > > and replaces it? Are there other headers that should be rewritten or > > > omitted that are not currectly rewritable? > > > > Yes, and the reason is that any number of us can come up with special-case > > header rewriting, and putting all that stuff in resend isn't the place > > to do it. > > The same case can be made for some of the rewrites it *already* does. That's true. However, it already does them; those rewrites are already in the code. You're proposing a new one. My argument was that your proposal can be repeated in an endless variety of ways (particularly the "Are there other headers that should be rewritten..." part), and the result of adopting them would be what? A mess. Aren't there other tools like procmail that already allow fairly arbitrary header rewriting? Why reinvent it in resend? Paul DuBois dubois@primate.wisc.edu From majordomo-users-owner Mon Jul 4 17:32:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA08401; Mon, 4 Jul 1994 17:32:28 GMT Received: from vader.egr.uri.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA08395; Mon, 4 Jul 1994 10:32:16 -0700 Received: by vader.egr.uri.edu (5.65/DEC-Ultrix/4.3) id AA05251; Mon, 4 Jul 1994 13:35:10 -0400 From: noah@vader.egr.uri.edu (Noah White) Message-Id: <9407041735.AA05251@vader.egr.uri.edu> Subject: More Fonter Questions To: majordomo-users@greatcircle.com Date: Mon, 4 Jul 1994 13:35:08 -0400 (EDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 1618 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Welp no one has had any sugestions yet, but I have been playing around with it in the mean time. I took out the mods. I made in config_parse.pl and put them in my listname.configure file. Now I get a header, _but_ not quite. He is what it is doing: 10,000 Maniacs Digest Monday, 4 July 1994 Volume 01 : Number 012 In this issue: [none] In this issue: Test1 ---------------------------------------------------------------------- As you can see it is generating 'In this issue:' for each subject! Why? I just want it to do that once and list the subjects, like it used to in 1.6x. Here is the mod I made to the listname.config file. It is worth noting that I can't get the \n new-lines (which are in Pauls example) to work. Also note that it is not printing anything after the _SUBJECTS_ portion....why not ? # message_fronter [string_array] (undef) # Text to be prepended to the beginning of all messages posted to the # list. The text is expanded before being used. The following # expansion tokens are defined: $LIST - the name of the current list, # $SENDER - the sender as taken from the from line, $VERSION, the # version of majordomo. If used in a digest, only the expansion token # _SUBJECTS_ is available, and it expands to the list of message # subjects in the digest message_fronter << END In this issue: _SUBJECTS_ See the end of the digest for information on subsc ribing to the $LIST mailing list. END Thanks for any help in advance...1.6 was so much easier to configure. -Noah From majordomo-users-owner Mon Jul 4 10:43:41 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA08422; Mon, 4 Jul 1994 17:34:02 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA08415; Mon, 4 Jul 1994 10:33:44 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qKrpC-00014xC; Mon, 4 Jul 94 10:28 PDT Message-Id: To: Software Development cc: majordomo-users@greatcircle.com Subject: Re: Changing "From:" via resend In-reply-to: Your message of Mon, 04 Jul 1994 11:26:42 -0500. <199407041626.LAA16553@saimiri.primate.wisc.edu> Date: Mon, 04 Jul 1994 10:28:47 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Aren't there other tools like procmail that already allow fairly arbitrary > header rewriting? Why reinvent it in resend? If I used procmail and co., and used it fully, I wouldn't need most of Majordomo. The idea is to have a useful, closed Majordomo suite for mailing list administration, not to use chunks of overlapping tools. --- ROGER B.A. KLORESE rogerk@QueerNet.ORG 2215-R Market Street #576 San Francisco, CA 94114 +1 415 ALL-ARFF "There is only one real blasphemy: the refusal of joy." -- Paul Rudnick From majordomo-users-owner Mon Jul 4 11:33:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA08793; Mon, 4 Jul 1994 18:23:42 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA08784; Mon, 4 Jul 1994 11:23:32 -0700 Message-Id: <199407041823.LAA08784@mycroft.GreatCircle.COM> To: "Roger B.A. Klorese" cc: Software Development , majordomo-users@greatcircle.com Subject: Re: Changing "From:" via resend In-reply-to: Your message of Mon, 04 Jul 1994 10:28:47 -0700 Date: Mon, 04 Jul 1994 11:23:30 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Roger B.A. Klorese" writes: # > Aren't there other tools like procmail that already allow fairly arbitrary # > header rewriting? Why reinvent it in resend? # # If I used procmail and co., and used it fully, I wouldn't need most of # Majordomo. The idea is to have a useful, closed Majordomo suite for # mailing list administration, not to use chunks of overlapping tools. Yes, this is more or less the philosophy I followed. I hate packages that, before I can use them, require me to obtain and install lots of _other_ packages. Now, that's not to say that Majordomo should do everything. For example, I felt that there were already good applications out there for retrieving files by email ("ftpmail", or whatever you want to call them), so I resisted putting any such features into Majordomo for a long time. Finally, I gave in and put simple "index" and "get" commands in (which somebody else wrote; sorry I can't recall who right now). I'm _still_ not sure that was the right decision. So... Header rewriting is the whole purpose of "resend". Why do some of it there and some of it in some other package? I mean, if you want to, feel free, but why make that the standard configuration? -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Mon Jul 4 11:39:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA08715; Mon, 4 Jul 1994 18:18:45 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA08708; Mon, 4 Jul 1994 11:18:32 -0700 Message-Id: <199407041818.LAA08708@mycroft.GreatCircle.COM> To: Software Development cc: rogerk@unpc.queernet.org (Roger B.A. Klorese), majordomo-users@greatcircle.com Subject: Re: Changing "From:" via resend In-reply-to: Your message of Mon, 4 Jul 1994 11:26:42 -0500 (CDT) Date: Mon, 04 Jul 1994 11:18:28 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Software Development writes: # > > > Is there a reason *not* to add a "-F" option that removes the "From:" header # > > > and replaces it? Are there other headers that should be rewritten or # > > > omitted that are not currectly rewritable? # > > # > > Yes, and the reason is that any number of us can come up with special-case # > > header rewriting, and putting all that stuff in resend isn't the place # > > to do it. # > # > The same case can be made for some of the rewrites it *already* does. # # That's true. However, it already does them; those rewrites are already # in the code. You're proposing a new one. My argument was that your # proposal can be repeated in an endless variety of ways (particularly the # "Are there other headers that should be rewritten..." part), and the result # of adopting them would be what? A mess. # # Aren't there other tools like procmail that already allow fairly arbitrary # header rewriting? Why reinvent it in resend? I think "resend" is the right place to put it (it was created for such things), but we need to figure out a different way of specifying the rewrites than via a command line option per possible rewrites; there are already far too many command line options for "resend". -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 Jul 5 03:43:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA12396; Tue, 5 Jul 1994 08:22:50 GMT Received: from megalon.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id BAA12381; Tue, 5 Jul 1994 01:22:28 -0700 Received: by megalon.com (8.6.8/SMI-5.3) id BAA01555; Tue, 5 Jul 1994 01:21:10 -0700 Date: Tue, 5 Jul 1994 01:21:10 -0700 From: Max Hozven - Network Support Message-Id: <199407050821.BAA01555@megalon.com> To: majordomo-users@greatcircle.com Subject: "Recipient names must be specified" alias in Majordomo Content-Length: 1342 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I'm just installed majordomo on my system (a Sun running Solaris 5.3 and Berkeley sendmail) and am having this problem: (Here's output of a "mail -v majordomo" test): Mail -v majordomo Subject: test info sample EOT 49 [megalon]:max:~ >> majordomo... aliased to "|/usr/local/mail/majordomo/wrapper majordomo" # $whereami -- What machine am I running on? $whereami = "megalon.megalon.com"; # $ftpmail_location = "FTP.$whereami"; megalon majordomo[1410] {Max Hozven - Network Support } info majordomo[1410] {Max Hozven - Network Support } help max... Recipient names must be specified Saving message in /home/max/dead.letter /tmp/majordomo.1410.* "|/usr/local/mail/majordomo/wrapper majordomo"... Sent I don't know why I am getting the error: "max... Recipient names must be specified" The alias "max" is a valid alias on the system. I've set up the necessary majordomo support files and alias entries to make "sample" a test alias (per the doc's). I've read all the support docs that came with this Majordomo distribution and I think the aliases file, and installed directories/files permissions are correct. If anyone can point me in the right direction, I'd appreciate it. Thanks, -Max Max Hozven max@megalon.com From majordomo-users-owner Tue Jul 5 06:33:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA14435; Tue, 5 Jul 1994 13:19:43 GMT Received: from edge.ercnet.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA14429; Tue, 5 Jul 1994 06:19:22 -0700 Received: by edge.ercnet.com (4.1/SMI-4.1) id AA17681; Tue, 5 Jul 94 08:21:36 CDT Date: Tue, 5 Jul 94 08:21:36 CDT From: jwarwick@edge.ercnet.com (John Warwick) Message-Id: <9407051321.AA17681@edge.ercnet.com> To: Majordomo-Users@GreatCircle.COM Subject: Unknown Mailer Error Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have been trying to get Majordomo to run, but I keep getting an 'unknown mailer error 1' message. Here is what happens when I try to test it: /edge/jwarwick>/usr/lib/sendmail -v majordomo@edge.ercnet.com majordomo@edge.ercnet.com... aliased to "|/edge/majordomo/wrapper majordomo" help "|/edge/majordomo/wrapper majordomo"... Connecting to via prog... "|/edge/majordomo/wrapper majordomo"... unknown mailer error 1 owner-majordomo... aliased to jwarwick Postmaster... aliased to tchoate tchoate... Connecting to via local... tchoate... Sent jwarwick... Connecting to via local... jwarwick... Sent Here are my aliases: owner-owner: jwarwick #Majordomo majordomo: "|/edge/majordomo/wrapper majordomo" majordom: owner-majordomo majordomo-owner: jwarwick owner-majordomo: jwarwick Thanks, john John Warwick From majordomo-users-owner Tue Jul 5 09:16:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA16198; Tue, 5 Jul 1994 15:56:04 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA16191; Tue, 5 Jul 1994 08:55:50 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA29078 (5.65c/IDA-1.4.4 for ); Tue, 5 Jul 1994 11:58:33 -0400 Message-Id: <199407051558.AA29078@cs.umb.edu> To: jwarwick@edge.ercnet.com (John Warwick) Cc: Majordomo-Users@greatcircle.com Subject: Re: Unknown Mailer Error In-Reply-To: Your message of "Tue, 05 Jul 1994 08:21:36 CDT." <9407051321.AA17681@edge.ercnet.com> Date: Tue, 05 Jul 1994 11:58:32 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Things to check: is your prog mailer /bin/sh, or is it /bin/false. A lot of sites disabled the prog mailer in the last round of sendmail security problems. does any program alias work correctly? does "|/path/to/wrapper majordomo" work (no space between | and "'s) In message <9407051321.AA17681@edge.ercnet.com>, John Warwick writes: >I have been trying to get Majordomo to run, but I keep getting an >'unknown mailer error 1' message. Here is what happens when I try >to test it: > >/edge/jwarwick>/usr/lib/sendmail -v majordomo@edge.ercnet.com >majordomo@edge.ercnet.com... aliased to "|/edge/majordomo/wrapper majordomo >" >help > >"|/edge/majordomo/wrapper majordomo"... Connecting to via prog... >"|/edge/majordomo/wrapper majordomo"... unknown mailer error 1 >owner-majordomo... aliased to jwarwick >Postmaster... aliased to tchoate >tchoate... Connecting to via local... >tchoate... Sent >jwarwick... Connecting to via local... >jwarwick... Sent > >Here are my aliases: > >owner-owner: jwarwick >#Majordomo >majordomo: "|/edge/majordomo/wrapper majordomo" >majordom: owner-majordomo >majordomo-owner: jwarwick >owner-majordomo: jwarwick > >Thanks, >john > >John Warwick -- 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 Jul 5 12:43:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA18652; Tue, 5 Jul 1994 19:25:41 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA18642; Tue, 5 Jul 1994 12:25:31 -0700 Received: by netcom.com (8.6.8.1/SMI-4.1/Netcom) id MAA21222; Tue, 5 Jul 1994 12:28:37 -0700 From: sylviac@netcom.com (Sylvia Caras) Message-Id: <199407051928.MAA21222@netcom5.netcom.com> Subject: Lost subscribers list To: majordomo-users@greatcircle.com Date: Tue, 5 Jul 1994 12:28:36 -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: 722 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk For the second time in a month, my subscribers list has been emptied. Do you think this is a netcom problem or a harrassment problem? Suggestions on how to proceed, please. I am not a programmer, am running majordomo courtesy of netcom. Since the first time, I have been who-ing and saving the result whenever there is an activity, so the reconstruction only took about an hour. But, ... . -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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 Tue Jul 5 12:53:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA18742; Tue, 5 Jul 1994 19:32:08 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA18682; Tue, 5 Jul 1994 12:29:00 -0700 Received: from bolis by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA23642; Tue, 5 Jul 94 12:30:54 -0700 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0qLEyV-0002YTC; Tue, 5 Jul 94 11:12 PDT Message-Id: From: Alan Millar Subject: Re: SMAIl .vs. SendMail To: hellman@proxxi.uf.se (Bror Hellman) Date: Tue, 5 Jul 1994 11:12:04 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Bror Hellman" at Jul 4, 94 11:45:52 am 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: 1087 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Bror Hellman spake of these matters: I'll assume we are talking about SMail 3 and not SMail 2. > I have several ptoblems with my MajorDomo. I think it's due to > incompatibility between SMAIL and SENDMAIL, but I don't really know for > sure since I can't get hold of the SMAIL-manual. > > Can anyone tell me what (if anything) that needs to be changed in > MajorDomo when running smail instead of sendmail? Primarily, the only problem is in how Smail interprets bracketed addresses in an alias :include: file. The solution is either to enable the listname.strip option or hack Majordomo to put a comma at the end of each line. > I *think* that the "-t" option doesn't comply with smail. I'm running SMail 3.1.28, and the "-t" works just fine. It just retrofitted 1.62 with it because I haven't done 1.92 yet, and it works great. - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: ftp://ftp.netcom.com/pub/amillar/welcome.html If only we were all weiner dogs, our problems would be solved! -Brave Little Toaster From majordomo-users-owner Tue Jul 5 14:03:30 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA19606; Tue, 5 Jul 1994 20:43:07 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA19599; Tue, 5 Jul 1994 13:42:57 -0700 Message-Id: <199407052042.NAA19599@mycroft.GreatCircle.COM> To: sylviac@netcom.com (Sylvia Caras) cc: majordomo-users@greatcircle.com Subject: Re: Lost subscribers list In-reply-to: Your message of Tue, 5 Jul 1994 12:28:36 -0700 (PDT) Date: Tue, 05 Jul 1994 13:42:55 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk sylviac@netcom.com (Sylvia Caras) writes: # For the second time in a month, my subscribers list # has been emptied. # # Do you think this is a netcom problem or a harrassment # problem? # # Suggestions on how to proceed, please. I am not # a programmer, am running majordomo courtesy of netcom. # # Since the first time, I have been who-ing and saving the # result whenever there is an activity, so the reconstruction # only took about an hour. But, ... . Has netcom been having disk-full problems? The only times I've seen Majordomo totally zap files is when the disk fills up while it's in the middle of adding someone to the list. It _should_ be more robust, but it's not; sorry about that. -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 Jul 5 15:33:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA20759; Tue, 5 Jul 1994 21:58:53 GMT Received: from sashimi.wwa.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA19879; Tue, 5 Jul 1994 14:05:18 -0700 Received: by sashimi.wwa.com (Smail3.1.28.1 #8) id m0qLHiF-000bm0C; Tue, 5 Jul 94 16:07 CDT Message-Id: Date: Tue, 5 Jul 94 16:07 CDT From: hactar@sashimi.wwa.com (RJ Pietkivitch) To: majordomo-users@GreatCircle.COM, sylviac@netcom.com Subject: Re: Lost subscribers list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I lost my member list too, not very long ago. The date on my zero-length member file matched an unsubscribe entry in the Log file. I suspect that the unsubscribe command failed and then blew away the member list for whatever unknown reason (spite?). Fortunately, I had made a copy of my member list a day or two before it got wiped. The list I run is moderated (ie, I approve all subscription requests) so there was no need for me to backtrack through the Log file in order to get any new members not in my personal file. I now make a copy my member file on a daily basis. Bob From majordomo-users-owner Tue Jul 5 16:06:02 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA21160; Tue, 5 Jul 1994 22:45:33 GMT Received: from infoexp.express.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA21154; Tue, 5 Jul 1994 15:45:24 -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 PAA18879 for ; Tue, 5 Jul 1994 15:48:18 -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 PAA19096 for ; Tue, 5 Jul 1994 15:48:13 -0700 Message-Id: <199407052248.PAA19096@alto.express.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 5 Jul 1994 15:50:57 -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 have installed majordomo 1.92 as documented. When I tried to test by using the echo help, this is what I got: majordomo... aliased to "|/home/sigweb/majordomo/wrapper majordomo" ld.so: warning: /usr/lib/libc.so.1.8 has older revision than expected 9 majordomo: No such file or directory "|/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 Saving message in /home/sigweb/pzee/dead.letter /home/sigweb/pzee/dead.letter... Sent Does this mean that majordomo 1.92 has conflicts with old version of sendmail? Thanks for any help in advance, 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 Tue Jul 5 16:23:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA21412; Tue, 5 Jul 1994 23:16:51 GMT Received: from hermes.intel.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA21406; Tue, 5 Jul 1994 16:16:40 -0700 Received: from pcocd2.intel.com by hermes.intel.com (5.65/10.0i); Tue, 5 Jul 94 16:17:19 -0700 Received: from fiw007 (fiw007.fm.intel.com) by pcocd2.intel.com with SMTP id AA28487 (5.65c/IDA-1.4.4 for ); Tue, 5 Jul 1994 16:16:50 -0700 Received: by fiw007 (4.1/FMDT-RS6000) id AA23855; Tue, 5 Jul 94 16:16:44 PDT From: "Anant Bukkapatnam - FES" Message-Id: <9407051616.ZM23853@fiw007.fm.intel.com> Date: Tue, 5 Jul 1994 16:16:43 -0700 X-Mailer: Z-Mail (3.0.1 23feb94) To: majordomo-users@greatcircle.com Subject: Help Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, I have majordomo1.63 running at our site. I did RTFM but did not find this point. Is it possible to tell majordomo to allow only the owner of the list to send mail to the list. Other people can only subcribe or perform other operations on it but cannot send mail to the list. This is really important for and any help in this direction will be appreciated. thanks From majordomo-users-owner Tue Jul 5 16:44:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA21569; Tue, 5 Jul 1994 23:35:09 GMT Received: from callisto.pas.rochester.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA21559; Tue, 5 Jul 1994 16:34:58 -0700 Received: (from colin@localhost) by callisto.pas.rochester.edu (8.6.9/8.6.9) id TAA29204 for majordomo-users@GreatCircle.COM; Tue, 5 Jul 1994 19:20:48 -0400 Date: Tue, 5 Jul 1994 19:20:48 -0400 From: colin sebastian roald Message-Id: <199407052320.TAA29204@callisto.pas.rochester.edu> To: majordomo-users@GreatCircle.COM Subject: Re: Lost subscribers list Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I now make a copy my member file on a daily basis. better yet, stick 0 6 * * * /bin/cp /usr/ath/mjd/lists/psi /usr/ath/mjd/lists/psi.sv in cron. (or is that what you mean?) anyway, would be kind to stick a warning to this effect into the distribution files somewhere. From majordomo-users-owner Wed Jul 6 03:51:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA27294; Wed, 6 Jul 1994 08:45:41 GMT Received: from eskimo.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id BAA27288; Wed, 6 Jul 1994 01:45:26 -0700 Received: by eskimo.com (5.65c/1.35) id AA11370; Wed, 6 Jul 1994 01:48:19 -0700 Date: Wed, 6 Jul 1994 01:48:18 -0700 (PDT) From: Dave Hart Subject: Re: Help (fwd) To: majordomo-users@greatcircle.com In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Tue, 5 Jul 1994, Anant Bukkapatnam - FES wrote: > Is it possible to tell majordomo to allow > only the owner of the list to send mail to the list. Set up a moderated list. You'll have to "approve" your own posts as well as anyone else's. If you always approve your own and never approve any others, you're in business. --- davehart@eskimo.com From majordomo-users-owner Wed Jul 6 05:39:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA28861; Wed, 6 Jul 1994 12:35:24 GMT Received: from idcresearch.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id FAA28855; Wed, 6 Jul 1994 05:35:05 -0700 From: mlevi@idcresearch.com Received: from ccmailout.idcresearch.com by idcresearch.com (5.0/NEARnet-idcresearch-1.5) id AA10280; Wed, 6 Jul 94 08:36:32 EDT Received: from ccMail by ccmailout.idcresearch.com id AA773509165 Wed, 06 Jul 94 08:39:25 EST Date: Wed, 06 Jul 94 08:39:25 EST Encoding: 221 Text Message-Id: <9406067735.AA773509165@ccmailout.idcresearch.com> To: majordomo-users@greatcircle.com Subject: Setting up a moderated list content-length: 215 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk It is not clear to me from the documentation I have how one sets up a moderated list with Majord. Is there a set of instructions I can grab from somewhere? Thanks, Mike Levi From majordomo-users-owner Wed Jul 6 06:11:16 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA29062; Wed, 6 Jul 1994 13:03:50 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA29056; Wed, 6 Jul 1994 06:03:24 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HEDRQCC06O001QV4@SYSWRK.UCIS.DAL.CA>; Wed, 6 Jul 1994 10:05:32 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HEDRQ2TD9S00PWWU@AC.DAL.CA>; Wed, 6 Jul 1994 10:05:22 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:majordomo-users@GreatCircle.COM id AA07155; Wed, 6 Jul 94 09:59:47 -0300 Date: Wed, 06 Jul 1994 09:59:46 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Digesting In-reply-to: <199407030701.AA29612@cs.umb.edu> from "John P. Rouillard" at Jul 3, 94 03:01:07 am To: rouilj@cs.umb.edu (John P. Rouillard) Cc: majordomo-users@GreatCircle.COM Message-id: <9407061259.AA07155@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: 936 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk You write: >Withmajordomo 1.92 there is a mkdigest command. So your cron job looks like: > >mail majordomo@wherever < /home/noah/.mkdigtext > >where .mkdigtext has: > > mkdigest > >Works like a charm. Alternatively you can use an echo of the command above, >but it doesn't work as well since a ps will give away your list password. I'm not sure what kind of charm this is, but as I posted before, when I try to create a digest in this way I get back the message: >>>> mkdigest *** digest: failed errors follow No messages. Stopped ABORT No messages. Stopped at majordomo.pl line 209, <_GEN_0> line 1. and I don't know enough perl to debug this. If anyone has any ideas what is happening I would appreciate advice. And yes, the command was indeed 'mkdigest list password', I'm not that literal! Just didn't want to publish that info. Bill Silvert From majordomo-users-owner Wed Jul 6 07:20:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA29538; Wed, 6 Jul 1994 14:05:47 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA29532; Wed, 6 Jul 1994 07:05:27 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qLXfM-00014xC; Wed, 6 Jul 94 07:09 PDT Message-Id: To: Dave Hart cc: majordomo-users@greatcircle.com Subject: Re: Help (fwd) In-reply-to: Your message of Wed, 06 Jul 1994 01:48:18 -0700. Date: Wed, 06 Jul 1994 07:09:30 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > On Tue, 5 Jul 1994, Anant Bukkapatnam - FES wrote: > > > Is it possible to tell majordomo to allow > > only the owner of the list to send mail to the list. > > Set up a moderated list. You'll have to "approve" your own posts as well > as anyone else's. If you always approve your own and never approve any > others, you're in business. Or use the -I flag to "resend", with a file with only your address in it. --- 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 Wed Jul 6 07:30:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA29561; Wed, 6 Jul 1994 14:09:23 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA29555; Wed, 6 Jul 1994 07:09:16 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA06199 (5.65c/IDA-1.4.4 for ); Wed, 6 Jul 1994 10:11:57 -0400 Message-Id: <199407061411.AA06199@cs.umb.edu> To: bill@biome.bio.dfo.ca (Bill Silvert) Cc: majordomo-users@greatcircle.com Subject: Re: Digesting In-Reply-To: Your message of "Wed, 06 Jul 1994 09:59:46 -0300." <9407061259.AA07155@biome.bio.ns.ca> Date: Wed, 06 Jul 1994 10:11:55 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Is your digest alias set up as described in the README file for 1.9x? You need the -C option (I think check the README to be sure) otherwise majordomo and digest don't work well together. In message <9407061259.AA07155@biome.bio.ns.ca>, Bill Silvert writes: >You write: > >>Withmajordomo 1.92 there is a mkdigest command. So your cron job looks like >: >> >>mail majordomo@wherever < /home/noah/.mkdigtext >> >>where .mkdigtext has: >> >> mkdigest >> >>Works like a charm. Alternatively you can use an echo of the command above, >>but it doesn't work as well since a ps will give away your list password. > >I'm not sure what kind of charm this is, but as I posted before, when I >try to create a digest in this way I get back the message: > >>>>> mkdigest >*** digest: failed errors follow >No messages. >Stopped >ABORT No messages. >Stopped at majordomo.pl line 209, <_GEN_0> line 1. > >and I don't know enough perl to debug this. If anyone has any ideas >what is happening I would appreciate advice. > >And yes, the command was indeed 'mkdigest list password', I'm not that >literal! Just didn't want to publish that info. > >Bill Silvert -- 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 Jul 6 12:09:41 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA01187; Wed, 6 Jul 1994 17:50:30 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA01179; Wed, 6 Jul 1994 10:50:16 -0700 Message-Id: <199407061750.KAA01179@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.38.193.5/16.2) id AA23555; Wed, 6 Jul 1994 12:52:17 -0500 From: Larry Sheldon Subject: Re: Suspension? To: paulp@is.internic.net Date: Wed, 6 Jul 94 12:52:16 CDT Cc: majordomo-users@greatcircle.com In-Reply-To: ; from "Paul Phillips" at Jul 1, 94 8:41 pm Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > I like this idea enough that I am going to implement it here. Because of > the way we archive individual messages, it won't be very difficult, but I > know there are at least a couple other ways to archive and I'm not quite up > to providing a general solution. > > I have messages archiving numerically -- i.e., when one goes to the list > it is copied into the archive dir as number 1725 or whatever number it is > up to. When a user issues whatever command we use for this (and I don't > want to use POSTPONE for the sake of less confusion) I will transfer the > name to a different file, say listname.postpone, along with the current > number. When the user issues RESUME, it will be a simple matter to > package up all the posts that have gone out since then and mail them > off. Of course, I will check the total file size and ask the user > whether he wants to receive it. > > Thoughts on this? A better way, perhaps? Sounds pretty good--some kind of an answer besides "your paying customers don't know what they want" is clearly needed. The one piece that you did not mention is that the notion of one notice to the server ought to take care of all lists on that server. > > --- > 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 | > > > On Fri, 1 Jul 1994, Larry Sheldon wrote: > > > And I say : > > I think a really customer-oriented, user-friendly thing would be something like > > what the (gasp, what a role model!) USPS does where you can stop deliveries > > for a period, then get all that was missed. > -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . . - L. F. (Larry) Sheldon, Jr. - . Unix Systems Administration . - Creighton University Computer Center-Old Gym Most of us can do more - . 2500 California Plaza than we think we can, . - Omaha, Nebraska, U.S.A. 68178 but usually less than - . lsheldon@creighton.edu we think we do. . - 402 280-2254 (work) - . 402 977-2946 (pager) "Bits & Pieces" . - 402 332-4622 (residence) - . . .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Thu Jul 7 01:24:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA04949; Wed, 6 Jul 1994 22:34:09 GMT Received: from hub.ucsb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA04913; Wed, 6 Jul 1994 15:33:00 -0700 Received: from dokoka (dokoka.ucsb.edu) by hub.ucsb.edu; id AA04382 sendmail 4.1/UCSB-2.1-sun Wed, 6 Jul 94 15:35:09 PDT for majordomo-users@greatcircle.com Received: from localhost.ucsb.edu by dokoka via SMTP (931110.SGI/920502.SGI.v2) for @hub.ucsb.edu:majordomo-workers@greatcircle.com id AA25715; Wed, 6 Jul 94 15:35:39 -0700 Message-Id: <9407062235.AA25715@dokoka> To: "Majordomo Users" , "Majordomo Workers" Subject: New Perl script: remind Reply-To: Alan Stebbens Date: Wed, 06 Jul 1994 15:35:37 -0700 From: Alan Stebbens Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have found that it is important to "clean house" every so often, and this includes mailing lists. One way is to automatically remind everyone on a mailing list that they are "on" it; this has two functions: * it keeps everyone periodically informed as to which mailing lists they are on, at least from a given list server * it automatically "cleans" the list of dead email addresses, since the bounced email will trigger an "autobounce" (if you've setup the "list-owner" alias correctly). The following is my contribution to majordomo to perform this function. It is designed to be run via "cron" periodically, say once a year. It will collect all of the users in all of Majordomo's mailing lists, and send one message to each user; the mail to each user will contain the particular lists of which the user is a member and an explanatory note with some small instructions. # Run on Jan 2 each year to let all users know which lists they're on 0 3 2 1 * /usr/home/majordomo/remind all The script can also be run manually, if you wish to verify the existence of a particular user: cd ~majordomo remind aks@hub The script has a -v (verbose) option and a -vv (very verbose) option, for those who like to watch things work. Suggestions or comments welcome. Enjoy +-------------------------+-----------------------------------------+ | Alan Stebbens | University of California, Santa Barbara | | Email: aks@hub.ucsb.edu | Center for Computational Sciences | | CCSE: (805) 893-3221 | & Engineering (CCSE) | | Voice: (805) 893-8135 | 3107 Engineering I | | Fax: (805) 893-8121 | Santa Barbara, CA 93106 | +-------------------------+-----------------------------------------+ ============================= cut here =================================== #!/usr/local/bin/perl # remind [-d] [-v[v]] [all | emailaddr ...] # # Remind the named users, or all of them, of which lists they # are participating. # # This script is intended to be run by "cron", say once a year, to # remind users that they are participating in an automated mailing list. # # If a user's email address is no longer valid, the rejected mail should # "auto-bounce" (if setup correctly), and the list should be "cleaner". # # Written by Alan Stebbens , June 1994. # $Source$ # $Revision$ # $Date$ # $Author$ # $State$ # # $Locker: $ # set our path explicitly # PATH it is set in the wrapper, so there is no need to set it here. #$ENV{'PATH'} = "/bin:/usr/bin:/usr/ucb"; # What shall we use for temporary files? $tmp = "/tmp/majordomo.$$"; # Before doing anything else tell the world I am majordomo # The mj_ prefix is reserved for tools that are part of majordomo proper. $main'program_name = 'mj_remind'; # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; while ($ARGV[0]) { # parse for config file or default list if ($ARGV[0] eq "-C") { $cf = $ARGV[1]; shift(@ARGV); } elsif ($ARGV[0] eq 'all') { $all_users++; } elsif ($ARGV[0] eq '-vv') { $verbose += 2; } elsif ($ARGV[0] eq '-v') { $verbose++; } elsif ($ARGV[0] eq '-d') { $debug++; } else { last; } shift(@ARGV); } if (! -r $cf) { die("$cf not readable; stopped"); } eval(`cat $cf`) || die "eval of majordomo.cf failed $@"; # Go to the home directory specified by the .cf file chdir("$homedir"); # All these should be in the standard PERL library unshift(@INC, $homedir); require "ctime.pl"; # To get MoY definitions for month abbrevs require "majordomo_version.pl"; # What version of Majordomo is this? require "majordomo.pl"; # all sorts of general-purpose Majordomo subs require "shlock.pl"; # NNTP-style file locking require "config_parse.pl"; # functions to parse the config files # Here's where the fun begins... $| = 1; # check to see if the cf file is valid die("listdir not defined. Is majordomo.cf being included correctly?") if !defined($listdir); # who do we send the body to if we step on a landmine? &set_abort_addr($whoami_owner); # who do sendmail messages appear to come from, by default? &set_mail_from($whoami); &set_mail_sender($whoami_owner); if (defined($mailer)) { &set_mailer($mailer); } # set our hostname (for use in log messages). $hostname = &chop_nl(`hostname`); # Collect the lists and remember them by user email addresses. sub collect_lists { %Lists = (); print "Scanning lists..\n" if $verbose; # scan through all the lists while (<${listdir}/*>) { s,^.*/,,; # strip off the leading path /[^-_0-9a-zA-Z]/ && next; # skip non-list files (*.info, etc.) $list = $_; print "Scanning list $list..\n" if $verbose > 1 && !$debug; # Get the list configuration for the description &get_config($listdir, $list) if !&cf_ck_bool($list, '', 1); open(LIST, "$listdir/$list") || &abort("Can't open list $listdir/$_"); while () { $_ = &chop_nl($_); ($addr) = &ParseAddrs($_); # get only the address part if (defined($Lists{$addr})) { $Lists{$addr} .= ' '.$list; } else { $Lists{$addr} = $list; } } close(LIST); } } # Remind a user of all the lists they are on. # # &remind_user($email_addr) sub remind_user { local($subscriber) = shift; return if $Done{$subscriber}; $Done{$subscriber}++; print "Reminding $subscriber..\n" if $verbose; unless ($debug) { # Set up the sendmail process to send mail to the list &set_mail_sender($whoami); &sendmail(MSG, $subscriber, "List membership reminder"); &set_mail_sender($whoami_owner); } else { open(MSG,">&STDOUT"); $| = 1; } print MSG <<"EOM"; This message is a reminder that you are subscribed to the mailing lists given below. You do not have to do anything to remain subscribed. EOM @lists = split(' ',$Lists{$subscriber}); foreach $list (@lists) { print "\t$list\n" if $verbose > 1; printf MSG " %-20s %-56s\n", $list, $config_opts{$list, 'description'}; } if ( $majordomo_request ) { print MSG <<"EOM"; If you ever want to remove yourself from any mailing list, send the following command in email to "LIST-request@$whereami" where LIST is the name of the list from which you wish to remove yourself. unsubscribe Or you can send mail to "$whoami" with the following command EOM } else { print MSG <<"EOM"; If you ever want to remove yourself from any mailing list, you can send mail to "$whoami" with the following command EOM } print MSG <<"EOM"; in the body of your email message: unsubscribe LIST $subscriber where LIST is the name of the list from which you wish to be removed. EOM print MSG <<"EOM"; If you wish additional information on participating with mailing lists managed by Majordomo, please send a message containing the command: help to $whoami. EOM # close (and thereby send) the announcement message to the list close(MSG); } $| = 1; # each arg is a user to remind or 'all' @ARGV = keys %Lists if $all_users && !@ARGV; &collect_lists; @users = keys %Lists; while ($user = shift(@ARGV)) { if (grep($user eq $_,@users)) { # check for exact match first &remind_user($user); } elsif ((@subs = grep(/^$user\@/,@users)) || (@subs = grep(/$user/,@users))) { if ($#subs == $[) { # exactly one match &remind_user($subs[0]); # remind him } else { unshift(@ARGV,@subs); # and loop back to do these } } else { print STDERR "No such user to remind: $user\n"; } } print "Done.\n" if $verbose; exit; From majordomo-users-owner Thu Jul 7 08:06:03 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA11786; Thu, 7 Jul 1994 14:12:47 GMT Received: from ruby.ora.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA11779; Thu, 7 Jul 1994 07:12:30 -0700 Received: from rubble.west.ora.com (rubble.west.ora.com [198.112.209.17]) by ruby.ora.com (8.6.8/8.6.4) with SMTP id KAA15527 for ; Thu, 7 Jul 1994 10:15:31 -0400 Received: by rubble.west.ora.com (4.1/SMI-4.1+JP-2.5) id AA04006; Thu, 7 Jul 94 07:15:10 PDT From: Jerry Peek Reply-To: jerry@ora.com X-Mailer: MH 6.8.3 To: mmorse@nsf.gov (Michael H. Morse) Cc: majordomo-users@GreatCircle.COM Subject: Re: Suspension? In-Reply-To: Message from mmorse@nsf.gov (Michael H. Morse) of "Fri, 01 Jul 1994 14:55:38 -0400." <199407011855.OAA23929@z.nsf.gov> Date: Thu, 07 Jul 1994 07:15:09 -0700 Message-Id: <4005.773590509@rubble.west.ora.com> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Mike Morse wrote (a week ago): > > In message <9407011615.AA11522@dokoka>, Alan Stebbens writes: > > >> I think NOMAIL is a totally redundant feature on a list with open > > >> subscription and unsubscription, but I'm about ready to add it in anyway > > >> just to lower the incoming mail volume. > > We should hear from someone who knows LISTSERV about exactly why these > features exist I'm just catching up on my email, but I don't see an answer down there. My best guess is that it's handy for lists that have a long approval process. The case that applies to Majordomo is lists that require approval before a subscription is accepted: a NOMAIL option means that the list owner doesn't have to approve a subscription again before the subscriber can get back on the list. Some LISTSERV setups make you send two or three separate mail messages to join a list. One is a statement that explains your background and interests and why you should be allowed to join the list. Another is a reply to a confirmation that makes sure mail is getting through to you. In cases like these, NOMAIL is a big win. I'm not sure that Majordomo has enough closed lists that a NOMAIL option makes sense for it. But it might, in some cases. --Jerry Peek, jerry@ora.com From majordomo-users-owner Thu Jul 7 09:17:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA13079; Thu, 7 Jul 1994 16:15:35 GMT Received: from lobster.wellfleet.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA11464; Thu, 7 Jul 1994 06:30:54 -0700 Received: from wellfleet.com by lobster.wellfleet.com (4.1/SMI-4.1) id AA08886; Thu, 7 Jul 94 09:31:31 EDT Message-Id: <9407071331.AA08886@lobster.wellfleet.com> Date: 07 Jul 1994 14:32:42 GMT From: PETER_GILIBERTI@wellfleet.com (Peter Giliberti) Organization: Wellfleet Communications Reply-To: PETER_GILIBERTI@wellfleet.com Subject: subscribes To: Majordomo-Users@GreatCircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk My list owners are complaining that users are subscribing to thier lists and the users receive a response that the subscribe has been forwarded to the list owner for approval. The list owners are NOT receiving the approval requests.......any ideas/??? This has just stopped working and I have not reconfigured my install in the past two weeks. Peter Giliberti Sr. Network Engineer Wellfleet Communications From majordomo-users-owner Thu Jul 7 10:26:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA13954; Thu, 7 Jul 1994 17:05:44 GMT Received: from infoexp.express.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA13948; Thu, 7 Jul 1994 10:05:22 -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 KAA20105 for ; Thu, 7 Jul 1994 10:08:21 -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 KAA21693 for ; Thu, 7 Jul 1994 10:08:15 -0700 Message-Id: <199407071708.KAA21693@alto.express.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 7 Jul 1994 10:10:59 -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 have posted this before and didn't get any response. Could someone help me here? Thanks, Philip I have installed majordomo 1.92 as documented. When I tried to test by using the echo help, this is what I got: majordomo... aliased to "|/home/sigweb/majordomo/wrapper majordomo" ld.so: warning: /usr/lib/libc.so.1.8 has older revision than expected 9 majordomo: No such file or directory "|/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 Saving message in /home/sigweb/pzee/dead.letter /home/sigweb/pzee/dead.letter... Sent Does this mean that majordomo 1.92 has conflicts with old version of sendmail? Or what's the problem? Thanks for any help in advance, 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 Jul 7 11:08:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA14994; Thu, 7 Jul 1994 17:59:38 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA14983; Thu, 7 Jul 1994 10:59:24 -0700 Message-Id: <199407071759.KAA14983@mycroft.GreatCircle.COM> To: pzee@express.com (Philip J. Zee) cc: majordomo-users@GreatCircle.COM Subject: Re: Majordomo help In-reply-to: Your message of Thu, 7 Jul 1994 10:10:59 -0800 Date: Thu, 07 Jul 1994 10:59:23 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk pzee@express.com (Philip J. Zee) writes: # I have posted this before and didn't get any response. Could someone help # me here? # # # Thanks, # # Philip # # # # I have installed majordomo 1.92 as documented. When I tried to test by # using the echo help, this is what I got: # # # majordomo... aliased to "|/home/sigweb/majordomo/wrapper majordomo" # ld.so: warning: /usr/lib/libc.so.1.8 has older revision than expected 9 # majordomo: No such file or directory # "|/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 # Saving message in /home/sigweb/pzee/dead.letter # /home/sigweb/pzee/dead.letter... Sent # # # Does this mean that majordomo 1.92 has conflicts with old version of # sendmail? Or what's the problem? I'm pretty sure this is in the FAQ. "unknown mailer error 5" means that "wrapper" exited with a status of 5. If you look at wrapper.c, it does an "exit(5)" when it failes to run the program it's been told to run ("majordomo" in this case). This means that either: 1) The "majordomo" script isn't in the directory (W_BIN in the Makefile) where "wrapper" expects to find it. 2) The "majordomo" script is there, but isn't executable. 3) The script is there and executable, but the perl interpreter isn't where the script expects it to be (/usr/local/bin/perl). If perl is installed somewhere other than /usr/local/bin/perl on your system, you need to change the "#!/usr/local/bin/perl" on the first line of all the scripts in the Majordomo package to reflect where perl really is. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Thu Jul 7 11:32:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA15409; Thu, 7 Jul 1994 18:26:03 GMT Received: from fml.co.uk by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA15401; Thu, 7 Jul 1994 11:25:51 -0700 Date: Thu, 7 Jul 94 18:55:07 BST From: a.beckett@fml.co.uk (Andrew Beckett) Message-Id: <9407071755.AA15404@fml.co.uk> To: pzee@express.com Subject: Re: Majordomo help Cc: majordomo-users@GreatCircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > I have installed majordomo 1.92 as documented. When I tried to test by > using the echo help, this is what I got: > > > majordomo... aliased to "|/home/sigweb/majordomo/wrapper majordomo" > ld.so: warning: /usr/lib/libc.so.1.8 has older revision than expected 9 > majordomo: No such file or directory > "|/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 > Saving message in /home/sigweb/pzee/dead.letter > /home/sigweb/pzee/dead.letter... Sent > > > Does this mean that majordomo 1.92 has conflicts with old version of > sendmail? Or what's the problem? > > Thanks for any help in advance, > > Philip > I suspect that you have not set the variable W_BIN in the Makefile correctly when you built wrapper. Is the directory W_BIN mounted on the machine that majordomo will run on? If you type: /home/sigweb/majordomo/wrapper rubbish it will come up with: rubbish: No such file or directory because rubbish is not in W_BIN. Similarly if majordomo is not in W_BIN, you'll get the same message. I doubt very much whether it's anything to do with the versions of libraries. Hope this helps, Andrew. ******************************************************************* * Andrew Beckett * * * Senior Design Engineer * * * Fujitsu Microelectronics Ltd * * * Highway House * phone : (0628) 71116 * * Norreys Drive * fax : (0628) 773990 * * Maidenhead. Berks SL6 4BW * email : a.beckett@fml.co.uk * ******************************************************************* From majordomo-users-owner Thu Jul 7 12:28:16 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA15787; Thu, 7 Jul 1994 18:42:15 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA15779; Thu, 7 Jul 1994 11:42:00 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qLxy6-00014wC; Thu, 7 Jul 94 11:14 PDT Message-Id: To: pzee@express.com (Philip J. Zee) cc: majordomo-users@greatcircle.com Subject: Re: Majordomo help In-reply-to: Your message of Thu, 07 Jul 1994 10:10:59 -0800. <199407071708.KAA21693@alto.express.com> Date: Thu, 07 Jul 1994 11:14:37 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I have installed majordomo 1.92 as documented. When I tried to test by > using the echo help, this is what I got: > > > majordomo... aliased to "|/home/sigweb/majordomo/wrapper majordomo" > ld.so: warning: /usr/lib/libc.so.1.8 has older revision than expected 9 > majordomo: No such file or directory > "|/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 > Saving message in /home/sigweb/pzee/dead.letter > /home/sigweb/pzee/dead.letter... Sent > > > Does this mean that majordomo 1.92 has conflicts with old version of > sendmail? Or what's the problem? There are two messaages reported here: 1) > ld.so: warning: /usr/lib/libc.so.1.8 has older revision than expected 9 No biggie. Your program was built on a system with the 1.9 version of the C library, but is runnnig on one with 1.8. This is probably not a problem. 2) > majordomo: No such file or directory This is the REAL problem. Either: - majordomo is not in the directory you told wrapper it would be in - perl is not at the location the majordomo script expects it --- 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 Thu Jul 7 12:37:59 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA15327; Thu, 7 Jul 1994 18:19:19 GMT Received: from antares.mcs.anl.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA15319; Thu, 7 Jul 1994 11:19:00 -0700 Received: from mcs.anl.gov (skeeve.mcs.anl.gov [140.221.5.130]) by antares.mcs.anl.gov (8.6.4/8.6.4) with ESMTP id MAA25132; Thu, 7 Jul 1994 12:55:41 -0500 Message-Id: <199407071755.MAA25132@antares.mcs.anl.gov> To: pzee@express.com (Philip J. Zee) cc: majordomo-users@GreatCircle.COM, rackow@antares.mcs.anl.gov Subject: Re: Majordomo help In-reply-to: Your message of "Thu, 07 Jul 1994 10:10:59 -0800." <199407071708.KAA21693@alto.express.com> Date: Thu, 07 Jul 1994 12:55:39 -0500 From: Gene Rackow Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk At this point, it is not a majordomo filure, but something that majordomo uses. You either compiled sendmail or perl on a sun running 4.1.3u1b and are attempting to run it on a 4.1.3 machine. Can't tell which without looking at them Try running each by hand and see what fails. --gene Philip J. Zee writes: >I have posted this before and didn't get any response. Could someone help >me here? > > >Thanks, > >Philip > > > >I have installed majordomo 1.92 as documented. When I tried to test by >using the echo help, this is what I got: > > >majordomo... aliased to "|/home/sigweb/majordomo/wrapper majordomo" >ld.so: warning: /usr/lib/libc.so.1.8 has older revision than expected 9 >majordomo: No such file or directory >"|/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 >Saving message in /home/sigweb/pzee/dead.letter >/home/sigweb/pzee/dead.letter... Sent > > >Does this mean that majordomo 1.92 has conflicts with old version of >sendmail? Or what's the problem? > >Thanks for any help in advance, > >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 Fri Jul 8 00:31:48 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA21785; Fri, 8 Jul 1994 00:31:48 GMT Received: from ruby.ora.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA21778; Thu, 7 Jul 1994 17:31:30 -0700 Received: from rubble.west.ora.com (rubble.west.ora.com [198.112.209.17]) by ruby.ora.com (8.6.8/8.6.4) with SMTP id UAA18091 for ; Thu, 7 Jul 1994 20:33:48 -0400 Received: by rubble.west.ora.com (4.1/SMI-4.1+JP-2.5) id AA06324; Thu, 7 Jul 94 17:33:31 PDT From: Jerry Peek Reply-To: jerry@ora.com X-Mailer: MH 6.8.3 To: majordomo-users@GreatCircle.COM Subject: Re: Lost subscribers list In-Reply-To: Message from colin sebastian roald of "Tue, 05 Jul 1994 19:20:48 -0400." <199407052320.TAA29204@callisto.pas.rochester.edu> Date: Thu, 07 Jul 1994 17:33:30 -0700 Message-Id: <6323.773627610@rubble.west.ora.com> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > I now make a copy my member file on a daily basis. > > better yet, stick > > 0 6 * * * /bin/cp /usr/ath/mjd/lists/psi /usr/ath/mjd/lists/psi.sv > > in cron. Well, you'd better hope that the file isn't empty when that cron job runs. :-/ I use RCS instead and run "ci -l" from a little script in my "majordom" crontab. If there are changes, it checks the new file into RCS. The nice thing about this, besides being able to get back the subscriber list, is that I can get *any* subscriber list. Say I want to count the number of list members who've been on for more than a year, or I realize that the subscribers file was zeroed three days ago but I hadn't noticed until now, or whatever: the RCS backups are nice to have. They don't take much room, either, because RCS just stores the differences between versions. -- Jerry Peek; O'Reilly & Associates; Sebastopol, CA 95472 USA; jerry@ora.com Info: gopher gopher.ora.com (or telnet, and login: gopher), or info@ora.com Orders: (800)998-9938, +1 707-829-0515, fax +1 707-829-0104, or order@ora.com From majordomo-users-owner Thu Jul 7 18:18:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA22054; Fri, 8 Jul 1994 00:54:45 GMT Received: from genome.lbl.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA22048; Thu, 7 Jul 1994 17:54:25 -0700 Received: from gener8.lbl.gov.hgc by genome.lbl.gov (4.1/1.39) id AA06132; Thu, 7 Jul 94 17:54:28 PDT From: jtran@genome.lbl.gov (John Tran) Message-Id: <9407080054.AA06132@genome.lbl.gov> Subject: installation quirk To: majordomo-users@greatcircle.com Date: Thu, 7 Jul 1994 17:57:05 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1630 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I am hoping that someone can help me with this problem that I have been experiencing while installing majordomo-1.92. In my $homedir/LISTDIR directory, I have several mailing lists. However, the problem seems to be that majordomo only recognizes two mailing lists. I have exhausted the configuration possibilities. In other words, during the testing phase: I created two identical mailing lists (different names, of course; however, majordomo replies "list_a> does not exist" to the "info", "who", and "subscribe" commands are issued when infact the "lists" command proves that exists. Also I obeserved that there are several types of the wrapper program (one with root as the owner, another one with daemon as the owner, and finally one with root as the owner) -- John Tran (510) 486-6717 email:john.tran@nd.edu First here is my /etc/aliases: # --------------------------------------------------------------------------- # sigweb # --------------------------------------------------------------------------- sigweb-owner: jtran sigweb-approval: sigweb-owner owner-sigweb-request: sigweb-owner owner-sigweb-outgoing: sigweb-owner owner-sigweb-archive: sigweb-owner sigweb: "|/home/hgc/data8/users/majordomo/majordomo-1.92/wrapper resend -p bulk-M 10000 -R -l sigweb -f sigweb-owner -h genome.lbl.hov -s sigweb-outgoing" sigweb-outgoing: :include:/home/hgc/data8/users/majordomo/LISTDIR/sigweb, sigwe-archive sigweb-archive: /home/hgc/data8/users/majordomo/LISTDIR/sigweb.archive sigweb-request: "|/home/hgc/data8/users/majordomo/majordomo-1.92/wrapper reques-answer sigweb" From majordomo-users-owner Fri Jul 8 08:44:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA04218; Fri, 8 Jul 1994 08:44:29 GMT Received: from relay.cv.ruu.nl by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id BAA04207; Fri, 8 Jul 1994 01:44:13 -0700 Received: from koninck.radth.ruu.nl by relay.cv.ruu.nl with SMTP id AA12233 (5.67b/IDA-1.5 for ); Fri, 8 Jul 1994 10:44:32 +0200 Received: by koninck.radth.ruu.nl id AA13894 (5.67b/IDA-1.4.4 for majordomo-users@greatcircle.com); Fri, 8 Jul 1994 10:46:34 +0200 From: Ric Exterkate Message-Id: <199407080846.AA13894@koninck.radth.ruu.nl> Subject: Messages delivered twice; time differences To: majordomo-users@greatcircle.com Date: Fri, 8 Jul 1994 10:46:34 +0100 (MDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 2978 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We have installed Majordomo at our site, and after a glorious start, we now have some trouble: every member of the list receives two copies of a message, sent by the list. In the sendmail log, it appears that resend is only called once, but for every message, archive is called twice, and the usernames also appear twice in the log: Jul 6 19:19:24 koninck sendmail[29636]: AA29636: to="|/home/majordomo/bin/wrapper resend -l hyperthermia -h radth.ruu.nl -f hyperthermia-owner -M 10000 -p bulk -r hyperthermia -R -s hyperthermia-outgoing", delay=00:00:10, stat=Sent, mailer=prog, relay=koninck.radth.ruu.nl Jul 6 17:19:24 koninck sendmail[29643]: AA29641: to="|/home/majordomo/bin/wrapper archive -f /home/majordomo/archive/hyperthermia/hyperth -m -a", delay=00:00:07, stat=Sent, mailer=prog, relay=koninck.radth.ruu.nl Jul 6 17:21:55 koninck sendmail[29643]: AA29641: to=Fred , Gene ,etc, etc, (cont'd), delay=00:02:38, stat=Sent, mailer=TCP, relay=prisma.cv.ruu.nl ------lines deleted------------ Jul 6 19:33:41 koninck sendmail[29654]: AA29641: to="|/home/majordomo/bin/wrapper archive -f /home/majordomo/archive/hyperthermia/hyperth -m -a", delay=00:14:24, stat=Sent, mailer=prog, relay=koninck.radth.ruu.nl Jul 6 19:33:55 koninck sendmail[29654]: AA29641:to=Fred , Gene ,etc, etc, (cont'd), delay=00:02:38, stat=Sent, mailer=TCP, relay=prisma.cv.ruu.nl Just after the first process of delivering the messages, I took a look at the mail queue. It show the following message: Mail Queue (1 request) --QID-- --Size-- -----Q-Time----- ------------Sender/Recipient------------ AA07113* 426 Thu Jul 7 15:48 hyperthermia-owner (User unknown) (daemon) "|/home/majordomo/bin/wrapper archiv firstName secondName Name2 Name3 etc. The layout of the majordomo list is the following: LastName, firstName secondName LastName, firstName etc. firstName LastName Who can help me with this problem, I cannot figure it out. I run a test list also at our site, and I don't have any trouble at all in this list. Thanks in advance, Ric P.S. NOTE, the time jumps, from 19:19:24 to 17:19:24 to 19:33:41 is not a mistake from me, but directly taken from the logfile. I've solved this problem by changing the wrapper: only USER and LOGNAME were put in the new environment, I've added TZ as well. After this change, the time jump had dissapeared. -- Ric Exterkate, Department of Radiotherapy, University Hospital Utrecht, Heidelberglaan 100, 3584 CX Utrecht, The Netherlands E-mail:R.Exterkate@radth.ruu.nl Phone:+31-30-508284 Fax:+31-30-513399 From majordomo-users-owner Fri Jul 8 10:48:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA05208; Fri, 8 Jul 1994 10:48:38 GMT Received: from garm.adm.ku.dk by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id DAA05202; Fri, 8 Jul 1994 03:48:28 -0700 Received: from odont.ku.dk (server1.odont.ku.dk [130.225.107.2]) by garm.adm.ku.dk (8.6.8.1/8.6) with SMTP id MAA29095 for ; Fri, 8 Jul 1994 12:51:29 +0200 Received: from TS/MERCURY by odont.ku.dk (Mercury 1.12); Fri, 8 Jul 94 12:51:45 +100 Received: from MERCURY by TS (Mercury 1.12); Fri, 8 Jul 94 12:51:33 +100 From: "Anders Nattestad" Organization: Dental School, Univ. of Copenhagen To: majordomo-users@greatcircle.com Date: Fri, 8 Jul 1994 12:51:23 GMT+100 Subject: Newbie question: How to enable aliases Priority: normal X-mailer: Pegasus Mail v3.1 (R1a) Message-ID: <5B59434443@odont.ku.dk> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello all, Sorry to bother the list with this kind of question, but I have tried allmost everthing else. I have compiled and installed majordomo 1.92 on a Linux and everything seems to be in place. I have placed the aliases in /etc/aliases as suggested. However the user majordomo is unknown to the system when mailing. So I tried to insert a dummy user with mail forwarding in the aliases file : dummy: root. This should make mail to dummy go to root instead. The user dummy is unkonown. The problem is with smail (Linux derivative of sendmail), which apparently does not read the aliases file. I looked in the smail documentation and found somewhere a config command : -oA alias-file, which I inserted into the smail configuration file. This had the effect that no mail at all comes through, not even to regular users. The -oA command must mess up the config of smail. But how then do I tell smail to use the /etc/aliases file ??? I have looked in all the possible faq and how-to's without luck. Hope someone can help. Anders. ------------------------------------------------------------------- Anders Nattestad, DDS, Ph.D, Dep. of Oral and Maxillofacial Surgery and Chairman of Computer Network and Multimedia Division. Dental School, Faculty of Health Science, University of Copenhagen Norre Alle 20, Copenhagen, Denmark, Ph.+4535326618, Fax +4535326625 From majordomo-users-owner Fri Jul 8 08:17:57 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA08735; Fri, 8 Jul 1994 15:11:49 GMT Received: from sparc by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA08728; Fri, 8 Jul 1994 08:11:23 -0700 Received: by sparc (5.0/SMI-SVR4) id AA26718; Fri, 8 Jul 1994 12:12:23 +0400 Date: Fri, 8 Jul 1994 12:12:22 -0300 (ADT) From: Steve MacLeod Subject: Returned mail: Can't create output (fwd) To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 1522 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Would anyone know the rights needed for the archive files? I currently have rwxrwxr.x on the /mail and /mail/archive directories the files are also 664 (rw.rw.r..) The paths are right ... my /etc/aliases entry ... .......................................................... # Majordomo # majordomo: "|/usr/local/majordomo/wrapper majordomo" majordomo-owner: mj-support owner-majordomo: mj-support owner-owner: mj-support majordom: mj-support listserv: majordomo # # Sample mailing list # sample: "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l sample -f Sample-Owner -h sparc.uccb.ns.ca -s sample-outgoing" owner-sample: sample-owner sample-outgoing: :include:/usr/local/mail/lists/sample, sample-archive owner-sample-outgoing: sample-owner sample-archive: /usr/local/mail/archive/sample owner-sample-archive: sample-owner sample-request: "|/usr/local/majordomo/wrapper request-answer sample" owner-sample-request: sample-owner sample-approval: smacleod sample-owner: smacleod owner-sample-owner: smacleod ................................................................. The error I get is : ................................................................. To: Postmaster@sparc Subject: Returned mail: Can't create output ----- Transcript of session follows ----- 550 /usr/local/mail/archive/sample... Can't create output ................................................................. I am running on SUN Sparc 10-40 / Solaris 2.3 Perl 4.036 Majordomo 1.92 Any ideas ? Thanks From majordomo-users-owner Fri Jul 8 16:03:35 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA09447; Fri, 8 Jul 1994 16:03:35 GMT Received: from umassmed.UMMED.EDU by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA09440; Fri, 8 Jul 1994 09:03:20 -0700 Received: from papaya.UMMED.EDU by umassmed.UMMED.EDU (5.61/HCX-2.2) (for @greatcircle.com.:majordomo-users@GreatCircle.COM ) id AA01575; Fri, 8 Jul 94 12:06:16 -0400 Received: (from naleks@localhost) by papaya.ummed.edu (8.6.8.1/8.6.6) id NAA08033; Fri, 8 Jul 1994 13:02:35 -0400 Date: Fri, 8 Jul 1994 13:02:35 +0100 From: Norm Aleks Subject: Re: Messages delivered twice; time differences To: Ric Exterkate Cc: majordomo-users@GreatCircle.COM In-Reply-To: <199407080846.AA13894@koninck.radth.ruu.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Fri, 8 Jul 1994, Ric Exterkate wrote: > We have installed Majordomo at our site, and after a glorious start, we now have > some trouble: every member of the list receives two copies of a message, sent by the I would be *very* interested in hearing what solution you come to ... I'm having a problem that sounds sort of similar. However, it doesn't happen all the time, just occasionally ... Could you forward me copies of anything really interesting, or forward them to the list? Thanks. Norm -- Norm Aleks - naleks@papaya.ummed.edu - UMASS Medical Center, Worcester, Mass. "For a generation, the most important gay march has been a long line of men and women coming out, one at a time." --Ellen Goodman From majordomo-users-owner Fri Jul 8 17:52:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA11469; Fri, 8 Jul 1994 17:52:27 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA11462; Fri, 8 Jul 1994 10:52:19 -0700 Received: from xt.cs.umb.edu by cs.umb.edu with SMTP id AA18623 (5.65c/IDA-1.4.4 for ); Fri, 8 Jul 1994 13:55:12 -0400 Message-Id: <199407081755.AA18623@cs.umb.edu> To: Steve MacLeod Cc: majordomo-users@greatcircle.com Subject: Re: Returned mail: Can't create output (fwd) In-Reply-To: Your message of "Fri, 08 Jul 1994 12:12:22 -0300." Date: Fri, 08 Jul 1994 13:55:11 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Steve MacLeod writes: > >Would anyone know the rights needed for the archive files? > >I currently have rwxrwxr.x on the /mail and /mail/archive directories > >the files are also 664 (rw.rw.r..) The way you have your alias for archiving set up, the archive files must be mode 666 to work reliably. >sample-archive: /usr/local/mail/archive/sample Set up sample-archive as in the examples in the READMe, using the wrapper and an archive program, and you can get by with mode 664, with the owner of the file, and group of the file being the effective owner and group set by the wrapper. -- 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 Jul 8 21:20:00 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA14508; Fri, 8 Jul 1994 21:20:00 GMT Received: from callisto.pas.rochester.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA14502; Fri, 8 Jul 1994 14:19:50 -0700 Received: (from colin@localhost) by callisto.pas.rochester.edu (8.6.9/8.6.9) id RAA09558 for majordomo-users@greatcircle.com; Fri, 8 Jul 1994 17:23:10 -0400 Date: Fri, 8 Jul 1994 17:23:10 -0400 From: colin sebastian roald Message-Id: <199407082123.RAA09558@callisto.pas.rochester.edu> To: majordomo-users@greatcircle.com Subject: resend header bug Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk a few weeks ago i described a bug where resend would sometimes take the first few lines of a message and stick them in the headers. this is particularly troublesome when someone has left a From: line at the top to indicate who is being quoted in the message (the From: gets moved into the headers, resulting in a message claiming to be from two different people, and worse, elm seems to read only the *second*, incorrect, entry. anyhow, i think i've found a pattern: this bug seems to strike any lines at the top of the message that contain colons. does that help anyone to track it down? -- colin | he opened up his mind and snapped out of the groove / he saw both roald | sides of everything and found he could not move. (james mcmurtry) From majordomo-users-owner Fri Jul 8 21:40:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA14726; Fri, 8 Jul 1994 21:40:54 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA14720; Fri, 8 Jul 1994 14:40:41 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA01687 (5.65c/IDA-1.4.4 for ); Fri, 8 Jul 1994 17:43:43 -0400 Message-Id: <199407082143.AA01687@cs.umb.edu> To: colin sebastian roald Cc: majordomo-users@greatcircle.com Subject: Re: resend header bug In-Reply-To: Your message of "Fri, 08 Jul 1994 17:23:10 EDT." <199407082123.RAA09558@callisto.pas.rochester.edu> Date: Fri, 08 Jul 1994 17:43:42 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199407082123.RAA09558@callisto.pas.rochester.edu>, colin sebastian roald writes: >a few weeks ago i described a bug where resend would sometimes take the >first few lines of a message and stick them in the headers. this is >particularly troublesome when someone has left a From: line at the >top to indicate who is being quoted in the message (the From: gets moved >into the headers, resulting in a message claiming to be from two different >people, and worse, elm seems to read only the *second*, incorrect, entry. I haven't been able to reproduce it on my test lists which means one of two things: 1) the 1.93 prototype code I am running doesn't suffer from it 2) the test case I got isn't sufficient for some reason >anyhow, i think i've found a pattern: this bug seems to strike any lines >at the top of the message that contain colons. does that help anyone to >track it down? My guess is that it would be in the code that handles the approved header in the body of the message, but I am not sure. I tried running the test case by hand through the 1.92 resend with no luck. If anybody else tracks it down, I would appreciate looking at the patch so I can make sure that it is really fixed and not merely masked in the 1.93 resend. -- 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 Jul 8 22:21:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA15275; Fri, 8 Jul 1994 22:21:55 GMT Received: from merlot.arc.nasa.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA15269; Fri, 8 Jul 1994 15:21:39 -0700 Received: from localhost.arc.nasa.gov by merlot.arc.nasa.gov (8.6.8/1.35) id PAA23671; Fri, 8 Jul 1994 15:26:11 -0700 Message-Id: <199407082226.PAA23671@merlot.arc.nasa.gov> To: "John P. Rouillard" cc: colin sebastian roald , majordomo-users@greatcircle.com Subject: Re: resend header bug In-reply-to: Your message of "Fri, 08 Jul 1994 17:43:42 EDT." <199407082143.AA01687@cs.umb.edu> Date: Fri, 08 Jul 1994 15:25:58 -0700 From: Alex Deacon - NAIC Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Collin, (and John) > My guess is that it would be in the code that handles the approved > header in the body of the message, but I am not sure. I tried running > the test case by hand through the 1.92 resend with no luck. If anybody > else tracks it down, I would appreciate looking at the patch so I can > make sure that it is really fixed and not merely masked in the 1.93 > resend. I *think* I patched a simillar problem I was having a couple of weeks ago. When an owner of a moderated list posted to the list with the Approved: command in the BODY of the message, header information (such as bulk, sender) was getting mixed in with the text of the message. This header info was being inserted after the first (or second, I dont remember) line of the message. And for some reason the subject line got blown away in the process also. This behaviour did not occur when the listowner placed the Approved: command in the header of the message. I came up with the following patch (for 1.92), its a hack, and hasn't been fully tested but it seems to be working well. Basically the header information looked like it was being rewritten when a valid Approved line was detected, however if this Approved: line is in the body of the message then there is no need to print the header info again. Comments? *** resend.dist Fri Jun 17 08:55:59 1994 --- resend Fri Jun 24 13:50:57 1994 *************** *** 153,159 **** } } if ($in_hdr) { ! if (/^\s*$/) { # end of header; add new header fields print OUT "Sender: $sender\n"; if (defined($opt_p)) { --- 153,160 ---- } } if ($in_hdr) { ! # if (/^\s*$/) { ####Original code (awdeacon) ! if (/^\s*$/ && ! $again) { # added to fix Approved: bug # end of header; add new header fields print OUT "Sender: $sender\n"; if (defined($opt_p)) { *************** *** 256,265 **** # Yes, it's a valid "Approved:" line... # So, we start over $restart = 1; ! close(OUT); ! unlink("/tmp/resend.$$.out"); ! open(OUT, ">/tmp/resend.$$.out") || ! die("resend: Can't open /tmp/resend.$$.out: $!"); last; } } --- 257,267 ---- # Yes, it's a valid "Approved:" line... # So, we start over $restart = 1; ! $again = 1; # part of fix by awdeacon ! #close(OUT); ! #unlink("/tmp/resend.$$.out"); ! #open(OUT, ">/tmp/resend.$$.out") || ! # die("resend: Can't open /tmp/resend.$$.out: $!"); last; } } From majordomo-users-owner Sat Jul 9 00:21:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA16826; Sat, 9 Jul 1994 00:21:58 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA16820; Fri, 8 Jul 1994 17:21:45 -0700 Message-Id: <199407090021.RAA16820@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.38.193.5/16.2) id AA27308; Fri, 8 Jul 1994 19:22:28 -0500 From: Larry Sheldon Subject: Re: resend header bug To: awdeacon@merlot.arc.nasa.gov (Alex Deacon - NAIC) Date: Fri, 8 Jul 94 19:22:27 CDT Cc: rouilj@cs.umb.edu, colin@callisto.pas.rochester.edu, majordomo-users@GreatCircle.COM In-Reply-To: <199407082226.PAA23671@merlot.arc.nasa.gov>; from "Alex Deacon - NAIC" at Jul 08, 94 3:25 pm Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Collin, (and John)(and Alex) > > > My guess is that it would be in the code that handles the approved > > header in the body of the message, but I am not sure. I tried running > > the test case by hand through the 1.92 resend with no luck. If anybody > > else tracks it down, I would appreciate looking at the patch so I can > > make sure that it is really fixed and not merely masked in the 1.93 > > resend. > > I *think* I patched a simillar problem I was having a couple of weeks > ago. When an owner of a moderated list posted to the list with the > Approved: command in the BODY of the message, header information (such > as bulk, sender) was getting mixed in with the text of the message. > This header info was being inserted after the first (or second, I dont > remember) line of the message. And for some reason the subject line > got blown away in the process also. > > This behaviour did not occur when the listowner placed the Approved: > command in the header of the message. > > I came up with the following patch (for 1.92), its a hack, and hasn't > been fully tested but it seems to be working well. Basically the > header information looked like it was being rewritten when a valid > Approved line was detected, however if this Approved: line is in the > body of the message then there is no need to print the header info > again. > > Comments? > [patch set out] This sounds like the problem (and the area of code I was looking at) about a year ago when we first brought up majordomo here--I gave up trying to put the "Approved" stuff in the body for just the reasons given above. I was (and am) too poorly trained to attempt very much perl code--and Brent was up to his ears it appeared, and I had to get something going--we finally got the approve program and process to run, but it seems like I had to make some mods to the code that handles "Approved" anywhere run, when I got the header version running I lost interest in the task. But I remember thinking that the "Approved-in-the-body" code looked like a kludge that probably worked at most at one site with some really site- local conditions. And as I recall, I decided the reason I was too frightened to proceed was that the code--having found "Approved:" somewhere, assummed that it had found it in the headers. I'm not sure if I have added anything here, but for what ever it is worth, the description above sounds really familiar. Oh, and it seems like I determined that the problem is exacerbated if you "forward" a piece to the list without deleting the MA-inserted blank line beore the text--the code (it seems like) keyed on the blank line as "eoh", even if it had already _found_ the end of the headers. -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . . - L. F. (Larry) Sheldon, Jr. - . Unix Systems Administration . - Creighton University Computer Center-Old Gym Most of us can do more - . 2500 California Plaza than we think we can, . - Omaha, Nebraska, U.S.A. 68178 but usually less than - . lsheldon@creighton.edu we think we do. . - 402 280-2254 (work) - . 402 977-2946 (pager) "Bits & Pieces" . - 402 332-4622 (residence) - . . .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Sat Jul 9 00:31:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA17007; Sat, 9 Jul 1994 00:31:45 GMT Received: from callisto.pas.rochester.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA16997; Fri, 8 Jul 1994 17:31:35 -0700 Received: (from colin@localhost) by callisto.pas.rochester.edu (8.6.9/8.6.9) id UAA09923; Fri, 8 Jul 1994 20:33:32 -0400 Date: Fri, 8 Jul 1994 20:33:32 -0400 From: colin sebastian roald Message-Id: <199407090033.UAA09923@callisto.pas.rochester.edu> To: lsheldon@bluejay.creighton.edu Subject: Re: resend header bug Cc: awdeacon@merlot.arc.nasa.gov, rouilj@cs.umb.edu, majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > I *think* I patched a simillar problem I was having a couple of weeks > > ago. When an owner of a moderated list posted to the list with the > > Approved: command in the BODY of the message, header information (such > > as bulk, sender) was getting mixed in with the text of the message. fwiw, i'm not running a moderated list, and i'm not using Approved: headers. i'm also not competent to decipher the perl, so i don't know if that matters. -- colin | he opened up his mind and snapped out of the groove / he saw both roald | sides of everything and found he could not move. (james mcmurtry) From majordomo-users-owner Sat Jul 9 03:50:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA20676; Sat, 9 Jul 1994 10:17:19 GMT Received: from zoom.bga.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id DAA20670; Sat, 9 Jul 1994 03:17:07 -0700 Received: (from fmouse@localhost) by zoom.bga.com (8.6.9/8.6.9) id FAA28984 for majordomo-users@greatcircle.com; Sat, 9 Jul 1994 05:20:13 -0500 From: Lindsay Haisley Message-Id: <199407091020.FAA28984@zoom.bga.com> Subject: Approve switches ???? To: majordomo-users@greatcircle.com Date: Sat, 9 Jul 1994 05:20:13 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 976 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm attemptint to set up moderated lists for use by some of our local list managers. According to the man page on approve (which came with md 1.92) I need to set up a .majordomo file with the appropriate information (which I've done) and use the syntax 'approve message_name' where message_name is the name of the file to which a BOUNCE message has been saved. Approve returns the following: You must specify direct recipients with -s, -c, or -b. What gives here? This may be an RTFM issue, but the man page makes no mention of switches for approve. Can someone give me some help with this ASAP? I've got folks breathing down the back of my neck to get their lists set up and configured. ----------------------------------------------- Lindsay Haisley |"On the Internet, no one knows you're a dog" | fmouse@bga.com | --- The New Yorker Magazine | Austin, Texas, USA ----------------------------------------------- * * * * * * * From majordomo-users-owner Sat Jul 9 16:53:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA22966; Sat, 9 Jul 1994 16:53:31 GMT Received: from zoom.bga.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA22960; Sat, 9 Jul 1994 09:53:15 -0700 Received: (from fmouse@localhost) by zoom.bga.com (8.6.9/8.6.9) id LAA06198 for majordomo-users@greatcircle.com; Sat, 9 Jul 1994 11:56:00 -0500 From: Lindsay Haisley Message-Id: <199407091656.LAA06198@zoom.bga.com> Subject: Re: Approve switches ???? To: rouilj@cs.umb.edu (John P. Rouillard) Date: Sat, 9 Jul 1994 11:54:40 -0500 (CDT) In-Reply-To: <199407091504.AA20018@cs.umb.edu> from "John P. Rouillard" at Jul 9, 94 11:04:11 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1660 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Actually after looking into it it appears that the error is coming out of mail which is invoked by approve. The situation is an odd one. approve is invoking mail with a command line of the form [stdout] | mail -s "" recipient Mail is barfing on the null subject string. If I rewrite the invocation so that it goes like.... [stdout] | mail -s " " recipient Then everything appears to work properly. Our system is BSDI Unix 1.1. The mail program is a rather old one which advirtises itself as Mail version 5.5 6/1/90. I'm not sure if an update is available or if it is if it would fix the problem. Thus spoke John P. Rouillard ... > Check your path. I think you are using the wrong approve. > > In message <199407091020.FAA28984@zoom.bga.com>, > Lindsay Haisley writes: > > >I'm attemptint to set up moderated lists for use by some of our local list > >managers. According to the man page on approve (which came with md 1.92) I > >need to set up a .majordomo file with the appropriate information (which > >I've done) and use the syntax 'approve message_name' where message_name is > >the name of the file to which a BOUNCE message has been saved. Approve > >returns the following: > > > >You must specify direct recipients with -s, -c, or -b. > > > >What gives here? This may be an RTFM issue, but the man page makes no > >mention of switches for approve. > > ----------------------------------------------- Lindsay Haisley |"On the Internet, no one knows you're a dog" | fmouse@bga.com | --- The New Yorker Magazine | Austin, Texas, USA ----------------------------------------------- * * * * * * * From majordomo-users-owner Sun Jul 10 01:42:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id BAA26356; Sun, 10 Jul 1994 01:42:45 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA26350; Sat, 9 Jul 1994 18:42:37 -0700 Received: from bolis by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA16865; Sat, 9 Jul 94 18:45:29 -0700 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0qMnXC-0002ZOC; Sat, 9 Jul 94 18:18 PDT Message-Id: From: Alan Millar Subject: Re: Newbie question: How to enable aliases To: an@odont.ku.dk (Anders Nattestad) Date: Sat, 9 Jul 1994 18:18:20 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <5B59434443@odont.ku.dk> from "Anders Nattestad" at Jul 8, 94 12:51:23 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: 1561 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Anders Nattestad spake of these matters: > > Hello all, > > Sorry to bother the list with this kind of question, but I have tried > allmost everthing else. > > I have compiled and installed majordomo 1.92 on a Linux and > everything seems to be in place. I have placed the aliases in > /etc/aliases as suggested. However the user majordomo is unknown to > the system when mailing. So I tried to insert a dummy user with mail > forwarding in the aliases file : dummy: root. This should make mail > to dummy go to root instead. The user dummy is unkonown. > > The problem is with smail (Linux derivative of sendmail), which > apparently does not read the aliases file. I looked in the smail > documentation and found somewhere a config command : -oA alias-file, > which I inserted into the smail configuration file. This had the > effect that no mail at all comes through, not even to regular users. > The -oA command must mess up the config of smail. But how then do I > tell smail to use the /etc/aliases file ??? > > I have looked in all the possible faq and how-to's without luck. The quick answer: the file is /usr/lib/aliases It's not in the /etc directory. (The long answer: RTFM. The SMail docs come in the doc disk sets of all the Linux distributions I've seen. If you can't find it, look on ftp.uu.net for the full SMail package.) - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: ftp://ftp.netcom.com/pub/amillar/welcome.html What part of "NO" don't you understand? From majordomo-users-owner Sun Jul 10 04:37:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id EAA27577; Sun, 10 Jul 1994 04:37:55 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA27571; Sat, 9 Jul 1994 21:37:47 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id XAA01120; Sat, 9 Jul 1994 23:49:48 -0500 Date: Sat, 9 Jul 1994 23:49:46 +0100 From: "Robert A. Hayden" Subject: Weird bounce To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm not sure how to inturrpret this bounce. I recently switched from smail to (I hope) sendmail and in testing out my majordomo lists, I got the following error: ----- 550 -R... User unknown 451 aa733@cleveland.Freenet.Edu... reply: read error from po.cwru.edu. aa733@cleveland.Freenet.Edu... Deferred: Connection reset by peer during client greeting with po.cwru.edu. 22447GBL@msu.edu,22626MGR@msu.edu... Deferred: Connection refused by msu.edu. ----- Now, I'm not sure where the -R is coming from and who it is that is unknown. ANyone have any ideas? Thanks. ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or Blue Earth County -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GAT d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From majordomo-users-owner Sun Jul 10 18:41:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA02165; Sun, 10 Jul 1994 18:41:43 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA02159; Sun, 10 Jul 1994 11:41:35 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id NAA05717; Sun, 10 Jul 1994 13:53:46 -0500 Date: Sun, 10 Jul 1994 13:53:45 +0100 From: "Robert A. Hayden" Subject: Help on digesting requested To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have spent all weekend trying to get digesting installed on one on my lists to no avail. I think the problem is that the documentation is not very clear about how the various perl scripts interact and I'm wary screwing stuff up. Can anyone take a moment to explain to me a little better how exactly digesting works and what one has to do to get it actually working? Sorry for such an open-ended question.... ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or Blue Earth County -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GAT d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From majordomo-users-owner Sun Jul 10 20:54:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA02542; Sun, 10 Jul 1994 20:54:08 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA02536; Sun, 10 Jul 1994 13:53:59 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA07453 (5.65c/IDA-1.4.4 for ); Sun, 10 Jul 1994 16:57:02 -0400 Message-Id: <199407102057.AA07453@cs.umb.edu> To: "Robert A. Hayden" Cc: Majordomo Users Subject: Re: Help on digesting requested In-Reply-To: Your message of "Sun, 10 Jul 1994 13:53:45 BST." Date: Sun, 10 Jul 1994 16:57:02 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , "Robert A. Hayden" writes: >I have spent all weekend trying to get digesting installed on one on my >lists to no avail. I think the problem is that the documentation is not >very clear about how the various perl scripts interact and I'm wary >screwing stuff up. > >Can anyone take a moment to explain to me a little better how exactly >digesting works and what one has to do to get it actually working? > >Sorry for such an open-ended question.... Arrange for the mail that you want digested to be sent to the digest program via an alias/entry like (taken from section 2.2 of the README): "| /tools/majordomo/wrapper digest -r -C -l test-digest test-digest-outgoing" where test-digest is the name of the digest list, and test-digest-outgoing is an alias that expands to the names of all of the people subscribed to the digest list. (In order to use mkdigest, the -digest-outgoing at the end of the alias is required.) Further info about digest is in section 2.5 of the README. The above will accumulate the messages to be placed into the digest. Digest in accumulate mode has an automatic mechanism to create and send a digest to prevent the creation of digests that are too large to be delivered via email. If the message currently being accumulated will make the digest larger than the max_size parameter in the test-digest config file, then a digest is automatically generated and sent to all of the people on the test-digest-outgoing alias. There is also an email accesible mechanism for creating a digest. If you wish to force a digest manually, the majordomo command: mkdigest test-digest will generate a digest for the test-digest. By putting something like: echo "mkdigest test-digest " | mail majordomo@your.site or mail majordomo@your.site < ~/.mkdigest-test (the file ~/.mkdigest-test has "mkdigest test-digest " as its contents) in your crontab(1) or as an at(1) job , digest creation can be automated. -- 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 Sun Jul 10 22:00:02 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA03282; Sun, 10 Jul 1994 22:00:02 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA03275; Sun, 10 Jul 1994 14:59:53 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id RAA09016; Sun, 10 Jul 1994 17:12:00 -0500 Date: Sun, 10 Jul 1994 17:11:59 +0100 From: "Robert A. Hayden" Subject: Re: Help on digesting requested To: "John P. Rouillard" cc: Majordomo Users In-Reply-To: <199407102057.AA07453@cs.umb.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Ok, that helped quite a bit and I have managed to get a test digest working. One of the things I noticed, and this may or may not be something I am doing wrong or simply something that digest can't do, is that there isn't a header of any kind int he digest that shows you the subjects of the messages contained within. I know that the majordomo software at queernet.org will do this, and I've seen other digestifiers that do something similiar (including LISTSERV). Is there a way to do this (easily) with majordomo? ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or Blue Earth County -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GAT d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From majordomo-users-owner Sun Jul 10 22:05:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA03363; Sun, 10 Jul 1994 22:05:11 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA03357; Sun, 10 Jul 1994 15:05:02 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA10822 (5.65c/IDA-1.4.4 for ); Sun, 10 Jul 1994 18:08:06 -0400 Message-Id: <199407102208.AA10822@cs.umb.edu> To: "Robert A. Hayden" Cc: majordomo-users@greatcircle.com Subject: Re: Help on digesting requested In-Reply-To: Your message of "Sun, 10 Jul 1994 17:11:59 BST." Date: Sun, 10 Jul 1994 18:08:05 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , "Robert A. Hayden" writes: >Ok, that helped quite a bit and I have managed to get a test digest >working. > >One of the things I noticed, and this may or may not be something I am >doing wrong or simply something that digest can't do, is that there isn't >a header of any kind int he digest that shows you the subjects of the >messages contained within. Its the message_fronter parameter for the digest list. The message_header parameter is for rfc822 headers. Something like the following (explanatory text is not necessary) should do what you want: # message_fronter [string_array] (undef) # Text to be prepended to the beginning of all messages posted to the # list. The text is expanded before being used. The following # expansion tokens are defined: $LIST - the name of the current list, # $SENDER - the sender as taken from the from line, $VERSION, the # version of majordomo. If used in a digest, only the expansion token # _SUBJECTS_ is available, and it expands to the list of message # subjects in the digest message_fronter << END In this issue: - - _SUBJECTS_ - See the end of the digest for information on subscribing to the bblisa or bblisa-digest mailing lists. END -- 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 Mon Jul 11 14:59:43 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA05261; Mon, 11 Jul 1994 14:59:43 GMT Received: from arsenic.eecs.berkeley.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA05241; Mon, 11 Jul 1994 07:59:29 -0700 Received: (kraitch@localhost) by arsenic.eecs.berkeley.edu (8.6.8/8.5) id IAA06046; Mon, 11 Jul 1994 08:02:40 -0700 Date: Mon, 11 Jul 1994 08:02:40 -0700 From: kraitch@EECS.Berkeley.EDU (mark kraitchman) Message-Id: <199407111502.IAA06046@arsenic.eecs.berkeley.edu> To: Majordomo-Users@GreatCircle.COM Subject: majordomo versus the Dreaded Dash Cc: usctnrtn@ibmmail.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Folks: In majordomo (or at least versions 1.60 through 1.92), a line beginning with a "dash" in a message to majordomo is consider a command for majordomo to stop processing commands (useful if your mailer adds a signature): #line 153 of 1.92 majordomo elsif ($cmd =~ /^-/) { print REPLY "END OF COMMANDS\n"; last; } It has come to my attention that some systems put such a dash in (some as the first line of the body of the message!). For example, IBM's OfficeVision gatewayed through IBM's Advantis network inserts the following line as the first line in the body of the message: ----------------------- Mail item text follows --------------- I understand that OfficeVision is one of the largest mainframe-based mail systems, so this could effect other people trying to send email to majordomo. Are people aware of this problem? Thanks in advance. From majordomo-users-owner Mon Jul 11 12:20:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA09979; Mon, 11 Jul 1994 18:41:53 GMT Received: from lobster.wellfleet.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA06302; Mon, 11 Jul 1994 09:12:54 -0700 Received: from wellfleet.com by lobster.wellfleet.com (4.1/SMI-4.1) id AA00620; Mon, 11 Jul 94 12:13:27 EDT Message-Id: <9407111613.AA00620@lobster.wellfleet.com> Date: 11 Jul 1994 16:58:57 GMT From: PETER_GILIBERTI@wellfleet.com (Peter Giliberti) Organization: Wellfleet Communications Reply-To: PETER_GILIBERTI@wellfleet.com Subject: URGENT To: Majordomo-Users@GreatCircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have created many lists that show up in a repsonse to a "lists" but send a user back unknown list and a help screen if they subscribe. Permissions and ownership look fine......PLEASE HELP!!!! >>>> subscribe clarify_SM_new pgiliber **** subscribe: unknown list 'clarify_SM_new' Peter Giliberti Sr. Network Engineer Wellfleet Communications From majordomo-users-owner Mon Jul 11 12:27:10 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA09693; Mon, 11 Jul 1994 18:25:40 GMT Received: from hutsur by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA02951; Fri, 8 Jul 1994 00:38:26 -0700 Received: from cetis.hut.nl by HUT.NL (PMDF V4.2-14 #6495) id <01HEGJJSHEOG0002YU@HUT.NL>; Fri, 8 Jul 1994 09:43:36 GMT +0100 Received: from CETIS-FS/MAILQUEUE by cetis.hut.nl (Mercury 1.11); Fri, 8 Jul 94 9:42:23 GMT+1 Received: from MAILQUEUE by CETIS-FS (Mercury 1.11); Fri, 8 Jul 94 9:42:11 GMT+1 Date: Fri, 8 Jul 1994 09:41:46 GMT+0100 From: Johan Pater Subject: Unknown mailer error 13 To: majordomo-users@greatcircle.com Message-id: <9316EBF68C9@cetis.hut.nl> Organization: Hogeschool Utrecht / Cetis X-Envelope-to: majordomo-users@greatcircle.com X-Mailer: Pegasus Mail v3.1 (R1a) Content-transfer-encoding: 7BIT Priority: normal Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have installed majordomo 1.92 and when i try to subscribe (give any command) then i get this error which isnt documented. I looked at the permission rights but i think that they are good. So i dont know what this error means or how i can get rid of it. Can someone help me with this please ? ----- Transcript of session follows ----- shlock: open(">/home/majordomo/lists/shlock.25424"): Permission denied at /ho me/majordomo/shlock.pl line 131, <> line 1. Can't create new config file /home/majordomo/lists/hutcis.config.out at /home /majordomo/config_parse.pl line 440, <> line 1. 554 "|/home/majordomo/wrapper majordomo"... unknown mailer error 13 Thanks, Johan Pater ------------------------------------------------------------------- | Cetis | | Centre for Educational Technology, Innovation and Stafftraining | | at the 'Hogeschool Utrecht' University for Vocational Education | ------------------------------------------------------------------- | INTERNET : JPATER@CETIS.HUT.NL | PO-BOX 573 | | FAX : (+31) (0)30-368180 | 3500 AN UTRECHT | | PHONE : (+31) (0)30-308117 | THE NETHERLANDS (EUROPE)| ------------------------------------------------------------------- From majordomo-users-owner Mon Jul 11 12:32:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA09783; Mon, 11 Jul 1994 18:29:03 GMT Received: from hutsur by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id EAA03315; Mon, 11 Jul 1994 04:16:07 -0700 Received: from cetis.hut.nl by HUT.NL (PMDF V4.2-14 #6495) id <01HEKY2PIQWG000ACQ@HUT.NL>; Mon, 11 Jul 1994 13:22:06 GMT +0100 Received: from CETIS-FS/MAILQUEUE by cetis.hut.nl (Mercury 1.11); Mon, 11 Jul 94 13:20:12 GMT+1 Received: from MAILQUEUE by CETIS-FS (Mercury 1.11); Mon, 11 Jul 94 13:19:49 GMT+1 Date: Mon, 11 Jul 1994 13:19:24 GMT+0100 From: Johan Pater Subject: Unknown mailer error 13 To: majordomo-users@greatcircle.com Message-id: <97D117F4F6C@cetis.hut.nl> Organization: Hogeschool Utrecht / Cetis X-Envelope-to: majordomo-users@greatcircle.com X-Mailer: Pegasus Mail v3.1 (R1a) Content-transfer-encoding: 7BIT Priority: normal Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I am trying to install majordomo but i keep getting this error when i want to subscribe a user or when i want to see the lists that i serve. I only have one list called Hutcis and below is the error i keep getting. shlock: open(">/home/majordomo/lists/shlock.8177"): Permission denied at /home/majordomo/shlock.pl line 131, <_GEN_1> line 1. Can't create new config file /home/majordomo/lists/hutcis.config.out at /home/majordomo/config_parse.pl line 440, <_GEN_1> line 1. 554 "|/home/majordomo/wrapper majordomo"... unknown mailer error 13 Could anybody help me with this error cause i cant find out what problem is causing this error. Thanks in advance, Johan Pater ------------------------------------------------------------------- | Cetis | | Centre for Educational Technology, Innovation and Stafftraining | | at the 'Hogeschool Utrecht' University for Vocational Education | ------------------------------------------------------------------- | INTERNET : JPATER@CETIS.HUT.NL | PO-BOX 573 | | FAX : (+31) (0)30-368180 | 3500 AN UTRECHT | | PHONE : (+31) (0)30-308117 | THE NETHERLANDS (EUROPE)| ------------------------------------------------------------------- From majordomo-users-owner Mon Jul 11 19:46:15 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA11087; Mon, 11 Jul 1994 19:46:15 GMT Received: from ns.ge.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA11070; Mon, 11 Jul 1994 12:45:59 -0700 Received: from [3.54.4.10] by ns.ge.com (5.65/GE Gateway 1.23) with SMTP id AA26817; Mon, 11 Jul 94 15:41:20 -0400 Received: from acc113.vf.ge.com (acc113.acc.vf.ge.com) by acc1.acc.vf.ge.com (4.1/GEA Sun server 2.7A)id AA03481; Mon, 11 Jul 94 15:47:12 EDT Date: Mon, 11 Jul 94 15:47:12 EDT From: bdavis@acc1.acc.vf.ge.com (Davis Blake) Message-Id: <9407111947.AA03481@acc1.acc.vf.ge.com> To: jpater@cetis.hut.nl Subject: Re: Unknown mailer error 13 Cc: majordomo-users@greatcircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Most likely a permission problems for directory /home/majordomo/lists make sure that the your majordomo group (typically majordom) owns the directory and can write to the directory. ++--+----+----+----+----+----+----+----+----+----+----+----+----+---++ ++ Blake Davis + ++ ++ Chief System Architect + 610.992.6139 Phone ++ ++ Information Services & Technologies + 610.992.6299 FAX ++ ++ Martin Marietta + ++ ++ 640 Freedom Center, 3rd floor + Davis.Blake@ist.vf.ge.com ++ ++ King of Prussia, PA 19406 + ++ ++--+----+----+----+----+----+----+----+----+----+----+----+----+---++ ----- Begin Included Message ----- From majordomo-users-owner@greatcircle.com Mon Jul 11 15:41:45 1994 Date: Fri, 8 Jul 1994 09:41:46 GMT+0100 From: Johan Pater Subject: Unknown mailer error 13 To: majordomo-users@greatcircle.com Organization: Hogeschool Utrecht / Cetis X-Envelope-To: majordomo-users@greatcircle.com X-Mailer: Pegasus Mail v3.1 (R1a) Content-Transfer-Encoding: 7BIT Priority: normal Sender: Majordomo-Users-Owner@greatcircle.com Content-Length: 1296 I have installed majordomo 1.92 and when i try to subscribe (give any command) then i get this error which isnt documented. I looked at the permission rights but i think that they are good. So i dont know what this error means or how i can get rid of it. Can someone help me with this please ? ----- Transcript of session follows ----- shlock: open(">/home/majordomo/lists/shlock.25424"): Permission denied at /ho me/majordomo/shlock.pl line 131, <> line 1. Can't create new config file /home/majordomo/lists/hutcis.config.out at /home /majordomo/config_parse.pl line 440, <> line 1. 554 "|/home/majordomo/wrapper majordomo"... unknown mailer error 13 Thanks, Johan Pater ------------------------------------------------------------------- | Cetis | | Centre for Educational Technology, Innovation and Stafftraining | | at the 'Hogeschool Utrecht' University for Vocational Education | ------------------------------------------------------------------- | INTERNET : JPATER@CETIS.HUT.NL | PO-BOX 573 | | FAX : (+31) (0)30-368180 | 3500 AN UTRECHT | | PHONE : (+31) (0)30-308117 | THE NETHERLANDS (EUROPE)| ------------------------------------------------------------------- ----- End Included Message ----- From majordomo-users-owner Mon Jul 11 21:05:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA12487; Mon, 11 Jul 1994 21:05:12 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA10990; Mon, 11 Jul 1994 12:41:18 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA18284 (5.65c/IDA-1.4.4 for ); Mon, 11 Jul 1994 15:44:02 -0400 Message-Id: <199407111944.AA18284@cs.umb.edu> To: Johan Pater Cc: majordomo-users@greatcircle.com Subject: Re: Unknown mailer error 13 In-Reply-To: Your message of "Fri, 08 Jul 1994 09:41:46 BST." <9316EBF68C9@cetis.hut.nl> Date: Mon, 11 Jul 1994 15:43:56 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9316EBF68C9@cetis.hut.nl>, Johan Pater writes: >I have installed majordomo 1.92 and when i try to subscribe (give any >command) then i get this error which isnt documented. I looked at the >permission rights but i think that they are good. So i dont know what >this error means or how i can get rid of it. > >Can someone help me with this please ? > > ----- Transcript of session follows ----- >shlock: open(">/home/majordomo/lists/shlock.25424"): Permission denied at /ho >me/majordomo/shlock.pl line 131, <> line 1. >Can't create new config file /home/majordomo/lists/hutcis.config.out at /home >/majordomo/config_parse.pl line 440, <> line 1. >554 "|/home/majordomo/wrapper majordomo"... unknown mailer error 13 The permissions for the directory: /home/majordomo/lists must be 775. the directory must be owned by the user that the wrapper runs as, and the group must be the same as the group that the wrapper runs as. Also the wrapper must be setuid and setgid. -- 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 Mon Jul 11 21:06:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA12566; Mon, 11 Jul 1994 21:06:24 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA11822; Mon, 11 Jul 1994 13:31:25 -0700 Message-Id: <199407112031.NAA11822@mycroft.GreatCircle.COM> To: PETER_GILIBERTI@wellfleet.com cc: Majordomo-Users@GreatCircle.com Subject: Re: URGENT In-reply-to: Your message of 11 Jul 1994 16:58:57 GMT Date: Mon, 11 Jul 1994 13:31:24 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk PETER_GILIBERTI@wellfleet.com (Peter Giliberti) writes: # I have created many lists that show up in a repsonse to a "lists" but send a # user back unknown list and a help screen if they subscribe. Permissions and # ownership look fine......PLEASE HELP!!!! # # >>>> subscribe clarify_SM_new pgiliber # **** subscribe: unknown list 'clarify_SM_new' # # Peter Giliberti # Sr. Network Engineer # Wellfleet Communications Majordomo accepts list names in mixed case, but converts them to all-lower-case before using them as part of a filename. Thus, make sure that the files associated with your list (including the list itself) have all-lower-case names. -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Mon Jul 11 21:36:03 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA13434; Mon, 11 Jul 1994 21:36:03 GMT Received: from zoom.bga.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA13424; Mon, 11 Jul 1994 14:35:44 -0700 Received: (from fmouse@localhost) by zoom.bga.com (8.6.9/8.6.9) id QAA24657; Mon, 11 Jul 1994 16:38:25 -0500 From: Lindsay Haisley Message-Id: <199407112138.QAA24657@zoom.bga.com> Subject: Re: Help on digesting requested To: rouilj@cs.umb.edu (John P. Rouillard) Date: Mon, 11 Jul 1994 16:38:25 -0500 (CDT) Cc: hayden@vorlon.mankato.msus.edu, majordomo-users@GreatCircle.COM In-Reply-To: <199407102057.AA07453@cs.umb.edu> from "John P. Rouillard" at Jul 10, 94 04:57:02 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1818 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thus spoke John P. Rouillard ... > > > In message , > "Robert A. Hayden" writes: > > >I have spent all weekend trying to get digesting installed on one on my > >lists to no avail. I think the problem is that the documentation is not > >very clear about how the various perl scripts interact and I'm wary > >screwing stuff up. > > > >Can anyone take a moment to explain to me a little better how exactly > >digesting works and what one has to do to get it actually working? > > > >Sorry for such an open-ended question.... > > Arrange for the mail that you want digested to be sent to the digest > program via an alias/entry like (taken from section 2.2 of the > README): > > "| /tools/majordomo/wrapper digest -r -C -l test-digest test-digest-outgoing" > > where test-digest is the name of the digest list, and > test-digest-outgoing is an alias that expands to the names of all of > the people subscribed to the digest list. (In order to use mkdigest, > the -digest-outgoing at the end of the alias is required.) Further > info about digest is in section 2.5 of the README. The above will > accumulate the messages to be placed into the digest. Something that tripped me up in working out the details of digests is that the digests "working directory" is of the form 'listname-digest' rather than just of the form 'listname'. This is obvious in retrospect but it was the only aspect of setting up a digest that I had to look more than twice at to get it to work. ----------------------------------------------- Lindsay Haisley |"On the Internet, no one knows you're a dog" | fmouse@bga.com | --- The New Yorker Magazine | Austin, Texas, USA ----------------------------------------------- * * * * * * * From majordomo-users-owner Tue Jul 12 02:06:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id CAA16749; Tue, 12 Jul 1994 02:06:20 GMT Received: from zoom.bga.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA12930; Mon, 11 Jul 1994 14:23:04 -0700 Received: (from fmouse@localhost) by zoom.bga.com (8.6.9/8.6.9) id QAA24142; Mon, 11 Jul 1994 16:25:57 -0500 From: Lindsay Haisley Message-Id: <199407112125.QAA24142@zoom.bga.com> Subject: Re: Unknown mailer error 13 To: jpater@cetis.hut.nl (Johan Pater) Date: Mon, 11 Jul 1994 16:25:56 -0500 (CDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <97D117F4F6C@cetis.hut.nl> from "Johan Pater" at Jul 11, 94 01:19:24 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1909 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thus spoke Johan Pater ... > Hi, > > I am trying to install majordomo but i keep getting this error when i > want to subscribe a user or when i want to see the lists that i > serve. I only have one list called Hutcis and below is the error i > keep getting. > > shlock: open(">/home/majordomo/lists/shlock.8177"): > Permission denied at /home/majordomo/shlock.pl line 131, <_GEN_1> > line 1. > Can't create new config file /home/majordomo/lists/hutcis.config.out > at /home/majordomo/config_parse.pl line 440, <_GEN_1> line 1. > 554 "|/home/majordomo/wrapper majordomo"... unknown mailer error 13 > > Could anybody help me with this error cause i cant find out what > problem is causing this error. This is probably a directory permission error. Make sure of the following. 1. You must have a user majordomo and a group majordom (GID 15 on our system, possibly required). The former in the passwd file and the latter in /etc/group. 2. Depending on your system, you must have either root or daemon as a member of group majordom. It probably wouldn't hurt to put in both in /etc/group. 3. Make sure that that /home and /home/majordomo are world executable and that /home/majordomo and /home/majordomo/lists are owned by user majordom and group majordom. I came up against this shlock error a bunch in the process of setting up symlinked directories for users' archives on our system, the result of which is that I inadverdantly sent one user close to half a meg of repeating shlock errors before discovering that I had created all the required directories but not the symlink between them! ----------------------------------------------- Lindsay Haisley |"On the Internet, no one knows you're a dog" | fmouse@bga.com | --- The New Yorker Magazine | Austin, Texas, USA ----------------------------------------------- * * * * * * * From majordomo-users-owner Tue Jul 12 02:35:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id CAA17154; Tue, 12 Jul 1994 02:35:17 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA17148; Mon, 11 Jul 1994 19:35:06 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id VAA10897; Mon, 11 Jul 1994 21:38:33 -0500 Date: Mon, 11 Jul 1994 21:38:31 +0100 From: "Robert A. Hayden" Subject: A couple more question on digesting To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I've got a couple more questions on digesting that I wanted to bounce here before I start breaking something. :-) -------------------------- For the list I have, there is a directory _listname-digest.archive_ where the completed digests are being stored, but I also noticed that there is a file forming called _listname-digest.archive.9407_ what is growing in size and contains all of the postings to the list since digesting was started, and when the digest is completed, this file doesn't erase or anything and just continues to append messages. I am assuming (perhaps wrong) that the following alias entry is what is creating this file: listname-outgoing::include:/home/majordomo/lists/listname, "| /home/majordomo/wrapper digest -r -C -l listname-digest \ listname-digest-outgoing", "| /home/majordomo/wrapper archive2.pl -a -m -f \ /home/majordomo/lists/listname-digest.archive" Is the archive2.pl entry necessary? Am I doing something wrong? --------------------------------------------------------------------- #2 Is there a way set up some kind of cron entry so that digests will get sent out if their is a posting over Xtime old? ie, if a digest is supposed to go out at, say, 25k, but it is only 12k and there is an item that is over 1day old, send the digest anyways. Is this the digest.diff patch in contrib? On a similiar note, if it is digest.diff that I need to apply, I did do a test apply, and I noted a could hunks failed. I'm not much of a perl hacker so I don't know what didn't work and I'm hesitant about using partially applied patches. (This is with a previously unpatched 1.92). So I went back to the old and I am running with UNPATCHED scripts. In any case, I appreciate all of your help :-) ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or Blue Earth County -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GAT d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From majordomo-users-owner Tue Jul 12 04:05:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id EAA18467; Tue, 12 Jul 1994 04:05:11 GMT Received: from zoom.bga.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA13475; Mon, 11 Jul 1994 14:38:48 -0700 Received: (from fmouse@localhost) by zoom.bga.com (8.6.9/8.6.9) id QAA24836; Mon, 11 Jul 1994 16:41:52 -0500 From: Lindsay Haisley Message-Id: <199407112141.QAA24836@zoom.bga.com> Subject: Re: URGENT To: PETER_GILIBERTI@wellfleet.com Date: Mon, 11 Jul 1994 16:41:51 -0500 (CDT) Cc: Majordomo-Users@GreatCircle.COM In-Reply-To: <9407111613.AA00620@lobster.wellfleet.com> from "Peter Giliberti" at Jul 11, 94 04:58:57 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 775 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thus spoke Peter Giliberti ... > > I have created many lists that show up in a repsonse to a "lists" but send a > user back unknown list and a help screen if they subscribe. Permissions and > ownership look fine......PLEASE HELP!!!! > > >>>> subscribe clarify_SM_new pgiliber > **** subscribe: unknown list 'clarify_SM_new' Does Majordomo have permission to read the list? It will run as daemon or root on your system and said users must have appropriate authority. Is the list mode 664? ----------------------------------------------- Lindsay Haisley |"On the Internet, no one knows you're a dog" | fmouse@bga.com | --- The New Yorker Magazine | Austin, Texas, USA ----------------------------------------------- * * * * * * * From majordomo-users-owner Tue Jul 12 06:31:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA20469; Tue, 12 Jul 1994 06:31:14 GMT Received: from mail.crl.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA20459; Mon, 11 Jul 1994 23:30:56 -0700 Received: from crl.crl.com (crl.com) by mail.crl.com with SMTP id AA15827 (5.65c/IDA-1.5 for ); Mon, 11 Jul 1994 23:30:52 -0700 Received: by crl.crl.com id AA15199 (5.65c/IDA-1.5); Mon, 11 Jul 1994 23:30:48 -0700 Date: Mon, 11 Jul 1994 23:30:48 -0700 From: Max D Hozven Message-Id: <199407120630.AA15199@crl.crl.com> To: majordomo-users@greatcircle.com Subject: Can't get Majordomo to work correctly under Solaris 2.3 Cc: maxh@crl.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, I just cannot get Majordomo to work under Solaris 2.3 (using Berkeley sendmail). If anyone has a working distribution (anything you can send, like aliases, info showing permissions of support files) they could tar up and email me, I'd really appreciate it. I've been over and over the support docs, but can never make it work 100%. I can compile it, but depending on my configuration I get permission errors, sendmail related errors, etc. In other respects this system works fine (mail works fine, etc). I must be missing something. Thanks, -Max maxh@crl.com From majordomo-users-owner Tue Jul 12 12:55:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA24080; Tue, 12 Jul 1994 12:55:39 GMT Received: from lobster.wellfleet.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id FAA24073; Tue, 12 Jul 1994 05:55:32 -0700 Received: from wellfleet.com by lobster.wellfleet.com (4.1/SMI-4.1) id AA18545; Tue, 12 Jul 94 08:56:07 EDT Message-Id: <9407121256.AA18545@lobster.wellfleet.com> Date: 12 Jul 1994 13:57:04 GMT From: PETER_GILIBERTI@wellfleet.com (Peter Giliberti) Organization: Wellfleet Communications Reply-To: PETER_GILIBERTI@wellfleet.com Subject: Re: Re: URGENT To: Majordomo-Users@GreatCircle.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Thnaks to all who answered...My problem is resolved by using all lower case.... Peter Giliberti Sr.Network Engineer Wellfleet Communications From majordomo-users-owner Wed Jul 13 00:28:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA04193; Wed, 13 Jul 1994 00:28:06 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA04184; Tue, 12 Jul 1994 17:27:54 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id TAA00485; Tue, 12 Jul 1994 19:31:26 -0500 Date: Tue, 12 Jul 1994 19:31:21 +0100 From: "Robert A. Hayden" Subject: Duplicate Postings To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk As you all know, I recently installed digesting on one of my mailing lists. Unfortunately, I am now encountering another rpoblem that is, well, rather annoying. For some reason that I cannot determine, *some* of the postings are appearing twice. The headers on each posting are identical. Unfortunately, I can't give much more detail than that because that's all I know. ANyone have a thought as to what might be causing this problem? ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or Blue Earth County -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GAT d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From majordomo-users-owner Wed Jul 13 15:13:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA10733; Wed, 13 Jul 1994 15:13:24 GMT Received: from dns.irm.r9.fws.gov by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA10722; Wed, 13 Jul 1994 08:13:09 -0700 From: clarkj@MAIL.FWS.GOV Received: from MAIL.FWS.GOV (mail.irm.r9.fws.gov) by dns.irm.r9.fws.gov (4.1/SMI-4.1) id AA24594; Wed, 13 Jul 94 09:24:07 MDT Received: from ccMail by MAIL.FWS.GOV id AA774116177 Wed, 13 Jul 94 09:16:17 MST Date: Wed, 13 Jul 94 09:16:17 MST Message-Id: <9406137741.AA774116177@MAIL.FWS.GOV> To: majordomo-users@greatcircle.com Subject: trouble getting started . Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Greetings all - I'm tring to get majordomo 1.92 running on a linux 486. I am also learning Unix etc. at the same time. I recompiled wrapper. I edit the aliases file and the majordomo.cf file. I changed the file in the majordomo director to 775, and the owner to majordomo. Thinking that it might be something with the mail system (and mjrdm not getting to it) i tried edited the mail alias to "smail" then "mail". seems fine so far. But when I run major it 'hangs'. produces no output. A ps done from another console shows it is S (sleep ? stalled ?). I assume that the system must ahve a user called majordomo. Must majordomo be the process that starts Majordomo ? thanks in advance for any thoughts and/or suggestions. John Clark US Fish & Wildlife Service clarkj@mail.fws.gov From majordomo-users-owner Wed Jul 13 17:22:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA11580; Wed, 13 Jul 1994 17:22:39 GMT Received: from ns.ge.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA11574; Wed, 13 Jul 1994 10:22:28 -0700 Received: from [3.54.4.10] by ns.ge.com (5.65/GE Gateway 1.23) with SMTP id AA09447; Wed, 13 Jul 94 12:02:12 -0400 Received: from acc113.vf.ge.com (acc113.acc.vf.ge.com) by acc1.acc.vf.ge.com (4.1/GEA Sun server 2.7A)id AA20621; Wed, 13 Jul 94 12:08:12 EDT Date: Wed, 13 Jul 94 12:08:12 EDT From: bdavis@acc1.acc.vf.ge.com (Davis Blake) Message-Id: <9407131608.AA20621@acc1.acc.vf.ge.com> To: majordomo-users@greatcircle.com Subject: Microsoft Mail Problems Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have some user's on my lists that use Microsoft Mail on a PC Network. I am using Majordomo v1.92 from a SunOS 4.1.3 machine. I have the listname.config files setup with the following options: reply_to = $SENDER sender = owner-listname when the message goes out it has a header similar to: From owner-notes Wed Jul 13 11:50:08 1994 Date: Wed, 13 Jul 94 11:50:05 EDT From: joe.smith@somewhere.usa.com To: notes Subject: test 11:54 Sender: owner-notes@ist.vf.ge.com Reply-To: joe.smith@somewhere.usa.com Content-Length: 7 ---- The problem is that the MS Mail SMTP gateway uses the first line "From owner-notes Wed Jul 13 11:50:08 1994" for "Reply" ing to and ignores the "From: joe.smith@somewhere.usa.com" and Reply-To: joe.smith@somewhere.usa.com lines, and therefore they reply to the list owner (me) rather than the person sending the message. Has anyone experienced similar problems. Are there are known solutions ? TIA, Blake Davis From majordomo-users-owner Wed Jul 13 17:52:36 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA11752; Wed, 13 Jul 1994 17:52:36 GMT Received: from midway.uchicago.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA11746; Wed, 13 Jul 1994 10:52:20 -0700 From: ckoenig@midway.uchicago.edu Received: from kimbark.uchicago.edu by midway.uchicago.edu for majordomo-users@greatcircle.com Wed, 13 Jul 94 12:55:17 CDT Received: from localhost.uchicago.edu by kimbark.uchicago.edu (4.1/UCCO-1.0A) id AA13227; Wed, 13 Jul 94 12:55:12 CDT Message-Id: <9407131755.AA13227@kimbark.uchicago.edu> To: majordomo-users@greatcircle.com Subject: Re: Microsoft Mail Problems In-Reply-To: Your message of "Wed, 13 Jul 94 12:08:12 EDT." <9407131608.AA20621@acc1.acc.vf.ge.com> Date: Wed, 13 Jul 94 12:55:12 -0500 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk This is probably more relevant to list management and mail administration in general, rather than specifically to the majordomo package, and this has been discussed in other forums before, with no resolution unfortunately. Someone who administers an MS-Mail SMTP gateway here on the U. of Chicago once forwarded me a copy of an email exchange he had with a Microsoft software engineer on this very topic. The Microsoft technical people insist that they are making a choice which is not contra-indicated under any Internet RFC's, namely that since they only have one slot in their message format for a reply address, and therefore they have to drop some of the Internet information, and choose which piece to use (i.e. envelope fields or header fields) they prefer to choose the SMTP envelope sender. They (Microsoft) seem to suggest that they make this preferred choice (having their end MUA return all replies only to the envelope sender) because of the RFC requirements that MTA's return non-delivery reports to the envelope sender. The problem is that there's no clear prohibition, in the RFC's, of what they're doing. It appears to be ambiguous. I even posted the details of their position to the comp.mail.headers newsgroup (gatewayed to the Header-People mailing list), and it generated a bit of discussion. Of course I'd like to prove that they have made a wrong interpretation, but the chapter and verse is just not there to pin it down...... The problem is that the RFC's never come out and state positively what is acceptable and unacceptable in this situation. People quoted various chapters and verses of RFC 1123 which say what an MTA has to do when returning non-delivery errors (these must go to the SMTP Envelope sender), and RFC 822 says what order the headers should be consulted (Reply-To:, From:) when an MUA constructs a reply, but the question never arises in the RFC's, about what a gateway should do in dropping some of the Internet information and consolidating/selecting down to the more limited set of info made available to a LAN mail system, or specifically, if it's OK or not OK for an MTA to use the envelope sender for making a reply to a delivered message, because the relevant RFC 822 headers have been made unavailable. I'd love it if someone could do better than this in constructing a canonical argument, based on RFC chapter and verse, showing what such gateways must do in feeding a single return address to their LAN mailer. If you can, you should contact Microsoft and argue directly with them, and let us know how it turned out! :-) You could also re-ignite the discussion on comp.mail.headers if you wish. Chris Koenigsberg: ckk@uchicago.edu, ckoenig@midway.uchicago.edu U. of Chicago Academic Information Technologies From majordomo-users-owner Thu Jul 14 03:33:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id DAA15379; Thu, 14 Jul 1994 03:33:13 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA15373; Wed, 13 Jul 1994 20:33:06 -0700 Received: from lunch.asd.sgi.com by sgi.sgi.com via SMTP (940627.SGI.8.6.9/910110.SGI) id UAA26176; Wed, 13 Jul 1994 20:36:23 -0700 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:majordomo-users@GreatCircle.COM id AA15681; Wed, 13 Jul 94 20:36:22 -0700 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9407140336.AA15681@lunch.asd.sgi.com> Subject: Re: A couple more question on digesting To: hayden@vorlon.mankato.msus.edu (Robert A. Hayden) Date: Wed, 13 Jul 1994 20:36:22 -0700 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Robert A. Hayden" at Jul 11, 94 09:38:31 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: 1675 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I am assuming (perhaps wrong) that the following alias entry is what is > creating this file: > > listname-outgoing::include:/home/majordomo/lists/listname, > "| /home/majordomo/wrapper digest -r -C -l listname-digest \ > listname-digest-outgoing", > "| /home/majordomo/wrapper archive2.pl -a -m -f \ > /home/majordomo/lists/listname-digest.archive" > > Is the archive2.pl entry necessary? Am I doing something wrong? Your assumption is correct. No, it is not necessary. The digest program makes archives of each issue already. > #2 > Is there a way set up some kind of cron entry so that digests will get > sent out if their is a posting over Xtime old? ie, if a digest is > supposed to go out at, say, 25k, but it is only 12k and there is an item > that is over 1day old, send the digest anyways. > > Is this the digest.diff patch in contrib? Yes. However, if you only want one day, you can just use a cron script to push a digest every day. Not sure how well this works. I wrote the digest.diff patches, which work quite well, for my purposes at least. > On a similiar note, if it is digest.diff that I need to apply, I did do a > test apply, and I noted a could hunks failed. I'm not much of a perl > hacker so I don't know what didn't work and I'm hesitant about using > partially applied patches. (This is with a previously unpatched 1.92). > So I went back to the old and I am running with UNPATCHED scripts. I can help you with that. Let me know which patches don't apply and I can send you new versions of those files. -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Thu Jul 14 03:38:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id DAA15402; Thu, 14 Jul 1994 03:38:54 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA15396; Wed, 13 Jul 1994 20:38:47 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id WAA07322; Wed, 13 Jul 1994 22:42:34 -0500 Date: Wed, 13 Jul 1994 22:42:33 +0100 From: "Robert A. Hayden" Subject: Re: A couple more question on digesting To: Paul Close cc: majordomo-users@GreatCircle.COM In-Reply-To: <9407140336.AA15681@lunch.asd.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Wed, 13 Jul 1994, Paul Close wrote: > Yes. However, if you only want one day, you can just use a cron script to > push a digest every day. Not sure how well this works. I wrote the > digest.diff patches, which work quite well, for my purposes at least. Well, the only thing I wonder is, let's say I have a cron entry to push a digest at 6pm every evening. If, by some fluke, the digest reset at say 5:20, and ther was only one entry of 1.5K in the digest, it would push out a tiny one. Thus, a push based on the age of the oldest entry would make sure that a digest got out, but not push out something that was artifically small (unless the traffic was, of course, very light). ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or Blue Earth County -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GAT d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From majordomo-users-owner Thu Jul 14 12:09:59 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA20014; Thu, 14 Jul 1994 12:09:59 GMT Received: from ESLGATE.ELSEVIER.CO.UK by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id FAA20008; Thu, 14 Jul 1994 05:09:46 -0700 From: d.gaunt@ESLGATE.ELSEVIER.CO.UK Received: from ESLSPIRES-Message_Server by ESLGATE.ELSEVIER.CO.UK with WordPerfect_Office; Mon, 11 Jul 1994 17:14:41 +0000 Message-Id: X-Mailer: WordPerfect Office 4.0 Date: Mon, 11 Jul 1994 17:13:28 +0000 To: majordomo-users@greatcircle.com Subject: suspend Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have just joined this list and caught the end of the suspend discussion. I would be very interested in such an option since we have closed lists. The BITNET listserv has a set command: set listname options where listname is either an individual list or * for all lists maintained by the particular listserv. options is one of: mail, digest, index, nomail The nomail option stops mail being distributed to you, it is useful when you are away for an extended period and are on closed or many open lists. Did anybody implement a suspend option for version 1.92? If so I would appreciate a copy of the code. From majordomo-users-owner Thu Jul 14 18:20:40 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA22830; Thu, 14 Jul 1994 18:20:40 GMT Received: from utdallas.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA22824; Thu, 14 Jul 1994 11:20:32 -0700 Received: from frog.utdallas.edu by utdallas.edu (ZMailer 2.1.3 #231) with BLIMP id <13947>; Thu, 14 Jul 1994 13:23:42 -0500 Subject: MAJORDOMO ABORT (fwd) From: Billy Barron To: majordomo-users@greatcircle.com Date: Thu, 14 Jul 1994 13:23:27 -0500 X-WWW-Page: http://www.utdallas.edu/acc/billy.html X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 532 Message-Id: <94Jul14.132342cdt.13947@utdallas.edu> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Why have I been getting the following messages? In reply to majordomo@utdallas.edu's message: >From daemon@utdallas.edu Thu Jul 14 13:08:10 1994 >To: majordomo-owner@utdallas.edu >From: majordomo@utdallas.edu >Subject: MAJORDOMO ABORT >Reply-To: majordomo@utdallas.edu >Message-Id: <94Jul14.130804cdt.13950@utdallas.edu> >Date: Thu, 14 Jul 1994 13:07:53 -0500 > >-- > > >MAJORDOMO ABORT > >HOSTILE ADDRESS Horney_Jean/furman@furman.edu > > -- Billy Barron, Network Services Manager, Univ of Texas at Dallas billy@utdallas.edu From majordomo-users-owner Thu Jul 14 18:25:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA22894; Thu, 14 Jul 1994 18:25:18 GMT Received: from gordius.gordian.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA22888; Thu, 14 Jul 1994 11:25:08 -0700 Received: from lantronix.com (arnie.lantronix.com [192.111.119.91]) by gordius.gordian.com (8.6.5/8.6.5) with SMTP id LAA22837 for ; Thu, 14 Jul 1994 11:27:57 -0700 Received: from shark.lantronix.com by lantronix.com (4.1/SMI-4.0) id AA29789; Thu, 14 Jul 94 11:27:55 PDT Date: Thu, 14 Jul 94 11:27:55 PDT From: troy@lantronix.com (Troy Wyatt) Message-Id: <9407141827.AA29789@lantronix.com> To: majordomo-users@greatcircle.com Subject: FAQ for setting up the get and index part. Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I cant find docs on how to set this feature up. Is it unsupported, or....... Please, could somone point me to the right area? troy From majordomo-users-owner Fri Jul 15 03:04:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id DAA28556; Fri, 15 Jul 1994 03:04:29 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA28550; Thu, 14 Jul 1994 20:04:21 -0700 Received: from lunch.asd.sgi.com by sgi.sgi.com via SMTP (940627.SGI.8.6.9/910110.SGI) id UAA25734; Thu, 14 Jul 1994 20:07:01 -0700 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:majordomo-users@GreatCircle.COM id AA21516; Thu, 14 Jul 94 20:07:00 -0700 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9407150307.AA21516@lunch.asd.sgi.com> Subject: Re: A couple more question on digesting To: hayden@vorlon.mankato.msus.edu (Robert A. Hayden) Date: Thu, 14 Jul 1994 20:07:00 -0700 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: from "Robert A. Hayden" at Jul 13, 94 10:42:33 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: 1287 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > Yes. However, if you only want one day, you can just use a cron script to > > push a digest every day. Not sure how well this works. I wrote the > > digest.diff patches, which work quite well, for my purposes at least. > > Well, the only thing I wonder is, let's say I have a cron entry to push a > digest at 6pm every evening. If, by some fluke, the digest reset at say > 5:20, and ther was only one entry of 1.5K in the digest, it would push > out a tiny one. Thus, a push based on the age of the oldest entry would > make sure that a digest got out, but not push out something that was > artifically small (unless the traffic was, of course, very light). That would be a problem. That's why I added the code to only make a digest if the oldest article was at least a certain age (even if that age is 1). I'm currently working on code to suppress making any digest on the fly. In other words, digests can only get "pushed" out. I'm planning on using this on quiet lists to make a weekly digest. Every Sunday one (or more) digest(s) goes out. The one or more business is because more than one digest's worth might accumulate over the week. Yours for better digests, -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Fri Jul 15 18:59:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA06548; Fri, 15 Jul 1994 18:59:01 GMT Received: from protocol.zycad.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA06530; Fri, 15 Jul 1994 11:57:24 -0700 Received: from zycad.zycad.com by protocol.zycad.com (4.1/SMI-4.1) id AA07204; Fri, 15 Jul 94 15:00:29 EDT Received: from dylan.zycad.com by zycad.zycad.com (4.1/SMI-4.1) id AA02348; Fri, 15 Jul 94 12:01:40 PDT Received: from localhost by dylan.zycad.com (4.1/SMI-4.1) id AA29248; Fri, 15 Jul 94 11:58:49 PDT Message-Id: <9407151858.AA29248@dylan.zycad.com> To: majordomo-users@greatcircle.com Subject: multiple hierarchical lists Date: Fri, 15 Jul 1994 11:58:48 -0700 From: Olly Stephens Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have just started to set-up lists of the form: -announce - announcements for -users - forum for discussion about -internal - forum for discussion about restricted to employees only. I want the announce list to also post to the users list, and the users list to also post to the internal list. According to management, all lists have to closed. I am archiving each list separately, and really only want the "real" messages for each group to be archived, rather than the ones that appear their through the hierarchy mechanism, so instead of adding "-users" as a member of "-announce" etc., I set up aliases of the form: ... -announce-outgoing: :include:.../-announce, :include:.../-users, :include:.../-internal, "|.../wrapper archive2.pl ... -f .../-announce" ... -users-outgoing: :include:.../-users, :include:.../-internal, "|.../wrapper archive2.pl ... -f .../-users" ... -internal-outgoing: :include:.../-internal, "|.../wrapper archive2.pl ... -f .../-internal" ... Now, in addition, I want to restrict any one person (in other words any one e-mail address) to only appearing in one of the three lists. Thus, my questions are: a) how can I automatically disallow multiple subscriptions to a set of lists? b) in the case of the internal list, can I make it non-approved subscrition and include some checking mechanism which only allows people from my domain? c) can I automatically maintain the "one list per address mechanism" i.e. can I change it so it sends the approval person a message of the form: > joe_bloggs@dom.ain has requested subscription to group -users > > (he is currently subscribed to -announce) And make it so that if the approval person approves it, he is automatically removed from -announce. c) because the lists are closed, someone like me (who is on the internal list) cannot send mail to the users list (correct?). How can I make it so that the subscription testing on a post knows about the hierarchy and allows this type of action. OR: a) am I going about this totally wrong? this stuff is brand new to me Thanks in advance, Olly From majordomo-users-owner Sat Jul 16 13:16:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA16670; Sat, 16 Jul 1994 13:16:20 GMT Received: from ruby.ora.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA16661; Sat, 16 Jul 1994 06:16:10 -0700 Received: from rubble.west.ora.com (rubble.west.ora.com [198.112.209.17]) by ruby.ora.com (8.6.8/8.6.4) with SMTP id IAA12779; Sat, 16 Jul 1994 08:20:45 -0400 Received: by rubble.west.ora.com (4.1/SMI-4.1+JP-2.5) id AA03638; Sat, 16 Jul 94 05:20:09 PDT From: Jerry Peek Reply-To: jerry@ora.com X-Mailer: MH 6.8.3 To: Olly Stephens Cc: majordomo-users@GreatCircle.COM Subject: Re: multiple hierarchical lists In-Reply-To: Message from Olly Stephens of "Fri, 15 Jul 1994 11:58:48 -0700." <9407151858.AA29248@dylan.zycad.com> Date: Sat, 16 Jul 1994 05:20:08 -0700 Message-Id: <3637.774361208@rubble.west.ora.com> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I have just started to set-up lists of the form: > > -announce - announcements for > -users - forum for discussion about > -internal - forum for discussion about restricted > to employees only. > > I want the announce list to also post to the users list, and the users list > to also post to the internal list. ...deleted... > Now, in addition, I want to restrict any one person (in other words any one > e-mail address) to only appearing in one of the three lists. > > Thus, my questions are: > > a) how can I automatically disallow multiple subscriptions to a set of lists? Whew. The subscription code is set up to check just one list at a time, I think. IMHO, it'd be easier to run a nightly cron job that compares the subscribers of all three lists. If you find a subscriber on more than one list, unsubscribe them from the least-used list (either announce or users). Also, send the subscriber an automated note explaining what was done. > c) can I automatically maintain the "one list per address mechanism" > i.e. can I change it so it sends the approval person a message > of the form: > > > joe_bloggs@dom.ain has requested subscription to group -users > > > > (he is currently subscribed to -announce) > > And make it so that if the approval person approves it, he is automatically > removed from -announce. That's something the cron job could mail to the approval person. But... unless you set up some kind of mail-enabled application that prompts the approval person for each message... seems like it'd be easier for the approval person to just send the subscribe/unsubscribe stuff by hand with the standard Majordomo commands. Or I guess you could hack the "approve" script to do what you want. --Jerry Peek, jerry@ora.com From majordomo-users-owner Sat Jul 16 17:21:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA17434; Sat, 16 Jul 1994 17:21:23 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA17428; Sat, 16 Jul 1994 10:21:12 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id MAA16051; Sat, 16 Jul 1994 12:25:54 -0500 Date: Sat, 16 Jul 1994 12:25:54 +0100 From: "Robert A. Hayden" Subject: Duplication problem To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am having a very annoying problem with random postings appearing twice on my majordomo lists. I made two changes before this started happening and I am trying to explore them both. A) I converted from smail to sendmail 8.6.9 B) I started digesting on two of my lists (the ones that are duplicating themselves) I've sent an identical description of this problem to the sendmail forums, and I want to approach the majordomo angle here. As I said, randomly I'll get one message that will appear twice. The headers of this message are identical, and as far as I can tell from the sendmail log, only one copy of being locally delivered (but then again, reading the sendmail log isn't exactly easy). As the problem, assuming it is majordomo, has to do with digesting, I am including a copy of the relevant portions of /etc/aliases for one digested list. Is there anything wrong with this entry that might cause this duplication problem? -------------------- /etc/aliases abstract ---------------------- listname: "|/home/majordomo/wrapper resend -R -l listname -h \ vorlon.mankato.msus.edu -r listname listname-outgoing" owner-listname: hayden@vorlon.mankato.msus.edu listname-owner: hayden@vorlon.mankato.msus.edu listname-approval: hayden@vorlon.mankato.msus.edu listname-outgoing::include:/home/majordomo/lists/listname, "| /home/majordomo/wrapper digest -r -C -l listname-digest \ listname-digest-outgoing", listname-digest:listname listname-digest-outgoing::include:/home/majordomo/lists/listname-digest owner-listname-digest:owner-listname owner-listname-digest-outgoing:owner-listname listname-digest-approval:owner-listname ----------- end abstract ----------- Thanks for your help. ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else, dammit -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GAT d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From majordomo-users-owner Sat Jul 16 20:48:45 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA18446; Sat, 16 Jul 1994 20:48:45 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA18440; Sat, 16 Jul 1994 13:48:34 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA11789 (5.65c/IDA-1.4.4 for ); Sat, 16 Jul 1994 16:51:18 -0400 Message-Id: <199407162051.AA11789@cs.umb.edu> To: "Robert A. Hayden" Cc: Majordomo Users Subject: Re: Duplication problem In-Reply-To: Your message of "Sat, 16 Jul 1994 12:25:54 BST." Date: Sat, 16 Jul 1994 16:51:17 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , "Robert A. Hayden" writes: >I am having a very annoying problem with random postings appearing twice >on my majordomo lists. I made two changes before this started happening >and I am trying to explore them both. [..] >As I said, randomly I'll get one message that will appear twice. The >headers of this message are identical, and as far as I can tell from the >sendmail log, only one copy of being locally delivered (but then again, >reading the sendmail log isn't exactly easy). Are you the only person getting a second copy of the message? Or is the entire list getting multiple copies? Were these letters being sent to multiple addresses? For example, does your address, and the lists address appear in the message, if so you will get two copies of the message. One via direct mail, and one copy via the mailing list. Does a particular originator (site, person or mailer) show up more often than any other? Are all of the received headers on the messages identical as well? I have seen multiple list submissions before and it almost always was a result of some upstream site crashing without properly noting that it had already delivered the message to the list. Usually the two messages differened in the received headers put on by the local sendmail. >As the problem, assuming it is majordomo, has to do with digesting, I am >including a copy of the relevant portions of /etc/aliases for one >digested list. Is there anything wrong with this entry that might cause >this duplication problem? > > [aliases insert elided] Well it looked ok to me. -- 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 Sat Jul 16 20:55:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA18472; Sat, 16 Jul 1994 20:55:38 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA18466; Sat, 16 Jul 1994 13:55:29 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA12023 (5.65c/IDA-1.4.4 for ); Sat, 16 Jul 1994 16:58:34 -0400 Message-Id: <199407162058.AA12023@cs.umb.edu> To: "Robert A. Hayden" Cc: Majordomo Users Subject: Re: A couple more question on digesting In-Reply-To: Your message of "Mon, 11 Jul 1994 21:38:31 BST." Date: Sat, 16 Jul 1994 16:58:33 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , "Robert A. Hayden" writes: >For the list I have, there is a directory _listname-digest.archive_ where >the completed digests are being stored, but I also noticed that there is >a file forming called _listname-digest.archive.9407_ what is growing in >size and contains all of the postings to the list since digesting was >started, and when the digest is completed, this file doesn't erase or >anything and just continues to append messages. > >I am assuming (perhaps wrong) that the following alias entry is what is >creating this file: You aren't wrong. The archive entry is creating the monthy archive file 9407. >listname-outgoing::include:/home/majordomo/lists/listname, > "| /home/majordomo/wrapper digest -r -C -l listname-digest \ > listname-digest-outgoing", > "| /home/majordomo/wrapper archive2.pl -a -m -f \ > /home/majordomo/lists/listname-digest.archive" > >Is the archive2.pl entry necessary? Digest archiving occurs automatically as a side effect of running digest. I hope to decouple that in the next release. In the alias above, you are ceeating your own digest for the listname mailing list, but you are putting it into the listname-digest archive directory rather than the listname archive directory. If you change the: /home/majordomo/lists/listname-digest.archive" to be: /home/majordomo/lists/listname.archive" You will have a monthly archive of all of the traffic on the list suitable for indexing with the contributed scripts. I don't think that the indexing scripts work properly with digest formatted files. >Am I doing something wrong? Arguably yes, you are mixing archives for the digest and direct mailing lists. If you are using private-get, people on the direct list can't access the archives in the digest archive area, and there is no archive for the direct list. -- 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 Sat Jul 16 21:26:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA18788; Sat, 16 Jul 1994 21:26:44 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA18781; Sat, 16 Jul 1994 14:26:33 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA13303 (5.65c/IDA-1.4.4 for ); Sat, 16 Jul 1994 17:29:48 -0400 Message-Id: <199407162129.AA13303@cs.umb.edu> To: Olly Stephens Cc: majordomo-users@greatcircle.com Subject: Re: multiple hierarchical lists In-Reply-To: Your message of "Fri, 15 Jul 1994 11:58:48 PDT." <9407151858.AA29248@dylan.zycad.com> Date: Sat, 16 Jul 1994 17:29:47 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9407151858.AA29248@dylan.zycad.com>, Olly Stephens writes: >Now, in addition, I want to restrict any one person (in other words any one >e-mail address) to only appearing in one of the three lists. > >Thus, my questions are: > > a) how can I automatically disallow multiple subscriptions to a set > of lists? You can't. The cron job script that somebody else recommended is your best bet. > b) in the case of the internal list, can I make it non-approved subscrition > and include some checking mechanism which only allows people from my > domain? If the lists are closed, you could build a tool that would include the checking mechanism for a local domain. Howver that assumes that people at your site don't leave forwarding addresses when they leave. > c) can I automatically maintain the "one list per address mechanism" > i.e. can I change it so it sends the approval person a message > of the form: > > > joe_bloggs@dom.ain has requested subscription to group -users > > > > (he is currently subscribed to -announce) > > And make it so that if the approval person approves it, he is > automatically removed from -announce. Well it is only perl code, so you could implement just about anything with enough time/energy. > c) because the lists are closed, someone like me (who is on the internal > list) cannot send mail to the users list (correct?). How can I make it > so that the subscription testing on a post knows about the hierarchy and > allows this type of action. No. closed only affects how subscriptions are done. It idesn't affect who can post to the list. The moderator or restrict_post variables are responsible for that. > OR: > > a) am I going about this totally wrong? this stuff is brand new to me No, your not going about it all wrong. Heirarchical lists are something that majordomo doesn't address currently. I have done some thinking about it and a suggested scheme was posted to majordomo-workers a while ago. But it doesn't work in general since it counts on having comments in the list file when it processes it. Just out of curiosity, what is the worst that could happen if somebody doesn't follow directions and subscribes to 2 or 3 of the 3 heirarchical lists. Just a bit more email traffic? Then end of the civilized universe? Solving the particular problem of multiple subscribes seems to be a lot of work for little gain. Sending the multiply subscribed person a nice form message with the output of "which" at the end should straighten them out I would think. -- 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 Sat Jul 16 22:20:11 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA19185; Sat, 16 Jul 1994 22:20:11 GMT Received: from sparc by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA19179; Sat, 16 Jul 1994 15:20:01 -0700 Received: by sparc (5.0/SMI-SVR4) id AA20827; Sat, 16 Jul 1994 19:21:17 +0400 From: smacleod@sparc.uccb.ns.ca (Steve MacLeod) Message-Id: <9407162221.AA20827@sparc> Subject: Security and lists ... To: majordomo-users@greatcircle.com Date: Sat, 16 Jul 1994 19:21:17 -0300 (ADT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 409 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk HI ... I was wondering if I could set up some security with my lists ... I am wanting to remove the ability for anyone who has an account on my machine to browse any of the lists I set up ... currently all lists are set up 664 ... is the world read attribute really necessary ... all of my list processes are either run by root or the owner majordomo ... group is majordom in all cases ... Thanks Steve From majordomo-users-owner Sat Jul 16 22:31:48 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA19246; Sat, 16 Jul 1994 22:31:48 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA19240; Sat, 16 Jul 1994 15:31:40 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id RAA18588; Sat, 16 Jul 1994 17:36:23 -0500 Date: Sat, 16 Jul 1994 17:36:23 +0100 From: "Robert A. Hayden" Subject: Re: Duplication problem To: "John P. Rouillard" cc: Majordomo Users In-Reply-To: <199407162051.AA11789@cs.umb.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Sat, 16 Jul 1994, John P. Rouillard wrote: > Are you the only person getting a second copy of the message? Or is > the entire list getting multiple copies? The entire list is getting them. > Were these letters being sent to multiple addresses? I thought of that, but no. I've had my own mailings to the list duplicated. > Does a particular originator (site, person or mailer) show up more > often than any other? No, it appears completely random. > Are all of the received headers on the messages identical as well? They appear to be identical, at least what I can see here. > Well it looked ok to me. Hmm. If it's not majordomo, then it must be sendmail. Time to go find a Bat Book. ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else, dammit -=-=-=-=-=-=-=- (GEEK CODE 2.0) GJ/CM d- h-- s-:++>s-:+ g+ p? au+ a- w++ v* c++(++++) UL++++$ P+>++ L++$ 3- N+++ K+++ W M+ V-- -p+(---)>$ Y++ t+ 5++ j r+++$ G- v+ b D+ b--- e+>++(*) u** h* f r-->+++ !n y++** From majordomo-users-owner Sun Jul 17 03:54:03 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id DAA20276; Sun, 17 Jul 1994 03:54:03 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA20270; Sat, 16 Jul 1994 20:53:53 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id WAA01021; Sat, 16 Jul 1994 22:58:42 -0500 Date: Sat, 16 Jul 1994 22:58:42 +0100 From: "Robert A. Hayden" Subject: Re: Duplication problem (fwd) To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk This appears to have been mistakenly sent to just me. ---------- Forwarded message ---------- Date: Sat, 16 Jul 94 21:19:35 CDT From: Larry Sheldon To: "Robert A. Hayden" Subject: Re: Duplication problem Robert Hayden, continuing the discussion, said: > On Sat, 16 Jul 1994, John P. Rouillard wrote: > > > Are you the only person getting a second copy of the message? Or is > > the entire list getting multiple copies? > > The entire list is getting them. > > > Were these letters being sent to multiple addresses? > > I thought of that, but no. I've had my own mailings to the list > duplicated. > > > Does a particular originator (site, person or mailer) show up more > > often than any other? > > No, it appears completely random. > > > Are all of the received headers on the messages identical as well? > > They appear to be identical, at least what I can see here. > > > Well it looked ok to me. > > Hmm. If it's not majordomo, then it must be sendmail. Time to go find a > Bat Book. We have a situation here where things at times look a little like what RH describes--only not every body gets the dupes--and the ones that do, may get many. Problem seems to be the sendmail that HP packs in H-PUX does not handle (all?) I/O errors--given a mail piece with local addresses A, B, C, D, E, F, . . . X, Y, and Z--if "X" is over-quota, A-W will get a new copy of the piece every fifteen minutes. (Position in the address string is not relevant, "sendmail" croaks on the over-quota, after delivering all before the problem, and none after it. And in croaking, leaves the whole shebang in the queue. This analysis be somebody who has had trouble getting past the Preface in the Bat Book. -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . . - L. F. (Larry) Sheldon, Jr. - . Unix Systems Administration . - Creighton University Computer Center-Old Gym Most of us can do more - . 2500 California Plaza than we think we can, . - Omaha, Nebraska, U.S.A. 68178 but usually less than - . lsheldon@creighton.edu we think we do. . - 402 280-2254 (work) - . 402 977-2946 (pager) "Bits & Pieces" . - 402 332-4622 (residence) - . . .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Sun Jul 17 06:51:51 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA21556; Sun, 17 Jul 1994 06:51:51 GMT Received: from protocol.zycad.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA21550; Sat, 16 Jul 1994 23:51:40 -0700 Received: from zycad.zycad.com by protocol.zycad.com (4.1/SMI-4.1) id AA09752; Sun, 17 Jul 94 02:54:40 EDT Received: from dylan.zycad.com by zycad.zycad.com (4.1/SMI-4.1) id AA14028; Sat, 16 Jul 94 23:55:48 PDT Received: from localhost by dylan.zycad.com (4.1/SMI-4.1) id AA05906; Sat, 16 Jul 94 23:52:57 PDT Message-Id: <9407170652.AA05906@dylan.zycad.com> To: majordomo-users@greatcircle.com Subject: resolving local host names Date: Sat, 16 Jul 1994 23:52:57 -0700 From: Olly Stephens Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk How can I munge addresses from local users which come in in the form "user@machine" into "user@dom.ain"? I want to do this because I don't want to restrict local subscribers to our lists to have to only post from the machine they subscribed from (like many other places, I assume, we tend to machine-hop quite often around here) I looked at the "mungedomain" variable but it doesn't say it copes with this form (and a brief scan of the code failed to locate the munging procedure) If this can be done easiest by modifying sendmail (or something else outside of majordomo, please let me know) Also, can I specify wildcards in my restrict_post files? It would be nice to be able to restrict postings to "*@dom.ain" - make it easy to set up internal lists or lists which were "read-only" to the outside world. Olly From majordomo-users-owner Sun Jul 17 14:04:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA24023; Sun, 17 Jul 1994 14:04:17 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA24017; Sun, 17 Jul 1994 07:04:07 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA25714 (5.65c/IDA-1.4.4 for ); Sun, 17 Jul 1994 10:06:55 -0400 Message-Id: <199407171406.AA25714@cs.umb.edu> To: Olly Stephens Cc: majordomo-users@greatcircle.com Subject: Re: resolving local host names In-Reply-To: Your message of "Sat, 16 Jul 1994 23:52:57 PDT." <9407170652.AA05906@dylan.zycad.com> Date: Sun, 17 Jul 1994 10:06:54 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9407170652.AA05906@dylan.zycad.com>, Olly Stephens writes: > >How can I munge addresses from local users which come in in the form >"user@machine" into "user@dom.ain"? > >I want to do this because I don't want to restrict local subscribers to >our lists to have to only post from the machine they subscribed from (like >many other places, I assume, we tend to machine-hop quite often around here) > >I looked at the "mungedomain" variable but it doesn't say it copes with >this form (and a brief scan of the code failed to locate the munging >procedure) It doesn't. Mungedomain (and indeed most of majordomo) assumes fully qualified domain addresses. >If this can be done easiest by modifying sendmail (or something else outside >of majordomo, please let me know) Yup. change your sendmail.cf to always provide a FQDN for email addresses. >Also, can I specify wildcards in my restrict_post files? It would be >nice to be able to restrict postings to "*@dom.ain" - make it easy to >set up internal lists or lists which were "read-only" to the outside world. Nope. The restrict post files are handled by &addr_match (which is where mungedomain is implemented), so it only handles real addresses. There may be some changes in access list mechanisms in the future, so I would expect that restrict_post will be folded into a more general access mechanism. -- 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 Sun Jul 17 17:21:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA24511; Sun, 17 Jul 1994 17:21:19 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA24504; Sun, 17 Jul 1994 10:21:08 -0700 Message-Id: <199407171721.KAA24504@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.37.109.11/16.2) id AA044715861; Sun, 17 Jul 1994 12:24:21 -0500 From: Larry Sheldon Subject: Re: Duplication problem (fwd) To: majordomo-users@greatcircle.com Date: Sun, 17 Jul 94 12:24:21 CDT In-Reply-To: ; from "Robert A. Hayden" at Jul 16, 94 10:58 pm Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > From majordomo-users-owner@GreatCircle.COM Sun Jul 17 12:15 CDT 1994 > Received: from pigeon.creighton.edu by bluejay.creighton.edu with SMTP > (1.37.109.11/16.2) id AA029105346; Sun, 17 Jul 1994 12:15:46 -0500 > Return-Path: > Received: from relay1.UU.NET by pigeon.creighton.edu with SMTP > (16.6/16.2) id AA00693; Sun, 17 Jul 94 12:15:22 -0500 > Received: from mycroft.GreatCircle.COM by relay1.UU.NET with SMTP > (relay) id QQwywu19033; Sun, 17 Jul 1994 00:00:15 -0400 > Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) > id DAA20276; Sun, 17 Jul 1994 03:54:03 GMT > Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) > id UAA20270; Sat, 16 Jul 1994 20:53:53 -0700 > Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id WAA01021; Sat, 16 Jul 1994 22:58:42 -0500 > Date: Sat, 16 Jul 1994 22:58:42 +0100 > From: "Robert A. Hayden" > Subject: Re: Duplication problem (fwd) > To: Majordomo Users > Message-Id: > Mime-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII > Sender: Majordomo-Users-Owner@GreatCircle.COM > Precedence: bulk > Status: RO > > This appears to have been mistakenly sent to just me. > > ---------- Forwarded message ---------- > Date: Sat, 16 Jul 94 21:19:35 CDT > From: Larry Sheldon > To: "Robert A. Hayden" > Subject: Re: Duplication problem > > Robert Hayden, continuing the discussion, said: > > > On Sat, 16 Jul 1994, John P. Rouillard wrote: > > > > > Are you the only person getting a second copy of the message? Or is > > > the entire list getting multiple copies? > > > > The entire list is getting them. > > > > > Were these letters being sent to multiple addresses? > > > > I thought of that, but no. I've had my own mailings to the list > > duplicated. > > > > > Does a particular originator (site, person or mailer) show up more > > > often than any other? > > > > No, it appears completely random. > > > > > Are all of the received headers on the messages identical as well? > > > > They appear to be identical, at least what I can see here. > > > > > Well it looked ok to me. > > > > Hmm. If it's not majordomo, then it must be sendmail. Time to go find a > > Bat Book. > > We have a situation here where things at times look a little like what RH > describes--only not every body gets the dupes--and the ones that do, may > get many. > > Problem seems to be the sendmail that HP packs in H-PUX does not handle > (all?) I/O errors--given a mail piece with local addresses A, B, C, D, E, > F, . . . X, Y, and Z--if "X" is over-quota, A-W will get a new copy of the > piece every fifteen minutes. (Position in the address string is not > relevant, "sendmail" croaks on the over-quota, after delivering all before > the problem, and none after it. And in croaking, leaves the whole shebang > in the queue. > > This analysis be somebody who has had trouble getting past the Preface > in the Bat Book. > > -- > -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- > . . > - L. F. (Larry) Sheldon, Jr. - > . Unix Systems Administration . > - Creighton University Computer Center-Old Gym Most of us can do more - > . 2500 California Plaza than we think we can, . > - Omaha, Nebraska, U.S.A. 68178 but usually less than - > . lsheldon@creighton.edu we think we do. . > - 402 280-2254 (work) - > . 402 977-2946 (pager) "Bits & Pieces" . > - 402 332-4622 (residence) - > . . > .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. > > -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . . - L. F. (Larry) Sheldon, Jr. - . Unix Systems Administration . - Creighton University Computer Center-Old Gym Most of us can do more - . 2500 California Plaza than we think we can, . - Omaha, Nebraska, U.S.A. 68178 but usually less than - . lsheldon@creighton.edu we think we do. . - 402 280-2254 (work) - . 402 977-2946 (pager) "Bits & Pieces" . - 402 332-4622 (residence) - . . .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Sun Jul 17 20:05:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA25936; Sun, 17 Jul 1994 20:05:12 GMT Received: from bluejay.creighton.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA24576; Sun, 17 Jul 1994 10:27:06 -0700 Message-Id: <199407171727.KAA24576@mycroft.GreatCircle.COM> Received: by bluejay.creighton.edu (1.37.109.11/16.2) id AA052596223; Sun, 17 Jul 1994 12:30:23 -0500 From: Larry Sheldon Subject: Re: Duplication problem (fwd) To: majordomo-users@greatcircle.com Date: Sun, 17 Jul 94 12:30:22 CDT Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Robert Hayden then said: > This appears to have been mistakenly sent to just me. Of the lists I still subscribe-to, this and one other seem to me to behave rudely--a reply goes to the author, instead of back to the list. And when I am tired I forget to go to the un-necessaary effort (which is not even possible for some of our customers) of examining the headers to see where the replay is going to go. Why is this? > > ---------- Forwarded message ---------- > Date: Sat, 16 Jul 94 21:19:35 CDT > From: Larry Sheldon > To: "Robert A. Hayden" > Subject: Re: Duplication problem > > Robert Hayden, continuing the discussion, said: > > > On Sat, 16 Jul 1994, John P. Rouillard wrote: > > > > > Are you the only person getting a second copy of the message? Or is > > > the entire list getting multiple copies? > > > > The entire list is getting them. > > > > > Were these letters being sent to multiple addresses? > > > > I thought of that, but no. I've had my own mailings to the list > > duplicated. > > > > > Does a particular originator (site, person or mailer) show up more > > > often than any other? > > > > No, it appears completely random. > > > > > Are all of the received headers on the messages identical as well? > > > > They appear to be identical, at least what I can see here. > > > > > Well it looked ok to me. > > > > Hmm. If it's not majordomo, then it must be sendmail. Time to go find a > > Bat Book. > > We have a situation here where things at times look a little like what RH > describes--only not every body gets the dupes--and the ones that do, may > get many. > > Problem seems to be the sendmail that HP packs in H-PUX does not handle > (all?) I/O errors--given a mail piece with local addresses A, B, C, D, E, > F, . . . X, Y, and Z--if "X" is over-quota, A-W will get a new copy of the > piece every fifteen minutes. (Position in the address string is not > relevant, "sendmail" croaks on the over-quota, after delivering all before > the problem, and none after it. And in croaking, leaves the whole shebang > in the queue. > > This analysis be somebody who has had trouble getting past the Preface > in the Bat Book. > > -- > -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- > . . > - L. F. (Larry) Sheldon, Jr. - > . Unix Systems Administration . > - Creighton University Computer Center-Old Gym Most of us can do more - > . 2500 California Plaza than we think we can, . > - Omaha, Nebraska, U.S.A. 68178 but usually less than - > . lsheldon@creighton.edu we think we do. . > - 402 280-2254 (work) - > . 402 977-2946 (pager) "Bits & Pieces" . > - 402 332-4622 (residence) - > . . > .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. > > -- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- . . - L. F. (Larry) Sheldon, Jr. - . Unix Systems Administration . - Creighton University Computer Center-Old Gym Most of us can do more - . 2500 California Plaza than we think we can, . - Omaha, Nebraska, U.S.A. 68178 but usually less than - . lsheldon@creighton.edu we think we do. . - 402 280-2254 (work) - . 402 977-2946 (pager) "Bits & Pieces" . - 402 332-4622 (residence) - . . .-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-. From majordomo-users-owner Mon Jul 18 00:05:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA28194; Mon, 18 Jul 1994 00:05:12 GMT Received: from bosnia.pop.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA27423; Sun, 17 Jul 1994 15:25:35 -0700 Received: from localhost (barr@localhost) by bosnia.pop.psu.edu (8.6.9/8.6.9) with ESMTP id SAA05642 for ; Sun, 17 Jul 1994 18:28:58 -0400 Message-Id: <199407172228.SAA05642@bosnia.pop.psu.edu> To: majordomo-users@greatcircle.com Subject: reply vs. reply In-reply-to: Your message of "Sun, 17 Jul 1994 12:30:22 CDT." <199407171727.KAA24576@mycroft.GreatCircle.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: Sun, 17 Jul 1994 18:28:56 -0400 From: David Barr Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199407171727.KAA24576@mycroft.GreatCircle.COM>, Larry Sheldon write s: >Of the lists I still subscribe-to, this and one other seem to me to >behave rudely--a reply goes to the author, instead of back to the list. And >when I am tired I forget to go to the un-necessaary effort (which is not >even possible for some of our customers) of examining the headers to see >where the replay is going to go. This is the way things are supposed to work. Most every mail user agent I have used has two "reply" functions -- one to reply to everyone and one to reply just to the original sender. Some il-conceived list software (cough *LISTSERV* cough) configures things such that you are *forced* to reply back to the list. If people's user agents cannot reply to the list again without doing some work then it's pretty clear that their software is broken, not Majordomo. --Dave From majordomo-users-owner Mon Jul 18 22:25:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA11534; Mon, 18 Jul 1994 22:25:25 GMT Received: from netcom.netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA11528; Mon, 18 Jul 1994 15:25:17 -0700 Received: by netcom.netcom.com (8.6.8.1/Netcom) id PAA04877; Mon, 18 Jul 1994 15:28:52 -0700 Date: Mon, 18 Jul 1994 15:28:52 -0700 (PDT) From: Dick Moores Subject: My list of Majordomos 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 These are from my .addressbook. Any additions or corrections? mdac mdac majordomo@acpub.duke.edu mdb mdb majordomo@baylisa.org mdbcs mdbcs majordomo@bcs.org mdbio mdbio majordomo@biome.bio.ns.ca mdbj mdbj majordomo@bluejay.creighton.edu mdbol mdbol majordomo@bolis.sf-bay.org mdc mdc majordomo@connect.com.au mdcac mdcac majordomo@cac.washington.edu mdcc mdcc majordomo@cc.gatech.edu mdcee mdcee majordomo@cee.hw.ac.uk mdch mdch majordomo@chicago.com mdchron mdchron majordomo@chron.com mdcis mdcis majordomo@cis.ufl.edu mdcoo mdcoo majordomo@coombs.anu.edu.au mddi mddi majordomo@di.ufpe.br mddiss mddiss majordomo@disserv.stu.umn.edu mdds mdds majordomo@dorsai.org mdengr mdengr listserv@engr.uark.edu mdg mdg majordomo@gemstar.com mdgc mdgc majordomo@greatcircle.com mdh mdh majordomo@halcyon.com mdhpa mdhpa majordomo@hpa.ph.man.ac.uk mdhub mdhub majordomo@hub.terc.edu mdins mdins majordomo@ins.com mdis mdis majordomo@is.internic.net mdisig mdisig majordomo@isig.mit.edu mdlerc mdlerc majordomo@lerc.nasa.gov mdlist mdlist majordomo@list.stanford.edu mdlr mdlr majordomo@losrios.cc.ca.us mdm mdm majordomo@mcs.net mdmail mdmail majordomo@mail.msen.com mdmarsh mdmarsh majordomo@marsh.cts.com mdmath mdmath majordomo@math.ohio-state.edu mdmaths mdmaths majordomo@maths.ex.ac.uk mdmlo mdmlo majordomo@mlo.dec.com mdmp mdmp majordomo@marketplace.com mdmtu mdmtu majordomo@mtu.edu mdmys mdmys majordomo@mystech.com mdn mdn majordomo@netcom.com mdnet mdnet majordomo@netmgrs.co.uk mdnmrc mdnmrc majordomo@nmrc.ucc.ie mdoi mdoi majordomo@oi.uchicago.edu mdornl mdornl majordomo@ornl.gov mdp mdp majordomo@plts.org mdpg mdpg majordomo@pangea.com mdpinus mdpinus majordomo@pinus.slu.se mdq mdq majordomo@queernet.org mdreswi mdreswi majordomo@reswi.en.open.de mdshell mdshell majordomo@shell.portal.com mdsod mdsod majordomo@sodium.mps.ohio-state.edu mdsol mdsol majordomo@sol.acs.uwosh.edu mdsun mdsun majordomo@sun-lamp.cs.berkeley.edu mdsvc mdsvc majordomo@svcdudes.com mdt mdt majordomo@traffic.engr.washington.edu mdtb mdtb majordomo@telebit.com mdtoad mdtoad majordomo@toad.com mdtrans mdtrans majordomo@trans2.b30.ingr.com mdu mdu majordomo@ucar.edu mdufl mdufl majordomo@ufl.edu mdumbc mdumbc majordomo@cs.umbc.edu mdun mdun majordomo@usenix.org mdunc mdunc majordomo@cs.unc.edu mdunix mdunix majordomo@unixhub.slac.stanford.edu mdup mdup majordomo@udlapvms.pue.udlap.mx mdux mdux majordomo@ux1.cso.uiuc.edu mdw mdw Majordomo@world.std.com mdwa mdwa majordomo@warren.mentorg.com mdx mdx majordomo@xmission.com mdz mdz majordomo@zilker.net From majordomo-users-owner Tue Jul 19 00:23:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA12347; Tue, 19 Jul 1994 00:23:25 GMT Received: from netcom.netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA12341; Mon, 18 Jul 1994 17:23:19 -0700 Received: by netcom.netcom.com (8.6.8.1/Netcom) id RAA23046; Mon, 18 Jul 1994 17:27:04 -0700 Date: Mon, 18 Jul 1994 17:27:04 -0700 (PDT) From: Dick Moores Subject: Re: My list of Majordomos 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 > What's your list for? I've already had several responses with additions for my list, but also a couple like the above. I should have added that I'm just trying to keep track of the Majordomos out there in hopes of finding interesting lists. I also send the list to anyone who requests it, but I'm really just doing it for myself. Dick Moores From majordomo-users-owner Tue Jul 19 00:41:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA12534; Tue, 19 Jul 1994 00:41:42 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA12527; Mon, 18 Jul 1994 17:41:31 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id TAA18038; Mon, 18 Jul 1994 19:46:55 -0500 Date: Mon, 18 Jul 1994 19:46:55 +0100 From: "Robert A. Hayden" Subject: Update on duplication bug To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I tried to CC: this from comp.mail.sendmail, but it didn't appear to work. --------------------------------------------------------------------------- Last week I posted describing a problem I was having with some messages mailed to my majordomo lists being suddenly duplicated and send out twice with identical headers and only one entry in the sendmail log. This is a quick update. ----------------- I got to wondering if the queueing mechanism might be causing the problem (I was running sendmail as "/usr/lib/sendmail -bd -q10m"). I thought perhaps that when the queue clearning invoked, the 10-minutes-previous incarnation was still running, screwing up locks or somethng and duplicating any mail that poured in (ie, sending it to both processes). Or perhaps somethign else in there. So I reset sendmail to run as "/usr/lib/sendmail -bd -q45m". Now, I am still getting duplicates, but importantly, I am getting fewer of them and they are spaced farther apart. This leads me to believe that something might be incorrect with regards to the mechanisms that exist to clear out the queue that causes any mail passing through to be duplicated. -> UPDATE SINCE ORIGNAL POSTING -> I tested by sending a message to a mailing list, and then -> invoking "/usr/lib/sendmail -q", this immediately caused a -> second message to get delivered. I am definately having this problem with majordomo. I am having inconsistent problems with other mail, and I cannot be sure if the problem is this bug or simply improper addressing on the part of the sender. Can anyone thing of what might be causing this problem? The system, once again, is Linux 1.1.13 using sendmail 8.6.9 -- ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else, dammit -=-=-=-=-=-=-=- (GEEK CODE 2.1) GJ/CM d- H-- s-:++>s-:+ g+ p? au+ a- w++ v* C++(++++) UL++++$ P+>++ L++$ 3- E---- N+++ K+++ W M+ V-- -po+(---)>$ Y++ t+ 5+++ j R+++$ G- tv+ b+ D+ B--- e+>++(*) u** h* f r-->+++ !n y++** From majordomo-users-owner Tue Jul 19 01:30:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id BAA13105; Tue, 19 Jul 1994 01:30:33 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA13099; Mon, 18 Jul 1994 18:30:23 -0700 Received: by netcom.com (8.6.8.1/SMI-4.1/Netcom) id SAA01873; Mon, 18 Jul 1994 18:31:10 -0700 Date: Mon, 18 Jul 1994 18:31:10 -0700 (PDT) From: James Cook Subject: Re: My list of Majordomos To: Dick Moores cc: majordomo-users@GreatCircle.COM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Mon, 18 Jul 1994, Dick Moores wrote: > > What's your list for? > Private investigators, information brokers, legal/public record researchers, intelligence analysts, law/business librarians with any investigative or commercial intelligence related duties. -- ______________________________________________________________________________ James Cook * The Information Professionals List Internet: jcook@netcom.com * OSS.NET Conference Center OSS.NET: jcook@oss.net Compuserve: 76520,2727 ============================================================================== From majordomo-users-owner Tue Jul 19 04:20:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id EAA13878; Tue, 19 Jul 1994 04:20:28 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA13872; Mon, 18 Jul 1994 21:20:12 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qQ6gl-00017FC; Mon, 18 Jul 94 21:21 PDT Message-Id: To: James Cook cc: Dick Moores , majordomo-users@greatcircle.com Subject: Re: My list of Majordomos In-reply-to: Your message of Mon, 18 Jul 1994 18:31:10 -0700. Date: Mon, 18 Jul 1994 21:21:53 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > > What's your list for? > > > > Private investigators, information brokers, legal/public record > researchers, intelligence analysts, law/business librarians with any > investigative or commercial intelligence related duties. Then it's none of your damn business. You have no right to know the users of a given software package, commercial or otherwise, especially for these dubious purposes. Please remove my system from your list, or you will be hearing from my attorney. --- 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 Jul 19 04:48:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id EAA14309; Tue, 19 Jul 1994 04:48:53 GMT Received: from futureinfo.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA14303; Mon, 18 Jul 1994 21:48:37 -0700 Received: by futureinfo.com (4.1/3.1.012693-Future InfoSystems); id AA04000 for majordomo-users@GreatCircle.COM; Tue, 19 Jul 94 00:48:07 EDT Date: Tue, 19 Jul 1994 00:40:24 -0400 (EDT) From: Willem Scholten Subject: Re: My list of Majordomos To: "Roger B.A. Klorese" Cc: James Cook , Dick Moores , 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 Hey Calm Down!! Don't you know that anything traveling over the Internet is "public record" if you have stuff to hide or want to hide, go to AT&T mail network.. Everytime you sent E-mail some of us will watch it... and may just add you to another beautiful list, ofcourse you are probably also one of those openents against a 'clipper chip' to create universal but secure point to point traffic... Just think how many lists you are on without knowing about them exisiting.. (I just added you to my automatic most flamed person list, because you used the word lawyer in your mail message, so I can flame you every 30 Seconds..NOT.. get it...) So a lawsuite Hmm....On what ground???? Stop watching t.v movies and listening to the news... Overdose of O.J Simpson case.... -Willem. On Mon, 18 Jul 1994, Roger B.A. Klorese wrote: > > > > What's your list for? > > > > > > > Private investigators, information brokers, legal/public record > > researchers, intelligence analysts, law/business librarians with any > > investigative or commercial intelligence related duties. > > Then it's none of your damn business. > > You have no right to know the users of a given software package, commercial > or otherwise, especially for these dubious purposes. > > Please remove my system from your list, or you will be hearing from my > attorney. > --- > 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 Jul 19 04:52:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id EAA14368; Tue, 19 Jul 1994 04:52:20 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA14361; Mon, 18 Jul 1994 21:52:09 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qQ6mc-00017GC; Mon, 18 Jul 94 21:27 PDT Message-Id: To: Dick Moores cc: majordomo-users@greatcircle.com Subject: Re: My list of Majordomos In-reply-to: Your message of Mon, 18 Jul 1994 17:27:04 -0700. Date: Mon, 18 Jul 1994 21:27:58 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I've already had several responses with additions for my list, but also a > couple like the above. I should have added that I'm just trying to keep > track of the Majordomos out there in hopes of finding interesting lists. > I also send the list to anyone who requests it, but I'm really just doing > it for myself. > > Dick Moores As several of us have pointed out, there are not a League of Majordomos, and many of us only wish our servers punlicized in the forums we select. --- 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 Jul 19 05:07:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id FAA14587; Tue, 19 Jul 1994 05:07:20 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA14579; Mon, 18 Jul 1994 22:07:10 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qQ7QI-00017UC; Mon, 18 Jul 94 22:08 PDT Message-Id: To: Willem Scholten cc: James Cook , Dick Moores , majordomo-users@greatcircle.com Subject: Re: My list of Majordomos In-reply-to: Your message of Tue, 19 Jul 1994 00:40:24 -0400. Date: Mon, 18 Jul 1994 22:08:48 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > Don't you know that anything traveling over the Internet is "public > record" if you have stuff to hide or want to hide, go to AT&T mail > network.. That doesn't give you the right to publish a book or other list with the address in it. --- 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 Jul 19 05:09:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id FAA14612; Tue, 19 Jul 1994 05:09:09 GMT Received: from protocol.zycad.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA14606; Mon, 18 Jul 1994 22:08:53 -0700 Received: from zycad.zycad.com by protocol.zycad.com (4.1/SMI-4.1) id AA14043; Tue, 19 Jul 94 01:12:01 EDT Received: from dylan.zycad.com by zycad.zycad.com (4.1/SMI-4.1) id AA02479; Mon, 18 Jul 94 22:13:04 PDT Received: from localhost by dylan.zycad.com (4.1/SMI-4.1) id AA16930; Mon, 18 Jul 94 22:10:13 PDT Message-Id: <9407190510.AA16930@dylan.zycad.com> To: majordomo-users@greatcircle.com Subject: domain munging in "resend" Date: Mon, 18 Jul 1994 22:10:13 -0700 From: Olly Stephens Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am using the file containing the list of subscribers as the same file for restrict_post. I also have mungedomain set to yes. I had to edit "resend" to enable the domain munging when it did the restriction checking, because it wasn't doing it before. Simple change: replace (this is version 1.92) @output = grep (&addr_match($from, $_), ); on line 307 of "resend" with @output = grep (&addr_match($from, $_, (&cf_ck_bool($opt_l,"mungedomain") ? 2 : undef)), ); My question is: was the munging deliberately left out of resend for some reason that I may not be aware of? or was it just [potential] oversight? PS> the configuration comments for "restrict_post" state that the filenames can be space or colon separated. Trial and error followed by a scan of the code indicates that this is not true - they must be separated by colon, TAB or NEWLINEs. Space-separated filenames cause errors of the form 'cannot open "file1 file2"' Olly From majordomo-users-owner Tue Jul 19 06:35:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA15268; Tue, 19 Jul 1994 06:35:09 GMT Received: from grunt.ksu.ksu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA15256; Mon, 18 Jul 1994 23:34:59 -0700 From: brtmac@ksu.ksu.edu Received: from mort by grunt.ksu.ksu.edu (8.6.8/1.34) id BAA14584; Tue, 19 Jul 1994 01:36:39 -0500 Received: by mort (8.6.8/1.34) id GAA24187; Tue, 19 Jul 1994 06:36:34 GMT Date: Tue, 19 Jul 1994 06:36:34 GMT Message-Id: <199407190636.GAA24187@mort> To: "Roger B.A. Klorese" Cc: Willem Scholten , James Cook , Dick Moores , majordomo-users@GreatCircle.COM Subject: Re: My list of Majordomos In-Reply-To: References: Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Verily did Roger B. A. Klorese say on July 18, 1994: >> Don't you know that anything traveling over the Internet is "public >> record" if you have stuff to hide or want to hide, go to AT&T mail >> network.. > >That doesn't give you the right to publish a book or other list with >the address in it. Actually, it probably does. Haven't you seen the Internet Whitepages for sale in many bookstores now? It was created by watching who posts to USENET groups. If you've posted to a USENET group in the last year or two, you are probably in it. Anything that is public knowlege can be made available to the public in any form. It's known as the freedom of infromation. On the other hand. Anyone creating a list should respect the wishes of people who don't wish to be listed and not put them in the list which get's released to the public. That's just plain courtesy. Brett McCoy, UNIX Systems Administrator Computing and Network Services Kansas State University, Manhattan KS 66506 vox: (913) 532-4908 / fax: (913) 532-5914 / e-mail: brtmac@ksu.ksu.edu From majordomo-users-owner Tue Jul 19 07:17:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA15576; Tue, 19 Jul 1994 07:17:28 GMT Received: from dunx1.ocs.drexel.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA15570; Tue, 19 Jul 1994 00:17:21 -0700 Received: from DialupEudora (ts1.noc.drexel.edu [129.25.12.13]) by dunx1.ocs.drexel.edu (8.6.9/8.6.4) with SMTP id DAA11098; Tue, 19 Jul 1994 03:18:06 -0400 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 19 Jul 1994 03:19:17 -0400 To: "Roger B.A. Klorese" From: snyderra@dunx1.ocs.drexel.edu (Bob Snyder) Subject: Re: My list of Majordomos Cc: majordomo-users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk At 1:08 AM 7/19/94, Roger B.A. Klorese wrote: >> Don't you know that anything traveling over the Internet is "public >> record" if you have stuff to hide or want to hide, go to AT&T mail >> network.. > >That doesn't give you the right to publish a book or other list with >the address in it. Errrr, really? I've seen people do just that, and I haven't heard any lawsuits about it. Unless the information is incorrect, I don't see where you would have a case. If you can cite references that make this actionable, I'd like to hear them. Otherwise, theatening legal action without a case seems silly and reckless. Bob -- Bob Snyder N2KGO MIME, RIPEM mail accepted snyderra@dunx1.ocs.drexel.edu finger for RIPEM public key When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl. From majordomo-users-owner Tue Jul 19 13:06:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA17692; Tue, 19 Jul 1994 13:06:05 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA17686; Tue, 19 Jul 1994 06:05:58 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA09154 (5.65c/IDA-1.4.4 for ); Tue, 19 Jul 1994 09:08:42 -0400 Message-Id: <199407191308.AA09154@cs.umb.edu> To: Olly Stephens Cc: majordomo-users@greatcircle.com Subject: Re: domain munging in "resend" In-Reply-To: Your message of "Mon, 18 Jul 1994 22:10:13 PDT." <9407190510.AA16930@dylan.zycad.com> Date: Tue, 19 Jul 1994 09:08:41 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9407190510.AA16930@dylan.zycad.com>, Olly Stephens writes: >I am using the file containing the list of subscribers as the same file >for restrict_post. I also have mungedomain set to yes. > >I had to edit "resend" to enable the domain munging when it did the >restriction checking, because it wasn't doing it before. > >Simple change: replace (this is version 1.92) > [change deeleted] >My question is: > > was the munging deliberately left out of resend for some reason that I > may not be aware of? > > or was it just [potential] oversight? Yes. It was an oversite. Once you allow domain munging, it has to be turned on for all address checks. >PS> the configuration comments for "restrict_post" state that the filenames > can be space or colon separated. Trial and error followed by a scan of > the code indicates that this is not true - they must be separated by > colon, TAB or NEWLINEs. Space-separated filenames cause errors of the > form 'cannot open "file1 file2"' thanks for the note. Hopefully the entire mechanism will be replaced by something more flexible and useful. -- 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 Jul 19 14:26:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA18097; Tue, 19 Jul 1994 14:26:14 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA18091; Tue, 19 Jul 1994 07:25:55 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA13591 (5.65c/IDA-1.4.4 for ); Tue, 19 Jul 1994 10:28:37 -0400 Message-Id: <199407191428.AA13591@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Majordomo BOF a LISA 8 in SD Date: Tue, 19 Jul 1994 10:28:36 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Is anybody interested in scheduling a majordomo BOF at LISA 8? I would guess a one hour slot would be good. I was thinking 8-9 on Tues or Wednesday. If people are interested, I'll go through the scheduling process. If anybody else would like to volunteer to schedule the bof with the LISA people, drop me a line, and I'll forward the info. -- 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 Jul 19 14:42:51 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA18188; Tue, 19 Jul 1994 14:42:51 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA18180; Tue, 19 Jul 1994 07:42:42 -0700 Received: from localhost by netcom.com (8.6.8.1/SMI-4.1/Netcom) id HAA16141; Tue, 19 Jul 1994 07:46:24 -0700 From: Jerry Peek Reply-to: jerry@ora.com X-Mailer: MH 6.8.3 To: "Robert A. Hayden" cc: Majordomo Users Subject: Re: Update on duplication bug In-reply-to: Message from "Robert A. Hayden" of "Mon, 18 Jul 1994 19:46:55 +0100." Date: Tue, 19 Jul 1994 07:46:24 -0700 Message-ID: <16140.774629184@netcom3> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > I got to wondering if the queueing mechanism might be causing the problem > (I was running sendmail as "/usr/lib/sendmail -bd -q10m"). I thought > perhaps that when the queue clearning invoked, the 10-minutes-previous > incarnation was still running, screwing up locks or somethng and > duplicating any mail that poured in (ie, sending it to both processes). > Or perhaps somethign else in there. > > So I reset sendmail to run as "/usr/lib/sendmail -bd -q45m". If you have a long queue, my impression is that a 10-minute time is too short. We use an hour. Somewhere in the sendmail docs (or in the sendmail Nutshell Handbook) is a warning about too-short settings of -q. Your mileage may vary, but yes, don't set your queue run time too short. Please keep us (or me, at least!) in touch about what you find. --Jerry Peek, jerry@ora.com From majordomo-users-owner Tue Jul 19 09:03:59 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA19226; Tue, 19 Jul 1994 15:51:57 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA19217; Tue, 19 Jul 1994 08:51:37 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA18165 (5.65c/IDA-1.4.4 for ); Tue, 19 Jul 1994 11:54:27 -0400 Message-Id: <199407191554.AA18165@cs.umb.edu> To: Majordomo-users@greatcircle.com Subject: Re: Majordomo BOF a LISA 8 in SD (what is LISA??) In-Reply-To: Your message of "Tue, 19 Jul 1994 11:34:31 EDT." <9407191534.AA28210@enterprz.crawford.com> Date: Tue, 19 Jul 1994 11:54:26 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I just received a spate (20) of email asking, what is LISA. Here is the standard blurb. 8TH USENIX SYSTEMS ADMINISTRATION CONFERENCE (LISA VIII) ANNOUNCEMENT & CALL FOR PARTICIPATION Extended abstracts due: May 23, 1994 Symposium: September 19-23, 1994 Town and Country Hotel San Diego, California Co-sponsored by USENIX, the UNIX and Advanced Computing Systems Professional and Technical Association, and SAGE, the System Administrators Guild The annual USENIX Systems Administration Conference provides a forum in which system administrators meet to share ideas and experiences. A growing success for the previous seven years, the USENIX Systems Administration Conference is the only conference which focuses specifically on the needs of system administrators. Its scope includes system administrators from sites of all sizes and configurations. "Automation: Managing the Computer of the 90's" is the theme of this year's conference. The conference will focus on tools to help system administrators automate administration tasks and troubleshoot problems. I think conference@usenix.org can be used to get more information. -- 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 Jul 19 09:13:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA19232; Tue, 19 Jul 1994 15:52:05 GMT Received: from gw1.att.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA19210; Tue, 19 Jul 1994 08:51:22 -0700 Received: from qsun.UUCP by ig1.att.att.com id AA17336; Tue, 19 Jul 94 11:52:44 EDT Message-Id: <9407191552.AA17336@ig1.att.att.com> From: debbie@qsun.att.com (Deborah A Hamilton +1 908 949 9459) Date: 19 Jul 94 15:53:00 GMT To: "John P. Rouillard" Original-From: qsun!debbie (Deborah A Hamilton +1 908 949 9459) Original-To: "John P. Rouillard" Cc: majordomo-users@greatcircle.com Subject: Re: domain munging in "resend" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk John wrote in response to Olly Stephens: >>PS> the configuration comments for "restrict_post" state that the filenames >> can be space or colon separated. Trial and error followed by a scan of >> the code indicates that this is not true - they must be separated by >> colon, TAB or NEWLINEs. Space-separated filenames cause errors of the >> form 'cannot open "file1 file2"' > > thanks for the note. Hopefully the entire mechanism will be replaced > by something more flexible and useful. I had the same problem with restrict_post plus an additional requirement. In setting up Majordomo for use at InterNIC Directory and Database Services, I had requests to provide the ability to restrict posting only the members of the lists and (optionally) to some additional ids as well as having the ability to restrict posting to only a FEW ids. The restrict_post feature as implemented in R1.92 only allows you to restrict posting to a few ids since you can only specify one id per file. I hacked the restrict_post code in resend to search the entire file for the id, not just the first record in the file. So now if I have a list to which only list members should post, I specify "restrict_post = :.restrict" and it scans the subscription list for matches on the id. If I need to add additional ids, they get listed in the file called .restrict. Of course the drawback is still there that the .restrict file can't be modified by the list owner via email. And - I have to make sure that if the list is set for restricted_post that the following ids are in .restrict and .restrict is specified in "restrict_post =": majordomo, majordomo-owner, owner-, -owner, the list owner's email id , and (requirement by my mailer's front end), Majordomo, and Majordomo-owner. Otherwise, I ran into some very frustrating BOUNCE/APPROVE loops when majordomo-owner tried to post to the list and when -owner tried to approve the request when I had "restrict_post = " (look at what headers are generated by the announce utility). If you're interested in the hack it's attached (sorry it's not in patch format), Also - if you're going to enhance restrict_post to be more flexible, I think the above ids need to be allowed to post to the list regardless of the setting of restrict_post. - Debbie ==================================================================== Deborah Hamilton debbie@qsun.att.com InterNIC Directory and Database (908) 949-9459 Services Support AT&T Bell Laboratories ==================================================================== Code changes to resend to provide more inclusive restrict_post option: 297 if ( defined($opt_I) && defined($from) && ! defined($approved) ) { 298 local($infile) = 0; 299 300 @files = split (/[:\t\n]+/, $opt_I); 301 302 foreach $file (@files) { 303 if ($file !~ /^\//) { 304 $file = "$listdir/$file"; 305 } 306 if ( open (LISTFD, "<${file}") != 0 ) { 307 308 # DAH - Add code to read and check EVERY address in the file, not 309 # just one address - this way we can restrict posts to 310 # a list of addresses contained in a file - which _could_ be the 311 # mailing list itself. This way, if you have a number of folks 312 # that you want to restrict the posting to, you don't need a 313 # file for each address. And you can have separate files too - 314 # one for list members and non-members. Each address in the 315 # file must be separated by a newline (\n). 316 # 317 # Replacing the next line with lines marked w/ inits 318 # @output = grep (&addr_match($from, $_), ); 319 320 local(@restrict) = (); # dah 321 while( ) { # dah 322 push(@restrict, &chop_nl($_)); # dah 323 } # dah 324 @output = grep (&addr_match($from, $_), @restrict); # dah 325 326 close (LISTFD); 327 328 if ( $#output != -1 ) { 329 $infile = 1; 330 last; 331 } 332 } else { 333 die("resend: Can't open $file: $!"); 334 } 335 } 336 337 if ( $infile == 0 ) { 338 &bounce ("Non-member submission from [$from]"); 339 } 340 } 341 342 if (defined($opt_A) && ! defined($approved)) { From majordomo-users-owner Tue Jul 19 16:42:53 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA20077; Tue, 19 Jul 1994 16:42:53 GMT Received: from amdext.amd.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA20065; Tue, 19 Jul 1994 09:42:39 -0700 Received: from amdint.amd.com by amdext.amd.com with SMTP id AA26046 (5.67a/IDA-1.5+AMD for ); Tue, 19 Jul 1994 09:45:31 -0700 Received: from dvorak.amd.com by amdint.amd.com with SMTP id AA20519 (5.67a/IDA-1.5+AMD for ); Tue, 19 Jul 1994 09:45:30 -0700 Received: from sardaukar.amd.com.amd.com by dvorak.amd.com (4.1/AMDSN-1.18) id AA14247; Tue, 19 Jul 94 11:45:28 CDT Received: by sardaukar.amd.com.amd.com (4.1/AMDC-1.18) id AA09596; Tue, 19 Jul 94 11:45:31 CDT Date: Tue, 19 Jul 94 11:45:31 CDT From: boris@dvorak.amd.com (Boris Yazlovitsky) Message-Id: <9407191645.AA09596@sardaukar.amd.com.amd.com> To: majordomo-users@greatcircle.com Subject: Bounced mail Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have a question: Is there currently a built-in feature in Majordomo that handles bounced mail in an automatic way? From what I understand, for each user that a letter has bounced, the bounce command executed at the shell level puts them all in the bounces list after removing them from the original mailing list(s). Yet is there a built-in feature that does it automatically? (question repeated) Boris From majordomo-users-owner Tue Jul 19 18:44:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA21728; Tue, 19 Jul 1994 18:44:28 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA21722; Tue, 19 Jul 1994 11:44:17 -0700 Received: from lunch.asd.sgi.com by sgi.sgi.com via SMTP (940627.SGI.8.6.9/910110.SGI) id LAA09495; Tue, 19 Jul 1994 11:47:45 -0700 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:majordomo-users@GreatCircle.COM id AA12977; Tue, 19 Jul 94 11:47:43 -0700 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9407191847.AA12977@lunch.asd.sgi.com> Subject: Re: A couple more question on digesting To: rouilj@cs.umb.edu (John P. Rouillard) Date: Tue, 19 Jul 1994 11:47:42 -0700 (PDT) Cc: hayden@vorlon.mankato.msus.edu, majordomo-users@GreatCircle.COM In-Reply-To: <199407162058.AA12023@cs.umb.edu> from "John P. Rouillard" at Jul 16, 94 04:58:33 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: 687 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > >Am I doing something wrong? > > Arguably yes, you are mixing archives for the digest and direct > mailing lists. If you are using private-get, people on the direct list > can't access the archives in the digest archive area, and there is no > archive for the direct list. I solve this by symlinking the two directories and making the digest archives the only archives. They're much more conveniently sized than daily or weekly archives. And my index maker program (shameless plug) makes it easy to get just the digests (archives) you want. The index maker is contrib/makeindex.pl. -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Tue Jul 19 21:08:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA23247; Tue, 19 Jul 1994 21:08:52 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA23240; Tue, 19 Jul 1994 14:08:20 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id QAA00598; Tue, 19 Jul 1994 16:13:37 -0500 Date: Tue, 19 Jul 1994 16:13:37 +0100 From: "Robert A. Hayden" Reply-To: "Robert A. Hayden" Subject: Duplication Bug Fixed To: Majordomo Users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk It seems that I have fixed the duplication problem that I was having. I figured I'd post a report of what was wrong and just give all of you a hearty thanks for your help. Apparenly, as I reported last night, the problem was releated to the periodic attemp to deliver queued mail. As it turns out, sendmail defaulted to rewriting the queue every 10 successful deliveries. Unfortunately, if sendmail invoked itself to clear the queue, any messages that had been delivered but not deleted from the queue would get delivered again. The solution was to use the -oC1 option (or the OC option in /etc/sendmail.cf) instructng sendmail to rewrite the queue after EACH successful delivery of mail. That way when the periodic queue clearing process starts, there won't be any delivered-but-stagnant mail in the queue. Unfortunately, neither the man page nor the .ps file that comes with it is very clear on this point. Norm Aleks was kind enough to dig out his Bat Book and pass the information along. Thanks everyone to all of your suggestions and help. It was most appreciated. ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else, dammit -=-=-=-=-=-=-=- (GEEK CODE 2.1) GJ/CM d- H-- s-:++>s-:+ g+ p? au+ a- w++ v* C++(++++) UL++++$ P+>++ L++$ 3- E---- N+++ K+++ W M+ V-- -po+(---)>$ Y++ t+ 5+++ j R+++$ G- tv+ b+ D+ B--- e+>++(*) u** h* f r-->+++ !n y++** From majordomo-users-owner Wed Jul 20 11:28:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA04066; Wed, 20 Jul 1994 11:28:54 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id EAA04055; Wed, 20 Jul 1994 04:28:27 -0700 Received: from bolis by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA09354; Wed, 20 Jul 94 04:31:30 -0700 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0qQU24-0002XUC; Tue, 19 Jul 94 22:17 PDT Message-Id: From: Alan Millar Subject: Re: Bounced mail To: boris@dvorak.amd.com (Boris Yazlovitsky) Date: Tue, 19 Jul 1994 22:17:26 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <9407191645.AA09596@sardaukar.amd.com.amd.com> from "Boris Yazlovitsky" at Jul 19, 94 11:45:31 am 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: 1399 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Boris Yazlovitsky spake of these matters: > > > I have a question: > Is there currently a built-in feature in Majordomo that > handles bounced mail in an automatic way? > From what I understand, for each user that a letter > has bounced, the bounce command executed at the shell level > puts them all in the bounces list after removing them from the > original mailing list(s). Yet is there a built-in feature > that does it automatically? (question repeated) I just posted a script here in the last few weeks to do exactly this. It currently works for 1.62. I think John Roulliard made a few minor changes to get it to work on 1.92. John: did you get it to work? I'm in the process of re-vamping it to make it more open-ended. While I'm at it, here's the plan: I'm going to split it into two parts. The first part will recognize and log bounces; this program will not be tied to Majordomo in particular so it should be able to work with other list software. The second program will read the bounce log and do the Majordomo stuff to handle the subscription change. This second program could presumably have counterparts for other list management software. Comments? - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: ftp://ftp.netcom.com/pub/amillar/welcome.html Reason notwithstanding, the universe continues unabated. From majordomo-users-owner Wed Jul 20 13:05:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA04599; Wed, 20 Jul 1994 13:05:06 GMT Received: from trans2.b30.ingr.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA04584; Wed, 20 Jul 1994 06:03:51 -0700 Received: by trans2.b30.ingr.com (5.65c/1.921207) id AA04888; Wed, 20 Jul 1994 07:55:32 -0500 From: bptatro@trans2.b30.ingr.com (Brian Tatro) Message-Id: <199407201255.AA04888@trans2.b30.ingr.com> Subject: bounce problem To: Majordomo-Users@greatcircle.com Date: Wed, 20 Jul 94 7:55:31 CDT X-Mailer: ELM [version 07.05.00.00 (2.3 PL11)] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello all, I received the following message form my mailserver. Anybody have an idea what it means? The program is supposed to move the address to the Bounce list, but there is nothing in a bounces list. Forwarded message: > From root Tue Jul 19 02:10 CDT 1994 > Date: Tue, 19 Jul 1994 02:10:02 -0500 > From: MAILER-DAEMON (Mail Delivery Subsystem) > Subject: Returned mail: User unknown > Message-Id: <199407190710.AA06091@trans2.b30.ingr.com> > To: root > > ----- Transcript of session follows ----- > 550 User unknown > > ----- Unsent message follows ----- > Received: by trans2.b30.ingr.com (5.65c/1.921207) > id AA06089; Tue, 19 Jul 1994 02:10:02 -0500 > Date: Tue, 19 Jul 1994 02:10:02 -0500 > Message-Id: <199407190710.AA06089@trans2.b30.ingr.com> > To: Bounces@trans2.b30.ingr.com > From: nobody@trans2.b30.ingr.com > Subject: Bouncing email from mailing lists at trans2.b30.ingr.com > Reply-To: majordomo@trans2.b30.ingr.com > > Your address has been moved to Bounces@trans2.b30.ingr.com > from some other mailing list at trans2.b30.ingr.com > because email to you was bouncing. Rest is the usual message. -- ========================================================================= This .sig space for rent. E=mc*2 --> It's not just a good idea, It's the LAW! (186,000 Miles/Sec) Brian Tatro Senior Editor Product Translation COMPUSERVE: 72154,531 Intergraph Corporation bptatro@trans2.b30.ingr.com ========================================================================== From majordomo-users-owner Wed Jul 20 13:52:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA04874; Wed, 20 Jul 1994 13:52:38 GMT Received: from amdext.amd.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA04867; Wed, 20 Jul 1994 06:52:20 -0700 Received: from amdint.amd.com by amdext.amd.com with SMTP id AA12497 (5.67a/IDA-1.5+AMD for ); Wed, 20 Jul 1994 06:55:08 -0700 Received: from dvorak.amd.com by amdint.amd.com with SMTP id AA26885 (5.67a/IDA-1.5+AMD for ); Wed, 20 Jul 1994 06:55:07 -0700 Received: from sardaukar.amd.com.amd.com by dvorak.amd.com (4.1/AMDSN-1.18) id AA17938; Wed, 20 Jul 94 08:55:06 CDT Received: by sardaukar.amd.com.amd.com (4.1/AMDC-1.18) id AA09880; Wed, 20 Jul 94 08:55:09 CDT Date: Wed, 20 Jul 94 08:55:09 CDT From: boris@dvorak.amd.com (Boris Yazlovitsky) Message-Id: <9407201355.AA09880@sardaukar.amd.com.amd.com> To: majordomo-users@greatcircle.com Subject: Re: Bounced mail Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Quoth Alan Millar: > And verily didst Boris Yazlovitsky spake of these matters: > > I have a question: > > Is there currently a built-in feature in Majordomo that > > handles bounced mail in an automatic way? > I just posted a script here in the last few weeks to do exactly this. > > It currently works for 1.62. I think John Roulliard made a few minor > changes to get it to work on 1.92. John: did you get it to work? > > I'm in the process of re-vamping it to make it more open-ended. > > While I'm at it, here's the plan: > > I'm going to split it into two parts. The first part will recognize > and log bounces; this program will not be tied to Majordomo in particular > so it should be able to work with other list software. The second > program will read the bounce log and do the Majordomo stuff to > handle the subscription change. This second program could presumably > have counterparts for other list management software. Comments? I assume that the types of bounces this script will work for are those which bounced to the owner of the list, and that the script will be invoked from /etc/aliases, right? Therefore, if a letter sent to owner-list is not a bounce, are you then going to resend it? > - Alan Boris From majordomo-users-owner Wed Jul 20 16:22:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA06197; Wed, 20 Jul 1994 16:22:26 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA06189; Wed, 20 Jul 1994 09:22:19 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA00529 (5.65c/IDA-1.4.4 for ); Wed, 20 Jul 1994 12:25:48 -0400 Message-Id: <199407201625.AA00529@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Majordomo BOF at LISA 8 on Wednesday September 21 1994 Date: Wed, 20 Jul 1994 12:25:47 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk There will be a Majordomo BOF from 8 to 9 pm on wednesday September 21 1994. Come and curse the originators and developers of majordomo 8-). I am guessing we will have about 40 people at the BOF, but I would like a better head count to give to Lee. If you will be attending LISA, and intend to attend the bof, please reply to this message. -- 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 Jul 20 18:22:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA07458; Wed, 20 Jul 1994 18:22:58 GMT Received: from coco.ca.rop.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA07443; Wed, 20 Jul 1994 11:21:45 -0700 Received: by coco.ca.rop.edu (8.6.9/SMI-4.1) id LAA13442; Wed, 20 Jul 1994 11:19:37 -0700 Date: Wed, 20 Jul 1994 11:19:37 -0700 From: pzee@coco.ca.rop.edu (Phillip J. Zee (Majordomo maintainer)) Message-Id: <199407201819.LAA13442@coco.ca.rop.edu> To: majordomo-users@greatcircle.com Subject: help on unknown mailer error 5 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have installed majordomo 1.92 and tested it. I got the following error: echo help | /usr/lib/sendmail -v majordomo majordomo... aliased to "|/export/home/sigweb/majordomo/wrapper majordomo" majordomo: No such file or directory "|/export/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 pzee... Sent In the doc, it says the this is caused by: 1. perl script is not executable -rwxr-xr-x 1 majordom majordom 42268 Jul 20 09:15 majordomo* So, it is executable 2. the location of perl program specified withe the #! line is incorrect which perl /usr/local/bin/perl head majordomo #!/usr/local/bin/perl So, not this one either. 3. location of the wrapper looks for perl scripts is not the location where the scripts are located. Not this one either. And I executed majordomo at command line: majordomo Can't locate ctime.pl in @INC at majordomo line 53. What's wrong here? Thanks, Philip From majordomo-users-owner Wed Jul 20 18:53:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA07670; Wed, 20 Jul 1994 18:53:58 GMT Received: from colossus.cse.psu.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA07663; Wed, 20 Jul 1994 11:53:45 -0700 Received: from localhost by colossus.cse.psu.edu with SMTP id <45519>; Wed, 20 Jul 1994 14:56:22 -0400 To: pzee@coco.ca.rop.edu (Phillip J. Zee (Majordomo maintainer)) cc: majordomo-users@greatcircle.com Subject: Re: help on unknown mailer error 5 X-Work-Address: Department of Computer Science, 121A Pond Laboratory The Pennsylvania State University, University Park, PA 16802 X-Work-Phone: +1 814 863 1142 (Voice) +1 814 865 3176 (FAX) In-reply-to: Your message of Wed, 20 Jul 1994 14:19:37 EDT. <199407201819.LAA13442@coco.ca.rop.edu> Date: Wed, 20 Jul 1994 14:56:13 -0400 From: Daniel R Ehrlich Message-Id: <94Jul20.145622edt.45519@colossus.cse.psu.edu> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- >I have installed majordomo 1.92 and tested it. I got the following error: >echo help | /usr/lib/sendmail -v majordomo >majordomo... aliased to "|/export/home/sigweb/majordomo/wrapper majordomo" >majordomo: No such file or directory >"|/export/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 >pzee... Sent > >In the doc, it says the this is caused by: >1. perl script is not executable > -rwxr-xr-x 1 majordom majordom 42268 Jul 20 09:15 majordomo* > > So, it is executable > >2. the location of perl program specified withe the #! line is incorrect > > which perl >/usr/local/bin/perl > > head majordomo >#!/usr/local/bin/perl > > So, not this one either. > >3. location of the wrapper looks for perl scripts is not the location where > the scripts are located. > Not this one either. > >And I executed majordomo at command line: >majordomo >Can't locate ctime.pl in @INC at majordomo line 53. > > >What's wrong here? > It would appear that perl is not properly installed in your system. Dan Ehrlich - Systems Analyst - PSU Computer Science and Engineering "Universities should be safe havens where ruthless examination of realities will not be distorted by the aim to please or inhibited by the risk of displeasure." - Kingman Brewster 2.6 fingerprint = 5C 01 7F 57 B0 AB 68 72 04 23 B9 BD 27 AD 85 60 echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc -----BEGIN PGP SIGNATURE----- Version: 2.6 iQB1AgUBLi1zPGG7cSjuJugFAQHOfgMAwrCXQdU5aF4mmo0sEL8MXKIYIx1D9mjB g4UWlFGAVCNtYoXLMUvgb20wqInM2yR5lZ6EEOxTBTuCgH1OxUJgJ4wB9SdPVM+W cEREIVqQ+Xzxd0n1CpfDjjAX4orJLR4j =oZkM -----END PGP SIGNATURE----- From majordomo-users-owner Wed Jul 20 19:04:08 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA07821; Wed, 20 Jul 1994 19:04:08 GMT Received: from cobra.ica.luz.ve by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA07798; Wed, 20 Jul 1994 12:01:55 -0700 Received: by cobra.ica.luz.ve id AA00749 (5.67b/IDA-1.5 for Majordomo-users@greatcircle.com); Mon, 18 Jul 1994 17:45:58 -0400 From: Cosimo Stufano Message-Id: <199407182145.AA00749@cobra.ica.luz.ve> Subject: Only Lower-case lists? To: Majordomo-users@greatcircle.com Date: Mon, 18 Jul 1994 17:45:56 -0400 (HLV) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 900 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, I am installing majordomo 1.92 and decided to use both upper and lower-case letter for the lists filenames. During tests I found out that the lists where recognized by majordomo "lists" and "which" commands but that "subscribe" "who", etc. produced the message "no such list". After a couple of hours of working with the perl debugger, I found the line "$clean_list =~ tr/A-Z/a-z/;" in majordomo.pl which converts the listname to lower-case before looking for its file, and therefore not finding any mixed-case listnames. While this helps reduce users errors and works smootly in the long run, it is not enfatized in the documentation, particularly, it is not mentioned in the transcription of the chapter on majordomo of the book by Jerry Peek which comes with the distribution. I hope this comments help other users struggling to install Majordomo Cosimo Stufano From majordomo-users-owner Wed Jul 20 19:11:46 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA07870; Wed, 20 Jul 1994 19:11:46 GMT Received: from firstfloor.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA07860; Wed, 20 Jul 1994 12:11:38 -0700 Received: from et.firstfloor.COM ([198.206.195.36]) by firstfloor.COM (4.1/SMI-4.1) id AA12190; Wed, 20 Jul 94 12:15:26 PDT From: swayland@firstfloor.COM (Scott Wayland, Technical Support) To: majordomo-users@greatcircle.com Subject: help on unknown mailer error 5 Reply-To: swayland@firstfloor.COM Date: Wed, 20 Jul 94 12:15:36 PDT Message-Id: <9407201915.247A2C@et.firstfloor.COM> X-Mailer: SelectMAIL 1.1 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk We really hate to jump on any one bandwagon. But, we just finished installing majordomo and are receiving an identical error. - unknown mailer error 5. Though the spicifics appear to be different. Our error is as follows: majordomo: No such file or directory 554 "|/export/local1/majordom/bin/wrapper majordomo"... unknown mailer error 5 We have verified that all paths are correctly pointing to /export/local1/majordom/bin directories for wrapper, perl and majordomo. As well as the associated aliases per majordomo-1.92.README and majordomo.manual. Granted that this is our first experence with majordomo. We more than likley have missed something so minor that our problem could be considered user initiated, not a majordomo bug. Though its not obvious to us at this time. So, any suggestions whatsoever would be greatly appreciated from someone who has found themselves at wits-end. Thank you in advance... Scott From majordomo-users-owner Wed Jul 20 19:52:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA08352; Wed, 20 Jul 1994 19:52:20 GMT Received: from Sun.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA08340; Wed, 20 Jul 1994 12:52:08 -0700 Received: from EBay.Sun.COM (female.EBay.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA11456; Wed, 20 Jul 94 12:55:05 PDT Received: from aiki.Ebay.Sun.COM by EBay.Sun.COM (5.0/SMI-5.3) id AA23465; Wed, 20 Jul 1994 12:55:02 +0800 Received: by aiki.Ebay.Sun.COM (5.x/SMI-SVR4) id AA14136; Wed, 20 Jul 1994 12:54:57 -0700 Date: Wed, 20 Jul 1994 12:54:57 -0700 From: Kenneth.Kron@EBay.Sun.COM (Kenneth Kron - (NSG) Applications Analyst) Message-Id: <9407201954.AA14136@aiki.Ebay.Sun.COM> To: pzee@coco.ca.rop.edu, ehrlich@cse.psu.edu Subject: Re: help on unknown mailer error 5 Cc: majordomo-users@GreatCircle.COM X-Sun-Charset: US-ASCII Content-Length: 2866 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Well I may have done the same thing wrong as everyone else who is getting this error message but my work around was... majordomo:unshift(@INC, "$Path_to_Perl"); majordomo:unshift(@INC, "$homedir/bin"); majordomo:unshift(@INC, $homedir); I had to include the bin directory for some reason or other. You should set the above Path_to_Perl to the directory that contains the "converted .h files (they are converted to .pl files). You should be able to find the "near" the perl exuecutable itself. kk > From majordomo-users-owner@GreatCircle.COM Wed Jul 20 12:38 PDT 1994 > To: pzee@coco.ca.rop.edu (Phillip J. Zee (Majordomo maintainer)) > Cc: majordomo-users@GreatCircle.COM > Subject: Re: help on unknown mailer error 5 > X-Work-Address: Department of Computer Science, 121A Pond Laboratory > The Pennsylvania State University, University Park, PA 16802 > X-Work-Phone: +1 814 863 1142 (Voice) +1 814 865 3176 (FAX) > From: Daniel R Ehrlich > Content-Type: text > Content-Length: 1718 > X-Lines: 56 > > -----BEGIN PGP SIGNED MESSAGE----- > > >I have installed majordomo 1.92 and tested it. I got the following error: > >echo help | /usr/lib/sendmail -v majordomo > >majordomo... aliased to "|/export/home/sigweb/majordomo/wrapper majordomo" > >majordomo: No such file or directory > >"|/export/home/sigweb/majordomo/wrapper majordomo"... unknown mailer error 5 > >pzee... Sent > > > >In the doc, it says the this is caused by: > >1. perl script is not executable > > -rwxr-xr-x 1 majordom majordom 42268 Jul 20 09:15 majordomo* > > > > So, it is executable > > > >2. the location of perl program specified withe the #! line is incorrect > > > > which perl > >/usr/local/bin/perl > > > > head majordomo > >#!/usr/local/bin/perl > > > > So, not this one either. > > > >3. location of the wrapper looks for perl scripts is not the location where > > the scripts are located. > > Not this one either. > > > >And I executed majordomo at command line: > >majordomo > >Can't locate ctime.pl in @INC at majordomo line 53. > > > > > >What's wrong here? > > > > It would appear that perl is not properly installed in your system. > > Dan Ehrlich - Systems Analyst - PSU Computer Science and Engineering > "Universities should be safe havens where ruthless examination of realities > will not be distorted by the aim to please or inhibited by the risk of > displeasure." - Kingman Brewster > 2.6 fingerprint = 5C 01 7F 57 B0 AB 68 72 04 23 B9 BD 27 AD 85 60 > echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc > > > -----BEGIN PGP SIGNATURE----- > Version: 2.6 > > iQB1AgUBLi1zPGG7cSjuJugFAQHOfgMAwrCXQdU5aF4mmo0sEL8MXKIYIx1D9mjB > g4UWlFGAVCNtYoXLMUvgb20wqInM2yR5lZ6EEOxTBTuCgH1OxUJgJ4wB9SdPVM+W > cEREIVqQ+Xzxd0n1CpfDjjAX4orJLR4j > =oZkM > -----END PGP SIGNATURE----- > > From majordomo-users-owner Wed Jul 20 20:30:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA08802; Wed, 20 Jul 1994 20:30:31 GMT Received: from gw1.att.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA08796; Wed, 20 Jul 1994 13:30:20 -0700 Received: from qsun.UUCP by ig1.att.att.com id AA14186; Wed, 20 Jul 94 16:32:53 EDT Message-Id: <9407202032.AA14186@ig1.att.att.com> From: debbie@qsun.att.com (Deborah A Hamilton +1 908 949 9459) Date: 20 Jul 94 20:33:00 GMT Original-From: qsun!debbie (Deborah A Hamilton +1 908 949 9459) To: majordomo-users@greatcircle.com Subject: Unexpected Token Error Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have Majordomo 1.92 implemented on my server and, in general, it's behaving very well. However, I've been seeing the following error in mail sent by majordomo in response to subscribes, help, etc requests. I was wondering if anyone else had seen this error and knows what causes it. I scanned the majordomo-users archives and FAQ and haven't seen any references to it. Some users are posting mail to majordomo@dsmail.internic.net to do subscribes, request help, indexes, etc. The message gets processed but the response that gets sent to the user is not delivered due to a syntax error. The error message that comes back is (Note: owner-graph-ti is aliased to debbie@qsun.att.com): > From: postmaster@ds.internic.net > Date: Tue, 19 Jul 09:32:00 1994 > To: debbie@qsun.att.com > Subject: smtp mail failed > Status: R > > Your mail to UNCCVM.UNCC.EDU is undeliverable. > ---------- diagnosis ---------- > <<< 501 Syntax Error. Unexpected Token '@' > ---------- unsent mail ---------- >From owner-graph-ti@dsmail.internic.net Tue Jul 19 09:31:58 EDT 1994 > remote from ds > To: FMA00HBR@UNCCVM.UNCC.EDU > From: Majordomo@dsmail.internic.net > Subject: Welcome to graph-ti > Reply-To: Majordomo@dsmail.internic.net > > -- > ... rest of message This particular message was the result of a user subscribing to graph-ti@dsmail.internic.net. The rest of the message was the welcome message for graph-ti. The user never got the message, but was successfully subscribed to the list. When a message is posted to graph-ti@dsmail.internic.net, it gets forwarded to the user just fine. This particular error is happening with a few other ids and if it occurs to an id, it then occurs consistantly: the requesting id can not get a response from a majordomo command because of the "Unexpected Token" error any time it sends a message to majordomo. However - it doesn't happen to ALL the ids. I've looked at the headers generated by majordomo and resend and can't find any differences other than the ids being placed in the From: and Reply-To: lines. But - they all look legal to me. Thanks for any help in advance. -Debbie =================================================================== Deborah Hamilton debbie@qsun.att.com InterNIC Directory and Database 908-949-9459 Services Support AT&T Bell Labortories From majordomo-users-owner Wed Jul 20 20:31:41 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA08826; Wed, 20 Jul 1994 20:31:41 GMT Received: from ftp.std.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA08818; Wed, 20 Jul 1994 13:31:34 -0700 Received: from world.std.com by ftp.std.com (8.6.8.1/Spike-8-1.0) id QAA13251; Wed, 20 Jul 1994 16:35:06 -0400 Received: by world.std.com (5.65c/Spike-2.0) id AA04885; Wed, 20 Jul 1994 16:35:04 -0400 Date: Wed, 20 Jul 1994 16:35:03 -0400 (EDT) From: Houghton Mifflin Math Subject: majordomo vs. other mail-list programs To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am interested in setting up a couple mailing lists but haven't settled on a software package. I would like to get some impressions from people who have used the software as to: - how hard majordomo is to set up and use (how long it take you?) - how often bugs come up and how difficult they are to fix I would be particularly interested to hear from any of you who have tried other mailing list programs - how did they stack up in features and usability vs. majordomo? Thank you all very much for any input you can provide. I truly appreciate your consideration. :) Please send responses directly to my account at sine@world.std.com unless you think this topic is of general interest. Thanks again, mike shelton sine@world.std.com From majordomo-users-owner Wed Jul 20 23:18:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA10530; Wed, 20 Jul 1994 23:18:44 GMT Received: from rip.psg.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA10524; Wed, 20 Jul 1994 16:18:38 -0700 Received: from moncol by rip.psg.com with smtp (Smail3.1.28.1 #7) id m0qQkxH-000309C; Wed, 20 Jul 94 16:21 PDT Received: by moncol; id AA01528; Wed, 20 Jul 1994 19:21:50 -0400 Message-Id: <9407202321.AA01528@moncol> From: moncol!s0086239@moncol.monmouth.edu Date: Wed, 20 Jul 94 19:21:50 EDT To: majordomo@RIP.PSG.COM X-Mailer: fastmail [version 2.3 PL11] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk LISTS From majordomo-users-owner Thu Jul 21 01:05:07 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id BAA11091; Thu, 21 Jul 1994 01:05:07 GMT Received: from relay3.UU.NET by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA11079; Wed, 20 Jul 1994 18:04:55 -0700 Received: from uucp4.UU.NET by relay3.UU.NET with SMTP id QQwzlc12998; Wed, 20 Jul 1994 21:08:22 -0400 Received: from octela.UUCP by uucp4.UU.NET with UUCP/RMAIL ; Wed, 20 Jul 1994 21:08:10 -0400 Received: from penang.octel by octela.octel.com (4.0/SMI-4.0) id AA13559; Wed, 20 Jul 94 14:22:03 PDT Received: by penang.octel (4.1/SMI-4.1) id AA05318; Wed, 20 Jul 94 14:32:19 PDT From: octela!penang!theen@uunet.uu.net (Theen-Theen Tan) Message-Id: <9407202132.AA05318@penang.octel> Subject: Re: majordomo vs. other mail-list programs To: uunet!world.std.com!sine@uunet.uu.net (Houghton Mifflin Math) Date: Wed, 20 Jul 1994 14:32:18 -0700 (PDT) Cc: uunet!GreatCircle.COM!majordomo-users@uunet.uu.net In-Reply-To: from "Houghton Mifflin Math" at Jul 20, 94 04:35:03 pm X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1012 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > > I am interested in setting up a couple mailing lists but haven't settled > on a software package. I would like to get some impressions from people > who have used the software as to: > > - how hard majordomo is to set up and use (how long it take you?) > - how often bugs come up and how difficult they are to fix > > I would be particularly interested to hear from any of you who have tried > other mailing list programs - how did they stack up in features and > usability vs. majordomo? > > Thank you all very much for any input you can provide. I truly > appreciate your consideration. :) > > Please send responses directly to my account at sine@world.std.com unless > you think this topic is of general interest. > > Thanks again, > > mike shelton > sine@world.std.com > > > I am trying to set up a mailing list service for my school and would appreciate responses to the above article to be posted on the mailing list. Thanks! -- theen theen tcube@mills.edu or theen@octel.com From majordomo-users-owner Thu Jul 21 04:01:20 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA16484; Thu, 21 Jul 1994 09:26:27 GMT Received: from sgiblab.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id CAA16477; Thu, 21 Jul 1994 02:26:11 -0700 Received: from bolis by sgiblab.sgi.com via UUCP (931110.SGI/911001.SGI) id AA23763; Thu, 21 Jul 94 02:29:02 -0700 Received: by hock.bolis.sf-bay.org (Smail3.1.28.1 #6) id m0qQrjo-0002a3C; Wed, 20 Jul 94 23:36 PDT Message-Id: From: Alan Millar Subject: Re: Bounced mail To: boris@dvorak.amd.com (Boris Yazlovitsky) Date: Wed, 20 Jul 1994 23:35:47 -0800 (PDT) Cc: majordomo-users@GreatCircle.COM In-Reply-To: <9407201355.AA09880@sardaukar.amd.com.amd.com> from "Boris Yazlovitsky" at Jul 20, 94 08:55:09 am 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: 734 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And verily didst Boris Yazlovitsky spake of these matters: > > I assume that the types of bounces this script will work for are those > which bounced to the owner of the list, and that the script will be > invoked from /etc/aliases, right? Yes, exactly right. > Therefore, if a letter sent to owner-list > is not a bounce, are you then going to resend it? Currently, I have the aliases set up to send to both the person and the program. If the program doesn't recognize a message as a bounce, it quietly ignores it. - Alan ---- Alan Millar E-Mail: amillar@bolis.SF-Bay.org System Administrator Web: ftp://ftp.netcom.com/pub/amillar/welcome.html "Windows/NT - From the people who brought you EDLIN" -Herb Peyerl From majordomo-users-owner Thu Jul 21 04:05:06 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA15848; Thu, 21 Jul 1994 08:35:19 GMT Received: from concorde.inria.fr by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id BAA15826; Thu, 21 Jul 1994 01:34:26 -0700 Received: from chiroubles.inria.fr (chiroubles.inria.fr [128.93.8.135]) by concorde.inria.fr (8.6.9/8.6.9) with ESMTP id KAA12749; Thu, 21 Jul 1994 10:37:41 +0200 Received: (from kafka@localhost) by chiroubles.inria.fr (8.6.8/8.6.6) id KAA03320; Thu, 21 Jul 1994 10:40:09 +0200 Date: Thu, 21 Jul 1994 10:40:09 +0200 (MET DST) From: Daniel Kafka Subject: Re: majordomo vs. other mail-list programs To: Houghton Mifflin Math cc: majordomo-users@GreatCircle.COM In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Wed, 20 Jul 1994, Houghton Mifflin Math wrote: > > I am interested in setting up a couple mailing lists but haven't settled > on a software package. I would like to get some impressions from people > who have used the software as to: > > - how hard majordomo is to set up and use (how long it take you?) > - how often bugs come up and how difficult they are to fix > > I would be particularly interested to hear from any of you who have tried > other mailing list programs - how did they stack up in features and > usability vs. majordomo? > > Thank you all very much for any input you can provide. I truly > appreciate your consideration. :) > > Please send responses directly to my account at sine@world.std.com unless > you think this topic is of general interest. > I've the same question, so please forward me a answer or put it in this mailing list. Thanks Daniel Kafka ------------------------------------------------------------------------------ Daniel Kafka, l'etudiant de l'Universite d'Economie a Prague E-mail: kafka@chiroubles.inria.fr - Institut National de Recherche en Informatique et Automatique Phone: +33 1 39 63 50 30 INRIA, Centre de Rocquencourt Fax: +33 1 39 63 55 34 BP 105, 78153 Le Chesnay CEDEX Twx: 633 097 F France. e-mail en Republique Tcheque : xkafd02@vse.cz xkafd02@csearn.bitnet From majordomo-users-owner Thu Jul 21 13:12:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA18020; Thu, 21 Jul 1994 13:12:17 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id GAA18013; Thu, 21 Jul 1994 06:12:01 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HEYQF09FLC0038A5@SYSWRK.UCIS.DAL.CA>; Thu, 21 Jul 1994 10:14:00 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HEYQEQ0LLC00U3IZ@AC.DAL.CA>; Thu, 21 Jul 1994 10:13:49 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA00985; Thu, 21 Jul 94 10:07:35 -0300 Date: Thu, 21 Jul 1994 10:07:35 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Re: majordomo vs. other mail-list programs In-reply-to: from "Daniel Kafka" at Jul 21, 94 10:40:09 am To: kafka@chiroubles.inria.fr (Daniel Kafka) Cc: sine@world.std.com, Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9407211307.AA00985@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: 1190 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >> I am interested in setting up a couple mailing lists but haven't settled >> on a software package. I would like to get some impressions from people >> who have used the software as to: >> >> - how hard majordomo is to set up and use (how long it take you?) >> - how often bugs come up and how difficult they are to fix > >I've the same question, so please forward me a answer or put it in this >mailing list. Although compilation and installation was pretty easy, for someone who is not very knowledgable about mailers the setup is confusing and poorly documented. Quite a few people continue to have problems with lock files because of a very confusing situation with regard to ownership and permissions under different operating systems, and the common solution seems to be to throw up one's hands and make a lot of files and directories world writable. Other than this, Majordomo is very nice, and I have found many of the experts to be friendly and helpful. -- 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 Thu Jul 21 14:30:44 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA18607; Thu, 21 Jul 1994 14:30:44 GMT Received: from inherent.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA18597; Thu, 21 Jul 1994 07:30:28 -0700 Received: by inherent.com (NX5.67d/Inherent1.2Mailhost) id AA03655; Thu, 21 Jul 94 07:31:47 -0700 Date: Thu, 21 Jul 94 07:31:47 -0700 From: Inherent Network Admin Center Message-Id: <9407211431.AA03655@inherent.com> Received: by NeXT.Mailer (1.100) Received: by NeXT Mailer (1.100) To: bill@biome.bio.dfo.ca (Bill Silvert) Subject: Re: majordomo vs. other mail-list programs Cc: kafka@chiroubles.inria.fr (Daniel Kafka), sine@world.std.com, Majordomo-Users@GreatCircle.COM (Majordomo Users) Reply-To: darren@inherent.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk And so wrote our friend Bill Silvert: > Although compilation and installation was pretty easy, for someone > who is not very knowledgable about mailers the setup is confusing > and poorly documented. Quite a few people continue to have problems > with lock files because of a very confusing situation with regard > to ownership and permissions under different operating systems, > and the common solution seems to be to throw up one's hands and > make a lot of files and directories world writable. > > Other than this, Majordomo is very nice, and I have found many of > the experts to be friendly and helpful. I agree with Bill when he states that setup of MajorDomo would be difficult for anyone who is not familiar with mailers, but the setup of anything to do with mail would naturally be so. It would not be a factor of Majordomo or LISTSERV, or any other list service program. One of the most generalized assumptions that has to made when producing software for the world to use is that people who at least know what they want to do and have a general idea about how to get there will use the software. But, of course, then there is the idea of _learning_ how to set up a mailing list and using it to learn about the mail system. Again, any list serving program is going to be confusing because it will bring up foreign concepts that the someone just has to grow accostomed to. I am worried by the fact that someone would "throw up one's hands and make a lot of files and directories world writable" because many List Managers have been able to work around the problems that others are facing, which means it is not a fault of the program--the documentation perhaps, but I personally have not perused all the specs so I do not know what is defined and what is not defined within them. Another factor that must be considered in the pros and cons of majordomo is this list. This mailing list is jut as much a part of the package as the perl scripts. I have watched the traffic over this list for quite a while and I must say that it has some of the most helpful and willing people that I have seen. I am not sure that any question has gone unanswered, and even some of the toughest questions have been carried out to their successful resolution, no matter how long it took. For someone learning how to use a mailing list, I would have to say that monitoring this list (and reading the archives) could not provide a better education (myself as an example. I learned listservers and how to use majordomo through the qeustions of others) of how to set up a list, and even general information about mailing programs (sendmail, smail, etc). I cannot offer an opinion on which service is better because I am biased toward MajorDomo automatically because it is all that I have worked with. However, I have read somewhat on LISTSERV, and it seems extremely comparable in the functionality that it provides to the user (list members), but setup I know nothing about. I just wish to offer the advice that the ails of others should not be weighted heavily in the decision because there are many people out here to help; a library was not made to look at, but through for the answers to questions each person has. The modern libraries of the interenet are the people themselves; no longer do we have the time to write books to answer the questions of mankind, but we still have the time to throw in our two bits. I can gurantee that anyone who first sets up a list will have problems with it at some(many) stage(s). The advice that I would offer is to make sure there is support (like this list) for whatever program is chosen, it will save a lot of greif, frustration, and lonliness. Darren McKee Network Administrator --- Darren McKee - Technical Staff | darren@inherent.com Network Administration Center | Tel.: 503-224-6751 Inherent Technologies, Inc. | Fax: 503-224-8872 2140 SW Jefferson St. Suite 130 | sysadmin@inherent.com Portland, Oregon USA 97201 | From majordomo-users-owner Thu Jul 21 14:51:13 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA18892; Thu, 21 Jul 1994 14:51:13 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA18868; Thu, 21 Jul 1994 07:50:42 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HEYTVFZQLC003775@SYSWRK.UCIS.DAL.CA>; Thu, 21 Jul 1994 11:53:34 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HEYTUTI9CW00VJL5@AC.DAL.CA>; Thu, 21 Jul 1994 11:53:04 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA01540; Thu, 21 Jul 94 11:46:53 -0300 Date: Thu, 21 Jul 1994 11:46:53 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Re: majordomo vs. other mail-list programs In-reply-to: <9407211431.AA03655@inherent.com> from "Inherent Network Admin Center" at Jul 21, 94 07:31:47 am To: darren@inherent.com Cc: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9407211446.AA01540@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: 2273 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Although I agree that setting up a mailing list is not a trivial task, the point I was trying to make about Majordomo (I have no idea whether this applies to other packages) is that the installation is tricky and difficult to debug with specific reference to ownership and permissions. I feel that these problems could be solved by using a better configuration method and improved documentation. For example, in January I set up a mailing last that was very active, which is how I learned about the permission problems with lock files. I was deluged with angry mail and had to go the world-writable directory route because I couldn't keep making people upset while I experimented. More recently I screwed up while trying to implement digests and ended up just cancelling the digest feature after sending out apologies to the lists affected. The big problem with mailing lists is that if you try to learn on the job, you affect many other users. This makes it valuable to have very explicit documentation and, if possible, a configuration program for the installation. Of course I realize that Majordomo is free and I am grateful to those who write and support it. This is not intended to be a flame, but I think it is worth pointing out that there are difficulties that are quite distinct from the general problems of managing mailing lists. Bill Silvert > I agree with Bill when he states that setup of MajorDomo would >be difficult for anyone who is not familiar with mailers, but the setup >of anything to do with mail would naturally be so. It would not be a >factor of Majordomo or LISTSERV, or any other list service program. > ... >I am worried by the fact that someone would "throw up one's hands and >make a lot of files and directories world writable" ... > ... >[this list] has some of the most helpful >and willing people that I have seen. I am not sure that any question >has gone unanswered, and even some of the toughest questions have been >carried out to their successful resolution, no matter how long it took. -- 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 Thu Jul 21 15:25:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA19528; Thu, 21 Jul 1994 15:25:28 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA19511; Thu, 21 Jul 1994 08:24:49 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qR01d-00014wC; Thu, 21 Jul 94 08:27 PDT Message-Id: To: bill@biome.bio.dfo.ca (Bill Silvert) cc: darren@inherent.com, Majordomo-Users@greatcircle.com (Majordomo Users) Subject: Re: majordomo vs. other mail-list programs In-reply-to: Your message of Thu, 21 Jul 1994 11:46:53 -0300. <9407211446.AA01540@biome.bio.ns.ca> Date: Thu, 21 Jul 1994 08:26:52 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > For example, in January I set up a mailing last that was very active, > which is how I learned about the permission problems with lock files. > I was deluged with angry mail and had to go the world-writable directory > route because I couldn't keep making people upset while I experimented. > > More recently I screwed up while trying to implement digests and ended > up just cancelling the digest feature after sending out apologies to the > lists affected. > > The big problem with mailing lists is that if you try to learn on the > job, you affect many other users. This makes it valuable to have very > explicit documentation and, if possible, a configuration program for the > installation. Anyone who implements a change and opens it TO THE PUBLIC without at least 2-3 days' dry-running should be shot. --- 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 Thu Jul 21 10:44:56 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA20774; Thu, 21 Jul 1994 17:12:39 GMT Received: from midway.uchicago.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA20765; Thu, 21 Jul 1994 10:12:16 -0700 From: ckoenig@midway.uchicago.edu Received: from kimbark.uchicago.edu by midway.uchicago.edu for Majordomo-Users@greatcircle.com Thu, 21 Jul 94 12:15:14 CDT Received: from localhost.uchicago.edu by kimbark.uchicago.edu (4.1/UCCO-1.0A) id AA23749; Thu, 21 Jul 94 12:14:58 CDT Message-Id: <9407211714.AA23749@kimbark.uchicago.edu> To: Majordomo-Users@greatcircle.com (Majordomo Users) Subject: Mail List Administration from Square One? In-Reply-To: Your message of "Thu, 21 Jul 94 08:26:52 PDT." Date: Thu, 21 Jul 94 12:14:57 -0500 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Many good points have been made, in discussions here on Majordomo-Users and also on List-Managers lists, and also on netnews (comp.mail.misc), and bits and pieces have even appeared in published articles and books. It hasn't all been collected, scrutinized, verified, summarized, etc., though, not unless that forthcoming O'Reilly book (Managing Internet Services) will do it? By "it" I mean the general discussion of generic concepts and synergistic effects and tie-ins from top down, or bottom up, or both, in Mailing List Administration, including Internet mail system administration (mentioning relevant concepts concerning Bitnet, UUCP, OSI X.400, where necessary), Sendmail, SMail, MMDF, whatever sits underneath, relevant Unix/VMS/MHS/whatever details below that, relation to Netnews and FTP (archive fetching), World Wide Web (proposed URL's for mailing list and list archive service) and the particular instantiation in software packages like Majordomo, LISTSERV, ListProc, procmail/formail, whatever. Something like "Internet Mailing List Administration, from Square One, including Prerequisite Concepts of Internet Mail and System Administration and Gatewaying, Relation to Netnews, Computing History, and Social and Political Psychology" would sell at least a few copies, maybe? It would also make a good seminar topic, and be a killer tutorial for Usenix or other conferences, too.... Maybe someday I'll have to take a stab at it :-) I did post an article about my minimal experience with Majordomo, and even more minimally with ListProc, to comp.mail.misc a few weeks ago, I'll see if I can dig up a copy, maybe I should forward it to List-Managers, where it's maybe more relevant than the specific Majordomo-Users list? Chris Koenigsberg: ckk@uchicago.edu, ckoenig@midway.uchicago.edu U. of Chicago Academic Information Technologies From majordomo-users-owner Thu Jul 21 10:50:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA21013; Thu, 21 Jul 1994 17:24:37 GMT Received: from midway.uchicago.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA20966; Thu, 21 Jul 1994 10:22:51 -0700 From: ckoenig@midway.uchicago.edu Received: from kimbark.uchicago.edu by midway.uchicago.edu for majordomo-users@greatcircle.com Thu, 21 Jul 94 12:26:13 CDT Received: from localhost.uchicago.edu by kimbark.uchicago.edu (4.1/UCCO-1.0A) id AA24229; Thu, 21 Jul 94 12:25:57 CDT Message-Id: <9407211725.AA24229@kimbark.uchicago.edu> Reply-To: ckk@uchicago.edu To: majordomo-users@greatcircle.com, list-managers@greatcircle.com Subject: My Listproc-Majordomo comparison Date: Thu, 21 Jul 94 12:25:56 -0500 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here's a slight revision of something I posted to comp.mail.misc, following up a thread there. Some people on the Majordomo-Users and List-Managers lists apparently hadn't seen this on the newsgroup. Feel free to add this to whatever archives. Tasos, the author of ListProc, said that I was basically on the mark concerning ListProc. Chris Koenigsberg: ckk@uchicago.edu, ckoenig@midway.uchicago.edu U. of Chicago Academic Information Technologies ######################## Subject: Re: Which is better Majordomo or Listserv? References: <2t7qgu$773@ccnet.ccnet.com> The real LISTSERV (Revised LISTSERV) relies on Bitnet networking transport protocols. A complex Unix list processor was written, in a partial emulation of the Bitnet LISTSERV. The "Listserv for Unix" system was renamed "listproc" last summer, after threats from the original LISTSERV author, because it differs in user interface and list owner interface from LISTSERV, and was accused of misleading users who would confuse it with the "real thing". Majordomo was apparently written, in Perl, because listproc (AKA Unix LISTSERV) was too complex and did not do quite what was needed to manage a set of Usenix SAGE mailing lists. LISTSERV and ListProc want the whole world to be interconnected, i.e. all mailing list server hosts can know about each other and exchange info on remote lists; someday I imagine there'll be a DNS-like namespace of mailing lists and server hosts out there somehow. Majordomo, on the other hand, is a much smaller package, designed for easier administration on an individual host, and I have even heard (on the Majordomo-Users list) that some Majordomo hosts do NOT wish their lists advertised publicly on the net. We (U. of Chicago Academic Information Technologies) are planning to go ahead and offer new campus list management service soon using Majordomo, but we did have some requests from faculty to use listproc (they asked for LISTSERV but since this is on Unix, they would have to get listproc instead). I tried briefly to configure and build listproc for a comparison test, but gave up when it got weird, probably too soon, maybe I'll try again when I have more time to play with compilers etc :-) Listproc documentation etc. is a bit cryptic and not well thought out overall, at least from the point of view of someone new to the concept trying to understand all of its complex workings. I have seen correspondence from the Listproc author, on the listproc users' mailing list archives, where he defends his documentation because it is in the usual Unix style. (maybe "damning by faint praise"? :-) Majordomo is simpler and written in Perl scripts, so documentation is more comprehensive, and is improving, as an active community of developers is contributing to it. It only took 2 days for the current maintainers to put out small patches to fix some recently-discovered potential security holes, and since it's Perl, no recompilation is needed. Listproc requires a server daemon to be alive, which forks off child processes somewhat like lpd, and appears to be designed to do a lot of complex, tricky things which requires a lot of C source code doing networking stuff (multi-level automated archiving and indexing, with retrieval via ftpmail, automatic digestification creation and propagation, remote cooperation of "peer" list hosts, interactive administration via TCP connections, operation over other transport and delivery protocols besides TCP and SMTP, maintain its own message queueing system independently of the system mail queues, ...), which are perhaps overkill (for us, in a completely Internet TCP/SMTP environment), perhaps not, this is what I'd like to hear more discussion about. Majordomo is more focused on the essentials of individual mailing list management, and is implemented as Perl scripts, which are modular and can be used in subsets, as they are individually invoked out of system mail aliases. It lets the underlying system software do the networking and message queueing stuff, so it doesn't have to deal with TCP sockets etc. Majordomo's recently-added archiving, digestification, etc. is simpler than listproc's, and is undergoing more improvements. Apparently, Listproc's daemon with its own queueing system used to give better performance, for high-traffic lists on heavily loaded server hosts, than older versions of sendmail. But now, newer sendmail versions have greatly improved efficiency so Majordomo with new sendmail may be just as fast and load-capable as a Listproc system. (comments welcomed on this point?) With Listproc, if you can get it configured and running smoothly, you can apparently join a growing inter-operating network of cooperating "peer" list hosts, and even inter-operate with Bitnet LISTSERV list hosts too. Thus your local users can easily find out about other lists elsewhere, you can have local re-distributions for a larger global list, etc. (but re-distributions can be a source of administrative headache when global list owners try to track down mysterious errors, or unsubscribe requests from people who aren't subscribed to the global list.... :-). One big flaw in Listproc's design, in my opinion (correct me if I'm wrong!), is that it does funny things to the headers of outgoing messages which are arguably "wrong" in the RFC 822 SMTP world (I've seen arguments in the listproc users' archives), and for incoming messages, it only uses the Unix From field (i.e. the SMTP Envelope MAIL FROM, in the SMTP world) to determine the sender's identity, for subscribing, unsubscribing, accepting or rejecting messages, etc. Majordomo on the other hand will use the RFC 822 headers (Gene Spafford's Perl code for parsing mail headers), so it will recognize a "Reply-To:" for example, and will allow you to subscribe your canonical address, even if the return path of your message is convoluted (although the list owner may need to approve your subscription). You have various per-list configuration options, about what appears in the various RFC 822/SMTP headers, concerning the return address for errors, the default reply address (to the list, to the original author, to the list owner/moderator, etc.)... Both Listproc and Majordomo share concepts like moderated lists. Listproc's moderated lists have a queue of incoming messages, and the moderator has to approve or reject them by giving the message queue numbers to the server, in order to clear the queue. For a moderated list, Majordomo simply bounces messages to the moderator and then forgets about them, so the moderator can easily re-submit them with an approval password in a new header. Any message arriving with the proper approval password header will be automatically approved and propagated to the list. An outfit called CREN, an offshoot of Educom, has taken over the development of both the Bitnet LISTSERV, and the Unix Listproc, and is planning to offer a commercial version of Listproc sometime later in 1994. They have a global vision building on the inter-operating "peer" list host concept, integrating gopher, ftp, etc. (their vision statement doesn't mention WWW but I assume that must be added soon :-). We are very interested to see if CREN's new Listproc version will come with improved support, including better documentation, and we might consider switching to it sometime in the future, but we are planning to stick with Majordomo for now. Chris Koenigsberg: ckk@uchicago.edu, ckoenig@midway.uchicago.edu U. of Chicago Academic Information Technologies From majordomo-users-owner Thu Jul 21 18:19:04 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA22007; Thu, 21 Jul 1994 18:19:04 GMT Received: from SYSWRK.UCIS.DAL.CA by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA22000; Thu, 21 Jul 1994 11:18:49 -0700 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.2-14 #2545) id <01HEZ12WZ1O00039NX@SYSWRK.UCIS.DAL.CA>; Thu, 21 Jul 1994 15:19:50 -0400 Received: from biome.bio.ns.ca (biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.2-14 #2545) id <01HEZ0YW98Z400U13C@AC.DAL.CA>; Thu, 21 Jul 1994 15:16:25 -0300 Received: by biome.bio.ns.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA02471; Thu, 21 Jul 94 15:10:10 -0300 Date: Thu, 21 Jul 1994 15:10:09 -0300 (ADT) From: bill@biome.bio.ns.ca (Bill Silvert) Subject: Re: majordomo vs. other mail-list programs In-reply-to: from "Roger B.A. Klorese" at Jul 21, 94 08:26:52 am To: rogerk@unpc.queernet.org (Roger B.A. Klorese) Cc: Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9407211810.AA02471@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: 849 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >Anyone who implements a change and opens it TO THE PUBLIC without at least >2-3 days' dry-running should be shot. 1. Setting up a list is the biggest change. How do you start a list without "opening it TO THE PUBLIC"? 2. In my posting I referred to a list that was very active and caused problems because of the lock file problem. How does anyone, especially a novice, test for that before the list is "open TO THE PUBLIC" in such a way as to catch a problem caused by heavy activity? 3. There is no information in the documentation about "dry-running", and running a list with just one subscriber is not much of a test. Bill -- 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 Thu Jul 21 18:25:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA22158; Thu, 21 Jul 1994 18:25:24 GMT Received: from lclark.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA22141; Thu, 21 Jul 1994 11:24:59 -0700 Received: from salmon.lclark.edu by lclark.edu; (5.65/1.1.8.2/28May94-0344PM) id AA25593; Thu, 21 Jul 1994 11:28:47 -0700 Date: Thu, 21 Jul 1994 11:24:05 -0700 (PDT) From: John Miller Subject: Re: My Listproc-Majordomo comparison To: majordomo-users@greatcircle.com In-Reply-To: <9407211725.AA24229@kimbark.uchicago.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Could someone post a simple list of higher-powered features that the LISTSERV/LISTPROC has that majordomo does not have? I thought I saw such a paragraph in the draft of the o'reilly Book, but it does not appear to be there. Thanks, John Miller 503-768-7226 From majordomo-users-owner Thu Jul 21 11:37:12 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA21502; Thu, 21 Jul 1994 18:01:06 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA21482; Thu, 21 Jul 1994 11:00:46 -0700 Message-Id: <199407211800.LAA21482@mycroft.GreatCircle.COM> To: ckk@uchicago.edu cc: majordomo-users@greatcircle.com, list-managers@greatcircle.com Subject: Re: My Listproc-Majordomo comparison In-reply-to: Your message of Thu, 21 Jul 94 12:25:56 -0500 Date: Thu, 21 Jul 1994 11:00:45 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk ckoenig@midway.uchicago.edu writes: # Majordomo was apparently written, in Perl, because listproc (AKA Unix # LISTSERV) was too complex and did not do quite what was needed to # manage a set of Usenix SAGE mailing lists. That was _exactly_ why Majordomo was written. I obtained and tried to install and configure listproc, spent a day or two on it, and decided it was going to be easier to write something in perl that would do exactly what I wanted. For a discussion of the why's and wherefore's and early genesis of Majordomo, take a look at my paper "How I manage 17 mailing lists without answering -request mail", originally published at the USENIX LISA 6 conference a couple of years ago, and now available for anonymous FTP from FTP.GreatCircle.COM, file pub/majordomo/majordomo.paper.ps.Z. # Majordomo, on the other hand, is a much smaller package, designed for # easier administration on an individual host Well, it started out that way anyway... There's a growing trend to add ever more features to Majordomo. This is one of the reasons I'm no longer actively involved in Majordomo development I have nothing against and no arguments with the folks (particularly John Rouillard, who is managing the whole effort) who are working hard to extend and expand Majordomo; I just have no interest in participating. Majordomo already does most of what _I_ want it to do. I'm extremely pleased that other folks are finding it useful, and finding it a good platform to use as a starting point for the things _they_ want to do. # and I have even heard (on # the Majordomo-Users list) that some Majordomo hosts do NOT wish their # lists advertised publicly on the net. Yes. I expect that there are at least as many Majordomo servers running private lists as public ones. # I tried briefly to configure and build listproc for a comparison test, # but gave up when it got weird, probably too soon, maybe I'll try again # when I have more time to play with compilers etc :-) Listproc # documentation etc. is a bit cryptic and not well thought out overall, # at least from the point of view of someone new to the concept trying # to understand all of its complex workings. I have seen correspondence # from the Listproc author, on the listproc users' mailing list # archives, where he defends his documentation because it is in the # usual Unix style. (maybe "damning by faint praise"? :-) As opposed to Majordomo's documentation, which was almost non-existant until recently... :-) Actually, the new README file that John Rouillard wrote, the chapter from the new "Managing Internet Information Services" book from O'Reilly & Associates that they let us extract and make available for anonymous FTP, the online manual pages for some components written by Jim Duncan, the FAQ originally assembled by Vincent Skahan, as well as contributions by lots of other folks, go a long way towards improving the documentation situation for Majordomo. # Majordomo is simpler and written in Perl scripts, so documentation is # more comprehensive, and is improving Well, OK. :-) When I was doing most of the Majordomo development, I always said that documentation (or lack thereof) was one of Majordomo's weak points, and I'm glad to see that the documentation is improving faster than new features are being added now that somebody else has taken over development. # as an active community of # developers is contributing to it. It only took 2 days for the current # maintainers to put out small patches to fix some recently-discovered # potential security holes, and since it's Perl, no recompilation is # needed. I think this is one of the key strengths of Majordomo: the very active Majordomo-Users and Majordomo-Workers mailing lists. They go a long way towards making up for the documentation (or lack thereof); you can ask a question, and get a helpful and almost immediate answer. # Apparently, Listproc's daemon with its own queueing system used to # give better performance, for high-traffic lists on heavily loaded # server hosts, than older versions of sendmail. But now, newer sendmail # versions have greatly improved efficiency so Majordomo with new # sendmail may be just as fast and load-capable as a Listproc system. # (comments welcomed on this point?) I have no experience with listproc in order to provide a comparison, but here's a data point. I run the Firewalls mailing list, with over 2000 subscribers and about 20-40 messages/day, plus a couple of dozen other mailing lists (totalling another couple of thousand subscribers and another 20-40 messages/day) on a Sun 3/60. Upgrading to the new 8.6.x version of Sendmail made an immense difference in performance. -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 Jul 21 11:53:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA22449; Thu, 21 Jul 1994 18:42:28 GMT Received: from uu3.psi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA22441; Thu, 21 Jul 1994 11:42:11 -0700 Received: from magpie.UUCP by uu3.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP; id AA20583 for ; Thu, 21 Jul 94 14:09:46 -0400 Received: by magpie (Smail3.1.28.1 #3) id m0qR2Qk-0000swC; Thu, 21 Jul 94 14:01 EDT Message-Id: Date: Thu, 21 Jul 94 14:01 EDT From: manes@magpie.com (Steve Manes) To: majordomo-users@greatcircle.com Subject: majordomo vs. other mail-list programs Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I run about thirty mailing lists for PBS and CPB... also some extracurricular ones, like the NYC Motorcyclists list. I used Kotsikonas' LISTSERV and LISTPROC for years and until recently so I have some basis for comparison. I decided to abandon LISTPROC when it was sold to a commercial entity, which has forbidden Kotsikonas from making any more bug fixes to the "freeware" version. Unfortunately, the latest LISTPROC had some nasty alligators and, although I enjoy a good hacking challenge, the code isn't well-documented and I don't have as much time as I used to for this kinda fun. The LIST* learning curve was very high for me, and I'm a software engineer (OTOH, maybe that's why). I first tried running it with SCO's MMDF and ran into a brick wall because of problems with SCO's piped aliases that stripped the first line off message headers, which are critical under LIST*. SMAIL fixed that problem. I also had problems with the server daemon dying until I learned to decipher the voluminous logging that LIST* maintains. File permissions are extremely critical with LIST*. Subscriber and manager security is extremely good with LIST*. The user's subscription address is yanked from the first line of the internet header rather than from the "From: " address, which makes it difficult (although not impossible) to spoof. OTOH, unless you're running mailing lists for the DoD, I don't know why such heavy subscription security is necessary. It was very problematic for the PBS list managers, some of whom lived on the road and had to manage lists from many different addresses. PBS finally asked me to investigate mailing list alternatives to LISTPROC because of the griping from content managers. Majordomo observations from a novice: >From what I've seen of MAJORDOMO so far, I like; although it also doesn't win prizes for its learning curve either. It would really help if there was just one tutorial source for building the sofware rather being directed to scattered info among the README file, Doc/majordomo.ora, Doc/majordomo.lisa6.ps, resend.README, etc. I now know the README file is the key installation doc but for those of us who methodically approach these things by printing out every text file in sight, it's confusing, especially when there is conflicting information. There is an inconsistency in the $mailer definition from majordomo.cf. Programs like 'digest', 'resend' and 'bounce-remind' ignore it and make hardwired calls to /usr/lib/sendmail anyway. UUCP-only SMAIL sites won't have /usr/lib/sendmail, although linking /bin/smail to /usr/lib/sendmail, which is what you do for SMTP support, fixes this. This SMAIL note should probably be put in the manual somewhere. I got the first MAJORDOMO digest of the NYC Motorcyclists list sent out last night but this morning was hammered by daemon error messages from uupsi3.com "Execution request failed" with no explanation given. This is obviously an SMAIL problem but I've never seen it before. Anyone have a clue?? One final note, 'resend' isn't removing its /tmp/resend.NNN.in and /tmp/resend.NNN.out files. Anyone have an easy way to check why this is happening? From majordomo-users-owner Thu Jul 21 18:59:58 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id SAA22656; Thu, 21 Jul 1994 18:59:58 GMT Received: from ftp.std.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id LAA22650; Thu, 21 Jul 1994 11:59:42 -0700 Received: from world.std.com by ftp.std.com (8.6.8.1/Spike-8-1.0) id PAA07353; Thu, 21 Jul 1994 15:03:07 -0400 Received: by world.std.com (5.65c/Spike-2.0) id AA27546; Thu, 21 Jul 1994 14:52:02 -0400 Date: Thu, 21 Jul 1994 14:52:01 -0400 (EDT) From: Houghton Mifflin Math Subject: Re: My Listproc-Majordomo comparison To: ckk@uchicago.edu Cc: majordomo-users@GreatCircle.COM, list-managers@GreatCircle.COM In-Reply-To: <9407211725.AA24229@kimbark.uchicago.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I have been doing some research on mailing lists and I would like to make a small clarification. Listproc (formerly named "Unix Listserv") will be released as a commercial product. However, try not to get this confused with another commercial product created by the original author of LISTSERV - "LISTSERV for Unix". LISTSERV for Unix has been ported over from the original VM platform on BITNET and is now fully functional and supported on Unix. LISTSERV for Unix is a product of L-SOFT International (sales@lsoft.com). From majordomo-users-owner Thu Jul 21 12:16:54 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA22949; Thu, 21 Jul 1994 19:10:53 GMT Received: from sgi.sgi.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA22943; Thu, 21 Jul 1994 12:10:42 -0700 Received: from lunch.asd.sgi.com by sgi.sgi.com via SMTP (940627.SGI.8.6.9/910110.SGI) id MAA09503; Thu, 21 Jul 1994 12:14:03 -0700 Received: by lunch.asd.sgi.com (931110.SGI/911001.SGI) for @sgi.sgi.com:Majordomo-Users@GreatCircle.COM id AA15547; Thu, 21 Jul 94 12:13:45 -0700 From: pdc@lunch.asd.sgi.com (Paul Close) Message-Id: <9407211913.AA15547@lunch.asd.sgi.com> Subject: Re: majordomo vs. other mail-list programs To: rogerk@unpc.queernet.org (Roger B.A. Klorese) Date: Thu, 21 Jul 1994 12:13:45 -0700 (PDT) Cc: bill@biome.bio.dfo.ca, darren@inherent.com, Majordomo-Users@GreatCircle.COM In-Reply-To: from "Roger B.A. Klorese" at Jul 21, 94 08:26:52 am X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 1612 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > > For example, in January I set up a mailing last that was very active, > > which is how I learned about the permission problems with lock files. > > I was deluged with angry mail and had to go the world-writable directory > > route because I couldn't keep making people upset while I experimented. > > > > More recently I screwed up while trying to implement digests and ended > > up just cancelling the digest feature after sending out apologies to the > > lists affected. > > > > The big problem with mailing lists is that if you try to learn on the > > job, you affect many other users. This makes it valuable to have very > > explicit documentation and, if possible, a configuration program for the > > installation. > > Anyone who implements a change and opens it TO THE PUBLIC without at least > 2-3 days' dry-running should be shot. What I do, instead of shooting myself :-), is make a separate majordomo setup just for testing. This allows me to test whatever configurations I like. As long as I don't break the aliases file, nobody knows. The aliases look something like this: majordomo: "/local/majordomo/wrapper majordomo" mjd-test: "/local/majordomo-test/wrapper majordomo" The important thing is that any test lists use /local/majordomo-test, not /local/majordomo! And in the config file in the test setup, make sure and make the owner mjd-test, not majordomo (or your majordomo replies will go to the wrong one). This setup also allows me to test new or beta releases of majordomo.... -- Paul Close pdc@sgi.com ...!{ames, decwrl, uunet}!sgi!pdc No fate but what we make From majordomo-users-owner Thu Jul 21 19:31:47 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA23335; Thu, 21 Jul 1994 19:31:47 GMT Received: from unpc.queernet.org by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA23237; Thu, 21 Jul 1994 12:25:30 -0700 Received: by unpc.queernet.org (Smail3.1.28.1 #5) id m0qR3m3-00014wC; Thu, 21 Jul 94 12:27 PDT Message-Id: To: bill@biome.bio.dfo.ca (Bill Silvert) cc: Majordomo-Users@greatcircle.com (Majordomo Users) Subject: Re: majordomo vs. other mail-list programs In-reply-to: Your message of Thu, 21 Jul 1994 15:10:09 -0300. <9407211810.AA02471@biome.bio.ns.ca> Date: Thu, 21 Jul 1994 12:27:17 -0700 From: "Roger B.A. Klorese" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > 1. Setting up a list is the biggest change. How do you start a list > without "opening it TO THE PUBLIC"? Easy. Unless you believe that people out there spend all their time sending mail to every address on the Internet seing if it has a Majordomo user, asking which lists it manages, etc... simple. You just don't publicize it. Use a fake name. Whatever. It's trivial. > 2. In my posting I referred to a list that was very active and caused > problems because of the lock file problem. How does anyone, especially > a novice, test for that before the list is "open TO THE PUBLIC" in such > a way as to catch a problem caused by heavy activity? Start a shell script, or open 50 windows, to submit 50 subscribe and unsubscribe requests at the same time. Forge them with fake users on your system, if you have to. > 3. There is no information in the documentation about "dry-running", and > running a list with just one subscriber is not much of a test. There's probably no information in your compiler manual about how to test any application your site writes or installs either. Let me try this differently: anyone who installs ANY software and puts it into production without dry-running it should be shot. You're apparently looking for a "configuring Majordomo without trying to read Perl, look at Majordomo debug output, or think about it as a Unix tool" document, from a software-customer perspective. I don't. I'm glad people are working on the software instead of documenting it for non-sysadmins. I'm glad it's a Unix toolkit, not a software package. --- 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 Thu Jul 21 19:34:05 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA23417; Thu, 21 Jul 1994 19:34:05 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA23406; Thu, 21 Jul 1994 12:33:51 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA25369 (5.65c/IDA-1.4.4 for ); Thu, 21 Jul 1994 15:35:11 -0400 Message-Id: <199407211935.AA25369@cs.umb.edu> To: manes@magpie.com (Steve Manes) Cc: majordomo-users@greatcircle.com Subject: Re: majordomo vs. other mail-list programs In-Reply-To: Your message of "Thu, 21 Jul 1994 14:01:00 EDT." Date: Thu, 21 Jul 1994 15:35:10 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Steve Manes writes: >>From what I've seen of MAJORDOMO so far, I like; although it also doesn't >win prizes for its learning curve either. It would really help if there was >just one tutorial source for building the sofware rather being directed to >scattered info among the README file, Doc/majordomo.ora, >Doc/majordomo.lisa6.ps, resend.README, etc. I now know the README file is >the key installation doc but for those of us who methodically approach these >things by printing out every text file in sight, it's confusing, especially >when there is conflicting information. In general, assume that the parent README is right. The subsidiary README's are primarially used when running the programs in standalone mode. This will be fixed before 1.93 ships hopefully. >There is an inconsistency in the $mailer definition from majordomo.cf. >Programs like 'digest', 'resend' and 'bounce-remind' ignore it and make >hardwired calls to /usr/lib/sendmail anyway. Fixed in 1.93 thanks to a patch from volf@eb.ele.tue.nl (Frank Volf). >UUCP-only SMAIL sites won't >have /usr/lib/sendmail, although linking /bin/smail to /usr/lib/sendmail, >which is what you do for SMTP support, fixes this. This SMAIL note should >probably be put in the manual somewhere. I'll add it. >One final note, 'resend' isn't removing its /tmp/resend.NNN.in and >/tmp/resend.NNN.out files. Anyone have an easy way to check why this is >happening? Yeah, its a bug. Look for a line that says: unlink("/tmp/resend.$$.*"); and change it to read: unlink(); I forgot the angle brackets and that prevnets the glob from happening. -- 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 Jul 21 12:55:28 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA23682; Thu, 21 Jul 1994 19:47:26 GMT Received: from midway.uchicago.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA23657; Thu, 21 Jul 1994 12:46:59 -0700 From: ckoenig@midway.uchicago.edu Received: from kimbark.uchicago.edu by midway.uchicago.edu for Majordomo-Users@greatcircle.com Thu, 21 Jul 94 14:50:20 CDT Received: from localhost.uchicago.edu by kimbark.uchicago.edu (4.1/UCCO-1.0A) id AA00533; Thu, 21 Jul 94 14:50:03 CDT Message-Id: <9407211950.AA00533@kimbark.uchicago.edu> To: Majordomo-Users@greatcircle.com (Majordomo Users) Subject: lifecycle upgrading, Re: majordomo vs. other mail-list programs In-Reply-To: Your message of "Thu, 21 Jul 94 15:10:09 -0300." <9407211810.AA02471@biome.bio.ns.ca> Date: Thu, 21 Jul 94 14:50:02 -0500 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk > 2. In my posting I referred to a list that was very active and caused > problems because of the lock file problem. How does anyone, especially > a novice, test for that before the list is "open TO THE PUBLIC" in such > a way as to catch a problem caused by heavy activity? ----- In fact, not only is help needed in setting up and debugging a new server and/or new list, but what about upgrading existing ones, especially high-volume ones? I've been asked to help a site on campus here where an old Majordomo is installed solely to run a mailing list with over 1000 subscribers and lots of traffic everyday; they're also running other old system components. They want help in upgrading everything. It's a touchy and sobering prospect, approaching such a beast and preparing to poke it in a way that might affect hundreds of incoming and outgoing messages in a single day..... Unfortunately the approach of many system people sometimes is to install something once in a baseline configuration, and hand it over to people who will run the system without understanding it, and then leave. That's what happened to the people who just asked for my help -- a predecessor of mine set them up and sent them on their way, and then left, at least a year ago. I always seem to come along later when the administrators are flailing for help because something has gone stale, and I'm always trying to explain at meetings & such how there is an ongoing software lifecycle, that installing a package (like Majordomo, or a version of Sendmail, or the PH/QI CSO nameserver, etc. etc.) is only the beginning of your ongoing work in maintaining and supporting it, and following along as the community of others develops a shared body of experience with it. Chris Koenigsberg: ckk@uchicago.edu, ckoenig@midway.uchicago.edu U. of Chicago Academic Information Technologies From majordomo-users-owner Thu Jul 21 20:40:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA24799; Thu, 21 Jul 1994 20:40:23 GMT Received: from hp.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA24793; Thu, 21 Jul 1994 13:40:07 -0700 Received: from hpkel02.cup.hp.com by hp.com with SMTP (1.36.108.7/15.5+IOS 3.13) id AA05735; Thu, 21 Jul 1994 13:43:25 -0700 Received: by hpkel02.cup.hp.com (1.38.193.5/15.5+IOS 3.20+cup+OMrelay) id AA01407; Thu, 21 Jul 1994 13:43:17 -0700 From: Ray Terry Message-Id: <9407212043.AA01407@hpkel02.cup.hp.com> Subject: Rookie asks about digests To: Majordomo-Users@GreatCircle.COM Date: Thu, 21 Jul 94 13:43:17 PDT Mailer: Elm [revision: 70.85.2.1] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Help, please... I just started setting up Majordomo yesterday. All seems to be testing out okay (basic commands, bounces, archiving into daily files, approvals, etc). But I can't finger out the digest portion. What I want to do (please tell me that I can do it) is have two lists, a my-list and a my-list-digest. Those that like multiple messages will subscribe to my-list and those that like digests will sub to my-list-digest. All subscribers will see the same msgs and the same replys, just either in digest form or in multiple msgs. Can I do that? If so, any hints would be greatly appreciated. Ray Terry raymail@hpkel02.cup.hp.com P.S. And re the discussion on Majordomo's set-up ease, I had very limited experience with sendmail, etc before yesterday, and I'm about ready to go public. From majordomo-users-owner Thu Jul 21 22:49:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA27466; Thu, 21 Jul 1994 22:49:18 GMT Received: from sashimi.wwa.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA27451; Thu, 21 Jul 1994 15:48:46 -0700 Received: from hp1 by sashimi.wwa.com with uucp (Smail3.1.28.1 #8) id m0qR6yy-000bmNC; Thu, 21 Jul 94 17:52 CDT Received: by hp1.holl.com (/\==/\ Smail3.1.25.1 #25.2) id ; Thu, 21 Jul 94 17:15 CDT Message-Id: From: dave@holl.com (David Vrona) Subject: mailing list blown away!!!! To: majordomo-users@greatcircle.com Date: Thu, 21 Jul 1994 17:15:12 -0600 (CDT) X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 484 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk How is it that the list of subscribers to a mailing list can be blown away?????? This has happened twice now.... dave -- David Vrona N9QNZ +1 708 680 2829 (voice) Hollister Incorporated +1 708 918 3860 (fax) 2000 Hollister Drive Internet: dave@hp1.holl.com Libertyville, IL 60048-3781 UUCP: {well connected}!gagme!hp1!dave Opinions expressed are my own and not those of Hollister Incorporated. From majordomo-users-owner Thu Jul 21 17:46:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA29517; Fri, 22 Jul 1994 00:03:37 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA29501; Thu, 21 Jul 1994 17:03:21 -0700 Message-Id: <199407220003.RAA29501@mycroft.GreatCircle.COM> To: Majordomo-Users, Majordomo-Workers Cc: mcb@greatcircle.com Subject: Majordomo-Users administrivia Date: Thu, 21 Jul 1994 17:03:17 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm pleased to announce that Michael C. Berch has joined Great Circle Associates; his duties include, among other things, acting as Postmaster@GreatCircle.COM. He's therefore taking over the day-to-day management (approving subscription requests, dealing with bounces, etc.) of most of the GreatCircle.COM mailing lists, including Majordomo-Users and Majordomo-Workers. Michael brings to the job many years of experience as an Internet user (stretching way back to an email address with".ARPA" in it) and list manager, and I'm sure he'll do just fine. I'll still be a frequent participant on the mailing list; if anything, I'll be taking part even more frequently, now that I'll no longer be buried under a flood of administrative email every day. As always, all routine requests (subscribe, unsubscribe, etc.) concerning the lists should go to Majordomo@GreatCircle.COM. Requests that simply cannot be handled by Majordomo should be sent to Majordomo-Users-Owner@GreatCircle.COM. Thanks! -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Fri Jul 22 15:03:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA10097; Fri, 22 Jul 1994 15:03:42 GMT Received: from sashimi.wwa.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA10088; Fri, 22 Jul 1994 08:03:22 -0700 Received: from hp1 by sashimi.wwa.com with uucp (Smail3.1.28.1 #8) id m0qRMCe-000bm5C; Fri, 22 Jul 94 10:08 CDT Received: by hp1.holl.com (/\==/\ Smail3.1.25.1 #25.2) id ; Fri, 22 Jul 94 09:45 CDT Message-Id: From: dave@holl.com (David Vrona) Subject: Re: mailing list blown away!!!! To: majordomo-users@greatcircle.com Date: Fri, 22 Jul 1994 09:45:39 -0600 (CDT) X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 770 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk According to John P. Rouillard: > >How is it that the list of subscribers to a mailing list can be blown away?? > >???? > > > >This has happened twice now.... > > Was your disk close to full? > Ah!!! Yes, now that you mention it. This event did coincide with a full disk. I assume that a subscription request came in when the disk was full or is it some other mechanism that is the culprit??? dave -- David Vrona N9QNZ +1 708 680 2829 (voice) Hollister Incorporated +1 708 918 3860 (fax) 2000 Hollister Drive Internet: dave@hp1.holl.com Libertyville, IL 60048-3781 UUCP: {well connected}!gagme!hp1!dave Opinions expressed are my own and not those of Hollister Incorporated. From majordomo-users-owner Fri Jul 22 15:45:39 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA11011; Fri, 22 Jul 1994 15:45:39 GMT Received: from gatekeeper.esl.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id IAA10994; Fri, 22 Jul 1994 08:45:22 -0700 Received: from smtp.esl.com (smtpout.esl.com) by gatekeeper.esl.com (4.1/SMI-4.1) id AA27538; Fri, 22 Jul 94 08:48:25 PDT Message-Id: Date: 22 Jul 1994 08:46:25 -0700 From: "John Carr" Subject: majordomo-test.cf? To: "majordomo-users" X-Mailer: Mail*Link SMTP/QM 3.0.0GM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk where is majordomo getting majordomo-test.cf as the file to use (see below)? I can't find where this is being established. I don't see any MAJORDOMO_CF env variable set anywhere (but I could be looking in the wrong place). I have /etc/majordomo.cf. Where can you suggest I start looking for this? I'm running this on a Sparc 10 under 4.1.3. ------------------------- From daemon Thu Jul 21 19:38:52 1994 Return-Path: Received: by gatekeeper.esl.com (4.1/SMI-4.1) id AB23369; Thu, 21 Jul 94 19:38:49 PDT Date: Thu, 21 Jul 94 19:38:49 PDT From: Mailer-Daemon (Mail Delivery Subsystem) Subject: Returned mail: unknown mailer error 2 Message-Id: <9407220238.AB23369@gatekeeper.esl.com> To: jcarr Status: R ----- Transcript of session follows ----- /home/majordomo/majordomo-test.cf not readable; stopped at /home/majordomo/request-answer line 26. 554 "|/home/majordomo/wrapper request-answer netadmin"... unknown mailer error 2 ----- Unsent message follows ----- Return-Path: Received: by gatekeeper.esl.com (4.1/SMI-4.1) id AA23367; Thu, 21 Jul 94 19:38:49 PDT Date: Thu, 21 Jul 94 19:38:49 PDT From: jcarr (John Carr) Message-Id: <9407220238.AA23367@gatekeeper.esl.com> To: netadmin-request Subject: lists lists From majordomo-users-owner Fri Jul 22 21:27:15 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA15875; Fri, 22 Jul 1994 21:27:15 GMT Received: from firstfloor.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA15868; Fri, 22 Jul 1994 14:27:08 -0700 Received: from et.firstfloor.COM ([198.206.195.36]) by firstfloor.COM (4.1/SMI-4.1) id AA23205; Fri, 22 Jul 94 14:30:44 PDT From: swayland@firstfloor.COM (Scott Wayland, Technical Support) To: majordomo-users@greatcircle.com Subject: File & Directory permissions Reply-To: swayland@firstfloor.COM Date: Fri, 22 Jul 94 14:30:35 PDT Message-Id: <9407222130.236BFC@et.firstfloor.COM> X-Mailer: SelectMAIL 1.1 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Great news folks... We finaly succeded in getting majordomo up and running. We believe that majordomo is going to prove itself to be a remarkable mailing list tool. We like the concept of making unique uid and gid for majordom to utilize on our network. Though, we have found that if we do not open the oid permissions to the entire world we receive 'unknown mailer error 13' errors due to some form of 'rwx' permissions being denied in the oid... Has anybody been able to find a work around for this while leaving majordomo its unique uid & gid ? Is there some way that the majordomo installation can be modified so that it is a completly selfcontained entity ? Thanks is advance. From majordomo-users-owner Sat Jul 23 19:01:18 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id TAA26152; Sat, 23 Jul 1994 19:01:18 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id MAA26127; Sat, 23 Jul 1994 12:00:28 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA09165 (5.65c/IDA-1.4.4 for ); Sat, 23 Jul 1994 15:04:02 -0400 Message-Id: <199407231904.AA09165@cs.umb.edu> To: majordomo-users@greatcircle.com Subject: Permissions in majordomo In-Reply-To: Your message of "Fri, 22 Jul 1994 14:30:35 PDT." <9407222130.236BFC@et.firstfloor.COM> Date: Sat, 23 Jul 1994 15:04:00 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk THERE IS NO REASON TO HAVE WORLD RWX PRIVS ON MAJORDOMO DIRECTORIES. IT WAS NOT DESIGNED THAT WAY AND THERE IS NO REASON FOR IT. There now that I have vented, we can get down to business. If you can't get majordomo to opwberate without world write permissions, then one of the following is wrong: 1) The wrapper is not setting the uid and gid 1) The setuid and setgid bits in the mode word are not set. Read chmod(1), and look at the su program to see a setuid program. 2) You are in a posix universe, but you compiled the wrapper with bsd semantics (tsk tsk) 3) setuid is somehow broken on your machine 2) The uid and gid that are set by the wrapper are not the uid and gid that own the majordomo directories 3) The majordomo directories are not mode 77? I.E. you set it to 55? or something silly like that. Fix the above problems and things will run fine without needing world write privs. Believe me, I have almost 30 installations running majordomo across all sorts of hardware and NONE of them have world writable directories. As a matter of fact most of them don;t have world readable directories. Sadly getting this right, seems to be easier to say than to do especially for UNIX novices, so I enclose the following script as an aide: #begin script #!/usr/local/bin/perl print "euid is: $>\n"; print "egid is: $)\n"; print "ruid is: $<\n"; print "rgid is: $(\n"; #== end script To use it, put the script (inbetween the #== lines) in the majordomo home directory. The majordomo home directory is the directory with majordomo and resend in it. Make sure to change the first line in the script (#!/usr/local/bin/perl) to point to the location of perl on your system. I put the script in a file called peid (print effective id). Make sure the files is executable (chmod +x peid usually does the trick). The patch /tools/majordomo is the patch tomy majordomo home directory. Replace that with the path to your majordomo home directory before executing the examples. Also, when I say uid or gid, I mean either the numeric values, or the names that those values map to. You can find out what your uid and gid look like by running the script directly. DO NOT run this test as root, it can create a false success. In my case running: /tools/majordomo/peid produces: euid is: 1249 egid is: 15 33 31 19 16 11 15 ruid is: 1249 rgid is: 15 33 31 19 16 11 15 The euid is my uid, and the egid is my gid (group other, not majordom). For the second test, we want to run the peid script using the majordomo wrapper program. DO NOT RUN THIS TEST AS ROOT, it will cause a false positive. You can run the script like so: /tools/majordom/wrapper peid If the wrapper complains about posix something or other (problem 1.2 above) recompile the wrapper using posix semantics as specified in the Makefile. If the script ran successfully, its output should look something like: euid is: 916 egid is: 34 34 33 31 19 16 11 15 ruid is: 916 rgid is: 34 34 33 31 19 16 11 15 Check the euid line. Grep for :916: through the password file (or use ypcat passwd | grep :916: if you run yellow pages/NIS). This number should be the uid of the majordom user (or in general the uid you specified in the makefile. If you chose to install it using daemon, the uid will usually be 1). The egid line gets the same treatment for the first number in the list, except that you look at the /etc/group file instead of the passwd file. Group 34 for my site is the majordom group. The wrapper may set the real uid and real gid as well depending on the system (bsd usually does, posix may not, I don't have a posix host handy to check.), however this is important, the euid and egid should not be your uid and your gid. If you get the same output from running peid with and without the wrapper, the wrapper script is not setting the uid or gid properly (problem 1) To track down this problem, make sure that the setuid and setgid bits are correct. Spend some time with the chmod man page to make sure you set the bits right (or you can play around and keep running the script till the euid and egid come up right). Check the makefile and make sure you set the proper uid and gid there. Keep working at it untill the euid matches the uid of the majordom user, and the egid matches that of the majordom group. Ok, so now the euid and egid match your majordom user and your majordom group. But wait we aren't done. We still need to check the owner and group ownerships on the directories (problem 2). All directories and files with the exception of the wrapper program should be owned by the euid and the first egid. (Technically this is a lie, but if you know its a lie, then you probably aren't having any permission problems 8-).) Make sure that every directory and file is properly owned. The only file that may not be owned by the majordom user and group is the wrapper program itself on a posix system, which will be owned by root. Now make sure that all the directories owned by majordom have mode 77? permissions (rwxrwx?-?) where the ? indicates that it doesn't matter what permissions are set there, but you shouldn't set the write permission 8-). The list of directories to change includes: the directory where the Log file is located the directory where the mailing list files and per list config files are located the directory where the archives are located (if you archive messages). Also change the permissions on the subdirectories of this directory the digest spool directory (if you are using it). Also change the permissions on the subdirectories of this directory. Whew. Now that all of these checks have been done, try sending mail to the list using the verbose mode for mail or sendmail as explained in the readme. Try subscribing etc. everything should now be working fine. If not, try this list again fromthe top. If you still can't get it to work, send mail to the majordomo-users list with the output of peid when run under the wrapper, and when not run under the wrapper, Yes, peid and a copy of the missive will be placed into the 1.93 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 Sat Jul 23 20:22:27 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA26557; Sat, 23 Jul 1994 20:22:27 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA26541; Sat, 23 Jul 1994 13:22:11 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA11146 (5.65c/IDA-1.4.4 for ); Sat, 23 Jul 1994 16:25:45 -0400 Message-Id: <199407232025.AA11146@cs.umb.edu> To: debbie@qsun.att.com (Deborah A Hamilton +1 908 949 9459) Cc: majordomo-users@greatcircle.com Subject: Re: domain munging in "resend" In-Reply-To: Your message of "19 Jul 1994 15:53:00 GMT." <9407191552.AA17336@ig1.att.att.com> Date: Sat, 23 Jul 1994 16:25:44 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9407191552.AA17336@ig1.att.att.com>, Deborah A Hamilton +1 908 949 9459 writes: >I had the same problem with restrict_post plus an additional >requirement. > >In setting up Majordomo for use at InterNIC Directory and Database >Services, I had requests to provide the ability to restrict posting >only the members of the lists and (optionally) to some additional >ids as well as having the ability to restrict posting to only a >FEW ids. The restrict_post feature as implemented in R1.92 only >allows you to restrict posting to a few ids since you can only specify >one id per file. I hacked the restrict_post code in resend to >search the entire file for the id, not just the first record in >the file. > >So now if I have a list to which only list members should post, I >specify "restrict_post = :.restrict" and it >scans the subscription list for matches on the id. If I need to add >additional ids, they get listed in the file called .restrict. This is what the proposed access list syntax will be. This will be used for ALL access lists, private*, restrict_post, advertize/noadvertize etc. There should be both a simple access mechanism to allow: all access, no access, members only access, password only access or access list access. So there would be two items that dealt with permissions. One item to select the mode of access, and one table to specify access criteria. This would replace things like private_which with which_access = {all, none, members, passwd } This sets the default action of the acl is empty. all => ALL allow formerly private_which = no none => ALL deny no former mechanism members => MEMBERS allow formerly private_which = yes passwd => use approve command with no former mechanism then there would be a corresponding which_acl that is looked at before the above default are used. I needed a scheme that was as flexible as the two keyword scheme used for advertize/noadvertize. One I like is reminisent of the tcpd wrappers configuration setup. Each line consists of an: expression action pair. Where the expressions are: /^rouilj/ - perl regular expression the regexp is enclosed in /'s. It supports a subset of the perl regular expressions. Only the following characters are allowed: any alphanumeric and the underscore (\w class) the characters .|\?<>$*^+/@:;[] the characters ( and ) and ' are allowed, but they are always escaped if they weren't in the original regexp, so they lose their original meaning. *cs.umb.edu - regular text straight text with no embedded whitespace is the same as the perl regexp /text/ except that the * character is replaced with ".*". ALL - matches anything, it is a simple form of * or /.*/. MEMBER - the address matches if is a member of the mailing list. If mungedomain is set for the list, then mungedomain is used when matching addresses. FILE= - the address matches if it is found in the file . If filespec is not an absolute path, it is considered to be in the majordomo mailing list directory. If mungedomain is set for the list, then mungedomain is in effect during the search. FILE= is equivalent to MEMBER. and action is: allow - the match causes access to be allowed deny - the match causes access to be denied The rules would be applied one after the other, the first match would end the search. I think this is as flexible as the current two entry advertize/noadvertize setup, and it puts it in one table which can be easily scanned. I think some examples are in order the pair: advertize = /cs.umb.edu/ noadvertize = would result in the acl: advertize_acl << END cs.umb.edu allow ALL deny END while advertize = /.*cs.umb.edu/ noadvertize = /@cs.umb.edu/ would be: advertise_list << @cs.umb.edu deny *cs.umb.edu allow ALL deny EOF The access_ only sets the defaults, so it is possible to do something like: access_which = passwd fooble which_acl << END /^rouilj@cs.umb.edu$/ allow /^rouilj@.*.mit.edu$/ deny END Which means I can send a which command from cs.umb.edu and have it work, but I will never get the which command to work from mit. Everybody else has to use an "approve fooble which" command. Alternatively, access_which = all which_acl << END /^rouilj@.*cs.umb.edu$/ deny END will prevent me from having access to the which command from cs.umb.edu. Quips, comments, evasions, questions, or answers anybody? Does anybody want to write this code 8-). -- 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 Sat Jul 23 20:53:02 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id UAA26767; Sat, 23 Jul 1994 20:53:02 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id NAA26722; Sat, 23 Jul 1994 13:49:34 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA11928 (5.65c/IDA-1.4.4 for ); Sat, 23 Jul 1994 16:48:13 -0400 Message-Id: <199407232048.AA11928@cs.umb.edu> To: debbie@qsun.att.com (Deborah A Hamilton +1 908 949 9459) Cc: majordomo-users@greatcircle.com Subject: Re: Unexpected Token Error In-Reply-To: Your message of "20 Jul 1994 20:33:00 GMT." <9407202032.AA14186@ig1.att.att.com> Date: Sat, 23 Jul 1994 16:48:13 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9407202032.AA14186@ig1.att.att.com>, Deborah A Hamilton +1 908 949 9459 writes: >Some users are posting mail to majordomo@dsmail.internic.net to >do subscribes, request help, indexes, etc. The message gets >processed but the response that gets sent to the user is >not delivered due to a syntax error. > >The error message that comes back is (Note: owner-graph-ti is aliased >to debbie@qsun.att.com): > >> From: postmaster@ds.internic.net >> Date: Tue, 19 Jul 09:32:00 1994 >> To: debbie@qsun.att.com >> Subject: smtp mail failed >> Status: R >> >> Your mail to UNCCVM.UNCC.EDU is undeliverable. >> ---------- diagnosis ---------- >> <<< 501 Syntax Error. Unexpected Token '@' >> ---------- unsent mail ---------- >>From owner-graph-ti@dsmail.internic.net Tue Jul 19 09:31:58 EDT 1994 >> remote from ds What the heck is a From (not from: line) doing in here. This implies that is was delivered to somebody's mailbox before it was bounced back to you. I could see sendmail or any other rfc822 agent having a problem with this line. It looks like the pup took a uucp hop, and it has that wierd "remote from" crap. >This particular error is happening with a few other ids and if it >occurs to an id, it then occurs consistantly: the requesting id can >not get a response from a majordomo command because of the "Unexpected >Token" error any time it sends a message to majordomo. However - >it doesn't happen to ALL the ids. By id, do you mean user id all at the same site, or by id do you mean email address? If the former, I would say that something is munging majordomo's reply message. Try setting up the majordomo command to send a carbon copy of the message to a local mail drop so you can see the message as it goes out. The easiest way would be to change the To: line in &sendmail defined in the file majordomo.pl to read: To: majordomo-drop, $to then set up the alias majordomo-drop to use the majordomo wrapper and an archive program and away you go. -- 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 Sat Jul 23 21:24:37 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA26976; Sat, 23 Jul 1994 21:24:37 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA26970; Sat, 23 Jul 1994 14:24:27 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA11928 (5.65c/IDA-1.4.4 for ); Sat, 23 Jul 1994 16:48:13 -0400 Message-Id: <199407232048.AA11928@cs.umb.edu> To: debbie@qsun.att.com (Deborah A Hamilton +1 908 949 9459) Cc: majordomo-users@greatcircle.com Subject: Re: Unexpected Token Error In-Reply-To: Your message of "20 Jul 1994 20:33:00 GMT." <9407202032.AA14186@ig1.att.att.com> Date: Sat, 23 Jul 1994 16:48:13 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <9407202032.AA14186@ig1.att.att.com>, Deborah A Hamilton +1 908 949 9459 writes: >Some users are posting mail to majordomo@dsmail.internic.net to >do subscribes, request help, indexes, etc. The message gets >processed but the response that gets sent to the user is >not delivered due to a syntax error. > >The error message that comes back is (Note: owner-graph-ti is aliased >to debbie@qsun.att.com): > >> From: postmaster@ds.internic.net >> Date: Tue, 19 Jul 09:32:00 1994 >> To: debbie@qsun.att.com >> Subject: smtp mail failed >> Status: R >> >> Your mail to UNCCVM.UNCC.EDU is undeliverable. >> ---------- diagnosis ---------- >> <<< 501 Syntax Error. Unexpected Token '@' >> ---------- unsent mail ---------- >>From owner-graph-ti@dsmail.internic.net Tue Jul 19 09:31:58 EDT 1994 >> remote from ds What the heck is a From (not from: line) doing in here. This implies that is was delivered to somebody's mailbox before it was bounced back to you. I could see sendmail or any other rfc822 agent having a problem with this line. It looks like the pup took a uucp hop, and it has that wierd "remote from" crap. >This particular error is happening with a few other ids and if it >occurs to an id, it then occurs consistantly: the requesting id can >not get a response from a majordomo command because of the "Unexpected >Token" error any time it sends a message to majordomo. However - >it doesn't happen to ALL the ids. By id, do you mean user id all at the same site, or by id do you mean email address? If the former, I would say that something is munging majordomo's reply message. Try setting up the majordomo command to send a carbon copy of the message to a local mail drop so you can see the message as it goes out. The easiest way would be to change the To: line in &sendmail defined in the file majordomo.pl to read: To: majordomo-drop, $to then set up the alias majordomo-drop to use the majordomo wrapper and an archive program and away you go. -- 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 Sat Jul 23 21:34:41 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA27055; Sat, 23 Jul 1994 21:34:41 GMT Received: from netcom.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA27049; Sat, 23 Jul 1994 14:34:33 -0700 Received: by netcom.com (8.6.8.1/SMI-4.1/Netcom) id OAA21059; Sat, 23 Jul 1994 14:38:36 -0700 From: sylviac@netcom.com (Sylvia Caras) Message-Id: <199407232138.OAA21059@netcom8.netcom.com> Subject: majordomo v listserv as address To: majordomo-users@greatcircle.com Date: Sat, 23 Jul 1994 14:38:36 -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: 1246 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Three months ago when netcom established my list, I was told to write to listserv@netcom.com When I did, I got instructions about majordomo, and used the address majordomo@netcom.com I used that address is printed publicity and there have been newsletter and bulletin printed articles. Now netcom is telling me I wasn't supposed to be using that address, queries to majrodomo are told my list doesn't exist, and I'm told to use listserv. Netcom says it is impossible to correct the problem, I must use listserv and may not use majordomo, EVER. Are they right? Is there a simple way to alias something or create a reply message from the majordomo address that points to listserv? Or something. It's not too much trouble to redo the electronic instructions, but there's no way I can change the print publicity that's gone out, and I hate to be losing credibility because of the no-such-list message. Any ideas? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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 not to take it up. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From majordomo-users-owner Sat Jul 23 22:04:55 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA27342; Sat, 23 Jul 1994 22:04:55 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA27335; Sat, 23 Jul 1994 15:04:50 -0700 Message-Id: <199407232204.PAA27335@mycroft.GreatCircle.COM> To: sylviac@netcom.com (Sylvia Caras) cc: majordomo-users@greatcircle.com Subject: Re: majordomo v listserv as address In-reply-to: Your message of Sat, 23 Jul 1994 14:38:36 -0700 (PDT) Date: Sat, 23 Jul 1994 15:04:48 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Since this is a mailing list management issue (i.e., what to do when your service provider throws you a curve), and not really something specific to Majordomo, might I suggest that the List-Managers@GreatCircle.COM mailing list might be a more useful place to discuss it than Majordomo-Users@GreatCircle.COM? -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Sat Jul 23 22:06:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA27386; Sat, 23 Jul 1994 22:06:26 GMT Received: from vorlon.mankato.msus.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA27378; Sat, 23 Jul 1994 15:06:18 -0700 Received: (from hayden@localhost) by vorlon.mankato.msus.edu (8.6.9/8.6.9) id RAA04979; Sat, 23 Jul 1994 17:13:12 -0500 Date: Sat, 23 Jul 1994 17:13:12 +0100 From: "Robert A. Hayden" Subject: Re: majordomo v listserv as address To: Sylvia Caras cc: majordomo-users@GreatCircle.COM In-Reply-To: <199407232138.OAA21059@netcom8.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk On Sat, 23 Jul 1994, Sylvia Caras wrote: > Now netcom is telling me I wasn't supposed to > be using that address, queries to majrodomo > are told my list doesn't exist, and I'm told > to use listserv. > > Netcom says it is impossible to correct the problem, > I must use listserv and may not use majordomo, EVER. I would think a simple alias would solve the problem: majordomo:listserv majordomo-owner:listserv-owner owner-majordomo:owner-listserv Unless they have majordomo set aside for soemthing else. ____ Robert A. Hayden <=> hayden@vorlon.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else, dammit -=-=-=-=-=-=-=- (GEEK CODE 2.1) GJ/CM d- H-- s-:++>s-:+ g+ p? au+ a- w++ v* C++(++++) UL++++$ P+>++ L++$ 3- E---- N+++ K+++ W M+ V-- -po+(---)>$ Y++ t+ 5+++ j R+++$ G- tv+ b+ D+ B--- e+>++(*) u** h* f r-->+++ !n y++** From majordomo-users-owner Sun Jul 24 21:26:14 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id VAA07351; Sun, 24 Jul 1994 21:26:14 GMT Received: from sparc by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id OAA07345; Sun, 24 Jul 1994 14:26:03 -0700 Received: by sparc (5.0/SMI-SVR4) id AA22410; Sun, 24 Jul 1994 18:27:42 +0400 Date: Sun, 24 Jul 1994 18:27:41 -0300 (ADT) From: Steve MacLeod Subject: Security problem with wrapper? To: majordomo-users@greatcircle.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII content-length: 2310 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am trying to get majordomo 1.92 running on my SUN Sparc machine running Solaris 2.3 ... I compiled using the posix options ... ... no matter what I do I must leave the wrapper program set as 4755 and owned by root ... this is very unsettling to me, When I set the wrapper to ... 4750 I get errors complaining about ... wrapper - cannot execute .. # echo testing|/usr/lib/sendmail -v sample sample... aliased to "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l sample -f Sample-Owner -h sparc.uccb.ns.ca -s sample-outgoing" "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l sample -f Sample-Owner -h sparc.uccb.ns.ca -s sample-outgoing"... Connecting to via prog... sh: /usr/local/majordomo/wrapper: cannot execute "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l sample -f Sample-Owner -h sparc.uccb.ns.ca -s sample-outgoing"... unknown mailer error 1 owner-sample... aliased to sample-owner sample-owner... aliased to smacleod Postmaster... aliased to smacleod smacleod... Connecting to via local... smacleod... Sent smacleod... Connecting to via local... smacleod... Sent # ls -l wrapper -rwsr-x--- 1 root majordom 7936 Jul 24 17:15 wrapper the error message that gets generated to postmaster is ... ----- Transcript of session follows ----- 554 "|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l sample -f Sample-Owner -h sparc.uccb.ns.ca -s sample-outgoing"... unknown mailer error 1 as well I must leave the /usr/local/majordomo directory set to 755 # cd /usr/local # ls -l total 22 drwxr-xr-x 5 majordom majordom 1024 Jul 24 17:15 majordomo drw-rw---- 4 majordom majordom 512 Jul 7 10:28 mail The only piece of security I can see here is that the users on my system can not write into the majordomo program directory ... if they did they could cause any process to be executed as root ... do I have a problem with this setup? I tied in the posix section changing the uid to 0 (root) ... still no difference ... can the setup be any more secure? Thanks -------------------------------------------------------------------- Steve MacLeod Microcomputer Specialist (902)539-5300x625 Computer Centre University College of Cape Breton Sydney, N.S. Fax (902)562-0119 Canada B1P 5S2 From majordomo-users-owner Mon Jul 25 07:36:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id HAA13734; Mon, 25 Jul 1994 07:36:29 GMT Received: from MegaVolt.hut.nl by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA13727; Mon, 25 Jul 1994 00:36:20 -0700 Received: from pizza.hut.nl by MegaVolt.hut.nl (5.0/SMI-SVR4) id AA05756; Mon, 25 Jul 1994 09:40:08 +0000 Received: by pizza.hut.nl (5.0/SMI-SVR4) id AA28288; Mon, 25 Jul 1994 09:40:13 +0000 From: koos@pizza.hut.nl (Koos van den Hout _U nix and we all_) Message-Id: <9407250840.AA28288@pizza.hut.nl> Subject: Security problem with wrapper? To: majordomo-users@GreatCircle.COM Date: Mon, 25 Jul 94 9:40:12 WET DST X-Mailer: ELM [version 2.3 PL2] Content-Length: 1086 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In a previous message, you wrote : > I am trying to get majordomo 1.92 running on my SUN Sparc machine running > Solaris 2.3 I have the same setup here. I did *not* install it myself but was directly involved (I am root). We had troubles getting it to run until we : - Made the majordomo home dir owned by majordomo and group majordom. - Made the majordomo home dir mode rwxrwxr-x - Added root and deamon to the majordom group in /etc/group The person who did the setup here is now on vacation so I can only answer global questions. Grtx. KH -- /-- Koos van den Hout ----------------------------------------------- Sysop --\ | AtHome:koos@kzdoos.hacktic.nl BBS Koos z'n Doos (+31-3402-56619 14400) | | AtWork:koos@hut.nl,koos@vpro.nl (+31-3402-36647 28800 vfc v32b v42b MNP5) | | URL: http://www.hut.nl | PGP key by finger | Still looking for a license | | /users/koos | koos@hacktic.nl | plate with 'RFC 822'. | | GCS d- p(-) c++(+++) l+ u+++ e++ m+(-) s+/- !n h f+ g+ w(++) t+ r !y(*) | From majordomo-users-owner Mon Jul 25 16:33:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA20517; Mon, 25 Jul 1994 16:33:09 GMT Received: from ns.ge.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id JAA20510; Mon, 25 Jul 1994 09:33:01 -0700 Received: from [3.54.4.10] by ns.ge.com (5.65/GE Gateway 1.23) with SMTP id AA10221; Mon, 25 Jul 94 12:28:30 -0400 Received: from acc113.vf.ge.com (acc113.acc.vf.ge.com) by acc1.acc.vf.ge.com (4.1/GEA Sun server 2.7A)id AA27079; Mon, 25 Jul 94 12:34:40 EDT Date: Mon, 25 Jul 94 12:34:40 EDT From: bdavis@acc1.acc.vf.ge.com (Davis Blake) Message-Id: <9407251634.AA27079@acc1.acc.vf.ge.com> To: majordomo-users@greatcircle.com Subject: Microsoft Mail Problem Resolution Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk A while back I sent out a plea for help with regard to having to support several users that had to use Microsoft Mail, and the problem that the MS Mail software used the first "From xyz line" (not the "From:, Sender:, or Reply-to: lines) when a user tried to reply to mail sent out by majordomo version 1.92 (or any other mail). Thank you for all the replies of sympathy and history of dealing with MS Mail and with Microsoft itself. The problem specific to majordomo software is that it places the owner- as the from address. I have modified the resend script to use the valid_addr of the originator. I have a somewhat limited set of user mail systems: SMTP (sun and chameleon), MAC MS MAIL, PC MS MAIL. It has worked successfully here for my situation, but your mileage may vary with other mail systems. Here it is: diff -c10 ist/resend orig/resend *************** *** 317,339 **** } if ( $infile == 0 ) { &bounce ("Non-member submission from [$from]"); } } if (defined($opt_A) && ! defined($approved)) { &bounce("Approval required"); } - - $valid_from = &valid_addr($from); - $sendmail_sender = $valid_from if $valid_from; $sendmail_cmd = "/usr/lib/sendmail $opt_m -f$sendmail_sender " . join(" ", @ARGV); if (defined($opt_d)) { $| = 1; print "Command: $sendmail_cmd\n"; $status = (system("cat /tmp/resend.$$.out") >> 8); unlink(); exit($status); --- 317,336 ---- *************** ++--+----+----+----+----+----+----+----+----+----+----+----+----+---++ ++ Blake Davis + ++ ++ Chief System Architect + 610.992.6139 Phone ++ ++ Information Services & Technologies + 610.992.6299 FAX ++ ++ Martin Marietta + ++ ++ 640 Freedom Center, 3rd floor + Davis.Blake@ist.vf.ge.com ++ ++ King of Prussia, PA 19406 + ++ ++--+----+----+----+----+----+----+----+----+----+----+----+----+---++ From majordomo-users-owner Mon Jul 25 10:49:03 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA21216; Mon, 25 Jul 1994 17:32:12 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id KAA21206; Mon, 25 Jul 1994 10:31:55 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA11485 (5.65c/IDA-1.4.4 for ); Sun, 24 Jul 1994 17:47:27 -0400 Message-Id: <199407242147.AA11485@cs.umb.edu> To: Steve MacLeod Cc: majordomo-users@greatcircle.com Subject: Re: Security problem with wrapper? In-Reply-To: Your message of "Sun, 24 Jul 1994 18:27:41 -0300." Date: Sun, 24 Jul 1994 17:47:26 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message , Steve MacLeod writes: >I am trying to get majordomo 1.92 running on my SUN Sparc machine running >Solaris 2.3 ... I compiled using the posix options ... ... no matter what I >do I must leave the wrapper program set as 4755 and owned by root ... Yup. That's posix for you. It has to be owned by root. >this is very unsettling to me, When I set the wrapper to ... 4750 I get >errors complaining about ... wrapper - cannot execute .. Your sendmail runs as daemon, so without world execute permission it can't run it. >[error run deleted] >as well I must leave the /usr/local/majordomo directory set to 755 I think you mean 777 8-), but its not that bad since all they can do is run the majordomo programs at the top of the majordomo tree, and that doesn't get them much more access than faking mail to majordomo would. ># cd /usr/local ># ls -l >total 22 >drwxr-xr-x 5 majordom majordom 1024 Jul 24 17:15 majordomo >drw-rw---- 4 majordom majordom 512 Jul 7 10:28 mail > >The only piece of security I can see here is that the users on my system >can not write into the majordomo program directory ... if they did they >could cause any process to be executed as root ... do I have a problem >with this setup? I tied in the posix section changing the uid to 0 (root) >... still no difference ... can the setup be any more secure? Well if your mail host never has mail sent on it (i.e. all mail comes in via smtp) create a bastion directory. Put the wrapper in /usr/local/majordomo/wrappers/wrapper and chown the wrappers directory to user daemon, mode 700. This way sendmail can execute the program since it can access it, but nobody not running as daemon can access the wrapper. Note that people on the mail host who attempt to send mail to majordomo will have it fail since the sendmail they invoke won't be able to access the majordomo directory. That's why we don't suggest a bastion directory approach. BTW if you move sendmail to the side and replace /usr/lib/sendmail with a program that accepts the message and then connects to the smtp port on the current host, the bastion directory method works fine. ssmtp works for this purpose. The only problem is that it doesn't accept the -t flag, but that's not a major problem except for majordomo 8-). No don't ask how I know the above mechanism works 8-(. -- 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 Mon Jul 25 22:09:25 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id WAA25117; Mon, 25 Jul 1994 22:09:25 GMT Received: from gateway.sandelman.ocunix.on.ca by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id PAA25102; Mon, 25 Jul 1994 15:08:43 -0700 Received: from latour.sandelman.ocunix.on.ca (latour.sandelman.ocunix.on.ca [192.139.46.129]) by gateway.sandelman.ocunix.on.ca (8.6.9/8.6.9) with SMTP id SAA13358; Mon, 25 Jul 1994 18:04:59 -0400 Received: from localhost by latour.sandelman.ocunix.on.ca with SMTP id AA14793 (5.65a/IDA-1.4.2); Mon, 25 Jul 94 17:48:56 -0400 Message-Id: <9407252148.AA14793@latour.sandelman.ocunix.on.ca> To: "John P. Rouillard" Cc: Steve MacLeod , majordomo-users@GreatCircle.COM Subject: Re: Security problem with wrapper? In-Reply-To: Your message of "Sun, 24 Jul 1994 17:47:26 EDT." <199407242147.AA11485@cs.umb.edu> Date: Mon, 25 Jul 1994 17:48:55 -0400 From: Michael Richardson Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Or, just set sendmail to queue all messages (Odq in the config file) and it will actually deliver them during the queue run. You'll want to run the queue every 15 minutes at least though. From majordomo-users-owner Mon Jul 25 23:38:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id XAA26639; Mon, 25 Jul 1994 23:38:19 GMT Received: from hp-cv.cv.hp.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id QAA26629; Mon, 25 Jul 1994 16:38:08 -0700 Received: from hp-pcd.cv.hp.com by hp-cv.cv.hp.com with SMTP (1.36.108.7/15.5+IOS 3.22+CV 1.0ext) id AA23369; Mon, 25 Jul 1994 16:41:47 -0700 Received: from hpcvcdv.cv.hp.com by hp-pcd.cv.hp.com with SMTP (1.37.109.8/15.5+IOS 3.22+OM+CV 1.0) id AA22842; Mon, 25 Jul 1994 16:41:46 -0700 Received: by hpcvcdv.cv.hp.com (1.37.109.8/15.5+IOS 3.22[SMTP-rly]+CV 1.0leaf) id AA14700; Mon, 25 Jul 1994 16:41:46 -0700 Date: Mon, 25 Jul 1994 16:41:46 -0700 From: Bruce Hauge Message-Id: <9407252341.AA14700@hpcvcdv.cv.hp.com> To: majordomo-users@greatcircle.com Subject: Address option in lists? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I'm a fairly new user of majordomo, so bear with me! Is there a way to get subscribed users to be added to a list so that their names on the list appear as: bruceh@cv.hp.com instead of: bruceh@hpcvcdv.cv.hp.com A second, but related question, is: Assuming I can achieve the first question, will the "which" command work correctly? It looks like it will still be trying to compare "bruceh@hpcvcdv.cv.hp.com" against "bruceh@cv.hp.com" and not finding a match. I found the "mungedomain" option in the configuration file, but that appears to only work if you were comparing "bruceh@cv.hp.com" against "bruceh@hp.com". Thanks for the help. +------------------------------------------------------------------------+ | Bruce Hauge | | HEWLETT-PACKARD COMPANY EMAIL: bruceh@cv.hp.com | | Integrated Circuits Business Division PHONE: (503) 715-2675 | | 1050 NE Circle Blvd., MS: 2U/HH32 FAX: (503) 715-2145 | | Corvallis, OR 97330 | +------------------------------------------------------------------------+ From majordomo-users-owner Tue Jul 26 00:15:35 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id AAA27255; Tue, 26 Jul 1994 00:15:35 GMT Received: from hermes.intel.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940615) id RAA27243; Mon, 25 Jul 1994 17:15:23 -0700 Received: from pcocd2.intel.com by hermes.intel.com (5.65/10.0i); Mon, 25 Jul 94 17:18:31 -0700 Received: from fiw007 (fiw007.fm.intel.com) by pcocd2.intel.com with SMTP id AA29050 (5.65c/IDA-1.4.4 for ); Mon, 25 Jul 1994 17:18:18 -0700 Received: by fiw007 (4.1/FMDT-RS6000) id AA07440; Mon, 25 Jul 94 17:18:18 PDT From: "Anant Bukkapatnam - FES" Message-Id: <9407251718.ZM7438@fiw007.fm.intel.com> Date: Mon, 25 Jul 1994 17:18:17 -0700 X-Mailer: Z-Mail (3.0.1 23feb94) To: majordomo-users@greatcircle.com Subject: Help Wanted for majordomo1.62 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, I am trying to run majordomo1.62 here. Is there a way in it to deny access to it from a different domain name. Any help on this will be appreciated. Thanks Anant Bukkapatnam From majordomo-users-owner Tue Jul 26 21:07:09 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA14644; Tue, 26 Jul 1994 21:07:09 GMT Received: from firstfloor.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA14637; Tue, 26 Jul 1994 14:06:59 -0700 Received: from et.firstfloor.COM ([198.206.195.36]) by firstfloor.COM (4.1/SMI-4.1) id AA02000; Tue, 26 Jul 94 14:10:58 PDT From: swayland@firstfloor.COM (Scott Wayland, Technical Support) To: majordomo-users@greatcircle.com Subject: RE: Permissions in majordomo are now set to Work As Designed Cc: jjames@firstfloor.COM Reply-To: swayland@firstfloor.COM Date: Tue, 26 Jul 94 14:09:32 PDT Message-Id: <9407262109.204B6C@et.firstfloor.COM> X-Mailer: SelectMAIL 1.2 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hello, We would like to express out sincere gratitude for the excellent advice received from this mailing list with regards to setting up our oid permissions. Our special THANKS to John (rouilj@cs.umb.edu) whos peid script did exactly what is was supposed to do. Scott From majordomo-users-owner Wed Jul 27 01:11:17 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA20208; Wed, 27 Jul 1994 01:11:17 GMT Received: from hermes.intel.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id QAA18154; Tue, 26 Jul 1994 16:26:55 -0700 Received: from pcocd2.intel.com by hermes.intel.com (5.65/10.0i); Tue, 26 Jul 94 16:30:08 -0700 Received: from fiw007 (fiw007.fm.intel.com) by pcocd2.intel.com with SMTP id AA00313 (5.65c/IDA-1.4.4 for ); Tue, 26 Jul 1994 16:29:42 -0700 Received: by fiw007 (4.1/FMDT-RS6000) id AA08285; Tue, 26 Jul 94 16:29:16 PDT From: "Anant Bukkapatnam - FES" Message-Id: <9407261629.ZM8283@fiw007.fm.intel.com> Date: Tue, 26 Jul 1994 16:29:15 -0700 X-Mailer: Z-Mail (3.0.1 23feb94) To: majordomo-users@greatcircle.com Subject: Majordomo Help Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, I need some help desperately, I opened this list to the users to subscribe, this is not a moderated list or anything, some people got subcribed successfully while others were not and the listowner gets this message, Can't append to /usr/local/majordomo/LISTS/shrlist: Interrupted system call I got on to the system, and found out lot of majordomo processes are suspended on it. I do not know the reason, the filesystems,etc seem fine to me. Any help on this will be truly appreciated. Is it because the gates to the list were suddenly opened and there was flood of subscribes? Thanks in advance Anant From majordomo-users-owner Wed Jul 27 00:32:50 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA27907; Wed, 27 Jul 1994 06:55:18 GMT Received: from usc.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id XAA27894; Tue, 26 Jul 1994 23:55:02 -0700 Received: from iris.usc.edu by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA11337; Tue, 26 Jul 94 23:58:38 PDT Received: (kyan@localhost) by iris.usc.edu (8.6.8.1/8.6.7+ucs) id XAA25089 for Majordomo-Users@GreatCircle.COM; Tue, 26 Jul 1994 23:58:37 -0700 Date: Tue, 26 Jul 1994 23:58:37 -0700 From: Kenneth Yan Message-Id: <199407270658.XAA25089@iris.usc.edu> To: Majordomo-Users@GreatCircle.COM Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk lists From majordomo-users-owner Wed Jul 27 20:53:29 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA12047; Wed, 27 Jul 1994 20:53:29 GMT Received: from caesun6.epg.harris.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA12031; Wed, 27 Jul 1994 13:53:16 -0700 Received: from iowa.epg.harris.com by caesun6.epg.harris.com (4.1/SMI-4.1) id AA15382; Wed, 27 Jul 94 16:56:51 EDT Received: by iowa.epg.harris.com (4.1/SMI-4.0) id AA00747; Wed, 27 Jul 94 17:02:18 EDT Date: Wed, 27 Jul 94 17:02:18 EDT From: dmp@epg.harris.com (Donald Patterson) Message-Id: <9407272102.AA00747@iowa.epg.harris.com> To: majordomo-users@greatcircle.com Subject: Help! in configuring majordomo Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk I am just configuring majordomo to manage a number of (15!) lists. I have been testing things with a single list for a few weeks, with things going pretty smoothly. But here are a few questions: 1. Why do my approval requests come from majordom and not majordomo? (They also tell me to send approvals *to* majordom, which is wrong.) My aliases file begins with: # listmgr: majordomo majordomo: "|/net/caesun6/home/users/majordomo/wrapper majordomo" majordomo-owner: dmp owner-majordomo: dmp majordom: dmp 2. Is it possible to have my archives go to a different site (that is not a majordomo server)? Alternatively (better yet?) is there an easy way to periodically push archives to a remote site (by ftp)? That way I could keep (only) the most recent archives at my majordomo site. 3. Is there an easy way that I can make files other than "info" available thru majordomo (such as a FAQ), or should I use ftpmail or something? Thanks in advance, _____________________________________________________________________________ Don Patterson, Iowa'82 \\ INTERNET : dmp@epg.harris.com | _ _ | Harris Corporation \\ UUCP : ...!uunet!x102a!dpatterson |_| |_| | | Engr. Productivity Group \\ CCMAIL : DPatters | _|_ |_/\/\/\|_| 1025 W. Nasa Blvd, MS E300\\ VOICE : (407) 729-3907| | | |_| |_| | Melbourne, FL 32919 \\ FAX : (407) 724-3399| WON BY ONE| |_________| From majordomo-users-owner Wed Jul 27 22:15:52 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id WAA13472; Wed, 27 Jul 1994 22:15:52 GMT Received: from enfm.utcc.utoronto.ca by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA13462; Wed, 27 Jul 1994 15:15:40 -0700 Received: from localhost by enfm.utcc.utoronto.ca with SMTP id <608080>; Wed, 27 Jul 1994 18:07:21 -0400 To: majordomo-users@GreatCircle.COM Subject: majordomo and zmailer? Organization: UT Network & Operations Services, External Network Fac. Mgmt. Phone: +1 416 978 0992 Date: Wed, 27 Jul 1994 18:07:20 -0400 From: "C. Harald Koch" Message-Id: <94Jul27.180721edt.608080@enfm.utcc.utoronto.ca> Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Has anyone used majordomo with zmailer? Anything special I should watch out for? -- C. Harald Koch | University of Toronto Computing & Communications harald@canet.ca | Network & Operations Services +1 416 978 0992 (voice) | External Network Facilities Managment +1 416 978 6620 (fax) | 4 Bancroft Ave., Rm 101, Toronto, ON M5S 1C1 From majordomo-users-owner Thu Jul 28 13:09:38 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA28630; Thu, 28 Jul 1994 13:09:38 GMT Received: from trans2.b30.ingr.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA28611; Thu, 28 Jul 1994 06:09:19 -0700 Received: by trans2.b30.ingr.com (5.65c/1.921207) id AA16835; Thu, 28 Jul 1994 08:01:32 -0500 From: bptatro@trans2.b30.ingr.com (Brian Tatro) Message-Id: <199407281301.AA16835@trans2.b30.ingr.com> Subject: Re: bounce problem (fwd) To: majordomo-users@greatcircle.com Date: Thu, 28 Jul 94 8:01:31 CDT X-Mailer: ELM [version 07.05.00.00 (2.3 PL11)] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, I set up a moderated list, and now everything is being bounced, even mail from list-owner. Any idea what went wrong? Brian -- ========================================================================= This .sig space for rent. E=mc*2 --> It's not just a good idea, It's the LAW! (186,000 Miles/Sec) Brian Tatro Senior Editor Product Translation COMPUSERVE: 72154,531 Intergraph Corporation bptatro@trans2.b30.ingr.com ========================================================================== From majordomo-users-owner Thu Jul 28 06:33:23 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id NAA28915; Thu, 28 Jul 1994 13:25:57 GMT Received: from trans2.b30.ingr.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id GAA28903; Thu, 28 Jul 1994 06:25:44 -0700 Received: by trans2.b30.ingr.com (5.65c/1.921207) id AA16890; Thu, 28 Jul 1994 08:18:02 -0500 From: bptatro@trans2.b30.ingr.com (Brian Tatro) Message-Id: <199407281318.AA16890@trans2.b30.ingr.com> Subject: more bounce info To: majordomo-users@greatcircle.com Date: Thu, 28 Jul 94 8:18:01 CDT X-Mailer: ELM [version 07.05.00.00 (2.3 PL11)] Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Here is a message I received in relation to the previous one sent by me. As far as I can tell, the program wants to move somebody to a bounce list and send them email. It seems that it can not resolve the address. Any hionts appreciated. Brian Forwarded message: > From root Thu Jul 28 02:10 CDT 1994 > Date: Thu, 28 Jul 1994 02:10:02 -0500 > From: MAILER-DAEMON (Mail Delivery Subsystem) > Subject: Returned mail: User unknown > Message-Id: <199407280710.AA16509@trans2.b30.ingr.com> > To: root > > ----- Transcript of session follows ----- > 550 User unknown > > ----- Unsent message follows ----- > Received: by trans2.b30.ingr.com (5.65c/1.921207) > id AA16507; Thu, 28 Jul 1994 02:10:02 -0500 > Date: Thu, 28 Jul 1994 02:10:02 -0500 > Message-Id: <199407280710.AA16507@trans2.b30.ingr.com> > To: Bounces@trans2.b30.ingr.com > From: nobody@trans2.b30.ingr.com > Subject: Bouncing email from mailing lists at trans2.b30.ingr.com > Reply-To: majordomo@trans2.b30.ingr.com > > Your address has been moved to Bounces@trans2.b30.ingr.com > from some other mailing list at trans2.b30.ingr.com > because email to you was bouncing. > > Here are the addresses currently on Bounces@trans2.b30.ingr.com > so that you can see which of your addresses is among them. > The comment for each address shows the date it was moved, <> -- ========================================================================= This .sig space for rent. E=mc*2 --> It's not just a good idea, It's the LAW! (186,000 Miles/Sec) Brian Tatro Senior Editor Product Translation COMPUSERVE: 72154,531 Intergraph Corporation bptatro@trans2.b30.ingr.com ========================================================================== From majordomo-users-owner Fri Jul 29 00:32:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id AAA06243; Fri, 29 Jul 1994 00:32:19 GMT Received: from aw.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA06237; Thu, 28 Jul 1994 17:32:06 -0700 Received: from [198.3.54.113] by aw.com (5.67b/Spike-2.1) id AA24564; Thu, 28 Jul 1994 20:32:27 -0400 Date: Thu, 28 Jul 1994 20:32:27 -0400 Message-Id: <199407290032.AA24564@aw.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: majordomo-users@greatcircle.com From: ari@aw.com (Ari Davidow) Subject: munging addresses and making archives work Cc: guym@aw.com Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Two questions: 1. We are running into some oddness where people sometimes use Eudora, and are recognized by the Majordomo list as "person@aw.com" and sometimes have telnetted in and are recognized as "person". Majordomo appears to be unable to recognize that "person" sending e-mail from aw.com, is the same as "person@aw.com". We are going to turn on munging addresses, but is this likely to work? Have we set something up very wrong? 2. The default config files (version 1.92?) seem to indicate that archiving doesn't yet work: ... # archive_dir [absolute_dir] (undef) # The directory where the mailing list archive is kept. This item does # not currently work. Leave it blank. archive_dir = ... Is this so, or did we just miss something? We =really= need to be able to maintain automated archives.... 3. I can't find the commands or whatever to include that customized page that new subscribers get--the one that would let us (I hope) include stuff beyond "Welcome to foo-talk", but "as a subscriber to foo-talk, you may also be interested in knowing about these resources...." I apologize if these are basic questions--feel free to send me to the appropriate, but heretofore missed, docs and request that I rtfm. ari davidow ari@bc.aw.com ari davidow ari@bc.aw.com From majordomo-users-owner Fri Jul 29 01:42:51 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id BAA06793; Fri, 29 Jul 1994 01:42:51 GMT Received: from cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id SAA06763; Thu, 28 Jul 1994 18:42:28 -0700 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA25845 (5.65c/IDA-1.4.4 for ); Thu, 28 Jul 1994 21:45:52 -0400 Message-Id: <199407290145.AA25845@cs.umb.edu> To: ari@aw.com (Ari Davidow) Cc: majordomo-users@greatcircle.com, guym@aw.com Subject: Re: munging addresses and making archives work In-Reply-To: Your message of "Thu, 28 Jul 1994 20:32:27 EDT." <199407290032.AA24564@aw.com> Date: Thu, 28 Jul 1994 21:45:51 -0400 From: "John P. Rouillard" Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk In message <199407290032.AA24564@aw.com>, Ari Davidow writes: >Two questions: > >1. We are running into some oddness where people sometimes use Eudora, and >are recognized by the Majordomo list as "person@aw.com" and sometimes have >telnetted in and are recognized as "person". Majordomo appears to be unable >to recognize that "person" sending e-mail from aw.com, is the same as >"person@aw.com". We are going to turn on munging addresses, but is this >likely to work? Have we set something up very wrong? Yeah, you need to have from addresses always specify a FQDN. No mungedomain won't work. >2. The default config files (version 1.92?) seem to indicate that archiving >doesn't yet work: >... > # archive_dir [absolute_dir] (undef) > # The directory where the mailing list archive is kept. This item do >es > # not currently work. Leave it blank. >archive_dir = >... >Is this so, or did we just miss something? We =really= need to be able to >maintain automated archives.... Archiving works fine, its just that it can't be controlled remotely yet. Just follow the examples in the README for setting up an archive program. >3. I can't find the commands or whatever to include that customized page >that new subscribers get--the one that would let us (I hope) include stuff >beyond "Welcome to foo-talk", but "as a subscriber to foo-talk, you may >also be interested in knowing about these resources...." newinfo is the command that installs the new info page. -- 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 Jul 29 11:38:22 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id LAA13680; Fri, 29 Jul 1994 11:38:22 GMT Received: from smtp4.aw.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id EAA13672; Fri, 29 Jul 1994 04:38:15 -0700 Received: from East-Message_Server by smtp4.aw.com with WordPerfect_Office; Fri, 29 Jul 1994 07:41:51 -0400 Message-Id: X-Mailer: Novell Symmetry 4.1 Date: Fri, 29 Jul 1994 07:45:11 -0400 From: Herve Bailey To: ari@aw.com, majordomo-users@GreatCircle.COM Cc: guym@aw.com Subject: munging addresses and making archives work -Reply Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk First, Archive works fine. Read previously sent e-mail. You indicated that you are turning up mundged addressing. I requested earlier that any changes be made by me during this test period. I'm concerned that changes can be made in areas where you may not have complete knowledge. one example of this is - you said that the config files indicate archiving may not be working - when in fact it is working fine. PLEASE - instead of trying to interpret the documentation which is TWO YEARS out of date and incomplete, I'd rather you adddress your questions to me directly. From majordomo-users-owner Fri Jul 29 15:26:31 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA15833; Fri, 29 Jul 1994 15:26:31 GMT Received: from hermes.intel.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA15816; Fri, 29 Jul 1994 08:26:17 -0700 Received: from pcocd2.intel.com by hermes.intel.com (5.65/10.0i); Fri, 29 Jul 94 08:29:18 -0700 Received: from fiw007 (fiw007.fm.intel.com) by pcocd2.intel.com with SMTP id AA21644 (5.65c/IDA-1.4.4 for ); Fri, 29 Jul 1994 08:29:10 -0700 Received: by fiw007 (4.1/FMDT-RS6000) id AA10837; Fri, 29 Jul 94 08:28:45 PDT From: "Anant Bukkapatnam - FES" Message-Id: <9407290828.ZM10835@fiw007.fm.intel.com> Date: Fri, 29 Jul 1994 08:28:42 -0700 X-Mailer: Z-Mail (3.0.1 23feb94) To: majordomo-users@greatcircle.com Subject: Clarifications Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi all, I am running majordomo1.62 on our site. Last week I had problems which were beyond me at that point to solve. I posted for some help but seems like none of you have seen that problem. Here is the problem, 1. I get the following error when somebody tried to subscribe to the list, MAJORDOMO ABORT Can't append to /usr/local/majordomo/LISTS/shrlist: Interrupted system call Any ideas on this. Infact this is working NOW again fine without any changes what so ever to majordomo. This leads me to think, that there could have been some of the following problems, a. Since this list was new and opened to everybody, suddenly there were lots of users trying to subscribe. After allowing some of the them to subscribe, majordomo failed on some concurrent processing ( I think the locking failed for some reason, IF I am right). There were atleast 50 users rejected with this problem and I got 50+ mails from majordomo complaining the problem. b. There could have been some disk problems at that time but the system log messages do not indicate anything about it, or any errors what so ever. **************************************************************** 2. This is a question which is totally unrelated to the above one, Is it possible in majordomo 1.62 to reject mail from other domains. This will help because the lists can be maintained with security and some of the users will not have concerns about it. I keep hearing about "munge domain" , I believe this is the feature in majordomo1.93. I am not clear on what it is. Can somebody explain me about this. Thanks in advance Anant From majordomo-users-owner Fri Jul 29 12:36:34 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id RAA17085; Fri, 29 Jul 1994 17:53:20 GMT Received: from caesun6.epg.harris.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id KAA17073; Fri, 29 Jul 1994 10:53:03 -0700 Received: from iowa.epg.harris.com by caesun6.epg.harris.com (4.1/SMI-4.1) id AA24991; Fri, 29 Jul 94 13:56:37 EDT Received: by iowa.epg.harris.com (4.1/SMI-4.0) id AA01743; Fri, 29 Jul 94 14:02:04 EDT Date: Fri, 29 Jul 94 14:02:04 EDT From: dmp@epg.harris.com (Donald Patterson) Message-Id: <9407291802.AA01743@iowa.epg.harris.com> To: majordomo-users@greatcircle.com Subject: get & index, and who/what should I alias majordom to? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk How do I associate a set of files with a particular list? I see majordomo.cf settings: $ftpmail_address What FTPMAIL server should I send requests to? $ftpmail_location What host should FTPMAIL look for my files on? but where do files go that I wish to make accessible to a particular list (or lists)? A 2nd question: the install instructions seem to suggest that majordom (ie., majordomo owner) be aliased to a "real" person. Problem is, all messages being sent by majordomo look like they're coming from majordom. Worse, help command response and approve request instruct people to send majordomo commands to majordom. This implies I should... alias majordom to majordomo or... find a way to change the responses that majordom is sending Help! From majordomo-users-owner Fri Jul 29 14:39:42 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id VAA19428; Fri, 29 Jul 1994 21:15:55 GMT Received: from mycroft.GreatCircle.COM by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id OAA19418; Fri, 29 Jul 1994 14:15:46 -0700 Message-Id: <199407292115.OAA19418@mycroft.GreatCircle.COM> To: "Anant Bukkapatnam - FES" cc: majordomo-users@greatcircle.com Subject: Re: Clarifications In-reply-to: Your message of Fri, 29 Jul 1994 08:28:42 -0700 Date: Fri, 29 Jul 1994 14:15:44 -0700 From: Brent Chapman Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk "Anant Bukkapatnam - FES" writes: # Hi all, # I am running majordomo1.62 on our site. Last week # I had problems which were beyond me at that point to solve. # I posted for some help but seems like none of you have seen that # problem. Here is the problem, # # 1. I get the following error when somebody tried to # subscribe to the list, # # MAJORDOMO ABORT # Can't append to /usr/local/majordomo/LISTS/shrlist: Interrupted system # call # # Any ideas on this. Infact this is working NOW again fine without any # changes what so ever to majordomo. This leads me to think, # that there could have been some of the following problems, # # a. Since this list was new and opened to everybody, suddenly # there were lots of users trying to subscribe. After allowing some of the them # to # subscribe, majordomo failed on some concurrent processing ( I think the locking # failed for some reason, IF I am right). There were atleast 50 users rejected # with # this problem and I got 50+ mails from majordomo complaining the problem. This is what happens when Majordomo eventually gives up after 10 minutes of trying once per second to get a lock on a file (/usr/local/majordomo/LISTS/shrlist in the example given above). This could be because Majordomo doesn't have write permissions for the directory the file is in, or it could be because the file really was locked for 10 minutes by other Majordomo processes. # **************************************************************** # 2. This is a question which is totally unrelated to the above one, # Is it possible in majordomo 1.62 to reject mail from other domains. This will # help because the lists can be maintained with security and some of the users # will not have concerns about it. I keep hearing about "munge domain" , I # believe # this is the feature in majordomo1.93. I am not clear on what it is. Can # somebody # explain me about this. munge_domain is a feature of 1.9x that tells Majordomo to treat addresses "user@bar.com" and "user@foo.bar.com" as identical (without munge_domain, and in all versions prior to 1.9x, Majordomo views those as different addresses). -Brent -- Brent Chapman | Great Circle Associates | Call or email for info about Brent@GreatCircle.COM | 1057 West Dana Street | upcoming Internet Security +1 415 962 0841 | Mountain View, CA 94041 | Firewalls Tutorial dates From majordomo-users-owner Sat Jul 30 03:38:19 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id DAA22853; Sat, 30 Jul 1994 03:38:19 GMT Received: from media.mit.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id UAA22841; Fri, 29 Jul 1994 20:38:08 -0700 Received: by media.mit.edu (5.57/DA1.0.4.amt) id AA13375; Fri, 29 Jul 94 23:41:55 -0400 Received: from localhost by kilpikonna.media.mit.edu; (5.65/1.1.8.2/15Jun94-0758PM) id AA11772; Fri, 29 Jul 1994 23:41:51 -0400 Message-Id: <9407300341.AA11772@kilpikonna.media.mit.edu> To: majordomo-users@greatcircle.com Reply-To: tamm@mit.edu (Steven L. Tamm) Subject: Dec Alpha and Core Dumps Date: Fri, 29 Jul 94 23:41:50 -0400 From: "Steven L. Tamm" X-Mts: smtp Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Hi, Has anyone solved the problems of core dumps with majordomo and perl 4.036 on Dec Alpha's? The problem is with perl and the majordomo script itself, not with the wrapper (as I had once thought). I told my boss the wonders of the majordomo I have on my NetBSD box, and she really want to get this working. -Steve From majordomo-users-owner Sat Jul 30 15:06:24 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA26925; Sat, 30 Jul 1994 15:06:24 GMT Received: from inet-gw-2.pa.dec.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA26915; Sat, 30 Jul 1994 08:06:15 -0700 Received: from us4rmc.pko.dec.com by inet-gw-2.pa.dec.com (5.65/27May94) id AA02510; Sat, 30 Jul 94 07:59:37 -0700 Received: from wrksys.enet by us4rmc.pko.dec.com (5.65/rmc-22feb94) id AA26343; Sat, 30 Jul 94 11:02:52 -0400 Message-Id: <9407301502.AA26343@us4rmc.pko.dec.com> Received: from wrksys.enet; by us4rmc.enet; Sat, 30 Jul 94 11:02:52 EDT Date: Sat, 30 Jul 94 11:02:52 EDT From: Jim Reisert -- MLO5-2/36A -- DTN 223-5747 30-Jul-1994 1103 To: tamm@mit.edu Cc: majordomo-users@us4rmc.pko.dec.com Apparently-To: majordomo-users@greatcircle.com Subject: RE: Dec Alpha and Core Dumps Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Steve wrote: >Has anyone solved the problems of core dumps with majordomo and perl >4.036 on Dec Alpha's? The problem is with perl and the majordomo script >itself, not with the wrapper (as I had once thought). Well, I haven't had a single problem since upgrading to Perl 5, now in either alpha or beta test. I found the sources at: ftp.funet.fi/pub/languages/perl/ports/perl5 - Jim -- James J. Reisert Internet: reisert@wrksys.enet.dec.com Digital Equipment Corp. UUCP: ...decwrl!wrksys.enet.dec.com!reisert 146 Main Street - MLO5-2/M16 Voice: 508-493-5747 Maynard, MA 01754 FAX: 508-493-0700 From majordomo-users-owner Sat Jul 30 15:21:33 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA27009; Sat, 30 Jul 1994 15:21:33 GMT Received: from inet-gw-2.pa.dec.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA27003; Sat, 30 Jul 1994 08:21:26 -0700 Received: from us4rmc.pko.dec.com by inet-gw-2.pa.dec.com (5.65/27May94) id AA02810; Sat, 30 Jul 94 08:08:08 -0700 Received: from wrksys.enet by us4rmc.pko.dec.com (5.65/rmc-22feb94) id AA26359; Sat, 30 Jul 94 11:03:24 -0400 Message-Id: <9407301503.AA26359@us4rmc.pko.dec.com> Received: from wrksys.enet; by us4rmc.enet; Sat, 30 Jul 94 11:11:24 EDT Date: Sat, 30 Jul 94 11:11:24 EDT From: Jim Reisert -- MLO5-2/36A -- DTN 223-5747 30-Jul-1994 1106 To: tamm@mit.edu Cc: majordomo-users@us4rmc.pko.dec.com Apparently-To: majordomo-users@greatcircle.com, tamm@mit.edu Subject: RE: Dec Alpha and Core Dumps Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Steve (tamm@mit.edu) asked: >Has anyone solved the problems of core dumps with majordomo and perl >4.036 on Dec Alpha's? The problem is with perl and the majordomo script >itself, not with the wrapper (as I had once thought). Well, I haven't had a single problem since upgrading to Perl 5, now in either alpha or beta test. I found the sources at: ftp.funet.fi/pub/languages/perl/ports/perl5 - Jim -- James J. Reisert Internet: reisert@wrksys.enet.dec.com Digital Equipment Corp. UUCP: ...decwrl!wrksys.enet.dec.com!reisert 146 Main Street - MLO5-2/M16 Voice: 508-493-5747 Maynard, MA 01754 FAX: 508-493-0700 From majordomo-users-owner Sat Jul 30 15:51:26 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id PAA27127; Sat, 30 Jul 1994 15:51:26 GMT Received: from xt.cs.umb.edu by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id IAA27121; Sat, 30 Jul 1994 08:51:16 -0700 Received: by xt.cs.umb.edu id AA15283 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Sat, 30 Jul 1994 11:55:07 -0400 Date: Sat, 30 Jul 1994 11:55:07 -0400 From: Alexander Fraser Message-Id: <199407301555.AA15283@xt.cs.umb.edu> To: majordomo-users@greatcircle.com Cc: tamm@mit.edu, reisert@wrksys.enet.dec.com In-Reply-To: <9407301503.AA26359@us4rmc.pko.dec.com> (message from Jim Reisert -- MLO5-2/36A -- DTN 223-5747 30-Jul-1994 1106 on Sat, 30 Jul 94 11:11:24 EDT) Subject: RE: Dec Alpha and Core Dumps Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk >>>>> Jim Reisert writes: Steve (tamm@mit.edu) asked: Has anyone solved the problems of core dumps with majordomo and perl 4.036 on Dec Alpha's? The problem is with perl and the majordomo script itself, not with the wrapper (as I had once thought). Well, I haven't had a single problem since upgrading to Perl 5, now in either alpha or beta test. I found the sources at: ftp.funet.fi/pub/languages/perl/ports/perl5 I have Majordomo working with perl5 after escaping a couple of $ in config_parse.pl. However, I am still having some problems with resend. In the routine check_hdr_line there is an undef which is causing the following .= op to return garbage (note that this is a problem with perl5a11d, not resend itself; I posted it to comp.lang.perl). I suppose I will hack around this on Monday. Jim, are you using resend? Cheers, Alex --- Alexander Fraser alex@cs.umb.edu From majordomo-users-owner Sun Jul 31 02:20:01 1994 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id CAA06531; Sun, 31 Jul 1994 02:20:01 GMT Received: from nova.unix.portal.com by mycroft.GreatCircle.COM (8.6.5/SMI-4.1/Brent-940726) id TAA06515; Sat, 30 Jul 1994 19:19:45 -0700 Received: from jobe.shell.portal.com (jobe.shell.portal.com [156.151.3.4]) by nova.unix.portal.com (8.6.7/8.6.4) with ESMTP id TAA26154 for ; Sat, 30 Jul 1994 19:22:58 -0700 Received: from localhost (chan@localhost) by jobe.shell.portal.com (8.6.4/8.6.4) id TAA12469 for majordomo-users@GreatCircle.COM; Sat, 30 Jul 1994 19:22:56 -0700 Date: Sat, 30 Jul 1994 19:22:56 -0700 From: Jeff Chan Message-Id: <199407310222.TAA12469@jobe.shell.portal.com> To: majordomo-users@GreatCircle.COM Subject: list to usenet gateway? Sender: Majordomo-Users-Owner@GreatCircle.COM Precedence: bulk Sorry if this isn't the appropriate place to post, but I'd like to connect one of my lists to a usenet newgroup with a one-way gateway. Does anyone have advice or pointers to a faq about doing this? Please reply by mail if you have info. Thanks in advance, Jeff Chan chan@shell.portal.com