Mailman 3 August 2010 - Mailman-Users

Multiple mailing list admin with a single login
by Steff Watkins 13 Aug '10

13 Aug '10

Hello, is there a way to setup a user login so that once they've logged in they'd automatically have admin/moderator rights over certain selected lists without having to log in to each list individually? Thanks, Steff --------------- Steff Watkins Natural History Museum, Cromwell Road, London, SW7 5BD Systems programmer Email: s.watkins(a)nhm.ac.uk Systems Team Phone: +44 (0)20 7942 6000 opt 2 ======== Many were increasingly of the opinion that they'd all made a big mistake in coming down from the trees in the first place. And some said that even the trees had been a bad move, and that no one should ever have left the oceans. - HHGTTG

2 1

"Own" files in .../mailman/lists ?
by Frank Elsner 12 Aug '10

12 Aug '10

Hello *, for various reasons I need to save some information about a list in a file (besides the .pck file) for easy access. Will it affect mailman operation if I place this file (e.g. list.info) in .../mailman/lists directory? Or should I use a different location? Thanks in advance. --Frank Elsner

3 4

How to send "mailman-owner" emails to more than one site admin
by Anthony Whyte 11 Aug '10

11 Aug '10

We are running Mailman 2.1.9 and I've included below a sample alias entries email that is sent to the mailman-owner whenever we create a new list. The question I have is how does one configure Mailman to post such alerts as that below to more than a single site administrator? Cheers, Anthony Whyte Sakai Foundation / University of Michigan ----------------------------------------------------------- Begin forwarded message: > From: mailman-owner(a)collab.sakaiproject.org > Date: August 10, 2010 10:45:38 AM EDT > To: mailman-owner(a)collab.sakaiproject.org > Subject: Mailing list creation request for list test > > The mailing list `test' has been created via the through-the-web > interface. In order to complete the activation of this mailing list, the > proper /etc/aliases (or equivalent) file must be updated. The program > `newaliases' may also have to be run. > > Here are the entries for the /etc/aliases file: > > test: "|/usr/lib/mailman/mail/mailman post test" > test-admin: "|/usr/lib/mailman/mail/mailman admin test" > test-bounces: "|/usr/lib/mailman/mail/mailman bounces test" > test-confirm: "|/usr/lib/mailman/mail/mailman confirm test" > test-join: "|/usr/lib/mailman/mail/mailman join test" > test-leave: "|/usr/lib/mailman/mail/mailman leave test" > test-owner: "|/usr/lib/mailman/mail/mailman owner test" > test-request: "|/usr/lib/mailman/mail/mailman request test" > test-subscribe: "|/usr/lib/mailman/mail/mailman subscribe test" > test-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe test"

3 2

moderate using SSH..
by Khalil Abbas 10 Aug '10

10 Aug '10

hi, is there a way to view and accept or reject held messages using command line via SSH instead of opening the web interface? Thanks..

3 2

Alias problem?
by Jian Gao 09 Aug '10

09 Aug '10

I know my question has been asked before many times. I tried to google out a solution myself and struggled two days with failure. So I came here to ask and hope you can help me. I setup an email server, installed postfix, courier, mysql(virtual domain/user), clamav, spamassassin, MailScanner. I have tested and all works fine. (Server OS is Centos 5.5) Then I installed mailman by "yum install mailman". Basically followed instruction from here: http://davmp.kimanddave.com/2008/03/30/installing-mailman-to-use-https-on-c… After create the mailman list, I added two subscribers and test the mail list. The maillog shows: |Aug 5 14:00:26 mail postfix/virtual[2984]: C5C3142F01CB: to=<mailman(a)mydomain.com>, relay=virtual, delay=0.4, delays=0.37/0.02/0/0.01, dsn=5.1.1, status=bounced (unknown user: "mailman(a)mydomain.com")| It seems postfix couldn't find the alias, am I right? Here is some of my configurations: [root@mail ~]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases,hash:/etc/mailman/alias broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 header_checks = regexp:/etc/postfix/header_checks html_directory = no inet_interfaces = all mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = mail.mydomain.com, localhost, localhost.localdomain myhostname = mail.mydomain.com mynetworks = 127.0.0.0/8 newaliases_path = /usr/bin/newaliases.postfix proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES sample_directory = /usr/share/doc/postfix-2.3.3/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_tls_cert_file = /etc/postfix/smtpd.cert smtpd_tls_key_file = /etc/postfix/smtpd.key smtpd_use_tls = yes transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf unknown_local_recipient_reject_code = 550 virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_create_maildirsize = yes virtual_gid_maps = static:5000 virtual_mailbox_base = /home/vmail virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_limit_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailbox_limit_maps.cf virtual_mailbox_limit_override = yes virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_maildir_extended = yes virtual_maildir_limit_message = "The user you are trying to reach is over quota." virtual_overquota_bounce = yes virtual_uid_maps = static:5000 ============================================ [root@mail ~]# cat /etc/mailman/aliases # This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE # unless you know what you're doing, and can keep the two files properly # in sync. If you screw it up, you're on your own. # The ultimate loop stopper address mailman-loop: /var/lib/mailman/data/owner-bounces.mbox # STANZA START: mailman # CREATED: Thu Aug 5 13:42:42 2010 mailman: "|/usr/lib/mailman/mail/mailman post mailman" mailman-admin: "|/usr/lib/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman" mailman-join: "|/usr/lib/mailman/mail/mailman join mailman" mailman-leave: "|/usr/lib/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/lib/mailman/mail/mailman owner mailman" mailman-request: "|/usr/lib/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/lib/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman" # STANZA END: mailman ================================================= [root@mail mailman]# cat /etc/mailman/mm_cfg.py # -*- python -*- # Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. """This module contains your site-specific settings. From a brand new distribution it should be copied to mm_cfg.py. If you already have an mm_cfg.py, be careful to add in only the new settings you want. Mailman's installation procedure will never overwrite your mm_cfg.py file. The complete set of distributed defaults, with documentation, are in the file Defaults.py. In mm_cfg.py, override only those you want to change, after the from Defaults import * line (see below). Note that these are just default settings; many can be overridden via the administrator and user interfaces on a per-list or per-user basis. """ ############################################### # Here's where we get the distributed defaults. from Defaults import * import pwd, grp ################################################## # Put YOUR site-specific settings below this line. ############################################################## # Here's where we override shipped defaults with settings # # suitable for the RPM package. # MAILMAN_UID = pwd.getpwnam('mailman')[2] MAILMAN_GID = grp.getgrnam('mailman')[2] ############################################################## # Set URL and email domain names # # # Mailman needs to know about (at least) two fully-qualified domain # names (fqdn) # # 1) the hostname used in your urls (DEFAULT_URL_HOST) # 2) the hostname used in email addresses for your domain (DEFAULT_EMAIL_HOST) # # For example, if people visit your Mailman system with # "http://www.dom.ain/mailman" then your url fqdn is "www.dom.ain", # and if people send mail to your system via "yourlist(a)dom.ain" then # your email fqdn is "dom.ain". DEFAULT_URL_HOST controls the former, # and DEFAULT_EMAIL_HOST controls the latter. Mailman also needs to # know how to map from one to the other (this is especially important # if you're running with virtual domains). You use # "add_virtualhost(urlfqdn, emailfqdn)" to add new mappings. # Default to using the FQDN of machine mailman is running on. # If this is not correct for your installation delete the following 5 # lines that acquire the FQDN and manually edit the hosts instead. #from socket import * #try: # fqdn = getfqdn() #except: # fqdn = 'mm_cfg_has_unknown_host_domains' DEFAULT_URL_HOST = 'mail.mydomain.com' DEFAULT_EMAIL_HOST = 'mydomain.com' add_virtualhost('mail.mydomain.com', 'mydomain.com') # Because we've overriden the virtual hosts above add_virtualhost # MUST be called after they have been defined. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) ############################################################## # Put YOUR site-specific configuration below, in mm_cfg.py . # # See Defaults.py for explanations of the values. # # Note - if you're looking for something that is imported from mm_cfg, but you # didn't find it above, it's probably in Defaults.py. MTA = 'Postfix' ============================= Thanks for help. Jian

2 6

Re: [Mailman-Users] mailman install problems (syntax error at line 1: `; ' unexpected)
by Gary R. Schmidt 07 Aug '10

