[Mailman-Users] Migrating many lists
Hi We have just installed Mailman and are in the process of testing the system. Part of our migration from Lyris to Mailman involves the moving over of approx. 70 lists to Mailman. These are are classified as open, closed, moderated, unmoderated etc. Some of these lists have their own list specific footers and headers, welcome docs etc. I'd like to know which is the best and most efficient way to create these lists. Do we just create them one at a time or is there a tool or template that allows for mass migration of lists that have similar settings. Thanks Rakshika ** Rakshika Bhana, [EMAIL PROTECTED] Health Systems Trust http://www.hst.org.za Tel: (031) 307 2954 Fax: (031) 304 0775 -- 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
Re: [Mailman-Users] Our Mailman web server is listening on port 81
04-Dec-03 at 22:45, Sasa Stupar ([EMAIL PROTECTED]) wrote : Our Mailman web server is listening on port 81 (not 80). I modified the config lines in mm_cfg.py to read... DEFAULT_URL_HOST = 'mail.stginternational.com:81' DEFAULT_EMAIL_HOST = 'stginternational.com' ...but all the links that Mailman creates omit the :81 portion of the URL, and therefore are incorrect. Example: After changing in mm_cfg.py run this: $prefix/bin/withlist -l -r fix_url mailman Did you notice the part in Defaults.py thus: # If you don't need to change DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in # your mm_cfg.py, then you're done; the default mapping is added # automatically. If however you change either variable in your # mm_cfg.py, then be sure to also include the following: # # add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) Regards, -- Simon White. Internet Consultant, Linux/Windows Server Administration. email, dns and web servers; php javascript perl asp; MySQL MSSQL Access Bridging the gap between management, HR and the tech team. -- 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
Re: [Mailman-Users] Set GID ?
04-Dec-03 at 16:27, Brent Shafer ([EMAIL PROTECTED]) wrote : I have the set to User: mailman - r,w,e (read, write, execute capabilities) Group: mailman - r,w,e Everybody: r,w,e This is not secure. This is not what you are told to do by the documentation. Setting something to rwx rwx rwx (usually we use x for execute rather than e, because that's how ls -l displays it...) is something I have never found necessary. Ever. checking permissions on /usr/local/mailman... configure: error: * Installation directory /usr/local/mailman is not configured pr operly! * Set-gid bit must be set for directory: /usr/local/mailman [EMAIL PROTECTED] mailman-2.1.3]$ To What am I supposed to set the gid, and how am I supposed to get that accomplished? /usr/local/mailman should look something like this: drwxrwsr-x 21 root mailman 4096 Sep 6 15:41 mailman This is clear in the documentation: Watch out if your site does something like mount /usr/local with the nosuid option. This will break Mailman, which relies on set-gid programs for its security. If this describes your environment, simply install Mailman in a location that allows setgid programs. Make sure the install directory is set to group `mailman' (or whatever you're going to specify as --with-groupname) and has the setgid bit set (but see README.BSD if you're on a BSD system). You probably also want to guarantee that this directory is readable and executable by everyone. For example, these shell commands will accomplish this: % cd $prefix % chgrp mailman . % chmod a+rx,g+ws . In your case, $prefix can be replaced by /usr/local/mailman, unless /usr or /usr/local are mounted nosuid. Regards, -- Simon White. Internet Consultant, Linux/Windows Server Administration. email, dns and web servers; php javascript perl asp; MySQL MSSQL Access Bridging the gap between management, HR and the tech team. -- 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
Re: [Mailman-Users] Migrating many lists
Hi We have just installed Mailman and are in the process of testing the system. Part of our migration from Lyris to Mailman involves the moving over of approx. 70 lists to Mailman. These are are classified as open, closed, moderated, unmoderated etc. Some of these lists have their own list specific footers and headers, welcome docs etc. I'd like to know which is the best and most efficient way to create these lists. Do we just create them one at a time or is there a tool or template that allows for mass migration of lists that have similar settings. There are three things you'll want to export and import. Two of them will be easy, the third one, which is what you're specifically asking about, is trickier. You'll need to do the following for *each* list: For exporting members, use the members.pl script which is found in the collection of scripts found in the URL I am providing below. You'll need to take the resulting file and break it into two text files, one for normal users, the other for digest users. You'll then use these as input for the mailman command that adds members, which is add_members. For each list you'll do this after the list is created. For exporting message archives, use the 'exp-arc.pl script. This will create mbox files that can be used to recreate pipermail versions of the archives once your mailman list is created. Finally - and this is what you were specifically asking about - there is a script called list-exp.pl that exports a list's settings into a text file. In theory you could use the resultant data as input for the mailman commands that create and configure your lists, which are newlist and create_list respectively. Here is the URL where will you find an assortment of Lyris scripts, including the ones I mentioned: http://www.lyris.com/products/listmanager/lm_6.1/scripts.html (should this be added to a FAQ somwhere? I suspect there will be more people who will migrate from Lyris to Mailman due to criminally exorbitant licensing fees, a desire to support open source instead, etc.) - Kevin -- 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] Unsubscribe without a password
Hello We have created a new mailman list and would have created an unsubscribe page for the users of the list however we are having problems unsubscribing the users without the need of a password. Can mailman be setup to allow the users to unsubscribe without a password. Our version is 2.0.13 Thank-you Jon -- 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
Re: [Mailman-Users] Unsubscribe without a password
05-Dec-03 at 13:17, Jon ([EMAIL PROTECTED]) wrote : We have created a new mailman list and would have created an unsubscribe page for the users of the list however we are having problems unsubscribing the users without the need of a password. Can mailman be setup to allow the users to unsubscribe without a password. Our version is 2.0.13 If you make your own subscribe page which takes the email address and adds it to a text file, you can schedule a task every night to read that file and unsubscribe the addresses in it. I have a version of this theory working on a server using PHP, a little shell script, and cron. Let me know if it's of any use to you. Regards, -- Simon White. Internet Consultant, Linux/Windows Server Administration. email, dns and web servers; php javascript perl asp; MySQL MSSQL Access Bridging the gap between management, HR and the tech team. -- 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] virtual host
Hello, sorry about my english, i'm not speak this language. I'm configuring a web/mail/ftp/ssh/etc-server. I'm using Mailman with Postfix to manage lists, and I have problems with the virtual domains. I have about 350 virtual hosts in this server but I can't configure the lists created to respond or to deliver the messages received. I use debian woody, Postfix, Apache 1.3.28... Thanks! Omar Liberatto HYPERLINK mailto:[EMAIL PROTECTED][EMAIL PROTECTED] BDU - Biblioteca Digital Universal HYPERLINK http://www.bdu.com.ar/http://www.bdu.com.ar Suscríbase a nuestro boletín literario El Boletín! HYPERLINK mailto:[EMAIL PROTECTED][EMAIL PROTECTED] Capital Federal - Argentina --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.445 / Virus Database: 250 - Release Date: 21/01/2003 -- 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] Problem with html messages in Mailman 2.1.2
HTML messages are properly passes on to non-digest members but not to digest members or to the archives. In both cases, the message is converted to a link but when one executes the link, the html code is shown instead of being converted ot a GUI page. Jacques -- Jacques L'Heureux, Columbia, Maryland -- -- 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
Re: [Mailman-Users] Our Mailman web server is listening on port 81
Hi,
I have the same problem:
I include in mm_cfg.py
DEFAULT_URL_HOST = 'myhost.com:port'
DEFAULT_EMAIL_HOST = 'my host.com'
add_virtualhost('myhost.com:port', 'my host.com' )
but the links omit the port in the URL.
Thanks in advance,
Ana
- Original Message -
From: Simon White [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 05, 2003 9:13 AM
Subject: Re: [Mailman-Users] Our Mailman web server is listening on port 81
04-Dec-03 at 22:45, Sasa Stupar ([EMAIL PROTECTED]) wrote :
Our Mailman web server is listening on port 81 (not 80). I
modified the config lines in mm_cfg.py to read...
DEFAULT_URL_HOST = 'mail.stginternational.com:81'
DEFAULT_EMAIL_HOST = 'stginternational.com'
...but all the links that Mailman creates omit the :81 portion
of the URL, and therefore are incorrect. Example:
After changing in mm_cfg.py run this:
$prefix/bin/withlist -l -r fix_url mailman
Did you notice the part in Defaults.py thus:
# If you don't need to change DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in
# your mm_cfg.py, then you're done; the default mapping is added
# automatically. If however you change either variable in your
# mm_cfg.py, then be sure to also include the following:
#
# add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
Regards,
--
Simon White. Internet Consultant, Linux/Windows Server Administration.
email, dns and web servers; php javascript perl asp; MySQL MSSQL Access
Bridging the gap between management, HR and the tech team.
--
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/ammdv62%40tid.es
--
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
Re: [Mailman-Users] Our Mailman web server is listening on port 81
05-Dec-03 at 16:37, Ana ([EMAIL PROTECTED]) wrote :
Hi,
I have the same problem:
I include in mm_cfg.py
DEFAULT_URL_HOST = 'myhost.com:port'
DEFAULT_EMAIL_HOST = 'my host.com'
add_virtualhost('myhost.com:port', 'my host.com' )
but the links omit the port in the URL.
I think you are supposed to put
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
as you have already defined these above.
You may also have to run
bin/withlist -l -r fix_url listname
Regards,
--
Simon White. Internet Consultant, Linux/Windows Server Administration.
email, dns and web servers; php javascript perl asp; MySQL MSSQL Access
Bridging the gap between management, HR and the tech team.
--
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] Subscribing to several lists at once? / Customized confirmation subjects
Hi! Because no native newsletter software seems to fit the newsletter requirements of a customer (not even close), we've chosen Mailman 2.1.x for this purposes, because we already have very good experiences with earlier Mailman versions, as well for mailing lists as for newsletters. And the 2.1 versions also have several more goodies useful for newsletters. But still some more or less important problems seems unsolved: We already have a form like http://www.debian.org/MailingLists/subscribe where you fill in your e-mail address just once and then select, on which lists you want to be subscribed. Currently, that script sends out a bunch of subscribe mails to the appropriate addresses. But currently the user will get one confirmation mail for each list he'd like to subscribe instead of a single one. Is there a possibility in Mailman to process a bunch of list subscriptions for a single user like one subscription, i.e. so that only one confirm mail is required? Anyone already had similiar problems? Another little customization thingy: IIRC Mailman 2.0.x had confirmation mail subjects looking like this: | listname -- confirmation of subscription -- request XX The new ones look just like this: | confirm Is it easily possible to customize this subject to be a little bit more understandable for a non-english speaking, non-technical audience, e.g. by a descriptive prefix in the configured language? Or do I need to patch Mailman and/or create new locales? And how do others deal with those horrible old Win95 mail clients (X-Mailer: Internet Mail Service (5.X..XX)) which break the subject by adding an additonal white space auf 60 or 70 characters? E.g. I customized an older Mailman version with a few German texts, e.g. the above mentioned old confirmation subject, so that it read like this: | Listname -- Bitte um Bestaetigung der Anmeldung -- Anfrage 388443 What I got back from a customer was this: | Subject: WG: Listname -- Bitte um Bestaetigung der Anmeldung -- Anfra | ge 388443 My shorthack solution was to write a Perl (Jehova! ;-) wrapper, which fixed the subject before passing it to Mailman. How are (were) others dealing with this problem? (It should not only happen with customized versions of Mailman but also with long list names and the umodified Mailman version.) Kind regards, Axel Beckert -- - Axel Beckert ecos electronic communication services gmbh it security solutions * dynamic web applications * consulting Mail: Tulpenstrasse 5 D-55276 Dienheim near Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 939-220 WWW:http://www.ecos.de/ Fax: +49 6133 939-333 - -- 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
Re: [Mailman-Users] shell script to make consolidated list from other lists?
On Friday 05 December 2003 01:01 am, Simon White wrote: 04-Dec-03 at 15:43, Dennis Black ([EMAIL PROTECTED]) wrote : Hmmm uniq -u means print only unique lines. uniq -d means only duplicate lines. uniq only works well if sort is applied first. add_members / sync_members will ignore dupes anyway (but sort then uniq might be quicker). tr is not obligatory but I can see what you're getting at (changing case so that everyone's emails are in lower case for both lists). Yep, I noticed this problem also in testing. I'd do something a bit more like (replace $prefix with path to mailman) # get member lists into the temp file $prefix/bin/list_members the-a-list /tmp/abc.wk1 $prefix/bin/list_members the-b-list /tmp/abc.wk1 # convert everything to lower case tr '[A-Z]' '[a-z]' /tmp/abc.wk1 /tmp/abc.wk2 I noticed in mm 2.1.x that list_members returns all lowercase unless you provide a flag to return original case as entered, so this isn't necessary. # deduplicate from 2nd temp file and overwrite 1st temp file, to save # counting upwards all the time; we could do this on one line and pipe # to another pipe and so on... but separating isn't such a bad thing sort -d /tmp/abc.wk2 | uniq /tmp/abc.wk1 # now sync back to the list $prefix/bin/sync_members -w=no -f /tmp/abc.wk1 the-big-list I now have a working script! So thanks again to all for your ideas and feedback! Regards, John -- 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
Re: [Mailman-Users] please help
On Thu, 2003-12-04 at 23:18, Shane Messer wrote: Man, I really hate to send a stupid email like this, but I have searched for the past hour trying to figure out a very simple problem, with no luck. I use a web company for hosting and I have no root access. I am provided use of the mailman script, v2.13. The problem is that I am trying to figure out a way to do a mass removal of all the users on a list without having to go through each letter and check them off, letter by letter. Here is what I have tried. 1.I tried to do a * in the mass removal. Doesn't work. 2.I tried to come up with a way to get an entire list on the screen at once, so I could do a mass removal with that list. No luck. Again, I only have access to the web interface and not the command line, so can you tell me a way to simply wipe all the users in the list quickly? Or simply list them and then I can drop the list into the mass removal box? I work for a vodka company (www.extremebeverage.com), so I will be happy to send lots of free samples to someone who can answer my question! :-) Thanks, Shane With an offer like that, who could refuse! Write a small robot script to access the admin website and do the check boxes for you. Linux has some very nice scripting tools that will help you out (links and wget come to mind). I've used them in the past to do load testing on web-sites. I setup them up to walk entire web trees multiple times. The principle is the same so with a bit of patience you should have something that will hammer away on the admin pages for you in a few minutes. Good Luck - Jon Carnes -- 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
Re: [Mailman-Users] Mailman won't send mail
Wow, great problem report... It looks to me like your Postfix is delivering the mail to Mailman, Mailmanctl is running and trying to drop the mail out to the specified SMTPHOST # SMTP host and port, when DELIVERY_MODULE is 'SMTPDirect'. # Make sure the # host exists and is resolvable (i.e., if it's the # default of localhost be # sure there's a localhost entry in your /etc/hosts file!) SMTPHOST = 'localhost' In your case the SMTPHOST is ns1.tcbug.org. Does this resolve? Is Postfix setup to accept mail from this IP address? I would switch back to using SMTPHOST = 'localhost' and then set that to 127.0.0.1 in my /etc/hosts file, then setup Postfix to relay any local posts from 127.0.0.1 It sounds like the problem is in Postfix. It looks like it is not allowing relay from the locally running Mailman application. Check out the error and warning logs for Postfix. Good Luck - Jon Carnes On Fri, 2003-12-05 at 13:36, Josh Paetzel wrote: I'm having an issue getting Mailman to send mail out to my mailing list. I've searched Google extensively, read the Mailman FAQ, and can't seem to get an answer to my problem. Sorry for the length of this email, but I'm going to try and be as complete as possible the first time around. According to the FAQ the following information should be listed: Mailman version - 2.1.3 How it was installed - FreeBSD ports system Version of OS - FreeBSD 5.2-BETA The MTA - Postfix 2.0.16,1 I've gone through the troubleshooting tips in the FAQ section 3.14 Brief Description of the Problem: Emails sent to my mailing list are silently absorbed by the mailman system. They don't bounce, they just appear to disappear. Mailman Configuration: Here's a copy of my mm_cfg.py # Put YOUR site-specific settings below this line. DEFAULT_URL = 'http://tcbug.org/cgi-bin/mailman' DEFAULT_EMAIL_HOST = 'tcbug.org' DEFAULT_URL_HOST= 'tcbug.org' MAILMAN_OWNER = '[EMAIL PROTECTED]' % DEFAULT_HOST_NAME SMTPHOST= 'ns1.tcbug.org' Logs: Here is the output of several of the logs on the system: /var/log/maillog contains the following when I try to send a mail: Dec 5 17:54:06 ns1 postfix/local[38668]: 3786EBA0A: to=[EMAIL PROTECTED], relay=local, delay=6, status=sent (|/usr/local/mailman/mail/mailman post tcbug) /usr/local/mailman/logs/error is empty /usr/local/mailman/logs/post: Dec 05 17:59:48 2003 (38597) post to tcbug from [EMAIL PROTECTED], size=1994, message-id=[EMAIL PROTECTED], 20 failures (There are 20 members on the mailing list in question) /usr/local/mailman/logs/smtp: Dec 05 17:54:09 2003 (38597) All recipients refused: (61, 'Connection refused') Dec 05 17:54:09 2003 (38597) [EMAIL PROTECTED] smtp for 1 recips, completed in 0.046 seconds Dec 05 17:54:09 2003 (38597) All recipients refused: (61, 'Connection refused') Dec 05 17:54:09 2003 (38597) [EMAIL PROTECTED] smtp for 1 recips, completed in 0.110 seconds /usr/local/mailman/logs/smtp-error: Dec 05 17:54:09 2003 (38597) delivery to [EMAIL PROTECTED] failed with code -1: ignore Dec 05 17:54:09 2003 (38597) delivery to [EMAIL PROTECTED] failed with code -1: ignore ...this is followed by similar messages for each of the members of the list. Just for kicks I've apt-get installed Mailman on a debian 3.0 box I have laying around, along with Postfix 2.0.x and everything works perfectly out of the box. I've been tearing my hair out trying to see what's different between the two installations, but I can't find it. Any and all advice, suggestions, clues, feats of magic, or beatings with the clue stick would be greatly appreciated. Thanks, Josh Paetzel [EMAIL PROTECTED] -- 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/jonc%40nc.rr.com -- 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
Re: [Mailman-Users] List admin abandons a list
On Fri, 2003-12-05 at 19:42, Rod Neep wrote: I have had a list admin (of three lists) *abandon* the mailing lists for which he was responsible. Unfortunately, he did this about three weeks ago without my knowledge and without any notice, and I only discovered the problem this evening. Moreover he just deleted his email address as list admin, leaving the field *blank*. Is there any way to prevent this happening again? For example, for the admin address to default to something else if left blank, or better still, for Mailman to inform me if an admin address is blank? Rod Sounds like a great job for a cron script! Try the ~mailman/bin/list_admins command in a cron script and add a bit of logic, and Viola! You will never be caught by surprise again - though this is the first time I've ever heard of this particular problem. Jon Carnes -- 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
RE: [Mailman-Users] adding subscriber names
There is a script called add_members in the ~mailman/bin directory. Fyi, D. Darwin Sanoy Principal Consultant and Trainer DesktopEngineer.com DesktopEngineerTraining.com --- Don't Think Out of the Box, Burn It --- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Smith Sent: Thursday, December 04, 2003 11:23 AM To: [EMAIL PROTECTED] Subject: [Mailman-Users] adding subscriber names Greetings- I have a question: is there a method to add the subscriber names, in addition to e-mail addresses, en masse? That would be really usefule to me. GNU Peace, Ron Carson Octadyne Systems -- 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/darwin%40desktopenginee r.com -- 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
Re: [Mailman-Users] please help
On 05 Dec 2003 19:55 , Jon Carnes [EMAIL PROTECTED] sent: On Thu, 2003-12-04 at 23:18, Shane Messer wrote: Man, I really hate to send a stupid email like this, but I have searched for the past hour trying to figure out a very simple problem, with no luck. I use a web company for hosting and I have no root access. I am provided use of the mailman script, v2.13. The problem is that I am trying to figure out a way to do a mass removal of all the users on a list without having to go through each letter and check them off, letter by letter. Here is what I have tried. 1. I tried to do a * in the mass removal. Doesn't work. 2. I tried to come up with a way to get an entire list on the screen at once, so I could do a mass removal with that list. No luck. Again, I only have access to the web interface and not the command line, so can you tell me a way to simply wipe all the users in the list quickly? Or simply list them and then I can drop the list into the mass removal box? I work for a vodka company (www.extremebeverage.com), so I will be happy to send lots of free samples to someone who can answer my question! :-) Thanks, Shane With an offer like that, who could refuse! Write a small robot script to access the admin website and do the check boxes for you. Linux has some very nice scripting tools that will help you out (links and wget come to mind). I've used them in the past to do load testing on web-sites. I setup them up to walk entire web trees multiple times. The principle is the same so with a bit of patience you should have something that will hammer away on the admin pages for you in a few minutes. can you send the [EMAIL PROTECTED] subject: who password to get the entire list? of change the mungled public view to show real address, do a list, cut and paste it into the mass removal, and there you go, then switch it back to the mungled view of the address you --at- domain dot com --- Chris McKeever If you want to reply directly to me, please use cgmckeever--at--prupref---dot---com http://www.prupref.com Prudential Preferred Properties www.prupref.com -- 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
