From majordomo-workers-owner Tue Apr 4 06:06:15 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA09211; Tue, 4 Apr 2000 06:02:32 -0700 (PDT) Received: from thelab.hub.org (nat196.230.mpoweredpc.net [142.177.196.230]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA09204 for ; Tue, 4 Apr 2000 06:02:27 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id KAA05210; Tue, 4 Apr 2000 10:18:44 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 4 Apr 2000 10:18:44 -0300 (ADT) From: The Hermit Hacker To: Michael Yount , mj2-dev@csf.colorado.edu Subject: Blank messages/MS Exchange to /dev/null ... ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Morning all ... Trying to debug a problem here where is someone sends a blank message from a MS Outlook/Exchange client to a Majordomo2 list, it just tends to disappear ... I set owners on the list to be myself: # owners # (empty) [address_array] # Who owns this list or majordomo installation? Majordomo will internally # forward mail received at the -owner address to all of these addresses. configset unixs owners << ENDAAB marc.fournier@acadiau.ca ENDAAB And the logs show: Apr 4 10:10:07 new-relay sendmail[20918]: e34DA6w20918: from=, size=1338, class=0, nrcpts=1, msgid=, proto=ESMTP, daemon=MTA, ] Apr 4 10:10:08 new-relay sendmail[20930]: e34DA8w20930: clone e34DA6w20918, owner=owner-unixs Apr 4 10:10:14 new-relay sendmail[20930]: e34DA8w20930: to="|/usr/local/lib/majordomo/bin/mj_enqueue -r -d acadiau.ca -l unixs", ctladdr= (1/0), delay=00:00:08, xdelay=00:00:03, mait Apr 4 10:10:16 new-relay sendmail[20987]: e34DAGw20987: from=, size=2032, class=0, nrcpts=1, msgid=<200004041310.e34DAGw20987@new-relay.acadiau.ca>, proto=SMTP, daemon=MTA, relay=lo] Apr 4 10:10:18 new-relay sendmail[20989]: e34DAGw20987: to=, delay=00:00:02, xdelay=00:00:01, mailer=esmtp, pri=122032, relay=relay.acadiau.ca. [131.162.2.90], dsn=2.0.0, stat=Sent (KAA) But I never actually see the message ... I just checked in the QUEUE directory and found the messages, so am not sure why I'm not seeing them in my mailbox ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From majordomo-workers-owner Tue Apr 4 06:23:57 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA09264; Tue, 4 Apr 2000 06:06:40 -0700 (PDT) Received: from thelab.hub.org (nat196.230.mpoweredpc.net [142.177.196.230]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id GAA09255 for ; Tue, 4 Apr 2000 06:06:34 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id KAA05277; Tue, 4 Apr 2000 10:22:56 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 4 Apr 2000 10:22:44 -0300 (ADT) From: The Hermit Hacker To: my2@hub.org Subject: Duplicate delivery supression ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk How do I turn that thing off? :) Trying to investigate a problem with lack of delivery of messages at work, where the user sends from MSOutlook/Exchange, and having found the error messages, they appear to all be: Subject: EFAA-D829-D8FC : CONSULT unixs Duplicate Message Checksum (Fri Mar 17 09:24:55 2000) Duplicate Partial Message Checksum (Fri Mar 17 09:24:55 2000) All the subjects are different, just the messages are blank: JAA-10065-unixs:Subject: E6C5-B487-6B5D : CONSULT unixs JAA-10065-unixs:Subject: blank test message from exchange KAA-20311-unixs:Subject: 8419-2252-854E : CONSULT unixs KAA-20311-unixs:Subject: test from exch with no body KAA-21189-unixs:Subject: EFAA-D829-D8FC : CONSULT unixs KAA-21189-unixs:Subject: another blank one from exch LAA-10895-unixs:Subject: A36D-B89B-8A95 : CONSULT unixs LAA-10895-unixs:Subject: empty msg from exch March 30 The problem: several of our lists are used as 'status lists', so that all ppl do is send a subject and no message body ... and, quite frankly, I don't want to have to 'accept' each on individually as they go through :) I've looked through the DEFAULT config, and can't find anything to suppress this, unless setting dup_lifetime=0 is how to do it? Thanks... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From majordomo-workers-owner Thu Apr 6 10:51:15 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA13093; Thu, 6 Apr 2000 10:41:59 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA13084 for ; Thu, 6 Apr 2000 10:41:53 -0700 (PDT) Received: from ee-nt (eckert@netcom10.netcom.com [199.183.9.110]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id KAA19657; Thu, 6 Apr 2000 10:58:32 -0700 (PDT) Message-Id: <3.0.5.32.20000406105409.00991280@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 06 Apr 2000 10:54:09 -0700 To: mj2-dev@csf.colorado.edu, majordomo-workers@GreatCircle.COM From: SRE Subject: apparent substitute_vars() bug (using $INCLUDE-help) Cc: eckert@climber.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk It's a little-known feature of Mj2 that help files can include other help files... something Jason added to allow text to be in more than one place without the two places getting out of synch. For example, in "files/en/help/aliasremove", you'll find: | NOTE: 'aliasremove' is the same as 'unalias' | Text below is from "help unalias": | $INCLUDE-help/unalias I just (re)discovered that this is a pathname, and realized that the current configset_* help files contain previously extracted portions of configshow output... which are now in "files/en/config/*" and don't need to be parsed out of configshow. On the other hand, they don't REALLY want to be duplicated in "files/en/help/configset_*", so I tried using $INCLUDE-config/addr_require_fqdn and it worked just great. Almost. For each line in the help file AFTER the $INCLUDE statement, I got this error: >> --== print on closed filehandle Symbol::GEN59 at >> /usr/local/lib/perl5.004/i386-freebsd/5.00404/IO/Handle.pm >> line 365, chunk 30. Three questions: 1. where should the $INCLUDE syntax be documented? 2. where can the $INCLUDE syntax be used? (only in help?) 3. is Majordomo.pm::substitute_vars() the only place $INCLUDE is evaluated? 4. Anyone want to steer me or just go fix this? The bug is that substitute_vars() is recursive, but always opens the output file and always closes the input file. Oops! Print to closed file handle results. I think $depth == 0 could be checked to decide, but hesitate to muck with this routine without guidance. The output file is a unique name in the tmp directory, so recursive calls may need to append to it... or it may need to be left open until the depth returns to 0. SRE mailto:eckert@climber.org | http://www.climber.org/eckert/ Info on peak climbing email lists mailto:info@climber.org Things change. People change. Things change people. From majordomo-workers-owner Thu Apr 6 12:06:22 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA13862; Thu, 6 Apr 2000 12:04:07 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA13855 for ; Thu, 6 Apr 2000 12:04:02 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id OAA21607; Thu, 6 Apr 2000 14:20:44 -0500 To: mj2-dev@csf.colorado.edu, majordomo-workers@GreatCircle.COM Subject: Re: apparent substitute_vars() bug (using $INCLUDE-help) References: <3.0.5.32.20000406105409.00991280@pop.climber.org> From: Jason L Tibbitts III Date: 06 Apr 2000 14:20:44 -0500 In-Reply-To: SRE's message of "Thu, 06 Apr 2000 10:54:09 -0700" Message-ID: Lines: 25 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "S" == SRE writes: S> 1. where should the $INCLUDE syntax be documented? Wherever the other expansions are documented. This should at least be referenced in the documentation for the 'put' command. S> 2. where can the $INCLUDE syntax be used? (only in help?) In any file referenced anywhere; it's a generic substitution. $INCLUDE'd files can have $INCLUDE statements. Depth is currently limited to 3. S> 3. is Majordomo.pm::substitute_vars() the only place $INCLUDE is S> evaluated? Yes. S> 4. Anyone want to steer me or just go fix this? The bug is that S> substitute_vars() is recursive, but always opens the output file and S> always closes the input file. Oops! The output filehandle should not be closed; it will automatically close itself when it goes out of scope. - J< From majordomo-workers-owner Thu Apr 6 14:36:19 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA14966; Thu, 6 Apr 2000 14:31:35 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA14959 for ; Thu, 6 Apr 2000 14:31:30 -0700 (PDT) Received: from ee-nt (eckert@netcom4.netcom.com [199.183.9.104]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id OAA21480; Thu, 6 Apr 2000 14:48:02 -0700 (PDT) Message-Id: <3.0.5.32.20000406142305.009c2250@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 06 Apr 2000 14:23:05 -0700 To: Jason L Tibbitts III From: SRE Subject: Re: Mj2: Re: apparent substitute_vars() bug (using $INCLUDE-help) Cc: mj2-dev@csf.colorado.edu, majordomo-workers@GreatCircle.COM In-Reply-To: References: <3.0.5.32.20000406105409.00991280@pop.climber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Thanks for the lightning-speed response, Jason! At 02:20 PM 4/6/00 -0500, Jason L Tibbitts III wrote: >$INCLUDE'd files can have $INCLUDE statements. >Depth is currently limited to 3. I buffed up the error message to show the current depth and the file being included. >The output filehandle should not be closed; it will automatically close >itself when it goes out of scope. I went ahead and closed it when exiting with $depth==0, just to be clean. I've tested the patch, and will commit it immediately. Revised help files to follow. >S> 1. where should the $INCLUDE syntax be documented? >Wherever the other expansions are documented. This should at least be >referenced in the documentation for the 'put' command. Yep, that's where the others are, which I'll mention in "help admin". >S> 2. where can the $INCLUDE syntax be used? (only in help?) >In any file referenced anywhere; it's a generic substitution. >From "help put", are these sorts of limitations still valid? > info > ---- > Sent in response to an info request. No variable substitutions are done. According to the old README.FILES, some files do not have any variable substitution done... so would $INCLUDE work? If so, would any other variables work? (if so, I'll update help) SRE mailto:eckert@climber.org | http://www.climber.org/eckert/ Info on peak climbing email lists mailto:info@climber.org "I know God will not give me anything I can't handle. I just wish that He didn't trust me so much." -- Mother Teresa From majordomo-workers-owner Thu Apr 6 22:06:20 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA18522; Thu, 6 Apr 2000 21:54:12 -0700 (PDT) Received: from thelab.hub.org (nat196.224.mpoweredpc.net [142.177.196.224]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id VAA18515 for ; Thu, 6 Apr 2000 21:54:07 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id CAA30989; Fri, 7 Apr 2000 02:10:47 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 7 Apr 2000 02:10:47 -0300 (ADT) From: The Hermit Hacker To: Michael Yount , mj2-dev@csf.colorado.edu Subject: Mailing lists losing configs ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Okay, I reported this once, but had no proof ... now I have proof. My mailing lists are randomly losing bits and pieces of their configurations: %!g grep X-Mail pgsql-*/*config* pgsql-committers/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-core/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-general/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-hackers/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-interfaces/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-novice/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-patches/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-ports/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-sql/_config: 'X-Mailing-List: $LIST@postgresql.org' %id uid=93(majordom) gid=1(daemon) groups=1(daemon) %!gr grep X-Mail pgsql-*/*config* pgsql-admin/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-committers/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-core/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-general/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-interfaces/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-novice/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-patches/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-ports/_config: 'X-Mailing-List: $LIST@postgresql.org' pgsql-sql/_config: 'X-Mailing-List: $LIST@postgresql.org' If you notice, the top list has 'pgsql-hackers' in it, the bottom list has it missing ... in fact, its complete _config file has been reduced to: %cat !$/_config cat pgsql-hackers//_config $VAR1 = { 'raw' => { 'sequence_number' => 5 }, 'parsed' => {} }; My procmailrc rules are based on the 'X-Mailing-List' header, so as soon as my filter breaks, I know that the _config file has once more been reset :( Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From majordomo-workers-owner Fri Apr 7 07:36:39 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA25624; Fri, 7 Apr 2000 07:21:56 -0700 (PDT) Received: from thelab.hub.org (nat196.224.mpoweredpc.net [142.177.196.224]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA25617 for ; Fri, 7 Apr 2000 07:21:51 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id LAA82228; Fri, 7 Apr 2000 11:38:41 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 7 Apr 2000 11:38:41 -0300 (ADT) From: The Hermit Hacker To: Michael Yount , mj2-dev@csf.colorado.edu Subject: More on 'duplicates issue' ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Just to add more to the fray ... we have a list here that we send a note to on the reboot of one of our servers ... the exact same message each and every time .. guess what? since moving to majorodom2, we haven't been receiving it :) IMHO, suppression of duplicates should be off by default, not on ... same as it was for Majordomo1 ... if you run a list that has a problem with it, then you should have to enable it, but that way *you* know it is enabled, instead of thinking you have a problem with your list(s) cause you didn't know it was enabled ... Then again, I'm having a problem with getting messages back to 'owner' on these lists, so this wouldn't be such a problem, but still ... from my past experiences, it looks like we've fixed a problem that didn't exist before, or, at least, was so rare nobody cared :( Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From majordomo-workers-owner Fri Apr 7 07:51:15 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA25732; Fri, 7 Apr 2000 07:31:20 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA25725 for ; Fri, 7 Apr 2000 07:31:15 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id JAA23790; Fri, 7 Apr 2000 09:48:05 -0500 To: majordomo-workers@GreatCircle.COM, mj2-dev@csf.colorado.edu Subject: Re: More on 'duplicates issue' ... References: From: Jason L Tibbitts III Date: 07 Apr 2000 09:48:05 -0500 In-Reply-To: The Hermit Hacker's message of "Fri, 7 Apr 2000 11:38:41 -0300 (ADT)" Message-ID: Lines: 24 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "THH" == The Hermit Hacker writes: THH> IMHO, suppression of duplicates should be off by default, not on I disagree. For certain atypical lists you actually want to see the same message over and over again. For the vast majority of cases, you want to trap duplicates. Sure, the trivial method for turning it off should be in the docs and in the FAQ and in the introductory message sent when a new list is created (when that functionality goes in) and perhaps the user should be queried about it when a list is converted from Mj1 to Mj2. But we have to choose defaults that are appropriate for the vast majority of lists. And that is to filter duplicates. THH> from my past experiences, it looks like we've fixed a problem that THH> didn't exist before, or, at least, was so rare nobody cared :( This is a feature that has been consistently requested in majordomo-users, at least since I became involved several years ago. It's also implemented by every other list management package I've ever had experience with (although in that Draconian "refuse the message" method that seems to characterize every package except Majordomo). I really doubt you can say that nobody ever cared. - J< From majordomo-workers-owner Fri Apr 7 08:06:17 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA25653; Fri, 7 Apr 2000 07:25:12 -0700 (PDT) Received: from thelab.hub.org (nat196.224.mpoweredpc.net [142.177.196.224]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id HAA25643 for ; Fri, 7 Apr 2000 07:25:06 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id LAA82280; Fri, 7 Apr 2000 11:41:57 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 7 Apr 2000 11:41:57 -0300 (ADT) From: The Hermit Hacker To: Michael Yount , mj2-dev@csf.colorado.edu Subject: _config being overwritten ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Just lost my message_headers again ... %ls -lt lists/hub.org/pgsql-hackers/_config -rw------- 1 majordom daemon 306 Apr 7 10:24 lists/hub.org/pgsql-hackers/_config Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org ---------- Forwarded message ---------- Received: from localhost (localhost [127.0.0.1]) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id LAA81912 for ; Fri, 7 Apr 2000 11:17:57 -0300 (ADT) (envelope-from pgsql-hackers-owner@hub.org) Received: from mail.hub.org by localhost with IMAP (fetchmail-5.3.0) for scrappy@localhost (single-drop); Fri, 07 Apr 2000 11:17:57 -0300 (ADT) Received: from hub.org (localhost [127.0.0.1]) by hub.org (8.9.3/8.9.3) with SMTP id JAA45804; Fri, 7 Apr 2000 09:57:53 -0400 (EDT) (envelope-from pgsql-hackers-owner+M21@hub.org) Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA45196 for ; Fri, 7 Apr 2000 09:52:12 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id OAA06299; Fri, 7 Apr 2000 14:03:44 GMT Message-ID: <38EDEAC0.87789751@alumni.caltech.edu> Date: Fri, 07 Apr 2000 14:03:44 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Momjian , Adriaan Joubert CC: Postgres Hackers List Subject: Bit types and initdb References: <200004071334.JAA10874@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailing-List: pgsql-hackers@postgresql.org Precedence: bulk Sender: pgsql-hackers-owner@hub.org > Thomas, are you going to add bit int From majordomo-workers-owner Fri Apr 7 09:21:49 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id JAA26785; Fri, 7 Apr 2000 09:15:34 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA26778 for ; Fri, 7 Apr 2000 09:15:30 -0700 (PDT) Received: from ee-nt (eckert@netcom18.netcom.com [199.183.9.118]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id JAA29902; Fri, 7 Apr 2000 09:32:23 -0700 (PDT) Message-Id: <3.0.5.32.20000407093157.009bea70@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 07 Apr 2000 09:31:57 -0700 To: majordomo-workers@GreatCircle.COM, mj2-dev@csf.colorado.edu From: SRE Subject: cross-posting (was Re: More on 'duplicates issue' ...) In-Reply-To: <20000407105441.C20475@lists.linuxppc.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk At 10:54 AM 4/7/00 -0500, Dave Wolfe wrote: >it sorta like bounce handling, which I suspect most list admins also >just ignore. Now, does anyone want to talk about cross-posting between If you can solve THAT one, I'll buy you dinner! It's pretty easy to trap a single msg that goes to many lists (at least with Mj2 access_rules) and bounce it with a message saying "you can't post to more than N lists on this server at once"... BUT all they have to do is send the post to one list at a time and you can no longer trap it. I've thought about feeding all lists from a master list that can watch for duplicates, but never got around to a real spec. Listserv has some sort of spam trap (which they won't document) that takes into account how many lists you post to and how similar the posts are. If you trigger the trap, as I once did, LSoft can shut you down on every listserv list worldwide. The servers all communicate with the Mother Ship on a fairly regular basis, and local admins are powerless to enable you to post until LSoft lifts the automatic sanction. I'm not suggesting Majordomo should go that way, just pointing to it as the limiting case. From majordomo-workers-owner Sun Apr 9 15:25:04 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA28629; Sun, 9 Apr 2000 15:12:26 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id PAA28619 for majordomo-workers@greatcircle.com; Sun, 9 Apr 2000 15:12:23 -0700 (PDT) Received: from lists.linuxppc.org (lists.linuxppc.org [169.207.161.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA26290 for ; Fri, 7 Apr 2000 08:38:23 -0700 (PDT) Received: (from dwolfe@localhost) by lists.linuxppc.org (8.9.1a/8.9.1) id KAA13960; Fri, 7 Apr 2000 10:54:42 -0500 Date: Fri, 7 Apr 2000 10:54:41 -0500 From: Dave Wolfe To: The Hermit Hacker Cc: Michael Yount , mj2-dev@csf.colorado.edu Subject: Re: More on 'duplicates issue' ... Message-ID: <20000407105441.C20475@lists.linuxppc.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from The Hermit Hacker on Fri, Apr 07, 2000 at 11:38:41AM -0300 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ The Hermit Hacker writes: ] > > [...] from my past experiences, it looks like we've fixed a problem > that didn't exist before, or, at least, was so rare nobody cared :( I'll add my $.02 too... Duplicate/repeated messages are a continual problem and have been since I first started running mail lists. I view it sorta like bounce handling, which I suspect most list admins also just ignore. Now, does anyone want to talk about cross-posting between lists? -- Dave Wolfe "Are ignorance and apathy a problem?" "I don't know and I don't care." From majordomo-workers-owner Sun Apr 9 15:40:02 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA28530; Sun, 9 Apr 2000 15:11:26 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id PAA28520 for majordomo-workers@greatcircle.com; Sun, 9 Apr 2000 15:11:23 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA15671 for ; Thu, 6 Apr 2000 15:13:22 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id RAA22145; Thu, 6 Apr 2000 17:30:10 -0500 To: mj2-dev@csf.colorado.edu, majordomo-workers@GreatCircle.COM Subject: Re: Mj2: Re: apparent substitute_vars() bug (using $INCLUDE-help) References: <3.0.5.32.20000406105409.00991280@pop.climber.org> <3.0.5.32.20000406142305.009c2250@pop.climber.org> From: Jason L Tibbitts III Date: 06 Apr 2000 17:30:10 -0500 In-Reply-To: SRE's message of "Thu, 06 Apr 2000 14:23:05 -0700" Message-ID: Lines: 16 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "S" == SRE writes: S> According to the old README.FILES, some files do not have any variable S> substitution done... so would $INCLUDE work? Hmmm. Majordomo::_list_file_get is the important routine here; if passed a hashref of substitutions then Majordomo::substitute_vars (i.e. $INCLUDE processing) will be called. Otherwise it won't. This is trivial to change so that $INCLUDE always works (just remove the test and make sure substitute_vars can handle undef for the substitution hash). I'd be making some of these trivial changes myself, but I don't have the time to test them before committing them. - J< From majordomo-workers-owner Sun Apr 9 15:55:02 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA28313; Sun, 9 Apr 2000 15:09:05 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id PAA28300 for majordomo-workers@greatcircle.com; Sun, 9 Apr 2000 15:09:01 -0700 (PDT) Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA23886 for ; Wed, 5 Apr 2000 04:05:25 -0700 (PDT) Received: from cc.univie.ac.at (wshm.cc.univie.ac.at [131.130.2.236]) by mailbox.univie.ac.at (8.9.3/8.9.3) with ESMTP id NAA18738; Wed, 5 Apr 2000 13:21:56 +0200 Message-ID: <38EB21D3.A773F333@cc.univie.ac.at> Date: Wed, 05 Apr 2000 11:21:55 +0000 From: Harald Michl Organization: Vienna University Computer Center X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.10 i586) X-Accept-Language: en MIME-Version: 1.0 To: Majordomo-Workers@GreatCircle.COM CC: Harald Michl Subject: Moderated Majordomo list Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hi! We have some moderated majordomo mailinglists, that work really fine. But recently there appeared one problem: Lets say, I have a moderated mailinglist info@host.net Then I have some addresses like info-owner, info-approve and also an info-list@host.net The approve mechanism works fine, if a person sends mail to the info@host.net address, but it passes the approve algorithm if a person sends directly to the info-list@host.net address. Do you have any solutions/recommendments for that? wkr Harald -- -------------------------------------------------------------------------- Harald Michl : e-mail: michl@cc.univie.ac.at Computer Center - ACOnet : Tel: +43 1 4277 - 140 78 Vienna University : Fax: +43 1 4277 - 9 140 Universitaetsstrasse 7 : RIPE-DB Handle: HM3550-RIPE A-1010 Vienna, Austria, Europe : PGP public key ID 0x507C08E0 -------------------------------------------------------------------------- From majordomo-workers-owner Sun Apr 9 16:10:10 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA28582; Sun, 9 Apr 2000 15:12:05 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id PAA28571 for majordomo-workers@greatcircle.com; Sun, 9 Apr 2000 15:12:02 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA18955 for ; Thu, 6 Apr 2000 22:44:15 -0700 (PDT) Received: from ee-nt (eckert@netcom10.netcom.com [199.183.9.110]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id XAA24869; Thu, 6 Apr 2000 23:00:58 -0700 (PDT) Message-Id: <3.0.5.32.20000406200759.009ad100@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 06 Apr 2000 20:07:59 -0700 To: mj2-dev@csf.colorado.edu, majordomo-workers@GreatCircle.COM From: SRE Subject: Re: Mj2: Re: apparent substitute_vars() bug (using $INCLUDE-help) In-Reply-To: References: <3.0.5.32.20000406105409.00991280@pop.climber.org> <3.0.5.32.20000406142305.009c2250@pop.climber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk At 05:30 PM 4/6/00 -0500, Jason L Tibbitts III wrote: >Hmmm. Majordomo::_list_file_get is the important routine here; if passed a >hashref of substitutions then Majordomo::substitute_vars (i.e. $INCLUDE >processing) will be called. Otherwise it won't. This is trivial to change >so that $INCLUDE always works (just remove the test and make sure >substitute_vars can handle undef for the substitution hash). I went to look at that... it's not so trivial after all. | Note that if $subs is provided, the returned filename will be a temporary | generated by substitute_vars. The caller is responsible for cleaning up | this temporary. Thank god for that comment in the source. If we let substitute_vars run every time, every call to _list_file_get will return a temporary file... and I'm not quite ready to go find every call and make sure all those temp files get cleaned up. I did set up substitute_vars so it accepts an undefined variable hash, so the motor is running when someone has time to take on _list_file_get. >I'd be making some of these trivial changes myself, but I don't have the >time to test them before committing them. I did at least implement backslash escaping for $INCLUDE, which unlike other variables was ALWAYS evaluted (boinking my example in the new "help variables" file). From majordomo-workers-owner Sun Apr 9 16:25:02 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA28597; Sun, 9 Apr 2000 15:12:12 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id PAA28587 for majordomo-workers@greatcircle.com; Sun, 9 Apr 2000 15:12:09 -0700 (PDT) Received: from crick.nih.go.jp (crick.nih.go.jp [202.241.78.17]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id AAA19785 for ; Fri, 7 Apr 2000 00:18:19 -0700 (PDT) Received: from nih.go.jp (winston.nih.go.jp [192.168.21.168]) by crick.nih.go.jp (8.9.2/3.7W) with ESMTP id QAA15132 for ; Fri, 7 Apr 2000 16:34:35 +0900 (JST) Message-ID: <38ED8F44.B0569471@nih.go.jp> Date: Fri, 07 Apr 2000 16:33:24 +0900 From: Jun ISHIKAWA X-Mailer: Mozilla 4.7C-ja [ja] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: ja, en MIME-Version: 1.0 To: Majordomo-Workers@GreatCircle.COM Subject: sequencer bug Content-Type: multipart/mixed; boundary="------------73691B958BA9DD1A1A28E385" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk This is a multi-part message in MIME format. --------------73691B958BA9DD1A1A28E385 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Dear developer, You should apply the attached patch. Regards, -- jun@nih.go.jp --------------73691B958BA9DD1A1A28E385 Content-Type: text/plain; charset=iso-2022-jp; name="sequencer.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="sequencer.patch" *** sequencer.orig Fri Apr 7 15:32:19 2000 --- sequencer Fri Apr 7 16:14:28 2000 *************** *** 19,22 **** --- 19,24 ---- # Based heavily upon the resend script included in the majordomo distribution + $sendmail_command = $sendmail_command || "/usr/lib/sendmail"; + # set our path explicitly $ENV{'PATH'} = "/bin:/usr/bin:/usr/sbin:/sbin"; *************** *** 400,404 **** } ! $sendmail_cmd = "/usr/lib/sendmail $opt_m -f$sendmail_sender " . join(" ", @ARGV); --- 402,406 ---- } ! $sendmail_cmd = "$sendmail_command $opt_m -f$sendmail_sender " . join(" ", @ARGV); *************** *** 542,548 **** # debugging, so just say it, don't do it open(MAIL, ">-"); ! print MAIL ">>> /usr/lib/sendmail -f$sendmail_sender -t\n"; } else { ! local(@mailer) = split(' ',"/usr/lib/sendmail -f$sendmail_sender -t"); open(MAIL, "|-") || &do_exec_sendmail(@mailer); } --- 544,550 ---- # debugging, so just say it, don't do it open(MAIL, ">-"); ! print MAIL ">>> $sendmail_command -f$sendmail_sender -t\n"; } else { ! local(@mailer) = split(' ',"$sendmail_command -f$sendmail_sender -t"); open(MAIL, "|-") || &do_exec_sendmail(@mailer); } --------------73691B958BA9DD1A1A28E385-- From majordomo-workers-owner Sun Apr 9 19:55:07 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA01033; Sun, 9 Apr 2000 19:48:40 -0700 (PDT) Received: from scifi.squawk.com (glock.squawk.com [208.176.124.157]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA01023 for ; Sun, 9 Apr 2000 19:48:11 -0700 (PDT) Received: from scifi.squawk.com (gateway.squawk.com [199.74.151.119]) by scifi.squawk.com (Postfix) with ESMTP id BAD63350C5; Sun, 9 Apr 2000 23:05:31 -0400 (EDT) Message-ID: <38F144FB.31423AE8@scifi.squawk.com> Date: Sun, 09 Apr 2000 23:05:31 -0400 From: Nick Simicich X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Harald Michl Cc: Majordomo-Workers@GreatCircle.COM Subject: Re: Moderated Majordomo list References: <38EB21D3.A773F333@cc.univie.ac.at> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Postfix allows you to protect certain addresses (according to a pattern) from being mailed to off system. I use that facility. Harald Michl wrote: > > Hi! > We have some moderated majordomo mailinglists, that work really fine. > But recently there appeared one problem: > > Lets say, I have a moderated mailinglist info@host.net > Then I have some addresses like info-owner, info-approve and also an > info-list@host.net > > The approve mechanism works fine, if a person sends mail to the > info@host.net address, but it passes the approve algorithm if a person > sends directly to the info-list@host.net address. > > Do you have any solutions/recommendments for that? > > wkr > > Harald > > -- > -------------------------------------------------------------------------- > Harald Michl : e-mail: michl@cc.univie.ac.at > Computer Center - ACOnet : Tel: +43 1 4277 - 140 78 > Vienna University : Fax: +43 1 4277 - 9 140 > Universitaetsstrasse 7 : RIPE-DB Handle: HM3550-RIPE > A-1010 Vienna, Austria, Europe : PGP public key ID 0x507C08E0 > -------------------------------------------------------------------------- From majordomo-workers-owner Thu Apr 13 04:21:21 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id EAA26338; Thu, 13 Apr 2000 04:17:10 -0700 (PDT) Received: from sonny.org (camaro.sonny.org [205.217.137.151]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id EAA26325; Thu, 13 Apr 2000 04:16:49 -0700 (PDT) Received: from sonny.org (daniel.sonny.org [205.217.137.65]) by sonny.org (8.8.8/8.8.3) with ESMTP id GAA01233; Thu, 13 Apr 2000 06:33:52 -0500 (CDT) Message-ID: <38F5B09F.A7219B79@sonny.org> Date: Thu, 13 Apr 2000 06:33:51 -0500 From: Dan Liston Organization: iPlanet E-Commerce Solutions, A Sun Netscape Alliance X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Chan Wilson CC: majordomo-announce@greatcircle.com, majordomo-workers@greatcircle.com, majordomo-users@greatcircle.com Subject: Re: Majordomo 1.94.5 released -- security and bugfix release References: <20000119162213B.cwilson@unknown-domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Is there a patch to fix what the unzubscribe_policy in 1.94.5 broke? Even with "unzubscribe_policy = closed", anyone can now unzubscribe without list-owner approval. I support a business with about 1000 employees that are mandatorily zubscribed to certain lists, such as announce and employee. Only the HR department can zubscribe and unzubscribe people from these lists. With 1.94.5, people have been able to unzubscribe themselves. I can see this as being a good thing for the open internet lists and allowing anyone to be removed from spam lists, but in a corporate environment, these lists membership must be tightly controlled. Do I need to revert back to 1.94.4? Thanks in advance, Dan Liston Chan Wilson wrote: > > Majordomo 1.94.5 has been released, another security bugfix release. > > Available from ftp.GreatCircle.com and ftp.sgi.com: > > ftp://ftp.greatcircle.com/pub/majordomo/majordomo.tgz > > ftp://ftp.sgi.com/other/majordomo/majordomo.tgz > > Thanks to all the volunteers who have produced the patches and made > them available to the community. > > --Chan > > Changes from 1.94.4 to 1.94.5 > > A straightforward patch release, 99% from the collected > 1.94.4 patches: > > o digest_rm_fronter and digest_rm_footer now work. > o unsubcribe_policy now has +confirm feature > o More hostile address checking > o archive2.pl makes archives world readable. > o bounce had an innocuous y2k bug, and wanted a 'bounces' list password even > when called as unsub > o better description of the moderator function. > o Fixes 'restrict_post = #!$list' substitution and blank lines > in config files > o Better error reporting when majordomo.cf is wrong. > o Detects some attachments sent as commands > o Approve commands can span lines now. > o resend has better messages for taboo_headers problems > o fixed: header corruption when Subject: is blank and subject tags are used. > > ========================================================================================= > archive2.pl.0 () Ensures archives are world readable. > bounce.0 () Bounce script and unsub. > config_parse.pl.1 () Another trivial 1.94.4 patch: moderator > config_parse.pl.2 (B) Fixes 'restrict_post = #!$list' substitution > config_parse.pl.5 (F) Fixes failing to accept newconfig... (cleaned) > config_parse.pl.6 (B) Fixes bug when several consecutive blank lines > or a trailing blank line appear in a string array > digest-config_parse.pl.1 (F) Adds the functionality promised by digest_rm_fronter > majordomo-config.1 (F) +config patches for unsubscribe_policy > majordomo.0b (B+) Fixes some error messages and minor bugs related to > aliasing -request to invoking majordomo with -l > majordomo.1 (F) PATCH: no attachments (was Re: Strange stuff) > majordomo.3 () A minor little patch that cleans up newinfo/newintro > majordomo.6 (F) Patch for APPROVE linewraps > majordomo.7 () Work-around for Perl 5.005 problem > majordomo.pl.1 (S+) Fixes security hole with :include:syslog (untested) > request-answer.0 () Request-answer should not reply to mailer-daemon et al > resend.2 (F) A nice patch for debugging taboo_headers > resend.5 (B++) Fixes header corruption when Subject: is > blank and subject tags are used > resend.8 () More headers for the skip headers string > resend_parse.1 () Corrected PATCH: moderator behavior From majordomo-workers-owner Fri Apr 21 13:22:39 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id NAA27663; Fri, 21 Apr 2000 13:09:20 -0700 (PDT) Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA27656 for ; Fri, 21 Apr 2000 13:09:13 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id NAA28220 for <@external-mail-relay.sgi.com:majordomo-workers@greatcircle.com>; Fri, 21 Apr 2000 13:23:52 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: from mando.engr.sgi.com (mando.engr.sgi.com [163.154.5.88]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id NAA17749 for <@cthulhu.engr.sgi.com:majordomo-workers@greatcircle.com>; Fri, 21 Apr 2000 13:28:34 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: (from relph@localhost) by mando.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id NAA60997; Fri, 21 Apr 2000 13:28:33 -0700 (PDT) Date: Fri, 21 Apr 2000 13:28:33 -0700 (PDT) Message-Id: <200004212028.NAA60997@mando.engr.sgi.com> From: John Relph To: majordomo-workers@greatcircle.com Subject: Silence Reply-to: relph@sgi.com Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Is it my imagination or have I heard nothing but silence in response to my last few posts to the list? Or were my posts not sent to the list? I sent one which was a proposed patch to Majordomo 1.94.5 and another which was a question about email addresses in informational messages from the server (and how Outlook screws them up). -- John From majordomo-workers-owner Fri Apr 21 14:23:11 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA28341; Fri, 21 Apr 2000 14:21:10 -0700 (PDT) Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id OAA28334 for ; Fri, 21 Apr 2000 14:21:04 -0700 (PDT) Received: from cthulhu.engr.sgi.com (gate3-relay.engr.sgi.com [130.62.1.234]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id OAA05181 for <@external-mail-relay.sgi.com:majordomo-workers@greatcircle.com>; Fri, 21 Apr 2000 14:35:44 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: from mando.engr.sgi.com (mando.engr.sgi.com [163.154.5.88]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id OAA60561 for <@cthulhu.engr.sgi.com:majordomo-workers@greatcircle.com>; Fri, 21 Apr 2000 14:40:25 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: (from relph@localhost) by mando.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id OAA62599; Fri, 21 Apr 2000 14:40:25 -0700 (PDT) Date: Fri, 21 Apr 2000 14:40:25 -0700 (PDT) Message-Id: <200004212140.OAA62599@mando.engr.sgi.com> From: John Relph To: majordomo-workers@greatcircle.com Subject: resend 1.94.5 patch Reply-to: relph@sgi.com Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Folks, I don't know what's happening, but my posts aren't getting to the list, so I'm trying again. Here's a patch for "resend" which bounces messages that have no "Subject:" line. I suppose it should be configurable, but this patch is not. I use this patch and have for some time. -- John *** resend.ORIG Fri Mar 24 09:48:58 2000 --- resend Fri Mar 24 09:56:36 2000 *************** *** 579,584 **** --- 579,585 ---- sub parse_header { local($gonna_bounce); local($kept_last) = 0; # our return flag/string. + local($subject_found) = 0; print STDERR "$0: parse_header: enter.\n" if $DEBUG; print STDERR "$0: parse_header: taboo_headers = $is_taboo_header\n" if $DEBUG; *************** *** 700,713 **** # prepend subject prefix # ! if ( (/^subject:\s*/i) ! && ($config_opts{$opt_l,"subject_prefix"} ne '')) { ! print STDERR "$0: parse_header: adding subject prefix\n" if $DEBUG; ! local($foo) = &config'substitute_values($config_opts{$opt_l,"subject_prefix"}, $opt_l);#'; ! local($foo_pat) = $foo; ! $foo_pat =~ s/(\W)/\\$1/g; ! s/^subject:[^\S\n]*/Subject: $foo /i if !/$foo_pat/; } # snag reply-to field --- 701,716 ---- # prepend subject prefix # ! if (/^subject:\s*/i) { ! if ($config_opts{$opt_l,"subject_prefix"} ne '') { ! print STDERR "$0: parse_header: adding subject prefix\n" if $DEBUG; ! local($foo) = &config'substitute_values($config_opts{$opt_l,"subject_prefix"}, $opt_l);#'; ! local($foo_pat) = $foo; ! $foo_pat =~ s/(\W)/\\$1/g; ! s/^subject:[^\S\n]*/Subject: $foo /i if !/$foo_pat/; ! } ! $subject_found = 1; } # snag reply-to field *************** *** 754,760 **** if (defined($opt_r)) { print OUT "Reply-To: ", &config'substitute_values($opt_r), "\n"; #'; } ! # print out per-list additonal headers if ( $config_opts{$opt_l,"message_headers"} ne '' ) { local($headers) = &config'substitute_values ( --- 757,775 ---- if (defined($opt_r)) { print OUT "Reply-To: ", &config'substitute_values($opt_r), "\n"; #'; } ! ! if ($subject_found == 0) { ! if ($config_opts{$opt_l,"subject_prefix"} ne '') { ! ! print STDERR "$0: parse_header: adding subject prefix\n" if $DEBUG; ! print OUT "Subject: ", ! &config'substitute_values($config_opts{$opt_l,"subject_prefix"}, $opt_l), #' ! " (none)\n"; ! } ! $gonna_bounce .= "Missing Subject line "; ! print STDERR "$0: parse_header: [$.] boing: $gonna_bounce\n" if $DEBUG; ! } ! # print out per-list additonal headers if ( $config_opts{$opt_l,"message_headers"} ne '' ) { local($headers) = &config'substitute_values ( From majordomo-workers-owner Fri Apr 21 15:57:36 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA29065; Fri, 21 Apr 2000 15:47:01 -0700 (PDT) Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA29058 for ; Fri, 21 Apr 2000 15:46:55 -0700 (PDT) Received: from cthulhu.engr.sgi.com (gate3-relay.engr.sgi.com [130.62.1.234]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id QAA06937; Fri, 21 Apr 2000 16:10:19 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: from mando.engr.sgi.com (mando.engr.sgi.com [163.154.5.88]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id QAA61350; Fri, 21 Apr 2000 16:06:06 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: (from relph@localhost) by mando.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id QAA64489; Fri, 21 Apr 2000 16:06:06 -0700 (PDT) Date: Fri, 21 Apr 2000 16:06:06 -0700 (PDT) From: relph@mando.engr.sgi.com (John Relph) Message-Id: <10004211606.ZM65000@mando.engr.sgi.com> In-Reply-To: Dave Wolfe "Re: Silence" (Apr 21, 17:53) References: <200004212028.NAA60997@mando.engr.sgi.com> <20000421175322.B21738@lists.linuxppc.org> Reply-To: relph@sgi.com X-Mailer: Z-Mail-SGI (3.2S.3 08feb96 MediaMail) To: Dave Wolfe Subject: Re: Silence Cc: majordomo-workers@greatcircle.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Dave, I would have thought that, too, except that I keep getting discussions on problems with MJ2. And I checked my subscription and sure enough I was still subscribed. So I don't know what happened except perhaps the moderator never approved my posting as you suggest. Hopefully you received the message I sent today which contained one of my patches. -- John On Apr 21, 17:53, Dave Wolfe wrote: >[ John Relph writes: ] >> Is it my imagination or have I heard nothing but silence in response >> to my last few posts to the list? Or were my posts not sent to the >> list? >> >> I sent one which was a proposed patch to Majordomo 1.94.5 and another >> which was a question about email addresses in informational messages >> from the server (and how Outlook screws them up). > >Apparently you aren't subscribed or you'd know if your messages were >distributed to the list, right? I don't recall the latter but I usually >respond to patches for 1.94, if nothing else w/ information about how >to submit them to the unofficial patch site. Since Mj-workers has been >rather quiet, the list owner seems rather slow about clearing the taboo >and admin traps. If you match any of the taboo/admin regexs your message >has to be approved to be posted. > >-- > Dave Wolfe From majordomo-workers-owner Fri Apr 21 16:07:37 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id PAA29128; Fri, 21 Apr 2000 15:54:04 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA29121 for ; Fri, 21 Apr 2000 15:53:57 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id SAA27294; Fri, 21 Apr 2000 18:13:23 -0500 To: majordomo-workers@greatcircle.com Subject: Re: Silence References: <200004212028.NAA60997@mando.engr.sgi.com> From: Jason L Tibbitts III Date: 21 Apr 2000 18:13:22 -0500 In-Reply-To: John Relph's message of "Fri, 21 Apr 2000 13:28:33 -0700 (PDT)" Message-ID: Lines: 10 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "JR" == John Relph writes: JR> Is it my imagination or have I heard nothing but silence in response to JR> my last few posts to the list? Or were my posts not sent to the list? Some of us are over on mj2-dev working on Majordomo2, and I watch this list for Mj2-related questions. I don't know who's working on Mj1 stuff at the moment. - J< From majordomo-workers-owner Fri Apr 21 20:07:37 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA01066; Fri, 21 Apr 2000 19:59:30 -0700 (PDT) Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA01059 for ; Fri, 21 Apr 2000 19:59:23 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id UAA01458; Fri, 21 Apr 2000 20:18:47 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: from mando.engr.sgi.com (mando.engr.sgi.com [163.154.5.88]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id UAA19525; Fri, 21 Apr 2000 20:18:44 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: (from relph@localhost) by mando.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id UAA71595; Fri, 21 Apr 2000 20:18:43 -0700 (PDT) Date: Fri, 21 Apr 2000 20:18:43 -0700 (PDT) From: relph@mando.engr.sgi.com (John Relph) Message-Id: <10004212018.ZM65773@mando.engr.sgi.com> In-Reply-To: Dave Wolfe "Re: resend 1.94.5 patch" (Apr 21, 21:31) References: <200004212140.OAA62599@mando.engr.sgi.com> <20000421213150.A18921@lists.linuxppc.org> Reply-To: relph@sgi.com X-Mailer: Z-Mail-SGI (3.2S.3 08feb96 MediaMail) To: Dave Wolfe Subject: Re: resend 1.94.5 patch Cc: majordomo-workers@greatcircle.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Dave, Okay, that one was received. I had two or three I had sent and I wasn't sure which ones people might have seen. What's the latest process for majordomo-patches? -- John On Apr 21, 21:31, Dave Wolfe wrote: >[ John Relph writes: ] >> >> Here's a patch for "resend" which bounces messages that have no >> "Subject:" line. I suppose it should be configurable, but this patch >> is not. I use this patch and have for some time. > >Hmmm... Looks a lot like your patch of July 1998 for 1.94.4. You should >probably send it to majordomo-patches@cloud.ccsf.cc.ca.us to have Joe >update it. > >-- > Dave Wolfe From majordomo-workers-owner Sat Apr 22 17:06:22 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id RAA11996; Sat, 22 Apr 2000 17:01:52 -0700 (PDT) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id RAA11988 for ; Sat, 22 Apr 2000 17:01:46 -0700 (PDT) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id TAA29065; Sat, 22 Apr 2000 19:21:15 -0500 To: The Hermit Hacker Cc: majordomo-workers@GreatCircle.COM, mj2-dev@csf.colorado.edu Subject: Re: restrict_post - how to? References: From: Jason L Tibbitts III Date: 22 Apr 2000 19:21:15 -0500 In-Reply-To: The Hermit Hacker's message of "Sat, 22 Apr 2000 18:26:20 -0300 (ADT)" Message-ID: Lines: 70 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "THH" == The Hermit Hacker writes: THH> How do I go about setting the restrict_post feature in mj2 such THH> that it will restrict to those on the list itself *and* on a second THH> list ... restrict_post works in a backwards-compatible way, except that you can (and must) manage the second list through majordomo instead of making it by hand. There's a lot of additional functionality there as well, and because of that it's pretty complicated. If before you had: restrict_post = listname listname.allow you can keep that, but instead of adding addresses to the listname.announce file by hand, you do something like: auxadd listname allow < Essentially, I have a list that ppl can subscribe to such that they THH> can post to the other lists, but not receive anything (ie. they are THH> subscribe to listA, but want to be able to cross-post to listB *or* THH> they are subscribed to a list from home, but want to be able to post THH> from work ) ... Ah, that's different. I'd say that the "nomail" option takes care of some of the first situation (they can sign up and say they don't want to get any mail), and the "alias" command completely takes care of the second. But you can still do this with restrict_post if you want. Say your special list is called "posters". Then you can have users sign up to "posters" and put this in restrict_post: configset listname restrict_post = listname: posters: Because of backwards compatibility, the interpretation of restrict_post is complicated. I'll try to describe it here so that it can get into the docs. With a colon, you're giving a list:auxlist pair and if auxlist is empty then the main list is checked. This lets you restrict based on the contents of other lists. Without a colon, we try to duplicate most conventions for naming of restrict_post files. If just the listname is present, we look in the subscriber file for this list. We do the same for listname.digest and listname-digest, since digests aren't separate lists any longer. Otherwise we try hard to find an auxlist that looks like what we were given. For listname-allow, we look for one named listname-allow and just allow. The same with listname.allow. The code for all of this is in Mj::Access::_d_post. Oh, and you can put your restrict list on one line (for backwards compatibility): restrict_post = blah:urgh hurl: allow or as an array, as it should have been in the first place: restrict_post <; Sat, 22 Apr 2000 17:16:07 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id VAA17630; Sat, 22 Apr 2000 21:35:42 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 22 Apr 2000 21:35:42 -0300 (ADT) From: The Hermit Hacker To: Jason L Tibbitts III cc: majordomo-workers@GreatCircle.COM, mj2-dev@csf.colorado.edu Subject: Re: restrict_post - how to? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk So, just to confirm, we're looking at: ===== configset pgsql-interfaces restrict_post = pgsql-interfaces: pgsql-loophole: restrict_post set to "pgsql-interfaces: pgsql-loophole:". ===== And that's it? if I wanted to do this in the DEFAULT config, could I do: $LIST: pgsql-loophole: On 22 Apr 2000, Jason L Tibbitts III wrote: > >>>>> "THH" == The Hermit Hacker writes: > > THH> How do I go about setting the restrict_post feature in mj2 such > THH> that it will restrict to those on the list itself *and* on a second > THH> list ... > > restrict_post works in a backwards-compatible way, except that you can (and > must) manage the second list through majordomo instead of making it by > hand. There's a lot of additional functionality there as well, and because > of that it's pretty complicated. > > If before you had: > > restrict_post = listname listname.allow > > you can keep that, but instead of adding addresses to the listname.announce > file by hand, you do something like: > > auxadd listname allow < address1@example.com > address2@example.com > END > > This adds the addresses to the auxiliary list "allow" belonging to > "listname". > > THH> Essentially, I have a list that ppl can subscribe to such that they > THH> can post to the other lists, but not receive anything (ie. they are > THH> subscribe to listA, but want to be able to cross-post to listB *or* > THH> they are subscribed to a list from home, but want to be able to post > THH> from work ) ... > > Ah, that's different. I'd say that the "nomail" option takes care of some > of the first situation (they can sign up and say they don't want to get any > mail), and the "alias" command completely takes care of the second. But > you can still do this with restrict_post if you want. Say your special > list is called "posters". Then you can have users sign up to "posters" and > put this in restrict_post: > > configset listname restrict_post = listname: posters: > > Because of backwards compatibility, the interpretation of restrict_post is > complicated. I'll try to describe it here so that it can get into the > docs. With a colon, you're giving a list:auxlist pair and if auxlist is > empty then the main list is checked. This lets you restrict based on the > contents of other lists. Without a colon, we try to duplicate most > conventions for naming of restrict_post files. If just the listname is > present, we look in the subscriber file for this list. We do the same for > listname.digest and listname-digest, since digests aren't separate lists > any longer. > > Otherwise we try hard to find an auxlist that looks like what we were > given. For listname-allow, we look for one named listname-allow and just > allow. The same with listname.allow. > > The code for all of this is in Mj::Access::_d_post. > > Oh, and you can put your restrict list on one line (for backwards compatibility): > > restrict_post = blah:urgh hurl: allow > > or as an array, as it should have been in the first place: > > restrict_post < blah:urgh > hurl: > allow > END > > - J< > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From majordomo-workers-owner Sun Apr 23 10:52:37 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA21122; Sun, 23 Apr 2000 10:43:41 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA21109 for ; Sun, 23 Apr 2000 10:43:35 -0700 (PDT) Received: from ee-nt (eckert@netcom4.netcom.com [199.183.9.104]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id LAA12136; Sun, 23 Apr 2000 11:03:12 -0700 (PDT) Message-Id: <3.0.5.32.20000423104328.00a38750@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 23 Apr 2000 10:43:28 -0700 To: majordomo-workers@GreatCircle.COM, mj2-dev@csf.colorado.edu From: SRE Subject: Re: Mj2: Re: restrict_post - how to? In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk At 07:21 PM 4/22/00 -0500, Jason L Tibbitts III wrote: >complicated. I'll try to describe it here so that it can get into the docs. Please review the Mj2 CVS tree for "help configset_restrict_post" and "help admin", to see if the references and description are now correct. SRE mailto:eckert@climber.org | http://www.climber.org/eckert/ Info on peak climbing email lists mailto:info@climber.org Things change. People change. Things change people. From majordomo-workers-owner Sun Apr 23 11:07:37 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id KAA21125; Sun, 23 Apr 2000 10:43:46 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id KAA21117 for ; Sun, 23 Apr 2000 10:43:39 -0700 (PDT) Received: from ee-nt (eckert@netcom4.netcom.com [199.183.9.104]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id LAA12145; Sun, 23 Apr 2000 11:03:21 -0700 (PDT) Message-Id: <3.0.5.32.20000423110031.009ea200@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 23 Apr 2000 11:00:31 -0700 To: majordomo-workers@GreatCircle.COM, mj2-docs@hpc.uh.edu, mj2-dev@csf.colorado.edu From: SRE Subject: Mj2 docs In-Reply-To: <20000423181118.C957@wyvernslair.ptw.com> References: <3.0.5.32.20000423100436.009f44b0@pop.climber.org> <3.0.5.32.20000422100319.00a32d20@pop.climber.org> <3.0.5.32.20000422180825.009fe8e0@pop.climber.org> <3.0.5.32.20000423100436.009f44b0@pop.climber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk At 06:11 PM 4/23/00 +0000, rex wrote: >I'm a complete newbie to running mjx on my own machine, and had some >trouble installing mj2. The problem (lack of a sym link) is rather >obscure, but probably common since it will affect most/all Red Hat >systems. I think the solution should be in the docs. In "help admin" there is a Section 7 which used to be in the release files as "COOKBOOK". Since list owners don't usually have access to the source, we have moved some of these files into the help system... but they are by no means exhaustive. Anyone who spends a lot of time looking for a solution, and either doesn't find it or finds it in [what you think is] a stoopid place, please send me a note! I'm always eager to hear about errors and omissions, ESPECIALLY in the area of documented real-world examples. >I gather from your post that you are involved in documenting mj2? I've volunteered to do the Mj2 help files, since that is where most of the documentation for list owners and list users is. Right now there is nothing anywhere in the docs that says how to reach me. Should there be? I'm reluctant to add it for fear of looking like I want to take over or be famous, but will if there is general concensus that the help file maintainer should be more visible. For now, just send stuff to any of the 3 lists I'm sending this message to, and I'll see it. I commit changes to Jason's Mj2 CVS tree at http://www.hpc.uh.edu/majordomo/index.html, but I don't create snapshots so the tarball might not have the latest help files in it. SRE mailto:eckert@climber.org | http://www.climber.org/eckert/ Info on peak climbing email lists mailto:info@climber.org "If you think education is expensive, try ignorance." -- Derek Bok, president of Harvard From majordomo-workers-owner Sun Apr 23 11:37:46 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA21457; Sun, 23 Apr 2000 11:35:41 -0700 (PDT) Received: from fog.ccsf.cc.ca.us (fog.ccsf.cc.ca.us [147.144.1.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id LAA21450 for ; Sun, 23 Apr 2000 11:35:36 -0700 (PDT) Received: from sol.ccsf.cc.ca.us (sol.ccsf.cc.ca.us [147.144.1.211]) by fog.ccsf.cc.ca.us (8.8.6 (PHNE_17135)/8.8.6) with SMTP id LAA03159; Sun, 23 Apr 2000 11:55:20 -0700 (PDT) Received: from localhost by sol.ccsf.cc.ca.us (SMI-8.6/SMI-SVR4) id LAA22336; Sun, 23 Apr 2000 11:55:14 -0700 Date: Sun, 23 Apr 2000 11:55:13 -0700 (PDT) From: "Joe R. Jah" To: John Relph cc: Dave Wolfe , majordomo-workers@greatcircle.com Subject: Re: resend 1.94.5 patch In-Reply-To: <10004212018.ZM65773@mando.engr.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On Fri, 21 Apr 2000, John Relph wrote: > Date: Fri, 21 Apr 2000 20:18:43 -0700 (PDT) > From: John Relph > Reply-To: relph@sgi.com > To: Dave Wolfe > Cc: majordomo-workers@greatcircle.com > Subject: Re: resend 1.94.5 patch > > Dave, > > Okay, that one was received. I had two or three I had sent and I > wasn't sure which ones people might have seen. What's the latest > process for majordomo-patches? I received it too, and placed your patch in: ftp://ftp.ccsf.org/majordomo-patches/1.94.5/resend.0 If you have sent other patches, and have not seen them on the list, chances are that no one else has seen them either. Please resend them to the list and CC them to: majordomo-patches@cloud.ccsf.cc.ca.us You can also upload patches to: ftp://ftp.ccsf.org/incoming and send a notification to the above email address. Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jjah@sol.ccsf.cc.ca.us From majordomo-workers-owner Sun Apr 23 12:37:41 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id MAA22057; Sun, 23 Apr 2000 12:33:48 -0700 (PDT) Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA22050 for ; Sun, 23 Apr 2000 12:33:41 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA07612; Sun, 23 Apr 2000 12:57:32 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: from mando.engr.sgi.com (mando.engr.sgi.com [163.154.5.88]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA09523; Sun, 23 Apr 2000 12:53:22 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: (from relph@localhost) by mando.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id MAA87125; Sun, 23 Apr 2000 12:53:21 -0700 (PDT) Date: Sun, 23 Apr 2000 12:53:21 -0700 (PDT) Message-Id: <200004231953.MAA87125@mando.engr.sgi.com> From: John Relph To: majordomo-workers@greatcircle.com CC: majordomo-patches@cloud.ccsf.cc.ca.us Subject: majordomo.pl address matching Reply-to: relph@sgi.com Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Folks, So, since my first try didn't seem to have made it, here's yet another patch for Majordomo 1.94.5. This patch tries to do better checking to see if two email addresses match because they are on different machines in the same domain. For example, as in the example in majordomo.pl, is considered to match . This patch increases the debugging output as well as doing a slightly better job of checking. Any comments? -- John *** majordomo.pl.O Sun Feb 27 16:21:38 2000 --- majordomo.pl Thu Apr 22 21:35:13 1999 *************** *** 173,183 **** return(undef); } ! if ($partial == 2 && ($a1[0] ne $a2[0])) { # see if addresses are # foo@baz.bax.edu, foo@bax.edu - local(@addr1,@addr2); - @addr1 = split(/\@/, $a1[0]); - @addr2 = split(/\@/, $a2[0]); if ( $#addr1 == $#addr2 && $#addr1 == 1 && $addr1[0] eq $addr2[0] && (index($addr1[1], $addr2[1]) >= $[)) { --- 178,193 ---- return(undef); } ! if ($a1[0] eq $a2[0]) { ! return(1); ! } ! ! local(@addr1,@addr2); ! @addr1 = split(/\@/, $a1[0]); ! @addr2 = split(/\@/, $a2[0]); ! ! if ($partial == 2) { # see if addresses are # foo@baz.bax.edu, foo@bax.edu if ( $#addr1 == $#addr2 && $#addr1 == 1 && $addr1[0] eq $addr2[0] && (index($addr1[1], $addr2[1]) >= $[)) { *************** *** 185,191 **** } } ! return($a1[0] eq $a2[0]); } # These are package globals referenced by &setabortaddr and &abort --- 195,217 ---- } } ! if ($#addr1 == 1) { ! print STDERR "addr_match: comparing $addr1[1] against $main'whereami\n" if $DEBUG; ! } ! if ($#addr2 == 1) { ! print STDERR "addr_match: comparing $addr2[1] against $main'whereami\n" if $DEBUG; ! } ! ! if ($addr1[0] eq $addr2[0]) { ! if ($#addr1 == 0 && $#addr2 == 1 && $addr2[1] eq $main'whereami) { #' ! return(1); ! } ! if ($#addr2 == 0 && $#addr1 == 1 && $addr1[1] eq $main'whereami) { #' ! return(1); ! } ! } ! ! return(0); } # These are package globals referenced by &setabortaddr and &abort From majordomo-workers-owner Sun Apr 23 14:41:36 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA23645; Sun, 23 Apr 2000 14:34:28 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA23628 for majordomo-workers@greatcircle.com; Sun, 23 Apr 2000 14:34:24 -0700 (PDT) Received: from lists.linuxppc.org (lists.linuxppc.org [169.207.161.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA00821 for ; Fri, 21 Apr 2000 19:12:32 -0700 (PDT) Received: (from dwolfe@localhost) by lists.linuxppc.org (8.9.1a/8.9.1) id VAA19147; Fri, 21 Apr 2000 21:31:51 -0500 Date: Fri, 21 Apr 2000 21:31:50 -0500 From: Dave Wolfe To: relph@sgi.com Cc: majordomo-workers@GreatCircle.COM Subject: Re: resend 1.94.5 patch Message-ID: <20000421213150.A18921@lists.linuxppc.org> References: <200004212140.OAA62599@mando.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200004212140.OAA62599@mando.engr.sgi.com>; from John Relph on Fri, Apr 21, 2000 at 02:40:25PM -0700 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ John Relph writes: ] > > Here's a patch for "resend" which bounces messages that have no > "Subject:" line. I suppose it should be configurable, but this patch > is not. I use this patch and have for some time. Hmmm... Looks a lot like your patch of July 1998 for 1.94.4. You should probably send it to majordomo-patches@cloud.ccsf.cc.ca.us to have Joe update it. -- Dave Wolfe From majordomo-workers-owner Sun Apr 23 14:55:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA23623; Sun, 23 Apr 2000 14:34:21 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA23613 for majordomo-workers@greatcircle.com; Sun, 23 Apr 2000 14:34:19 -0700 (PDT) Received: from lists.linuxppc.org (lists.linuxppc.org [169.207.161.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id PAA28934 for ; Fri, 21 Apr 2000 15:33:59 -0700 (PDT) Received: (from dwolfe@localhost) by lists.linuxppc.org (8.9.1a/8.9.1) id RAA25230; Fri, 21 Apr 2000 17:53:23 -0500 Date: Fri, 21 Apr 2000 17:53:22 -0500 From: Dave Wolfe To: relph@sgi.com Cc: majordomo-workers@GreatCircle.COM Subject: Re: Silence Message-ID: <20000421175322.B21738@lists.linuxppc.org> References: <200004212028.NAA60997@mando.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200004212028.NAA60997@mando.engr.sgi.com>; from John Relph on Fri, Apr 21, 2000 at 01:28:33PM -0700 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ John Relph writes: ] > Is it my imagination or have I heard nothing but silence in response > to my last few posts to the list? Or were my posts not sent to the > list? > > I sent one which was a proposed patch to Majordomo 1.94.5 and another > which was a question about email addresses in informational messages > from the server (and how Outlook screws them up). Apparently you aren't subscribed or you'd know if your messages were distributed to the list, right? I don't recall the latter but I usually respond to patches for 1.94, if nothing else w/ information about how to submit them to the unofficial patch site. Since Mj-workers has been rather quiet, the list owner seems rather slow about clearing the taboo and admin traps. If you match any of the taboo/admin regexs your message has to be approved to be posted. -- Dave Wolfe From majordomo-workers-owner Sun Apr 23 15:10:08 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA23507; Sun, 23 Apr 2000 14:32:50 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA23497 for majordomo-workers@greatcircle.com; Sun, 23 Apr 2000 14:32:47 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA16895 for ; Tue, 18 Apr 2000 22:24:33 -0700 (PDT) Received: from ee-nt (eckert@netcom4.netcom.com [199.183.9.104]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id WAA07056; Tue, 18 Apr 2000 22:43:25 -0700 (PDT) Message-Id: <3.0.5.32.20000418224327.009de6f0@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Tue, 18 Apr 2000 22:43:27 -0700 To: majordomo-workers@GreatCircle.COM, mj2-dev@csf.colorado.edu From: SRE Subject: resubscribe command? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk I keep having people ask this question: >I forget...is there an easy way to tell the list server that >it should take all of my list subscriptions and shift them from >"xxx@yyy.com" to "aaa@bbb.com"? I've considered writing an external hack to parse the output of "show" and turn it into a bunch of commands (including sub, unsub, alias, and set) that recreate the subscriptions. This would also be useful for bulk list moves from one server or virtual domain to another, but it's not as clean as having a resub command in the server itself. Has anyone done something similar? Does anyone think it should be done (or should NOT be done?) Should the command (if done as a built-in) be "resubscribe" or "reregister" or something totally new like "changeaddress"? Built-in or external script? SRE mailto:eckert@climber.org | http://www.climber.org/eckert/ Info on peak climbing email lists mailto:info@climber.org Things change. People change. Things change people. From majordomo-workers-owner Sun Apr 23 15:25:10 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA23448; Sun, 23 Apr 2000 14:31:48 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA23438 for majordomo-workers@greatcircle.com; Sun, 23 Apr 2000 14:31:45 -0700 (PDT) Received: from audumla.mdacc.tmc.edu (audumla.mdacc.tmc.edu [143.111.64.70]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id NAA27916 for ; Mon, 17 Apr 2000 13:48:31 -0700 (PDT) Received: from [143.111.69.34] (stargazer.mdacc.tmc.edu [143.111.69.34]) by audumla.mdacc.tmc.edu (8.8.8+Sun/8.8.8) with ESMTP id QAA04674 for ; Mon, 17 Apr 2000 16:06:52 -0500 (CDT) Mime-Version: 1.0 X-Sender: ems@audumla.mdacc.tmc.edu (Unverified) Message-Id: Date: Mon, 17 Apr 2000 16:06:46 -0500 To: majordomo-workers@greatcircle.com From: "Eric M. Sisson" Subject: Change between Majordomo-1.94.4 and 1.94.5 Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Greetings, Majordomo Workers, Recently I upgraded Majordomo from version 1.94.4 to 1.94.5, and the following evening a cron job that generated the digest of a mailing list failed, complaining that the hostname had no domain name. I finally tracked the problem to routine "valid_addr" in file majordomo.pl. The following change allowed digest creation and mailing to resume: 605c605 < if (!(/\@/ && /\./)) { --- > if ((/\@/ && !/\./)) { Note that in version 1.94.4, in file majordomo.pl routine "valid_addr" has the following at line 590: if (/\@/ && !/\./) { so that my change actually restored the behavior of version 1.94.4. Some extra background information is that I am running Majordomo with Perl version 5.005_03 on a Sun running SunOS 5.6. SunOS insists on having simple hostnames rather than fully-qualified domain names in the hosts file (/etc/inet/hosts on SunOS-5.x). Perhaps adding confusion to this, I specify an alias for the host in Majordomo's configuration file. I am not calling this a bug, but it is a change in behavior that did have a negative effect on my operation. I wanted to bring it to your attention to give you all the opportunity to review the decision to make that change. Thanks to all involved for developing and maintaining Majordomo. I have used it for several years with many lists and find it a valuable tool. Regards, Eric Sisson -- Eric M. Sisson, Research Programmer Internet: ems@mdacc.tmc.edu Academic and Research Computing - Box 159 voice: 713-745-0610 University of Texas M. D. Anderson Cancer Center fax: 713-745-0615 1515 Holcombe Boulevard Houston, Texas 77030 From majordomo-workers-owner Sun Apr 23 15:40:08 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id OAA23492; Sun, 23 Apr 2000 14:32:38 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id OAA23482 for majordomo-workers@greatcircle.com; Sun, 23 Apr 2000 14:32:36 -0700 (PDT) Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA15463 for ; Tue, 18 Apr 2000 19:20:12 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA09886 for <@external-mail-relay.sgi.com:majordomo-workers@greatcircle.com>; Tue, 18 Apr 2000 19:43:08 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: from mando.engr.sgi.com (mando.engr.sgi.com [163.154.5.88]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id TAA85608 for <@cthulhu.engr.sgi.com:majordomo-workers@greatcircle.com>; Tue, 18 Apr 2000 19:39:04 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: (from relph@localhost) by mando.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id TAA15384; Tue, 18 Apr 2000 19:39:04 -0700 (PDT) Date: Tue, 18 Apr 2000 19:39:04 -0700 (PDT) Message-Id: <200004190239.TAA15384@mando.engr.sgi.com> From: John Relph To: majordomo-workers@greatcircle.com Subject: Outlook and Majordomo help Reply-to: relph@sgi.com Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hi folks, A user has complained that Microsoft Outlook and Outlook Express incorrectly makes an HTML mailto: link out of the mail addresses in Majordomo help messages. For example, Majordomo sends a confirmation message which contains the following: Someone (possibly you) has requested that your email address be added to or deleted from the mailing list "chalkhills@sgiblab.sgi.com". If you really want this action to be taken, please send the following commands (exactly as shown) back to "majordomo@sgiblab.sgi.com": Outlook will convert the two email addresses into mailto: links as follows: Someone (possibly you) has requested that your email address be added to or deleted from the mailing list "chalkhills@sgiblab.sgi.com". If you really want this action to be taken, please send the following commands (exactly as shown) back to "majordomo@sgiblab.sgi.com": Which is completely broken and bogus. But which also makes it difficult for Outlook users to easily send the "auth" message. I was thinking about trying to patch Majordomo such that the message would appear as follows: Someone (possibly you) has requested that your email address be added to or deleted from the mailing list . If you really want this action to be taken, please send the following commands (exactly as shown) back to : But there is a conflict with the "help" message: In the description below items contained in []'s are optional. When providing the item, do not include the []'s around it. Items in angle brackets, such as
, are meta-symbols that should be replaced by appropriate text without the angle brackets. Anybody have any brilliant ideas? -- John From majordomo-workers-owner Sun Apr 23 22:39:29 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA27731; Sun, 23 Apr 2000 22:28:19 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [205.147.43.2]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA27724 for ; Sun, 23 Apr 2000 22:28:14 -0700 (PDT) Received: from ee-nt (eckert@netcom3.netcom.com [199.183.9.103]) by kachina.jetcafe.org (8.9.1/8.9.1) with SMTP id WAA15436; Sun, 23 Apr 2000 22:48:00 -0700 (PDT) Message-Id: <3.0.5.32.20000423224756.00a591b0@pop.climber.org> X-Sender: eckert@pop.climber.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 23 Apr 2000 22:47:56 -0700 To: relph@sgi.com From: SRE Subject: Re: Outlook and Majordomo help Cc: majordomo-workers@GreatCircle.COM In-Reply-To: <200004190239.TAA15384@mando.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk At 07:39 PM 4/18/00 -0700, John Relph wrote: >A user has complained that Microsoft Outlook and Outlook Express >incorrectly makes an HTML mailto: link out of the mail addresses [snip] >Anybody have any brilliant ideas? Other than switching to a REAL mail tool? Tell them to turn off HTML formatting in their configuration/preferences menu. Most will tell you it can't be done, or can only be done per-message, but I've seen people manage to do it. They generate even more muck when they send, so I put the "demime" perl script in a pipe to clean up commands being sent TO the server. From majordomo-workers-owner Wed Apr 26 08:21:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA07008; Wed, 26 Apr 2000 08:14:06 -0700 (PDT) Received: from clifford.inch.com (clifford.inch.com [207.240.140.163]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id IAA07000 for ; Wed, 26 Apr 2000 08:13:59 -0700 (PDT) Received: (from omar@localhost) by clifford.inch.com (8.9.3/8.8.5) id KAA11888 for majordomo-workers@GreatCircle.COM; Wed, 26 Apr 2000 10:26:00 -0400 Message-ID: <20000426102600.A11875@clifford.inch.com> Date: Wed, 26 Apr 2000 10:26:00 -0400 From: Omar Thameen To: majordomo-workers@GreatCircle.COM Subject: patches for listname-unzubscribe address? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Are there any patches to Mj1 which allow users to zubscribe by sending email to listname-zubscribe@domain.com rather than, or in addition to, the listname-request@domain.com? Omar From majordomo-workers-owner Sat Apr 29 19:36:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA27632; Sat, 29 Apr 2000 19:31:35 -0700 (PDT) Received: from thelab.hub.org (nat194.149.mpoweredpc.net [142.177.194.149]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA27625 for ; Sat, 29 Apr 2000 19:31:22 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id XAA00445; Sat, 29 Apr 2000 23:52:21 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 29 Apr 2000 23:52:21 -0300 (ADT) From: The Hermit Hacker To: Michael Yount , mj2-dev@csf.colorado.edu Subject: problem with current CVS ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Morning all ... upgraded today, and noticed a sudden drop (to zero) of mail to my lists ... checked the .debug file, and found: Can't locate Errno.pm in @INC (@INC contains: /usr/libdata/perl/5.00503/mach /us r/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/lo cal/lib/perl5/site_perl/5.005) at /usr/local/majordomo/bin/mj_enqueue line 41. BEGIN failed--compilation aborted at /usr/local/majordomo/bin/mj_enqueue line 41 Found it in ports on my FreeBSD box, but shouldn't Errno-1.09 be something that Makefile.PL checks for? :) Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From majordomo-workers-owner Sat Apr 29 19:51:24 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA27704; Sat, 29 Apr 2000 19:42:04 -0700 (PDT) Received: from thelab.hub.org (nat194.149.mpoweredpc.net [142.177.194.149]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA27696 for ; Sat, 29 Apr 2000 19:41:58 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id AAA00567; Sun, 30 Apr 2000 00:03:06 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 30 Apr 2000 00:03:06 -0300 (ADT) From: The Hermit Hacker To: Michael Yount , mj2-dev@csf.colorado.edu Subject: 'Can't call method "head" ... ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Does this mean anything: %tail mj_majord.debug --== MIME::ParserBase::parse_preamble(): multipart message has no parts Can't call method "head" on an undefined value at /usr/local/majordomo/bin/mj_qu euerun line 462, chunk 19. --== MIME::ParserBase::parse_preamble(): multipart message has no parts Can't call method "head" on an undefined value at /usr/local/majordomo/bin/mj_qu euerun line 462, chunk 19. --== MIME::ParserBase::parse_preamble(): multipart message has no parts Can't call method "head" on an undefined value at /usr/local/majordomo/bin/mj_qu euerun line 462, chunk 19. --== MIME::ParserBase::parse_preamble(): multipart message has no parts Can't call method "head" on an undefined value at /usr/local/majordomo/bin/mj_qu euerun line 462, chunk 19. --== MIME::ParserBase::parse_preamble(): multipart message has no parts Can't call method "head" on an undefined value at /usr/local/majordomo/bin/mj_qu euerun line 462, chunk 19. Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From majordomo-workers-owner Sun Apr 30 22:05:59 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA10923; Sun, 30 Apr 2000 21:43:28 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA10910 for majordomo-workers@greatcircle.com; Sun, 30 Apr 2000 21:43:25 -0700 (PDT) Received: from lists.linuxppc.org (lists.linuxppc.org [169.207.161.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA26467 for ; Sun, 23 Apr 2000 19:49:54 -0700 (PDT) Received: (from dwolfe@localhost) by lists.linuxppc.org (8.9.1a/8.9.1) id WAA31100; Sun, 23 Apr 2000 22:09:40 -0500 Date: Sun, 23 Apr 2000 22:09:40 -0500 From: Dave Wolfe To: relph@sgi.com Cc: majordomo-workers@GreatCircle.COM Subject: Re: Outlook and Majordomo help Message-ID: <20000423220940.B30799@lists.linuxppc.org> References: <200004190239.TAA15384@mando.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200004190239.TAA15384@mando.engr.sgi.com>; from John Relph on Tue, Apr 18, 2000 at 07:39:04PM -0700 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ John Relph writes: ] > > A user has complained that Microsoft Outlook and Outlook Express > incorrectly makes an HTML mailto: link out of the mail addresses in > Majordomo help messages. So why do they continue to use a mailer that mangles their mail? (Rhetorical question, don't answer). Contrary to Bill's commands, they do have a choice. > Outlook will convert the two email addresses into mailto: links as follows: > > Someone (possibly you) has requested that your email address be added > to or deleted from the mailing list " HREF="mailto:chalkhills@sgiblab.sgi.com".">chalkhills@sgiblab.sgi.com". > > If you really want this action to be taken, please send the following > commands (exactly as shown) back to " HREF="majordomo@sgiblab.sgi.com":">majordomo@sgiblab.sgi.com": > > Which is completely broken and bogus. But which also makes it > difficult for Outlook users to easily send the "auth" message. How so? That part of the message is supposed to be stripped away and to reply only w/ the auth command. The key word there being "reply", not click on every address their mailer corrupts and highlights. I view it as an intelligence test to gain admittance to my lists. ;-> -- Dave Wolfe From majordomo-workers-owner Sun Apr 30 22:10:14 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA10951; Sun, 30 Apr 2000 21:43:41 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA10941 for majordomo-workers@greatcircle.com; Sun, 30 Apr 2000 21:43:37 -0700 (PDT) Received: from lists.linuxppc.org (lists.linuxppc.org [169.207.161.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA26784 for ; Sun, 23 Apr 2000 20:11:44 -0700 (PDT) Received: (from dwolfe@localhost) by lists.linuxppc.org (8.9.1a/8.9.1) id WAA31189; Sun, 23 Apr 2000 22:31:32 -0500 Date: Sun, 23 Apr 2000 22:31:32 -0500 From: Dave Wolfe To: relph@sgi.com Cc: majordomo-workers@GreatCircle.COM, majordomo-patches@cloud.ccsf.cc.ca.us Subject: Re: majordomo.pl address matching Message-ID: <20000423223132.C30799@lists.linuxppc.org> References: <200004231953.MAA87125@mando.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200004231953.MAA87125@mando.engr.sgi.com>; from John Relph on Sun, Apr 23, 2000 at 12:53:21PM -0700 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ John Relph writes: ] > > This patch tries to do better checking to see if two email addresses > match because they are on different machines in the same domain. For > example, as in the example in majordomo.pl, is > considered to match . > > This patch increases the debugging output as well as doing a slightly > better job of checking. > > Any comments? Yes, can you please use unified diff format so the old and new lines are together? For Gnu diff that's the -u option. I can't tell if your changes even do the same thing, but it appears that they attempt to deal w/ unqualified addresses (no domain). Don't know about stock 1.94.5, but other patches disallow unqualified addresses. Your best bet is to fix your MTA so that you never get unqualified addresses. It prevents a lot of other problems that way. > ! local(@addr1,@addr2); > ! @addr1 = split(/\@/, $a1[0]); > ! @addr2 = split(/\@/, $a2[0]); > ! > ! if ($partial == 2) { # see if addresses are I can't tell what the alternative to the 'if' is now, but it seems odd to move the splits out of the 'if' given that the only place they were used was inside it. > ! if ($#addr1 == 1) { > ! print STDERR "addr_match: comparing $addr1[1] against $main'whereami\n" if $DEBUG; > ! } > ! if ($#addr2 == 1) { > ! print STDERR "addr_match: comparing $addr2[1] against $main'whereami\n" if $DEBUG; > ! } ICK! Please combine the conditions: print STDERR "addr_match: comparing $addr1[1] against $main'whereami\n" if $DEBUG && $#addr1 == 1; print STDERR "addr_match: comparing $addr2[1] against $main'whereami\n" if $DEBUG && $#addr2 == 1; -- Dave Wolfe From majordomo-workers-owner Sun Apr 30 22:27:43 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA10998; Sun, 30 Apr 2000 21:44:06 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA10985 for majordomo-workers@greatcircle.com; Sun, 30 Apr 2000 21:44:04 -0700 (PDT) Received: from lists.linuxppc.org (lists.linuxppc.org [169.207.161.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA05460 for ; Mon, 24 Apr 2000 09:18:13 -0700 (PDT) Received: (from dwolfe@localhost) by lists.linuxppc.org (8.9.1a/8.9.1) id LAA16794; Mon, 24 Apr 2000 11:38:02 -0500 Date: Mon, 24 Apr 2000 11:37:58 -0500 From: Dave Wolfe To: "Eric M. Sisson" Cc: majordomo-workers@GreatCircle.COM Subject: Re: Change between Majordomo-1.94.4 and 1.94.5 Message-ID: <20000424113758.H13769@lists.linuxppc.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Eric M. Sisson on Mon, Apr 17, 2000 at 04:06:46PM -0500 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ Eric M. Sisson writes: ] > > Recently I upgraded Majordomo from version 1.94.4 to 1.94.5, and the > following evening a cron job that generated the digest of a mailing > list failed, complaining that the hostname had no domain name. I > finally tracked the problem to routine "valid_addr" in file > majordomo.pl. The following change allowed digest creation and > mailing to resume: > > 605c605 > < if (!(/\@/ && /\./)) { > --- > > if ((/\@/ && !/\./)) { > > Note that in version 1.94.4, in file majordomo.pl routine > "valid_addr" has the following at line 590: > > if (/\@/ && !/\./) { > > so that my change actually restored the behavior of version 1.94.4. > > Some extra background information is that I am running Majordomo with > Perl version 5.005_03 on a Sun running SunOS 5.6. SunOS insists on > having simple hostnames rather than fully-qualified domain names in > the hosts file (/etc/inet/hosts on SunOS-5.x). Perhaps adding > confusion to this, I specify an alias for the host in Majordomo's > configuration file. > > I am not calling this a bug, but it is a change in behavior that did > have a negative effect on my operation. I wanted to bring it to your > attention to give you all the opportunity to review the decision to > make that change. If you read the message following the 'if', you'll see that it's trying to detect addresses that aren't FQDNs (Fully Qualified Domain Names). You don't say what address is being checked but I gather it's local to the Mj server. While you have the source and can make any local modifications you desire, I think you need to fix your local MTA configuration to always fully qualify local addresses so that unqualified remote addresses can be detected. -- Dave Wolfe From majordomo-workers-owner Sun Apr 30 22:38:55 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA10881; Sun, 30 Apr 2000 21:42:38 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA10871 for majordomo-workers@greatcircle.com; Sun, 30 Apr 2000 21:42:35 -0700 (PDT) Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id MAA22060 for ; Sun, 23 Apr 2000 12:34:42 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA24305 for <@external-mail-relay.sgi.com:majordomo-workers@greatcircle.com>; Sun, 23 Apr 2000 12:49:42 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: from mando.engr.sgi.com (mando.engr.sgi.com [163.154.5.88]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA99809 for <@cthulhu.engr.sgi.com:majordomo-workers@greatcircle.com>; Sun, 23 Apr 2000 12:54:23 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: (from relph@localhost) by mando.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id MAA86769; Sun, 23 Apr 2000 12:54:23 -0700 (PDT) Date: Sun, 23 Apr 2000 12:54:23 -0700 (PDT) Message-Id: <200004231954.MAA86769@mando.engr.sgi.com> From: John Relph To: majordomo-workers@greatcircle.com Subject: Outlook and Majordomo help Reply-to: relph@tmbg.org Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Hi folks, A user has complained that Microsoft Outlook and Outlook Express incorrectly makes an HTML mailto: link out of the mail addresses in Majordomo help messages. For example, Majordomo sends a confirmation message which contains the following: Someone (possibly you) has requested that your email address be added to or deleted from the mailing list "chalkhills@sgiblab.sgi.com". If you really want this action to be taken, please send the following commands (exactly as shown) back to "majordomo@sgiblab.sgi.com": Outlook will convert the two email addresses into mailto: links as follows: Someone (possibly you) has requested that your email address be added to or deleted from the mailing list "chalkhills@sgiblab.sgi.com". If you really want this action to be taken, please send the following commands (exactly as shown) back to "majordomo@sgiblab.sgi.com": Which is completely broken and bogus. But which also makes it difficult for Outlook users to easily send the "auth" message. I was thinking about trying to patch Majordomo such that the message would appear as follows: Someone (possibly you) has requested that your email address be added to or deleted from the mailing list . If you really want this action to be taken, please send the following commands (exactly as shown) back to : But there is a conflict with the "help" message: In the description below items contained in []'s are optional. When providing the item, do not include the []'s around it. Items in angle brackets, such as
, are meta-symbols that should be replaced by appropriate text without the angle brackets. Anybody have any brilliant ideas? -- John From majordomo-workers-owner Sun Apr 30 22:57:33 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA11012; Sun, 30 Apr 2000 21:44:11 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA10997 for majordomo-workers@greatcircle.com; Sun, 30 Apr 2000 21:44:06 -0700 (PDT) Received: from lists.linuxppc.org (lists.linuxppc.org [169.207.161.3]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA05677 for ; Mon, 24 Apr 2000 09:49:44 -0700 (PDT) Received: (from dwolfe@localhost) by lists.linuxppc.org (8.9.1a/8.9.1) id MAA17378; Mon, 24 Apr 2000 12:09:38 -0500 Date: Mon, 24 Apr 2000 12:09:37 -0500 From: Dave Wolfe To: relph@sgi.com Cc: majordomo-workers@greatcircle.com, majordomo-patches@cloud.ccsf.cc.ca.us Subject: Re: majordomo.pl address matching Message-ID: <20000424120937.J13769@lists.linuxppc.org> References: <200004231953.MAA87125@mando.engr.sgi.com> <20000423223132.C30799@lists.linuxppc.org> <10004232053.ZM97064@mando.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <10004232053.ZM97064@mando.engr.sgi.com>; from John Relph on Sun, Apr 23, 2000 at 08:53:14PM -0700 Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [ John Relph writes: ] > On Apr 23, 22:31, Dave Wolfe wrote: > >I can't tell if your changes even do the same thing, but it appears that > >they attempt to deal w/ unqualified addresses (no domain). Don't know > >about stock 1.94.5, but other patches disallow unqualified addresses. > >Your best bet is to fix your MTA so that you never get unqualified > >addresses. It prevents a lot of other problems that way. > > Actually, I am comparing the addresses to "majordomo@where.am.i". To > make sure that neither of the addresses is the address of majordomo. > I think. You know, it's been so long since I hacked this that I don't > even remember what it was I was trying to do. But I do know that this > change fixed some problems I was having. (I hope it wasn't the unQ'ed > address problem.) I guess I'll have to look at it once more. (I wish > I had emacs on my majordomo machine.) You may be right about the > unQ'ed address hack, though. [...] > if ($addr1[0] eq $addr2[0]) { > if ($#addr1 == 0 && $#addr2 == 1 && $addr2[1] eq $main'whereami) { #' > return(1); > } > if ($#addr2 == 0 && $#addr1 == 1 && $addr1[1] eq $main'whereami) { #' > return(1); > } > } Nope, $whereami is the local FQDN, $whoami is Majordomo@$whereami. Annotated: # if user names are the same... if ($addr1[0] eq $addr2[0]) { # if addr1 has no domain and addr2 does and addr2's domain is my # domain, then return true. if ($#addr1 == 0 && $#addr2 == 1 && $addr2[1] eq $main'whereami) { #' return(1); } # if addr2 has no domain and addr1 does and addr1's domain is my # domain, then return true. if ($#addr2 == 0 && $#addr1 == 1 && $addr1[1] eq $main'whereami) { #' return(1); } } In other words, you expect to receive unqualified local addresses and want to detect them. Unfortunately, unqualified remote addresses that match local users will be matched too. Understand that I have no intention of telling you what you can or can't do w/ your Mj installation. If it works for you, it's served its purpose. But I think the real problem is w/ the MTA configuration and that makes the changes unsuitable for general use. Same story for the LookOut!...er, OutLook users; those folks definitely need a lot of help, probably more than a help file or instructions in a mail message can offer. You might want to look into Majordomo2 instead, which simplifies the authentication exchange somewhat. -- Dave Wolfe From majordomo-workers-owner Sun Apr 30 23:11:44 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA10938; Sun, 30 Apr 2000 21:43:36 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA10928 for majordomo-workers@greatcircle.com; Sun, 30 Apr 2000 21:43:34 -0700 (PDT) Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id TAA26546 for ; Sun, 23 Apr 2000 19:58:27 -0700 (PDT) Received: from cthulhu.engr.sgi.com (gate3-relay.engr.sgi.com [130.62.1.234]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id UAA06570; Sun, 23 Apr 2000 20:22:21 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: from mando.engr.sgi.com (mando.engr.sgi.com [163.154.5.88]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id UAA79821; Sun, 23 Apr 2000 20:18:10 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: (from relph@localhost) by mando.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id UAA95730; Sun, 23 Apr 2000 20:18:09 -0700 (PDT) Date: Sun, 23 Apr 2000 20:18:09 -0700 (PDT) From: relph@mando.engr.sgi.com (John Relph) Message-Id: <10004232018.ZM96651@mando.engr.sgi.com> In-Reply-To: Dave Wolfe "Re: Outlook and Majordomo help" (Apr 23, 22:09) References: <200004190239.TAA15384@mando.engr.sgi.com> <20000423220940.B30799@lists.linuxppc.org> Reply-To: relph@sgi.com X-Mailer: Z-Mail-SGI (3.2S.3 08feb96 MediaMail) To: Dave Wolfe , relph@sgi.com Subject: Re: Outlook and Majordomo help Cc: majordomo-workers@greatcircle.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On Apr 23, 22:09, Dave Wolfe wrote: >[ John Relph writes: ] >> >> A user has complained that Microsoft Outlook and Outlook Express >> incorrectly makes an HTML mailto: link out of the mail addresses in >> Majordomo help messages. > >So why do they continue to use a mailer that mangles their mail? >(Rhetorical question, don't answer). Contrary to Bill's commands, they >do have a choice. Perhaps that's so, but that doesn't mean that we can't help them out just a little. >> Outlook will convert the two email addresses into mailto: links as follows: >> >> Someone (possibly you) has requested that your email address be added >> to or deleted from the mailing list "> HREF="mailto:chalkhills@sgiblab.sgi.com".">chalkhills@sgiblab.sgi.com". >> >> If you really want this action to be taken, please send the following >> commands (exactly as shown) back to "> HREF="majordomo@sgiblab.sgi.com":">majordomo@sgiblab.sgi.com": >> >> Which is completely broken and bogus. But which also makes it >> difficult for Outlook users to easily send the "auth" message. > >How so? That part of the message is supposed to be stripped away and to >reply only w/ the auth command. The key word there being "reply", not >click on every address their mailer corrupts and highlights. I view it >as an intelligence test to gain admittance to my lists. ;-> It's true that if a person reads the instructions and follows them, it should work. But Outlook also highlights the majordomo address, which in theory should make it easy for the fluser to click on that address and then cut and paste the "auth" line(s) into the new message being composed. Unfortunately, Outlook botches it. The real problem here is that I get complaints about the difficulty of subscribing. I would rather make it slightly easier (in this particular case, given the quirks of the mailer) so that I don't have to answer questions personally. After all, Majordomo does also say If you have any questions about the policy of the list owner, please contact "chalkhills-approval@sgiblab.sgi.com". (Yes, I know this isn't a policy question, but this is the address of a "live human being" and thus there is the expectation of real help being given. I may be a curmudgeon, but I don't necessarily want to be an asshole all the time.) So basically, if all I have to do is to change the format of a few lines of help text, then I'm all for it. So I'm still looking for suggestions on the format. Thanks. -- John >-- > Dave Wolfe From majordomo-workers-owner Sun Apr 30 23:27:42 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA11741; Sun, 30 Apr 2000 22:49:16 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id WAA11731 for majordomo-workers@greatcircle.com; Sun, 30 Apr 2000 22:49:13 -0700 (PDT) Received: from central.undoo.com (pbi-dsl.undoo.com [63.199.100.82]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id JAA23462 for ; Thu, 27 Apr 2000 09:36:10 -0700 (PDT) Received: from opal.undoo.com (IDENT:jsweet@opal.undoo.com [192.168.100.30]) by central.undoo.com (8.9.3/8.9.3) with ESMTP id JAA04592 for ; Thu, 27 Apr 2000 09:56:36 -0700 Message-Id: <200004271656.JAA04592@central.undoo.com> To: majordomo-workers@greatcircle.com Subject: majordomo config-test suggested patch MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" Content-ID: <4064.956854549.0@opal.undoo.com> Date: Thu, 27 Apr 2000 09:56:35 -0700 From: Jerry Sweet Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4064.956854549.1@opal.undoo.com> Content-Description: explanation Patch description: My humble offering of a suggested patch to config-test to do the following things: - Say what's wrong with the list directory permissions. - Say what's being sent in the registration message. Majordomo version: majordomo-1.94.5 Patches: config-test Jerry Sweet undoo.com ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4064.956854549.2@opal.undoo.com> Content-Description: config-test patch *** config-test.orig Wed Aug 27 08:17:13 1997 --- config-test Thu Apr 27 09:44:21 2000 *************** *** 186,192 **** if (-r $listdir && -w $listdir && -x $listdir) { &good("list directory $listdir has good permissions."); } else { ! &bad("list directory $listdir has bad permissions"); } } else { print "Hmmm, list directory $listdir doesn't exist\n or isn't a directory.\n"; --- 186,192 ---- if (-r $listdir && -w $listdir && -x $listdir) { &good("list directory $listdir has good permissions."); } else { ! &bad("list directory $listdir has bad permissions - should be 777"); } } else { print "Hmmm, list directory $listdir doesn't exist\n or isn't a directory.\n"; *************** *** 349,355 **** ($cf) closely, and if it still looks okay, consider asking the majordomo-users mailing list at "majordomo-users\@greatcircle.com" for assistance. Be sure ! and fully specify what your problems are, and what type of machine (and operating system) you are using. Enjoy! --- 349,355 ---- ($cf) closely, and if it still looks okay, consider asking the majordomo-users mailing list at "majordomo-users\@greatcircle.com" for assistance. Be sure ! to specify fully what your problems are, and what type of machine (and operating system) you are using. Enjoy! *************** *** 360,370 **** if ( ! -e $registration_file || `cat $registration_file` ne $majordomo_version) { print <<"ZOT"; I see you haven't registered this version of Majordomo. By registering, you will be notified of patches and further releases ! of Majordomo. Shall I send email to majordomo-registration\@greatcircle.com ! to register this version? (I'll cc $whoami_owner) ZOT #' --- 360,382 ---- if ( ! -e $registration_file || `cat $registration_file` ne $majordomo_version) { + $uname_info = `uname -a`; print <<"ZOT"; I see you haven't registered this version of Majordomo. By registering, you will be notified of patches and further releases ! of Majordomo. Shall I send the following email to register this version? ! The message will look like this: ! ! To: majordomo-registration\@greatcircle.com ! From: $whoami ! Sender: $whoami_owner ! Subject: Majordomo Registration ! ! Majordomo Version: $majordomo_version ! Perl version $] ! Majordomo Owner: $whoami_owner ! Uname: $uname_info ! ZOT #' *************** *** 389,395 **** print REG "Majordomo Version: $majordomo_version\n"; print REG "Perl version $]\n"; print REG "Majordomo Owner: $whoami_owner\n"; ! print REG "Uname: " . `uname -a`; close REG; } else { print "Ooooh, like to live dangerously, eh?!\n\n"; --- 401,407 ---- print REG "Majordomo Version: $majordomo_version\n"; print REG "Perl version $]\n"; print REG "Majordomo Owner: $whoami_owner\n"; ! print REG "Uname: " . $uname_info; close REG; } else { print "Ooooh, like to live dangerously, eh?!\n\n"; ------- =_aaaaaaaaaa0-- From majordomo-workers-owner Sun Apr 30 23:31:26 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id VAA10964; Sun, 30 Apr 2000 21:43:45 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id VAA10954 for majordomo-workers@greatcircle.com; Sun, 30 Apr 2000 21:43:41 -0700 (PDT) Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id UAA26914 for ; Sun, 23 Apr 2000 20:33:33 -0700 (PDT) Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id UAA07858; Sun, 23 Apr 2000 20:53:16 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: from mando.engr.sgi.com (mando.engr.sgi.com [163.154.5.88]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id UAA08512; Sun, 23 Apr 2000 20:53:15 -0700 (PDT) mail_from (relph@mando.engr.sgi.com) Received: (from relph@localhost) by mando.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id UAA97079; Sun, 23 Apr 2000 20:53:14 -0700 (PDT) Date: Sun, 23 Apr 2000 20:53:14 -0700 (PDT) From: relph@mando.engr.sgi.com (John Relph) Message-Id: <10004232053.ZM97064@mando.engr.sgi.com> In-Reply-To: Dave Wolfe "Re: majordomo.pl address matching" (Apr 23, 22:31) References: <200004231953.MAA87125@mando.engr.sgi.com> <20000423223132.C30799@lists.linuxppc.org> Reply-To: relph@sgi.com X-Mailer: Z-Mail-SGI (3.2S.3 08feb96 MediaMail) To: Dave Wolfe , relph@sgi.com Subject: Re: majordomo.pl address matching Cc: majordomo-workers@greatcircle.com, majordomo-patches@cloud.ccsf.cc.ca.us Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk On Apr 23, 22:31, Dave Wolfe wrote: >[ John Relph writes: ] >> >> This patch tries to do better checking to see if two email addresses >> match because they are on different machines in the same domain. For >> example, as in the example in majordomo.pl, is >> considered to match . >> >> This patch increases the debugging output as well as doing a slightly >> better job of checking. >> >> Any comments? > >Yes, can you please use unified diff format so the old and new lines are >together? For Gnu diff that's the -u option. Here's such a diff: --- /usr/local/majordomo-1.94.5/majordomo.pl.orig Sun Feb 27 16:21:38 2000 +++ majordomo.pl Sun Feb 27 19:10:40 2000 @@ -173,11 +173,16 @@ return(undef); } - if ($partial == 2 && ($a1[0] ne $a2[0])) { # see if addresses are + if ($a1[0] eq $a2[0]) { + return(1); + } + + local(@addr1,@addr2); + @addr1 = split(/\@/, $a1[0]); + @addr2 = split(/\@/, $a2[0]); + + if ($partial == 2) { # see if addresses are # foo@baz.bax.edu, foo@bax.edu - local(@addr1,@addr2); - @addr1 = split(/\@/, $a1[0]); - @addr2 = split(/\@/, $a2[0]); if ( $#addr1 == $#addr2 && $#addr1 == 1 && $addr1[0] eq $addr2[0] && (index($addr1[1], $addr2[1]) >= $[)) { @@ -185,7 +190,23 @@ } } - return($a1[0] eq $a2[0]); + if ($#addr1 == 1) { + print STDERR "addr_match: comparing $addr1[1] against $main'whereami\n" if $DEBUG; + } + if ($#addr2 == 1) { + print STDERR "addr_match: comparing $addr2[1] against $main'whereami\n" if $DEBUG; + } + + if ($addr1[0] eq $addr2[0]) { + if ($#addr1 == 0 && $#addr2 == 1 && $addr2[1] eq $main'whereami) { #' + return(1); + } + if ($#addr2 == 0 && $#addr1 == 1 && $addr1[1] eq $main'whereami) { #' + return(1); + } + } + + return(0); } # These are package globals referenced by &setabortaddr and &abort >I can't tell if your changes even do the same thing, but it appears that >they attempt to deal w/ unqualified addresses (no domain). Don't know >about stock 1.94.5, but other patches disallow unqualified addresses. >Your best bet is to fix your MTA so that you never get unqualified >addresses. It prevents a lot of other problems that way. Actually, I am comparing the addresses to "majordomo@where.am.i". To make sure that neither of the addresses is the address of majordomo. I think. You know, it's been so long since I hacked this that I don't even remember what it was I was trying to do. But I do know that this change fixed some problems I was having. (I hope it wasn't the unQ'ed address problem.) I guess I'll have to look at it once more. (I wish I had emacs on my majordomo machine.) You may be right about the unQ'ed address hack, though. >> ! local(@addr1,@addr2); >> ! @addr1 = split(/\@/, $a1[0]); >> ! @addr2 = split(/\@/, $a2[0]); >> ! >> ! if ($partial == 2) { # see if addresses are > >I can't tell what the alternative to the 'if' is now, but it seems odd >to move the splits out of the 'if' given that the only place they were >used was inside it. Here's the full (new) code: if ($a1[0] eq $a2[0]) { return(1); } local(@addr1,@addr2); @addr1 = split(/\@/, $a1[0]); @addr2 = split(/\@/, $a2[0]); if ($partial == 2) { # see if addresses are # foo@baz.bax.edu, foo@bax.edu if ( $#addr1 == $#addr2 && $#addr1 == 1 && $addr1[0] eq $addr2[0] && (index($addr1[1], $addr2[1]) >= $[)) { return(1); } } if ($#addr1 == 1) { print STDERR "addr_match: comparing $addr1[1] against $main'whereami\n" if $DEBUG; } if ($#addr2 == 1) { print STDERR "addr_match: comparing $addr2[1] against $main'whereami\n" if $DEBUG; } if ($addr1[0] eq $addr2[0]) { if ($#addr1 == 0 && $#addr2 == 1 && $addr2[1] eq $main'whereami) { #' return(1); } if ($#addr2 == 0 && $#addr1 == 1 && $addr1[1] eq $main'whereami) { #' return(1); } } return(0); >> ! if ($#addr1 == 1) { >> ! print STDERR "addr_match: comparing $addr1[1] against $main'whereami\n" if $DEBUG; >> ! } >> ! if ($#addr2 == 1) { >> ! print STDERR "addr_match: comparing $addr2[1] against $main'whereami\n" if $DEBUG; >> ! } > >ICK! Please combine the conditions: > > print STDERR "addr_match: comparing $addr1[1] against $main'whereami\n" > if $DEBUG && $#addr1 == 1; > > print STDERR "addr_match: comparing $addr2[1] against $main'whereami\n" > if $DEBUG && $#addr2 == 1; > >-- > Dave Wolfe -- John From majordomo-workers-owner Sun Apr 30 23:38:55 2000 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id WAA11786; Sun, 30 Apr 2000 22:49:33 -0700 (PDT) Received: (mcb@localhost) by honor.greatcircle.com (8.8.5/Honor-980202-1) id WAA11773 for majordomo-workers@greatcircle.com; Sun, 30 Apr 2000 22:49:26 -0700 (PDT) Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id WAA00389; Thu, 27 Apr 2000 22:15:53 -0700 (PDT) Received: from judge.mcom.com (judge.mcom.com [205.217.237.53]) by netscape.com (8.8.5/8.8.5) with ESMTP id WAA26738; Thu, 27 Apr 2000 22:30:25 -0700 (PDT) Received: from netscape.com ([205.217.240.34]) by judge.mcom.com (Netscape Messaging Server 4.03) with ESMTP id FTPOWM00.XCP; Thu, 27 Apr 2000 22:36:22 -0700 Message-ID: <3909235C.9CB1A662@netscape.com> Date: Fri, 28 Apr 2000 00:36:28 -0500 From: Dan Liston Organization: iPlanet E-Commerce Solutions, A Sun Netscape Alliance X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com CC: Omar Thameen , Jeff Lasman , majordomo-workers@greatcircle.com Subject: Re: patches for listname-(un)zubscribe address? References: <20000426102600.A11875@clifford.inch.com> <390756BA.B694B852@netscape.com> <20000426182720.B12655@clifford.inch.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk Your list must have an open or auto (un)zubscribe_policy if you do not want the user to be burdened with a confirmation message. It will work with open+confirm, but that kind of defeats the purpose, doesn't it. This is how I set up the alias; listname-(un)zubscribe: "|/majordomo/wrapper (un)zubscribe listname" By copying zubscribe to unzubscribe and replacing all occurances of zubscribe in the file with unzubscribe, you get the second tool. I suppose I could have got fancy and used the same tool for both zubscribe and unzubscribe depending on which way it was called, like the bounce tool does, or even grabbed the $sender variable from the listname.config file, but this is the down and dirty and IT WORKS! :) You will need to edit the location of perl, and if you have a preference, choose a $sender to match your taste as well. Please consider this a skeleton with lots of room for flesh. Dan Liston --------BEGIN FILE----------- #!/usr/local/bin/perl # The above needs to be edited to match your system # $Revision: 0.01 $ # $Date: 2000/04/27 22:44:33 $ # $Author: dliston $ # Shamelessly stolen from request-answer # PATH is set in the wrapper, so there is no need to set it here. # Any variables defined in majordomo.cf will not be defined here. # Example aliases file entry: # $list-subscribe: "|/path/to/majordomo/wrapper subscribe $list" # Uncomment the $sender variable of your liking. Just be sure you # have an entry in aliases that matches the $sender that you choose. # The default $sender, owner-$list fits sendmail systems perfectly. # Read and execute the .cf file $cf = $ENV{"MAJORDOMO_CF"} || "/etc/majordomo.cf"; if ($ARGV[0] eq "-C") { $cf = $ARGV[1]; shift(@ARGV); shift(@ARGV); } if (! -r $cf) { die("$cf not readable; stopped"); } require "$cf"; chdir($homedir) || die("Can't chdir(\"$homedir\"): $!"); unshift(@INC, $homedir); require "shlock.pl"; require "majordomo.pl"; &ParseMailHeader(STDIN, *hdrs); $reply_to = &RetMailAddr(*hdrs); $reply_to = join(", ", &ParseAddrs($reply_to)); die("subscribe: $reply_to is not a valid return address.\n") if (! &valid_addr($reply_to)); # robots should not reply to other robots... if ($reply_to =~ m/$majordomo_dont_reply/i) { &abort( "$whoami: not replying to $1 to avoid mail loop.\n"); } $in_reply_to = $hdrs{"message-id"} . ", from " . $hdrs{"from"}; $list = $ARGV[0]; $sender = "owner-$list\@$whereami"; #$sender = "$list-owner\@$whereami"; #$sender = "$list-request\@$whereami"; #$sender = "$list-approval\@$whereami"; $mailcmd = eval qq/"$bounce_mailer"/; if (defined($isParent = open(MAIL, "|-"))) { &do_exec_sendmail(split(' ',$mailcmd)) unless $isParent; } else { &abort("Failed to fork prior to mailer exec"); } print MAIL <<"EOM"; To: $whoami From: $reply_to Subject: mail to $list-subscribe\@$whereami In-Reply-To: $in_reply_to subscribe $list $reply_to EOM close(MAIL); exit 0; ---------------END FILE----------------- Final note: I have tested both the subscribe and unsubscribe versions of this file on my system successfully. Omar Thameen wrote: > > The majordomo program will still require that you put the request in the > body of the message. I was hoping to find a way such that any email to > listname-zubscribe would add them to the list. > > Omar > > On Wed, Apr 26, 2000 at 03:51:06PM -0500, Dan Liston wrote: > > No patch needed. Just create an alias like; > > listname-zubscribe: "|/whatever/majordomo/wrapper majordomo -l listname" > > > > Dan Liston > > > > Omar Thameen wrote: > > > > > > Are there any patches to Mj1 which allow users to zubscribe by > > > sending email to listname-zubscribe@domain.com rather than, or > > > in addition to, the listname-request@domain.com? > > > > > > Omar