07 Aug '10

On Thu, August 5, 2010 07:14, CJ Keist wrote: > Hi, > Trying to install mailman mailman-2.1.13rc on Solaris 10x86. > Getting an error when I try to do make install. I found similar post on > this error on making sure using correct version of python. I have two > version of python installed, there is the native python that comes with > Solaris, version 2.4.6, and then I installed a newer version from > Blastwave 2.6.2. It doesn't matter what version I use, still get same > error with make install. > > setenv PATH > /usr/bin:/usr/sbin:/opt/csw/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/sfw/bin [SNIP] Don't do this stuff in csh, use sh or bash. Set your path so that Blastwave/OpenCSW is searched first: PATH=/opt/csw/bin:/usr/bin:/usr/sbin:/usr/ccs/bin:/usr/openwin/bin:/usr/sfw/bin export PATH Cheers, Gary B-)

5 11

can you temporarily disable individual lists?
by Alan Rubin 06 Aug '10

06 Aug '10

Hello, Is it possible to temporarily disable an individual mailing list? I'm not referring to 'emergency moderation' - this doesn't work when the current moderator may be prone to errors, etc. Regards, Alan Rubin Unix Systems Administrator Midrange Server Group, Data Centre Services Department of Business and Employment Northern Territory Government Phone: +61 (08) 8999 5111 Fax: +61 (08) 8999 7493 e-Mail: alan.rubin(a)nt.gov.au

