Mailman 3 August 2012 - Mailman-Users

nntp -> dovecot POP3
by Thufir Aug. 28, 2012

Aug. 28, 2012

I've seen mention that mailman can be used between nntp and e-mail. What I'm looking for is to send nntp messages to e-mail, just one way. I don't need a full gateway such as gmane, just one way is sufficient. Currently I'm using dovecot-postfix in Ubuntu with leafnode (http://leafnode.sourceforge.net/ )as the nntp server. What would be involved in directing mailman at leafnode, on localhost, to e-mail a particular newsgroup? thanks, Thufir

2 5

RTFM gate_news
by Thufir Aug. 27, 2012

Aug. 27, 2012

Where is the documentation for mailman gate_news and how is it configured? I'm running Leafnode on localhost and am using a dovecot-postfix mail stack on Ubuntu. How can I wire them together with mailman to export usenet messages? The best info I've found about gate_news is: http://opensource.apple.com/source/mailman/mailman-117/mailman/cron/gate_ne… I'm sure it's on GNU as well, and the usage seems not terribly difficult, at least judging the comments in the above code. Am I just not seeing the manual/tutorial? thanks, Thufir

2 3

illegal list name (FQDN & hostname)
by Thufir Aug. 27, 2012

Aug. 27, 2012

Why does mailman see or use @dur for the FQDN when it should be dur.bounceme.net? thufir@dur:~$ thufir@dur:~$ thufir@dur:~$ sudo newlist mailman Enter the email of the person running the list: hawat.thufir(a)gmail.com Initial mailman password: Create a new, unpopulated mailing list. Usage: /usr/sbin/newlist [options] [listname [listadmin-addr [admin-password]]] Options: -l language --language=language Make the list's preferred language `language', which must be a two letter language code. -u urlhost --urlhost=urlhost Gives the list's web interface host name. -e emailhost --emailhost=emailhost Gives the list's email domain name. -q/--quiet Normally the administrator is notified by email (after a prompt) that their list has been created. This option suppresses the prompt and notification. -h/--help Print this help text and exit. You can specify as many of the arguments as you want on the command line: you will be prompted for the missing ones. Every Mailman list has two parameters which define the default host name for outgoing email, and the default URL for all web interfaces. When you configured Mailman, certain defaults were calculated, but if you are running multiple virtual Mailman sites, then the defaults may not be appropriate for the list you are creating. You also specify the domain to create your new list in by typing the command like so: newlist --urlhost=www.mydom.ain mylist where `www.mydom.ain' should be the base hostname for the URL to this virtual hosts's lists. E.g. with this setting people will view the general list overviews at http://www.mydom.ain/mailman/listinfo. Also, www.mydom.ain should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if the email hostname to be automatically determined. If you want the email hostname to be different from the one looked up by the VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can specify `emailhost' like so: newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist where `mydom.ain' is the mail domain name. If you don't specify emailhost but urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST will be used for the email interface. For backward compatibility, you can also specify the domain to create your new list in by spelling the listname like so: mylist(a)www.mydom.ain where www.mydom.ain is used for `urlhost' but it will also be used for `emailhost' if it is not found in the virtual host table. Note that '--urlhost' and '--emailhost' have precedence to this notation. If you spell the list name as just `mylist', then the email hostname will be taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL (as defined in your Defaults.py file or overridden by settings in mm_cfg.py). Note that listnames are forced to lowercase. The list admin address need to be a fully-qualified address, like owner(a)example.com, not just owner. Illegal list name: mailman@dur thufir@dur:~$ thufir@dur:~$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 dur.bounceme.net # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters thufir@dur:~$ thufir@dur:~$ cat /etc/hostname dur.bounceme.net thufir@dur:~$ thufir@dur:~$ hostname dur.bounceme.net thufir@dur:~$ thufir@dur:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS" thufir@dur:~$ The help page: https://help.ubuntu.com/community/Mailman doesn't provide any troubleshooting which I see. However, I'm not the only one to get this message: http://mail.python.org/pipermail/mailman-users/2006-August/052587.html However, I see no solution available. thanks, Thufir

2 3

Group mismatch puzzle
by Lindsay Haisley Aug. 27, 2012

Aug. 27, 2012

I've set up mailman 2.1.15 on a new server, properly configured with "--with-mail-gid=mail" and I can create lists from scratch on it, and they appear to be working perfectly. I have a number of lists on an older server, however, (also running mailman) which I want to move to the new server. I have a script which I've used previously with good results to do this which creates three tarballs: * The contents of the directory /var/lib/mailman/lists/<listname> * The archive files under /var/lib/mailman/private/<listname> * The mbox file in /var/lib/mailman/private/<listname>.mbox Additionally a flag file indicates whether or not archives are public. The receiving server has a script which just undoes this, putting all the files in the right place and creating a symlink in /var/lib/mailman/public if the flag file is present indicating that the list has public archives. This script pair worked perfectly for moving lists between servers using the same Linux distribution, but at this point I'm moving from a server running Gentoo Linux to one running Ubuntu Server Linux, where the GID table is somewhat different. When I try to post to a _moved_ list, I get a failure with the following error in the mail logs: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "mail", but the system's mail server executed the mail script as group "man". Try tweaking the mail server to run the script as group "mail", or re-run configure, providing the command line option `--with-mail-gid=man'. [i.e. "mail" != "man"] It seems that the group "mail" has a GID of 12 on the old server, however this GID corresponds to the group "man" on the new server and "mail" has a GID of 8. All the group ownerships of the pickle files and archive files are proper on the new server (group "mailman") so the GID if 12 must be encoded as a number somewhere _within_ the list files imported from the old server, and when the list is put in place on new server, the GID is matched up with the group "man", and a group mismatch is flagged. Does anyone have any idea how to fix this? I can't find any way to access the mail wrapper script GID in the list web UI (which apparently is stored per-list since lists created _on_ the server work OK). I have bunch of lists to move, so this will need to be fixed. Recreating all lists manually with their thousands of administrator and user prefs is out of the question! -- Lindsay Haisley | "Real programmers use butterflies" FMP Computer Services | 512-259-1190 | - xkcd http://www.fmp.com |

2 3

Migration of old debian woody mailman server
by Peter Merritt Aug. 24, 2012

Aug. 24, 2012

I have to migrate a dead mailman server running on debian woody to a new Ubuntu server. The drive failed and I was able to image the drive to a new drive but mailman will not run, seems that their is significant problems with the current mailman installation. All the commands seem die with python tracebacks. The data directories for mailman seen to be OK. I did some research on moving a list to a new server an it seems reasonably easy. But I am concerned about moving from an older version of mailman to a newer version. Additionally, I am going to use postfix for the mta, the old server is using exim. I also notice postgres running on the old server and wonder if exim/mailman could be using to for management. I did not have time to fully research the setup, its been running unattended for 8+ years. I am looking for input about possible pitfalls and ideas to make this go easier Any help would be greatly appreciated. Peter partsmaps(a)weirdwater.org <- Do not Use

3 2

Will this cause problems for the lists?
by Steff Watkins Aug. 23, 2012

Aug. 23, 2012

Hi all, Just been reading the wonderful emails and pages about upgrading Mailman, which is a task I've had to do once before. Now one thing that really gives me the shivers is the idea of installing the new updated version of Mailman right over the old/current version as I've seen suggested a couple of time. OK, if it works for you fine but I feel that that leaves you very little room for rollback should the new version not perform quite as expected. So I currently have a nice working setup that's installed as /usr/local/mailman-2.x.x symlink'ed to /usr/local/mailman and that works just fine. It allows me to have the current version and the previous version there for comparison/rollback/experimenting. Now one thing I have noticed that has bothered me/caused me some problems with this sort of setup is that everytime I have to upgrade I have to copy all the mail-list data out, then make sure that ownerships/permissions of the mail-list data in its new location is correct. So I had an idea. What if I make a directory, /usr/local/mailman-data for instance and then symlink the data, lists and archive directories from the current active mailman directories back into this separated data directory. I've been running with this setup for a few days now and it seems to be working just fine, no complaints from users or systems. I'm also thinking that it is likely to make upgrades require less downtime as the new version can be built and linked into the current list data and then rolled over. OK, maybe not if there a file format conversion needed but in general yes. However, I'm just wondering if I may be building up a problem for myself when one of the "less frequent" Mailman processes or events occur. So is separating the data out from the mailman binaries in this way a good idea or not worth the effort? Regards, Steff Watkins ----- Steff Watkins Natural History Museum, Cromwell Road, London,SW75BD 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

Mailman: Recipient address rejected: User unknown in local recipient table
by Futchko, Rose Aug. 22, 2012

Aug. 22, 2012

Good Morning, I just finished migrating Mailman from one server to another, following the instructions at URL http://wiki.list.org/pages/viewpage.action?pageId=4030682 I am running Mailman version is 2.1.15 But now I am seeing the following error in my /var/log/maillog "NOQUEUE: reject: RCPT from unknown[]: 550 5.1.1 <external IP Address>: Recipient address rejected: User unknown in local recipient table; from=<d> to=<> proto=ESMTP helo=<[]>" Here is my postconf -n output: alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 html_directory = no inet_protocols = all mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, list.$mydomain mydomain = informs.org myhostname = mail.informs.org myorigin = $myhostname newaliases_path = /usr/bin/newaliases.postfix readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES recipient_delimiter = + sample_directory = /usr/share/doc/postfix-2.6.6/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtpd_recipient_restrictions = permit_mynetworks reject_unauth_destination unknown_local_recipient_reject_code = 550 Here is my mm_cfg.py config file: DEFAULT_URL_HOST = 'list.informs.org' DEFAULT_EMAIL_HOST = 'list.informs.org' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) MTA = 'Postfix' ************* Can someone please counsel as to how to correct this error? Thank you, Rose Rose Futchko Director of Information Technology INFORMS 7240 Parkway Drive, Suite 300 Hanover, MD 21076 Rose.Futchko(a)INFORMS.org 443.757.3500

2 1

is bin/find_members available from web interface directly ?
by Bruce Harrison Aug. 21, 2012

Aug. 21, 2012

I know I can do a subscribe/unsubscribe via a web call: List a member: http://example.com/mailman/admin/<listname>/members?findmember=<email-address>&setmemberopts_btn&adminpw=<adminpassword> Is it possible to call the /bin/find_member script to retrieve a list of lists a person is subscribed to? Is there another way to get this particular bit of information? Bruce Harrison UT Martin

2 1

Mailman Problems under OSX Lion
by David Dodell Aug. 21, 2012

Aug. 21, 2012

This list is my last hope on getting my problems fixed. I am running OSX Lion (not Mountain Lion). Mailman was part of the default installation. I have two issues which I have gotten absolutely no help from Apple Enterprise Support ... basic answer, we don't support open source software and couldn't answer me on why they installed / advertised mailing lists but don't support it ... but I regress. (1) First issue is cosmetic. At the bottom of each administrative page, mailman does not display the icons which I see on ever other mailman website ... basically the mailman / python logos. Not a real big deal, besides the cosmetic irk. I've checked the docs, found the path in the config file, and sure enough the images are there in the path, but they still do not display. Ideas? (2) Second issue is more serious. I can't get list moderation to work. A message comes in to be moderator, I get email notification of this. However, if I login to the administrator page, "pending moderator requests", if I try to approve, reject, or any other command on that page, NOTHING happens ... the message keeps appearing, no action is taken etc. I've repaired all permissions, but besides that, lost on what to try next. Would appreciate any insight. Thank you. David Dodell

8 18

Problem when creating new lists
by David Renstrom Aug. 21, 2012

Aug. 21, 2012

Hi, Everytime I create a new list using the Web interface in Mailman I get the following error: Bug in Mailman version 2.1.14 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. The file /etc/mailman/Virtual-mailman has changed ownership from mailman to apache. I have to change it manually and then run the genaliases and postmap commands to make the system work correctly again. Could someone please tell me what's wrong because I'm kinda lost? See below for more info. Content of /var/log/mailman/error: Aug 20 23:54:13 2012 (29703) command failed: /usr/sbin/postalias /etc/mailman/aliases (status: 1, Operation not permitted) Aug 20 23:54:13 2012 admin(29703): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(29703): [----- Mailman Version: 2.1.14 -----] admin(29703): [----- Traceback ------] admin(29703): Traceback (most recent call last): admin(29703): File "/usr/lib/mailman/scripts/driver", line 112, in run_main admin(29703): main() admin(29703): File "/usr/lib/mailman/Mailman/Cgi/create.py", line 56, in main admin(29703): process_request(doc, cgidata) admin(29703): File "/usr/lib/mailman/Mailman/Cgi/create.py", line 239, in process_request admin(29703): sys.modules[modname].create(mlist, cgi=1) admin(29703): File "/usr/lib/mailman/Mailman/MTA/Postfix.py", line 238, in create admin(29703): _update_maps() admin(29703): File "/usr/lib/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps admin(29703): raise RuntimeError, msg % (acmd, status, errstr) admin(29703): RuntimeError: command failed: /usr/sbin/postalias /etc/mailman/aliases (status: 1, Operation not permitted) admin(29703): [----- Python Information -----] admin(29703): sys.version = 2.7.1 (r271:86832, Apr 12 2011, 16:15:16) [GCC 4.6.0 20110331 (Red Hat 4.6.0-2)] admin(29703): sys.executable = /usr/bin/python admin(29703): sys.prefix = /usr admin(29703): sys.exec_prefix = /usr admin(29703): sys.path = ['/usr/lib/mailman/pythonlib', '/usr/lib/mailman', '/usr/lib/mailman/scripts', '/usr/lib/mailman', '/usr/lib64/python27.zip', '/usr/lib64/python2.7/', '/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages'] admin(29703): sys.platform = linux2 admin(29703): [----- Environment Variables -----] admin(29703): HTTP_COOKIE: SESSae9265d1ff1a26d16ed53a0ed247816c=i2mjdepcbf7rgac7kgreaeh2t3; SESSd6dc799775a4e319c149c4959a84efa2=vah0edt1d26euphiurqulrncd1 admin(29703): SERVER_SOFTWARE: Apache/2.2.21 (Fedora) admin(29703): SCRIPT_NAME: /mailman/create admin(29703): SERVER_SIGNATURE: <address>Apache/2.2.21 (Fedora) Server at www.ungasynskadade.se Port 80</address> admin(29703): admin(29703): REQUEST_METHOD: POST admin(29703): SERVER_PROTOCOL: HTTP/1.1 admin(29703): QUERY_STRING: admin(29703): CONTENT_LENGTH: 151 admin(29703): HTTP_USER_AGENT: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.0; Trident/5.0) admin(29703): HTTP_CONNECTION: Keep-Alive admin(29703): HTTP_REFERER: http://www.ungasynskadade.se/mailman/create admin(29703): SERVER_NAME: www.ungasynskadade.se admin(29703): REMOTE_ADDR: 94.254.99.6 admin(29703): SERVER_PORT: 80 admin(29703): SERVER_ADDR: 91.123.204.174 admin(29703): DOCUMENT_ROOT: /var/www/html admin(29703): PYTHONPATH: /usr/lib/mailman admin(29703): SCRIPT_FILENAME: /usr/lib/mailman/cgi-bin/create admin(29703): SERVER_ADMIN: root@localhost admin(29703): HTTP_HOST: www.ungasynskadade.se admin(29703): HTTP_CACHE_CONTROL: no-cache admin(29703): REQUEST_URI: /mailman/create admin(29703): HTTP_ACCEPT: text/html, application/xhtml+xml, */* admin(29703): GATEWAY_INTERFACE: CGI/1.1 admin(29703): REMOTE_PORT: 59287 admin(29703): HTTP_ACCEPT_LANGUAGE: sv admin(29703): CONTENT_TYPE: application/x-www-form-urlencoded admin(29703): HTTP_ACCEPT_ENCODING: gzip, deflate Cheers, /David R.

2 1