From jeff@onion.rain.com Fri Oct 2 19:36:11 1992 Return-Path: Received: from onion.rain.com by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-920924) id AA05970; Fri, 2 Oct 92 19:36:11 PDT Received: by onion.rain.com (/\==/\ Smail3.1.25.1 #25.12) id ; Fri, 2 Oct 92 19:36 PDT Message-Id: To: majordomo-users@GreatCircle.COM Reply-To: jeff@onion.rain.com Subject: A tiny bug with request-recording Date: Fri, 02 Oct 92 19:35:54 -0700 From: Jeff Beadles Oops, I had forgotten to send in this little bugfix. It probably doesn't hurt many folks, but in request-recording, there's ... (lines 18-22) &ParseMailHeader(STDIN, *hdrs); $reply_to = &RetMailAddr(*hdrs); $reply_to = join(", ", &ParseAddrs($reply_to)); $in_reply_to = $hdrs{"message-id"} . ", from " . $hdrs{"from"}; $list = @ARGV[0]; ^- This should be '$' as in "$list = $ARGV[0];" You want a single element of ARGV, thus it should be referenced with a dollar sign. (If you had an associative array, it would be: "$list = $ARGV{0};". The []'s & {}'s indicate that it is an array.) I dunno why this works, but it does, at least for most people. Also, I've been thinking about the stripping of comments from user's email addresses. I'm thinking about leaving it turned off by default, but allowing the user to put the following in their majordomo.cf file: $strip_address_comments = 1; Sound reasonable? I'll hopefully have a patch available in a few days. (work is hell right now. :) Later, -Jeff -- Jeff Beadles jeff@onion.rain.com From brent@GreatCircle.COM Fri Oct 16 16:21:58 1992 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA15643; Fri, 16 Oct 92 16:21:58 PDT Message-Id: <9210162321.AA15643@mycroft.GreatCircle.COM> To: majordomo-users@GreatCircle.COM Subject: [bostic@vangogh.CS.Berkeley.EDU (Keith Bostic): Everyone complains about the clueless, but...] Date: Fri, 16 Oct 92 16:21:56 -0700 From: Brent Chapman I am _so_ tempted to set something like this up... It would be absolutely trivial under Majordomo... Any volunteers braver than I? :-) -Brent ------- Forwarded Message Date: Fri, 16 Oct 92 15:14:05 -0700 From: bostic@vangogh.CS.Berkeley.EDU (Keith Bostic) Message-Id: <9210162214.AA00568@vangogh.CS.Berkeley.EDU> To: /dev/null@vangogh.CS.Berkeley.EDU Subject: Everyone complains about the clueless, but... From: dd@mv.us.adobe.com (David DiGiacomo) Subject: Everyone complains about the clueless, but... (N.B. Honeyman did it first.) Date: Tue, 13 Oct 1992 11:35:27 -0400 From: mathew@mantis.co.uk (mathew) To: nm-list@reef.cis.ufl.edu Subject: clueless list Attacking Deep Structure writes: | MJM -- I have an idea. Why don't you create a new list to which any | person who sends a subscribe/unsubscribe message to a list proper | will be added, in addition to having his request fulfilled? This | way, a list will slowly be built up of people who simply have no clue | about how mailing lists work. | | Each day, a daemon will send a message out to everyone on the list, saying | something like, "You have been automatically added to this list because | you are an ignorant dipshit. There is no one watching this list; the | only way you can become unsubscribed is to figure out the Internet | standard for issuing control messages to mailing lists. If you had | followed proper etiquette to begin with, you would not now be on this | list. Later, d00d." | | This public service list would be available to all list maintainers, | and would have a conspicuous normal address like | "dumb-fuckers-sender." The brainless sods who were subscribed could | bleat like sheep to each other as they sent mail to the list trying to | get unsubscribed. I'm sure it would sustain itself quite nicely after | it had been operational for about a day and a half. | | This is a serious request. I've done it. clueless@mantis.co.uk, the Clueless Users Network Test System (aka the Clueless Users Mailing List). To subscribe, forge mail from the guilty party saying subscribe clueless and send it to clueless-request@mantis.co.uk. He can then happily reply to the regular mail messages, and have his replies sent to everyone else on the list. He can also send lots of "UNSUB CLUELESS" messages to clueless@mantis.co.uk and have them forwarded too. Eventually he'll discover the right way to unsubscribe. The regular mail message reads: > From: clueless@mantis.co.uk > To: clueless@mantis.co.uk > Subject: Welcome, clueless user! > > Welcome to the Clueless Users Network Test System, an intelligence test > for the ignorant and impolite. > > You have been automatically added to this mailing list because you sent a > subscription request like "UNSUB ME" out to the entire readership of a > mailing list, instead of sending it to the list server or list maintainer. > > There is nobody of worth reading this mailing list. The only way you can > become unsubscribed is to figure out the standard way of unsubscribing > from an Internet mailing list. Until that time, you will get these > messages regularly. > > If you made an innocent mistake in sending your "UNSUB ME" out to the > entire list, then you will know how to unsubscribe from this list > immediately and no harm will be done. > > If, on the other hand, you simply have no clue how to deal with mailing > lists, you'd better start reading up on the subject before you go > blundering around again. Your attention is cordially drawn to the > newsgroups news.announce.newusers, news.newusers.questions, and > news.answers. > > Final hint: the mailing list address is clueless@mantis.co.uk. > > Have fun. mathew ------- End of Forwarded Message From brent@GreatCircle.COM Sun Oct 25 23:20:46 1992 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA03887; Sun, 25 Oct 92 23:20:46 PST Message-Id: <9210260720.AA03887@mycroft.GreatCircle.COM> To: scs@lokkur.dexter.mi.us, phil@eecs.nwu.edu, neumann@csl.sri.com, marke@violet.berkeley.edu, rob@violet.berkeley.edu, steve@uunet.uu.net, bjork@telebit.com, mcb@presto.ig.com, shibumi@presto.ig.com, majordomo-users@GreatCircle.COM, sage-online@usenix.org Reply-To: brent@GreatCircle.COM Subject: New mailing list for Internet mailing list managers Date: Sun, 25 Oct 92 23:20:45 -0800 From: Brent Chapman There was a "Mailing Lists" workshop session at the USENIX System Administration Conference (LISA VI) in Long Beach, CA, on October 22, 1992. The participants in that workshop expressed a desire for a mailing list for discussions of issues related to managing Internet mailing lists, including (but not limited to) software, methods, mechanisms, techniques, and policies. I've created the list as "List-Managers@GreatCircle.COM". That address is a direct mail reflector; all messages sent to that address are immediately forwarded to the list. There is digestified version of the list is available as "List-Managers-Digest@GreatCircle.COM". The digestified version has exactly the same messages as the direct version; the messages are simply bundled into digests daily (or more frequently, if traffic warrants). Both lists are unmoderated. To join the List-Managers mailing list, send the command subscribe list-managers in the body of a message to "Majordomo@GreatCircle.COM". If you want to subscribe something other than the account the mail is coming from, such as a local redistribution list, then append that address to the "subscribe" command; for example, to subscribe "local-list-managers": subscribe list-managers local-list-managers@your.domain.net To subscribe to the digestified version, substitute "list-managers-digest" for "list-managers" in the examples above. The list is currently in "hold down" mode while the initial flood of subscription requests is processed. All messages sent to the list while it's in this mode will be returned to the sender with a note asking the sender to hold on to the message until the list is opened for general traffic. I expect the initial flood of subscription requests to subside and the list to be opened for general traffic around the end of October. All messages to the list are being archived. A copy of the archive is available by anonymous FTP from host FTP.GreatCircle.COM, directory "pub/archive", compressed file "list-managers.Z". The copy of the archive available by anonymous FTP is updated every night at midnight local time (0700 GMT in the summer, 0800 GMT in the winter). At some point, I intend to add archive-access commands to the Majordomo server, to make the archives available to folks without anonymous FTP access. I'll announce that when it happens. I'm very aggressive when it comes to bounced email. If email to you bounces for more than 24 hours, I'll probably simply drop you from the list; you'll have to resubscribe when you get the problem fixed, and retrieve the archives to find out what you missed. For further information, contact: Brent Chapman Great Circle Associates Brent@GreatCircle.COM 1057 West Dana Street +1 415 962 0841 From brent@GreatCircle.COM Wed Oct 28 10:50:29 1992 Return-Path: Received: from localhost by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA13115; Wed, 28 Oct 92 10:50:29 PST Message-Id: <9210281850.AA13115@mycroft.GreatCircle.COM> To: List-Managers@GreatCircle.COM, Majordomo-Users@GreatCircle.COM Subject: Re: How does majordomo get around sendmail limits In-Reply-To: Your message of Wed, 28 Oct 92 09:36:52 -0800 Date: Wed, 28 Oct 92 10:50:28 -0800 From: Brent Chapman Michael Rutman writes: # I am using majordomo, and it looks like it justs creates and mantains # an :include file for the aliases. Don't these files have 1024 # character limits? Or am I just seriously misunderstanding things. Some old versions of Sendmail may have such a limitation, but it is definitely not present in the version of Sendmail that I'm using (the standard one shipped by Sun with SunOS 4.1.1). The Firewalls mailing list is over 21k long, and the Firewalls-Digest list is over 4k, and both work just fine. Questions like this are more appropriate to Majordomo-Users than List-Managers, by the way. Majordomo-Users is for discussions specificly related to the Majordomo software. List-Managers is for more general mailing list management discussions, like policies, procedures, common problems, and so forth. -Brent From barb@locutus.cs.colorado.edu Thu Oct 29 17:54:48 1992 Return-Path: Received: from locutus.cs.colorado.edu by mycroft.GreatCircle.COM (4.1/SMI-4.1/Brent-921015) id AA19015; Thu, 29 Oct 92 17:54:48 PST Received: by locutus.cs.colorado.edu id AA00352 (5.65c/IDA-1.4.4 for majordomo-users@greatcircle.com); Thu, 29 Oct 1992 18:50:58 -0700 Date: Thu, 29 Oct 1992 18:50:58 -0700 From: Barbara Dyker Message-Id: <199210300150.AA00352@locutus.cs.colorado.edu> Received: by NeXT Mailer (1.63) To: majordomo-users@GreatCircle.COM Subject: helpful create list script Cc: ornstein@locutus.cs.colorado.edu This is a script to create a new majordomo mailing list. I have it runnging from inetd so people who don't have accounts on our majordomo system can create lists. Although it can be run normally as well. The list doesn't really exist until $whomai_owner sets up the aliases. majordomo stream tcp nowait mjrdomo /usr/local/etc/tcpd create-list Barbara J. Dyker Department of Computer Science Computer Systems Manager Campus Box 430B, ECEE00-69 barb@cs.colorado.edu University of Colorado (303) 492-2545 Boulder, CO 80309-0430 #!/usr/local/bin/taintperl # create-list: create a new majordomo managed mailing list. # Sets up all the files and sends mail to $whoami_owner to # create aliases. Change $notify to notify someone else. # Also notifies the list owner with an introduction. # # Copyright 1992, Barbara J. Dyker. All Rights Reserved. For use by # permission only. # barb@cs.colorado.edu $| = 1; # set path explicitly $ENV{'PATH'} = "/bin:/usr/bin:/usr/ucb"; print "\nHowdy, Majordomo here. You are about to create a new mailing list. If that is not your intention, disconnect now.\n\n"; # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; die("$cf not readable; stopped") if (! -r $cf); eval(`cat $cf`); $notify = $whoami_owner; # Setup the list include file while ($listname eq "" || -e "$listdir/$listname" || $listname !~ /^[-_0-9a-zA-Z]*$/) { print "Enter list name: "; $listname = ; &wack($listname); } &touch("$listdir/$listname"); chmod(0664,"$listdir/$listname"); # Password while ($password eq "") { print "Enter administrative password for $listname (plain text): "; $password = ; &wack($passwd); } open(PASS,">$listdir/$listname.passwd") || die "Can't open $listname.passwd: $!\n"; print PASS "$password\n"; close(PASS); chmod(0664,"$listdir/$listname.passwd"); # Info file print "Enter info file...\n This file will be mailed to each new subscriber. Enter a period (.) on a line by itself to end.\n\n"; open(INFO,">$listdir/$listname.info") || die "Can't open $listname.info: $!\n"; while () { &wack($_); last if ($_ eq '.'); print INFO "$_\n"; } close(INFO); chmod(0664,"$listdir/$listname.info"); # Owner print "Email address for mailing list approvals: "; $owner = ; &wack($owner); # Closed print "Should all subscribe/unsubscribe requests require approval? (y/n) "; $closed = ; &wack($closed); if ( $closed eq "y" ) { &touch("$listdir/$listname.closed"); chmod(0664,"$listdir/$listname.closed"); } # Notify majordomo for aliases open(MAIL,"|/usr/lib/sendmail $notify") || die "Can't open sendmail: $!\n"; select(MAIL); $ENV{'USER'} = "Majordomo" if ($ENV{'USER'} eq ""); print <<"EOM"; From: $ENV{'USER'}@$whereami To: $notify Subject: please setup aliases for newly created list Listname: $listname Owner: $owner Closed: $closed $listname: $listname-alias@$whereami $listname-alias: :include:$listdir/$listname $listname-request: "|$homedir/wrapper request-recording $listname" $listname-approval: $owner EOM close(MAIL); select(STDOUT); print "\n$notify notified to create aliases.\n"; # Notify owner &wack($password); open(MAIL,"|/usr/lib/sendmail $owner") || die "Can't open sendmail: $!\n"; select(MAIL); print <<"EOM"; From: $whoami To: $owner Subject: New mailing list created for you Listname: $listname Password: $password Owner: $owner Closed: $closed This list is managed by $whoami, and automated mailing list manager. You are the owner of this mailing list. Messages to this mailing list should be addressed to $listname@$whereami. They will be delivered to all users who subscribe to $listname. A closed list is one where you will be asked to approve all subscribe requests. Otherwise, you will only be required to approve requests that are made by someone other than for whom the request is made. As the owner of $listname, $whoami will ask you to approve subscribe/unsubscribe requests as needed. All commands to Majordomo should be sent via email to $whoami in the body of a message. Majordomo understands the following password-protected commands to allow you to perform routine mailing list housekeeping activities: approve {subscribe|unsubscribe}
Allows a list owner to subscribe or unsubscribe someone from their list. passwd Allows a list owner to change the password for their list. newinfo Allows a list owner to set the text a user receives when they do an "info" command or subscribe to the list. In addition, $whoami understands the following commands that any user may submit: subscribe [
] Subscribe yourself (or
if specified) to the named . unsubscribe [
] Unsubscribe yourself (or
if specified) from the named . which [
] Find out which lists you (or
if specified) are on. who Find out who is on the named . info Retrieve the general introductory information for the named . lists Show the lists served by this Majordomo. help Retrieve this message. end Stop processing commands (useful if your mailer adds a signature). For questions or problems with Majordomo, email $whoami_owner. Sincerely, $whoami EOM close(MAIL); select(STDOUT); print "\n$owner notified about how it works.\n"; print "\nLater.\n"; # Like chop, but removes any and only cr/nl from the end of the string. # This is for when we get started via inetd. sub wack { foreach (@_) { /[\r\n]*$/; $_ = $`; } } sub touch { foreach (@_) { open(FILE,">$_") || die "Can't open $_: $!\n"; close(FILE); } }