From majordomo-users-owner@greatcircle.com Mon Dec 3 14:11:08 2007 Received: from skywalker.dahl-stamnes.net (38.80-203-206.nextgentel.com [80.203.206.38]) by mycroft.greatcircle.com (Postfix) with ESMTP id E1D64D81E8 for ; Mon, 3 Dec 2007 14:11:07 -0800 (PST) Received: from jedi.dahl-stamnes.net (jedi.dahl-stamnes.net [194.213.166.140]) by skywalker.dahl-stamnes.net (8.13.1/8.13.1) with ESMTP id lB3MB4Wm021071 for ; Mon, 3 Dec 2007 23:11:04 +0100 Received: from jedi.dahl-stamnes.net (jedi.dahl-stamnes.net [127.0.0.1]) by jedi.dahl-stamnes.net (8.13.4/8.13.4) with ESMTP id lB3MB4HN017996 for ; Mon, 3 Dec 2007 23:11:04 +0100 Received: from localhost (localhost [[UNIX: localhost]]) by jedi.dahl-stamnes.net (8.13.4/8.13.4/Submit) id lB3MB4Kp017994 for majordomo-users@greatcircle.com; Mon, 3 Dec 2007 23:11:04 +0100 From: =?iso-8859-1?q?J=F8rn_Dahl-Stamnes?= Reply-To: mr.domo@dahl-stamnes.net To: majordomo-users@greatcircle.com Subject: majordomo and MySQL Date: Mon, 3 Dec 2007 23:11:04 +0100 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200712032311.04296.mr.domo@dahl-stamnes.net> X-Archive-Number: 200712/1 X-Sequence-Number: 5702 Hello folks, Is there any way to 'attach' a mailinglist to an SQL database containing th= e=20 e-mail adresses? Today I have a script on one host that extract the e-mail adresses from a=20 MySQL database and copy the files to the majordomo/Lists directory. The script extract two files - one that is used to tell who is allowed to p= ost=20 to the list and one file that is the list itself. =2D-=20 J=F8rn Dahl-Stamnes homepage: http://www.dahl-stamnes.net/dahls/ From majordomo-users-owner@greatcircle.com Mon Dec 3 14:35:53 2007 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3137AD80AB for ; Mon, 3 Dec 2007 14:35:52 -0800 (PST) Received: from mail.sonny.com (mcafee.sonny.com [192.168.1.3]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0JSH001TDW3L1P@mail.sonny.com> for majordomo-users@greatcircle.com; Mon, 03 Dec 2007 16:35:45 -0600 (CST) Received: from [192.168.1.68] (magnum.sonny.com [192.168.1.68]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0JSH00302W3LI0@mail.sonny.com> for majordomo-users@greatcircle.com; Mon, 03 Dec 2007 16:35:45 -0600 (CST) Date: Mon, 03 Dec 2007 16:30:52 -0600 From: Daniel Liston Subject: Re: majordomo and MySQL In-reply-to: <200712032311.04296.mr.domo@dahl-stamnes.net> To: mr.domo@dahl-stamnes.net Cc: majordomo-users@greatcircle.com Message-id: <4754839C.70707@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 8BIT User-Agent: Thunderbird 1.5.0.12 (X11/20071019) References: <200712032311.04296.mr.domo@dahl-stamnes.net> X-Archive-Number: 200712/2 X-Sequence-Number: 5703 Are you asking a majordomo question or a SQL question? What benefit do you gain by storing the mailing list in two places? I am sure you already see the down side of how much extra time it takes retrieving data from the SQL container, only to write it where and how majordomo would have written it natively. To someone with only a hammer, everything looks like a nail. Jørn Dahl-Stamnes wrote: > Hello folks, > > Is there any way to 'attach' a mailinglist to an SQL database containing the > e-mail adresses? > > Today I have a script on one host that extract the e-mail adresses from a > MySQL database and copy the files to the majordomo/Lists directory. > > The script extract two files - one that is used to tell who is allowed to post > to the list and one file that is the list itself. > From majordomo-users-owner@greatcircle.com Mon Dec 3 14:46:11 2007 Received: from skywalker.dahl-stamnes.net (38.80-203-206.nextgentel.com [80.203.206.38]) by mycroft.greatcircle.com (Postfix) with ESMTP id B4DDCD80AB for ; Mon, 3 Dec 2007 14:46:10 -0800 (PST) Received: from jedi.dahl-stamnes.net (jedi.dahl-stamnes.net [194.213.166.140]) by skywalker.dahl-stamnes.net (8.13.1/8.13.1) with ESMTP id lB3Mk95c021276 for ; Mon, 3 Dec 2007 23:46:09 +0100 Received: from jedi.dahl-stamnes.net (jedi.dahl-stamnes.net [127.0.0.1]) by jedi.dahl-stamnes.net (8.13.4/8.13.4) with ESMTP id lB3Mk9fQ018582 for ; Mon, 3 Dec 2007 23:46:09 +0100 Received: from localhost (localhost [[UNIX: localhost]]) by jedi.dahl-stamnes.net (8.13.4/8.13.4/Submit) id lB3Mk9rm018581 for majordomo-users@greatcircle.com; Mon, 3 Dec 2007 23:46:09 +0100 From: =?iso-8859-1?q?J=F8rn_Dahl-Stamnes?= Reply-To: mr.domo@dahl-stamnes.net To: majordomo-users@greatcircle.com Subject: Re: majordomo and MySQL Date: Mon, 3 Dec 2007 23:46:08 +0100 User-Agent: KMail/1.8 References: <200712032311.04296.mr.domo@dahl-stamnes.net> <4754839C.70707@sonny.org> In-Reply-To: <4754839C.70707@sonny.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200712032346.09003.mr.domo@dahl-stamnes.net> X-Archive-Number: 200712/3 X-Sequence-Number: 5704 On Monday 03 December 2007 23:30, Daniel Liston wrote: > Are you asking a majordomo question or a SQL question? What benefit do y= ou > gain by storing the mailing list in two places? I am sure you already see > the down side of how much extra time it takes retrieving data from the SQL > container, only to write it where and how majordomo would have written it > natively. > > To someone with only a hammer, everything looks like a nail. Because I have a place where people register themself as a user (ref.=20 http://www.dahl-stamnes.net/Stmbk/) and I whish to make a list where some=20 users shall be allowed to send emails to all registered users. When they ar= e=20 registered as a user they are automatically in the list. A user may change his profile (which contain both a primary and a secondary= =20 e-mail adresse) and I want majordomo to use the adresses stored in the SQL= =20 database. I know that other mailing lists are able to use SQL databases directly, so = why=20 can't majordomo use it? Today it works by using a perl script which create the files. But since the= =20 script is run by cron, it may cause delays. =2D-=20 J=F8rn Dahl-Stamnes homepage: http://www.dahl-stamnes.net/dahls/ From majordomo-users-owner@greatcircle.com Mon Dec 3 15:43:27 2007 Received: from mailbox.onlinepolicy.net (mailbox.onlinepolicy.net [209.237.247.99]) by mycroft.greatcircle.com (Postfix) with ESMTP id BC26219CE47 for ; Mon, 3 Dec 2007 15:43:26 -0800 (PST) Received: from [172.24.16.114] (rdmsw.xensource.com [69.84.254.194]) by mailbox.onlinepolicy.net (Postfix) with ESMTP id 10C8873624; Mon, 3 Dec 2007 15:43:26 -0800 (PST) Message-ID: <4754949D.3000005@queernet.org> Date: Mon, 03 Dec 2007 15:43:25 -0800 From: "Roger B.A. Klorese" User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Daniel Liston CC: mr.domo@dahl-stamnes.net, majordomo-users@greatcircle.com Subject: Re: majordomo and MySQL References: <200712032311.04296.mr.domo@dahl-stamnes.net> <4754839C.70707@sonny.org> In-Reply-To: <4754839C.70707@sonny.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200712/4 X-Sequence-Number: 5705 Daniel Liston wrote: > Are you asking a majordomo question or a SQL question? What benefit > do you > gain by storing the mailing list in two places? There's no benefit at all to storing it in two places. But many modern MLM's store lists in databases and select the target addresses at send-time, instead of keeping them in a flat file. That's likely what he's asking, and the answer is that, no, Majordomo 1 does not do it. Majordomo 2 does, but it's not very efficient, and it has some specific schema requirements. From majordomo-users-owner@greatcircle.com Mon Dec 3 16:27:43 2007 Received: from QMTA09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96]) by mycroft.greatcircle.com (Postfix) with ESMTP id BB990D81EA for ; Mon, 3 Dec 2007 16:27:42 -0800 (PST) Received: from OMTA05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by QMTA09.emeryville.ca.mail.comcast.net with comcast id LPYx1Y00L0vp7WL0A04r00; Tue, 04 Dec 2007 00:27:46 +0000 Received: from [192.168.1.128] ([24.61.94.0]) by OMTA05.emeryville.ca.mail.comcast.net with comcast id LQTj1Y00A00UbZk0800000; Tue, 04 Dec 2007 00:27:46 +0000 X-Authority-Analysis: v=1.0 c=1 a=cjzb7ZWKZyoA:10 a=5l-7njzsAAAA:8 a=LtK-aOiQhx3I0u5yDn4A:9 a=L9U_G3JkuJOme7qCFGwA:7 a=YMOo8NUkTpk-yKwEgodK02nx1dkA:4 a=5WZzfXpOq_gA:10 Mime-Version: 1.0 Message-Id: Date: Mon, 3 Dec 2007 19:27:34 -0500 To: Daniel Liston From: John Watkins Subject: Re: Newbie and the replacelist command--second request Cc: Majordomo-users Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Archive-Number: 200712/5 X-Sequence-Number: 5706 In response to the previous messages, what is involved in getting information about the replace list function and installing it? Does anyone know who might have a copy and be able to advise me? At 2:18 PM -0600 11/17/07, Daniel Liston wrote: >John, replacelist is not a standard majordomo command. If your old isp >would like to contribute to majordomo, we would be happy to evaluate it >for inclusion in a future release. ;) Thanks. I've tried to get in touch with them but don't have much help. In the weeks before I changed suppliers, the old one wasn't operating and didn't reply to queries. > >On the other hand, if you have the membership list and the config file >from your list, I am fairly sure your new provider can help you get it >back into operation. I do have both. Is that all that's needed? Can I just substitute the old config file for the new one? Or must the new provider do something more. They frankly say they make majordomo available but don't support it, suggesting greatcircle instead. -- Working together, we can create a simpler, more humane society that actually solves its problems, treats everyone fairly, and helps everyone achieve their full potential. John Watkins Founder and Creative Director The Alliance for Human Empowerment 379 Amherst Street #234, Nashua, NH 03063 http://humanemp.org From majordomo-users-owner@greatcircle.com Mon Dec 3 18:13:51 2007 Received: from mail.scasey.com (206-169-90-115.static.twtelecom.net [206.169.90.115]) by mycroft.greatcircle.com (Postfix) with ESMTP id 44BD0D80DD for ; Mon, 3 Dec 2007 18:13:50 -0800 (PST) Received: (qmail 21951 invoked from network); 4 Dec 2007 02:13:46 -0000 Received: from unknown (HELO ?192.168.1.100?) (70.171.220.23) by 0 with SMTP; 4 Dec 2007 02:13:46 -0000 Message-ID: <4754B7D8.5080008@scaseyllc.com> Date: Mon, 03 Dec 2007 19:13:44 -0700 From: Sean Casey User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: [Fwd: Re: majordomo and MySQL] Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Archive-Number: 200712/6 X-Sequence-Number: 5707 Once again I didn't pay attention to the To: on my reply. Sean -------- Original Message -------- Jørn Dahl-Stamnes wrote: > On Monday 03 December 2007 23:30, Daniel Liston wrote: >> Are you asking a majordomo question or a SQL question? What benefit do you >> gain by storing the mailing list in two places? I am sure you already see >> the down side of how much extra time it takes retrieving data from the SQL >> container, only to write it where and how majordomo would have written it >> natively. >> >> To someone with only a hammer, everything looks like a nail. > > Because I have a place where people register themself as a user (ref. > http://www.dahl-stamnes.net/Stmbk/) and I wish to make a list where some > users shall be allowed to send emails to all registered users. When they are > registered as a user they are automatically in the list. > > A user may change his profile (which contain both a primary and a secondary > e-mail adresse) and I want majordomo to use the adresses stored in the SQL > database. > I know that other mailing lists are able to use SQL databases directly, so why > can't majordomo use it? > > Today it works by using a perl script which create the files. But since the > script is run by cron, it may cause delays. > What I have done to allow web-based "registration" is have the perl script send the email to majordomo. I also have (at times) either 1) written a log file or 2) updated a database, to capture non-majordomo related information about the registration, but have passed the zubzcription on to majordomo via his email interface, and eliminated the hassle of trying to update or maintain the lists/ file outside the majordomo environment/process. This also allows the request to trigger the confirm, moderation, or any other processes configured for the list with no effort on my part beyond "composing" and sending the email to majordomo. http://aok.net/lists HTH Sean From majordomo-users-owner@greatcircle.com Mon Dec 3 21:40:50 2007 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8D5AFD81C2 for ; Mon, 3 Dec 2007 21:40:49 -0800 (PST) Received: from mail.sonny.com (mcafee.sonny.com [192.168.1.3]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0JSI0011OFRO6Z@mail.sonny.com> for majordomo-users@greatcircle.com; Mon, 03 Dec 2007 23:40:36 -0600 (CST) Received: from [192.168.1.68] (magnum.sonny.com [192.168.1.68]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0JSI00406FRNFB@mail.sonny.com> for majordomo-users@greatcircle.com; Mon, 03 Dec 2007 23:40:36 -0600 (CST) Date: Mon, 03 Dec 2007 23:35:43 -0600 From: Daniel Liston Subject: Re: Newbie and the replacelist command--second request In-reply-to: To: Majordomo-users Cc: John Watkins Message-id: <4754E72F.7050808@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5.0.12 (X11/20071019) References: X-Archive-Number: 200712/7 X-Sequence-Number: 5708 John Watkins wrote: >> On the other hand, if you have the membership list and the config file >> from your list, I am fairly sure your new provider can help you get it >> back into operation. > > I do have both. Is that all that's needed? Can I just substitute the old > config file for the new one? Or must the new provider do something more. > They frankly say they make majordomo available but don't support it, > suggesting greatcircle instead. > The following information is available in the list-owner-info document that comes with the majordomo files from greatcircle, so you can ignore the misleading "undocumented" statement below. ;) The "undocumented" commands for use by list owners are: * approve passwd {subscribe|unsubscribe} list [address] This is so that you can approve subscription or unsubscription actions that need approval by the list owner. Note that this is just a standard "subscribe" or "unsubscribe" command prefixed with "approve password" (where you substitute the password for your list, which is listed above, for "password"). * approve passwd who list This allows you to get the list of addresses for your anonymous list. Without the password, even the list owner can not see who is on the list. * passwd list old_passwd new_passwd This is so you can change the password for your list, if you desire. * newintro list password This is so that you can replace the information file that people get when they do "intro list" or "subscribe list". It reads everything after the "newintro" command to end-of-message or the word "EOF" on a line by itself as the new intro for the list. * newinfo list password This replaces the information file that people get when they do "info list". (This file is also sent by "subscribe list" if the intro file doesn't exist.) This reads everything after the "newinfo" command to end-of-message or the word "EOF" on a line by itself as the new info for the list. * config list password Retrieves a self-documenting configuration file for the list list. The password can be the password contained in the file list.passwd or the admin_password in the configuration file. * newconfig list password Validates and installs a new configuration file. It reads everything after the "newconfig" command to end-of-message or the word "EOF" on a line by itself as the new info for the list. The config file is expected to be a complete config file as returned by "config". Incremental changing of the config file is not yet supported. As soon as the config file is validated and installed its settings are available for use. This is useful to remember if you have multiple commands in your mail message since they will be subject to the settings of the new config file. If there is an error in the config file (incorrect value...), the config file will not be accepted and the error message identifying the problem line(s) will be returned to the sender. Note that only the error messages are returned to the sender not the entire config file, so it would be a good idea to keep a copy of your outgoing email message. * writeconfig list password Write a new config file in standard form. Writeconfig forces a rewrite of the config file with all default values in place (or current values if the config file already exists). It is useful to use after an upgrade of Majordomo since it will add the new keywords for people to change. It also updates the documentation in the file if that has changed. * mkdigest digest list name password mkdigest digest list name digest outgoing alias password Generate a digest immediately without waiting to reach the maxlength given in the config file. The first form will cause the digest to be sent to an alias found by appending "-outgoing" to the digest list name. Because this can be a security concern, the second form allows specification of the name of the alias that the outgoing digest will be sent to.