From majordomo-workers-owner Tue Jan 9 07:15:13 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id GAA15724; Tue, 9 Jan 2001 06:59:24 -0800 (PST) Received: from jester.ti.com (jester.ti.com [192.94.94.1]) by honor.greatcircle.com (Postfix) with ESMTP id A7B9217E8C for ; Tue, 9 Jan 2001 06:59:19 -0800 (PST) Received: from dlep6.itg.ti.com ([157.170.188.9]) by jester.ti.com (8.11.1/8.11.1) with ESMTP id f09ExI922215 for ; Tue, 9 Jan 2001 08:59:18 -0600 (CST) Received: from dlep6.itg.ti.com (localhost [127.0.0.1]) by dlep6.itg.ti.com (8.9.3/8.9.3) with ESMTP id IAA08740 for ; Tue, 9 Jan 2001 08:59:17 -0600 (CST) Received: from dleefp70.itg.ti.com (dleefp70.itg.ti.com [157.170.134.90]) by dlep6.itg.ti.com (8.9.3/8.9.3) with ESMTP id IAA08727 for ; Tue, 9 Jan 2001 08:59:17 -0600 (CST) Received: by dleefp70.itg.ti.com with Internet Mail Service (5.5.2650.21) id ; Tue, 9 Jan 2001 08:57:46 -0600 Message-ID: <6DD22B82EC6AD31182E00008C791AC8E046F91@dleefp02.itg.ti.com> From: "Hansel, Glen" To: "'majordomo-workers@greatcircle.com'" Subject: restrict post Date: Tue, 9 Jan 2001 08:57:58 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk How close is the functionality and the implementation on the restrict post logic in Majordomo 1.94.4 and Majordomo 2? We are currently running Majordomo 1.94.4 and we need more flexibility with restrict post than the "mungedomain" option appears to provide. In particular, we would like to have some way to easily include everybody within a specific domain, like "*@ti.com". The idea here is to allow all internal users to post to the mailing list but restrict all external users. There are probably other special cases where this sort of thing could be useful. If Mj2 already has that capability, that's great and I would like to receive the details so that I can backfit the same concept into our Majordomo 1.94.4. If Mj2 doesn't have this capability yet, would that functionality interest anyone else? If you need somebody to develop it because of resource issues, I think my management would be willing to let me spend some time working on it. Regards, Glen Hansel ghansel@ti.com Texas Instruments From majordomo-workers-owner Tue Jan 9 08:30:13 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA16625; Tue, 9 Jan 2001 08:24:24 -0800 (PST) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (Postfix) with ESMTP id 5151717E8C for ; Tue, 9 Jan 2001 08:24:19 -0800 (PST) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id KAA17849; Tue, 9 Jan 2001 10:24:17 -0600 To: "Hansel, Glen" Cc: "'majordomo-workers@greatcircle.com'" , mj2-dev@csf.colorado.edu Subject: Re: restrict post References: <6DD22B82EC6AD31182E00008C791AC8E046F91@dleefp02.itg.ti.com> From: Jason L Tibbitts III Date: 09 Jan 2001 10:24:17 -0600 In-Reply-To: "Hansel, Glen"'s message of "Tue, 9 Jan 2001 08:57:58 -0600" Message-ID: Lines: 46 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk [This reply is also CC'd to mj2-dev] >>>>> "HG" == Hansel, Glen writes: HG> How close is the functionality and the implementation on the restrict HG> post logic in Majordomo 1.94.4 and Majordomo 2? That depends on what you're asking. Mj2 supports the restrict_post variable for backwards compatibility, but instead of keeping the addresses in a special file that you can't remotely edit, Mj2 supports an arbitrary number of "auxiliary lists" per list that you can manipulate remotely. You can restrict posting to these. You can also do restriction based on pattern matching or a host of other things. HG> We are currently running Majordomo 1.94.4 and we need more flexibility HG> with restrict post than the "mungedomain" option appears to provide. mungedomain is Mj1's method of handling "fuzzy matching" on addresses. Mj2 extends this concept greatly, but it sounds as if that's not what you're looking for. HG> In particular, we would like to have some way to easily include HG> everybody within a specific domain, like "*@ti.com". The idea here is HG> to allow all internal users to post to the mailing list but restrict HG> all external users. What you want is "access_rules", the generalized access control mechanism. To consult the list owner on posts not coming from ti.com, use a stanza like: # Consult the owner if the user's host doesn't end in "ti.com" post consult $host !~ /ti\.com$/ You can do a rather large number of things using this mechanism. You can restrict subscriptions (and indeed any command) this way as well. HG> If Mj2 already has that capability, that's great and I would like to HG> receive the details so that I can backfit the same concept into our HG> Majordomo 1.94.4. I'm not sure how you would backfit this into Mj1. Mj2 is a complete rewrite. - J< From majordomo-workers-owner Tue Jan 9 11:46:18 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id LAA18711; Tue, 9 Jan 2001 11:42:35 -0800 (PST) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (Postfix) with ESMTP id 3CE8B17E8C for ; Tue, 9 Jan 2001 11:42:30 -0800 (PST) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id NAA18425; Tue, 9 Jan 2001 13:42:27 -0600 To: Dave Wolfe Cc: "Hansel, Glen" , "'majordomo-workers@greatcircle.com'" , mj2-dev@csf.colorado.edu Subject: Re: restrict post References: <6DD22B82EC6AD31182E00008C791AC8E046F91@dleefp02.itg.ti.com> <20010109132702.A15036@firewall.austin.rr.com> From: Jason L Tibbitts III Date: 09 Jan 2001 13:42:27 -0600 In-Reply-To: Dave Wolfe's message of "Tue, 9 Jan 2001 13:27:02 -0600" Message-ID: Lines: 23 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "DW" == Dave Wolfe writes: DW> Careful! That also matches "multi.com", etc. Perhaps you meant DW> $host !~ /[@.]ti\.com$/ $host, as its name suggests, contains only the hostname, so it will never have an '@' in it. To anchor to the beginning or force a dot: $host !~ /(^|\.)ti\.com$/ perhaps, or just $host = ti.com if you know addresses won't have any extra hostnames. DW> Or am I mis-remembering what's allowed in Mj regexes? There's no difference between what you get in Perl, although we're nice and backwhack an '@' if you forget to. - J< From majordomo-workers-owner Wed Jan 10 08:30:54 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA04463; Wed, 10 Jan 2001 08:13:41 -0800 (PST) Received: from tower.ti.com (tower.ti.com [192.94.94.5]) by honor.greatcircle.com (Postfix) with ESMTP id 86E3617E8C for ; Wed, 10 Jan 2001 08:13:35 -0800 (PST) Received: from dlep6.itg.ti.com ([157.170.188.9]) by tower.ti.com (8.11.1/8.11.1) with ESMTP id f0AGD2929060; Wed, 10 Jan 2001 10:13:02 -0600 (CST) Received: from dlep6.itg.ti.com (localhost [127.0.0.1]) by dlep6.itg.ti.com (8.9.3/8.9.3) with ESMTP id KAA05482; Wed, 10 Jan 2001 10:13:01 -0600 (CST) Received: from dleefp70.itg.ti.com (dleefp70.itg.ti.com [157.170.134.90]) by dlep6.itg.ti.com (8.9.3/8.9.3) with ESMTP id KAA05476; Wed, 10 Jan 2001 10:13:01 -0600 (CST) Received: by dleefp70.itg.ti.com with Internet Mail Service (5.5.2650.21) id ; Wed, 10 Jan 2001 10:11:29 -0600 Message-ID: <6DD22B82EC6AD31182E00008C791AC8E046F93@dleefp02.itg.ti.com> From: "Hansel, Glen" To: "'Jason L Tibbitts III'" Cc: "'majordomo-workers@greatcircle.com'" , mj2-dev@csf.colorado.edu Subject: RE: restrict post Date: Wed, 10 Jan 2001 10:11:44 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk > What you want is "access_rules", the generalized access > control mechanism. > To consult the list owner on posts not coming from ti.com, > use a stanza > like: > > # Consult the owner if the user's host doesn't end in "ti.com" > post > consult > $host !~ /ti\.com$/ > > You can do a rather large number of things using this > mechanism. You can > restrict subscriptions (and indeed any command) this way as well. I'm not at all familiar with mj2 options but the above stanza appears that the original message will be sent to the owner of the mailing list if the sender is not permitted to post to this mailing list. Then the owner has the option to approve the posting of the message or to reject it. Depending on the owner, this could take hours or days or maybe never. Meanwhile the sender is thinking that his message was actually sent because he never received any error message back. Is there also another option in mj2 to automatically reject the original message and send an error back to the sender? We have implemented an automatic rejection on our mj1 and do not want to give it up when we go to mj2. Regards, Glen Hansel From majordomo-workers-owner Wed Jan 10 09:00:31 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id IAA04836; Wed, 10 Jan 2001 08:47:50 -0800 (PST) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (Postfix) with ESMTP id 3394D17E8C for ; Wed, 10 Jan 2001 08:47:45 -0800 (PST) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id KAA26977; Wed, 10 Jan 2001 10:47:43 -0600 To: "Hansel, Glen" Cc: "'majordomo-workers@greatcircle.com'" , mj2-dev@csf.colorado.edu Subject: Re: restrict post References: <6DD22B82EC6AD31182E00008C791AC8E046F93@dleefp02.itg.ti.com> From: Jason L Tibbitts III Date: 10 Jan 2001 10:47:43 -0600 In-Reply-To: "Hansel, Glen"'s message of "Wed, 10 Jan 2001 10:11:44 -0600" Message-ID: Lines: 32 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >>>>> "HG" == Hansel, Glen writes: HG> I'm not at all familiar with mj2 options but the above stanza appears HG> that the original message will be sent to the owner of the mailing list HG> if the sender is not permitted to post to this mailing list. Then the HG> owner has the option to approve the posting of the message or to reject HG> it. Correct. HG> Depending on the owner, this could take hours or days or maybe HG> never. Also correct, although the consultation will expire after a configurable amount of time. HG> Meanwhile the sender is thinking that his message was actually HG> sent because he never received any error message back. That depends. If the user is a list member, they can choose whether or not they will be notified of stalled posts (along with various other events). If the user is not a member, the nonmember_flags setting controls this. HG> Is there also another option in mj2 to automatically reject the HG> original message and send an error back to the sender? Just use "deny" in place of "consult". You can also customize the message that is sent. You can send out different messages in different circumstances. You can consult the owner for some things and reject the message for others. - J< From majordomo-workers-owner Thu Jan 18 05:47:09 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA20172; Thu, 18 Jan 2001 05:32:52 -0800 (PST) Received: from thelab.hub.org (unknown [24.71.145.220]) by honor.greatcircle.com (Postfix) with ESMTP id E79C617EC9 for ; Thu, 18 Jan 2001 05:32:45 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0IDTht54238; Thu, 18 Jan 2001 09:29:43 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 18 Jan 2001 09:28:21 -0400 (AST) From: The Hermit Hacker To: , Subject: bug in mj_shell/createlist? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk it just sort of 'hangs' there ... jan 6th build, so it might have been fixed since? mail# su - majordomo %mj_shell -p cras4zaz Entering Majordomo interactive mode. Type majordomo commands. Use the 'end' command to exit. Majordomo>createlist pgsql-interfaces-jdbc scrappy@postgresql.org ^C %mj_shell -p cras4zaz Entering Majordomo interactive mode. Type majordomo commands. Use the 'end' command to exit. Majordomo>createlist pgsql-interfaces-jdbc scrappy@postgresql.org Createlist failed. **** The "pgsql-interfaces-jdbc" list already exists. Majordomo> 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 Jan 18 06:02:15 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id FAA20370; Thu, 18 Jan 2001 05:51:00 -0800 (PST) Received: from thelab.hub.org (unknown [24.71.145.220]) by honor.greatcircle.com (Postfix) with ESMTP id 35F3B17EC1 for ; Thu, 18 Jan 2001 05:50:55 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0IDlqC54599; Thu, 18 Jan 2001 09:47:52 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 18 Jan 2001 09:46:30 -0400 (AST) From: The Hermit Hacker To: , Subject: Can't locate object method "build" via package "MIME::Entity" ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk >From today's build ... Majordomo>createlist pgsql-jdbc scrappy@postgresql.org Can't locate object method "build" via package "MIME::Entity" at blib/lib/Majordomo.pm (autosplit into blib/lib/auto/Majordomo/_createlist.al) line 4112. 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 Jan 18 07:47:50 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id HAA21593; Thu, 18 Jan 2001 07:41:07 -0800 (PST) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (Postfix) with ESMTP id 25B3917EC1 for ; Thu, 18 Jan 2001 07:41:01 -0800 (PST) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id JAA02274; Thu, 18 Jan 2001 09:40:51 -0600 To: The Hermit Hacker Cc: , Subject: Re: bug in mj_shell/createlist? References: From: Jason L Tibbitts III Date: 18 Jan 2001 09:40:50 -0600 In-Reply-To: The Hermit Hacker's message of "Thu, 18 Jan 2001 09:28:21 -0400 (AST)" Message-ID: Lines: 9 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 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> it just sort of 'hangs' there ... It sends out a message, and sometimes the MTA will take time to do something. If you turn on debugging (-D) you can find out for sure what it's doing. - J< From majordomo-workers-owner Thu Jan 18 16:49:50 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id QAA26852; Thu, 18 Jan 2001 16:38:00 -0800 (PST) Received: from epithumia.math.uh.edu (epithumia.math.uh.edu [129.7.128.2]) by honor.greatcircle.com (Postfix) with ESMTP id 461B317ECC for ; Thu, 18 Jan 2001 16:37:55 -0800 (PST) Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.9.3/8.9.3) id SAA04206; Thu, 18 Jan 2001 18:37:46 -0600 To: The Hermit Hacker Cc: , Subject: Re: mj_shell -p removelist ... References: From: Jason L Tibbitts III Date: 18 Jan 2001 18:37:46 -0600 In-Reply-To: The Hermit Hacker's message of "Thu, 18 Jan 2001 20:26:25 -0400 (AST)" Message-ID: Lines: 7 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 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> such a thing exist that I'm not finding? I think you want createlist-destroy. - J< From majordomo-workers-owner Mon Jan 22 19:32:59 2001 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-980720-1) id TAA02337; Mon, 22 Jan 2001 19:28:16 -0800 (PST) Received: from thelab.hub.org (SHW2-202.accesscable.net [24.71.145.202]) by honor.greatcircle.com (Postfix) with ESMTP id D06DF17E8B for ; Mon, 22 Jan 2001 19:28:10 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0N3QGW38214; Mon, 22 Jan 2001 23:26:16 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 22 Jan 2001 23:26:16 -0400 (AST) From: The Hermit Hacker To: , Subject: testing ... (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-workers-owner@GreatCircle.COM Precedence: bulk AFter upgrading to latest, checking that subject_prefix is set: mail# pwd /usr/local/src/majordomo mail# cd ~majordomo/lists/postgresql.org/ mail# grep subject_prefix */_config pgsql-admin/_config: 'subject_prefix' => '[ADMIN]', pgsql-announce/_config: 'subject_prefix' => '[ANNOUNCE]', pgsql-bugs/_config: 'subject_prefix' => '[BUGS]', pgsql-committers/_config: 'subject_prefix' => '[COMMITTERS]', pgsql-core/_config: 'subject_prefix' => '[CORE]', pgsql-docs/_config: 'subject_prefix' => '[DOCS]', pgsql-general/_config: 'subject_prefix' => '[GENERAL]', pgsql-hackers/_config: 'subject_prefix' => '[HACKERS]', pgsql-interfaces/_config: 'subject_prefix' => '[INTERFACES]', pgsql-jdbc/_config: 'subject_prefix' => '[JDBC]', pgsql-novice/_config: 'subject_prefix' => '[NOVICE]', pgsql-odbc/_config: 'subject_prefix' => '[ODBC]', pgsql-patches/_config: 'subject_prefix' => '[PATCHES]', pgsql-php/_config: 'subject_prefix' => '[PHP]', pgsql-ports/_config: 'subject_prefix' => '[PORTS]', pgsql-sql/_config: 'subject_prefix' => '[SQL]', it doesn't appear to be being used on my two newer lists, pgsql-jdbc and pgsql-odbc ... comparing the _config file between pgsql-hackers (where it works) and pgsql-jdbc (where it doesn't), nothing is jumpign out at me as being wrong ... help? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org ---------- Forwarded message ---------- Date: Mon, 22 Jan 2001 20:38:52 -0400 (AST) From: The Hermit Hacker To: pgsql-jdbc@postgresql.org Subject: testing ... checking the subject_prefix ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org