6 9

HELP of sorts
by Dave Foran 05 Aug '10

05 Aug '10

Group I had Mailman installed and running well on my old Fedora Core 3 box I got a new system and install CentOS 5.0 and mailman-2.1.9-4.el5.i386 is installed and working I ported all the data from /var/lib/mailman/ from the old, to the new system and it is working well to a point I tried to create a new list from the mailman/admin page and I get an error I am not authorized to create lists The only issue I see is I have 2 mailman site lists. One that was ported over and one that got created when mailman starting running on teh new system Last night I was getting a messge that Oops we have a bug while trying to get to the "menu" of public lists. That has cleared up, and now I have the issue of trying to create a new list but get the above error. ( I did create the list from the command line so I am out of the water) I thought about deleteing the 2 sitelists, taring the remaining, and maybe uninstall and reinstalling mailman, Create a new site list and un-tar the remaining back Might some one have some insight on how to proceed to correct my errors THANKS Dave --- --------------------------------------------------------------------------- Dave Foran Internet ONLY:dave@hamnet.org Cruise Missile Coordinates 41.36.46N 81.25.53W ---------------------------------------------------------------------------

2 1

mail is getting misdirected
by Goodman, William 04 Aug '10

04 Aug '10

Hi all, I'm using version 2.1.12rc1 on CentOS 5.2 64 bit and postfix-2.3.3-2. I thought I configured mailman correctly, but I have issues when list members reply to al messages, this is the issue when I post a message from mylist(a)lists.jcvi.org<mailto:mylist@lists.jcvi.org> it is sent to all subscribers, however when they try to respond the users are automatically responding to mylist(a)jcvi.org<mailto:mylist@jcvi.org>. Why is mailman truncating the lists.jcvi.org ? Where is the configured in mailman or postfix ? Please help I need to upgrade my OS and software but now I know my list server is not working as designed. Bill

2 1

making my mailman archives searchable on my intranet
by Syn, Joonho 04 Aug '10

04 Aug '10

I"m trying to make our internal list archives searchable by my co-workers on our intranet. Anyone else out there done something similar not using Namazu? If so, what did you use and what were the pitfalls you ran across?

3 3