[Mailman-Users] Program to Change List Real Name
Mailman Folks, Who do I convert these manual instructions into a program? bin/withlist bar m.real_name='bar' m.Lock() m.Save() m.Unlock() ^D Thanks. Jim -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Cannot Lock Mailing Lists
Mailman Gurus, I'm running Mailman 2.1.14 CPanel Version. When I try to update a mailing list with config_list or with_list, the program hangs. # ../bin/withlist fuustl-coffeehourchat_lists.firstuustlouis.org Loading list fuustl-coffeehourchat_lists.firstuustlouis.org (unlocked) The variable `m' is the fuustl-coffeehourchat_lists.firstuustlouis.org MailList instance m.real_name = 'fuustl-coffeehourchat' m.Lock() [never returns] I tried retarting Mailman. How do I get Mailman to allow updates? Jim -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Program to Change List Real Name
On 6/1/11 8:51 PM, UUN Hostmaster wrote: Mailman Folks, Who do I convert these manual instructions into a program? bin/withlist bar m.real_name='bar' m.Lock() m.Save() m.Unlock() ^D First of all, that is wrong. the m.Lock() will reload the list object and undo the m.real_name='bar'. Just add -l to the withlist command and don't do either m.Lock() or m.Unlock(). To make a script, put something like def rename_list(mlist): if not mlist.Locked(): mlist.Lock() mlist.real_name = mlist.internal_name() mlist.Save() mlist.Unlock() in a file named rename_list.py in Mailman's bin/ directory and then you can run bin/withlist -r rename_list bar However, if this is cPanel there may be problems with the above. Mark, Thank you. What kinds of problems do you anticipate with cPanel Mailman? I looked at the config_list of a CPanel Mailman mailing list: list-name_domain-name.tld. It appears like a normal Mailing installation except that the real_name = list-name Otherwise, the folders and files are named list-name_domain-name.tld I am migrating some Majordomo Mailing lists to a CPanel Mailman installation. Thanks. Jim Jim -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Program to Change List Real Name
On 6/2/2011 2:13 PM, UUN Hostmaster wrote: Mark Sapiro wrote: I am migrating some Majordomo Mailing lists to a CPanel Mailman installation. So what are you really trying to accomplish? If you create the lists with cPanel's list create process (as opposed to Mailman's bin/newlist) they should get the appropriate real_name. Mark, I can't use the cPanel Web Interface because I have too many mailing lists to create. If I use the Mailman newlist command to create list-name_domain-name.tld, I need to change the real_name from list-name_domain-name.tld to list-name. Also, I have to create my own entries in the /etc/valiases/domain-name.tld file. I found a program that will extract the needed information from the Majordomo files: majordomo2mailman.pl. I had to modify parts of the program to add the real_name and host_name, so I could create the list-name_domain-name.tld for the newlist command. I modified your python program to fit my needs: def rename_list(mlist): if not mlist.Locked(): mlist.Lock() mlist.real_name = mlist.internal_name().split(_ + mlist.host_name)[0] mlist.Save() mlist.Unlock() It works. Jim -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Outbox Flooded
Red Hat 9.0 with Mailman using Postfix as the MTA, we've managed to flood the outbox (whatever that is) with thousands of accidental messages that resulted from a series of poor choices in the setup. A nasty situation is upon us, sending out countless unintened (and unwanted) messages in the name of Mailman. We are despirately trying to discover the origin, queue, or otherwise staging file of the messages so we can pre-empt their transfer. The majority of these are messages generated from automated notifications within Mailman. I have attempted to use a previously recommended prompt command (postsuper -d ALL but this seems to only empty the Postfix queue. The messasges keep coming! It appears they are being genereated and then delivered to Postfix. Does anyone have an idea where we can terminate the messages before they get to Postfix and are sent? Nathan Morgan 972-231-9300 www.jbagroup.net -- Please Note The information in this E-mail message is legally privileged and confidential information intended only for the use of the individual(s) named above. If you, the reader of this message, are not the intended recipient, you are hereby notified that you should not further disseminate, distribute, or forward this E-mail message. If you have received this E-mail in error, please notify the sender. Thank you -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Clear Cache
On our maiden voyage, we were mass subscribing to our list when we realized it was sending the subscription message for each address. We decided we did not want this, so we stopped the MTA. Now, we have lots of unsent messages in the cache that we'd like to remove. Does anyone happen to know how to clear the cache/queue? Nathan Morgan 972-231-9300 www.jbagroup.net -- Please Note The information in this E-mail message is legally privileged and confidential information intended only for the use of the individual(s) named above. If you, the reader of this message, are not the intended recipient, you are hereby notified that you should not further disseminate, distribute, or forward this E-mail message. If you have received this E-mail in error, please notify the sender. Thank you -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Initial Configuration
I have apparently successfully installed Mailman on a Red Hat 9.x server but now am faced with initial configuration questions. I was able to set the password using /var/mailman/bin/mmsitepass but am not sure what I am suppose to edit in /var/mailman/Mailman/mm_cfg.py for my site, or the significance of the /var/mailman/bin/upd update. Can I get a heads up on what needs to be configured to make this work? Thanx a heap! -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman and Apache suEXEC with Virtual Hosts
I searched all the archives and FAQ. Has anyone solved the problem of getting Mailman 2.1 to run in a Virtual Host with Apache 1.3 suEXEC? Would it work to create a second Name-Based VirtualHost (mailman.domain.tld) for each IP-Based Domain (www.domain.tld) with the VirtualHost User.Group specified as mailman.mailman? Does Mailman require that the directories be setgid or just require that the user.group be mailman.mailman? Does this old solution still work? Begin Forwarded Message Date:11/17/99 8:41 PM Received:11/18/99 12:59 AM From:Doug Muth - Suespammers.org SysAdmin, doug at suespammers.org To: Tom Geller, tom at tgeller.com On Mon, Nov 15, 1999 at 10:13:45AM -0800, Tom Geller wrote: I posted a note to Mailman-Users with your offer of documentation for suEXEC, and two people wrote me privately to say, Sure, I'm interested. So I think it's worth writing up. (Feel free to forward this in it's entirety) On the system I administer (A Redhat 6.0 installation) we are running suEXEC so that users can safely run CGIs. However, this presents difficulties with Mailman, since its CGIs are SGID so that, in a normal environment, any user can run it. That being said, here's how to set up an installation of Mailman in an suEXEC environment: 1. Create your installation directory. I used /usr/local/apache/htdocs/mailman on my system. I have mailman in the /usr/local/apache/htdocs directory since that is root to suEXEC. 2. You'll need to create a Mailman user, then chgrp the directory to the Mailman user so that the configure script doesn't complain. Then, chmod 2755 the directory since configure also wants it to be SGID. 3. Run configure like this: ./configure --prefix=/usr/local/apache/htdocs/mailman --with-cgi-gid=doug --with-mail-gid=your_mailservers_gid 4. Make install 5. Change ownership on the Mailman installation to the user owning it. chmod -R doug.doug /usr/local/apache/htdocs/mailman worked for me. 6. chmod u-s,g-s the contents of the cgi-bin directory so that suEXEC doesn't complain about trying to run a SUID/SGID program. 7. chmod g-w cgi-bin so that suEXEC doesn't complain about the directory being writable by others. 8. Configure the webserver(s) using Mailman with the User and Group directive to be set accordingly. 9. Proceed with the other steps in the mailman installation, but be sure that it's done in terms of the user that you set this up, NOT mailman. In fact, after configure is run, you should be able to safely delete the mailman user and his home directory, as they will not be needed anymore. If anyone has any questions or comments, I'm not on the Mailman-users list, so feel free to write me directory at dmuth at suespammers.org! Cheers, -- Doug Muth -- http://www.claws-and-paws.com/ -- Whois: DTM47 Suespammers.org SysAdmin and BOFH *** http://www.suespammers.org/ - End Forwarded Message - -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] RE: digest sent to list posting address, why?
hmm, well, if no ideas, can anyone confirm whether or not this is expected or unexpected behavior? would a list of related settings from the admin webgui be useful? tia, ~steven -Original Message- From: Steven [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 04, 2002 7:28 PM To: '[EMAIL PROTECTED]' Subject: digest sent to entire list, why? Hi, I'm running 2.0.11 One of my new lists sent the first digest to the list posting address today from [EMAIL PROTECTED] 'on behalf of' [EMAIL PROTECTED] to [EMAIL PROTECTED] Coincidentally(?) the time stamp matched that of a post I had approved and which was sent at the same time as the digest. It was a simple plain text post I'd approved (mime is disabled for the list in question.) My impression had been, from the digest settings I'd chosen in the admin webgui, that the digest would only be sent to list members who had opted to receive the digest instead of separate posts. I'm baffled by the digest having been mailed to the list posting address and therefore all members of the list. (and a thought which just came to mind, will the digest be included in the next digest since it went to the list address? ug.) I've searched the admin webgui settings and found nothing, I've read the readmes and found nothing, I searched http://www.python.org/cgi-bin/faqw-mm.py with all the strings and search types I could think of and came up with nothing. I browsed through the TOC there and found nothing. What am I overlooking? How do I prevent the digest from being sent to the entire list via the list's posting address? I had 7 unsubs within 10 minutes of that going out, so I'd like to prevent a repeat. tia, ~steven -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Re: [Mailman-Users] RE: digest sent to list posting address, why?
thanks for the idea chuq, but I'm fairly certain the the 'on belhalf of' is a result of mailman's Show member addrs so they're not directly recognizable as email addrs? feature under 'privacy options' which I do have set to 'yes' for the list in question. Full headers on the message in question follow here: Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: (qmail 26787 invoked from network); 4 Jun 2002 21:45:08 - Received: from unknown (HELO rattletrap.shults.org) ([216.231.50.34]) (envelope-sender [EMAIL PROTECTED]) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for [EMAIL PROTECTED]; 4 Jun 2002 21:45:08 - Received: from rattletrap.shults.org (localhost.localdomain [127.0.0.1]) by rattletrap.shults.org (8.11.6/8.11.2) with ESMTP id g54Lk3001611 for [EMAIL PROTECTED]; Tue, 4 Jun 2002 14:46:03 -0700 Date: Tue, 04 Jun 2002 14:45:04 -0700 Message-ID: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: discussion digest, Vol 1 #1 - 20 msgs X-Mailer: Mailman v2.0.11 MIME-version: 1.0 Content-type: multipart/mixed; boundary=216.231.50.34.503.1589.1023227104.823.6791 To: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: [EMAIL PROTECTED] X-Reply-To: [EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED]?subject=help List-Post: mailto:[EMAIL PROTECTED] List-Subscribe: http://lists.shakespeare-monologues.org/mailman/listinfo/discussion, mailto:[EMAIL PROTECTED]?subject=subscribe List-Id: A discussion list with an online archive brfor users of shakespeare-monologues.org discussion.lists.shakespeare-monologues.org List-Unsubscribe: http://lists.shakespeare-monologues.org/mailman/listinfo/discussion, mailto:[EMAIL PROTECTED]?subject=unsubscribe On Wed, 5 Jun 2002, Chuq Von Rospach wrote: On 6/5/02 4:43 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: One of my new lists sent the first digest to the list posting address today from [EMAIL PROTECTED] 'on behalf of' [EMAIL PROTECTED] to [EMAIL PROTECTED] Did you check the Received: lines to make sure this thing didn't make a round trip through some user's mail client? Because that on behalf of sounds an awful lot like it got forwarded or redirected. Take a look at a set of full headers to see whether maybe it got sent out normally, and then someone who received it did this to you Um, for you. Um... -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Re: [Mailman-Users] RE: digest sent to list posting address, why?
DOH! I just compared those headers to another email. Delivered-to: uh, seems I subscribed that address to test the digest and promptly forgot I'd done so. I'll just go stand in the corner now. Thanks for listing, hope it provided some amusement at least. *sheepish grin* ~steven On Wed, 5 Jun 2002 [EMAIL PROTECTED] wrote: thanks for the idea chuq, but I'm fairly certain the the 'on belhalf of' is a result of mailman's Show member addrs so they're not directly recognizable as email addrs? feature under 'privacy options' which I do have set to 'yes' for the list in question. Full headers on the message in question follow here: Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: (qmail 26787 invoked from network); 4 Jun 2002 21:45:08 - Received: from unknown (HELO rattletrap.shults.org) ([216.231.50.34]) (envelope-sender [EMAIL PROTECTED]) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for [EMAIL PROTECTED]; 4 Jun 2002 21:45:08 - Received: from rattletrap.shults.org (localhost.localdomain [127.0.0.1]) by rattletrap.shults.org (8.11.6/8.11.2) with ESMTP id g54Lk3001611 for [EMAIL PROTECTED]; Tue, 4 Jun 2002 14:46:03 -0700 Date: Tue, 04 Jun 2002 14:45:04 -0700 Message-ID: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: discussion digest, Vol 1 #1 - 20 msgs X-Mailer: Mailman v2.0.11 MIME-version: 1.0 Content-type: multipart/mixed; boundary=216.231.50.34.503.1589.1023227104.823.6791 To: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: [EMAIL PROTECTED] X-Reply-To: [EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED]?subject=help List-Post: mailto:[EMAIL PROTECTED] List-Subscribe: http://lists.shakespeare-monologues.org/mailman/listinfo/discussion, mailto:[EMAIL PROTECTED]?subject=subscribe List-Id: A discussion list with an online archive brfor users of shakespeare-monologues.org discussion.lists.shakespeare-monologues.org List-Unsubscribe: http://lists.shakespeare-monologues.org/mailman/listinfo/discussion, mailto:[EMAIL PROTECTED]?subject=unsubscribe On Wed, 5 Jun 2002, Chuq Von Rospach wrote: On 6/5/02 4:43 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: One of my new lists sent the first digest to the list posting address today from [EMAIL PROTECTED] 'on behalf of' [EMAIL PROTECTED] to [EMAIL PROTECTED] Did you check the Received: lines to make sure this thing didn't make a round trip through some user's mail client? Because that on behalf of sounds an awful lot like it got forwarded or redirected. Take a look at a set of full headers to see whether maybe it got sent out normally, and then someone who received it did this to you Um, for you. Um... -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
[Mailman-Users] remove email address from Mailman-Footer?
Hi, I've searched high and low and have either missed the answer to this during my search or it's very well hidden. How to I remove, hide or munge the list-owner's address from the Mailman-Footer to protect it from being scooped up by spambots? I'm speaking particularly of this phrase at the bottom of the listinfo page for a list: ListName list run by [EMAIL PROTECTED] ListName administrative interface (requires authorization) tia, ~steven -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
[Mailman-Users] bin/newlist hangs after initial password entered
system: redhat 7.1 with all available updates for packages that I have installed. versions of related packages: mailman-2.0.11 Python 1.5.2 sendmail 8.11.6-2.7.1 apache 1.3.22-1.7.1 so, I've doubled checked all the steps in the INSTALL file and the related README files. When I run cd to /home/mailman and run bin/newlist, it hangs after I enter the password at the Initial $listname password: prompt. I've given it as long as 15 minutes, and it still just sits there. I'd expect it to prompt me to confrim the password at the point, but alas, nothing. I've tried running newlist as both root and mailman (both su'd to those accounts and having logged in directly with those accounts via ssh) here's the command exactly as I'm running it and the first few prompts up to the time it hangs: [root@rattletrap mailman]# bin/newlist -o nloutput Enter the name of the list: test Enter the email of the person running the list: steven_at_shults.org Initial test password: and that's where it hangs Here's what I find in /var/log/messages while waiting for a response: May 27 18:12:55 rattletrap sshd(pam_unix)[16170]: session opened for user root by (uid=0) and here's what I get after giving up on newlist and hitting ^c (ctrl-c): Traceback (innermost last): File bin/newlist, line 220, in ? main() File bin/newlist, line 169, in main mlist.Create(listname, owner_mail, pw) File /home/mailman/Mailman/MailList.py, line 786, in Create self.__lock.lock() File /home/mailman/Mailman/LockFile.py, line 286, in lock self.__sleep() File /home/mailman/Mailman/LockFile.py, line 424, in __sleep time.sleep(interval) KeyboardInterrupt [root@rattletrap mailman]# any ideas folks? tia, ~steven -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
